0% found this document useful (0 votes)
14 views49 pages

Telemetry Equipment Specification for Substations

The document outlines specifications for telemetry works at substations AHMD-F, BRGN-F, and BRGN-G, requiring bidders to comply with detailed engineering, installation, and integration requirements for telemetry equipment connected to SDCC/JDCC. Bidders must provide a compliance table, submit documentation on equipment and power requirements, and ensure all equipment meets MEWRE standards, including cybersecurity measures. The scope includes installation, testing, and training, with strict adherence to international standards and local authority approvals.

Uploaded by

baskarang82
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views49 pages

Telemetry Equipment Specification for Substations

The document outlines specifications for telemetry works at substations AHMD-F, BRGN-F, and BRGN-G, requiring bidders to comply with detailed engineering, installation, and integration requirements for telemetry equipment connected to SDCC/JDCC. Bidders must provide a compliance table, submit documentation on equipment and power requirements, and ensure all equipment meets MEWRE standards, including cybersecurity measures. The scope includes installation, testing, and training, with strict adherence to international standards and local authority approvals.

Uploaded by

baskarang82
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

55

21. SPECIFICATION FOR TELEMETRY WORKS


SUBSTATIONS TO BE FULLY MONITORED
BY SDCC/JDCC

AHMD-F, BRGN-F & BRGN-G

The Bidder offer should be fully compliant with the following specifications
and providing a compliance table for this specifications paragraph by
paragraph with supporting documents. Any offer not containing this table will
be excluded.

The Bidder must install and commission all necessary telemetry equipment
and perform the engineering works for connection of the above-mentioned
substations to SDCC/JDCC in accordance with contracts for the construction,
renewal and upgrading of NCC/ECC/JABR DCC/SHUB DCC and the latest
contract for substations connected to NCC/ECC/JABR DCC/SHUB DCC and
its approved scope of supply.

The Bidder should submit a confirmation to the effect that he is fully aware of
all information, scope of work, specifications of required equipment & works.

All equipment, software programs and services foreseen to be delivered in the


substations or their far end substations or in the control center must be of the
latest design and in accordance with the state of the art in the supervisory
control system field and accordingly subject to MEWRE approval.

The work in the main telemetry equipment shall be under the direct
supervision of its manufacturer and should be included in tender prices.

The Bidder shall allocate for this project qualified engineers who have a
minimum experience of 6 years in erection, testing & commissioning of
telemetry equipment and Integration works of new substations in control
56

centers and intermediate substations, which shall be subject to MEWRE


approval.

The Bidder shall submit with his offer filled sheets stating full particulars of
electronic equipment and their allied software they propose to provide for the
execution of the works and to complete a reliable working system.

The Bidder should provide information with his offer about the power
requirements for each piece of equipment provided at each location.

The Bidder has to submit the details of the lifetime of the equipment intended
to be supplied by him. This will be considered in the tender evaluation. If an
alternative equipment is approved later then the contractor must indicate that
the lifetime is equal or better than the previously offered equipment.

The Bidder has to make use of all existing equipment / cablings / terminations
installed in different substations and in the CC buildings and any other
equipment as requested by MEWRE.

The Bidder has to include in his offer all modifications to the existing and
reused equipment to make them compatible for usage in their proposed
system. He should include as well the supply of all additional equipment
needed to make them suitable for usage in their proposed system.

In case if any of the existing equipment / cabling / terminations cannot be


reused then the Bidder has to include in his offer supply of new equipment /
cabling / terminations in order to make the system complete for reliable
functioning to the satisfaction of MEWRE. Such unused equipment / material
/ cabling / terminations etc. are to be removed and properly packed and
handed over to MEWRE stores and the supplier has to make provision for
such removal, packing and handing over.

The Telemetry equipment shall be supplied from a manufacturer that is fully


compliant with MEWRE specifications / requirements and the nominated
57

manufacturer for telemetry equipment will be subject to MEWRE final


approval after signing the contract and MEWRE has the right to study any
nominated manufacturer by the contractor later for MEWRE approval without
any objection from the side of the contractor (in case of disapproval, then the
contractor has to nominate another name for study/ approval)

General Notes for the price schedules:

The Bidder to submit a quotation for all services required and as detailed in
the enclosed price schedule for telemetry equipment. However, it is to be
noted that the price quoted should cover all works
(equipment/material/service) needed for the connection, monitoring and
control of the substations.

Any equipment/material/service added or deleted in price schedule has to be


substantiated by a complete explanation otherwise; such a change will not be
considered.

Any item mentioned in the specifications of the above-mentioned contracts,


but not mentioned specifically in the schedules will have to be supplied /
rendered and the same may be added to the relevant schedule otherwise the
same will have to be supplied / rendered free of cost.

Where quantities are not written the same are to be filled according to the
requirements.

The Bidder has to offer prices for all parts. Any partial offer will not be
considered.

10 G MPLS-TP links should be established between the new substations and


their far end substations used for the routing, which would require MPLS-TP
from the same vendor as that proposed in the new substations to be made
available by the bidder if needed in their far end substations.
58

All equipment proposed to be used on this project has to be approved by


MEW before the manufacture or the placing of order for such equipment.

The Bidder shall allow in his offer for all expenses likely to be required by
exceptionally inclement weather conditions and power network restrictions
and no financial claim will be entertained in this regard.

Attachments for Specifications for Telemetry Equipment:

RTU, MPLS-TP, 48V DC System, ODF, Digital Intertrip Equipment (if


applicable) & Documentation should be provided that is fully compliant with
the following attached specifications:

• Attachment 1 – Specifications for RTU


• Attachment 2 – Specifications for MPLS-TP
• Attachment 3 – Specifications for 48V DC System
• Attachment 4 – Specifications for ODF
• Attachment 5 – Specifications for Documentation
• Attachment 6 – Specification for Digital Intertrip Equipment

Scope of Wroks:

The works mainly, but not limited to, comprise of the following:

- All necessary works from TTB cabinets to the respective Control Centre for
Supervision and Control of related substations. This also includes works
related to the auxiliary power supplies.
59

- All telemetry, telecommunications & tele-control equipment (including the


intertrip equipment for the Over Head Line circuits) and auxiliary power
supply materials, services and works needed not only in the related sub
stations but also in the intermediate substations and in respective Control
Centers.

- The RTU to be supplied should be suitable to handle the IEC 6087-5-104


and IEC 61850 communication protocols with the existing interoperability list
in respective control center. The offered RTU should be equipped with latest
internationally recommended Cybersecurity functionalities / licenses as per
MEWRE requirements including next generation firewall (NGFW) with the
required security, performance, certification, networking, management and
security fabric.

- MPLS-TP nodes supplied under the contract should be equipped with latest
internationally recommended Cybersecurity functionalities / licenses. It
should be equipped with redundant hardware for Power Over Ethernet and
layer 3 routing functionalities as specified in attachment 2.

- MPLS-TP backbone nodes should have a packet switching capacity of up to


960G, it should be hardware ready /upgradeable (with the same chassis by
adding 100G line cards) to at least (100GbE).

- The modifications of computer system software & hardware, if required,


modification of existing displays and creation of new displays required for the
Supervision and Control of related substations.

- The transmission (if requested by MEWRE) of the Surveillance and Security


Camera (CCTV) System streams from the new substations (using GbE port in
new MPLS-TP equipment in these substations) to the CCTV Control Center
for Video Surveillance through the new MPLS-TP links and the existing
SDH/MPLS-TP backbone in arrangement with the respective control center/s
maintenance contractor/s.
60

- Interfacing equipment necessary to ensure compatibility between new and


existing equipment including design, renovation, expansion, or construction of
any facilities required for the equipment provided under the contract.
Interfacing shall also include planning for a smooth integration of the existing
and new installations without interruption of current operations.

- The IP telephone sets to be supplied in the substations should be capable of


integration with MEW IP Telephony System, support SIP protocol, support
Power over Ethernet, can be integrated in existing IT/IP infrastructure, have
an integrated Ethernet switch and have security features. It should be
connected to PoE ports of MPLS-TP equipment or an industrial Ethernet
switch.

- Proper packing and handing over of the removed unused equipment /


material / accessories to MEWRE stores as per specifications.

- Engineering, technical assistance and on job training during the contract


period to the Kuwaiti workforce to the satisfaction of MEWRE.

- On site installation and integration of all contractor-supplied equipment into


the existing network

- Performance of factory acceptance tests (FAT), commissioning tests and site


acceptance tests (SAT) for the offered telemetry systems in compliance with
performance requirements specified as per MEWRE’s specifications and
requirements and subject to MEWRE’s approval at the design stage.

- Shipment of all equipment (hardware, software and firmware)

- Documentation for the offered telemetry systems (soft and hard copies) as
per MEWRE’s specifications and requirements as shown in attachment 5 and
subject to MEWRE’s approval at the design stage.
61

- In intermediate substations 48V DC auxiliary power supplies will be in


general available at the substations wherein the contractor has to connect to
the spare MCBs in the distribution panel or else the same to be extended if
required. If the capacity of existing auxiliary power supplies is insufficient
then the same has to be replaced and its cost has to be included in the offered
price.

- Space for installation of the equipment at the stations will be in general


available within the existing communications rooms. The costs for any
shifting, rearrangement has to be included in the offer.

- All the batteries must be lead-acid, vented type with separate 2V / cell,
housed in clear translucent containers, with marking of maximum and
minimum fluid level and marks of polarity. The battery plug will be spark
proof. All Batteries are to be provided with name plates indicating the type,
capacity etc. and their maintenance and operational procedures.

- The rating/capacity for the Charger and Battery set for the new substations
mentioned in the price schedules is tentative and provisional and subject to
MEWRE approval at the design stage after submittal of all required
calculations considering 30% spare capacity and if higher rating / capacity
was found by MEWRE to be needed then is should be supplied.

- If the equipment or parts for them are no more manufactured, then an


alternative is to be proposed and approved then it will be binding on the
contractor to supply the alternative equipment / part at a price that is not more
than what is mentioned for the original proposed equipment / part and subject
to MEWRE approval.

- The sizing/configuration/no. & type of cards for the RTU, MPLS-TP &
Intertrip (if applicable) systems to be provided for the new substations and
their intermediate substations under the above-mentioned tender will be as a
minimum as indicated in the telemetry contractor’s technical offer and as per
62

MEWRE’s specifications and requirements and subject to MEWRE’s


approval at the design stage.

- The sizing/configuration/capacity of the DC systems to be provided for the


new substations and their intermediate substations – if needed - under the
above-mentioned tender will be as per MEWRE’s specifications and
requirements and subject to MEWRE’s approval at the design stage.

- The Bidder should provide two laptops with the specified design to operate
and maintain RTU and telecommunication equipment complete with original
soft copy, all cable connection and configuration setting.. etc. this should be
handed over to control center maintenance department.

- The Bidder is requested to extend the maintenance and guarantee period for
main equipment (RTU and/or Telecommunication) to three years in case the
proposed telemetry contractor is not the manufacturer of these equipment.

- The Bidder offer should be fully compliant with tender conditions,


specification, and having a technical proposal for all components of the
offered telemetry system with all necessary documents proving this
compliance. Any offer not fulfilling this condition will be excluded

- The Bidder to provide a compliance table for the proposed RTU, MPLS-TP
& Digital Intertrip equipment (if applicable) with MEWRE’s specifications in
attachments 1, 2 & 6 paragraph by paragraph providing a snapshot and
reference of the items/paragraphs in the documents attached with their
technical proposal to prove compliance for each paragraph. Reference to full
documents will not be acceptable.
63

- The telemetry equipment proposed to be delivered under the above-


mentioned tender should be equipped with lifelong licenses needed to achieve
the specified equipment availability / reliability / maintainability including
supported protocols and data points expansion though out its lifetime.

- The Bidder to confirm that the proposed telemetry contractor takes the
engagement to supply upon MEWRE’s request any sub sets, modules and
spare parts etc… of the equipment supplied under this tender for a period of
20 years after the final taking over of the system.

