SE NS-066 - ptclNOCInventoryMgt... · SE NS-066 SYSTEM ENGINEERING WING ... configuration, testing,...

PAKISTAN TELECOMMUNICATION COMPANY LIMITED

SE NS-066 SYSTEM ENGINEERING WING OF PTCL

May 25, 2010

SERIES NS: NEW TECHNOLOGIES, VALUE ADDED SERVICES & DATA NETWORKS Specifications of New Technologies, VAS, Data Network and Allied Systems

Network Engineering Resource Information Management (NERIM) Tool for PTCL NOC

PTCL Specification NS-066

NS-066

May 2010 NERIM Tool for PTCL NoC of 25

Change History

The table below lists the significant, product-impacting changes to the document.

Editorial changes and cosmetic changes are not listed.

Issue Date Revised By Description of Change Section or

table

1 25-05-2010 Nadeem Bukhari, Initial Version

NS-066


TABLE OF C O N T E N T S

1 INTRODUCTION 4

2 GENERAL REQUIREMENTS 4

3 DELIVERABLES 6

4 PRODUCT REQUIREMENTS 8 5 ENVIRONMENTAL CONDITIONS 18

6 POWER SUPPLY REQUIREMENTS 19

7 PROTECTION AND EARTHING 19

8 RELIABILITY AND AVAILABILITY REQUIREMENT 20

9 WARRANTY PERIOD 20

10 MAINTENANCE SUPPORT AND SPARES 20

11 SYSTEM BACKUP 21

12 QUALITY ASSURANCE 21

13 ACCEPTANCE TESTING 21

14 SUPPLY RECORD 23

15 DOCUMENTATION 23

16 LOCAL TRAINING 23

17 STATEMENT OF COMPLIANCE 24

NS-066


1. INTRODUCTION

1.1 Pakistan Telecommunications Company Limited (PTCL) is the incumbent and the

largest ICT services provider in Pakistan with its huge telecommunication

network pertaining to Switching, Transmission, WLL and IT throughout Pakistan.

With the rapid growth of information technology, efficient and timely

communication and saving overhead expenditures have become the key issues for

an organization to improve its competitiveness.

1.2 PTCL desires to procure a Network Engineering Resource Information

Management (NERIM) tool i.e. inventory tool for logical and physical entities

of its telecom network on multi-vendor multi-technology PTCL Network

Operations Center (NOC) platform.

1.3 The purpose of these specifications is to provide the guidelines to the interested

bidders/ vendors for supply of such equipment. These specifications cover the

minimum standards and requirements for the Network Engineering Resource

Information Management (NERIM) tool for PTCL NOC platform.

2 GENERAL REQUIREMENTS

2.1 The vendor shall be responsible to survey, Install, test, integrate & commission

and put into service, the system/solution at Islamabad (Main NoC) & Karachi

(DR site) in accordance with the standards and Specifications as issued by PTCL.

2.2 The offered solution shall cover modeling of the PTCL‟s entire network (Core,

Radio, Transmission, IP and service network), end to end visualization of the

network in different granularity, network planning, development design, and

configuration, network resource management, service modeling, service

configuration and activation of the network being managed by the PTCL Network

Operations Center (NOC).

2.3 Reconciliation functionality shall also be required to ensure proper reflection of

the real network by periodically comparing data of the inventory with information

of different network elements through different element management systems.

2.4 The Vendor shall be fully responsible for the supply, delivery, installation,

integration, configuration, testing, and commissioning of the whole system

(including hardware, Software, terminals, RTUs, licenses, accessories etc.) to

meet the PTCL requirement.

2.5 The offered solution shall include the installation, provisioning of all materials,

services including all local costs/taxes as well. Any item required to complete the

whole system for commissioning, but omitted or ignored due to any reason, but is

NS-066


necessary to complete the project shall be the responsibility of the contractor to

provide at his own cost.

2.6 The offered solution shall also provide planners to model future planned network

based on standard engineering principles.

2.7 The tool shall generate different types of report on network resource.

2.8 The vendor shall Install/deploy the newest available version of the products with

latest new patches or updates at the time of deployment.

2.9 The vendor will provide hardware/software, including Servers, Storage solution,

UPS, clients, alarms monitoring solution and Rack with accessories as per PTCL

specifications.

2.10 The vendor shall also be responsible to access and calculate the bandwidth impact

on PTCL network due to deployment of these services.

2.11 The vendor shall also be responsible to provide complete documentation and any

required installation and management software/licenses for all hardware/software.

2.12 The Vendor shall be responsible for equipment integration with existing NOC

