TELECOMMUNICATION INFRASTRUCTURE COMPANY

TECHNICAL SPECIFICATIONS
of
NG-SDH & DWDM Equipment

For
I.R.IRAN'S National Backbone Project
of th Five Years Plan




Planning and Engineering Affairs
December

II
Table of Contents
Contents Page
) General Conditions....
-) Introduction................................................................................................................
-) Scope of Work
...........................................................................................................
-) General Tender Conditions........................................................................................
-) Response Format........................................................................................................
-) Equipment
Requirements.......
) Network.........................................................................................................................
-) Introduction..............................................................................................
-) Transmission....
.) Synchronization............................................................................................
-) Protection
.................................................................................................................
-) DCN Management
Network.....................................................................................
) NG-SDH Technical
Specifications...............................................................................
-) General Considerations............................................................................................
-) Operating Modes .....................................................................................................
-) Network Topologies ................................................................................................
-) System Transmission Capacity ...............................................................................
-) Electrical
Interfaces..................................................................................................
-) Order
Wire....................................................................................................
-) Optical Interfaces.....................................................................................................
-) Optical Amplifier.....................................................................................................
-) Optical Attenuator....................................................................................................
-) Dispersion
Compensation.......................................................................................

III
-) Optical Patch cord and
Pigtail................................................................................
-) Data
Interfaces........................................................................................................
-) Ethernet Topologies...............................................................................................
-)
Synchronization......................................................................................................
-) System
Protection...................................................................................................
Table of Contents
Contents Page
-) Network Protection and Restoration......................................................................
-) System Management .............................................................................................
-)
Safety..............................................................................................
) DWDM Technical
Specifications.................................................................................
-) General Considerations............................................................................................
-) System
Applications.....................................................................................
--) Optical Terminal (De)Multiplexer Equipment.......
--) Optical Add/Drop Multiplexer Equipment.............
--) Optical Amplifier
Equipment..............................
--) Regenerative
Terminal............................................
-) Equipment Safety.........................................................................................
-) Network Topology.......................................................................................
-) Additional Requirements.........................................................................................
--) Optical Supervisory Channel .................................
--) Order Wire Channel...............................................
-) System Components Characteristics........................................................................
--) TX / RX Transponder.............................................

IV
--) Optical
(De)Multiplexer..........................................
--) Optical Add / Drop
Multiplexer..............................
--) Optical Amplifire................................................
--) Optical
Attenuator...............................................
--) Gain Flattening
Filter..............................................
--) Optical
Isolator........................................................
--) Chromatic Dispersion Compensator.......................
--) Polarization Mode Dispersion Compensator.........
--) Optical Connector.................................................
--) Optical
Termination..............................................
-) Power Consumption.....................................................................................
Table of Contents
Contents Page
-) System Management........................................................................................
--) Configuration Management............................................................................
--) Fault
management...........................................................................................
--) Security Management.....................................................................................
--) Alarm
Management.........................................................................................
--) Performance Management..............................................................................
--) System Management Interface......................................................................
-) System Interfaces.....................................................................................
--) Optical Interfaces............................................................................................
--) Elecrical
Interfaces..........................................................................................
-) Safety
Requirements.......................................................................................

V
--) Elecrical Safety............................................................................................
--) Optical
Safety...............................................................................................
-) System Technical
Specifications...........................................................................
) Network Synchronization
Equipments.......................................................................
-) Introduction..
-)
Synchronization
--) Primary Reference Source.............................................................................
---) Requierment Definition....................................................................
---) Requirement Specification...............................................................
---) System
Characteristics......................................................................
---) Functional Characteristics................................................................
---) Physical
Characteristics....................................................................
---) General
Characteristics.....................................................................
---) Quality Assurance
Provisions...........................................................
--) Synchronization Supply
Unit.........................................................................
---) General Requirements.....................................................................
---) Requirement Specifications............................................................
Table of Contents
Contents Page
---) Major Components...........................................................................
---) System
Characteristics......................................................................
---) Functional Characteristics................................................................
---) Architecture......................................................................................
---) Module
Requirment..........................................................................

VI
---) Performance
Monitoring...................................................................
---)SSU Local
Management....................................................................
---) Disaster
Recovery...........................................................................
---)Physical
Characteristics...................................................................
-) Synchronization Network Management System..............................
--) Management
Requirements............................................................................
--) Functional Requirements...............................................................................
--) Alarm
Management........................................................................................
--) Configuration Management...........................................................................
--) Asset Management
Requirements..................................................................
--) Performance Management.............................................................................
--) Security Management....................................................................................
--) Network Time Management..........................................................................
) Network Management.................................................................................................
-) General Requirements...
--) General
.
-) Fault Managemet Function...........................
-) Security Managemet Function.. .
-) Configuration Management Function.........................................................
-) Performance Management Function...........................................................
-) Application Development Function.......
-) Network Management System User Interface........................................................
-) Configuration Backup and Recovery

Table of Contents

VII
Contents Page
-) Other
Requirements....
-) DCN.....
-) Processing of Routing..
-) VPN
.
-) GUI Requirement.....
-) NML-EML Interface Requirement ...
-) Non-Functional Requirement ....
-) Project Implementation ...
-)Training .......
-) Maintenance Period.....
-) Documentation and Software Provision.....
-) Customer contract/ SLA & QoS management ....
-) Customer contract, QoS/ SLA data administration ....

) ASON/ASTN
..
-) Introduction....
-) Structure.....
--) Transport Plane
--) Control Plane...
--) Management Plane..
--) Interconnection Model Between ASON/ASTN and the Customer Network
--) Intelligent Control
Mode......
-) Functional Requirements for Control
Plane...
--) Connection Management.
--) Auto Discovery and Link Management..
--) Routing

VIII
--) Signalling....
Table of Contents
Contents Page
--) Graceful
Deletion.
--) Naming and
Addressing...
--)
Reliability.....
--) Security........
-) Technical Requirements for Protection / Restoration...
--) Traditional SDH Protection Switching Capability.
--) Mesh Protection / Restoration Capability...
--) Mutual Conversion Between the PC Service and SPC/SC Service
-) Technical Requirements for The Transport Plane ....
--) Node....
---) Cross-Connect
Capability...............................................................
---) Service
Capability...........................................................................
---) Hot Backup Capability of Boards / Cards......................................
--) Netwoking Capability.....
--) SDH Interface.....
--) Ethernet Service......
--) Node Performance...
-) Timing & Synchronization Requirements.
-) NM Function Requirements..
) Maintenance.......
-) Introduction
-) Obligations for Maintenance and Technical
Support.
) Training.......................................................................................................................
-) Introduction......

IX
-) Training courses .......
--) The Whole Of
Subject....
--) Comprehensive course for trainers and
supervisors......
--) Planning
course......
Table of Contents
Contents Page
--) Installation & Commissioning course
......
--) Maintenance & Operation course......
-) Requirements........
) Test Equipment....................................................................................
) Special Tools and Acc......................................................................................
) Technical
Support....................................................................................................
) Documentation.........................................................................................................
-) General........
-) System Manual.......
-) Instruction Manual......
-) Installation
Drawing........
-) Repair Manual........
-) Inventory
Sheets......
) Factory Test and
Acceptance..............................................................................
-) General........
-) Factory
Test.........
-) Field Acceptance Test.........

X
-) Final Acceptance By TIC.......
) System Performance and its
Requirements...........................................................
) Maintenance Annex.............................................................
-) Spare
unit.........
-) Support And After Sales Service
............
-) Duty Of Contractor During One-Year
Maintenance.......
-) Repair Facilities..........
-) Training...........
Appendix......

) Tabel of Obligations & Responsibilities
......
) Route Plan........( pages)
Table of Contents
Contents Page
) Station Names
............
) Traffic Matrix ..........(
pages)
) Network Link Capacity Estimation (All links & ASON links)... ( pages)
) Equipment Modification Procedure ...

) Additional Planning Informations. (
pages)
) Evaluation Parameters . (
pages)

XI
) Compliance Statement ...














Chapter One
) GENERAL CONDITIONS

-) Introduction
--) The telecommunication infrastructure company of Iran (hereinafter called TIC)
intends to establish Next Generation SDH(NG-SDH) and DWDM networks
based on ASON/ASTN technology to cover its requirements for
th
year plan.
--) This is a turnkey project. The contractor shall supply all necessaries and
services for preparation of network and a period of maintenance. The detailed
responsibility of TIC & the contractor is according to App..
--) All the softwares needed for performance of the equipments shall be the latest
versions with un-limited license.

-) Scope of Work
A. Main Equipment
--)TIC intends to establish a transport network using NG-SDH & DWDM
technologies over a two layer network as follows:

---)ASON/ASTN layer consisting of nodes that must be connected to
each other using direct logical links over DWDM pipes.


---)None- ASON/ASTN layer.

--)The complete list of whole network station names is attached in App..
--)Traffic matrix showing the protection type of each demand is attached in App.
for whole network. Offered equipments must meet at least the traffic matrix requirements
in terms of tributary for each station.

Bidders are also requested to provide the following tributary interfaces in addition to the
traffic matrix:




Port Type DVB
FE(/)

Quantity
ports * port



--)Bidders are requested to submit the detailed report &result of their design based on
required criterions that is attached in App..

B. Network management according to chapter and sections . and ..
C. Synchronization according to chapter and section ..
D. Spares according to chapter .
E. Documentation according to chapter .
F. Installation materials and special tools according to chapter .
G. Test equipment (optional) according to chapter .
H. Training and repair center facilities containing a small network based on ASON/ASTN
technology containing nodes.

Note: All the software needed for this project shall be the latest versions and their licenses
shall have no time limitation.
-)General Tender conditions
--) The tender should be integrated . Incomplete/partial tenders will be rejected.
--) The bidder shall provide a complete Bill of Materials, to meet all requirements
mentioned in this technical specification, including its appendices. In case of
any discrepancy between different parts of the technical specifications, the
bidder shall inform TIC in writing about the discrepancies, before submitting
his/her proposal to the tender committee.
Then, TIC will inform all bidders about its viewpoints on paper, which shall be
regarded as the basis for the technical and price proposals.
--) If an item or some items have been omitted from the bidders Bill of Materials
and the contract had been signed, the contractor will be responsible to provide
all equipment, materials, or services to meet the requirements of this
specifications or those mutually agreed upon, without any additional cost.
--) The list of the manufacturers of the important components (Optical components,
Microprocessors, etc.) and their countries of origin shall be submitted with the
technical proposal.

--) Sufficient documents, showing that all proposed equipments are field proven at
least for twelve () months, shall be included in the technical proposal.
--) Optional items in this specifications are part of the main items of the project
and the bidders should propose them. However, TIC may or may not require
such optional items.
--) Proposed Optional items should be clearly identified in the technical and price
proposals.
--) A complete time schedule for the whole project including training,factory
test,installation,commissioning, dates shall be in the technical proposal.
--) The bidder shall guarantee the prompt replacement of damaged, deteriorated or
failed parts and units for a period of one () year after project final acceptance
test at his cost. For the exchanged parts and units, there should be a one-() year
guarantee from the date of replacement.
--) Panels/units and parts (or their equivalents) should be available for a minimum
of fifteen () years after delivery.
--) The time schedule should be so that the whole project be completed within
(eighteen) months from the opening date of L/C (exclusive of one year
maintenance period). Proposals with shorter time is preferred.
--) The contractor should provide a spare pool in Iran so that all shortages or
damaged units can be supplied/replaced quickly, in order to prevent any delay in
project implementation. This spare pool shall contain adequate quantities of all
units and shall be shipped to Iran within equipment delivery period.
--)Equipment modification procedure should be according to app.

--) The Supplied System should be Expandable.

-)Response Format
--) The bidder shall make a point by point compliance statement to all items of the
present specifications according to form "C" of App..
--) The Supplied system should meet all latest necessary ITU-T and the other
related Telecommunication recommendations.
--) The bidder shall state why he can not comply some of the items or why TIC
should reconsider its position.
--) The bidders proposal shall embody necessary supporting data such as
calculations, catalogues, etc.

--) The Bill of Materials shall be prepared in two copies. One copy with prices
shall be attached to the price proposals (Envelope-C). The other copy, which
shall be exactly the same as the first copy but without prices, shall be attached to
the technical proposal (Envelope-B).
--) The network plan and Bill of Materials submitted with the technical proposals
shall be prepared according to App..
--) The bidder shall provide the details necessary to demonstrate that the proposal
meets the requirements of these specifications. The details shall include
schematics, mechanical assemblies, drawings, etc.
--) Any abbreviation or symbol used in the schematics, drawings and calculations
shall be clearly described.
--) The Provided drawings shall be submitted with the technical proposal for all
types of the stations.
--) Typical drawings, which show the rack configuration of each type of stations
(rack layout drawing).
--) Drawings showing the units, which shall be provided for each subrack of each
type of stations (subrack face drawings).
--) A supply record of the proposed equipment shall be attached to the technical
proposal.
--) All the Documents should be prepared in software format and be submitted on
a compact disk (CD) with the logo of the bidder. It is needed to prepare three
hard copies with the signature of the bidder in all pages of documents. There
would not be any limitation in copying of them for TIC.

--) Interpretation and variation of any items can be done according to TIC
permission.

--) The following information shall be submitted with the technical proposal:
(Proposal which does not contain these Annexes will not be considered)

Annex-: Time schedule for whole project after opening of L/C including
manufacturing, factory inspection, training, shipping, custom clearance,
transportation to sites, installation, commissioning, test & acceptance.
Annex-: A list containing full names of all proposed units and equipment and
related software (NG-SDH and DWDM equipment, network management system
and synchronization), their manufacturers and countries of origin.
Annex-: A list containing names of the manufacturers of all components (ICs,
Microprocessors, Optical Components, etc.) utilized in the proposed equipment
and the countries of origin.

Annex-: Network management system configuration proposed for this project
(including the details of DCN planning).
Annex-: Supply record for all types of equipment.
Annex-: Equipment catalogues.
Annex-: Network management system catalogues.
Annex-: Synchronization system catalogues.
Annex-: Measuring equipment catalogues.
Annex-: Detailed list of maintenance special tools and accessories.
Annex-: Detailed list of installation materials for each type of station (Except
cablerack, structure, DDF and ODF/OCDF).
Annex-: Detailed list of installation special tools.
Annex-:Power consumption of the proposed equipment totally for the whole
project.
Annex-: Power consumption of all stations.
Annex-: MTBF figures for all equipments.
Annex-: Rack layout and rack face drawings.
Annex-: List of standard factory tests.
Annex-: Power budget calculations (for DWDM and NG-SDH equipment).
Annex-: List of spare units.
Annex-: List of spare pool units.
Annex-: Maintenance strategy.
Annex-: Technical support strategy.
-)EQUIPMENT REQUIREMENTS
--) All equipment supplied, including installation materials, shall be new, of highest
quality, undamaged, of recent manufacture, or a type currently manufactured,
and incorporating all modifications at time of production which results in an
improved product for applying to this system.
--) Only completely developed and field proven equipments shall be proposed.
Prototype equipment will not be accepted.
--) TIC reserves the right to reject any bidder whose equipment has not been proven
in the field for a minimum period of twelve () months. The technical proposal
shall embody the results of the manufacturers latest field proven experience.

--) Racks specifications shall be in accordance with ETSI standard with dimensions
of mm x mm x mm (WxHxD).
--) Since the height of the racks in existing stations is mm, bidders should
propose the necessary adapters for their racks to be able to fix the existing
structures.
--) Front access designed for racks shall be preferred. It could be possible to mount
racks back-to-back, side-by-side. The bidder shall submit typical drawing for
each case, showing the racks spacing and dimensions.
--) The equipment shall be designed in some way to enable it to be easily and
quickly installed. The preparation at the site of inter-rack harnesses and other
installation materials shall be avoided as far as possible. The arrangement of
racks shall be provided so that the future expansions shall be possible by only
adding equipment or software modification without the necessity of major re-
organization or replacement of the initial installation, i.e. racks, with sub-
assemblies and modules, shall, from the beginning, be wired with all harnesses,
connectors, hardware, etc. necessary for the expansion to full capacity.
--) Racks shall be secured to the floor and be super structure in order to withstand
overturning moments caused by cable pulling or earthquake effects. Sufficient
bracing to withstand earthquake forces of intensity on the mercalli scale (.g
horizontal acceleration) shall be provided. The racks and shelves shall survive
an earthquake qualification test consisting of application of sinusoidal force
accelerations of . g horizontal (in each of two orthogonal directions) and
. g vertical, linearly swept in frequency from to Hz and return to Hz
at . Hz/Sec. The two horizontal and one vertical portions of this test shall be
applied separately.
--) Expansion of the proposed system shall be possible without service interruption.
--) All of the equipments and materials such as racks, shelves, units, pigtails, patch
cords, PDBs, etc. shall be packed separately for each station. Every individual
shelf shall be pre-wired.
--) The mechanical design of equipment shall be so that the installation of the
units or panels on wrong positions would not be possible.
--) The bidder shall state if any type of wiring is required during installation of the
equipment in the stations (e.g. soldering, wrapping, etc.).
--) The office electrical cables for inter-connecting the different equipments are of
several types:
a) Coaxial cable for Electrical Interface.
b) Cables for E& FE
c) Power cable for DC power distribution
d) Alarm and supervisory cables

--) The bidder shall state the type and maximum length of cable intended to use in
each category mentioned above as well as the type of support necessary in the
usual inter-connection cabling such as ladder racking, overall grid.
--) The connections which are supposed to be semi-permanent shall not be
soldered.
--) All types of equipment shall be designed so that incorrect operations during
commissioning or maintenance would not cause any damage.
--) Empty positions of racks shall be covered by plates.
--) All plug- in units shall be replaceable very quickly without using any special
tools.
--) Possibility of accidental touch of dangerous parts of the equipment shall be
reduced to the minimum.
--) Safety conditions shall conform to IEC publication.
--) Replacement parts and controls should be designed such that the danger of
mechanical and electrical hazards are minimized. Warnings shall be clearly
placed in English on unavoidable hazards. Personnel shall be protected from all
hazardous voltages. Wherever an unavoidable danger from exposure to any
hazardous voltages (such as those that can be exposed due to removal of covers)
exists, there shall be a warning of such dangers to personnel in large English
letters. All exposed metals shall be at ground potential.
--) Composition of different materials joined together shall be chosen so that
electrolytic corrosion does not occur.
--) Inflammable materials shall be used.
--) Brittle material, such as cast-iron, zinc or glass shall not be used.
--) Wherever possible, standard consumable parts shall be used. These parts
should be available from more than one manufacturer.
--) Modular and plug-in concept shall be utilized throughout. All modules shall be
readily removable from the front of the rack without any requirement of shutting
off the power prior to removal.
--) Copper wire cables and terminal plugs shall be provided. Aluminum wire will
not be allowed.
--) Cooling of the all units is preffered to be based on normal air convection and
/or heat sink arrangement.
--) All equipment sub-racks, units, modules, parts, and components shall be
clearly marked.
--) All labels, marking and other identifications, shall be in English or with
symbols as per ITU, IEC or ISO or other internationally recognized
recommendations. They shall be durable and of high quality.

--) The markings should be such that constant use of plugs or switches does not
cause the designation to peel or rub off.
--) All assemblies and sub-assemblies and other modules capable of being
exchanged during normal maintenance shall be marked with:
a) Function
b) Manufacturers identification
c) Identification used in handbook and drawings
d) Model number (if applicable)
e) Serial number
--) Maximum heat dissipation allowed for station or office circuit equipment areas
shall be given in terms of W/m

, average over the total minimum recommended

floor area, as stated by the bidder in response to item -. The bidder shall
provide maximum total heat dissipation figure for each individual rack provided
for each equipment type, taking into account available options and the worst-
case operating conditions assumed for each type.
--) Markings and identifications on modules, components and parts must exactly
match designations used in handbooks, drawings and pictures.
--) All equipment shall have mounted designation cards which are designed to
provide appropriate information.
--) The equipment shall be designed to facilitate quick fault localization and
restoration to service by only exchanging modules without any field repair of
faulty ones.When a new unit has been placed in service, necessary adjustments
shall be minimized.
--) The reliability and stability of the equipment shall be such as to allow routine
maintenance interval not become less than (six) months for equipment installed
in normal offices. The longest routine maintenance rate recommended shall be
stated by the bidder.
The bidder shall describe any special feature of his equipment which will facilitate
maintenance. There shall be information in the tender about estimated number of
man-hours and maintenance periods necessary for routine maintenance.
--) All measuring, alarm and performance parameters monitoring, and remote
controls shall be performed via a portable LCT (Local Craft Terminal).
Connection and disconnection of the portable LCT and its operation shall not
affect the operation and performance of the system.
--)If necessary routine adjustment controls shall be readily accessible from the
front of the equipment without removal of the units.
--) All connectors, cable harnesses, and inter/intra-rack wiring shall be clearly
identified so that no ambiguity can occur.

--) The equipment shall be so arranged that it is automatically switched off or
power removed in case of any fault that other parts of the equipment might be
damaged.
--) The circuitry for this function should be designed to minimize false operation.
--) The maintenance test of any unit shall be done without interrupting traffic.
--) All faulty units/panels shall be replaced and repaired under contractors
responsibility.
--) The equipment shall be designed so that all maintenance adjustments and
measurements can be performed from the front of the equipment without service
interruption.
--) The equipment characteristics and performance shall comply with the latest
ITU-T, OIF and IETF recommendations.
--) No component or device shall be designed to operate in excess of its maximum
voltage or current rating as specified in the relevant manufactures data sheets,
over the range of conditions required by this specifications.
--) All equipment and devices shall be suitably protected against over voltage,
over current and ground leakage.
--) Direct current devices shall be protected against voltage polarity reversal.
--) Non-fuse breaker (NFB) power distribution fusing shall be provided for all
equipment shelves. Each rack shall have a separate fuse.
--) Operation of fuses and/or circuit breakers within terminal equipment shall
cause the initiation of office alarms. For designs in which fuse operation directly
completes an alarm contact, there must be complete galvanic isolation between
the main circuit and the alarm circuit. It shall be preferred that a unique lamp or
equivalent display be provided within the terminal rack to distinguish the
presence of a fuse or circuit breaker alarm.
Fuses used within the terminal equipment shall preferably be of the indicating type.
That is, it should be possible to distinguish which group of fuses has operated
through the presence of a distinct visual indication. If such indication is not
provided, the bidder shall describe the method(s) by which the operated fuse may be
isolated.
--) The equipment shall be resistant to transients from the switching equipment,
power or other sources arriving on power supply leads, and digital line
interfaces.
--) All connectors shall be of high quality and be so designed and constructed that
the overall mechanical and electrical performance of the connector is not
degraded or impaired by the repeated connections and disconnections that will
be normally experienced during the designed life of the equipment.
--) The component used in the equipment shall be of such quality and be used in
such a way that at least a years life period can be foreseen for the equipment
when operating in a given operation environment.

--) All equipments shall be connected to a rack ground bar.
--) All metallic parts shall be electrically bonded together.
--) Providing of stations earthing system is not covered by this specifications, but
the contractor shall clearly mark and indicate the location on the rack where the
connection shall be made.
--) All equipments (except test equipment and computers)shall be designed to
operate with to VDC as described below. Test equipment and
computers shall operate with (+/-%) VAC, (+/-%) Hz.
Primary Power Sources
a) The power sources available in each station are:
- v DC with positive pole grounded
b) Normal Variations
- v DC Voltage variation +% v
- AC ripple upto . Vpp
c) Extreme variations
- v DC source Voltage variation - v to v
These characteristics apply to equipment which is directly fed from the primary
power sources.
--) In case of not using on-board power supply, suitable power supply unit
redundancy shall be provided in each subrack for increased reliability.
--) The distribution system shall limit transients so that a short circuit in one
distribution branch will not cause the voltage in another distribution branch to
exceed the voltage accuracy requirements.
--) Short interruption of power supply:
The bidder shall state the duration of power interruption & the equipment
shall withstand without service interruption or initiation of alarm.
--) The service shall continue without any break or transient disturbance if the
battery charger is switched to and from forced or equalization charging, if the
AC power to the battery rectifier suddenly fails with batteries in order.
--) Transients on DC primary power sources:
a) Transients of V and duration of microsecond on DC supply leads
shall cause no damage to the equipment.
b) Primary source voltage of any magnitude less than nominal shall not cause
equipment damage.

--) Primary power source noise:
a) The stated performance of the equipment shall be maintained:
A. With power source noise in any KHz bandwidth, between
KHz and KHz, less than mv r.m.s. from the v primary
power source.
B. With power source noise in the voice frequency band upto-
dBmp from the v primary power source.
--) The design objective for the distribution loss, including cabling, fuses,
switches, circuit breakers, etc. from the battery poles to the power connection at
each individual rack shall be as follows for all operating conditions :
For a v feed system . v
The bidder shall state how the primary power sources are protected and distributed in each
rack line up and in each individual rack.
--) The primary input of any power supply shall be fused on the negative polarity
of the input voltage.
--) Any power supply shall not be damaged if the DC input voltage is applied with
the wrong polarity. The bidder shall describe the method by which such
protection is achieved.
--) Local power supplies shall be protected against over currents and over
voltages. The bidder shall give the values of the protection limits and how the
protection is implemented.
--) Each power supply shall be controlled with visual and audible alarms.
--) Power supplies which feed more than two systems must be equipped with
redundant power units.
a) Each normal and redundant unit shall be capable of supplying the total
power consumption requirements of the equipment for which it has been
designed.
b) Control lamp(s) shall indicate which power units are operating and in case
of failure, switching to the redundant power supply shall be automatic and
shall cause no activation of major urgent alarm for the system supplied.
c) A single defective power unit shall give only minor or non-urgent alarms
d) In case of failure of both normal and redundant power units, major or
urgent alarms shall be given.
--) Two independent power distribution lines, A and B, shall be used for the alarm
and monitoring functions in the equipment.
--) It shall be possible to terminate two independent power distribution lines in the
equipment.

--) Printed circuit boards shall be composed of a high strength heat resistant
fiberglass base material or an equivalent with bonded copper sheet circuitry.
--) Plug-in circuit boards shall employ two opposite bifurcated contacts. A tarnish
resistant metal such as gold or palladium shall be used for the connector
contacts.
--) All printed circuit boards or other assemblies containing electrostatic sensitive
devices shall carry a suitable warning label advising of the need to observe
electrostatic protection. The front panel of such equipment shall also carry the
same warning. Antistatic wrist straps shall be supplied at the maintenance
centers of the stations for which these kinds of devices are supplied.
--) The workmanship, material and finish of all supplied equipment shall be free of
all defects and shall embody the best features of contemporary
telecommunications equipment.
--) All thread sizes for screws, nuts and bolts shall conform to a standard system,
preferably the metric system.
--) Equipment shall be packed to withstand severe vibration as may be
encountered during transportation in Iran.
--) Mechanical shocks that occur during maintenance (such as opening and closing
the cabinet doors, connecting and disconnecting of cables, etc.) shall not affect
the transmission performance.
--) The equipment shall be packed to resist fungus or mold during transportation
and storage.
--) Equipment must be fully protected against effects of air borne dust and sand.
--) All electronic equipment or other items which may be affected by fungus or
mold shall be suitably tropicalized.
--) Environmental Parameters:
Any digital equipment supplied to the TIC shall operate satisfactorily (per
the criteria stated in this specification) as follows :
a) Normal Operating Conditions:
Ambient temperature (I) +
o
C to +
o
C.
Relative humidity:
For I<
o
C % to %
For I>
o
C % to X%
(X decrease linearly From % to %)
Altitude:

- to meters above mean sea level (m.a.m.s.l)
Ambient refers, to conditions at a location . meters above the floor and
. meter in front of the equipment.
b) Short term and extreme operating conditions:
Under the following conditions the equipment shall continue to
give service, with allowance for reasonable degradation of
performance from the requirements stated in this specification:
Ambient temperature -
o
C to +
o
C .
Relative humidity % to %
Earthquake: upto intensity on the mercalli scale
Shortterm temperature and humidity conditions will not persist more than
hours continuously & not more than days in one year. The office
equipment shall remain operational when subjected to earthquake
environments specified above even though some physical damages may
occur.
c) Transportation and Storage:
During transportation and storage (on-working) the packaged equipment
shall withstand without damage in the following conditions :
Temperature: -
o
C to +
o
C
Relative humidity: % to %
Altitude: - to m.a.m.s.l
Vibrations: One sweep of . from to Hz during
minutes at a rate of . octave /min.
Shocks: One shock pulse of G during ms applied in
each possible orientation axis parallel to the transportation
longitudinal axis.
--) The equipment provided shall be compatible with the bidders existing and
planned facilities which shall not form a part of this specification.
--) Quality Requirements:
a) Quality Assurance:
Bidders shall include documentation containing full details of the quality
assurance systems which will be applicable for the specified equipment.

The quality assurance systems shall comply with the latest ISO standard.
b) Quality Control:
Suppliers shall demonstrate that their organizations are capable of
maintaining a qualification standard that meets all specified requirements.
The quality of equipment shall comply with the requirements in
specification with the latest ISO standard.
The operation of the quality procedures will be confirmed by assessment
visits and suppliers shall state their agreement.
--) Life Time Operating Conditions:
The operating life time of the equipment shall be at least years. All specified
values shall be valid under all operating conditions and during the life time of the
equipment and shall fully comply to the specifications given in this chapter.
--) Electromagnetic Environment:
a) The supplier shall guarantee trouble-free operational performance of the
equipment in the electromagnetic environment as well as tolerance to electrostatic
discharge as specified in the relevant parts of ITU-T recommendations which are
based on related IEC.
b) The requirement for emission is that the equipment shall fulfill the requirements
specified in document CISPR .
--) In the time between finalizing the LOM and delivering the equipment if the
newer version of this equipment had been produced, the winner should offer the
latest version too, TIC reserves the right to choose each kind of the offered
equipment.