- The Bidder to confirm that the proposed telemetry contractor takes full
responsibility for the implementation of signal list as per MEWRE’s standard
pickup up data (PUD) sheets.

- For design purposes, for equipment inside buildings the ambient temperature
should be taken as -6 to +55oC and all equipment must stand continuous
operation at this temperature and at a relative humidity of 100% and must be
made dust proof by use of air-filters etc.
Equipment should not sustain damage at 85oC. Equipment operating in the
open air must stand continuous operation at 85oC surface temperature due to
sun radiation. It should be possible to store all the equipment at a temperature
of 85oC.

- All materials supplied and tested under this contract should be as per
International Standards such as IEC, BSS, IEEE, ITU-T etc…Copies of all
used standards will be furnished in English language whenever requested by
the Owner.

- The Bidder is to allow in his total tender price for obtaining approvals for all
works from the concerned local authorities wherever necessary and for
meeting their requirements in all respects at any time throughout the contract
period. No addition to the total price or extension of time to the contract
period will be entertained in this regard.
64

- The Bidder has to make sure that all works executed under this contract
confirms in all respects to the requirements of the international safety
standards and regulations as issued from time to time by MEWRE and other
Government authorities. The precautionary measures taken shall be to the
satisfaction of the Owner.

CHANNEL ROUTING:

- The new substations should be connected with two distinct data routes &
one telephone route to SHUB DCC and two distinct data routes & one
telephone route to the JABR DCC, using 10 G MPLS-TP links with their
far end substations used for the routing (which would require MPLS-TP
from the same vendor as that proposed in the new substations to be made
available by the bidder if needed in their far end substations) and then
through the existing SDH/MPLS-TP backbone in arrangement with the
respective control center maintenance contractor. The routes are subject to
MEWRE’s approval in the design stage.

- Any equipment needed to achieve the above channel routing but not
included specifically in the price’s schedules will have to supplied /
rendered and the same may be added to the relevant price schedule
otherwise the same will have to be supplied / rendered free of cost.

Integration Works in Respective Control Center and Intermediate substations:

The integration works to be carried out in respective control centers &


intermediate substations should cover the following works:

- Modification of Software for Computer Systems.


- Integration into Network Management System
- Integration into MEWRE IP Telephone System.
65

In addition to the above-mentioned works it should cover any other works for
the proper functioning of the proposed telemetry system including but not
limited to connection & monitoring of the contractor’s equipment in
intermediate substations and respective Control Centers.

Modification of Software for computer systems covers the integration of the


new substations into the SCADA/EMS system at SDCC/JDCC for an RTU
using IEC 6087-5-104 communication protocol with the existing
interoperability list in respective control center. The Bidder should arrange for
these integration works to be carried out by the respective control center
maintenance contractor or original SCADA System manufacturer for the
respective control center/s in case there is no running maintenance contract for
the respective control center/s.

Integration into Network Management System covers the routing /


transmission of the new substations’ data/telephone/NMS channels/traffic
through the existing SDH/MPLS-TP network and monitoring of new MPLS-
TP equipment proposed in substations by an Umbrella NMS and their
integration / management into the existing major (which is covering the
majority of the respective control center SDH network) Network Management
System (NMS) in the respective control center if these equipment can be
integrated to / managed with the existing major NMS, otherwise arrangements
should be made by the bidder for integration / management of these
equipment by an existing non major compatible NMS or a new dedicated
NMS should be provided in the respective control center by the bidder that is
able to integrate / manage the new MPLS-TP equipment. The Bidder should
arrange for these integration works to be carried out in coordination with the
respective control center maintenance contractor.

Integration into MEWRE IP Telephone System covers the programming in the


PABX of the respective control center/s for the IP Telephone lines with
appropriate parameters, downloading appropriate HFA firmware to the IP
telephone sets, configuring the IP telephone sets with the appropriate IP
addresses / parameters of the assigned route for which the connections /
66

programming / parameterizing is pre-configured / pre-assigned in the


SDH/MPLS-TP/Network Data Switches, configuring the IP telephone sets
with the programmed parameters for the IP telephone line in the PABX of the
respective control center/s. The Bidder should arrange for these integration
works to be carried out by the respective control center maintenance
contractor or original Telephone System manufacturer for the respective
control center/s in case there is no running maintenance contract for the
respective control center/s.
67

Attachment 1

REMOTE TERMINAL UNITS (R.T.U):

The Bidder offer should be fully compliant with tender conditions, specification, and
providing the requested technical proposal with clarifications and a compliance table for the
following specifications in this attachment paragraph by paragraph providing a snapshot and
reference of the items/paragraphs in the documents attached with their technical proposal to
prove compliance for each paragraph. Reference to full documents will not be acceptable.
Any offer not containing this table along with technical proposal and documents proving this
compliance will be excluded.

1. General:

Under this Contract the supply & installation of new RTUs using the IEC 870-5-104 communication protocol with
interoperability list of MEW only are to be included in the offer. The RTUs to be supplied should be fully equipped for all
the bays as indicated in the bus bar arrangement including spare bays and 30% spare capacity AND ALL TERMINALS
EVEN FOR SPARE TERMINALS ON THE TTB ARE TO BE WIRED TO THE RTU. The RTUs are to be connected to
Town DCC directly and to ECC through ICCP.

1.1. Functions:

The purpose of the remote terminal units is to transmit data collected locally to the Front End Sub-system. The data may
cover:
o Tele-measurements
o Status and Indications
o Service messages / alarms of the local supervisory equipment.

The RTUs will receive from the Front End Sub-system instructions to perform or to have performed,
typically:
o Switch remote controls (e.g. circuit breakers, load break switches isolators, Tap changer etc.)
o Instructions given to automated controllers (e.g. automatic reclosers, Automat Generation control, etc.)
o Cyclic type instructions.
o Arrhythmic type set point values.

THE CONTRACTOR WILL FORESEE INSTALLATION OF NEW RTUs WHICH USES THE
INTERNATIONAL COMMUNICATION PROTOCOL IEC 870-5-104 WITH INTEROPERABILITY LIST
OF MEW AND COMMISSION THEM WITH TOWN DCC UNDER THIS CONTRACT.

1.2. GENERAL CONFIGURATION:

The RTUs are and will be at least 32 bits 33 MHz microprocessor based. Exclusively hardwired systems are not
acceptable.

The main processing unit of an RTU is or will not be twinned. All parameters are to be modifiable locally by the portable
test sets through simple procedure and remotely by a simple software procedure via the main computers.

1.3. ACQUISITION OF ANALOG TELE-MEASUREMENTS:

1.3.1. ELECTRICAL CHARACTERISTICS OF SIGNALS:


68

The magnitude to be converted will be fed in the form of a direct current of which the variation range may vary, depending
on the case:

From - 10 to + 10 mA or 0 to 10 mA with the possibility of a continuous overload of 30% without damage.

A residual ripple with a peak-to-peak amplitude of 0.1 mA at 50 Hz frequency may be superimposed on the operative
signal. The supplier will take all the necessary precautions to eliminate this parasite component so that the conversion
precision remains within the limits stipulated below, it is assumed that the effective spectrum of the signal is under 0.5 Hz.

1.3.2. ACCURACY:

The overall accuracy of the chain including the transducer and up to the display at the control centre will be better than 1%
of the full scale.

1.3.3. READING AND TRANSMISSION SPEED:

All Tele-measurements should be processed every 2/4/30 SECONDS, taking into consideration not the present number of
substations, BUT THE TOTAL CAPACITY OF THE SYSTEM except in the case of transmission of more urgent messages.
But the time of transmission must not exceed TWO CYCLES in any case.

Spontaneous transmission of telemeasurements must be considered. Tele-measurements shall be transmitted when


significant change to the last transmitted value is detected, provided that the value for the significant change is adjustable
from 0% to 20% of the nominal value. This adjustable parameter is possible to be set globally, individually and / or as per
measurement type.

1.4. SIGNALS AND ALARMS:

The signals and alarms are be fed to the R.T.U. in the form of relay contacts free of potential. Barrier equipment consisting
of opto-couplers between the transfer terminal blocks and the R.T.U. are or will be installed.

1.4.1. TYPES OF SIGNALS AND ALARMS PROCESSED:

TWO STATE SIGNALS (Double Pole Signals):

The state period may vary from 50 milliseconds up to several hours. These are transmitted on a change of state and on
interrogation from the Front End Sub-System.

The presence or absence of both states simultaneously (open & close for example) must cause an alarm signal at the Control
Centre.

FLEETING ALARMS:

These alarms are picked up if they stay more than 25 milliseconds and they must be transmitted on appearance (auto-trip
signal, for example).

PERSISTENT ALARMS:

These alarms stay from few seconds up to many hours and they are transmitted on appearance and disappearance. Some of
these alarms are suppressed for 5 seconds as they could appear transiently.

TRANSFORMER TAP POSITIONS:


69

Each transformer has 21 positions (except few cases) which are connected to the RTU as 21 free contacts. The indication
is transmitted as soon as a transformer tap change moves from one position to the other (a supervision time of 20 seconds
is allowed between two positions after which an alarm signal must be initiated).

EQUIPMENT ALARMS:

All the alarms of the telemetry, power supply & communication equipment are sent to the Control Centre in a
comprehensive form.

1.4.2. VALIDITY:

From the stand point of data acquisition, a state lasting less than 10 ms is virtually devoid of significance on account of
interference phenomena and of contact rebound.

However, any information lasting over 25 ms is considered.

1.4.3. CASCADE:

Some incidents on the network cause a series of virtually simultaneous changes of state and alarms.

No indication is or will be lost in such a case (Fleeting alarms), but a delayed transmission can be expected. The R.T.U.
must be able to store in a buffer all the indications that might occur simultaneously. The number of data to be stored must
be equal to N/2, if N is the number of Tele-signaling relating to the corresponding R.T.U. type.

1.4.4. REPETITIVE SIGNALS:

Any acquired signal if repeated certain number of times within a period have to be blocked from transmission to the Control
Centre (Adjustable parameters should be available for the number of time and period). Such a signal blocking has to be
sent individually to the Control Centre. Once such a repetitive condition disappear the R.T.U. will send individually a de
blocking message for that particular signal and release the normal processing for the same.

1.4.5. TIME TAGGING OF SIGNALS:

The time tagging is done by the Front End Computers for Jabriya & Shuaiba DCC but in the case of NCC, Jahra and Town
DCCs the time tagging is done by the RTUs.

1.5. COMMANDS:

The Front End Sub-system transmits the following commands to the RTU:

o Switching Commands
o Set Points
o House Keeping Instructions

1.5.1. SWITCHING COMMANDS:

[Link]. SINGLE COMMANDS:


70

Such as switching on or off of a circuit breaker or raising and lowering of a tap changer. For this purpose the RTU must
have a set of possible duration pulses for implementation of the control varying from 0.5 second up to 20 seconds.

[Link]. GROUP COMMANDS:

Such as switching (ON & OFF) simultaneously a group of transformers which are normally operating in parallel or a
combination of transformers and BC .

In both cases, i.e. single command or group command, the necessary check before implementation process must be done
earlier to the execution of the command.

1.5.2. SET POINTS:

The RTU equipment must be ready to incorporate this facility by merely adding modules in future as it is not needed now.

1.5.3. HOUSE KEEPING INSTRUCTIONS:

The suppliers must detail what house keeping instructions the Control Centre will send to the RTUs.

1.6. CONDITIONS OF OPERATIONS:

The RTUs must invariably be electrically isolated from the circuits running out of the substation control building.

It is recommended that the potential used on high voltage equipment does not penetrate into the remote control equipment.
The input / output electronic circuits of such equipment must have the following levels of insulation:

- dielectric resistance at 50 Hz : 500 Volts


- surge wave in common mode : 500 Volts
in differential mode : 300 Volts

