twisted pair metering system...(symbol by iec 62053-52) direct connectrd: ct connected: accuracy...

Israel Electric Corp Central Metering unit Specification # 306-5-03-15

Israel Electric Corp Central Metering unit of 197

I read and understand Signature __________________

TWISTED PAIR METERING SYSTEM

SPECIFICATION

SPEC # 306-5-03-15

VERSION 1.0

06.05.2015

IECo Catalog No. 3966298 2109148

Connection MODE Direct , CT connected

Measuring elements structure (symbol by IEC 62053-52)

Direct connectrd:

CT connected:

Accuracy classes by IEC standards

Direct connected: 2 IEC62053-21

3 IEC62053-23

CT connected 1 IEC 62053-21

2 IEC62053-23




All general chapters such as RAM, list of deliverables, acceptance tests – refer to all

components.

Since no unified formalism this spec uses a single terminology "twisted pair". The terms

line pair, twisted communication pair – mean the same.

Main responsible personnel:

Person name role Signature/date

Asher Yonai Tender coordinator

Edward Feinstein Type test labs representative expert

Netzah Calamaro National Meters unit Metrologist

Eliezer Abramowitz Comm. and meters specialist

Itzhak Mashiach Electrical and remote Metering

department

Michael Levi National Meters Unit manager

Additional reviewers:

Person name role Signature/date

Zeev Feller Gateway/data concentrator expert

Siani Yuval IT Expert

Khosro Mahaban Expert at spec integration

Nava Donai Amat

Arik Perelmoter Amat




Table of Contents

INTRODUCTION .................................................................................................................................................. 8

CHAPTER “A”: TECHNICAL REQUIREMENTS FOR PREPARATION OF THE PROPOSALS ..................................... 10

PREPARATION OF THE PROPOSALS…………………………………………………………………………………………………………11

SPECIFIC BID SUBMISSION INSTRUCTIONS ..............................................................................................17

SAMPLES WITH PROPOSAL ......................................................................................................................19

ADDENDUM 1: SAMPLES TESTING & DEMONSTRATION (TECHNICAL STAGE) ........................................22

IECO METERS TESTS & APPROVALS PROCESSES SEQUENCE ...................................................................26

BIDDER'S INCOMPATIBILITY TO SPEC PARAGRAPHS ISSUES ...................................................................27

CHAPTER "B": TECHNICAL REQUIREMENTS DOCUMENT FOR DIRECT METER METROLOGY ........................... 28

CHAPTER B.1: METROLOGY REQUIREMENTS ..............................................................................................29

CHAPTER B.2: STANDARD TAILORING……………………………………………………………………………………………………30

CHAPTER B.3: METER PHYSICAL CHARACTERISTICS………………………………………………………………………………..32

CHAPTER B.4: SHIPMENT AND HANDLING…………………………………………………………………………………………..…40

CHAPTER C. POLY-PHASE CT-CONNECTED ELECTRICITY METER……….………………….………………………………45

CHAPTER C.1: METROLOGY REQUIREMENTS…………………………………………………………………………………….…46

CHAPTER C.2: METER PHYSICAL CHARACTERISTICS………………………………………………………………………….….47

CHAPTER C.3: PACKAGING……………………………………………………………………………………………………………….….50

CHAPTER C.4: ADDITIONAL REQUIREMENTS…………………………………………………………………………………….…50

CHAPTER D: METER GATEWAY, SPECIFICATIONS FOR METER GATEWAYS/DATA

CONCENTRATORS…………………………………………………………………………………………………………………………….………..53

PART 1: OVERVIEW…….……………………………………………………………………………………………………………………………..53

PART 2: MMS DETAILED TABLE OF REQUIREMENTS…………………………………………………………………………………..64

CHAPTER E. METER MMS DRIVER: REQUIREMENTS FROM METERING MANAGEMENT SOFTWARE

DRIVER………………………………………………………………………………………………………………………………………………………71

CHAPTER F. METERS MANAGENENT SOFTWARE: REQUIREMENTS FROM METERING MANAGEMENT

SOFTWARE………………………………………………………………………………………………………..……………………………………….72

CHAPTER F.1.: QUESTIONNAIRES & DECELERATIONS ................................................................................ 85

CHAPTER F.1.1.: RELIABILITY, AVAILABILITY AND MAINTAINABILITY (RAM) .......................................... 83

CHAPTER F.1.2.: BIDDER QUALIFICATION QUESTIONNAIRE ................................................................... 91

CHAPTER F.1.3.: BIDDER PREVIOUS EXPERIENCE &INSTALLATIONS .................................................... 104

CHAPTER “G”: TECHNICAL REQUIREMENTS FOR METER APPLICATIONS…………………………….…….………………105

CHAPTER G.1: METER CONFIGURABLE PARAMETERS FILES………………………………………………………………….106

G.1A.: TOU SPECIAL DATES & DST DATES LIST .................................................................................. 1114

CHAPTER G.2: RECORDER / DATA LOGGER / LOAD SURVEY .................................................................... 117

CHAPTER G.3: METER COMMUNICATION LOCAL & REMOTE ................................................................ 1178




CHAPTER G.4: DIRECT/CT CONNECTED METER HW / R.T.C BATTERY / OUTPUTS AND GATEWAY/DATA

CONCENTRATOR THE SAME, AND REMOTE/DIRECT FIRMWARE/(TOU/DST) CONFIGURATION UPDATE

................................................................................................................................................................ 1189

CHAPTER H: DIRECT/CT CONNECTED METER AND GATEWAY/DATA CONCENTRATORSECURITY AND

MMS SECURITY

.................................................................................................................................................................. 123

CHAPTER I: SOFTWARE AND ROUTINES / DATA FLOW AND PROCESS ..................................................... 125

I.1. : /PORTABLE PC / LAB PC / SERVER FUNCTIONS / APPLICATIONS .................................................. 128

I.2.: REQUIREMENTS FOR INTEGRATION OF NEW DEVICE DRIVERS INTO ZFA-F DLMS / COSEM ........ 134

I.3.: TOU & DST DIAGNOSTIC TEST TOOL & METERS CONFIGURATION VERIFY TEST TOOL ................. 134

I.4.: IECO OUTPUT FILES STRUCTURE/FORMAT & INTERRUPTIONS ........................................................ 138

I.5.: BILLING FILE & TECHNICAL DATA .................................................................................................. 138

I.6.: LOAD SURVEY/PROFILE ................................................................................................................. 148

I.7. SPECIFICATION FOR BEHAVIOUR OF LOAD PROFILE STATUS WORD STATE MACHINE ...................... 154

I.8.: LOG BOOK (EVENTS) .................................................................................................................... 1612

I.9.: OFF THE SHELF PRODUCT DECLARATION .................................................................................... 1634

BIDDER’S OFF THE SHELF PRODUCT DECLARATION & UNDERTAKING STATEMENT OF COMPLIANCE

.......................................................................................................................................................... 164

I.10.: LIST OF RELEVANT PUBLICATIONS ................................................................................................... 166

: LIST OF RELEVANT PUBLICATIONS ...................................................................................................... 166

I.11.: METER TESTS A.R.O ..................................................................................................................... 16667

DIRECT/CT CONNECTED METER, GATEWAY/DATA CONCENTRATOR, OTHER ACCEPTANCE TESTS (A.R.O)

.............................................................................................................................................................. 164

CHAPTER I.12.: LIST OF ABBREVIATIONS / GLOSSARY .............................................................................. 169

CHAPTER I.13.: TRAINING COURSES SYLLABUS ........................................................................................ 172

CHAPTER I.14.: TECHNICAL DOCUMENTATION & SOFTWARE REQUIREMENTS .................................... 1723

CHAPTER I.15.: WARRANTY & FOLLOW ON SUPPORT.............................................................................. 173

ANNEXURE A – SUMMARY OF DATA .............................................................................................................. 178

A.1. STATEMENT OF WORK….. ................................................................................................ ……………179

ANNEXURE B: DELIVERABLES……………………………………………………………….…………………………….…………………188

ANNEXURE C: GLOSSARY (ONLY) OF DELIVERABLES ............................................................................ 195

ANNEXURE D: OBIS CODES AND OBJECTS DESCRIPTION FOR IECo DRIVERS……………………………………………..196

Table of Figures

Figure 1 – IECo meters tests & approvals processes sequence ................................................................. 26

Figure 2 – Direct Connected Meter connections diagram ......................................................................... 29

Figure 3 shaped-head screw for terminal cover………………………………………………………………………….…………35

Figure 4 Protective Sleeve for Terminal Cover Screw …………………………….………………………………………………36

Figure 5-a – direct meter nameplate example ......................................................................................... 37




Figure 5-b - CT connected connected nameplate meter

example……………………………………………………………….37

Figure 6– Stranded Steel Wire for Sealing ................................................................................................ 39

Figure 7 –- Sealing (if meter case is not welded/soldered/glued)

................................................................................................................................................................ 40

Figure 8 – Example of mounting bracket ..................................................... .1שגיאה! הסימניה אינה מוגדרת

Figure 9 – Pallet ............................................................................................ .שגיאה! הסימניה אינה מוגדרת Figure 10: CT connected connected meter connection scheme…………………………………………………….…….…47

Figure 11- IECo connection scheme for CT connected meters, including a primary meter and a secondary

backup meter ………………………………………..…………………………………………………………………………………………...51

Figure 12 - a typical Israeli residential model serving as Techno-Economical evaluator and containing 120

apartments………………………………………..………………………………………………………………………………………………..55

Figure 13 - a second demonstration of the Techno-Economical model………………………………………………….56

Figure 14 - The cellular protocol generations enabled by this tender for gateways/data-concentrators

………………………………………………………………………………………………………………………………………………………….57

Figure 15- integration to metering management software……………………………………………..…………………...59

Figure 16 - 3 communication protocols optional to the tender specification………………………………………...62

Figure 17 – Reallin IECo probe PC use Figure 17-b – Abacus probe with USB plug for lab PC use ...... 1257

Figure 18 – TOU / DST/ Displays / CONFIG / Files meter update ............................................................ 131

Figure 19 – TOU / DST/ Displays / CONFIG / Files meter update .......................................................... 1324




List of Tables

Table 1 – Conformance Summarizing ....................................................................................................... 14

Table 2 – Example table for set of tests of TOU /DST /special days ........................................................ ..20

Table 3 – DLMS / COSEM SW passwords .................................................................................................. 21

Table 4 – Technical Data .......................................................................................................................... 25

Table 5 – Uncertainty of Measurement......................................................... .שגיאה! הסימניה אינה מוגדרת

Table 6 – Test points and limits of errors ................................................................................................. 31

Table 7 – Meter Reliability Data ............................................................................................................... 86

Table 8 - RAM historical Field data for meter Model No…. ....................................................................... 86

Table 9 – Bidder Personnel ......................................................................... ...שגיאה! הסימניה אינה מוגדרת

Table 10 – Bidder Manpower Resources .................................................................................................. 97

Table 11 – Special Field Service Engineering Manpower .......................................................................... 98

Table 12 – Bidder SW Resources .............................................................................................................. 99

Table 13 – Bidder previous experience &installations ............................................................................ 100

Table 14 - TOU 2010 map ...................................................................................................................... 112

Table 15 – IECo special days of year 2016 Table 16 - IECo special days of year 2017 ................ 113

Table 17 – IECo special days of year 2018 Table 18 – IECo special days of year 2019 !שגיאה

הסימניה אינה מוגדרת.

Table 19 – DST Time ............................................................................................................................... 116

Table 20 – Communication time limitations ........................................................................................... 118

Table 21 – SW level operations .............................................................................................................. 127

Table 22 - Software to be supplied by Bidder ......................................................................................... 121

Table 23 –PC / Lab PC / Server applications ........................................................................................... 131

Table 24 – TOU & DST verification test example ............................................................................... 137

Table 25 – DLMS / COSEM ..................................................................................................................... 138

Table 26 - IECo output 2 OBIS code convert (part of the file) ................................................................. 138

Table 27 – Standard IEC File Structure.................................................................................................... 140

Table 28 – Header Line Data Characteristics .......................................................................................... 146

Table 29 – Header Line Data Example .................................................................................................... 148

Table 30 – Data Line Characteristics ....................................................................................................... 149

Table 31 - Data Line Example ................................................................................................................. 149

Table 32 – Status Code bit set ................................................................................................................ 151

Table 32A – Additional LOAD SURVEY - STATUS CODE BIT SET………………………………………………………………………………152

Table 33 – Duplicate Data Fields ............................................................................................................ 155




Table 34 – SIP Data ................................................................................................................................ 157

Table 35 – Glossary (only) of Deliverables .............................................................................................. 192




.א

INTRODUCTION

1. Purchaser

The Israel Electric Corporation (IECo)

2. Tender Name

Poly-phase kWh & kVArh CT Connected Meters with –Twisted Pair Communication:

I. Type 1: for direct connection with time of use and load profile registers

II. Type 2: for CT connected connection, low voltage CT meter, with time of use and

load profile registers;

III. Type 3: gateway or data concentrator enabling data reading and configuration

update from the specified meters.

1. Mandatory requirement per commercial stage: The manufacturer must provide (i) 4 meters (samples) configured (see Samples with proposal) to this tender requirements of the proposed meter, ii) In addition 2 CT meters, (iii) a single gateway, (iv) a configuration software for portable PC, (v) an MMS software for installation + spare repeaters/filters, in case they shall be required during installation, (vi) Antenna+ cable. All of this together with the technical offer and all software accessories that shall allow testing and inspection by the Israel Electric Co. The samples that shall be sent must be of the same manufacturer and from the same plant that will manufacture the meters supplied regularly, after winning the tender.

3. Projects Location

Residential consumers at Israel that, are located at residential building containing

typically about 120 apartments.

4. Project description

The Israel Electric Corporation (IECo) intends to extend new installations or to

replace outdated Direct Connected (whole current) meters with Time of Use (TOU)

and load survey recording metering by utilizing static electricity meters, specified

herein. The components described herein are targeted for residential buildings,

and the solution is twisted pair with one of several protocols, defined at chapter D,

figure 16, p. 61 bellow. The specification is of a twisted pair metering system:

4.1. The first component that this document establishes is the poly-phase

direct meter with load profile and TOU, as described at chapter B pp. 28-45 bellow.

A meter with additional reactive measurement shall not be rejected by this tender.

4.2. The second component at this spec is a specification for Poly-phase kWh

CT meter measuring active/reactive import/export energy (kWh/kVARh), having both

time of use and load profile registration to be submitted as part of the Bidder's

proposal in reply to Purchaser's Bid. The meter spec is described starting chapter C

pp. 42-47 bellow. The first meter covers current range of up to 100 Ampere. The

second component defined by this tender is a poly-phase CT meter, with both active

and reactive energy measurement capability for both time of use and load profile.

4.3. The third component by this tender is a gateway or data concentrator. By

gateway this means an element enabling communication through it to a cluster of




meters. By data concentrator it means the same + the ability to store the data

collected by the data concentrator to the meters. IECo requires a gateway as minimal

requirement. The gateway/Data concentrator is described at chapter D pp. 52-67

bellow.

4.4. The fourth component is a provision of a “Meter Management System1”

(MMS). The specification of the MMS is the subject of chapter F, pp. 98-115 bellow.

4.5. The fifth component is a driver = technical assistant and low level

routines for IECo implementation of database and API to IECo billing system.

The interface shall be developed by IECo. Project's integrating company must

provide all required technical information that needs to be provided, in order to

develop an driver that connects manufacturer's MMS data to Israel Electric Company

org. (IECo) billing system. The API is to be developed by IECo computerization

department (AMAT) but it requires: (i) full technical info support from MMS

manufacturer and project integrator, (ii) provision of low level routines to access MMS

database to AMAT IECo, (iii) withstand a predefined schedule for execution of

project, within 3 months starting from signing commercial contract for the entire

project. The driver is described at chapter E p. 71.

In addition, this document specifies certain purchaser's requirements with which

Bidder's proposed equipment must comply.

1 MMS is mainly the application software.




CHAPTER “A”: TECHNICAL REQUIREMENTS FOR

PREPARATION OF THE PROPOSALS




PREPARATION OF THE PROPOSALS

General instructions

1.1. Bidders shall prepare their Proposals in conformity with all requirements of the

Tender Documents, including the attached Proposal Form. (Chapter I.14, p. 173.

Technical documentation).

1.2. The details and information provided by the Bidder in the Proposal Form must be

printed (not handwritten) on the Proposal Form itself or on separate documents on

which the questions of the Proposal Form must be reproduced.

1.3. The Bidder shall organize his proposal documents so that each Annexure “B”

paragraph is followed by the respective Annexure “C” paragraph. Annexure “C”

paragraphs shall carry the same paragraph number of the respective Annexure “B”

paragraph with the addition of the suffix “a” and shall be printed in a different font in

order to distinguish Annexure “C” paragraphs from Annexure “B” paragraphs. The

same with chapters A, B, C,…,I in correspondence to A-I at the spec. A numbered

paragraph includes all material in both numbered and unnumbered paragraphs up to

the next numbered paragraph. The Bidder shall provide details of each exception and

alternative. In each and every paragraph, the Bidder shall specify all the

characteristics of his proposed meter which are relevant to the said paragraph.

1.4. The Bidder must provide a response to each and every section in the Proposal Form.

1.5. The pertinent Standards and/or Specifications. (Bidders shall indicate the link(s) of

the relevant publication(s) of the Standards and/or specifications on the Internet)

1.6. If responding on a separate document, the response must follow the same order and

bear the same numbers as those of the Proposal Form, and must refer to all subjects

mentioned in the Tender Form in a full, precise, clear, explicit and unequivocal

manner.

For example

Paragraph 2.1 in the proposal will contain a reply or comment to item 2.1 of the RFP,

paragraph 2.2 will include the reply or comment to item 2.2, etc. Where items

contained in the RFP do not require any response or comment, the proposal shall

reflect a response of “No reply”, and the next item will maintain its original number in




the RFP If a particular question is irrelevant to the Bidder, the Bidder must write

“N/A".




1.7. Classification of the Technical part

The Bidder's reply to the Technical part must be classified as belonging to one AND

ONLY ONE of the following three categories:

Conform (C) – The Bidder's currently available proposed System meets the

requirements in the manner indicated by the Technical part.

Alternative (A) – The Bidder's currently available proposed System uses an

approach at variance with the Technical part, which the Bidder believes meets the

intent of the Technical part. The Bidder shall explain the proposed alternative. In

addition, the Bidder shall specify, where applicable, the effort in man days, required

to provide a fully conforming item.

Exception (X) – The Bidder's proposed System does not meet the requirements of

the Technical part and no alternative is proposed.

For example

DIAL TEST MODE

For dial test acceleration of the initial change of normal kWh resolution shall be done.

The dial test mode shall be activated for at least 60 min (necessary software shall be

included in the offer). In this mode, the display shall show 2 or 3 digits after the

decimal point. The meter will exit the dial test mode to normal display resolution either

by a command via the optic port, or when it is powered down.

Dial test mode is required for active, import and export energy, for a continuous

duration of at least 2minutes, for testing. If manufacturer does not abide to that

requirement, then alternatively it is possible, for meter to include dial test mode

through communication software. If both these means are absent then if manufacturer

accepts to provide a firmware version, enabling active import/export through dial test

mode for at least 2minutes.

D.1.3.a filling the conformance section

Tender integrator and/or manufacturer should fill in the manufacturer's companies

names, and the integrator's name for each module specified by the tender: direct

meter, indirect meter, gateway/data concentrator, MMS. Meter model type field should

be filled in. The accuracy of the KWh display is already 3 digits after the decimal point.

In the absence of conformance alternatives or exceptions in any individual paragraph,

IECo will assume that the Bidder's proposed System is in conformance with the

Technical part, and if the Bidder is awarded this Tender, the Bidder shall be required

to meet all such requirements without exception.

Notified Specifications by the spec, must be sufficient to demonstrate how the Bidder

proposes to comply with the applicable requirements, including full explanations of the

techniques, disciplines and procedures to be utilized. Failure to submit all required




technical information for the purpose of evaluation of a proposal may result in a

rejection of the proposal.

A conformance summarizing table in a list each numbered paragraph, in the Technical

part, stating for each, the relevant category of response (C, A or X)- shall be provided by

the Bidder as ANNEXURE A.

For Example

ID Requirement Remarks Bidders' Response

Req.2.13

Set/alter TOU table

M

Conform (C);

See details in 4.2.1.1.a

Req.2.14

Cumulative register

of kWh data shall be

separately

stored for each TOU

tariff

Conform (C);

Req.2.15

Only one season and

one TOU tariff shall

be in operation

during any time

Conform (C);

Req.2.16

The contractor shall

fill table 4.2.3

Alternate (A);

Partial data is available.

See table 4.2.3

Table 1 – Conformance Summarizing

1.8. The Bidder must show /explain /point to documents/ manuals / software /

demonstrate how is Proposal meet the requirements.

1.9. In case a requirement can’t be fulfillment the Bidder must indicate it in the

place assigned for this.

1.10. The Proposal shall not, by including or omitting information, mislead the reader.




1.11. Bidder shall not include any reservations, qualifications or conditions regarding the

terms of the Tender Documents, including the Agreement, and may not delete,

change or add to the contents of the Tender Form, unless specifically otherwise

stated in the form.

1.12. Proposals must be submitted in English or Hebrew. The Bidder is entitled to

include attachments to its Proposal in either English or Hebrew (such as technical

descriptions, manuals, test results etc.)

1.13. The Proposals shall be duly signed by the Bidders in the place indicated for

signature, and the signature shall certified by an attorney as specified in the

Proposal Form. In addition, the Bidder shall initial each page of the Proposal

1.14. The Proposal must consist of the following documents:

1.14.1. The completed Proposal Form (including the documents required to be

submitted as specified therein).

1.14.2. The Bidder must attach a table of contents to all its appendices and

documents, specifying the number of each appendix and document, its

subject, and the specific provision in the Proposal Form to which it relates.

1.14.3. Identification of Sensitive Information – The Bidders shall indicate, as

instructed in the Proposal Form, any information in their Proposal which they

consider as commercially sensitive or of a confidential nature.

The Tender Bond

The following requirements should be fulfilled:

1. The Proposal must be submitted as one original and two identical copies (three

altogether). The original Proposal which contains the original Tender Bond must be

marked with the word "original". Each copy must be marked "copy".

2. In addition, the Bidder must include a CDROM or memory sticks containing two PC-

readable software copies of the Bidder's Proposal, one in Microsoft Word or Microsoft

Excel format and one in PDF or other format that does not enable the file to be

altered.

3. Every page in the original copy of the Proposal must be stamped with the Bidder’s

stamp, and in the appropriate locations the Bidder must sign with its stamp and its full

signature. The foregoing applies to the original copy of the Proposal Form and its

appendices, without exceptions, including any written response of the Tender

Committee to a request for clarifications.




Annexes of the Proposal

The Bidder must attach to its Proposal all annexes and documents in accordance with the instructions specified in the Proposal Form. The numbering of such annexes and documents must match the numbering of the Proposal Form. In addition, the Bidder must clearly number all pages of the Proposal, including any attached annexes, in a consecutive numbering starting from one.




SPECIFIC BID SUBMISSION INSTRUCTIONS

In order to prove compliance with the requirements the Bidder is required to submit along

with the technical proposal the following documentation (as demanded in submittal table).

All applicable documents shall be in English (some documents may be in other languages

if allowed by IECo), and should refer to the factory where the proposed meters are

manufactured:

1. The Bidder shall authorize his agreement to every item of this specification by signing.

2. The Bidder shall concentrate in separate page all the requirements that his product/offer does not comply with.

3. A true copy of a certificate of type (pattern) approval from an authorized body (institute, laboratory or competent organization), confirming that the meter type, identical with the proposed one, complies with all the requirements of M-Bus protocol according to EN 13757-1, 2, 3. If the implemented protocol is rather Euridis then it should be in accordance with IEC 62056-31 standard. If protocol is RS-435 based then it should be in accordance with that standard. The certificates must be of the proposed meters: direct, CT, and gateway/Data Concentrator (gateway is only in accordance to communication protocol Euruidis or M-Bus or RS-485).

4. Bidders are required to provide a certificate and the necessary supplementary documents to prove compliance with all requirements of IEC/EN 62052-11 and IEC/EN 62053-21 and IEC/EN 62053-23 and IEC 62056 series of standards (DLMS/COSEM, IEC/EN 62056). The certificates must be of the proposed meters: direct, CT, and gateway/Data Concentrator (gateway is only in accordance to dlms/cosem). The certificate must include complete test results according to all requirements of the above standards, or the test results will be supplied separately, performed by an ISO 17025 accredited laboratory such as PTB, OFGEM, KEMA, NMI, NATA, METAS, or other national or international body, accredited or avowed by one of above laboratories to provide meter type (pattern) approval. The meter should carry a dlms/cosem logo. The manufacturer should notify in writing a list of supported dlms/cosem features and communication protocols by that specific model type. For full conditions of acceptance of accreditation by IECo