Chapter two
) Network
-) Introduction
Network Requirements for establishing transmission network are considered in three
following sections: Transmission, Sinchronization, Network management and
Protection.
-) Transmission
The TIC intends to establish a transmission network .The bidder shall submit the
transmission network plan..
-) Syncronization
--) The bidder shall submit the Synchronization network plan and equipment
according to proposed transmission network.
--) The proposed Synchronization Network must be according to ITU-T G.,
G., G., G. and G. Recommendations.
--) The proposed Synchronization Network must include PRS as main equipment
and standby.
-) Protection
The bidder shall use the following protection mechanisms in the transport network:
--) MSP (Multiplex Section Protection)
a) Bidder will use MSP + between any local switchs (including BTS, MSC, RS
and other equipment) and the connected SDH equipment.
b) The MSP + shall work in non-revertive and revertive mode.
c) The MSP + shall be supported at STM-, STM-, STM- and STM- (where
applicable)
d) The Bidder is required to support MSP + in their offered equipment.
--) SNCP/N (Sub-Network Connection Protection, Non-Intrusively monitored)
a) Tenderer will use SNCP/N on all bit rates in their sub-networks and meshed
network connections.
b) The SNCP shall work in non-revertive and revertive mode.
c) The SNCP shall be supported at VC-, VC--xc, VC-, VC--xc, VC- and
VC--xc (where applicable).

d) The Bidder is required to support SNCP/N in their offered equipment.
--) F. MS-SPRing (Two fibres Multiplex Section Shared Protection Ring)
a) Bidder will use F. MS-SPRing in all STM-/STM- transport rings. In cases
with capacity problems, the Tenderer will implement a higher bit-rate, assuming
that implementing higher bit-rate is more cost effective than utilizing an additional
fibre pair.
b) The MS-SPRing working will be working in revertive mode.
c) The bidder is required to support F. MS-SPRing in their offered equipment.
d) The bidder shall state how many MS-SPRing rings their system can be member of.
--) LCAS (Link Capacity Adjustment Schema)
a) In order to offer higher availability to their subscribers, the bidder will implement
point-to-point LCAS in their data network.
b) The bidder is required to support LCAS in their offered equipment.

-) DCN

Management Network
--) DCN network shall provide necessary infrastraucture for supervisory of
equipment and network management.
--) DCN Network must have higher reliability.
--) DCN Network must have sufficient bit rate.

Data Communication Network.

Chapter: three
) NG-SDH Technical Specifications
-) General Considerations
--) The system shall confirm to the latest ITU-T recommendation, IETF & IEEE
standards, if it is not confirmed some sections of standards; provider should
define its deviation with reason.
--) Provider shall submit detailed specifications of hardware and software
upgrading capability.
--) Provider shall notify nominal bit rate, bit rate tolerance, coding, scrambling
and error detection/correction mechanism for all interfaces.
--) SDH frame structure shall be according to ITU-T G..
--) Software upgrading, control, alarms monitoring, levels provision of the
system must be possible locally and remotely, without any service
interruption.
--) FEC (Forward Error Correction) or EFEC (Enhancement FEC) mechanism
shall be used for Gbps and higher bit rates.
--) System shall work over existing single mode fiber optic cables between nodes
in this project according to App. .
--) Provider shall describe capability of system operation with OTN (Optical
Transport Network) according to ITU-T G..
--) Provider shall describe the using intelligent optical networks features in
system according to the following Recommendations:
a) ITU-T G., ITU-T G. and ITU-T G. for ASTN (Automatic
Switched Transport Network) and ASON (Automatic Switched Optical
Network)
b) IETF Recommendation for Protocols based on GMPLS (Generalized
Multi Protocol Label Switching)
c) OIF-UNI (Optical Internetworking Forum-User Network Interface)
--) Provider shall fully transfer technical knowledge of NG-SDH systems to TIC
(Telecommunication Infrastructure Company) personnels.
--) System identification shall be related to their application type intra office,
Short haul, Long haul, Very long haul & Ultra long haul shall identify to
Application codes: I, S, L, V and U according to ITU-T G. and ITU-T
G. for systems with and without optical amplifier.
--) Provider shall notify all optical and electrical connectors used for system
interconnections.
--) Provider shall provide all adaptors needed between System connectors.


-) Operation modes
--) System shall support following operation modes:
a) TM (Terminal Multiplexers)
b) ADM (Add-Drop Multiplexers)
c) DXC (Digital Cross-Connect)
-) Network Topologies
--) System shall support the following network topologies:
a) Point-to-Point
b) Linear
c) Ring/Multi Ring
d) Mesh
-) System transmission capacity
--) Provider shall fulfill table . for all type of System in this project.
--) Cross-connect for all VCs (Virtual Container) must operate at full non
blocking mode and support following functionalities:
a) Tributary to Line
b) Tributary toTributary
c) LinetoLine
d) Loop Back
e) Drop & Continue
f) Uni-Directional/Bi-Directional
g) Broadcasting Connections
--) Provider shall fulfill switching cross connection matrix at table .

Table .: System transmission capacity
Port per Card Max Access port per single Sub rack Service Type
E (VC-)
E (VC-)
Electrical STM-
Optical STM-
Optical STM-
Optical STM-
Optical Colored STM-
Optical STM-
Optical Colored STM-
Fast Ethernet, / Mbps
RPR FE
Gigabit Ethernet
RPR GE
Gigabit Ethernet
FDDI
Digital Video
ESCON
Fiber Channel
FICON
ATM E

ATM STM-
Table .: Switching matrix capacity
Switch Matrix
Lower Order Matrix unit
(VC-) Capacity
Board Type
High Order Matrix unit
(VC-) Capacity
Board
Type




-) Electrical interfaces
--) E (HDB, Kbps ppm) interfaces must be according to ITU-T G.
and with / impedance.
--) E interface Jitter tolerance must be according to ITU-T G..
--) E interface Mask must be according to ITU-T G. and provider must
submit related mask diagram.
--) E interface must support Unframed and framed modes according to ITU-T
G..
--) E (HDB, Kbps ppm) interface shall be according to ITU-T G.
and with impedance.
--) E interface Jitter tolerance must be according to ITU-T G..
--) E interface Mask must be according to ITU-T G. and provider must
submit related mask diagram.
--) STM-(CMI, Kbps ppm) interface must be according to ITU-T
G. and impedance.
--) STM- interface Jitter tolerance must be according to ITU-T G..
--) STM- interface Mask must be according to G. and provider must submit
related mask diagram.
-) Order wire

--) System must be equipped with Order Wire channel using DTMF signaling for
test, installation and maintenance used by operators between nodes of
network.
--) Order wire channel must provide voice connection for operators with the
following methods:
a) By numbering (max to )
b) Teleconference
c) Playback for all terminals
--) If two stations are talking to each other, it must be possible for other stations
to be connected to the conversation via dialing a specified digit or code
number (conference).
--) System must have at least two order wire channels for communicating with
back and forward terminals.
--) The system must be able to provide multi directions order wire channel.
--) Each terminal must have the capability to define numbering for order wire
channel.
--) The system must have express order wire channel (selective) with access to
PABX channel.
--) Provider must notify additional capability of order wire such as answering
machine and interconnection between NG-SDH & DWDM.
--) Provider must fulfill specifications of order wire in table ..
Table .: Specifications of order wire channel
Parameters value
Number of OW channels in terminal
Number of OW channels in ADM
Type of handset interface
W
W
Type of hand set connector
parameters minimum maximum
Level of output voice signal (dBm)

Level of input voice signal (dBm)

-) Optical interfaces
--) Specifications of all optical interfaces without optical amplifier must be
according to ITU-T G..
--) Specifications of all optical interfaces with optical amplifier must be
according to ITU-T G..
--) Specifications of all optical amplifiers must be according to ITU-T G., G..
--) Provider must notify calculation method and results of link power budget and
maximum span length over existing optical fiber cable routes.
--) Provider must present eye diagram for all optical transmitters.
--) Provider must fulfill specification of all optical interfaces in table ..
Table .: Specifications of optical interface
Description Unit Parameter
- Optical source type
nm Wavelength transmitter
dBm Maximum Transmitter Power
dBm Minimum Transmitter Power
Max Min
dBm Tunable Transmission Power & Range

dB Minimum Extinction Ratio
nm Received operating wavelength range
dB Minimum Receiver Sensitivity
dB Minimum Receiver Overload
- OSNR

ps/nm Maximum Dispersion tolerance in the receiver
km Span Length
- Connector Type
dB Optical Reflection Loss

--) All optical interfaces must have separate optical modules according to MSA
(Multi Source Agreement), type of optical modules are listed as following:
a) SFP (Small Form factor Pluggable) or SFF (Small Form Factor) for Bit
rates up to . Gbps and GE
b) XFP (Gb small Form factor Pluggable) for STM-
c) XENPAK for GE
--) For direct connection to DWDM/CWDM systems, STM-, STM- and
STM- optical modules must be able to replace with tunable colored modules
according to ITU-T G../G...
--) Central wavelength and connector type of optical interfaces must be specified
according to table ..
Table .: Central wavelength and connector type of optical interfaces
Connector Central wavelength
Optical
interface
SC/PC
FC/PC
ST
DIN
E
LC
nm
nm
STM-
SC/PC
FC/PC
ST
DIN
E
LC
nm
nm
DWDM .... Wavelength (THz)
Tunable for ... Channel, Channel spacing,
.... Central Wavelength (THz)
CWDM.... Wavelength (nm)
STM-
SC/PC
FC/PC
ST
DIN
E
nm
nm
DWDM .... Wavelength (THz)
Tunable for ... Channel, Channel spacing,
.... Central Wavelength (THz)
STM-

LC CWDM.... Wavelength (nm)
SC/PC
FC/PC
ST
DIN
E
LC
nm
nm
DWDM .... Wavelength (THz)
Tunable for ... Channel, Channel spacing,
.... Central Wavelength (THz)
CWDM.... Wavelength (nm)
STM-
SC/PC
FC/PC
ST
DIN
E
LC
nm
nm
DWDM .... Wavelength (THz)
Tunable for ... Channel, Channel spacing,
.... Central Wavelength (THz)
CWDM.... Wavelength (nm)
STM-

-)Optical amplifier
--) Systems with optical amplifiers must be according to ITU-T G. and ITU-T
G..
--) Provider must fulfill specifications of optical Booster and Pre-Amplifier in
table . and table ..
Table .: Specifications of optical Booster Amplifier
Parameters Unit
Value
Minimum Maximum
Operating wavelength range nm
Total input power range dBm
Total output power range dBm
Amplification gain range dB
ability to hold output power constant and range dBm
ability to hold gain constant and range dBm

Insertion loss dB
Saturation output power dBm
Input overload power dBm
Noise figure (P
in
= dBm) dB
Gain flatness dB
Maximum reflectance tolerable at output dB
Input reflectance dB
Polarization Mode Dispersion (PMD) Ps/nm
Polarization Dependent Gain (PDG) dB
Pump wavelength nm
Pump leakage dBm
Connector type -
Table .: Specifications of optical Pre Amplifier
Parameters Unit
Value
Minimum Maximum
Operating wavelength range nm
Total input power range dBm
Total output power range dBm
Amplification gain range dB
ability to hold output power constant and range dBm
ability to hold gain constant and range dBm
Insertion loss dB

Saturation output power dBm
Input overload power dBm
Noise figure (P
in
= dBm) dB
Gain flatness dB
Maximum reflectance tolerable at output dB
Input reflectance dB
Polarization Mode Dispersion (PMD) Ps/nm
Polarization Dependent Gain (PDG) dB
Pump wavelength nm
Pump leakage dBm
Connector type -


-) Optical Attenuator
--) Provider must declare each part of the system that needs optical attenuator with
its value in this project.
--) Connector of optical attenuators must be accommodated with equipments.
--) Provider must fulfill specifications of fixed optical attenuator in table ..
--) In case of using any type of VOA (Variable Optical Attenuator) in the system,
Provider must fulfill specification of VOA in table .
Table .: Specifications of fixed optical attenuator
Parameters Unit
Value
Minimum Maximum
Operating wavelength range nm
Attenuation dB
Insertion loss dB

Return loss dB
Polarization Dependent Loss (PDL) dB
Tolerable input power dBm
Connector type -

Table .: Specifications of VOA
Parameters Unit
Value
Minimum Maximum
Operating wavelength range nm
Attenuation range dB
Resolution dB
Insertion loss dB
Return loss dB
Polarization Dependent Loss (PDL) dB
Tolerable input power dBm
Connector type -


-) Dispersion compensation
--) Chromatic Dispersion Compensator or DCM (Dispersion Compensator
Module) must be according to ITU-T G..
--) Provider must declare compensation method and location of DCM in the system in this
project.
--) Provider must fulfill specifications of DCM in table ..
Table .: Specifications of passive chromatic dispersion compensation
Value Parameter
Maximum Minimum
Operating wavelength range (nm)
Insertion loss (dB)
Return loss (dB)

Polarization Dependent Loss (dB)
Polarization Mode Dispersion (ps) PS/nm
Tolerable input power (dBm)
Connector type
PMD (ps) Dispersion (ps/nm) Insertion loss(dB) Compensation equivalent km of G.
.

.













--)Provider must declare compensation method, location and specification of PMD
compensator, if used in this project.

-) Optical Patch Cord and Pigtail
--) Optical patch cords must be suitable for connection to ODF (Optical
Distribution Frames) with minimum length of m, single mode fiber and
DIN connector (ODF side).
--) Performance of optical pigtail and patch cord connector must not be degraded
before times of plugging-in and plugging-out.
--) Optical Pigtail must be suitable for connection to ODF (Optical Distribution
Frames) with minimum length of m, single mode fiber and DIN connector
(ODF side).
--) Provider must fulfill specifications of optical patch cords in table . and
optical pigtails in table ..

Table .: Specifications of optical patch cord
Value Unit Parameters
dB Insertion loss
dB Return loss
Kg Tensile strength
dB Polarization Dependent
Loss (PDL)
dBm Tolerable input power
ps PMD
System side ODF side
- Connector type


Table .: Specifications of optical pigtail
Value Unit Parameters
dB Insertion loss
dB Return loss
Kg Tensile strength
dB Polarization Dependent
Loss (PDL)
dBm Tolerable input power
ps PMD
- Connector type

-) Data Interfaces
--) The system must be capable of transfering Ethernet traffic over full TDM
(STM-n) based networks.
--) The system must be capable of transfering Ethernet traffic without MPLS
(Multi Protocol Label Switching) over SDH network.
--) The system must be capable of transfering Ethernet traffic with MPLS using
Label binding and Forwarding over SDH networks.
--) The system must be capable of implementing point-to-point L MPLS VPN
(Layer MPLS Virtual Private Network) by the following interfaces:
ATM to ATM

Ethernet/VLAN to Ethernet/VLAN
TDM to TDM
--) The system must support L Private Ethernet Line service.
--) Provider must declare the capability of the system for supporting L MPLS
VPN service, if it is supported.
--) The system must be capable of supporting Fast Reroute Redundant LSP, if it
is supported.
--) MPLS signaling must be based on LDP (Label Distribution Protocol), if it is
supported.
--) System capability for TE (Traffic Engineering) must be based on RSVP-TE
(Resource Reservation Protocol), if it is supported.
--) All data interfaces must fully support VCAT (Virtual Concatenation)
according to ITU-T G..
--) All data interfaces must fully support LCAS (Link Capacity Adjustment
Scheme) for Low Order and High Order according to ITU-T G..
--) Provider must notify Deferential Path Delay for VCAT.
--) The system must support the following management system commands for
VCG (Virtual Concatenation Group):
a) Add a member to VCG

b) Remove a member from VCG
c) Lock out a member from VCG
--) All data interfaces must support GFP (General Framing Procedure) type T
and F, according to ITU-T G..
--) Provider must notify capability of the system for supporting LAP-S (Link
Access Procedure SDH) according to ITU-T X. and X. and LAP-F
(Link Access Procedure-Frame relay) according to ITU-T Q. and Q.,
if it is supported.
--) System must be able to limit bandwidth at client node with Mbps steps.
--) System must be able to provide dedicated or non-dedicated bandwidth.
--) Provider must notify maximum number of simultaneous VCGs per each
card.
--) Layer non blocking switch fabric forwarding capacity of data interfaces
must be at least Gbps, maximum capacity must be notified by
provider.
--) Mapping of Ethernet frame with VCG capability must be done as followed:

a) Mbps by mapping to VC-nv
b) Mbps by mapping VC-nv and VC-nv
c) Gbps by mapping VC-nv and VC-nv
d) Gbps by mapping VC-nv and VC-nv
--) System must support QoS (Quality of Service) and CoS (Class of Service)
based on MPLS for VLAN and MAC (Media Access Control) address of
each port.
--) Ethernet MAC switches must be able to be logically partitioned into virtual
MAC switches.
--) Minimum MAC address table must be ., the maximum must be notified
by Provider.
--) System must support MAC address filtering.
--) System must support transparently forwarding incoming IEEE .Q
VLAN tag Ethernet frames.
--) System must support CoS according to IEEE .p.
--) System must support EPL (Ethernet Private Line), EVPL (Ethernet Virtual
Private Line), EPLAN (Ethernet Private LAN) and EVPLAN (Ethernet
Virtual Private LAN) services.
--) System must support VLAN ID and at least . Active VLAN,
Maximum Active VLAN must be notified by Provider
--) System must be capable to configure MTU (Maximum Transmission Unit)
up to bytes (Jumbo frames) for bridging on Gigabit Ethernet ports, and
up to bytes for bridging and routing on Fast Ethernet.
--) System must support congestion avoidance RED (Random Early Detection)
and WRED (Weighted Random Early Detection).
--) System must support the following queuing services:
a) Priority queuing
b) Custom queuing
c) WFQ (Weighted Fair Queuing)
d) CBWFQ (Class-Based WFQ).
--) System must support the following queuing algorithms:
a) Real-time class
b) Assured quality class
c) Best effort class
--) System must support RPR (Resilient Packet Ring) according to
IEEE ..
--) RPR Services must support CoS priorities with A, B and C service class
according to IEEE ..

--) RPR service must support steering and wrapping protection with switching
time less than ms according to IEEE ..
--) Layer Ethernet must have the following features:
a) Flow Control (.x)
b) Ethernet Bridging (.d)
c) Class of Services (.p)
d) Spanning Tree Protocol (.d)
e) Rapid Spanning Tree Protocol-RSTP (.w)
f) VLAN Trunking Protocol-VTP (.q)
g) Multiple Spanning TreeMSTP (.s)
h) Link Aggregation (.ad)
i) Tunneling-Q in Q (.q)
j) Authentication Mechanism for Security.(.x)
--) Ethernet Base-T Interface must be according to IEEE ..
--) Ethernet /Base-TX Interface must be according to IEEE .u.
--) Ethernet //Base-TX Interface must be according to IEEE .z.
--) Ethernet GE Interface must be according to IEEE .ae.
--) FC (Fiber Channel) Interface must be according to ANSI X..
--) ESCON (Enterprise Systems Connection) Interface must be according to
IBM SA.
--) FICON (Fiber Connectivity) Interface must be according to ANSI X..
--) DVB-ASI (Digital Video Broadcasting-Asynchronous Serial Interface)
Interface must be according to ITUT J..
--) Data interface connectors must be according to Table ..

Table .: type of data interface optical connectors
Optical data interface Connector
Base-FX (FE) LC SC MTRJ
Base (GE) LX SX ZX LC SC MTRJ
GE LC SC MTRJ
FC
LC SC MTRJ
ESCON
LC SC MTRJ
FICON LC SC MTRJ
DVB
LC SC MTRJ

-) Ethernet topologies
--) In Point-to-point Ethernet connection the two ports must have the capability of
connection in separate ports, separate units and separate shelves.
--) In Point-to-point Ethernet connection the following cases must be supported:
a) Layer Ethernet Private Line based on static bandwidth (i.e. a VCG)
b) Layer Ethernet forwarding scheme (i.e. no MAC switching)
--) Point-to-point Ethernet connection must support Layer Ethernet Private Line
mapped into MPLS with QoS guarantees and differentiated services.
--) Point-to-point Ethernet from customer end side to the Virtual MAC Switch
shall be implemented with either Layer Ethernet Private Lines (i.e. Ethernet
mapped into VCGs) or Layer Ethernet Private Lines (i.e. based on MPLS).
--) In Point-tomultipoint Ethernet connection, there must be the capability of
connecting multiple Ethernet ports(Customer ports) to one port(aggregation
port).
--) In Point-tomultipoint Ethernet connection, Ethernet Switches in SDH Nodes
must be able to be logically divided into a number of Virtual MAC Switches,
each corresponding to one customer.
--) Connection between customers to virtual MAC in the same domain must be
implemented via Layer Ethernet Private Lines or Layer Ethernet Private Lines.

--) The system which is connecting a customer port, must be able to transparently
forward incoming IEEE .Q VLAN tag Ethernet frames.
--) The system which is connecting aggregation port must be able to forward
incoming IEEE .Q VLAN tag Ethernet frames to the customer which the
port belongs to by examining.
--) System must be capable of transfering Ethernet frames completely
transparently.
-) Synchronization
--) System must have the following three synchronization modes according to
ITU-T G., ITU-T G. and ITU-T G.:
a) Locked
b) Hold over with accuracy . ppm/day
c) Free running with accuracy . ppm.
--) Synchronization equipment must support SSM (Synchronization Status
Message) monitoring and algorithm for priority definition according to
ITU-T G. and ITU-T G..
--) System must have synchronization output ports.
--) System must be able to automatically return to higher priority input when it
comes back to normal mode.
--) System must have KHz timing reference according to ITU-T G..
--) KHz timing reference Interface must have or Impedance
and balanced or unbalanced mode.
--) Jitter of KHz timing reference output port must be according to
ITU-T G..
--) System must have Kbps timing reference with HDB coding according to
ITU-T G., ITU-T G..
--) Kbps timing reference Interface must have or Impedance
and balanced or unbalanced mode.
--) System must have tributary channels timing reference capability.
--) System must have line (STM-n) timing reference according to ITU-T G..
--) Provider must fulfill input and output synchronization ports specification in
table ..

Table .: list of synchronization ports
Input synchronization ports
Type Description



Output synchronization ports
Type Description



-)System Protection
--) Equipments protection must be supported in all topologies.
--) System must support the following protection types:
a) + protection for all optical interfaces of intra-office (shelves
interconnection).
b) :n protection for all electrical interfaces, provider must specify the value of n.
c) + protection for all common units.
d) + protection for switch matrices.
--)Provider must declare if the protection units are the same as working units.
--)Provider must define the location of the protection units.
-) Network Protection and Restoration
--) Network and Traffic protection must be supported in all topologies.
--) The following Protection functionalities must be supported and provider must
notify the switching time value of them:
a) Revertive or non-Revertive
b) Wait To Restore
c) Manual, force or automatic switching for working or protection paths
--) System must support + MSP (Multiplex Section Protection) according to
ITU-T G..
--) System must support + MSP protection for all STM-n interfaces.

--) Provider must notify MSP configuration methods and limitations for all
interfaces.
--) System must support SNCP (Sub-Network Connection Protection) type I
(Inherently) and N (Non-intrusive) for all interfaces and topologies according
to ITU-T G..
--) System must support SNCP I/N protection for all VC, VC-xc, VC, VC-
xc, VC and VC-xc.
--) Provider must describe high order and low order SNCP protection
configuration.
--) Equipments must support F-MSPRing (Multiplex SectionShared
Protection Ring) or F-MSPRing for STM-, STM- or STM-
according to ITU-T G..
--) System must support mesh protection and restoration mechanism.
--) System must support SLA (Service Level Agreement), Provider must fulfill
table ..
Table .: Specification of SLA
Protection/SLA levels Protection type Switching time delay









-) System management
--) System management must support the following functions according to ITU-T
M:
a) Fault Management
b) Configuration Management
c) Accounting Management
d) Performance Management

e) Security Management
--) Connection between EMS (Element Management Systems) and NEs (Network
Element) must be according to SNMP (Simple Network Management
Protocol) protocol with Q interface according to ITU-T G. with Rj-
connector (/ base-T) over LAN network.
--) System must support RS-, LAN, IEEE, USB interface for
connecting to LCT (Local Craft Terminal).
--) All management system capabilities must also be performed by LCT.
--) System must be remotely controlled and managed according to ITU-T Q.
and ITU-T Q..
--) System must have the capability of being locally managed with personal
computer by F interface.
--) System must use DCC (Data Communication Channel) channels for local
maintenance and management for at least NEs.
--) System must be capable of being connected to LAN and WAN for NE
management.
--) System OS (Operating System) must be fully redundant.
--) Local access to NE must not be possible without network management
permission.
--) System management must have suitable GUI (Graphical User Interface)
software for viewing physical structure, provisioning and management of NE.
--) System software must have suitable online help for operating, maintenance
and troubleshooting.
--) System software must have user management features such as operation class
and user accessible levels.
--) System software must be able to view block diagram and functional view of
system components.
--) System management database information must be the same as NE contents
and information.
--) System software must be capable of identifying the following information for
all of the system components:
a) Card name and type
b) Card serial number
c) Software version
d) Hardware version
e) Date of production

f) Guarantee expiration date
--) Provider must notify any additional information besides above items.
--) System software must be capable of configuring system components
according to the following functions:
a) Enabling and disabling of any interface
b) Wavelength tuning of any tunable optical interface
c) Adjusting optical amplifier gain
d) Adjusting optical interfaces output power
e) Configuring signal structure and overhead bytes
f) Switch over configuration
g) Plug and Play feature
--) System software must record history log of faults and alarms types, event
time, fault severity and probable causes of them.
--) System software must indicate unit operation status by a suitable GUI.
--) System must have alarm signals and control signals for housekeeping,
provider must notify the maximum number of them.
--) System must be able to define housekeeping alarms for any monitoring
points.
--) System software must be able to display the number of housekeeping alarms
with the severity of them.
--) System software must be capable of controlling and monitoring other systems
such as battery and rectifier using housekeeping alarms.
--) System software must have order wire channel fault management.
--) System software must be able to define and classify different alarm severities.
--) System software must be able to implement filtering on the following event
fields.
a) All events
b) Some of events
c) Source of events
d) Duration of events
e) Severity
f) Date & time
g) Friendly name

h) Alarm type
i) Probable cause
j) Reservation status
k) Cleaning status
l) Acknowledge Status
m) Correlated notification flag
n) Repetition counter
--) System software must have audible and visual alarms.
--) System software must be able to define and adjust alarms threshold level.
--) System software must be able to monitor at least the following alarms by
LCT and report them to the network management:
a) Loss of Frame
b) Loss of Multi frame
c) AIS (Alarm Indication Signal)
d) High BER
e) Loss of pointer
f) Loss of sync
g) RSOH adapter failure
h) MSOH adapter failure
i) Loss of signal
j) Mismatch of signal label
k) Loss of timing references
l) Mismatch of path trace
m) Fail of cross connection
n) Laser failure
o) Power Supply Failure
p) High Temperature alarm
q) Fan failure
--) System software must be capable of defining local user accessible level by
the network manager.
--) System software must be fully protected against any type of virus with
upgradeable virus database.

--) System must be able to create all performance reports according to ITU-T
G..
--) System must be able to create report for threshold levels and alarm indication
status due to threshold crossing.
--) System must be able to implement performance monitoring for all
measurable parameters in minute and hour periods.
--) System must be able to display performance monitoring results for all
sections and conditions.
--) System software must be able to measure transmission output and receiver
input power level for all optical interfaces and environment temperature.
--) System must be capable of implementing performance measuring on several
ports simultaneously; provider must notify the simultaneous performance
measure list.
--) Provider must notify limitation cases in the simultaneous performance
measuring.
--) System management must be able to record history log for all NE operators
in each access level, this log must contain: operator name, connection
date/time and its activity descriptions.
--) Provider must notify NE information storage media type and its
replaceability, replaceable ability storage media is preferred.
-) Safety
--) System must support safety requirements according to IEC
Recommendation.
--) For avoiding any probable hazards for operators, provider must declare all
safety comments.
--) System must have complete grounding facility to avoid any hazards due to
thunderbolt, short circuit and electrical shock.
--) All electrical parts must be protected against short circuit and overloads.
--) System must support optical safety requirement according to IEC -, IEC
- and ITU-T G. Recommendations.
--) All connectors of optical monitoring points and unused optical ports must be
protected by suitable reusable caps against dust.
--) System must have suitable caution labels for all optical sources.
--) System must check optical link in adjustable period activation time for
automatic laser restart.
--) Provider must fulfill table . for ALS (Automatic Laser Shutdown) and
APSD (Automatic Power Shutdown).

Table .: Time constants for automatic shutdown
Time constant Reference points Value
Terminal response activation time MPI-R to MPI-S
Terminal deactivation time MPI-R to MPI-S
BA activation time R' to MPI-S
BA deactivation time R' to MPI-S
PA activation time MPI-R to S'
PA deactivation time MPI-R to S'
Pulse length for manual and automatic restart N/A
Pulse repetition time for automatic restart N/A
Reference points S' and R' are specified in ITU-T Rec. G..
BA=Booster Amplifier
PA=Pre-Amplifier
MPI-R=Main Path Interface reference point-Receive
MPI-S=Main Path Interface reference point-Source


Chapter: Four


) DWDM Technical Specifications
-) General Consideration
--) The supplied DWDM system must be in accordance with ITU-T Rec. G..
--) This Technical Specification is used for Gbit/s DWDM equipment and
the system for Optical Fiber Cable (OFC) telecommunication trunk project.
--) Application Wavelength Range of the DWDM system must be considerd in the
C & L bands.
--) The Maximum Distance between Optical Line Terminal should be stated for
different cases.
--) The Maximum span length should be stated for different cases.
--) The Operating Wavelength range for supplied DWDM equipment must be in
accordance with ITU-T G.. standard.
--) The nominal central frequencies for supplied DWDM equipment must be
according to ITU-T G...(ITU-T Grid)
--) The proposed DWDM equipment should work with different types of single
mode fibers( G., G., G., G. and G.) according to
suggested route plan (Appendix ).
--) The supplier should explain the functional structure of its DWDM system for
providing optical transport Network interface with requirements of ITU-T
G. recommendation.
--) The bidder should state the capability of its DWDM system for optical
cross-connect applications. (If Applicable)
--) The bidder should state the possibility for construction of optical intelligent
networks according to the following Requirement:
a) ITU-T G., G. and G.(ASTN / ASON).
b) GMPLS based Protocols.
c) OIF-UNI, I-NNI and E-NNI.