For TELE-SIGNALLING the de-coupling device must be able to cope with the following insulation in addition to the
connecting cables and input/output terminals of RTU.

- Dielectric performance : 2 KV at 50 Hz during 1 min.


- Surge Wave in common mode : 2 KV
in differential mode : 1 KV

The RTUs must be designed so that no false instruction is able to act and no false data may be furnished, despite:

o Any defect in or on the equipment making up the system.


o A short or long cut of the main power supply or of one of the power supplies of the system,
occurring at any time.
o Any interference collected by the external circuits.

No reloading of programmes should be needed after a short or long cut in power supply while in
operation. All of the operating system has to be stored in a non-volatile memory (PROM, EPROM)
but not in RAM.

1.7. SECURITY OF OPERATION:

The RTUs must be provided with internal checking devices for the detection of errors and/or failures in the equipment.
71

Such surveillance must cover all of the functions specified earlier i.e. acquisition of signals, acquisition and coding of
measurements, control instructions, links with the data concentrator etc.

The suppliers will describe the surveillance procedures and systems proposed as well as the consequences of the detection
of a defect, including:

o the checking of each subassembly (analog / numerical converter, acquisition of telesignaling etc.).
o The reciprocal checking between the various sub-assemblies.
o The safety of data interchange at interfaces (checking of address and checking of the instruction before
validation).

THE DESCRIPTION OF SUCH CHECKING MUST BE SUFFICIENTLY PRECISE TO ENABLE THE


FOLLOWING TO BE CHECKED:

o Simple breakdowns
o Random failures
o Operation disturbed by interference
o Partial or complete power supply failures
Consequently, after detection, the appropriate counter-measures must be undertaken such that:
o The incorrect data are not transmitted.
o No wrong instruction or adjustment can be operative.

WHENEVER THIS MAY BE EASILY DONE, SUCH CHECK MUST BE ABLE TO LOCATE THE
DEFECTS. HOWEVER, AT THIS PHASE, IT IS CONSIDERED MORE IMPORTANT TO DETECT
THE DEFECTS RATHER THAN TO LOCATE THEM.

The resumption of normal conditions of operation must initiate the checking of the condition of the components and signals,
and the sending there of to the Control Centre (overall checking of signals).

Any starting, whether automatically or manually performed, must cause a complete initialization of the system.

Finally, each RTU must be designed to incorporate a DUMMY BREAKER. This dummy breaker will be operated from the
control desk to check the operation of the remote control system.

1.8. DEFECTIVE OPERATION:

When a defect is detected, an appropriate signal must be sent to control centre's Control Room and possibly certain
functions may be inhibited:

o A breakdown of the remote control circuits must disable all of the remote control functions (unless, of course,
the failure affects only one output circuit);
o On the contrary, a failure of a dispensable component or printed circuit card must not disturb the proper
operation of the rest of the system.

1.9. POWER SUPPLY:

The RTUs will be supplied with a local 48 V DC source of which its voltage may vary between 42 and 58 volts.
(The positive pole of the DC power supply will be connected to the earth.)

1.10. EQUIPMENT ENCLOSURES:


72

All equipment are housed and will be enclosed in racks, preferably having the standard 19" size, in keeping with IEC
publication 297, with DUST PROOF LOCKABLE DOORS. Same identical locks are to be provided for all RTU cubicles.
Master keys for each RTU is to be supplied and this key should be able to open any RTU / Communication Equipment
Cubicle in Control Centre or in substations.

Ventilation and a cooling fan or fans in the cubicle must be foreseen by the supplier in order to maintain the RTUs in proper
operation by avoiding the increase of the temperature in the RTUs up to 55 oC and 100% humidity non condensation.

One extension plug in test board with plug will be provided with each RTU.

An internal lighting of the cubicles must be provided.

50 V DC and 240 V AC sockets to be provided in all cabinets, in addition to prominent labeling.

1.11. COMPONENTS:

In choosing materials and their finishes, a suitable regard is to be given to the humid tropical conditions under which
equipment is to work. Wherever possible the equipment must be hermetically closed and normal repairs carried out by
replacement of units or assemblies. Sealed units will be suitable for repair under controlled laboratory conditions. Tropical
grade materials will be used wherever possible.

1.11.1. METALS:

Iron and steel are in general to be painted or galvanized. Parts may alternatively have chromium or copper nickel plating
or other approved protective finish. Small iron and steel parts (other than stainless steel) of all the instruments and electrical
equipments, the cores of electromagnets and the metal parts of relays and mechanisms are to be treated in an approved
manner to prevent rusting. Cores, etc..., which are built up of laminations or not, for any other reason, be anti-rust treated,
are to have all the exposed parts thoroughly cleaned and heavily enameled, lacquered or compounded.

When it is necessary to use dissimilar metals in contacts, the contractor will have, if possible, to see to it that the potential
difference between them in the electrochemical series is not greater than 0.5 volt.

If this is not possible, the contact surfaces of one or both of the metals are to be electro-plated or otherwise finished in such
a manner that the potential difference is reduced within the required limits or, if practicable, the two metals are to be
insulated from each other by an approved insulating material or a coating of approved varnish compound.

1.11.2. SCREWS, NUTS, SPRINGS, PIVOTS, etc.:

The use of iron and steel is to be limited in the instruments and electrical relays wherever possible. Steel screws, when they
are used, are to be zinc, cadmium or chromium plated, or when the plating is not possible owing to the limitations of
tolerance, are to be corrosion-resisting steel. Instrument screws (except those forming part or a magnetic circuit) are to be
of brass or bronze. Springs are to be of non rusting material, e.g. phosphor bronze or nickel-silver, as far as possible. Pivots
and other parts of which non-ferrous material is unsuitable are to be of approved rust proof steel.

1.11.3. FABRICS, CORK, PAPER, etc.:

Fabrics, cork, paper and similar materials, which are not subsequently to be protected by impregnation, are to be adequately
treated with an approved fungicide. Sleeving and fabrics treated with linseed oil or linseed oil varnishes are not to be used.

1.11.4. PRINTED CIRCUIT BOARDS AND CIRCUITRY:

o The circuitry will be completely solid state.


73

o The printed circuit boards will be epoxy glass material.


o The components having a shelf life of less than 5 years are not to be used.
o The electrolytic capacitors having a shorter shelf life may be used provided they will reform themselves after
one hour in service.

1.11.5. WOOD:

The use of wood in equipment is to be avoided as far as possible. When the wood is used, woodwork is to be of thoroughly
seasoned teak or other approved wood which is resistant to fungal decay and is to be free from shakes and warp, sap and
wane, knots, faults and other blemishes. All woodwork is to be suitably treated to protect it against the ingress of moisture
and from the growth of fungus and termite attack, unless it is naturally resistant to those causes of deterioration. All joints
in woodwork are to be dovetailed or tongued and pinned as far as possible. Metal fittings used are to be of non-ferrous
material.

1.11.6. ADHESIVES:

Adhesives are to be especially selected to ensure the use of types which are impervious to moisture, resistant to mold
growth, and not subject to the ravages of insects. Synthetic resin cement only is to be used for joining wood. Casein cement
is not to be used.

1.11.7. CABLES:

Flame retardant cables shall be used for the connection of all equipment.

1.12. MAINTENANCE:

The equipment will be designed to reduce repair time to a minimum. This reduction may be achieved by:

o The standardisation of the components


o Easily supervised assemblies
o A simple and easy procedure for the location of the faults.

THE MANUFACTURER MUST INDICATE THE MODULARITY OF THE INPUT/OUTPUT CIRCUIT PLUG IN
CARDS HE INTENDS TO USE.

The methods to be used for the location of the faults and/or to facilitate the required adjustments during the various
maintenance phases will be included in the documents to be furnished before the installation of equipment.

Each RTU will be provided with a set of operation and maintenance instruction manual and actual wiring diagram.

2. SYSTEM OPERATING PROCEDURE:

2.1. GENERAL:

From the standpoint of the transmission of the messages, two types of procedures must be distinguished:

o CYCLIC TRANSMISSION (2 / 4 / 30 seconds for Power Stations / Z & W sub stations / Other stations cycle
for tele-metering and 15 minutes for the Energy Values Transmission for example)
o ARRHYTHMIC TRANSMISSION
which requires to be:
- on interrogation in case of general check.
74

- spontaneous (change of state and telesignaling)

2.2. PRIORITY:

The suppliers must adhere to the priorities for transmission of teleinformation for the RTUs and their satellites which must
in general be:

INFORMATION:

a. Services messages
b. Change of states, alarms and indications
c. General check of the states of the signals.
d. Filtered alarms
e. Set point values
f. Tele-measurements cycle

INSTRUCTIONS:

a. time synchronization signal.


b. Automatic Load Shedding.
c. Remote Control Instructions.
d. Set point values.

Commands should not be affected by information priorities as they are sent from the Control Centre and not from the
R.T.U.

2.3. DURATION OF TRANSMISSION:

The duration of transmission must be safe in the event of some abnormality or in the presence of a message having a higher
priority. A change of state of device must reach the control centre in a time less than THREE SECONDS in case of point
to point connection to Control Centre and less than FOUR SECONDS when it passes through data concentrator. (These
timings apply up to 5 simultaneous change of state from one R.T.U.)

2.4. REMOTE CONTROL:

2.4.1. VALIDITY OF THE CHECKING:

The remote control procedure must be designed such that in the event of failure on the Front End Sub-System, the control
command instruction must be blocked.

2.4.2. DURATION OF TRANSMISSION:

Unless there is an abnormality in the procedure and / or transmission, or the presence of a message with a higher priority,
the time between the execution of the control command order from the control centre operation desk and the closing of the
R.T.U terminal relay must be under 3 SECONDS.

2.5. SAFETY OF THE OPERATION:

The data message between the Front End Sub-system and the outstations must be checked.

o by the return information (back and forth procedure) or by checking the code complementary.
75

o and by any redundancy code ensuring adequate safety (hamming distance = 4 for telesignaling and
telemeasurements and a hamming distance = 6 for telecommands).

The probability of furnishing a wrong order or a wrong signal must be less than 10 -9. In the case of the tele-metering, a
degree of safety of about 10-7 will be permissible.

The proposed RTU should be supplied from one of the approved manufacturers/suppliers or a supplier achieving the
prequalification criteria as mentioned in document LIST OF APPROVED TELEMETRY EQUIP SUPPLIERS &
PREQUALIFICATION CRITERIA

If a new type of RTU - other than the RTUs approved and operational in MEWRE SCADA system in NCC/ECC/Jabriya
DCC/Shuaiba DCC/Town DCC/Jahra DCC - is proposed in the offer then for the sake of testing the modules a new Test
RTU should be supplied as well for testing the defective modules under this contract along with a set of spare parts

3. RTU MANAGEMENT SYSTEM:

The RTUs to be supplied under this tender should fulfil the following requirements for RTU Management
System:

1) NMS must be installed on-premises with no cloud dependencies


2) NMS software must support installation in RedHat Linux OS NMS or Windows Machine.
3) NMS must be capable of running in a VMware environment or Hypervisor environment with RedHat Linux OS or
Windows operating system.
4) NMS must support FCAS management of RTUs (Fault Management, Configuration, Administration, Security)
5) The centralized NMS must comply with relevant industry standards and regulations e.g. 62443-2-4
6) Communication between NMS and RTUs must be securely authenticated
7) Communication between NMS and RTUs must be encrypted
8) NMS must support role-based access to limit activities allowed by each user
9) Authentication method for Role-based access is configurable and can use either local profiles on NMS, or use
external Authentication server e.g. RADIUS
10) NMS must support a configurable password policy for user access
11) NMS must provide a dashboard providing a summary of RTU fleet (number of devices discovered, number of
devices reachable / offline)
12) NMS must support upload of the following data files to RTU: HMI (HMI library and UI projects), PLC packages.
13) NMS must provide ability for RTU configuration restore
14) if backup is available - provide the option to restore to the last available backup configuration (with a date of the
last backup displayed).
15) All security events on RTU must be logged and can be displayed in NMS
16) NMS must provide an audit trail with a log report of all activities performed, including name of user
4. RTU CYBERSECURITY:

4.1 The RTUs to be supplied under this tender should fulfil the following requirements:

S. No. Criteria
1 Vendor assess vulnerabilities and identifies security remediation for the products and services
provided according to the lifecycle product strategy of the software version
76

2 Vendor communicates vulnerabilities within a time period based on the nature and criticality
of the vulnerability according to Common Vulnerability Scoring and Common Vulnerabilities
and Exposure frameworks such as ISO/IEC 29147 and 30111
3 Local RTU access is restricted (password, PKI, certificate)
4 Remote RTU access is restricted (password, PKI, certificate)
5 RTU credentials and authentication methods can be changed and updated
6 User account management is in accordance to IEC62351-8
7 If certificates are used, they can be managed and revoked according to IEC62351-9
8 Exchange of credential and configuration data between RTU and any other system is
encrypted
9 RTU has different levels of access, with different and configurable privileges
10 RTU firmware is hashed and cannot be loaded on 3rd party devices
11 Data flow between RTU and any northbound system is encrypted according to IEC62351-3
and/or IEC62351-5
12 Configuration change and security events are logged
13 Traffic between RTU and external systems can be limited on IP address eg. With a firewall
14 Traffic between RTU and external systems can be limited logical port basis eg. With a
firewall
15 Firewall can separate traffic into zones
16 Certificates are protected by a hardware based secure chip
17 The development and engineering of the RTU is in accordance with IEC 62443 security
procedures
18 Vendor can provide cybersecurity certification (IEC62443, IEC62351 or equivalent) from an
independent party
77

4.2 The RTUs to be supplied under this tender should be equipped with a firewall having the following
specifications as a minimum:
1) Features:
1. The firewall should provide an application-centric, scalable and secure SD-WAN solution with next generation
firewall (NGFW).
2. Firewall must be capable of analyzing OT protocols such as: modbus, MMS, and others.
3. Protect against cyber threats and provide tight integration of the network to the new generation of security.
4. Interface: Multiple GE RJ45 and GE SFP slots.
5. Threat Protection: 580 Mbps.
6. NGFW: 950 Mbps.
7. IPS: 975 Mbps.
8. Firewall: 8 Gbps.

2) Security:
1. Identifies thousands of applications inside network traffic for deep inspection and granular policy enforcement.
2. Protects against malware, exploits, and malicious codes in both encrypted and non-encrypted traffic.
3. Prevents and detects against known attacks using continuous threat intelligence from AI-powered Lab’s
security services.
4. Proactively blocks unknown sophisticated attacks

3) Performance:
1. Engineered for Innovation using purpose-built security processors (SPU) to deliver the industry’s best threat
protection performance and ultra-low latency.
2. Provides industry-leading performance and protection for SSL encrypted traffic including the first firewall
vendor to provide TLS 1.3 deep inspection.

4) Certification:
1. Independently tested and validated best security effectiveness and performance.
2. Received unparalleled third-party certifications from NSS Labs, ICSA, Virus Bulletin, and AV Comparatives.

5) Networking:
1. Dynamic Path Selection over any WAN transport to provide better application experience based on self-healing
SD-WAN capabilities.
2. Advanced routing, Scalable VPN, multi-cast and IPV4/IPV6 forwarding powered by purpose-built network
processors.

6) Management:
1. SD-WAN Orchestration provides intuitive and simplified workflow for centralized management and
provisioning of business policies in a few easy clicks.
2. Expedited deployment with Zero touch provisioning well-suited for large and distributed infrastructure
3. Automated VPN tunnels for flexible hub-to-spoke and full-mesh deployment at scale to provide bandwidth
aggregation and encrypted WAN paths.
4. Predefined compliance checklists analyze the deployment and highlight best practices to improve the overall
security posture.

7) Security Fabric:
1. Enables Fabric-ready partners’ products to provide broader visibility, integrated end-to-end detection, threat
intelligence sharing, and automated remediation.
2. Automatically builds Network Topology visualizations which discover IoT devices and provide
complete visibility to Fabric-ready partner products.
78

Attachment 2

MPLS-TP Equipment

The Bidder offer should be fully compliant with tender conditions, specification, and providing
the requested technical proposal with clarifications and a compliance table for the following
specifications in this attachment paragraph by paragraph providing a snapshot and reference of
the items/paragraphs in the documents attached with their technical proposal to prove
compliance for each paragraph. Reference to full documents will not be acceptable. Any offer
not containing this table along with technical proposal and documents proving this compliance
will be excluded

1. DEFINITION OF THE SYSTEM


1.1. Main System requirement,

1.1.1 The proposed system platform must be based on MPLS-TP technology


The proposed system platform shall be a scalable product range usable for the aggregation and backbone
layer of the network and fitting to the utility substation environment of MEWRE. The proposed systems
shall be packet based with SDH interfaces for migration from SDH to MPL-TP as SDH is in phase out
mode.
1.1.2 The proposed system must support the transmission and migration of multi-services traffic of the existing
network. Therefore, the platform shall support the migration from SDH interface such as STM-16, STM-
4, STM-1, E1, C37.94 and it must support Ethernet interface such as FE, GE, 10GE, and it must support
the transmission of PCM interfaces (using external PDH equipment if needed) such as FXS/FXO, RS232,
RS422, X.21 and V.35, 2/4wire.
1.1.3 Support Hitless Protection Switching for Relay. The HPS scheme is based on the dual feed and selective
receiving mechanism. In the selective receiving direction, service caching and delay alignment are
performed to ensure that the end-to-end delay does not change after switching and no bit error occurs in
the service.
1.1.4 The MPLS-TP line rate should be at least 10G for access network and aggregation network, and hardware
ready/upgradable (with the same chassis by adding 100G line cards) to at least 100G smoothly at the
network backbone. The MPLS-TP should be the main and only core of the system while seamless
interworking with SDH is to be provided.
1.1.5 The proposed system based on MPLS-TP technology supporting 80KM to 150KM 10G and 1G
respectively without repeater. For extra long-haul repeater-less transmission between 150KM to 400KM
proposed system shall be interoperable with long-haul amplifier and boosters’ solutions wherever
needed.
1.1.6 The proposed system shall support resilience against multiple simultaneous failures at the backbone layer
of the network
1.1.7 The proposed equipment shall support non-blocking switching between any service slots.
79

1.1.8 The equipment shall provide the capability to encrypt MPLS-TP traffic (end-to-end tunnel encryption).
This encryption shall not increase latency/jitter in the network. Any proposed solution shall be
standardized and not proprietary.
1.2. The system shall comply with the latest relevant standards of ITU-T, IEEE and ETSI. The Declaration of
Conformity, which states that the bidding systems subject to the tender shall conform to the relevant
standards, shall be provided with the bid.

1.3. The system shall be able to interface and cooperate with the surveillance, control and information
collection (SCADA) system, Power Transmission Line protection signaling system and communication
devices (PAX, PLC) available.

1.4. The Mean Time Between Failure (MTBF) and Mean Time to Repair (MTTR) values for the cards and
units in the entire system shall be explicitly stated. Bidder shall explain in detail the calculation methods
related to MTBF and MTTR in the proposal.

1.5. Common alarm lamps shall be provided for each shelf. There shall be threshold alarms for physical
measurement (optical receive / transmission signal loss, bit error rates in reception direction, card failure,
etc.). These alarms should be expendable to alarm monitoring, recording and analysis devices of the
station via independent contacts.

1.6. The electronic cards in the system shall be removable and installable under energy.

1.7. If the -48 VDC voltages that feeds the system is interrupted and re-supplied, the system must be switched
on automatically without requiring any soft or hard start. Measures will be taken to ensure that the systems
are not damaged in the event of reverse feeds or short circuit conditions. How the systems are protected
against these situations shall be explained.

1.8. In case of interruption of the energy supplying the memories for any reason in the system, there should be
no software loss and system information should not be reloaded when power is supplied.

1.9. The bidding equipment must support IEEE 1588v2.


1.10. Temperature and EMC hardened
Especially important are the environmental conditions. The MPLS-TP systems for the substations for
the aggregation network layer shall be operable in an ambient temperature range of -5° to +55° C for
long term.
The MPLS-TP system shall be substation hardened and certified to the following standards:

Type tests
Electromagnetic compatibility
IEC 60870-2-1
IEC 61000–6–2, EN 61000–6–2
IEC 61000–6–4, EN 61000-6–4
IEC 61000–6–5
IEC 61850-3
80

IEEE 1613
Emission
CISPR32, EN 55032
Immunity
IEC 61000–4–2, EN 61000–4–2
IEC 61000–4–3, EN 61000–4–3
IEC 61000–4–4, EN 61000–4–4
IEC 61000–4–5, EN 61000–4–5
IEC 61000–4–6, EN 61000–4–6
IEC 61000–4–8, EN 61000–4–8
IEC 61000–4–16, EN 61000–4–16
IEC 61000–4–17, EN 61000–4–17
IEC 61000–4–18, EN 61000–4–18
Shock and vibration
IEC 60 721 –3–3, class 3M1
IEC 60 721 –3–2, class 2M1

Ambient conditions IEC 61850-3


Storage
Temperature range - 25°C … + 70°C
Humidity Max 95%, non-condensing
Transport
Temperature range - 25°C … + 70°C
Humidity Max 95%, non-condensing
Operation
Temperature range - 25°C … +55°C
Startup temperature - 25°C
Humidity Max 95%, non-condensing

2. MPLS-TP ADD / REMOVE MULTIPLEXER & OPTIC INTERFACE TECHNICAL


SPECIFICATIONS

The offered systems product range shall be modular and effectively operated as a terminal Multiplexer or add
/ drop Multiplexer configuration. The proposed systems shall support any topology (ring, link, mesh, tree,
star). For normal substations it shall have a packet switching capacity of 220G. For backbone stations the
system shall provide a switching capacity of up to 960G.
The new MPLS-TP systems shall be based Multiprotocol Label Switching-Transport Profile (MPLS-TP)
which is a variant of the MPLS protocol that is used in packet switched data networks. MPLS-TP is the product
of a joint Internet Engineering Task Force (IETF)/International Telecommunication Union
Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the
IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport
network for the following interfaces (Ethernet, Fast Ethernet, Gigabit Ethernet, VLAN, E1, STM-1/4/16)
2.1 Interface and its characteristics
- 100GbE
- 10 GbE Interface
81

- GbE (optical/electrical) Interface


- FE Interface
- FX Interface (using external PDH equipment if needed)
- E1 Interface
- Clear Channel: E1
For access nodes:
12x 10GbE NNI redundant interfaces should be provided with 8x 10GbE interfaces equipped with SFP+/XFP
modules (10GbE) sufficient for suitable distances to far end substations.
For aggregation nodes:
12x 10GbE NNI redundant interfaces should be provided with 12x 10GbE interfaces equipped with SFP+/XFP
modules (10GbE) sufficient for suitable distances to far end substations.
For backbone nodes:
16x 10GbE NNI redundant interfaces should be provided with 16x 10GbE interfaces equipped with SFP+/XFP
modules (10GbE) sufficient for suitable distances to far end substations.

2.2 The MPLS-TP system shall support TPS protection