5. If the tests are performed in a laboratory other than those listed above, the laboratory should be internationally accredited to standard: ISO 17025, by an internationally accepted organization accustomed commonly used at western or OECD labs, such as ILAC or A2LA, and provide proof that its Scope of Work includes meter testing and certification. A true copy of the laboratory accreditation certificate should be enclosed. Separate to the organization accrediting for ISO 17025, another accreditation over the metrological standards (IEC/EN 62052-11, IEC/EN 62053-21) should come from a separate organization internationally acceptable from the following options: (i) a notified body from NANDO list, such as defined for this tender by the preliminary document. (http://ec.europa.eu/enterprise/newapproach/nando/index.cfm?fuseaction=directive.nb&refe_cd=EPOS_43437). No inheritance to a third party lab, by an MID notified body shall be acceptable by this tender. Such a laboratory shall not be accepted by this tender. (ii) PTB, OFGEM, KEMA, NMI, NATA, METAS. Some all of these labs is at NANDO list (iii) Lab accreditation on metrological standards from an OECD country

http://ec.europa.eu/enterprise/newapproach/nando/index.cfm?fuseaction=directive.nb&refe_cd=EPOS_43437

http://ec.europa.eu/enterprise/newapproach/nando/index.cfm?fuseaction=directive.nb&refe_cd=EPOS_43437




standard institute – shall be acceptable only based on IECo judgment and is less preferable.

Note:

IEC/EN 62052-11, IEC/EN 62053-21 and IEC/EN 62053-23 compliance certificates given

by advanced bodies from "List of bodies notified under 2004/22/EC Measuring

Instruments Directive (MID)" will be also adopted. MID – notified bodies must cover the

MI-003 product range and ability to provide each one of MID articles: Type-examination

(MID, Annex B), QA of Production process (MID, Annex D), QA plus design examination

(MID, Annex H1).

6. Alternatively to IEC/EN 62052-11, IEC/EN 62053-21 standards, at test certificate

according to EN 50470-1, and EN 50470-3 shall be accepted. List of acceptable

accredited labs is only according to options 5-(i) to 5-(iii) above. The alternative

standard EN 50470-3, abides to active energy only. For CT meter, proposal for

reactive energy, only certificate according to IEC/EN 62053-23 shall be acceptable.

7. Only an accredited lab, with legal and financial warranty (limited to) over the model

type testing shall be acceptable. A lab with permission to provide calibration certificate

only for meter samples is insufficient.

8. A copy of a certificate of compliance with ISO 9001 (2008) standard .The certificate should be valid for the date of tender proposal, and refer to the specific factory where the meters are manufactured.

9. A list of utilities, which have purchased electricity meters of a similar type and of the same manufacture, proposed in the bid, during a period of five years, just preceding the last date for submission of technical proposals. Such list shall include the dates of sale, the quantities sold, the meter model type, and the name of person to whom IECo may contact at these utilities. By similar IECo means not only according to standard IEC 62052-11.

10. Filled copy of Bidder's Qualification Questionnaire (not required if the Bidder is a regular supplier of solid-state meters to IECo).

11. Filled copy of the R.A.M. Questionnaire. RAM data should be of the exactly proposed model type.

12. Bidder Quality Assurance Manual (not required if the Bidder is a regular supplier of solid-state meters to IECo).

13. Filled copy of Conformity with requirements questionnaire.

14. Calibration certificates and traceability charts for all relevant test and calibration equipment.

15. The Bidder shall attach with the technical offer a complete description of the meter with all its properties and its detailed relation to each item of this specification.

16. The documents & manuals shall be organized as described in Chapter I.14. - Documentation / data and software with proposal.




17. As referring to selling experience at preliminary document, manufacturer may add for proof installation spot pictures of at least 50 meters at a utility that is an OECD country. Alternatively IECo checks occasionally for validity of selling experience data.

SAMPLES WITH PROPOSAL

1. The Bidder shall provide together with the technical offer (i) 4 (four) configured direct

meters (configuration consists of: metrology & TOU 2015 & special days, DST, load recording MD, load profile - Addendum 1 herein). Direct meter samples are to be supplied together with the technical offer for inspection by the Israel Electric Co. (ii) In addition 2 CT meter, (iii) a single gateway, (iv) plus configuration software for portable PC, (v) plus MMS software for installation + availability if difficulty during installation, (vi) plus Antenna+ cable. The deliverables are provided. The meters shall be accompanied by the necessary software and any other hardware to connect the system.

2. The samples shall be from the same plant that will supply the meters in case the

Bidder is awarded an order. The same rule applies for CT meter samples,

gateway/data concentrator.

3. IECo enables one of two options: (i) A probable pc ( lent to IECo for the tender

period ) installed activated and configured with the software's needed to test

and operate the meters samples. (ii) Alternatively manufacturer representative or

customer support shall install within short time at IECo laptop open for installations, all

tender required software for evaluation. The installation is bounded to very short time

(<1 week), at beginning of technical phase.

4. The samples shall include all modules / extra cards needed for accomplishing these

technical requirements.

5. The IECo shall be allowed to perform tests on the samples according to its judgment.

6. The samples shall be tested according to Addendum 1 herein.

7. The Bidder shall send experts to IECo metering lab (2-4 days) in purpose of instruct /

demonstrate and test the samples and clarify proposal misunderstanding.

8. The sample meters will be stored at IECo store for 6 months after the winner gets the

order. During this period the Bidder can get the meter by written request. After this

time period the meters will not be returned (exclude the Bidder that gets an order - his

meters will stored as reference). Meters may return faulty after IECo tests.

9. As a part of the samples submission they should be attachment with filled

configurations readable print screens /snapshots of the configuration and the

meters configuration files that meets this Spec requirements(incompatible

should be marked). (TOU /DST /Special Days General definitions/ Recorder /

communication and ECT.)

10. The Bidder shall send a set of tests of TOU /DST /special days of the configured




meters. The tests should show that the meter meets the requirements.

For Example

Test

Script

No

Holidays/

DST pass

Test Start

Date Time

Test

Duration

Expected

Rate

Register

Actual Rate

Register

Test Result

1 31/12/2005

23:55:00

00:06 3 3 Pass

3 31/03/2006

01:55:00

00:10 3 4 Fail

2 30/03/2006

23:55:00

00:06 3 3 Pass

4 31/03/2006

07:55:00

00:05 3 3 Pass

5 31/03/2006

08:00:00

00:05 2 2 Pass

Table 2 – Example table for set of tests of TOU /DST /special days

Note:

The IECo reserves the right, at its sole discretion, to allow a Bidder, who has not

submitted one or more of the above listed documents or meter samples, along with its

technical proposal, to accomplish its proposal and to submit the missing

documents/samples within such extra time as allowed by IECo. The IECo is allowed to

disqualify Bidders, who have not submitted the above listed documents within such extra

time, if any.




11. DLMS/COSEM features – In order to make Connection via third parties DLMS

Software using universal software to read meter parameters we need some

parameters / passwords as mention below .The Bidder shall sent the following

DLMS/COSEM features connection parameters:

Data for Optical Direct TCP/IP connections

Baud rate: ________

Communication timing (ms / n of retries) :___________

Short Name (SN) referencing

Logical Name (LN) referencing

Meter address: 0x____ – upper HDLC address 0x__ lower HDLC address 0x__ (broadcast address)

Password (s)

Application Association

Client address Password (default value)

Master 0x1-

Writer 0x1-

Reader 0x1-

management 0x1-

Table 3 – DLMS / COSEM SW passwords

Lowest level (without password) and Low level (with password) security.




ADDENDUM 1: SAMPLES TESTING & DEMONSTRATION (TECHNICAL STAGE)

As part of this tender (technical stage) the manufacture is required to demonstrate

the samples of the meters and the software according to these issues:

1. Meter definitions / parameters:

Configuring the samples with these parameters:

1.1. Metrology – 2 quadrants import /export active (output pulse led, high resolution

display).

1.2. TOU, DST – TOU 20152 & special days & DST & MD & billing dates

1.3. Load survey 4 channels + events (power fails / absence of phases / time & date

changes)

2. Tests 2.1. Metrology Type approval tests

2.2. Meter operation according the configuration parameters

2.3. Load survey recording

2.4. Events recording

3. Meter updating through direct and remote communication

3.1. Configuration

3.2. Date/time

3.3. TOU

3.4. DST

3.5. Display

4. Meter communication

4.1. Gateway/Data concentrator to MMS system: cellular, 3G (Edge) or better: 3.5G,

or 4G (LTE).

4.2. Meter to Gateway – twisted pair communication: Euridis, or ModBus or RS485.

4.3. Meter readings (billing, recorder, technical) through gateway/Data

Concentrator.

4.4. Event log power fails / absence of phases / time & date changes through

gateway/Data Concentrator.

2 TOU 2015 – Israeli TOU has not changed starting 2010.




5. Other characteristics

6. Meter data processing – output files




Content of submittal table

Equipment is lent to IECo for the period of technical evaluation. It is to be returned to

manufacturer representative after technical stage termination.

Description Quan

tity Hard copy / CD or DOK

Reference Note Comply

Hardware

Direct Connected meters

8 ---

General : Samples with proposal

Configured to requirements

optical head

1 _ General : Samples with proposal

if needed)

special RS-485 cable

1 _ General : Samples with proposal

(if needed)

CT connected connected meter

2

_ General :

Samples with

proposal

Configured

to

requiremen

ts

Gateway or Data Concentrator

2

_ General :

Samples with

proposal

Configured

to

requiremen

ts

Antenna+ cable 1 --

General :

Sample with

proposal

Installation

equipment

Portable

installation

equipment

1

Only if

needed

Test

Equipment

Portable

Control station

or install

software on

IECo portable

PC

1

General :

Samples with

proposal

Configured

to

requiremen

ts

Software CONFIG/ communicate

CD General : Samples with proposal




MMS3 software 1

For communication with meters/Gateways

Bidder technical offer

filled &Signed all items and tables of this specification

2 3&1

General: Specific bid submission instructions

Manuals Meter operation 2 3&1 Chapter I.14.

SW operation 2 3&1 Chapter I.14.

QA manual 2 3&1 Chapter I.14.

Certificates

ISO9001-2008 2 3&1 Chapter I.14.

IEC/EN 62052-11

2 3&1 Chapter I.14.

IEC/EN 62053-21

2 3&1 Chapter I.14.

IEC/EN 62053-23

2 3&1 Chapter I.14.

IEC 62056-21/46/47/53/61/62/

3 3&1 Chapter I.14. DLMS/Cosem

Test reports

IEC/EN 62052-11

2 3&1 Chapter I.14.

IEC/EN 62053-21

2 3&1 Chapter I.14.

IEC/EN 62053-23

2 3&1 Chapter I.14.

Questionnaires

RAM 3&1 Chapter F.1.1.

Qualification 3&1 Chapter F.1.2.

Bidder previous experience &installations

Chapter F.1.3.

Declaration Off the shelf 1&1 Chapter I.9. & Threshold Conditions

Table 4 – Technical Data

CD or memory stick (Disk on key)

3 MMS – Metering Data Management Software.

Specification # 306-3-02-13

Israel Electric Corp Central Metering unit Page | 26


IECO METERS TESTS & APPROVALS PROCESSES SEQUENCE

Figure 1 – IECo meters tests & approvals processes sequence

Type tests Limited Applications tests

Metrology tests-accuracy & h.v

Certifications & documents authentication

Metrology tests-accuracy & h.v

A.R.O Approval

&acceptance Tests

Testing all meter & system applications

According to this specification

Accuracy & high voltage

Chapter I.11.

Addendum 1

Chapter I.11

Addendum 2

Follow on deliveries

Technical stage tests

A.R.O Preliminary delivery 5 meters

Initial delivery

Functionality verification

Accuracy & high voltage Functionality & Initialization verification

Work Statement

Par 9

Work Statement

Par 9

Limited Accuracy tests Installations tests at consumer premises

Field tests

Work Statement

Par 9.9 Accuracy &applications

References Process Tests




BIDDER'S INCOMPATIBILITY TO SPEC PARAGRAPHS ISSUES

On this page the Bidder shall list all paragraphs his offer does not conform to.

Example: ANNEXURE "B" – Chapter B-3 paragraph 8.1 – details: ___________

1.

2.

3.




CHAPTER "B": TECHNICAL REQUIREMENTS DOCUMENT

FOR DIRECT METER METROLOGY




All general chapters such as RAM, list of deliverables, acceptance tests – refer to all

components.

CHAPTER B: DIRECT CONNECTED METERS

B.1 METROLOGY REQUIREMENTS

1.1 Three-phase four-wire connection.

1.2 Absolute Active Total and Negative Active Total registered energy. A meter with

additional reactive energy measuring shall not be rejected.

1.3 Reference voltage (Un): 3*230/400 V.

1.4 Reference basic current (Ib): 3*10 A or 3*5 A.

1.5 Maximum current (Imax): 3*100 A.

1.6 Reference frequency: 50 Hz.

1.7 Accuracy class 2 for active metering according to IEC/EN 62053-21.

1.8 Connection Diagram:

10 129763 41

L1L2L3N

comm.

Figure 2 – Direct Connected Meter connections diagram

1.9 On the Figure 2: meter main terminal markings shall be marked on the terminal block by

irremovable numbers.

1.10 Over-voltage Protection: the meter must withstand a continuous heightened voltage up to

400 V upon each of the voltage inputs (section B.2.: Standards tailoring: IEC/EN 62053-21

standard tailoring 2).




B.2 STANDARDS TAILORING

IEC 62052-11 standard tailoring

1. Paragraph 3.3.1 - add: "Window's and optical port transparency shall not be altered or

degraded when exposed to solar and ultraviolet radiation". The Meter shall be indoor meter with

additional protection as defined below.

2. For 3.2.4 - display device which displays the content(s) of the memory

Add: "Active energy should be displayed by kWh and as principal units, but a special reading

with resolution of 10 Watt-hour or less should be enable” (for dial test purposes).

3. Temperature range should be in accordance with IEC 62052-11, table 5. Humidity range

shall be in accordance with same standard table 6, and climatic durability in accordance

with IEC 62052-11. IECo preserves the right to repeat tests in accordance with that

standard.

Note:

An energy value will be exposed to reading in reasonable resolution as cut down number and not

as rounded up one.

4. Paragraph 3.2.5. Fourth row: delete the following words: "an electromechanical device or".

Note:

Only electronic display is acceptable.

5. For Paragraph 3.4 Definitions related to insulation – choose application 3.4.6 insulating

encased meter of protective class II

IEC/EN 62053-21 standard tailoring

1. All relevant references on corresponding accuracy class.

2. Over-voltage Protection – Above and beyond the requirements specified in IEC/EN 62053-

21, the meter must withstand a continuous heightened voltage up to 400 V upon each of

the voltage inputs. The "worst case test" scenario is when such over-voltage should be

applied upon all three elements during two hours simultaneously. The meter shall not be

damaged and must perform correctly when back to its initial working condition. There

should not be any change of meter metrological features.

IEC/EN 62053-23 standard tailoring

All relevant references on corresponding accuracy class.

IEC 62058-31 Standard tailoring




Add Note: The methods and procedures of this Standard may be used for Acceptance Inspection

of whatt-hour and var-hour combined meters. Tests 1, 2 are common, rest of tests should be

carried out twice: for whatt-hour meter and for var-hour meter by consecutive order. Special

marking for test #3: 3- starting current for Wh-meter, 3a – starting current for var-hour meter.

Special marking of test numbers in "Table 6 – Accuracy test points and percentage error limits"

should be provided accordingly. Namely: if the test points for whatt-hour meter of Class 2 are

marked by 4,5,6,7,8 and 9 the test numbers for var-hour meter of Class 3 should be marked as:

4a,5a,6a,7a,8a,9a respectively.

Nonconformities found in 4-4a….9-9a will be considered as non-critical in classification of

nonconformities by table 4 of IEC 62058-31.

Table 5 – Uncertainty of Measurement

Class of Meter Power factor

2 3

0.4% 0.5% 1

0.6% 0.7% 0.5 Inductive

Table 6 – Test points and limits of errors

Test # Current Power

factor

For poly -

phase

Balanced or

unbalanced

Percentage

Error limits for meter

of class.

2

IEC/EN

62053-21

3

IEC/EN

62053-23

4,4a 0.05 I b <I<0.1 I

b

1.0 Balanced ±2.5 ±4.0

5,5a I b 1.0 Balanced ±2.0 ±3.0

6,6a I b 0.5

inductive

Balanced ±2.0 ±3.0

7,7a I b 1.0 1 phase loaded ±3.0 ±4.0




8,8a I b 1.0 1 phase loaded

,different phase

from test no 7

±3.0 ±4.0

9,9a Imax 1.0 Balanced ±2.0 ±3.0

Note: Accuracy tests sequence must start at test no. 4 and finish at no. 9

B.3 METER PHYSICAL CHARACTERISTICS

B.3.1 METER CASE

3.1.1 The meter case shall be made of non-hygroscopic insulating material, self-extinguishing

class V2 according to IEC 60695-11-10, and withstand the tests defined in IEC 60068.

3.1.2 It shall be insulating encased with protective class II according to IEC 62052-11, and

sealed against penetration of dust and moisture (IP 51, per IEC 60529).

3.1.3 If required, the manufacturer must provide IECo with exact insulation tests connection

scheme and instruction. Specific instructions must be provided to data transfer ports.

3.1.4 Its shape shall be accordance to DIN 43857-2 on the assumption of meter features,

performance and be within the overall dimensions as given by this Specification.

3.1.5 Any area of the meter case must be able to withstand the spring hammer test with energy

equal to 0.35 J.

B.3.2 DISPLAY & DISPLAY WINDOW

3.2.1 The display window shall be made of transparent, UV radiation resistant polycarbonate,

or another equivalent material. If a material other than polycarbonate is used, the Bidder is

required to submit a full description about its characteristics and evidence for its quality and

durability.

3.2.2 The meter display shall be LCD with good contrast and wide viewing angle for easy meter

readout.

3.2.3 It should have a wide operating temperature range (industrial grade) and a life time of at

least 15 years.

3.2.4 For dial test acceleration of the initial change of normal kWh/kvarh resolution shall be

done. The dial test mode shall be activated for at least 60 min (necessary software shall be

included in the offer). In this mode, the display shall show 2 or 3 digits after the decimal point.

The meter will exit the dial test mode to normal display resolution either by a command via the

optic port and when it is powered down.

B.3.3 TERMINAL BLOCK




3.3.1 The terminal block should be made of glass-filled polycarbonate

3.3.2 The shape of terminal block and its cover shall be in accordance with DIN 43857 or

BS7856 on the assumption of meter features performance and within the overall dimensions as

given by this Specification.

3.3.3 Surrounding insulating material shall not obstruct connection of isolated cables into the

terminals bores.

B.3.4 TERMINALS

3.4.1 Each terminal must be provided with two screws to tighten copper conductor directly (so

called "pillar-bar-type" terminal), or by means of lift-clip which pinches a conductor (so-called

"lift-type" terminal).

3.4.2 "Pillar-bar-type" terminal must be made of brass and be protected against corrosion.

3.4.3 The pinching clip of "lift-type" terminal must be either made of Steel 8,8 and be Nickel

plated (5 micron min), or made of brass and be protected against corrosion. IECo approves

also for the terminal thread to be made of an alloy of brass and cupper, or stainless steel with

anti-galvanic plating, or any other metallic material that manufacturer proves with references

and testing that it is non-corrosive and anti-galvanic plated.

3.4.4 The terminals in their tightened position must allow steady bottom connection of the meter

to "quick springy connectors" of Test Benches for metrological tests.

3.4.5 There must not be access to internal parts of the meter through the terminals.

3.4.6 The bore diameter for sleeved stranded external conductor connection – including neutral

– shall be 9-0.2 mm at least, in accordance with ISO 286-1, 282-2 tolerances standards. Both

neutral terminals (input/output) shall be either one single solid piece or two pieces securely

joined together and non-detachable manually.

B.3.5 TERMINAL SCREWS

3.5.1 The pinching screw diameter must be at least M6. The screw bottom must be chamfered,

without rough edges. The pinching screws must be either made of Steel 8,8 and be Nickel

platted (5 micron min), or made of brass and be protected against corrosion.

3.5.2 In any case, there should no galvanic couple be set up between the screws, terminals

and copper conductor.

3.5.3 The meters must be supplied with all pinching screws fully inserted into the terminals, and

tightened enough to prevent being loosened due to vibrations during transportation.

3.5.4 Bidder is required to state the maximum allowed torque to be applied to the pinching

screws.

B.3.6 TERMINAL COVER

3.6.1 The terminal cover shall be of extended type, made of non-breakable, UV radiation

resistant, self-extinguishing insulating material Class V-2 according to IEC 60695-11-10.




3.6.2 The cover shall have free space of 60 mm for the connecting cables, not exceeding the

overall meter dimensions (see clause B.3.9). The actual available free space is subject to

discussion with IECo.

3.6.3 The cover shall be firmly attached to the case with one or two shaped-head screws in

protective sleeves (fig. 11, 12), which are an integral part of the cover. The cover shall be

packed for shipping unscrewed, together with the meter, while the measures are taken to

prevent the cover from "self-tightening" during transportation. The shaped screws, however,

shall be inserted into their places in the cover.

3.6.3 The shaped-head screw shall have a hole suitable for sealing of the terminal block with

sealing wire. The screw shall have M4x0.5 thread and be made of MS58 brass 10µm nickel-

plated. The shaped-head screw shall be protected from slip out from the sleeve when not

tightened.

3.6.4 The phase sequence and connections with the terminals marked as per clause B.1.8 of

this Specification shall be attached on the inner side of the cover.

3.6.5 Manufacturer writing commitment to adapt the terminal cover to the Spec requirements in

case of order award is acceptable.




Shaped-Head Screw for Terminal Cover:

Figure 3 shaped-head screw for terminal cover




Protective Sleeve for Terminal Cover Screw

Figure 4 - Protective Sleeve for Terminal Cover Screw

B.3.7 NAMEPLATE

3.7.1 The nameplate could be an intrinsic part of the meter case or cover, or made by

permanent fade-proof overprint on the front cover surface.

3.7.2 In addition to the marking required by IEC/EN 62052-11 and IEC/EN 62053-52 the meter

nameplate shall show manufacturing country, the official logo of the Israel Electric Co. and an

encircled code number consisting of 3 or 4 digits.

3.7.3 The code number will be given to the Bidder who is awarded the order.

3.7.4 The 8 digit serial number shall be marked with digits at least 4 mm high height.

3.7.5 The serial and the code number shall be included in bar-code mark etched on the plate.

3.7.6 The marking shall be done in code 128C with 12 digits, the first four digits for the meter

code and 8 digits for the serial number.

3.7.7 The minimum height of the bar-code mark shall be 10mm in medium density.

3.7.8 The bar-code coding and readability shall be checked and confirmed by IECo.

3.7.9 The result shall be at least 95% and light reflection at least 80%.




3.7.10 The meter current range shall be marked in the form where the maximum current is

marked with larger digits than the basic current (10-100 A).

3.7.11 The final format of the nameplate is subject to IECo approval.

Figure 5-a – direct meter Nameplate example

Figure 5-b: CT connected connected meter nameplate example

B.3.8 SEALING

3.8.1 The meter base and cover should be either ultrasonically welded or permanently glued

together to prevent access to internal components.

3.8.2 Alternatively, screws shall secure the meter cover to the base. The screws should be

sealed.




Any solution of the following with the aim of disabling any opening of front panel for fraud

and theft:

(i) screws with sheared head;

(ii) unidirectional rotation screws;

(iii) any other method proposed by manufacturer, provided that manufacturer convinces

IECo that it is efficient at prevention of detachment of front panel from meter body without

breaking meter.

3.8.3 The seals shall be of the same type, made of tin-coated electrolyte copper and crimped

on a galvanized or stainless steel cable ("rope").

3.8.4 The seal should be fixed adjacent as much as possible to the screw which is sealed, and

the surplus cable ends should be cut off adjacent to the seal.

3.8.5 Measures should be taken in order to prevent user wounding from sharp seals' edges.

3.8.6 If the meter is not welded or glued it should have tamper evidence sticker on both meter's

sides.

3.8.7 Drawings of the sealing cable are attached (Figure 6).

3.8.8 Drawings and details of the preferable and alternative seals are shown in Figure 7.

3.8.9 The Bidder must submit a sample of the proposed seal for IECo's approval. Exactly the

same type of seal shall be used throughout the period of supply. Any further change in seal

shape or format must be notified to IECo in advance, and approved.

3.8.10 The meter shall carry metrological marking that demonstrates the initial calibration

performed on the meter.




Figure 6 – Stranded Steel Wire for Sealing

R2.00

R1.25 +0.05

1.50 Ref.

R0.75

4.00 Ref.

Welding or

soldering

6.00 8.00 -0.50

13.00 Ref.1.00

Coining 5.00

0.75 +0.05

Welding

(Alternative shape)

Dimensions: mm

Tolerance (unless stated otherwise): ±0.2 mm

Material: tin-coated electrolyte copper

Tin plating: 5 µm minimum




Plate thickness: 0.75 mm nominal

Rockwell Hardness: 55-65 T15

Coining:

One side: Israel Electric Corp. logo

Other side: The manufacturer initial calibration sign

Figure 7 - Sealing (if meter case is not welded/soldered/glued)

B.3.9 OVERALL DIMENSIONS

3.9.1 According to DIN 43857.

3.9.2 W 180 mm between bottom fixing holes axis, H 320 mm (including terminal

cover), D 140 mm.

B.3.10 MOUNTING BRACKET

3.10.1 The meter shall be equipped with mounting bracket to allow easy mounting.

3.10.2 The top mounting hole shall be duplicated. At that, one hole within meter rear

and other of protrusive type, that could be intrinsic case lug or detachable eyelet.

3.10.3 The top mounting arrangement could be an integral part of the meter base,

slide-out, reversible or a clip-on accessory.

3.10.4 The top mounting bracket shall enable mounting on M5 screw. Examples of the

mounting bracket are shown below.

Extended Retracted

KM

Extended Retracted

KM

Reversible Type

Slide-out Type




Figure 8 – Example of mounting bracket

3.10.5 The bracket shall withstand the pressure coming from the mounting screw

(where applicable). The closing torque on the screw is 3 Nm at least.

Notes

A protecting disk will be put on each pressing screw right before the mounting.

If the suspension clip is not of slide-on type it must be supplied to the purchaser in

extended position.

B.3.11 BOTTOM MOUNTING HOLES

3.11.1 The meter shall have two bottom holes for its fixing by means of M5 screws.

3.11.2 The bottom holes must be covered by the terminal cover after its setting and

sealing.

B.3.12 WEIGHT

Weight: 2.5 kg (excluding the terminal cover).

B.3.13 OPTICAL PORT

The meter should be equipped with an optically isolated interface, physically conforming

to IEC 62056-21. This interface shall be located on the front panel of the meter, and be

fully accessible. The baud rate in non-visible light shall be at least 2400 bit/s after log-

on, and no more than 9600 bit/s.

The optical port shall be used for reading the energy consumption registers and other

data, such as the meter serial number and status flags. It is also used to enable and

disable the Dial Test display mode. It shall not be possible to reset the main energy

register, or to change the meter number, constant and other metrological parameters via

the optical port.

The port shall be equipped with a ferro-metallic ring or an optical port of any type, for

attaching the optical adapter head. The ring must be in accordance with IEC62056-21

pp. 25-29 and must withstand:

a. Detachment strength of at least 5 Newton between probe and port, while probe is

touching the port. ABACUS probes, and REALLIN USB probes shall be used (also

Successful reading).

b. Detachment strength of at least 1.5 Newton between probe and port, while probe

is 2mm far from the port.




In addition to IEC 62056-21, successful reading of large load-profile data for at least 20

minutes, using an optical probe (Abacus and Reallin).

B.3.14 METROLOGICAL TEST OUTPUT

3.14.1 LED / LED-s outside the optical communication port must be provided on the

meter front panel for metrological purposes. LED will flash in direct proportion to the

power flow regardless of the current direction.

3.14.2 LED conversion from emitting light to extinction or back shall denote the test

pulse length.

3.14.3 LED light shall be in the visible spectrum (preferably red), and shall not be

modulated.

3.14.4 In case there is only one LED for both active and reactive energies modes,

the switch between the modes (active/reactive) should be done by using front panel

push buttons or/and by simple software operation.

B.3.15 EXCESSIVE MAGNETIC FLUX PROTECTION

3.15.1 The meter shall detect and will be protected against external continuous

magnetic flux levels which exceed the value defined in IEC/EN 62053-21, paragraph

8.2.4.

3.15.2 There shall be a time & date stamp/records in the meter log book each time the

excessive Magnetic Flux sensor is activated.

B.3.16 ENERGY REGISTERS

The meter shall register and display absolute active total energy (|A|, OBIS 15.8.0). In

addition, internally there shall be negative active total energy (A-, OBIS 2.8.0) as well as

absolute active total energy (|A|, OBIS 15.8.0) in two separated registers.

B.3.17 NEUTRAL CONNECTION LOST OPERATION

The meter shall continue to operate even when the neutral alone or in common with any

one of three phases are removed. The errors in energy measurement shall not exceed

the limits allowed in the standards regarding single-phase load.

B.3.18 METER SERIAL NUMBER & METER CODE

3.18.1 The meter's unique serial number shall be recorded both as printed numbers

and barcode, and also recorded in permanent memory, and available for readout via

the optical port. It shall be impossible to change or delete the serial number.

3.18.2 The barcode and the internal memory's serial number shall consist of 12 digits:

the first 4 digits shall be the meter code, and the next 8 digits shall be the unique serial




number, of which the first 2 digits are the year code (e.g. 15) and the other 6 digits are

the consecutive serial.

B.3.19 VOLTAGE LINKS

The voltage circuit connections (links), if any, shall be unavailable for opening by

conventional means, when the cover of the terminal block is open. Conventional means

meaning is without breaking of the link or tightening elements, and unopened by a

conventional force using hand tools, and easily noticed if damaged.

Note:

The meters must be supplied to IECo with the links closed and checked for continuity.

B.3.20 ENVIRONMENTAL SERVICE CONDITIONS

Meters shall be finished to keep all specified features when installed indoors in humid

tropical environment.

B.3.21 SPARE PARTS

3.21.1 The Bidder shall be committed to supply spare parts to IECo as required to

maintain and repair the quantity of the purchased meters, if asked for.

3.21.2 The parts shall be supplied as long as the meters are purchased and shall

continue to be available at least 5 years after the Bidder has stopped supplying the

purchased meter type.

3.21.3 After this time, before the termination of the spare parts supply, the Bidder shall

provide IECo with all the necessary information to produce the spare parts, or inform

IECo of alternative sources.

3.21.4 Along with the offer the Bidder shall provide the Bidder's part numbers of the

offered spare parts