--) The supplier should describe the possibility of the system to configure OVPN
and explain the features of the plan for the future developments.
--) The Supplier should specify the following parameters for development:
a) Maximum Channel Numbers
b) Minimum Channel Spacing.
c) Maximum Channel Capacity.
d) System Bandwidths.
--) The supplier shall specify the available types of protection schemes:
a) OSNC
b) OMSP Ring
--) The Supplier shall state the possibility of incorporation new devices:
a) Raman Amplifire
b)Tunned Laser Transponder
c) Combining.
--) The supplier shall state the specific code technology that is used in the
DWDM equipment working with the fiber G.. And the supplier shall state
how to overcome the nonlinear effect caused by the fiber G..
--) The supplier shall consider the transfer technical knowledge of DWDM
system.
--) In the future, the proposed DWDM shall be upgradable to support Gb/s
traffic channel without any impact on the existing traffic. The supplier shall
fully describe in technical details.
-) System Applications
The supplied DWDM system must be applicable in the following equipments:
a) Optical terminal (De) multiplexer equipment.
b) Optical amplifier equipment.
c) Optical add and drop multiplexer equipment.
d) Regenerative terminal.
--) Optical Terminal (De)Multiplexer Equipment(OTM)
---) The OTM shall implement the functions as described in ITU-T Rec. G.
section .. and shall include the following:
a.Interface to/from optical line terminal equipment
b.Wavelength mux/demux

c.Booster/pre-amplification
d.Dispersion compensation device
e.Optical supervisory channel termination
f.Optical performance monitoring
---) The number of spans between two OTM without Regenerator, should be clearly
stated in the offers.
---) The application codes systems with line amplifiers should be given in the
proposal (compatible with ITU-T standard G.).
---) The procedure for expanding and upgrading of the system to increase the number
and capacity of channels should be clearly stated.
---) The attenuation ranges for application codes of multi-channel systems with line
amplifiers should be acknowledged in the offers and compatible with ITU-T standards
(G.).
---) Details of the transmitter-receiver system including any type of optical
amplifiers that will be used, should be given in the offers.
---) The RX- Transponder should support R signal regeneration.
---) The supplier should state the parameters for transponder (parameter definition
according to ITU-T G.

, G.

, Etsi ETS

standards).
---) The supplier shall state the maximum distance between (De)multiplexer
Equipments without using optical regenerator in the path.
--) Optical Add/Drop Multiplexer Equipment
---) The OADM to be offered shall be in accordance with ITU-T Rec. G. and
include the following functions:
a) Line amplification
b) Pre/post dispersion compensation for the add/drop channels
c) Optical channel add/drop module
d) Optical supervisory channel termination
e) Optical performance monitoring
---) The wavelength grid and selection of channel wavelengths for OADM should be
compatible with ITU-T Rec. G. G...
---) The maximum number of wavelengths that can be added/dropped
simultaneously should be stated.
---) The supplier shall state any need to pre/post amplification for using in the
OADM terminal.

---) The supplier shall state any need to optical attenuators for using in the OADM
terminal.
---) It should be clear whether the pass through wavelength are subject to R/R
regeneration.
---) The supplier Shall state the maximum number of OADM stations between the
final terminals without regenerator.
---) The supplier should state the maximum span lengths between two successive
OADM terminals
--) Optical Amplifier Equipment (OA)
---) The OA shall implement at least the following functions:
a) Line amplification
b) Dispersion compensation device
c) Optical Supervisory Channel termination
d) Optical performance monitoring
---) The type of amplifiers proposed for the given network topology (pre-amplifiers,
power amplifires-boosters, in-line amplifiers) should be stated in the offers.
---) In order to allowing insertion of DCM

s between two stages of amplification,

the optical amplifiers should be Erbium-dopped type dual-stage (pumping laser
wavelengths preferably at and/or nm).
---) The maximum number of cascaded in-line amplifiers per span should be
mentioned in the offers.
---) The supplier shall state the capability of system in keeping constant the output
power level and the necessary procedure.
---) The supplier shall state the parameters for in-line amplifiers (parameter
definition according to ITU-T G., G., Etsi ETS standards).
--) Regenerative Terminal
---) Regenerative terminal must be capable to regenerate electrically the optical
channel.
---) In addition to (de)multiplexer terminals, regtenerative terminals should contain
optical transmitter and receiver equipment for OEO

procedure.

Dispersion Compensation Modules

OEO: Optical-Electrical-Optical

-) Equipment Safety
--) The power supply unit must be protected in + manner in each section or shelf (if
there isnt specific design for independent power on board).
--) The protection scheme for optical interfaces must be configurable as +.
--) The protection scheme for electrical interfaces must be configurable as :N.
--) Protection parts must be switched automatically with defective section without
interruption in system performance.
--) The supplier should state the type of protection :N for different types of electrical
interface units.
--) It isnt permitted to use external connection on PCB layout.
--) The supplier shall apply sufficient fuses to control current, voltage and response
time of system.
-) Network Topology
--) The supplied DWDM systems should work with different network architectures
such as point to point (point to multipoint), star, chain, ring and mesh.
--) By using mesh topology, it must be possible to protect all kind of stations and
paths.
-) Additional Requirements
--) Optical supervisory channel
---) The supplied DWDM equipment should support OSC

to convey the
information of network management.
---) OSC shall not restrict the span space between adjacent OAs.
---) OSC should normally work even during the OLA failures.
---) The OSC data should be partitioned, have R function ability and be bi-
directional in the OLAs.
---) OSC should be able to add or drop any supervisory information at each OLA
station, so that it could extract the received information correctly and add the new
information to the OSC.

Optical supervision channel

---) OSC shall realize communication between regeneration sections.
---) OSC shall have self-management function. The supplier should explain its
method and the capability.
---) The wavelength of OSC should be nm. If other wavelength is used
for OSC, the supplier must explain the reason and the relevant factors considered.
---) The OSC line rate shall be . Mbit/s and the frame format shall be in
accordance with ITU-T Rec. G. , If the bit rate of OSC is not Mb/s, the supplier
should explain the reason and the relevant factors considered in detail.
---) OSCs physical interface and frame structure should be according to ITU-T
G. and G. separately. The supplier should indicate the OSC bit rate, frame
structure and the application of each byte in table mode.
---) The BER for OSC should be no less than E
-
.
---) It shall be possible to control the output power level of OSC by management
software.
---) The supplier should state the parameters listed in table (-) for OSC.
Table -: The Supervisory Channel Characteristics
Clause Parameter Max Min
Nominal Bit Rate (Mbps)

Coding

Transmitter at Reference Point S
Central Wavelength (nm)
Type of Source
Spectral Characteristics: RMS Width@-dB (nm)
Mean Launched Power (OFA type) (dBm)
Extention Ratio (dBm)
Optical Path
Attenuation Range (dB)
Dispersion Range (ps/nm)
Reflectance Range (dB)
Receiver at Reference Point R
Sensitivity (dBm) @ BER=
-

Overload (dBm) @ BER=
-

Optical path penalty (dB)
Receiver Reflectance (dB)

Attention: the characteristics must be given for three different types of fiber (SMF, DSF
and NZDSF) according to the specified route plan.
--) Order Wire Channel
---) DWDM equipment must be equipped with order wire system to provide
operator's communication channel among other existing stations in the network for test,
maintenance and commissioning.
--
-

) Order wire system should provide three different calls:

(a) Selective address calling. The number of address is no less than .
(b) Group calling.
(c) Broadcasting calling.
---) At least two order wire channel must be provided for communication between
the neighbour stations and different directions.
--
-) At least one byte of OSC should be used to provide an order wire
communication channel for the purpose of communicating among optical multiplex
sections; and another one byte should be used for the purpose of communicating among
optical amplifier sections in one optical multiplex section. At least another one byte
should be used to provide a user's channel.
--
-) The supplier should provide simultaneously the regeneration section orderwire
byte (E) used as local orderwire channel for voice communication between regenerators
and the multiplex section order wire byte (E) to be used by operators.
--
-) EOW should have multi-directional communication ability.
---) It must be possible to consider a specific number for each station in the order
wire channel.
---) The communication between NG-SDH and DWDM systems must be provided
from its order wire channel.
---) The supplier should state other system facilities such as answering machine, etc.
--
-) The supplier should state the parameters listed in table (-) for OW.

Table -: Order Wire Channel Characteristics(OW)
Clause Parameter Value
Number of O.W channels at the far-end terminal

Number of directions in O.W channel


Number of O.W channels at intermediate terminal

Type of O.W interface

Parameter Max Min
Speech output level (dBm)

Speech input level (dBm)

Speech output power (w)
-) System Components Characteristics
--) TX / RX Transponder
---) The supplier should provide transponders for operating in the nm
windows. (the system must support nm window if it is necessary).
---) The proposed transponders should be capable of receiving the optical signals
from client side with bit rates up to Gbps (STM-, ).
--
-) The supplier should state transponders capability for providing the following
SDH optical tributary interfaces according to the Rec. ITU-T G. and/or ITU-T G..
STM-(SDH) STM-(SDH) STM-(SDH) STM-(SDH) STM-(SDH)
---) Besides SDH service interface, the DWDM system shall support the following
data interfaces in accordance with Rec. ITU-T G., IEEE802 series:
Gigabit Etherner(GbE) GE WAN, LAN
GE ESCON, Ficon, FC
In case, one or more of the above mentioned SDH-interfaces currently are not supported
by the proposed system, the supplier shall provide a schedule when this interface will be
available.
---) The supplier should state the types of optical connectors used in transponders
according to the following table:
MU ST
E
FDDI DIN SC FC
--
-) Each transponder should provide tunable laser for covering all working
channels.(C or L Band).

---) The supplier should state procedures for stability, tunability and control of
output optical power level in TX transponders.
--
-) It should be guaranteed that system's BER is <

E
-
in SDH-REG terminal and
the supplier shall state the maximum number of transponders that can be cascaded without
exceeding the BER of

E
-
in the system.
--
-) The proposed optical transponders (including SDH, GE, FE and Arbitrary
Rates) have to support the R function (Retiming, Regenerating, and Reshaping).
--
-) Forward error correction (FEC) function:
The DWDM system shall be compliant with G. in the use of forward error correction.
Since G. allows the use of proprietary FEC systems, the supplier shall state whether
they implement proprietary or standard based FEC systems on the DWDM channels and
illustrate the improvements over non-FEC and G. standard FEC systems.
--
-) The supplier should indicate the improvement of BER and optical power
budget.
--
-) The OTU

with FEC function should also monitor, RSOH byte (B, J) and
MSOH byte (B), non-intrusively.
--
-) All the transponders with T-MUX function should support replaceable
interface (GBIC or SFP) on client side.
---) The supplier should state system capabilities for OTN

applications according
to international standards.
---) The supplier should state the following additional features provided in
transponder according to ITU-T Rec. G. and G..
a) The equipment capability for multiplexing SDH signals (STM- ~ STM-) in client
side and providing one optical channel in DWDM side for transport at G.
b) The equipment capability for combining GE signals in the client side and providing
one optical channel in DWDM side for transporting at G. The supplier should describe
the multiplex structure.
c) The equipment capability for combining GE signals in the client side and providing
one optical channel in DWDM side for transporting at .G. The Supplier should
describe the multiplex structure.

Optical Transponder Unit

Optical Transponder Network

d) The equipment capability for using both GE PHY WAN and GE PHY LAN
service interfaces.
e)The system capability for monitoring supervisory channel should be stated to identifiy
the fault location and severity.
---) The supplied transponder must have sufficient control circuits for protection
against applied out of band input power level
---) The supplier should complete parameter values listed in table - & -.

Table -: Optical TX Transponder Characteristics [ITU-T G.]
Clause Parameter Max Min
Channel Input power Range (dBm)

Channel Output power Range (dBm)

Input Return Loss(dB)
Input Wavelength Range (nm)

Output Wavelength Range (nm)


Frequency Stability

Modulated Spectral Bandwidth
Extention Ratio (dBm)


Output Channels Wavelength (nm)
distance between Adjacent Channels (nm)
Bit Error Rate (BER)

Table -: Optical RX. Transponder Characteristics [ITU-T G.]
Clause Parameter Max Min
Channel Input power Range (dBm)

Channel Output power Range (dBm)

Input Wavelength Range (nm)
Output Wavelength Range (nm)
Frequency Stability
Sensitivity (dBm) @ BER=
-

Overload (dBm) @ BER=
-

Input Dispersion Tolerance


Channel OSNR
Bit Error Ratio (BER)
Optical Reflectance (dB)

--)Optical (De)Multiplexer
---) The supplier should specify the minimum channel spacing when the maximum
number of channels are applied.
--
-) The supplier should provide the OM/OD modules with channels in the first
phase of the project.
---) The supplier should specifiy the maximum and minimum number of channels
that can be used.
--
-) The supplier should indicate whether there are special protection schemes or
termination methods for optical channels if some of them are not in-use.
---) The supplier should state protection procedures for optical (de) multiplexer.
---) The system performance must not decrease when the total capacity is not in use.
---) The supplier should specify (de)multiplexed channel wavelengths.
--
-) Because there are different types of optical (de)multiplexer, the supplier should
indicate the type of supplied optical (de) multiplexer.
---) The supplier should complete parameter values listed in table - & -.


Table -: Optical Multiplexer Characteristics [ITU-T G.]
Clause Parameter Max Min
Channel insertion loss (dB)

Channel insertion loss deviation (dB)

. (dB), Channel Bandwidth (nm)
(dB), Channel Bandwidth (nm)
Reflectance (dB)
Polarization dependent loss (PDL)

(dB)
Polarization dependent reflectance (dB)
Allowable input power (dBm)


Polarization mode dispersion (PMD) (ps)
Channel frequency range (GHz)
Ripple (dB)
Adjacent channel isolation (dB)
Non-adjacent channel isolation (dB)
Bidirectional (near-end) isolation (dB)
Bidirectional (near-end) crosstalk attenuation (dB)

Table -: Optical DeMultiplexer Characteristics [ITU-T G.]
Clause Parameter Max Min
Channel insertion loss (dB)

Channel insertion loss deviation (dB)

. (dB), Channel Bandwidth (nm)
(dB), Channel Bandwidth (nm)
Reflectance (dB)
Polarization dependent loss (PDL)

(dB)
Polarization dependent reflectance (dB)
Allowable input power (dBm)


Polarization mode dispersion (PMD) (ps)
Channel frequency range (GHz)
Ripple (dB)
Adjacent channel isolation (dB)
Non-adjacent channel isolation (dB)
Bidirectional (near-end) isolation (dB)
Unidirectional (far-end) crosstalk attenuation (dB)



--)Optical Add/Drop Multiplexer
---) Reconfigurable OADM multiplexers (R-OADM)
a) The R-OADM shall be capable of adding and dropping channels with wavelength
re-use.
b) The R-OADM shall be fully remotely configurable.
c) The R-OADM shall be capable of add/dropping at least
%
of channels.
d) The supplier shall state the details of the architecture for the R-OADM.
---) OADM at fixed wavelengths means the OADM that can add/drop several fixed
wavelengths. The number of add/drop wavelengths should be scalable and the OADM
should support any wavelength add/drop.
---) The supplier shall describe also the minimum and maximum wavelength number
that the OADM can add/drop.
---) The supplier shall indicate the central frequency of the wavelengths.
---) The supplier shall complete parameter values listed in table

.
Table -: Optical add/drop multiplexer (OADM) Characteristics [ITU-T G.]
Clause Parameter Max Min
Input to output, Channel insertion loss (dB)
Input to drop, Channel insertion loss (dB)
Add to output, Channel insertion loss (dB)
Channel insertion loss deviation (dB)
Reflectance (dB)
Polarization dependent loss (PDL) (dB)
Type of OADM subsystem
Number of add/drop/through channels
Type of passband profile (flat-top or Gaussian)
Channel wavelength range (nm)
Channel frequency range (GHz)
dB passband width (nm)
dB passband witdth (nm)
Ripple (dB)
Input to drop, Adjacent channel isolation (dB)
Input to drop, Non-adjacent channel isolation (dB)
Input to output, Channel extinction (dB)
Allowable input power (dBm)


Polarization mode dispersion (PMD) (ps)

---) The supplier should provide detailed technical material on OADMs type,
manufacture, functional block diagram, etc.
---) The application of OADM should not influence the DWDM span number and
span space.
--) Optical Amplifier
---) The optical amplifier (include OBA

, OLA

and OPA

) used in DWDM system

should meet the requirements in ITU-T Rec. G. and other correlative ITU-T
recommendations.
---) The supplier shall indicate the technical solution for flatting OAs gain curve and
OAs functional block diagram.
---) Automatic Amplifier Gain Balance:
a) The supplied amplifiers using in DWDM system should have the function of
automatic power balance such as gain lock to guarantee system performance if
an accidental wavelength add/drop occurred.
b) The supplier should illuminate the process of automatic amplifier gain balance in
detail and system stable time.
c) During the process of automatic amplifier gain balance, working channels should
not be influenced(without break or BER).
---) The supplier should state whether Raman amplification is available in the
DWDM systems. If available,details should be stated including the diagram of the
amplification and the technical specifications.
---) The supplier Shall state capability of ROPA

for increasing span length, if it is

provided.
---) The supplier should indicate the technical solution for flatting optical power
level in transmision line.
---) The supplier should state the parameters listed in table (-), (-) & (-) for
all types of OA (OPA, OBA,OLA).

Optical Booster Amplifier

Optical In Liner Amplifier.

Optical Pre Amplifier

Remote Optically Pumped Amplifier: (ROPA)

Table -: Optical Booster Amplifier Characteristics [IEC -]
Clause Parameter Max Min
Channel Allocation (nm , THz)
Channel Input Power Range (dBm)
Total Input Power Range (dBm)
Channel Output Power Range (dBm)
Maximum Total Output power (dBm)
Channel addition /removal gain response (dB)
Multichannel gain variation (dB)


Channel signal Spontaneous noise figure (dB)
Maximum reflectance tolerable at output
Maximum reflectance tolerable at input
Input reflectance
Output reflectance
Pump leakage to input( for OFA)
Gain ripple (for SOA)

Gain Clamping
Input Power Range (dBm)
Lasing Wavelength (nm)
Laser Power Leakage (dBm)
Table -: Optical PreAmplifier Characteristics [IEC -]
Clause Parameter Max Min
Channel Allocation (nm , THz)
Channel Input Power Range (dBm)
Total Input Power Range (dBm)
Channel Output Power Range (dBm)
Maximum Total Output power (dBm)
Channel addition /removal gain response (dB)
Channel signal Spontaneous noise figure (dB)
Channel Gain (dB)


Multichannel gain variation (dB)
Maximum reflectance tolerable at output
Maximum reflectance tolerable at input
Input reflectance
Output reflectance

Clause Parameter Max Min
Pump leakage to output( for OFA)
Gain ripple (for SOA)

Gain Clamping
Input Power Range (dBm)
Lasing Wavelength (nm)
Laser Power Leakage (dBm)

Table -: Optical In Line Amplifier Characteristics [IEC -]
Clause Parameter Max Min
Channel Allocation (nm , THz)
Channel Input Power Range (dBm)
Total Input Power Range (dBm)
Channel Output Power Range (dBm)
Maximum Total Output power (dBm)
Channel addition /removal gain response (dB)
Multichannel gain variation (dB)
Multichannel gain Change Difference (dB)


Channel signal Spontaneous noise figure (dB)
Maximum reflectance tolerable at output
Maximum reflectance tolerable at input
Input reflectance
Output reflectance
Multicannel gain tilt (dB/dB)
Cannel gain (dB)
Gain ripple (for SOA)

Gain Clamping
Input Power Range (dBm)
Lasing Wavelength (nm)
Laser Power Leakage (dBm)
Polarization mode dispersion (PMD) (ps)

--) Optical Attenuator
--
-

) The supplier is not allowed to use fixed optical attenuators among units out of
system.
--
-

)Setting the attenuation in optical attenuators must be possible by management

software.
--
-

) The supplier shall state the parameters listed in table (-) for optical
attenuators.

Table -: Optical attenuator Characteristics [ITU-T G.]
Clause Parameter Max Min
Insertion loss

(dB) (fixed attenuator)
Reflectance (dB)
nm window, Operating wavelength range
(nm)

nm window, Operating wavelength range
(nm)

Polarization dependent loss (PDL) (dB)
Polarization dependent reflectance (dB)
Allowable input power (dBm)


Polarization mode dispersion (PMD) (ps)
Insertion loss tolerance (dB)
Attenuation range (variable attenuator) (dB)
Incremental attenuation (variable attenuator) (dB)

--)Gain Flattening Filter
---) The gain equalization technique in the optical amplifier module must be
indicated by supplier in details.
---

) The supplier should state the parameters listed in table (

-
) for optical gain
flattening filter.

Table -: Optical Gain Flattening Filter Characteristics [ITU-T G.]
Clause Parameter Max Min

Insertion loss

(dB)

Reflectance (dB)

Operating wavelength range (nm)

Polarization dependent loss (PDL)
(dB)


Polarization dependent reflectance
(dB)


Allowable input power (dBm)



Polarization mode dispersion (PMD)
(ps)


--) Optical Isolator
---) If optical isolator is used, the supplier shall state the parameters listed in table
(-).

Table -: Optical Isolator Characteristics [ITU-T G.]
Clause Parameter Max Min
Insertion loss (dB)
Backward loss (isolation)
Reflectance (dB)
nm window, Operating wavelength
range

nm window Operating wavelength range
Polarization dependent loss (PDL)

(dB)
Polarization dependent reflectance (dB)
Allowable input power (dBm)


Polarization mode dispersion (PMD) (ps)

--) Chromatic Dispersion Compensator
---) The supplied chromatic dispersion compensator or DCM

shall conform to
ITU-T Rec. G., G. and other correlative ITU-T recommendations.
---) The supplier shall describe technical solution for compensation of chromatic
dispersion.
---) The supplier shall describe DCFs position in DWDM system.
---) The supplier should state the parameters listed in table (-) for chromatic
dispersion compensator.

Dispersion Compensation Module

Table -: Passive (chromatic) dispersion compensator Characteristics [ITU-T G.]
Clause Parameter (km of G. equivalent compensation) Max Min
Insertion loss . (dB)
Insertion loss (dB)
Insertion loss . (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Insertion loss (dB)
Reflectance (dB)
Operating wavelength range (nm)
Polarization dependent loss (PDL)

(dB)
Polarization dependent reflectance (dB)
Allowable input power (dBm)


Dispersion over operating wavelength range .(ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range .(ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Dispersion over operating wavelength range (ps/nm)
Polarization mode dispersion (PMD) (ps)
Polarization mode dispersion (PMD) . (ps)
Polarization mode dispersion (PMD) (ps)

Clause Parameter (km of G. equivalent compensation) Max Min
Polarization mode dispersion (PMD) . (ps)
Polarization mode dispersion (PMD) (ps)
Polarization mode dispersion (PMD) (ps)
Polarization mode dispersion (PMD) (ps)
Polarization mode dispersion (PMD) (ps)
Polarization mode dispersion (PMD) (ps)
Polarization mode dispersion (PMD) (ps)


Polarization mode dispersion (PMD) (ps)

--) Polarization Mode Dispersion Compensator
---) If PMD compensator is used, the supplier shall describe technical solution for
compensation.
---) If PMD compensator is used, the supplier shall state the parameters listed in
table (-).
---) The supplied PMD compensator shall conform to ITU-T Rec. G.
recommendations.


Table -: Parameters PMD Compensator at Receiver [ITU-T G.]
Claus
e
Parameter Max Min
Fiber Type:
Parameters related to optical power
Minimum total input power(dBm)
Maximum total input power(dBm)
Maximum reflectance at the input port (dB)

Polarization dependent reflectance at the input port(dB)


Minimum channel input power (dBm)


Maximum channel input power (dBm)


Optical Signal Characteristics


Minimum bit rate (Gbps)


Maximum bit rate (Gbps)


Modulation format (RZ, NRZ)


Maximum number of channels


Nominal channel central freqencies (THz)


Channel spacing (GHz)


Maximum central frequency deviation (GHz)

Polarization independent parameters of the preceding optical path

Minimum amount of accumulated Chromatic Dispersion (ps/nm)


Maximum amount of accumulated Chromatic Dispersion (ps/nm)


Polarization parameters at the input port


Maximum average input DGD (ps)


Maximum instantaneous input DGD (ps)


Maximum polarization rotation speed (rad/ms)


Maximum DGD rate of change (ps/ms)


Maximum magnitude of the PCD (ps

)


Maximum magnitude of the depolarization (ps

)

DWDM transmission system parameters applied to each channel

Maximum OSNR penalty due to DGD (dB)


Minimum PMDC receiver sensitivity (dBm)



--) Optical Connector
---) The supplier shall state the type of the optical connectors adopted in the
equipment.
---) The supplier should state the type of constructing materials.
---) Lifetime: the performance should not be degraded after more than times
of insertion and removal.
---) The supplier shall state the parameters listed in table (-) for optical
connectors.

Table -: Optical connector Characteristics [ITU-T G.]
Clause Parameter Max Min
Insertion loss (dB)
Reflectance (dB)
nm window, Operating wavelength range

(nm)
nm window, Operating wavelength range

(nm)
Polarization dependent loss (PDL)

(dB)
Polarization dependent reflectance (dB)
Allowable input power (dBm)


Polarization mode dispersion (PMD) (ps)
--) Optical Termination
) The supplier should state the parameters listed in table (-) for optical terminations.
Table -: Optical termination Characteristics [ITU-T G.]
Clause Parameter Max Min
Reflectance (dB)
nm window, Operating wavelength range

(nm)
nm window, Operating wavelength range

(nm)
Polarization dependent reflectance (dB)
Allowable input power (dBm)

-) Power Consumption
--) The supplier shall state the maximum power consumption of units listed in
table(-).

Table -: Maximum Power Consumption of Units (watt)
Claus
e
Parameter Max
Tx Transponder
Rx Transponder
Optical Multiplexer
Optical Demultiplexer
Optical Pre-Amplifier

Optical In-Line Amplifire


Optical Booster Amplifire


Optical Add/Drop Multiplexer


Chromatic Dispersion Compensator


PMD Compensator


Management System


Speech Order Wire


Auxiliary Units


--) The supplier shall state the mean power consumption for different kinds of
equipments listed in table (-).
Table -: Mean Power Consumption of Equipments (watt)
Claus
e
Parameter Max
Optical Terminal (De)Multiplexer Equipment
Optical Amplifire Equipment
Optical Add and Drop Multiplexer Equipment
Regenerative Terminal
-) System Management
--) The supplied DWDM system should be equipped with sufficient management
software for physical structure monitoring.
--) It should be possible for the management system, to view status, type and access
level of network users in the graphical user interface.
--) System software should exhibit block diagram and function view of equipment
units.

--) There shouldnt be any difference between information of the system and network
management.
--) Configuration Management
---) In the management software, it should be possible to configure system
components according to the followings:
a) Activation or inactivation of (de)multiplexer channels by Transponder.
b) Tuning of transponder wavelengths in operating range.
c) Possibility of adding / dropping optical channels.
d) Possibility of protection for optical wavelengths.
e) Capability of gain adjusting in optical amplifire
f) Capability of adjusting in optical attenuator.
g) Capability of adjusting optical input and output power level at each port.
---) It should be possible to recognize supervisory channel by NSAP or Mac.Address.
---) It should be possible to communicate with management system through serial or
parallel ports.
---) Software system shall include the followings:
a) Card serial number
b) Part code
c) Software version
d) Hardware version
e) production date
f) End of guarantee date
--) Fault Management
---) Software should support the followings:
a) Record of path faults: This report should include type, time, severity, possible cause
and deletion of fault.
b) Records of system's component faults
---) Software should be able to show status of each part , by existing monitors.
---) For supporting housekeeping, supplier shall equip system for minimum alarm
signals and control signals.

---) It should be possible to define alarms for monitoring sections.
---) It should be possible to show number of alarms with relevant classes.
---) System should be able to supervise sub sytem equipments such as power supplies
( battery and rectifier) and in the case of failure, create sufficient alarms.
---) Fault management should be performed on supervisory and orderwire channel.
---) In case of break in each of (de)multiplexed or add/drop multiplexed channels, It
should be possible to send sufficient alarms to the management system.
--) Security Management
---) Facilities to control operators which can access to the different levels of
management system should be provided by the network manager.
---) There should be a security management software to prevent viruses from entering
in to the system.
---) It shall be possible to provision and control permormance of the system
components by using local craft terminal. The connection to the system should be
provided by RS- cable and modem.
--) Alarm Management
---) Software management should be equipped with sufficient graphical user interface
to observe different statuses of the system components and their performance.
---) It should be possible to provide alarm signals in two manners: audible and visual.
---) System shall be able to show control and house-keeping alarm singnals.
---) Software shall be able to filter and adjust alarm levels.
--) Performance Management
---) It should be possible to measure parameters of performance monitoring in
periods of not more than minutes and hours.
---) It should be possible to view performance of different units ( in service or out of
service).
---) Management of quality decrease in optical channels should be considered with
fault reports and sufficient alarms.
---) It should be possible to measure power, voltage, current and temperature and
prewarning due to end of life time for all active optical components (laser, optical
detector).

---) It should be possible to control bias and modulation current of lasers in two
manners: hardware and software.
---) There should be performance history.
--) System Management Interface
---) The interface between DWDM line system and EM should be Qx interface. And
the interface information model should be the subset of ITU-T G.. The supplier should
provide the detailed standard material of its protocol stack and information model.
--
-) The interface between DWDM EM and higher-level network management
system should be CORBA interface. NMS should support CORBA interface compliant
with TMF MTNM V. (TMF//)
--
-) An NMS alarm arises due to the failure concerning the NMS itself. For example,
the following NMS alarms should be supported: communication interruption between
NMS and NEs, continuous NMS login failures, threshold-crossing event of NMS database
space, and threshold-crossing event of remaining disk space on NMS computer.
--
-) NMS should manage end-to-end DWDM wavelength.
--
-) Alarm management and performance management of circuits should be
supported.
--
-) The signal flow diagram should be provided. A DWDM site (for example, an
OADM site) can contain multiple subracks, so the signal flow of optical NEs in this site
can be very complicated. In this case, a figure is needed to display the signal flow among
the boards. This figure logically displays the processing of optical signal flow in DWDM
sites.
--
-

) Workstation interface: OTM and OA of DWDM system should have F

communication interface in order to connect with workstation. The F interface should
conform to the requirements in ITU-T Rec. V.

/V.

or V.

/V.

.
---) The internal connection between EMS and NEs should be in accordence with
SNMP v. Qx for LAN.
---) It should have RS connector with . Kbps bit rate for connecting Q
interface for monitoring terminal equipment.
---) There should be an interface for connecting to operating system.
---) Local interface: RS interfaces is needed with a compatible personal
computer and laptop for local processing and to have a connection.in . Kbps bit rate.