setup and with the EMSs as required.

2.13 The vendor shall undertake to resolve compatibility issues if any between the

offered solution & existing network/infrastructure. The vendor shall be fully

responsible to resolve all compatibility issues for the deployment and functioning

of the desired service/solution.

2.14 The vendor shall ensure proper and un-interruptive functioning of the existing

system, while integrating the new entities in installation / integration process.

2.15 The vendor shall offer High Availability option for the offered solution with

clustering solution for hardware & software.

2.16 The vendor shall ensure the scalability of the offered solution with modular

expansion. The offered solution shall be scalable and modular to accommodate

future expansion.

2.17 The vendor shall not quote “End of sale / End of Life products, services etc. The

vendor shall also provide the life cycle and product roadmap of offered network

components.

2.18 The Vendor shall also responsible to provide any related equipment such as

connecting cables, power supplies, accessories required for rack mounting or for

NS-066


any activities required for project execution etc. which may be required for proper

functioning of servers, Storage solution and UPS.

2.19 The offered solution shall be completed in all aspects and the vendor shall be

responsible to provide any item (without extra cost) not explicitly mentioned in

the BOQ, but required for full/efficient functioning of the offered solution.

2.20 PTCL reserves the right to make changes in the specification at any time without

any notice.

2.21 PTCL reserves the right to add (on the quoted price) or drop any offered

equipment in the order placed on the vendor.

2.22 PTCL cannot guarantee that any of the requirements, standards, regulations, and

conditions of this specification are not covered or protected by copyright or patent

of a third party.

3 DELIVERABLES

3.1 Basic Functional Areas

The offered solution shall realize the following functions:

a. Physical inventory management

b. Logical inventory management

c. Network Modeling

d. Network Visualization

e. Network Change Management

f. Workflow management

g. Define network and service configurations

h. Order and schedule future resources to meet expected demands

i. Provide a federated database for other operational support systems

j. Work Order Management

3.2 The vendor shall be adequately and effectively integrate the offered solution with

desired domains (through EMS, NE), other inventory repositories and existing

NOC OSS infrastructure.

NS-066


3.3 The offered solution shall be scalable enough, so that upcoming networks

regarding IMS, GPON and NGN could also be integrated.

3.4 The vendor shall integrate the offered solution with HP Open View products

currently deployed in PTCL NOC.

3.5 The offered solution provided shall be able to integrate with any EMS‟ database

and should be independent of the version deployed.

3.6 The vendor shall also provide connectivity plan for interconnection of

EMSs/Databases, compatible with the NOC‟s existing TCP/IP Data Network,

along with the Inventory product.

3.7 Elementary Architecture

The vendor shall offer the product with following major components

a. Inventory Engine and Repository

b. Workflow & Work Order Manager

c. Network Change Manager

d. NBI-Pollers/Adapters for Inventory Data Collection (for

Discovery/Manual Data Collection)

e. Activation/Provisioning Engine (Optional)

3.8 Business Expectations

The vendor „s offered solution shall also meet following business requirements

a. Capex Optimization

b. Efficiency

c. Outage Reduction

d. Compliance

3.9 Domains to be integrated

The vendor shall integrate following domains with its offer product

a. WLL (voice and data) Network

b. End-to-End Transport, IP/Data Services Network (Including NGN

Network)

c. MMBB (DSLAMs/BRASs/IPTV)

d. OFAN

e. Up coming NGN, IMS & GPON network

NS-066


3.10 The vendor shall provide a web-based management platform of all the products

(Servers/Adapters/Network Devices) to be deployed.

3.11 The vendor shall provide a Disaster Recovery solution, which would act as a

standby inventory platform.

3.12 The vendor shall also provide Process definition and work-flow set up for the

inventory management process in accordance with the setup on the EMS side.

3.13 The short listed vendor(s) shall arrange visit of PTCL engineers to one of their

biggest reference site, where this offered solution is functional/operational. The

site selected for PoC shall have the same solution deployed in their setup. This

offered solution should be integrated with HP Open View (TeMIP) Platform.

3.14 The Vendor shall be responsible to train 04 PTCL resources regarding O&M

perspectives as well as “Advanced Training” in collaboration with PTCL training

department, for the services and solution as per attached BoQ.

4. PRODUCT REQUIREMENTS

4.1 The desired Inventory shall enable PTCL to develop network configurations for

telecom equipment (base stations, multiplexers, switches and transmission nodes)

and circuit (physical and virtual) layout records such as virtual circuits, VPNs,