3.21.5 The Bidder shall detail other recommended (if any) spare parts like lithium

battery.

B.4 SHIPMENT AND HANDLING

4.1 Each meter must be packed, together with its not tightened terminal cover and fixing

screws, in a separate cardboard box, which can be opened and re-closed without needing

adhesives. The measures should be taken to prevent the cover from "self-tightening"

during transportation. The shaped screws, however, shall be inserted into their places in

the cover.

4.2 The box shall prevent, as much as possible, penetration of dust during long storage

periods. The box must be designed for multiple use and be robust, with wall thickness of at

least 4 mm.




4.3 The packaging will protect the meters against shock and vibration, preventing damage

due to the road conditions during transport and distribution in the countryside. The

electrical and mechanical properties shall not be affected by these disturbances.

4.4 4 to 8 boxed meters should be packed together in a group box. This box shall be

marked – on the front (wide side) and on the narrow side – with the Bidder name,

meter type, meter code, IECo catalog number 3966298 for details and catalog number

2109148 for CT-connected meter, production serial numbers (or these numbers' lot

borders), serial number bar-codes (or bar-codes' borders), manufacturing year, sign

“FRAGILE” and the Israel Electric Co. logo.

4.5 For shipping the group boxes shall be close packed by stockpiles of suitable quantities

on pallets. A stockpile will be protected against moisture by a polyethylene hood, covered

with a cardboard cover (hood), and fixed onto the pallet by parallel polypropylene bands,

using protection angle bars at the corners.

4.6 The hood shall be marked – on the front (wide side), on the narrow side and on the

top – with IECo logo, the Bidder's name, meter type, meter code, IECo catalog number

3966298 or 2109148, production serial numbers' borders, serial number bar-codes

borders, manufacturing year, the IECo order number, sign “FRAGILE”.

4.7 The pallet shall also carry a unique label (for example, "Pallet 1 out of 24") to

distinguish it in the total shipment.

4.8 An impact detector ("Shock Watch") label shall be attached to the cardboard hood of

several pallets in each container to warn of possible rough handling during shipment,

transport and storage.

4.9 The general form, overall and access dimensions of the pile are as given below.

4.10 Each pallet should contain between 70 and 200 meters.

4.11 The actual number of meters on each pallet will be agreed with the IECo when the

Bidder is awarded an order.




10

50

-1

00

250 ±20100 -10

800 -40

11

0 +

10

15

0 -

10

150 -10

1200 -200

KMKM

Cardboard Hood Polyethylene Hood

(Dimensions in mm)

Maximum gross weight: 250 kg.

Figure 9 – Pallet

Note:

The wooden pallet should be treated and protected against woodworms and other vermin.

The cardboard and polyethylene hood design could be in any of the following forms:

a. Both the cardboard and polyethylene hoods could be open at the bottom, per drawing

b. The cardboard hood could be an inverted box, and be easily separated from the base, either manually or with a box cutter

c. The polyethylene hood could be a close-fitting cover, and be easily separated from the base, either manually or with a cutter

If options "b" or "c" are used, then a separation line – about 10 mm above the pallet – should be

clearly marked.




CHAPTER C. POLY-PHASE CT-CONNECTED ELECTRICITY METER

The Specification refers to Static whatt-hour/var-hour Meter, with three measuring

elements, connected via Current Transformers. The meters shall comply with all

requirements of IEC/EN 62052-11, IEC/EN 62053-22 and IEC/EN 62053-23

publications.

Note: If there are contradictions between the requirements of this Specification and

those of the standards, the requirements of the Specification will prevail.

C.1 METROLOGY REQUIREMENTS

1.1 Three-phase four-wire connection.

1.2 Positive active total (A+, OBIS 1.8.0) energy, negative active total (A-, OBIS 2.8.0.) energy, positive reactive total (R+, OBIS 3.8.0.), negative reactive total energy registration. 1.3 Reference voltage: 3 x 230/400 V.

1.4 Reference frequency: 50 Hz.

1.5 Reference rated current (In): 3 x 5 A.

1.6 Reference maximum current (Imax): 3 x 6 A at least.

1.7 Multiplication factor: 100/5 A. Primary side energy is to be registered and displayed.

1.8 Accuracy class 1 for active energy (Wh) in accordance with IEC 62053-21, and class 2 for reactive energy (varh) in accordance with IEC 62053-23. Note: Accuracy class of the submitted meter, that is better than accuracy class required by this Spec herein, shall be accepted. The same is legitimate for accuracy classes according to EN 50470-1, 3. The nameplate shall display the Spec accuracy class, and acceptance tests will be conducted by IECo in accordance to the Spec required accuracy class. 1.9 Communication hardware:

For communication hardware considerations of terminals, screws and cables

manufacturer must refer to section 18, p. 57 of this Specification.




1.10 Connection Diagram

1 2 3 4 5 6 7 8 9 11

L1

L2

L3

N

S1 S2

P1 P2

S1 S2

P1 P2

S1 S2

P1 P2

Current

transformers

Output

Mains To Service

Meter

Figure 10: CT connected meter connection scheme.

Note: The connection terminals of mains and customer service must be marked on the

terminal block as given on the diagram with irremovable numbers.

1.11 Over-Voltage Protection

Above and beyond the requirements specified in IEC/EN 62053-22, the meter must

withstand a continuous heightened voltage up to 400 V upon each of the voltage inputs.

The "worst case test" scenario is when such over-voltage should be applied upon all

three elements during two hours simultaneously. The meter shall not be damaged, and

continue to operate properly when the over-voltage condition is removed. Any change of

meter metrological features will not come out.

C.2 METER PHYSICAL CHARACTERISTICS

C.2.1 METER CASE

Refer to section B.3.1 for details.

C.2.2 DISPLAY & DISPLAY WINDOW


C.2.3 TERMINAL BLOCK

The meter must be of surface mounting bottom-connected type on the assumption

of meter features and performance and within the overall dimensions as given by

this Specification. Outer case made of insulating material shall not obstruct




connection of isolated wires into the terminals bores.

C.2.4 TERMINALS

2.4.1 Each terminal must be provided with two screws to tighten copper conductor directly

(so called "pillar-bar-type" terminal), or by means of lift-clip which pinches a conductor (so-

called "lift-type" terminal). There should be no galvanic couple set up between the screws,

terminals and copper conductor – joined alloys potential difference must not exceed 0.15 V

(refer ASTM G-82 Standard).

2.4.2 "Pillar-bar-type" terminal must be made of brass and be protected against corrosion.

2.4.3 (i) The pinching clip of "lift-type" terminal must be either made of Steel 8,8 and be

Nickel plated (5 micron min), (ii) or made of brass and be protected against corrosion. (iii)

IECo approves also for the terminal and clip to be made of an alloy of brass and copper,

(iv) or stainless steel with anti-galvanic plating, (v) or any other metallic material that

manufacturer proves with references and testing that it is non-corrosive and anti-galvanic

plated.

2.4.4 The terminals in their tightened position must allow steady bottom connection of the

meter to "quick springy connectors" of Test Benches for metrological tests.

2.4.5 There must not be access to internal parts of the meter through the terminals.

2.4.6 Both neutral terminals (input/output) shall be either one single solid piece or two

pieces securely joined together and non-detachable manually. The bore for external cable

connection shall allow for easy accommodation of 2 mm2 and 4 mm2 wires as well as

ensuring perfect contact.

2.4.7 Both current and voltage terminals shall be located in the same row.

C.2.5 TERMINAL SCREWS

The pinching screws must be made either of Steel 8,8 and be Nickel plated (5 micron min),

or made of brass and be protected against corrosion. The screws heads must be of slot

type only.

The screw bottom must be chamfered without rough edges.

There should no galvanic couple be set up between the screws, terminals and copper

conductor – joined alloys potential difference must not exceed 0.15V (refer ASTM G82

Standard).

The meters must be supplied with all terminal screws fully inserted into the terminals, and

gently tightened to prevent being shaken lose during transportation.

Manufacturer is required to state the maximum allowed torque to be applied to the

pinching screws.

C.2.6 TERMINAL COVER

The terminal cover shall be made of non-breakable, self-extinguishing insulating material

Class V-2 according to IEC 60695-11-10.




The cover shall be extended type with free space of at least 40 mm for the connecting

cables, without exceeding the overall meter dimensions. The actual available free

space is subject to discussion with IECo.

The screws shall enable the sealing of the terminal block. The screws shall be protected

against corrosion.

The screws shall be protected from slip out from the sleeve when not tightened.

After the meter is mounted, no access to the installation screws as well as terminals or

cables shall be possible without breaking the seal or the cover itself.

The connection diagram of the meter with terminals marking should be attached to or

stamped on the inner side of the cover.

C.2.7 NAMEPLATE


Ct-connected meter exceptions:

- The meter current range shall be marked in such

manner: 3X100/5; 5(6) A

- The meter constant shown on the nameplate shall

include the multiplication factor (x20) – see also clause C.2.13.

C.2.8 SEALING

Refer to section B.3.8 for details

C.2.9 OVERALL DIMENSIONS

Refer to section B.3.9.2 for details.

C.2.10 MOUNTING BRACKET


C.2.11 BOTTOM MOUNTING HOLES


C.2.12 OPTICAL PORT


C.2.13 METROLOGICAL TEST OUTPUT


Ct-connected meter exception:

The constant for measured energy that is to be registered and displayed, shall be

derived from 5000 imp/kWh (imp/kvarh) or higher, regarding secondary values (as




applied to the meter terminals). The secondary values shall be multiplied by 20,

considered as a factor to primary energy record.

C.2.14 EXCESSIVE MAGNETIC FLUX PROTECTION


C.2.15 ENERGY REGISTERS

The meter shall register and display positive active total (A+, OBIS 1.8.0) energy as

well as negative active total (A-, OBIS 2.8.0.) energy, and positive reactive total (R+,

OBIS 3.8.0.), as well as negative reactive total energy (R-, OBIS 4.8.0.) – in four

separated registers.

C.2.16 NEUTRAL CONNECTION LOST OPERATION


C.2.17 METER SERIAL NUMBER & METER CODE


C.2.18 ENVIRONMENTAL SERVICE CONDITIONS


C.3 PACKAGING

Refer chapter B.4 for details.

C.4 ADDITIONAL REQUIREMENTS

Additional requirements: R.T.C. backup battery, and remote firmware/configuration

upgrade

1. An R.T.C. backup battery is required as defined per direct/CT connected meter+

gateway/Data Concentrator at p. 119 – all relevant sections.

2. Remote and direct firmware update per gsteway/Data Concentrator - are required as

defined centrally per direct/CT connected meter+ gateway/Data Concentrator at p.

119 – all relevant sections.

3. Remote and direct configuration files (TOU/DST) update – are required as defined

centrally per direct/CT connected meter+ gsteway/Data Concentrator at p. 119 – all

relevant sections.

LIST OF RELEVANT STANDARD PUBLICATIONS

1. IEC/EN 62052-11 (2003 ( Electricity metering equipment (A.C.) - General

requirements, tests and test conditions - Part 11: Metering equipment

2. IEC/EN 62053-21 (2003 ( Electricity metering equipment (A.C.) –particular

requirements –Part 21: Static meters for active energy (classes 1 and 2)




3. IEC/EN 62053-23 Ed. 1.0 b: 2003 Electricity metering equipment (A.C.) - Particular

requirements - Part 23: Static meters for reactive energy (classes 2 and 3). Reactive

energy not required and shall not be tested against standard.

4. IEC 62058-11 (2008)Electricity metering equipment (A.C.) – Acceptance inspection -

Part 11: General acceptance inspection methods

5. IEC 62058-31 (2008(Electricity metering equipment (A.C.) – Acceptance inspection -

Part 31: Particular requirements for static meters for active energy (classes 0,2 S,

0,5 S, 1 and 2).

6. IEC 60605 (1994)Equipment Reliability Testing - Compliance test plans for failure rate

and mean time between failures assuming constant failure rate

7. IEC 60300-3-2 (1993 ( Dependability management - Part 3: Application guide - Section

2: Collection of dependability data from the field

8. IEC 62059-21 (2002 ( Electricity metering equipment - Dependability - Part 21:

Collection of meter dependability data from the field

9. IEC 60068 (1988 ( Environmental testing

10. IEC 60529 (2001 ( Degree of protection provided by enclosures (IP Code)

11. IEC 60695-11-10 Test flames – 50 W horizontal and vertical flame test methods

12. IEC 62056 series of standards:

12.1. IEC 62056-42: Physical layer services and procedures for connection-oriented

asynchronous data exchange

12.2. IEC 62056-46: Data link layer using HDLC protocol

12.3. IEC 62056-47: COSEM transport layers for IPv4 networks

12.4. IEC 62056-53: COSEM Application layer

12.5. IEC 62056-61: Object identification system (OBIS)

12.6. IEC 62056-62: Interface classes

12.7. IEC 62056-21: Direct local data exchange (3d edition of IEC 61107) describes

how to use COSEM over a local port (optical or current loop)

12.8.

13. Dependent on proposed line-pair communication protocol proposed by manufacturer:

13.1. If Euridis communication is proposed: IEC 62056-31: Electricity metering -

Data exchange for meter reading, tariff and load control - Part 31: Use of local

area networks on twisted pair with carrier signaling.

13.2. If M-Bus is proposed: EN/IEC 13757-{1, 2, 3}: Communication systems for

meters. 13757-1) Data exchange.

13757-2: physical and link layer, 13757-3: implementation layer.




13.3. If RS-485 is proposed: ANSI 485 standard.

BIDDER RAM DECLARATION

a) The Bidder shall state in Table A1 of the Annex AA attached to this document, the

minimum guaranteed MTTF, and the operational service life length values of his offered

meter, when operated within their specified environmental extreme conditions, as per the

Specification of the meter. The sum rate and these components values as predicted

and verified (tested) will be reflected at MTTF state.

b) The Bidder shall state also in Table A2 of the Annex AA, the RAM historical field data of

his offered meter.

c) The Bidder shall state the rationales for his above-mentioned declarations

(usage/tests/analysis/estimation).

The reliability prediction results should be reported in methods and procedures of IEC

62059-41 as for non-repairable system

14. Communication hardware:

For communication hardware considerations of terminals, screws and cables

manufacturer must refer to chapter D, section 18, p. 11 of this Specification.




chapter D Meter Gateway, Specifications for Meter gateways/Data Concentrators

Introduction

This specification lays down the requirements for the procurement of residential / condominium

meters data concentrator equipment and accompanying hardware/software tools to enable

installation, maintenance and troubleshooting. The term GW/DC refers herein to Gateway or

Data Concentrator.

This specification is in two parts; the first part presents the scope and general requirements of the

GW/DC project and the second part is a table containing detailed requirements that will form the

basis for the evaluation of the tender.

Part 1: OVERVIEW

1. Scope: layout of the array of Gateways/meters for a residential / condominium building

4. The meter gateway (GW)/ data concentrator, in our context, relates to the use of twisted pair

technology for the last-mile (connection among the different metering vendor to the GW/DC).

The minimum requirement is for a gateway: i.e. a system without memory storage, but with

connectivity to all meters connected through it. The more elaborate solution is of a Data

Concentrator: capable in addition of storage of consumption data, load profile, event log – for

all the meters.

5. The solution should provide stable remote and also direct load profile daily reading, for

typically 120 apartments, through cellular modem. The solution should also fit reading a single

meter load profile for a longer period of up to 30 days. Cellular modem protocol should be

3.0G (Edge) or better: 3.5G or 4G (LTE).

6. The proposal should present a solution for a typical residential / condominium model of 120

apartments. The solution should present how many GW-s are required for the typical

residential / condominium model. The proposal should relate to the typical residential /

condominium model. That way a comparative method is enabled between a technology with

32 meters per gateway for example, and a technology with 200 meters per gateway.




Figure 12: a typical Israeli residential model serving as Techno-Economical evaluator and containing 120 apartments.

Manufacturer has to specify how many Gateways/Data Concentrators are required, how many meters are

connectable to a single gateway/Data Concentrator. Master gateway does not necessarily reside at the highest floor.

It is optional to arrange the gateway at any arrangement inside residence as long as it is accessible. Figure 13 is an

alternative view of the required project. The connecting thread through all gateways/DC-s symbolizes that all

gateways connect to same twisted pair.

A manufacturer proposing a single gateway/Data concentrator sufficient for two buildings shall also be accepted.

Main theme is that there are 120 apartments per building. For a list of all permitted protocols the bidder is referred

to Figure 16, p. 61. For a list of all permitted cellular generations the reader is referred to figure 14.




Figure 13: a second demonstration of the Techno-Economical model, enabling comparative evaluation of solutions.

If larger than two hierarchies are required, then manufacturer must specify that. The connecting thread through all

gateways/DC-s symbolizes that all gateways connect to same twisted pair.

7. It is a spec requirement that from a single building there shall be a single gateway/data-

concentrator concentrating all data from all gateways/Data Concentrators and a single SIM-

CARD is dedicated to each building. It is known that some technologies use a master gateway

and slave gateways, and some technologies have a FAN-IN4 of >100 meters to a single

gateway/Data Concentrators, so a single gateway/Data Concentrator is sufficient per a

building.

8. It is spec requirement that manufacturer should submit at his proposal, a detailed layout

schematic of the modules allocation inside the building. The schematic should provide

implementation details responding to Appendix F: Meter Gateway, sections herein.

9. The GW/DC is responsible for the acquisition and processing, of data from the meters. If

proposed solution is a DC then it is also responsible for recording and storing. The DC is

typically installed close to building entrance. Either: at the entrance to the building, or close to

the roof. Manufacturer should provide cables and antenna for installation of end point antenna

outside building, preferably on the roof.

10. The GW/DC should support connection to the WAN environment via cellular generation 3.0

(Edge) or better: 3.5G or 4G generation (LTE) and terrestrial dial up telephony network. Figure

G.3. is repeated for convenience:

4 FAN-IN – number of meters accessible at most to a single gateway/data-concentrator




Figure 14: The cellular protocol generations enabled by this tender for gateways/data-concentrators. The

phones are heuristic only and symbolize a modem of generations 3.0G (Edge) or better: 3.5G or 4G (LTE).

11. The average residential / condominium building model, is also taking into consideration that in

Israel most buildings are made of reinforced concrete, and that they include an internal

metal door, as dictated by Israeli rules of construction. Therefore the apartments and the

building form some sort of a Faraday cage. It is the responsibility of the bidder to provide and

budget extension comm. Cables that enable routing an antenna outside of the building.

Preferable solution is locating the antenna on the roof, but manufacturer may propose an

alternative solution bound to IECo approval.

12. Each gateway/Data Concentrator collects data from meters connected to it, and subsequently

delivering processed data to the Meter Operations Center to Metering Management

SoftwareMMSMeters Management System (MMS) system. Eventually entire building and all

the building connected should be capable of remote reading by the MMS system.

13. Main functionalities typically include automatic detection of meters, meter

registration/cancellation, meter synchronization, and periodic and on-demand reads.

14. The meter manufacturer may cooperate with another company to propose a universal

gateway for example. A cooperation of two manufacturers or more is possible, as long as

there is a single integrator that is sole responsible for everything within project and especially

the following items:




a) Integrator must be the manufacturer of at least one hardware component of direct/CT

connected-CT meter, gateway/data concentrator.

Integration of GW/DC to meters (direct meter and CT connected meter) requirement

#1. Ability of GW to read an array of meters, including load profile, consumption report,

and event log. Ability to send messages to individual meters. That means that the

message handling chapter of selected communication standard should be implemented.

b) Integration of GW/DC to meters requirement #2. In case GW/DC is not from same

manufacturer as meters, then it is responsibility of the Integrator / contractor to integrate

GW/DC to meter, within a reasonable time. Meters and GW/DC should be submitted to

IECo during technical tender phase, already integrated.

15. Integration of GW/DC - to "Metering Management software" (MMS).

1) Primary manufacturer provides a: "meter management software", it must still provide a

detailed knowledge and low level routines for direct communication to that software

database.

2) In addition, the manufacturer shall provide all required assistance to IECo, while IECo

computerization department (AMAT) implements the driver to IECo current billing system

named SAP system named "Shoval". That includes low level routines if required, and

withstand a period of 3 months from signing the contract. The low level batch routines, if

required, should be executable from high level software, such as dot NET (C#) software.

These routines may be required for enabling direct access to manufacturer's MMS

database.

Integrator is responsible for everything with respect to IECo even if there are sub-

contractors performing the project or delivering some modules.




Figure 15.: integration to metering management software provision of an independent “metering management

software.

c) Experience of IECo is that cellular modems become idle due to communication erroneous

events, such as network power-down due to cellular network maintenance. Since

Gateway/Data Concentrator communication to MMS is cellular, manufacturer is required

as must, to arrange for a hardware/other proven automatic periodic modem reset,

usually once a day. IECo experience shows that software reset is usually partial and

insufficient. In case modems idle-ness is serial, it is manufacturer responsibility to remedy

it through hardware periodic automatic modem reset.





For communication hardware considerations of terminals, screws and cables manufacturer

must refer to section 18, p. 59 of this specification.

17. Responsibility as regards to IECo output files:

1.17.1. IECo output files are defined at Chapter I.4., pp. 143-152. It is responsibility of MMS

system provided by manufacturer to collect all data mentioned at these files: 1) IECo

billing file chapter I.5, pp. 138-147. 2) Load profile, Chapter I.6., pp. 148-162. 3) Events log

file, chapter I.7. pp. 162-164.

1.17.2. It is responsibility of manufacturer to provide all data required, and to be responsibly of

schedule for integration to "Shoval" IECo systems.

1.17.3. It is "Shoval" that produces IECo output files as described at 1.13.1 above. In order to

obtain that all data as defined at sections 1.13.1.1.-1.13.1.2., should be accumulated and

provided by manufacturer MMS. Assistance to IECo is as defined at section 15.3 p. 57.

18. Additional requirements: R.T.C. backup battery, and remote firmware/configuration upgrade

1.18.1. An R.T.C. backup battery is required as defined per direct/CT connected meter+

gateway/Data Concentrator at p. 119 – all relevant sections.

1.18.2. Remote and direct firmware update per gateway/Data Concentrator - are required as

defined centrally per direct/CT connected meter+ gateway/Data Concentrator at p. 119 –

all relevant sections.

1.18.3. Remote and direct configuration files (TOU/DST) update – are required as defined

centrally per direct/CT connected meter+ gateway/Data Concentrator at p. 119 – all

relevant sections.


18.1. Manufacturer should provide IECo with instructions what is required and what is maximal

torque to be operated over the screws for tightening twisted pair cables.

18.2. It is manufacturer responsibility for screws and terminals materials recommendation to be of

non-corrosive and non-galvanic plating or non-corrosive and non-galvanic materials.

18.3. It is manufacturer responsibility to correctly instruct IECo which cables to use to be of non-

corrosive plating or non-corrosive materials. Meters, Gateways and communication cables shall

be installed by IECo.

18.4. It is manufacturer responsibility to recommend on cable types for communication wiring of

the two pair communication. Manufacturer should describe required electric parameters from the

wires: impedance, insulation, etc. Wires should be standard.




1.1 Communication Technology – definition of permitted protocols and requirements

1.1.1 DC-s shall communicate with meters (twisted pair) according to one of protocols specified

at p. 7 section 6 above. Vendors that reply to this spec should follow one of the above

mentioned protocols, and provide certificates and test reports on the protocols.

Figure 16: 3 communication protocols optional to the tender specification.

For this tender only the protocols: M-Bus, Euridis and RS-485 shall be accepted. A manufacturer

proposing Power-Line-Communication (PLC) technology shall not be accepted at the current tender.

The same rule abides to RF technology. RF technology shall not be accepted at this tender.

1.1.2 Each GW/DC should be able to support communication with at least 32 meters. But as

stated at p. 8, clause 6, the techno-economic model should relate to how many GW-s or

other modules such as repeaters/enhancers, are required per a standard residential

/condominium building.

1.1.3 If additional modules such as repeaters/enhancers are required –then manufacturer

should specify that also.

1.1.4 Each GW/DC should be able to communicate with meters up to a distance of 100 m.

(Average distance between a house and a corresponding meter is 20 m).

1.1.5 GW/Data Concentrators should be able to access 99.5% of meters.

1.1.6 After a period of stabilization, availability and reliability of system should reach 99.5%.

If additional components are required in order to improve availability/reliability to 99.5%,

then it is responsibility of manufacturer to propose and budget at initial proposition:

components, and estimate their quantity based on data of typical building including




reinforced concrete, including steel doors in apartment entrance, and single additional

room at apartment.

1.1.7 GW/DC-s should provide local interface through one of the following methods:

i) RS 485 interface

ii) Infra-red optical interface as per IEC 62056-21 standard

iii) Ethernet

1.1.8 GW/DC-s shall communicate with the MMS via cellular communication of 3.0G generation

(Edge) or generation 3.5G or 4G (LTE).

1.2 Installation approach

1.2.1 GW/DC-s should be installed prior to installation of corresponding meters.

1.2.2 Technician should not require prior knowledge of the low voltage network structure to be

able to carry out installation process. (Checks and studies of the networking shall be

performed once during the preliminary stage).

1.2.3 Primary manufacturer should provide installation and testing equipment within tender

proposition and budget it at separate item.

1.3 Delivery and Maintenance

1.3.1 The vendor shall submit a brief description of the system(s), its architecture and function

1.3.2 The proposed system(s) must conform to the requirements of IEC 1036 as a minimum

1.3.3 he vendor shall specify the levels of electromagnetic emissions of his proposed system(s)

through:

i) Radiation

ii) Conduction

The levels specified shall be supported by acceptable specification and/or standards.

1.3.4 The vendor shall provide together with and as part of the system all the necessary

software required to perform the functions and activities as described in the table of

requirements

1.3.5 The vendor shall provide hardware and software tools to identify faults and malfunctioning

in the field

1.3.6 The vendor shall provide all necessary maintenance manuals as described in the table of

requirements

1.3.7 The vendor shall provide a sample concentrator, concentrator software, operating manuals

and appropriate interface for testing (within 30 days from date of contract agreement).

1.3.8 The concentrator shall have a warranty against any defects, which may develop due to

faulty material, calibration, transportation or workmanship for a period of 4 years from the

date of delivery. All defective concentrators shall be replaced at the supplier's cost.




1.3.9 After delivery of concentrators the vendor shall conduct training for at least 3 days for at least 20

people on site in Israel. The vendor should provide a training syllabus among documents

submitted for tender.

1.3.10 The vendor shall meet the cost of the training. Training shall cover and not be limited to:

1) GW/DC features

2) GW/DC installation

3) GW/DC software

4) GW/DC communication features

2. MMS system, introduction: performance and latency requirements

Herein are main requirements from MMS. Table 2 further shall expand requirements.

ID Requirement Importan

ce

Remarks

2.2.2. Performance

2.2.2.2. Store and manage data of

20,000 meters

M

2.2.2.2. Hold/maintain data of up to 3

years in the live system

database

M Older data

should be

archived for an

additional 5

years

2.2.2.2. Schedule automated reads

per meter every single day. In

later stage scheduled

automated reads per meter at

least every single day.

M

2.2.2.2. Import, validate and store

80,0005 meter periods reads

in a single hour processing

M This calculation

is based on 15

min meter

5 80,000=4 periods/hour*20,000 meters = Total number of periods per hour per all meters.




window with a total of

approximately 1,920,0006

periods reads a day

samples and

double of

minimum

capacity and

daily uploads

2.2.2.2. Provide usage data for

creation of 20,000 bills/

statements per day

M Assuming

monthly bills are

spread over 5

days

2.2.2.2. Respond to Billing system

requests for billing input

information7 as close to real-

time as possible

L

2.2.2.2. Respond to meter reads on-

demand request within 10

minutes time

M Total response

time including

AMI should be

within minutes

2.2.2.2. Read of load profile latency Once a day

within 30

minutes reading

time per single

meter

2.2.2.2. Read of self-reads latency Once a day

