Southern Regional Power Committee, Bangalore - Kar

__________________________________________________________________________________ Record Notes of U-NMS Meeting held on 07.12.2020

Southern Regional Power Committee, Bangalore

Record Notes of the UNMS meeting held on 07.12.2020 through webEx

1 Introduction

A special meeting was held to discuss Unified Network Management System

(UNMS) & Communication issues on 07.12.2020 through webEx. The list of

participants is enclosed as Annexure - I.

Shri A Balan, Member Secretary, SRPC welcomed the participants of the special

meeting on UNMS and ISTS Communication System. He informed that the issue was

discussed in various meetings and in the 37th

meeting of TCC and state utilities

requested for more information on the benefits of UNMS to their system. He requested

PGCIL/CTU to clarify their doubts about the UNMS system. He informed that the

outcome of the meeting would be put up for approval in the 38th

meeting of TCC/SRPC

meeting scheduled on 22nd

& 23rd

of Dec 2020.

Shri Abhimanyu Gartia, Executive Director, SRLDC welcomed the participants

and mentioned about the UNMS discussions had in the 158th

OCC at Kochi and other

meetings and informed the following:

(a) The scheme was recommended technically. He emphasised the need of

UNMS for the transmission system availability and communication system

availability and stated it is important for Grid security.

(b) The quick fault detection and restoration is highly essential as the

availability of transmission equipment will be certified by SRPC and the

communication system availability will have commercial implications.

(c) PSDF funding is required for the investment by the States and CTU as the

system would be used across the country and for cross border power flows

also.

Shri H.H Sharan, CGM (LD & C), CTU made a Presentation on Regulatory

Requirement and features of Unified Network Management System. The

presentation is enclosed herewith as Annexure - II.

2. Salient points of Presentation made by CTU/PGCIL on Unified Network

Management System (UNMS)

a. CERC notified Communication Regulation in May’17 which envisaged

Centralized Supervision System for ISTS Communication.

b. CTU shall be the Nodal Agency for implementation of system for centralized

supervision for quick fault detection and restoration of ISTS Communication.

c. Communication Regulations requires all Users of CTU, NLDC, RLDCs, SLDCs,

STUs to maintain the communication channel availability at 99.9% annually,

provided that with back up communication system, the availability of

communication system should be 100%.

d. Central Electricity Authority (Technical Standards for Communication System in

Power System Operations) Regulations, notified in Feb 2020, specify that User

shall keep evidence of compliance on availability for the previous two calendar

years plus the current year for all the interfaces which are in operation.


e. CEA, Communications regulation specifies network management system shall

have features to store necessary information and facility to generate report on

communication system availability of major equipment as well as the data

channels on daily or weekly or monthly or annually basis. It also envisages

centralised monitoring shall be in main and back-up control centre architecture

with centralised database and twenty-four hours maintenance on all days.

f. Approx. 16000Kms OPGW network in Southern Region with approx. 500 nodes

which are being monitored by approx. 8 nos. NMS (proprietary make Network

Management System). There are also approx. 50 nodes which are standalone and

not being monitored on any NMS.

g. OPGW Communication network has grown in size and complexity. Efficient

management of network is essential.

h. Centralized supervision is not possible with current infrastructure in view of

multiple NMSs and Standalone NEs in the network.

i. Majority of ISTS Communication nodes implemented by other utilities are not

visible in existing NMSs affecting Centralized Supervision.

j. Present NMSs were considered with requirement mainly for monitoring and

maintenance of implemented Communication Nodes.

k. In the present infrastructure, there is no provision of automatic report generation,

centralized database and data retention for 3 years as per regulations

requirement.

l. The proposed UNMS project shall integrate all existing NMSs and standalone

Network Elements of ISTS & State Utility communication network in single

unified NMS.

m. Explained the present scenario (topology) of NMS and future scenario of NMS

with UNMS.


n. Explained the hierarchical setup of the UNMS System.

o. Computer Hardware & Software for UNMS Applications (Servers &

Workstations).

p. Applications considered are following :

(i) Network Resource Management ( Visibility of Network, Asset mgmt. etc)