cross connects, leased circuits, etc. using standard templates for the assignment of

resources.

4.2 The tool shall be able to

a. Manage current inventories of network resources and capacity, down to a

rack, shelf, slot, port, virtual channel/circuits and tributaries level

b. Track Order and maintain schedule for future resources to meet expected

demands

c. Support identification of network outages, its service impact through

seamless integration with existing NOC OSS platform

d. Support Combined Discovery and Activation capabilities

4.3 The offered solution shall also support

a. A complete, multi-vendor, multi-technology data discovery

b. Automated, manual or assisted inventory reconciliation

c. Complex service activation spanning multiple Network elements and

EMSs. (Optional)

4.4 The offered solution shall support PTCL operations across the board:

NS-066


a. Network Engineering – system design, capacity engineering, facilities

planning and transmission design.

b. Operations – field support, installation, network management

c. Management – engineering reports, network reports, work order

management, accounting/asset control and business planning,

d. Customer Care – customer order handling, service availability and

workflow integration (Optional)

e. IT management - system and software management. (Optional)

4.5 The offered solution shall have a state-of-the-art and flexible architecture and be

able to fulfill service providers requirements for a network, service and IT

resource OSS solution. The integral components of the offered solution should

be:

a. Flexible Resource and Service Modelling: NERIM Object modelling

should allow fast modelling of new resources and services without

customization effort.

b. Dedicated View on Services and Network Resources: The tool should

have viewing and access rights to the information that is required.

c. Accurate Data: NERIM tool combined with Discovery tool should have

the capability to provide the possibility to load changes in the network into

the network, service and IT resource inventory database and reconcile the

data.

d. Common View on all Data: NERIM tool should allow easy access out to

other inventory information, stored in existing systems. It should allow to

get a common view on the network and all services, no matter where this

data is stored.

e. Easy Integration with other OSS and BSS Components: NERIM

should provide an open API interface along with J2EE architecture to

allow easy integration with other OSS / BSS components.

f. Centralized or Decentralized Architecture: NERIM should allow both

forms of implementations, dependent upon the architecture and user

requirements within the network and user environments.

g. Proven and Mature Architecture: At least five years proven availability

on a 3-tier, J2EE architecture helping to ensure high performance,

reliability and flexibility.

4.6 The offered product shall have Self Management of the products as an integral

part of the system.

4.7 The offered product shall be able to backup data automatically on regular basis

and should be able to restore.

NS-066


4.8 All the dimensioning (Network Bandwidth/Data rate requirements and Data

Center requirements) shall be provided by the vendor.

4.9 The offered server hardware shall be scalable to accommodate all management

functions.

4.10 Latest version of Hardware shall be offered along with all the new patches that

have been released till the date of installation.

4.11 The vendor shall ensure that all the devices deployed against the project are

SNMP enabled and can be managed through a user friendly web interface.

4.12 The vendor shall offer High Availability option for the offered solution with

respect to hardware & software. Clustering solution shall be deployed for the

Application and DB servers.

4.13 The vendor shall providing all licensing and installation details.

4.14 The vendor shall be responsible, in accordance with PTCL requirements for Inter-

working with existing GIS and SAP solution. (Optional)

4.15 The Bidder shall be responsible, in accordance with PTCL requirements for Inter-

working of the supplied system with PTCL B&CC system for billing and service

provisioning

4.16 The offered solution must maintain a comprehensive, extensible, meta-data driven

model of all logical inventory, for example: circuits, numbering schemes, and

network elements.

4.17 The offered system shall be able to support all transmission media and elements

e.g. microwave, fiber optic, satellite, leased-line, shared bandwidth, DDF, direct

cable, DXX, etc.

4.18 The offered solution must support New technologies - as networks grow and

develop there is a need to provide the flexibility and tools to implement new

technologies and services within the same environment.

4.19 The offered solution must not be restricted in its support of different network

technology types. Therefore it must be capable of easy configuration to model

new and emerging technologies.

4.20 The offered solution must provide a single, coherent and integrated database for

storing logical and physical inventory and resource data and the services riding

these resources

NS-066


4.21 The offered solution must be capable of providing an integrated data model across

multiple technologies.

4.22 The offered system must maintain a comprehensive, extensible, meta-data driven

model of physical and logical network inventory including passive and active

devices.

4.23 The offered solution must support Equipment configuration information -

definitions of equipment (racks, shelves, slots, cards and ports), connections

(fiber, leased lines, etc), and the hierarchies within these types of equipment and

connections

4.24 The offered system must be capable of modeling new/emerging technologies.

