UNMS Introduction and General Information
UNMS Introduction and General Information
Section 1
Table of Contents
1.1 Introduction......................................................................................................2
1.2 Existing Communication System:..................................................................2
1.3 Project Overview..............................................................................................3
1.4 Project Requirements......................................................................................5
1.4.1 Scope of Works.....................................................................................5
1.4.2 General Requirements.........................................................................6
1.4.3 Teaming Agreement of Contractor with OEM.................................7
1.5 General Responsibilities And Obligations.....................................................9
1.5.1 Poject Implementation Plan................................................................9
1.5.2 Contractor's Responsibilities and Obligations..................................9
1.5.3 The Employer Responsibilities and Obligations.............................11
1.6 General Bidding Requirements....................................................................11
1.7 Table of Compliance......................................................................................12
1.8 Organization of the Technical Specification Document.............................13
1.9 Applicable Standards.....................................................................................13
Section 1
1.1 Introduction
This Volume II of the Bid Document describes the technical specifications for
Unified NMS system (U-NMS) being procured by the Employer (Power Grid
Corporation of India Limited) for managing Regional Communication System of
Inter-State Transmission system (ISTS) and State Utilities Communication Network
within a region and National Communication System for Inter-Regional
Communication system .
There are some nodes which came up as part of transmission system projects for
which only Craft Terminal based NMS is provided. Visibility of such nodes is not
available in existing NMS. The details of existing communication system and NMS
is provided in Appendices.
The U-NMS shall be provided with main and back-up configuration. Location of
Northern Region U-NMS for main configuration is Manesar and for back-up
configuration is Lucknow. Extended clients/workstations shall be provided at State
level (SLDCs) and also for other utilities as per requirement which shall have access
to both main as well as back-up configuration of regional U-NMS. U-NMS locations
are indicative only and may change during engineering and implementation.
Figure 1.1
U-NMS shall be integrated with existing NMSs and standalone NEs such as
SDH/PDH/DCPS etc., which are not being monitored on any NMS of ISTS
Communication and State Communication Network within the region. This shall
further be integrated with SCADA server at LDC and SCADA server at REMC for
RTU availability. The logical connectivity of U-NMS shall be as shown in Figure 1.2:
Figure 1.2
1) The scope for the U-NMS Package shall be for Supply, Installation,
customization, commissioning, training, operation and maintenance of
centralized NMS (U-NMS) for Regional and State configuration including
hardware & software for servers, workstation, storage devices, network
switches, firewall & IDPS, Video Projection System (VPS), Printer, Furniture
etc. and documentation as per the requirement specified in different sections
of the Technical Specifications.
4) AMC services for supplied and commissioned U-NMS system for seven (7)
years including one (1) year defect liability period.
6) Integration & Testing with any other Control Centre (CC) on standard
7) Technical & Commercial tie-ups with existing vendors for NMS/NEs and
OEM’s of U-NMS modules.
(* NE/NMS can be of any technology such as SDH, PDH, MPLS, VSAT, Radio,
etc.)
The Contractor is encouraged to offer standard products and designs. However, the
Contractor must conform to the specification requirements and provide any additional
equipment necessary to meet the requirements stated herein.
It should be noted that preliminary design information and bill of quantity are
indicative only; the Contractor shall verify jointly (with Employer) the design data
during the site surveys & detail engineering and finalise the BoQ as required for
ultimate design & system performance.
The Bidder's proposal shall address all functional and performance requirements
within this specification and shall include sufficient information and supporting
documentation in order to determine compliance with this specification without
further necessity for inquiries.
The Bidder's proposal shall clearly identify all features described in the specifications
or in any supporting reference material that will not be implemented; otherwise, those
features shall become binding as part of the final contract.
The bidders are advised to visit sites (at their own expense), prior to the submission
of a proposal, and make surveys and assessments as deemed necessary for proposal
submission.
The successful bidder (Contractor) is required to visit all sites. The site visits shall
include all necessary surveys to allow the contractor to perform the design and
implementation functions. The Contractor shall submit the site survey format for
Employer’s approval and inform their site survey schedule to the Employer well in
advance. The site survey schedule shall be finalized in consultation with the
Employer. The Employer may be associated with the Contractor during their site
survey activities.
After the site survey, the Contractor shall submit to the Employer a survey report as
per the approved survey format. This report shall include at least the following items:
The bidder should submit JDU with respective major OEM(s) (for supply of
application software modules, server hardware et.) to ensure timely Supply,
Installation, Commissioning, Performance/SLA(s), Warranty & Maintenance as
specified in Technical Specifications. Contractor & respective major OEM(s) of
offered product(s) shall sign and submit a Teaming, which shall at least include
followings:
1) OEM(s) shall provide required skill sets to the Contractor to enable them to
execute the project deliverables (Network/ System Design, Deployment (I & C),
Testing, Operational Support, Future network Augmentation, New Service
Deployment for customers & Contingencies situations).
2) OEM(s) shall also provide all the requisite assistance to the Contractor for project
completion, warranty & AMC.
4) The OEM(s) shall provide all the know-how required to design and size the
solution as per requirement as specified in Technical Specifications to the Contractor
for the equipment supplied.
6) Technical & Commercial terms and conditions shall be mutually agreed between
Bidder & OEM(s) and shall form part of submitted bid agreement.
7) Availability of Subject Matter Expertise (SME) on site from OEM shall be ensured
in case Contractor is not able to resolve the problem.
ii. Identified SME(s) to be attached with respective contractor for the period of
delivery and up to an identified milestone.
iii. Designated OEM(s) representative shall be available for all Project Steering
committee meetings.
8) OEM shall give an undertaking that the SLA applicable to their solution will be
supportable. OEM shall give undertaking that current version of the software
including updates, software patches released time to time will be supported for next 7
years excluding the contract implementation period.
9) The OEM shall clearly define its policy of releasing major and minor version each
year. The implementation shall be based on a product configuration with a clear
product roadmap for the contract period.
10) OEM shall deliver the following to Contractor for finally delivering to Employer:
i. Licensed copy of all OEM applications that are within the scope of implementation
by Contractor.
ii. Licensed copy of development and runtime versions of the report writer products
and other products bundled with the application.
iii. List and specifications of all available Application Program Interface (APIs) in
each version.
iv. Installation for all OEM applications that are within the scope of implementation
by Contractor.
v. Product Specifications of all OEM applications that are within the scope of
implementation by Contractor.
xiii. Guaranteed response times for typical OLTP (Online Transaction Processing)
and batch transactions on various configurations of the suggested hardware (if
applicable).
xv. Warranty, Post Warranty, and Operational Support programs offered by OEM–
including commercial implications, SLA and availability of local support facilities.
This shall include problem resolution, application maintenance, change requests, as
well as policy for upgrades and updates.
This section describes the general responsibilities and obligations of the Contractor
and the Employer.
The Bidder's technical proposal shall include a project implementation plan and
schedule that is consistent with the implementation plan detailed in other sections &
appendices of this specification. The Implementation plan shall include the activities
of both the Contractor and the Employer, showing all key milestones and clearly
identifying the nature of all information and project support expected from the
Employer. The Employer and Contractor shall finalise the detailed Implementation
plan following award of the contract.
Contractor's obligations include, but are not limited to, the following:
(1) Provide a complete turnkey implementation and assume responsibility for all
integration and implementation issues in order to deliver an operable system.
(2) Provide a working system that meets the functional and performance
requirements of this specification.
(3) To ensure the completion of the entire implementation within the scheduled
time frame as mentioned in the tender fulfilling the entire tender terms and
conditions.
(4) Site visits and studies necessary to identify and provide all equipment needed
to implement U-NMS.
(5) Development of installation and safety guidelines and procedures for the
(6) Implement all associated minor civil works and identify any major civil works
such as expansion or construction of rooms, trenches necessary for installation
of proposed equipment and provide details of such works to the Employer.
(7) Define source power requirement for each cabinet/ rack of equipment
provided at each location.
(8) All cabling wiring including supply, laying and termination of cables (signal,
power supply & earthing), DC/AC distribution boards.
(10) Supply, installation, testing and commissioning of all hardware, software and
firmware required to satisfy this specification.
(11) Staging, maintenance and security of the staging area including the full
responsibility for protection from fire and theft.
(12) Configure all features and functionalities in the network as indicated by the
Employer during detail Engineering and implementation.
(13) Compliance of all applicable security related requirements as per latest DoT
guidelines with subsequent amendments.
(15) Tie up with existing communication system provider for providing necessary
system information of existing OEMs of Communication system for getting
required information for seamless integration with U-NMS system as per
requirements mentioned in different sections here.
(18) Functional Acceptance Test for Software, Factory Acceptance Test (FAT) for
hardware, Site Acceptance Testing (SAT) and Integrated Site Acceptance Test
(ISAT) for all hardware, software and firmware provided.
(20) Support for Operation, Maintenance and debugging of the items through final
acceptance, and maintenance (including deployment of resources) throughout
the defect liability period and after defect liability period as defined in other
section of these specifications.
(22) Analytics development and updating the trending quarterly during Warranty
& AMC period.
The Employer will provide the following items and services as part of this Project:
(5) Approval of key personnel/ Project Manager/ resident Engineer at Site for the
project.
(6) Witness of tests & approval of survey, test & design documents.
The Bidder shall be responsive to the Employer's technical requirements as set forth
in this specification. The Bidder's proposal shall include the following:
(1) The Technical Proposal including the documents listed in the Table 1-2: Bid
Documents Checklist shall be provided in the bid.
(2) A detailed project implementation plan and schedule that is consistent with the scope
of the project and Employer's specified objectives. The plan shall include the
activities of both the Contractor and Employer, show all key milestones, and clearly
identify the nature of all information and project support to be provided by Employer.
Manpower resources proposed to be deployed by the Contractor during the execution
phase shall be clearly indicated.
(3) One System Integrator shall submit only one U-NMS solution. Else, bidder shall not
be considered for evaluation.
Bidder shall use one copy of Volume I, "Conditions of Contract," and Volume II,
"Technical Specifications" to indicate compliance status with those volumes. Within
the right-hand margin, Bidder shall indicate compliance status to each paragraph
along with a crU-NMS-reference to its proposal and an index key for any explanation
or comment.
In addition, the Bidder shall annotate the Table of Contents of each of the above
stated volumes to provide a high-level summary of compliance status. In both cases,
the following symbols, and no others, shall be used:
Only one symbol shall be assigned to a paragraph and shall indicate the worst case
level of compliance for that paragraph. This annotation may be hand written.
Bidder shall also underline, on the compliance copy, all requirements to which
exceptions have been taken (X) or to which alternatives have been proposed (A).
Each alternative shall be clearly and explicitly described. Such descriptions shall use
the same paragraph numbering as the bid document sections addressed by the
alternatives. All alternative descriptions shall be in one contiguous section of the
Bidder's proposal, preferably in the same volume, and titled "Alternatives." A
separate section titled "Exceptions" should be provided containing any discussion or
explanation Bidder chooses to provide concerning exceptions taken. Alternatives
which do not substantially comply with the intent of the bid documents will be
considered exceptions.
The Employer will assess the merits of each alternative and exception and will be the
sole judge as to their acceptance.
The following standards and codes shall be generally applicable to the equipment and
works supplied under this Contract, wherever applicable:
5. TMF-MTNM 3.5
6. TMF-MTOSI 4.0
7. SNMPv2 / SNMPv3 Interface
8. SID v13 (Shared Information Model)
9. IETF MIB II - RFC 1213 (Interface and IP Address)
10. IETF MPLS - RFC 4221 (LSR, LDP, TE STD MIBS)
11. IETF Entity MIB RFC 4133 (Chassis/Card)
12. ETF RFC 2922– LLDP MIB
13. ITU-T G.707 based SDH Multiplexing hierarchy to be handled as part of
Inventory Model
14. ITU-T G.709 based WDM/OTN Multiplexing hierarchy to be handled as part
of Inventory Model
15. ITU-T G.7041 based GFP /EoSDH to be handled as part of Inventory Model
16. ITU-T G.7042 based LCAS /EoSDH to be handled as part of Inventory Model
17. ITU-T G.841 based SDH Protection mechanisms to be handled as part of
Inventory Model & Impact analysis
18. TEC GR No: TEC GR No TEC/GR/I/ESI-001/03/MAR12 for Mid-Tier
Storage.
19. TEC GR No. TEC/GR/I/ESI-001/03/MAR12 for SAN Switches
20. TEC-GR No: GR/LSW-01/04 MAR-11 for LAN Switches
21. TEC GR no. GR/FWS-01/02 SEP 2006 for Firewall
22. TEC GR no. GR/IPS-01/01 NOV 2006 for IPS
23. The ITU-T TMN model and components
24. ITU-T standard M.3000, M.3010, M.3599
25. U-NMS/J Standards
26. OSI and ITU-T X.73x series System Management Function (SMF) standards
and recommendations
27. ITU-T X.730, X731 , X.732, X.733 & X.736
28. ISO 27001 standards
29. ITIL v3 standard / eTOM standard
30. ISO/IEC 15408 standards wherever applicable
31. BS 25999 and ISO 22301 for DC-DR
All supplied softwares shall be of latest version w.r.t. date of bid opening, inclusive
of revisions, which are in force at the date of approval of solution/system design
document. Where new specifications, codes, and revisions in NMS/TMN/U-NMS are
issued during implementation & AMC, the Contractor shall make available such
revised updates & upgrades along with configuration required. Moreover, the
clearance for any such updates in NMS/TMN is to be provided by U-NMS contractor
after due testing in test & development setup of U-NMS system.
In the event the Contractor offers to supply material and/or equipment in compliance
to any standard other than Standards listed herein, the Contractor shall include with
their proposal, full salient characteristics of the new standard for comparison.
In case the requirements stipulated in the specifications are stringent than those
specified by the standards, the specification shall override the standards.