Synchronization shall be supported from External clock 2MHz, 2MBit, Synchronization Ethernet (G.8261,
G.8262) • IEEE 1588v2.
All optical outputs shall have automatic laser cutting capability in case of open circuit. The Automatic Laser
Shutdown (ALS) feature shall comply with the relevant ITU-T recommendation.
2.3 The offered systems shall comply with the technical specifications and the ETSI, IEEE and ITU-T
recommendations in cases not specified here.
The MPLS-TP Equipment shall further be compliant to the following standards:
IEEE802.1D Media access control (MAC) bridges IEEE802.1Q Virtual bridged local area networks IEEE802.1ad
Provider bridges IEEE802.1ah Provider backbone bridges
IEEE802.3 Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer
specifications
ITU-T G.8113.2 OAM mechanisms for MPLS-TP networks using the tools defined for MPLS
RFC 4664 Framework for layer 2 virtual private networks (L2VPNs)
RFC 3811 Definitions of textual conventions for multiprotocol label switching (MPLS) management
RFC 3812 Multiprotocol label switching (MPLS) traffic engineering management information base
RFC 3813 Multiprotocol label switching (MPLS) label switching router (LSR) management information base
RFC 3032 MPLS label stack encoding RFC 3036 LDP specification RFC 3037 LDP applicability
RFC 3985 Pseudo wire emulation edge-to-edge (PWE3) architecture
RFC 4448 Encapsulation methods for transport of Ethernet over MPLS networks
RFC 4720 Pseudowire emulation edge-to-edge (PWE3) frame check sequence retention
RFC 4553 Structure-agnostic time division multiplexing (TDM) over packet (SAToP)
draft-ietf-pwe3-vccv-11 Pseudo wire virtual circuit connectivity verification (VCCV)
IEEE 802.1Q (Clause13)
The multiple spanning tree protocol (MSTP) RFC 0826 Ethernet address resolution protocol RFC 3046 DHCP
relay agent information option

RFC 3270 Multi-protocol label switching (MPLS) support of differentiated services


82

ITU-T G.8113.2 OAM mechanisms for MPLS-TP networks using the tools defined for MPLS
ITU-T G.703 Physical/electrical characteristics of hierarchical digital interfaces
ITU-T G.707 Network node interface for the synchronous digital hierarchy (SDH)
ITU-T G.841 Types and characteristics of SDH network protection architectures
ITU-T G.957 pOptical interfaces for devices and systems relating to the synchronous digital hierarchy

2.4 The MPLS-TP Systems shall be installed in cabinets and the the MPLS-TP system shall be substation
hardened and certified to the following standards:
EN 55022 : 2010/AC:2011 (Class A)
IEC 61000-4-2 : 2008
IEC 61000-4-3 : 2006+A1: 2007+A2: 2010
ETSI EN 300 386 V1.6.1 (2012-09)
IEC 61000-4-4 : 2012
IEC 61000-4-5 : 2014
IEC 61000-4-6 : 2013
IEC 61000-4-8 : 2009

The multiplex systems shall be based on MPLS-TP Technology and working on basic transmission rate
of 10 Gbps & 1 Gbps. Furthermore it shall allow migration from SDH with Circuit Emulation Service on
basis of un-channelized STM-1/4/16

The MPLS-TP Equipment provides multiplexing/switching functions on basis on packing switching


technology.

• The switching matrix shall allow for non-blocking Label switched path between the respective
interfaces.
• The Optical Power to be offered shall be such that under normal operating condition, the BER of
the system at the receiver is better than 1x10-10. Error performance versus the receive signal shall
be verified during the factory acceptance tests.

2.5 Scalability of MPLS solution


A lower scale and a higher scale version of the MPLS function shall be available.
The lower scale version shall support at least

• ≥ 15 x protected hierarchical VPLS networks in parallel in a 200 nodes MPLS network,


considering a backbone of 15 devices.
• ≥ 50 x protected point to point links with guaranteed switchover time < 50 ms
• ≥ 100 x protected point to point links with guaranteed switchover time < 500 ms
• ≥ 100 x protected point to point links with guaranteed switchover time < 1 s

The higher scale version shall support at least three times the resources of the lower scale version.

2.6 Equipment Protection


The equipment should support all the core units and System redundancy features as listed as follows:
• 1+1 hot backup protection for System control and communication
83

• 1+1 hot backup protection for Timing and Synchronization


• 1+1 hot backup protection for Cross-connection
• 1+1 hot backup protection for Power supply

Network-Level Protection
- SDH Link MSP liner protection or Similar based upon MPLS-TP protection schemes: 1:1 or
1+1 protection, bidirectional ≤50ms
- MC-MSP MSP liner protection or Similar based upon MPLS-TP protection schemes : 1:1
protection, bidirectional, ≤50ms
- LSP 1:1/1+1 LSP linear protection: 1:1/bidirectional, revertive/nonrevertive ≤50ms
- PW 1:1 PW linear protection: 1:1 bidirectional, revertive/nonrevertive ≤50ms
- LSP SNC/S LSP sub-net protection: 1:1 bidirectional, revertive/nonrevertive ≤50ms
- Dual-homing Network protection APS, command switch ≤200ms
- Link aggregation (inter and intra board, multi-chassis)
- UNI/NNI LAG 1:1 and UNI load sharing
- The laser shall automatically cut-off when the link is disturbed
- Interworking (Data and Management plane) with SDH installed base

2.7 Synchronization
The synchronization of the MPLS-TP Equipment shall be based on the following standards:
- ITU-T G. 783, G.811, G.812, G.813, G.823, G.826.
- The clock sources shall be from
- External Clock (input)
- Without service -2048kbit/s(G.703) -2048kHz(G.703)
- External Clock (output)
- Without service -2048kbit/s(G.703) -2048kHz (G.703)
- SDH Clock (input/output)
- With service -STM-1
- PDH Clock (input/output)
- With service -The first and second E1 interfaces
- Ethernet (input/output)
- With service -GE -10GE
- Synchronization Ethernet (G.8261)
- IEEE 1588v2 (TC, OC, BC, TC+OC, TC+BC)

The equipment shall automatically switch to another clock if the reference timing is lost and
automatically revert back upon restoration. The accuracy of the internal clock as well as the details of
the clock signal distribution shall also be stated in the offer.

The equipment shall be capable of diverting timing references between the STM-16/ 2 Mbit/s and a G.703
tributary interfaces.

2.8 Jitter/Wander:
84

The jitter and wander tolerance for MPLS-TP Systems shall be according to the following standards:
ITU-T G.813

2.9 Optical Budget Calculation


The Contractor shall submit the details of the power budget calculations stating the following (based
on 0.25 dB/km optical fibre attenuation at 1550 nm):
• Transmitter Power
• Minimum receive Signal @ BER 1x10-10
• Connector Loss
• Repair Splice Loss
• Power Penalty (Chromatic dispersion and LD reflection Loss)
• Maintenance Margin (> 2dB)
• Other Loss
• System Margin

The optical Budget Evaluation shall also contain an evaluation on the Link Dispersion considering the
used optical module

2.10 OAM Functions


The MPLS-TP equipment shall allow the following OAM options:
It shall provide multiple levels of OAM, such as service interface status monitoring, performance
testing, fault localization, and insulation. It shall ensure the high quality of carrier-class network
management and maintenance.
OAM standards supported in each level:
- RFC 5586 MPLS Generic Associate Channel
- RFC 5860 Requirements for OAM in MPLS Transport Network
- RFC 5880 Bidirectional Forwarding Detection (BFD)
- RFC 6371 Operations, Administration and Maintenance Framework for MPLS-Based Transport
Networks
- RFC 6426 MPLS On-Demand Connectivity Verification and Route Tracing
- RFC 6428 Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication
for the MPLS Transport Profile

The alarm functions shall include but not limited to:


• Alarms classified as critical, major, minor, and information.
• Indications of loss of incoming signal.
• Visual and audible indication of alarms.
• Test function of alarm indicators to ensure workability of alarm indicators.

Alarm functions shall be detailed by the Contractor, e.g. if implemented in Telecommunication


Network Management System.

2.11 Alarm related OAM:


- Continuity and Connectivity Check (CC): Used to check whether connections are normal. –
85

- Alarm Indication Signal (AIS): Used to send path failure signal in service layer to customer
layer.
- Remote Defect Indication (RDI): Used for near end to feedback a remote defect indication
signal to remote end when near end detect the failure.
- Loopback (LB): Used to open loopback of links, and MEP is the launching point of loopback
request packet. The execution point can be either MEP or MIP.
- Link Trace (LT): Link trace, can be realized by hop loopback.
- Lock (LCK): Lock function, used to inform a MEP that service has been stopped due to
management demand of relative service layer or sub layer. Then this MEP can judge whether
the service interruption is predictable or caused by faulty.
Performance related OAM
- Frame Loss Measurement (LM): Frame loss measurement, used to measure singledirection
drop ratio from one MEP to another MEP.
- Packet Delay Measurement (DM): Packet delay measurement, used to test the total packet
latency and jitter of one packet sent from MEP A to MEP B then sent back to MEP B
Other OAM
- Customer Signal Fail (CSF): Customer Signal Fail, used to transfer failure signal in customer
layer from source end of MPLS-TP link to its destination end.
- Throughput: Swallowing capability test, it can set the transmission rate of data packets, while
completing the measurement of packet loss and delay.
- Automatic Protection Switching (APS): Automatic protection switching signal complies with
ITU-T G.8131/G.8132 protocol, it sends APS frame to peer end device, then executes
protection switch action.

Test functions of the equipment shall include as a minimum:


• Transmit output
• Receive Sensitivity
• Frame Loss
• Packet Delay
• Protection switching
• Service telephone
• Alarms
• Supply Voltages
• Test loops

2.12 The Contractor shall give details of all other functions available on the equipment / [Link]
equipment shall have a proven record by submitting a reference list, that it has been installed and operated in
similar environment. The power supply voltage and range shall comply with the characteristics of the DC system,
the rated voltage being 48 Volt DC [Link] MPLS-TP systems for the substations shall be operable in an ambient
temperature range of -5° to +55° C for long term.

2.13 MPLS-TP main requirements:


1) IETF RFC 5921 (07/2010) A Framework for MPLS in Transport Networks
2) The equipment should comply with RFC5921.
3) The equipment shall support MPLS Pseudo-wire as per RFC3985.
86

5) The equipment shall support MPLS G-ACH as RFC5586.


6) The equipment shall comply with RFC5860.
7) The equipment shall comply with
RFC 3031 "Multiprotocol Label Switching Architecture "
RFC 3032 MPLS Label Stack Encoding
RFC 3270 Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
RFC 5462 Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
Class" Field
RFC 5960 MPLS Transport Profile Data Plane Architecture
RFC 7213 MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet Addressing
RFC 2685 Virtual Private Networks Identifier
RFC 3811 Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS)
Management
RFC 3812 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base
(MIB)
RFC 3813 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management
Information Base (MIB)
RFC 5601 Pseudowire (PW) Management Information Base (MIB)
RFC 5602 Pseudowire (PW) over MPLS PSN Management Information Base (MIB)
RFC 5603 Ethernet Pseudowire (PW) Management Information Base (MIB)
RFC 5718 An In-Band Data Communication Network For the MPLS Transport Profile
RFC 6370 MPLS Transport Profile (MPLS-TP) Identifiers
RFC 7331 Bidirectional Forwarding Detection (BFD) Management Information Base
RFC 6378 MPLS Transport Profile (MPLS-TP) Linear Protection
RFC 7324 Updates to MPLS Transport Profile Linear Protection

2.14 MPLS-TP OAM functions are required. All functions need to be applicable on network layer (PW/tunnel)
and per domain (end-to-end and tandem connection).
1) LSP End-to-End Monitoring must be supported.
2) MEP must be supported.
3) MIP must be supported.

RFC 5586 MPLS Generic Associated Channel


RFC 5860 Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport
Networks
RFC 5880 Bidirectional Forwarding Detection (BFD)
RFC 6426 MPLS On-Demand Connectivity Verification and Route Tracing
RFC 6428 Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS
Transport Profile
ITU-T G.8113.2 "Operations, administration and maintenance mechanisms for MPLS-TP networks using the
tools defined for MPLS"

2.15 Quality of service


Hardware support to ensure device internal and user traffic quality of service shall be provided.
• ≥ 8 hardware queues per physical port
• Configurable scheduling profiles
87

• Priority mapping tables (DSCP, PCP, EXP, PHB, TC)


