Docstoc

1413

Document Sample
1413 Powered By Docstoc
					 TELECOMMUNICATION INFRASTRUCTURE COMPANY




TECHNICAL SPECIFICATIONS
                         of

NG-SDH & DWDM Equipment

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




           Planning and Engineering Affairs
                   December 2007


                          1
                                                Table of Contents
Contents                                                                                                                     Page

1) General Conditions……………………………..……….…………………………….1
  1-1) Introduction................................................................................................................1
  1-2) Scope of Work ...........................................................................................................1
  1-3) General Tender Conditions........................................................................................2
  1-4) Response Format........................................................................................................3
  1-5) Equipment Requirements…………..…..……….………….….……………………5
2) Network.........................................................................................................................14
  2-1) Introduction…………..............................................................................................14
  2-2) Transmission………………….…………………………..……………………….14
  2.3) Synchronization………............................................................................................14
  2-4) Protection .................................................................................................................14
  2-5) DCN Management Network.....................................................................................15
3) NG-SDH Technical Specifications...............................................................................16
  3-1) General Considerations............................................................................................16
  3-2) Operating Modes .....................................................................................................17
  3-3) Network Topologies ................................................................................................17
  3-4) System Transmission Capacity ...............................................................................17
  3-5) Electrical Interfaces..................................................................................................19
  3-6) Order Wire………....................................................................................................19
  3-7) Optical Interfaces.....................................................................................................20
  3-8) Optical Amplifier.....................................................................................................23
  3-9) Optical Attenuator....................................................................................................25
  3-10) Dispersion Compensation.......................................................................................26
  3-11) Optical Patch cord and Pigtail................................................................................27
  3-12) Data Interfaces........................................................................................................28
  3-13) Ethernet Topologies...............................................................................................32
  3-14) Synchronization......................................................................................................33
  3-15) System Protection...................................................................................................34



                                                                 II
                                            Table of Contents
Contents                                                                                                            Page

  3-16) Network Protection and Restoration......................................................................34
  3-17) System Management .............................................................................................35
  3-18) Safety………………..............................................................................................39
4) DWDM Technical Specifications.................................................................................41
  4-1) General Considerations............................................................................................41
  4-2) System Applications……….....................................................................................42
       4-2-1) Optical Terminal (De)Multiplexer Equipment………………….....………..42
       4-2-2) Optical Add/Drop Multiplexer Equipment……………......…….…....……..43
       4-2-3) Optical Amplifier Equipment……………………............................………..44
       4-2-4) Regenerative Terminal......................................…………………....………..44
  4-3) Equipment Safety….……........................................................................................44
  4-4) Network Topology……….......................................................................................45
  4-5) Additional Requirements.........................................................................................45
       4-5-1) Optical Supervisory Channel ...........................…………..……………..…..45
       4-5-2) Order Wire Channel..........................................……………………....…….46
  4-6) System Components Characteristics........................................................................47
       4-6-1) TX / RX Transponder.......................................………….………....……….47
       4-6-2) Optical (De)Multiplexer....................................…………………....………..50
       4-6-3) Optical Add / Drop Multiplexer........................…………………....………..52
       4-6-4) Optical Amplifire..............................................……………………………..53
       4-6-5) Optical Attenuator............................................…………………….………..55
       4-6-6) Gain Flattening Filter........................................…………………....………..56
       4-6-7) Optical Isolator..................................................…………………....………..56
       4-6-8) Chromatic Dispersion Compensator.................……………………....……..57
       4-6-9) Polarization Mode Dispersion Compensator....……………..……….……..59
       4-6-10) Optical Connector...........................................…………………....………..61
       4-6-11) Optical Termination........................................……………………....……..61
  4-7) Power Consumption……….....................................................................................61



                                                           III
                                            Table of Contents
Contents                                                                                                              Page

  4-8) System Management……........................................................................................62
       4-8-1) Configuration Management............................................................................63
       4-8-2) Fault management...........................................................................................63
       4-8-3) Security Management.....................................................................................64
       4-8-4) Alarm Management.........................................................................................64
       4-8-5) Performance Management..............................................................................64
       4-8-6) System Management Interface......................................................................64
  4-9) System Interfaces…….……....................................................................................65
       4-9-1) Optical Interfaces............................................................................................65
       4-9-2) Elecrical Interfaces..........................................................................................66
  4-10) Safety Requirements…….......................................................................................66
       4-10-1) Elecrical Safety............................................................................................66
       4-10-2) Optical Safety...............................................................................................67
4-11) System Technical Specifications…...........................................................................68
5) Network Synchronization Equipments.......................................................................71
  5-1) Introduction………………………………………………………………………..71
  5-2) Synchronization……………………………………………………………………71
       5-2-1) Primary Reference Source.............................................................................71
                5-2-1-1) Requierment Definition....................................................................71
                5-2-1-2) Requirement Specification...............................................................71
                5-2-1-3) System Characteristics......................................................................71
                5-2-1-4) Functional Characteristics................................................................72
                5-2-1-5) Physical Characteristics....................................................................74
                5-2-1-6) General Characteristics.....................................................................74
                5-2-1-7) Quality Assurance Provisions...........................................................75
       5-2-2) Synchronization Supply Unit.........................................................................75
                5-2-2-1) General Requirements.....................................................................76
                5-2-2-2) Requirement Specifications............................................................77



                                                            IV
                                            Table of Contents
Contents                                                                                                             Page

                5-2-2-3) Major Components...........................................................................77
                5-2-2-4) System Characteristics......................................................................77
                5-2-2-5) Functional Characteristics................................................................78
                5-2-2-6) Architecture......................................................................................79
                5-2-2-7) Module Requirment..........................................................................79
                5-2-2-8) Performance Monitoring...................................................................81
                5-2-2-9)SSU Local Management....................................................................82
                5-2-2-10) Disaster Recovery...........................................................................83
                5-2-2-11)Physical Characteristics...................................................................83
  5-3) Synchronization Network Management System.............................……………….83
        5-3-1) Management Requirements............................................................................83
        5-3-2) Functional Requirements...............................................................................84
        5-3-3) Alarm Management........................................................................................85
        5-3-4) Configuration Management...........................................................................86
        5-3-5) Asset Management Requirements..................................................................86
        5-3-6) Performance Management.............................................................................86
        5-3-7) Security Management....................................................................................87
        5-3-8) Network Time Management..........................................................................87
6) Network Management.................................................................................................88
  6-1) General Requirements………………………………………….………………..88
  6-1-1) General ………………………………………………………………………….89
 6-2) Fault Managemet Function………………………………………...........................89
  6-3) Security Managemet Function………………………………..………………… .93
  6-4) Configuration Management Function……….........................................................94
  6-5) Performance Management Function………...........................................................97
  6-6) Application Development Function……………………..……………....….……99
  6-7) Network Management System User Interface........................................................99
   6-8) Configuration Backup and Recovery……………………………………………100



                                                            V
                           Table of Contents
Contents                                                                 Page

 6-9) Other Requirements……………………………………………………….…...…101
 6-10) DCN………………..……………………………………………………….…..102
 6-11) Processing of Routing……………………………………………………..……103
 6-12) VPN …………………………………………………………………………….103
 6-13) GUI Requirement……………………..…………………….…….…………….105
 6-14) NML-EML Interface Requirement ….…………………………….………….106
 6-15) Non-Functional Requirement ……..……………………….………………….107
 6-16) Project Implementation …………………………………………………..…….109
 6-17)Training …………..………………………………………………..……..…….110
 6-18) Maintenance Period…………………………………………..…..…………….113
 6-19) Documentation and Software Provision…………………..………..………….114
 6-20) Customer contract/ SLA & QoS management …………..………………….….115
 6-21) Customer contract, QoS/ SLA data administration ………..……….………….116


7) ASON/ASTN …………..……………………………………………………………118
 7-1) Introduction……………………………………………………..………………..118
 7-2) Structure…………………….………………………………………………...….118
     7-2-1) Transport Plane……………………………………………………………118
     7-2-2) Control Plane…………………….……………………………..…………118
     7-2-3) Management Plane……………….……………………….………………119
   7-2-4) Interconnection Model Between ASON/ASTN and the Customer Network 120
     7-2-5) Intelligent Control Mode………..……..…………………..………………120
 7-3) Functional Requirements for Control Plane…………………..………………….120
     7-3-1) Connection Management………………………….………………………120
     7-3-2) Auto Discovery and Link Management………………………..…………121
     7-3-3) Routing……………………………………………………………………121
     7-3-4) Signalling..………………………………………..………………………122



                                     VI
                                                       Table of Contents
Contents                                                                                                                     Page

 7-3-5) Graceful Deletion………………………………………………….……………123
         7-3-6) Naming and Addressing……………..………………………….…………123
 7-3-7) Reliability...…………………………………………………………..…………123
         7-3-8) Security.....……………………………………………………..….………124
  7-4) Technical Requirements for Protection / Restoration……..…………………….125
         7-4-1) Traditional SDH Protection Switching Capability….……………………125
         7-4-2) Mesh Protection / Restoration Capability………...………………………125
         7-4-3) Mutual Conversion Between the PC Service and SPC/SC Service………130
  7-5) Technical Requirements for The Transport Plane ….…………………..……….130
         7-5-1) Node……………………………………….…..……………….…………130
                  7-5-1-1) Cross-Connect Capability...............................................................130
                  7-5-1-2) Service Capability...........................................................................131
                  7-5-1-3) Hot Backup Capability of Boards / Cards......................................132
         7-5-2) Netwoking Capability….………..……………..…………………………132
         7-5-3) SDH Interface……………………………..…..……….…………………132
         7-5-4) Ethernet Service………………………….…...…………..………………133
         7-5-5) Node Performance……………….………………………..………………134
  7-6) Timing & Synchronization Requirements……………………….………………134
  7-7) NM Function Requirements………………………………………..……………134
8) Maintenance…………………………………………….……….…….…..………..135
  8-1) Introduction………………………………………………………………………135
  8-2) Obligations for Maintenance and Technical Support…………………………….135
9) Training.......................................................................................................................137
9-1) Introduction…………………………………………….…...…….……….………137
9-2) Training courses …….…………………………...………...………………………137
9-2-1) The Whole Of Subject…………………………………..………………………..137
9-2-2) Comprehensive course for trainers and supervisors…….…………………….....138
9-2-3) Planning course……………………………………………..…………..………..139



                                                                VII
                                                Table of Contents
Contents                                                                                                              Page

9-2-4) Installation & Commissioning course …………………….…………...………..140
9-2-5) Maintenance & Operation course…………………………………....…………..140
9-3) Requirements..………………………………………………………....…………..141
10) Test Equipment……………....................................................................................143
11) Special Tools and Acc.…….....................................................................................148
12) Technical Support....................................................................................................149
13) Documentation.........................................................................................................150
13-1) General…………………………………..…………….…...…….……….………150
13-2) System Manual………………………………………..…...…….……….………152
13-3) Instruction Manual…………………………………….…...…….……….………153
13-4) Installation Drawing…………………………..……….…...…….……….………155
13-5) Repair Manual………………………………………...…...…….……….………156
13-6) Inventory Sheets……………………………………….…...…….……….………157
14) Factory Test and Acceptance…..............................................................................158
14-1) General……………………………………….…...…………..….……….………158
14-2) Factory Test…………………….…...………………………..….…….….………159
14-3) Field Acceptance Test……………………….…...……….…….……..….………160
14-4) Final Acceptance By TIC…………………………….…...…….…….….………161
15) System Performance and its Requirements...........................................................163
16) Maintenance Annex…..……………………...........................................................165
16-1) Spare unit…………………………….…...……………………..……..….………165
16-2) Support And After Sales Service ……….……….…...…….…..…….…...………165
16-3) Duty Of Contractor During One-Year Maintenance……..……..……..….………165
16-4) Repair Facilities……………….…...……………………….…..……..….………166
16-5) Training……………………………….………….…...………..…..….….………166
Appendix…………………………………………………………..……….………..….168
  1) Tabel of Obligations & Responsibilities …………………...……………...………169
  2) Route Plan…..……………………………………....…………..………171(2 pages)



                                                            VIII
                               Table of Contents
Contents                                                                     Page

  3) Station Names …………………………..………………...…………..…...…..…172
 4) Traffic Matrix ……………………...………………………......….……181(14 pages)
 5) Network Link Capacity Estimation (All links & ASON links)………...   82(7 pages)
 6) Equipment Modification Procedure ……………………………..…………….                       183
 7) Additional Planning Informations…………………………………….                   187(2 pages)
 8) Evaluation Parameters …………………………………………….                          188(1 pages)
 9) Compliance Statement …………………………………………..…………….                             189




                                      IX
Chapter One

1) GENERAL CONDITIONS

1-1) Introduction
   1-1-1) 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 4th 5year plan.
   1-1-2) 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.1.
   1-1-3) All the softwares needed for performance of the equipments shall be the latest
         versions with un-limited license.



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

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


       1-2-1-2)None- ASON/ASTN layer.


1-2-2)The complete list of whole network station names is attached in App.3.
1-2-3)Traffic matrix showing the protection type of each demand is attached in App.4
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(10/100)
                   Quantity             60 ports         50*8 port




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


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


Note: All the software needed for this project shall be the latest versions and their licenses
shall have no time limitation.

1-3)General Tender conditions
   1-3-1) The tender should be integrated . Incomplete/partial tenders will be rejected.
   1-3-2) 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.
   1-3-3) If an item or some items have been omitted from the bidder‟s “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.
   1-3-4) 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.
   1-3-5) Sufficient documents, showing that all proposed equipments are field proven at
          least for twelve (12) months, shall be included in the technical proposal.
   1-3-6) 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.
   1-3-7) Proposed Optional items should be clearly identified in the technical and price
          proposals.



                                                2
  1-3-8) A complete time schedule for the whole project including training,factory
         test,installation,commissioning,… dates shall be in the technical proposal.
  1-3-9) The bidder shall guarantee the prompt replacement of damaged, deteriorated or
         failed parts and units for a period of one (1) year after project final acceptance
         test at his cost. For the exchanged parts and units, there should be a one-(1) year
         guarantee from the date of replacement.
  1-3-10) Panels/units and parts (or their equivalents) should be available for a minimum
        of fifteen (15) years after delivery.
  1-3-11) The time schedule should be so that the whole project be completed within
        18(eighteen) months from the opening date of L/C (exclusive of one year
        maintenance period). Proposals with shorter time is preferred.
  1-3-12) 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.
  1-3-13)Equipment modification procedure should be according to app.6


  1-3-14) The Supplied System should be Expandable.



1-4)Response Format
  1-4-1) The bidder shall make a point by point compliance statement to all items of the
         present specifications according to form "C" of App.9.
  1-4-2) The Supplied system should meet all latest necessary ITU-T and the other
         related Telecommunication recommendations.
  1-4-3) The bidder shall state why he can not comply some of the items or why TIC
         should reconsider its position.
  1-4-4) The bidder‟s proposal shall embody necessary supporting data such as
         calculations, catalogues, etc.
  1-4-5) 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).
  1-4-6) The network plan and “Bill of Materials” submitted with the technical
         proposals shall be prepared according to App.4.
  1-4-7) 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.
  1-4-8) Any abbreviation or symbol used in the schematics, drawings and calculations
         shall be clearly described.

                                               3
1-4-9) The Provided drawings shall be submitted with the technical proposal for all
       types of the stations.
1-4-10) Typical drawings, which show the rack configuration of each type of stations
      (rack layout drawing).
1-4-11) Drawings showing the units, which shall be provided for each subrack of each
      type of stations (subrack face drawings).
1-4-12) A supply record of the proposed equipment shall be attached to the technical
      proposal.
1-4-13) 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.


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


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


  Annex-1: 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-2: 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-3: A list containing names of the manufacturers of all components (IC‟s,
   Microprocessors, Optical Components, etc.) utilized in the proposed equipment
   and the countries of origin.
  Annex-4: Network management system configuration proposed for this project
   (including the details of DCN planning).
  Annex-5: Supply record for all types of equipment.
  Annex-6: Equipment catalogues.
  Annex-7: Network management system catalogues.
  Annex-8: Synchronization system catalogues.
  Annex-9: Measuring equipment catalogues.
  Annex-10: Detailed list of maintenance special tools and accessories.
  Annex-11: Detailed list of installation materials for each type of station (Except
   cablerack, structure, DDF and ODF/OCDF).

                                          4
   Annex-12: Detailed list of installation special tools.
   Annex-13:Power consumption of the proposed equipment totally for the whole
    project.
   Annex-14: Power consumption of all stations.
   Annex-15: MTBF figures for all equipments.
   Annex-16: Rack layout and rack face drawings.
   Annex-17: List of standard factory tests.
   Annex-18: Power budget calculations (for DWDM and NG-SDH equipment).
   Annex-19: List of spare units.
   Annex-20: List of spare pool units.
   Annex-20: Maintenance strategy.
   Annex-21: Technical support strategy.

1-5)EQUIPMENT REQUIREMENTS
 1-5-1) 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.
 1-5-2) Only completely developed and field proven equipments shall be proposed.
        Prototype equipment will not be accepted.
 1-5-3) TIC reserves the right to reject any bidder whose equipment has not been proven
        in the field for a minimum period of twelve (12) months. The technical proposal
        shall embody the results of the manufacturer‟s latest field proven experience.
 1-5-4) Racks specifications shall be in accordance with ETSI standard with dimensions
        of 600mm x 2200 mm x 300mm (WxHxD).
 1-5-5) Since the height of the racks in existing stations is 2600mm, bidders should
        propose the necessary adapters for their racks to be able to fix the existing
        structures.
 1-5-6) 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 rack‟s spacing and dimensions.
 1-5-7) 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.


                                               5
1-5-8) 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 8 on the mercalli scale (0.2g
       horizontal acceleration) shall be provided. The racks and shelves shall survive
       an earthquake qualification test consisting of application of sinusoidal force
       accelerations of 0.25 g horizontal (in each of two orthogonal directions) and
       0.16 g vertical, linearly swept in frequency from 1 to 10 Hz and return to 1 Hz at
       0.05 Hz/Sec. The two horizontal and one vertical portions of this test shall be
       applied separately.
1-5-9) Expansion of the proposed system shall be possible without service interruption.
1-5-10) 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.
1-5-11) The mechanical design of equipment shall be so that the installation of the
      units or panels on wrong positions would not be possible.
1-5-12) The bidder shall state if any type of wiring is required during installation of the
      equipment in the stations (e.g. soldering, wrapping, etc.).
1-5-13) 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
1-5-14) 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.
1-5-15) The connections which are supposed to be semi-permanent shall not be
      soldered.
1-5-16) All types of equipment shall be designed so that incorrect operations during
      commissioning or maintenance would not cause any damage.
1-5-17) Empty positions of racks shall be covered by plates.
1-5-18) All plug- in units shall be replaceable very quickly without using any special
      tools.
1-5-19) Possibility of accidental touch of dangerous parts of the equipment shall be
      reduced to the minimum.
1-5-20) Safety conditions shall conform to IEC publication.
1-5-21) 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

                                             6
       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.
1-5-22) Composition of different materials joined together shall be chosen so that
      electrolytic corrosion does not occur.
1-5-23) Inflammable materials shall be used.
1-5-24) Brittle material, such as cast-iron, zinc or glass shall not be used.
1-5-25) Wherever possible, standard consumable parts shall be used. These parts
      should be available from more than one manufacturer.
1-5-26) 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.
1-5-27) Copper wire cables and terminal plugs shall be provided. Aluminum wire will
      not be allowed.
1-5-28) Cooling of the all units is preffered to be based on normal air convection and
      /or heat sink arrangement.
1-5-29) All equipment sub-racks, units, modules, parts, and components shall be
      clearly marked.
1-5-30) 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.
1-5-31) The markings should be such that constant use of plugs or switches does not
      cause the designation to peel or rub off.
1-5-32) All assemblies and sub-assemblies and other modules capable of being
      exchanged during normal maintenance shall be marked with:
      a) Function
      b) Manufacturer‟s identification
      c) Identification used in handbook and drawings
      d) Model number (if applicable)
      e) Serial number
1-5-33) Maximum heat dissipation allowed for station or office circuit equipment areas
      shall be given in terms of W/m2, average over the total minimum recommended
      floor area, as stated by the bidder in response to item 1-4. 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.
1-5-34) Markings and identifications on modules, components and parts must exactly
      match designations used in handbooks, drawings and pictures.


                                              7
1-5-35) All equipment shall have mounted designation cards which are designed to
      provide appropriate information.
1-5-36) 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.
1-5-37) The reliability and stability of the equipment shall be such as to allow routine
      maintenance interval not become less than 6(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.
1-5-38) 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.
1-5-39)If necessary routine adjustment controls shall be readily accessible from the
      front of the equipment without removal of the units.
1-5-40) All connectors, cable harnesses, and inter/intra-rack wiring shall be clearly
      identified so that no ambiguity can occur.
1-5-41) 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.
1-5-42) The circuitry for this function should be designed to minimize false operation.
1-5-43) The maintenance test of any unit shall be done without interrupting traffic.
1-5-44) All faulty units/panels shall be replaced and repaired under contractor‟s
      responsibility.
1-5-45) The equipment shall be designed so that all maintenance adjustments and
      measurements can be performed from the front of the equipment without service
      interruption.
1-5-46) The equipment characteristics and performance shall comply with the latest
      ITU-T, OIF and IETF recommendations.
1-5-47) No component or device shall be designed to operate in excess of its maximum
      voltage or current rating as specified in the relevant manufacture‟s data sheets,
      over the range of conditions required by this specifications.
1-5-48) All equipment and devices shall be suitably protected against over voltage,
      over current and ground leakage.
1-5-49) Direct current devices shall be protected against voltage polarity reversal.



                                            8
1-5-50) Non-fuse breaker (NFB) power distribution fusing shall be provided for all
      equipment shelves. Each rack shall have a separate fuse.
1-5-51) 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.
1-5-52) The equipment shall be resistant to transients from the switching equipment,
      power or other sources arriving on power supply leads, and digital line
      interfaces.
1-5-53) 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.
1-5-54) The component used in the equipment shall be of such quality and be used in
      such a way that at least a 20 years life period can be foreseen for the equipment
      when operating in a given operation environment.