---) Far-end interface: RS interfaces and a compatible personal computer and
laptop are needed for local processing of network elements based on DCC channels
with a connection in . Kbps.
---) Far-end interface should be in accordance with G. recommendation for
transport management network.
---) For possibility of element management, It is nessesary to have a connection
with LAN and WAN Networks.
-) System Interfaces
--) Optical Interfaces
---) The supplier shoud provide optical interface in the client side for connection to
classic SDH and NG-SDH equipment according to REC. ITU-T G. and G.. The
supplier shall specify the corresponding bit rate. (Mbps, Mbps, .Gbps, Gbps)
---) The supplier shall provide necessary optical interfaces for connection to OTN

according to proposed capacity.
---) The supplier shoud provide optical supervisory channel with capacity (~
Mbps) working in the out of band channels wavelength range.
---) The supplier should state and provide necessary types of optical connectors
according to the following table:
f) PC e) ST d) FDDI c) DIN b) SC a) FC
--) Electrical Interfaces
---) The supplier shall provide necessary electrical Interfaces for connecting to the
management layers (system & network).
---) The supplier shall state the system capacity for connecting to the network
management.
E Gigabit Ethernet (
Mbps)
Fast Ethernet Mbps Ethernet
Mbps
---) The supplier shall state the type of necessary connection ports for management
system.

Optical Transmission Network

LAN RS USB
---) The supplier shall provide necessary interfaces for optical supervisory channel.
---) The supplier shall provide necessary interfaces for order wire channel.
-) Safety Requirements
--) Electrical Safety
The bidder shall comply:
---) Electrical and mechanical safety requirements for proposed system according
to IEC standard.
---) Safety status of the connections with other equipments (such as
telecommunication network voltage for remote alarms, housekeeping, rack lamps and
tributary connections protected, safety extra low voltage for all the other).
---) Safety labelling must be considerd at main points of the proposed system.
---) To avoid from damaging, training of personnel must be provided for electrical
safety for installation, commission and maintenance.
---) For avoiding damages due to thunderbolt, short circuit and the electrical shock
hazards, system must have grounding scheme.
---) The all of electrical sections must have protection scheme against short circuit
and overload.
---) The system must be protected against dust, insects , rodent and termite.
---) For preventing access to the control keys, the system must have sufficient
equipment for protection.
--) Optical Safety
---) The supplier shall comply optical safety requirements for proposed system
according to REC. IEC -, IEC - and ITU-T G..
---) The proposed DWDM equipment should have sufficient labels for optical
safety. The classification of hazard levels for optical sources should be in accordance with
IEC-, and ITU-T G. recommendations.
---) All optical connectors, terminating either fibers and transmitters/receivers,
should be provided with protective covers when any optical link is disconnected for
installation/test/maintenance purposes.

---) In the case of break in the fiber or disconnection in each connecting section it
is necessary to provide capability of automatic laser shut down(ALS) or automatic power
shut down(APSD) in optical amplifiers in accordance with ITU-T G.
recommendation.
---) According to REC. ITU-T G., the automatic power reduction must be
provided during seconds.
---) When the connection in the OTS

has been repaired, either an automatic or a

manual restart is necessary to restore transmission within the OTS. A restart shall not be
initiated within s from the moment of the connection interruption occurred or from
the finishing of a previous (unsuccessful) restart action, unless connectivity is guaranteed.
---) For avoiding damage, the training of personnel must be provided for optical
safety for installation, commission and maintenance.
--
-) All active optical devices should have lifetime pre-warning function. The
supplier should provide its working principle.
---) The supplier shall state time constants for automatic power shut down (ALS &
APSD) in the different sections of optical link according to table (-).

Optical Trasmission Section

Table -: Time constants for automatic shutdown [ITU-T G.]
Time constant Reference points Value Note
Terminal response activation time MPI-R to MPI-S
Terminal deactivation time MPI-R to MPI-S
BA deactivation time R' to MPI-S
BA activation time R' to MPI-S
PA deactivation time MPI-R to S'
PA activation time MPI-R to S'
Pulse length for manual and automatic restart N/A
Pulse repetition time for automatic restart N/A
NOTE The LOS condition applies even in the presence of ASE.
NOTE Reference points S' and R' are specified in ITU-T Rec. G..

-) System Technical Specifications
--) The supplier shall specify physical layer characteristics for inter-city DWDM
system according to table (-).


Table -: Inter-City DWDM System Technical Specifications [ITU-T G.]
Application code Value Units







Number of Channels
Min. Channel Spacing
Bit-Rate / Format of Channels
Max. BER
Max Span Length
Max Target Length
Operating Wavelength Range

GHz


Km
Km
nm







Transmitter Transponder Outputs
Spectral Characteristics
Mean Launched Power
Extinction Ratio
Eye Pattern mask
Central Frequency
Central Frequency Deviation


dBm


GHz
GHz






Optical Booster Amplifire output
Optical Transmit-side Crosstalk
Channel Output Power
Total Launched Power maximum
Optical Channel Signal-to-Noise Ratio
Maximum Channel Power Difference at Point output

dB
dBm
dBm
dB
dB







Optical Line Amplifier
Multichannel Gain Variation
Multichannel Gain Tilt
Multichannel Gain-change Difference
Total Received Power maximum
Total Launched Power maximum
Signal Spontaneous Noise Figure

dB
dB/dB
dB
dBm
dBm
dB





Optical Path
Attenuation
Dispersion
Maximum Discrete Reflectance
Minimum Return Loss

dB
ps/nm
dB
dB








PreAmplifire Input
Mean channel input power
maximum
minimum
Mean total input power maximum
Channel Signal-to-Noise Ratio
Optical Signal Crosstalk
Maximum Channel Power Difference at Point Input


dBm
dBm
dBm
dB
dB
dB


Optical DEMUX.Output ports
Optical Crosstalk at individual channel output ports

dB

Application code Value Units








ReceiverTransponder Inputs
Receiver Sensitivity
Receiver Overload
Optical Path Penalty
Receiver Reflectance
Optical Signal-to-Noise Ratio
Minimum Receiver Wavelength
Maximum Receiver Wavelength

dBm
dBm
dB
dB
dB
nm
nm


Supervisory Channel
Channel Wavelength

nm



Chapter: Five

) NETWORK SYNCHRONIZATION
EQUIPMENTS
-) Introduction
Synchronization requirements are defined in the two sections; network synchronization
and network synchronization management.
-) Synchronization
Synchronization network is consisting of primary reference source and secondary
reference source.
--)Primary Reference Source
---) Requirement Definition
a) The cesium primary reference source shall be based on the cesium isotope Cs to
obtain a timing reference with good long term stability according to ITU-T G..
b) The cesium primary reference source will provide synchronization reference
outputs in the form of . Mbit/s accoding to section of ITU-T G. and .
MHz according to section of ITU-T G., being software selectable.
c) The outputs can be used for the synchronization of telecommunication equipment
directly, or they can be used as input references of synchronization supply units
(SSUs).
d) The cesium primary reference source will be used with an SSU, or as a stand-alone
PRC.
---) Requirement Specification
Equipment vendor: products will only be accepted from vendors that are the original
manufacturer of the cesium physics assembly.
---) System Characteristics
----) . Mbit/s interface
a) The electrical characteristics of the . Mbit/s electrical interfaces shall conform to
ITU-T recommendation G., section , with an impedance of or ohm
(unbalanced or balanced).

b) The equipment shall be supplied with connectors for both the balanced and unbalanced
modes as standard, and it should not be necessary to purchase additional option modules
for balanced and unbalanced modes.
----) . MHz Interface
a) The electrical characteristics of the . MHz electrical interface shall conform to
ITU-T recommendation G., section , with an impedance of or ohm
(unbalanced or balanced).
b) The equipment shall be supplied with connectors for both the balanced and unbalanced
modes as standard, and it should not be necessary to purchase additional option modules
for balanced and unbalanced modes.
----) Power Supply Interface
a) The equipment shall operate via a duplicated power feeding system sharing a common
battery positive.
b) The equipment shall be capable of operating from a power supply with a nominal
voltage of - VDC (positive-earth), with a range of - VDC to - VDC.
c) The equipment must be able to tolerate occasional short duration spikes and
fluctuations that could occur on the input power supply as a result of battery charging
without any degradation of the overall system performance.
----) Alarm Interface
a) The cesium primary reference source shall provide an alarm interface for the
connection of an external alarm by means of dry changeover relay contact.
---) Functional Characteristics
----) Applications:
a) The cesium primary reference source must be capable of providing
synchronization to the following types of synchronization nodes.
- PRC nodes
- Class- transit nodes (Enhanced)
- Class- transit nodes (Standard)
- Local nodes (Exceptional cases)
b) The cesium primary reference source shall function as a PRC under normal
circumstances.
----) Performance
a) The performance and stability of the cesium primary reference source for PRC nodes
shall comply with ITU-T recommendation G. and ETSI recommendation ETS
-.
----) Accuracy
a) The following table details, the required accuracy and stability, required:

Table : Accuracy and stability requirements
Performance Measure Requirement
Accuracy, Calibrated to <= x-
Accuracy (OC OC) <= x-
Accuracy over Environment <= x-
Retrace (reproducibility) <= .x-
Averaging Time
s .x-
s .x-
s .x-
, s .x-
, s .x-
Warm-up time (typical) minutes
----) Electromagnetic Immunity
a) The cesium primary reference source shall not be susceptible to interference from other
telecommunication equipment or radio signals.
----) Number of outputs
a) A single cesium primary reference source shall provide at least two () software
selectable telecommunication outputs and one () MHz sine wave output.
----) Output types
a) The cesium primary reference source must provide two () . Mbit/s and two ()
. MHz outputs.
b) The . Mbit/s and . MHz outputs must be user selectable.
c) The . Mbit/s signal shall be structured in accordance with ITU-T
recommendation G., and shall provide signals with CCS and CAS, selectable.
d) The . Mbit/s signal shall support synchronization status messaging according to
ITU-T G..

----) Synchronization quality messaging
a) Synchronization status messaging will be a definite requirement.
b) The cesium primary reference source shall be capable of generating synchronization
status messages.
c) The synchronization quality messaging of the cesium primary reference source will be
compatible with the timing markers as specified in ITU-T recommendation G., used
by the NG-SDH transmission equipment.
----) Initialization Cold start and warm start
a) In the case of a cold start, where the cesium primary reference source has been stored in
power down conditions for an extended period of time, then it shall be fully operational
within minutes upon power-up.
b) In the case of a warm start, where the power has been off for a short period of time, it
shall be fully operational within minutes after the power has been restored.
----) Power supply unit
a) The cesium primary reference source shall have a duplicated power supply unit input,
which is + protected.
----) Power Failure
a) The cesium primary reference source must be able to tolerate an uncontrolled power
failure without damaging the equipment. When the power is restored after a total power
failure, the cesium primary reference source must automatically be restored to the
configuration it had prior to the power failure without operator intervention.
----) Power Brown-Out
a) During a power brown-out, the input voltage to the cesium primary reference source
gradually falls to less than % of the normal operating voltage. The cesium primary
reference source must be able to tolerate such a power brown-out without damaging the
equipment.

---) Physical Characteristics
----) Equipment Practice
a) The equipment practice for installation into ETSI mm racks is required. The
racks will use natural airflow in such a way that there is no need for forced air cooling of
the system. The racks shall be capable of accepting top or bottom power cable and top or
bottom signal cable entry.
----) Architecture
a) It shall be possible to re-configure the cesium on site for either front access or rear
access installation in a cabinet.
----) Earthling
a) It shall be possible to earth a signal cable on either input or output side, or on both
sides. The equipment shall have a positive power earth and a separate signal earth (rack
earth). The signal earth shall not carry any power current. The connection of the positive
power supply to the signal ground in the rack shall be an optional strapping facility.

---) General Characteristics
----) Reliability
a) The suppliers warranty on the physics assembly shall be at least (twelve) years and
the warranty on the electronic assembly shall be at least two () years.
----) Maintainability
a) The system shall require no routine maintenance or adjustment to keep it in operation,
and no external test equipment shall be required to maintain the system.
----) Operation
a) The equipment must meet the specifications when in operation, while being subjected
to normal temperature controlled locations (+C) with no forced air cooling applied.
----) Transportability
a) The equipment will be permanently mounted on a fixed position.
----) Documentation and technical information
a) The technical information supplied shall be comprehensive and adequate for the
installation, operation and maintenance of the equipment.
---) Quality assurance provisions
Bidder shall demonstrate compliance to ISO : and ISO . Quality audit
shall be made available upon request.
--) Synchronization Supply Unit
Requirement Definition
---) The synchronization supply unit (SSU), as part of the synchronization network,
shall function as a stand-alone network element, separate from any other
telecommunication equipment.
---) The SSU is needed for the intra-node timing distribution in a synchronization
network with architecture as specified in ITU-T recommendation G..
---) The SSU shall be able to select an input reference from various . Mbit/s
and . MHz sources (including GPS), using digital transmission error checking,
synchronization quality messages and input priorities as criteria.
---) It will remove phase unstabilities from the selected reference and will provide
multiple . Mbit/s and . MHz outputs.
---) In the case of a failure of all input references, SSU will maintain the output
accuracy and stability based on the internal clock modules by entering the hold-over
mode.
---) SSU shall provide the facility to perform non-intrusive performance monitoring
on a number of signals simultaneously with a measurement resolution of nanosecond.
---) A local management terminal will be used for the local management of SSU.
---) SSU will also be managed through the synchronization management network
via the remote management interface.

---) All critical elements of SSU shall be duplicated to ensure maximum
availability.
---)SSU will be configured differently to be used at the various node types,
including PRC nodes, class- and class- transit nodes and local nodes.
---) SSU shall be based on technology no older than three () years.


---) General Requirements
----) Each SSU shall have either a de-centralized power supply configuration that
is each plug-in module shall have its own power supply unit.
----) Synchronization status messaging is required. SSU shall be capable of
receiving and generating synchronization status messages via the .Mbit/s interfaces.
The synchronization quality messaging of SSU will be compatible with the timing
markers as specified in ITU-T recommendation G., used by the NG-SDH and classic
SDH transmission equipment.
----) It shall be possible to expand the output capacity of the SSU in service,
without interrupting the synchronization and without degrading the overall system
performance.
----) Upgradeability:
a) SSU shall be modularly upgradeable.
b) SSU shall be upgradeable from a Class- transit node SSU to a Class- transit node
SSU as well as from a Class- transit node SSU to a PRC node SSU without service
interruption or degradation.
c) All new releases of hardware, firmware or software shall be incorporated without
service interruption.
----)SSU shall provide a minimum availability of .% for the redundant
system. Vendor shall advise minimum number of spares and recommended MTTR to
achieve requested availability.
----) The system shall require no routine maintenance or adjustment to keep it in
operation, and no external test equipment shall be required to maintain the
system. Maintenance shall be performed on a card replacement basis so as to keep the
maintenance skill level as low as possible.
----) Interchangeability
a) It shall be possible to replace any printed circuit board without the need for re-
adjustment, interrupting the existing synchronization service and without switching off
any power supply.
b) The replacement module should be automatically re-programmed including the input,
clock, output and where applicable, the communication module without user intervention.
c) Using hardware jumpers for configuration of any module is not acceptable.
d) All modules and cards of the same type shall be physically and electrically compatible
and interchangeable between similar stations.

----) The technical information supplied shall be comprehensive and adequate for
the installation, operation and maintenance of the equipment.
----) Maintenance
a) The equipment shall provide sufficient local and remote diagnostic capability to assist
maintenance staff in fault localization.
b) Maintenance is to be accomplished by means of replacing cards or modules. The alarm
indications shall be such that the faulty card or module can be easily identified without the
need for detailed on-site diagnostics using external test equipment.

---) Requirement Specification
Products will only be accepted from vendors that are the original manufacturer of the SSU
Assembly.
---) Major components
----) Input Unit
a) The unit is responsible for the synchronization input reference selection, using digital
transmission error detection, performance monitoring, input priority tables, and
synchronization status message (SSM) levels.
b) All input ports shall provide performance monitoring capability. The capability of
monitoring the performance of all synchronization inputs simultaneously with a resolution
less than or equal to nanosecond must be implemented in the input module.
c) It is not acceptable for a separate or dedicated module to perform input performance
monitoring.
----) Local Oscillator Unit
a) This unit shall be responsible for providing the primary reference distribution for PRC
nodes and the required hold-over stability (for all other types of nodes) when there is no
input reference available to provide clock references to be used in the reference selection
process and to filter the selected input to remove phase unstabilities.
----) Communication Unit
a) The unit shall provide a sophisticated communication unit for local and remote
management.
----) Output Unit
a) The unit provides multiple synchronization outputs to be used for the synchronization
of a node.
----) Power Supply
a) Power supplies must be integrated on each SSU module.
b) It will not be acceptable to use a centralized power supply.
----) Management and communications unit
a) A dedicated communication module is to be used for the remote management of the
SSU. This includes the supervisory as well as the local and remote management
interfaces.

b) Failure of the communication module shall only result in failure in communicating with
the SSU.
c) Corrected timing outputs shall be continued unaffected in this event.
---) System Characteristics
----) . Mbit/s Interface
a) The electrical characteristics of the . Mbit/s electrical interfaces shall conform to
ITU-T recommendation G., section , with an impedance of or ohm
(unbalanced or balanced).
b) The equipment shall be supplied with connectors for both the balanced and unbalanced
modes as standard, and it should not be necessary to purchase additional option modules
for balanced and unbalanced modes.
----) . MHz Interface
a) The electrical characteristics of the . MHz electrical interfaces shall conform to
ITU-T recommendation G., section , with an impedance of or ohm
(unbalanced or balanced).
b) The equipment shall be supplied with connectors for both the balanced and unbalanced
modes as standard, and it should not be necessary to purchase additional option modules
for balanced and unbalanced modes.
----) Power Supply Interface
a) The equipment shall operate via a duplicated power feeding system sharing a common
battery positive.
b) The equipment shall be capable of operating from a power supply with a nominal
voltage of - VDC (positive-earth), with a range of - VDC to - VDC.
c) The equipment must be able to tolerate occasional short duration spikes and
fluctuations that could occur on the input power supply as a result of battery charging
without any degradation of the overall system performance.
----) Alarm Interface
a) SSU shall provide an alarm interface for the connection of an external alarm by means
of dry changeover relay contacts.
b) Major, minor and critical alarm contacts shall be provided.
c) SSU must store at least alarm/events.
----) Communication Interface
a)SSU shall provide three RS- interfaces, a -base-T Ethernet interface and a USB
interface.
---) Functional characteristics
----) Applications:
SSU must be capable of providing synchronization to the following types of
synchronization nodes:
a) SSU as primary reference clock

- PRC nodes
b) SSU as slave clock
Class- transit nodes
Class- transit nodes
----) Performance
a) The performance and stability of SSU for PRC nodes shall comply with ITU-T
recommendation G. when PRC reference inputs such as cesium or GPS are provided.
b) The performance of SSU for class- transit nodes shall comply with ITU-T
recommendation G..
c) The performance and stability of SSU for class- transit nodes and local nodes shall
comply with ITU-T recommendation G..
d) The following table specifies the accuracy and holdover stability required at different
types of nodes:

Table : Accuracy and stability guidelines for different node types
Criteria PRC node Class- transit node Class- transit node
Long term accuracy Better than
x -
x
-
(GLONASS h)
x
-
(GPS h)
x
-
( year)
Holdover
( hours at C)
N/A < x- < x-
---) Architecture
----) SSU must have a modular design.
----) All service affecting modules, including the input modules, local oscillator
modules and the output modules, shall be : protected.
----)Removing any single card from the system shall not interrupt the signal
outputs.
----) There shall be no damage to SSU if an attempt is made to insert a card in the
wrong position.
----) Configuration databases shall be stored in three different hardware modules.
---) Module requirements
----)SSU shall not have a dedicated controller unit that is responsible for the
internal management of SSU.
----) SSU shall provide the following Communication Interfaces.
a) Three RS- interfaces supporting direct serial and dial-up modem connections for
ASCII and TL.

b) One-base-T Ethernet interface supporting ASCII, TELNET, TL, NTP and SNMP
connections.
c) Integrated ASCII Terminal.
d) Telecommunication Language (TL).
e) Network Time Protocol (NTP) Server application.
f) Network Time Protocol (NTP) Client application.
g) SNMP Management Interface.
----) GPS/GLONASS Module
a) SSU will be able to accept timing references from GPS/GLONASS receiver module(s)
that must be integrated into the SSU shelf.
b) The GPS module shall not be integrated into input, controller, or local oscillator
modules.
c) The GPS module shall not require an input port to the input module.
----) Input Module
a SSU input module must accept no less than two () reference inputs.
----) Input Types
a) SSU must accept . Mbit/s and . MHz telecom inputs.
b). Mbit/s signals shall be structured in accordance with ITU-T G., and shall
accept signals with CCS or CAS, selectable, and with SSM byte.
c) SSU must accept MHz, . MHz, MHz, and MHz sine or square wave
inputs.
d) It must be possible to combine different input types on a single SSU in any
combination.
----) Input Selection
a) Check for digital error events, including LOS, OOF, CRC (selectable), BPV and AIS
and disqualify those references of which the error events exceed pre-set thresholds.
b) Select valid inputs using from a pre-set user defined priority.
c)Disqualified input references that exceed pre-set performance thresholds based on at
least the following reference types:
Cesium
GPS
Network
d) Weight the qualified input references according to the quality as indicated by the
synchronization quality messages and according to a user selectable priority table (The
quality of signal is more important than user selectable priority).
e) If no valid input is present, the SSU must enter the holdover mode.
----) Local Oscillators
a) The following oscillator types must be used for different types of nodes:

PRC nodes : Cesium
Class- transit nodes : Rubidium
Class- transit nodes : Rubidium
Local nodes : Stratum E Crystal
b) The frequency output from the local oscillators should be based on direct digital
synthesis to avoid direct adjustment of the local oscillators. DPLL or PLL systems will
not be acceptable.
c) Any oscillator (Rubidium and STE) shall not require any adjustment, calibration or
maintenance throughout its entire lifetime ( years).
d) The local oscillators within SSU will enable SSU to comply to the overall system
performance standards for each node type.
e) The local oscillators will be used to eliminate phase transients and jitter and to reduce
frequency wander feed through.
----) Output Modules
a) A single SSU with one management connection shall be capable of providing a
minimum of protected outputs.
b) Each output module shall have no less than outputs.
c) It shall be possible to configure SSU to operate with unprotected outputs without blank
sub-rack slots (there should be no abandoned slots).
d)SSU shall provide . Mbit/s and . MHz outputs as specified in ITU-T
recommendation G..
e). Mbit/s signals shall be structured in accordance with ITU-T recommendation
G., and shall provide signals with CCS or CAS, selectable, and must provide SSM
byte in compliance with ITU-T G..
f) All outputs shall have an automatic drive impedance adjustment for or ohm. It
should not be necessary to adjust the SSU for a change in impedance, or use external
balloon or converter devices for this purpose.
g) It must be possible to combine different output signal types on a single SSU in any
combination of outputs.
h) All outputs of a single SSU will be phase aligned.
I) It shall be possible to manage outputs at the individual output level.
j) It shall be possible for the user to assign a text string to name each output individually
for direct correlation to network elements.
----) Equipment Switching Stability
a) The phase discontinuity of the SSU output may never exceed the limits outlined in
Table below:
Table : Maximum Phase Discontinuity Allowed
Switching Criteria Maximum Phase Discontinuity

A transfer between reference inputs; nanosecond
A transfer between input cards; nanosecond
A transfer between local oscillator cards; nanoseconds, i.e., <= / UI
Output protection switching. nanosecond
b) It shall be possible to perform equipment protection switching manually via the
management.
c) All equipment protection switching shall be performed automatically by default.
----) Expansion Shelves
a) It shall be possible to add up to four additional expansion shelves.
b) Expansion cables shall be : protected.
c) It shall be possible to manage individual outputs in the expansion shelves.
---) Performance monitoring
----) Performance monitoring shall be implemented on the SSU input hardware
and separate performance measurement hardware shall not be necessary.
----) Performance monitoring shall be possible on up to inputs simultaneously.
----)Inputs may be the input references used by the SSU, or any other
synchronization signal (performance monitoring only).
----)Performance monitoring shall be done on all . Mbit/s and . MHz
inputs.
----)SSU shall store hours of performance data for all inputs.
----) The performance data shall be collected with ns or better resolution.
----) The data shall be processed into the required formats in real time, to produce
at least the following graphs with the local management terminal or with the
synchronization management system:
Maximum time interval error (MTIE)
Time deviation (TDEV)
Phase
FREQ OFF: Frequency Offset
----) For each of the graph types, it must be possible to display the masks as
defined in the relevant ITU-T specifications with the data.
----) It shall be possible to save the performance data to an external file for later
analysis.
----) The performance monitoring shall be non-intrusive.

---) SSU Local Management
The management functionality in this paragraph refers to local management, performed on
the SSU itself and via a local terminal.
----) Fault Management
a) Faults shall be classified as critical, major or minor.
b) No less than alarms/events shall be stored in the SSU.
c) Alarms will be indicated locally on the SSU by LEDs. The indications must be
sufficient to enable troubleshooting without the need to be connected to a local or remote
management system.
d) Major, minor and critical alarm indications shall be extended to form-C relay contacts
to provide audible and visual indications in the station.
e) Alarms will be reported to the local management terminal, which will keep an alarm
log with date and time stamped alarms.
----) Configuration Management
a) All equipment configuration changes shall be possible via the local management
terminal.
----) Performance Management
a)SSU will constantly monitor all input references and provide indications and alarms to
indicate any degradation in performance.
----) Security Management
a) Access to different areas of the local management terminal shall be limited to users or
user groups by means of password protection.
b) Passwords and privileges shall be authorized by a system administrator.
c) Local access to the system shall be controlled by the synchronization management
system.
----) Management of integrated GPS receiver(s)
a) It shall be possible to manage the GPS/GLONASS receivers via the management
facilities of the SSU, so that only one management connection is necessary.
---) Disaster recovery
SSU must be able to tolerate an uncontrolled power failure without damaging the
equipment or during a power brown-out; the input voltage to the SSU gradually falls to
less than % of the normal operating voltage. When the power is restored after a total
power failure or power brown-out, the SSU must automatically be restored to the
configuration it had prior to the power failure or power brown-out without operator
intervention.
---) Physical Characteristics
----) Equipment practice: The equipment practice for installation into
ETSI *mm racks is required.

----) The racks will use natural airflow in such a way that there is no need for
forced air cooling of the system. The racks shall be capable of accepting top or bottom
power cable and top or bottom signal cable entry.
----) Earthing: It shall be possible to earth a signal cable on either input or output
side, or on both sides.
----) The equipment shall have a positive power earth and a separate signal earth
(rack earth). The signal earth shall not carry any power current.
----) The connection of the positive power supply to the signal ground in the
rack shall be an optional strapping facility.
----) Connectors
a) All ohm sub-rack connectors shall be BNC type.
b) The ohm sub-rack connectors shall be DE type.
----) The SSU shall not be susceptible to interference from other
telecommunication equipments or radio signals, and shall comply with EN -
class B, EMC requirements.
----) The equipment must meet the specifications when in operation, while being
subjected to temperature controlled locations with no forced air cooling applied.
----) The equipment will be permanently mounted in a fixed position.
----) Bidder shall demonstrate compliance to ISO .
-) SYNCHRONIZATION NETWORK MANAGEMENT SYSTEM
(SNMS)
The synchronization network management system shall provide the following general
features:
--) Management Requirements
---) The synchronization management system shall provide a platform for full
FCAPS based synchronization element management.
---) The synchronization management system shall be simple to install, configure and
operate.
---) The synchronization management system shall be based on commercially
available PC hardware and associated operating systems.
---) The SNMS shall be based on modern client-server principles allowing one server
to communicate to the network elements, and multiple clients to be connected to the server.
---) Additional clients should not need to interface the synchronization elements
directly.

---) It should be possible to achieve all the functional requirements of the SNMS
using just the server application.
--) Functional requirements
---) A synchronization management system shall be capable to oversee the
functioning of the synchronization network element (SNE) and the synchronization
network remotely.
---) The synchronization management system shall have the capability of managing
the synchronization supply units (SSUs) along the entire network from a single network
operation centre (NOC).
---) The SNMS should be manageable and controlled by EMS and NMS.
---) The SNMS shall be based on the UNIX or Windows Professional or
Windows XP Professional platforms, and will use industry standard communication
hardware and software tools.
---) The bidder shall declare its server ability to accept the maximum client working
at the same time.
---) The bidder must declare the maximum number of NEs per workstation.
---) The SNMS must have the capability to have resiliency and fail-over functionality
that protects the management system if the server / workstation is failed while the SNMS
is running.
---) The SNMS shall support Network connectivity between the SSUs and
synchronization management system over TCP/IP.
---) The SNMS shall provide a comprehensive view of the synchronization elements,
including a geographical display and a hierarchical (containment tree) display of the
synchronization network and its elements.
---) The SNMS shall conform to TMN standards and perform the following TMN
management functions:
a) Fault Management
b) Performance Management
c) Configuration Management
d) Inventory Management
e) Security Management.

---) The SNMS shall monitor the tracing/observing satellite number, satellite tracing
status of the GPS or GLONASS system.
---) The SNMS must be expandable.
--) Alarm/Fault Management
---) The SNMS must check the connection with the SSUs periodically, and notify
the operator of the loss of connection.
---) An alarm condition shall be indicated by a flashing icon or change of color so
that attention is drawn to the fault.
---) It shall be possible to detect alarm conditions on any of the synchronization
elements without human intervention.
---) The SNMS must manage different levels of alarms defined as:
a. Minor Alarms
Minor alarm shall indicate the events which do not affect the performance and
operation of the system.
Part of input reference signals are lost;
The frequency deviation of input reference signals exceeds the threshold;
The transmission parameters (LOS, BPV, OOF, AIS, CRC) of input
reference signals exceed the monitoring thresholds;
The majority voting result of input reference signals is Unavailable.
b. Major Alarms
Major alarm shall indicate the events which could impact the performance or
reduce the redundancy, but do not render the system in-operational.
All input reference signals are lost;
Fault occurs to any power supply of the system;
Any of redundant boards gets faulty;
Any of other boards gets faulty;
Any of output ports gets faulty.
c. Critical Alarms
Critical alarms shall indicate the events that affect the working of the
synchronization equipment e.g. loss of both redundant output boards.
d. The SNMS must maintain and display the alarms chronologically in the order in
which they occurred.
e. The SNMS must display the different levels of alarms (Major, Minor and
Critical) in different colors.
f. The SNMS must not hide an alarm until the condition is cleared in the
synchronization element, even if the alarm is acknowledged.
g. The SNMS must have the ability to drill down to the synchronization element
to determine more specific information on the alarm.