(ii) Configuration Management ( Provisioning of services etc)

(iii) Fault Management ( Alarms handling, Availability calculation etc)

(iv) Performance Management (Link performance etc. )

(v) Common Modules ( Interface with Users, Report generation)

(vi) Historian (To manage database)

q. Presented the Benefits of UNMS and informed that estimated cost of Southern

Regional UNMS scheme estimated at Rs 109 Crores and AMC charges -Rs 5

Crores per annum for 7 years.


r. National UNMS shall be implemented for managing inter-regional and cross-

border links. National UNMS shall be integrated with all regional UNMSs.This

shall be implemented in main & back-up configuration. Estimated Cost of

National UNMS– Rs. 109 Crs. AMC charges - Rs 5 Crs per annum for 7 years.

Implementation of National UNMS shall be done after approval of all regional

UNMS. Tariff for National UNMS to be shared by all regions.

s. Unified Centralized Network Management System (UNMS) for ISTS

Communication was deliberated in the 158th

OCC, Special (UNMS) meeting on

07.11.2019, 36th

TCC /37th

SRPC and in 37th

TCC Meetings. The draft Technical

specification was circulated by SRPC vide lr dt 21.04.2020.

t. Explained the Provisions in TS for integration of UNMS with existing NMS/NE

and upcoming National UNMS.

u. NERPC (NIT done on 26.10.20) and NRPC (NIT being done on 08.12.20)

already approved the UNMS Scheme.

3. Gist of Deliberations in the meeting:

(a) APTRANSCO: APTRANSCO sought clarification from CTU regarding the

compatibility of their ICCP, existing equipment and MPLS equipment being

installed in their communication system for the integration of UNMS. They

expressed their concern on high cost of the project and sought 100 % PSDF

funding. They also wanted to address the configuration issue with proprietary

systems. Expressed that different OEMs are involved to configure the equipment

with UNMS.

(b) TSTRANSCO: Welcomed the UNMS proposal, and stated that the architecture of

the UNMS should be compatible with the state NMS system. They informed that

one Work Station (WS) is necessary at SLDC for back up purpose and requested

for UNMS reporting to state level also. They sought for SDH equipments should

be able to integrate with the UNMS and standardization of SDH/equipment used

for communication system. TS also expressed that the cost of UNMS system is

high and sought for PSDF funding.

(c) KPTCL informed that the integration of communication equipment is limited to

Inter-State / ISTS nodes. Their Satellite based NMS can’t be shared with 3rd

party

NMS. The required configuration may be around 10 % nodes from STUs and the

balance would be in respect of CTUs. They expressed their concern on the cost of

the project and sought 100 % PSDF funding.

(d) KSEBL wanted to clarify whether data would be collected from state NMS or

from communication equipment. They are in the process of upgrading their

communication system from SDH to MPLS technology and hence their new

equipment shall be compatible to the UNMS.

(e) TANTRANSCO wanted CTU to clarify whether their existing communication

equipment in Chennai and Madurai using OPGW are to be removed from UNMS

integration. They expressed their difficulties to coordinate with OEM for the

integration of equipment with ULDC. They are in the process of upgrading their

communication system from SDH to MPLS technology and hence their new

equipment shall be compatible to the UNMS. They expressed their concern on the

cost of the project and sought 100 % PSDF funding.


(f) SRLDC presented their observation on the Technical Specification for UNMS for

ISTS & State Utility Communication Network for the inclusion / modification to

be made by CTU for SR UNMS system. Copy of SRLDC presentation is enclosed

as Annexure - III.

(g) CTU/PGCIL informed that Rs. 109 Cr has been estimated as project cost for

Southern Region for the implementation of UNMS. AMC Maintenance Cost is

estimated at Rs 5 Crores per Annum. The tariff will include AMC for 7 years

Period. Also, project cost of National UNMS shall be shared by all constituents

similar to PoC tariff. After getting approval in the SRPC forum they will prepare

DPR. While replying to the query of 100% PSDF funding for UNMS project by

Members, it was informed that normally 50% funding only given for

communication projects by PSDF Committee (and some projects up to 70%) and

remaining project cost has to be borne by the constituents. The cost will be