How the product addresses the introduction of new/emerging technologies.

4.25 The offered solution shall support a flexible yet configurable object model.

4.26 The offered Inventory solution should support a base object model including Site

(location), Equipment (container, shelf, slot, card, port etc), Cable (cable, pair,

strand etc), Segment, Path, Network and Customer and a base set of attributes for

each object.

4.27 The offered Inventory solution should provide a highly flexible and configurable

object model that includes capabilities to model today‟s technologies and services

as well as supporting the ability to manage new and emerging technologies.

4.28 The offered solution shall have the functional ability to perform Resource

Inventory Entities, Specifications and Associations.

4.29 The offered solution shall be able to create and show the relationship: Service &

Network Nodes Supporting the Service.

4.30 The offered solution shall support the definition of Network parameters (cell

parameters, RF parameters etc).

4.31 The offered solution shall support the definition of Switching functions -

definition of switching function groups, software functions etc in the MSC and

associated switching network e.g. X25, C7, Tariff parameters etc.

4.32 The offered solution must support Service Inventory function to manage service

instances, modeling and its relations with supplying physical and logical

resources.

4.33 Locations (Sites)

NS-066


4.33.1 The offered solution must support Location information - where network

elements (latitude and longitude) are located in the network topology.

4.33.2 The offered solution must identify each resource and provide details on its

geographical location (region, site, room etc).

4.33.3 The offered system must be able to record location coordinate and

administrative address (PO BOX code, city, street, number, etc) or numeric

(coded).

4.33.4 The offered solution must be capable of modeling definable location

hierarchies. For example, a hierarchy of country, region, city, site, and room.

4.33.5 The offered system must be able to represent geographical locations using a

hierarchical / containership relationship, where a "Parent" geographical

location contains "child" geographic locations, which in turn can contain other

"Child" geographic locations until the lowest level contains the actual network

site locations (e.g. continent, country, region, market, city, site / building,

floor, room, etc).

4.33.6 The offered system must provide geo-spatial information on the device

location.

4.33.7 The offered solution shall be able to capture Co-Location management

including floor space management (GUI based, site plan, floor plan, logistic,

facilities, utilities).

4.33.8 The offered solution must be able to track and manage floor and rack space,

model power consumption as well as HVAC parameters.

4.34 Physical Equipment

4.34.1 The offered system must be able to represent identification of physical

equipment at a location.

4.34.2 The offered solution must be able to model devices including bay, rack, shelf,

slot, card, port, and cross connect.

4.34.3 The offered Inventory solution should support for physical network element

management through the Equpment object which provides a hierarchical

(container, shelf, slot, card port) model across multi-technology, multi-vendor

networks.

4.34.4 Equipment can be either of two types: containers or shelves. Containers are

equipment elements that contain other equipment, such as bays and cabinets.

Shelves are pieces of equipment that house slots where cards are placed. Slots

NS-066


can also be configured to have daughter and granddaughter slots. Cards may

have Ports and Child-Cards and combinations of both ports and cards.

a) Which ports are used?

b) Number of used ports.

c) Number of free ports.

4.34.5 The Equipment Object provides fields to manage location information, within

its parent “site” location.

4.34.6 The offered solution must support inventory for media, equipment, cards,

rack, module, port, circuit, etc.

4.34.7 The offered solution must provide the ability to easily add new equipment

and/or card types through configuration of relevant meta-data.

4.34.8 The offered solution must be able to model manufacturer specific features

including simple port-only devices and complex devices containing multiple

rack, shelf, and slot configuration.

4.34.9 The offered system must be able to support equipment models configuration

rules, such as card dependencies, including:

a) “Required cards Z1, Z2,…Zn to be installed to allow installation of

card Z”

b) “Incompatible cards Z1, Z2 … Zn not to be installed to allows

installation of card Z”

c) Validation Tables


rules, such as card dependencies.


rules, such as card dependencies, including: “Available slots for installation of

card Z”.

4.34.12 The offered solution must support configuration information: ID, serial

number, dimensions (for hardware), contact information, provisioning status,

etc.

4.34.13 The offered solution shall provide support for asset management.

4.34.14 The offered solution system must provide/methods for Device

creation/deletion/removal.

4.34.15 The offered solution shall be able to support planning installation of a new

device.

NS-066


4.34.16 The offered solution shall be able to support planning the installation of a new

card in the installed device.

4.34.17 The offered solution must support manually adding the card to the slot and

defining the appropriate port configuration.

4.34.18 The offered solution must support adding the card using a template, again the

card definition will be determine by the over-riding equipment definition.