h. The SNMS must store the alarms for future analysis.
i. The SNMS shall generate measurement results in numerical and graphical forms for
comparison with industry standards. It shall be capable of correlating information
relating to performance of the synchronization system to evaluate short and long
term trends.
--) Configuration Management
SNMS must provide the control of all the functions available on the synchronization
elements, enabling re-configuration, manual control, and other operating functions.
--) Asset Management Requirements
SNMS should be able to display the configuration of the SSU elements graphically, and
should display at least the following informations:
a) SSU Module location within the shelf
b) SSU Module hardware part number
c) SSU Module hardware revision level
d) SSU Module software part number
e) SSU Module software revision level
--) Performance Management
---)SNMS shall have the ability to upload input performance data from the
synchronization elements.
---) MTIE

, TDEV

, Frequency offset, and phase information must be uploaded

from all SSUs where GPS/GLONASS is installed; only phase information from the
GPS/GLONASS module must also be uploaded.
---)SNMS shall collect the performance data automatically or on demand from the
synchronization elements.
---)SNMS must store the performance information that is retrieved from the
synchronization elements.
---)SNMS shall generate measurement results in graphical format with the ITU-T
standard masks for comparison.
---)SNMS shall be able to export the measurement results in numerical format for
further analysis using third party products such as Microsoft Excel.
--) Security Management

Mean Time Interval Error

Time Deviation

---)SNMS shall support different levels of user access to assign different operating
and provision privileges for each user.
---) There should be a capability of creating, maintaining and adjusting
management domains, adding additional security while also providing organizational
view for the NEs.
--) Network Time Management
The offered NMS shall provide simple and straightforward management functions
for network time synchronization on the following three levels:
a) Monitoring and controlling the network devices e.g., setup and configuration;
b) Comprehensive management of clients and devices;
c) Providing audit trail of time synchronization across the network. It shall be
possible to perform the following activities from the workstation assigned to
network time management:
A. Perform core setup functions of all timeservers i.e., installation,
monitoring, configuration, and troubleshooting problems
B. Monitor time synchronization network-wide i.e., whether all clients
synchronized within a specified threshold.
C. Implement network-wide timekeeping strategies.
D. Multiple levels of fall-back time sources
E. Safeguard against malicious or inadvertent tampering with network time
keeping.Having functions to prevent users from manually changing the
time on machines to falsify records.
F. Check whether the time on any monitored system was correctly
synchronized at a particular time and date with a specified time source.
G. Generate complete information to allow auditors to determine when a
machine was last synchronized, with what time source, as well as its
variance from the reference time source.
H. Security features to ensure that the entire system time is correct,
including protection from rogue time servers, denial-of-service attacks
etc.


Chapter:

) Network Management

-) General Requirements
)Network management system shall be according to ITU-T Recommendation M.
series with the emphasis on M., M. and M..
) Network Management system shall cover at least EML

, NML

and optionally SML

.
) Each Network Element (NE) shall be managed through local, area and central
management by considering (NMS

, NCT

, and LCT

)
) Two network managers for Tehran (SC and SC) as hot standby to each other and the
third one with an independent DCN in Esfahan (SC) shall be considered.
) The bidder shall suggest the best topology and design for Element Management
Systems (EMSs) locations based on the distribution of NEs and the capabilities of its
network management system in order to achieve the optimum availability. The locations
of EMSs shall be selected by considering the priority list of the control centers
(provinces)..
-) each EMS shall manage all NEs in the related stations.
-) each control center shall only be able to control its own NEs.
-) each NE shall be managed by at least two EMSs.
) The remaining control centers which are not selected as EMS shall be considered as
element managers which comply with all FCAPS management functions in each province,
separately according to TMF , , and .

Element Management Layer

Network Management Layer

Service Management Layer

Network Management System

Network Craft Terminal

Local Craft Terminal

) NMS, EMS and the remaining control centers shall have the capability of managing all
NEs such as SDH and WDM.
) Security for network management shall be based on ITU Rec. .
) The standby system shall be able to be switched manually and automatically.
) NMS and EMS shall be equipped with necessary standards in order to be integrated
horizontally and vertically with any other management system.
) NMS shall be able to connect Next Generation Network (NGN) management and
elements.
) NMS and EMS shall support OCH Client, OMS, OTS, and OSC Trails.


--) GENERAL
. All texts (Documentation, Helps Menu and Etc) shall be in English
. The database shall be configurable by USER
. Loges and helps shall be on line
. The proposed system shall be scaleable according to the network size
. All menus shall be accessible by mouse and /or keyboard
. The proposed system shall have a self checking facility
. The proposed system shall be able to detect DCN channels Failure.
. All events and measured values ( such as optical transmission test and
measurements) displays shall be real time )
. the date and time of NE , EMS And NMS shall be sync and adjusted
automatically according to NMS
. NMS shall be able to report any requested ticket and in this case, the bidder should
provide any required software.
. The bidder shall indicate power consumption for all network management systems
. The bidder shall provide separate UPS for all network management systems

-) Fault Management Function

) Fault management function shall be according to ITU-T recommendation M..
) The Fault Management shall provide facilities to monitor faults in the network objects
( of course the NE's shall provide the system connection alarm points ).
) NMS/EMS/LCT shall be able to illustrate any fault graphically which can show the
type or subject of event's type of element and the location of element.

) Fault management shall be able to support the following alarm severities such as:
- Critical
- Major
- Minor
- Warning
) The severity of the fault is indicated with a corresponding color.
) It shall be possible for operator to customize colors for each severity class.
) Alarm state shall be identified:
- Raised: It shows starting a definite alarm.
- Cleared: It shows removing a fault which was reported before.
- Acknowledge: It shows the existence of one or more acknowledged faults in network
elements.
) The fault state of a network object shall either be normal or faulty and be indicated with
a corresponding color.
) EMS shall be able to do alarm correlation process.
) The cleared unacknowledged alarms ( in history log ) shall be indicated to operator on
monitor by an indicator.
) Cleared faults shall be stored in a fault history database. Deletion of entries in fault
history requires a special access right.
) The storage capacity shall be enough for current alarms and historical alarms in
database.
The bidder shall submit full description of the proposed system (HW,SW, OS , Functions ,
DCN , Max No. of Manageable NEs ,event , and PM values .storage capacity etc. )
) history event log shall have exceeding warning.
) Each active fault entry shall contain at least the following attributes:
a. Fault source
b. node , location and module
c. Fault description and code
d. Fault classification
e. Possible cause and suggested actions to correct the problem
f. Fault raised and cleared time
g. Fault count

h. Fault acknowledgement time
i. Acknowledged operator
) Fault history entry shall contain at least the following attributes:
a. Fault source
b. node , location and module
c. Fault description and code
d. Fault classification
e. Fault raised and cleared time
f. Fault count
g. Fault acknowledgement time
h. Acknowledged operator
) It shall be possible to use state filtering according to operator's selection.(such as all
events , specific event type , event source , event duration)
) A toggle filtering shall be possible through a Combo box.
) It shall be possible to define different beep types for alarm indications and the severity
threshold that causes the system to beep. Beep frequency shall be definable.
) The NMS shall contain a fault consistency check, which shall automatically compare
the information in the database with the information in the hardware of the network.
) It shall be possible to record problem description into a Trouble Ticket.
) The Trouble Ticket shall provide facilities to record information on network service
problems.
) Additional information on the problem shall either be attached to the Trouble Ticket,
or shall be accessed from the Trouble Ticket.
) A customer/channel Trouble Ticket shall be attached to a customer or channel and
shall usually be created as a response to a customer complaint.
) The Trouble Ticket shall define an initiating operator and a responsible operator.
) Initiating operator shall edit, close and delete the Trouble Ticket. Other operators shall
only be able to view the Trouble Ticket.
) A text including source and result of source shall be indicated by moving mouse on
an alarm.
) Alarm type shall be identified for each fault:
- Primary alarm: Network element causes alarm.
- Secondary alarm: The alarm occurred through other equipments.

) There shall be an index list of all possible alarms which can be made by network
element.
) There shall be an index list of all possible fault reasons for each alarm , which is
defined by system or operator , and It shall be viewable.
) Each event shall be recognized on real time.
) System shall synchronize and adjust alarm data between network elements and NMS
automatically and manually.
) It shall be possible to log all alarms and their information.
) Fault data in EMS shall be stored manually and automatically.
) In EMS, network element alarms shall be cleared automatically after removing alarm.
( shall be remain in history log. )
) It shall be possible to send selected alarms to the outside of EMS or NMS through
Pager, SMS or Email automatically, to a user by permission.
) Network management system shall be able to recognize the location of fault in
transmission environment (for example OTDR). (Optional)
) Management system shall be able to make a virtual fault manually for test in the
service.
) If a maintenance job is made for test by operator, a maintenance alarm shall be
appeared in NMS and EMS.
) It shall be possible to define which groups of events and status will be reported
automatically and which groups will be reported by operator's request.
42) The element management shall receive , process , and display events notifications. The events
shall included NE alarms, status events, external alarms, management system alarms , and
threshold crossing alarms.
43) Events shall be presented in the following ways :
Event summary list
Global event list
Graphical presentation of the event source (up to module level)
Event statistics

44) Unacknowledged events shall be displayed in blinking state .
45) Event summary list shall include the names of the managed stations and the relevant highest
class of severity of events present at the time of display . Stations without event notification
shall be displayed as normal and with a proper color (e,g.green) . The names of the stations
shall be shown by color in accordance with their highest class of severity of events present at

the time of display , and flashing before acknowledgement. After acknowledgment, they shall
be presented by steady colors.
46) The global event list shall display current event situation of the entire NEs managed by the
relevant element manager.
47) For every event , the global event list shall contain the following information :
Event severity (by proper colors)
Date/time of events in local time
NE name (name of event source)
Location of event source (up to module level)
Event state (acknowledged, unacknowledged, presented by steady and blinking
colors)
Service affected or not
Probable cause of events.

48) For graphical presentation, different icons shall be used to represent different NEs. The color
of the icons shall be according to the highest class of severity of the current events of the NE.
The graphical presentation shall be up to module level.
49) Event statistics shall present the total number of each class of current events of the entire NEs
managed by an element manager.
50) All events, including acknowledged and cleared ones shall be recorded in the history event
log. The storage capacity shall be enough for events or performance values .
51) Acknowledgment shall be possible for a single event, all events shown on a page of screen ,
and entire events of a station.
52) An audible alarm for changing status shall be provided. The operator shall be able to
activate/deactivate it. For acknowledged event, audible alarm shall cease. also The operator
shall be able to activate/deactivate audible alarm for special alarms.

-) Security Management Function

) Security management function shall be according to ITU-T recommendation M..
And ..
) Security Management shall provide facilities to control operators' access to the
Network Management System.
) Each operator shall have a user name and a password.
) The access control shall be based on the use of operator user names and passwords.

) All successful and unsuccessful login and logout attempts shall be stored in a log
accessible for an operator with the highest security management access rights.
) The user access rights shall determine which Network Management System user
interface components can be used by the related operator. And also The administrator
shall be able to customize the access rights for each operator.
) Additional security shall be achieved by setting a password expiration time and by
setting a login attempt limit.
) The operator with the highest security access rights can restrict other operators to
access the system.
) The system shall be controlled such that a VPN operator cannot access the system
without a pre-programmed hardware identification module.
) The MANAGEMENT system shall have been protected for any unauthorized access
via DCN or other related network.
) It shall be possible to log all events.
) It shall be possible to access network through DCN equipments and remote facilities.
) Access to all Databases shall be possible through extra ID and Password.
) It shall be possible to define a time out for login job for users.
) It shall be installed a sufficient firewall with update ability for connecting to other
networks.
) Administrator must be able to change the passwords , add/remove users (operators), define
password expiry time , enable/disable user access rights and specify user levels.
) Network management system shall have a database of user's information and abilities.
) If any user enter wrong password for defined times, user's ID shall be locked .
) Administrator shall be able to change the default user permission and define extra job
in each access level.
) User's account expiration time shall be defined by administrator.
) System shall accept only complex Password combination of numbers, letters and
special characters and at least characters.
) A main version Anti-virus with valid and permanent Licence with updating ability
shall be installed on computer systems.
) If operator doesn't use a computer for a defined time, the screen shall be locked
automatically. It shall get password for unlocking screen.
) It shall be possible to check for signs of software intrusion.
) Any information from previous user shalln't be seen on the screen.

) Each user can be able to change his/her own password and default facilities
) LCT (Local Craft Terminal) shall work by NMS authorizing
-) Configuration Management Function
) Configuration management function shall be according to ITU-T recommendation
M..
2) Configuration management shall support the following :
OS configuration:
- OS resource parameters (printers , clock , etc)
- Fault management parameters (e.g. filter definition, alarm
configuration)
- Security management parameters
- Service indication
NE configuration, i.e. to read the current configuration of NEs and to change
settings . Applicable items include :
- Cross connection setting
- Configuration of signal structure and overhead byte
- Configuration of clock source and distribution
- Configuration of MSP, BSMR and card protection
- Network elements reset
- Switchover state
- Loops Setting (for the NEs having this capability)
- End-to End paths design.

) Network management system shall support the following services:
- Uni-directional and bi-directional
- Point to point and point to multipoint
- End to end protected and unprotected
) It shall support LCAS and GFP protocol.q
)Network Configuration Function shall provide facilities to define the topology and
configuration of the network.
) The network topology shall be determined by the placement of locations, nodes, trunks
on a network map.
) The network configuration shall be determined by equipping nodes with units and
interface modules, and by binding trunks to interfaces.

) Network objects shall be processed through three stages during installation and
dismantling. These three stages shall be:
a. Stage supporting objects that are planned into database
b. Stage supporting hardware installations
c. Tests and stage for objects in production
) Preplanning shall be possible for channels and network topology (see b) without
connecting the network. All the related Network Elements shall be updated with a single
action in Network Management System.
) Network management system shall be able to recognize physical links automatically.
) Provisioning of embedded control channel must to be supported by Network
Management System.
) The Network Configuration Function shall provide facilities to define the parameters
for nodes, units and interfaces. Group operations to allow parameterization of several
interfaces at a time shall be included.
) The system shall contain an integrated unit software download manager facility with
the following features:
a. Scanning unit software versions from the network element
b. Downloading new unit software from network management to network elements
c. Capability of selecting the exiting software versions in a network element by user.
) The facilities to define and monitor network synchronization system shall be included
in the Network Configuration Function.
) The system shall automatically maintain, monitor and distribute real time in each
network element. This real time shall contain time and date information.
) The user can proceed with the following diagnostics:
a. Memory tests
b. Control bus tests
c. Cross-connection matrix and bus tests
d. Operating voltage tests
e. LED tests
f. Data interface circuit states
g. Interface and line loop activation
) It shall be possible to change the active cross-connection card or matrix by one
operator command or automatically.
) The system shall be able to create script files, such as channel provision, to speed up
programming repetitive actions.

) The system shall contain an integrated mechanism to allocate identification number
intervals for network objects (NE Addressing). Definition of IDs that are not in
compliance with programmed network numbering plan shall be automatically restricted
by the system.
) The operator shall be able to assign information on each interface, such as connected
base station / node location, name, type, address of port and exchange block. This
information must be seen from fault management application.
) The system shall count number of faults of each interface in the network and report it
to the configuration management.
) System shall be able to recognize all the new equipments through autodiscovery
process.
) It shall be possible to view the created paths between network elements graphically
and control it in the NMS level.
) Network management system shall be able to create, update, delete and restore
network management topology data.
) Updated topology in network configuration (nodes, trunks and channels) shall be
viewable for all users simultaneously.
) It shall be possible to select protection type and activate or deactivate protection on a
single channel level via management network.
) Network management system shall be able to define different protection architectures
such as:
- F-MSPRing and F-MSPRing
- Drop and Continue
- SNCP(I,N)
- Mesh and Restoration
- ASON architecture
- manual and automatic switching
-) Network management system shall support ASON network management
ASON domain creation
ASON Topology
ASON software version
ASON link management (Available bandwidth)
Create ASON Circuit (intelligence to SDH)
Upgrade SDH service to ASON service
Monitoring all trials such as SDH and ASON

) Creating and viewing Cross-connection in path and trail shall be possible through text
and graphic.
) Creating of other paths with defined characteristics, between two nodes, shall be
possible through copying one path.
) It shall be possible to view all path information as a table and also access details of
each path by clicking on it in graphical view.
) Configuration management shall have an inventory file from all network elements.
) NMS shall have capacity management such as number of exiting paths and total
unused capacity of network and per path, and
-) Performance Management Function
) Performance management function shall be according to ITU-T recommendation
M..G-G
1-1 ) The element manager shall collect , process , present , and log performance data according
to ITU-T G.826 recommendation , of the NEs which provide these data .
) Performance Management includes the following function set groups:
Performance Quality Assurance.
Performance Monitoring.
Performance Control.
Performance Analysis
) Performance management shall include the following parameters:
-ES( Error Seconds )
-SES( Severely Error Seconds )
-BBE( Background Block Error )
-UAT( Unavailable Time)
-UAS( Unavailable Second )
- Availability percent
-PJE( Pointer Justification Event )
For above items , it shall be possible to measure packet required parameters (Packet loss,
Delay).

) The Performance Management shall provide facilities to monitor the performance of all
trunks and channels.
) There shall be two types of performance parameter collection intervals: minutes and
hours and unavailable time shall be reported to the operator as a warning and the measuring time
shall be defined by authorized operator.
) There shall be performance history file for evaluating performance of transmission
systems.
) Thresholds shall be set for the performance parameters manually and standard based.
When the data monitored exceeded the thresholds, the system shall give corresponding
alarms on the NMS. The operator shall be able to change the settings of thresholds.
) Any exit from thresholds in minutes and hours periods shall be reported to the
operator immediately.
) Performance data shall be reported as soon as requested by operator.
) It shall be possible to get the periodical performance report by means of network
failure analysis for predicting faults.
) Dedicated ports performance data shall be able to report by operator's request.
) It shall be possible to send these reports to other analyzing environments (for example
Excel).
) It shall be possible to report the end-to-end and area-to-area performance for all
channels.
) It shall be possible for the performance statistics to be reported in tabular as well as in
a graphical form such as a histogram.
) The load in a link shall be presented as the ratio of used capacity to available capacity.
) The performance measurement shall be calculated continuesly and automatically and
manually for each service and it mus be able to present results on web
) The storage capacity for performance values shall be enough

-) Application Development Function

) It shall be possible for the user to design and implement his/her own management
software applications with a set of Network Management System integrated software
development tools.
) The developed applications shall be able to monitor and create customized reports
based on the existing run time network data, e.g. detected network errors.
) It shall be possible to enhance existing Network Management workflows to speed up
Network Management processes like network configuration.

) The developed applications shall support controlled timer and simultaneous task
execution for applications like queries.
) It shall be possible to design and set the graphical user interface.
) It is possible to integrate the developed applications with the existing Network
Management services to the same Network Management Server with the current network
,The NMS applications (or components) shall be able to interface towards existing NMS,
or other Network Management Systems where required (TMN) .
)The User shall be able to create shortcuts on the screen or icons in the tools menu for
most used items.

-) Network Management System User Interface

) The user interface shall be graphical and consisted of a hierarchical set of tools. These
tools shall be controlled by selecting objects with a mouse and inputting information with
a keyboard.
) It shall be possible to view the network in both tree-like and graphical format.
) All the NMS tools shall be opened from the main program such as a NMS Toolbox.
) Each tool, in turn, shall consist of a set of windows and dialogues.
) The system shall not have any limitation for number of simultaneous opened windows
and dialogues.
) The system shall support at least several simultaneous program sessions in one
management workstation thus making it possible for the operator to run several identical
applications at the same time.
) The windows shall graphically represent various network elements and objects.
) In addition to the graphical user interface, the system shall support an integrated macro
manager facility to execute command files and thus speed up the configuration process. It
shall be possible for operator to edit these macros.
) The system shall provide a comprehensive and easy-to-use on-line help facility in each
application to get the best resolution.
) The system main dialogues for trunks, nodes and channels shall contain filteration
facility with wildcard option to ease searching and sorting of information in large
networks.
) Each of the(ports, protections, clocks and DCNs) shall be as a menu, so for example,
it shall be possible to view all synchronizing networks or all clocks in one window, and it
shall be possible to update these windows by query. Also it shall be possible to be updated
automatically according to the defined time.
) System shall be able to indicate all network elements such as NG-SDH and C/DWDM
in one graphical view.

) All the related information such as wavelength, NE type, characteristics and NE
address shall be shown through moving the mouse on NE.
) When NMS access the NE via EMS, the command execution shall be only possible
by NMS and it shall be shown in EMS by a special icon.
) Network manager shall be able to give/take access rights to local users.

-) Configuration backup and recovery

) The NE shall be able to restore its configuration database to the last known stable
condition in the case of the corruption of configuration data.
) The NE shall create a backup of configuration data by downloading stable data to
nonvolatile storage (such as Tape, DVD) located either on the NE, Laptop or on a remote
server.
) NE shall save updates and changes to the latest archive of configuration data and
the NE shall maintain a backup of this configuration change data.
) The NE shall be able to restore configuration data from a backup following the
detection of corrupted data in the configuration database.
) The management system shall download the backup files to NE in essential case(s).
) The NE shall do this job by receiving commands from management system.
) The management system shall be able to create a backup manually and automatically in
defined periodical time by the operator.
) Servers backup shall be done in two modes:
- Full backup (including OS, applications and database and )
- Data backup
Data including:
- Alarms, (History and Current)
- Log files (System, commands and security)
- Network Configuration (NE type .NE (NSAP, IP) Stations Configuration, Ports
and connections between them, CROSS CONNECTIONS, CARDS and their
serial number,
- Users (Setting and ID)
- PERFOMANCE MONITORING Result
- NE Software Version

- And
-) other requirements
) Maximum access time to the network shall be less than minute, if DCN works as
standard.
) Minimum upload and download bit rate shall be kb/s.
) Minimum capacity for storing alarms shall be enough for at least . alarms.
) Minimum capacity for storing log files shall be enough for at least log files.
) Each system shall be equipped with at least network connection cards.
) Numbers and speed of ports shall be based on computer requirements and in
accordance with the newest technology.
) Systems shall be able to work in all environment conditions.
) The system shall have Tape Drive and DVD Drive
) The vendor shall fill table for hardware characteristics.
.) Monitor type for NMS and EMS shall be LCD and at least ".

Table : Hardware characteristics
OS Monitor Disk
Memory
Main
Memory
Clock Rate CPU Hardware
Client
Server

) Software shall be able to work on Windows, Linux, platforms.
) Server shall have Mirror disks. All databases of the server shall be stored in two
identical mirror disks simultaneously. When one of them fails the other one shall do the
job without any interruption.
) Software and hardware shall be the latest versions in delivery time.
) Client and server shall have telnet ability.

) The ability of internet connecting via Leased line shall be possible, and it shall be
possible to be activated or inactivated, by network manager.
) Hardware equipments of network management system shouldn't be limited to a special
company, and shall be provided easily and it shall be supported for at least years.
) The bidder shall submit the detailed technical specifications of the hardware of the
proposed element manager. Each element manager shall be equipped with at least large
capacity hard disk with efficient RAM , color monitor , laser printer , etc.
-) DCN

The bidder shall submit the DCN plan for this project to be used in supervisory and
management network of the project and also offer DCN topology with complete protect .-

) DCN shall provide environment for TMN

management messages communication.

) DCN shall provide environment for signaling messages communication for ASTN

and
ASON components in different topologies such as linear, ring and mesh.
) The topology of each DCN sub network shall contain mesh or ring or other topology in
order to protect DCN.
) Data communication channels between NEs including GNE

shall support OSI over

IP

.
) The EMS and NMS connections shall be done through a WAN

with a proper speed.

) The WAN topology connecting EMSs shall be ring or mesh in order to protect DCN.
) DCN architecture shall support OSI over IP
) Physical channels among NEs shall support ECC

including DCC

channels for SDH

and GCC in OTN

Data Communication Network

Telecommunication Management Network

Automatic Switching Transport Network

Gateway Network Element

OSI over IP

Wide Area Network

Embedded Control Channel

Data Communication Channel

) Each area shall consist of optimum GNEs in order to increase reliability
) All routers and peripherals connecting EMSs in WAN network shall be managed in
NMS (DCN management).

-) Processing of the routing

) NMS shall be able to calculate and implement the routing for LOP

, HOP

and Trial.
) NMS shall be able to calculate and implement the routing based on using cost factor
over physical links.
) NMS shall be able to calculate and implement the routing for ASTN and ASON nodes.
) NMS shall be able to calculate and implement the routing based on shortest path first
(OSPF).
) NMS shall be able to calculate and implement the routing based on at least three
predefined conditions.
) NMS shall be able to calculate and implement the routing based on at least passing
nodes.
) NMS shall be able to calculate and implement the routing base on link disjoint
procedure.
) NMS shall be able to calculate and implement the routing using Node disjoint
procedure.
) NMS shall have the capability of demonstration of the routing for all related elements
including nodes, port, units, slots and other features and the path address.
-) VPN

) The network management system shall support virtual private networking.
) Virtual private network shall be consisted of the following components:
a. Shared and dedicated nodes
b. Dedicated trunks

Optical Transport Network

Low Order Path

High Order Path

Virtual Private Network

c. Virtual trunks
d. Shared and dedicated interfaces
) The virtual private network operator shall not be able to see those parts of the network
belonging to the real network operator or other VPN operators.
) The manager shall be able to view VPN tunnels.
) It shall be possible to define security levels for VPN tunnel.
) User's identification shall be recognized for security, only the authorized users shall be
able to have access to this network.
) It shall be possible to define security policies in VPN.
) There shall be provided facilities to change the topology of the network.
) It shall be possible to add, delete or change equipments, sites, traffic and etc easily in
the management system.
) It shall be possible for the operator to assign a group of management capabilities to an
external company or a customer.
) It shall be possible to inform customer about important events such as failing or
reconnecting the service.
) It shall be possible to show the service performance to customer network.
) It shall be possible to report all the changes, deletion, additions and etc.
14) The offered equipment shall fully comply both individually and as a complete system with the
following international ITU recommendations, in addition to any other recommendation
mentioned hereafter in this specification. Response for each ITU-T recommendation is
required separately.
M.3010: Principle for a telecommunication management network (TMN)
M.3100: Generic network model
G.774 : SDH management information model for the network element view
G.773 : Protocols suits for Q-interface for management of transmission
system
G.783 : Characteristics of Synchronous Digital Hierarchy (SDH) equipment
functional blocks
G.784 : SDH management
X.7xx Series




X.700 : OSI 7 layers reference model
X.701 : System management overview
X.720 : Management information model
X721 : Definition of management information
X722 : Guide-lines for the definition of managed objects

-) GUI Requirements

) The GUI shall simplify EMS usage by adding off-line/on-line proper help (graphical or
text based) for all functionalities of EMS.
) The GUI shall simplify navigation and access with point-and-click maps feature.
) The GUI shall simplify navigation and access with pull down menus feature.
) The NMS shall support intuitive navigator and GUI interface for physical (such as
Nodes) and logical network (such as location collection of nodes in a geographical
location-, trunk bundles collection of trunks between nodes-, and channels) view.
) The NMS shall support secure web-based LCT for easy and convenient access of NEs
in the field (optional).
) The NMS shall support having interface with multi level network topology maps (both
tree-like and graphical format).
) All layers of transmission including DWDM, SDH and NG-SDH elements shall be
seen at the same window.
) The GUI shall have a real-time view of all network events.
) The GUI shall support accessing to all (FCAPS) functionalities of the EMS via a
customizable toolbox.
Each tool, in turn, shall consist of a set of windows and dialogues.
) The GUI shall support simultaneous open active windows (e.g. fault Summery
windows for different elements).
) The user interface (UI) shall be based on a windows based GUI and must be platform
independent (e.g. Java, web-based, or other)

Scanned documentation such as building, floor and cabling plans, images and photos shall
be accessible from within the GUI
If all windows of the UI have been closed, the user session must be terminated and the
user must be logged out.
An undo and redo command shall be provided for all UI commands.
The complete system documentation shall be accessible from the UI for authorized users.
) The GUI shall clearly indicate when commands are being processed and the UI is not
ready for input.
) The GUI shall support wizards and templates during any type of creation activity.
)The GUI shall be able to show the NEs in a graphical windows based form.
In addition to the GUI, the system shall support an integrated macro manager facility to
execute command files and thus speed up the configuration process. No such applications
that are run on different operating systems or computer platforms shall be deemed
acceptable.
Configuration updates on network topology (NEs, trunks, channels) executed in one user
interface computer shall be visible for all other operators and no data conflict shall occur.
)The system main dialogues for trunks, nodes and channels shall contain filteration
facility with wildcard option to ease searching and sorting information in large networks.
)The GUI shall prepare facilities for fault management including:
Each fault shall be displayed on related section in the layers of LCT/EMS/NMS.
Showing the alarm severity with different colors that can be defined by the user.
Showing the alarm status with different colors that can be defined by the user.
Showing the NE status whether it's normal or there exist any problem, with different
colors that can be defined by the user.
Providing filters in the format of a drop-down list control.
Providing a feature (i.e. a checked box) to toggle the filter.
Having tool-tips for each alarm.
In the alerting state the object shall contain one or more unacknowledged faults. This is
indicated with a blinking color on a corresponding object. Once the fault is acknowledged,
blinking shall stop and the color shall get steady.
)The EMS shall support GUI cut-through (GCT) feature to allow the NMS to access the
EMS user interface.
) EMS GCT functionality on NMS shall be the same as the one available to an EMS
client user when invoked within the EMS.

-) NML-EML Interface Requirements