recovered in tariff mechanism. They also informed that the observation made by

SRLDC would be taken care in their specification.

(h) CTU/PGCIL shared their Contact personnel name and contact nos for clarifying

the doubts about the UNMS scheme .The contact details as follows.

S.No Name Designation Contact No Email ID

1 Shri

H.H.Sharan

CGM(LD&C) 9873549014 sharan@

powergridindia.com

2 Smt. Shyama

Kumari

DGM 9873918459 shyama@

powergridindia.com

4. Conclusion

(a) Members agreed in principle (technically) and recommended the scheme for

approval of forthcoming 38th

TCC/SRPC. There was no representation from

PED, Puducherry in this meeting. However, they had agreed for the same in the

earlier OCC Meetings.

(b) CTU/PGCIL will approach for PSDF funding as the system would be used

across the country and for cross border power flows also.

(c) All state utilities to get approval from their competent authority and submit their

comments to SRPC/SRLDC/PGCIL to have fruitful discussions in the

forthcoming TCC/SRPC convened on 22nd

/23rd

December 2020.

(d) State utilities will furnish the details sought in the format (prepared by LD&C,

PGCIL) to SRPC/SRLDC/PGCIL by the end of December, 2020. The details of

all NMS/EMS/Standalone systems which need to be integrated with UNMS

needs to be furnished.

(e) CTU/PGCIL informed that the UNMS will monitor the fibres being exclusively

used for Power Sector only.

(f) States entities to include necessary terms in the agreement with Vendors before

making procurement of new NMS/EMS equipment and software to ensure

compatibility with UNMS so that integration of new Nodes can be made with

UNMS without any hindrance.


(g) States entities to assess the propriety issues of existing NMS/EMS for

integration with UNMS.LD&C, PGCIL would address the propriety issues of

common vendors (ISTS & State sector).

(h) CTU/PGCIL assured of highest level compliance of cyber security

specifications in the UNMS complying with all the applicable guidelines.

(i) MS, SRPC informed that the recommendations would be put up to TCC/SRPC

for approval. He requested the States to furnish the data sought by PGCIL.

5. MS, SRPC thanked all the participants for getting clarity on various UNMS scheme

(configuration issues) and for agreeing in principle (technically) for the UNMS

Scheme. He informed that the recommendation would be put up for approval of 38th

TCC / SRPC meeting convened on 22nd

/23rd

December 2020.

*********

Annexure - I

S.No Name(S/Shri/Smt) Designation Organization Email address

1 Anandarao CE, TELECOM APTRANSCO

2 Sridhar EE, TELECOM APTRANSCO

3 B Hanumantha Rao DEE, TELECOM APTRANSCO

4 B Durga Bhavani AEE,TELECOM/SCADA

5 C Ramesh Babu TSTRANSCO [email protected]

6 Mr. Sunil NX EE Communication KSEBL

7 K P Rafeeque AEE KSEBL [email protected]

8 Biju Anrews AEE, TNMS KSEBL

9 Dixon TC AEE, Communication KSEBL

10 Abhilash EL AE, TNMS KSEBL

11 Bindhu M KSEBL [email protected]

12 K Navin kumar EE P&C-1 TANTRANSCO

13 T G Kannagi AEE TANTRANSCO

14 Sivakumar Thiagarajan [email protected]

15 S B Chandrashekharaiah EE SCADA KPTCL [email protected]

16 H.H.Sharan CGM(LD&C) CTU [email protected]

17 Harish Nair Sr. DGM, RTAMC SR-II, PGCIL [email protected]

18 Y Rajesh Kumar Sr. DGM-ULDC SR-II, PGCIL [email protected]

19 MD Mahamood SR-II, PGCIL [email protected]

20 K Sudhakar Rao Sr. DGM SR-I, PGCIL

21 Surender SR-I, PGCIL [email protected]

22 Ms Sunita Chohan [email protected]

23 Abhimanyu Gartia ED SRLDC [email protected]

24 T R Ganesh GM SRLDC [email protected]

25 Rakesh Sharan DGM SRLDC [email protected]

26 A Rajkumar CM SRLDC [email protected]