1-5-55) All equipments shall be connected to a rack ground bar.
1-5-56) All metallic parts shall be electrically bonded together.
1-5-57) 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.
1-5-58) All equipments (except test equipment and computers)shall be designed to
      operate with –36 to –72 VDC as described below. Test equipment and
      computers shall operate with (220+/-15%) VAC, 50(+/-10%) Hz.
 Primary Power Sources
      a) The power sources available in each station are:
                   - 48 v DC with positive pole grounded
      b) Normal Variations
                   - 48 v DC Voltage variation +%20 v
                   - AC ripple upto 0.5 Vpp
      c) Extreme variations
                   -48 v DC source Voltage variation -36 v to –72 v


                                             9
     These characteristics apply to equipment which is directly fed from the primary
     power sources.
  1-5-59) In case of not using on-board power supply, suitable power supply unit
        redundancy shall be provided in each subrack for increased reliability.
  1-5-60) 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.
  1-5-61) 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.
  1-5-62) 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.
  1-5-63) Transients on DC primary power sources:
           a) Transients of 300 V and duration of 4 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.
  1-5-64) Primary power source noise:
           a) The stated performance of the equipment shall be maintained:
                  A. With power source noise in any 3 KHz bandwidth, between 10 KHz
                     and 20 KHz, less than 100mv r.m.s. from the –48 v primary power
                     source.
                  B. With power source noise in the voice frequency band upto-35
                     dBmp from the –48 v primary power source.
  1-5-65) 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 48 v feed system 2.0 v
The bidder shall state how the primary power sources are protected and distributed in each
rack line up and in each individual rack.
  1-5-66) The primary input of any power supply shall be fused on the negative polarity
        of the input voltage.
  1-5-67) 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.
  1-5-68) 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.

                                             10
1-5-69) Each power supply shall be controlled with visual and audible alarms.
1-5-70) 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.
1-5-71) Two independent power distribution lines, A and B, shall be used for the alarm
      and monitoring functions in the equipment.
1-5-72) It shall be possible to terminate two independent power distribution lines in the
      equipment.
1-5-73) Printed circuit boards shall be composed of a high strength heat resistant
      fiberglass base material or an equivalent with bonded copper sheet circuitry.
1-5-74) 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.
1-5-75) 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.
1-5-76) 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.
1-5-77) All thread sizes for screws, nuts and bolts shall conform to a standard system,
      preferably the metric system.
1-5-78) Equipment shall be packed to withstand severe vibration as may be
      encountered during transportation in Iran.
1-5-79) 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.
1-5-80) The equipment shall be packed to resist fungus or mold during transportation
      and storage.
1-5-81) Equipment must be fully protected against effects of air borne dust and sand.



                                           11
1-5-82) All electronic equipment or other items which may be affected by fungus or
      mold shall be suitably tropicalized.
1-5-83) 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)        +5oC to +45oC.
               Relative humidity:
                     For I<30 oC              15% to 90%
                     For I>30 oC              15% to X%
                       (X decrease linearly From 80% to 45%)
               Altitude:
                     - 50 to 4000 meters above mean sea level (m.a.m.s.l)
          Ambient refers, to conditions at a location 1.5 meters above the floor and
          0.4 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        -5oC to +55oC .
                     Relative humidity          10% to 95%
                     Earthquake: upto intensity 8 on the mercalli scale
          Short–term temperature and humidity conditions will not persist more than
          72 hours continuously & not more than 15 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:                 -30 oC to +80 oC
                     Relative humidity:           5 % to 100%
                     Altitude:                    -50 to 4000 m.a.m.s.l
                     Vibrations: One sweep of 0.5 from 5 to100 Hz during 45
                      minutes at a rate of 0.1 octave /min.


                                         12
                     Shocks: One shock pulse of 30 G during 20 ms applied in
                      each possible orientation axis parallel to the transportation
                      longitudinal axis.
1-5-84) The equipment provided shall be compatible with the bidder‟s existing and
      planned facilities which shall not form a part of this specification.
1-5-85) 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.
1-5-86) Life Time Operating Conditions:
 The operating life time of the equipment shall be at least 20 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.
1-5-87) 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 22.
1-5-88) 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.




                                          13
Chapter two

2) Network
2-1) Introduction
  Network Requirements for establishing transmission network are considered in three
  following sections: Transmission, Sinchronization, Network management and
  Protection.

2-2) Transmission
  The TIC intends to establish a transmission network .The bidder shall submit the
  transmission network plan..

2-3) Syncronization
  2-3-1) The bidder shall submit the Synchronization network plan and equipment
         according to proposed transmission network.
  2-3-2) The proposed Synchronization Network must be according to ITU-T G.824,
         G.823, G.821, G.803 and G.825 Recommendations.
  2-3-3) The proposed Synchronization Network must include PRS as main equipment
         and standby.

2-4) Protection
The bidder shall use the following protection mechanisms in the transport network:
  2-4-1) MSP (Multiplex Section Protection)
   a) Bidder will use MSP 1+1 between any local switchs (including BTS, MSC, RS
      and other equipment) and the connected SDH equipment.
   b) The MSP 1+1 shall work in non-revertive and revertive mode.
   c) The MSP 1+1 shall be supported at STM-1, STM-4, STM-16 and STM-64 (where
      applicable)
   d) The Bidder is required to support MSP 1+1 in their offered equipment.
  2-4-2) 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-12, VC-12-xc, VC-3, VC-3-xc, VC-4 and
        VC-4-xc (where applicable).
   d)   The Bidder is required to support SNCP/N in their offered equipment.
  2-4-3) 2F. MS-SPRing (Two fibres Multiplex Section Shared Protection Ring)

                                              14
     a) Bidder will use 2F. MS-SPRing in all STM-16/STM-64 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 2F. MS-SPRing in their offered equipment.
     d) The bidder shall state how many MS-SPRing rings their system can be member of.
     2-4-4) 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.



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




1
    Data Communication Network.

                                               15
Chapter: three

3) NG-SDH Technical Specifications
3-1) General Considerations
  3-1-1)    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.
  3-1-2)    Provider shall submit detailed specifications of hardware and software
           upgrading capability.
  3-1-3)    Provider shall notify nominal bit rate, bit rate tolerance, coding, scrambling
           and error detection/correction mechanism for all interfaces.
  3-1-4)   SDH frame structure shall be according to ITU-T G.707.
  3-1-5)    Software upgrading, control, alarms monitoring, levels provision of the
           system must be possible locally and remotely, without any service
           interruption.
  3-1-6)    FEC (Forward Error Correction) or EFEC (Enhancement FEC) mechanism
           shall be used for 10Gbps and higher bit rates.
  3-1-7)    System shall work over existing single mode fiber optic cables between nodes
           in this project according to App. 2.
  3-1-8)   Provider shall describe capability of system operation with OTN (Optical
           Transport Network) according to ITU-T G.709.
  3-1-9)    Provider shall describe the using intelligent optical networks features in
           system according to the following Recommendations:
           a) ITU-T G.807, ITU-T G.8070 and ITU-T G.8080 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)
  3-1-10) Provider shall fully transfer technical knowledge of NG-SDH systems to TIC
          (Telecommunication Infrastructure Company) personnels.
  3-1-11) 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.691 and ITU-T
          G.957 for systems with and without optical amplifier.
  3-1-12) Provider shall notify all optical and electrical connectors used for system
          interconnections.
  3-1-13) Provider shall provide all adaptors needed between System connectors.



                                             16
3-2) Operation modes
 3-2-1) System shall support following operation modes:
        a) TM (Terminal Multiplexers)
        b) ADM (Add-Drop Multiplexers)
        c) DXC (Digital Cross-Connect)

3-3) Network Topologies
 3-3-1)    System shall support the following network topologies:
          a) Point-to-Point
          b) Linear
          c) Ring/Multi Ring
          d) Mesh

3-4) System transmission capacity
 3-4-1)   Provider shall fulfill table 3.1 for all type of System in this project.
 3-4-2)    Cross-connect for all VCs (Virtual Container) must operate at full non
          blocking mode and support following functionalities:
          a) Tributary –to– Line
          b) Tributary –to–Tributary
          c) Line–to–Line
          d) Loop Back
          e) Drop & Continue
          f) Uni-Directional/Bi-Directional
          g) Broadcasting Connections
 3-4-3)   Provider shall fulfill switching cross connection matrix at table 3.2




                                             17
                             Table 3.1: System transmission capacity

         Service Type               Max Access port per single Sub rack   Port per Card

E1 (VC-12)

E3 (VC-3)

Electrical STM-1

Optical STM-1

Optical STM-4

Optical STM-16

Optical Colored STM-16

Optical STM-64

Optical Colored STM-64

Fast Ethernet, 10/100 Mbps

RPR FE

Gigabit Ethernet

RPR GE

10 Gigabit Ethernet

FDDI

Digital Video

ESCON

Fiber Channel

FICON

ATM E3

ATM STM-1


                                                 18
                       Table 3.2: Switching matrix capacity

                                         Switch Matrix

    Board       High Order Matrix unit                        Lower Order Matrix unit
                                            Board Type
    Type           (VC-4) Capacity                               (VC-12) Capacity




3-5) Electrical interfaces
 3-5-1) E1 (HDB3, 2048 Kbps ±50ppm) interfaces must be according to ITU-T G.703
        and with 120 / 75 impedance.
 3-5-2) E1 interface Jitter tolerance must be according to ITU-T G.823.
 3-5-3) E1 interface Mask must be according to ITU-T G.703 and provider must
        submit related mask diagram.
 3-5-4) E1 interface must support Unframed and framed modes according to ITU-T
        G.704.
 3-5-5) E3 (HDB3, 34368 Kbps ±20 ppm) interface shall be according to ITU-T G.703
        and with 75  impedance.
 3-5-6) E3 interface Jitter tolerance must be according to ITU-T G.823.
 3-5-7) E3 interface Mask must be according to ITU-T G.703 and provider must
        submit related mask diagram.
 3-5-8) STM-1(CMI, 155520 Kbps ±20ppm) interface must be according to ITU-T
        G.703 and 75  impedance.
 3-5-9) STM-1 interface Jitter tolerance must be according to ITU-T G.825.
 3-5-10) STM-1 interface Mask must be according to G.703 and provider must submit
         related mask diagram.

3-6) Order wire
 3-6-1)    System must be equipped with Order Wire channel using DTMF signaling for
          test, installation and maintenance used by operators between nodes of
          network.
 3-6-2)    Order wire channel must provide voice connection for operators with the
          following methods:
          a) By numbering (max to 999)

                                           19
          b) Teleconference
          c) Playback for all terminals
 3-6-3)    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).
 3-6-4)    System must have at least two order wire channels for communicating with
          back and forward terminals.
 3-6-5)   The system must be able to provide multi directions order wire channel.
 3-6-6)    Each terminal must have the capability to define numbering for order wire
          channel.
 3-6-7)    The system must have express order wire channel (selective) with access to
          PABX channel.
 3-6-8)   Provider must notify additional capability of order wire such as answering
          machine and interconnection between NG-SDH & DWDM.
 3-6-9)   Provider must fulfill specifications of order wire in table 3.3.

                      Table 3.3: Specifications of order wire channel

                         Parameters                          value

              Number of OW channels in terminal

              Number of OW channels in ADM


                                                              2W
              Type of handset interface
                                                              4W

              Type of hand set connector


                         parameters                 minimum       maximum

              Level of output voice signal (dBm)

              Level of input voice signal (dBm)



3-7) Optical interfaces
 3-7-1)    Specifications of all optical interfaces without optical amplifier must be
          according to ITU-T G.957.



                                              20
   3-7-2)      Specifications of all optical interfaces with optical amplifier must be
              according to ITU-T G.691.
   3-7-3)     Specifications of all optical amplifiers must be according to ITU-T G.662, G.663.
   3-7-4)     Provider must notify calculation method and results of link power budget and
              maximum span length over existing optical fiber cable routes.
   3-7-5)     Provider must present eye diagram for all optical transmitters.
   3-7-6)     Provider must fulfill specification of all optical interfaces in table 3.4.

                           Table 3.4: Specifications of optical interface

                      Parameter                        Unit                 Description

Optical source type                                      -

Wavelength transmitter                                  nm

Maximum Transmitter Power                              dBm

Minimum Transmitter Power                              dBm

                                                                      Min                 Max
Tunable Transmission Power & Range                    dBm



Minimum Extinction Ratio                                dB

Received operating wavelength range                     nm

Minimum Receiver Sensitivity                            dB

Minimum Receiver Overload                               dB

OSNR                                                     -

Maximum Dispersion tolerance in the receiver           ps/nm

Span Length                                             km

Connector Type                                           -

Optical Reflection Loss                                 dB




                                                  21
3-7-7)       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 2.5 Gbps and GE
            b) XFP (10Gb small Form factor Pluggable) for STM-64
            c) XENPAK for 10 GE
3-7-8)       For direct connection to DWDM/CWDM systems, STM-4, STM-16 and
            STM-64 optical modules must be able to replace with tunable colored
            modules according to ITU-T G.694.1/G.694.2.
3-7-9)       Central wavelength and connector type of optical interfaces must be specified
            according to table 3.5.
              Table 3.5: Central wavelength and connector type of optical interfaces

 Optical
                                     Central wavelength                            Connector
interface
                                                                                       SC/PC
                                                                                       FC/PC
                 1310 nm                                                               ST
 STM-1
                 1550 nm                                                               DIN
                                                                                       E2000
                                                                                       LC
                1310 nm                                                                SC/PC
                1550 nm                                                                FC/PC
                DWDM ………..…….. Wavelength (THz)                                        ST
 STM-4
                Tunable for …...… Channel, ………Channel spacing,                         DIN
               ……….... Central Wavelength (THz)                                        E2000
                CWDM…………….... Wavelength (nm)                                          LC
                1310 nm                                                                SC/PC
                1550 nm                                                                FC/PC
                DWDM ………..…….. Wavelength (THz)                                        ST
STM-16
                Tunable for …...… Channel, ………Channel spacing,                         DIN
               ……….... Central Wavelength (THz)                                        E2000
                CWDM…………….... Wavelength (nm)                                          LC
                1310 nm                                                                SC/PC
                1550 nm                                                                FC/PC
                DWDM ………..…….. Wavelength (THz)                                        ST
STM-64
                Tunable for …...… Channel, ………Channel spacing,                         DIN
               ……….... Central Wavelength (THz)                                        E2000
                CWDM…………….... Wavelength (nm)                                          LC
                1310 nm                                                                SC/PC
                1550 nm                                                                FC/PC
                DWDM ………..…….. Wavelength (THz)                                        ST
STM-256
                Tunable for …...… Channel, ………Channel spacing,                         DIN
               ……….... Central Wavelength (THz)                                        E2000
                CWDM…………….... Wavelength (nm)                                          LC

                                                22
3-8)Optical amplifier
 3-8-1) Systems with optical amplifiers must be according to ITU-T G.662 and ITU-T
         G.663.
 3-8-2)Provider must fulfill specifications of optical Booster and Pre-Amplifier in
         table 3.6 and table 3.7.
                     Table 3.6: Specifications of optical Booster Amplifier

                                                                              Value
                        Parameters                         Unit
                                                                     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 (Pin=0 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


                                                23
Pump leakage                                              dBm

Connector type                                              -

                    Table 3.7: Specifications of optical Pre Amplifier

                                                                         Value
                     Parameters                          Unit
                                                                  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 (Pin=0 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



                                             24
 Connector type                                                -




3-9) Optical Attenuator
 3-9-1) Provider must declare each part of the system that needs optical attenuator with
          its value in this project.
 3-9-2) Connector of optical attenuators must be accommodated with equipments.
 3-9-3) Provider must fulfill specifications of fixed optical attenuator in table 3.8.
 3-9-4) In case of using any type of VOA (Variable Optical Attenuator) in the system,
          Provider must fulfill specification of VOA in table 3.9
                      Table 3.8: Specifications of fixed optical attenuator

                                                                    Value
                      Parameters                Unit
                                                        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 3.9: Specifications of VOA

                                                                    Value
                      Parameters                Unit
                                                        Minimum          Maximum

        Operating wavelength range               nm

        Attenuation range                        dB

        Resolution                               dB

        Insertion loss                           dB

        Return loss                              dB

        Polarization Dependent Loss (PDL)        dB



                                                 25
             Tolerable input power                dBm

             Connector type                         -




   3-10) Dispersion compensation
     3-10-1) Chromatic Dispersion Compensator or DCM (Dispersion Compensator
             Module) must be according to ITU-T G.691.
     3-10-2) Provider must declare compensation method and location of DCM in the system in this
              project.
     3-10-3) Provider must fulfill specifications of DCM in table 3.10.
               Table 3.10: Specifications of passive chromatic dispersion compensation

                   Parameter                                           Value
                                                        Minimum                    Maximum
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
Compensation equivalent km of G.652           Insertion loss(dB)    Dispersion (ps/nm)   PMD (ps)
    2.5
    5
    7.5
    10
    20
    30
    40
    50
    60
    70
    80
    90
    100

                                                   26
110
120


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



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

                     Table 3.11: Specifications of optical patch cord

                  Parameters             Unit                   Value

            Insertion loss                dB

            Return loss                   dB

            Tensile strength              Kg

            Polarization Dependent dB
            Loss (PDL)
            Tolerable input power  dBm

            PMD                           ps

                                                     ODF side      System side
            Connector type                 -




                       Table 3.12: Specifications of optical pigtail

                  Parameters             Unit                   Value

            Insertion loss                dB

            Return loss                   dB

            Tensile strength              Kg


                                                27
              Polarization Dependent dB
              Loss (PDL)
              Tolerable input power  dBm

              PMD                        ps

              Connector type             -


3-12) Data Interfaces

  3-12-1)    The system must be capable of transfering Ethernet traffic over full TDM
             (STM-n) based networks.
  3-12-2)    The system must be capable of transfering Ethernet traffic without MPLS
             (Multi Protocol Label Switching) over SDH network.
  3-12-3)    The system must be capable of transfering Ethernet traffic with MPLS using
             Label binding and Forwarding over SDH networks.
  3-12-4)    The system must be capable of implementing point-to-point L2 MPLS VPN
             (Layer 2 MPLS Virtual Private Network) by the following interfaces:
              ATM to ATM
              Ethernet/VLAN to Ethernet/VLAN
              TDM to TDM
  3-12-5)    The system must support L1 Private Ethernet Line service.
  3-12-6)    Provider must declare the capability of the system for supporting L3 MPLS
             VPN service, if it is supported.
  3-12-7)    The system must be capable of supporting Fast Reroute Redundant LSP, if it
             is supported.
  3-12-8)    MPLS signaling must be based on LDP (Label Distribution Protocol), if it is
             supported.
  3-12-9)    System capability for TE (Traffic Engineering) must be based on RSVP-TE
             (Resource Reservation Protocol), if it is supported.
  3-12-10) All data interfaces must fully support VCAT (Virtual Concatenation)
           according to ITU-T G.707.
  3-12-11) All data interfaces must fully support LCAS (Link Capacity Adjustment
           Scheme) for Low Order and High Order according to ITU-T G.7042.
  3-12-12) Provider must notify Deferential Path Delay for VCAT.
  3-12-13) The system must support the following management system commands for
           VCG (Virtual Concatenation Group):
            a) Add a member to VCG


                                              28
       b) Remove a member from VCG
       c) Lock out a member from VCG
3-12-14) All data interfaces must support GFP (General Framing Procedure) type T
         and F, according to ITU-T G.7041.
3-12-15) Provider must notify capability of the system for supporting LAP-S (Link
         Access Procedure SDH) according to ITU-T X.85 and X.86 and LAP-F
         (Link Access Procedure-Frame relay) according to ITU-T Q.922 and Q.933,
         if it is supported.
3-12-16) System must be able to limit bandwidth at client node with 1Mbps steps.
3-12-17) System must be able to provide dedicated or non-dedicated bandwidth.
3-12-18) Provider must notify maximum number of simultaneous VCGs per each
         card.
3-12-19) Layer 2 non blocking switch fabric forwarding capacity of data interfaces
         must be at least …… Gbps, maximum capacity must be notified by
         provider.
3-12-20) Mapping of Ethernet frame with VCG capability must be done as followed:
       a) 10 Mbps by mapping to VC12-nv
       b) 100 Mbps by mapping VC12-nv and VC3-nv
       c) 1 Gbps by mapping VC3-nv and VC4-nv
       d) 10 Gbps by mapping VC3-nv and VC4-nv
3-12-21) 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.
3-12-22) Ethernet MAC switches must be able to be logically partitioned into virtual
         MAC switches.
3-12-23) Minimum MAC address table must be ……., the maximum must be notified
         by Provider.
3-12-24) System must support MAC address filtering.
3-12-25) System must support transparently forwarding incoming IEEE 802.1Q
         VLAN tag Ethernet frames.
3-12-26) System must support CoS according to IEEE 802.1p.
3-12-27) System must support EPL (Ethernet Private Line), EVPL (Ethernet Virtual
         Private Line), EPLAN (Ethernet Private LAN) and EVPLAN (Ethernet
         Virtual Private LAN) services.
3-12-28) System must support 4096 VLAN ID and at least …………. Active VLAN,
         Maximum Active VLAN must be notified by Provider



                                        29
3-12-29) System must be capable to configure MTU (Maximum Transmission Unit)
         up to 9018 bytes (Jumbo frames) for bridging on Gigabit Ethernet ports, and
         up to 1998 bytes for bridging and routing on Fast Ethernet.
3-12-30) System must support congestion avoidance RED (Random Early Detection)
         and WRED (Weighted Random Early Detection).
3-12-31) System must support the following queuing services:
       a) Priority queuing
       b) Custom queuing
       c) WFQ (Weighted Fair Queuing)
       d) CBWFQ (Class-Based WFQ).
3-12-32) System must support the following queuing algorithms:
       a) Real-time class
       b) Assured quality class
       c) Best effort class
3-12-33) System must support RPR (Resilient Packet Ring) according to
         IEEE 802.17.
3-12-34) RPR Services must support CoS priorities with A, B and C service class
         according to IEEE 802.17.
3-12-35) RPR service must support steering and wrapping protection with switching
         time less than 50 ms according to IEEE 802.17.
3-12-36) Layer 2 Ethernet must have the following features:
       a) Flow Control (802.3x)
       b) Ethernet Bridging (802.1d)
       c) Class of Services (802.1p)
       d) Spanning Tree Protocol (802.1d)
       e) Rapid Spanning Tree Protocol-RSTP (802.1w)
       f) VLAN Trunking Protocol-VTP (802.1q)
       g) Multiple Spanning Tree–MSTP (802.1s)
       h) Link Aggregation (802.1ad)
       i) Tunneling-Q in Q (802.1q)
       j) Authentication Mechanism for Security.(802.1x)
3-12-37) Ethernet 10Base-T Interface must be according to IEEE 802.3.
3-12-38) Ethernet 10/100Base-TX Interface must be according to IEEE 802.3u.
3-12-39) Ethernet 10/100/1000Base-TX Interface must be according to IEEE 802.3z.
3-12-40) Ethernet 10GE Interface must be according to IEEE 802.3ae.
3-12-41) FC (Fiber Channel) Interface must be according to ANSI X3.230.
3-12-42) ESCON (Enterprise Systems Connection) Interface must be according to
         IBM SA–0394–03.


                                        30