• Priority configuration for individual protocols (e.g. PSC, MCC, …)
• Port and service based rate limiting (at least single rate two color marker (SR2CM))
• Configurable storm control for unicast, unknown unicast, multicast and broadcast per port
• Access Control List
• Flow Control

The MPLS-TP Equipment shall allow QoS classification on the following parameters
- L2: VLAN, PRI, MAC address, TPID
- CIR/EIR/CBS/EBS
- WRED
- 8 QoS classes
- Class-based queuing
- SP, SP+DWRR
- Color aware and color blind mode

2.16 Transport Ethernet Interface


Up to 8 x 10Gbit/s optical ports shall be available for Ethernet uplink purposes. The ports shall be available for
the synchronization source selection process and support synchronous Ethernet (Sync-E / ESMC) as well as
PTP.

1Gbit/s optical / electrical ports shall be available for Ethernet uplink purposes as well.

The uplink 1 Gbit/s and 10 Gbit/s uplink interfaces shall be upgradable to support MPLS-TP encapsulation.

2.17 Access Ethernet Interface


For MPLS-TP based networks the Ethernet L2 or IP L3 interface cards shall function as provider edge
(PE). L2/L3 shall also be possible via a Switch/Routing system. Ethernet/ IP modules or Switches and
Routers with the following functionalities shall be available.

Layer 2 Ethernet switching/ MPLS attachment service access interfaces.

• At least 12 ports per module


• Ethernet electrical connection: 10/100/1000BaseT
• Ethernet optical connection: 100Base-FX and 1000Base-LX/-SX/-EX/-ZX
• Support of VLAN tag stacking
• Protection by means of xSTP, ERPS or L2GP in case of MPLS based networks
• Port and VLAN based rate limiting
• Hard QoS (8 queues per physical port)
• Priority handling (PCP/ TC/ PHB/ EXP) shall be configurable
• Port based access (all traffic is mapped into MPLS-TP services)
• VLAN based access (separation of VLANs into different MPLS-TP services)
• Mix of port and VLAN based access and mapping into VPWS/ VPLS on the same physical port
• Configurable storm control for unicast, unknown unicast, multicast and broadcast per port
• Traffic policing/ rate limiting shall be supported
• Traffic type filtering shall be supported (multicast, broadcast, unicast)
88

• VLAN mapping shall be possible

Ethernet routing modules shall comply with the following specification.


Low capacity layer 3 routing interface card with access to TDM bus.

• At least 4 ports per module


• Ethernet connection: at least 10/100BaseT
• Routing Protocols: static IPv4 routing, OSPF2 v2, RIP v2
• WAN protocols: PPP, MLPPP
• WAN capacity: up to 16 x 2Mbit/s
• WAN ports: ≥ 30
• Redundancy: EQP (1:1 hardware protection) and VRRP
• Port based rate limiting
• Soft QoS (software queuing)
This functionality can be provided by an industrial managed rack switch.

High capacity layer 3 routing interface card with access to 1Gbit/s and 10Gbit/s backplane.

• At least 12 x FE/ GbE optical/ electrical SFP based front interfaces


• At least 16 x virtual routing functions (VRF/ VPRN)
• Wire speed forwarding on all ports (1GbE or 10GbE backplane access)
• At least IPv4 unicast routing (IPv6 ready)
• OSPFv2 (RFC 2328)/ static routing
• OSPF authentication (Simple/ MD5)
• VRRPv3 (RFC 5798)
• At least 1:1 NAT, one instance per VRF
• At least basic firewalling (ACL rules/ DoS protection/ port and VLAN based rate limiting)
• Layer 3 hardware supported QoS (DSCP/ 8 queues per physical port)
• SNMP MIBs (at least IF counters/ alarms)
• Maintenance features (Ping/ trace route)
• At least 128 x VLAN interfaces per module
• At least 128 x VRRP instances per module
• At least 32 x VRRP link tracking per module
• DHCP forwarding
This functionality can be provided by an industrial managed rack switch.

A module with Power over Ethernet shall be available to power e.g. camera, telephone set (Voice over
IP). MDI / MDIX shall be supported on electrical interfaces.

• At least 12 x PoE ports per module


• PoE and PoE+ standard. At least 2 x PoE+ with up to 30 W shall be supported per card. In case
end devices do not need the full PoE+ power capacity the remaining PoE capacity shall be shared
among all ports on the same module.
• At least 84 W of PoE power per module
This functionality can be provided by an industrial managed rack switch.
89

MPLS-TP Layer2 complies with the following specification:


• RFC 2702: Requirements for traffic engineering over MPLS
• RFC 3031: MPLS architecture
• RFC 3469: Framework for multi-protocol label switching (MPLS)-based recovery
• RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field •
Renamed to "Traffic Class" Field
• RFC 3811: Definitions of textual conventions for multiprotocol label switching (MPLS)
management
• RFC 3813: Multiprotocol label switching (MPLS) label switching router (LSR) management
information base
• RFC 3814: Multiprotocol label switching (MPLS) forwarding equivalence class to next hop label
forwarding entry (FEC-To-NHLFE) management information base
• RFC 4221: Multiprotocol label switching (MPLS) management overview
• RFC 4377: Operations and management (OAM) requirements for multi-protocol label switched
(MPLS) networks
• RFC 4378: A framework for multi-protocol label switching (MPLS) operations and management
(OAM)
• RFC 3032: MPLS label stack encoding
• RFC 3443: Time to live (TTL) processing in multi-protocol label switching (MPLS) networks
• RFC 4182: Removing a restriction on the use of MPLS explicit NULL
• RFC 3609: Tracing requirements for generic tunnels
• IETF RFC 3916: Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)
• IETF RFC 3985: Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
• IETF RFC 5085: Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control
Channel for Pseudowires
• IETF RFC 5254: Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)
• IETF RFC 4448: Encapsulation Methods for Transport of Ethernet over MPLS Networks
• RFC3916: Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)
• RFC3985: Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
• RFC4446: IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
• G.8113.1: Operations, Administration and Maintenance mechanism for MPLS-TP
networks([Link])
• RFC5860: Requirements for OAM in MPLS Transport Networks
• RFC6371: Operations, Administration, and Maintenance Framework for MPLS-Based Transport
Networks
• RFC6291: Guidelines for the Use of the "OAM" Acronym in the IETF
• RFC5586: MPLS Generic Associated Channel
• RFC6423: Using the Generic Associated Channel Label for Pseudowire in the MPLS
• RFC6427: MPLS Fault Management Operations, Administration, and Maintenance (OAM)
• RFC6435: MPLS Transport Profile Lock Instruct and Loopback Functions
• RFC6426: MPLS On-Demand Connectivity Verification and Route Tracing
• RFC6375: A Packet Loss and Delay Measurement Profile for MPLS-Based Transport
• RFC5718: An In-Band Data Communication Network For the MPLS Transport Profile
90

3. OPERATION AND MANAGEMENT SYSTEM (NMS) TECHNICAL SPECIFICATIONS


The network management system (NMS) shall have facilities to supervise, monitor, control and configure
each equipment and the whole network. It shall have capabilities of fault, configuration, performance and
security management. It shall provide various graphical views to the network such as geographical
overview, logical network structure, and hierarchical view. The network management system shall allow
to define different user profiles. Different views shall be possible for different users. The Network
Management System shall allow several users to access the NMS at the same time where changes become
visible to all users.

The NMS shall provide a Graphical User Interface with definable network displays (maps). Icons
symbolizing sub-networks, equipment and sections shall be available to be placed on a background image.
Drill down to display greater details down to equipment port level shall be possible. An online help shall
be integrated in the NMS.

The NMS shall provide a graphical shelf view of the devices. Currently installed and configured modules
in the network element shall be displayed. Current alarm and status information for the different modules
and ports shall be presented with dynamic coloring of the network element.

Security in the NMS shall be organized around domains, profiles, and users with defined privileges.
Profiles shall define access rights to different NMS functions (e.g. map view, alarm view). User privileges
shall be configurable to define user access rights for a defined number of functions.

The NMS shall have a graphical representation of the synchronization status of the network elements (for
TDM traffic as well as for SyncE).

Main/Standby functionality shall be supported by the NMS. In case of a failure of the main NMS, the
standby NMS shall take over. Replication of the databases shall be automatically performed.

NMS shall allow the operator to manage and monitor the entire network in an efficient way. The NMS
shall have the following functionality: network configuration, configuration of services, monitoring,
diagnostics, activation-deactivation of interface modules, bandwidth allocation, alarms and event logging
and graphical network representation.

The network management systems shall connect to the network elements via SNMPv3.
The connection of the NMS shall be organized via an in band communication network. This in band
communication channel shall be auto established between the different network nodes. This network shall
be based on standard routing protocols which have to be selected based on the scalability and converging
time when the network reconfigures after an extension or network element failure.
It must be possible to connect the NMS system to the network at any node via Ethernet.
Via the NMS, it shall be possible to configure the hardware modules that make up the network: nodes,
network cards, interface cards and optical transceivers. This shall be possible via drag and drop and
guidance to the operator in which slots certain hardware can be equipped.

Following service assurance tools must be present:


91

- Bit error test for E1, C37.94, OLS, Serial, CODIR with loopback possibility (network or line)
- Signal level test for 2/4Wire E&M interface
- MPLS-TP end-tp-end delay test for point-to-point tunnels
- Interface end-to-end delay test for E1, C37.94, OLS, Serial, CODIR, 2/4Wire E&M

The network management system should be able to manage third party devices in a similar way as the
MPLS-TP nodes:
− Devices should support SNMPv2 or SNMPv3 to monitor 3rd-party device
− An image of the managed device shall be displayed when creating the specific type of device in the
network management system
− It shall be possible to select the Ethernet ports that require management
− The 3rd party device shall be part of the network topology and links from the MPLS-TP nodes to the
device to be monitored
− Custom alarms must be configurable and displayed in the alarm list of the network management
system

The communication between the NMS and the MPLS-TP equipment shall be SNMP v3 based and
encrypted.

To guarantee delivery of correctly working ethernet services such as IEC104 or IEC61850, supplier is to
provide a recent MEF certificate for offered equipment which is preferably MEF3.0 level for E-LINE,
E-LAN and E-TREE; This certificate should be valid for ethernet services running OVER an MPLS-TP
network. MEF certificates for native carrier ethernet services are not relevant and will not be accepted.

The NMS for new MPLS-TP equipment shall also be able to manage all existing SDH Equipment in the
network. It shall be possible for end-to-end service management between the new MPLS-TP equipment and
the SDH installed base. Protection mechanisms such as E1 VPAPS and dual homing E1 SNCP between the
new MPLS-TP equipment and the SDH installed base shall be managed in the NMS system.

The NMS system to be offered shall at least provide the following services.
• NMS access shall be provided to newly installed MPLS-TP systems which are connected to each other
by fiber line for monitoring and supervision.
• The SDH installed base shall be managed as well, to have end-to-end network management capability
• The system shall comply with the recommendation ITU-T G.784.
• NEs and connections shall be displayed on the topology.
• NEs added to the network shall be detected by NMS and automatically displayed in topology.
• To display different states of NEs and subnets, alarms in the topology view shall be displayed as
different colors or symbols.
• NEs on the network shall have the test feature to detect connection errors.
• It shall generate appropriate alarms by monitoring the performance of the circuits.
• Alarms may be listed. Each alarm shall have a defined alarm type category.
• Graphic display shall be available and the alarm status shall be monitored via graphic display.
92

• All alarms shall be recalled from memory when it is necessary to keep them on the platform for at least
6 months. When requested, date and time records shall be exported.
• The fault location on the network shall be detected.
• When the fault is rectified, it shall return to the normal operating position.
• In normal and faulty conditions, the performance shall be supervised, faults shall be monitored,
processed, recorded, error files shall be created and graphic imaging shall be performed.
• Network configurations shall be defined in the system, software for the network elements that can be
changed shall be installed remotely.
• System configurations shall be able available, stored, copied and reloaded.
• Authorization shall be performed on different user levels and unauthorized access to the system shall
be blocked.
• Software upgrade shall be possible during the application phase.
• Systems shall be locally controlled on the station where they are located.
• Configuration change and testing shall be able to be done from center.
• Failures shall be reported.
• All activities at the system level must be recorded with a tracking record linked to the user name. A
detailed Event Log shall allow for the follow-up of all operations performed on the system by different
users / processes.