27 Sarath Babu Manager SRLDC

28 A Balan MS SRPC [email protected]

29 R M Rangarajan SE SRPC [email protected]

30 A Kesavan EE SRPC [email protected]

31 N S Malini EE SRPC [email protected]

32 M Sriharsha AEE SRPC [email protected]

33 Bharath AE SRPC [email protected]

List of Participants for U-NMS and ISTS Communication System meeting held on 07.12.2020

mailto:[email protected]






SOUTHERN REGION

U-NMS FOR

ISTS & STATE UTILITY COMMUNICATION

NETWORK

Date: 07.12.2020

SOUTHERN REGION

SOUTHERN REGION

CERC COMMUNICATION REGULATIONS 2017

CERC notified Communication Regulation in May’17 whichenvisaged Centralized Supervision System for ISTSCommunication.

• CTU shall be the Nodal Agency for implementation ofsystem for centralized supervision for quick fault detectionand restoration of ISTS Communication.

• Communication Regulations requires all Users of CTU, NLDC,RLDCs, SLDCs, STUs to maintain the communicationchannel availability at 99.9% annually, provided that withback up communication system, the availability ofcommunication system should be 100%.

SOUTHERN REGION

CEA Technical Standards

Based on CERC communication regulations, CEA in its technicalstandards for communication system in power systemoperations regulation, 2020, specified for the following :

Data retention for the previous 02 calendar years plus thecurrent year for all the Interfaces which are in operation tokeep evidence on compliance of availability.

Facility to generate report on communication systemavailability on daily/weekly/monthly/annually basis.

Centralized monitoring in main & back-up architecture withcentralized database and 24 hours maintenance on all days.

Approx. 16000Kms OPGW network in Southern Region with approx. 500 nodeswhich are being monitored by approx. 8 nos. NMS (proprietary make NetworkManagement System). There is also approx. 50 nodes which are standalone and notbeing monitored on any NMS.

OPGW Communication network has grown in size and complexity. Efficientmanagement of network is essential .

Centralized supervision is not possible with current infrastructure in view ofmultiple NMSs and Standalone NEs in the network.

Majority of ISTS Communication nodes implemented by other utilities are notvisible in existing NMSs affecting Centralized Supervision.

Present NMSs were considered with requirement mainly for monitoring andmaintenance of implemented Communication Nodes.

In the present infrastructure, there is no provision of automatic report generation,centralized database and data retention for 3 years as per regulations requirement.

The proposed UNMS project shall integrate all existing NMSs and standaloneNetwork Elements of ISTS & State Utility communication network in single unifiedNMS.

Background – Present System

Vendor

Proprietary NMS

Vendor

Proprietary NMS*

Standalone systems

without NMS

Mesh Communication Network with multiple make Communication equipment

Vendor Proprietary

NMS*

Present Scenario of Network Management

Vendor Proprietary

NMS Vendor Proprietary

NMS*

U-NMS

Standalone systems

without NMS

Vendor Proprietary

NMS*

Any future

technology viz.

MPLS, Radio,

DWDM etc.

The proposed UNMS shall be integrated with multiple make NMS and standalone

communication equipment to give integrated view of Network and Centralized Supervision.

Future Scenario of Network Management with UNMS

NER

U-NMS

(Main & Back-up)

National U-NMS

(Main & Back-up)

SR

U-NMS

(Main & Back-up)

NR

U-NMS

(Main & Back-up)

ER

U-NMS

(Main & Back-up)

WR

U-NMS

(Main & Back-up)

Workstation

NR SLDCs

Workstation Workstation Workstation Workstation

NER SLDCs SR SLDCs ER SLDCs WR SLDCs

HIERARCHICAL SET-UP IN UNMS SCENARIO

Benefits of U-NMS Visualisation of all ISTS and State Utility Communication Nodes in Single NMS

facilitating effective network monitoring.

Capability to interface with multiple make NMSs and Network Elements.

Centralized provisioning of data and voice Services.

Advance features such as availability calculations, automated fault report generation, assets monitoring etc.

Support for preventive maintenance based on health of network through the system

Data retention for 02 calendar years plus the current year for all interfaces in