The EMS shall support TMF (OFCOURSE it shall be based on the latest standards)
interface as its northbound interface .
The EMS shall support other standard protocols such as SNMP V-, ODBC, RMON,
and CMIP (Q) as its interface for connecting to other systems.
The EMS shall support standard interfaces such as SNMP V-, and TL as its
southbound interface.
The EMS shall support customizable XML interfaces for its integration with other
management systems such as Trouble Ticketing Systems.
-) Non-Functional Requirements
)Usability
a)All user interactions can be configured to be in English or Farsi language.
b)The system makes use of a Windows oriented, graphical user interface offering a similar
look-and-feel across all customer-, product- and order types.
)Self Care
a)It must be possible for a customer to enter an order in the Order Front End without any
special training.
b)The Self Care component will make use of an Internet page oriented, graphical user
interface offering a similar look-and-feel across all product- and order types.
c)The system must have the ability to send data to the user via email or SMS.
)Scalability
a)The supported number of concurrent users per instance of the front-end will meet
enough number of projected users per outlet location.
)Supportability
a)It must be possible to define new data fields to be presented to the user.
)Design Constraints
a)Front-end communication with other components will be for internal as well as external
use (reseller) and for external use additional security like encryption and strong
authentication is required.
)Online User Documentation and Help System Requirements

a)The system shall have an online help section in which the most used
Functionality is worked out.
b)The system shall display a help text when a user leaves the mouse button on buttons,
pictures, etc.
c)The on line help shall contain the following information:
i) Abbreviations
ii) Introduction to the managing system
iii) Step by step description of how to use the system
iv) Description of windows
v) Troubleshooting
)Performance
a)The maximum delay time between agents and main site must be . second.
)Capacity and Scalability
a)The solution design which shows the system shall have sufficient capacity to function
with the anticipated increase in demand on the SDH networks.
b)The solution design shall ensure the solution implemented for management at the
national level (of the Backbone network), shall be able to scale down to provide similar
functionality at the provincial level.
c)The solution design which ensures the solution shall be scalable to support additional
users, as management is de-centralized, and the staff at local maintenance centers
increases.
d)The solution design shall state where the headroom constraints or limits of any proposed
systems exist.
e)The solution design shall confirm the approach that will be taken to meet known growth
with the deployment of the technical architecture.
)Performance and Volumetric
a)The solution design shall state across the whole solution, and for any relevant system
component, the level of performance / throughput that is proposed.
)Environmental
a)The solution design shall describe power and voltage requirements of the specified
systems and infrastructure items.
b)The solution design shall identify any heat or chilling requirements of the specified
systems.
)Installation and Site

a)The solution design shall include a plan for installing the solution, including network
infrastructure, at TIC premises.
b)The solution design shall specify the space requirements for the solution. The
description shall clearly state the additional space required for systems expansion over of
years periods.
c)The solution design shall provide full plans for installation of hardware and systems
implementation.
)Flexibility
a)The solution design shall show the flexibility of the solution to allow the end user
configuration of future on-going anticipated activities such as, but not limited to
vi) administration,
vii) adding NE to manage,
viii)user customizations for display set-up
)Planning and Scheduling
a)The Bidder shall provide during the requirements phase and maintain during all other
phases a detailed project plan, implementation, integration and testing schedule.
b)The Bidder shall monitor and report the progress determining where the project is
behind schedule and imposing the necessary corrective actions to ensure the project stays
on track, inform the project leader of the Error in due time! Unknown document property
name..
c)The Bidder shall provide monthly progress reports, which shall include hard- and
softcopies of the project plan in a Microsoft Project compatible format.
)Change Control Management
a)The Bidder shall administer the change control process through which changes to the
project are identified, documented and processed through a formal approval process.
)Logistics and Material Management
a)The Bidder shall be fully responsible and accountable for order placement, material
manufacture as well as the shipment to the Islamic Republic of Iran for all equipment
required for the implementation of the project. The Bidder must ensure that delivery takes
place in proper time to avoid any negative effect on the implementation schedule.
b)The Bidder shall be directly responsible for equipment transportation to designated
sites, material management, hosting, security, storage and administration of maintenance
spare parts, tools and test sets.

-) Project Implementation
Equipment/Application Shipment

The Bidder shall ensure that all necessary permissions for importing the equipment and
software as per contractually agreed Bill of Quantities into the Islamic Republic of Iran
are in place.
Telecommunication Infrastructure Company will take no responsibility for delays
resulting from customs clearance etc.
Equipment / Application Installation
The Bidder shall install all equipment/applications as included in the approved Bill of
Quantities as per contract at the designated sites.
The Bidder shall install all equipment/applications within the installation time-frame as
per provided and approved project plan.
Before the overall implementation of the equipment/applications commence, the Bidder
shall provide a copy of the standard technical installation practices used. This document
shall cover all aspects of the installation including the DCN.
Testing and Commissioning
The Bidder shall follow established standards and procedures for software, system and
hardware testing.
The Bidder shall describe procedures being followed for systems integration and user
acceptance testing
The Bidder shall compile the full acceptance testing documentation including of a list of
test cases before the testing and commissioning phase commences
The Bidder shall provide all tools and test equipment required to conduct install, test and
commission the equipment (e.g. load generators, software test suites)
The Final Acceptance Certificate shall be issued not later than months after the
Provisional Acceptance Certificate has been issued, provided all outstanding items are
closed
The Bidder shall provide proper tools for any reinstallation and decommissioning via
EMS by Authorized Network Manager
Operation Transfer and Technical Support
The Bidder shall provide technical support throughout the requirement, implementation,
integration, testing and commissioning phases of the project.
The transfer of operational responsibility shall be carried out in a phased manner and only
after local personnel has been certified on the systems.
The Bidder shall provide a detailed plan regarding the transfer of operational
responsibility to local staff.
For a successful transfer of operational responsibility, the Bidder must ensure that
complete and updated system documentation and up-to-date Operations and Maintenance
manuals have been handed over to the staff of Telecommunication Infrastructure
Company.

-) Training

General
. Telecommunication Infrastructure Company is placing the outmost importance
to the Network Management training of its own personnel by the Bidder. The
objective of the Network Management training to be provided by the Bidder is to
facilitate and achieve a maximum transfer of technical knowledge as well as to
enable the staff of Telecommunication Infrastructure Company to operate,
maintenance and manage the network of Telecommunication Infrastructure
Company after the final acceptance of the project
. The Bidder shall arrange and conduct training in the most efficient way using
state of the art techniques, methods and training facilities.
. The training personnel of the Bidder must have proven their experience in the
field and shall be certified.

. The following types of Management training shall be provided by the Bidder:
a. General Training (e.g. operating systems like UNIX, Solaris; networking,
security, billing and customer care fundamentals)
b. Network Management Training
c. Technical relevant Training
d. Operation and Maintenance Training
e. Network and Customer Service Planning , re-planning

. The courses shall be arranged according to table below
Type No. Of
trainees
Duration(w.d) Time
Technical and
Network
Management

days Before
installation
General -
Operation and
Maintenance

days Before
installation
Network and
Service Planning ,
re-planning


days before
first shipment
Installation and
commissioning

days Before

installation

. The training shall be provided as follows:
a. Train the trainer as installation and commissioning , Service and Network
manager - element manager courses (overseas)
b. Train the trainer as installation and commissioning- element manager
courses (overseas)
c. Train the trainer instructor lead courses (overseas)
d. Local training instructor lead
e. On the job (overseas)
f. On the job (local)
g. The language of training and instruction shall be:
- English in the case of overseas course
- The documentation and all course and training materials shall be provided
in English , and also all documentation for training shall be provided as both
softcopy and hardcopy
- Instructor lead training shall consist of class room lectures, class room
exercises, practical exercises, and certifications
. The Bidder shall supply the following information:
a. A comprehensive training program detailing the subjects, timing, duration
and location of each training course
b. A complete syllabus for each training course with the associated objectives
clearly stated, together with a description of the training documentation
and material proposed for each course (it shall be confirmed by network
management general office )
c. A description of the training documentation and proposed material for each
course.
d. The timing of the training courses shall be appropriately phased into the
overall schedule and the duration of each training section shall be adequate
to meet the objectives listed in the specification. The Bidder shall submit
two months prior to the commencements of each course:
e. A detailed description of the course contents including course syllabus and
lesson plans
f. A course timetable
g. A set of draft training documentation and materials (e.g. training manuals,
lecture notes, charts and slides)
h. A brief course description stating the entrance requirements, certification
criteria and course objectives in clear terms.
. Bidders Training Personnel
a. The Bidder shall state the number, qualifications and experience of the
Bidders training personnel allocated for this project.
b. The training personnel must have both the academic as well as the practical
qualification and experience to convey the theoretical knowledge and the
practical skills needed to operate and maintain the proposed solution.
Proof must be given that the training personnel have gained some first hand
experience in previous projects.
c. The Bidder must assure that all training personnel involved in conducting
the training are proficient in both written and conversational English to

ensure the most efficient transfer of knowledge. It would be advantageous
if the Bidders training personnel has conversational knowledge of the
Farsi language
d. The Bidders training personnel shall maintain a systematic procedure of
monitoring and reporting the progress of all trainees besides the task of
lecturing.

. On the Job Training
a. The objective of on-the-job training is to provide maximum training and
direct involvement in the installation, integration, testing, maintenance and
operation by the personnel of Telecommunication Infrastructure Company.
For that reason the Bidder is requested to propose a well-devised, well-
managed, well-executed on-the-job training program.
b. On-the-job training shall commence from the beginning of installation and
integration planning and shall continue throughout the installation,
integration, commissioning until the end of the joint operations and
maintenance period.
c. The on-the-job training shall include the use of all processes and
procedures provided by Telecommunication Infrastructure Company as
well as all that have been produced by the Bidder during the project, in
particular during the operations and maintenance period.
. Training Material/Equipment /Facilities
a. The Bidder shall provide adequate numbers of training documentation and
training aids during all training courses to be conducted
b. The Bidder shall be responsible to supply full classroom accommodation
including whiteboards, furniture, overhead projectors, computers for
computer based training and stationary items for all courses conducted in
the Islamic Republic of Iran.
c. The Bidder shall provide details regarding the overseas training facility
being used.
d. All necessary training documentation and material (e.g. handbooks,
operation manuals, training manuals, other) shall be available to the
trainees of Telecommunication Infrastructure Company undergoing the
relevant training course conducted by the Bidder
e. The Bidder shall provide two sets of instructor notes for each course
f. The Bidder shall issue a complete set of equipment manuals, operation and
maintenance handbooks and other material that will be used for the training
to each trainee at least one month before the training commences.
g. Where hardcopies are being provided by the Bidder, all training material
shall be of excellent printing quality. For softcopies the relevant readers
(e.g. Acrobat reader, Flash player, word etc.) shall be provided together
with the softcopies.
-)Maintenance Period
Initial Network management Equipment Maintenance Period

.The Bidder shall maintain the network management relevant equipment installed and
commissioned during the period between the Interim Acceptance Certificate and the Final
Acceptance Certificate,..
.During the above maintenance period, the Bidder shall keep sufficient and competent
technical personnel who are well trained to localize and attend to the faults and for the
routine/ periodic maintenance mutually agreed with the Telecommunication Infrastructure
Company. Telecommunication Infrastructure Company technical personnel will
participate in all types of operations and maintenance during this period.
.The Bidder shall provide full access to technical support personnel from first line to
third line or expert support on a x x (twenty four hours per day x seven days per
week throughout the entire year). A dedicated engineer and/or team of engineers shall be
responsible for the Telecommunication Infrastructure Company account. The Bidder shall
provide contact e-mails such as phone number, cell phone number, and e-mail and web
address.
.The Bidder shall keep sufficient stock of spare parts in the Islamic Republic of Iran to
provide mission critical support.
.The technical maintenance of the software shall include the application of all relevant
debugging, enhancements, updates, recommended upgrades, and new revisions/version of
the software. It does also include technical assistance and support to the staff of
Telecommunication Infrastructure Company for system operation and administration.
.The Bidder shall provide detailed and clear escalation procedures applicable to all
works, including escalation to third party suppliers/manufacturers. The escalation
procedures must define fault response and resolution times.
Operation Support Period
.The Bidder shall provide a proposal for operation support for a period of twelve months,
in which the Bidder will support and operate the entire EMS environment. This period
will start on the date that the Interim Acceptance Certificate has been issued, until one
year after the Final Acceptance Certificate has been issued
.The Bidder shall provide a detailed proposal for the operation support period, detailing
the proposed organizational set-up (team), number of resources and include either specific
resources (CV) or job descriptions. The proposal shall provide a detailed description of
the work performed during the operation period, which shall at least be in line with the
scope of work statement of requirements. If the number of staff cannot be determined
exactly, the Bidder shall quote for one resource for each of the different jobs. The
following shall be taken into account:

The Bidder shall manage, operate and support the entire EMS
environment including help desk and CC operations on a xx
basis (twenty four hours per day, seven days per week, and days
per year).
During the operations support period the Bidder is requested to
supply, test and fine tune all processes required to run the EMS
environment, e.g. trouble ticketing, order handling etc.
All processes shall be properly documented and must comply with
ISO quality standards.
The Bidder shall have transferred the knowledge required to operate
and support the entire EMS environment latest by the end of the
operations support period to the personnel of Telecommunication
Infrastructure Company.
The Bidder shall reduce his own staff gradually during the operation
support period. The staff of Telecommunication Infrastructure
Company shall be able to operate, support, and manage the EMS
environment independently at least three months before the end of
the operations support period. The Bidder shall provide a proposal
on how to achieve this goal.
The Bidder shall complete the on-job-training of all
Telecommunication Infrastructure Company resources, which
include the required training on the developed operation processes
and procedures three months before the end of the Operation
Support Period.
For the last three months of the Operation Support Period the Bidder
shall constantly monitor and vet the day to day operation by the staff
of Telecommunication Infrastructure Company. The results shall be
reported on a weekly basis and corrective measures shall be
proposed if the quality of the operation, support and maintenance as
carried out by the staff of Telecommunication Infrastructure
Company is not satisfactory.

-)Provision of Documentation and Software
.The Bidder shall provide all necessary documentations such as:
a. Equipment
b. Software and Applications
c. Software and Hardware Configurations
d. Operational processes and procedures
e. Solution architecture and interfaces
f. Installation and commissioning procedures
.The Bidder shall provide complete Operations and Maintenance manuals for the
provided solution.

.The Bidder shall provide a detailed list of documentations that will be provided, with a
short description of each book or manual.
.All documentations shall be provided in softcopy (CD-ROM) and hardcopy, with
enough quantity of each of softcopies and hardcopies.
.The Bidder shall supply enough back-up copies (Tape, CD-ROM and ...) of all
software(s) supplied, which will include the operating software, application software, and
installation manuals.
-)Customer contract/ SLA & QoS management:
Customer contract SLA/QoS management is responsible for management and
administration of relevant customer- and its contract, QoS & SLA related data for the
existing customers of each service group. The customer contract SLA/QoS management
system shall be a central module that has to provide up to date customer contract
SLA/QoS management and other customer administration data to all relevant function
blocks in the area of Service Fulfillment, Service Assurance Customer interface
management and Billing.
Customers may be flat customers, business customers, company customers or large
account customers. All data items shall be grouped according to:
. Customer data
. Contract data/services
. Transmission service equipment data
. Flat Company
. Large Company
The system has to support the management of all kinds of customer data relevant fields.
The supplier has to give a detailed description of its system capabilities
All customer relevant data fields must be configurable as mandatory or not.
At least the management of the following customer data relevant fields have to be
supported by the system:
. Unique customer ID.
. First name of the customer
. Second surname
. Name of the customer.
. Name of the company.
. Legal status of the company
. Customer specific contact person.
. Contact telephone number of the customer.
. E-mail address of the customer.
. Fax number of the customer.
. Date of birth of the customer.

. The address format and fields shall be flexibly configurable for each of the listed
address types. The supplier shall give a detailed description of the capability of its
solution:
Business address
Delivery address for bill and bill part
Alternative address for the itemized bill
. Banking data and banking arrangement data
. Credit/Debit card data
. Taxation relevant customer data (such as tax numbers, VAT codes, etc.)
. Payment related data
The system shall support management of all transmission service related customer
resource information in accordance with the related contracts (e.g. equipments like
network termination units)
The system shall support the management of different customer groups (segments) related
data. The supplier shall give a detailed description of its system capabilities in this regard
for at least the following customer groups:
. Business customers
. Large corporate customer
. VIP customer group.
The system shall support the management of risk class related data. In addition, the
system shall automatically assign customer to certain risk classes based on a scoring
algorithms. The supplier shall give a detailed description of its system capabilities. As for
the risk class data management ,the system shall support at least
a. Low risk classes
b. Medium risk classes
c. High risk classes
d. Very high risk classes
The system shall support customer attribute related data management (i.e. VIP,
Government, Military, Industry, etc.)

-)Customer contract, QoS/ SLA data administration

. It must be possible to link each contract (at least) to one customer. Each customer
shall be able to have many contracts with one or several services and products.
. The system shall support different contract, QoS/ SLA types (i.e. for leasing, fixed
lines, support, etc..). The supplier shall give a detailed description of its system
capabilities
. At least the following contract QoS/ SLA related data shall be supported and
managed by the system:

a. Unique Contract QoS/ SLA IDs
b. Beginning and end of contracts, QoS/ SLAs with effective dates
c. Details about the service packages and QoS contracted by the customer and
defined in SLAs
d. Details about all services & QoS contracted by the customer and defined in
SLAs.
e. Flags about activation/deactivation/suspension date & effective dates
f. Information about the contracted tariff/rate/ discount plans with effective
dates
g. Information about the service duration and QoS & SLA time frames
h. Data about the dealer, service provider, rd parties, etc (e.g. name,
address).The supplier shall give a detailed description of its system
capabilities.
i. Status information related data about the contract (i.e. active, suspended
etc.), SLA and QoS parameter.
i. Information about the actual tax code for the contract.
ii. Information about the actual VAT type for the contract.
iii. Relevant data regarding contracted tax exemptions for the customer
iv. Data about the contracted payment methods (e.g cash, postal,
check, direct debit, ...)
v. Information about the contracted payment mode (i.e. advanced,
credit).
vi. It shall be possible to define contract relevant flexible fields for
specific contract concessions. The supplier shall describe its system
capabilities in detail.





Chapter: Seven



) ASON/ASTN
-) Introduction
The vendors should establish ASON/ASTN technology for NG-SDH and DWDM, their
proposed equipment shall be based on these technical specifications. They may also put
forward their suggestions along with the detailed information and descriptions according
to the specific situation about the technical performance of their own products.
-) Structure
The transport plane (TP), the control plane (CP) and the management plane (MP), must be
separated not only in terms of logical functions, but also should be separated physically to
satisfy the following function requirements:
--)Transport Plane
The transport plane of the ASON/ASTN must adopt the SDH and OTN technology, and
its network nodes shall comply with the basic function requirements for the SDH and
OTN nodes respectively defined in G. and G..
--) Control Plane
The control plane should be according to the relevant recommendations such as ITU
G. and G..
The control plane of the ASON/ASTN shall meet the following basic function
requirements:
---) It shall provide distributed connection control and management functions,
including connection establishment, deletion, query and modification.
---) It shall provide the routing function, including the distribution of routing
information and the calculation of the routes.
---) It shall provide the signaling function which it shall be able to implement
connection management.
---) It shall provide the auto discovery function, including neighbor discovery,
resource discovery and topology discovery.

---) It should provide the link management function. The control plane shall be able
to maintain control channels, data links and traffic engineering links between it's two
adjacent nodes, and isolate and locate the errors that occur to any of the data links, so as to
implement fast protection/restoration.
---) It shall be applicable to different network topologies including chain, ring and
mesh networks.
---) It shall be able to provide multiple protection/restoration mechanisms.
---) It shall adopt the standard control plane protocols and shall be able to implement
interconnection and interworking in complex environment networks such as the multiple-
vendor environment, the multi-network domain environment and the multiple-operator
environment, so as to implement end-to-end connection management.
---) The proposed system OIF confirmation documents should be submitted.
---) It shall explain the techniques for increasing control plane reliability,
expandability and efficiency.
---) The failure of the control plane shall not affect the existing connections in the
transport plane.
---) It shall have the ability to process collisions that may occur when there exist
two or more simultaneous quests for using the same network resources.
---) The logic topology of the control plane shall be independent of the physical
topology of the transport plane.
---) Its software shall adopt the modular structure.
- The maintenance or update of any module or the append of a new module shall not
affect the other modules.
- The errors within a certain software module shall be controlled within the same module
without causing any errors to the other software modules.
---) The last version of the utilized software shall be provided and specified. The
date of software release must be also specified.
--) Management plane
The management plane of the ASON/ASTN shall meet the following basic function
requirements:
---) It shall implement maintenance management of the transport plane, the control
plane and the whole system.

---) It shall also be responsible for the coordination between the three planes.
---) It shall complete five TMN functions as specified in M.: Performance
management, fault management, configuration management, customer management and
security management.
---) It shall be able to implement the basic connection management functions,
including connection establishment, connection deletion, connection query and connection
modification.
---) It shall be able to set the attributes of connections.
--) Interconnection Model Between ASON/ASTN and the
Customer Network
The overlay model shall be adopted for the interconnection between the ASON/ASTN and
the exsiting customer network.
--) Intelligent Control Mode
The ASON/ASTN is required to support the distributed intelligent control plane.
-) Functional Requirements for Control Plane
--) Connection Management
---) The ASON/ASTN shall be able to provide the following three types of
connections:
a) Permanent Connection (PC)
b) Switched Connection (SC)
c) Soft Permanent Connection (SPC)
---) The ASON/ASTN control plane shall be able to establish connections as follow:
a) Connection establishment mode: The control plane of the ASON/ASTN shall be
able to support the following three modes of connection establishment:
A. Auto establishment of connections
B. Manual establishment of connections
C. Semi-auto establishment of connections
b) The control plane of the ASON/ASTN shall be able to establish connections at the
granularity bandwidth of VC and VC.
c) Origination of the connection establishment request: The control plane of the
ASON/ASTN shall be able to support the following mode to originate a
connection establishment request:

A. User-originated connection establishment request, usually the
establishment request of a Switched Connection (SC).
B. NMS-originated connection establishment request, usually the
establishment request of a Soft Permanent Connection (SPC).
---) The ASON/ASTN control plane should support the connection query and
modification functions. When necessary, it shall be able to query the states or attributes of
connections.
---) The attributes that should be able to be modified: Bandwidth modification (add
or delete virtual concatenation members through cooperation with the LCAS), service
class modification (modify high-class services into low-class services; support the change
of low-class services into high-class services when network resources permit).
---) Vendors should specify system capability in supporting the customer to directly
request via signaling for connection modification. The control plane should have the
upgrade capability in this respect and the equipment vendors should be able to provide
upgrade service for the operator if the operator has such requirements in the future. (The
vendors should state which attributes of connections can be modified and which cannot, as
well as the impact of modifying connection attributes on services)
--) Auto Discovery and Link Management
---) The control plane of ASON/ASTN should have the auto discovery and link
management functions
---) In addition to supporting auto discovery, the control plane should also support
manual configuration. The relationship between the manually-configured information and
the information obtained through auto discovery can be as follows:
a) The manually-configured information can overwrite the information obtained
through auto discovery.
b) The manually-configured information can supplement the information obtained
through auto discovery.
---) Auto discovery shall be able to automatically discover neighbors, resources and
topology.
(The vendors should describe the auto discovery technology that is adopted for their
equipment, including the used protocols and implementation mechanism)
---) The equipment of different vendors may adopt different protocols to manage
link resources, such as LMP, OSPF-TE, PNNI and other private protocols. To adopt the
LMP as the link management protocol, the relevant requirements of IETF shall be
satisfied.
(The vendors should describe the link management technology they adopt for their
equipment, including the used protocols and implementation mechanism)


--) Routing
The routing of the ASON/ASTN control plane should satisfy recommendations G.
and G.. In addition to implementing the two basic functions (distribution of network
topology/resource information and path calculation), the control plane of ASON/ASTN
should satisfy the following function requirements.
---) Intra-domain routing protocol: It is required that the OSPF-TE protocol be
adopted as the intra-domain routing protocol.
---) Inter-domain routing protocol: The options include BGP, OSPF-TE and DDRP.
---) The following four types of disjoint routes should be supported:
a) Link disjoint
b) Node disjoint
c) Shared Risk Link Group Disjoint (SRLG Disjoint)
d) Path correlation
---) The definition of the Shared Risk Link Group (SRLG) should be flexible and
defined physically and logically. (The vendors should describe how to define the SRLG
and the corresponding operation process in details.)
---) The following constraint conditions should be supported during route
calculation:
a) Link management weight and path cost.
b) Path shortest first.
c) Bandwidth.
d) The nodes and links that must be passed.
e) The nodes and links that cannot be passed.
--) Signaling
The ASON/ASTN signaling shall be accordding to recommendations G. and
G. and it shall meet the following function requirements.
---) Basic requirements:
a) It should support established connection, deletion, query and modification
b) It should support inband and outband channels as well as the separation of
control channels from data channels

c) It should implement the priority transfer of signaling messages to ensure that the
protection/restoration signaling message can be processed first and help quick
protection/restoration operations.
d) It should support the selection of UNI signaling.
e) Inter-domain and intra-domain signaling protocols should be relatively
independent.
f) It should have the expandable signaling capability set.
g) It should guarantee the performance requirements of the network and must
minimize the impact of the network scale on the network performance
---) The control plane of ASON/ASTN should support recommendation ITU-T
G.. (RSVP-TE signaling protocol).
---) The control plane of ASON/ASTN should be capable of selecting signaling
protocol between ITU-T G.. (PNNI) and G.. (CR-LDP).
---) The ASON/ASTN technology of the respective vendor should be compatible
with the ASON/ASTN technology of the other vendors and otherwise should give
sufficient solution.
---) In order to suite the RSVP-TE signaling for distributed call and connection
management functions of ASON/ASTN, it's signaling protocol should be expanded in
accordance with Recommendations ITU G., ITU G. and G...
---) The RSVP-TE signaling should support the establishment of soft permanent
connections (SPCs).
---) To enhance the explicit route functions, the RSVP-TE signaling should provide
explicit label control.
---) The RSVP-TE signaling should support the transfer of connection protection
feature. Upon receipt of the path message that carries the protected object, the node must
check if it supports the required protection feature. Only the connection request that
satisfies the expected protection type requirements will be further processed.
---) The RSVP-TE signaling should introduce new administrative status information
objects to transfer them and it should have the following two functions:
a) Indication of the connection status.
b) Setting of the connection management status.
---) The control channel of ASON/ASTN can be separated from the data channel.
In that case, the control channel has no one-to-one correspondence with the data channel.
In order for the control channel to identify the relevant data channe correctly l, the RSVP-
TE signaling should be able to use the expanded interface ID object to identify each data
channel.

--) Graceful deletion
The RSVP-TE signaling should support the graceful deletion of connections, i.e. first, a
signaling message should be sent to notify each node of the connection before the
connection is really deleted.
--) Naming and Addressing
In order for the network to have good expandability and smooth evolution capability, the
control plane should support the following three types of network address separation:
a) Node address in the optical transport network
b) TNA address
c) Customer equipment address
--) Reliability
---) The control plane should have good reliability and be able to continue its work
in the case of faults.
---) To improve the network viability, the control plane and the data plane should
have their respective fault detection mechanisms. The fault detection mechanism of the
control plane should be able to differentiate the faults of the control channels from those
of the control plane software, thus implementing the location and isolation of network
faults.
---) The control plane should provide reliable transmission of signaling messages.
---) The network fault of a certain place in the control plane should not affect the
operation of the other nodes in the control plane.
---) Any network fault of the control plane can only affect the service provisioning
capability of the control plane rather than affecting the existing connections in the optical
network.
---) Any failure of the control plane shall not cause failure of the management plane.
---) If the network fault of the control plane affects the connection being established,
the relevant error message should be sent in due time to the source node to reject the
connection establishment request or request for path recalculation, or ask to wait for the
network fault of recovering before reattempting the connection. Also, the partial
established connection should be deleted in time.
---) After the network fault of the control plane is recovered, quick synchronization
of various status messages between the relevant nodes should be implemented to recover
various status information, including the connection status of the transport plane, the
connection status of the control plane and the available network resources. The node with
its fault recovered should be able to re-obtain the connection information of its neighbors

and should be able to re-obtain the status information of the established connections
before the fault also occures.
---) If any incomplete partial connection is detected in the network after the network
fault of the control plane is recovered, the incomplete partial connection should be deleted
in time.
--) Security
---) Incorrect connections should be prevented during the connection establishment
process.
---) The control plane itself should have the appropriate security mechanism to
guard against illegal intrusions.
---) The control plane should be able to prevent various unrecognized access, strictly
authorize and authenticate the users entering the control domain, and restrict the network
resources used by the users according to the management policies of the operator.
---) The control plane should not be able to distribute the route topology information
of the optical network via the UNI to outside the optical network.
---) The control plane should be able to securely and reliably transfer various
discovery information (including neighbor discovery, resource discovery and topology
discovery) and freachability information. It should ensure the integrity and confidentiality
of various connection management information (such as connection
establishment/deletion/query/modification).
---) The control plane should be able to periodically transfer its various event
information related to security to the management plane.
---) The management plane should be able to analyze and judge these event
information to check if such information violates or threatens the security measures of the
control plane, and should implement the corresponding policies.
---) The control plane should be able to generate various alarm information related
to security events, and periodically transfer such information to the management plane.
-) Technical Requirements for Protection/Restoration
--) The ASON/ASTN is required to have multiple protection/restoration mechanisms,
so as to meet the different network application requirements.
--) ASON/ASTN should map the different classes of services into the different
protection/restoration mechanisms, so that during the connection establishment the
ASON/ASTN is able to adopt the corresponding protection/restoration mechanism
according to the COS parameter.

--) The ASON/ASTN equipment is required to support protection switching of the
traditional SDH networks as well as mesh protection/restoration.
--) Traditional SDH Protection Switching Capability
---) The ASON/ASTN node based on the SDH technology should support the SDH
protection switching function and the available protection mode should include the
following:
a) Multiplex Section Protection (MSP)
b) Multiplex Section Shared Protection Ring (MS-SPRing)
c) Sub Network Connection Protection (SNCP)
d) Dual Node Interconnection (DNI) protection
---) The switching time shall not be more than ms in the case of protection
switching upon failure of a node.
---) Of the above, MSP, MS-SPRing and SNCP should meet the requirements set
forth in Recommendation G. while DNI should meet the requirements set forth in
Recommendation G..
--) Mesh Protection/restoration Capability
---) The mesh protection/restoration of the ASON/ASTN shall meet the following
basic function requirements:
a) The ASON/ASTN should support multiple mesh protection/restoration
mechanisms and these mechanisms should be able to correspond to the classes of
services, so as to meet the diversified requirements of various services for
protection/restoration.
b) The control plane should support the modification of the protection/restoration
attributes of connections.
c) The control plane and the transport plane should have their respective fault
detection mechanisms.
d) The control plane should provide a reliable transfer mechanism of
protection/restoration messages. The transfer of the protection/restoration
message should be able to resist multi-point network faults.
e) To ensure the protection/restoration performance, the control plane should first
process the protection/restoration signaling messages.
f) The normal connection management operations (such as connection deletion or
modification of some attributes of a connection) should not cause the start of the
protection/restoration process.