3-12-43) FICON (Fiber Connectivity) Interface must be according to ANSI X3.230.
3-12-44) DVB-ASI (Digital Video Broadcasting-Asynchronous Serial Interface)
         Interface must be according to ITU–T J.83.
3-12-45) Data interface connectors must be according to Table 3.12.




                                        31
                   Table 3.12: type of data interface optical connectors

                   Connector                    Optical data interface

              LC     SC      MTRJ                  100Base-FX (FE)

              LC SC        MTRJ        1000Base (GE) LX SX ZX

              LC     SC      MTRJ                       10 GE

              LC     SC      MTRJ                         FC

              LC     SC      MTRJ                      ESCON

              LC     SC      MTRJ                       FICON

              LC     SC      MTRJ                        DVB


3-13) Ethernet topologies
 3-13-1) In Point-to-point Ethernet connection the two ports must have the capability of
          connection in separate ports, separate units and separate shelves.
 3-13-2) In Point-to-point Ethernet connection the following cases must be supported:
         a) Layer 1 Ethernet Private Line based on static bandwidth (i.e. a VCG)
         b) Layer 1 Ethernet forwarding scheme (i.e. no MAC switching)
 3-13-3) Point-to-point Ethernet connection must support Layer 2 Ethernet Private Line
          mapped into MPLS with QoS guarantees and differentiated services.
 3-13-4) Point-to-point Ethernet from customer end side to the Virtual MAC Switch
          shall be implemented with either Layer 1 Ethernet Private Lines (i.e. Ethernet
          mapped into VCG‟s) or Layer 2 Ethernet Private Lines (i.e. based on MPLS).
 3-13-5) In Point-to–multipoint Ethernet connection, there must be the capability of
          connecting multiple Ethernet ports(Customer ports) to one port(aggregation
          port).
 3-13-6) In Point-to–multipoint 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.
 3-13-7) Connection between customers to virtual MAC in the same domain must be
         implemented via Layer 1 Ethernet Private Lines or Layer 2 Ethernet Private Lines.
 3-13-8) The system which is connecting a customer port, must be able to transparently
         forward incoming IEEE 802.1Q VLAN tag Ethernet frames.



                                              32
 3-13-9) The system which is connecting aggregation port must be able to forward
         incoming IEEE 802.1Q VLAN tag Ethernet frames to the customer which the
         port belongs to by examining.
 3-13-10) System must be capable of transfering Ethernet frames completely
         transparently.

3-14) Synchronization
 3-14-1) System must have the following three synchronization modes according to
          ITU-T G.810, ITU-T G.811 and ITU-T G.812:
          a) Locked
          b) Hold over with accuracy ±0.37 ppm/day
          c) Free running with accuracy ±4.6 ppm.
 3-14-2) Synchronization equipment must support SSM (Synchronization Status
          Message) monitoring and algorithm for priority definition according to
          ITU-T G.781 and ITU-T G.783.
 3-14-3) System must have synchronization output ports.
 3-14-4) System must be able to automatically return to higher priority input when it
          comes back to normal mode.
 3-14-5) System must have 2048 KHz timing reference according to ITU-T G.703.
 3-14-6) 2048 KHz timing reference Interface must have 75 or 120 Impedance
          and balanced or unbalanced mode.
 3-14-7) Jitter of 2048 KHz timing reference output port must be according to
          ITU-T G.813.
 3-14-8) System must have 2048 Kbps timing reference with HDB3 coding according to
          ITU-T G.703, ITU-T G.704.
 3-14-9) 2048 Kbps timing reference Interface must have 75 or 120 Impedance
          and balanced or unbalanced mode.
 3-14-10) System must have tributary channels timing reference capability.
 3-14-11) System must have line (STM-n) timing reference according to ITU-T G.813.
 3-14-12) Provider must fulfill input and output synchronization ports specification in
         table 3.13.




                                           33
                         Table 3.13: list of synchronization ports

                              Input synchronization ports

 Type                                          Description




                             Output synchronization ports

 Type                                          Description




3-15)System Protection
 3-15-1) Equipments protection must be supported in all topologies.
 3-15-2) System must support the following protection types:
     a) 1+1 protection for all optical interfaces of                 intra-office   (shelves
         interconnection).
     b) 1:n protection for all electrical interfaces, provider must specify the value of n.
     c) 1+1 protection for all common units.
     d) 1+1 protection for switch matrices.
 3-15-3)Provider must declare if the protection units are the same as working units.
 3-15-4)Provider must define the location of the protection units.

3-16) Network Protection and Restoration
 3-16-1) Network and Traffic protection must be supported in all topologies.
 3-16-2) 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
 3-16-3) System must support 1+1 MSP (Multiplex Section Protection) according to
          ITU-T G.841.
 3-16-4) System must support 1+1 MSP protection for all STM-n interfaces.
 3-16-5) Provider must notify MSP configuration methods and limitations for all
          interfaces.


                                              34
 3-16-6) 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.841.
 3-16-7) System must support SNCP I/N protection for all VC12, VC12-xc, VC3, VC3-
          xc, VC4 and VC4-xc.
 3-16-8) Provider must describe high order and low order SNCP protection
          configuration.
 3-16-9) Equipments must support  2F-MSPRing (Multiplex Section–Shared
         Protection Ring) or 4F-MSPRing for STM-4, STM-16 or STM-64
         according to ITU-T G.841.
 3-16-10) System must support mesh protection and restoration mechanism.
 3-16-11) System must support SLA (Service Level Agreement), Provider must fulfill
         table 3.14.
                           Table 3.14: Specification of SLA


 Protection/SLA levels    Protection type                      Switching time delay

           1

           2

           3

           4

           5


3-17) System management
 3-17-1) System management must support the following functions according to ITU-T
          M3010:
         a) Fault Management
         b) Configuration Management
         c) Accounting Management
         d) Performance Management
         e) Security Management
 3-17-2) Connection between EMS (Element Management Systems) and NEs (Network
         Element) must be according to SNMP (Simple Network Management
         Protocol) protocol with Q3 interface according to ITU-T G.773 with Rj-45
         connector (10/100 base-T) over LAN network.

                                            35
3-17-3) System must support RS-232, LAN,  IEEE1394, USB interface for
         connecting to LCT (Local Craft Terminal).
3-17-4) All management system capabilities must also be performed by LCT.
3-17-5) System must be remotely controlled and managed according to ITU-T Q.811
         and ITU-T Q.812.
3-17-6) System must have the capability of being locally managed with personal
         computer by F interface.
3-17-7) System must use DCC (Data Communication Channel) channels for local
         maintenance and management for at least 32 NEs.
3-17-8) System must be capable of being connected to LAN and WAN for NE
         management.
3-17-9) System OS (Operating System) must be fully redundant.
3-17-10) Local access to NE must not be possible without network management
        permission.
3-17-11) System management must have suitable GUI (Graphical User Interface)
        software for viewing physical structure, provisioning and management of NE.
3-17-12) System software must have suitable online help for operating, maintenance
        and troubleshooting.
3-17-13) System software must have user management features such as operation class
        and user accessible levels.
3-17-14) System software must be able to view block diagram and functional view of
        system components.
3-17-15) System management database information must be the same as NE contents
        and information.
3-17-16) 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
3-17-17) Provider must notify any additional information besides above items.
3-17-18) System software must be capable of configuring system components
        according to the following functions:
        a) Enabling and disabling of any interface


                                          36
        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
3-17-19) System software must record history log of faults and alarms types, event
        time, fault severity and probable causes of them.
3-17-20) System software must indicate unit operation status by a suitable GUI.
3-17-21) System must have 24 alarm signals and 24 control signals for housekeeping,
        provider must notify the maximum number of them.
3-17-22) System must be able to define housekeeping alarms for any monitoring
        points.
3-17-23) System software must be able to display the number of housekeeping alarms
        with the severity of them.
3-17-24) System software must be capable of controlling and monitoring other systems
        such as battery and rectifier using housekeeping alarms.
3-17-25) System software must have order wire channel fault management.
3-17-26) System software must be able to define and classify different alarm severities.
3-17-27) 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


                                           37
        m) Correlated notification flag
        n) Repetition counter
3-17-28) System software must have audible and visual alarms.
3-17-29) System software must be able to define and adjust alarms threshold level.
3-17-30) 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
3-17-31) System software must be capable of defining local user accessible level by the
        network manager.
3-17-32) System software must be fully protected against any type of virus with
        upgradeable virus database.
3-17-33) System must be able to create all performance reports according to ITU-T
        G.783.
3-17-34) System must be able to create report for threshold levels and alarm indication
        status due to threshold crossing.
3-17-35) System must be able to implement performance monitoring for all measurable
        parameters in 15 minute and 24 hour periods.


                                          38
 3-17-36) System must be able to display performance monitoring results for all
         sections and conditions.
 3-17-37) System software must be able to measure transmission output and receiver
         input power level for all optical interfaces and environment temperature.
 3-17-38) System must be capable of implementing performance measuring on several
         ports simultaneously; provider must notify the simultaneous performance
         measure list.
 3-17-39) Provider must notify limitation cases in the simultaneous performance
         measuring.
 3-17-40) 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.
 3-17-41) Provider must notify NE information storage media type and its
         replaceability, replaceable ability storage media is preferred.

3-18) Safety
 3-18-1) System must support safety requirements according to IEC 60950
          Recommendation.
 3-18-2) For avoiding any probable hazards for operators, provider must declare all
          safety comments.
 3-18-3) System must have complete grounding facility to avoid any hazards due to
          thunderbolt, short circuit and electrical shock.
 3-18-4) All electrical parts must be protected against short circuit and overloads.
 3-18-5) System must support optical safety requirement according to IEC 60825-1,
          IEC 60825-2 and ITU-T G.664 Recommendations.
 3-18-6) All connectors of optical monitoring points and unused optical ports must be
         protected by suitable reusable caps against dust.
 3-18-7) System must have suitable caution labels for all optical sources.
 3-18-8) System must check optical link in adjustable period activation time for
          automatic laser restart.
 3-18-9) Provider must fulfill table 3.15 for ALS (Automatic Laser Shutdown) and
          APSD (Automatic Power Shutdown).




                                             39
                 Table 3.15: 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.662.
BA=Booster Amplifier
PA=Pre-Amplifier
MPI-R=Main Path Interface reference point-Receive
MPI-S=Main Path Interface reference point-Source




                                              40
Chapter: Four




4) DWDM Technical Specifications
4-1)   General Consideration
  4-1-1) The supplied DWDM system must be in accordance with ITU-T Rec. G.692.
  4-1-2) This Technical Specification is used for 32×10Gbit/s DWDM equipment and
        the system for Optical Fiber Cable (OFC) telecommunication trunk project.
  4-1-3) Application Wavelength Range of the DWDM system must be considerd in the
        C & L bands.
  4-1-4) The Maximum Distance between Optical Line Terminal should be stated for
        different cases.
  4-1-5) The Maximum span length should be stated for different cases.
  4-1-6) The Operating Wavelength range for supplied DWDM equipment must be in
        accordance with ITU-T G.696.1 standard.
  4-1-7) The nominal central frequencies for supplied DWDM equipment must be
        according to ITU-T G.694.1.(ITU-T Grid)
  4-1-8) The proposed DWDM equipment should work with different types of single
        mode fibers( G.652, G.653, G.654, G.655 and G.656) according to suggested
        route plan (Appendix 2).
  4-1-9) The supplier should explain the functional structure of its DWDM system for
        providing optical transport Network interface with requirements of ITU-T G.709
        recommendation.
  4-1-10) The bidder should state the capability of its DWDM system for optical
        cross-connect applications. (If Applicable)
  4-1-11) The bidder should state the possibility for construction of optical intelligent
        networks according to the following Requirement:
  a) ITU-T G.8070, G.8080 and G.807(ASTN / ASON).
  b) GMPLS based Protocols.
  c) OIF-UNI, I-NNI and E-NNI.
  4-1-12) The supplier should describe the possibility of the system to configure OVPN
        and explain the features of the plan for the future developments.
  4-1-13) The Supplier should specify the following parameters for development:


                                            41
  a) Maximum Channel Numbers
  b) Minimum Channel Spacing.
  c) Maximum Channel Capacity.
  d) System Bandwidths.
   4-1-14) The supplier shall specify the available types of protection schemes:
  a) OSNC
  b) OMSP Ring
   4-1-15) The Supplier shall state the possibility of incorporation new devices:
  a) Raman Amplifire
  b)Tunned Laser Transponder
  c) Combining.
   4-1-16) The supplier shall state the specific code technology that is used in the
         DWDM equipment working with the fiber G.653. And the supplier shall state
         how to overcome the nonlinear effect caused by the fiber G.653.
   4-1-17) The supplier shall consider the transfer technical knowledge of DWDM
         system.
   4-1-18) In the future, the proposed DWDM shall be upgradable to support 40 Gb/s
         traffic channel without any impact on the existing traffic. The supplier shall
         fully describe in technical details.

4-2)   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.

 4-2-1) Optical Terminal (De)Multiplexer Equipment(OTM)
   4-2-1-1) The OTM shall implement the functions as described in ITU-T Rec. G.681
   section 7.2.3 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

                                              42
        f.Optical performance monitoring
4-2-1-2) The number of spans between two OTM without Regenerator, should be clearly
stated in the offers.
4-2-1-3) The application codes systems with line amplifiers should be given in the
proposal (compatible with ITU-T standard G.692).
4-2-1-4) The procedure for expanding and upgrading of the system to increase the number
and capacity of channels should be clearly stated.
4-2-1-5) 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.692).
4-2-1-6) Details of the transmitter-receiver system including any type of optical amplifiers
that will be used, should be given in the offers.
4-2-1-7) The RX- Transponder should support „3R‟ signal regeneration.
4-2-1-8) The supplier should state the parameters for transponder (parameter definition
according to ITU-T G.661, G.662, Etsi ETS 300672 standards).
4-2-1-9) The supplier shall state the maximum distance between (De)multiplexer
Equipments without using optical regenerator in the path.

 4-2-2) Optical Add/Drop Multiplexer Equipment
4-2-2-1) The OADM to be offered shall be in accordance with ITU-T Rec. G.681 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
4-2-2-2) The wavelength grid and selection of channel wavelengths for OADM should be
compatible with ITU-T Rec. G.692 ،G.694.1.
4-2-2-3) The maximum number of wavelengths that can be added/dropped simultaneously
should be stated.
4-2-2-4) The supplier shall state any need to pre/post amplification for using in the
OADM terminal.
4-2-2-5) The supplier shall state any need to optical attenuators for using in the OADM
terminal.
4-2-2-6) It should be clear whether the pass through wavelength are subject to 2R/3R
regeneration.
4-2-2-7) The supplier Shall state the maximum number of OADM stations between the
final terminals without regenerator.

                                               43
4-2-2-8) The supplier should state the maximum span lengths between two successive
OADM terminals

    4-2-3) Optical Amplifier Equipment (OA)
4-2-3-1) 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
4-2-3-2) The type of amplifiers proposed for the given network topology (pre-amplifiers,
power amplifires-boosters, in-line amplifiers) should be stated in the offers.
4-2-3-3) In order to allowing insertion of DCM1s between two stages of amplification,
the optical amplifiers should be Erbium-dopped type dual-stage (pumping laser
wavelengths preferably at 980 and/or 1480 nm).
4-2-3-4) The maximum number of cascaded in-line amplifiers per span should be
mentioned in the offers.
4-2-3-5) The supplier shall state the capability of system in keeping constant the output
power level and the necessary procedure.
4-2-3-6) The supplier shall state the parameters for in-line amplifiers (parameter definition
according to ITU-T G.661, G.662, Etsi ETS 300672 standards).

    4-2-4) Regenerative Terminal
4-2-4-1) Regenerative terminal must be capable to regenerate electrically the optical
channel.
4-2-4-2) In addition to (de)multiplexer terminals, regtenerative terminals should contain
optical transmitter and receiver equipment for OEO2 procedure.

4-3)      Equipment Safety
4-3-1) The power supply unit must be protected in 1+1 manner in each section or shelf (if
there isn‟t specific design for independent power on board).
4-3-2) The protection scheme for optical interfaces must be configurable as 1+1.
4-3-3) The protection scheme for electrical interfaces must be configurable as 1:N.
4-3-4) Protection parts must be switched automatically with defective section without
interruption in system performance.




1
    Dispersion Compensation Modules
2
    OEO: Optical-Electrical-Optical

                                               44
4-3-5) The supplier should state the type of protection 1:N for different types of electrical
interface units.
4-3-6) It isn‟t permitted to use external connection on PCB layout.
4-3-7) The supplier shall apply sufficient fuses to control current, voltage and response
time of system.

4-4)      Network Topology
4-4-1) The supplied DWDM systems should work with different network architectures
such as point to point (point to multipoint), star, chain, ring and mesh.
4-4-2) By using mesh topology, it must be possible to protect all kind of stations and
paths.

4-5)      Additional Requirements
    4-5-1) Optical supervisory channel
4-5-1-1) The supplied DWDM equipment should support OSC1 to convey the information
of network management.

4-5-1-2) OSC shall not restrict the span space between adjacent OAs.

4-5-1-3) OSC should normally work even during the OLA failures.

4-5-1-4) The OSC data should be partitioned, have 3R function ability and be bi-
directional in the OLAs.

4-5-1-5) 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.

4-5-1-6) OSC shall realize communication between regeneration sections.

4-5-1-7) OSC shall have self-management function. The supplier should explain its
method and the capability.
4-5-1-8) The wavelength of OSC should be 151010nm. If other wavelength is used for
OSC, the supplier must explain the reason and the relevant factors considered.
4-5-1-9) The OSC line rate shall be 2.048 Mbit/s and the frame format shall be in
accordance with ITU-T Rec. G.704 , If the bit rate of OSC is not 2Mb/s, the supplier
should explain the reason and the relevant factors considered in detail.
4-5-1-10) OSC‟s physical interface and frame structure should be according to ITU-T
G.703 and G.704 separately. The supplier should indicate the OSC bit rate, frame
structure and the application of each byte in table mode.
4-5-1-11) The BER for OSC should be no less than 110E-11.


1
    Optical supervision channel

                                               45
4-5-1-12) It shall be possible to control the output power level of OSC by management
software.
4-5-1-13) The supplier should state the parameters listed in table (4-1) for OSC.
                       Table 4-1: The Supervisory Channel Characteristics

     Clause                         Parameter                           Max     Min
       1      Nominal Bit Rate (Mbps)
       2      Coding

                               Transmitter at Reference Point S
       3      Central Wavelength (nm)
       4      Type of Source
       5      Spectral Characteristics: RMS Width@-10dB (nm)
       6      Mean Launched Power (OFA type) (dBm)
       7      Extention Ratio (dBm)
                                          Optical Path
       8      Attenuation Range (dB)
       9      Dispersion Range (ps/nm)
       10     Reflectance Range (dB)
                                Receiver at Reference Point R
       11     Sensitivity (dBm) @ BER=10-9
       12     Overload (dBm) @ BER=10-9
       13     Optical path penalty (dB)
       14     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.

 4-5-2) Order Wire Channel
4-5-2-1) 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.
4-5-2-2) Order wire system should provide three different calls:
 (a) Selective address calling. The number of address is no less than 999.
 (b) Group calling.
 (c) Broadcasting calling.
4-5-2-3) At least two order wire channel must be provided for communication between
the neighbour stations and different directions.
4-5-2-4) 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
                                                46
sections in one optical multiplex section. At least another one byte should be used to
provide a user's channel.
4-5-2-5) The supplier should provide simultaneously the regeneration section orderwire
byte (E1) used as local orderwire channel for voice communication between regenerators
and the multiplex section order wire byte (E2) to be used by operators.
4-5-2-6) EOW should have multi-directional communication ability.
4-5-2-7) It must be possible to consider a specific number for each station in the order
wire channel.
4-5-2-8) The communication between NG-SDH and DWDM systems must be provided
from its order wire channel.
4-5-2-9) The supplier should state other system facilities such as answering machine, etc.
4-5-2-10) The supplier should state the parameters listed in table (4-2) for OW.


                       Table 4-2: Order Wire Channel Characteristics(OW)

       Clause                        Parameter                                  Value
         1      Number of O.W channels at the far-end terminal
         2      Number of directions in O.W channel
         3      Number of O.W channels at intermediate terminal
         4      Type of O.W interface

                                     Parameter                            Max           Min
         5      Speech output level (dBm)
         6      Speech input level (dBm)
         7      Speech output power (w)

4-6)     System Components Characteristics
 4-6-1) TX / RX Transponder
4-6-1-1) The supplier should provide transponders for operating in the 1550 nm windows.
(the system must support 1310 nm window if it is necessary).
4-6-1-2) The proposed transponders should be capable of receiving the optical signals
from client side with bit rates up to 10 Gbps (STM-4, 16).
4-6-1-3) The supplier should state transponders capability for providing the following
SDH optical tributary interfaces according to the Rec. ITU-T G.957 and/or ITU-T G.691.

    STM-1(SDH)          STM-4(SDH)          STM-16(SDH)          STM-64(SDH)       STM-256(SDH)


4-6-1-4) Besides SDH service interface, the DWDM system shall support the following
data interfaces in accordance with Rec. ITU-T G.707, IEEE802 series:


                                                 47
                       10 GE WAN, LAN               Gigabit Etherner(GbE)

                       ESCON, Ficon, FC                    40 GE


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.
4-6-1-5) The supplier should state the types of optical connectors used in transponders
according to the following table:

        FC        SC           DIN        FDDI            E2000             ST   MU

4-6-1-6) Each transponder should provide tunable laser for covering all working
channels.(C or L Band).
4-6-1-7) The supplier should state procedures for stability, tunability and control of output
optical power level in TX transponders.
4-6-1-8) It should be guaranteed that system's BER is <10E-12 in SDH-REG terminal and
the supplier shall state the maximum number of transponders that can be cascaded without
exceeding the BER of 10E-12 in the system.
4-6-1-9) The proposed optical transponders (including SDH, GE, FE and Arbitrary Rates)
have to support the 3R function (Retiming, Regenerating, and Reshaping).
4-6-1-10) Forward error correction (FEC) function:
The DWDM system shall be compliant with G.709 in the use of forward error correction.
Since G.709 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.709 standard FEC systems.
4-6-1-11) The supplier should indicate the improvement of BER and optical power
budget.
4-6-1-12) The OTU1 with FEC function should also monitor, RSOH byte (B1, J0) and
MSOH byte (B2), non-intrusively.
4-6-1-13) All the transponders with T-MUX function should support replaceable interface
(GBIC or SFP) on client side.
4-6-1-14) The supplier should state system capabilities for OTN2 applications according
to international standards.
4-6-1-15) The supplier should state the following additional features provided in
transponder according to ITU-T Rec. G.709 and G.957.



1
    Optical Transponder Unit
2
    Optical Transponder Network

                                               48
  a) The equipment capability for multiplexing SDH signals (STM-1 ~ STM-16) in client