the network etc.

Analytics for predictive analysis and recommendations for efficient management.

Facilitate reliable and resilience network.

Services through Backup UNMS in case Main UNMS fails

“ Proposed UNMS with above features shall facilitate

compliance of Communication Regulations 2017”

UNMS – Southern Region

POWERGRID made a detailed presentation on UNMS in 158th OCC meetingheld on 09.08.2019 at Kochi and in Special meeting on UNMS held on07.11.2019 at Bangalore.

UNMS Scheme was further discussed in 36th TCC and 37th SRPC meeting heldon 01.02.2020 at Hyderabad, Telengana, AP and TANTRANSCO . It was agreedto call a separate meeting for detailed discussion on scope and technicalrequirement of the scheme.

There were constraints in having meeting due to COVID-19 Pandemic hencePOWERGRID provided draft technical specification as desired by SRPC. Thedraft technical specification was circulated vide letter dated 21.04.2020 bySRPC.

Comments of KSEB received while other constituents have to furnish thesame.

UNMS Scheme was further discussed in 37th TCC meeting held on 28.10.2020through VC. It was agreed to call a separate meeting for further discussionand recommendations of same to be taken up in next SRPC .

Proposed UNMS-SR at a Glance Computer Hardware & Software for UNMS Applications ( Servers & Workstations)

Applications considered are following :

• Network Resource Management ( Visibility of Network, Asset mgmt. etc)

• Configuration Management ( Provisioning of services etc)

• Fault Management ( Alarms handling, Availability calculation etc)

• Performance Management (Link performance etc. )

• Common Modules ( Interface with Users, Report generation)

• Historian (To manage database)

Firewall and IDPS for security of installed system

Video Projection System(VPS) and UPS

AMC of supplied system for 7 years

U-NMS Configuration for Regional centre to consist of Servers, Storage Devices, VPS, Switches,Routers, Firewall, Remote workstations, Printer, Furniture etc. in dual LAN in Main (HighAvailability-HA) and Backup configuration to manage ISTS regional, inter-regional and CrossBorder communication links.

U-NMS Configuration for for SLDCs shall consist of Remote workstations, Switches, Routers,Firewall Printer, Furniture etc. with rights to access servers of respective Regional UNMS centreto manage their respective Intra-state Communication Network.

UNMS-SR at a Glance

Estimated Cost of the Scheme – Rs. 109 Crs.

AMC charges - Rs 5 Crs per annum for 7 years.

AMC charges are considered for manpower deployment on 24/7 basis at Regional UNMS main and back-up.

At State level, manpower deployment is considered for general shift on all days and on call basis as per requirement.

UNMS- National

National UNMS shall be implemented for managing inter-regional

and cross-border links.

National UNMS shall be integrated with all regional UNMSs

This shall be implemented in main & back-up configuration.

Estimated Cost of National UNMS– Rs. 109 Crs.

AMC charges - Rs 5 Crs per annum for 7 years.

Implementation of National UNMS shall be done after approval of

all regional UNMS.

Tariff for National UNMS to be shared by all regions.

Provisions in TS for integration of UNMS with existing NMS/NE and upcoming National UNMS

---------------------------------------------------------------------------------------------------------

Compliance of Industry Standards to facilitate integration

ITU-T X.73x, M.3000, M.3010, M.3599

North Bound Interface Compliant

TMF-814 - CORBA based NML-EML Interface

Cyber security standard clause 14 of the Central Electricity Authority (Technical Standards for Communication System in Power System Operations) Regulations, 2020

IT and IT related elements against ISO/IEC 15408 standards.

Information Security Management System against ISO 27000 series Standards

It is envisaged to implement UNMS Project in six (6) separatepackages, five regional UNMS to manage regional communicationnetwork and one for national to manage inter-regionalcommunication network.

Status of UNMS scheme in various Regions

Region Approval Status Implementation Status

NER Approved by NERPC NIT done on 26.10.20

NR Approved by NRPC NIT being done on 08.12.20

ER Agreed in Sub-Committee. To be

approved in coming ERPC meeting

To be taken up after approval in

ERPC