4.34.19 The offered solution must support Status Management capabilities after

creation or modification.

4.34.20 The offered solution shall be able to support Add-Drop Mux details.

4.35 Physical Connectivity (Cable and Segment)

4.35.1 The offered solution must provide the ability to model different physical media.

This must include but not be restricted to copper, fiber, microwave, and radio.

4.35.2 The offered system shall be able to support Fiber Optic physical network.

4.35.3 The offered solution must be able to represent all physical connectivity and media

relating to network technologies (fiber, copper, leased line, Ethernet, etc)

4.35.4 Cable

a) The offered solution shall be able to provide cable utilization and details (core

number and status) report.

b) The offered solution must tell how users can specify how the cables are

composed, whether they are copper, fiber, optical etc.

c) Cable identities can be automatically generated based on operator procedures and

naming conventions.

d) Users have the ability to create cables from pre-existing templates.

e) Users can specify unlimited levels of containment to allow the modeling of cables

within cables.

f) Cable pairs/strands can be terminated on ports or other cable pairs/strands.

g) Filtering on cables can be performed to allow a user to find connections that meet

specific criteria.

NS-066


h) The administrator can define and configure the values for the Binder Color,

Pair/Strand Color and Pair/Strand Bandwidth:

i) Cable pairs to be stubbed and reserved for future use.

ii) Fields for planned installation, test, and in-service dates are available

providing valuable data for project management and tracking of

cables.

iii) Reports can be generated on the cable capacity, utilization and

terminations

i) The offered solution shall be capable to highlight free capacity represented by

cables, which are either connected just at one end, or are not connected at all:

i) How the cables are composed, whether they are copper, fiber, optical

etc.

ii) Users can specify unlimited levels of containment to allow the

modeling of cables within cables.

iii) Cable pairs/strands can be terminated on ports or other cable

pairs/strands.

iv) Filtering on cables can be performed to allow a user to find

connections that meet specific criteria.

v) Cable pairs to be stubbed and reserved for future use.

4.35.5 Segment

a) The offered system must provide the ability to model all types of leased lines.

Following information shall be at least available:

i) Renewal Date

ii) Last Renewal Date

iii) Renewal Term

iv) Billing Code

v) Vendor.

b) It shall be possible to create new circuit segments by means of copying existing

segments.

c) Filtering on segments can be performed to allow a user to find connections that

meet specific criteria.

NS-066


d) Fields for planned installation, test, and in-service dates are available, providing

valuable data for project management and vendor tracking in the segment.

e) Report on various aspects of leased-line management and costing shall be

available.

f) The offered solution shall support networks from Other Leased Operators., i.e. a

sub-network where only the edges and the available capacity are known up to the

point of interconnect (PoI).

4.36 Logical Connectivity (Path & Network)

4.36.1 The offered solution must support end-to-end bandwidth information -

management of bandwidth definitions providing the ability to view the

network connectivity from end to end capacity and utilization planning with

the ability to set thresholds at all levels.

4.36.2 The offered system shall provide the ability to display the relationship

between logical circuits and specific customer services. For example allowing

a user to identify which circuits or links are related to which services.

4.36.3 Users can create, manage and maintain all path and service types through the

administration functionality.

4.36.4 Path Identities can be automatically generated based on operator procedures

and naming conventions.

4.36.5 Users shall have the ability to create paths from pre-existing templates.

4.36.6 Fields for planned installation, test, and in-service dates shall be available,

providing valuable data for project management and tracking of the paths or

services.

4.36.7 There shall be unlimited levels of containment to allow the modeling of path

or service hierarchies (64K, E1, E3, STM-1, STM-16, STM-64 etc).

4.36.8 The offered solution shall have the ability to define relationship types such as

primary, secondary, backup etc.

4.36.9 Filtering on paths can be performed to allow a user to find connections that

meet specific criteria.

4.36.10 Path Bandwidth management shall provide the following functions:

a) Discrete bandwidth settings on path channels

NS-066


b) Path channel templates

c) Over subscription control

d) Merging and splitting of channels

4.36.11 Trunk Group Management and ATM bandwidth management shall be

intrinsically contained in the Path object business logic.

4.36.12 Users shall be able to create a new path revision to represent a future design

for a connections or services.

4.36.13 The offered solution shall have the ability to represent layer 3 services (e.g.

VPN, MPLS, ATM cloud or other “network” abstractions).

4.36.14 The offered solution shall have the ability to represent the Network Object as

a separate node in the GUI for the purposes of visualization and navigation.