within 30

minutes reading

time per a single

meters

2.2.2.22. Download a complete

configuration file to meters

Within one

month per a

single meter. A

push button

action per all

meters.

6 80,000 periods/(hour*meters)*24 hours= 1,920,000 periods/all-meters/day. = total number of periods per day per

all meters.

7 Requests from the MMS system to perform billing per a specific meter - now. Now = Close to real-time.




2.2.2.22. Remote firmware upgrade Within one

month per entire

array

Part 2: MMS – detailed Table of Requirements

ID

Requirement

Importance Remarks

Req. 2.1. Devices should satisfy IEC Standards

2.1.1 IEC 60068-2 regarding mechanical, vibrations, heat and fire resistance tests

M

2.1.2 Insulation test IEC 60060-1 M

2.1.3 Test of immunity to electrostatic discharges IEC 61000-4-2

M

2.1.4 Test of immunity to electromagnetic RF fields IEC 61000-4-3

M

2.1.5 Test of immunity to fast transient bursts IEC 61000-4-4

M

2.1.6 Test of Surge immunity IEC 61000-4-5 M

2.1.7 Test of immunity to conducted disturbances IEC 61000-4-6

M

2.1.8 Test of conducted and radiated emissions test EN 55022

M

2.1.9 GW/DC -s should conform to the degree of protection of at least IP51 as given in IEC 60529

M

2.2.1 GW/DC should have a lifetime of 15 years

Req. 2.2 Operating conditions requirements

2.2.1 Relative humidity durability range 5%-95%

M

2.2.2 Temperature range from -10oC to 60oC

M

Req. 2.3 Electromagnetic Compatibility

2.3.1 Dielectric strength: 4 kV, 50 Hz, (IEC 610-0-4-5)

M

2.3.2 Electrostatic discharge: 15 kV (IEC 610-0-4-2)

2.3.3 Burst: 4 kV (IEC 610-0-4-4)

M




2.3.4 Impulse voltage 12kV, 1,2/50 μs (IEC 62052-11)

M

2.3.5 High frequency electromagnetic field 10 V/m and 30 V/m (IEC 610-0-4-3)

M

Req. 2.4 Nameplate and Housing requirements

2.4.1 Each data DC shall be marked legibly and indelibly with the following information:

(a) Device description

M

(b) Complete model number

M

(c) Power supply voltage

M

(d) Serial No. and year of manufacture

M

(e) Transceiver Type

M

(f) Maximum Current M

2.4.2 Protection fuses on the DC housing; four-pole MCB for disconnecting the neutral as well as the 3 phases

M

Req.2.5 GW/DC Lifetime

2.5.1 GW/DC should have a lifetime of 15 years

Req. 2.6 Clock Requirements

2.6.1 GW/DC device must have a real-time clock (RTC)

M

2.6.2 Capability to synchronize RTC via communications from MOC

M

2.6.3 Capability to synchronize all "children" meters via DLMS metering application protocol

M

2.6.4 Capability to automatically carry out the Israel official DST winter-summer time change for a period of 1 year (according to supplied calendar)

M

2.6.5 Back-up solution to guarantee operation of the clock and calendar in the event that main power is lost for at least 1 week for the lifetime of the GW/DC

M

Req. 2.7 Functional Requirements

2.7.1 Meter Registration/De-registration




2.7.1.1 GW/DC-s should automatically recognize meters on installation/de-installation. (Plug & play meter registration/de-registration).

M

2.7.1.2 Status of meter registration should be communicated to and displayed on meter user interface (LED, display or installation tool)

M

2.7.1.3 In case of failure to register the meter installer should have access to tools for remotely triggering recognition process

M

2.7.2 Data receiving/transmission

2.7.2.1 The GW/DC should have three independent channels for transmission and three independent channels for reception

M

2.7.2.2 Automatically send data to central systems once a day or according to configurable schedule

M

2.7.2.3 Capability to program requests for periodic reads

M

2.7.2.4 On-demand meter reading, manual requests to specific meter

M

2.7.2.5 Broadcast capability (to all available devices)

M

2.7.2.6 Multicast capability (to selected group of devices)

M

2.7.2.7 Uncast capability (to single meter) M

2.7.3 Monitoring and Network Management

2.7.3.1 Each GW/DC should be capable of being managed as a unique device

M

2.7.3.2 Availability of monitoring and management tools to ascertain the network status at any time

M

2.7.3.3 Automatic new registrations and de-registrations should be capable of being managed without user intervention

M

2.7.3.4 Automatic configuration of repeaters following a change in network topology

M

2.7.2 Data Transfer

2.7.2.1 The GW/DC should transfer information on each dependent device including:




(a) Physical device identifier, preset in the factory

M

(b) Device type or other identifiers

M

(c) MAC address of the modem associated with the device

M

(d) Device status: in service, temporary failure or permanent failure

M

(e) Load profiles for at least 4 channels on energy at 15 minute intervals, for at least 10 days

M

(f) Daily data for billing purposes M

(g) Meter events M

2.7.2.2 Each GW/DC should be able to transfer reading of minimally up to 32 clients. Storage is optional.

2.7.2.3 The GW/DC should transfer information on internal GW/DC events

M

2.7.2.4 Each GW/DC should be able to transfer at least 2 different tariff tables

M

2.7.2.5 Each GW/DC should be able to transfer calendar table, including DST summer/winter time change and special days for at least 1 year

M

2.7.2.5 Once the available memory is full for a particular parameter the oldest data should be deleted first to be replaced with the most recent data

M

2.7.2.6 In cases where a meter changes its GW/DC ownership, the GW/DC should be able to update its meter list, but continue to store data of de-registered meter until a scheduled date for data transmission to MOC

M

2.7.3 Event Logging

2.7.3.1 GW/DC-s should be capable of reading the following events from the meter

M

(a) Standard event log M




(b) Tamper detection event log M

(c) Power quality event log (start/stop) M

(d) Demand Management event log M

(e) Common event log M

(f) Power/electricity event log M

(g) Firmware event log M

(h) Synchronization event log M

(i) Disconnect event log M

(j) Time correction event log M

2.7.5 GW/DC self-diagnostics and Reporting

2.7.5.1 Communication statistics log and reporting

M

2.7.5.2 GW/DC-s can be configured to detect loss of communication to meters that previously had good communications

M

2.7.5.3 Provision of push notifications about sudden loss of communications from meters that previously had good communications

M

2.7.5.4 Internal "DC events" log with timestamp M

2.7.5.5 Automatic management of retries in the data reading/transmitting

M

2.7.5.6 Logical reboot function M

2.7.5.7 Remote firmware uploading for meters and DC itself

M

2.7.5 Meter synchronization

2.7.5.1 Perform synchronization of all its dependent meters once per day

M




2.7.5.2 Capability to execute synchronization cycle manually

M

2.7.6 Power-cut handling

2.7.6.1 Data should not be harmed in even of sudden power cut situation

M

2.7.6.2 During shutdown process all unsaved data should be saved to the flash memory

M

2.7.7 Previous data recovery

2.7.7.1 If the data for a scheduled task cannot be sent, at the next scheduled time for sending data the DC should automatically try to send both the current data and previous missing data. E.g. for a daily task, if data from yesterday could not be sent, today the DC should automatically try to send yesterday and today's data.

M

2.7.8 Firmware upgrade

2.7.8.1 Capability for local and remote firmware upgrade

M

2.8 Security

2.8.1 Data/message encryption at store and in transit

M

2.8.2 Password management M

2.9 Maintenance

2.9.1 The following maintenance manuals should be provided:

(a) For field maintenance level M

(b) For laboratory maintenance level M

(c) Test equipment manuals including testing instruction and test equipment description, theory of operation

M

(d) Storage instructions M

(e) Software manuals M




2.9.2 The following tools should be available for handling faults and malfunctioning in the field:

(a) Facility for checking the communication between the GW/DC and meter and between the DC and MOC

M

(b) Receiving an indication via display or LED, when GW/DC is properly connected to the voltage network

M

(c) A local tool/facility for readout of data and log file

M

(d) Facility for local reprogramming of the GW/DC

M

(e) Availability of GUI map/flowchart/diagram which shows the status of all meters connected to the GW/DC

M

Abbreviations:

GW/DC Gateway/Data

Concentrator

MOC Meter Operations

Center

LAN Local Area Network

WAN Wide Area Network

Edge Cellular generation 3.0

LTE Cellular generation 4.0




CHAPTER E. METER MMS DRIVER: REQUIREMENTS FROM METERING

MANAGEMENT SOFTWARE DRIVER

Interface to metering management software

As specified at GW/DC appendix, the manufacturer winning the tender is responsible also for

communication to IECo. The manufacturer shall provide - metering management system for

remote communication, of its own. The manufacturer shall in addition provide an API8 enabling

simple full access to its meter management software database. By an API it is not meant an

existing application such as SQL studio Microsoft, but rather an API enabling IECo a higher level

access to database. Any suggestion by manufacturer is acceptable bound to IECo judgment, and

manufacturer should attempt to convince IECo of API sufficiency. Requirement to provide all

technical material and low level access routines for development of drivers to IECo billing

software SAP "Shoval" software.

7.1.1. The manufacturer shall provide – a Metering Management SoftwareMMSMeters

Management System (MMS) system for remote communication, to all meters. For definition of

MMS basic functionality see chapter XX, MMS.

7.1.2. In addition, the manufacturer shall provide a driver to IECo current billing system named

SAP system "Shoval".

7.1.3. The drivers shall be defined and developed by computerization section of IECo (AMAT).

The manufacturer bidder should provide the "Computerization section" of IECo (AMAT), with all of

the information required by that department. In addition if low level batch routines, that are