The NMS shall allow to display in one view the existing SDH network elements and the new MPLS-TP
network elements

A comprehensive alarm management shall show current alarms such, that icons of the network elements
change their colours according to the alarm level. The alarms shall be categorised as critical, major, minor
alarms and of the warnings and a summary shall indicate the total number of them in the entire network.
An alarm list shall list all alarms of the entire network according to the time of their occurrence. It shall
be possible to filter alarms with various filter criteria. Operators shall be able to add comments to the
alarms. It shall be possible to integrate foreign objects such that their alarms are integrated into the alarm-
list, that they can be made visible as icons in the NMS views and that the icons change colours according
to the Alarm State.

The new fiber optic telecommunication system nodes shall be integrated into the existing management
system and these nodes shall allow the direct intercommunication with existing telecommunication nodes
via OSPF routing protocol. Furthermore the new telecommunication system nodes shall support
interworking with existing nodes via STM-16 interface and shall also support GFP/LCAS- and Ethernet
Layer 2 functionalities like 802.1q/p/s/w/x/ad between new and existing nodes.

Every Network Element shall have a built-in Signal Generator and Analyzer to analyze communication
paths. It must be possible to cross connect the Generator and Analyzer to transmission channels and
terminate the signal in other Network Elements. The configuration must be possible locally with the craft
access terminal and remotely with the TMS or the craft access terminal. It must be possible to loop-back
signals locally and remotely using the craft access terminal or the NMS.

4. Craft Access Terminal


93

The craft access terminal shall allow to connect to all Network Elements in the communications network
using the TCP / IP protocol so that the craft access terminal can be connected to any point of the corporate
network. The craft access terminal shall support configuration, maintenance, and status information. It
shall provide a windows oriented user interface.
94

Attachment 3

POWER SUPPLY EQUIPMENT (48V DC System)

GENERAL:

Under this contract the contractor is required to supply, install and commission power supplies for the substations
for their monitoring and control as well as for the telephony. Further any provision of equipment as a result of
such monitoring the autonomy of the batteries in intermediate sub stations and in the respective Control Centers
are to be checked and if need arises for any replacement the same is to be included in this contract after fully
utilizing the available spare capacity. The contractor is allowed to make use of all the existing power supplies in
the intermediate sub stations and in the Control Centers. All the necessary provisions for the charger room and
battery room such as availability of MCBs in the main Low Tension board, distribution boards, cabling, all civil
works such as making new holes and covering & sealing of unused abandoned holes etc. are to be coordinated
with the main switchgear contractor who will build the sub station. All changes necessary additions / alterations
needed for reusing the existing equipment are to be foreseen and included in the offered price. All works that
are needed are to be foreseen and provided in addition to any other alterations needed under this contract.

The rating/capacity for the Charger and Battery set for the new substation/s mentioned in the price schedules is
tentative and provisional and subject to MEW approval at the design stage after submittal of all required
calculations considering 30% spare capacity and if higher rating / capacity was found by MEWRE to be needed
then is should be supplied.

The supervisory control equipment of the Control Centre and those of the Substations will be fed without cut
irrespective of the conditions of supply of the alternating current main or diesel supply and they must be totally
free of micro-cuts and interference.

The CONTROL CENTRE is provided with a supply system that feeds no-cut alternating current (2 nos.) to the
existing main computers and to front end computers (except for Jahra DCC where 2 separate UPS is provided
for the Main Servers and Front Ends) with their peripheral equipment and is to be used for supplying the needed
power for the newly supplied equipment under this contract. All changes necessary in the main Low-Tension
board, distribution boards, cabling, all civil works such as making new holes and covering & sealing of unused
abandoned holes etc. are to be foreseen and provided in addition to any other alterations needed for re-using the
existing equipment. In case if the system autonomy conditions of 10 hours for NCC & Jabriya DCC and 8
hours for Shuaiba DCC, Jahra DCC and Town DCC are not met then new UPS system is to be proposed
replacing the existing one and its cost included in the offer.

The Centre is also equipped with a "rectifier-battery" set, this set being, in the normal case, supplied with
alternating current from the electrical network of MEW, or Diesel Generator. This supplies direct current, at the
nominal voltage of 48V DC for the existing telecommunication equipment and mimic board of DCC. All
changes necessary in the main Low-Tension board, distribution boards, cabling, all civil works such as making
new holes and covering & sealing of unused abandoned holes etc. are to be foreseen and provided in addition to
any other alterations needed for re-using the existing equipment. In case if the system autonomy conditions of
10 hours for Jabriya DCC (NCC) and 8 hours for Shuaiba DCC, Jahra DCC and Town DCC are not met
95

then new power supply system is to be proposed replacing the existing one and its cost included in the
offer.

A separate rectifier-battery set exists for the telephony equipment in CC, this set, being in the normal case, fed
by alternating current from the MEW electrical network or Diesel Generator. In case if the system autonomy
conditions of 24 hours are not met then new power supply system is to be proposed replacing the existing
one and its cost included in the offer.

However, in the event of prolonged failure of the alternating current system, a quick-starting standby diesel
generator system is provided as well.

For the Substations, the requirements are limited to one local supply source of direct current to feed the tele-
communications, telephony and outstation teleinformation equipment, etc., and also to furnish the Tele-
communication polarity for indications, alarms and remote controls.

Generally, as regards the batteries in NCC/DCC and the substations, the necessary autonomy for the
control functions is of 10 hours for Jabriya DCC / NCC & 8 hours for Shuaiba, Jahra & Town DCCs
except for the telephony system, which is 24 hours for all.

The tenderers will take into consideration the environmental conditions of temperature and humidity for the
proposed equipment as mentioned in specific conditions.

Flame retardant cables will be used for the connections of all components in CC and substations whether as a
new supply or part of replacement of existing ones utilizing the existing equipment.

Further, the heat dissipation, air changes etc., are to be considered for the newly supplied equipment including
the ones replacing the old existing equipment allowed to be utilized but not used due to any reason and
accordingly the changes or replacements, if any, are to be made and their cost included in the offer.

DIRECT CURRENT SUPPLY FOR THE SUBSTATIONS:

1. GENERAL CHARACTERISTICS:

Each battery will consist of 24 accumulator cells of Lead-Acid "semi-fixed" or "compact stationary"
type. The autonomy of each battery set will be of 10 hours for Jabriya DCC / NCC substations &
8 hours for Shuaiba, Jahra & Town DCCs substations.
Each battery will mandatorily be operated in the floating battery mode to eliminate entirely, even in a
transient period, any over voltage, which might damage the supplied transistorized equipment. A
charger will be installed, which will supply a maximum voltage of 58 V, and in no event any higher
voltage even during an extremely short time interval is allowed.

2. CONDITIONS OF OPERATION:

The charging device must perform the following functions:


96

2.1. Normal operation as floating battery:

it must supply a constant voltage to the following:

- battery topping-up current

- current absorbed by user

Both charger and battery will furnish the current peaks exceeding the charger peak load.

2.2. Failure of A.C. supply:

The battery will supply the power absorbed by the user only.

2.3. Return of A.C. supply:

There are two possibilities:

Duration of failure less than 5 minutes:

The rectifier will resume its previous operating mode i.e. floating battery mode or boost charge mode.

Duration of failure over 5 minutes:

The rectifier will operate automatically at the boost charge rate during 12 hours (adjustable between 0
and 24 hours); then will automatically return to its floating battery operating mode. No manual switch
will be required to pass over to boost charge.

2.4. Manual Adjustment:

A manually controlled adjusting device will be required to perform the following operations:

o In the event of failure of the voltage regulating device, there will be the possibility of using the
charger by manually regulating the voltage to between 46 and 54 V at an amperage of between
0 and I nominal, at an A.C. supply voltage of between + 10% of its rated value.

The switch to change over to manual will be located inside the rectifier to prevent its being accessible
to unauthorized persons.

3. ELECTRICAL CHARACTERISTICS:

3.1. A.C. supply voltage:

The nominal A.C. supply voltage has the following characteristics:


97

- 415 V, 3 phases, 50 Hz
- Fluctuation limits of nominal voltage: +10%
- Fluctuation limits of frequency: +2 %-8%.

3.2. Floating battery and boost voltages:

The rated floating battery voltage is 53.5 V


The rated boost voltage is 57.6 V

3.3. Rated power:

The rated power will be equal to the product of the rated boost voltage by the rated rectified amperage.

THIS VALUE WHICH DETERMINES THE DIMENSIONING OF THE CHARGER MUST


BE SPECIFIED BY THE TENDERER COMPATIBLE WITH THE PROPER
MAINTENANCE OF BATTERIES AND CONSUMPTION OF THE VARIOUS ITEMS OF
EQUIPMENT FED i.e. THE NEW EQUIPMENT SUPPLIED UNDER THIS CONTRACT
PLUS THE CONSUMPTION OF EXISTING EQUIPMENT WHICH WILL REMAIN
CONNECTED FOR CC, PLUS THE CONSUMPTION OF EXISTING EQUIPMENT
ALLOWED TO BE USED BY MEW AS INDICATED IN DIFFERENT CHAPTERS PLUS
AN EXTRA RESERVE OF 30%.

In general, the rated amperage of each charger will be equal to the maximum using amperage.

3.4. Filtering:

Each charger has a filtering device. With the charger supplying a purely resistive charge, the r.m.s.
A.C. values measured at the resistor terminals are less than 300 mV at 50 Hz and less than 10 mV
between 300 and 3000 Hz. The charger will however be always connected to the battery, that is it will
never feed the load directly.

3.5. Risk of Over voltage:

To prevent any over voltage, it will in all the cases be made impossible for the charger to operate
directly on the user load.

3.6. Supervision of the Voltage of the Battery:

A relay connected down line of the user output protection will be incorporated in the charger to give
the necessary alarms in case of over voltage, under voltage and trips for over voltage.

3.7. Earthing of positive pole of user system:

In the distribution cabinet of the user outputs, 1 bolted strip to earth the positive pole at a single point.
98

3.8. Signals and Alarms:

All the defects and failures must cause the lighting of lamps and the closing of one single loop on the
alarm circuit. A drop of A.C. voltage during system disturbances must not be deemed as a charger
defect and will not cause an alarm. However, loss of A.C. supply to the charger is to be signalled as
an alarm.

3.9. Protection and operation instrument:

Whatever its capacity the chargers will mandatorily be provided with a contactor on the A.C. side to
enable it to be automatically de-energized in addition to an MCB or contactor on the A.C. Distribution
board of the substation.

On the DC. side the charger will be supplied with 2 magnetic switches or 1 two pole circuit breaker to
ensure selectivity of the switching and with an adequate cutting capacity.
All the auxiliary circuits inside of charger will have miniature circuit breakers.

4. DC DISTRIBUTION:

All the necessary DC distribution boards and cabling are provided and connected to the existing
equipment. For new equipment if any changes, replacement or additions to them are required then they
are to be provided by the tenderer according to his needs.

5. TECHNOLOGY:

5.1. PRESENTATION:

Each equipment will be designed in the form of free standing cubicle or wall cabinet with adequate
measures to fulfill the environmental conditions and protection class defined elsewhere.

All the connecting terminals, controls and switches and test points will be readily accessible and
clearly identifiable.

Screwed name plates will be installed on every cabinet.

All cables will be labeled with engraved cable identifiers and all wires are labeled with stenciled plastic
markers.

5.2. MAINTENANCE:

Each equipment will incorporate test points allowing for the complete checking of the proper
operation, trouble-shooting and repair.
99