side and providing one optical channel in DWDM side for transport at 10G.
  b) The equipment capability for combining 8GE signals in the client side and providing
one optical channel in DWDM side for transporting at 10G. The supplier should describe
the multiplex structure.
  c) The equipment capability for combining 2GE signals in the client side and providing
one optical channel in DWDM side for transporting at 2.5G. The Supplier should describe
the multiplex structure.
  d) The equipment capability for using both 10GE PHY WAN and 10GE PHY LAN
service interfaces.
  e)The system capability for monitoring supervisory channel should be stated to identifiy
the fault location and severity.
4-6-1-16) The supplied transponder must have sufficient control circuits for protection
against applied out of band input power level
4-6-1-17) The supplier should complete parameter values listed in table 4-3 & 4-4.


               Table 4-3: Optical TX Transponder Characteristics [ITU-T G.957]

      Clause                          Parameter                      Max         Min
         1      Channel Input power Range (dBm)
         2      Channel Output power Range (dBm)

         3      Input Return Loss(dB)
         4      Input Wavelength Range (nm)
         5      Output Wavelength Range (nm)
         6      Frequency Stability
         7      Modulated Spectral Bandwidth
         8      Extention Ratio (dBm)
         9      Output Channels Wavelength (nm)
        10      distance between Adjacent Channels (nm)
        11      Bit Error Rate (BER)




                                                  49
               Table 4-4: Optical RX. Transponder Characteristics [ITU-T G.957]

      Clause                          Parameter                       Max         Min
         1      Channel Input power Range (dBm)
         2      Channel Output power Range (dBm)

         3      Input Wavelength Range (nm)
         4      Output Wavelength Range (nm)
         5      Frequency Stability
         6      Sensitivity (dBm) @ BER=10-9
         7      Overload (dBm) @ BER=10-9
         8      Input Dispersion Tolerance
         9      Channel OSNR
        10      Bit Error Ratio (BER)
        11      Optical Reflectance (dB)



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




                                                  50
         Table 4-5: Optical Multiplexer Characteristics [ITU-T G.671]

Clause                         Parameter                         Max    Min
   1       Channel insertion loss (dB)
   2       Channel insertion loss deviation (dB)

   3       0.5 (dB), Channel Bandwidth (nm)
   4       3 (dB), Channel Bandwidth (nm)
   5       Reflectance (dB)
   6       Polarization dependent loss (PDL) (dB)
   7       Polarization dependent reflectance (dB)
   8       Allowable input power (dBm)
   9       Polarization mode dispersion (PMD) (ps)
  10       Channel frequency range (GHz)
  11       Ripple (dB)
  12       Adjacent channel isolation (dB)
  13       Non-adjacent channel isolation (dB)
  14       Bidirectional (near-end) isolation (dB)
  15       Bidirectional (near-end) crosstalk attenuation (dB)


       Table 4-6: Optical DeMultiplexer Characteristics [ITU-T G.671]

Clause                         Parameter                         Max    Min
  1       Channel insertion loss (dB)
  2       Channel insertion loss deviation (dB)

  3       0.5 (dB), Channel Bandwidth (nm)
  4       3 (dB), Channel Bandwidth (nm)
  5       Reflectance (dB)
  6       Polarization dependent loss (PDL) (dB)
  7       Polarization dependent reflectance (dB)
  8       Allowable input power (dBm)
  9       Polarization mode dispersion (PMD) (ps)
 10       Channel frequency range (GHz)
 11       Ripple (dB)
 12       Adjacent channel isolation (dB)
 13       Non-adjacent channel isolation (dB)
 14       Bidirectional (near-end) isolation (dB)
 15       Unidirectional (far-end) crosstalk attenuation (dB)




                                         51
 4-6-3)Optical Add/Drop Multiplexer
4-6-3-1) 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 50% of channels.
   d) The supplier shall state the details of the architecture for the R-OADM.
4-6-3-2) 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.
4-6-3-3) The supplier shall describe also the minimum and maximum wavelength number
that the OADM can add/drop.
4-6-3-4) The supplier shall indicate the central frequency of the wavelengths.
4-6-3-5) The supplier shall complete parameter values listed in table 4-7.
        Table 4-7: Optical add/drop multiplexer (OADM) Characteristics [ITU-T G.671]

         Clause                       Parameter                        Max    Min
            1     Input to output, Channel insertion loss (dB)
            2     Input to drop, Channel insertion loss (dB)
            3     Add to output, Channel insertion loss (dB)
            4     Channel insertion loss deviation (dB)
            5     Reflectance (dB)
            6     Polarization dependent loss (PDL) (dB)
            7     Type of OADM subsystem
            8     Number of add/drop/through channels
            9     Type of passband profile (flat-top or Gaussian)
           10     Channel wavelength range (nm)
           11     Channel frequency range (GHz)
           12     1 dB passband width (nm)
           13     3 dB passband witdth (nm)
           14     Ripple (dB)
           15     Input to drop, Adjacent channel isolation (dB)
           16     Input to drop, Non-adjacent channel isolation (dB)
           17     Input to output, Channel extinction (dB)
           18     Allowable input power (dBm)
           19     Polarization mode dispersion (PMD) (ps)

4-6-3-6) The supplier should provide detailed technical material on OADM‟s type,
manufacture, functional block diagram, etc.

                                                52
4-6-3-7) The application of OADM should not influence the DWDM span number and
span space.

    4-6-4) Optical Amplifier
4-6-4-1) The optical amplifier (include OBA1, OLA2 and OPA3) used in DWDM system
should meet the requirements in ITU-T Rec. G.663 and other correlative ITU-T
recommendations.
4-6-4-2) The supplier shall indicate the technical solution for flatting OA‟s gain curve and
OA‟s functional block diagram.
4-6-4-3) 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).
4-6-4-4) 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.
4-6-4-5) The supplier Shall state capability of ROPA4 for increasing span length, if it is
provided.
4-6-4-6) The supplier should indicate the technical solution for flatting optical power level
in transmision line.
4-6-4-7) The supplier should state the parameters listed in table (4-8), (4-9) & (4-10) for
all types of OA (OPA, OBA,OLA).




1
    Optical Booster Amplifier
2
    Optical In Liner Amplifier.
3
    Optical Pre Amplifier
4
    Remote Optically Pumped Amplifier: (ROPA)

                                               53
      Table 4-8: Optical Booster Amplifier Characteristics [IEC 61291-4]

Clause                           Parameter                      Max        Min
  1        Channel Allocation (nm , THz)
  2        Channel Input Power Range (dBm)
  3        Total Input Power Range (dBm)
  4        Channel Output Power Range (dBm)
  5        Maximum Total Output power (dBm)
  6        Channel addition /removal gain response (dB)
  7        Multichannel gain variation (dB)
  8        Channel signal Spontaneous noise figure (dB)
  9        Maximum reflectance tolerable at output
 10        Maximum reflectance tolerable at input
 11        Input reflectance
 12        Output reflectance
 13        Pump leakage to input( for OFA)
 14        Gain ripple (for SOA)
 15                            Input Power Range (dBm)
 16        Gain Clamping       Lasing Wavelength (nm)
 17                            Laser Power Leakage (dBm)

         Table 4-9: Optical PreAmplifier Characteristics [IEC 61291-4]

Clause                           Parameter                      Max        Min
  1        Channel Allocation (nm , THz)
  2        Channel Input Power Range (dBm)
  3        Total Input Power Range (dBm)
  4        Channel Output Power Range (dBm)
  5        Maximum Total Output power (dBm)
  6        Channel addition /removal gain response (dB)
  7        Channel signal Spontaneous noise figure (dB)
  8        Channel Gain (dB)
  9        Multichannel gain variation (dB)
 10        Maximum reflectance tolerable at output
 11        Maximum reflectance tolerable at input
 12        Input reflectance
 13        Output reflectance
 14        Pump leakage to output( for OFA)
 15        Gain ripple (for SOA)
 16                            Input Power Range (dBm)
 17        Gain Clamping       Lasing Wavelength (nm)
 18                            Laser Power Leakage (dBm)

                                         54
               Table 4-10: Optical In Line Amplifier Characteristics [IEC 61291-4]

      Clause                           Parameter                        Max          Min
         1       Channel Allocation (nm , THz)
         2       Channel Input Power Range (dBm)
         3       Total Input Power Range (dBm)
         4       Channel Output Power Range (dBm)
         5       Maximum Total Output power (dBm)
         6       Channel addition /removal gain response (dB)
         7       Multichannel gain variation (dB)
         8       Multichannel gain Change Difference (dB)
         9       Channel signal Spontaneous noise figure (dB)
        10       Maximum reflectance tolerable at output
        11       Maximum reflectance tolerable at input
        12       Input reflectance
        13       Output reflectance
        14       Multicannel gain tilt (dB/dB)
        15       Cannel gain (dB)
        16       Gain ripple (for SOA)
        17                           Input Power Range (dBm)
        18       Gain Clamping       Lasing Wavelength (nm)
        19                           Laser Power Leakage (dBm)
        20       Polarization mode dispersion (PMD) (ps)



 4-6-5) Optical Attenuator
4-6-5-1) The supplier is not allowed to use fixed optical attenuators among units out of
system.
4-6-5-2)Setting the attenuation in optical attenuators must be possible by management
software.
4-6-5-3) The supplier shall state the parameters listed in table (4-11) for optical
attenuators.




                                                   55
                   Table 4-11: Optical attenuator Characteristics [ITU-T G.671]

         Clause                            Parameter                         Max   Min
            1         Insertion loss (dB) (fixed attenuator)
            2         Reflectance (dB)
            3         1310 nm window, Operating wavelength range (nm)
            4         1550 nm window, Operating wavelength range (nm)
            5         Polarization dependent loss (PDL) (dB)
            6         Polarization dependent reflectance (dB)
            7         Allowable input power (dBm)
            8         Polarization mode dispersion (PMD) (ps)
            9         Insertion loss tolerance (dB)
           10         Attenuation range (variable attenuator) (dB)
           11         Incremental attenuation (variable attenuator) (dB)



 4-6-6)Gain Flattening Filter
4-6-6-1) The gain equalization technique in the optical amplifier module must be
indicated by supplier in details.
4-6-6-2) The supplier should state the parameters listed in table (4-12) for optical gain
flattening filter.
           Table 4-12: Optical Gain Flattening Filter Characteristics [ITU-T G.671]

                Clause                     Parameter                       Max   Min
                  1        Insertion loss (dB)
                  2        Reflectance (dB)
                  3        Operating wavelength range (nm)
                  4        Polarization dependent loss (PDL)
                           (dB)
                  5        Polarization dependent reflectance
                           (dB)
                  6        Allowable input power (dBm)
                  7        Polarization mode dispersion (PMD)
                           (ps)


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




                                                      56
                     Table 4-13: Optical Isolator Characteristics [ITU-T G.671]

            Clause                        Parameter                      Max      Min
              1        Insertion loss (dB)
              2        Backward loss (isolation)
              3        Reflectance (dB)
              4        1310 nm window, Operating wavelength range
              5        1550 nm window Operating wavelength range
              6        Polarization dependent loss (PDL) (dB)
              7        Polarization dependent reflectance (dB)
              8        Allowable input power (dBm)
              9        Polarization mode dispersion (PMD) (ps)



    4-6-8) Chromatic Dispersion Compensator
4-6-8-1) The supplied chromatic dispersion compensator or DCM1 shall conform to
ITU-T Rec. G.671, G.692 and other correlative ITU-T recommendations.
4-6-8-2) The supplier shall describe technical solution for compensation of chromatic
dispersion.
4-6-8-3) The supplier shall describe DCF‟s position in DWDM system.
4-6-8-4) The supplier should state the parameters listed in table (4-14) for chromatic
dispersion compensator.




1
    Dispersion Compensation Module

                                                   57
Table 4-14: Passive (chromatic) dispersion compensator Characteristics [ITU-T G.671]

Clause      Parameter (km of G.652 equivalent compensation)           Max      Min
  1                        Insertion loss 2.5 (dB)
  2                         Insertion loss 5 (dB)
  3                        Insertion loss 7.5 (dB)
  4                        Insertion loss 10 (dB)
  5                        Insertion loss 20 (dB)
  6                        Insertion loss 30 (dB)
  7                        Insertion loss 40 (dB)
  8                        Insertion loss 50 (dB)
  9                        Insertion loss 60 (dB)
 10                        Insertion loss 70 (dB)
 11                        Insertion loss 80 (dB)
 12                        Insertion loss 90 (dB)
 13                        Insertion loss 100 (dB)
 14                        Insertion loss 110 (dB)
 15                        Insertion loss 120 (dB)
 16                           Reflectance (dB)
 17                  Operating wavelength range (nm)
 18                Polarization dependent loss (PDL) (dB)
 19                Polarization dependent reflectance (dB)
 20                    Allowable input power (dBm)
 21        Dispersion over operating wavelength range 2.5(ps/nm)
 22         Dispersion over operating wavelength range 5(ps/nm)
 23        Dispersion over operating wavelength range 7.5(ps/nm)
 24        Dispersion over operating wavelength range 10(ps/nm)
 25        Dispersion over operating wavelength range 20(ps/nm)
 26        Dispersion over operating wavelength range 30(ps/nm)
 27        Dispersion over operating wavelength range 40(ps/nm)
 28        Dispersion over operating wavelength range 50(ps/nm)
 29        Dispersion over operating wavelength range 60(ps/nm)
 30        Dispersion over operating wavelength range 70(ps/nm)
 31        Dispersion over operating wavelength range 80(ps/nm)
 32        Dispersion over operating wavelength range 90(ps/nm)
 33        Dispersion over operating wavelength range 100(ps/nm)
 34        Dispersion over operating wavelength range 110(ps/nm)
 35        Dispersion over operating wavelength range 120(ps/nm)
                  Polarization mode dispersion (PMD) (ps)
 36             Polarization mode dispersion (PMD) 2.5 (ps)
 37              Polarization mode dispersion (PMD) 5 (ps)


                                           58
    Clause       Parameter (km of G.652 equivalent compensation)          Max     Min
      38             Polarization mode dispersion (PMD) 7.5 (ps)
      39             Polarization mode dispersion (PMD) 10 (ps)
      40             Polarization mode dispersion (PMD) 20 (ps)
      41             Polarization mode dispersion (PMD) 40 (ps)
      42             Polarization mode dispersion (PMD) 60 (ps)
      43             Polarization mode dispersion (PMD) 80 (ps)
      44            Polarization mode dispersion (PMD) 100 (ps)
      45            Polarization mode dispersion (PMD) 120 (ps)



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




                                               59
          Table 4-15: Parameters PMD Compensator at Receiver [ITU-T G.666]

Claus                               Parameter                                Max   Min
  e
 1      Fiber Type:
        Parameters related to optical power
 2      Minimum total input power(dBm)
 3      Maximum total input power(dBm)
 4      Maximum reflectance at the input port (dB)
 5      Polarization dependent reflectance at the input port(dB)

 6      Minimum channel input power (dBm)

 7      Maximum channel input power (dBm)
                         Optical Signal Characteristics

 8                           Minimum bit rate (Gbps)

 9                          Maximum bit rate (Gbps)

 10                       Modulation format (RZ, NRZ)

 11                       Maximum number of channels

 12                 Nominal channel central freqencies (THz)

 13                          Channel spacing (GHz)

 14               Maximum central frequency deviation (GHz)

             Polarization independent parameters of the preceding optical path
 15     Minimum amount of accumulated Chromatic Dispersion (ps/nm)

 16     Maximum amount of accumulated Chromatic Dispersion (ps/nm)
                   Polarization parameters at the input port

 17                     Maximum average input DGD (ps)

 18                   Maximum instantaneous input DGD (ps)

 19               Maximum polarization rotation speed (rad/ms)

 20                   Maximum DGD rate of change (ps/ms)

 21                   Maximum magnitude of the PCD (ps2)

 22              Maximum magnitude of the depolarization (ps2)

              DWDM transmission system parameters applied to each channel
 23                Maximum OSNR penalty due to DGD (dB)

 24                Minimum PMDC receiver sensitivity (dBm)




                                               60
 4-6-10) Optical Connector
4-6-10-1) The supplier shall state the type of the optical connectors adopted in the
equipment.
4-6-10-2) The supplier should state the type of constructing materials.

4-6-10-3) Lifetime: the performance should not be degraded after more than 1000 times of
insertion and removal.
4-6-10-4) The supplier shall state the parameters listed in table (4-16) for optical
connectors.


                     Table 4-16: Optical connector Characteristics [ITU-T G.671]

           Clause                           Parameter                        Max    Min
             1        Insertion loss (dB)
             2        Reflectance (dB)
             3        1310 nm window, Operating wavelength range (nm)
             4        1550 nm window, Operating wavelength range (nm)
             5        Polarization dependent loss (PDL) (dB)
             6        Polarization dependent reflectance (dB)
             7        Allowable input power (dBm)
             8        Polarization mode dispersion (PMD) (ps)

 4-6-11) Optical Termination
1) The supplier should state the parameters listed in table (4-17) for optical terminations.
                    Table 4-17: Optical termination Characteristics [ITU-T G.671]

   Clause                                Parameter                           Max      Min
       1         Reflectance (dB)
       2         1310 nm window, Operating wavelength range (nm)
       3         1550 nm window, Operating wavelength range (nm)
       4         Polarization dependent reflectance (dB)
       5         Allowable input power (dBm)

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




                                                     61
                 Table 4-18: Maximum Power Consumption of Units (watt)

                    Claus                 Parameter                 Max
                      e
                      1        Tx Transponder
                      2        Rx Transponder
                      3        Optical Multiplexer
                      4        Optical Demultiplexer
                      5        Optical Pre-Amplifier
                      6        Optical In-Line Amplifire

                      7        Optical Booster Amplifire

                      8        Optical Add/Drop Multiplexer

                      9        Chromatic Dispersion Compensator

                      10       PMD Compensator

                      11       Management System

                      12       Speech Order Wire

                      13       Auxiliary Units



4-7-2) The supplier shall state the mean power consumption for different kinds of
equipments listed in table (4-19).
                Table 4-19: Mean Power Consumption of Equipments (watt)

              Claus                          Parameter                    Max
                e
                1          Optical Terminal (De)Multiplexer Equipment
                2          Optical Amplifire Equipment
                3          Optical Add and Drop Multiplexer Equipment
                4          Regenerative Terminal

4-8)   System Management
4-8-1) The supplied DWDM system should be equipped with sufficient management
software for physical structure monitoring.
4-8-2) It should be possible for the management system, to view status, type and access
level of network users in the graphical user interface.
4-8-3) System software should exhibit block diagram and function view of equipment
units.



                                                     62
4-8-4) There shouldn‟t be any difference between information of the system and network
management.

 4-8-1) Configuration Management
4-8-1-1) 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.
4-8-1-2) It should be possible to recognize supervisory channel by NSAP or Mac.Address.
4-8-1-3) It should be possible to communicate with management system through serial or
parallel ports.
4-8-1-4) 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

 4-8-2) Fault Management
4-8-2-1) 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
4-8-2-2) Software should be able to show status of each part , by existing monitors.
4-8-2-3) For supporting housekeeping, supplier shall equip system for minimum 24 alarm
signals and 24 control signals.
4-8-2-4) It should be possible to define alarms for monitoring sections.
4-8-2-5) It should be possible to show number of alarms with relevant classes.


                                               63
4-8-2-6) 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.
4-8-2-7) Fault management should be performed on supervisory and orderwire channel.
4-8-2-8) 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.

 4-8-3) Security Management
4-8-3-1) Facilities to control operators which can access to the different levels of
management system should be provided by the network manager.
4-8-3-2) There should be a security management software to prevent viruses from entering
in to the system.
4-8-3-3) 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-232 cable and modem.

 4-8-4) Alarm Management
4-8-4-1) Software management should be equipped with sufficient graphical user interface
to observe different statuses of the system components and their performance.
4-8-4-2) It should be possible to provide alarm signals in two manners: audible and visual.
4-8-4-3) System shall be able to show control and house-keeping alarm singnals.
4-8-4-4) Software shall be able to filter and adjust alarm levels.

 4-8-5) Performance Management
4-8-5-1) It should be possible to measure parameters of performance monitoring in
periods of not more than 15 minutes and 24 hours.
4-8-5-2) It should be possible to view performance of different units ( in service or out of
service).
4-8-5-3) Management of quality decrease in optical channels should be considered with
fault reports and sufficient alarms.
4-8-5-4) 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).
4-8-5-5) It should be possible to control bias and modulation current of lasers in two
manners: hardware and software.
4-8-5-6) There should be performance history.

 4-8-6) System Management Interface
4-8-6-1) 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.774. The supplier should
provide the detailed standard material of its protocol stack and information model.


                                               64
4-8-6-2) The interface between DWDM EM and higher-level network management
system should be CORBA interface. NMS should support CORBA interface compliant
with TMF MTNM V2.0 (TMF814/513/608)

4-8-6-3) 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.
4-8-6-4) NMS should manage end-to-end DWDM wavelength.
4-8-6-5) Alarm management and performance management of circuits should be
supported.
4-8-6-6) 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.
4-8-6-7) 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.10/V.11 or V.28/V.24.
4-8-6-8) The internal connection between EMS and NEs should be in accordence with
SNMP v.2 ،Qx for LAN.
4-8-6-9) It should have RS232 connector with 38.4 Kbps bit rate for connecting Q3
interface for monitoring terminal equipment.
4-8-6-10) There should be an interface for connecting to operating system.
4-8-6-11) Local interface: RS232 interfaces is needed with a compatible personal
computer and laptop for local processing and to have a connection.in 38.4 Kbps bit rate.
4-8-6-12) Far-end interface: RS232 interfaces and a compatible personal computer and
laptop are needed for local processing of 32 network elements based on DCC channels
with a connection in 38.4 Kbps.
4-8-6-13) Far-end interface should be in accordance with G.773 recommendation for
transport management network.
4-8-6-14) For possibility of element management, It is nessesary to have a connection
with LAN and WAN Networks.

4-9)    System Interfaces
 4-9-1) Optical Interfaces
4-9-1-1) 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.707 and G.691. The
supplier shall specify the corresponding bit rate. (155Mbps, 622Mbps, 2.5Gbps, 10Gbps)




                                             65
4-9-1-2) The supplier shall provide necessary optical interfaces for connection to OTN1
according to proposed capacity.
4-9-1-3) The supplier shoud provide optical supervisory channel with capacity (2~4
Mbps) working in the out of band channels wavelength range.
4-9-1-4) The supplier should state and provide necessary types of optical connectors
according to the following table:

         a) FC       b) SC          c) DIN         d) FDDI        e) ST        f) PC

    4-9-2) Electrical Interfaces