executable from high level software, such as dot NET (C#) software, are required - then the

manufacturer should provide them to that IECo section. These routines may be required for

enabling direct access to manufacturer's MMS database.

CHAPTER F. METERS MANAGEMENT SOFTWARE: REQUIREMENTS FROM

METERING MANAGEMENT SOFTWARE

8 API – Application Program Interface.




Manufacturer should propose and register at list of deliverables, a metering management software

capable. Herein are specified the requirements. A simple MMS may also be sufficient if it abides

to the following sections.

F.1 GENERAL REQUIREMENTS

All meters in tariff trial should be managed under one meter data management (MMS)

system

MMS should include head end system (HES) functionality

"Shoval" SAP billing system is the billing system.

Vendors that reply to this RFP should propose an interim solution to work with legacy

system until SAP is available. This solution does not necessarily have to be provided

through the MMS.

F.1.1 FOR THE PROJECT THE FOLLOWING HAVE BEEN IDENTIFIED AS "MUST HAVES"

FOR THE FIRST STAGE:

- The requirements previously specified at table p. 63.

- Transformer level metering/balancing

- Ability to share data for use in customer-facing applications. E.g. via web-services

interface

F.F.2. THE FOLLOWING HAVE BEEN IDENTIFIED AS "LATER STAGE":

- Event notification:

o Outage event

o Voltage disruptions

o Fraud/Tamper

- Data warehouse9

- Test , production, development environments

- Solution should be "Shoval" SAP.

The implementation of later stage options is dependent on IECo management decisions.

F.2. DELIVERY AND MAINTENANCE

H.2.1 The vendor shall submit a brief description of the system(s), its architecture and

function

H.2.2 The vendor shall provide all necessary maintenance manuals

H.2.3 The MMS shall have a warranty for a period of 3 years from the date of delivery.

9 Data Warehouse – a database for storage of meters data, as acceptable at: MMS systems.




H.2.4 The vendor shall conduct training for at least 10 days for at least 10 people on site in

Israel. The vendor should provide a training syllabus among documents submitted for

tender.

H.2.5 The vendor shall meet the cost of the training.

H.2.6 MMS shall be installed on IECo servers.

H.2.7 MMS shall be delivered with licenses for at least 5 IECo employees.

H.2.8 MMS shall enable separate installation at different servers of database and application.

H.3. PART TWO - MMS REQUIREMENTS TABLE

Next, you will find a list of requirements for the IECo Project MMS solution.

1. The table is structured as follows:

“ID”: each of the listed requirements has a unique ID for referencing purposes

“Requirement”: this columns contains a text description of the requirement for the MMS

“Importance”: we distinguish 2 statuses:

“M” = Must Have for the first stage of the project during which IECo will continue to use legacy

systems for billing. This requirement must be fulfilled by the proposed solution; the required

functionality must be available before first meters are installed in Q1 2015.

“L” = Must be possible in the later stage from 2017 once SAP is implemented. “First Stage”

and “Later Stage (Options)": in case the way of implementing the requirement is different for

the first stage of the project versus the following stages, an indication of the way in which the

requirement should be filled, is given in the respective column. The solution of the first stage

of the project must support the requirement in the way as described under “First Stage” and

be “upgradeable” in line with the description under “Later Stage (Options)” without needing to

be (partially) rebuilt.

“Remarks”: this column includes some extra information or clarifications regarding the

requirement

2. There are 3 main categories in the requirements as listed below:

Meter-to-Cash supporting functionality can be regarded as “core” for an MMS-S. This

category and the majority of its detailed requirements is “Must have” for the Project.

The Operations category contains 2 types of functionality: reporting aggregated

consumption/production at the transformer level is considered a "Must have". The aggregated

reporting at transformer level as supported by an MMS is typically a monthly report, not a near

real time report. Delivery of (outage and voltage) alarms, including in near-real time, and

outage/voltage event logging are not a priority in the first stage.




6. Table of requirements:

ID Requirement Importance First Stage Later Stage

(SAP)

Remarks

6.1. General Requirements

6.1.1. MMS, in our context, serves not

only as a data repository but as

an umbrella of services that

enable additional processing.

The MMS must be able to

perform analytical services,

such as the following per a

specific meter through the

gateways/DC-s:

Collection of load-profile,

convertible preferably to

.XLS format

Collection of consumption

as defined at IECo

Collection of Events log

M

6.1.2. The MMS must allow at least

basic viewing, editing and input

of all MMS data.

Enable access via user interface.

M

6.1.3. The MMS must enable access

to all data for application

"Shoval" via API. Requirements

are defined at chapter on driver

to MMS.

Minimal API is provision of

username and password to

access a standard database e.g.

SQL, Oracle, Access. Other

requirement is for code to be

embeddable at the above IECo

applications as batches.

M




6.1.4. Basic reporting and analysis

must be available on all MMS

data in such way that it does

not compromise the

performance of operations of

normal MMS tasks

M

6.1.5. The MMS should support 4

different types of data, and

related processes:

Meter device, meter

relations and device

data

Consumption data

Billing related info (e.g.,

tariff types, TOU types,

customer segments)

Event log

1.

M

6.1.6. The MMS should support all

data concentrator functionality

as defined in the specifications

for smart meter data

concentrator

M

6.1.7. The MMS could also support

additional types of data, and

related processes:

Operational

information; i.e., outage

alarms

Power Quality events

such as low or high

voltage alarms

L




6.1.8. The focus of the project is on

residential meters. The MMS

should support residential

meters.

M

6.1.9. The MMS should be able to

register the relation between a

main meter, and a

gateway/Data Concentrator.

M EV not considered

a priority at this

stage

6.1.10. The MMS should be able to

register the change of

customers in a premise, but

without necessarily knowing the

customer name and info; to

create a billing slice

M A solution

should be

offered but

does not

necessarily

have to be in

MMS

This will be

done via SAP

6.1.11. The MMS must be able to use

“time-slices” on all its entities

and attributes, and apply these

time-slices in calculations (e.g.,

ability to change the TOU

aggregation scheme as of a

certain date, and aggregate all

relevant 15’ minute periods,

before the date of change using

the old version of the formula,

while using the new version of

the formula on 15’ minutes

periods data relating to a time

after the change)

M It is expected that

aggregated data

will be passed to

billing system

6.1.12. There should be a logging of all

events in the MMS for future

analysis/reporting.

M

6.2. Functional Requirements per

Business Domain

6.2.1. consumption to billing chain

functionalities

6.2.1.1. Able to interface with SAP M




6.2.1.2.

Support online end-to-end

chain check during new meter

device installations

M

6.2.1.3.

Support service address with

multiple meters (apartments

and “commons” meters) and

logical relation between meters

M

6.2.1.4.

Interface with and obtain meter

interval data (15’) from multiple

head ends, at least daily

acquisition.

If meters count cumulative TOU

registers, also collect these

data.

M

MMS should

collect aggregated

and interval data.

CELLULAR and

twisted-pair

meters should

both be

supported

6.2.1.5.

Support import and export data

series for a single directly

connected residential meter

point

M

6.2.1.6.

Support import, export, check

reads, and reactive data series

for a single CT connected meter

point

M

6.2.1.7.

Support on demand punctual

meter reading request for

meter data (near real time)

M

only by

operational

users via

MMS

operational

users via

MMS and/or

customer

services

representativ

es via SAP

CRM

6.2.1.8.

Perform automatic validation

on meter data through protocol

layers, with a logging of meter

points to be investigated

manually by users

(dlms/cosem for example

M via MMS

operational

users via

MMS




include auto-validation)

6.2.1.9.

Automatically propose

replacement interval data

through estimation (e.g., in case

of missing data), but with an

indication that it is a

replacement

M

6.2.1.10. Support manual triggering of an

estimate M

6.2.1.11.

Support manual user editing of

interval data, including copying,

deleting; through user screens,

and while keeping an audit trail

of changes

M

6.2.1.12. Store validated meter data M

6.2.1.13.

Make validated meter data

available for use by other

processes, such as

aggregations/reporting at

"Shoval" IECo application.

M

6.2.1.14.

Summarize interval data into

billing determinants (e.g., time

of use buckets)

M

6.2.1.15. Store summarized usage M

6.2.1.16.

Generate aggregated output file

for the SAP-SHOVAL billing

system

M

6.2.1.17.

Allow Tariff schemes and TOU

schemes to be updated through

user screens

M

For

operational

users via

MMS

6.2.1.18.

Support all knowledge by

manufacturer for generation of

interface with SAP billing

system, preferable according to

L




SAP standards.

6.2.1.19.

Receive and register a

confirmation from the head end

about disconnect/activation/re-

energization or capacity

reduction/reinstatement having

been executed at the

switch/meter.

M

6.2.1.20.

Provide interface for manual

meter reads and indicate as

manual read

M

Through a

dedicated

screen, and

file upload

Cases where

meter was

broken, replaced

6.2.1.21. Support billing cycle triggered

by SAP Billing system L

6.2.1.22. Support on-demand file export

to billing system M

6.2.1.23.

The MMS is required to support

meter disablement/

removal/replacement cases of a

meter

M

6.2.1.24. Aggregate DG loads per

transformer (e.g., sum impact

on a transformer of all DG’s

inside premises that are fed

through this transformer);

typically a monthly calculation

M

6.2.1.25. Generate reports and/or

provide user screens that show

reporting results ; typically on a

monthly basis

M

6.2.1.26. Provide to the Operations

department the validated

metering data (15’ series)

according to similar timescales

as applies to the aggregation

reports (i.e., monthly).

M

6.2.1.27.

Compare the sum of

M




consumptions at Home level,

from EV’s and production from

DG for one specific transformer,

with the metered value at the

transformer for the same 15’

period. Identify deviations that

are not justified by technical

losses alone.

6.2.1.28. Provide overview (report) of

unjustifiable deviations. The

report should reflect power

losses and possible thefts.

M

6.3. Functional requirements

related to administration

aspects

6.3.1. Configuration

6.3.2. Authorizations

6.3.2.1. Allow an administrator profile

to assign user profiles to users,

and user rights (for viewing,

entering, changing specific

types of data) to user profiles.

Provide administrator screens

to allow this activity.

M

6.3.2.2. All users must log in to the

system using a user name and

password, which gives them

access for viewing and/or

editing in to those areas as

defined by their user profile

type.

M

6.3.3. Audit trail

6.3.3.1. Logging of all modifications to

MMS data, who did it, and

when

M




6.4. High Level Technical

Requirements

6.4.1. Performance

6.4.1.1. Store and manage data of X

meters

M X = 50,000

6.4.1.2. Hold data of up to 3 years in the

live system

M Older data should

be archived for an

additional 5 years

6.4.1.3. Schedule automated reads per

meter every X. In later stage

scheduled automated reads per

meter every X and at least every

Y.

M X = 1 day

X = 4 hours

Y = 1 day

6.4.1.4. Import, validate and store X

meter reads in a Y hour

processing window with a total

of approx Z reads a day

M X =

9,600,000

(=50,000*96

*2)

Y = 1

Z =

9,600,000

This calculation is

based on 15 min

meter samples

and double of

minimum

capacity and daily

uploads

6.4.1.5. Provide usage data for creation

of X bills/statements per day

M X = 5,000 Assuming monthly

bills are spread

over 5 days

6.4.1.6. Respond to Billing system

requests for billing input

information

L

6.4.1.7. Respond to meter reads on-

demand request within X time

M X = 10

minutes

Total response

time including

AMI should be

within minutes

6.4.2. Flexibility

6.4.2.1. Provide flexible scalability to

support number of meters as

described in the performance

M




requirements

6.4.3. Reliability

6.4.3.1. The Solution to support fail over

to back up site

M

6.4.3.2. Support system recovery time

of no more than 1 hour (backup

system operational within the

hour)

M

6.4.3.3. The system must be able to deal

with weekly regular

maintenance activities in less

than 4 hours per week

M

6.4.4. Availability

6.4.4.1. The system should be online

and available 99.97% of the

time.

M

6.4.4.2. Support X IECo customer service

representatives/users accessing

the system simultaneously

M X = 30 In the first stage

operational users

will also provide

customer service

6.4.5. Usability

6.4.5.1. User screens should include

links to support guides

M

6.4.5.2. The system should provide user

friendly navigation

M

6.4.5.3. The system should provide

automatic refresh of screens

M

6.4.6. Standards

6.4.6.1. The solution must SAP

compatible

N/L

6.4.6.2.

The solution is to be compatible

with IEC 62056 DLMS/COSEM

L




6.4.6.3. The solution must be compliant

with CIM as specified in IEC

61970

M

6.4.7. Security

6.4.7.1. The solution must comply with

IECo Information Security

Policies and with Israeli

legislation and regulations

M

6.4.7.2. The solution must comply with

IEC and Israeli data protection

legislation and regulation

M

6.4.7.3. There should be separation

between the MMS database

and MMS application execution.

i.e. the MMS database should

be installed to a separate

server.

M

6.4.7.4. MMS should perform pre-

authentication of DC before

enabling access, according to

one of:

DC MAC address

DC serial number

DC IP address

DC passwords

DC keys: private, public, other

M

6.4.7.5. MMS should enable uni-

direction: i.e. to enable DC

access to MMS only by request

from MMS

M

6.4.8. Licenses

6.4.8.1. Single installation with access at

least 15 users, based on

separate usernames and

passwords.

6.4.8.2.

Enable two licenses: test and

active. Two versions of MMS-s

shall exist.




CHAPTER F.1: QUESTIONNAIRES & DECELERATIONS

CHAPTER F.1.1.: RELIABILITY, AVAILABILITY AND MAINTAINABILITY (RAM)

1. Definitions

The following definitions are valid for all Reliability, Availability, and Maintainability (RAM)

purposes in the Specification for electronic watt-hour meters. The RAM parameters are

characteristics of the meter design and production only, when they are properly used and

maintained.

1.1. Electronic Meters – See items of Specification least

1.2. Failure – Failure is any event where a meter has stopped functioning, or exceeds its

specification limits, and requires repair or replacement.

1.3. Failure Rate – The failure rate, of a meter is the number of failures per operating time

unit. The system failure rate for the meter will mean the sum of the failure rates of its

components, i.e. = 1 + 2 + 3 + … + n.

1.4. MTTF – MTTF is the mean time between the meter installation and operation, and the

first failure.

1.5. Reliability – Reliability is a design characteristic defining the ability of a product to

perform satisfactorily. Therefore: Reliability is the probability that a meter will perform

without failures, for a pre-defined period of time, when used under stated conditions (at

IECo site). MTTF is a reliability parameter, in accordance with definitions of IEC 60050-

191.

1.6. Life Length – Life length of a meter is the time until the first failure in operation.

1.7. Maintenance – Maintenance is any action taken to replace a faulty meter with a properly

working one, after a failure, and test the operable condition of a replaced meter.

1.8. Maintainability – Maintainability is a design characteristic defining the ability of an item to

be replaced quickly and checked for its operable condition after a failure.

Note:

Since IECo's approach to meter fault elimination is by means of valid replacement of a damaged

meter by another one (new or used, however tested as revised product) conducting by

appropriate billing, maintainability is converting to influence of definite meter type on mean time

of these replacement.




2. RAM Requirements

A RAM report is applicable to any of the three major hardware components: direct meter, CT

connected meter, gateway/or data concentrator.

The Bidder is required to provide IECo with meters with the following RAM properties:

2.1 Reliability

2.1.1 Operational TTF (time to first failure): At least 15 years.

2.1.2 Operational service life time: At least 15 years, without the need for maintenance

or recalibration.

2.2 Maintainability – The meter will be “preventive maintenance” free for its entire life

length.

3. RAM Information

The Bidder shall submit to IECo the following information regarding RAM:

3.1. Reliability prediction report according IEC 62059-41.

3.2. RAM activities in his plant concerning the offered meter, and how he is organized to

perform these activities.

3.3. Supervising on his sub-Bidders, suppliers and vendors for their RAM activities.

3.4. The optimization shall consider the following:

3.4.1. Criticality (long supply time, high price, short life length, high failure rate, single

supply source, sensitive or vulnerable materials, etc.

3.4.2. Latent failure rate (), and induced failure rate (caused by human).

3.4.3. Turn Around Time (door to door).

3.4.4. Quantity in service.

3.4.5. Recommended “probability of no shortage” (spares availability) on shelf.

3.4.6. Cost

4. Bidder RAM Declaration

4.1. The Bidder shall state in Table A1 of the Annex AA attached to this document, the

minimum guaranteed MTTF, and the operational service life length values of his offered

meter, when operated within their specified environmental extreme conditions, as per the

Specification of the meter. The sum rate

and verified (tested) will be reflected at MTTF state.

4.2. The Bidder shall state also in Table A2 of the Annex AA, the RAM historical field data of

his offered meter.

4.3. The Bidder shall state the rationales for his above-mentioned declarations (usage/tests/

analysis/estimation).

4.4. The reliability prediction results should be reported in methods and procedures of IEC

62059-41 as for non-repairable system.




5. RAM Field Data

The Bidder shall submit to IECo historical RAM field data of all installed meters (identical to his

offer), at all sites, supplied during the last 5 years, by fulfilling Table A3 in Annex AA

questionnaire. A parcel of each component of

statistics. The RAM report should include specific model type, and years of thecollected data

6. Reliability Demonstration

IECo has the privilege to exercise a Reliability Field Demonstration (RFD) concerning the supplied

meter. The purpose of the RFD is to verify that the meters meet the reliability requirement, i.e.,

MTTFF of 15 years.

If subject to execution, the RFD will be conducted in accordance with the following principles:

6.1. The RFD shall be objective, quantitative and based on data collection from returned faulty

meters (see IEC 60300-3-2 Application Guide, IEC 62059-21).

6.2. The Bidder has nothing to do in the RFD, except to participate in the Failure Review

Board (FRB). However, the Bidder has to do his best in his plant in the following areas, in

order to supply to IECo with reliable meters, and this to pass the RFD with high

probability:

6.2.1. Design and Development

6.2.2. Parts, materials, and components

6.2.3. Manufacturing Processes

6.2.4. Quality Assurance and Control

6.2.5. Tests and inspections

6.2.6. Sub Bidders, Suppliers, and Vendors supervision

6.2.7. Packaging, Handling, Storage, and Transportation (PHST)

6.3. The FRB is the only body entitled to classify failures as “Relevant”, or “Non-relevant” for

the purpose of the RFD.

6.4. The Bidder is responsible for productive agency of RFD results.

6.5. The RFD shall be ended with either ACCEPT, or REJECT result.

6.6. The meaning of REJECT result is violation of the specification, and the contract will deal

with such a situation.

6.7. The RFD will be framed in accordance with standard reliability test methods.




Note:

It is recommended to:

Explore IEC 60300-2, in order to demonstrate the dependability program of the offered meter.

Explore IEC 62059-11 and IEC 62059-21, in order to demonstrate the dependability level by means of internationally agreed procedures for dependability data collection.

However, if it will be agreed between IECo and winner of the Contract, another equivalent test plan could be chosen and published, as required by the relevant national body of the country where the meter is manufactured.

6.8. The complete RFD plan, including demonstration parameters, will be prepared after

contract award, in consultation between IECo. Reliability, and Equipment Dept., and the

contract winner.




Annex AA

RAM Questionnaire

Static (solid-state) active energy three-phase meters with serial communication, Model No._____________ and ____________, complying with Specification 306-3-03-11.

1. Bidder Declaration

Reliability and Life Length

The reliability parameters of the meter are as follows:

Table A1: Meter Reliability Data

Reliability Parameter MTTF/Life

Operational MTTF (years)

Operational Service Life Length (years)

Rationale(usage/tests/analysis/estimation)

Table 7 – Meter Reliability Data

2. RAM Field Data

Table 8 - RAM historical Field data for meter Model No. ________________

2014

2013

201 2

2011

2010

2009

Field Data

Total number of installed meters

Total number of replacements for any reason

Failures due to wrong design

Failures due to faulty production

Failures due to bad use/ handling

Random failures




CHAPTER F.1.2.: BIDDER QUALIFICATION QUESTIONNAIRE

Bidder Qualification Questionnaire

Note:

The data provided in this chapter should refer only to the plant where the meters are

manufactured.

1. General

1.1 Company’s Name: ___________________________________________________

1.2 Commercial Address:____________________________________________

______________________________________________________________________

1.3 Telephone No.: ______________________________________________________

1.4 Fax No.: ___________________________________________________________

1.5 Questionnaire Respondent’s Personal Data:

Name: _____________________________________________________________

Position: ___________________________________________________________

Telephone No. (if different to 1.3 above) _________________________________

Date: _________________ Signature: ___________________________

2. Company Profile

2.1 General Description of the Company (e.g. Bidder of...):

____________________________________________________________________

____________________________________________________________________

2.2 Management Organization (attach organization chart showing directors and other key

personnel):

____________________________________________________________________




2.3 Corporate Structure:

______________________________________________________________

2.3.1 Management Organization of the Manufacturing Division/Plant/Service directly

responsible for manufacturing the Equipment or supply the Service.

___________________________________________________________________

2.4 Local Israeli Agent (if any):

Name: _____________________________________________________________

Address: ___________________________________________________________

Phone No.: _________________________________________________________

For what purposes: __________________________________________________

2.5 The profile of the Company Field

System Engineering ____________________________________________

2.6 Product Engineering ____________________________________________

2.7 Manufacturing _________________________________________________

Construction/Erection ___________________________________________

Services ______________________________________________________

2.8 Describe ownership capital and share structure:

___________________________________________________________________

___________________________________________________________________

2.8.1 Authorized Capital: _____________________

2.8.2 Issued Capital: _________________________

2.9 Annual value of work undertaken for each of the last five years and projected for the

current year:

__________________________________________________________________

2.9.1 Home: ____________________________________________________________

2.9.2 Internationally: _____________________________________________________




2.10 Attach the most recent audited financial report (profit/loss, assets, liabilities,

balance sheet), and for the two previous years.

___________________________________________________________________

___________________________________________________________________

2.11 Names and addresses of associated companies, if any, to be involved in the

project and whether as joint venture, parent, subsidiary or other.

___________________________________________________________________

___________________________________________________________________

2.12 If Company responding is a subsidiary, describe the extent of involvement, if any, of the parent company in the Project, administratively, technically, financially, other.

___________________________________________________________________

___________________________________________________________________

2.13 Name and address of Bankers from who references can be obtained.

__________________________________________________________________

__________________________________________________________________

3. Company Capabilities

3.1 General

3.1.1 Total turnover (specify total turnover for the last five years, yearly)

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

3.1.2 Detail amount of raw materials purchased by the company for the last five years (answer if corresponds to your activities).

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

3.1.3 Describe the main products and services.

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________




3.1.4 Give details of the principal equipment, which has been designed and/or manufactured:

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

3.2 Indicate number of years of experience as supplier of Product in:

3.2.1 Own country: ________________________________________________

3.2.2 International Market:___________________________________________

3.3 Number of years experience as sub Bidder/sub-supplier in:

3.3.1 Own country: _______________________________________________

3.3.2 International market: _________________________________________

3.4 Give a reference list of the major works (or contracts) that the Company had carried out

recently (last five years). Specify at least:

3.4.1 Location of the project;

3.4.2 Year of project was put in operation;

3.4.3 Materials handling with the equipment;

3.4.4 Principal technical parameters;

3.4.5 Value of the contract:

3.4.6 Scheme diagrams of other information related to the project.

3.4.7 What major obstacles were encountered, if any, in design, manufacturing, delivery,

warranty, operation and scheduling in the above major works

3.4.8 Similarity to our IECo specifications.




3.5 Personnel (fill in the table):

Table 9 – Bidder Personnel

Note:

In case the Company employs temporary personnel, please specify their qualification and quantity

with the same description as above.

Personnel Description

Department Engineers

and other

academics

Technician

s

Craftsme

n

Operator

s

Other

personne

l

Tota

l

Management

Manufacturing

Engineering

Quality Assurance

Quality Control

Sales

Purchasing

Others




3.6 Total Facilities

3.6.1 Actual area:

3.6.1.1 Manufacturing ___________________________________________ m2

3.6.1.2 Storage _________________________________________________ m2

3.6.1.3 Office __________________________________________________ m2

3.6.1.4 Erection of subassemblies __________________________________ m2

3.6.1.5 Laboratories and experimental facilities _______________________ m2

3.6.1.6 Others __________________________________________________ m2

Total: ____________________________ m2

3.7 Describe the location of:

3.7.1 Main office ____________________________________________________

___________________________________________________________________

3.7.2 Main facilities __________________________________________________

___________________________________________________________________

3.8 Main machinery available in the above facilities ___________________________

___________________________________________________________________

___________________________________________________________________

3.9 Access to the Manufacturing and Erection facilities _________________________

___________________________________________________________________

___________________________________________________________________

3.10 Detail the manufacturing capability: _____________________________________

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

3.10.1 Capacity for manufacturing the specific Meter: ________________ units / month.




3.11 Technological Capability

3.11.1 List the national and international standards used in design _____________

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

3.11.2 Specify the relevant licensing agreements signed, with whom and their purposes.

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

3.11.3 Specify the relevant “patent use” agreements signed, with whom and their purposes.

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________

___________________________________________________________________




4. Quality Assurance and Quality Control Organization

4.1 Specify the quality level the company and its subsidiaries are qualified, according to which

standards, and the name of the accreditation bodies.

___________________________________________________________________

4.2 Do you have your own Quality Assurance Manual and/or Quality Control Manual?

(Yes/No – give details)

___________________________________________________________________

4.3 Does your company have and utilize Quality Control procedures and instructions?

(Detail titles and date of approval).

___________________________________________________________________

4.4 For purchasing materials, components, equipment (Yes/No)

___________________________________________________________________

4.5 For use and maintenance of equipment (Yes/No)

___________________________________________________________________

4.6 For acceptance test of purchased material/components (Yes/No)

___________________________________________________________________

4.7 Indicate where it takes place ____________________________________________

___________________________________________________________________

4.8 For materials and products handling and storage (Yes/No)

___________________________________________________________________

4.9 For fabrication processes (Yes/No) (indicate name of procedures)

___________________________________________________________________

4.10 For shipping (Yes/No)

___________________________________________________________________

4.11 For final inspection of your products before delivery (Yes/No)

___________________________________________________________________

4.12 Do you consider your procedures and instructions are as contractual with your

client?

___________________________________________________________________

4.13 Internal Documentation and Certificates:




4.13.1 Are there any procedures regarding the issuance, distribution and retrieval system?

4.13.2 For the documentation issued for:

4.13.3 Processes: _________________________________________________________

4.13.4 Material certificates: _________________________________________________

4.13.5 Inspection and tests: _________________________________________________

4.13.6 Documents for approval by the purchaser: ________________________________

4.13.7 Does your company have procedures for design review and control? (Yes/No)

4.13.8 (Detail names and dates of approval).

4.13.9 __________________________________________________________________

_

4.13.10 ____________________________________________________________

_______

4.13.11 Describe the procedure applied to materials and products with defects:

4.13.12 ____________________________________________________________

_______

4.13.13 ____________________________________________________________

_______

4.14 Describe the capability (human resources, equipment, facilities, technology, etc.) to

perform:

4.14.1 Measurements

_______________________________________________________

4.14.2 Special tests

_________________________________________________________

4.14.3 Calibration system

____________________________________________________

5. Engineering Organization

5.1 List current Executive Directors, if any, within the engineering organization (only to be

answered if specially indicated by IECo)

5.1.1 Name: _____________________________________________________________

5.1.2 Present Position held __________________________, since __________________

5.1.3 Years experience in profession __________________________________________

5.1.4 Years experience in company ___________________________________________




5.2 List key personnel who would be assigned to Project (If more than one, please add extra

sheets).

5.2.1 Name: _____________________________________________________________

5.2.2 Present Position held __________________________, since _________________

5.2.3 Years experience in profession _______________________________________

5.2.4 Years experience in company ________________________________________

5.2.5 Would such person(s) be solely assigned to the Project?

5.2.6 (Yes/No) _________________________________________________________




6. Please fill in the following table:

Field

Number of Employees

Current Position

Engineers Technicians Administration

Conceptual Design

Research and Development

Process/System Design/ Eng.

Detail Design

Architecture

Civil Works

Construction

Electrical Engineering

Automation & Control

Manufacturing Engineering

Models

Software Engineering

Electronic Engineering

Packaging Engineering

Table 10 – Bidder Manpower Resources

Total:




7. Special Field Service Engineering Manpower

Please fill in the following table:

Areas

Number of Employees

Current Position

Engineers and

other academics

Technicians

Administration

Project Manager

Construction/Erection Management

Tests & Inspection

Laboratories:

Metallurgy

Electrical

Chemical

Quality Control

Customer Service

Table 6 – Special Field Service Engineering Manpower

Total:

Remarks: __________________________________________________________________

8. Computation Capability:

8.1 Equipment (Hardware)

8.1.1 Describe the Company’s own equipment: ___________________________

___________________________________________________________________

___________________________________________________________________




8.2 Software:

Field Program’s Name Main Characteristics

Process Engineering

Civil Engineering

Mechanical Engineering

Project Management

Project Control

CAD

Others

Table 7 – Bidder SW Resources




CHAPTER F.1.3.: BIDDER PREVIOUS EXPERIENCE &INSTALLATIONS

In this page the Bidder shall report his previous installations with the proposed

Meter (electricity companies / utilities, locations, quantities, years of installations))

Utilities name Meter type locations quantity years of

installations

Table 8 – Bidder previous experience &installations




CHAPTER "G": TECHNICAL REQUIREMENTS FOR METER

APPLICATIONS




CHAPTER G.1: METER CONFIGURABLE PARAMETERS FILES

General configurations definitions & programmable parameters:

The Bidder shall define his proposed Meter in strict compliance with the mentioned main

requirements according to the following topics.

The following abides to direct meter, CT meter, and gateway/Data Concentrator modules.

0. General requirements

0.1. In order to accomplish the TOU electric tariff / pricing in Israel the meter should

have the abilities to change/ Update parameters in the meters at the consumers

premises the update is done remotely by MMS, The meter and the supporting SW

should enable to perform this updates controlled and audited ( in file ID ) without

Changed / damaged the meter data

0.2. Updates parameters requirement : The meter updating parameters / CONFIG files

should be done by Safety method Changes should become effective after

verification the data integrity. partial data parameters should Not be accepted and

become effective in the meter.

0.3. All CONFIG files could be read /upload from the meter by means of SW in

order to compare the CONFIG files To reference CONFIG files.

0.4. Configuration software for lab should be easy to use. It should enable programming at

IECo by IECo local technicians of TOU, DST, special days, displays screens order and

any other required configuration.

Note: Meter Bidders are allowed to change the meter firmware and the relevant software in order

to comply with this requirement.

Firmware requirements

The bellow requirements apply mostly to the firmware, but also to lab maintenance software

1. TOU & Special days

1.1. The general definitions of the TOU structure are according the Table 14 TOU (2010).

Note: Updates the TOU structure (days type, seasons, etc.) is happening once to 5-10 years.

1.2. The Meter shall input and store any TOU and /or special days table covering at least one

years in one table/file.

1.3. A new TOU shall become effective immediate or at future date.

1.4. In case their are 2 tables present and future each of them shall cover at least 4

years.

1.5. At least 4 seasons per year( the seasons dates are repeating for each year)




1.6. At least 4 rates/ tariffs per season

1.7. At least 4 types of days per season (16 days type)

1.8. At least 6 Tariff change points per day indicating the beginning of tariff

1.9. Cumulative register of kWh and data shall be separately stored for each tariff

1.10. Special Days

Special days are determined as the Jewish holidays / special dates (based on moon

movement adjustment to sun based calendar ) so the days are variable and not

reparable to Gregorian calendar. The meter should support special days by implementing

the following option: Enough special points for definition of "special days" (holidays& holidays

evening )covering at least 4 (8-12 years be preferred ) About 16 holidays & holidays

evening per year is needed, some are overlapping with Saturday (Appendix B-5a –

special days) total 60-120 points .

The figures and drawings of this chapter are mainly for demonstration. The mandatory and

overriding requirements are those defined herein at chapter G.1, section 1.

Note: Meter Bidders are allowed to change the meter firmware and the relevant software in

order to comply with this requirement. This rules applies to special days and DST.

2. Self read/ Billing data

2.1. The Meter shall be able to store at least 4 self reads/ billing data

2.2. There should be feasibility to read the current data only or one or more of the

self reads.

2.3. The number of reading of self reads from the meter should be parameter (0 or 1 or 2

or 3 or 6 ) of the reading SW .

2.4. The last 4 self reads/billing should be read first (last in first out- LIFO)

2.5. Self reading shall be performed by the Meter in either one of the following ways:

2.5.1. Automatically at the end of a calendar month.

2.5.2. Deliberately, by personnel performing maintenance operations using a a portable

PC and remotely through MMS.

2.6. Self read after downloading a new configuration tables shall be a programmable

parameter.

2.7. After self-reading is performed, the maximum demand register shall be zeroed.

3. Seasons

3.1. At least 4 seasons shall be definable.

3.2. A season shall be defined by a month and a day

3.3. Season starting at 00:00 hours of the defined day in every year,




3.4. Shall be superseded when the next season becomes effective.

3.5. Holidays and weekdays shall be definable during a season.

3.6. Ending of a maximum demand time interval shall be performed before the end of a

season. If necessary, self-reading shall be performed before a new season becomes

effective

3.7. Only one season and one tariff shall be in operation during any time

4. Daylight Saving Time

Two options for implementing DST shall be accepted:

4.1. Option 1: DST for lifetime of the meter based on fixed formula.

The meter is loaded (remotely via MMS) with DST dates for a number of years – at least 2

years.

Therefore, it is now possible to define and realize the DST dates in the meter for multiple

years (covering the lifetime of the meter), without the need to change/refresh the dates

remotely via MMS.

The DST start and end dates are stipulated by the new law is as follows:

4.1.1. DST starts at 02:00 on Friday before the last Sunday in March. The meter time is

moved forward by 1 hour, so the time change is as follows: 01:59 --> 02:00 -->

03:00.

4.1.2. DST ends at 02:00 on the last Sunday of October

4.1.3. . The meter time is moved back by 1 hour, so the time change is as follows: 01:59

--> 02:00 --> 01:00.

4.2. Option 2: Different Years Date

4.2.1. Daylight saving time shall be defined by its beginning date, ending date and time

difference from standard time (one hour or more).

4.2.2. At least 4 different years dates (on & off).

4.2.3. DST time shall become effective on the date prescribed for daylight saving time

beginning, at 02:00 to 03:00 hours.

4.2.4. Standard time shall become effective on the date prescribed for daylight saving

time ending, at 02:00 to 01:00 hours.

4.2.5. In case of missing DST definition file or DST definition file expired dates the meter

shall work at standard time.

4.2.6. The different years dates shall be in destined file .A new definition file shall

become effective immediate or at dedicated date.

4.2.7. Updating meter time with PC/remotely with real time while DST is valid shall not

damage the meter time.




4.2.8. There should be a flag in the meter and accessible while reading (IEC file)

that the meter is at DST time.

4.2.9. Updating meter (Before and after the DST dates are effective) with new

dates shall change the meter time correctly to the updating dates and time.

5. Maximum demand/cumulative max demand

Maximum demand shall be calculated over 15 minute intervals for every tariff type separately:

medium, high, low.

5.1. These intervals shall be terminated by Meter time update and loss of power.

5.2. A new (shorter) time interval shall immediately begin after an interval is terminated in

order to complete 15 minutes.

5.3. Maximum demand calculation time intervals shall be synchronized with the beginning of

an hour according to the Meter time base.

5.4. Recording of maximum demand time shall be performed at the end of its respective time

interval.

5.5. Maximum demand shall be managed for all tariffs, Monthly maximum demand, cumulative

maximum demand, date and time of maximum demand shall be stored for all tariffs.

5.6. Each record shall contain the date and time of the recorded maximum demand

occurrence, this time being the end of the respective time interval.

5.7. A new maximum demand shall be recorded only if it is bigger than the prevailing one, at

the end of the respective time interval.

5.8. The beginning of a new calculation time interval due to interference, loss of power etc.

shall zero the momentary maximum demand fields.

5.9. Once self reading is performed, the monthly maximum demand value shall be added to

the cumulative maximum demand register; monthly maximum demand value and time

registers shall be cleared.




6. Meter displayed data

6.1. Displayed data their order for each display item shall be programmable.

6.2. Changing between Displayed data shall be by push button and auto scrolling (regular

using).

6.3. Displayed data time duration shall be programmable.

6.4. The Displayed data programmable parameters should be in destined CONFIG file.

7. Displayed formats

7.1. kWh (and kVARh for CT connected meter) shall have a 6 digits display, 000000 to

999999, passing which, the displayed value shall start at zero again.

7.2. Monthly maximum demand shall have a 4 digits display, 000.0 to 999.9

7.3. Cumulative maximum demand shall have a 6 digits display, 00000.0 to 99999.9

7.4. Date & Time DD/MM/YY 24h

8. Status displayed / indicators

8.1. Operative rate /tariff

8.2. Phases existence /non existence

8.3. Phases sequence order

8.3.1. Negative consumption flag (the flag shall be extinguished after reading),

8.3.2. In case the meter detects reverse energy an indication shall be given during the

reading process.

8.3.3. Failure indication and code (if any).

9. Energy data

9.1. Effective tariffs active tariff and time.

9.2. Total kWh to bill (import).

9.3. Only for CT connected meter: Total kVARh.

9.4. Only for CT connected meter: Total kWh and kVARh per each tariff; tariff name or code.

9.5. Monthly value accompanied by its respective date and time

9.6. Maximum demand cumulative value

9.7. If not comprehended from TOU section, separate registers for each tariff.

10. Dial test (High resolution display) mode

10.1. High resolution 10Wh/VARh for dial test /accuracy testing

10.2. Changing to this mode by the meter push buttons and SW




10.3. The dial test mode shall end by SW/ push buttons or timer action

10.4. This display mode is for meter accuracy testing at lab or consumer premises only

10.5. High resolution data should be read by SW.

10.6. Exit from dial test mode shall be: manual by software or buttons. And automatic

after an hour from entry or on power down.




APPENDIX B2-1A: TOU & SPECIAL DATES & DST DATES LIST

Israel TOU table has not changed since 2010.




Table 14 – TOU 2010 map

-




G.1A. TOU special dates & DST dates list

Special dates

TOU Table data for the next four years are specified below

Table 95 – IECo special days of year 2016 Table 106 - IECo special days of year 2017

# Holiday Name

Day Type

Date

1 Pesach

Holiday evening

10/04/2017

2 Holiday 11/04/2017

3 Pesach2

Holiday evening

16/04/2017

4 Holiday 17/04/2017

5 Atzmaout

Holiday evening

01/05/2017

6 Holiday 02/05/2017

7 Shavuot

Holiday evening

30/05/2017

8 Holiday 31/05/2017

9 Rosh-Hashana

Holiday evening

20/09/2017

10 Holiday 21/09/2017

11 Holiday 22/09/2017

12 Yom-Kippur

Holiday evening

29/09/2017

13 Holiday 30/09/2017

14 Sukkoth

Holiday evening

04/10/2017

15 Holiday 05/10/2017

16 Simchat Torah

Holiday evening

11/10/2017

17 Holiday 12/10/2017

# Holiday Name Day Type Date

1.

Pesach

Holiday

Evening 22/04/2016

2. Holiday 23/04/2016

3.

Pesach 2

Holiday

Evening 28/04/2016

4. Holiday 29/04/2016

5.

Atzmaout

Holiday

Evening 11/05/2016

6. Holiday 12/05/2016

7.

Shavuot

Holiday

Evening 11/06/2016

8. Holiday 12/06/2016

9.

Rosh-

Hashana

Holiday

Evening 02/10/2016

10. Holiday 03/10/2016

11. Holiday 04/10/2016

12.

Yom-Kippur

Holiday

Evening 11/10/2016

13. Holiday 12/10/2016

14.

Sukkoth

Holiday

Evening 16/10/2016

15. Holiday 17/10/2016

16. Simchat

Torah

Holiday

Evening 23/10/2016

17. Holiday 24/10/2016




Table 11 – IECo special days of year 2018

# Holiday Name

Day Type

Date

1 Pesach

Holiday evening

30/03/2018

2 Holiday 31/03/2018

3 Pesach2

Holiday evening

05/04/2018

4 Holiday 06/04/2018

5 Atzmaout

Holiday evening

18/04/2018

6 Holiday 19/04/2018

7 Shavuot

Holiday evening

19/05/2018

8 Holiday 20/05/2018

9 Rosh-Hashana

Holiday evening

09/09/2018

10 Holiday 10/09/2018

11 Holiday 11/09/2018

12 Yom-Kippur

Holiday evening

18/09/2018

13 Holiday 19/09/2018

14 Sukkoth

Holiday evening

23/09/2018

15 Holiday 24/09/2018

16 Simchat Torah

Holiday evening

30/09/2018

17 Holiday 01/10/2018




Table 12 – IECo special days of year 2019

# Holiday Name

Day Type

Date

1 Pesach

Holiday evening

19/04/2019

2 Holiday 20/04/2019

3 Pesach2

Holiday evening

25/04/2019

4 Holiday 26/04/2019

5 Atzmaout

Holiday evening

08/05/2019

6 Holiday 09/05/2019

7 Shavuot

Holiday evening

08/06/2019

8 Holiday 09/06/2019

9 Rosh-Hashana

Holiday evening

29/09/2019

10 Holiday 30/09/2019

11 Holiday 01/10/2019

12 Yom-Kippur

Holiday evening

08/10/2019

13 Holiday 09/10/2019

14 Sukkoth

Holiday evening

13/10/2019

15 Holiday 14/10/2019

16 Simchat Torah

Holiday evening

20/10/2019

17 Holiday 21/10/2019




Day light saving time dates

# Start Date Start

Time End Date

End

Time

2015 27/03/2015 02:00 25/10/2015 02:00

2016 25/03/2016 02:00 30/10/2016 02:00

2017 24/03/2017 02:00 29/10/2017 02:00

2018 23/03/2018 02:00 28/10/2018 02:00

2019 29/3/2019 02:00 27/10/2019 02:00

Table 13 – DST Time

CHAPTER G.2: RECORDER / DATA LOGGER / LOAD SURVEY

1. Meter memory capacity –At least 4 channels meter memory capacity covering 1/4 hour

resolution for 45 days real different calendar dates (at least ) or 5 minutes resolution 14 days.

2. Each channel should record one of the parameters below:

2.1. Recording import kWh energy

2.2. Recording export kWh energy

2.3. Only for CT connected meter: Recording import kVARh energy.

2.4. Only for CT connected meter: Recording export kVARh energy

3. The amount of the dates will not change / reduce because of events.

4. Events statuses channel - this channel shall be additional channel to energy channels.

5. Each period as an event status word and doesn’t change or vanish as long as its energy is

recorded.

6. There should be a feasibility to read only segment part of the recording data between given

dates.(1 day resolution)

7. For this tender the requirement is for 2 output data files:

7.1. Current IECo file .txt - ASCII file, the format are detailed in Chapter I clause I.6.

7.2. Implementation of DLMS / COSEM based on obis file.

8. The time stamp shall be presented at winter / standard time.




9. Shifting data to DST in/out time shall be process in IECo computers after reading.

10. There should be a status word (in the IEC billing file) defining the recorder/survey parameters

configured in the meter.

CHAPTER G.3: METER COMMUNICATION LOCAL & REMOTE

1. Local optical communication port

1.1. An optically isolated connector, physically conforming to IEC62056-21(2002) which shall

be installed on the front panel of the Meter and shall be immediately accessible (there

shall be no need to remove a cover for access).

1.2. Port HW – The optical port should work with I.E.C.O REALIN USB optical probe

(IEC 61107) as well as with abacus f6z Probe (IEC 1107).

1.3. Data baud rate: 300---9600 bits/sec

For optical probe view, kindly please observe figure 17 p. 125.

2. Serial Communication port (local & remote)

2.1. If the Meter has a serial communication port supporting all portable PC activities and

remote communication applications then it has to be RS-485.

2.2. Data baud rate: constant baud rate at least 9600 bits/sec.

2.3. This connection shall utilize at least two wires as follows: transmit; receive.

2.4. The Bidder shall provide adequate quantity of cables wired with matching connectors to

RS-485 connector port (9 pin).

2.5. The serial port should connect to server with this communications technology

3. Communicating two or more meters (in case the meters equipped with Serial

Communication port) at the same site with one communication line

3.1. Background: IECo connects at end points of burden > 100 Amperes, a "metering system" consisting of a primary (CT) meter and a secondary (CT) backup meter. For that system a single twisted pair configuration is required. The implied connection is then for these two meters to connect through the twisted pair connection, through a single gateway.

3.2. These meters must be enabled for communication by twisted pair as cascaded in series to each other.

Communication protocol and output files standards – General Requirements

1. Sources /manuals

The Bidder shall supply the communication protocol Reference data and manual

Also the SW source for the pc is subjugated to confidential (Non-Disclosure) agreements.




2. Data readings time limitation

Current

Current + 4

Billing Log File Load Survey

Local PC .5min 2min 1min 8 min

Remote PC (TEL

line)

1min 3min 1.5 min 8 min

Remote PC(GSM

data)

1.5min 4min 2min 12min

Remote packets 2min 5min 2.5min 10min

Table 20 – Communication time limitations

Notes:

Time is in minutes

Data reading - 4 quadrants + TOU + max demand (all 4 quadrants)

Load survey - 5 channels 15min 42 days' data

Local Dce2meter or pc 2 meter baud rate 9600

The Time is without connection time.

Latency times are expected order of magnitude times, and a different time figure shall be

accepted as long as it is not too far from above figures. Example for too far: 30 min.

CHAPTER G-4: DIRECT/CT CONNECTED METER HW / R.T.C BATTERY / OUTPUTS AND

GATEWAY/DATA CONCENTRATOR THE SAME, AND REMOTE/DIRECT

FIRMWARE/(TOU/DST) CONFIGURATION UPDATE

1. Meter electronic H.W / Firmware




1.1. The operational meter service life length will be at least 15 Years with no Preventive

Maintenance (R.T.C battery excluded).No Preventive Maintenance = such as L.C.D. or

electrolyte capacitors replacement or calibrations.

1.2. TOU table, consumption data, self-reading data load survey and similarly significant

data and parameters shall be stored in a non-volatile memory.(data retention- meter

lifetime- no battery backup )

1.3. The Meter shall store technical and self-test results data and make them available for

reading, by means of a portable PC or remotely by communication means.

1.4. The meter should have built in test (BIT) function that shall check the meter working

properly

1.5. The B.I.T function shall work periodic and while power up.

1.6. The B.I.T should check meter elements like : the micro-p/ memories / clocks RTC/

P.S /operations SW/data integrity .the manufacture should describe/ explain how

the tests are created

1.7. The output of the tests should be a status flag that can be display/ read from the

meter.

1.8. The meter power supply should work even if only a single phase is operating (as

required by standard IEC 62053-21).

1.9. A super capacitor is optional to R.T.C. battery, but it shouldn't be electrolyte.

1.10. The gateway/Data Concentrator shall be with R.T.C. backup battery.

1.11. The Bidder will list the all electrolyte capacitors /tantalums capacitors their

positions and functionality and their main parameters – at meters direct/CT connected

and at gateway/Data Concentrator.

1.12. The Bidder will explain the measuring elements technology and meter

calibrations procedures

1.13. Updating meter CONFIG / TOU / DST parameters files should become valid &

functioning only after examination the integrity of the file, in case the file was

failed to receive in the meter the old file should stay valid & functioning.

1.14. Direct/CT connected Meter + gateway/Data Concentrator firmware update –(

if needed ) the manufacture should describe/ explain the procedure to do the

direct (as opposed to remote firmware) update (like optical port / RS485 port at

consumer premises or at lab/ open the meter cover / does it damage the meter

data). A remote firmware update is a mandatory requirement and remote TOU/DST

configuration through gateways/DC for all meters. It is expected that entire meters array

shall be firmware updated within a month from dispatch of new firmware and as defined




at IECo output files chapter, firmware version and configuration file names are registered

inside meter, and output to the IECO consumption/billing file. MMS system and

gateways/DC-s are responsible to distinguish between a new gateway firmware version

and a new meter. If it's a meter firmware version then it should be propagated further

through gateways/DC-s to entire meters array. In addition distinguishability between

direct and CT connected firmware versions is required.

1.15. The firmware updated process Should be protected and inspected The

process Should be protected and not damage the meter data . All firmware update

by IECo are enabled. For example: remote and direct. Through an optical probe, or

requirement to open terminal block and connect a downloader card. The options of not

updating firmware at IECo, but only through uninstall meter and dispatch to

manufacturer, or of not updating at all, are not permitted by IECo. If manufacturer

accepts to add a firmware update function, he is entitled to replace meter samples at

IECo.

1.16. IECo meter code (4 digits stored in the meter memory) should be part of the meter

readings data.

1.17. As a part of the documentations that shall be supplied A.R.O The Bidder

will supply An updated electronic scheme + components list

1.18. Manufacturer shall provide a list of changes performed over firmware from

version approved by type test lab.

2. R.T.C. battery:

2.1. The Meter shall operate for at least 15 years without preventive maintenance,

maintaining its conformance to the specification

2.2. Internal Real Time Clock (RTC) quartz crystal base shall generate the Meter time base

2.3. R.T.C accuracy: quartz crystal <± 2min/year at 25°C, including power failure and

other interruptions)