g) To facilitate the operation, maintenance and management of the network, the
management plane should be able to start the protection/restoration process.
h) The control plane should support multiple restoration priorities and should
process the high-priority connections first.
i) In the case of protection/restoration of a connection, the control plane should
keep the status information of this connection until the protection/restoration
succeeds.
j) In the case of restoration failure of a connection, the control plane should delete
the partial connection already established in the restoration attempt process.
---) In the case of network faults, the fault message should be able to be quickly
transmitted to the relevant node, so as to start the protection/restoration process.
---) The vendors should state which type of fault transfer mechanism they adopt.
---) With the participation of the control plane, the ASON/ASTN should be able to
dynamically provide the protection path.
---) The working path works normally but network faults occur to the protection
path:
In this case, the ASON/ASTN should be able to establish a new protection path for
the working path with the participation of the control plane. It should meet the following
function requirements:
a) It should report the relevant event to the control plane and the management
plane in time.
b) When the fault is cleared, it should be able to return to the original
protection path or maintain the current protection path according to the
NMS setting.
---) Network faults occur to the working path works while the protection path works
normally:
When network faults occur to the working path, its service should be timely switched
over the protection path while the original protection path should become the working
path. With the participation of the ASON/ASTN control plane, a new protection path
should be able to be established and the ASON/ASTN should satisfy the following
function requirements:
a) It should timely report the relevant event to the control plane and the
management plane.

b) In the case that the fault is cleared, it should be able to return to the original
working path or maintain the current working path according to the NMS setting.
---) With the participation of the ASON/ASTN control plane, the ASON/ASTN
should be able to dynamically provide the restoration path and conduct route calculation
of the restoration path just after the network fault occurs.
---) The ASON/ASTN should support + protection and : protection.
---) + protection should support bi-directional switching mechanism.
---) The + protection switching time should be less than ms.
---) After the protection switching is finished, the protection switching event
should be reported to the NMS.
---) Protection switching criteria: In one of the following conditions, +
protection switching should be conducted:
a) Loss of Frame (LOF)
b) Loss of Signal (LOS)
c) Multiplex Section AIS (MS-AIS)
d) B/B Bit error threshold exceeded (BOVER/BOVER)
---) In : case, the ASON/ASTN should meet the following function
requirements:
a) It should adopt the bi-directional switching mechanism.
b) The protection path should be able to transmit the extra low-priority services.
When the working path is faulty, the low-priority services of the protection path
should be discarded.
c) After the protection switching is finished, the protection switching event should
be reported to the NMS.
d) After the working path recovers from fault, the services should be able to be
returned. However, a certain time is required before the services can be returned
and this waiting time should be able to be set through the NMS in the unit of
second.
---) Protection switching criteria: In one of the following conditions, :
protection switching should be conducted:

a) Loss of Frame (LOF)
b) Loss of Signal (LOS)
c) Multiplex Section AIS (MS-AIS)
d) B/B Bit error threshold exceeded (BOVER/BOVER)
---) The ASON/ASTN should support two trigger modes of mesh rerouting:
A. Hard rerouting
a) It means the mesh rerouting automatically triggered by the network fault.
b) Upon completion of the rerouting, the rerouting event should be reported to
the NMS.
B. Soft rerouting
c) Soft rerouting is manually triggered through the NMS for the goal of
network management
d) It should satisfy the requirement of Make-Before-Break, i.e., the
restoration path is established first and then the working path is
disconnected.
e) During soft rerouting, the system should be able to implement the rerouting
based on the constraint conditions.
---) Hard rerouting should be conducted in one of the following conditions:
e) Loss of Frame (LOF)
f) Loss of Signal (LOS)
g) Multiplex Section AIS (MS-AIS)
h) B/B Bit error threshold exceeded (BOVER/BOVER)
---) The network should be able to return to the original working path or maintain
the current working path according to the network policies of the network operator and the
NMS setting.
---) In the case of returning to the original working path, the following function
requirements should be satisfied:
a) The return operation should not impact the services.
b) Till the end of the switching, the restoration return event should be reported to
the control plane in time.

---) Priority requirements of mesh restoration
- Since, it cannot be guranteed that there are sufficient network resources to recover all the
affected network connections, the ASON/ASTN should support the priority division of
mesh restoration, so as to guarantee that the important services will be recovered before
less important ones. (The vendors should state the restoration priority division mechanism
adopted for their equipment.)
- There are two processing modes when multiple mesh restoration circuits of the same
priority are faulty:
a) Serial processing.
b) Parallel processing.
---) The ASON/ASTN should provide the mesh protection/restoration capability of
large traffic cases and it should be able to protect and recover multiple paths
simultaneously.
---) The ASON/ASTN should guarantee that all the recoverable mesh protection
paths can complete protection switching within ms.
---) Mesh restoration time: Suppose that there is such a network: . ASON/ASTN
nodes composing a mesh network whose diameter reaches at most .. km and all the
nodes are located in .. control domains. Each node adds/drops .. connections and their
destination nodes can be any node in the entire network. Then the mesh restoration time is
required as follows: In the case of a single network fault, the restoration time of all the
recoverable mesh connections should be less than . seconds.
---) Path modification capability requirements of connections: The cause of
modification may be one or more of the following:
a) As viewed from the current network resources, the path used by the old
connection is not the best.
b) The actual path is inconsistent with the path in the network plan.
c) The modification is for maintenance management.
d) The modification is for traffic engineering.
---) The ASON/ASTN should support the path modification of the existing
connections and should satisfy the following requirements:
a) The new connection may be established in the auto, semi-auto or manual mode.
b) The switching operation should be triggered by the NMS.
c) The switching should not impact the existing services.

---) Coordination mechanism of mesh protection/restoration: to avoid
simultaneously starting the protection process and the restoration process, ASON/ASTN
should adopt the mode of protection first and restoration next.


--) Mutual Conversion Between the PC Service and the SPC/SC
Service
In mutual conversion between the PC service and the SPC/SC service of ASON/ASTN,
the statically assigned services should be able to be smoothly upgraded to the dynamic
connection services or vice versa.
a) The network nodes should be able to implement smooth ASON/ASTN software
load or unload.
b) The services should be able to implement smooth online interconversion between
dynamic connection SC/SPC and static connection PC.
-) Technical Requirements for the Transport Plane
--) Node
The nodes in the ASON/ASTN transport plane based on SDH should satisfy the basic
function requirements of SDH nodes, as well as the specific requirements given in the
specifications of G..
---) Cross-connect capability
----) The equipment should have a flexible SDH VC cross-connect matrix with the
cross-connect granularity of VC and VC. (The vendors should provide a detailed
description of the cross-connect specifications.)
----) For the OXC equipment, the bi-directional non-blocking cross-connect
capacity of a single rack should be at least G. The cross-connect matrix shall have
smooth online upgrade and capacity expansion capability. (The vendors should provide
details about the upgrade and capacity expansion of the cross-connect matrix.)

Table -: bi-directional non-blocking cross connect capacity
MSTP (Type ) MSTP (Type )
OXC
G G G
Min HO XC

G G G
Min LO XC

----) The supported cross-connect types should include:
a) Unidirectional
b) Bi-directional
c) Unidirectional broadcast
d) Loopback
e) Drop & continue
----) Online detection of services:
Within the broadcasting via cross connection without interrupting service connections
after the service provisioning, the equipment should provide the function to online
detection services, as shown in the following figure
Equipment
Service ingress Service egress
Online detection
interface of services

Fig. -: online detection of services
----) The online detection of services should satisfy the following function
requirements:
a) The cross connection used for detection should be able to be created and deleted
by configuring the cross-connect matrix, and such creation or deletion should not
cause any impact on the services.
b) The detection granularity should reach the VC level.
c) There should be no special requirement for the service detection interface, and

the system should be able to use any idle service interface that can satisfy the
required rate in the equipment as the service detection interface.
---) Service capability:
----) The supplier shall state system capacity for MSTP service.
ATM E E STM- STM- STM-
STM- STM- FE GE GE


----) The supplier shall state system capacity for OXC services.
ATM E E STM- STM- STM-
STM- STM- FE GE GE


---) Hot backup capability of boards/cards
----) The node should implement hot backup of multiple types of boards/cards,
which should at least include the control board, the cross-connect board, the power board
and the clock board. (The vendors should give a detailed description of the hot backup
capability of the boards/cards they provide.)
----) Forced active/standby switch-over should be able to be executed on the
boards with hot backup through the NMS.
----) The plugging/unplugging and switch-over operations of the control board
with + protection should not cause any impact on the existing services. The faulty
control board, once repaired, should be able to synchronize information with the currently
working control board rapidly.
----) The plugging/unplugging and switch-over operations of the cross-connect
board with hot backup should have minimum impact on the existing services and the
impact time should be at the millisecond level. The faulty cross-connect board, once
repaired, should be able to synchronize information with the currently working cross-
connect board rapidly.
----) The plugging/unplugging and switchover operations of the power board and
the clock board with + protection should not cause any impact on the existing services.

--) Networking Capability
In addition to supporting the traditional SDH ring and chain networking modes, the
transport plane should support mesh networking.
--) SDH interface
---) The interface requirements of the SDH-based multi-service transmission node
are given in the table below.








Table -: Types of SDH interface and their requirements


---) GE interface requirements:
a) The GE interface supported by the ASON/ASTN nodes should be according to
requirements given in IEEE . z.
b) The GE physical interface should support Base-SX and Base-LX.
Interface Interface type Satisfied standard
Optical interface
STM- ITU-T/ G.
STM- ITU-T/ G.
STM- ITU-T/ G.
STM- ITU-T/ G.
Electrical interface M ITU-T/ G.

--) Ethernet Service
---) The ASON/ASTN should support the point-to-point transparent transmission of
Ethernet services and guarantee the transparency of the protocols in L and above.
---) Encapsulation protocols of Ethernet data frames: The GFP encapsulation
protocol should be adopted. The specific technical specifications of the GFP should
satisfy the requirements in ITU-T G.
---) Mapping of Ethernet services into SDH containers: The equipment is required to
provide the virtual concatenation mapping and the consecutive concatenation mapping
modes of VC channels, so as to provide channels of the appropriate size for use by data
services and guarantee the integrity of the data frames during the transmission.
---) The mapping of Ethernet interfaces into SDH containers should satisfy the
requirements as given in the table below.
Table -: Mapping of Ethernet interfaces into SDH containers
Ethernet interface SDH mapping unit
Mbit/s adaptive interface
VC--Xc/v
VC--Xc/v
---) When virtual concatenation mapping is adopted, the system should support the
LCAS mechanism and should be able to dynamically adjust the number of virtual
concatenations.
---) The specific technical specifications of the LCAS should satisfy the
requirements in ITU-T G..
---) All VC containers should be able to be transmitted on different physical routes.
---) When a certain VC member in the network fails, the system should be able to
automatically reduce the concatenation capacity, and when the network recovers, the
system should be able to automatically increase the concatenation capacity.
---) The ASON/ASTN should support the manual/forced increase/decrease of the
concatenation capacity.
---) When a member fails, the system should be able to keep effective data
transmission for normal members.

---) The ASON/ASTN should be able to seamlessly increase or decrease
bandwidth, and such increase/decrease should not cause any damage to the services when
the bandwidth is sufficient.
--) Node Performance
---) The SDH performance indices of the ASON/ASTN nodes should satisfy the
requirements related to the SDH equipment interfaces as given in ITU-T G..
---) For the store-and-forward and forward-by-bit equipments, forwarding delay
should be low. (The vendors should state the typical delay value.)
-) Timing & Synchronization Requirements
The ASON/ASTN should support and satisfy the requirements of timing &
synchronization section.
-) NM Function Requirements
The ASON/ASTN should support and satisfy the requirements of NM function section.

Chapter: Egiht

) Maintenance


-) Introduction
The vendor must provide all the obligations for maintenance and equipment support
aforementioned below.
-) Obligations for maintenance and technical support
--) If the equipments are damaged in a period of five years since first installation and
establishment, the faulty parts must be exchanged by the vendor.
--) The system must have appropriate direction for system maintenance for failure
prevention, performance improvement and failure removal.
--) The system must have sufficient direction for routine maintenance in order to
avoid failure occurring.
--) The vendor is required to train maintenance personnel.
--) The vendor is required to support the possibility of establishing -hour
connection between maintenance personnel and expert personnel of the vendor for
consultation and guidance up to final equipment delivery.
--) The vendor is required to provide a list of units and spare parts needed for
operation in a five year maintenance period after the guarantee period.
--) The vendor should provide a list of the time between failure and exchange time of
the parts of the equipment.
--) The vendor is required to give technical information about each of the parts and
units of the system separately. If failure occured in a part of the system which the vendor
has not provided it's technical information, the vendor is obliged to pay for the damages.
--) The vendor is required to provide maintenance services in software part of the
system, including: software installation, software upgrading, providing back up copy,
installing necessary softwares for protection and the way of using software.

--) The vendor is required to provide reformatory performances including: finding
and localizing failure, failure removal and exchanging the faulty parts.
--) Maintenance operations must be done locally or by TMN.
--) There should be appropriate warning marks in the system for maintenance
operation.
--) The warning marks should be in three forms: emergency, inemergency and
indicative.
--) The system must be capable of measuring the characteristics of input/output
optical signal of each unit.
--) The parameters values displayed by the software must be the same as the values
measured by the hardware.
--) The system must be capable of measuring all parameters related to PDH signal
quality and NG-SDH signal quality by local management or TMN on the basis of G.
standard.
--) The vendor is required to give information about measurement devices and
instruments necessary for system maintenance.
--) The vendor is required to supply a list of needed equipments and also to repair all
the system units including hardware and software repair in the system maintenance
period.
--) The vendor is required to establish the mobile maintenance unit to provide
emergency maintenance services for equipment failure removal. The MMU must have the
capability of standard tests and must have appropriate technical science for failure
removal. In case of failure occurring the team must be equipted with necessary
measurement instruments like: network analyzer (electrical-optical), OTDR, movable
power meter, optical source,variant optical attenuator, connectors, and necessary
transformers and appropriate toolbox for cable failure removal and fiber.
--) Software look back tests in all levels should be possible.
--) Since the repair of fundamental units is done by manufacturer company, the
repair cost of every unit must be determined in first year, second year, third year up to the
end of the average work period of the system. It is necessary to mention that the repair
costs will be payed after the guarantee period. Furthermore, the costs must be on the basis
of units classification.
--) Repairing a unit and returning it by the contractor should not take more than
month.

Chapter Nine
) Training
-) Introduction
TIC has given the crucial role to training and maximum transferring of technical
knowledge (planning, installation, commissioning, maintenance, management). Training
courses and their requirements have been discussed in this section.
-) Training courses
Training will be done in the following categories:
Instruction and supervision
Planning
Installation & commissioning
Maintenance & Operation
The list ..shows the whole subjects which must be considered in training courses.
Afterward, these subjects are categorized based on trainees profession in order to define
courses. Along with courses title, participants assumed background and planned
expectations are mentioned.
--)Whole subjects
---)WDM & NG-SDH, Systems and networks: Principles and overview
---)WDM & NG-SDH, Systems and networks: network architectures (layer
network architectures, hybrid networks and reference architectures)
---)Traffic handling, old and new methods: description and comparison
---)Network topologies and protections: methods description
---)Network topologies and protections: designing (methods, strategies and design
algorithms)
---)Planning: planning software
---)Optical line active/passive components: necessities and power budget
calculations
---)Synchronization: aspects, necessities and reference clock supply networks
(overview)
---)Synchronization: designing (methods, strategies and designing algorithms)
---) Equipments structure (Rack, subracks, units, connectors ): description
and technical specifications.


---)Equipment installation: physical aspects and installation instruments
---)Equipment installation: accessories, jumpers position, cables. and practice
of installation.
---)Equipment commissioning: initial programming and upgrade procedure
(practice)
---)Equipment commissioning: startup and system configuration (software
practice)
---)Equipments working modes: alarms, events and performance parameters.
---)Equipments working modes: periodic checks and troubleshooting.
---)Out of service test: system tests
---)In service test: loaded link tests
---)Network management: overview
---)Network management: management layers and protocols, instrument
requirements, DCN
---)Network management: software (installation and practice)
---)Probable changes in this generation of systems: discussion
--)Instruction and supervision course
Trainees should have an appropriate background in transmission systems and networks
and are expected to be in charge of technical or instruction support for this project.They
must be able to train and supervise TIC personals independently.
---) Circumstance
Location: bidders training center
Number of participants:
Total duration days: working days
Theory/practical: working days
Absolute practical: working days
During the Practical work the trainees will be
divided into subgroups:
Planning
Network management
NG-SDH
WDM

---) Course Subjects
.... WDM & NG-SDH, Systems and networks: network architectures (layer
network architectures, hybrid networks and reference architectures)
.... Traffic handling, old and new methods: description and comparison
.... Network topologies and protections: designing (methods, strategies and design
algorithms)
.... Planning: planning software

.... Optical line active/passive components: necessities and power budget
calculations
.... Synchronization: designing (methods, strategies and designing algorithms)
.... Equipments structure (Rack, subracks, units, connectors ): description and
technical specifications.
.... Equipment commissioning: initial programming and upgrade procedure
(practice)
.... Equipment commissioning: startup and system configuration (software
practice)
.... Equipments working modes: alarms, events and performance parameters.
.... Equipments working modes: periodic checks and troubleshooting.
.... Out of service test: system tests
.... In service test: loaded link tests
.... Network management: management layers and protocols, instrument
requirements, DCN
.... Network management: software (installation and practice)
.... Probable changes in this generation of systems: discussion
--)Planning course
Trainees should have an appropriate background in PDH/SDH networks and are expected
to be able to use planning software and carry out plans independently. They will be in
charge of network planning for this project.

---) Circumstance
Location: bidders training center Location: Iran with bidder trainer
Number of participants: Number of participants:
Total Course: working days
Total Course: working days

---) Course Subjects
.... WDM & NG-SDH, Systems and networks: Principles and overview
.... Traffic handling, old and new methods: description and comparison
.... Network topologies and protections: designing (methods, strategies and design
algorithms)
.... planning: planning software
.... Optical line active/passive components: necessities and power budget
calculations
.... Synchronization: aspects, necessities and reference clock supply networks
(overview)
.... Equipments structure (Rack, subracks, units, connectors ): description and
technical specifications.
.... Equipment commissioning: startup and system configuration (software
practice)
.... Network management: overview
.... Network management: software (installation and practice)






--)Installation & Commissioning course
Trainees should have an appropriate background in PDH/SDH systems and are expected
to be in charge of installation and commissioning of the systems.

---) Circumstance
Location: bidders training center Location: Iran with bidder trainer
Number of participants: Number of participants:
Total Course: working days
Total Course: working days

---) Course Subjects
.... WDM & NG-SDH, Systems and networks: Principles and overview
.... Network topologies and protections: methods description
.... Synchronization: aspects, necessities and reference clock supply networks
(overview)
.... Equipments structure (Rack, subracks, units, connectors ): description and
technical specifications.
.... Installation
a) Equipment installation: physical aspects and installation instruments
b) Equipment installation: accessories, jumpers position, cables. and
practice of installation.
.... Commissioning
a) Equipment commissioning: initial programming and upgrade procedure
(practice).
b) Equipment commissioning: startup and system configuration (software
practice)
c) Equipments working modes: alarms, events and performance parameters.
d) In service test: loaded link tests
.... Network management: overview
.... Network management: software (installation and practice)
--)Maintenance & Operation course
Trainees should have an appropriate background in PDH/SDH systems and are expected
to control the performance of target systems and have the ability to do general
maintenance, prompt maintenance and troubleshooting.

---) Circumstance
Location: bidders training center Location: Iran with bidder trainer
Number of participants: Number of participants:

Total Course: working days
Total Course: working days

---) Course Subjects
.... WDM & NG-SDH, Systems and networks: Principles and overview
.... Network topologies and protections: methods description
.... Synchronization: aspects, necessities and reference clock supply networks
(overview)
.... Equipments structure (Rack, subracks, units, connectors ): description and
technical specifications.
.... Equipment commissioning: startup and system configuration (software
practice)
.... Equipments working modes: alarms, events and performance parameters.
.... Equipments working modes: periodic checks and troubleshooting.
.... In service test: loaded link tests
.... Network management: overview
.... Network management: software (installation and practice) .


-) Training General Requirements

--) The bidder should provide comprehensive training program detailing the subjects,
time duration and description of each item.
--) The bidder should supply the complementary syllabus (if required).
--) The bidder should install and commission all training systems two weeks before the
commencements of each course.
--) The bidder should provide adequate numbers of training documentation & training
aids during all training courses to be conducted.
--) The bidder should provide video-CD from the whole training course & deliver it to
TIC.
--) The bidder should be responsible to supply documents for each course conducted in
Iran one week before the commencements of each course.
--) Where hard copies & softcopies are being provided by the bidder, all training
materials should be of excellent quality.
--) The bidder should provide one set of training manuals & training software for each
trainee.
--) The bidder should provide one CD set of training maintenance & installation &
commissioning & technical manuals for each trainee.
--)All training materials (CD & manuals) should be copy free for TIC.
--)The bidder should conduct all courses in English or Farsi.
--)The bidder should provide all training materials in English or Farsi.
--)The bidder should conduct the practical training according to syllabus.
--)The bidder should conduct the practical training using the same test equipments
which is allocated for this project.





--)The bidders training personnel shall maintain a systematic procedure of
monitoring & reporting the progress of all trainees besides the task lecturing.
--) At the end, the quality of training courses will be evaluated by TIC. The
evaluation criteria will be provided by TIC to the successful bidder before the
training commences.
--)Any local or overseas unsatisfactory training course should be re-conducted
locally in Iran.
--)The bidder should submit following record items of training personnel two months
before the commencement of each course:
--)
a) Academic education & training experience record allocated for this project.
b) Presentation of creditable university certification
c) Creditable training experience allocated for this project.
--)The participation of TIC cannot be used by the bidder to hold TIC responsible for
any damage or delays as a result of their participation. The bidder is fully
responsible for correct supervision, delivering and handling over a free operational
system within timelines of the project.









hapter Ten

) Test Equipment
Technical Specifications of Test Instruments



) General
-) Bidders should propose all kinds of test equipments necessary for installation,
commissioning and maintenance of all equipments in this tender. TIC will decide
to firm the quantity of each type if necessary. Therefore the following items will
be valid in case of selecting any type of test equipments.

-) All test equipments shall be from well reputed manufacturers with guarantee for
calibration and repair maintenance services for a period of years from the of
contract signing date.

-) The contractor shall supply complete instruction manuals and service manual for
operation of the test instruments. All manuals should be in English .

-) Each test equipment shall be supplied with one set of accessories e.g. interfaces,
cables, connectors , adaptors, fixtures, etc.

-) All test equipments should be in strong light weight , dust proof carrying case with
suitable shock absorber padding .

-) The test equipment design must be such that faulty unit parts and components may
be easily identified and replaced. The modular and plug-in concept shall be
utilized in the design of test equipment.


-) Bidders shall provide a price quote for test jigs , extender board , special tools and
connectors special tester and test equipment for repair of proposed test equipment .

-) A schedule of maintenance and repair training shall be included in the technical
proposal .

-) The repair training on module replacement basis is required for all test equipments.

-)The test equipment characteristics and performance shall comply with the latest
ITU-T recommendations .

-)The test equipment shall be packed to withstand severe vibrations as may
encounter during transportation .

-)The test equipment shall be packed to resist fungus or mold during transportation
and storage .

-)The test equipment shall be designed for operation in the field, it shall be equipped
with protective device so that the front panel shall not be damaged due to
accidental shocks.
-) Spare

--)A complete set of spare modules and consumable parts for maintenance ,
repairing and calibration shall be proposed. The quantities shall be sufficient for
years of maintenance .

--)A list of spare modules shall be submitted and included with the
following information :

a) Description
b) Type

c) Part no. ( international part no. )
d) Manufacturer part no.
e) Quantity
f) Price for each item

--)The bidder shall guarantee to furnish the spare modules for a period of years
after delivery .

-) Instruction manual

--)The bidder shall provide proper instruction manuals for all test equipments .
These manual shall contain all information necessary for operation repair and
calibration of each test equipment and shall include the following as minimum :

a)A general description of test equipment, assembly, subassembly
modules(including thin/thick film modules), etc. with block diagrams and
circuit diagram.
b)A complete description of the operation procedure for test equipment.
c)A complete description of the function of each module and circuit.
d)Fault-finding and analysis procedure with diagnostic charts and procedure of
repairing all units and circuits in test equipment .
e)A complete description of the procedure of alignment and calibration of test
equipment .
f)Spare components list comprising all parts used with manufactures name, stock
no, description and any additional data necessary for identification.

--)All instruction manual drawings should exactly show every piece in test
equipment as delivered. Labels, signs and other identification on controls and
parts of test equipment must be identical to that that written in the instruction
manuals, or drawing circuits, etc .

-) Repair training


--)The bidder shall submit price quotation and schedule for training program
designed to train experienced trainees in repair at module level and calibration
of test equipment.



--)At the end of repair and calibration training , the contractor will certify that the
trainees have demonstrated the ability to successfully identify and replace
defective modules and calibration of all test equipments .

--)The training course shall include the following as a minimum :

- Test equipment description and theory of operation.
- Block diagram and circuit diagram description.
- Software structure description (if applicable).
- Repair and trouble shooting procedures for all of the units and circuits and
replacement of module .
- Alignment and calibration procedure for all test equipment.
- Practical exercises on simulated faulty units being performed by the trainees.
- Practical exercises for replacement of faulty modules.
- Checking repaired units for satisfactory results with test equipment.

--)The bidder shall submit price quotation and schedule for maintenance operation
separate training, designed to train trainees for working days.

-) Environment

All test instruments shall meet the following minimum conditions except
otherwise stated .


Continuous Operation :

- Temperature -C degrees to Full performance specifications to be met
+C degrees under use
- Rel humidity up to %

Storage and Transportation in Packages :

- Temperature -C degrees to No damage during storage and
+C degrees transportation
- Rel humidity up to %



-) Power requirements

Dual power input +/-V AC, Hz +/-Hz with battery pack option, if
available.

-)Optical connectors of test instruments should be preferably from FC/PC type. In
case of using any type of connector other than DIN, the bidder should provide suitable
adapter or patch cord for connecting to DIN connectors.


Chapter: Eleven


) Special Tools and Acc


) Special Tools and Accessories for Installation
and Maintenance

List of special tools and accessories, extenders , cables , etc required for installation ,
commissioning and maintenance operations shall be separately recommended and quoted.
Ordinary tools e.g. screw drivers , pliers , cutters , drilling tools , key sets , soldering iron ,
hammers , etc. are not required .

Only special tools with special use for the proposed equipment shall be offered and
identified with its description , make/model. Detailed technical description, their use and
operational features shall be submitted . sets of special tools and accessories should be
offered. ( if needed ) .



Chapter: Twelve


) Technical Support


-)Regarding the complex and wonderment network, TIC needs to be supported by
the contractor after implementation of the project.
This support could be done through dispatching of experts, submitting the
additional documents or short term training.
Bidders also are requested to clearly specify how this support will be performed.

-) The contractor should arrange and establish a supporting team in IRAN
.Bidders should submit sufficient documents in this regard.

-) Bidders should submit the personal specification and qualification of the
mentioned team.

-) Bidders should specify the maximum time to clear the technical problems and
questions announcing from TIC.




Chapter: Thirteen


) Documentation

TECHNICAL DOCUMENTS



-) General

--)The following documents shall be provided by the contractor :

- System manual
- Equipment/system instruction manuals
- Installation manual
- Installation drawings
- Repair manuals
- Factory test procedures and test data sheets
- Field test procedures and test data sheets
- Inventory sheets
- Diskettes of installation and level drawings

--)All documents shall contain the following :


- Description of all volumes of each document ( to be included in all
volumes of the relevant document )
- Content of each volume and section
- Safety information ( where applicable )
- Cautions regarding operation and/or replacement of the modules (where
applicable)
- Guide to use the document
- Complete list and description of all abbreviations and symbols used in each
document, (to be included in all volumes of the relevant document).
--)All documents shall be in English

--)All documents must exactly reflect every piece of equipment as delivered. Lables
, signs and other identification on controls and parts of the equipment must be
identical to that which is written in documents .

--)TIC will prepare any information needed for preparing the installation drawings ,
if the contractor requires and specifies such information .

--)The documents shall contain all information needed to install , test , operate ,
maintain , and repair the equipments / system covered by this specifications .

--)All binders shall be of high quality with metal rings that lock in place .

--)The size of the volumes , pages , characters , symbols , and drawings shall be
properly chosen , so that reading the texts and drawings and using them can be
easily done .

--)All documents shall be delivered to TIC at least two () months before the first
equipment shipment.


--) sets of Soft and Hard copies of all documents shall be provided by the
contractor , and submitted to the TIC planning & engineering department at least
sixty () days prior to the first shipment. Updated or reissued sections shall be
provided as above subsequent release by the supplier .

--)TIC reserves the right to ask for addendum sheets , additional information , or to
reject any part or all of the documents and ask for the revised ones . The
documents which do not satisfy the requirements mentioned in this section or
those mutually agreed upon should be prepared by the contractor. All document
modifications shall be delivered within four () months after TIC request and at
the contractors cost.


-) System manual

--)The system manual shall contain the following as a minimum :

- List of all documents
- General description of the equipments
- MUX plan
- Route plans
- System layout
- System layout of the network management system
- Local and express orderwire system layout ( including the dialing number
of stations)
- Power consumption of each station
- List of maintenance centers and their relevant stations ( included in this
specifications)

- External alarm and status assignment table ( alarm and status list will be
provided by TIC )
- Block and level diagram of each station
- Rack layout of each station
- Rack facing of each station ( showing the units mounted in each rack )
- Brief description of the equipment (including summarized
characteristics of the equipment )
- Brief description of the hardware and software of the network management
system
- Power Budget for each section