4-9-2-1) The supplier shall provide necessary electrical Interfaces for connecting to the
management layers (system & network).
4-9-2-2) The supplier shall state the system capacity for connecting to the network
management.

       Ethernet 10           Fast Ethernet 100           Gigabit Ethernet (1000         E1
        Mbps                     Mbps                          Mbps)

4-9-2-3) The supplier shall state the type of necessary connection ports for management
system.

        USB                   RS 232                 LAN                   …

4-9-2-4) The supplier shall provide necessary interfaces for optical supervisory channel.
4-9-2-5) The supplier shall provide necessary interfaces for order wire channel.

4-10) Safety Requirements
    4-10-1) Electrical Safety
The bidder shall comply:
4-10-1-1) Electrical and mechanical safety requirements for proposed system according to
IEC 60950 standard.
4-10-1-2) 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).
4-10-1-3) Safety labelling must be considerd at main points of the proposed system.
4-10-1-4) To avoid from damaging, training of personnel must be provided for electrical
safety for installation, commission and maintenance.



1
    Optical Transmission Network

                                              66
4-10-1-5) For avoiding damages due to thunderbolt, short circuit and the electrical shock
hazards, system must have grounding scheme.
4-10-1-6) The all of electrical sections must have protection scheme against short circuit
and overload.
4-10-1-7) The system must be protected against dust, insects , rodent and termite.
4-10-1-8) For preventing access to the control keys, the system must have sufficient
equipment for protection.

    4-10-2) Optical Safety
4-10-2-1) The supplier shall comply optical safety requirements for proposed system
according to REC. IEC 60825-1, IEC 60825-2 and ITU-T G.664.
4-10-2-2) The proposed DWDM equipment should have sufficient labels for optical
safety. The classification of hazard levels for optical sources should be in accordance with
IEC60825-1,2 and ITU-T G.664 recommendations.
4-10-2-3) 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.
4-10-2-4) 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.664 recommendation.
4-10-2-5) According to REC. ITU-T G.664, the automatic power reduction must be
provided during 3 seconds.
4-10-2-6) When the connection in the OTS1 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 100 s from the moment of the connection interruption occurred or from
the finishing of a previous (unsuccessful) restart action, unless connectivity is guaranteed.
4-10-2-7) For avoiding damage, the training of personnel must be provided for optical
safety for installation, commission and maintenance.
4-10-2-8) All active optical devices should have lifetime pre-warning function. The
supplier should provide its working principle.
4-10-2-9) The supplier shall state time constants for automatic power shut down (ALS &
APSD) in the different sections of optical link according to table (4-20).




1
    Optical Trasmission Section

                                               67
                     Table 4-20: Time constants for automatic shutdown [ITU-T G.664]

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




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




                                                     68
     Table 4-21: Inter-City DWDM System Technical Specifications [ITU-T G.692]

                           Application code                    Value     Units
1      Number of Channels
2      Min. Channel Spacing                                              GHz
3      Bit-Rate / Format of Channels
4      Max. BER
5      Max Span Length                                                   Km
6      Max Target Length                                                 Km
7      Operating Wavelength Range                                        nm
                  Transmitter Transponder Outputs
 5     Spectral Characteristics
 6     Mean Launched Power                                               dBm
 7     Extinction Ratio
 8     Eye Pattern mask
 9     Central Frequency                                                 GHz
10     Central Frequency Deviation                                       GHz
       Optical Booster Amplifire output
11     Optical Transmit-side Crosstalk                                   dB
12     Channel Output Power                                              dBm
13     Total Launched Power maximum                                      dBm
14     Optical Channel Signal-to-Noise Ratio                             dB
15     Maximum Channel Power Difference at Point output                  dB
                       Optical Line Amplifier
16     Multichannel Gain Variation                                       dB
17     Multichannel Gain Tilt                                            dB/dB
18     Multichannel Gain-change Difference                               dB
19     Total Received Power maximum                                      dBm
20     Total Launched Power maximum                                      dBm
21     Signal Spontaneous Noise Figure                                   dB
                             Optical Path
22     Attenuation                                                       dB
23     Dispersion                                                        ps/nm
24     Maximum Discrete Reflectance                                      dB
25     Minimum Return Loss                                               dB
                         PreAmplifire Input
       Mean channel input power
26     – maximum                                                         dBm
27     – minimum                                                         dBm
28     Mean total input power maximum                                    dBm
29     Channel Signal-to-Noise Ratio                                     dB
30     Optical Signal Crosstalk                                          dB
31     Maximum Channel Power Difference at Point Input                   dB
                   Optical DEMUX.Output ports
32     Optical Crosstalk at individual channel output ports              dB




                                             69
                       Application code         Value   Units
                   ReceiverTransponder Inputs
33   Receiver Sensitivity                               dBm
34   Receiver Overload                                  dBm
35   Optical Path Penalty                               dB
36   Receiver Reflectance                               dB
37   Optical Signal-to-Noise Ratio                      dB
38   Minimum Receiver Wavelength                        nm
39   Maximum Receiver Wavelength                        nm
                    Supervisory Channel
40   Channel Wavelength                                 nm




                                      70
Chapter: Five



5) NETWORK SYNCHRONIZATION
    EQUIPMENTS
5-1)    Introduction
Synchronization requirements are defined in the two sections; network synchronization
and network synchronization management.

5-2)    Synchronization
Synchronization network is consisting of primary reference source and secondary
reference source.

 5-2-1)Primary Reference Source
5-2-1-1) Requirement Definition

   a) The cesium primary reference source shall be based on the cesium isotope Cs133 to
   obtain a timing reference with good long term stability according to ITU-T G.811.

   b) The cesium primary reference source will provide synchronization reference
   outputs in the form of 2.048 Mbit/s accoding to section 9 of ITU-T G.703 and 2.048
   MHz according to section 13 of ITU-T G.703, 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
   (SSU‟s).

   d) The cesium primary reference source will be used with an SSU, or as a stand-alone
   PRC.

5-2-1-2) Requirement Specification
Equipment vendor: products will only be accepted from vendors that are the original
manufacturer of the cesium physics assembly.
5-2-1-3) System Characteristics
5-2-1-3-1) 2.048 Mbit/s interface
a) The electrical characteristics of the 2.048 Mbit/s electrical interfaces shall conform to
ITU-T recommendation G.703, section 9, with an impedance of 75 or 120 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.
5-2-1-3-2) 2.048 MHz Interface

                                              71
a) The electrical characteristics of the 2.048 MHz electrical interface shall conform to
ITU-T recommendation G.703, section 13, with an impedance of 75 or 120 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.
5-2-1-3-3) 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 -48 VDC (positive-earth), with a range of -36 VDC to -72 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.
5-2-1-3-4) 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.
5-2-1-4) Functional Characteristics
5-2-1-4-1) Applications:

       a) The cesium primary reference source must be capable of providing
       synchronization to the following types of synchronization nodes.

- PRC nodes
- Class-1 transit nodes (Enhanced)
- Class-2 transit nodes (Standard)
- Local nodes (Exceptional cases)
b) The cesium primary reference source shall function as a PRC under normal
circumstances.
5-2-1-4-2) Performance
a) The performance and stability of the cesium primary reference source for PRC nodes
shall comply with ITU-T recommendation G.811 and ETSI recommendation ETS 300
462-6.
5-2-1-4-3) Accuracy
a) The following table details, the required accuracy and stability, required:




                                               72
                       Table 1: Accuracy and stability requirements

                     Performance Measure                Requirement

                    Accuracy, Calibrated to             <=± 1x10-12

                    Accuracy (25OC ± 5OC)               <= ±2x10-12

                  Accuracy over Environment             <= ±3x10-12

                    Retrace (reproducibility)          <= ±1.2x10-12

                          Averaging Time


                                   1s                     3.0x10-11


                                  10 s                    1.3x10-11


                                  100 s                   3.0x10-12


                                 1,000 s                  9.5x10-13


                                10,000 s                  3.0x10-13


                    Warm-up time (typical)               30 minutes

5-2-1-4-4) Electromagnetic Immunity
a) The cesium primary reference source shall not be susceptible to interference from other
telecommunication equipment or radio signals.
5-2-1-4-5) Number of outputs
a) A single cesium primary reference source shall provide at least two (2) software
selectable telecommunication outputs and one (1) 10MHz sine wave output.
5-2-1-4-6) Output types
a) The cesium primary reference source must provide two (2) 2.048 Mbit/s and two (2)
2.048 MHz outputs.
b) The 2.048 Mbit/s and 2.048 MHz outputs must be user selectable.
c) The 2.048 Mbit/s signal shall be structured in accordance with ITU-T recommendation
G.704, and shall provide signals with CCS and CAS, selectable.
d) The 2.048 Mbit/s signal shall support synchronization status messaging according to
ITU-T G.781.
5-2-1-4-7) Synchronization quality messaging
a) Synchronization status messaging will be a definite requirement.


                                                73
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.708, used
by the NG-SDH transmission equipment.
5-2-1-4-8) 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 60 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 30 minutes after the power has been restored.
5-2-1-4-9) Power supply unit
a) The cesium primary reference source shall have a duplicated power supply unit input,
which is 1+1 protected.
5-2-1-4-10) 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.
5-2-1-4-11) Power Brown-Out
a) During a power brown-out, the input voltage to the cesium primary reference source
gradually falls to less than 50 % of the normal operating voltage. The cesium primary
reference source must be able to tolerate such a power brown-out without damaging the
equipment.

5-2-1-5) Physical Characteristics
5-2-1-5-1) Equipment Practice
a) The equipment practice for installation into ETSI 600×300mm 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.
5-2-1-5-2) Architecture
a) It shall be possible to re-configure the cesium on site for either front access or rear
access installation in a cabinet.
5-2-1-5-3) 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.
5-2-1-6) General Characteristics
5-2-1-6-1) Reliability
a) The supplier‟s warranty on the physics assembly shall be at least 12 (twelve) years and
the warranty on the electronic assembly shall be at least two (2) years.


                                               74
5-2-1-6-2) 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.
5-2-1-6-3) Operation
a) The equipment must meet the specifications when in operation, while being subjected
to normal temperature controlled locations (+25°C) with no forced air cooling applied.
5-2-1-6-4) Transportability
a) The equipment will be permanently mounted on a fixed position.
5-2-1-6-5) Documentation and technical information
a) The technical information supplied shall be comprehensive and adequate for the
installation, operation and maintenance of the equipment.
5-2-1-7) Quality assurance provisions
Bidder shall demonstrate compliance to ISO 9001:2000 and ISO 14001. Quality audit
shall be made available upon request.

 5-2-2) Synchronization Supply Unit
Requirement Definition
5-2-2-1) 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.
5-2-2-2) The SSU is needed for the intra-node timing distribution in a synchronization
network with architecture as specified in ITU-T recommendation G.803.
5-2-2-3) The SSU shall be able to select an input reference from various 2.048 Mbit/s and
2.048 MHz sources (including GPS), using digital transmission error checking,
synchronization quality messages and input priorities as criteria.
5-2-2-4) It will remove phase unstabilities from the selected reference and will provide
multiple 2.048 Mbit/s and 2.048 MHz outputs.
5-2-2-5) 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.
5-2-2-6) SSU shall provide the facility to perform non-intrusive performance monitoring
on a number of signals simultaneously with a measurement resolution of 1 nanosecond.
5-2-2-7) A local management terminal will be used for the local management of SSU.
5-2-2-8) SSU will also be managed through the synchronization management network via
the remote management interface.
5-2-2-9) All critical elements of SSU shall be duplicated to ensure maximum availability.
5-2-2-10)SSU will be configured differently to be used at the various node types,
including PRC nodes, class-1 and class-2 transit nodes and local nodes.
5-2-2-11) SSU shall be based on technology no older than three (3) years.




                                             75
5-2-2-1) General Requirements
5-2-2-1-1) Each SSU shall have either a de-centralized power supply configuration that is
each plug-in module shall have its own power supply unit.
5-2-2-1-2) Synchronization status messaging is required. SSU shall be capable of
receiving and generating synchronization status messages via the 2.048Mbit/s interfaces.
The synchronization quality messaging of SSU will be compatible with the timing
markers as specified in ITU-T recommendation G.708, used by the NG-SDH and classic
SDH transmission equipment.
5-2-2-1-3) 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.
5-2-2-1-4) Upgradeability:
a) SSU shall be modularly upgradeable.
b) SSU shall be upgradeable from a Class-2 transit node SSU to a Class-1 transit node
SSU as well as from a Class-1 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.
5-2-2-1-5)SSU shall provide a minimum availability of 99.99% for the redundant system.
Vendor shall advise minimum number of spares and recommended MTTR to achieve
requested availability.
5-2-2-1-6) 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.
5-2-2-1-7) 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.
5-2-2-1-8) The technical information supplied shall be comprehensive and adequate for
the installation, operation and maintenance of the equipment.
5-2-2-1-9) 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.




                                               76
5-2-2-2) Requirement Specification
Products will only be accepted from vendors that are the original manufacturer of the SSU
Assembly.
5-2-2-3) Major components
5-2-2-3-1) 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 1 nanosecond must be implemented in the input module.
c) It is not acceptable for a separate or dedicated module to perform input performance
monitoring.
5-2-2-3-2) 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.
5-2-2-3-3) Communication Unit
a) The unit shall provide a sophisticated communication unit for local and remote
management.
5-2-2-3-4) Output Unit
a) The unit provides multiple synchronization outputs to be used for the synchronization
of a node.
5-2-2-3-5) Power Supply
a) Power supplies must be integrated on each SSU module.
b) It will not be acceptable to use a centralized power supply.
5-2-2-3-6) 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.
5-2-2-4) System Characteristics
5-2-2-4-1) 2.048 Mbit/s Interface
a) The electrical characteristics of the 2.048 Mbit/s electrical interfaces shall conform to
ITU-T recommendation G.703, section 9, with an impedance of 75 or 120 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.


                                               77
5-2-2-4-2) 2.048 MHz Interface
a) The electrical characteristics of the 2.048 MHz electrical interfaces shall conform to
ITU-T recommendation G.703, section 13, with an impedance of 75 or 120 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.
5-2-2-4-3) 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 -48 VDC (positive-earth), with a range of -36 VDC to -72 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.
5-2-2-4-4) 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 500 alarm/events.
5-2-2-4-5) Communication Interface
a)SSU shall provide three RS-232 interfaces, a 10-base-T Ethernet interface and a USB
interface.
5-2-2-5) Functional characteristics
5-2-2-5-1) 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-1 transit nodes
    Class-2 transit nodes
5-2-2-5-2) Performance
a) The performance and stability of SSU for PRC nodes shall comply with ITU-T
recommendation G.811 when PRC reference inputs such as cesium or GPS are provided.
b) The performance of SSU for class-1 transit nodes shall comply with ITU-T
recommendation G.812.
c) The performance and stability of SSU for class-2 transit nodes and local nodes shall
comply with ITU-T recommendation G.812.
d) The following table specifies the accuracy and holdover stability required at different
types of nodes:

                                               78
               Table 2: Accuracy and stability guidelines for different node types

Criteria                  PRC node        Class-1 transit node           Class-2 transit node

Long term accuracy        Better than     4x10-12(GLONASS 24h)           5x10-10(1 year)
                          5x10 -12
                                          1x10-12(GPS 24h)

Holdover                  N/A             < 5x10-11                      < 5x10-11
(24 hours at 25° C)

5-2-2-6) Architecture
5-2-2-6-1) SSU must have a modular design.
5-2-2-6-2) All service affecting modules, including the input modules, local oscillator
modules and the output modules, shall be 1:1 protected.
5-2-2-6-3)Removing any single card from the system shall not interrupt the signal outputs.
5-2-2-6-4) There shall be no damage to SSU if an attempt is made to insert a card in the
wrong position.
5-2-2-6-5) Configuration databases shall be stored in three different hardware modules.
5-2-2-7) Module requirements
5-2-2-7-1)SSU shall not have a dedicated controller unit that is responsible for the internal
management of SSU.
5-2-2-7-2) SSU shall provide the following Communication Interfaces.
a) Three RS-232 interfaces supporting direct serial and dial-up modem connections for
ASCII and TL1.
b) One10-base-T Ethernet interface supporting ASCII, TELNET, TL1, NTP and SNMP
connections.
c) Integrated ASCII Terminal.
d) Telecommunication Language 1 (TL1).
e) Network Time Protocol (NTP) Server application.
f) Network Time Protocol (NTP) Client application.
g) SNMP Management Interface.
5-2-2-7-3) 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.
5-2-2-7-4) Input Module
a SSU input module must accept no less than two (2) reference inputs.
5-2-2-7-5) Input Types


                                                 79
a) SSU must accept 2.048 Mbit/s and 2.048 MHz telecom inputs.
b)2.048 Mbit/s signals shall be structured in accordance with ITU-T G.704, and shall
accept signals with CCS or CAS, selectable, and with SSM byte.
c) SSU must accept 1 MHz, 2.048 MHz, 5 MHz, and 10 MHz sine or square wave inputs.
d) It must be possible to combine different input types on a single SSU in any
combination.
5-2-2-7-6) 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.
5-2-2-7-7) Local Oscillators
a) The following oscillator types must be used for different types of nodes:
    PRC nodes : Cesium
    Class-1 transit nodes : Rubidium
    Class-2 transit nodes : Rubidium
    Local nodes : Stratum 3E 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 ST3E) shall not require any adjustment, calibration or
maintenance throughout its entire lifetime (20 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.
5-2-2-7-8) Output Modules
a) A single SSU with one management connection shall be capable of providing a
minimum of 460 protected outputs.
b) Each output module shall have no less than 20 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).



                                               80
d)SSU shall provide 2.048 Mbit/s and 2.048 MHz outputs as specified in ITU-T
recommendation G.703.
e)2.048 Mbit/s signals shall be structured in accordance with ITU-T recommendation
G.704, and shall provide signals with CCS or CAS, selectable, and must provide SSM
byte in compliance with ITU-T G.781.
f) All outputs shall have an automatic drive impedance adjustment for 75 or 120 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 20 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.
5-2-2-7-9) Equipment Switching Stability
a) The phase discontinuity of the SSU output may never exceed the limits outlined in
Table below:
                Table 3: Maximum Phase Discontinuity Allowed

    Switching Criteria                                Maximum Phase Discontinuity

    A transfer between reference inputs;              1 nanosecond

    A transfer between input cards;                   1 nanosecond

    A transfer between local oscillator cards;        60 nanoseconds, i.e., <= 1/8 UI

    Output protection switching.                      1 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.
5-2-2-7-10) Expansion Shelves
a) It shall be possible to add up to four additional expansion shelves.
b) Expansion cables shall be 1:1 protected.
c) It shall be possible to manage individual outputs in the expansion shelves.
5-2-2-8) Performance monitoring
5-2-2-8-1) Performance monitoring shall be implemented on the SSU input hardware and
separate performance measurement hardware shall not be necessary.
5-2-2-8-2) Performance monitoring shall be possible on up to 9 inputs simultaneously.
5-2-2-8-3)Inputs may be the input references used by the SSU, or any other
synchronization signal (performance monitoring only).


                                                 81
5-2-2-8-4)Performance monitoring shall be done on all 2.048 Mbit/s and 2.048 MHz
inputs.
5-2-2-8-5)SSU shall store 24 hours of performance data for all inputs.
5-2-2-8-6) The performance data shall be collected with 1 ns or better resolution.
5-2-2-8-7) 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
5-2-2-8-8) 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.
5-2-2-8-9) It shall be possible to save the performance data to an external file for later
analysis.
5-2-2-8-10) The performance monitoring shall be non-intrusive.
5-2-2-9) SSU Local Management
The management functionality in this paragraph refers to local management, performed on
the SSU itself and via a local terminal.
5-2-2-9-1) Fault Management
a) Faults shall be classified as critical, major or minor.
b) No less than 500 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.
5-2-2-9-2) Configuration Management
a) All equipment configuration changes shall be possible via the local management
terminal.
5-2-2-9-3) Performance Management
a)SSU will constantly monitor all input references and provide indications and alarms to
indicate any degradation in performance.
5-2-2-9-4) 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.

                                                 82
5-2-2-9-5) 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.
5-2-2-10) 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 50% 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.
5-2-2-11) Physical Characteristics
5-2-2-11-1) Equipment practice: The equipment practice for installation into
ETSI 2200*600×300mm racks is required.
5-2-2-11-2) 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.
5-2-2-11-3) Earthing: It shall be possible to earth a signal cable on either input or output
side, or on both sides.
5-2-2-11-4) The equipment shall have a positive power earth and a separate signal earth
(rack earth). The signal earth shall not carry any power current.
5-2-2-11-5) The connection of the positive power supply to the signal ground in the rack
shall be an optional strapping facility.
5-2-2-11-6) Connectors
a) All 75 ohm sub-rack connectors shall be BNC type.
b) The 120 ohm sub-rack connectors shall be DE9 type.
5-2-2-11-7) The SSU shall not be susceptible to interference from other
telecommunication equipments or radio signals, and shall comply with EN 300 386-2
class B, EMC requirements.
5-2-2-11-8) The equipment must meet the specifications when in operation, while being
subjected to temperature controlled locations with no forced air cooling applied.
5-2-2-11-9) The equipment will be permanently mounted in a fixed position.
5-2-2-11-10) Bidder shall demonstrate compliance to ISO 9001.



5-3) SYNCHRONIZATION NETWORK MANAGEMENT SYSTEM
(SNMS)
   The synchronization network management system shall provide the following general
      features:

 5-3-1) Management Requirements
5-3-1-1) The synchronization management system shall provide a platform for full FCAPS
based synchronization element management.


                                              83
5-3-1-2) The synchronization management system shall be simple to install, configure and
operate.
5-3-1-3) The synchronization management system shall be based on commercially available
PC hardware and associated operating systems.
5-3-1-4) 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.
5-3-1-5) Additional clients should not need to interface the synchronization elements
directly.
5-3-1-6) It should be possible to achieve all the functional requirements of the SNMS using
just the server application.

 5-3-2) Functional requirements
5-3-2-1) A synchronization management system shall be capable to oversee the
functioning of the synchronization network element (SNE) and the synchronization
network remotely.
5-3-2-2) The synchronization management system shall have the capability of managing
the synchronization supply units (SSU‟s) along the entire network from a single network
operation centre (NOC).
5-3-2-3) The SNMS should be manageable and controlled by EMS and NMS.
5-3-2-4) The SNMS shall be based on the UNIX or Windows 2000 Professional or
Windows™ XP Professional platforms, and will use industry standard communication
hardware and software tools.
5-3-2-5) The bidder shall declare its server ability to accept the maximum client working
at the same time.
5-3-2-6) The bidder must declare the maximum number of NE‟s per workstation.
5-3-2-7) 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.
5-3-2-8) The SNMS shall support Network connectivity between the SSU‟s and
synchronization management system over TCP/IP.
5-3-2-9) 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.
5-3-2-10) The SNMS shall conform to TMN standards and perform the following TMN
management functions:
   a) Fault Management

   b) Performance Management

   c) Configuration Management


                                             84
      d) Inventory Management

      e) Security Management.