Such test points will be clearly visible on the typical schematic. The adjusting and maintenance
instructions will specify the signal values and wave forms which must normally be found and
maintenance manual must be accompanying each set of equipment.

Normal tools and measuring devices will be supplied with each power unit of CC and substations.

5.3. BATTERIES:

All the batteries must be lead-acid type, vented type with separate 2V / cell, housed in clear translucent
containers, with marking of maximum and minimum fluid level and marks of polarity. The battery
plug will be spark proof.

All the batteries are to be placed on stands.

All Batteries are to be provided with name plates indicating the type, capacity etc. and their
maintenance and operational procedures.

6. USE OF EXISTING EQUIPMENT

The tenderer is allowed to make use of the existing charger, batteries, inverters, dc. distribution boards,
fuse boxes and the cabling to them for the NCC/DCC and sub stations.

The Tenderer has to include all necessary modifications or supply of new equipment / material
necessary to make use of the existing equipment, cabling, fuse / MCB rating etc. compatible with their
system and equipment.

In case if the equipment as indicated to be utilized is inadequate in capacity or quantity the


tenderer has to include in his offer supply of additional equipment / material or replacing the
equipment allowed for use and their cost included in his offer. Such unused equipment / material
is to be removed from the site and properly packed and handed over to MEW stores and the
tenderer has to make provision in his offer for the same.
100

Attachment 4

Optical Distribution Frame (ODF)

Wall mounted:

• Two doors, a lock with two areas, one for patching with patch cord entry/ exit and one for splicing
with fiber optic cable entry.
• Have Patch cord guides for routing the patch cords properly and provide sufficient space for storing
multi-fiber loose tube reserves under the splice cassette.
• Low-loss connectors/adapters (< 0.3 dB) including the loss in bulk head, loss in the connector splice
and the loss in the pigtail.
• Capacity: 48 fibers.
• All spare fibres shall be properly terminated and spliced on connectors of the same type within the
frame.
• Connectors/adapters shall be FC/PC or SC/PC simplex.
• Have Pigtails for G655 fibers. Fibers numbering stickers should be included.
• Material: steel or aluminum.
• Rated to IP54.
• Fully-loaded with all required parts for installation & cable splicing.
• Operable in an ambient temperature range of -6° to +55°

Rack Mounted:

• Standard 19-inch structure.


• Adaptors on front panel.
• Modularity in design with firm structure.
• Material: Cold Rolled Steel or Aluminum
• corrosion resistant.
• Have Patch cord guides for routing the patch cords properly and provide sufficient space for storing
multi-fiber loose tube reserves under the splice cassette.
• Low-loss connectors/adapters (< 0.3 dB) including the loss in bulk head, loss in the connector splice
and the loss in the pigtail.
• Capacity: 48 fibers.
• All spare fibres shall be properly terminated and spliced on connectors of the same type within the
frame.
• Connectors/adapters shall be FC/PC or SC/PC simplex.
• 48 optical splices in 4 trays.
• Pigtails for G655 fibers.
• Fibers numbering stickers should be included.
• Fully-loaded with all required parts for installation & cable splicing.
• Operable in an ambient temperature range of -6° to +55°.
101

Attachment 5

ENGINEERING, DRAWINGS AND DOCUMENTS:

1 -SURVEYS AND ENGINEERING:

The engineering necessary for the completion of the entire system will be performed by the Contractor
upon the coming in force of the contract, and will include:

- The co-ordination of surveys,


- Engineering and construction schedules
- The preparation of general principles (characteristics, standards, specifications concerning the
equipment to be supplied, and some specific customer's equipment and supply),
- The final preparation of the tele-information plan and telecommunication system connected with
existing telecommunication channels or channels to be created, in co-operation with MEW
- Explanatory diagrams of connection in control centre and sub stations,
- Particular specifications concerning equipment included in the supply,
- Detailed specifications and functions of proposed software,
- List of corresponding equipment,
- Connection diagram between equipment included in the supply,
- Receipt of various pieces of equipment from the suppliers,
- Erection instructions and specifications for the setting in of the equipment,
- Checking of civil engineering works, in particular detailed construction / work plans

2. DESIGNS AND DRAWINGS & TECHNICAL DOCUMENTS:

All submissions, drawings, technical documents etc. have to be submitted to Kuwait standards
Approval:

The Contractor shall provide within the time limit fixed in the Contract, technical literature pertaining
to erection, operation & maintenance of all equipment, sketches and plans which appear on a list to be
prepared beforehand. These documents shall be supplied in 3 sets for approval along with a soft copy
before manufacturing or start of erection.

The Contractor shall submit to the Engineer for approval during the progress of the work and within a
reasonable time such drawings and any other technical literature of the equipment, which he intends to
supply, connected with this Contract for approval. Copies of all drawings, and technical literature,
which require approval, shall be provided to MEW by the Contractor, and shall consist of 3 sets along
with a soft copy. One copy will be returned to the contractor duly approved.

The Contractor shall be responsible for all errors and omissions in the drawings and plans, whether or
not these drawings and plans have been approved by MEW Ministry of Electricity & Water's. Approval
of these documents in no way releases the Contractor from his responsibility. In the event, after the
approval of the final drawings, it is deemed necessary to effect modifications thereto, the Contractor
103

Attachment 6

DIGITAL INTERTRIP EQUIPMENT

The Bidder offer should be fully compliant with tender conditions, specification, and providing
the requested technical proposal with clarifications and a compliance table for the following
specifications in this attachment paragraph by paragraph providing a snapshot and reference of
the items/paragraphs in the documents attached with their technical proposal to prove
compliance for each paragraph. Reference to full documents will not be acceptable. Any offer
not containing this table along with technical proposal and documents proving this compliance
will be excluded

Applications:
The intertrip equipment should cover three types of application:
* Operation of the “permissive” type which favours reliability.
* Operation of the “blocking” type which favours transfer time.
* Operation of the “direct tripping” type which favours security.
Each command in a given system is independent and can therefore be customized.

Architecture:
− Modular design
− Redundant power supply
− Digital Line Interface (G703.6 (E1).
− Ethernet Line Interface (electrical interface (10/100Base-TX).
− Optical Line Interface (for multimode and single mode fibers with SFPs for 850 nm,
1310 nm, 1550 nm (IEEE C37.94)
− Protection Interface (Electrically isolated contact type command input/output circuits,
GOOSE type with up to 8 GOOSE messages according to IEC 61850-8-1)
− Management Interface.

Features:
− up to 8 independent commands in digital/optical/ethernet interfaces in any combination
with each command configurable for blocking, permissibe or direct tripping.
− Adaptive signal processing for shortest transfer times.
− Continuous channel supervision with alarm if channel is unavailable or has insufficient
quality.
− Inegrated event recorder and trip counters.
− Event and Alarm Logging, synchronized with IRIG-B, 1PPS or NTP/SNTP.
− SNMP Network Management System compatability.
104

− Ready against cyber/IT secur


− A serial / ethernet port for programming and monitoring through PC the local and
remote statations
− For maintenance: Manual Loop Test, Automatic Loop Test, Delay Measurement
− Advanced Communication protocols to ensure reliable trafer of commands.
− Power Supply immunity to withstand impulse and transients of tp to 10,000 V
− Hight quality realys able to withstand voltage of 10KV between coil and contacts.
− Optoisolated Command Inputs.
− Optoisolated Relay Outputs.
− Error Detection and Coding (Link Loss Detection, LOS Detection, Line Code Violation
Detection)
− Burst inteference with significantly greater amplitudes than the wanted siganls is
largely suppressed.
− Noise Aanalysis in the unused wanted signal circuits.
− Power supply with short circuit protection and reverse power input protection

Climatic conditions:
Operating Temperature: -10C to + 55C
Maximum Relative humidity: 95% at 40C as per IEC 60068-2-3
Storage Temperature: -25C to + 70C

Compliance with IEC Recommendations:


IEC 60834-1,
IEC 61000-4-1/2/3/4/5/6/8/12/16,
IEC 870-2-1
IEC 60068-2-1/2//6/14/29/30/78

Common questions

Powered by AI

MPLS-TP technology is critical for integrating new substations with existing networks through the provision of multiplexing and switching functions. It allows for non-blocking Label Switched Paths and migration from SDH with Circuit Emulation Service. It must comply with several technical standards, including ITU-T G.8113.2 for OAM, IETF RFC 5921 for MPLS frameworks, and others such as RFC 3985, 5660, and 3031 for architecture and management . The MPLS-TP systems must be operable in extreme temperature ranges and ensure quality of service through hardware support for internal and user traffic .

The equipment must be operable in an ambient temperature range of -6°C to +55°C within buildings and withstand continuous operation at 85°C due to sun radiation for outdoor units. It must be dust-proof and handle 100% relative humidity. For storage, equipment should tolerate temperatures up to 85°C without damage . MPLS-TP systems must also be compatible with varying temperature conditions specified in environmental standards .

Contractors are expected to ensure that all telemetry equipment supplied is fully compliant with tender conditions and specifications and maintain them for a minimum guarantee period of three years if the contractor is not the manufacturer. The contractor must also ensure lifelong licenses for equipment reliability and maintainability. Additionally, they must confirm the supply of subsets, modules, and spare parts for up to 20 years after final acceptance . All works executed under the contract must align with MEWRE and international standards .

The telemetry equipment must be supplied by a manufacturer fully compliant with MEWRE specifications and requirements. The proposed manufacturer is subject to final approval by MEWRE after the contract signing, and MEWRE reserves the right to study and potentially disapprove a nominated manufacturer at any point, requiring the contractor to nominate another for approval. The equipment must be fully compliant with the specifications detailed in several attachments, including RTU, MPLS-TP, and others . All equipment must also include lifelong licenses for availability, reliability, and maintainability .

MEWRE ensures quality and compliance by requiring that all materials used meet international standards such as IEC, BSS, IEEE, and ITU-T . The bidder must allow for approvals from local authorities and ensure works conform to international safety standards. Furthermore, compliance is validated through a structured proposal that includes a compliance table referencing MEWRE's specifications for RTU, MPLS-TP, and other equipment. The telemetry equipment must withstand temperature variations and maintain specified performance levels such as achieving an optical power that ensures a BER better than 1x10-10 .

The document ensures scalability by specifying that the MPLS system must support a range of protected network configurations, such as VPLS networks and point-to-point links with established switchover times. It must offer lower and higher scale versions to accommodate growth. The systems should be substation-hardened and certified against standards to operate in harsh conditions, ensuring long-term operability. The equipment must also comply with several RFC standards for management and operations .

The new substations require integration through dual data routes and a telephone route to SHUB and JABR DCC using 10 G MPLS-TP links. This routing must support integration into existing SDH/MPLS-TP backbones. Protocols such as IEC 6087-5-104 for SCADA/EMS integration are used, and the routes must be approved by MEWRE. Equipment proposed must support a range of IETF RFCs like 3031, 3985, 5085, and standards for pseudo-wire emulation and transport profile .

MPLS-TP systems must provide at least 8 hardware queues per physical interface to ensure quality of service. These queues help manage and prioritize data traffic effectively, complying with standards like RFC 3031, 3032, and others for managing MPLS operations. Supporting standards include RFC 5860 for OAM and RFC 6371 for the OAM framework .

Integration requires software modifications for computer systems, network management system incorporation, and connection to MEWRE IP Telephone System. Using protocols like IEC 6087-5-104, new substations are integrated into existing SCADA/EMS systems at control centers. MPLS-TP network supports routing and transmission needed for data integration into SDH/MPLS-TP infrastructures .

Compliance is established through a detailed proposal that includes a compliance table checking each aspect of the submitted telemetry system against MEWRE's specifications in attachments. Suppliers must provide paragraph-by-paragraph references within their technical proposal, ensuring proof of compliance without referencing entire documents. Non-compliant bids are excluded. Lifelong licenses for key components are required to ensure system reliability and compliance over the contract period .

You might also like