2.4. The battery is for operating the RTC while power failure. Data shall be stored with

nonvolatile memory without battery

2.5. Time update – immediately after the communication end( no -spread the time Over

time intervals )

2.6. Mains synchronization is unacceptable.

2.7. The Meter RTC shall be capable of operating continuously at least for 15 years including

2 years of storage prior to installation, by means of a (Lithium) battery.(shall be

connected to meter before installation)




2.8. Super cap as a main backup is not acceptable as alternative solution to R.T.C. backup

battery – only additional to the battery.

3. Battery life monitoring & warning

If a battery is the solution for R.T.C. backup then:

3.1. The meter should have register that shall accumulate the time (hours) From the

moment the battery is installed and the time the battery is working during power fail

/storage.

3.2. Battery life monitoring with measuring the battery voltage and compare it to reference

voltage with comparator method.

3.3. There should be a flag in the meter status bit that shall warn that the battery

need to be replaced.

3.4. The register value should be reset after replacing new battery (SW application).

3.5. The register value should be readable and are part of the IECo reading file.

4. Battery technical data

The Bidder should provide this data:

4.1. The current that is being consumed from battery while power failure / storage.

4.2. The battery capacity (mAh)

4.3. The battery and connector data-sheets

4.4. Change of parameters with time during meter life cycle.




CHAPTER H: DIRECT/CT CONNECTED METER AND GATEWAY/DATA

CONCENTRATOR SECURITY AND MMS SECURITY

The following abides to all components of this tender spec: direct/CT connected meter and

gateway/Data Concentrator. in short it shall be abbreviated as "meter".

1. Protection against fraud and meter tampering

1.1. The meter shell protected against attempts to tamper the measuring results and

unauthorized access to the registers containing parameters that influence results of

measurements.

1.2. There should be hardware protection and the software protection.

2. Hardware protection includes

2.1. Sealing of a terminal cover and a meter cover as required in Chapter B1-2.

2.2. Access to the main and auxiliary terminals is not possible without breaking the seals on

the terminal block.

2.3. Access to the main meter board cannot be without breaking the seals on the meter cover

and removing it.

3. Software protection includes

3.1. Information security in accordance with dlms/cosem as specified by standard IEC 62056

or dlms/cosem blue book. Meaning: privileged access levels for read only, write,

configure.

3.2. Software locks of registers, passwords and a password with an encryption algorithm

3.3. Logbook where changes of parameters which influence results of measurement are

recorded together with a time stamp that cannot be deleted.

3.4. Reversed phase sequence – in event /log book.

3.5. Counters of power shortages

3.6. Detection of different incorrect operations of a meter-registration of uncommon meter

operation conditions, which might be caused by non-authorized intervention into the

meter connection:

3.7. Reversed phase sequence.

3.8. Presence of phase voltages.

3.9. Counter of voltage failures.

3.10. Logbook records – All significant events that give information on failures,

interventions into the meter, settings, etc. are recorded into the logbook. The logbook

cannot be deleted except if the meter is re-configured.




3.11. Software locks of registers – All registers that contains parameters which influence

or contains results of measurement, meter statuses or different counters of events are

protected with software locks. These locks should be unlocked first if content of the

register is to be changed.

4. Keyes & Passwords

4.1. There should be passwords & keys with an encryption algorithm. The passwords are

protected against changing and reading. In case there is need for a password changing

or reading, then one should have a key for encoding/decoding the password, otherwise

access is disabled.

4.2. Levels of authorization – Right to access to different registers is organized in levels of

authorization, Every wrong password is counted by the wrong passwords counter and

registered in the logbook together with date and time of the attempt.




CHAPTER I: SOFTWARE AND ROUTINES / DATA FLOW AND PROCESS

System computing hardware and OS

The Bidder shall provide the software and all other means required for data exchange between

the Meter and the portable PC/lab pc/servers via the different communication media

System hardware and (Operating System) OS:

Note:

1. Portable PC: Control station for the test equipment run meter software's (should be

supplied by Bidder see deliveries)

1.1. Portable PC An advanced core (CPU chip) as compared to current market. Current

advanced core is core i5.

1.2. Screen size 15"

1.3. 4GB RAM or more.

1.4. 350GB HD or more.

1.5. Operating System: Windows 7 or Windows 8 and one generation ahead: windows 9 or

10.

1.6. COM PORT: USB2

2. Servers:

2.1. Operating system: Windows Server 2003, 2008 and above

2.2. COM PORT: 4 or more USB and virtual ports

3. In case of third party SW, the Bidder shall provide the Software license needed to from SW

developer.

4. SW license – all software licenses (Bidder and Third Party Company) should be for unlimited

time duration.




Figure 17 – Reallin IECo probe for PC use Figure 17-b – Abacus probe with USB plug for lab PC use




Data files and auxiliary management / control files requirements:

1. Meter data output files

1.1. There are 3 out data files reads from the meter:

1.2. Billing data, limited Technical, events &log.

1.3. Survey data

1.4. Full technical & events & log data.

1.5. The the PC data output meter files shall have the same data files structure

2. Communication / Data Conversion SW report results err file

2.1. The SW will create an error file while / after running

2.2. The report results are for IECo managing SW usage.

2.3. The Error File, output of the Software, will be 3 bytes long (leading zero format is

preferable and shall be scored with 1 out of 100 additional point) containing results

codes of operation.

2.4. If the communication /data conversion is ended with no error the ERR.dat will contain the

value 000, else the error code Meter files shall be provided in ASCII format.

2.5. While setting the time there will be only error file as output.

3. SW log file – Each SW shall be accompanied by log file describing activities status and

errors.


Israel Electric Corp Central Metering unit of

197


I.1. : /PORTABLE PC / LAB PC / SERVER FUNCTIONS / APPLICATIONS

1. The different application shall run by different parameters (routine / function running

with different parameters excluding the lab PC SW). The manufacturer is expected to

submit specific communication software tools for laptops.

2. The manufacturer may budget the developed software at a separate serial number,

and submit the tool pricing within the tender proposition.

3. N/A

4. portable pc shall be the same SW (exe & dll .ect)

5. The software baud rate fixed /variable baud-rate is according application and meter

port usages and Connections.

Table 141 – SW level operations

Level Performed by Activities

0

Operator (meter

reader) with

portable PC

a. Meter reading, automatic meter time

updating. Automatic downloading and

uploading of data. (For example: day

light saving time, new TOU etc).

1

Technician (meter

installer/maintainer

With portable PC

a. All the activities of level 0

b. Diagnostics (Local & Remote), self-

reads (billing), etc. Determination if

Meter is operational or defective

2

Technician/Engineer

Laboratory PC

b. All the activities of level 1

c. Generate meter CONFIG files,

Perform maintenance, and test

TOU/DST validity. Downloading of

software, initialization of counters,

update data, parameters and

passwords etc.

3 Technician/Engineer

Servers

a. Remote metering and maintenance

(day light saving time, new TOU etc)




Table 15 - Software to be supplied by Bidder

Manufacturer is kindly requested to carefully pay attention to all items required, especially to 4), 5).

Experience based, these two items are un-noticed with sufficient care, while responding to this table.

No. SW Name &

Description

Applications Operation

Mode OS

Integrated

With IECo

SW

Com

port

Computing

platform

Optical

port

Spec details

Description

No of

Copies

License

1 MMS10 -

Meters

configuration

&management

installed at IECo

servers

Create files

Needed to

CONFIG&

OPERATE

the meter

Bidder

H.M.I & menu Win7

Stand alone

Com 1-4

USB

USB to

com

Desk top PC

Portable PC

IECo

1107&po

rt

Abacus

1107

Table

21&23

10

2

portable PC Meter reading

& maintenance

Function

With

Parameters

((embedded at

IECo

applications)

Win7 Com

USB Portable pc

IECo

1107&po

rt

Abacus

1107

Table

21&23

100 PC

4

Remote metering

Communication

Meter reading

&maintenance

c2s .s2c

Batch Function

With

Parameters

(embedded at

IECo

applications

"Magic", "SAP")

Windo

ws 7

server

IECo

A.M.R

Com232

USB &

virtual

Com

PC

Server

-

Table

21&23

10

5 All required

technical data +

low level routines

to IECo to

construct a driver

for access MMS

by "Shoval"

application

Meter reading

&maintenance -

Windo

ws 7

server

- -

PC Server

-

- Table

21&23

-

6 portable Pc for

next future new

windows

Version s (1 ver)

Meter reading

&maintenance

-

Win

Mobil

e

SW RS485 or

USB

Portable PC New

optical

1107 232

or USB

Table

19&21

100 PC

10

MMS = Meter Management system




*working with cloud

computing platforms -

T.B.D

Table 163 – PC / Lab PC / Server applications

portable PC Meter updating

CONFIG/ TOU / DST /

Display

Operation Portable PC LAB PC Server

1

Read meter billing data(current + billing / parametric

choice)

√ √ √

2 Set time & date adjust unconditionally √ √

3 Set time adjust +_10 min / broadcast √ √ √

4 Configure meter general definitions √ √ √

5 Configure meter tariff (rate information & special days) √ √ √

6 Configure meter DST dates √ √ √

7 Configure meter displays √ √ √

8 Change meter passwords √ √ √

9 Configure meter interval recording

(characteristics/open/close)

√ √ √

10 Read profiles (interval recording) √ √ √

11 Read log book & technical data & mains power diagnostics √ √ √

12 Read meter CONFIG. Files (gen/TOU/DST /display…) √ √ √

13 Read reverse energy flag status √ √ √

14 Clear reverse flag √ √ √

15 Perform billing reset √ √

16 Read instantaneous (volts, currents etc.) √ √ √

17 Configure energy led to kWh or kVARh √ √

18 Reset battery registers √ √

19 Adjust meter to hi res /dial test mode √ √

20 Read High resolution registers √ √

21 Read the active TOU status (1 or 2 or 3 etc.) √ √

22 Generate configure / TOU / DST / Displays files √




Start

Read

meter

Get config

File name

Is

there

matching?

Cross

Reference

table

Compare

Files

Names

Update meter

With new file

End

yes endNo

Is the file

Transferred

/accepted?

Work with

Previous file

Report okyes

Report errno end

Work with

updated file

Report no

matching

Tou /dst / realys /displays /config/ files meter update

Figure 18 – TOU / DST/ Displays / CONFIG / Files meter update

Note:

The files should have ID names that can be read from the meter (like in IECo file ) the ID

is part of the CONFIG file and is given while the file was created.

Updating DST dates file and time while standard time or DST is operative, shall not affect meter

time.

Meter displaying time is the operative time (standard or DST).




Start

Read

meter

Get config

File name

Is

there

matching?

Cross

Reference

table

Compare

Files

Names

Update meter

With new file

End

yes endNo

Is the file

Transferred

/accepted?

Work with

Previous file

Report okyes

Report errno end

Work with

updated file

Report no

matching

Tou /dst / realys /displays /config/ files meter update

Figure 19 – TOU / DST/ Relays / Displays / CONFIG / Files meter update

Note:

The files should have ID names that can be read from the meter (like in IECo file ) the ID

is part of the CONFIG file and is given while the file was created.

Updating DST dates file and time while standard time or DST is operative, shall not affect meter

time.

Meter displaying time is the operative time (standard or DST).




I.2.: REQUIREMENTS FOR INTEGRATION OF NEW DEVICE DRIVERS INTO DLMS / COSEM

"SHOVAL" SAP/ERP SYSTEM

IECo SW for remote metering and data processing are "Metzah"- present day software and "Shoval"

SAP/ERP – the future plans, to which all IECo is migrating - its management, and billing systems.

As a part of this Spec. the meter Bidder shall provide all the technical required data (as described herein) to

IECo computerization department (AMAT), the department in charge of developing the drivers. Objective is

to facilitate integration to IECo system, and to enable the drivers development, within 3 months each. The

meter manufacturer shall provide the dlms/cosem implemented list of data objects including their OBIS

code, and their basic structure.

Requirements for Device Driver Integration:

1. Rules to ensure quick integration of a new DLMS / COSEM Device Driver

The following books are to be used as references:

1.1. DLMS / COSEM Green Book 7th edition

1.2. DLMS / COSEM Blue Book 9th edition"

Any anomaly from these books will cause delays. So anything which is Bidder specific and does not

follow the defaults should be avoided.

2. DLMS / COSEM Green Book

Communication Profiles

The two following communication profiles are supported (see figure 3 Green Book):

2.1. 3-layer, connection-oriented (CO), HDLC-based profile. This comprises the COSEM AL, the HDLC-based data link layer and the PhL, for connection-oriented asynchronous data exchange. It supports DLMS User Association, COSEM Architecture and Protocols, Seventh Edition DLMS User Association 2009-12-22 DLMS UA 1000-2 Ed. 7.0 20/310 data exchange via a local – optical or electrical –port according to IEC 62056-21, leased lines and the PSTN or the GSM telephone network.

2.2. TCP-UDP/IP based communication profiles. These profiles support data exchange via the Internet over various physical media, like Ethernet, ISDN, GPRS, PSTN or GSM using PPP etc. In these profiles, the COSEM AL is supported by the COSEM transport layer(s), comprising a wrapper and the Internet TCP or UDP protocol. Lower layers can be selected according to the media to be used, as the TCP-UDP layers hide their particularities.

3. Recommended referencing method

Use of Logical names (LN referencing) recommended. In this context the following services are

supported:

3.1.




3.2.

4. NOT supported

4.1.

4.2.

4.3. ss security: High Level Security (HLS)

4.4. -Release service (association release is done by disconnecting the supporting layer of the

AL).

5. DLMS / COSEM Blue Book

5.1. Supported interface classes are: Class id 1, 3, 4, 5, 7, 8, 10, 11, 15, 20, 21

Strictly use of the Object Identification System (OBIS)




I.3.: TOU & DST DIAGNOSTIC TEST TOOL & METERS CONFIGURATION VERIFY TEST

TOOL

Two additional (to "Shoval" SAP) applications / test programs are developed by IECo resources

based on the Bidder pc program. These require batch functions with parameters.

Application: 1 TOU & DST Diagnostic Test Tool

Diagnostic test tool uses test scripts to verify that an installed TOU & DST table is operating

correctly by using IECo developed software program running the meter manufacture pc

program that Enable to change the meter time and date to calculated pre-selected test

points and read the meter.

The tested points are generated by IECO SW.

The program compare the meter tariff variability to expected tariff at the selected test

points

At the end a report is produced (see example next page) and analyzed for differences

if any.

This program is running each time there is a change in the TOU or DST data to check the

new CONFIG before distribute to all meters .

The test process:

Setting the date and time to a known value.

Running the meter “on load” for a fixed length of time.

Reading the meter to see which rate register has advanced.

Comparing the rate register advance to the expected rate register.

The tool will only complete a test properly if the meter is on load and registering energy

consumption.

The test point number is automatically generated.

Each Test Point sets the meter date and time to a known value and checks that the correct rate

register has been incremented. The script then moves to the next test point, sets a new date

and time and checks that the correct rate register has been incremented.

Test Start Date = the date the meter should be set to for the test.

Test Start Time = the time the meter should be set to for the test.

Test Duration = length of time meter should be on load in order to verify that the test is

successful (This will depend on the kW load, a high kW load requires a shorter time

than a low kW load).

Expected Rate Register = the rate resister that should be incremented by this test.

Generates a report

Notes:

The meter shall be loaded with IECo load equipment.

The Bidder can propose similar program that tests the TOU & DST functionality.




Application 2 Meters Configuration Verify Test Tool

IECo developed software program running the meter Bidder pc program that Enable

to read /write the configurations data from the meter and compare it to reference

confirmed configuration file.

This test is performed on each meter before installation (as part of acceptance test




Table 174 – TOU & DST verification test example

Test

Script No

PC test Time &

date

Test Start

Date Time

Test

Duration

Expected

Rate

Register

Actual Rate

Register

Test

Result

1 31/12/2005 23:55:00 00:06 3 4 Fail

3 31/03/2006 01:55:00 00:10 3 4 Fail

2 30/03/2006 23:55:00 00:06 3 4 Fail

4 31/03/2006 07:55:00 00:05 3 3 Pass

5 31/03/2006 08:00:00 00:05 2 3 Fail

6 31/03/2006 11:55:00 00:05 2 4 Fail

7 31/03/2006 12:00:00 00:05 3 4 Fail

8 31/03/2006 14:55:00 00:05 3 3 Pass

9 31/03/2006 15:00:00 00:05 2 3 Fail

10 31/03/2006 21:55:00 00:05 2 4 Fail

11 31/03/2006 22:00:00 00:05 3 4 Fail

12 12/04/2006 06:55:00 00:05 3 3 Pass

13 12/04/2006 07:00:00 00:05 2 3 Fail

14 12/04/2006 22:55:00 00:05 2 4 Fail

15 12/04/2006 23:00:00 00:05 3 4 Fail

16 13/04/2006 16:55:00 00:05 3 3 Pass

17 13/04/2006 17:00:00 00:05 2 3 Fail

18 13/04/2006 22:55:00 00:05 2 4 Fail

19 13/04/2006 23:00:00 00:05 3 4 Fail

20 17/05/2006 05:55:00 00:05 3 3 Pass

21 17/05/2006 06:00:00 00:05 2 3 Fail

22 17/05/2006 07:55:00 00:05 2 2 Pass

23 17/05/2006 08:00:00 00:05 1 2 Fail




I.4. IECO OUTPUT FILES STRUCTURE/FORMAT & INTERRUPTIONS

I.5.: BILLING FILE & TECHNICAL DATA

Output files

The Bidder shall produce 2 types of out puts formats:

IECo current format

OBIS code files

Table 18 – DLMS / COSEM

Billing output files Load survey File & events Event log File Remarks

DLMS/COSEM

IECo structure

Appendix B2-7A

IECo structure

Appendix B2-7B ASCII

OBIS Code OBIS Code OBIS Code

Table 196 - IECo output 2 OBIS code convert (part of the file)




Table 27 – Standard IEC File Structure

5 Current reading date 3 0.9.1, 0.9.2

6 Import total kWh 3 1.8.0

7 Export total kWh 3 2.8.0

8 Import total kVARh 3 3.8.0

9 Export total kVARh 3 4.8.0

10 Import total kWh in Rate 1 4 1.8.1

11 Max demand in kWh within a given period in time of Rate 1

4 1.6.1

12 Cumulative max demand in kWh in time of Rate 1

4 1.2.1

13 Date and time of Max demand in KWh in time of Rate 1

4 1.6.1

14 Import total kVARh in Rate 1 4 3.8.1

15 Max demand in kVARh in a given period in time of Rate 1

4 3.6.1

For list of all OBIS codes and their structure the manufacturers are referred to ANNEXURE C, p. 193.




I.6.: LOAD SURVEY/PROFILE

Interpreting load survey

Header Line

The first line of the Load Survey is the header. This contains the following information:

0415000508530001S0607041133000000010000016001070400000607042345044

For list of all OBIS codes and their structure the manufacturers are referred to ANNEXURE C, p. 193.

Table 208 – Header Line Data Characteristics

Data Type Size Line

Meter Number D 8 1

Meter Code D 4

Line Number D 4

ID X 1 (s)

Reading Data & Time DDMMYYhhmm D 10

Pulse Multiplier (converts pulses to kW)

D 8

Pulse Divider D 8

Recording Start Date & Time DDMMYYhhmm D 10

Recording end Date & Time D 10




Number of Periods Per Hour D 2

Number of Channels D 1

Spare Blank 734




Taking the data from the line above, we get the following information:

Table 21 – Header Line Data Example

04150005 Meter Number

0853 Meter Code

0001 Line Number

S ID

0607041133 Reading Data & Time DDMMYYhhmm

00000001 Pulse Multiplier

00000160 Pulse Divider

0107040000 Recording Start Date & Time DDMMYYhhmm

0607042345 Recording end Date & Time

04 Number of Periods Per Hour

2 Number of Channels




Data Lines

One line from the load survey output file looks like this:

0415000508530002S06070400000313023340000233200002332000023440000233000002315000023240000232

5000023160000232100002329000023300000233300002347000023350000232900002320000023200000233000

0023440000234100002371000023250000228300002286000022980000223100002192000021550000215700002

2050000218600002128000021280000214400002144000021650000214500002162000020940000210400002115

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000

This can be broken down and interpreted as follows:

Table 30 – Data Line Characteristics

Data Type Size Line

Meter number D 8 2**

Meter Code D 4

Line number D 4

ID X 1 (s)

Data date & time DDMMYYhhmm 10

Channel number D 2

Energy type D 3

Pulse count* D 4

Status Bytes (hex) 4

For 5 minute SIPs (survey interval period), there would be 3 lines for each day (in the above format). These

would cover the time ranges 00:00 – 08:00, 08:00 – 16:00, 16:00 – 24:00

There would be in each line:

1 instance of Meter No, Line No, Bidder Code, Date & Time, Channel No, Energy Type

96 instances of Pulse Count + Status Byte

The first characters contain header information. This can be seen more easily if we separate it out ...

0415000508530002S060704000001130

Table 221 - Data Line Example

04150005 Meter Serial Number = 04150005

0853 Meter Code = 0853

0002 Line Number 0002

S ID

0607040000 Data Date & Time = 06/07/2004 00:00




01 Channel 01

130 Energy Type = 13010 (8216 = export)

** All subsequent data refers to the Load Survey values and status codes **

2334 Pulse Count = 2334

0000 Status Code = 000016




Status Code

The Status Code is a binary bit mask. The following table gives the meaning for each bit set.

Table 23 – Status Code bit set

Name Bit No Binary Hex

Supply failure – in the same period 0 00000000 00000001 00 01

Long supply failure 1 00000000 00000010 00 02

Filler (invalid data), for missing periods within a recorded

day, not for whole missing days

2 00000000 00000100 00 04

Time change – forward on the same date 3 00000000 00001000 00 08

Time change – backward on the same date 4 00000000 00010000 00 10

Date change forward 5 00000000 00100000 00 20

Date change backward 6 00000000 01000000 00 40

unused 7 00000000 10000000 00 80

unused 8 00000001 00000000 01 00

unused 9 00000010 00000000 02 00

Phase failure (any length) –phase 1 (the only phase there

is)

A 00000100 00000000 04 00

unused B 00001000 00000000 08 00

Phase failure (any length) –phase 2 unused C 00010000 00000000 10 00

unused D 00100000 00000000 20 00

Phase failure (any length) –phase 3 unused E 01000000 00000000 40 00

unused F 10000000 00000000 80 00

Note:

If more than one bit is set, the corresponding Hexadecimal value will reflect this. For example, if there is

a time change forward (due to DST changeover) at the same time as a power failure then bits 0 and 3

would be set.

This gives a binary value of 00000000 000010012 = 00 0916.

For long supply failure the status bit will be set throughout the duration of the power outage.

For time and/or date changes forwards the status bit will be set in the SIP which was current when the

change was executed and in the SIP containing the time to which the clock was set. (All SIPs in between

will contain filler data and will have only the appropriate bit set.)

For time and/or date changes backwards the status bit will be set in the SIP which was current when

the change was executed, the SIP containing the time to which the clock was set and all SIPs in

between. (Since the data will be summed and may therefore appear to be irregular.)

Each pulse count (and associated status code) for each integration period is shown in the 4 columns

above. In order to get the demand value in kWh, use the pulse multiplier and pulse divider fields.

Demand in kWh = (Count) x Divider

Multiplier x (number of periods per hour)




For the first value (0000:0000 – 0000:15), this works out at ...

35.58458.14160

12334 KWh

Filler data will appear as zeros with a status code of 000416.




I.7. SPECIFICATION FOR BE HAVIOUR OF LOAD PROFILE STATUS WORD STATE MACHINE

Table 32A – Additional LOAD SURVEY - STATUS CODE BIT SET

No. SPECIFICATION FOR BEHAVIOUR OF LOAD PROFILE STATUS WORD STATE MACHINE

1

1. Blank days inserted as a result of forward date change show status flag 0004 signifying Invalid period. A

period not stepped is invalid.

2. At the end point of a forward date change crossing day midnight boundary, status should be 0020, not

0000.

0020 = forward date change.

Example #1: date changed forward from 1/1/14 02:00 to 10/1/14 04:00 due to application command.

Period of 10/1/14 04:00, is marked 0020, and periods starting 1/1/14 02:00 and terminating 10/1/14

03:45 including are marked 0004.

1/1/14 02:00 10/1/14 04:00

3. Time change forward at same day:

Example #2: In summer time DST entry, a time change from 02:00 to 03:00 should show code 0008 (time

change forward at same date) and not code 0020 (date change forward crossing day boundary). This is

because in time change does not cross midnight date boundary. In reality it will never occur. In addition

this is still a valid status flag.

1/3/14 02:00 1/3/14 03:00

4. Time change backwards at same date: should code 0010.

Example #3: Exit from DST should occur at 02:00 and time should change to 01:00.

Left boundary, which is destination time is marked 0010, and all periods that were valid turn into invalid

but the data (pulse count) is aggregated. As they are repeatedly stepped they become valid 0000 and

more according to events.

1/3/14 01:00 1/3/14 02:00

0020 0004 0004 0004 0004 0004 0004 0004

0008 0004 0004 0004 0004 0004 0004 0004

Time direction

Time direction

Time direction

0004 0004 0004 0004 0004 0004 0004 0010





2

5. Date change backward crossing midnight boundary (00:00) should code 0040.

Example #4: date change command to meter to change from 10/3/14 02:00 to 1/3/14 01:00.

1/3/14 01:00 10/3/14 02:00

Phase voltage failures, and all phases power downs

3

1. Long power supply failure: Status Code 0002 for periods in which a long supply failure (=across at least

one period boundary) starts, continues or ends – regardless of these periods having valid data or not. This

includes inserted blank days.

Example #5: meter is at storage disconnected from grid from 1/3/14 02:00 till 10/3/14 03:00

1/3/14 02:00 10/3/14 03:00

2. Status Code 0001 for periods with meter supply off for part of one period only.

Example #6: meter is with long power supply from 02:07 till 02:14.

1/3/14 02:07 1/3/14 02:14

0004 0004 0004 0004 0004 0004 0004 0040

Time direction

0002 0002 0002

3

0002 0002 0002 0002 0002

Time direction

0001

Time direction





3. Invalid period: Status Code 0004 for periods in which there is no valid data and no other flag.

Example #7: meter time is 1/3/14 02:00:00. Meter has not passed yet periods forward. All periods

forward are with status 0004.

1/3/14 02:00 10/3/14 03:00

Example #8: meter has gone backwards at DST exit from 26/10/14 03:00 to 26/10/14 02:00.

Then periods in between except period 02:00 are with invalid 0004 code. That's although meter has been

at these periods previously. Data of these periods is aggregated. Previous value and future value should

be summed.

Example #9: meter has gone back due to time change backward. The same: from source time to

destination period it is 0004 except destination period. That's although meter has been at these periods

previously. Data of these periods is aggregated. Previous value and future value should be summed.

1/3/14 01:00 10/3/14 02:00

Single phase failures:

Phase R is 0400, phase S is 1000, phase T is 4000.

Examples:

R+ S: 1400=400+ 1000,

R+ S+ T: 5402= 4000+1000+0400+0002 phase failures during different times up to complete power down_

Since only a single phase exists, there can be no valid 5402 status code. Only 0002.

For true long supply failure 002 is a valid status code – power down failure.

4 Status Code=0001 for periods where power down is off at various times during a single period + full short

supply failure during part of the same period.

5

If R, S, T fail separately and this results in a total supply failure, status is 5402 or 5401.

Status code will be 0001 (for short supply failure – ER-3 point 1 in the same period) or 0002 (long supply

failure, during several periods) if failure is simultaneous.

Any long supply failure will only show 0002 (in the event of at least one individual phase failure) at the start

and end periods– all intermediate periods will only contain 0002.

8

Suspected error: Incorrect time change backwards status flag – includes (suspected) non-existent short

supply fail -ER-8 not reproducible but partially supported in the same manner as ER-7.

0011 (and 0012) is a possible status code: (time update backwards into a period which is already marked with

a supply failure). Time update backwards without any supply failure should be marked as 0010 only.

9 Energy of repeated periods is accumulated and not overridden.

0004 0004 0004

3

0004 0004 0004 0004 0004

Time direction

0004 0004 0004 0004 0004 0004 0004 0040

Time direction





10

General principle 1: if there is interference between flagging of supply-related conditions and flagging of

date/time-related conditions. It is stressed by IEC that these sets of conditions must be handled

independently of each other.

11

General principle 2: Because of complex time changes during laboratory tests, or occasionally because of

errors in the field, it can happen that the meter(s) traverse certain time periods more than once.

If there are multiple events in the log covering any such periods, the survey periods will be marked with flags

relating to all of the traverses. For instance, such a period might show both a time set (forward or backward)

and a power failure even though they actually happened on separate occasions.

In the field, this will also be the case. However, smaller time sets (1 or 2 hours forward/back) are much less

likely to create complex data.

Duplicate Data Fields

The output file shall normally contain no more than one record for each date. Input data from

the meter will however contain two or more parameter-days with the same date as a result of

any time change which is not small, or of change of survey definition (energy types, scaling, or

SIP length).

Reason for duplication Action to be taken

Data collection resumed after

an interruption, data sets

overlapping

Eliminate duplicate days

Time change (other than a

small adjustment)

For each channel, combine

days having the same date

Table 243 – Duplicate Data Fields

Input records with the same date are handled as follows, where the “first” record means the

one that is encountered first in reading sequentially from the beginning of the input file (RES or

ALL), and an “extra” record is any record after the “first”.

Any extra record which results from a change in time is combined with the preceding record

with the same date to give a single output record. If there are more than two records with the

same date then the output should be as if the first two records were combined and the result

then treated as a new first record to be combined with the third record, and so on.

To combine records, first pulse counts and status values are calculated for each record , then

SIPs notionally having the same timestamp are combined with each other. Combine SIPs

according to this table:

SIP in first record SIP in extra record SIP in output record

Valid Invalid Copy count and status from SIP




in first record

Invalid Valid Copy count and status from SIP

in second record

Invalid Invalid Invalid (zero count, filler status)

Valid Valid Sum of counts, and inclusive-

OR of statuses, in first record

and extra record

Table 25 – SIP Data

In the event of a change in scaling, a new set of data is started (including header info).

DST Offset

In the meter, Load Survey is always maintained using base time.




Load profile example

0415049408530001S0609061430000000010000016020080600000609062345042

0415049408530002S060906000001150007000000071000000720000007300000070000000700000006900000071000000750

00000760000007700000076000000780000008000000075000000740000007500000074000000740000007000000075000000

65000000530000007900000088000002130000038500000272000003310000036900000378000003890000041900000424000

00389000003850000038600000400000003450000041300000456000003990000032100000429000004050000032200000444

00000479000004730000045800000452000004370000040500000404000004200000042800000462000004620000000000040

00000040000000400000004000000040000000400000004000000040000000400000004000000040000000400000004000000

04000000040000000400000004000000040000000400000004000000040000000400000004000000040000000400000004000

000040000000400000004000000040000000400000004000000040000000400000004000000040000000400000004

0415049408530003S060906000002130007900000079000000800000008400000089000000890000008800000084000000810

00000820000008100000083000000820000008600000081000000820000008400000083000001020000013100000151000001

38000001640000022600000265000005930000098300000758000009120000098400000968000010080000107600001075000

01037000010240000104800001071000009710000107000001128000010440000091800001112000010980000096100001178

00001183000011590000114100001139000011180000106200001027000010430000106800001172000012010000000000040

00000040000000400000004000000040000000400000004000000040000000400000004000000040000000400000004000000

04000000040000000400000004000000040000000400000004000000040000000400000004000000040000000400000004000

000040000000400000004000000040000000400000004000000040000000400000004000000040000000400000004

0415049408530004S050906000001150002800000027000000270000002700000026000000270000002800000027000000320

00000330000003200000031000000320000003300000034000000320000003100000032000000300000003000000039000000

39000000490000008000000091000002120000039500000302000003260000033000000348000004040000032000000402000

00372000003330000032700000436000003260000038300000389000003740000041800000328000004250000031700000418

00000457000003450000042800000442000003110000042900000343000003800000043500000426000004310000042700000

33400000434000003860000029400000278000002780000024400000255000002090000022000000183000001930000024500

00017000000169000001600000015600000106000000670000006200000061000000440000004000000034000000300000003

600000080000000750000007400000074000000750000007500000074000000750000007200000073000000730000

0415049408530005S050906000002130007400000081000000800000007900000080000000780000007400000070000000730

00000730000007200000073000000730000007400000075000000760000007500000076000000930000013100000153000001

37000001710000023100000289000005990000099600000825000009180000092200000946000010440000089100001028000

01006000009180000086900001083000009020000102200001006000009970000110700000936000011200000091100001119

00001188000009610000115700001164000009060000111700000957000010150000110600001070000010970000105500000

88900001077000009770000079200000762000007900000071000000777000006580000070500000668000006740000071600

00054100000477000004700000046200000406000003420000033400000330000002200000020300000195000001900000014

700000089000000880000008600000085000000860000008700000085000000850000008200000082000000820000

0415049408530006S040906000001150002500000029000000270000002800000027000000300000002800000025000000310

00000320000003400000033000000330000003200000033000000330000003400000033000000330000003500000042000000

43000000800000008800000093000002310000039500000293000003070000028900000383000003150000038200000375000

00336000004250000031400000409000003900000036100000445000003580000036300000352000003320000032000000370

00000392000003590000042500000309000004240000034500000356000004260000034100000472000004710000033300000

42900000322000004060000036400000314000003550000027300000342000002840000022500000203000002120000023200

00016400000168000001420000012800000119000001290000011300000104000000350000003000000021000000170000000

700000019000000280000002700000025000000260000002600000027000000270000002600000025000000250000

0415049408530007S040906000002130006900000074000000810000008100000081000000810000007300000070000000730

00000730000007700000074000000760000007200000074000000770000007700000077000001190000017100000192000001

85000002130000026600000324000006480000100700000834000009330000090000001034000009340000104000001009000

00960000011090000089000001012000009860000096600001148000009770000100500001017000009760000093900000993

00001027000009480000108900000865000010710000091200000935000010760000087100001133000011670000090100001

09100000900000010320000092900000838000009500000075200000892000007960000075600000687000007050000070400

00058100000580000005290000050600000492000004980000048400000468000002240000020000000187000001790000017

100000108000000750000007200000070000000700000007100000070000000710000007000000071000000710000

0415049408530008S030906000001150003700000035000000360000003500000035000000380000003600000036000000400

00000400000004000000040000000370000003900000040000000380000003900000039000000380000004000000048000000




51000000650000009300000099000002340000041600000422000003760000040200000407000004150000040700000421000

00395000003760000037500000405000003940000038000000463000004200000040400000412000003920000040200000424

00000466000004740000046200000354000004480000045400000346000004020000049900000503000004880000041200000

35400000449000003530000033600000325000003280000026500000276000002300000021200000186000002430000016300

00015000000138000001200000013900000159000001570000012400000125000000160000000300000001000000020000001

800000018000000280000002700000025000000280000002800000026000000280000002800000026000000280000

0415049408530009S030906000002130008800000093000001000000009700000092000000880000008700000091000000920

00000890000008900000089000000870000008800000090000000910000009100000091000001070000013700000167000001

71000001980000025500000293000007010000110000001118000010010000104800001058000010730000106400001104000

01064000010440000104500001071000010410000102100001173000010930000107400001152000011220000112200001124

00001186000012320000120000000994000011350000113600000937000010680000116100001197000012230000109300000

97900001105000009190000086400000823000008640000074000000777000006940000072400000623000007000000056700

00058500000561000005190000052400000517000004990000045600000454000002330000020900000201000001970000018

500000140000000750000007500000070000000750000007200000074000000700000007200000071000000710000

0415049408530010S020906000001150003800000037000000370000003700000034000000350000003500000036000000340

00000350000003600000034000000340000003500000036000000360000003400000036000000350000003500000042000000

44000000390000003900000037000000360000003600000037000000370000003700000037000000380000003900000039000

00039000000390000003700000036000000380000004000000038000000380000003600000036000000360000004000000039

00000040000000390000003800000040000000380000003800000042000000410000004100000040000000400000004100000

041000000400000003900000039000000400000004100000039000000400000920000




I.8.: LOG BOOK (EVENTS)

For list of all OBIS codes and their structure the manufacturers are referred to

ANNEXURE C, p. 193.

Events – log file / events file book

1. The meter should have a log file / book that cover this topics /events:

1.1. At least 40 power failures- all phases or separate phase failure (partial)

Note:

(Sag / swell events if available should not recorded in this list).

1.2. At least 20 communication events such as:

1.2.1. Meter read

1.2.2. Time update

1.2.3. Configure files updates

2. At least 15 meter HW / SW problems such as:

2.1. B.I.T failures.

2.2. Watch – dog event

2.3. SW crash

2.4. At least 20 measuring events -such as:

2.4.1. Reverse phase

2.4.2. Reverse current

2.4.3. Low power factor

2.4.4. Generation

3. Each event shall accompanied with date and time start &stop time stamp

Note:

The same event shall be reported once at start stop time /date and shall not dump the

event data memory.

4. This file should be separate and not part of the load survey data events status .

5. While reading all the events data shall be read to separate event file.

6. Each event class shall be recorded separated (not intermixed) and not trample other

class.




I.9.: OFF THE SHELF PRODUCT DECLARATION

BIDDER’S OFF THE SHELF PRODUCT DECLARATION & UNDERTAKING

STATEMENT OF COMPLIANCE

I, the undersigned, ___________________ [name of Bidder’s authorized signatory], in my capacity as

__________________ [title or position of authorized signatory] of_______________________[name of

Bidder] (the “Bidder”), do hereby declare as follows:

1. The Bidder has received the Tender Documents and has carefully read all their contents;

2. The Bidder undertakes to comply with the terms and conditions of the tendering process, as set forth

in the Tender Documents;

3. The Bidder represents and warrants that it is capable of supplying the Products and rendering all the

Services within the time frames detailed in the Tender Documents and undertakes to abide by them.

4. The Meters and the software and all other services proposed by the Bidder hereunder will be

provided in accordance with the requirements set forth in the Tender Documents;

5. All representations, warranties, proposals and descriptions made by the Bidder are true, accurate

and

6. Our Proposal shall be binding upon us in accordance with the terms and conditions set out in the

Tender Documents.

1. The Meter that is proposed in this tender is off the Shelf Products and complying with the requirement defined below: 1.1. Is completely defined (design, construction and performance) by a formal technical

specification. 1.2. Is manufactured in accordance with formal production drawings, processes and

procedures which govern all stages and aspects of the manufacturing process. 1.3. Have successfully passed all qualification tests and the environmental tests in

particular. 1.4. Is manufactured with strict adherence to the prescribed quality assurance procedures,

which have to include in-process inspection procedures. 1.5. Is currently manufactured with at least 4000 units installed at electrical power utilities during the

last two years, and the accumulated operational data proves high reliability indicating the Product is mature.

1.6. Is regularly checked for reliability by field data collection, collation and corrective action taken when needed.

1.7. Is accompanied by a complete set of manufacturing drawings and procedures, reliability prediction, user manuals and maintenance manuals.

2. In case where changes are needed in order to comply with the TENDER EQUIREMENTS they will done in this terms and conditions: 2.1. The changes should not involve the measuring elements. 2.2. The function/application to be effected by the change is already exist and there is a need to

make only some minor changes In software without a need for change in hardware whatsoever.

2.3. The changes should not result in a need to certify the meter. 2.4. The changes should not cause any delay in time schedule. 2.5. I.E.C engineers should have the absolute right to approve or reject the proposed change.




Note: Permitted changes mentioned in the spec are DST and Holidays applications .

Bidder's Information

Bidder’s Full Name: Bidder’s Address

Street: City State / Province Zip/Postal Code Country

Bidder's Contact Information: Telephones: Fax: e-mail:

Signature

____________________ Date:____________________




I.10.: LIST OF RELEVANT PUBLICATIONS

: LIST OF RELEVANT PUBLICATIONS

See in this spec




I.11.: METER TESTS A.R.O

DIRECT/CT CONNECTED METER, GATEWAY/DATA CONCENTRATOR, OTHER ACCEPTANCE

TESTS (A.R.O)

Testing of applications and software

Meter Acceptance Tests: Testing of applications and software for electronic meters with TOU, load survey and

communications functions.

The following testing applies to direct/indirect meter, gateway/DC, and MMS.

Purpose:

Described in this document are the procedures for testing of applications and software for electronic meters with

TOU, load survey and communications functions to be accepted by and deployable at Israel Electric Corporation

(IECo). Tested shall be performed on the winning manufacturer direct meter, CT connected meter, and gateway/Data

Concentrator.

Below are described the acceptance tests and documentation required of the meter supplier which have to be

provided. Passing these tests is a prerequisite for acceptance of the meter for installations at IEC. This document is

general and does not provide detailed description of precise test techniques nor does it include unique specification

details which may vary from meter to meter.

Note:

This document does not include metrological accuracy tests or fabrication/enclosure specification and labeling

checks. These are described in a separate document issued by Meter Testing Laboratory.

1. Testing of TOU, DST and relay outputs (if applied)

1) Creation of the correct files in the main software, 2) loading of configuration into the meter, 3) manual checking