5-3-2-11) The SNMS shall monitor the tracing/observing satellite number, satellite tracing
status of the GPS or GLONASS system.
5-3-2-12) The SNMS must be expandable.

     5-3-3) Alarm/Fault Management
5-3-3-1) The SNMS must check the connection with the SSU‟s periodically, and notify
       the operator of the loss of connection.
5-3-3-2) An alarm condition shall be indicated by a flashing icon or change of color so
       that attention is drawn to the fault.
5-3-3-3) It shall be possible to detect alarm conditions on any of the synchronization
       elements without human intervention.
5-3-3-4) 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.

                                                85
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.

     5-3-4) 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.

     5-3-5) 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

     5-3-6) Performance Management
5-3-6-1)SNMS shall have the ability to upload input performance data from the
synchronization elements.
5-3-6-2) MTIE1, TDEV2, Frequency offset, and phase information must be uploaded from
all SSU‟s where GPS/GLONASS is installed; only phase information from the
GPS/GLONASS module must also be uploaded.
5-3-6-3)SNMS shall collect the performance data automatically or on demand from the
synchronization elements.
5-3-6-4)SNMS must store the performance information that is retrieved from the
synchronization elements.
5-3-6-5)SNMS shall generate measurement results in graphical format with the ITU-T
standard masks for comparison.
5-3-6-6)SNMS shall be able to export the measurement results in numerical format for
further analysis using third party products such as Microsoft Excel™.




1
    Mean Time Interval Error
2
    Time Deviation

                                              86
 5-3-7) Security Management
5-3-7-1)SNMS shall support different levels of user access to assign different operating
and provision privileges for each user.
5-3-7-2) There should be a capability of creating, maintaining and adjusting
management domains, adding additional security while also providing organizational
view for the NEs.

 5-3-8) 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.




                                             87
Chapter: 6



  6)        Network Management

  6-1) General Requirements
  1)Network management system shall be according to ITU-T Recommendation M.3000
  series with the emphasis on M.3200, M.3400 and M.3050.
  2) Network Management system shall cover at least EML1, NML2 and optionally SML3.
  3) Each Network Element (NE) shall be managed through local, area and central
  management by considering (NMS4, NCT5, and LCT6)
  4) Two network managers for Tehran (SC1 and SC2) as hot standby to each other and the
  third one with an independent DCN in Esfahan (SC2) shall be considered.
  5) 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)..
  5-1) each EMS shall manage all NEs in the related stations.
  5-2) each control center shall only be able to control its own NEs.
  5-3) each NE shall be managed by at least two EMSs.
  6) 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 513, 608, and 814.
  7) NMS, EMS and the remaining control centers shall have the capability of managing all
  NEs such as SDH and WDM.




  1
      Element Management Layer
  2
      Network Management Layer
  3
      Service Management Layer
  4
      Network Management System
  5
      Network Craft Terminal
  6
      Local Craft Terminal


                                                88
8) Security for network management shall be based on ITU Rec. 3400.
9) The standby system shall be able to be switched manually and automatically.
10) NMS and EMS shall be equipped with necessary standards in order to be integrated
horizontally and vertically with any other management system.
11) NMS shall be able to connect Next Generation Network (NGN) management and
elements.
12) NMS and EMS shall support OCH Client, OMS, OTS, and OSC Trails.




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



6-2) Fault Management Function

1) Fault management function shall be according to ITU-T recommendation M.3400.
2) 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 ).
3) 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.
4) Fault management shall be able to support the following alarm severities such as:

        - Critical

        - Major



                                              89
         - Minor

         - Warning

5) The severity of the fault is indicated with a corresponding color.
6) It shall be possible for operator to customize colors for each severity class.
7) 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.
8) The fault state of a network object shall either be normal or faulty and be indicated with
a corresponding color.
9) EMS shall be able to do alarm correlation process.
10) The cleared unacknowledged alarms ( in history log ) shall be indicated to operator on
monitor by an indicator.
11) Cleared faults shall be stored in a fault history database. Deletion of entries in fault
history requires a special access right.
12) 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. )
13) history event log shall have exceeding warning.
14) 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
15) Fault history entry shall contain at least the following attributes:
 a. Fault source


                                                90
  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
16) It shall be possible to use state filtering according to operator's selection.(such as all
events , specific event type , event source , event duration)
17) A toggle filtering shall be possible through a Combo box.
18) 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.
19) 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.
20) It shall be possible to record problem description into a Trouble Ticket.
21) The Trouble Ticket shall provide facilities to record information on network service
problems.
22) Additional information on the problem shall either be attached to the Trouble Ticket,
or shall be accessed from the Trouble Ticket.
23) 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.
24) The Trouble Ticket shall define an initiating operator and a responsible operator.
25) Initiating operator shall edit, close and delete the Trouble Ticket. Other operators shall
only be able to view the Trouble Ticket.
26) A text including source and result of source shall be indicated by moving mouse on an
alarm.
27) Alarm type shall be identified for each fault:
- Primary alarm: Network element causes alarm.
- Secondary alarm: The alarm occurred through other equipments.
28) There shall be an index list of all possible alarms which can be made by network
element.
29) 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.
32) Each event shall be recognized on real time.
33) System shall synchronize and adjust alarm data between network elements and NMS

                                                 91
automatically and manually.
34) It shall be possible to log all alarms and their information.
35) Fault data in EMS shall be stored manually and automatically.
36) In EMS, network element alarms shall be cleared automatically after removing alarm.
( shall be remain in history log. )
37) 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.
38) Network management system shall be able to recognize the location of fault in
transmission environment (for example OTDR). (Optional)
39) Management system shall be able to make a virtual fault manually for test in the
service.
40) If a maintenance job is made for test by operator, a maintenance alarm shall be
appeared in NMS and EMS.
41) 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)


                                                   92
             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.




6-3) Security Management Function

1) Security management function shall be according to ITU-T recommendation M.3400.
And ……..
2) Security Management shall provide facilities to control operators' access to the
Network Management System.
3) Each operator shall have a user name and a password.
4) The access control shall be based on the use of operator user names and passwords.
5) 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.
6) 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.
7) Additional security shall be achieved by setting a password expiration time and by
setting a login attempt limit.
8) The operator with the highest security access rights can restrict other operators to
access the system.
9) The system shall be controlled such that a VPN operator cannot access the system
without a pre-programmed hardware identification module.

                                                   93
10) The MANAGEMENT system shall have been protected for any unauthorized access
via DCN or other related network.
11) It shall be possible to log all events.
12) It shall be possible to access network through DCN equipments and remote facilities.
13) Access to all Databases shall be possible through extra ID and Password.
14) It shall be possible to define a time out for login job for users.
15) It shall be installed a sufficient firewall with update ability for connecting to other
networks.
16) 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.

17) Network management system shall have a database of user's information and abilities.
18) If any user enter wrong password for defined times, user's ID shall be locked .
19) Administrator shall be able to change the default user permission and define extra job
in each access level.
20) User's account expiration time shall be defined by administrator.
21) System shall accept only complex Password combination of numbers, letters and
special characters and at least 8 characters.
22) A main version Anti-virus with valid and permanent Licence with updating ability
shall be installed on computer systems.
23) If operator doesn't use a computer for a defined time, the screen shall be locked
automatically. It shall get password for unlocking screen.
24) It shall be possible to check for signs of software intrusion.
25) Any information from previous user shalln't be seen on the screen.
26) Each user can be able to change his/her own password and default facilities
27) LCT (Local Craft Terminal) shall work by NMS authorizing

6-4) Configuration Management Function
1) Configuration management function shall be according to ITU-T recommendation
M.3400.

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

                                                   94
            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.

3) 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
4) It shall support LCAS and GFP protocol.q1
5)Network Configuration Function shall provide facilities to define the topology and
configuration of the network.
6) The network topology shall be determined by the placement of locations, nodes, trunks
on a network map.
7) The network configuration shall be determined by equipping nodes with units and
interface modules, and by binding trunks to interfaces.
8) 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
9) 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.
10) Network management system shall be able to recognize physical links automatically.
11) Provisioning of embedded control channel must to be supported by Network
Management System.
12) 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.
13) The system shall contain an integrated unit software download manager facility with
the following features:

                                                  95
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.
14) The facilities to define and monitor network synchronization system shall be included
in the Network Configuration Function.
15) The system shall automatically maintain, monitor and distribute real time in each
network element. This real time shall contain time and date information.
16) 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
17) It shall be possible to change the active cross-connection card or matrix by one
operator command or automatically.
18) The system shall be able to create script files, such as channel provision, to speed up
programming repetitive actions.
19) 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.
20) 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.
21) The system shall count number of faults of each interface in the network and report it
to the configuration management.
22) System shall be able to recognize all the new equipments through autodiscovery
process.
23) It shall be possible to view the created paths between network elements graphically
and control it in the NMS level.
24) Network management system shall be able to create, update, delete and restore
network management topology data.
25) Updated topology in network configuration (nodes, trunks and channels) shall be
viewable for all users simultaneously.
26) It shall be possible to select protection type and activate or deactivate protection on a
                                               96
single channel level via management network.
27) Network management system shall be able to define different protection architectures
such as:
- 2F-MSPRing and 4F-MSPRing
- Drop and Continue
- SNCP(I,N)
- Mesh and Restoration
- ASON architecture
- manual and automatic switching
27-1) 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
28) Creating and viewing Cross-connection in path and trail shall be possible through text
and graphic.
29) Creating of other paths with defined characteristics, between two nodes, shall be
possible through copying one path.
30) 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.
31) Configuration management shall have an inventory file from all network elements.
32) NMS shall have capacity management such as number of exiting paths and total
unused capacity of network and per path, and …

6-5) Performance Management Function
1) Performance management function shall be according to ITU-T recommendation
M.3400.G821-G828
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 .

2) Performance Management includes the following function set groups:
• Performance Quality Assurance.


                                                97
• Performance Monitoring.
• Performance Control.
• Performance Analysis
3) 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).
4) The Performance Management shall provide facilities to monitor the performance of all
trunks and channels.
5) There shall be two types of performance parameter collection intervals: 15 minutes and 24
hours and unavailable time shall be reported to the operator as a warning and the measuring time
shall be defined by authorized operator.

6) There shall be performance history file for evaluating performance of transmission
systems.
7) 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.
8) Any exit from thresholds in 15 minutes and 24 hours periods shall be reported to the
operator immediately.
9) Performance data shall be reported as soon as requested by operator.
10) It shall be possible to get the periodical performance report by means of network
failure analysis for predicting faults.
11) Dedicated ports performance data shall be able to report by operator's request.
12) It shall be possible to send these reports to other analyzing environments (for example
Excel).
13) It shall be possible to report the end-to-end and area-to-area performance for all
channels.
14) It shall be possible for the performance statistics to be reported in tabular as well as in
a graphical form such as a histogram.


                                                98
15) The load in a link shall be presented as the ratio of used capacity to available capacity.
16) The performance measurement shall be calculated continuesly and automatically and
manually for each service and it mus be able to present results on web
17) The storage capacity for performance values shall be enough



6-6) Application Development Function

1) 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.
2) 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.
3) It shall be possible to enhance existing Network Management workflows to speed up
Network Management processes like network configuration.
4) The developed applications shall support controlled timer and simultaneous task
execution for applications like queries.
5) It shall be possible to design and set the graphical user interface.
6) 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) .
7)The User shall be able to create shortcuts on the screen or icons in the tools menu for
most used items.



6-7) Network Management System User Interface

1) 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.
2) It shall be possible to view the network in both tree-like and graphical format.
3) All the NMS tools shall be opened from the main program such as a NMS Toolbox.
4) Each tool, in turn, shall consist of a set of windows and dialogues.
5) The system shall not have any limitation for number of simultaneous opened windows
and dialogues.
6) 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.
                                                99
7) The windows shall graphically represent various network elements and objects.
8) 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.
9) The system shall provide a comprehensive and easy-to-use on-line help facility in each
application to get the best resolution.
10) 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.
11) 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.
12) System shall be able to indicate all network elements such as NG-SDH and C/DWDM
in one graphical view.
13) All the related information such as wavelength, NE type, characteristics and NE
address shall be shown through moving the mouse on NE.
14) 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.
15) Network manager shall be able to give/take access rights to local users.



6-8) Configuration backup and recovery

1) 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.
2) 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.
3) 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.
4) The NE shall be able to restore configuration data from a backup following the
detection of corrupted data in the configuration database.
5) The management system shall download the backup files to NE in essential case(s).
6) The NE shall do this job by receiving commands from management system.
7) The management system shall be able to create a backup manually and automatically in
defined periodical time by the operator.
8) Servers backup shall be done in two modes:
   1- Full backup (including OS, applications and database and …)


                                              100
   2- 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 …

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


Table 1 : Hardware characteristics

    Hardware     CPU         Clock Rate     Main            Disk          Monitor     OS
                                            Memory          Memory

    Client

    Server




                                               101
10) Software shall be able to work on Windows, Linux,… platforms.
11) Server shall have 2 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.
12) Software and hardware shall be the latest versions in delivery time.
13) Client and server shall have telnet ability.
14) The ability of internet connecting via Leased line shall be possible, and it shall be
possible to be activated or inactivated, by network manager.
15) 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 10
years.
16) 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 ,19 ” color monitor , laser printer , etc.

6-10) DCN1
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 .-
4
1) DCN shall provide environment for TMN2 management messages communication.
2) DCN shall provide environment for signaling messages communication for ASTN3 and
ASON components in different topologies such as linear, ring and mesh.
3) The topology of each DCN sub network shall contain mesh or ring or other topology in
order to protect DCN.
4) Data communication channels between NEs including GNE4 shall support OSI over
IP5.
5) The EMS and NMS connections shall be done through a WAN6 with a proper speed.
6) The WAN topology connecting EMSs shall be ring or mesh in order to protect DCN.
7) DCN architecture shall support OSI over IP



1
    Data Communication Network
2
    Telecommunication Management Network
3
    Automatic Switching Transport Network
4
    Gateway Network Element
5
    OSI over IP
6
    Wide Area Network

                                               102
8) Physical channels among NEs shall support ECC1 including DCC2 channels for SDH
and GCC in OTN3.
9) Each area shall consist of optimum GNEs in order to increase reliability
10) All routers and peripherals connecting EMSs in WAN network shall be managed in
NMS (DCN management).



6-11) Processing of the routing

1) NMS shall be able to calculate and implement the routing for LOP4, HOP5 and Trial.
2) NMS shall be able to calculate and implement the routing based on using cost factor
over physical links.
3) NMS shall be able to calculate and implement the routing for ASTN and ASON nodes.
4) NMS shall be able to calculate and implement the routing based on shortest path first
(OSPF).
5) NMS shall be able to calculate and implement the routing based on at least three
predefined conditions.
6) NMS shall be able to calculate and implement the routing based on at least passing
nodes.
7) NMS shall be able to calculate and implement the routing base on link disjoint
procedure.
8) NMS shall be able to calculate and implement the routing using Node disjoint
procedure.
9) 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.

6-12) VPN6
1) The network management system shall support virtual private networking.
2) Virtual private network shall be consisted of the following components:


1
    Embedded Control Channel
2
    Data Communication Channel
3
    Optical Transport Network
4
    Low Order Path
5
    High Order Path
6
    Virtual Private Network

                                             103
a. Shared and dedicated nodes
b. Dedicated trunks
c. Virtual trunks
d. Shared and dedicated interfaces
3) 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.
4) The manager shall be able to view VPN tunnels.
5) It shall be possible to define security levels for VPN tunnel.
6) User's identification shall be recognized for security, only the authorized users shall be
able to have access to this network.
7) It shall be possible to define security policies in VPN.
8) There shall be provided facilities to change the topology of the network.
9) It shall be possible to add, delete or change equipments, sites, traffic and etc easily in
the management system.
10) It shall be possible for the operator to assign a group of management capabilities to an
external company or a customer.
11) It shall be possible to inform customer about important events such as failing or
reconnecting the service.
12) It shall be possible to show the service performance to customer network.
13) 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




                                                104
             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


6-13) GUI Requirements


1) The GUI shall simplify EMS usage by adding off-line/on-line proper help (graphical or
text based) for all functionalities of EMS.
2) The GUI shall simplify navigation and access with point-and-click maps feature.
3) The GUI shall simplify navigation and access with pull down menus feature.
4) 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.
5) The NMS shall support secure web-based LCT for easy and convenient access of NEs
in the field (optional).
6) The NMS shall support having interface with multi level network topology maps (both
tree-like and graphical format).
7) All layers of transmission including DWDM, SDH and NG-SDH elements shall be
seen at the same window.
8) The GUI shall have a real-time view of all network events.
9) 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.
10) The GUI shall support simultaneous open active windows (e.g. fault Summery
windows for different elements).
11) 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.


                                              105
12) The GUI shall clearly indicate when commands are being processed and the UI is not
ready for input.
13) The GUI shall support wizards and templates during any type of creation activity.
14)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.
15)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.
16)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.
17)The EMS shall support GUI cut-through (GCT) feature to allow the NMS to access the
EMS user interface.
18) EMS GCT functionality on NMS shall be the same as the one available to an EMS
client user when invoked within the EMS.

6-14) NML-EML Interface Requirements


The EMS shall support TMF 814(OFCOURSE it shall be based on the latest standards)
interface as its northbound interface .
The EMS shall support other standard protocols such as SNMP V2-3, ODBC, RMON,
and CMIP (Q3) as its interface for connecting to other systems.
The EMS shall support standard interfaces such as SNMP V2-3, and TL1 as its
southbound interface.


                                               106
The EMS shall support customizable XML interfaces for its integration with other
management systems such as Trouble Ticketing Systems.

6-15) Non-Functional Requirements
1)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.
2)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.
3)Scalability
a)The supported number of concurrent users per instance of the front-end will meet
enough number of projected users per outlet location.
4)Supportability
a)It must be possible to define new data fields to be presented to the user.
5)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.
6)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

7)Performance
a)The maximum delay time between agents and main site must be 0.1 second.

                                                 107
8)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.
9)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.
10)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.
11)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
5 years periods.
c)The solution design shall provide full plans for installation of hardware and systems
implementation.
12)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
13)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.


                                             108
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.
14)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.
15)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.



6-16) 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


                                             109
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 12 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.

6-17) Training


General
     1. 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
     2. The Bidder shall arrange and conduct training in the most efficient way using
        state of the art techniques, methods and training facilities.
     3. The training personnel of the Bidder must have proven their experience in the
        field and shall be certified.


     4. 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

                                              110
       e. Network and Customer Service Planning , re-planning


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

Technical and                                                 30 days Before
Network                                                       installation
Management

General -                                                     30 days Before
Operation and                                                 installation
Maintenance

Network and                                                   60days before
Service Planning ,                                            first shipment
re-planning



Installation and                                              30 days Before
commissioning                                                 installation



 6. 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
 7. 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 )

                                       111
    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.
8. Bidder‟s Training Personnel
    a. The Bidder shall state the number, qualifications and experience of the
        Bidder‟s 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 Bidder‟s training personnel has conversational knowledge of the
        Farsi language
    d. The Bidder‟s training personnel shall maintain a systematic procedure of
        monitoring and reporting the progress of all trainees besides the task of
        lecturing.


9. 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.
10. 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


                                        112
                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.

6-18)Maintenance Period
Initial Network management Equipment Maintenance Period
1.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,..
2.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.
3.The Bidder shall provide full access to technical support personnel from first line to
third line or expert support on a 24 x 7 x 365 (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.
4.The Bidder shall keep sufficient stock of spare parts in the Islamic Republic of Iran to
provide mission critical support.
5.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.
6.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



                                              113
1.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
2.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 24x7x365
                     basis (twenty four hours per day, seven days per week, and 365 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.



6-19)Provision of Documentation and Software
1.The Bidder shall provide all necessary documentations such as:



                                             114
                 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
2.The Bidder shall provide complete Operations and Maintenance manuals for the
provided solution.
3.The Bidder shall provide a detailed list of documentations that will be provided, with a
short description of each book or manual.
4.All documentations shall be provided in softcopy (CD-ROM) and hardcopy, with
enough quantity of each of softcopies and hardcopies.
5.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.

6-20)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:
   1.   Customer data
   2.   Contract data/services
   3.   Transmission service equipment data
   4.   Flat Company
   5.   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:
   1.   Unique customer ID.
   2.   First name of the customer
   3.   Second surname
   4.   Name of the customer.
   5.   Name of the company.
   6.   Legal status of the company

                                              115
   7. Customer specific contact person.
   8. Contact telephone number of the customer.
   9. E-mail address of the customer.
   10. Fax number of the customer.
   11. Date of birth of the customer.
   12. 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
   1.   Banking data and banking arrangement data
   2.   Credit/Debit card data
   3.   Taxation relevant customer data (such as tax numbers, VAT codes, etc.)
   4.   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:
   1. Business customers
   2. Large corporate customer
   3. 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.)



6-21)Customer contract, QoS/ SLA data administration


   1. 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.



                                               116
2. 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
3. At least the following contract QoS/ SLA related data shall be supported and
   managed by the system:
       a. Unique Contract QoS/ SLA ID‟s
       b. Beginning and end of contracts, QoS/ SLA‟s with effective dates
       c. Details about the service packages and QoS contracted by the customer and
           defined in SLA‟s
       d. Details about all services & QoS contracted by the customer and defined in
           SLA‟s.
       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, 3rd 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.




                                          117
Chapter: Seven




7) ASON/ASTN
7-1)    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.

7-2)    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:

 7-2-1)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.707 and G.709.

 7-2-2) Control Plane
The control plane should be according to the relevant recommendations such as ITU
G.807 and G.8080.
The control plane of the ASON/ASTN shall meet the following basic function
requirements:
7-2-2-1) It shall provide distributed connection control and management functions,
including connection establishment, deletion, query and modification.
7-2-2-2) It shall provide the routing function, including the distribution of routing
information and the calculation of the routes.
7-2-2-3) It shall provide the signaling function which it shall be able to implement
connection management.
7-2-2-4) It shall provide the auto discovery function, including neighbor discovery,
resource discovery and topology discovery.
7-2-2-5) 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.

                                               118
7-2-2-6) It shall be applicable to different network topologies including chain, ring and
mesh networks.
7-2-2-7) It shall be able to provide multiple protection/restoration mechanisms.
7-2-2-8) 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.
7-2-2-9) The proposed system OIF confirmation documents should be submitted.
7-2-2-10) It shall explain the techniques for increasing control plane reliability,
expandability and efficiency.
7-2-2-11) The failure of the control plane shall not affect the existing connections in the
transport plane.
7-2-2-12) 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.
7-2-2-13) The logic topology of the control plane shall be independent of the physical
topology of the transport plane.
7-2-2-14) 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.
7-2-2-15) The last version of the utilized software shall be provided and specified. The
date of software release must be also specified.

 7-2-3) Management plane