4.36.15 The offered solution shall have the ability to define capacity, consumption

capabilities and behavior of “networks”.

4.36.16 The offered solution shall have the ability to leverage the basic functions of

bandwidth management that are inherent today within the core object model.

4.36.17 The offered solution shall have the ability to view and navigate the network

and its underlying definitions graphically.

4.36.18 The offered solution must support “end-to-end” connectivity view irrespective

of technology deployed:

a) PSTN Voice Circuits

b) E1 circuit switch connects

c) SDH connections and hierarchies

d) ATM PVCs

e) Frame Relay PVCs and Virtual Circuits

f) IP VPN Connections

g) Customer circuits/services.

4.36.19 The offered solution must support logical hierarchies and channel mapping.

4.36.20 The offered solution shall be able to display bearers list, details and utilization

(high utilization infra to be inputs to new plan strategies).

4.36.21 The offered solution must support future consumption of planned capacity for

planned connections and services.

4.36.22 The offered solution shall support Signaling (SS7) - management of the

signaling connections, link-sets and routes across the network.

NS-066


4.36.23 The offered solution shall support routing/provisioning (i.e. the allocation of

resources to a customer).

4.36.24 The offered solution must provide end-to-end and convergent view of the

network, that covers access, switch, IP and transport technologies (used by

mobile operators), both at the physical and the logical levels, including, but

not limited to ISDN, IP, ATM, SDH, PDH, microwave.

4.36.25 The offered solution shall have the ability to provide End to end and

hierarchical views of the network resources (physical, logical and services)

irrespective of the underlying transport or logical technologies.

4.36.26 The offered solution must provide a wide range of circuit topologies.

4.36.27 The offered system shall support but not limited to following network

structures:

Point to Point

Point to Multipoint

Structures in Ring

Structures in Tree

Structures in Chain

Structures in Star.

4.36.28 The offered system shall support network hierarchy: Backbone, National

network, Regional network, Local network.

4.36.29 The offered system shall be able to display path list, details and utilization.

4.36.30 The offered solution shall provide details of path list details, utilization rates

and information about associated objects through the User Client or in the

form of Reports.

5 ENVIRONMENTAL CONDITIONS

5.1. Continuous Performance

5.1.1. The equipment shall work continuously according to the Technical Specifications,

in the following environmental conditions under shelter without deterioration in

the performance: -

5.1.1.1. Ambient Temperature: 0°C to 55°C

5.1.1.2. Relative Humidity: 0% to 100% (non-condensing)

5.1.2. The offered system shall provide necessary air circulation inside itself.

NS-066


5.1.3. The room noise level of the offered equipment shall not exceed 60 dBA. The

bidder is required to specify the relevant levels.

6 POWER SUPPLY REQUIREMENTS

6.1. The terminals offered shall operate on 220 VAC; 50 to 60 Hz.

6.2. Optional DC power supply -48 VDC shall be available. In case of different DC

supply, the vendor shall provide suitable converters for -48VDC.

6.3. The guaranteed performance of the equipment must be maintained for the

following variations of power supply (as measured at the power input to each

rack):

6.3.1. Voltage variation: ± 20%

6.3.2. AC ripple: Up to 0.5V peak to peak

6.4. The bidder shall state critical parameters, defining the level of performance

degradation that may be expected.

6.5. The bidder shall describe the total power consumption per sub-rack, fully loaded.

7 PROTECTION AND EARTHING

7.1. The system supplied shall be protected from damage caused by accidental

reversal of power supply polarity.

7.2. The offered equipment supplied shall, without permanent damage or degradation

of performance, withstand surges applied at power input terminals and all

interfaces in accordance with ITU-T and FCC standards. The bidder shall specify

the standards that their offered equipment complied to.

7.3. The equipment power earths must be connected to the node earth terminal.

7.4. The bidder shall follow the earthing procedure & resistance as per latest version

of PTCL guidelines GL-02.

8 RELIABILITY AND AVAILABILITY REQUIREMENT

8.1. The bidder shall submit Mean Time Between Failure (MTBF) figures for the

offered system.

8.2. The method of derivation of these figures shall be explained and it shall be

highlighted whether the derivation is based on past usage or mathematical model

only.

NS-066


8.3. The bidder shall submit a detailed calculation of availability for the proposed

system.

9 WARRANTY PERIOD

9.1. The bidder will be responsible to replace the faulty units or faulty parts during the

warranty period free of cost.

9.2. The bidder shall provide PTCL operation and maintenance personnel with

technical support in the event of a problem that requires immediate attention.