WR Under discussion To be taken up after approval in

WRPC

National Approved in NRPC & NERPC To be taken up after approval of

all regional UNMS

Thanks for Your Kind Attention Please

U-NMS for ISTS & State Utility

Communication Network

Volume II - Technical Specification for U-NMS

Section 1 :INTRODUCTION and GENERAL INFORMATION

1.3 Project Overview

…..

• The U-NMS shall be provided with main and back-up configuration. Location of Northern SouthernRegion U-NMS for main configuration is Manesar and for back-up configuration is Lucknow XXXXX. Extendedclients/workstations shall be provided at State level (SLDCs) and also for other utilities as per requirement whichshall have access to both main as well as back-up configuration of regional U-NMS . U-NMS locations areindicative only and may change during engineering and implementation.

Comment: In initial planning itself, client/workstations should be provided at RLDCs also.

Original:

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

Deletion:

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. As per the scope of project “U-NMS shall facilitate centralized supervision, operation & control of the Regional and State level Communication system on round the clock basis”.Since,the project is to monitor communication system,monitoring RTUs ,PMUs availability is not within it’s scope.The various communication links between LDCs used for ICCP,PDC communication need to be monitored.


Figure 1.2

Comment: No direct connectivity with SCADA servers of LDCs, RTU,PMU device status not in project scope.


1.3 Project Overview

New addition:

Following applications are considered for U-NMS functionality:

a.…

h. Communication Channel Availability reports in compliance to CERC Communication Regulations 2017.

1.4.1 Scope of Works

Original:

6. Integration & Testing with any other Control Centre (CC) on standard protocol such SCADA server at LDC/SCADA server at REMC etc. as required.

Deletion:

6. Integration & Testing with any other Control Centre (CC) on standard protocol such SCADA server at LDC/SCADA server at REMC etc. as required.

1.4.2 General Requirements

….

The successful bidder (Contractor) is required to visit all sites. The site visits shall include all necessary surveys to allow thecontractor to perform the design and implementation functions. The Contractor shall submit the site survey format for Employer’sapproval and inform their site survey schedule to the Employer well in advance. The site survey schedule shall be finalized inconsultation with the Employer. The Employer may be associated with the Contractor during their site survey activities.

Comment: Definition of employer & owner for clarification


1.4.3 Teaming Agreement of bidder with OEM

…. Contractor & respective major OEM(s) of offered product(s) shall sign and submit a Teaming, which shallat least include followings:

1…

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 productsbundled with the application.

iii. List and specifications of all available Application Program Interface (APIs) in each version with samplecode for integration


1.5.2 Contractor's Responsibilities and Obligations

1…

New Addition:

23. Periodic Communication Channel Availability reports in compliance to CERCCommunication Regulations 2017.

1.5.3 The Employer Responsibilities and Obligations

1…

…

New Addition:

7.Arranging necessary permission for site visits/entry to owners of NEs.

Section 2:U-NMS Software Specifications

• 2.2 General Requirements

• Deletion:

• 2.2.9 The system shall support integration with SCADA system of Control Centers such as Load Dispatch Centers (LDCs) & Renewable Energy Management System (REMC) on standard protocol such as ICCP/web services/OPC etc.

Rationale: Communication system & Decision support system of RLDC/SLDC are independent systems. There should be always boundary between them.

• Insertion :

• 2.2.9/2.2.10 The system shall support the Application Program Interface for Automatic Generation of Periodic Reports.

Rationale: RLDC/SLDC requires automated reports on Communication availability & its utilization and expected to be part of General Requirements of TS.

Section 2:U-NMS Software Specifications Continued…

2.3 Control Centre Architecture:

• Original :

• 2.3.2 The infrastructure offered for proposed solution shall be completely virtualized and it shall be possible to scale it vertically and horizontally for future requirements. Supply, installation & commissioning of Software for virtualization shall be in the scope of bidder. Details of hardware requirement are elaborated in Section-3 of this Technical Specifications.

• Modified:

• 2.3.2 The infrastructure offered for proposed solution shall be completely virtualized/ Containerized and it shall be possible to scale it vertically and horizontally for future requirements. Supply, installation & commissioning of Software for virtualization shall be in the scope of bidder. Details of hardware requirement are elaborated in Section-3 of this Technical Specifications.