The management plane of the ASON/ASTN shall meet the following basic function
requirements:
7-2-3-1) It shall implement maintenance management of the transport plane, the control
plane and the whole system.
7-2-3-2) It shall also be responsible for the coordination between the three planes.
7-2-3-3) It shall complete five TMN functions as specified in M.3010: Performance
management, fault management, configuration management, customer management and
security management.
7-2-3-4) It shall be able to implement the basic connection management functions,
including connection establishment, connection deletion, connection query and connection
modification.
7-2-3-5) It shall be able to set the attributes of connections.



                                                119
 7-2-4) 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.

 7-2-5) Intelligent Control Mode
The ASON/ASTN is required to support the distributed intelligent control plane.

7-3) Functional Requirements for Control Plane
 7-3-1) Connection Management
7-3-1-1) 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)
7-3-1-2) 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 VC4 and VC12.
   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).
7-3-1-3) 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.
7-3-1-4) 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).
7-3-1-5) Vendors should specify system capability in supporting the customer to directly

                                              120
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)

 7-3-2) Auto Discovery and Link Management
7-3-2-1) The control plane of ASON/ASTN should have the auto discovery and link
management functions
7-3-2-2) 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.
7-3-2-3) 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)
7-3-2-4) 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)


 7-3-3) Routing
The routing of the ASON/ASTN control plane should satisfy recommendations G.8080
and G.7715. 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.
7-3-3-1) Intra-domain routing protocol: It is required that the OSPF-TE protocol be
adopted as the intra-domain routing protocol.
7-3-3-2) Inter-domain routing protocol: The options include BGP, OSPF-TE and DDRP.
7-3-3-3) The following four types of disjoint routes should be supported:

     a) Link disjoint

     b) Node disjoint

     c) Shared Risk Link Group Disjoint (SRLG Disjoint)

                                             121
    d) Path correlation

7-3-3-4) 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.)
7-3-3-5) 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.

 7-3-4) Signaling
The ASON/ASTN signaling shall be accordding to recommendations G.8080 and G.7713
and it shall meet the following function requirements.
7-3-4-1) 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
7-3-4-2) The control plane of ASON/ASTN should support recommendation ITU-T
G.7713.2 (RSVP-TE signaling protocol).
7-3-4-3) The control plane of ASON/ASTN should be capable of selecting signaling
protocol between ITU-T G.7713.1 (PNNI) and G.7713.3 (CR-LDP).
7-3-4-4) 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.
7-3-4-5) 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.8080, ITU G.7713 and G.7713.2.


                                             122
7-3-4-6) The RSVP-TE signaling should support the establishment of soft permanent
connections (SPCs).
7-3-4-7) To enhance the explicit route functions, the RSVP-TE signaling should provide
explicit label control.
7-3-4-8) 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.
7-3-4-9) 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.
7-3-4-10) 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.

 7-3-5) 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.

 7-3-6) 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

 7-3-7) Reliability
7-3-7-1) The control plane should have good reliability and be able to continue its work in
the case of faults.
7-3-7-2) 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.
7-3-7-3) The control plane should provide reliable transmission of signaling messages.



                                               123
7-3-7-4) The network fault of a certain place in the control plane should not affect the
operation of the other nodes in the control plane.
7-3-7-5) 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.
7-3-7-6) Any failure of the control plane shall not cause failure of the management plane.
7-3-7-7) 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.
7-3-7-8) 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.
7-3-7-9) 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.

 7-3-8) Security
7-3-8-1) Incorrect connections should be prevented during the connection establishment
process.
7-3-8-2) The control plane itself should have the appropriate security mechanism to guard
against illegal intrusions.
7-3-8-3) 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.
7-3-8-4) 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.
7-3-8-5) 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).
7-3-8-6) The control plane should be able to periodically transfer its various event
information related to security to the management plane.
7-3-8-7) 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.


                                              124
7-3-8-8) The control plane should be able to generate various alarm information related to
security events, and periodically transfer such information to the management plane.

7-4)      Technical Requirements for Protection/Restoration
7-4-1) The ASON/ASTN is required to have multiple protection/restoration mechanisms,
so as to meet the different network application requirements.

7-4-2) 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.
7-4-3) The ASON/ASTN equipment is required to support protection switching of the
traditional SDH networks as well as mesh protection/restoration.

 7-4-1) Traditional SDH Protection Switching Capability
7-4-1-1) 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

7-4-1-2) The switching time shall not be more than 50 ms in the case of protection
switching upon failure of a node.
7-4-1-3) Of the above, MSP, MS-SPRing and SNCP should meet the requirements set
forth in Recommendation G.841 while DNI should meet the requirements set forth in
Recommendation G.842.

 7-4-2) Mesh Protection/restoration Capability
7-4-2-1) 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.


                                               125
        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.
7-4-2-2) 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.
7-4-2-3) The vendors should state which type of fault transfer mechanism they adopt.
7-4-2-4) With the participation of the control plane, the ASON/ASTN should be able to
dynamically provide the protection path.

7-4-2-5) 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.

7-4-2-6) Network faults occur to the working path works while the protection path works
normally:

When network faults occur to the working path, it‟s service should be timely switched
over the protection path while the original protection path should become the working

                                                126
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.

7-4-2-7) 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.
7-4-2-8) The ASON/ASTN should support 1+1 protection and 1:1 protection.
7-4-2-9) 1+1 protection should support bi-directional switching mechanism.
7-4-2-10) The 1+1 protection switching time should be less than 50 ms.
7-4-2-11) After the protection switching is finished, the protection switching event should
be reported to the NMS.
7-4-2-12) Protection switching criteria: In one of the following conditions, 1+1 protection
switching should be conducted:

     a) Loss of Frame (LOF)

     b) Loss of Signal (LOS)

     c) Multiplex Section AIS (MS-AIS)

     d) B1/B2 Bit error threshold exceeded (B1OVER/B2OVER)

7-4-2-13) In 1:1 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.
7-4-2-14) Protection switching criteria: In one of the following conditions, 1:1 protection
switching should be conducted:

                                             127
    a) Loss of Frame (LOF)

    b) Loss of Signal (LOS)

    c) Multiplex Section AIS (MS-AIS)

    d) B1/B2 Bit error threshold exceeded (B1OVER/B2OVER)

7-4-2-15) 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.
7-4-2-16) 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)   B1/B2 Bit error threshold exceeded (B1OVER/B2OVER)

7-4-2-17) 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.
7-4-2-18) 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.
7-4-2-19) Priority requirements of mesh restoration



                                             128
- 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.

7-4-2-20) 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.
7-4-2-21) The ASON/ASTN should guarantee that all the recoverable mesh protection
paths can complete protection switching within 50 ms.
7-4-2-22) 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.
7-4-2-23) 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.
7-4-2-24) 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.
7-4-2-25) 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”.




                                               129
 7-4-3) 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.

7-5)      Technical Requirements for the Transport Plane
 7-5-1) 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.709.
7-5-1-1) Cross-connect capability
7-5-1-1-1) The equipment should have a flexible SDH VC cross-connect matrix with the
cross-connect granularity of VC4 and VC12. (The vendors should provide a detailed
description of the cross-connect specifications.)
7-5-1-1-2) For the OXC equipment, the bi-directional non-blocking cross-connect
capacity of a single rack should be at least 320G. 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 7-1: bi-directional non-blocking cross connect capacity

                                 OXC     MSTP (Type 1) MSTP (Type 2)

                 Min HO XC      320 G         160G               80G

                 Min LO XC       20G           20G               10G



7-5-1-1-3) The supported cross-connect types should include:

       a) Unidirectional

       b) Bi-directional

       c) Unidirectional broadcast



                                              130
     d) Loopback

     e) Drop & continue

7-5-1-1-4) 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. 7-1: online detection of services

7-5-1-1-5) 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.

7-5-1-2) Service capability:
7-5-1-2-1) The supplier shall state system capacity for MSTP service.

  ATM             E1              E3                 STM-1                STM-0            STM-4

  STM-16          STM-64          FE                 GE                   10GE



7-5-1-2-2) The supplier shall state system capacity for OXC services.




                                                   131
  ATM            E1             E3             STM-1          STM-0          STM-4

  STM-16         STM-64         FE             GE             10GE



7-5-1-3) Hot backup capability of boards/cards
7-5-1-3-1) 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.)
7-5-1-3-2) Forced active/standby switch-over should be able to be executed on the boards
with hot backup through the NMS.
7-5-1-3-3) The plugging/unplugging and switch-over operations of the control board with
1+1 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.
7-5-1-3-4) 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.
7-5-1-3-5) The plugging/unplugging and switchover operations of the power board and
the clock board with 1+1 protection should not cause any impact on the existing services.

 7-5-2) Networking Capability
In addition to supporting the traditional SDH ring and chain networking modes, the
transport plane should support mesh networking.

 7-5-3) SDH interface
7-5-3-1) The interface requirements of the SDH-based multi-service transmission node are
given in the table below.




                                            132
                Table 7-2: Types of SDH interface and their requirements


                       Interface         Interface type    Satisfied standard


                                             STM-1           ITU-T/ G.957


                                             STM-4           ITU-T/ G.957
                   Optical interface
                                           STM-16            ITU-T/ G.957


                                           STM-64            ITU-T/ G.691


                  Electrical interface       155M            ITU-T/ G.703



7-5-3-2) GE interface requirements:
    a) The GE interface supported by the ASON/ASTN nodes should be according to
        requirements given in IEEE 802.3 z.

    b) The GE physical interface should support 1000Base-SX and 1000Base-LX.

 7-5-4) Ethernet Service
7-5-4-1) The ASON/ASTN should support the point-to-point transparent transmission of
Ethernet services and guarantee the transparency of the protocols in L2 and above.
7-5-4-2) 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.7041
7-5-4-3) 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.
7-5-4-4) The mapping of Ethernet interfaces into SDH containers should satisfy the
requirements as given in the table below.
              Table 7-3: Mapping of Ethernet interfaces into SDH containers

                        Ethernet interface                SDH mapping unit

                                                      VC-3-Xc/v
                1000Mbit/s adaptive interface
                                                      VC-4-Xc/v


                                               133
7-5-4-5) 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.
7-5-4-6) The specific technical specifications of the LCAS should satisfy the requirements
in ITU-T G.7042.
7-5-4-7) All VC containers should be able to be transmitted on different physical routes.
7-5-4-8) 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.
7-5-4-9) The ASON/ASTN should support the manual/forced increase/decrease of the
concatenation capacity.
7-5-4-10) When a member fails, the system should be able to keep effective data
transmission for normal members.
7-5-4-11) 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.

 7-5-5) Node Performance
7-5-5-1) 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.825.
7-5-5-2) For the store-and-forward and forward-by-bit equipments, forwarding delay
should be low. (The vendors should state the typical delay value.)

7-6)    Timing & Synchronization Requirements
The ASON/ASTN should support and satisfy the requirements of timing &
synchronization section.

7-7)    NM Function Requirements
The ASON/ASTN should support and satisfy the requirements of NM function section.




                                             134
Chapter: Egiht



8) Maintenance


8-1) Introduction
The vendor must provide all the obligations for maintenance and equipment support
aforementioned below.

8-2) Obligations for maintenance and technical support
8-2-1) 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.
8-2-2) The system must have appropriate direction for system maintenance for failure
prevention, performance improvement and failure removal.
8-2-3) The system must have sufficient direction for routine maintenance in order to avoid
failure occurring.
8-2-4) The vendor is required to train maintenance personnel.
8-2-5) The vendor is required to support the possibility of establishing 24-hour connection
between maintenance personnel and expert personnel of the vendor for consultation and
guidance up to final equipment delivery.
8-2-6) 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.
8-2-7) The vendor should provide a list of the time between failure and exchange time of
the parts of the equipment.
8-2-8) 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.
8-2-9) 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.
8-2-10) The vendor is required to provide reformatory performances including: finding
and localizing failure, failure removal and exchanging the faulty parts.
8-2-11) Maintenance operations must be done locally or by TMN.
8-2-12) There should be appropriate warning marks in the system for maintenance
operation.

                                             135
8-2-13) The warning marks should be in three forms: emergency, inemergency and
indicative.
8-2-14) The system must be capable of measuring the characteristics of input/output
optical signal of each unit.
8-2-15) The parameters values displayed by the software must be the same as the values
measured by the hardware.
8-2-16) 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.826
standard.
8-2-17) The vendor is required to give information about measurement devices and
instruments necessary for system maintenance.
8-2-18) 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.
8-2-19) 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.
8-2-20) Software look back tests in all levels should be possible.
8-2-21) 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.
8-2-22) Repairing a unit and returning it by the contractor should not take more than 1
month.




                                              136
Chapter Nine

9) Training
9-1) 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.

9-2) Training courses
Training will be done in the following categories:
       Instruction and supervision
      Planning
      Installation & commissioning
      Maintenance & Operation
The list 9.2.1shows 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, participant‟s assumed background and planned
expectations are mentioned.

 9-2-1)Whole subjects
9-2-1-1) WDM & NG-SDH, Systems and networks: Principles and overview
9-2-1-2) WDM & NG-SDH, Systems and networks: network architectures (layer network
         architectures, hybrid networks and reference architectures)
9-2-1-3) Traffic handling, old and new methods: description and comparison
9-2-1-4) Network topologies and protections: methods description
9-2-1-5) Network topologies and protections: designing (methods, strategies and design
         algorithms)
9-2-1-6) Planning: planning software
9-2-1-7) Optical line active/passive components: necessities and power budget
         calculations
9-2-1-8) Synchronization: aspects, necessities and reference clock supply networks
         (overview)
9-2-1-9) Synchronization: designing (methods, strategies and designing algorithms)
9-2-1-10) Equipment‟s structure (Rack, subracks, units, connectors …): description and
         technical specifications.




                                             137
9-2-1-11)Equipment installation: physical aspects and installation instruments
9-2-1-12)Equipment installation: accessories, jumper‟s position, cables…. and practice of
        installation.
9-2-1-13)Equipment commissioning: initial programming and upgrade procedure
        (practice)
9-2-1-14)Equipment commissioning: startup and system configuration (software practice)
9-2-1-15)Equipment‟s working modes: alarms, events and performance parameters.
9-2-1-16)Equipment‟s working modes: periodic checks and troubleshooting.
9-2-1-17)Out of service test: system tests
9-2-1-18)In service test: loaded link tests
9-2-1-19)Network management: overview
9-2-1-20)Network management: management layers and protocols, instrument
        requirements, DCN…
9-2-1-21)Network management: software (installation and practice)
9-2-1-22)Probable changes in this generation of systems: discussion

 9-2-2)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.
9-2-2-1) Circumstance
               Location: bidder‟s training center
                Number of participants: 20
                Total duration days: 30 working days
                Theory/practical: 20 working days
                Absolute practical: 10 working days
                During the Practical work the trainees will be
                divided into 4 subgroups:
                   Planning
                   Network management
                   NG-SDH
                   WDM


9-2-2-2) Course Subjects

9.2.2.2.1 WDM & NG-SDH, Systems and networks: network architectures (layer
          network architectures, hybrid networks and reference architectures)
9.2.2.2.2 Traffic handling, old and new methods: description and comparison
9.2.2.2.3 Network topologies and protections: designing (methods, strategies and design
          algorithms)
9.2.2.2.4 Planning: planning software
9.2.2.2.5 Optical line active/passive components: necessities and power budget
          calculations
9.2.2.2.6 Synchronization: designing (methods, strategies and designing algorithms)


                                            138
9.2.2.2.7 Equipment‟s structure (Rack, subracks, units, connectors …): description and
           technical specifications.
9.2.2.2.8 Equipment commissioning: initial programming and upgrade procedure
           (practice)
9.2.2.2.9 Equipment commissioning: startup and system configuration (software
           practice)
9.2.2.2.10 Equipment‟s working modes: alarms, events and performance parameters.
9.2.2.2.11 Equipment‟s working modes: periodic checks and troubleshooting.
9.2.2.2.12 Out of service test: system tests
9.2.2.2.13 In service test: loaded link tests
9.2.2.2.14 Network management: management layers and protocols, instrument
           requirements, DCN…
9.2.2.2.15 Network management: software (installation and practice)
9.2.2.2.16 Probable changes in this generation of systems: discussion

 9-2-3)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.


9-2-3-1) Circumstance
Location: bidder‟s training center                Location: Iran with bidder trainer
Number of participants:12                         Number of participants:24
Total Course: 20 working days
                                                  Total Course: 30 working days



9-2-3-2) Course Subjects
9.2.3.2.1 WDM & NG-SDH, Systems and networks: Principles and overview
9.2.3.2.2 Traffic handling, old and new methods: description and comparison
9.2.3.2.3 Network topologies and protections: designing (methods, strategies and design
           algorithms)
9.2.3.2.4 planning: planning software
9.2.3.2.5 Optical line active/passive components: necessities and power budget
           calculations
9.2.3.2.6 Synchronization: aspects, necessities and reference clock supply networks
           (overview)
9.2.3.2.7 Equipment‟s structure (Rack, subracks, units, connectors …): description and
           technical specifications.
9.2.3.2.8 Equipment commissioning: startup and system configuration (software
           practice)
9.2.3.2.9 Network management: overview
9.2.3.2.10 Network management: software (installation and practice)




                                            139
 9-2-4)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.


9-2-4-1) Circumstance
Location: bidder‟s training center                Location: Iran with bidder trainer
Number of participants: 20                        Number of participants: 60
Total Course: 20 working days
                                                  Total Course: 30 working days



9-2-4-2) Course Subjects
9.2.4.2.1 WDM & NG-SDH, Systems and networks: Principles and overview
9.2.4.2.2 Network topologies and protections: methods description
9.2.4.2.3 Synchronization: aspects, necessities and reference clock supply networks
          (overview)
9.2.4.2.4 Equipment‟s structure (Rack, subracks, units, connectors …): description and
          technical specifications.
9.2.4.2.5 Installation
          a) Equipment installation: physical aspects and installation instruments
          b) Equipment installation: accessories, jumper‟s position, cables…. and
              practice of installation.
9.2.4.2.6 Commissioning
          a) Equipment commissioning: initial programming and upgrade procedure
              (practice).
          b) Equipment commissioning: startup and system configuration (software
              practice)
          c) Equipment‟s working modes: alarms, events and performance parameters.
          d) In service test: loaded link tests
9.2.4.2.7 Network management: overview
9.2.4.2.8 Network management: software (installation and practice)

 9-2-5)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.


9-2-5-1) Circumstance
Location: bidder‟s training center                  Location: Iran with bidder trainer
Number of participants: 48                          Number of participants: 96
Total Course: 20 working days
                                                    Total Course: 30 working days




                                            140
9-2-5-2) Course Subjects
9.2.5.2.1 WDM & NG-SDH, Systems and networks: Principles and overview
9.2.5.2.2 Network topologies and protections: methods description
9.2.5.2.3 Synchronization: aspects, necessities and reference clock supply networks
           (overview)
9.2.5.2.4 Equipment‟s structure (Rack, subracks, units, connectors …): description and
           technical specifications.
9.2.5.2.5 Equipment commissioning: startup and system configuration (software
           practice)
9.2.5.2.6 Equipment‟s working modes: alarms, events and performance parameters.
9.2.5.2.7 Equipment‟s working modes: periodic checks and troubleshooting.
9.2.5.2.8 In service test: loaded link tests
9.2.5.2.9 Network management: overview
9.2.5.2.10 Network management: software (installation and practice) .



9-3) Training General Requirements


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




                                            141
9-3-15)The bidder‟s training personnel shall maintain a systematic procedure of
        monitoring & reporting the progress of all trainees besides the task lecturing.
9-3-16) 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.
9-3-17)Any local or overseas unsatisfactory training course should be re-conducted
        locally in Iran.
9-3-18)The bidder should submit following record items of training personnel two months
        before the commencement of each course:
9-3-19)
            a) Academic education & training experience record allocated for this project.
            b) Presentation of creditable university certification
            c) Creditable training experience allocated for this project.
9-3-20)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.




                                              142
hapter Ten



10) Test Equipment
          Technical Specifications of Test Instruments




10)    General
10-1) 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.


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


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


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


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


10-6) 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.


10-7) 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 .




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


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


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


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


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


10-13) 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.
10-14) Spare


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


10-14-2)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


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

                                                144
10-15) Instruction manual


10-15-1) 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 manufacture‟s name, stock
             no, description and any additional data necessary for identification.


10-15-2) 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 .


10-16) Repair training


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




10-16-2) 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 .


10-16-3) The training course shall include the following as a minimum :
                                              145
        1- Test equipment description and theory of operation.
        2- Block diagram and circuit diagram description.
        3- Software structure description (if applicable).
        4- Repair and trouble shooting procedures for all of the units and circuits and
        replacement of module .
        5- Alignment and calibration procedure for all test equipment.
        6- Practical exercises on simulated faulty units being performed by the trainees.
        7- Practical exercises for replacement of faulty modules.
        8- Checking repaired units for satisfactory results with test equipment.


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


10-17) Environment


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


       Continuous Operation :


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


       Storage and Transportation in Packages :


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




                                             146
        10-18) Power requirements


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


10-19)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 47256 connectors.




                                                     147
Chapter: Eleven




11) Special Tools and Acc



11) 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 . 80 sets of special tools and accessories should be
offered. ( if needed ) .




                                                 148
Chapter: Twelve




12) Technical Support


  12-1)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.



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



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



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




                                           149
Chapter: Thirteen




13) Documentation

                        TECHNICAL DOCUMENTS




13-1) General


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


       1- System manual
       2- Equipment/system instruction manuals
       3- Installation manual
       4- Installation drawings
       5- Repair manuals
       6- Factory test procedures and test data sheets
       7- Field test procedures and test data sheets
       8- Inventory sheets
       9- Diskettes of installation and level drawings


13-1-2)All documents shall contain the following :


       1- Description of all volumes of each document ( to be included in all
          volumes of the relevant document )
       2- Content of each volume and section
       3- Safety information ( where applicable )


                                              150
       4- Cautions regarding operation and/or replacement of the modules (where
          applicable)
       5- Guide to use the document
       6- Complete list and description of all abbreviations and symbols used in each
          document, (to be included in all volumes of the relevant document).
13-1-3)All documents shall be in English


13-1-4)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 .


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


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


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


13-1-8)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 .


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


13-1-10)5 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 (60) days prior to the first shipment. Updated or reissued sections shall be
       provided as above subsequent release by the supplier .


13-1-11)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 (4) months after TIC request and at
       the contractor‟s cost.

                                              151
13-2)System manual


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


1- List of all documents
2- General description of the equipments
3- MUX plan
4- Route plans
5- System layout
6- System layout of the network management system
7- Local and express orderwire system layout ( including the dialing number
         of stations)