10 MAINTENANCE SUPPORT AND SPARES

10.1. The bidder shall prescribe the maintenance philosophy and operating procedures

of the offered system; in particular they shall describe in detail the following:

10.1.1. Procedure of routine maintenance and administration.

10.1.2. Fault location, repair and reconfiguration.

10.1.3. Control of the system under abnormal condition.

10.1.4. System tests and performance measurements.

10.1.5. The bidder shall recommend the type of routine / preventive maintenance

tests and their duration, giving the test set ups and their procedures.

10.2. The bidder should have local competence in Pakistan to support PTCL during and

after implementation.

10.3. The bidder shall clearly indicate the point of presence in Pakistan for maintenance

purpose and will mention the cost of repair for each level of maintenance for

hardware and software separately.

10.4. The bidder shall specify briefly first, second and third line of maintenance support

along with down time.

10.5. The bidder shall provide a cost and terms and conditions for maintenance contract

for one year after the expiry of warranty period. PTCL at its discretion may enter

into a maintenance contract that may be extendible with mutual agreement on

year-to-year basis.

10.6. The bidder shall maintain sufficient quantity of spares at the bidder's point of

presence in Pakistan during warranty / maintenance period.

10.7. Maintenance charges for a period of 5 years shall be quoted separately.

10.8. The bidder must recommend and list full details of spare parts required for the

maintenance of the system for a period of five years.

NS-066


10.9. The bidder must provide spares needed for replacement of faulty modules during

the warranty period at its own cost. These spares must be handed over to PTCL to

be used during warranty period.

10.10. 5% of each kind of modules supplied must be offered as spares, which must be

included in evaluation.

10.11. The bidder must guarantee supply of spares for 10 years.

10.12. Upgraded version of software supplied must be provided, free of cost, for 5 years

by the bidder.

11 SYSTEM BACKUP

The bidder shall provide a comprehensive backup plan and strategy to ensure that

all the critical system configurations are backed-up according to a planned

schedule.

12 QUALITY ASSURANCE

12.1. The bidder will ensure that equipment supplied shall be the latest model available

in the market.

12.2. The bidder shall also provide life cycle of the offered network components.

12.3. The bidder will ensure that no part of the equipment supplied is refurbished.

13 ACCEPTANCE TESTING

13.1. The bidder shall arrange and specify test equipments/instruments along with the

set up arrangements and configuration details to conduct installation and

acceptance testing. The bidder shall also furnish technical details of the required

test equipments/instruments.

13.2. All the test instruments required for such testing shall be the responsibility of the

bidder.

13.3. Vendor should follow the latest version of PTCL guidelines GL-05. The

acceptance procedure shall consist of the following three parts:

13.3.1. Checking of inventory of items against purchase order

13.3.2. Physical installation acceptance

13.3.3. Functional tests under specified conditions

13.4. Inventory

All hardware in the offered system shall be physically counted and recorded, and

be checked against the purchase order, including literature and detached items like

NS-066


test equipment, peripherals etc.

13.5. Physical Installation

13.5.1. All wiring, fixtures, civil works (if required) etc. Shall be checked for

acceptance according to sound engineering practices.

13.5.2. The hardware shall be checked for scratches or physical damage. Except

for minor items, the shortcomings shall be made good before functional

test is started.

13.6. Functional Testing

13.6.1. Provisional Acceptance Testing (PAT)

13.6.1.1. After installation, the equipment shall be subjected to acceptance

testing in accordance with the PAT document.

13.6.1.2. The bidder shall submit PAT document prepared by the vendor

(manufacturer), covering all the aspects of the Technical

Specifications well in advance. The plan shall suggest tests to

respond to individual items of the Technical Specifications in such

a way that no item is left untested in the end.

13.6.1.3. PTCL shall approve the test procedures and may add additional

tests to those offered by the bidder as deemed necessary to prove

the satisfactory performance of the system.

13.6.1.4. Acceptance tests shall be carried out in the specified environmental

conditions to establish that the system meets the Technical

Specifications.

13.7. In addition to other tests, the supplier shall arrange the testing of offered system

at full load to demonstrate the maximum capacity of the system.

14 SUPPLY RECORD

14.1. The offered system must be field-proven, employing sound engineering practices,

state of the art technology and capable of operating continuously with a very high

degree of reliability.

14.2. The Bidder must provide record of supply to show past experience of the

"supplier". The record of supply must include information on the count year of

installation, the type of system supplied, and capacity of the system application

detailing:

14.2.1. Date of supply / commissioning

14.2.2. Names and address of the operator: A brief introduction of the operator