Rationale: As per the current technology trends, containerized is most beneficial, Containerization was developed to solve many of the problems of virtualization. The purpose of the containers is to encapsulate an application and its dependencies within its own environment. This allows them to run in isolation while they are using the same system resources and the same operating system. Having said that it is up to the OEM/Bidder to select the technology best suited to the product development life cycle management with good reliability.

SUGGESTION


2.3 Control Centre Architecture:

• Original :

• 2.3.6 The Control Center architecture shall be scalable and shall have high performance. Critical network equipment such as Switches, Routers and firewalls shall be provided on a redundant mode with device level redundancy.

• Modified:

• 2.3.6 The Control Center architecture shall be scalable and shall have high performance. Critical network equipment such as Switches, Routers and firewalls shall be provided on a redundant mode with device level & Power supply redundancy.

Rationale: Normally Switches and GPS receivers etc.. are supplied with single Power supply module,however Switches are critical component in facilitating the redundancy of applications in most controlcenter Architectures, even if we have routers and firewall with dual power supply, many times we faceissue with connectivity loss with critical process within entire system, hence it is recommended to envisageswitches with Dual power supply

SUGGESTION


2.4 Software requirements for U-NMS

Original:

•The U-NMS system shall have capability of integration with multiple wired/wireless technologies like SDH, PDH, DWDM,CWDM, ASON, OTN, PTN, MPLS), VSAT, Radio etc. from multiple vendors. However, during implementation of U-NMS,transmission system technology, termination/cross-connect/Access system configured in the network shall be considered forintegration in the proposed U-NMS. U-NMS shall ensure seamless operation & management of Communication network viz.fault Management, Design & Provisioning, Inventory management, Performance monitoring etc. without dependency onunderlying NMS. The delay/latency added due to U-NMS in existing Communication system shall not exceed 1ms. ProposedU-NMS Performance Parameters for various aspects are provided at appendix.

Modified:

•The U-NMS system shall have capability of integration with multiple wired/wireless technologies like SDH, PDH, DWDM,CWDM, ASON, OTN, PTN, MPLS(IP & TP), VSAT, Radio etc. from multiple vendors. However, during implementation ofU-NMS, transmission system technology, termination/cross-connect/Access system configured in the network shall beconsidered for integration in the proposed U-NMS. U-NMS shall ensure seamless operation & management ofCommunication network viz. fault Management, Design & Provisioning, Inventory management, Performance monitoringetc. without dependency on underlying NMS. The delay/latency added due to U-NMS in existing Communication systemshall not exceed 1ms. Proposed U-NMS Performance Parameters for various aspects are provided at appendix.

Rationale: MPLS Transport Profile (MPLS-TP) is rapidly becoming the transport protocol of choice – as it delivers onthe transport essentials in a packet architecture, please refer CIGRE D2-309_2016: MPLS-TP as packet platform forcritical services in power transmission.

Reasons for 1ms latency due to U-NMS.


2.4.1.1 Network Resource Management (Network Discovery & Inventory Management):

Inventory data in the context of U-NMS refers to service/circuit, logical and physical network inventory data besides others required in order to implement the service-assurance related functionality of the U-NMS. The data that has to be maintained shall include the following but not limited to:

1…

….

4.Since any communication network will undergo frequent changes, there should be an automatic way to discover the newly addedlinks. Deletion of the existing links shall also be possible by adopting a similar approach with user confirmation. The system shouldsupport dynamic addition/deletion of new links.

5. The system shall provide for the categorization of the circuits (Healthy Circuits, Hanging Circuits, etc.) and shall discover thecircuits found hanging and the same would be identified and reported to the user.

…….

8.The system shall support circuit end-to-end route discovery and display in GUI view, including network, node, card, port, andtimeslot with all internal patching etc. (MUX /DEMUX, OUT level).

Modified:

4. Since any communication network will undergo frequent changes, there should be an automatic way to discover the newly addedlinks. Deletion of the existing links shall also be possible by adopting a similar approach with user confirmation. The system shouldsupport dynamic addition/deletion of new links and modification of existing links.