8- Power consumption of each station
9- List of maintenance centers and their relevant stations ( included in this
          specifications)
10- External alarm and status assignment table ( alarm and status list will be
           provided by TIC )
11- Block and level diagram of each station
12- Rack layout of each station
13- Rack facing of each station ( showing the units mounted in each rack )
14- Brief description of the equipment (including summarized
           characteristics of the equipment )
15- Brief description of the hardware and software of the network management
           system
16- Power Budget for each section




                                                152
13-3)Instruction manual


13-3-1)The following instruction manuals shall be delivered :


1- NG-SDH and DWDM equipment instruction manuals
2- test equipment instruction manuals
3- Network management system hardware instruction manuals
4- Network management system instruction manual ( User‟s Guide )
5- Network management system instruction manual ( Administrator‟s Guide)
6- Synchronization instruction manuals
7- Special tools manuals


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


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


13-3-3-1)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


13-3-3-2)Equipment description , including :


       a) Block and level diagrams

                                               153
       b) Description of functional operation ( signal follow and each unit‟s
         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).


13-3-3-3)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


13-3-3-4)The network management system instruction manual (User‟s 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 .


13-3-3-5)The network management system instruction manual ( Administrator‟s 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

                                               154
          screens, defining alarm filtering , etc .
       c) Data base information
       d) Security management information




13-4) Installation drawings


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


       1- 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 ,


       2- System assembly for each station


       3- Interface cable assembly description


       4- Alarm cable assembly description


       5- Racks structure layout


       6- Inter- rack and power wiring diagram


       7- Method of rack physical installation


       8- Alarm wiring


       9- Installation method for network management system software and hardware


       10- Wiring diagram of intermediate distribution board


       11- Any other drawings needed for installation of the supplied equipment

                                               155
13-5) Repair manual


13-5-1)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




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


       a) Code number and it‟s 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




13-5-3)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 .

                                              156
13-6) Inventory sheets


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


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


6.2    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




                                              157
Chapter: Fourteen




14) Factory Test and Acceptance
14-1)General


14-1-1)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.


14-1-2)The TIC representatives reserve the right to inspect the supplier and/or sub-
supplier‟s 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.

14-1-3)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.

14-1-4)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.




                                              158
14-2)Factory Test
14-2-1)The supplier shall notify the TIC at least 3 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)


14-2-2)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.


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


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


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


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


14-2-7)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.


14-2-8)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.


14-2-9)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.



14-2-9-1)Tests on DWDM equipment.:


       A-Transponder

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


14-2-9-2)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


14-2-9-3)ASON/ASTN function tests


14-2-9-4)Network management tests


14-9-2-5)Network synchronization tests


14-3) Field Acceptance test


14-3-1)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 .

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


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


14-3-3)If a problem become apparent during the installation and testing of the
contractor‟s 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 contractor‟s 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.


14-4)Final Acceptance by TIC


14-4-1)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 (4) weeks after informing the
contractor about such deficiencies.
              e)Successful completion of the installation, tests &
commissioning.


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


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


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


                                             161
14-4-5)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.




                                             162
Chapter: Fifteen




15) System Performance and its Requirements

          SYSTEM PERFORMANCE AND RELIABILITY
                    REQUIREMENTS




15-1) 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.


15-2) The MTBF occurring in the parts of the equipment shall not be less than 4 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 .


15-3) 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


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


15-4) 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.




                                           164
Chapter: Sixteen




16) Maintenance Annex
   16-1)Spare unit
   16-1-1) 10% of total price of the contract should be allocated to provide the spare
   unites.
   16-1-2)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
   16-1-1. The contractor should deliver the required units maximum after three months.



   16-2)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.



   16-3)Duty of contractor during one-year maintenance
16-3-1)The bidder should submit its schedule for the maintenance of equipment during
this period.
16-3-2)The contractor should do the removal operation of impairment by the way that
MTTR should not be more than 4 hours.
16-3-3)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.
16-3-4)The contractor should do all the periodic tests of systems, according to the
recommendations in the technical documents of system, then report the result.
16-3-5)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).



                                             165
   16-4)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 :

16-4-1)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:

16-4-1-1) The units should be repaired during maximum 20 days after handing over and
       taking to the factory.

16-4-1-2) 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.

16-4-2)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.

16-4-2-1)The repair cost of units should not be more than 30% of new unit price
       mentioned in the L.O.P of the contract.

16-4-3)Repair equipment

       The bidder shall submit its proposal list for the following detailed items.

16-4-3-1)The equipments by which, the repair department will be able to check the
impairment and repaired units to make sure of their correct operation.
16-4-3-2)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.
16-4-3-3)Technical documents, which according to them, experts will be able to find the
fault and test the units up to module level.



16-5)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



                                              166
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.




                                            167
Appendix




    168
App.1




         Table of Obligation and Responsibilities

                                Activity                                       Contractor   TIC


   1. Detailed specification of space, air conditioning & power
   requirements for the equipments in each station
                                                                                  ×

   2. Defining the specification of fuses required for each rack                  ×

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

   4. Specifying the location for installation of equipment in each station.                ×

   5. Providing space, air conditioning & power requirements in each
   station.
                                                                                            ×

   6. Providing DDF, OCDF, ODF, cable rack & structure                                      ×

   7. Providing electrical cables required between DDF & equipment                ×

   8. Providing required patch cords, pigtails & couplers.                        ×

   9.Providing end row PDB & related power cables                                           ×

   10. Providing test equipment & any tools needed during implementation          ×

   11. Factory inspection                                                         ×         ×

   12. Station by station packing of the equipments                               ×

   13. Shipment of the equipments to IRAN                                         ×

   14. Customs clearance                                                          ×


                                                        169
15. Transporting equipments to the stations.             ×

16. Station earth resistance measurement                 ×

17. Installation & commissioning                         ×

18. Test & acceptance with comprehensive reports         ×

19. Providing detailed installation drawings             ×

20. Specifying fiber optic cable parameters                  ×

21. Station entry permission                                 ×

22. One year trial maintenance                           ×

23. Providing test & acceptance procedure                ×

24.Providing comprehensive maintenance procedure         ×




                                                   170
App.2
                            PHYSICAL/LOGICAL TOPOLOGY




                                    REFER TO FILES:




        2007-12-05 4th-PlanPhysical Topology(App.2).pdf & 2007-12-05 4th-Plan Logical
                                     Topology(App.2).pdf




                                              171
App.3
                               Station Names
                                           Station         Network
   ID             Station   Abbriviation                                Province
                                            Type            Layer


    1    Abadeh                 ADH         REP            Non-ASON        Fars


    2    Ahar                   AHR          JN            Non-ASON   East-Azarbayjan


    3    Ahwaz SC1             AWZ1          SC             ASON        Khuzestan


    4    Ahwaz SC2             AWZ2          SC             ASON        Khuzestan


    5    Aligoodarz             ALG         REP            Non-ASON      Lorestan


    6    Amol                   AML         REP            Non-ASON    Mazandaran


    7    Anar                  ANAR         REP            Non-ASON      Kerman


    8    Arak                   ARK          PC             ASON         Markazi


    9    Ardakan                AKN         REP            Non-ASON        Yazd


    10   Ardebil                ABL          PC             ASON          Ardebil


    11   Ardestan              ARDS         REP            Non-ASON      Esfahan


    12   Asadabad-ES          ASD-ES        ADM            Non-ASON      Hamedan


    13   Ashkhaneh             AKNH         REP            Non-ASON   North-Khorasan


    14   Astara                 ASA         ADM            Non-ASON        Gilan


    15   AzadShahr              AZD         REP            Non-ASON      Golestan


    16   Babazeyd              BABZ         REP            Non-ASON      Lorestan


    17   Babol SC1             BBL1          SC             ASON       Mazandaran


    18   Babol SC2             BBL2          SC             ASON       Mazandaran


    19   Bafgh                  BFG         REP            Non-ASON        Yazd


    20   Baft                  BAFT         REP            Non-ASON      Kerman


    21   Baghat                 BGT         REP            Non-ASON     Hormozgan


    22   Bam                    BAM         REP            Non-ASON      Kerman




                                                     172
23   Bandar Abbas      BBS    PC           ASON          Hormozgan


24   Bandar Anzali     BDA    REP         Non-ASON          Gilan


25   Bandar Asaluyeh   ASU    ADM         Non-ASON        Bushehr


26   Bandar Bushehr    BBR    PC           ASON           Bushehr


27   Bandar Deylam     BLM    REP         Non-ASON        Bushehr


28   Bandar Genaveh    BGV    ADM          ASON           Bushehr


29   Bandar Kangan     BKG    JN          Non-ASON        Bushehr


30   Bandar Khamir     BKM    REP         Non-ASON       Hormozgan


31   Bandar Lengeh     BLH    PC           ASON          Hormozgan


32   Bardeskan         BAR    REP         Non-ASON    Khorasan Razavi


33   Bazargan          BZR    ADM          ASON       West-Azarbayjan


34   Behbahan          BBN    REP         Non-ASON       Khuzestan


35   Bijar             BIJ    REP         Non-ASON       Kordestan


36   Birizk            BIK    REP         Non-ASON       Hormozgan


37   Birjand           BJD    PC           ASON       South-Khorasan


38   Bojnurd           BND    PC           ASON        North-Khorasan


39   Borazjan          BJN    REP         Non-ASON        Bushehr


40   Borujen           BRJ    JN           ASON      Charmahal Bakhtiari


41   Bostan            BTN    REP         Non-ASON       Khuzestan


42   BostanAbad        BOT    REP         Non-ASON    East-Azarbayjan


43   Buchir            BCH    REP         Non-ASON       Hormozgan


44   Buin Zahra        BZHR   REP         Non-ASON        Ghazvin


45   Burujerd          BDJ    PC          Non-ASON        Lorestan


46   Chahbahar         CBR    PC           ASON      Sistan Baluchestan


47   Chahgaz           CHGZ   REP         Non-ASON    Khorasan Razavi



                                    173
48   Chalus         CLS    PC          Non-ASON      Mazandaran


49   Chupanan       CHPN   REP         Non-ASON        Esfahan


50   Damghan        DMGH   REP         Non-ASON        Semnan


51   Daran          DRN    REP         Non-ASON        Esfahan


52   Darpahn        DPN    REP         Non-ASON      Hormozgan


53   Dashte Abbas   DAA    REP         Non-ASON         Ilam


54   Davarzan       DVZN   REP         Non-ASON    Khorasan Razavi


                                                     Kohkiluye
55   Dehdasht       DDT    REP         Non-ASON
                                                    Boyerahmad


56   Dehloran       DHLN   REP         Non-ASON         Ilam


57   Delijan        DLJN   REP         Non-ASON        Markazi


58   Delvar         DLV    REP         Non-ASON        Bushehr


59   Deyhuk         DYHK   JN           ASON            Yazd


60   Dezful         DFL    PC          Non-ASON       Khuzestan


61   Divandarreh    DVDR   REP         Non-ASON       Kordestan


                                                     Kohkiluye
62   Dogonbadan     DGBN   REP         Non-ASON
                                                    Boyerahmad


63   Domzanoogeh    DMZG   JN           ASON          Lorestan


64   Esfahan SC1    ESF1   SC           ASON           Esfahan


65   Esfahan SC2    ESF2   SC           ASON           Esfahan


66   Esfarayen      ESRN   REP         Non-ASON    North-Khorasan


67   EshghAbad      ESBD   REP         Non-ASON         Yazd


68   Espakeh        EPK    REP         Non-ASON   Sistan Baluchestan


69   Espidan-RS     EDN    REP         Non-ASON        Esfahan


70   Evoghli        EVI    REP         Non-ASON   West-Azarbayjan


71   Fasa           FSA    REP         Non-ASON         Fars




                                 174
72   Ferdos          FDS    REP         Non-ASON    South-Khorasan


73   Firoozkuh       FZKH   REP         Non-ASON         Tehran


74   Garmsar         GRS    REP         Non-ASON        Semnan


75   Germi           GMI    REP         Non-ASON         Ardebil


76   Ghaen           GHN    REP         Non-ASON    South-Khorasan


77   Ghasre Shirin   GSRS   REP         Non-ASON      Kermanshah


78   Ghazvin         GZN    PC           ASON           Ghazvin


79   Ghiro Karzin    GRKZ   REP         Non-ASON          Fars


80   Ghom            GHM    PC           ASON            Ghom


81   Ghorveh         GHRV   REP         Non-ASON       Kordestan


82   Ghotb Abad      GHTB   REP         Non-ASON       Hormozgan


83   Ghuchan         GCN    REP         Non-ASON    Khorasan Razavi


84   Gilane Gharb    GLNG   REP         Non-ASON      Kermanshah


85   Golmoorty       GLMY   REP         Non-ASON   Sistan Baluchestan


86   Gonabad         GBD    REP         Non-ASON    Khorasan Razavi


87   Gonbade Kavus   GDKS   PC          Non-ASON        Golestan


88   Gorgan          GGN    PC           ASON           Golestan


89   Gushaki         GSHK   REP         Non-ASON   Charmahal Bakhtiari


90   Hamedan SC1     HDN1   SC           ASON           Hamedan


91   Hamedan SC2     HDN2   SC           ASON           Hamedan


92   Harang          HRNG   REP         Non-ASON       Hormozgan


93   Ilam            ILM    PC           ASON             Ilam


94   Iranshahr       ISR    PC           ASON      Sistan Baluchestan


95   Islamshahr      ILR    REP         Non-ASON         Tehran


96   Jahrom          JRM    REP         Non-ASON          Fars



                                  175
97    Jakigoor      JKGR   JN          Non-ASON   Sistan Baluchestan


98    Jandaqh       JDG    REP         Non-ASON        Esfahan


99    Jask          JASK   ADM          ASON         Hormozgan


100   Javan Rood    JVR    REP         Non-ASON      Kermanshah


101   Jiroft        JFT    REP         Non-ASON        Kerman


102   Jolfa         JLF    ADM         Non-ASON    East-Azarbayjan


103   Kahnuj        KNJ    JN           ASON           Kerman


104   Kahoorestan   KHRS   REP         Non-ASON      Hormozgan


105   Karaj         KRJ    PC           ASON           Tehran


106   Kashan        KSN    PC           ASON           Esfahan


107   Kazeroon      KZN    PC          Non-ASON         Fars


108   Kerman        KRN    PC           ASON           Kerman


109   Kermanshah    KRSH   PC           ASON         Kermanshah


110   Khalkhal      KHLL   REP         Non-ASON        Ardebil


111   Khash         KHSH   JN          Non-ASON   Sistan Baluchestan


112   Khonj         KOJ    REP         Non-ASON         Fars


113   khormooj      KHMJ   REP         Non-ASON        Bushehr


114   KhorramAbad   KBD    PC           ASON          Lorestan


115   Khoy          KHY    PC          Non-ASON   West-Azarbayjan


116   Lahijan       LJN    PC          Non-ASON         Gilan


117   Lar           LAR    REP         Non-ASON         Fars


118   Lirdaf        LDF    REP         Non-ASON      Hormozgan


119   Loshan        LSHN   REP         Non-ASON         Gilan


120   Mahabad       MBD    REP         Non-ASON   West-Azarbayjan


121   Maksookhteh   MKST   REP         Non-ASON   Sistan Baluchestan



                                 176
122   Malayer        MYR     REP         Non-ASON       Hamedan


123   Maragheh       MGH     REP         Non-ASON    East-Azarbayjan


124   Marand         MND     JN          Non-ASON    East-Azarbayjan


125   Marivan        MAR     REP         Non-ASON       Kordestan


126   Marvdasht      MDT     REP         Non-ASON         Fars


127   Mashhad SC1    MSD1    SC           ASON       Khorasan Razavi


128   Mashhad SC2    MSD2    SC           ASON       Khorasan Razavi


129   Mayamey        MYMY    REP         Non-ASON        Semnan


130   Mehran         MHN     ADM         Non-ASON         Ilam


131   Meymeh         MMH     REP         Non-ASON        Esfahan


132   Miandoab       MDB     JN          Non-ASON   West-Azarbayjan


133   Mianeh         MNH     PC           ASON       East-Azarbayjan


134   Minab          MNB     JN          Non-ASON      Hormozgan


135   Mirjaveh       MJV     ADM         Non-ASON   Sistan Baluchestan


136   Moalleman      MOLN    REP         Non-ASON        Semnan


137   Moghayeh       MGHY    REP         Non-ASON      Hormozgan


138   MoraveTappeh   MRTP    REP         Non-ASON       Golestan


139   Naeen          NAN     JN           ASON           Esfahan


140   Naybandan      NYBN    REP         Non-ASON         Yazd


141   Nehbandan      NBND    JN          Non-ASON    South-Khorasan


142   Neishabur      NBR     PC          Non-ASON    Khorasan Razavi


143   Neyriz         NYR     REP         Non-ASON         Fars


144   Nikshahr       NKSR    REP         Non-ASON   Sistan Baluchestan


145   Noor Abad-A    NRB-A   REP         Non-ASON         Fars


146   Noor Abad-B    NRB-B   REP         Non-ASON       Lorestan



                                   177
147   Nordooz          NDZ    ADM         Non-ASON    East-Azarbayjan


148   Nosrat Abad      NSBD   REP         Non-ASON   Sistan Baluchestan


149   Orumiyeh         ORM    PC           ASON      West-Azarbayjan


150   Oskanloo         OSKL   REP         Non-ASON    East-Azarbayjan


151   Piranshahr       PRNS   REP         Non-ASON   West-Azarbayjan


152   Pishin           PSHN   ADM         Non-ASON   Sistan Baluchestan


153   Poldasht         PLD    REP         Non-ASON   West-Azarbayjan


154   Rafsanjan        RFJ    PC           ASON           Kerman


155   Ramhormoz        RMH    REP         Non-ASON       Khuzestan


156   Rasht            RST    PC           ASON            Gilan


157   Ravar            RVR    JN           ASON           Kerman


158   Razan            RZN    REP         Non-ASON       Hamedan


159   Roudan           RDN    REP         Non-ASON      Hormozgan


160   Sabzevar         SZR    PC           ASON       Khorasan Razavi


161   Safashahr        SFSH   REP         Non-ASON         Fars


162   Saghez           SGZ    PC           ASON          Kordestan


163   Sagzi            SGZI   JN          Non-ASON        Esfahan


164   Salafchegan      SAG    JN          Non-ASON         Ghom


165   Salmas           SLMS   JN           ASON      West-Azarbayjan


166   Sanandaj         SNJ    PC           ASON          Kordestan


167   Sar Pole Zahab   SZB    REP         Non-ASON      Kermanshah


168   Sarakhs          SRKS   ADM         Non-ASON    Khorasan Razavi


169   Saravan          SVN    REP         Non-ASON   Sistan Baluchestan


170   Sarbandar        SBR    REP         Non-ASON       Khuzestan


171   Sarbaz           SBZ    REP         Non-ASON   Sistan Baluchestan



                                    178
172   Sarbisheh     SBS    REP         Non-ASON    South-Khorasan


173   Sardasht      SDST   REP         Non-ASON    West-Azarbayjan


174   Sari          SRI    PC           ASON         Mazandaran


175   Saveh         SVH    PC           ASON           Markazi


176   Semnan        SMN    PC           ASON           Semnan


177   SeroAb        SOB    REP         Non-ASON    South-Khorasan


178   ShahreBabak   SHBK   REP         Non-ASON        Kerman


179   ShahreKord    SKD    PC           ASON      Charmahal Bakhtiari


180   Shahreza      SHA    REP         Non-ASON        Esfahan


181   Shahrud       SRD    PC           ASON           Semnan


182   Shendasad     SNDS   ADM         Non-ASON    South-Khorasan


183   Shiraz SC1    SHZ1   SC           ASON             Fars


184   Shiraz SC2    SHZ2   SC           ASON             Fars


185   Shoorgaz      SHGZ   REP         Non-ASON        Kerman


186   Sirjan        SJN    JN           ASON           Kerman


187   S-Rain        RAIN   REP         Non-ASON        Kerman


188   Sufian        SFN    JN           ASON       East-Azarbayjan


189   S-Zabol       SZBL   JN          Non-ASON   Sistan Baluchestan


190   Tabas         TBS    REP         Non-ASON          Yazd


191   Tabriz SC1    TBZ1   SC           ASON       East-Azarbayjan


192   Tabriz SC2    TBZ2   SC           ASON       East-Azarbayjan


193   Takab         TKB    REP         Non-ASON    West-Azarbayjan


194   Takestan      TKN    REP         Non-ASON        Ghazvin


195   Taybad        TYBD   ADM         Non-ASON    Khorasan Razavi


196   Tehran SC1    TRN1   SC           ASON            Tehran



                                 179
197   Tehran SC2               TRN2   SC           ASON           Tehran


198   Torbate Heidarieh        THD    PC          Non-ASON    Khorasan Razavi


199   Torbate Jam              TJM    JN          Non-ASON    Khorasan Razavi


                                                                Kohkiluye
200   Yasuj                    YSJ    PC           ASON
                                                               Boyerahmad


201   Yazd                     YZD    PC           ASON            Yazd


202   Yazdan                   YDN    ADM         Non-ASON    South-Khorasan


203   Zabol                    ZBL    JN          Non-ASON   Sistan Baluchestan


204   Zahedan                  ZHN    PC           ASON      Sistan Baluchestan


205   Zanjan                   ZJN    PC           ASON           Zanjan


206   ZarAbad                  ZRBD   REP         Non-ASON   Sistan Baluchestan


207   Zarand                   ZRND   REP         Non-ASON        Kerman




          Station Type         QTY.


                    ASON        62
                                      207
                Non-ASON       145


                         REP   111


                          SC    16


                          PC    43    207


                          JN    22


                     ADM        15




                                            180
App.4



                            Traffic Matrix



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




                                            181
App.5


        Network Line Capacity Estimation



        REFER TO FILE:2007-12-04 4th-Plan Cable & Logical ASON Links (App.5).xls




                                            182
App.6


        Equipment Modification Procedure
         1. Response to Engineering Deficiencies


         1.1 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.



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




         2. Conditions of Supplier Changes and Modifications


         2.1 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,
             thirty (30) days notice shall be required except for those cases where an extremely
             unsatisfactory condition requires immediate action on the part of the supplier.



                                                   183
2.2 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.




                                         184
2.3 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.
2.4 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.




2.5 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


                                          185
       -   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.




                                             186
App.7




        ADDITIONAL               PALANNING CONSIDERATIONS




        REFER TO FILE:2007-12-04 4th-Plan Additional Planning Considerations (App.7).doc




                                               187
App.8




        EVALUATION          PARAMETERS




           REFER TO FILE: evaluechart860912




                           188
App.9


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




                                                        189

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:13
posted:1/7/2012
language:English
pages:198
jianghongl jianghongl http://
About