-)Instruction manual

--)The following instruction manuals shall be delivered :

- NG-SDH and DWDM equipment instruction manuals
- test equipment instruction manuals
- Network management system hardware instruction manuals
- Network management system instruction manual ( Users Guide )
- Network management system instruction manual ( Administrators Guide)
- Synchronization instruction manuals
- Special tools manuals


--)For test equipment, computers and their peripheral equipment , the standard
instruction manuals prepared by their manufacturers will be sufficient

--)The instruction manuals of the equipment shall contain the following as a
minimum :

---)General description of equipment , including :

a) System block diagrams ( showing all external connections )
b) Equipment block diagrams ( showing the internal connections between the
modules of the equipment )
c) Rack facing
d) Equipment performance ( electrical , mechanical and environmental -
characteristics ).
e) Alarms and controls
f) Routine maintenance of the equipment

---)Equipment description , including :

a) Block and level diagrams
b) Description of functional operation ( signal follow and each units
function)
c) Instructions for operating the equipment (including interface jacks,
controls, indicators, test jacks, strapping/switching options, turning on/
off the equipment )
d) Full description of routine , preventive, and corrective maintenance of the
equipment (including necessary test equipment and accessories, trouble
shooting, module replacement, alignments, tests, precautions, etc).


---)Module description , including list of modules and the following items for
each module :

a) General description
b) Performance characteristics
c) Block diagram
d) Alarm circuit
e) Controls
f) Test and adjustments
g) Strapping/switching options ( where applicable )
h) Full description of the module , its parts , and circuits

---)The network management system instruction manual (Users Guide) shall
include system description, system functions description, examples of different
displays and reports (e.g.event log report , measuring report ,etc .) and the guide
for operators to use the system .

---)The network management system instruction manual ( Administrators Guide )
shall include the following items :

a) General description of the system ( software and hardware ) and its
functions.
b) Information needed for system modification such as planning and setting
the system , defining and editing items , creating and editing graphical
screens, defining alarm filtering , etc .
c) Data base information
d) Security management information


-) Installation drawings


--)Installation drawings shall contain the following as a minimum :

- Table of equipments for each station , including name of the station, name(s) of
the opposing stations (s) , rack No. , equipment name , code No. , and serial
number ,

- System assembly for each station

- Interface cable assembly description

- Alarm cable assembly description

- Racks structure layout

- Inter- rack and power wiring diagram

- Method of rack physical installation

- Alarm wiring

- Installation method for network management system software and hardware

- Wiring diagram of intermediate distribution board

- Any other drawings needed for installation of the supplied equipment



-) Repair manual

--)The repair manual shall contain the following as a minimum :

a) Equipment block and level diagram

b) Module block and level diagram
c) Circuit diagram(s) for each module
d) Parts location diagrams , which show the names and locations of the
components on printed circuit boards
e) Part list which includes all electrical components and mechanical parts
( screws, washers ,etc. ) used in a particular board .
f) Repair procedure for all modules
g) Repair procedure for all boards ( on component replacement basis)
h) Module description
i) Description of circuits of each module


--)In the part lists, the following information shall be submitted for each electrical
component :

a) Code number and its equivalent
b) Symbol ( same as that used in part location diagrams )
c) Description
d) Quantity ( used in each particular board )
e) Manufacturer name and address


--)The repair procedures shall describe all necessary tests , required test equipment,
machinery, and tools, connection points to test equipment, any necessary
alignments, and instructions to use test jigs and test racks .



-) Inventory sheets

--)Inventory sheets shall be prepared for each station and shall include the following
:

- Station name
- Table of equipment of the station , their names, code and serial numbers
- Rack facings showing all of the modules mounted on each rack

. Separate inventory sheets shall be prepared with the following items :

a) Test equipment
b) Spare modules , parts , and equipment
c) Training center equipment
d) Repair center equipment
e) Installation tools
f) Maintenance tools and accessories
g) Documents




Chapter: Fourteen


) Factory Test and Acceptance
-)General

--)The supplier will provide documented evidence of his quality assurance
program, which will assure compliance with the requirements of the contract. The
quality program must assure adequate quality throughout all areas of contract
performance, i.e., design, development, fabrication, processing, assembly, inspection,
test, maintenance, packing and associated documentation and shipping. The supplier
will audit his quality program at periodic intervals. The contractor must have assigned
the responsibility to specific organization and personnel for various elements of
quality function. The authority and responsibility for these quality assurance elements
must be clear and comprehensive.


The quality program, including performance, processes and producing will be subject
to review by the TIC representatives.


The supplier will make objective evidence of quality conformance readily available to
the TIC representatives.


--)The TIC representatives reserve the right to inspect the supplier and/or sub-
suppliers plan during all phases of manufacturing, testing and preparation of
equipment for shipment. The TIC representatives shall have free entry at all
reasonable working times while work on the contract covered by this specifications is
being performed.

--)The supplier shall afford with no charge the TIC representatives, , all
reasonable facilities and assistance necessary to satisfy the TIC representatives that the
work is being performed in accordance with the requirements of this specifications.

--)All works and materials shall be open to inspection, acceptance or rejection
by the customer representatives at all times, but any omission or failure to disapprove
or reject any work or material shall not be construed to imply the acceptance of any
defective work or materials. The supplier shall remove at his own expense any work
or material condemned by the TIC representatives and will re-build or replace the
same with no extra charge.



-)Factory Test
--)The supplier shall notify the TIC at least months before the equipment is
ready for factory testing of individual modules as well as factory system tests, in order
that the TIC representatives may carry out first inspections.(Test procedures shall the
submitted at the same time)

--)TIC reserves his right to make inspection on all goods to be delivered before
shipping and a test certificate signed by the TIC representatives shall be attached to
each packing if such inspections have made.

--)Three () copies of factory test procedure shall be submitted to TIC (Soft &
hard copies)

--)Two copies of the factory test results shall be submitted to the TIC.

--)All factory tests will be carried out on sample test basis. The samples will be
selected by TIC inspectors.

--)The sampling rate will be mutually agreed between TIC and the contractor.
However, it will be at least ten () percent of each type of the proposed equipment.
At least one sample per each kind of the proposed equipment will be tested.

--)TIC reserves the right to inquire and add any other possible tests before
approving the list as an official contract document and the contractor should declare
their clear acceptance of this requirement.

--)Testing programs that cover the acceptance tests of units and groups of units
of all equipment/system in the factory shall be carried out in consultation with TIC.
Facilities shall be provided for TIC to witness the testing in the factory.


--)All equipments/systems shall be set up in a network configuration in the
laboratory/factory simulating field conditions to see the system performance at room
temperature by conducting the following tests.



---)Tests on DWDM equipment.:

A-Transponder
B-Optical multiplexer/demultiplexer
C-Optical Add/drop
D-Optical amplifiers (Booster, in-line amplifier, Pre-Amplifier)
E-Optical Link

---)Tests on SDH equipment :

A-Electrical/ Optical interfaces (Line/Tributaries-SDH/Ethernet)
B-Clock & synchronization
C-Power supply & fan
D-Equipment protection
E-Alarms
F-Environmental
G-Software
H-Cross-connect & add/drop
I-Concatenation
J-BER tests

---)ASON/ASTN function tests

---)Network management tests


---)Network synchronization tests

-) Field Acceptance test

--)Bidders should submit a list of provisional commissioning tests and test
data sheets for the required network describing the procedure, the measuring
equipment needed, and the results that must be obtained (which should be the
same as those mentioned in the technical offer) for each test. The test should
include those needed separate equipment specification as well as those needed for
the whole network according to the latest ITU-T Recommendation for optical
fiber networks. These documents shall be submitted to TIC not later than the date
of the shipment of the first part of the equipment .


--)The copies of the complete field test procedure and data sheets shall be
provided :

a)Three() copies of test procedures
b)One () set of test data sheets

--)If a problem become apparent during the installation and testing of the
contractors equipment, the contractor may be required to conduct such additional
tests as may be necessary in the opinion of the TIC representative, to show the
compliance with this specifications or with the contractors own specifications for
the equipment. If the problem is due to the equipment design or manufacturing, the
contractor shall take proper actions to solve the problem at his cost.

-)Final Acceptance by TIC

--)Acceptance of the equipment/services by TIC shall be contingent upon the
following :

a)Successful completion of the factory test.

b)Inventory verification of all items included in the BOM of the
contract (equipment, materials, tools, spares, documents, etc.).
c)Successful completion of training courses
d)Rectification of all deficiencies discovered in the documents
(installation drawings, etc.) within at most four () weeks after informing the
contractor about such deficiencies.
e)Successful completion of the installation, tests &
commissioning.

--)Any deficiencies revealed during the above activities shall be recorded on the
contractor supplied documents, previously approved by TIC.

--)Functional deficiencies revealed during acceptance testing shall be rectified
by the contractor in thirty () days following completion of that portion of the test
procedures.

--)Documentation and inventory deficiencies shall be rectified in thirty days
following their discovery.

--)After all deficiencies have been rectified by the contractor, and all contractual
obligations have been met, TIC will issue a certificate of acceptance in a contractually
agreed upon form.





Chapter: Fifteen


) System Performance and its Requirements

SYSTEM PERFORMANCE AND RELIABILITY
REQUIREMENTS



-) The Mean Time Between Failures (MTBF) requirements of this section shall
preferably be based on fault statistics after the first year of operation. In case of
predicted MTBF values , the bidders shall give data on the source of calculating
assumptions and be in a position to give any further information on the subject , if
requested by the TIC.

-) The MTBF occurring in the parts of the equipment shall not be less than years
under working conditions as stated in part B. Failures to be considered are those
which result in field replacement of the unit(s) and for which any fault or defect is
detected during the repair procedure. In addition to the expected MTBF of all
common units of the SDH equipments , the bidders shall give the expected MTBF
of all units with and without redundancy .

-) Fault detection devices and procedures as well as the modularity of the digital
equipment shall be designed in such a way that the mean time to repair ( MTTR)
of the equipment at all locations is minimized. This MTTR will include (
disregarding the travel time ) :

a) Fault detection , isolation of the faulty unit with the assistance of alarm ,
operational displays and test equipment.

b) Replacement of faulty unit


c) Setting to correct level , alignment and setting options

The bidder shall give the itemized MTTR figures for this equipment.

-) The bidder shall submit, with the proposal , complete design, performance and
reliability calculations based upon the data and requirements contained in this
specifications .

Any assumption , theoretical formula , empirical formula , curves and process of
calculations employed shall be clearly shown.




Chapter: Sixteen


) Maintenance Annex
-)Spare unit
--) % of total price of the contract should be allocated to provide the spare
unites.
--)In order to recognize unit failure rate, this company intends to submit the
number and list of the required spare units, six months after commissioning based on
unit price in L.O.P and with considering the credit amount which is mentioned in part
--. The contractor should deliver the required units maximum after three months.

-)Support and after sale services
The contractor should undertake after sale technical services up to ten years after
the end of the guarantee period and if necessary, should guarantee selling of
accessory equipment and spare units through a separate contract with offered basic
prices.

-)Duty of contractor during one-year maintenance
--)The bidder should submit its schedule for the maintenance of equipment during
this period.
--)The contractor should do the removal operation of impairment by the way that
MTTR should not be more than hours.
--)The contractor should submit all the fault reports and disordering status include
the time and cause of impairment in the network and a complete description of how to
remedy the faulty situation, maximum one week after happening.
--)The contractor should do all the periodic tests of systems, according to the
recommendations in the technical documents of system, then report the result.

--)The contractor should cooperate and coordinate with introduced persons on
behalf of this company in order to transfer technical experiences and also arrange monthly
practical training courses for mentioned persons related to the events in the network
(including faults, creating the circuits and periodic tests).

-)Repair facilities
This company intends to give the repair of all the equipment which are concerned
in this project via a contract at the end of the guarantee period.
Thus the bidders should submit their technical proposals as following :
--)Repair of faulty units
The contractor should do the repair of units according to repair contract after the
end of the gurantee period based on the following conditions:
---) The units should be repaired during maximum days after handing over and
taking to the factory.
---) The contractor has to repair and calibrate all the test equipments which are
required for the project equipment after the end of the guarantee period, thus for
the repair they should submit the proposal for ten years.
--)Repair expenditure
The bidder shall submit its offered price of the repair for each unit separately and
optionally according to the percentage of unit price.
---)The repair cost of units should not be more than % of new unit price
mentioned in the L.O.P of the contract.
--)Repair equipment
The bidder shall submit its proposal list for the following detailed items.
---)The equipments by which, the repair department will be able to check the
impairment and repaired units to make sure of their correct operation.

---)All the softwares which are required for the test processing of the equipment.
This softwares should be upgraded according to the network and system changes.
---)Technical documents, which according to them, experts will be able to find the
fault and test the units up to module level.

-)Training
For all of the units of the systems, the repair training should be performed at the
manufacturer factory, and it should be done in a way that the trained persons (repair
experts), should be able to find fault and repair faulty units of the systems after this
course, up to module level and the programming should be in such a way that the training
on the sample of purchased equipment could be accomplished.


Appendix






Table of Obligation and Responsibilities
Activity
Contractor
TIC
. Detailed specification of space, air conditioning & power
requirements for the equipments in each station

. Defining the specification of fuses required for each rack

. Calculation and specifying the size of power cables needed for each
rack (Between end row PDB & equipment racks)

. Specifying the location for installation of equipment in each station.
. Providing space, air conditioning & power requirements in each
station.

. Providing DDF, OCDF, ODF, cable rack & structure
. Providing electrical cables required between DDF & equipment
. Providing required patch cords, pigtails & couplers.
.Providing end row PDB & related power cables
. Providing test equipment & any tools needed during implementation
. Factory inspection
. Station by station packing of the equipments
App.

. Shipment of the equipments to IRAN
. Customs clearance
. Transporting equipments to the stations.
. Station earth resistance measurement
. Installation & commissioning
. Test & acceptance with comprehensive reports
. Providing detailed installation drawings
. Specifying fiber optic cable parameters
. Station entry permission
. One year trial maintenance
. Providing test & acceptance procedure
.Providing comprehensive maintenance procedure



PHYSICAL/LOGICAL TOPOLOGY
REFER TO FILES:
-- th-PlanPhysical Topology(App.).pdf & -- th-Plan Logical
Topology(App.).pdf

App.



Station Names
ID Station Abbriviation
Station
Type
Network
Layer
Province
Abadeh ADH REP Non-ASON Fars
Ahar AHR JN Non-ASON East-Azarbayjan
Ahwaz SC AWZ SC ASON Khuzestan
Ahwaz SC AWZ SC ASON Khuzestan
Aligoodarz ALG REP Non-ASON Lorestan
Amol AML REP Non-ASON Mazandaran
Anar ANAR REP Non-ASON Kerman
Arak ARK PC ASON Markazi
Ardakan AKN REP Non-ASON Yazd
Ardebil ABL PC ASON Ardebil
Ardestan ARDS REP Non-ASON Esfahan
Asadabad-ES ASD-ES ADM Non-ASON Hamedan
Ashkhaneh AKNH REP Non-ASON North-Khorasan
Astara ASA ADM Non-ASON Gilan
AzadShahr AZD REP Non-ASON Golestan
Babazeyd BABZ REP Non-ASON Lorestan
Babol SC BBL SC ASON Mazandaran
Babol SC BBL SC ASON Mazandaran
Bafgh BFG REP Non-ASON Yazd
Baft BAFT REP Non-ASON Kerman
Baghat BGT REP Non-ASON Hormozgan
Bam BAM REP Non-ASON Kerman
App.

Bandar Abbas BBS PC ASON Hormozgan
Bandar Anzali BDA REP Non-ASON Gilan
Bandar Asaluyeh ASU ADM Non-ASON Bushehr
Bandar Bushehr BBR PC ASON Bushehr
Bandar Deylam BLM REP Non-ASON Bushehr
Bandar Genaveh BGV ADM ASON Bushehr
Bandar Kangan BKG JN Non-ASON Bushehr
Bandar Khamir BKM REP Non-ASON Hormozgan
Bandar Lengeh BLH PC ASON Hormozgan
Bardeskan BAR REP Non-ASON Khorasan Razavi
Bazargan BZR ADM ASON West-Azarbayjan
Behbahan BBN REP Non-ASON Khuzestan
Bijar BIJ REP Non-ASON Kordestan
Birizk BIK REP Non-ASON Hormozgan
Birjand BJD PC ASON South-Khorasan
Bojnurd BND PC ASON North-Khorasan
Borazjan BJN REP Non-ASON Bushehr
Borujen BRJ JN ASON Charmahal Bakhtiari
Bostan BTN REP Non-ASON Khuzestan
BostanAbad BOT REP Non-ASON East-Azarbayjan
Buchir BCH REP Non-ASON Hormozgan
Buin Zahra BZHR REP Non-ASON Ghazvin
Burujerd BDJ PC Non-ASON Lorestan
Chahbahar CBR PC ASON Sistan Baluchestan

Chahgaz CHGZ REP Non-ASON Khorasan Razavi
Chalus CLS PC Non-ASON Mazandaran
Chupanan CHPN REP Non-ASON Esfahan
Damghan DMGH REP Non-ASON Semnan
Daran DRN REP Non-ASON Esfahan
Darpahn DPN REP Non-ASON Hormozgan
Dashte Abbas DAA REP Non-ASON Ilam
Davarzan DVZN REP Non-ASON Khorasan Razavi
Dehdasht DDT REP Non-ASON
Kohkiluye
Boyerahmad
Dehloran DHLN REP Non-ASON Ilam
Delijan DLJN REP Non-ASON Markazi
Delvar DLV REP Non-ASON Bushehr
Deyhuk DYHK JN ASON Yazd
Dezful DFL PC Non-ASON Khuzestan
Divandarreh DVDR REP Non-ASON Kordestan
Dogonbadan DGBN REP Non-ASON
Kohkiluye
Boyerahmad
Domzanoogeh DMZG JN ASON Lorestan
Esfahan SC ESF SC ASON Esfahan
Esfahan SC ESF SC ASON Esfahan
Esfarayen ESRN REP Non-ASON North-Khorasan
EshghAbad ESBD REP Non-ASON Yazd
Espakeh EPK REP Non-ASON Sistan Baluchestan
Espidan-RS EDN REP Non-ASON Esfahan
Evoghli EVI REP Non-ASON West-Azarbayjan

Fasa FSA REP Non-ASON Fars
Ferdos FDS REP Non-ASON South-Khorasan
Firoozkuh FZKH REP Non-ASON Tehran
Garmsar GRS REP Non-ASON Semnan
Germi GMI REP Non-ASON Ardebil
Ghaen GHN REP Non-ASON South-Khorasan
Ghasre Shirin GSRS REP Non-ASON Kermanshah
Ghazvin GZN PC ASON Ghazvin
Ghiro Karzin GRKZ REP Non-ASON Fars
Ghom GHM PC ASON Ghom
Ghorveh GHRV REP Non-ASON Kordestan
Ghotb Abad GHTB REP Non-ASON Hormozgan
Ghuchan GCN REP Non-ASON Khorasan Razavi
Gilane Gharb GLNG REP Non-ASON Kermanshah
Golmoorty GLMY REP Non-ASON Sistan Baluchestan
Gonabad GBD REP Non-ASON Khorasan Razavi
Gonbade Kavus GDKS PC Non-ASON Golestan
Gorgan GGN PC ASON Golestan
Gushaki GSHK REP Non-ASON Charmahal Bakhtiari
Hamedan SC HDN SC ASON Hamedan
Hamedan SC HDN SC ASON Hamedan
Harang HRNG REP Non-ASON Hormozgan
Ilam ILM PC ASON Ilam
Iranshahr ISR PC ASON Sistan Baluchestan

Islamshahr ILR REP Non-ASON Tehran
Jahrom JRM REP Non-ASON Fars
Jakigoor JKGR JN Non-ASON Sistan Baluchestan
Jandaqh JDG REP Non-ASON Esfahan
Jask JASK ADM ASON Hormozgan
Javan Rood JVR REP Non-ASON Kermanshah
Jiroft JFT REP Non-ASON Kerman
Jolfa JLF ADM Non-ASON East-Azarbayjan
Kahnuj KNJ JN ASON Kerman
Kahoorestan KHRS REP Non-ASON Hormozgan
Karaj KRJ PC ASON Tehran
Kashan KSN PC ASON Esfahan
Kazeroon KZN PC Non-ASON Fars
Kerman KRN PC ASON Kerman
Kermanshah KRSH PC ASON Kermanshah
Khalkhal KHLL REP Non-ASON Ardebil
Khash KHSH JN Non-ASON Sistan Baluchestan
Khonj KOJ REP Non-ASON Fars
khormooj KHMJ REP Non-ASON Bushehr
KhorramAbad KBD PC ASON Lorestan
Khoy KHY PC Non-ASON West-Azarbayjan
Lahijan LJN PC Non-ASON Gilan
Lar LAR REP Non-ASON Fars
Lirdaf LDF REP Non-ASON Hormozgan

Loshan LSHN REP Non-ASON Gilan
Mahabad MBD REP Non-ASON West-Azarbayjan
Maksookhteh MKST REP Non-ASON Sistan Baluchestan
Malayer MYR REP Non-ASON Hamedan
Maragheh MGH REP Non-ASON East-Azarbayjan
Marand MND JN Non-ASON East-Azarbayjan
Marivan MAR REP Non-ASON Kordestan
Marvdasht MDT REP Non-ASON Fars
Mashhad SC MSD SC ASON Khorasan Razavi
Mashhad SC MSD SC ASON Khorasan Razavi
Mayamey MYMY REP Non-ASON Semnan
Mehran MHN ADM Non-ASON Ilam
Meymeh MMH REP Non-ASON Esfahan
Miandoab MDB JN Non-ASON West-Azarbayjan
Mianeh MNH PC ASON East-Azarbayjan
Minab MNB JN Non-ASON Hormozgan
Mirjaveh MJV ADM Non-ASON Sistan Baluchestan
Moalleman MOLN REP Non-ASON Semnan
Moghayeh MGHY REP Non-ASON Hormozgan
MoraveTappeh MRTP REP Non-ASON Golestan
Naeen NAN JN ASON Esfahan
Naybandan NYBN REP Non-ASON Yazd
Nehbandan NBND JN Non-ASON South-Khorasan
Neishabur NBR PC Non-ASON Khorasan Razavi

Neyriz NYR REP Non-ASON Fars
Nikshahr NKSR REP Non-ASON Sistan Baluchestan
Noor Abad-A NRB-A REP Non-ASON Fars
Noor Abad-B NRB-B REP Non-ASON Lorestan
Nordooz NDZ ADM Non-ASON East-Azarbayjan
Nosrat Abad NSBD REP Non-ASON Sistan Baluchestan
Orumiyeh ORM PC ASON West-Azarbayjan
Oskanloo OSKL REP Non-ASON East-Azarbayjan
Piranshahr PRNS REP Non-ASON West-Azarbayjan
Pishin PSHN ADM Non-ASON Sistan Baluchestan
Poldasht PLD REP Non-ASON West-Azarbayjan
Rafsanjan RFJ PC ASON Kerman
Ramhormoz RMH REP Non-ASON Khuzestan
Rasht RST PC ASON Gilan
Ravar RVR JN ASON Kerman
Razan RZN REP Non-ASON Hamedan
Roudan RDN REP Non-ASON Hormozgan
Sabzevar SZR PC ASON Khorasan Razavi
Safashahr SFSH REP Non-ASON Fars
Saghez SGZ PC ASON Kordestan
Sagzi SGZI JN Non-ASON Esfahan
Salafchegan SAG JN Non-ASON Ghom
Salmas SLMS JN ASON West-Azarbayjan
Sanandaj SNJ PC ASON Kordestan

Sar Pole Zahab SZB REP Non-ASON Kermanshah
Sarakhs SRKS ADM Non-ASON Khorasan Razavi
Saravan SVN REP Non-ASON Sistan Baluchestan
Sarbandar SBR REP Non-ASON Khuzestan
Sarbaz SBZ REP Non-ASON Sistan Baluchestan
Sarbisheh SBS REP Non-ASON South-Khorasan
Sardasht SDST REP Non-ASON West-Azarbayjan
Sari SRI PC ASON Mazandaran
Saveh SVH PC ASON Markazi
Semnan SMN PC ASON Semnan
SeroAb SOB REP Non-ASON South-Khorasan
ShahreBabak SHBK REP Non-ASON Kerman
ShahreKord SKD PC ASON Charmahal Bakhtiari
Shahreza SHA REP Non-ASON Esfahan
Shahrud SRD PC ASON Semnan
Shendasad SNDS ADM Non-ASON South-Khorasan
Shiraz SC SHZ SC ASON Fars
Shiraz SC SHZ SC ASON Fars
Shoorgaz SHGZ REP Non-ASON Kerman
Sirjan SJN JN ASON Kerman
S-Rain RAIN REP Non-ASON Kerman
Sufian SFN JN ASON East-Azarbayjan
S-Zabol SZBL JN Non-ASON Sistan Baluchestan
Tabas TBS REP Non-ASON Yazd

Tabriz SC TBZ SC ASON East-Azarbayjan
Tabriz SC TBZ SC ASON East-Azarbayjan
Takab TKB REP Non-ASON West-Azarbayjan
Takestan TKN REP Non-ASON Ghazvin
Taybad TYBD ADM Non-ASON Khorasan Razavi
Tehran SC TRN SC ASON Tehran
Tehran SC TRN SC ASON Tehran
Torbate Heidarieh THD PC Non-ASON Khorasan Razavi
Torbate Jam TJM JN Non-ASON Khorasan Razavi
Yasuj YSJ PC ASON
Kohkiluye
Boyerahmad
Yazd YZD PC ASON Yazd
Yazdan YDN ADM Non-ASON South-Khorasan
Zabol ZBL JN Non-ASON Sistan Baluchestan
Zahedan ZHN PC ASON Sistan Baluchestan
Zanjan ZJN PC ASON Zanjan
ZarAbad ZRBD REP Non-ASON Sistan Baluchestan
Zarand ZRND REP Non-ASON Kerman

Station Type QTY.
ASON


Non-ASON
REP


SC
PC

JN
ADM


Traffic Matrix
REFER TO FILE: --
th
-Plan Traffic Matrix Split Layers (App.).xls



App.


Network Line Capacity Estimation
REFER TO FILE:--
th
-Plan Cable & Logical ASON Links (App.).xls

App.


Equipment Modification Procedure

. Response to Engineering Deficiencies

. The customer shall issue written engineering notification when the supplied
equipment :
- Does not satisfy the purposes for which it was intended.
- Does not fulfill the requirements under which it was manufactured or
inspected.
- Does not operate properly.
- Requires excessive field maintenance
Or for
- Drafting and typographical discrepancies in current drawings, descriptions and
operational handbooks.
- Irregularities or errors on customer orders.

. The supplier shall acknowledge receipt of the notification within a period of
days and shall establish an objective for the investigation and resolution of the
problem with a written report to the customer within an additional days.


. Conditions of Supplier Changes and Modifications

. Any changes to the equipment furnished in accordance with this specification that
would influence its operations, its life, or its interchangeability with equipment
previously supplied in accordance with this specification requires prior written
notification to the customer. In order for the customer to review such change,
App.

thirty () days notice shall be required except for those cases where an extremely
unsatisfactory condition requires immediate action on the part of the supplier.

. Any changes in equipment shall be classified into one of the following five
classes:

Class A: Changes which are needed to correct inoperative electrical or mechanical
conditions, extremely unsatisfactory maintenance or operating conditions, safety
hazards, or system incompatibility which is judged severe enough to have to be
made to all units in process, stock, or installed.

Class B: Same as Class A except that the inoperative or extremely unsatisfactory
conditions are caused by circuit combinations or options which exist only on some
of the equipments.

Class C: Same as Class A except that the conditions may be allowed to exist on a
temporary basis. In some cases, equipment may be shipped without incorporating
that change at the time.

Class D: Changes which are vitally important to justify their application to
equipment being manufactured (as soon as reasonably possible) and which are
recommended for application to existing installations in the field. Examples of this
class of change include:
a) Providing new features that directly affect subscriber service.
b) Providing design improvements which result in better service
capabilities, longer life or improved performance margins.
c) Providing changes in design which result in important cost saving to
the customer.

Class E: Other changes not sufficiently important to justify application to
production units within any specified time period and not sufficiently important to
recommend for application to existing installations in the field.



. The supplier shall, at the time of notification, designate the class of the proposed
change in accordance with the above description. For Class A, B and C changes,
the supplier shall update, at his own cost, all warranted equipment furnished in
accordance with this specification. For Class D changes, the supplier shall first
notify the customer of the exact nature of the change. Details on the proposed
implementation procedure, including cost saving to the customer, if any, for
equipment which is being or will be supplied, shall be discussed with the
customer. The customer shall at his option determine if such changes shall be
incorporated in equipment previously shipped. Should such changes be deemed
necessary, the supplier shall make arrangements for the necessary equipment
modification at prices and schedules to be mutually agreed upon prior to
implementation. For Class E changes, documentation shall be provided as
necessary.
. Changes or modifications occurring during the production of the equipment
intended for the customer may be made without the approval of the customer. The
customer shall receive prior written notification on proposed changes as soon as
possible.


. Design changes and modification notices

Notifications to the customer of equipment design changes and modifications shall
include the following information:
- Supplier
- Contract
- Product
- Change classification (A,B,C,D,E)
- Material affected
- Reason for change
- Description of change
- Estimated cost to implement
- Marking and method of identifying changed units

- Documentation affected (including edition and date of all documentation and
drawings requiring changes)
- Number of affected units in service
- Date in which changes will be implemented
- Changes in performance characteristics (if any)

The supplier shall maintain a complete history of all shipments of racks, shelves, and
circuit modules of facilitate changes and modifications and maintain records of
documentation distribution of facilitate updating. Records shall include an identification
or code which can be cross-referenced to the schematic drawings, drawing edition, and
month of manufacture. Records shall be made accessible to the customer or his
representative.




























ADDITIONAL PALANNING CONSIDERATIONS



REFER TO FILE:--
th
-Plan Additional Planning Considerations (App.).doc












App.










EVALUATION PARAMETERS





REFER TO FILE: evaluechart







App.

SUPPORTING
PARTIALLY COMPLIED NOT COMPLIED COMPLIED
FORM C
BIDDERS RESPONSE
PARAGRAPH REFERENCE
Compliance Statement

App.