must be presented along with its total subscriber lines. Official web site of

the operator must be provided

14.2.3. Equipment details or type of system

14.2.4. System Capacity

NS-066


15 DOCUMENTATION

The bidder shall submit two (2) sets of following documents mentioned below, in

English Language, at the time of supply of equipment.

15.1. System Documents

15.1.1. System Description Manual

15.1.2. System Installation / Setup Manual

15.1.3. Operation & Maintenance Manual

15.1.4. System Administration Manual

15.1.5. Emergency Procedures /Error Handling Manual

15.1.6. System Recovery / Restart Manual

15.1.7. Complete data sheets and part lists must be included

15.1.8. The bidder may provide any other additional information, if necessary.

15.2. Software Documentation

15.2.1. The Bidder shall supply all software documents necessary for operation,

maintenance, modification and upgrading of the software of the system.

15.2.2. The documentation including test and comments must be in English.

15.2.3. All the software documents shall be preferably in CD-ROM.

15.2.4. The bidder shall also supply licensed software on CD‟s along with

documentation describing detail installation and configuration procedure.

16 LOCAL TRAINING

16.1. The Vendor shall provide local trainings & support for pre-sales & solution

design to PTCL.

16.2. The bidder must arrange training on installation, testing and operation of the

offered systems at supplier premises in Pakistan. The number of trainees for each

type of equipment has been specified in the respective Bill of Quantity.

16.3. Installation/configuration/testing of complete system must be demonstrated by the

supplier during training.

16.4. The bidder shall provide hard and soft copies of Training manuals.

17 STATEMENT OF COMPLIANCE

17.1. The Bidder shall furnish a clause-by-clause compliance for each and every clause

of technical specification separately both in hard copy and softcopy formats on

separate CD. As far as possible, the bidder shall provide the detailed technical

description for each compliance statement. The page number shall be indicated

whenever an attached document is referred. More over the softcopy of the

compliance statement shall contain the hyperlinks to the reference documents.

17.1.1. "FULLY COMPLIANT", if the systems and functions offered fully meets

NS-066


the tender requirement without any ifs or buts.

17.1.2. "PARTIALLY COMPLIANT", if the systems and functions offered meet

the tender requirement partially, the bidder shall state the reason why the

offer is partially compliant. However, if the bidder is able to fulfill the

specified requirement later, the time schedule for this shall be stated. In

such cases, the bidder shall clearly mention the extent to which other

requirements or specifications are affected.

17.1.3. "NON COMPLIANT", if systems and functions cannot meet the

requirements, the bidder shall also state the reasons for it.

17.1.4. In case of absence or unclear statements of compliance for any specified

requirement, PTCL will interpret that particular requirement as being

"NON COMPLIANT".

17.2. Bidder shall submit clause-by-clause technical compliance according to the

format as under with the bid.

Clause

No. Complied

Non

Complied

Partially

Complied

Deviation/Details

in case of

Partially

Compliance

Hyperlinks

to the

referenced

documents

(of soft

copy).

17.3. The bidder shall include in its proposal the detailed technical information,

drawings and functional descriptions of the offered equipment to provide the

compliance to the technical requirements.

17.4. The documents submitted with the bid shall be in appropriate format and well

organized. A table of contents must be attached in the beginning of the document.

17.5. Responses from the bidders shall be a valid part of the contractual commitment

process. Any clarification against a query if received and agreed by the PTCL

will stand as a condition of the contract – for which potential penalties „could‟ be

levied if it is felt necessary and contractually correct.

17.6. The Query shall be submitted according to the following format

17.6.1. Tender/contract No:

17.6.2. Title of Project:

17.6.3. Bidder's Name:

17.6.4. Query No:

S No. Relevant

Document

Clause

No /Page

No

Original

Statement

Question

Response

NS-066


17.7. PTCL may ask any bidder to raise the standard and capability of its offered

system to match with better standard or capability of the system offered by its

competitor for PTCL required network.

17.8. PTCL reserves the right to add (on the quoted price) or drop any item in the order

placed on the successful bidder.

17.9. Along the statement of compliance the bidder shall submit in the technical

proposal un-priced BoQ for technical evaluation.

-------------------------- END OF SPECIFICATIONS -----------------------

SE NS-066 - ptclNOCInventoryMgt... · SE NS-066 SYSTEM ENGINEERING WING ... configuration, testing,...

Documents

Transcript of SE NS-066 - ptclNOCInventoryMgt... · SE NS-066 SYSTEM ENGINEERING WING ... configuration, testing,...