of 200 TOU points representing different rates on workdays, weekends and holidays in all seasons, 4) including

the switchover to DST and back to standard time. The purpose of this test is to verify correct operation of meter

within each rate and period.

2. Testing of load survey and events log file

Operating the load survey recorder in Single and dual channel modes, in 15 and 5 minute resolutions, causing various

power failure and time & date shifting events (forward and backward). The accuracy of the survey record will be

verified by a reference recorder that is in use at AC. Testing of maximum demand recording in regular, long, and

short period and in periods with power failure.

3. Testing of PC applications on Windows 7

Installation of applications onto a PC.

Independent run of the following applications through gateway to {direct/CT connected meters}:

3.1 Meter reading

3.2 Load survey reading

3.3 Meter time correction – during standard time and DST.

3.4 Reading of meter event log

3.5 Changing TOU table.

3.6 Changing DST table – during standard time and DST.

3.7 Changing of output relay configuration

3.8 Reading of all configuration files from the meter for verification against reference configuration files.

3.9 Checking of file format converters on PC.

3.10 Checking of all output files.




Integrating the above applications provided by the supplier into the shell program that will be used to run them.

4. Remote communication (remote metering)

4.1 Remotely reading the meter, changing configuration tables, and performing all operations as described in

(4) within the main software using a: Cellular 3.0G or 3.5G or 4G (based on proposed solution) – Modem and

IECo server's tests as in 5.1 above.

Running all the independent applications (routines) provided by the supplier as described in (4) in remote mode, and

integrating these applications into shell software used in IEC to run them.

5. Checking of output files – Checking of file format converters, output file for billing (.iec), output file of load

survey record, event log.

Note:

All communications tests will simulate and check conditions of lost connection between the meter and the remote

operating program. We will check the impact of and possible damage to the meter and/or operating software

resulting from such conditions, and the self-recovery ability of both the meter and the operating software.

6. Accelerated aging testing

IECo preserves the right to perform accelerated aging tests shall be performed at IECo based on standards IEC 62059-

31-1, and IEC 62059-41. IECo shall decide which segments of these standards to implement. Construction of a

reliability model shall produce the following outputs to IECo: 1) verification of RAM report, 2) early alert on potential

serial failures, as part of the approval of model. 3) Potentially prediction of model expected life-time, and possibly

cost estimation (only) of meter OPEX+ CAPEX based on knowledge of serial failures, and their cost. If serious failures

are detected then model might not be approved.

The accelerated aging tests shall be run on every new manufacturing batch – for verification of coherence of product

quality over the years, and detection of potential changes. If serious failures detected, then batch might not be

accepted.

7. Documentation

Receipt of up to date manuals and documentation for operating all the above applications. Receipt of test reports, from the meter Bidder regarding all the above applications (excluding integration with the shell software). Communication protocol details (after signing of NDA). It is possible to submit this software at a later mutually agreed time after receipt of the initial shipment of meters.

8. Verification software for checking the correctness of TOU and DST tables in meter (test 1). It is possible to

submit this software at a later mutually agreed time after receipt of the initial shipment of meters.

Note:

Discovery of problem or incompatibility in the software requires repeating of all the above tests after correcting the

problem.

9. High voltage tests

If meter manufacturer performs and presents serial acceptance insulation tests according to IEC 62052-11, to every

meter of that model type, before exiting the factory, then no model type insulation tests shall be performed.

Otherwise model type tests shall be performed.




CHAPTER I.12.: LIST OF ABBREVIATIONS / GLOSSARY

AA After Approval

AC Alternate Current

AEO After Exercise of Option

ANSI American National Standards Institute

ARO After Receipt of Order

ATP Acceptance Test Procedure

ATR Acceptance Test Report

ARO After recive order

ATS Automatic Test System

CCITT International Telegraph and Telephome Consultative Committee

CM Configuration Management

COC Certificate of Conformance; Certificate of Compliance

CT Current Transformer

CDR Critical design review

DC Direct Current

DFD Data Flow Diagrams

DR Design Review

EMC Electromagnetic Compatibility

ESD Electrostatic Discharge

FAT Factory Acceptance Test

FDR Final Design Review

FCA Free Carrier, Airport

FMECA Failure Mode Effects and Criticality Analysis

HW Hardware

ICD Interface Control Document

IEC International Electrotechnical Commission




IECo Israel Electric Corporation LTD.

ILS Integrated Logistoc Support

LAT Laboratory Acceptance Test

LCC Life Cycle Cost

MON Months

MTBF Mean Time Between Failures

MTTF Mean Time to Failure

MTTR Mean Time to Repair

PC Personal Computer

PHS&T Packaging, Handling, Storage and Transportation

PPL Provisioning Parts List

PR Program Review

PRELIM Preliminary

QA Quality Assurance

QC Quality Control

QTY Quantity

REF Reference

RFP Request for Proposal

RTC Real Time Clock

RAM Reliability, Maintainability and Availability

RSPL Recommended Spare Parts List

SEQ Sequence

SIP Survey Interval Period

SPEC Specification

SOW Statement of Work

SR Self Read

SW Software

TARIFF Rate in the TOU Structure




TOU Time of Use

WBS Work Breakdown Structure

WRS Work Responsibility Structure

IECo Israel Electric Corporation Ltd.

LCD Liquid Crystal Display

LED Light Emitting Diode

MTTF Mean time to first failure

TTF Time to first failure

VT Voltage Transformer

OBIS Object Identification System




CHAPTER I.13.: TRAINING COURSES SYLLABUS

Training courses

Training content

The training organized at IEC plant for technicians and engineers. Training should cover direct/CT connected meters,

gateway/Data Concentrator and all software applications required by this tender.

Up to a maximum of 15 trainees - per training.

Training programs shall be based on a balanced compromise between theory and practice.

For keeping courses interactive, different supports are used such as: presentation by slides, demonstration of PC,

hands on sessions.

Complete training manuals will be given including:

Training programs

All training shall be conducted in Israel in English or Hebrew.

Training facilities

er testing facilities

Functional Product Training – 1 Week Course

Day 1 – Introduction to Product/Range, Features.

9-00 am to 12-30 pm, 1-30 pm to 4-00 pm.

Day 2 – Meter Hardware block diagrams and electronics scheme, Meter Wiring,

9-00 am to 12-30 pm, 1-30 pm to 4-00 pm.

Day 3 - Testing in Laboratory expectance tests and type tests including Hands-On

9-00 am to 12-30 pm, 1-30 pm to 4-00 pm.

Day 4 - Software – Metering (Firmware) software metrology Meter Support Software, 9-00 am to 12-30 pm, 1-30

pm to 4-00 pm.

Day 5 - Customer Support Problems

Questions and Answer Session.

9-00 am to 12-30 pm

General Discussion, Other Topics, Documentation and Handouts.

1-30 pm to 4-00 pm.

At the end of the course each trainee receives an accreditation certificate and a complete manual.




CHAPTER I.14.: TECHNICAL DOCUMENTATION & SOFTWARE REQUIREMENTS

1. Documentation / data and software with proposal

Documents shall be in Hebrew or English /dimensions and quantities shall be in the SI units

At least one hard copy of each documents is needed & soft copy PDF or doc format

1.1 Checklist Submittal list

1.2 Answers to the SPECIFICATION (306-3-03-13 entire specification).

1.3 Documentation quality: must be of reasonable quality and depth as compared to normative

what IECo is receiving from major meter manufacturers. I.E. a 30 pages manual is

probably insufficient.

Manual has to define all configurations such as TOU/DST/special days, dial test mode

entry/exit.

Manuals have to relate to most aspects described at tender spec. manuals with plenty of

issues left un-described at manuals – documentation is insufficient.

This document shall be designated: Bidder specification - chapter B

1.4 Meter Type approval Certificate.

1.5 ISO 9001(2008)-certificate

This document shall be designated: Bidder certifications documents- chapter F

1.6 Quality questionnaire.

1.7 RAM questionnaire.

1.8 Pervious METERS installation questionnaire.

1.9 "Off the shelf” meter declaration.

This document shall be designated: Bidder answers to Questionnaires – chapter F, and

Includes Functional diagrams and Block diagrams.

1.10 Operation Manual. Shall be of satisfactory depth and include sufficient data for

functional operation.

1.11 Installation Manual -- Installation drawings installation instructions.

1.12 Software manuals- A complete set of manuals shall be provided for the Run time

Software SW modules description, input/output parameters description, operating time

budget, description of SW methodology and algorithms.

1.13 Quality manual.

This document shall be designated: Manuals and Drawings chapter I.

1.14 Software for operate and test the meter in the technical stage.

Final data Submittal - Documentation and data A.R.O

As a part of the 5 preliminary samples delivery for approval following documents shall be

provided:

1.15 Acceptance Test Reports applications & SW – meter applications (TOU /DST /

survey data outputs etc.)

1.16 Acceptance Test Reports metrology for the preliminary delivery and for each

delivery.




1.17 Electronics schematics + components list & data sheets + Layout drawings+

mechanical and assembly drawings.

1.18 Maintenance Manuals + recommended replaceable parts + Storage instructions.

1.19 Software manuals - A complete set of manuals shall be provided for all the SW

required.

Note: For each SW there shall be a description of SW methodology and algorithms,

SW modules, SW installation SW files & folders input/output parameters, SW operation.

1.20 Software testing & Q.A tests reports – each SW shall be tested before delivery

to IECo the tests results shall be sent along with SW delivery each version and

correction shall be marked and tested, the manuals shall be updated.

1.21 Communication protocol Reference data and manual + sources.

Note: All manuals shall be updated in case of changes.

CHAPTER I.15.: WARRANTY & FOLLOW ON SUPPORT

Warranty

1. Hw repair 1.1 The Bidder shall be responsible for the meter quality and correct operation for a period of

36 months from the time the meters have been supplied. Repair of systematic failures,

design defects and of latent defects, performing retrofits and updating relevant

documentation subsequently. Systematic failures during first year – 36 months shall be

measured from time after fix them. Systematic failures detected after installation, after

model approval, during warranty period – the bidder is committed to extend warranty

period within extra 12 months.

1.2 The Bidder shall replace each faulty meter that has been returned to the Bidder during the

warranty period – excluding those that have been damaged due to incorrect usage – with

a new or repaired meter at no cost (including transportation), within 3 months from the

date the faulty meters have been returned.

Note:

The claims regarding particular meters will be ever valid for fault events that precede the warranty

expire. The claim validity will expire with termination of declared meter life period.

1.3 A faulty meter is defined as the case where the meter does not meet one or more of the requirements in this Specification, as well as requirements for safety, reliability, physical integrity, etc.

1.4 If during the warranty period more than 0.5% of the installed meters fail to meet the requirements of this specification, the warranty period shall be doubled. For the definition of Failure, see Chapter B-14 Appendix 14a, Clause A1, Paragraph 2.

1.5 The Bidder shall be informed about the failures found, in order to be able to perform corrective actions.

1.6 The Bidder's technical staff will coordinate an investigation for the determination reasons for the faults found, as well as corrective measures. These shall be coordinated with IECo technical experts dealing with preventive measures, diagnostics and failure statistics. The report upon each corrective measure will be directed to IECo immediately after the execution.

1.7 Each such repaired meter shall be returned to Purchaser together with a report defining the failure and corrective action. (even for unfixable Meters)