5. The system shall provide for the categorization of the circuits (Healthy Circuits, Hanging Circuits, etc.) and shall discover thecircuits found hanging and the same would be identified and reported to the user.

8. The system shall support circuit end-to-end route discovery and display in GUI view, including network, node, card, port, VCG andtimeslot with all internal patching etc. (MUX /DEMUX, OUT level).


Original:

35.The system shall have the capability to make changes in the 3rd party system based on discrepancy

identified.

Comment: Need discussion

43. Discovery and Inventory (Passive):

New Addition:

vi) System shall have the capability to retrieve the communication channel ,VCG utilization(node wise) report in user defined format.

2.4.1.2 Design, Assign, Activation/Provisioning, Configuration and Re- Engineering

6) The bandwidth provisioning system shall automate the end-to-end provisioning for a given source and destination for the entire Communication network hierarchy.

Comment: Need discussion



Original:

15.There shall be a front end to monitor the status of the requests and any errors in processing.

16.All the activities happening through the system shall be tracked and a history shall be maintained at leastfor 3 months online in system & 3 years in archive mode.

17.The offered system shall be configurable & customizable

Modified:

15.There shall be a front end dashboard to monitor the status of the requests and any errors in processing.

16. All the activities happening through the system shall be tracked and a history shall be maintained at leastfor 3 months online in system & 3 years in archive mode.

17. The offered system shall be configurable ,customizable and user friendly

SUGGESTION



Original:

23. The system shall support automatic bandwidth grooming feature across multiple Networks .

Comment: Whether ,it will override end to end bandwidth provision?

Original:

24. The system shall facilitate feasibility study for providing a circuit of a particular capacity between two end points and also block the network resources for a configurable time period & export API’s for external applications too.

Modified:

24.The system shall facilitate feasibility study for providing a circuit of a particular capacity between two end points and also block the network resources for a configurable time period & export API’s for external applications too, with sample code for easy utilization of API.



Original:

31.The system shall propose various path options for different services between two locations or NEs – shortest, least cost, minimum delay and optimized path based

on the following:

i. Cost

ii. Rings count & Hop Count

iii. Bandwidth Available

32. The system shall provide capability to a user to be able to reject the best path computed/proposed by tool and to select/view from alternative options.

Comment: Whether ,it will override end to end bandwidth provision?

Original:

45. The system shall provide Network planning & capacity optimization tool to study the following:

…..

New Addition:

viii. System shall have the facility to list out the impacts of failure of one or more SDH equipment or STM link to other SDH layers riding over them and associatedcommunication channels provisioned.


2.5 Common Functional Requirements of U-NMS

2.5.1 Unified U-NMS Console (Common Reporting & Dash boarding System)

2.5.1.6 Reporting

Original:

New Addition:

13 System shall be able to provide the all provisioned communication channels and their paths in user defined format.

2.6.4 System Security, Access Control Management System & Audit (CERT-In or other guideline as applicable)

1..

12.The audit shall be completed within end of every year during Implementation, warranty & AMC period. The report shall contains at leastfollowing:

….

iv. Audit Report - In Depth Analysis of findings /Corrective Measures & Recommendations along with Risk Analysis: The findings of the entireaudit Process should be critically analyzed and controls should be suggested as corrective /preventive measures for strengthening / safeguardingthe Telecom assets of POWERGRID utilities against existing and future threats in the short /long term. Report should contain suggestions/recommendations for improvement in the systems wherever required. If recommendations for Risk Mitigation/ Removal could not beimplemented as suggested, alternate solutions shall be provided. Also, if the formal procedures are not in place for any activity, evaluate theprocess & the associated risks and give recommendations for improvement as per the best practices.

Comment: Entire communication infrastructure not alone POWERGRID


2.10 IT Setup:

New addition:

Proposed system shall have facility for the VPN connectivity for remote access for authorized personnel andnecessary cyber security provisions in line with CERT-IN Guidelines shall be in place for such VPNConnectivity.

SUGGESTION

Documents

Southern Regional Power Committee, Bangalore - Kar