2. SW repair /support

2.1 The Bidder shall be responsible for the meter SW (firmware) and the aux software

supplies by him for this tender for the correct operation & functioning for the period of

meter life span as defended in this tender .

2.2 The Bidder shall respond within eight hours to every software (meter SW and aux SW)

failure call (Telephone/email/fax) and within four hours to every fatal (system) software

failure call during normal working days. The Bidder shall identify & verify and correct the

failure within 48 hours thereafter, or shall provide a satisfactory temporary fix until such

time when the software is fully operational. This service shall be provided countrywide, in

all relevant facilities of the Purchaser.

2.3 Automatic submissions of updates and corrections to Software modules. Updates to "third

party" modules shall be field tested and validated by the Bidder.

2.4 Every SW problem new version/correction shall accompany with documentations

describe the problem & consequences and the corrections were made, every versions

shall be marked and dated.

2.5 Every new SW /corrections shall be accompanied by SW tests and SW QA approval.

2.6 Software follow-on support services shall be provided for the period of the meter life span.

Note:

In case the Bidder can’t support the software for any reason, it will notice the purchaser that

software support is going to stop 12 months before.

3. Documentations updates

Automatic submissions of updates and corrections to manuals, drawings, catalogs, specifications,

reliability data and all other documentation provided under this and subsequent contracts.

4. Follow-On Support

4.1 The Bidder shall conduct Follow-On Support activities (after the expiration of the warranty

period).

4.2 The activities shall be defined under this paragraph and shall consist of:

4.2.1 Telephone/email/written consultation.

4.2.2 Assistance/troubleshooting/consultation at Purchaser's facilities.

5. HW repair

The following refers to direct/CT connected-CT meter and to gateway/Data Concentrator and

to antennas.

5.1 IECo shall not repair defected and unfixable meters after warranty period.

5.2 The Bidder shall repair systematic failures, design defects and of latent defects that shall

be exposed after warranty period and filed tests.

6. SW repair /support

The following refers to MMS, batch remote SW for PC, low level routines for "Shoval" SAP

and IECo application. Please pay attention to batch – executable within applications with a

command-line.

6.1 See warranty – SW repair /support details in the paragraph above.

6.2 Notification of new functions, applications or other software modules becoming

available for incorporation in Purchaser's Product.

6.3 The Bidder shall propose such software and its integration upon Purchaser's request.




6.4 Adaptation to new common operating system such as Windows 8.1 for PC, or windows

8 for servers.

7. New hardware / cease of old meter manufacturing 7.1 Notification of new hardware becoming available for incorporation in Purchaser's

Product. The Bidder shall propose such hardware and its integration upon Purchaser's

request.

7.2 If after 5 years from the first delivery of the order the Bidder decides to cease

manufacture the meter for any reason, it will give the Purchaser at least 12 months

prior written notice that manufacture of the meter is going to cease.

7.3 After which 12-month period the Bidder shall no longer be obligate to provide hardware

meters or spare- parts of the follow- on support program.

7.4 On receiving that notice the purchaser may place a lifetime buy order for meters or

spare parts with the condition that the order is placed to the Bidder place no later than

9 months prior to the date the meter is to cease.




DIRECT POLY-PHASE KWH CT CONNECTED KWH & KVARH METERS, GATEWAY/DATA CONCENTRATOR - WITH TIME OF USE AND LOAD PROFILE REGISTERS

ANNEXURE A – DATA SUMMARY

Version 1.0




ANNEXURE A – SUMMARY OF DATA




A.1. STATEMENT OF WORK

SUMMARY OF DATA

1. Scope

Under this Statement of Work (SOW), the Bidder shall be responsible for the delivery of the

Product, which is defined in Annexure "B", (the Specification), in quantities defined herein. The

Bidder shall manufacture, assemble, test, preserve and ship the Product associated equipment

and documentation and provide services in accordance with the Contract. The Bidder shall be

responsible for the satisfactory operation of the Product.

2. Applicable Documents

The Bidder shall list all documents forming a part of this SOW to the extent specified therein.

The following documents shall form a part of this SOW to the extent specified herein. Chapter

I.10.: List of Relevant Publications

3. Program Management

The Program

The Bidder shall appoint a Program Manager preferably in Israel. He shall serve as a

Local point for the Purchaser and shall have the authority to commit company's resources

in order to perform this Program in accordance with the Contract.

3.1 The Bidder shall provide a Work Breakdown Structure (WBS) diagram

describing the structure of the Program in detail.

3.2 The Bidder shall provide a definitive description of every WBS task. The

description shall include the following items:

3.2.1 Task name

3.2.2 WBS number of the task

3.2.3 Task objective

3.2.4 Task description

3.2.5 Input (a list of all inputs required for the performance of the task)

3.2.6 Output (a list of all the outputs of the task)

4. Schedule (GANTT)

The Bidder shall provide under this paragraph a master schedule for the performance of

all WBS tasks. Schedule data shall be provided in the form of PERT diagrams and their

derivative GANTT charts. The GANTT and PERT diagrams shall include detailed steps,

critical path that may influence the final date, period of time for each step, and the

responsibility for execution of each step.

5. Program Review (PR) and Progress Reports




The Bidder shall propose under this paragraph PR's, the objectives of which are as

follows:

5.1 Solving Program Management problems

5.2 Presentation of Program Status by Bidder

The Bidder shall define the structure of his Progress Reports in accordance with the

requirements of paragraph 18.3 herein.

6. Design Reviews (DR)

6.1 CDR & FDR

Following are Purchaser's requirements for conducting Design Reviews. The Bidder

shall describe his proposed DR procedures under this paragraph based on paragraph

18.5 herein and these requirements. The Bidder shall conduct DR with Purchaser's

personnel, the main objectives of which shall be:

6.1.1 To clarify and eliminate all misunderstandings, differences, errors and

omissions based on the preliminary documentation, drawings and

procedures.

6.1.2 To ensure the adequacy of technical solutions proposed for Purchaser's

requirements.

The DR shall be based on the preliminary documentation which shall be submitted in

accordance herein, but no later than one month before the respective DR is

scheduled.

The DR shall be scheduled no later than three 1 month ARO. All DR documentation

per the paragraph above shall be submitted to the Purchaser no later than one (1)

month ARO. DR Agenda is to be provided by Purchaser no later than two (2) weeks

before the DR. The DR shall be held at Purchaser's facilities in Israel.

6.2 Sub Bidders Management

The Bidder shall define those parts of his Product which are supplied by Bidder's sub

Bidders. For each such part (hardware, software etc.) the Bidder shall identify its

respective sub Bidder. The Bidder shall state his policy and procedures regarding Sub

Bidder Management.

6.3 Changes

The Bidder shall propose change procedures for software and hardware delivered

under the Contract and shall be subject to Purchaser's approval.

7. Testing Program

Inspection and Test (I&T) Plan.

The inspection and Test (I&T) Plan shall cover the following stages:

7.1 Manufacturing inspection and testing process of equipment (hardware) and

software (including sub Bidders).

7.2 Full Factory Acceptance Testing, providing full performance verification.




8. Laboratory Acceptance Testing

The Bidder shall list the Tests/Inspections tests.

The I&T Plan shall state the procedures for executing the testing items mentioned in

paragraph above covering the following issues as a minimum:

8.1 Test/Inspection Procedures - shall be divided into equipment and software and

shall be submitted to Purchaser for approval. Each specific measurement shall be

identified, its tolerance defined and proper measurement equipment selected.

8.2 Acceptance/rejection criteria and associated operating conditions shall be defined

for each data item and for each function. Retest guidelines/procedures shall be

defined as well.

8.3 The procedures shall include free testing, performed by Purchaser's personnel or

its representatives. The Bidder shall list the test procedures.

8.4 Inspection and test schedules shall be in accordance with the time schedule as

defined by the Bidder. The Bidder shall give sample notice as to the time and the

place when each batch of Products shall be ready for such Inspection and Testing,

in order to enable the participation of Purchaser's personnel, or its representatives.

Submittal of the Inspection Test Reports shall be listed by the Bidder.

9. Acceptance Tests

9.1 Type tests - technical stage - sample meters test.

9.2 Meter Approval Acceptance Tests – A.R.O – I.11..

9.3 Continues deliveries Acceptance Tests – after meter and software approval

and filed testing success

9.3.1 Factory Acceptance Tests (FAT) and initial calibration mutual report - for

each meter.

9.3.2 Laboratory Acceptance Tests (LAT) - IECo lab accuracy tests, high–voltage

tests, functional tests-configuration files verification.

9.3.3 Accuracy tests at IEC labs and consumer premises during meter

installations.

9.4 Acceptance Tests comprise three Sets of Tests as mentioned herein above:

9.4.1 Factory Acceptance Tests (FAT)

9.4.2 Field Testing (FT)

9.4.3 Laboratory Acceptance Tests (LAT)

9.5 The Bidder shall prepare and submit for Purchaser's approval an Acceptance

Test Procedure (ATP) for the Acceptance Tests below:

9.5.1 The Acceptance Tests shall be performed according to the approved

procedures.

9.5.2 Successful completion of Acceptance Testing shall be prerequisite to

Acceptance, which shall be constituted by duly signing a Certificate of

Acceptance.




9.5.3 The Product test equipment and spare parts shall be examined to determine

conformance to the applicable drawings and all requirements of the

Specification.

9.5.4 The Product shall be operated for a period of time sufficient to establish

stability of performance. The performance/functional characteristics of the

Product shall be measured in accordance with the approved ATP and the

data recorded.

9.5.5 If the Product fails to meet the Acceptance Tests, it shall be rejected. Field

testing of the Product shall not be made until it is determined that the

Product meets all Specification requirements. The Product may be reworked

or have parts replaced to correct the cause of rejection. Final particulars

concerning the rejection and action to correct the fault shall be submitted.

9.5.6 Unless otherwise specified, all Acceptance Tests shall be conducted under

the standard conditions (environmental) which have to be specified by

Bidder in the ATP.

9.6 Series Production, Inspection Test and Acceptance Test

9.6.1 The meters shall be manufactured and calibrated in homogeneous

production series and supplied in piles. The piles on appropriate pallets will

be grouped for shipping in standard containers, trucks, or other

simultaneously shipped aggregate platforms. An inspection shall follow the

"serial quality" approach regarding units of such containers or trucks.

9.6.2 Accuracy, AC voltage and functionality tests results including initial

calibration data of each shipped meter shall be sent to the Meter Test

Station Department of the Israel Electric Co. in Excel or Access files on

memory disks or other electronic media prior to each shipment, for purpose

of metrology normalcy. The results of tests that have been performed on

samples at the Bidder plant for quality inspection purposes shall also be

sent in the same format. Each shipped platform arrangement will be

announced and attached to the test report.

9.6.3 Acceptance lot-by-lot inspection by attributes will be performed at the Meter

Test Station according to IEC62058-11, ISO 2859-1 and IEC62058-31. A lot

for the acceptance inspection will be defined as cumulative quantity of piles

that have been delivered to IECo Metering Unit premises within one

container or truck. Alternatively, IECo may define a lot at its sole discretion.

9.6.4 Inspection level II will be used. Single sampling plan for normal inspection,

AQL=1 will be used regarding non-critical nonconformities (as per table 4 in

IEC 62058-31).

For critical nonconformities (as per table 4 in IEC 62058-31) Single

sampling plan for normal inspection with acceptance number 0 will be used.

9.6.5 If lot will be rejected next lots will be tested according to Double sampling

plan for normal inspection.

Other meter's attributes may be tested for conformity. Failures in these tests

will be considered as non-critical nonconformities.




9.6.6 Regarding nonconforming meters applicable procedures are given by IEC

62058-11 and shall be continued by the following measures. In case of

rejection the whole lot will be replaced by reshipping, or arresting on the

place with 100% revision before presenting for re-inspection. The

Contractor will be responsible for bearing all associated costs. The

Contractor will be notified by phone/facsimile/e-mail. Rejection of five or

more lots upon the same order delivery will be considered as Contractor's

failure, and will lead to legal action.

9.6.7 The results of the acceptance tests will be reported to the IECo Import

Department that will notify the Bidder about the acceptance tests failure.

9.6.8 The nonconforming meters within a lot in quantities, which are still within

acceptance criteria, will be subject to replacement if claimed by the

Purchaser.

Note: In order to prevent any holdback in IECo to install newly purchased meters

due to rejected lots, the Bidder will be obligated to expedite extra

deliveries, above and beyond the agreed timetable.

9.6.9 If three or more meters delivered according to the same order will be found

with a same failure caused by production failure, or wrong meter

construction, or component failure, which affects normal operation of the

meter, the failure will be considered as "serial failure" and will lead to legal

action.

9.6.10 During the life cycle of the meters IECo may conduct from time to time and

at its sole discretion number of tests detailed in the Type Test procedure, in

order to ascertain the stability of the meter metrology characteristics. If the

meters fail to comply with the test requirements, the Bidder will assume

responsibility.

9.6.11 IECo representative, at IECo's sole discretion, may visit and inspect the

active production line being used to manufacture and assemble the meters

in order to assure the suitability and compatibility of the new (or renewed)

meter deliveries with all the requirements of this specification at any stage of

the contract.

9.7 In addition to the inspection the following tests shall be included in the LAT:

9.7.1 Functional tests of both HW and SW.

9.7.2 Total and summary of tariff (TOU) registers equality .

9.7.3 Visual inspection (external), checking pushbuttons, loose items etc.

9.7.4 Corresponding time show.

9.7.5 Five units randomly selected from each batch shall be opened and

inspected as follows:

9.7.5.1 Printed circuit board(s) integrity and coating.

9.7.5.2 Quality and cleanliness of soldering.

9.7.5.3 Tightening of screws, connections and connectors etc.




9.7.5.4 The acceptance number for the functional tests as by 9.1.1-

9.1.4 shall be 1.

9.7.5.5 The acceptance number for the inspections as by 9.1.5 shall

be 4.

9.8 Field Testing

The Field Test shall be performed by the Purchaser as follows:

9.8.1 The Products delivered under the preliminary and initial deliveries (as

defined in 18.1 herein) shall be installed at Purchaser's customer's

premises. The Products shall be operated and monitored, to verify their

ability to meet the requirements of Annexure "B". All test equipment,

training, documentation and design review must be delivered by the Bidder

and accepted by the Purchaser prior to the start of the test.

9.8.2 The test shall run for 6 months after the installation of the Products supplied

under "initial delivery". The Products shall demonstrate compliance with all

the requirements of Annexure "B”.

9.8.3 The availability of metering service in case of half year replacement meant

time and according to MTBF shall be 99.7% at least.

9.8.4 The appropriate failure rate as a function of availability and meter reading

interval will be approved by mean field data collection.

9.8.5 The collecting field data, failure classification and sampling plan- according

to IEC TR62069-11, IEC TR 62059-21.1.3.6. The field data collection will be

performed by IEC Central Metering Unit during 1 year starting from

installation of about 50 first meters.

9.8.6 Provided that field data will point to inadequate failure rate, IECo will

exercise a right to prolong the warranty term pro rata to availability

deterioration.

9.8.7 Accelerated Life Test (Aging) – The meter type shall undergo accelerated

life tests (at maximum voltage and current, and extended temperatures –

above and beyond the operating temperature range) in order to

demonstrate its reliability and long service life. The test shall be carried out

per IEC 62059-41 methodology, and its results shall be provided with the

technical offer.

9.9 Quality Assurance (QA) System

The Bidder's Quality Assurance Program shall meet the requirements described in

ISO 9001 (2008).

The Israel Electric Co. shall have the right to audit and comment on Bidder's

Quality Assurance System, regardless of whether it was previously audited by a

certifying agency or any other body. IECo experts may ask to visit the Bidder's

plant at the technical stage of proposal evaluation or later. The Contractor shall

submit under this paragraph his QA Manual and procedures for:




Calibration (including explanation of calibration chains for main measurements

that make conditions to quality of final product)

Qualification of suppliers

Non conformities and corrective actions.

9.9.1 A mutually agreed inspection plan, including witness points, shall be agreed

between the Purchaser and the Bidder.

9.9.2 Any subsequent alteration to this program shall require Purchaser’s

agreement prior to start of any work affected by these alterations.

9.9.3 When subcontracting part of the works, Bidder shall submit 2 copies of his

un priced orders to his sub- Bidder(s) for materials, services and parts,

clearly marked with the purchaser’s demand and shall specifically indicate

Bidder's quality requirements from his sub–Bidder(s(.

9.9.4 Test and inspection certificates as required in specification and the

applicable standards shall be submitted immediately following their

generation.

9.9.5 The certificates shall be original signed by the Bidder and contain actual

values measured. The generation of certificates, including those generated

by sub-suppliers, shall bear no extra cost to Purchaser.

9.9.6 Source inspection, including inspection of local manufacturing, shall be

conducted by proficient approved organizations or individuals, using

documented procedures. Any independent inspector shall be subject to

Purchaser’s approval.

9.9.7 Modification of the Meter Design and Technology (hardware & software) -

Any change in technology processes – including its replacement,

modification of the meter form, structure of parts or materials from which the

parts are made of – after IECo has approved the meter, shall be done only

after written agreement with the Israel Electric Co. has been settled. For

obtaining this agreement the Bidder shall present the company the

following:

The engineering drawings describing the modification

Samples to be tested in the Israel Electric Co. according to its judgment

Proof that the proposed modification does not decrease the quality or performance of the meter.

Note:

In case the main manufacturing line is replaced by another, an IECo representative will

inspect and approve the new premises before manufacturing will commence there.If the

said modifications result in degradation of meter performance or quality, IECo reserves

the right to demand that the meters be returned to their original form. If it has been

agreed between the Bidder and the IECo to carry out the modification, the Bidder shall

inform the company in writing about the serial number of the first modified meter, and the

batch or shipment identification details.




9.10 Follow-On Engineering and Support - As required at chapter I.15..

9.11 Warranty – Chapter I.15.

9.12 Test Equipment and Tools

9.12.1 The Bidder shall specify and propose all Test Equipment and Tools required

for the proper maintenance and operation of the Product.

9.12.2 The Bidder shall define Test Equipment and Tools in the following

categories:

9.12.2.1 Standard Test Equipment and Tools

9.12.2.2 Special Test Equipment and Tools

9.12.2.3 Support Equipment and Tools

9.13 Electromagnetic Compatibility (EMC) Program

Electromagnetic Compatibility (EMC) Program

The Bidder shall conduct an EMC program. The Bidder shall resolve all EMC and

lightning protection problems of the Product(s) after its installation, and repair all

relevant equipment (and software) consequently.

9.14 Software Development Program

Software Development Program

The Bidder shall define under this paragraph his Software Program, addressing the

following topics as a minimum:

9.14.1 Software and firmware development methodology.

9.14.2 The Bidder shall define in detail the computerized software development

tools and describe their utilization throughout the software development

phase.

9.14.3 Software and firmware updating methodology.

9.14.4 Related documentation updating.

9.14.5 Testing methodology.

9.14.6 Software and firmware maintenance related procedures.

9.15 Installation Program

9.15.1 The Bidder shall submit his Installation Plan under this paragraph.

9.15.2 The Plan shall define policy, procedures and activities made by Bidder and

Purchaser so that the Product are installed by Purchaser's personnel

according to Bidder's detailed instructions and under his supervision

ensuring that the Product is ready to successfully pass Field and Laboratory

Acceptance Tests.

The Program is aimed at bringing the Product and Test Equipment to successfully

pass the Field and Laboratory Acceptance Tests until full commissioning.




9.16 Training courses

Training courses / content

9.16.1 The training organized at IEC plant for technicians and engineers.

9.16.2 Training programs shall be based on a balanced compromise between

theory and practice.

9.16.3 For keeping courses interactive, different supports are used such as:

presentation by slides, demonstration of PC, hands on sessions.

9.16.4 Complete training manuals will be given including Copy of slides presented

and Technical guides.

9.16.5 All training shall be conducted in Israel, in English or in Hebrew.

9.16.6 Training programs proposed syllabus Chapter I.13..




ANNEXURE B: DELIVERABLES

List of Deliverables

The Bidder shall list in detail all the items to be delivered under the Contract along with

their delivery dates in accordance with the division (and subdivision, if any) provided

herein.

1. Hardware:

Table 35 – Deliverables HW

Seq.

Nu.

IECo

Cat No. Description

Qty

Delivery Date Comments

1.1

Direct -

5260057

CT –

5260058

Data

concentrator

5260059

Direct Connected 3 phase Active

TOU static meter + load profile.

9,000

Technical

evaluation

stage On

submission of

proposal

(based on

special

permission

only from IECo

two weeks

later)

1.2 Direct -

5260057

CT –

5260058

Data

concentrator

5260059

Antenna -

5260168

Preliminary delivery

For mode type approval +

accelerated aging testing

10 direct +

4 CT +

2

gateway/Data

Concentrator

+

2 antennas

2Mo. ARO A.R.O.-After

Receive Order

1.3 Direct -

5260057

CT –

5260058

Data

concentrator

5260059

Antenna -

5260168

Initial delivery+ Field test deliveries 8 Pallets 2 Mo. (FCA)

A.A-After Approval

+ field tests 8

months approval

1.4 Direct -

5260057 Follow on yearly deliveries Overall : Each year:




CT –

5260058

Data

concentrator

/gateway

5260059

Antenna -

5260168

CT connected

110

100+20011

option

100

Year+_year

1.5 5238175

Portable Control station (test

equipment) for configuring

/formatting and maintaining of

electronic TOU meter and for

consumption + load profile data

collection

2

2Mo.ARO

11

Gateway/Data Concentrator is measured 1 per building of 120 apartments. In case for example only 32 meters are

enabled per gateway then 4 gateways are counted herein as 1 gateway. Pricing should be in accordance with that

solution.




Initial and follow on deliveries are conditioned upon Purchaser's approval of the products

delivered under the preliminary delivery. (Including all software versions and applications).

IEC shall test meter and software 2 weeks. An order to Initial delivery shall take IEC about 3-4

weeks, total time to initial delivery 6 months after receiving order to 5 meters(18.1.1.1).

Follow on yearly deliveries are conditioned upon Purchaser's success of the Product's in-

field test herein.

2. Software:

Seq.

Nu. Description Qty

Delivery Date

(Mo. ARO) Comments

3.1 SW for portable PC (list here a detailed

definition of all SW delivered) 100 2

3.2 SW - configuration laboratory 10 2

3.3. Low level access routines to MMS from

IECo application "Shoval"

1 1 month

These routines

for rd/wr to

MMS data base

– to be provided

to Shoval team

for embedding

at API

3.4. Metering Management software 1 license –

15 people

access with

usernames/

passwords

Immediately

3.5. Batch software for remote access to

meters direct/CT connected through

gateway/Data Concentrator

10 2

Table 36– Deliverables SW




3. Documentation

Each line that's relevant to hardware abides per all hardware modules: direct meter, CT meter, gateway/Data

Concentrator

Each line that's relevant to software abides per all software modules: MMS, function with parameters to portable PC,

diagnostic software per lab and per field.

Seq.

Nu. Description

Qty Delivery

Date (mo.) Comments

Prelim Final ARO AA

3.1 Software documents(manuals) 1 2 1 2

3.2 Software tests reports 2

3.3 Drawings 1 2 ---- 2

3.4 Tech. documents and reports 1 2 1 2

3.5 Testing reports 1 2 1 2

3.6 Maintenance Manuals 1 2 1 2

3.7 Installation Manual (direct / CT

connected, gateway/Data

Concentrator)

1 2 1 2

3.8 Operation Manual (direct / CT

connected, gateway/Data

Concentrator)

1 2 1 2

3.9 Training Manual

(direct / CT connected, gateway/Data

Concentrator)

1 15 1 2

3.10 Communication protocol reference

data and manual + Sources

(direct / CT connected, gateway/Data

Concentrator)

- 2 - 2

3.11 Program management DR & CDR &

GANT




3.12 ATR 2 2

3.13 Progress Report monthly

3.14 Notification of delay as required

3.15 Failure reports (HW/SW) as required

3.16 Meter Testing: Accuracy configuration

communication reports Each Delivery

Table 267 – Deliverables Documentation

Note:

All documentation shall be updated by the Bidder in accordance with the "As Built" configuration, as

recorded just before Field Acceptance approval by the Purchaser.

Suitableness to Chapter I.14. paragraphs 1.1 – 1.12 & 2.1 – 2.7

All documentation shall be sent in electronic form (CD) doc or PDF format. The CD shall be marked

with content / version &dates, at least one set for each should be in hard copy.

The Bidder shall list the different documents for each one of the Products under the appropriate heading.

An ATR (Acceptance Test Report) shall be delivered with each system/equipment

4. Services

Seq.

Nu.

Description

Qty

Delivery Date

(Mo. ARO)

Comments

5.1 training 1

set

Shall be Coordinated with IECo

5.2 Warranty 1

set

Chapter I.15.

5.3 Follow-on engineering and

support(including win 7 next-version

upgrade)

After warranty period ending

Software support Chapter I.15.

Table 38 – Deliverables Services




5. Reviews

Seq.

Nu. Description Qty

Delivery Date

(Mo. ARO) Comments

6.1 Design Review 1 set 2

6.2 Program Reviews 1 set I

Table 39 – Deliverables Reviews

(I) As required

6. Testing Schedules

The Bidder shall provide a schedule of tests and inspections, defined in acceptance tests, in the following

format:

Seq.

Nu.

Test

Date

Comments

6.1 Inspections for Product(s) xx through yy

FAT for Products(s) xx through yy

LAT for Products(s) xx through yy

Field Test

(іI)

(I)

(I), (ii)

(ii)

Table 40 – Deliverables Testing Schedules

(i) List the tests according to Products serial numbers (xx,yy).

(ii) Performed by the Purchaser.

7. Hardware /Software / services Options

Seq.

Nu. Description Qty

Delivery Date

(Mo. ARO) Comments

7.1 Development of function

with parameters (batch-

40 If non-existent off-the-shelf

software product then it is




able) if non-existent for

portable PC

mandatory to develop and

budget separately as software

writing service

Table 41– Deliverables Service Options




ANNEXURE C: GLOSSARY (ONLY) OF DELIVERABLES

List of Deliverables

Table 35 – Hardware /Software / services Options Deliveries (according to Deliveries List 18)

Item

Nu.

IECo Cat

Nu. Description

1 5260057 Direct Connected three phase Active TOU static meter + recorder

(reactive energy in addition, not rejected)

2 1100008648 Software services for configuration laboratory

3 2863249 Software services for Portable PC

4 2863090 Training

5 2210250 Spare parts

6 5238175 Portable Control station (test equipment) software and system for

configuring /formatting and maintaining of electronic TOU meter

7 5260058 CT connected 3 phase Active + Reactive TOU static meter + load

profile recorder

8 5260059 Gateway/DATA CONCENTRATOR

+ cellular modem inherent/external to gateway

9 5260165 meters data management software (MMS)

10 5260166 Assistance + low level access routines to embed at IECo driver to

"Shoval" IECo systems

11 5260167

Maintenance

- Improvement of communication to 97% availability

- (if repeater required)

12 5260080 Meters/GW-s Installation equipment

13 5260081 Meters/GW-s Diagnostics equipment

14 5260168 Meters/GW-s Antenna and routing cable to route antenna outside

building or at roof




ANNEXURE D: OBIS CODES AND OBJECTS DESCRIPTION FOR IECO DRIVERS

Listed herein all the energy variables and if exist their dlms/cosem OBIS code as required by IECo for implementation

of drivers between meter and IECo applications: (1) for IECo MMS, (2) for portable PC. The integrator of the system

must provide these fields as dlms/cosem objects or variables. These variables are being used to implement IECo:

report file, load profile file, and event log file.

Kindly please pay attention to these two important notes:

In accordance to standard there's a prefix A.B. preceding all of the OBIS code specified by this table.

The IECo current Attribute Name field, specified herein is not exact standard name, but there is 1:1

mapping and the name specified here is usually simple to comprehend.