Date: November 15, 2019 E- Tender No. Smart Metering ... · including smart meters (with/without net-metering) with Pre-paid configuration, communication infrastructure along with

Clarifications to Queries against the Request for Proposal (RfP) for Selection of AMI Implementing Agency for implementation of Smart Metering in Shimla and Dharamsala City in Himachal Pradesh

Page 1 of 84

Date: November 15, 2019

E- Tender No. Smart_Metering/Himachal_Pradesh/A136 Date: 20.9.2019

Clarifications to Queries

with respect to

Request for Proposal (RfP)

for

Selection of AMI Implementing Agency

for

Implementation of Smart Metering

in

Shimla and Dharamsala City in Himachal Pradesh


Page 2 of 84

Clarifications with respect to RfP (Volume – I)

S.No Reference Clause Existing Provision Queries raised by Bidders Reply/Clarification

1. Volume-I

Important Dates and

Amounts

Pre-bid meeting - If meeting required, the

same would be intimated to bidders

It is requested to have a Pre-Bid Meeting to clarify queries.

Pre-Bid Meeting already

held on 24.10.2019.

2. Last date and time for online bidding – 21.11.2019 upto 15:00 hrs Last date and time for receipt of RFP - 21.11.2019 upto 15:00 hrs Technical Bid Opening - 21.11.2019 at

15:30 hrs

To prepare an exact estimation as per the requirement of RfP and to make our best competitive offer, the last date of bid submission may be further extended by at least 3 weeks

Please refer Amendment

No. 2 to RfP.

3. Please extend the Bid submission date to 4 weeks’ time from the date of issuance of clarifications

4. Transaction Fee (Non- Refundable) - Rs.

15,000 plus GST @18%

As per Annexure 16 of the RfP, we understand that the Transaction fee to be paid online. However, it is requested to clarify whether to Pay online or a Demand Draft is to be submitted along with the Bid.

Please refer S.No. 12 of

Annexure 16 of the RfP

which states the following:

“……A bidder can deposit

the transaction fee through

Debit Card/Credit card/Net

Banking by selecting the

online payment option or

through NETF/ RTGS.

Payment through online

mode is authorized

immediately while through

NEFT/RTGS is authorized

by the system upon receipt

of payment (this can take

approx. 1 working day)”

5. Bid Security as Demand Draft or Bank

Guarantee, valid for a period of 1 year

(Refundable) - Rs. 50,00,000

In this clause, the validity of Bid Security has been mentioned as 1 Year whereas in Clause 4.17 it has been mentioned that the bid security shall be valid for 120 days beyond the end of validity period of the bid. As the bid validity is for 6 Months from the submission of the Bid, the

The Bid Security would be

valid for a period of 120

days beyond the end of

validity period of the bid.


Page 3 of 84


validity of Bid Security would 10 Months from the date of submission of the Bid. It is requested to clarify the Bid Security validity period.

6. Please provide the estimated value of the RfP.

The Bidder to ascertain the

same on its own.

7. Volume-I

Clause 3.2 (About this

Request for Proposal)

HPSEB Ltd. proposes to implement Smart

Metering/ AMI Project in Shimla and

Dhramsala towns of Himachal Pradesh for

around 1.50 lakh consumers

Please clarify whether the quantity mentioned in this RfP will be scattered in entire Shimla and Dharamsala Cities or it will be specific to any Sub-division. Kindly provide Consumer list/ index as this will help Bidders in assessing precise Resource requirements and Costing. Please clarify whether these are

replacement Meters or New

connections.

The meters have to be

installed in Shimla and

Dharamshala.

Further, all existing meters

are to be replaced and any

new connection will also be

on Smart Meter.

8. Volume-I

Clause 3.3 (About the

AMI Project)

This Request for Proposal (this “RFP”) is

issued by PFCCL on behalf of HPSEB Ltd.

for selecting a Consortium or a Contractor

for supply, installation, testing,

commissioning and maintenance of

Advanced Metering Infrastructure,

including smart meters (with/without net-

metering) with Pre-paid configuration,

communication infrastructure along with

applications for Head End System (HES),

Meter Data Management (MDM) System

for rolling out around 1,35,000 Smart

Metering (plus additional installation of

smart meters as per new connection

requirement in Operation and

As per BOQ and RFP Vol-I, section 3.2, the total no. of smart meter is 1.50 Lakh. But as per the clause in RFP Vol-I Section 3.3, Annexure G and RFP Vol-II Section 1.2 the total no. of smart meter is 1.35 Lakh. Please confirm the numbers of smart meters/ nodes and amend the clause appropriately.

The no. of nodes would be

as per Price Bid Format

(Annexure 17) with 20%

expansion for future

requirement.


Page 4 of 84


Maintenance (O&M) period)……

9. Volume-I

Clause 4.2.6 (General

Terms for Bidding)

PFCCL may, at its sole discretion, ask for

additional information/ document and/ or

seek clarifications from a Bidder after the

Bid Submission Deadline, inter alia, for the

purposes of removal of inconsistencies or

infirmities in its Bid. However, no change

in the substance of the Financial Bid shall

be permitted by PFCCL, unless

specifically sought by PFCCL as per

Clause 4.15.9

Clause No. 4.15.9 is not available in this RfP. Please clarify.


No. 2 to RfP.

10. Volume-I

Clause 4.3.1 (Qualifying

Requirement)

…………… Bidder must meet the following

minimum eligibility requirements

individually and in case of a consortium,

collectively by the members of

Consortium, except where specifically

mentioned………….

Please allow EPC Mode for participation

in the bid process in a manner similar to

the tender issued by Jammu & Kashmir

Power Development Department.

The provisions of the RfP

shall prevail.

11. Volume-I

Clause 4.3.1 (Qualifying

Requirement)

….. The Bidder would be required to furnish along with the bid, a letter of undertaking from the Holding Company/ Subsidiary Company/ Sub-Contractors supported by Board resolution, extending support for execution of the contract by the bidder in case of award. Bidders can use credentials of the Sub-Contractors for meeting the Qualifying Requirement. However, multiple bidders can use credentials of the same Sub-Contractors subject to the condition that a Sub-Contractor cannot participate as Bidder/ Consortium Member in the bid process. The bidder has to submit detailed roles & responsibilities of the Consortium

Please confirm whether the

requirement of submission of a letter

of undertaking supported by Board

resolution, extending support for

execution of the contract by the bidder

in case of award can be fulfilled with

MAF in case of subcontractors. If not,

please specify a format for the same.

The Bidder can submit the

Manufacturer Authorization

for sub-contractors as per

their own format. But, it

must fulfil the requirement

of the RfP to meet the

Qualification Requirement

12. Please share the Manufacturer

Authorization Format

13. Please clarify whether a System

Integrator can bring in Sub

Contractors who meet the Qualification

Criteria as mentioned in 4.3.1 A) Meter

Manufacturer, B) Communication

Network and D) Meter Data

The Meter Manufacturer/

Supplier has to be part of

the Consortium (not

necessarily as a Lead

Bidder).

The bidder can bring in


Page 5 of 84


Members/ Sub-Contractor partners to PFCCL along with the bid……….. In case Bidder does not manufacture or produce any major equipment or component of the overall Solution to be provided as the Scope of Work, then the Bidder is required to submit the Manufacturer’s /OEM’s Authorization stating the required support from the Manufacturer/OEM with respect to supply, support, etc for a period of seven (7) years from the date of operational acceptance of the system by PFCCL/ HPSEB Ltd…… Basis the Public Procurement Policy for Micro and Small Enterprises (MSEs) Order by GoI dated March 23, 2012, it has been decided to give opportunity to Micro & Small Enterprises (MSEs) registered with National Small Industries Corporation (NSIC) (under Single Point Registration Scheme) through NSIC-Consortium route. In light of this, the Bidder shall source meters (as bought out) or downstream components of the meters from MSEs of value greater than or equal to 20% of the metering component of the contract price. Out of this requirement of minimum 20% procurement from MSEs, 4% is earmarked for units owned by Schedule Caste /Schedule Tribes…. For startup firms, gazette notification dated 17 Feb 2016, G.S.R. 180(E) and policy circular No. 1(2)(1)/2016-MA dated 10 March 2016, and the subsequently issued guidelines shall be considered for waiving off respective qualifying requirements for

Management. It is requested to allow the

same as this would increase the

competition.

other agencies as sub-

contractors in line with the

RfP.

14. Lead bidder should be in the business

of manufacturing and supplying (OEM)

digital electricity pre-paid meter/

electricity smart meters in the

preceding three (3) completed Financial

Years.

15. We understand that Communication

service provider can also participate

as Sub Contractor and provide

solution to multiple bidders.

The understanding of the

bidder is correct.

16. We understand that System Integrator

and Meter data Management provider

can participate as sub-contractors

17. Distribution Licensee may be allowed

to participate in the bid


shall prevail. Please also

refer Amendment No. 2

regarding Modified

Qualification Requirement

18. Please clarify whether a Distribution

Licensee can participate as a Lead

Bidder and have eligible Meter

Suppliers/ System Integrators as sub-

contractors

19. Global experience of Bidders may be

accepted


shall prevail.

20. All PSUs and Govt. department should

be exempted from purchase fee for the

RFP, tender fee & Bid security/EMD.

As per GFR 2017, all MSEs, should be

exempted from purchase fee, Tender

Fee & Bid security/EMD.

For claiming this exemption, MSE must

provide proof of being registered as MSE


shall prevail.


Page 6 of 84


sourcing of meters subject to mandatorily meeting quality and technical specifications as specified in Volume-1 and Volume-2 of this RFP….

with any agency mentioned in the

notification of Ministry of MSME indicated

below:

a. Khadi and Village Industries

Commission.

b. Khadi and Village Industries Board

c. Coir Board

d. National Small Industries Corporation

e. Directorate of handcraft and handloom

f. Udyog Aadhar Memorandum issued

by Ministry of MSF or any other body

specified by Ministry of MSME

21. Volume-I

Clause 4.3.1(A)(1)(a)

(Qualifying Requirement-

QR For Meter

Manufacturing -

Technical Experience)

The Bidder/ consortium member must have i. Manufactured and supplied minimum

40,000 nos. of Meters for AMI (cumulative) with required hardware, software and other associated accessories etc. in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP

Or

ii. Manufactured and supplied minimum 10,000 nos. of Pre-paid Meters with cellular/ RF communication with required hardware, software and other associated accessories etc. in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP

The clause may be modified as per the

following:

“The Bidder/ consortium member must

have

i. Manufactured and supplied minimum 40,000 nos. of Meters for AMI (cumulative) out of which 50% should be installed with required hardware, software and other associated accessories etc. by the

Bidder/ consortium member in

Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP

Or ii. Manufactured and supplied minimum

10,000 nos. of Pre-paid Meters with cellular/ RF communication out of which 50% should be installed with required hardware, software/ Cloud services and other associated

accessories etc. by the Bidder/ consortium member in Indian


No. 2 to RfP.


Page 7 of 84


Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP

22. Please reduce the minimum quantity to

30,000 no. of meters. Markings under

Tender Evaluations methodology

should be changed accordingly.


No. 2 to RfP.

23. As smart meters have been very recently introduced in Indian Power utilities, please also consider experience of digital electricity meters/ unidirectional static energy meters.


No. 2 to RfP.

24. The quantum of meters for AMI to 10000


No. 2 to RfP.

25. The clause may be modified as per the

following:

i. “Manufactured and supplied minimum

40,000 nos. of Meters for AMI/ AMR (cumulative) with required hardware, software and other associated accessories etc. in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP

Or

ii. Manufactured and supplied minimum 10,000 nos. of Pre-paid Meters with cellular/ RF communication with required hardware, software and other associated accessories etc. in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP”


No. 2 to RfP.

26. Volume-I

Clause 4.3.1(A)(1)(b)

The Bidder/ consortium member must have manufacturing facility in India with an in-house NABL accredited lab since last two years (i.e. FY 2017-18 onwards)

Please consider the manufacturer which has testing & calibration equipment traceable to NABL accredited laboratory to ensure accurate testing calibration as


No. 2 to RfP


Page 8 of 84



QR For Meter

Manufacturing -

Technical Experience)

per IS 16444/13779 for acceptance test.


following:

“The Bidder/ consortium member must have manufacturing facility in India with an in-house NABL accredited lab or equivalent certification before commencement of supply since last two years (i.e. FY 2017-18 onwards)”


following:


have manufacturing facility in India with

an in-house NABL accredited lab since

last two years (i.e. FY 2017-18

onwards) life time membership of

NABL accredited lab/Valid certificate

of in house accredited LAB.

or

Self-declaration of submission of In

house NABL certified lab certificate

within 3 months from date of award of

contract, failing which Performance

Security shall be forfeited.”


following:


have manufacturing facility in India with

an in-house NABL accredited lab or a tie

up with a NABL Lab”

30. Volume-I

Clause 4.3.1(B)


In case of a consortium, this requirement

has to be met individually by one of the

consortium members in its entirety

In Qualifying Requirement as well as the Tender Evaluation Methodology, the Bidder/ Consortium member should fulfil the Qualifying Requirement.


bidder is correct.


Page 9 of 84


QR For Communications

Network)

Accordingly, it would be the

Communication Service Provider

which has to fulfil the Qualifying

Requirement.

31. Volume-I

Clause 4.3.1(B)(1)


QR For Communications

Network)

1.

a) The Bidder/ consortium member should

have implemented project(s) with at

least 40,000 (cumulatively)

communication module/ endpoints

(manufacturing, supply, installation,

integration, maintenance &

management) involving Radio

Frequency (RF) mesh in Licensed

frequency band as permitted by WPC

or in Unlicensed frequency band in

India in the last 7 years (i.e. FY 2012-13

onwards) till the date of issuance of this

RfP.

b) The Bidder/ consortium member must

have successfully integrated their NIC/

Communication module with meters of

at least 3 manufacturers in India till

HES and/or MDMS.

2.

a) Bidder/ consortium member should be

ISO 9001:2008 certified or Bidder

should have CMMI Level 3 (minimum)

certification.

b) Bidder/ consortium member should

have ISO 14001 and ISO 27001

certifications

As implementation of only limited projects of Smart Grid with RF Communication has taken place in India, please accept the vendors who have experience in successfully implementing RF communication with 40,000 end points in India or abroad.


shall prevail.


following:

a) “The Bidder/ consortium member

should have implemented project(s)

with at least 40,000 (cumulatively)

communication module/ endpoints

(manufacturing, supply, installation,

integration, maintenance &

management) involving GPRS or

Radio Frequency (RF) mesh in

Licensed frequency band as permitted

by WPC or in Unlicensed frequency

band in India in the last 7 years (i.e.

FY 2012-13 onwards) till the date of

issuance of this RfP.

b) The Bidder/ consortium member must

have successfully integrated their

GPRS/ NIC/ Communication module

with meters of at least 3 manufacturers

in India till HES and/or MDMS.”


shall prevail.


30,000 no. communication module/

endpoints. Markings under Tender


No. 2 to RfP.


Page 10 of 84


Evaluations methodology should be

changed accordingly.


10,000 no. communication module/

endpoints. Markings under Tender

Evaluations methodology should be

changed accordingly.


No. 2 to RfP.

35. Please allow integration of NIC/

Communication module with meters of at

least 2 manufacturers in India till HES

and/or MDMS instead of 3

manufacturers


shall prevail.

36. Please change the scope of RF solution provider to Supply & Integration since in all the previous AMR tenders, the scope for RF supplier was only manufacturing and Supply whereas from installation to management was taken care by meter supplier. Alternatively, we would suggest to make it valid cumulatively for all consortium partners


shall prevail.

37. Please accept ISO 9001:2015 instead of ISO 9001:2008 since 2015 is an upgradation to 2008


No. 2 to RfP.

38. The Bidder should be allowed to have a valid ISO/CMMi certificate on or before the date of bid instead of date of publication of RfP.


No. 2 to RfP.

39. Volume-I

Clause 4.3.1(C)(1)


QR For System

Integration - Technical

a) The Bidder/ consortium member must

have experience of integration of HES

with MDM on standard interfaces and

data exchange models (CIM/XML) for

at least 40,000 consumers

(cumulatively) in Indian Power

As this RFP involves implementation of core AMI applications (HES and MDMS) on the cloud, bidders’ credentials in supply, installation, testing and commissioning of control centre hardware may not be relevant. Seeking credentials of bidders who have implemented the proposed solutions (HES, MDMS) on


No. 2 to RfP.


Page 11 of 84


Experience of Integration

with MDM)

Distribution Utility(s) in the last 7 years

(i.e. FY 2012-13 onwards) till the date

of issuance of this RfP.

b) The Bidder/ consortium member should

have supplied, installed, tested and

commissioned Control Centre

hardware and application software for

at least 40,000 end points

(cumulatively) in Indian Power

Distribution Utility(s) in the last 7 years

(i.e. FY 2012-13 onwards) till the date

of issuance of RfP which are in

successful operation for at least One

(1) year.

Evaluation Document Required:

i. Contract/ Purchase Order (PO)/ Work

Order (WO) indicating client name,

scope of work, period of work etc.

ii. Certificate from the client on successful

implementation and operation of the

project.

cloud may ensure to get bidders who have requisite experience involving cloud. We believe that testing the “implementation” experience (and not just integration experience) on proposed product will ensure that PFCCL gets the bidders with required competence to ensure project success. Please relax the “operational for 1 year” part as well. Accordingly, the clause may be amended as per the following: “The Bidder/ consortium member should have supplied, installed, tested and commissioned proposed HES and MDMS on cloud Control Centre hardware and application software for at least 40,000 end points (cumulatively) in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of RfP which are in successful operation for at least One (1) year.”

40. As implementation of only limited projects of Smart Grid has taken place in India, requirement of 40000 end points/ consumers may be reduced to 20000. Markings under Tender Evaluations methodology should be changed accordingly.


shall prevail.

41. Experience to be sought till the date of submission of bid instead of date of issuance of RfP


shall prevail.

42. Please amend Sub-Clause (b) as per the following: “The Bidder/ consortium member should have supplied, installed, tested and


shall prevail.


Page 12 of 84


commissioned Control Centre hardware and application software for at least 40,000 end points (cumulatively) in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of RfP which are in successful operation for at least One (1) year.”

43. Following additional evaluation

Document may be sought:

i. In case the System Integrator is a

Power Distribution Utility which is

having an in house experience,

self-certification from authorized

signatory of the System Integrator

shall be acceptable.


No. 2 to RfP.


30,000 no. of consumers. Markings

under Tender Evaluations

methodology should be changed

accordingly.


No. 2 to RfP.

45. Volume-I

Clause 4.3.1(C)(2)


QR For System

Integration - Technical

Experience as Cloud

Service Provider and

Quality Certification)

a) Bidder/ consortium member must be

Empaneled Cloud Service Provider by

DEITY (Department of Electronics and

Information Technology) for Public

cloud, Virtual Private Cloud and

Community Government Cloud

b) Bidder/ consortium member must have

at least 3 Data Centers in at least two

different seismic zones in India

c) Bidder/ consortium member should have

at least 5 different Internet Carrier

Terminating

d) Bidder/ consortium member should be

As the experience can be met by a cloud

service provider, kindly make this as a

separate Qualification Requirement for

“Cloud Service Provider” and the

bidder may be allowed to propose

“Cloud Service Provider” as Sub

Contractor who meets the Qualification

Requirement.

It is suggested that the following

Qualification Requirement can be

mentioned:

“Bidder/ Consortium member should


No. 2 to RfP.


Page 13 of 84


having the capability to provide Hybrid

Cloud services, i.e. a combination of

Bare Metal/ Private Cloud and Public

Cloud infrastructure from each

availability zone.

e) Cloud services should be supported with

committed performance driven storage

offering (Committed Storage on cloud)

f) Bidder/ consortium member should have

at least two (2) Work Orders from

Central Government/ State Government/

PSU /Semi- Government of India in the

last 7 years (i.e. FY 2012-13 onwards)

till the date of issuance of this RfP.

Bidder/ consortium member should have

the following Quality Certifications:

i. ISO/IEC 27001certified for Information Security with well-planned and structured escalation procedures

ii. Certified ISO/IEC 20000-1 for DC service quality and delivery

iii. Certified for minimum of Tier III level against TIA-942 specifications

iv. Must have Government Community Cloud running audited and successfully audited by STQC.

have experience of executing

AMI/AMR/RMS projects on Cloud/ On

premises DC, DR similar to that

proposed in RFP in Indian Power

Distribution Utility(s) in the last 7

years”

46. It is suggested that bidder’s credentials in

implementation of HES, MDM on cloud

should be verified while the cloud

services are procured from a sub-

contractor. As a cloud vendor is generally

not a System Integrator, please remove

this clause from QR for System Integrator

criteria.

47. Please confirm whether CSP should be MEITY Empanelled


bidder is correct.

48. The documents from clients may not be insisted upon as arranging documents for old projects would be difficult


shall prevail.

49. Please consider at least 2 Data Centers (instead of 3) in at least two different seismic zones in India


shall prevail.

50. Since the Telecom market has undergone consolidation (for e.g. Idea and Vodafone have merged), very few ISPs are left in the market. We request to please reduce the number of ISP from 5 to 4 different ISP


shall prevail.

51. Please clarify whether the clause “Cloud services should be supported with committed performance driven storage offering (Committed Storage on cloud)” means committed IOPS

Understanding of bidder is

correct

52. Please remove the requirement of the

Quality Certifications mentioned in The provisions of the RfP


Page 14 of 84


the RfP. shall prevail.

53. Please remove S.No. (b) to (f) and S.No. (iv)


shall prevail.

54. Volume-I

Clause 4.3.1(D)(1)


QR For Meter Data

Management Provider -

Data Handling

Capability)

The Bidder/ consortium member should

have successfully implemented/ under

implementation and integrated with HES

for at-least 40,000 numbers of smart

meter/ AMI system with connect/

disconnect features with two-way

communication in a single project in any

Indian Power Distribution Utility in the last

7 years (i.e. FY 2012-13 onwards) till the

date of issuance of this RfP.

Evaluation Document Required:

i. Contract/ Purchase Order (PO)/

Work Order (WO) indicating client

name, scope of work, period of work

etc.

ii. Certificate from the client on

successful implementation on and

operation of the project.

It may be appreciated that the core

functionalities of Meter Data Management

(MDM) are not Data Acquisition as the

same is handled by HES. All the meters

installed for high value consumers like

LTCT, HT and whole current meters also

have 15 minutes interval data. The

capabilities of MDM are to store and

process the meter data and not

communication which is handled by HES

etc.

Accordingly, the clause may be amended

as per the following:

“The Bidder/ consortium member should

have successfully implemented/ under

implementation and integrated with HES

for at-least 40,000 numbers of smart

meter/ AMI system/ LTCT/HTCT Meters

with connect/ disconnect features with

two-way communication in a single

project or cumulatively in any Indian

Power Distribution Utility in the last 7

years (i.e. FY 2012-13 onwards) till the

date of issuance of this RfP.”


No. 2 to RfP.

55. The clause may be amended as per the

following:

“The Bidder/ consortium member should have successfully implemented/ under implementation and integrated with HES for at-least 40,000 numbers of smart


Page 15 of 84


meter/ AMI/ AMR system with connect/ disconnect features with two-way communication in a single project in any Indian Power Distribution Utility in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP.”

56. As MDM is the critical component of the project and the success of the entire project depends on its success, it is essential to ensure that MDM provided is having proven implementation experience on proposed product. Accordingly, the clause may be amended as per the following: “The Bidder/ consortium member should

have successfully implemented the

proposed MDM/ under implementation

and integrated with HES for at-least

40,000 numbers of smart meter/ AMI

system with connect/ disconnect features

with two-way communication in a single

project in any Indian Power Distribution

Utility in the last 7 years (i.e. FY 2012-13

onwards) till the date of issuance of this

RFP.”

57. As implementation of only limited projects of Smart Grid has taken place in India, requirement of 40000 number of meters may be reduced to 20000


shall prevail.

58. Please make this as part of Qualifying Requirement of System Integrator and remove from Qualifying Requirement of MDM Provider


shall prevail.

59. Following additional evaluation

Document may be sought:


No. 2 to RfP.


Page 16 of 84


In case the System Integrator is a Power Distribution Utility which is having an in house experience, self-certification from authorized signatory of the System Integrator shall be acceptable.

60. Please reduce the minimum quantity to 30,000 no. of meters. Markings under Tender Evaluations methodology should be changed accordingly.


shall prevail.

61. The Proposed MDM should have been

Integrated with minimum 3 different Head

End Systems / MDAS system and 2

different billing system in any Indian Power

Distribution Utility in the last 7 years (i.e.

FY 2012-13 onwards) till the date of

issuance of this RfP

The clause may be amended as per the following: “The Proposed MDM should have been Integrated with minimum 2 3 different Head End Systems / MDAS system and 1 2 different billing system in any Indian Power Distribution Utility in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP”


shall prevail.

62. a) The Bidder/ consortium member

should be an ISO

9001:2008 certified.

b) Bidder should have CMMI Level 3

(minimum) certification.

c) Bidder should have ISO 14001 and ISO 27001 certification

As ISO 14001 is an environmental certification which is relevant for manufacturing companies and not for IT product/services companies, please remove it. Instead ISO 20000 can be used as ISO 20000 checks for IT competency and ensures that MDM provider has strong support mechanism. Further, please consider CMMi Level 5. Accordingly, the clause may be amended as per the following: “ a) The Bidder/ consortium member

should be an ISO

9001:2008 certified.


No. 2 to RfP.


Page 17 of 84


b) Bidder should have CMMI Level 5 3

(minimum) certification.

c) Bidder should have ISO 20000 ISO

14001 and ISO 27001 certification”

63. Volume-I

Clause 4.3.1(E)(a)


Financial Requirement)

Net Worth in best Three Financial Years

out of the last five years (i.e. FY 2014-15

onwards) should be positive. Net worth

shall be as defined under the Companies

Act, 2013


following:

“Net Worth for the last three financial

years should be positive. Net worth

means sum total of the paid up capital

and free reserves (excluding reserves

created out of revaluation) reduced by

aggregate value of accumulated

losses (including debit balance in

profit and loss account for current

year) and intangible assets.”


shall prevail.

64. Volume-I

Clause 4.3.1(E)(b)


Financial Requirement)

Minimum Average Annual Turnover

(MAAT) of the bidder (Average of best

Three Financial Years out of the Last Five

Financial Years i.e. FY 2014- 15 onwards)

should not be less than INR 100 Cr. MAAT

means annual total income as

incorporated in the profit & loss account

except non-recurring income e.g. sale of

fixed assets

The MAAT requirement may be INR 80

Cr as MAAT instead of 100 Cr


shall prevail.

65. The MAAT requirement may be INR

150 Cr as MAAT instead of 100 Cr

66. The MAAT requirement may be INR

400 Cr as MAAT instead of 100 Cr

67. Volume-I

Clause 4.3.2.1

(Consortium Bids)

In case a bid is submitted by a consortium

of two or more firms (No. of members shall

not be more than 3) as consortium

members, the members of consortium

shall meet the following requirements:

a. All the members of the consortium shall

meet individually the financial

requirement criteria given at 4.3.1.D.1

(a) above.

It seems there is a typographical error in mentioning clause nos. 4.3.1.D.1 (a) and 4.3.1.D.1 (b) instead of 4.3.1.E.1 (a) and 4.3.1.E.1 (b). Please amend the clause.


No. 2 to RfP.

68. Please amend the clause as per the following: “In case a bid is submitted by a

consortium of two or more firms (No. of


shall prevail.


Page 18 of 84


b. The Lead Consortium Member shall

meet not less than 50% of the

minimum financial requirement criteria

given at clause no. 4.3.1.D.1 (b) above.

c. Each of the other Consortium

Member(s) individually shall meet not

less than 25% of the minimum financial

requirement criteria given at clause no.

4.3.1.D.1 (b) above.

members shall not be more than 3) as

consortium members, the members of

consortium shall meet the following

requirements:

a. All the members of the consortium

shall meet individually the financial

requirement criteria given at 4.3.1.E.1

(a) above.

b. The Lead Consortium Member shall

meet not less than 50% (in case of

MSE 20%) of the minimum financial

requirement criteria given at clause

no. 4.3.1.E.1 (b) above.

c. Each of the other Consortium

Member(s) individually shall meet not

less than 20% 25% of the minimum

financial requirement criteria given at

clause no. 4.3.1.E.1 (b) above.”

69. Volume-I

Clause 4.3.2.7

(Consortium Bids)

Each member of the consortium shall have

a registered office (under the Companies

Act 1956 with Registrar of Companies) and

operations in India

Please amend the clause as per the following: “Each member of the consortium shall have a registered office (under partnership firm / under the Companies Act 1956 with Registrar of Companies) and operations in India” Self-attested copies of Certificate of incorporation /Self attested copies of Partnership Deed should be accepted.


shall prevail.

70. Volume-I

Clause 4.3.2.9

(Consortium Bids)

Bidder/ member of consortium should not

be blacklisted/ barred by any Govt.

Organization or Regulatory Agencies or

Govt. Undertaking. Bidder should submit a

self- undertaking signed by its Authorized

Signatories for same as per format

This clause may be restricted to HPSEB only i.e. Bidder/Member of consortium should not be blacklisted/ debarred by HPSEB, as sometimes blacklisting is done on frivolous grounds without going into the merits of the case.


shall prevail.


Page 19 of 84


prescribed in Annexure 3. It is important to mention that most of the States mention a condition in their RfPs that the bidder should not be blacklisted/ debarred from the Discoms/ associated Discoms of the State issuing the RfP.

71. Volume-I

Clause 4.7.8

(Compliance)

….. Bidders are free to list more than one

Subcontractor against each item of the

facilities except for core components of

AMI like RF Communication, MDM, HES,

Cloud.

Please allow multiple subcontractors for Cloud Service Provider Package


shall prevail.

72. Volume-I

Clause 4.7.9

(Compliance)

PFCCL reserves the right to remove any

proposed subcontractor of the Bidder prior

to award of any work related to either the

Bidding or Project, or during the work,

without assigning any reason thereof

Please remove the clause The provisions of the RfP

shall prevail.

73. Volume-I

Clause 4.12.3 (Method of

Submission of Bid)

In addition to the electronic submission, the

Bidder shall also provide 1 no. of hard

copy/(ies) of the Technical Bid to PFCCL in

a sealed envelope before the Bid

Submission Deadline at PFC Consulting

Ltd. 9th Floor, A-Wing, Statesman House,

Connaught Place, New Delhi – 110 001

Please remove requirement of Hardcopy Submission.

The bidder is also required

to submit a Hard Copy of

the bid along with

submission of the same on

the e-bidding portal as

mentioned in the RfP.

74. Volume-I

Clause 4.9.3

(Clarifications)

Any such clarifications issued shall be sent

to all the Bidders to whom the RFP has

been issued

As per Clause B of Notice Inviting Tender, the RFP can be directly downloaded free of cost from www.pfcclindia.com and Tender fee can be submitted along with Bid document. However, Clause 4.9.3 (Page No. 36) states that PFCCL will issue RFP. Please clarify whether PFCCL will issue RFP document’s hard copy in advance.

The RfP has already been

issued by PFCCL and

uploaded on PFCC’s

website

www.pfcclindia.com and e-

bidding portal

www.mstcecommerce.com/

eprochome/pfccl.

75. Volume-I

The Financial Bid shall clearly indicate the

cost of all hardware, software, services,

Please clarify whether Bidder can quote for any one of the selected cities i.e.

The Bidders have to quote

for the entire quantity for

http://www.pfcclindia.com/

http://www.pfcclindia.com/

http://www.mstcecommerce.com/eprochome/pfccl

http://www.mstcecommerce.com/eprochome/pfccl


Page 20 of 84


Clause 4.15.2 (Financial

Bid)

operation, maintenance, recurring costs,

taxes, duties, levies, cess and all other

costs that contribute to the installation,

operation and maintenance of the

Project…..

either Shimla or Dharamsala or Partial quantity.

both the cities.

76. Volume-I

Clause 4.15.9 (Financial

Bid)

Reverse Auction: PFCCL reserves the

right to conduct the reverse auction (if

required) for the products/ services being

asked in the tender. The terms and

conditions for such reverse auction event

shall be as per the Acceptance Form

attached as Annexure - B of this document.

The bidders shall mandatorily submit a

duly signed copy of the Acceptance Form

along with the tender document as a token

of acceptance

Please remove the Reverse Auction Clause

The will be no reverse

auction.

77. Volume-I

Clause 5.1.2 (Overview

Bid Evaluation Process)

The Bid submitted by the Bidder shall

consist of a Technical Bid and a Financial

Bid. The Technical Bid shall be submitted

as a hard and soft copy to PFCCL, while

the Financial Bid shall only be submitted

electronically.

As this is e-tender, kindly confirm whether

the hard copy is also to be submitted.

The bidder is also required

to submit a Hard Copy of

the bid along with

submission of the same on

the e-bidding portal as


78. Volume-I

Clause 5.1.4.1 (Overview

Bid Evaluation Process -

Second Stage-Technical

Evaluation for Project

Implementing

Consortium)

The Technical Bids of all Bidders

qualifying the Eligibility Criteria shall be

scored based on the criteria including but

not limited to volume, reliability and timely

delivery of similar work done, as outlined

in Clause 4.3.1. The bidders scoring more

than 70 marks out of 100 as described in

technical bid evaluation (Annexure A) shall

qualify for the next stage of evaluation

Please reduce the qualifying marks to

60


shall prevail.

79. Please reduce the qualifying marks to

50


shall prevail.

80. Volume-I

At the time the Contract is awarded, the

quantity indicated in the BoQ of the

Negative Quantity variation is not possible after execution of project. Please remove the word "Decrease"


shall prevail.


Page 21 of 84


Clause 5.9.2 (Award of

Contract)

Financial Bid shall not be modified.

However, PFCCL reserves the right to

increase or decrease the number of items

under this contract upto 1 year after

project implementation i.e. till completion

of first year of FMS period, subject to the

limit of 20% of the existing number of

items, covered under the Contract, without

any change in the unit prices or other

terms and conditions of the RFP and the

Bid

from this clause.

81. Volume-I

Clause 5.9.7 (Award of

Contract)

The successful Bidder shall provide an

undertaking that the key staff identified for

the project (as submitted in its Technical

Bid) shall be available for the respective

proposed work requirement, anytime

during the duration of the Project, till its

successful completion.

Please amend the clause as per the following: “The successful Bidder shall provide an

undertaking that the key staff identified

for the project (as submitted in its

Technical Bid) shall be available for the

respective proposed work requirement,

anytime during the duration of the

Project, till its successful completion. If

due to any circumstances the key staff

is not available for the project, a

similar experienced key staff will be

replaced with approval of PFCCL.”


No. 2 to RfP.

82. Volume-I


Conditions of Contract -

Interpretation)

In the event of an inconsistency between

the terms of the RFP, Bid document and

the subsequent Contract, the terms of this

RFP hereof shall prevail

Please amend the clause as per the following: “In the event of an inconsistency between the terms of the RFP, Bid document and the subsequent Contract, the terms of Contract RFP shall prevail.”


shall prevail.

83. Volume-I

Clause 6.16(h)

(HPSEB’s

Provide necessary support to Contractor,

as may be required, in relation to

(amongst others) access to HPSEB’s/

consumers premises, installation of AMI

We understand that PFCCL/ HPSEBL will arrange Consumer approvals and Power Supply arrangement (including Power consumption) to install and operate DCU/ Router (AMI

HPSEB would provide all

necessary support to the

Contractor in line with the

RfP.


Page 22 of 84


Responsibilities) infrastructure, repair and maintenance

services, signing of ownership and license

agreements with the HPSEB’s/ consumers

Infrastructure).

84. Volume-I

Clause 6.16(l) (HPSEB’s

Responsibilities)

Allow Contractor to use existing power and

water supply and necessary equipment

required for civil construction (if applicable)

We understand there is no Civil work in the scope of Bidder.

There is no civil work

involved in the scope of

Bidder. However, minor

Civil works associated with

the installation of the smart

meters such as pointing,

grouting, mortar touch-ups,

carpentry, etc., are to be

done by the Bidder, if

required.

85. Volume-I

Clause 6.18.6 (Terms of

Payment)

Payments shall be made promptly by

PFCCL, no later than fifty (50) days after

submission of an invoice or request for

payment by Lead Consortium Member,

and PFCCL has accepted it. No interest

shall be paid by PFCCL on delayed

payments

Please amend the clause as per the following: “Payments shall be made promptly by PFCCL, no later than fifty (50) thirty (30) days after submission of an invoice or request for payment by Lead Consortium Member, and PFCCL has accepted it. No interest shall be paid by PFCCL on delayed payments.”


shall prevail.

86. Volume-I

Clause 6.19 (Payment

Schedule)

Payment Schedule There is no provision for quoting the

FMS charges during the Installation

and Commissioning period (first 24

months of Project) for the meters that

have been successfully installed and

commissioned.

The Milestone “2” can only be achieved

after successful commissioning of the all

the IT infrastructure and 5% of Smart

Meters and once the Cloud Infrastructure

is commissioned there would be recurring

charges for the IT infrastructure and FMS


No. 2 to RfP.


Page 23 of 84


charges for the metes installed, as these

need to be maintained until the project

achieves “Go Live”.

It is requested to consider and issue the

clarification/ amendment.

87. Please changes the lot size to 28 lots of 5000 smart meters instead of 14 lots of 10000 smart meters

88. The Payment terms are stringent. For healthy cash flow and timely completion of the Project, it is requested to keep the following payment terms: i. Advance Payment: 10% of total

value of contract including GST (Supply & Installation) as “Mobilization Advance” after signing the contract with PFCCL / HPSEBL.

ii. Supply Payment: Balance 90%

including GST against delivery of material in HPSEBL Stores.

iii. Installation & Commissioning

Payment: Balance 90% including GST on Prorata basis against Installation and Commissioning.

iv. FMS: 100% including GST on Monthly

basis against submission of bills.

89. It may be appreciated that manufacturers make advance payment to their suppliers and as per payment schedule of the RfP, it would have huge cost impact on project and will increase the bid price.


Page 24 of 84


Hence, the payment schedule may be modified as per the following to make the bid more competitive: “Supply: (a) 60% supply + 100% taxes against the supply of the material on pro-rata basis. (b) 30% of supply payment shall be released along with installation on pro-rata basis. (c) 10% payment on completion of installation and integration. Installation: (a) 90% of supply payment shall be released along with installation on pro-rata basis. (b) 10% payment on completion of installation and integration. Operation & Maintenance payment: FMS charges will be paid quarterly on pro rata basis against invoice and successful operation.”

90. Please modify the clause as per the following:

S.

No

Milestone Payment (%of

Contract Value

Excluding FMS

Charges)

1 Acceptance of Letter of Award (LoA), submission of Performance Security for project implementation as per clause 6.21.1.1, execution of Agreement between PFCCL and the Contractor and updation of PFC web portal regarding award details by PFCCL and approval of survey

2%


Page 25 of 84


reports of the entire project area.

2 Delivery, site installation and integration of first lot of 5% smart meters with related hardware, software and equipment and successful completion Field Installation and Integration Test (FIIT

20%

3 Delivery of smart meters along with related hardware, software and equipment at Project site after Factory Acceptance Test (FAT). This payment shall be released on pro-rata basis against successful delivery for each of the 14 lots of 10000 smart meters

48%

4 Against successful completion of Field Installation and Integration Test (FIIT) of each of the 14 lots of 10000 smart meters

10%

5 Installation, commissioning and integration of all AMI Hardware, Software, field material in Project Area and Site Acceptance test (SAT)

5%

6 3 months of Successful operation of AMI System as per SLA/ Guaranteed Performance Test (GPT) and operational acceptance.

5%

7 Completion of 7 years Facility Management Services (FMS) period

Yearly payments for FMS Period Year 1 to Year 7 (Total 10%) as per below: 2%,2%, 2%, 1%, 1%, 1% & 1%

Total 100%


Page 26 of 84


8 Charges towards FMS during FMS period of 7 years (to be initiated only after submission of Performance Security for FMS as per clause 6.21.1.2) (Total FMS charges for the period of 7 years should be minimum 20% of the Contract Value Excluding FMS Charges

On Quarterly basis on satisfactory completion of FMS.

91. Please modify the clause as per the following:

S.

No


Contract Value

Excluding FMS

Charges)

1 Acceptance of Letter of Award (LoA), submission of Performance Security for project implementation as per clause 6.21.1.1, execution of Agreement between PFCCL and the Contractor and updation of PFC web portal regarding award details by PFCCL and approval of survey reports of the entire project area.

10% of contract value along with 100% GST

2 Delivery, site installation and integration of first lot of 5% smart meters with related hardware, software and equipment and successful completion Field Installation and Integration Test (FIIT).


3 Delivery of smart meters along with related hardware, software and equipment at Project site after Factory Acceptance Test (FAT). This payment shall be released on pro-rata basis considering delivery, site installation and integration of 14 lots of 10000 smart meters each with related



Page 27 of 84


hardware, software & equipment after successful completion Field Installation and Integration Test (FIIT) of each lot.



5 3 months of Successful operation of AMI System as per SLA/ Guaranteed Performance Test (GPT) and operational acceptance.

-

6 Completion of 1st year FMS

2.5% every quarter along with 100% GST or PFCCL can pay 10% of retention value on submission of 10% BG of Retention value valid thru 1 year

7 Completion of balance 6 years Facility Management Services (FMS) period

Total 100%



In case delay occurs due to Utility issues, Site readiness, Local body issues, Weather conditions, Political changes, Public disturbances, Customer shall make upfront payment against milestone immediately. In case of delay in payment, Customer shall make interest bearing payment to contractor

92. Please modify the clause as per the


Page 28 of 84


following: S.

No


Contract Value

Excluding FMS

Charges)

1 Acceptance of Letter of Award (LoA), submission of Performance Security for project implementation as per clause 6.21.1.1, execution of Agreement between PFCCL and the Contractor and updation of PFC web portal regarding award details by PFCCL and approval of survey reports of the entire project area.

10%

2 Delivery, site installation and integration of first lot of 5% smart meters with related hardware, software and equipment and successful completion Field Installation and Integration Test (FIIT).

10%

3 Delivery of smart meters along with related hardware, software and equipment at Project site after Factory Acceptance Test (FAT). This payment shall be released on pro-rata basis considering delivery, site installation and integration of 14 lots of 10000 smart meters each with related hardware, software & equipment after successful completion Field Installation and Integration Test (FIIT) of each lot.

40%


10%

5 3 months of Successful 10%


Page 29 of 84


operation of AMI System as per SLA/ Guaranteed Performance Test (GPT) and operational acceptance.

6 Completion of 1st year FMS

10%

7 Completion of balance 6 years Facility Management Services (FMS) period

10%

Total 100%



In case delay occurs due to Utility issues, Site readiness, Local body issues, Weather conditions, Political changes, Public disturbances, Customer shall make upfront payment against milestone immediately. In case of delay in payment, Customer shall make interest bearing payment to contractor

93. The clause may be amended as per the following: “Supply of Equipment

Sixty Percent (60%) against receipt of Materials including 100% taxes (as applicable)

Thirty Percent (30%) – Lot wise installation and one (1) month meter reading data with minimum 95% availability in MDMs.

Ten Percent (10%) – Completion of next three (3) continuous month with at least 98%-meter reading data availability in MDMS & acceptance

Supply of Application License

Hundred(100%) against supply of


Page 30 of 84


license of Software Application(HES, MDM, Mobile App and Web portal) along with grant of End User License for software applications

Implementation

Ninety Percent (90%) including 100% Taxes (as applicable) against installation and 95% data availability for one month.

Ten Percent (10%) against Completion of next three (3) continuous monthly billing cycle with at least 98%-meter reading data availability

Erection & Integration

Thirty percent (30%) - against setting up of Application environment consist of HES & MDM in cloud infra and application demonstration to utility.

Forty Percent (40%) – Meters installed under one feeder are connected to application environment and receipt of three (3) months meter reading data with at least 95% availability at MDMs

Twenty Percent (20%) – All smart Meters as per BOQ are installed, commissioned and connected to HES, MDM Application over and Integrated with Existing Applications.

Ten Percent (10%) – Completion of next three (3) continuous monthly billing cycle with at least


Page 31 of 84


98%-meter reading data availability & user acceptance to the satisfaction/ approval of the Employee”

94. Volume-I

Clause 6.20 (Taxes &

Duties)

For goods supplied from outside India,

Contractor shall be entirely responsible for

all taxes, duties ……. Income tax at

source will be deducted by PFCCL as per

the applicable law and regulation and TDS

certificate shall be issued to the

Successful Bidder by PFCCL

For the Goods supplied, the vendor has

to submit the Invoice for the Full Value of

Goods, whereas he will receive payments

as per the milestones specified over the

project period.

It is requested to make “Full GST”

payments against the respective

Invoices submitted for Goods

Supplied and the Goods Cost

(excluding GST) can be paid on

milestone basis as specified. As per

the current clauses in the RfP, it would

inflate the costs and affect Cash Flow

and compliances.

In the tender issued by Jammu &

Kashmir Power Development

Department, the same has been

considered.


No. 2 to RfP.

95. General It is requested to confirm the applicability

of BOCW cess for this project.

If it is applicable, please clarify whether it

is 1% or 2% of Contract Value (including

GST). Accordingly, please make the

provision in price schedule to quote the

same.

Taxes & Duties would be as

per clause 6.20 of the RfP

96. Volume-I

Clause 6.21.1.1

Within fourteen (14) days of the

notification of Contract award, provide a

Performance Security for project

The validity of this BG should only be upto six months from the date of Operational Acceptance as the one


shall prevail.


Page 32 of 84


(Performance Security) implementation in the form of an

irrevocable Bank Guarantee valid up to a

period of six months after one (1) year

from the date of Operational Acceptance

of the project, or extended thereafter…..

year after that is already been covered in FMS period and would unnecessary increase the financial burden on the Bid.

97. Volume-I

Clause 6.21.1.2

(Performance Security)

Also submit a separate Performance

Security for FMS in form of an irrevocable

Bank Guarantee with value of 10%

Contract Value excluding FMS Cost plus

10% of FMS cost, valid for period of 6

months from date of completion of seven

year FMS or extended thereafter…...

The period of 7 years is too long. Accordingly, it is requested that Performance security may be accepted on yearly renewal basis.


shall prevail.

98. Please amend the clause as per the following: “Also submit a separate Performance Security for FMS in form of an irrevocable Bank Guarantee with value of 10% Contract Value excluding FMS Cost plus 10% of FMS cost, valid for period of 6 months from date of completion of seven year FMS or extended thereafter…...”


shall prevail.

99. Volume-I

Clause 6.28.1

(Insurance)

The Goods supplied under the Contract

shall be fully insured by the Contractor, in

INR, against loss or damage incidental to

manufacture or acquisition, transportation,

storage, and delivery, in the manner

specified in the RFP

We understand that once the material is delivered in HPSEB’s Stores, HPSEB’s standard Insurance Polices shall be applicable. It is requested to accept the same and amend the clause as once meters are installed in Consumer Premises, the Contractor does not have any control on the installed material.


shall prevail.

100. Volume-I

Clause 6.30.2

(Inspection and Tests)

The inspections and tests may be

conducted on the premises of the

Contractor, at point of delivery, and/or at

the final destination of the Goods, or in

another place in India as per the

requirement. Subject to Clause 6.30.3, if

conducted on the premises of the

Please note that Inspection and tests will be conducted at the Smart Meter factory only. Testing at site or outside premises is not possible. Accordingly, please remove this requirement.


shall prevail.


Page 33 of 84


Contractor or its Subcontractor, all

reasonable facilities and assistance,

including access to drawings and

production data, shall be furnished to the

inspectors at no charge to PFCCL/

HPSEB

101. Volume-I

Clause 6.31.1

(Liquidated Damages

and Penalty)

…if the Contractor fails to deliver any or all

of the Goods or perform the Related

Services within the period specified in the

Contract, PFCCL shall without prejudice to

all its other remedies under the Contract,

deduct from the Contract Price, as

liquidated damages, a sum equivalent to

0.5% of the value of the Goods or Related

Services of contract value for each week

or part thereof of delay until actual delivery

or performance, subject to a maximum of

10% of contract value, cumulatively for

entire sum of Liquidated Damages across

entire contract

In case of delay, LD shall be applicable only on undelivered/ delayed portion instead of on whole Contract Value. It is requested to amend the clause accordingly.


shall prevail.

102. It should be ensured that bidder will be obliged to pay LD only for his delay in work. Any delay caused due to PFCCL/ HPSEB shall not hamper the bidder. In case there is delay in project completion due to reasons not attributable to the contractor (eg. Delay in drawing approval, documentation, Site fronts availability, regulatory and statutory approvals, Certifications etc.), then the project completion date will be extended suitably without levy of liquidated damages/ penalties and additional cost incurred by the contractor on account of such delays shall be paid by PFCCL.


shall prevail.

103. Volume-I

Clause 6.32 (Warranty)

General As per this clause, warranty shall remain valid for 5 years after operational acceptance of the AMI system and for balance 2 years contractor to provide AMC. However, as per clause 9.3 of Volume 2, the period of maintenance support shall be seven (7) years from Operational Acceptance by PFCCL/ HPSEB. The period of maintenance support shall

The period of maintenance support shall include

Five years of Warranty (Defect Liability) period commencing from the date of Operational Acceptance; and

Annual Maintenance Support for two years


Page 34 of 84


include five years Warranty (Defect Liability) period commencing from Operational Acceptance and Seven (7) years thereafter. Please confirm that for the last two years, no product warranty is required and any defect in the product will be addressed on additional cost

thereafter at no extra cost.

104. Volume-I

Clause 6.40

(Termination)

General In the event of early termination, there is no mention of Early Termination Payments. Please consider the same.


shall prevail.

105. New Clause to be added Termination of contract by Contractor: Contractor shall be entitle to terminate the contract for below mentioned reasons, a. If Contractor does not receive the

reasonable response within 42 days after giving notice.

b. If Owner is unable to provide site front as per agreed schedule

c. If Owner is unable to make the payment within the agreed time period

d. If the Owner substantially fails to perform his obligation under the contract

e. If the prolonged suspension affects the whole of the work.

f. o If the Owner become bankrupt or insolvent goes into liquidation has a receiving or administration order made against him. Compounds with his creditors or carries on business under a receiver trustee or manager for the benefit of his creditors or if any act is done or event occurs which has a similar effect to any of these acts or events."


shall prevail.


Page 35 of 84


106. Volume-I

Clause 6.40.3(a)

(Termination for

Convenience)

PFCCL, by Notice of 30 (thirty) days sent

to Contractor, may terminate the Contract,

in whole or in part, at any time for its

convenience. The Notice of termination

shall specify that termination is for

PFCCL’s convenience, the extent to which

performance of the Contractor under the

Contract is terminated, and the date upon

which such termination becomes effective

As any contract is a Legal agreement between the Purchaser and Vendor, termination cannot be done as per convenience of the Purchaser.


shall prevail.

107. Volume-I

Clause 6.40.4

(Consequences of

Termination)

Upon Termination of the Contract, the

Contractor shall:

a. Prepare and present a detailed exit

plan within five (5) calendar days of

termination notice receipt to the CEO,

PFCCL (“Exit Plan”).

b. CEO, PFCCL and along with

designated team will review the Exit

plan. If approved, Contractor shall

start working on the same

immediately. If the plan is rejected,

Contractor shall prepare alternate

plan within two (2) calendar days. If

the second plan is also rejected,

PFCCL will provide a plan for

Contractor and it should be adhered

by in totality…………………………

The clause may be amended as per the following: “Upon Termination of the Contract, the

Contractor shall:

a. Prepare and present a detailed exit

plan within five (5) Ten (10)

calendar days of termination notice

receipt to the CEO, PFCCL (“Exit

Plan”).

b. CEO, PFCCL and along with

designated team will review the Exit

plan. If approved, Contractor shall

start working on the same

immediately. If the plan is rejected,

Contractor shall prepare alternate

plan within two (2) seven (7)

calendar days. If the second plan is

also rejected, PFCCL will provide a

plan for Contractor and it should be

adhered by in totality………..”


shall prevail.

108. Volume-I

Annexure A (Tender

Evaluation Methodology)

General Please clarify whether credentials of sub-

contractor can be used as the same is

allowed for QR criteria.


Bidder is correct


Page 36 of 84


109. Volume-I

Annexure A (Tender

Evaluation Methodology)

S.

No Description Qualifying Criteria

Max

Score

1 Manpower

Experience

Strength of the team

proposed for

undertaking the

assignment including

the qualification,

experience and time

proposed on field as

well as on support &

maintenance

20

2 Meter

Manufacturing

Experience

The Bidder/

consortium member

have

1. Manufactured

and supplied

minimum 40,000

nos. of Meters for

AMI (cumulative)

with required

hardware,

software and

other associated

accessories etc.

in Indian Power

Distribution

Utility(s) in the

last 7 years (i.e.

FY 2012-13

onwards) till the

date of issuance

of this RfP

Or

2. Manufactured and supplied minimum 10,000 nos. of Pre-paid Meters with cellular/ RF communication with required hardware, software and other associated accessories etc. in Indian Power Distribution

15

A bidder who might clear the minimum

Qualifying Requirement as specified in

the Clause 4.3.1 of the RfP, will not be

able to score the minimum marks. It is

requested to kindly amend the Tender

Evaluation Methodology.


shall prevail. 110.

111. Please amend the clause as per the

following: S.


Max

Score

1 Manpower

Experience

Strength of the team proposed for undertaking the assignment including the qualification, experience and time proposed on field as well as on support & maintenance

20

2 Meter

Manufacturi

ng

Experience

The Lead Bidder Bidder/ consortium member have 1. Manufactured and supplied minimum 40,000 nos. of Meters for AMI (cumulative) as per IS16444 with required hardware, software and other associated accessories etc. in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP Or 2. Manufactured and supplied minimum 10,000 nos. of Pre-paid Meters with cellular/ RF

15


No. 2 to RfP.


Page 37 of 84


Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP

3 Experience in

Integration

with MDM

The Bidder/

consortium member

must have

experience of

integration of HES

with MDM on

standard interfaces

and data exchange

models (CIM/XML)

for at least 40,000

consumers

(cumulatively) in

Indian Power

Distribution Utility(s)

in the last 7 years

(i.e. FY 2012-13

onwards) till the date

of issuance of this

RfP.

10

4 Experience as

Cloud Service

Provider

Bidder/ consortium

member should have

at least two (2) work

orders from Central

Government / State

Government/ PSU

/Semi- Government

of India in last 7

years (i.e. FY 2012-

13 onwards)

10

5 Experience in

Communicatio

n

The Bidder/

consortium member

should have

implemented

project(s) with at

least 40,000

(cumulatively)

communication

module/ endpoints

(manufacturing,

supply, installation,

10

communication with required hardware, software and other associated accessories etc. in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP

3 Experience

in

Integration

with MDM

The Lead Bidder Bidder/ consortium must have experience of integration of HES with MDM on standard interfaces and data exchange models (CIM/XML) for at least 40,000 consumers (cumulatively) in Indian Power Distribution Utility(s) in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP.

10

4 Experience

as Cloud

Service

Provider

Bidder/ consortium The Lead Bidder should have an experience of Implementing atleast one AMI Project with Indian utility on Cloud Service successfully in last 7 years (i.e. FY 2012-13 onwards)

10

5 Experience

in

Communica

tion

The Lead Bidder Bidder/ consortium member should have implemented project(s) with at least 40,000 Smart Meter (cumulatively) communication module/ endpoints (manufacturing, supply, installation, integration, maintenance & management) involving Radio

10


Page 38 of 84


integration,

maintenance &

management)

involving Radio

Frequency (RF)

mesh in Licensed

frequency band as

permitted by WPC or

in Unlicensed

frequency band in

India in the last 7

years (i.e. FY 2012-

13 onwards) till the

date of issuance of

this RfP.

6 Experience as

Meter Data

Management

(MDM)

Provider

The Bidder/

consortium member

should have

successfully

implemented/ under

implementation and

integrated with HES

for at-least 40,000

numbers of smart

meter/ AMI system

with connect/

disconnect features

with two-way

communication in a

single project in any

Indian Power

Distribution Utility in

the last 7 years (i.e.

FY 2012-13 onwards)

till the date of

issuance of this RfP.

10

7 Approach &

Methodology

Bidder to submit a

brief on Approach &

Methodology for

executing the Project

10

8 Financial

Criteria

Minimum Average

Annual Turnover

(MAAT) of the bidder

(Average of best

Three Financial

Years out of the Last

15

Frequency (RF) mesh in Licensed frequency band as permitted by WPC or in Unlicensed frequency band in India in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP.

6 Experience

as Meter

Data

Managemen

t (MDM)

Provider

The Lead Bidder Bidder/ consortium member should have successfully implemented/ under implementation and integrated with HES for at-least 40,000 numbers of smart meter/ AMI system with connect/ disconnect features with two-way communication in a single project in any Indian Power Distribution Utility in the last 7 years (i.e. FY 2012-13 onwards) till the date of issuance of this RfP.

10

7 Approach &

Methodolog

y

The Lead Bidder to submit a brief on Approach & Methodology for executing the Project

10

8 Financial

Criteria

Minimum Average Annual Turnover (MAAT) of the Lead bidder (Average of best Three Financial Years out of the Last Five Financial Years i.e. FY 2014- 15 onwards) should not be less than INR 150 Cr

15

Total 100

112. Marking criteria for Cloud Service

Provider should be deleted and another

marking criteria should be added for


shall prevail.


Page 39 of 84


Five Financial Years

i.e. FY 2014- 15

onwards) should not

be less than INR 100

Cr

Total 100

Meter Manufacturer as per the following: S.


Max

Score

1 Meter

Manufacturing

Experience

The Bidder must

have a IS16444

Certificate for at least

one (1) type of meter

that is to be supplied

before submission of

bid

10

113. Volume-I

Annexure A(A.2) (Tender

Evaluation Methodology -

Meter Manufacturing

Experience - Pre-Paid/ AMI

Experience)

Requirement Criteria Score

Bidder/ consortium

member must have

manufactured and

supplied minimum 10,000

nos. of Pre-paid Meters

with cellular/ RF

communication with

required hardware,

software and other

associated accessories

etc. in Indian Power

Distribution Utility(s) in the

last 7 years (i.e. FY 2012-

13 onwards) till the date of


>=40,000 15

>=20,000 and <40,000

10

>=10,000 and <20,000

5

The requirement of 40,000 Pre-Paid

Meter is big. It is requested to amend the

clause as per the following: Requirement Criteria Score

Bidder/ consortium

member must have

manufactured and

supplied minimum 10,000

nos. of Pre-paid Meters

with cellular/ RF

communication with

required hardware,

software and other

associated accessories

etc. in Indian Power

Distribution Utility(s) in the

last 7 years (i.e. FY 2012-

13 onwards) till the date of


>=10,000 15

>=7,000 and <10,000 10

>=5,000 and <7,000

5


No. 2 to RfP.

114. Volume-I

Annexure C (Format of

Deviation Sheet)

Deleted Since the tender is for Turnkey Project, it is requested to allow & accept Bid with few minor technical deviations if any and provide Technical Deviation Annexure Sheet to fill and submit the same along with the Bid.


shall prevail.

115. Volume-I

Annexure D (Use Cases

for Demonstration of

Interoperability

Solutions)

…… All use cases shall be tested for each

meter make

As the Bidder needs to showcase demo setup from meter to MDM and end to end integration needs lots of efforts & cost, please amend the clause as per the following: “All use cases shall be tested for atleast two make of Indian Meter each meter


shall prevail.


Page 40 of 84


make”.

116. Volume-I

Annexure D(S.No.1)

(Use Cases for

Demonstration of

Interoperability Solutions

- Read Demand &

Energy Data

Automatically from

Customer Premises)

……..At scheduled freq meter sends data

to HES (thru DCU/ACP). Consumption

details will be 15 min block data, and data

could be incremental to what was sent by

meter in preceding instance

At scheduled freq meter sends billing data

to HES (thru DCU/ACP).

As ACP is not part of the RFP, please amend as per the following: “Read Demand & Energy Data Automatically from Customer Premises: ……At scheduled freq meter sends data to HES (thru DCU/ACP). Consumption details will be 15 min block data, and data could be incremental to what was sent by meter in preceding instance. At scheduled freq meter sends billing data to HES (thru DCU/ACP).”

“ACP” may be read as

“Access Points”

117. Volume-I

Annexure D(S.No.3)

(Use Cases for

Demonstration of

Interoperability Solutions

- Utility detects

tampering or theft at

customer site)

….. HES sends disconnect command to

meter (thru DCU/ACP)……

As ACP is not part of the RFP, please amend as per the following: “…..HES sends disconnect command to meter (thru DCU/ACP)……”

“ACP” may be read as

“Access Points”

118. Volume-I

Annexure D(S.No.10) (Use Cases for Demonstration of Interoperability Solutions – Time Synchronization)

Sync up of meters / DCUs/ master data

and Network Hierarchy in case of

installation of new meters / DCUs

We understand that this functionality is for addition of new meters/ DCU into the AMI communication hierarchy with time synchronisation in place. Accordingly, please amend as per the following: “Sync up time for of meters / DCUs/ master data and Network Hierarchy in case of installation of new meters / DCUs”


shall prevail.

119. Volume-I

Annexure E (Project

Implementation

Schedule)

General Please mention Execution Period and

FMS period categorically as the same

is not mentioned presently.

The Project has to be

implemented within 24

months.

The FMS period for a

particular lot of meters


Page 41 of 84


would commence from the

date of Operational

Acceptance of that lot and

would continue for a period

of 84 months from that

date.

120. FMS Period – 7 Years from Operational

Acceptance

The maximum project time line should be

2 years for implementation and 5 years

for warranty cum FMS because guaranty/

warranty and life cycle of imported

components in smart meters are provided

only for 5 years. None of the suppliers

provide any support beyond this period.

In addition, technology transition takes

place at every 5 years.

Accordingly, the project time line

should be 2 + 5 years i.e. total 7 years.


shall prevail.

121. Volume-I

Annexure 10 (Format of

Bill of Quantities)

SNo Item

Description

Unit Quantity

Shimla Dharamsala

1. Single Phase

Whole current

Smart Meter

10-60 A with

Box

Nos. 112934 31844

2. Three Phase

whole current

Smart Meter

10-60 A with

Box

Nos. 1383 390

As per this clause, the rating of Single Phase Whole current Smart Meter with Box would be 10-60 A. However, as per Volume II (Technical Specifications), the Single Phase Smart Meter Current Rating is 5-30Amp / 10-60Amp. The standard Current Ratings in India for Single Phase Smart Meter is 5-30 A. Further, here it has been mentioned that the rating of Three Phase Whole current Smart Meter with Box would be 10-60 A. However, as per Volume II (Technical


No. 2 to RfP.


Page 42 of 84


Specifications), the Three Phase Smart Meter Current Rating is 10-60 A/ 20-100 A. Further, in Annexure 17 of RfP, it has been mentioned as 10-40 A. The standard Current Ratings in India for Three Phase Smart Meter is 10-60 A. Hence, it is requested to clarify the actual

Current Rating of Single Phase &

Three Phase Smart Meters and their

split up quantity (if any).

122. Bidder may be allowed to quote for

any type of smart meter.


shall prevail.

123. Volume-I

Annexure 17 (Price Bid

Format)

Supply and FMS price schedule of Shimla

and Dharamshala

Please provide a single BOQ for Software, Cloud DC and Control Centre as License would be common for entire scope of project. The Supply and FMS should be common for Common Data Centre, Software License and Control Centre. Only Field Equipment can be distinguished.


No. 2 to RfP.

124. The Price for IT Infrastructure over cloud & Connectivity for applications has been requested for Shimla and Dharamsala separately. Please confirm if we need to propose different cloud environment for Shimla and Dharamsala. If single cloud environment is required, please amend the price schedule in supply and FMS accordingly.


No. 2 to RfP.

125. In Price schedule, application (HES, MDM & Mobile APP & web portal) License + Implementation + System Integration+ Advisory services cost has been sought for Shimla and Dharamsala separately. Please confirm if different


No. 2 to RfP.


Page 43 of 84


logical instances are to be created for Shimla and Dharamsala in different cloud environment. If not required, kindly amend the price schedule in supply and FMS accordingly.

126. S.No. 7 of the Price Schedule (Supply Schedule) has many items from different vendors which will get commenced and commissioned at different stages of supply and implementation Hence, it is request to segregate the line items as 1. Head End System (HES) licenses (1

Lumpsum) 2. Meter Data management System and

Android &/ IOS Mobile App and web portal (1 Lumpsum)

3. IT Infrastructure over cloud & Connectivity

4. System Implementation and Advisory Services

The above changes are mandatory for billing perspective because S.No. 1 to 2 are supply items and will be supplied from different vendors. Further, S.No. 4 is services item and cannot be clubbed along with the Supply item.


No. 2 to RfP.

127. We understand that training is to be provided 2 times a year during first 3 years for HPSEB and PFCCL. In Price Schedule, price for training has been sought for Shimla and Dharamsala differently. Please confirm if we need to provide training 2 times a year for Shimla and Dharamsala separately.


No. 2 to RfP.


Page 44 of 84


128. We understand that Advisory service is not a separate scope of work and is part of hand holding work. Bidder shall not consider any separate cost of Advisory services. Please clarify


No. 2 to RfP.

129. There is an error in formula of column "N" where "Addition" is required in place of "Multiplication".


No. 2 to RfP.

130. General Performance Security, Liquidated Damages and Penalty

Please amend the respective clauses with “Ex-work” instead of “contract value” as the tax part goes to Government & it will impose additional burden on the financial bid.


shall prevail.


Page 45 of 84

Clarifications with respect to RfP (Volume – II)


131. Volume-II

Clause 1.4.1(i) (Scope of

Work)

Single phase whole current Smart Meter

(with/without net-metering) with Pre-paid

configuration and with suitable

communication technology (Smart Meters

proposed shall be able to work in pre-paid

as well as post-paid configuration as per

the HPSEB’s Needs. There should not be

restriction in case HPSEB wants to use

some Smart Meters in Pre-Paid and some

in Post-Paid mode)

As the configuration of Pre-paid

functionality would be available on the

HES, please amend the clause

accordingly.

The Pre-paid functionality

is to be provided on HES/

MDM.

132. Volume-II

Clause 1.4.1(iii) (Scope

of Work)

CT operated three phase Smart Meter

(with/without net-metering) with Pre-paid

configuration and with suitable

communication technology (Smart Meters

proposed shall be able to work in pre-paid

as well as post-paid configuration as per

the HPSEB’s Needs. There should not be

restriction in case HPSEB wants to use

some Smart Meters in Pre-Paid and some

in Post-Paid mode)

CT Operated smart meters do not

support pre-payment configuration by

design. So please amend the clause

suitably.


No. 2 to RfP.

133. Volume-II

Clause 1.4.1(iv) (Scope

of Work)

RF canopy or GPRS based

communication………..

We understand that the RF requirement

is for “RF Canopy” and for some

points where RF might not be possible

then the bidder can install GPRS

based Smart Meters. Kindly clarify if our

understanding is correct.


bidder is correct.

134. As per RfP, wherever RF is not feasible

GPRS based communication shall be

established. Please consider only one

technology either RF or GPRS. So

please remove the clause “wherever


shall prevail.


Page 46 of 84


RF is not feasible GPRS based

communication shall be established”

135. As per RfP, the Contractor has to assess

and maintain buffer so that in case of new

installation, smart meters are installed by

the Contractor without any delay. In this

regard, please indicate quantity to be

kept as buffer for immediate

installation.

The bidder has to ascertain

the requirement of buffer

on its own

136. Please confirm that the data regarding

boundary of Sub-Divisions for

conducting the site survey would be

provided to the contractor on project

initiation.


bidder is correct.

137. Volume-II

Clause 1.4.1(v) (Scope

of Work)

Integration of Network Integration Card

(NIC)/ Communication Module with meters

of at least 3 manufacturers in India, to

enable the respective meters to

seamlessly integrate with proposed HES

and MDMS thus enabling interoperability

of the system. In future, it would be

bidders’ responsibility to integrate new

meter or any other application/ equipment

as decided by HPSEB.

We understand that the RFP is for smart meters and any new meters to be integrated will be complying to IS 16444 and IS 15959. Please confirm. Please provide clarity on the new

application/ equipment which need to be

integrated

Any new meters to be

integrated will be complying

to latest version of IS 16444

and IS 15959.

Bidder would have to

facilitate HPSEB in

integration of future

technologies/ new

application/ equipment by

providing whatever data

required by HPSEB at that

time.

138. In case of NIC module being integral part of the meter, its integration with any other make of meters may not be possible. Scope of the bidder shall be limited to the quantities and necessary services defined in this tender.

Communication module

has to be modular and plug

& play type for all meter

types


Page 47 of 84


Accordingly, remove this clause

139. We understand that the bidder would be responsible to integrate with the 3rd party meters which are already declared integrated by the bidder. Any other meter manufacturer apart from the one mentioned by the bidder if introduced by HPSEB shall be done on mutual agreeable terms and conditions and additional cost. Please confirm.


shall prevail.

140. Volume-II

Clause 1.4.1(viii) (Scope

of Work)

Integration of HES with MDMS & MDMS

with existing applications of HPSEB……

Please provide details of the existing

applications of HPSEB.

The integration requirement

would include integration

with

i. R-APDRP modules like

MDM, Energy Audit etc.

ii. ISU-Billing like CRM,

Billing, Consumer

Portal etc.

iii. Integration with

Payment Gateway

Service Provider and

ISU-Billing for prepaid

functionality.

141. Volume-II

Clause 1.4.1(viii) (Scope

of Work)

IT System - Design, procure, supply,

installation, testing, Cyber Security,

commission and operation & maintenance

of complete IT System. IT Infrastructure

shall be on cloud to host the HES, MDM

and Web Applications. Security of data

hosted on cloud shall also be the

responsibility of the Contractor. System

Security and access with due

consideration of data privacy,

confidentiality cyber security guidelines

Please confirm hosting that needs to be proposed on GCC, VPC, Public cloud

Hosting of both DC and DR

should be on GCC

142. Please define the Cyber Security Type and authorized lab if any.

The same would be as per

MEITY Guidelines

143. Volume-II Mobile app (Android and iOS based) for We understand that Mobile App is The understanding of the


Page 48 of 84


Clause 1.4.1(xi) (Scope

of Work)

consumers required for iOS & Android and not for

Windows platform

bidder is correct.

144. Volume-II

Clause 1.4.1(xviii)

(Scope of Work)

Develop an overall AMI Architecture

capable of upgrades and scaling out as

per future requirements

We understand from Annexure G that

only HES and MDM shall be developed

keeping in mind 20% expansion in the

no of nodes in future. Also the additional

end points that shall come in project area

will only be considered to be integrated in

system in future

The bidder has to develop

the overall AMI architecture

in such a manner that it

meets the scaling up

requirements of HPSEB in

future to the extent


145. Volume-II

Clause 1.4.1(xxi) (Scope

of Work)

Baseline Study and formulation of DPR We presume that this is not part of the scope of this RFP. Please remove this clause

Baseline Study and

formulation of DPR is in the

scope of RfP.

146. Volume-II

Clause 1.4.1(xxv)(c)

(Scope of Work)

Business Process Re-engineering:

Contractor shall do an in depth study of

commercial processes of HPSEB to form

an understanding of “As-Is” processes

being carried out. Based on this

understanding a gap analysis shall be

done with respect to requirements post

deployment of new AMI systems &

necessary recommendations for making

suitable changes in processes shall be

made to HPSEB

We presume that this is not part of the scope of this RFP. Please confirm

The same is in the scope of

RfP.

147. Volume-II

Clause 1.4.1(xxv)(d)

(Scope of Work)

Integration Services: Smooth operations

of AMI and usage of full functionalities

offered by AMI shall require its integration

with many existing systems as well as

planned future technology deployments.

The Contractor shall assist HPSEB

engineers in identification of use cases for

integration of AMI with other systems. The

Please confirm whether for all integrations with legacy or any other third party applications, the integration points required from these applications shall be established by the respective application owners.


bidder is correct.


facilitate HPSEB in


technologies/ new




Page 49 of 84


Contractor will integrate AMI system with

existing application/systems of HPSEB as

per HPSEB’s requirement and also

facilitate for integration of AMI system with

future system/applications of HPSEB


time.

148. Volume-II

Clause 1.4.1(xxvii)

(Scope of Work)

The Contractor shall establish the Back-

End IT system with scalability features to

handle all HPSEB consumers i.e.

consumers of HPSEB in entire State of

H.P. for next 15 years.

We understand that cloud services shall

provide flexibility to handle all future AMI

consumers of HPSEB for next 15 years.

However, the cost of cloud and

associated services for additional

quantities beyond this tender shall be

borne by HPSEB. Please clarify.


bidder is correct. As per

clause 1.4.1 (viii), IT

Infrastructure shall be on

cloud to host the HES, MDM

and Web Applications


following:

“The Contractor shall handle the project

till its contract period and train HPSEB

employees to independently handle

the system for upcoming years

establish the Back-End IT system with

scalability features to handle all

HPSEB consumers i.e. consumers of

HPSEB in entire State of H.P. for next

15 years.”


shall prevail.

150. Please confirm the projected growth for sizing to be factored.

As per clause 1.4.1 (viii), IT

Infrastructure shall be on

cloud to host the HES, MDM

and Web Applications to

provide flexibility to handle

all future AMI consumers of

HPSEB for next 15 years

151. Volume-II

Clause 1.4.1(xxviii)

Smart Meters proposed should have the

provision of Pre-paid mode ….. Integration

for pre-payment recharge coupon with

Please clarify that system based

Prepayment is to be provided through

MDM. There will be no prepayment

The Pre-paid functionality

is to be provided on HES/

MDM.


Page 50 of 84


(Scope of Work) existing billing application of HPSEB intelligence in the smart meter as all

calculations shall be done by prepayment

module at the system level. Coupon

insertion can be availed via Mobile

application. All transaction by the

consumer will be done via electronic

media.

It is requested to accept the pre-paid

metering facilities IS 16444 / IS 15959

Standard.

152. Volume-II

Clause 1.4.3 (Scope of

Work)

….The Contractor shall also bear the cost

of recurring charges for GPRS/3G/4G,

static ISP connection and any license fee

for operating RF in licensed frequency

band till completion of maintenance period

Please modify the clause as per the

following:

“….The Contractor shall also bear the

cost of recurring charges for

GPRS/3G/4G, static ISP connection

and any license fee for operating RF in

licensed frequency band till completion of

maintenance period. For GPRS/3G/4G

and static ISP connection, tripartite

agreement will be signed between

HPSEB, the contractor and the service

provider wherein the contractor shall

facilitate the services for HPSEB, and

HPSEB shall directly pay the charges

to the service provider.”


shall prevail.

153. Volume-II

Clause 2.2.1 (Access to

Utility Facilities)

PFCCL to facilitate through HPSEB

management, safe and reasonable access

to utility premises for contractor’s

personnel and third party vendors. This

facilitation shall include, space for data

centers, working space including air

conditioning, light, ventilation, electric

power and outlets. The contractor’s

For storage of meters, DCU, IT

hardware and their accessories, we

understand HPSEB shall provide

proper and secured storage facility

during the implementation period and

storage of spares and accessories

during O&M period.


bidder is correct.

Utility shall provide the

storage space, however,

the safety and security of

the stored items shall be

the responsibility of the


Page 51 of 84


personnel shall comply with all applicable

rules, regulations and requirements

relating to visitors on the premises of

HPSEB

bidder

154. Volume-II

Clause 2.4.1.21

(Contractor’s

Responsibilities and

Obligations)

To provide storing, maintenance of storing

area and security including full

responsibility for protection from theft and

fire for all the items to be supplied. The

warehouse may be a temporary storage

area to be constructed by contractor.

Space for material storage would be

provided by HPSEB at no extra cost for

storing the supplied equipment in

respective areas where project work is in

progress

We understand that utility shall provide

storage facility in its premise and the

Contractor shall deploy its manpower for

storing, maintenance & security.

155. Volume-II

Clause 2.4.1.26

(Contractor’s


Obligations)

To provide full backup of all installed

software applications and data

Please confirm backup that needs to be provisioned at DR site.

Please refer Clause 3.8.8

and 3.8.10 of RfP (Vol-II)

156. Volume-II

Clause 2.4.1.27

(Contractor’s


Obligations)

To test restoration of the system from the

backup provided

-

157. Volume-II

Clause 2.4, 2.5 and 2.6

(Contractor’s


Obligations, Exclusion

If any Cable/ Service cable is required,

the same to be in scope of consumer

only.

Any Cable/ Service cable

required for the project

would be provided by

HPSEB. 158. We understand that cable will be

provided & installed by HPSEB for all

kind of connections (new connection/


Page 52 of 84


from Contractor’s Scope,

Employer/ Utility’s


Obligations)

replacement) under the Routine

cabling work.

159. Volume-II

Clause 3.1.2 (AMI

Functional Requirement)

The main objective of AMI is to enable two

way communication between smart energy

meter and Head End System (HES) to

enable remote reading, monitoring &

control of electrical energy meters

(consumer, feeder, DT meters etc.) to

serve as repository of record for all raw,

validated and edited data. The sanitized

data may be subscribed by other utility

function for higher order analysis and

billing and collection engine etc.

Please amend the clause as per the

following:

“The main objective of AMI is to enable

two way communication between smart

energy meter and Head End System

(HES) to enable remote reading,

monitoring & control of electrical energy

meters (consumer, feeder, DT meters

etc.) to serve as repository of record for

all raw, validated and edited data. The

sanitized data may be subscribed by

other utility function for higher order

analysis and billing and collection engine

etc.”


shall prevail.

160. Volume-II

Clause 3.1.3.(ix) (AMI


Import of legacy data from existing

modules/ MDAS of RAPDRP wherever

possible. The extent and modalities of

integration with the existing system

including RAPDRP has to be worked out

by the bidder

We understand that the bidder shall

integrate with the existing MDAS of

RAPDRP over interface which is capable

of CIM/Multispeak/xtract. Please clarify

if the bidder is required to migrate all

the legacy data from existing module

to cloud as it will lead to additional

cost and size of the cloud


shall prevail.

161. Volume-II

Clause 3.1.3.(xii) (AMI


The System will accurately maintain

system time synchronization across all

devices to ensure accuracy of data. The

system should support the interfacing with

the future Smart Grid functionalities like

peak load management, outage

management system, distribution

We understand that time synchronization

shall be done though NTP server at

system level so as to ensure accuracy of

data throughout the system.

We also understand that the utility shall

ensure that future smart grid

functionalities like peak load

The clause is self-

explanatory. The bidder has

to design a system that will

accurately maintain system

time synchronization

across all devices to ensure

accuracy of data.


Page 53 of 84


automation including self-healing system,

GIS, distribution transformer monitoring

units, Electric vehicle, distributed energy

resources etc

management, outage management

system, distribution automation including

self-healing system, GIS, distribution

transformer monitoring units, Electric

vehicle, distributed energy resources etc

will be integrated with system at

additional cost and time

Further, the bidder needs to

build in a system that

would support the future

Smart Grid functionalities.


facilitate HPSEB in


technologies/ new




time


following:

“The System will accurately maintain

system time synchronization across all

devices to ensure accuracy of data. The

system should support upon

upgradation as part of future projects ,

the interfacing with the future Smart

Grid functionalities like peak load

management, outage management

system, distribution automation

including self- healing system, GIS,

distribution transformer monitoring

units, Electric vehicle, distributed

energy resources etc.”

163. Volume-II

Clause 3.1.3(xiii) (AMI


Communication network shall preferably

be able to support multiple applications

Please provide the details of Applications The Bidder needs to

ascertain the applications

that would be required and

submit the bid accordingly.

164. Volume-II


AMI System

Requirement)

Smart Meter (Single phase whole current,

Three phase whole current, CT & PT

operated three phase meters and CT

operated three phase meters) …... Smart

meter, router/ access points/ DCU, MDM,

HES and other operational/requisite

software as part of fully functional AMI

CT & PT Operated Three Phase Meter

specification is not provided in this

document. Please provide the same


No. 2 to RfP.


Page 54 of 84


system

165. Volume-II


AMI System

Requirement)

Contractor shall adhere with appropriate

security algorithm for encryption &

decryption. For smooth functioning of

entire system, it is essential that the

details of such algorithm including the

mechanism of security key generation be

kept in a secured escrow account which

shall be used by the utility only in case of

termination of the contract for reasons

whatsoever

Security Algorithm and Encryption should be driven by standards as applicable and manufacture specific driven logic should be discouraged. Please amend the clause as per the following: “Contractor shall adhere with appropriate standards based security algorithm for encryption & decryption. For smooth functioning of operations it should be hardware based key storage and not manufacture specific algorithm entire system, it is essential that the details of such algorithm including the mechanism of security key generation be kept in a secured escrow account which shall be used by the utility only in case of termination of the contract for reasons whatsoever.”


shall prevail.

166. Volume-II

Clause 3.3.4.1.1 (Type

tests and test

certificates)

Single phase and three phase whole

current Smart meter shall be type tested

for all the type tests as per IS: 16444

(latest version) and three phase CT

operated Smart Meter shall be type tested

for all the type tests as per IS: 16444 Part-

2 (latest version) in a government

approved laboratory. The number of

sampling for testing of meters and criteria

for conformity would be as per IS 16444

and IS 16444 Part-2. The supplier shall

have to submit all type test certificates

along with the bid.

As IS:16444 Standard is quite recent, there are not many Meter variants which are type tested as per IS: 16444. It is requested to allow Bidders to submit Single Phase & Three Phase Smart Whole Current Meter Type Test Reports along with the Bid and to submit the Type Test Reports of other variant meters before the commencement of Supply in line with your specifications clause No. 3.3 of Volume II


No. 2 to RfP.

167. Bidder may be allowed to submit all type test certificates before supply of meters.

As clarified above

168. Volume-II Type test should not be older than 3 years. The Bidder should be allowed to submit As clarified above


Page 55 of 84


Clause 3.3.4.1.2 (Type

tests and test

certificates)

Without above type test certificate the offer

shall not be considered. Employer

reserves right to select randomly one

meter from offered lots for inspection for

its type test and if meter during type test is

found failed then either the order placed

shall be cancelled with Contractor to

collect all meters at its cost for the

supplied meters or Contractor shall have

to replace all supplied meters at their cost

after manufactured and successful type

test within time frame given by the

Employer.

its bid with a valid copy of BIS Certificate (IS-16444) of at least one type of whole current smart meter required in the RfP & self-declaration undertaking for submission of BIS Certificate for the offered Product as per IS 16444 before delivery of Smart Meter failing which Performance Security shall be forfeited. Without above BIS Certificate, the offer shall not be considered.

169. Volume-II

Clause 3.3.5(c) (General

and Constructional

Requirements for

Meters)

In Home Display (IHD) shall be optional

and the specifications of the same would

be as per agreement between the bidder

and the utility

We understand that IHD is not required as Mobile app shall be provided to consumers


No. 2 to RfP.

170. Volume-II

Clause 3.3.5.9.1 (Meter

Box)

The Meter Box would be provided as per

latest standards and requirement of

HPSEB

Please clarify whether supply of Meter Box is in the Bid’s Scope. Since Technical Specification of the Box have not been provided, in case if Boxes are required then please provide the detailed Technical Specification of:

1. Single Smart Meter Box 2. Three Phase Meter Box 3. LT CT Operated Meter Box. 4. CT Ratio & its Technical

Specification


No. 2 to RfP.

171. Volume-II

Clause 3.4(g)(xi)

(Communication

The equipment shall be weatherproof,

dustproof and constructed for outdoor

installation on poles (minimum rating: IP-

55). A suitable mounting provision shall be

We understand that DCU is usually mounted in external environment and needs to be protected with corresponding grade of environmental protection. Hence minimum rating of IP65 is required.


No. 2 to RfP.


Page 56 of 84


Infrastructure) made for the equipment

172. Volume-II

Clause 3.4.2.1(g) (Data

Concentrator Unit (DCU)

based Communication

Network)

New Clause proposed Downstream Message and Application Authentication: Application white labelling and digital signatures should be employed to ensure that only approved applications can run within network equipment. All downstream commands should be signed using standards-based approaches based on the utility private key. Endpoints should enforce signature validation before acting on any command to prevent rogue commands or man-in-the-middle vulnerabilities.


shall prevail.

173. Volume-II

Clause 3.4.2.1(h) (Data


based Communication

Network)

New Clause proposed The network should employ encryption key segmentations at the individual and group levels, with a minimum of AES 256-bit encryption keys. Certified Root of Trust: The solution should support a root of trust where the private key is vaulted (hardware based). This vault should be FIPS validated to ensure strong protection of keys.


shall prevail.

174. Volume-II

Clause 3.4.2.1(i) (Data


based Communication

Network)

New Clause proposed Secure Key Storage and Lifecycle Management: Secure storage of device-specific keys should be protected via encryption to protect key storage at rest and during system use. Device-specific keys and network-specific keys should be configurable and support mature key rolling and lifecycle management processes


shall prevail.

175. Volume-II

Clause 3.4.3.1 (Data


based Communication

The Data Concentrator Unit is a gateway

for communication of data between the

Smart Meters and the HES. The Data

Concentrator Unit receives information

from the Smart Meter on a scheduled/

As per AMI standards, data storage shall not reside anywhere in the communication network and will merely act as communication channel to pass on the data from meter to HES.


No. 2 to RfP.


Page 57 of 84


Network) need basis and stores the data, which can

be accessed by HES for onward transfer

to MDM.

The DCU provides the central link

between Smart Meters and HES, enabling

continuous/periodic meter read and

control. DCU shall exchange data from

smart meters on RF / PLC communication

and with HES on WAN.

Please amend the clause as per the following: “The Data Concentrator Unit is a gateway for communication of data between the Smart Meters and the HES. The Data Concentrator Unit receives supports information from the Smart Meter on a scheduled / need basis and stores the data, which can be accessed by, to HES for onward transfer to MDM.”

176. We understand DCU shall exchange data from smart meter on RF and with HES on WAN. PLC Is not required in this tender.

177. Volume-II

Clause 3.4.3.1.1 (Data


based Communication

Network - Hardware &

Power Supply of DCU)

Enclosure/box of DCU shall be

minimum IP55 or better compliant. A

suitable mounting arrangement

required for DCU installation shall also

be provided.

A suitable and optimum power supply

shall be provided keeping in view that

even in case of outage in one or two

phases, DCU can be powered. DCU

should be capable of withstanding

surges & voltage spikes of 6KV as per

IEC 61000-4-5 standards. Power

supply shall be terminated on suitable

sized MCB to facilitate isolation during

on-site maintenance.

DCU shall have battery with backup for

5 hour for normal meter reading, to

push tamper event, carry out on

demand reading and the network

health status/ connectivity continuity &

check. DCU should have the suitable

We understand that DCU is usually mounted in external environment and needs to be protected with corresponding grade of environmental protection. Hence minimum rating of IP65 is required


No. 2 to RfP.

178. DCU should have battery with backup for 8 hour


Page 58 of 84


feature to send power outage and

restoration message to the HES. The

battery shall have a guaranteed life of 5

years…..

179. Volume-II



based Communication

Network - Configuration,

Functionality & Interface

of DCU)

DCU shall have following configuration

functionalities:

It shall be able to configure the

communication with underlying nodes/

meters.

It shall pull data from the field devices

and push the data at configured

intervals to the HES. It should also

support the HES in pulling data from the

field devises/meters. The data

acquisition (Push/Pull) frequency shall

be programmable. DCU shall be

capable to prioritize control commands.

DCU shall ensure a secure

communication to HES and shall have

internal memory for storing interval data

for at least 5 days.

DCU shall support on demand read and

ping of individual/group of meters.

It shall support IPv4 and IPv6 network

addressing.

DCU shall push events like tamper,

power off etc. to HES immediately on

occurrence/receipt from field

devices/meters.



installation on poles (minimum rating:

IP-55). A suitable mounting provision

Please amend the clause as per the following: “It pull data shall support data transportation from the field devices and push the data at configured intervals to the HES as part of push data mechanism. It should also support the HES in pulling data from the field devises/meters. The data acquisition (Push/Pull) frequency shall be programmable. DCU shall be capable to prioritize data.”


No. 2 to RfP.

180. Security Standards Applicable for AMI does not allow data to be stored in DCU. Data shall be stored in Meter as per ISI5959 part 2 and 3. Please clarify.

There is no restriction as

per standard

181. Please amend the clause as per the following: “The equipment shall be weatherproof, dustproof and constructed for outdoor installation on poles (minimum rating: IP-55 65). A suitable mounting provision shall be made for the equipment.”


No. 2 to RfP.


Page 59 of 84


shall be made for the equipment.

Enclosure: Provision for security sealing

shall be provided and in case the

gasket of the cover is used for

protection against moisture, dust and

insects, the gasket shall be made of

weather and aging resistant material.

The list of standards followed in all the

devices/equipment used in

communication network shall be

furnished

182. Volume-II

Clause 3.4.3.2.1(j) (Data


based Communication

Network - Router based

RF Mesh Network -

General Requirement of

Router based RF Mesh

Network)



installation on poles (minimum rating: IP-

55). A suitable mounting provision shall be

made for the equipment

Please amend the clause as per the following: “The equipment shall be weatherproof, dustproof and constructed for outdoor installation on poles (minimum rating: IP-55 65). A suitable mounting provision shall be made for the equipment”


No. 2 to RfP.

183. Volume-II

Clause 3.4.3.2.1(m)

(Data Concentrator Unit

(DCU) based

Communication Network

- Router based RF Mesh

Network - General

Requirement of Router

based RF Mesh

Network)

Routers / Access Points shall have

suitable power supply arrangements.

Provision of battery backup for at least 5

hour shall be there to continue operation in

case of power supply failure. The life

expectancy of battery shall be 5 years or

more

Please amend the clause as per the following: “Routers / Access Points shall have suitable power supply arrangements. Provision of battery backup for at least 5 8 hour shall be there to continue operation in case of power supply failure. The life expectancy of battery shall be 5 years or more”


No. 2 to RfP.

184. Volume-II It shall periodically monitor meter reads/ DCU/ Access Point is a RF communication element and failed reads



Page 60 of 84


Clause 3.4.3.2.2.1(f)

(Data Concentrator Unit

(DCU) based

Communication Network

- Router based RF Mesh

Network - Configuration,

Functionality & Interface)

downstream commands and shall retry

and reconnect in case of failed events/

reads

and events are managed by HES as all the data packets are encrypted at any time in the RF communication network. Please amend the clause as per the following: “It shall periodically monitor communication network downstream and shall retry and reconnect in case of communication failure to any node in the network meter reads/ downstream commands and shall retry and reconnect in case of failed events/ reads”

No. 2 to RfP.

185. Volume-II



based Communication

Network - Router based

RF Mesh Network -

Testing of the DCU

/Access Point)

…….

(f) Resistance to heat and fire….

Specific Test for the Equipment is not available for such equipment therefore it is requested to delete or make self-declaration acceptable

Suggestion accepted as no

standard is mentioned

186. ….The bidder shall provide IP-55

compliance test certificate for DCU/Access

Point.

Please amend the clause as per the following: “…..The bidder shall provide IP-55 65 compliance test certificate for DCU/Access Point.”


No. 2 to RfP.

187. Volume-II

Clause 3.5(d) (Head End

System (HES))

… HES shall support storage of raw meter

data, alarms and alerts for minimum 3

days….

HES should store data for at least 45 days so that if there is any failure in MDM, the data from HES can be recovered for last 45 days. Please amend the clause accordingly.


shall prevail.

188. Volume-II

Clause 3.5(e)(xii) (Head

End System (HES))

Network information in case more than

one technology is deployed in field

between the two devices

HES can support network information of other technology only if the technology provider shares the network information Please confirm that the technology provider will provide all network information.

Suggestion accepted.

189. Volume-II

HES shall export all meter data (as per IS

15959) to MDM via CIM/XML. In addition,

Please keep the technology open for integration of HES with MDM. Even in

The export of all data would

be as per Clause 6.2 of


Page 61 of 84


Clause 3.5(e)(xiii) (Head

End System (HES))

it should conform to IEC 61968-9 as well

as MultiSpeak v3.0 standards to interface

with pre-existing MDM solution. In case,

Discom has implemented any SOA/ ESB

architecture, the data exchange to and

from HES shall be through this ESB

RFP's released by other utilities the integration preference has been kept open as per CEA Guidelines. HES shall be Service Oriented Architecture (SOA) enabled with well documented standard interfaces to support integration through web-services/ APIs to exchange data with upstream systems like MDMs. HES shall exchange all meter data (as per IS 15959) to MDM complying CIM/XML/JSON*/ IEC61968 or any other open standard. The Integration approach shall follow the general principles outlined in IEC 61968-9/ MultiSpeak v3.0 standards for Interface architecture with pre-existing MDM solution. In case, utility has implemented any SOA/ ESB architecture, the data exchange to and from HES shall be through this ESB. *More recent technology than XML is JavaScript Object Notation (JSON). Support for JSON is now found in many modeling and integration tools. JSON is widely used for CIM based information exchanges. JSON is currently defined by IETF RFC 7159

CEA’s “Functional

Requirements of Advanced

Metering Infrastructure

(AMI) In India” which states

the following:

“HES shall preferably

interface with MDM on

standard interfaces and the

data exchange models and

interfaces shall comply with

CIM / XML / IEC 61968 or

any other open standard.

The solution shall be

Service Oriented

Architecture (SOA)

enabled.”

190. Volume-II

Clause 3.5.4 (Head End

System (HES) -

Integration)

HES shall export all meter data (as per IS

15959) to MDM via CIM/XML. In addition,

it should conform to IEC 61968-9 as well

as MultiSpeak v3.0 standards to interface

with pre-existing MDM solution. In case,

utility has implemented any SOA/ ESB

architecture, the data exchange to and

from HES shall be through this ESB

191. Volume-II

Clause 3.5.1.1(c) (Head

End System (HES) -

Configuration)

HES shall facilitate programming of

following meter parameters:…….

Setting of parameters for time of day

(TOD/ TOU) billing

TOD Recording Parameters cannot be changed, however, TOD Timings can be reprogrammed. Please consider the same

The same would be as

defined for meter in IS16444

192. Volume-II

Clause 3.5.1.1(p) (Head

End System (HES) -



Setting threshold limits for monitored

parameters

Please provide the list of Parameters for which threshold limit is to be set.


shall prevail.


Page 62 of 84


Configuration)

193. Volume-II

Clause 3.5.1.1(q) (Head

End System (HES) -

Configuration)



Provision for adding more programming

features in future (The bidder may suggest

more parameters as per the requirement)

Please provide the list of features which you may add in future


shall prevail.

194. Volume-II

Clause 3.5.3.2.2 (Head

End System (HES) -

Monitoring and Reporting

Capability - Non Critical

Reporting)

…… HES shall have feature to send

email/SMS notification of configured

alarms & events to selected users.

Interface of highly secure data from multiple point to multiple application may cause security concerns. It is recommended that only one interface for HES i.e. MDMS should be allowed and rest of the integration should be through MDMS. The clause may be amended as per the

following:

"…..HES shall send all notification to

MDM and MDM should have feature to

send email/SMS notification of configured

alarms & events to selected users.”


No. 2 to RfP.

195. Volume-II

Clause 3.6.5.1

(Customer Service

Support)

The MDM Shall allow configuring multiple

TOU/TOD options (e.g. the number and

duration of TOU rate periods) by customer

type, tariffs and day type (weekend,

weekdays, and holidays) and by season

We understand that this requirement is applicable only if Meter is in Prepaid Functionality.


shall prevail.

196. Volume-II

Clause 3.6.5.5

(Customer Service

Support)

MDM shall have the ability to properly

account for special metering situations

such as check metering, sub metering,

prepaid metering and net metering when

calculating billing determinants and

sending them to billing and other systems

Please delete the requirement of check Metering and Sub Metering or elaborate the requirements clearly.


No. 2 to RfP.

197. Volume-II

Clause 3.6.8.3

(Customer Service

MDM shall support the web portal or shall

have the ability to interface with the 3rd

party portal/ utility portal to provide the

consumer near real time online views of

Please confirm whether the portal for providing consumer related data can be an extension of MDM or the bidder needs to provide a separate web application.


shall prevail.


Page 63 of 84


Support) both usage and cost and helping

consumers to understand electricity usage

and cost information, alerts and

notifications and energy savings tips with

different levels of detail. The portal should

support the view for past electricity usage,

last week’s, yesterday’s, current days or

other period etc. as per selection. The

portal should provide user friendly access

to consumer for their data via colorful

graphs and charts and can download the

data into a spreadsheet.

198. Volume-II

Clause 3.6.14.3

(Integration with other

Systems)

MDM integration with other systems shall include but not be limited to the following: b. Utility Administration……..

Please elaborate the requirement. The provisions of the RfP

shall prevail.

199. Volume-II

Clause 3.8 (Cloud

Service Provider (CSP)

Requirements)

General IT Infra for hosting HES and MDM for both Shimla and Dharamsala locations should be on same cloud

Suggestion accepted

200. Please specify whether IT infra on cloud is to be hosted on public cloud or Government Community Cloud (GCC)

Hosting of both DC and DR

should be on GCC along

with latest generation of

servers 2.4 Ghz and above

201. Volume-II

Clause 3.8.3(e) (Cloud

Network Requirement)

CSP should ensure that Internet vNIC card is having minimum 1 Gbps network connectivity and service NIC card is on 10 Gbps for better internal communication

Please elaborate the requirement of vNIC in Cloud

The same to be as per

MEITY Guidelines

202. Volume-II

Clause 3.8.3(g) (Cloud


Must ensure that public IP address of cloud VMs remains same even if cloud VM gets migrated to another data center due to any incident

Since the Internet subnets are different at all Datacenters (multiple DC of same CSP or Multiple DC of Multiple CSP), it is technically impossible to keep the public IP same during the VM movement. Please clarify

Clause Deleted

203. Volume-II

CSP must ensure that public IP address of cloud VMs remains same even if cloud VM

Clause Deleted


Page 64 of 84


Clause 3.8.3(h) (Cloud


network is being served from multiple CSP datacenters.

204. Volume-II

Clause 3.8.5(c) (Cloud

Storage Service

Requirements)

CSP should clearly differentiate its storage offering based on IOPS. There should be standards IOPS offering per GB and high-performance disk offering for OLTP kind of workload. CSP should delivery minimum 8000 IOPS per TB for OLTP load. The IOPS for

The clause may be amended as per the following: “CSP should clearly differentiate its storage offering based on IOPS. There should be standards IOPS offering per GB and high-performance disk offering for OLTP kind of workload. CSP should delivery minimum 3000 8000 IOPS per TB for OLTP load. The IOPS for”

CSP should delivery

minimum 3000 IOPS per TB

for OLTP load.

However IOPS should be

sufficient to cater to the

performance requirement of

the project during its entire

life cycle.

205. Volume-II

Clause 3.8.7(a) (Data

Management)

CSP should clearly define policies to handle data in transit and at rest.

Please share the details of the policies.

The same to be as per

MEITY Guidelines

206. Volume-II

Clause 3.8.8(b) (Disaster

Recovery Management)

RPO should be less than or equal to 2 hours and RTO shall be less than or equal to 12 hours

As per this clause, the required RPO is 2 Hours. However, as Clause 4.4.16 (Service Level Agreements), the required RPO is 4 Hours. Please clarify


No. 2 to RfP (SLA Part).

RPO and RTO shall strictly

be as per MEITY Guidelines

207. Volume-II

Clause 3.8.8(e) (Disaster


In the event of a site failover or switchover, DR site will take over the active role, and all requests should be routed through that site. The pre-requisite to route request to DR should be articulated properly and shared by CSP

Please confirm whether HPSEB is looking for Active or Passive DR.


shall prevail.

208. Volume-II

Clause 3.8.8(f) (Disaster


Whenever there is failover from primary to secondary, compute environment for the application at DR site shall be equivalent to DC

Please confirm about the security

component redundancy at DR site that

needs to be considered.


shall prevail.

209. Volume-II

Clause 3.8.8(i) (Disaster


The CSP shall clearly define the procedure for announcing DR based on the proposed DR solution. The CSP shall also clearly specify the situations in which disaster shall be announced along with the

Please confirm the number of mock DR Drill required in a year in order to check business continuity.

The number of mock DR

Drill required in a year

would be at least 2

210. Announcing the DR cannot be a sole The same shall be as per


Page 65 of 84


implications of disaster and the time frame required for migrating to DR. The CSP shall plan all the activities to be carried out during the Disaster Drill and issue a notice to the Department at least two weeks before such drill

responsibility of CSP. It should be a joint responsibility of Bidder/ consortium member and Customer. A Disaster Recovery Committee/ Panel must be formed including members from all stakeholders to decide and announce the DR.

the DR Implementation Plan

to be finalised post Award

of Contract

211. Volume-II

Clause 3.8.11(c) (Web

Application Firewall as

Service)

CSP WAF should be able to perform packet inspection on every request covering all 7 layers

As WAF works on 7th layer of OSI, please amend the clause as per the following: "CSP WAF should be able to perform packet inspection on 7 7th (Application layer of OSI) layers.


No. 2 to RfP

212. Volume-II

Clause 3.8.12(i)

(Database support

service)

Configuration, installation & maintenance of Automatic Storage Management (ASM), capacity planning/sizing estimation of the Database setup have to be taken care by the vendor.

As ASM is a part of Oracle database, please remove this clause.

The same shall be as per

provisioned database

requirements

213. Volume-II

Clause 3.8.13 (Cyber

Security)

General As per RFP, required security components are Firewall, IPS/IDS, Antivirus, SIEM, DDoS, HIPS, WAF. Please confirm whether the bidder needs to provide the above security devise as a cyber-security.

Please also confirm whether the security Firewall, IPS/ IDS, Antivirus, SIEM, DDoS, HIPS, and WAF can be proposed on software/ Virtual/ hardware instance.


shall prevail.

214. Volume-II

Clause 4.4 (Service

Level Agreements)

General Please amend as per Annexure-I Please refer Amendment

No. 2 to RfP.

215. Availability of GPRS services is on

best-effort basis as none of the

network service providers (Airtel,

Vodafone Idea, etc.) commit to any


shall prevail.


Page 66 of 84


kind of SLA. Therefore, downtime

occurred because of non-availability

of network shall not be factored while

calculating SLA and no penalty should

be levied from the contractor because

of this issue.

216. Volume-II

Clause 4 (Service Level

Agreements - Scheduled

Interval data readings at

a fixed periodicity during

the day as decided by

utility)

Periodic collection of the 15/30 minute

interval load profile data after every

15/30/60/120 minutes

i. From 95% of meters within 5 minutes

ii. From 98% of meters before next

periodic packet is scheduled


following:

“Periodic collection of the 15/30 minute


15/30/60/120 minutes

i. From 95% 90% of meters within 5 10

minutes

ii. From 98% 95% of meters before next

periodic packet is scheduled”


shall prevail.


following:

“Periodic collection of the 15/30 minute


15/30/60/120 minutes

i. From 95% of meters within 5 60

minutes

ii. From 98% of meters before next

periodic packet is scheduled


shall prevail.

218. Volume-II


Agreements - Remote

load control commands

for selected meters with

acknowledgement/

response for selected

meters)

The clause specifies SLAs for a group of

maximum of 5000 AMI meters

In all other Parameters in SLA like Ping Response and Remotely Read events, a group of 1000 meters are considered. Please amend these clauses as 1000 meters to maintain the consistency.


shall prevail.


Page 67 of 84


219. Volume-II


Agreements - For remote

connect/disconnect with

acknowledgement/


meters)

220. Volume-II


Agreements - Remotely

altering settings in meter/

firmware upgrade with

acknowledgement/


meters)

For a group of 1000 AMI meters:

Action performed at 99% of meters

within 30 minutes; and

Action performed at 99.5% of meters

within 1 hour

Remote firmware upgrade depends on size of firmware image which varies with meter type, works on multicasting principle. HES always try to upgrade the firmware during low traffic of the day. Hence, for firmware upgrade, it is advisable to follow the CEA guidelines which is globally accepted and implemented across Indian Utilities. As per CEA guidelines the SLA is

Action performed at 99% of meters within 24 hours; and

Action performed at 99.9% of meters within 36 hours.

Please amend the clause accordingly


No. 2 to RfP.

221. Volume-II


Agreements - AMI

Network (all hardware,

software, smart meters,

Cloud Infrastructure and

field equipment) Uptime)

99% on Monthly basis.

Penalty will be 1% of the FMS Charges

per month for every 1% or part there of

decrease in availability under 99%).

Penalty will be calculated separately for

Hardware and Software Availability. The

maximum deduction shall be limited to

FMS charges paid for that particular

period.


following:

“Penalty will be 1% of the FMS Charges

of non-read Meters per month for every

1% or part there of decrease in

availability under 99% 95%). Penalty will

be calculated separately for Hardware

and Software Availability. The maximum

deduction shall be limited to FMS

charges paid for that particular period.”


shall prevail.

222. Volume-II

General Since bidder is supposed to quote

lumpsum charges for Training in price bid

Training would have to be

provided to the identified


Page 68 of 84


Clause 5.1 (Training

Requirements – General)

format, please give details about no. of

person attending the training, no of

days for each training etc.

personnel of PFCCL and

HPSEB on operation and

maintenance of AMI

Infrastructure (at least 2

times a year during first 3

years for 6 persons per

batch)

223. Volume-II

Clause 5.1.4 (Training

Requirements – General)

In addition two Engineer’s from utility and/

or PFCCL shall be stationed at the

contractor’s works during development/

customization of solution as per tender.

The deputed utility/ PFCCL engineers

shall be involved with the project till its

completion

We understand that the expenses of

those engineers like Lodging,

Boarding, travel etc. will be borne by

the customer.


bidder is correct.

224. Volume-II

Clause 6 (System

Hardware Requirements)

System Hardware Requirements We understand that the requirements

are in generic for the control center

hardware that are to be deployed at

DISCOM and are generic guidelines for

the cloud infrastructure. Kindly clarify.

The System Hardware

Requirements shall be as

per MEITY guidelines for

cloud

225. We understand that this section was

prepared considering the entire IT

infrastructure to be at HPSEB

premises. However as IT hardware

setup will be hosted on cloud for

which specifications & requirements

are already mentioned in the tender

document, this section should be

removed from tender document.

226. Volume-II

Clause 6.2 (System

Hardware Requirements

- Hardware

General Please confirm whether the specification is for onsite.


Page 69 of 84


Configuration)

227. Volume-II

Clause 6.3.2 (System

Hardware Requirements

- Router)

General As infrastructure is proposed on Government community cloud and perimeter router cannot be configured as per specific client requirement, it has to be setup as per the standard data centre rule. Please confirm that the router will be in shared mode.

228. Volume-II


Software Requirements -

Software Standards -

Design and Coding

Standards for AMI

Applications and Utilities)

General As standard products will be offered

as software solutions, these standards

will not be applicable.

Standard products offered

should meet the

requirements of the project.

The licenses for infra

should be genuine.

229. Volume-II

Clause 7.1.2(b) (System



Applications)

Modularity: Software shall be modular i.e. functionally partitioned into discrete, scalable, reusable modules consisting of isolated self-contained functional elements & designed for ease of change. The system shall make maximum use of common industry standards for interfaces

As standard products will be offered

as software solutions, these standards

will not be applicable.


shall prevail.

230. Volume-II

Clause 7.1.2(d) (System



Applications)

Portability & Interoperability: The system shall be designed for hardware independence and operation in a network environment that facilitates interoperability and integration of third party applications. AMI applications should support multiple RDBMS systems including Oracle, Microsoft SQL Server and MySQL

The HES solution to be provided by us

supports only MySQL and MDM

solution supports only MS-SQL. These

are not interoperable with other

RDBMS. Kindly clarify whether this is

acceptable.


shall prevail.


Page 70 of 84


231. Volume-II




Operating System)

The operating system of all the equipment

of AMI application system including

network equipment shall be latest version

released up to six months prior to FAT.

The operating system shall be hardened to

provide robust security. The operating

system and data file shall be placed in

different disk partitions…..

The operating system for running AMI

applications should be selected on the

basis of best compatibility with

application software, selected at the

time of bidding. However, the

contractor shall ensure all the

functionalities and efficiency as

expected by HPSEB/ PFCCL in this

tender.


shall prevail.

232. Volume-II



Network Software -

Network Management

System (NMS))

….. The network management software

shall be based on the latest secured

version of Simple Network Management

Protocol ver. 3.0 (SNMPv3)….

Please delete ver. 3.0 (SNMPv3) The provisions of the RfP

shall prevail.

233. ……. Apart from real-time monitoring of

critical network devices, the above

information shall be collected and stored

at user configurable periodicities i.e. 5

minutes to 60 minutes. The Network

Management System (NMS) shall be

capable of storing the above data for a

period of one (1) year at an interval of 5

minutes….


following:

“…. Apart from real-time monitoring of

critical network devices, it should also

be capable of supporting historical

data… the above information shall be

collected and stored at user

configurable periodicities i.e. 5

minutes to 60 minutes. The Network

Management System (NMS) shall be

capable of storing the above data for a

period of one (1) year at an interval of

5 minutes”


shall prevail.

234. …. In case more than one technology of

AMI (example PLC and RF between Smart

Meter & DCU) deployed in the field. It shall

maintain statistics on the performance and

availability of data being delivered per AMI

technology

Please delete as PLC would not be

applicable


shall prevail.

235. Volume-II General

As standard products will be offered Please refer Amendment


Page 71 of 84




Database –

Development Tools)

as software solutions, no development

tool is required & will not be supplied.

Please confirm.

No. 2 to RfP.

236. Volume-II

Clause 7.4 (System


Display Generation,

Management and

Integration (Display

Management and

Reporting))

The Contractor shall provide necessary

software tools preferably browser based

for the generation, management and

Integration of AMI application displays.

Displays shall be generated and edited

interactively using this display generation

software delivered with the system. All

displays, symbols, segments, and user

interaction fields shall be maintained in

libraries. The size of any library and the

number of libraries shall not be

constrained by software. The display

generator shall support the creation,

editing, and deletion of libraries, including

copying of elements within a library and

copying of similar elements across

libraries. Execution of the display

generator functions shall not interfere with

the on-line AMI application functions…..

Request to remove this entire clause

as the specifications are similar to

SCADA system and not required in

AMI package.


shall prevail.

237. Volume-II

Clause 9.13.2

(Maintenance - Payment

of FMS Charges)

Availability

of AMI

System per

Month

% Deduction

> 99% NIL

Less than

99%

Penalty will be 1% of the FMS

Charges per month for every 1% or

part there of decrease in availability

under 99%). Penalty will be calculated

separately for Hardware and Software

Please maintain SLA @ 97% below

which penalty should be applicable.


No. 2 to RfP.


Page 72 of 84


Availability. The maximum deduction

shall be limited to FMS charges paid

for that particular period.

238. Volume-II

Annexure A (A2) (Whole

Current A.C. Single

Phase Two Wire Smart

Energy Meter Of

Accuracy Class 1.0 (with/

without net-metering) -

Communication)

………..In case of GPRS/3G/4G based

meter, the meter shall accommodate SIM

card of any service provider………..

It is requested to amend the clause as

per the following:

“In case of GPRS/3G/4G based meter or

NBIoT with fall back to GPRS, the

meter shall accommodate SIM card of

any service provider”


shall prevail.

239. Volume-II


Current A.C. Single


Energy Meter Of


without net-metering) –

Other Specifications -

Current Rating)

5-30A / 10-60A We understand the current rating shall be

10-60 A as per BOQ


No. 2 to RfP (BoQ Part).

240. Volume-II


Current A.C. Single


Energy Meter Of




Real Time Clock(RTC))

As per IS 16444/ IS 15884

The clock day/ date setting and

synchronization shall only be possible

through password/ Key code command

from one of the following:

From remote server through

suitable communication network.

Hand Held Unit (HHU) or Meter testing

work bench and this shall need

password enabling for meter;

The methodology for the

synchronization would be as per

In AMI, RTC is kept in sync by the

system. RTC updation through HHU

with the help of optical port is not

recommended due to security

concerns.

Hence, programming in AMI will be done

Over the air.


No. 2 to RfP.


Page 73 of 84


requirement of Utility

241. Volume-II


Current A.C. Single


Energy Meter Of




Anti-Tamper Features)

….. Meter shall be tested for high voltage

discharge (Spark) up to 35 KV as per

CBIP 325.

We understand that Meter would be

tested as per the field condition. Please

define the testing method.


shall prevail.

242. Volume-II

Annexure B (B3) (Whole

Current A.C. Three

Phase Four Wire Smart

Energy Meter Of




Current Rating)

10-60 A / 20-100 A We understand the current rating shall

be 20-100A as the consumer

requirements are increasing every year


No. 2 to RfP (BoQ Part).

243. We understand that 10-100A rating will

also be acceptable against 20-100A as it

provides extended range of energy

measurement

244. Volume-II


Current A.C. Three


Energy Meter Of




Real Time Clock(RTC))

As per IS 16444/ IS 15884

The clock day/ date setting and

synchronization shall only be possible

through password/ Key code command

from one of the following:

From remote server through

suitable communication network.

Hand Held Unit (HHU) or Meter testing

work bench and this shall need

password enabling for meter;

The methodology for the

synchronization would be as per

In AMI, RTC is kept in sync by the

system. RTC updation through HHU

with the help of optical port is not

recommended due to security

concerns.

Hence, programming in AMI will be done

Over the air. Please clarify.


No. 2 to RfP.


Page 74 of 84


requirement of Utility

245. Volume-II


Current A.C. Three


Energy Meter Of




Data Display Facility

(Manual/ Automatic))

… Current month MD in kVAh… It seems there is a typographical error in mentioning 'kVAh' instead of 'kVA' for MD at different places in specifications. We request you to kindly amend the

clause


No. 2 to RfP.

246. Volume-II

Annexure C (C1) (Three

phase CT operated

alternating current smart

meter Of Accuracy Class

0.5S (with/ without net-

metering) – General

Standards Applicable for

Meter

IS 15959 Part 1 & Part 2 with latest

amendments

For LTCT Operated Meters the applicable DMLS Standard is IS 15959 Part 3. You are requested to replace 'IS 15959 Part 2' with the prevailing DMLS 'IS 15959 Part 3 Standard'


No. 2 to RfP.

247. Volume-II


phase CT operated




metering) – Other

Specifications – Time of

Use (In case of net-

meter both export &

Should support at least eight (8) Time of

day tariff registers with programmable

time zones and storage of billing

parameters (kW, kVA, kWh & kVAh)

As per IS 15959 Part 2 and 3, TOD

parameters are defined for import

energy and import demand only.

Please clarify.


shall prevail.


Page 75 of 84


import parameters to be

measured))

248. Volume-II


phase CT operated




metering) – Other

Specifications -

Parameters With net-

metering)

Instantaneous parameters: As per category

C1 meters according to IS 15959: Part-3:

2017.

Billing parameters: As per category B

meters according to IS 15959: Part-3:

2017

Load survey / Interval data parameters:

As per category B meters according to IS

15959: Part-3: 2017. 35 (Power ON) days

data to be recorded with 15 minutes

integration period. The register shall

automatically rollover the data after 35

days based on first in first out (FIFO).

Instantaneous Voltage, Instantaneous

Current and Instantaneous Power Factor

have to read for every 15 minutes as

part of Interval data. The billing

parameters shall be retained in the meter

for 6 months and should automatically

rollover.

Category defined for LTCT smart

meters as per IS 15959 part 3 is D3 and

profiles parameters are defined in

standard for same.

Suggestion accepted

249. Category B’ is not applicable for Smart LT CT Operated Meters and not available in DLMS IS 15959 Part 3 Standard. This seems to be typographical error.

Please replace the 'Category B' with

'Category D3' in the specification.

250. Volume-II


phase CT operated




metering) – Other

Specifications - Power

Quality Information)

Logging of quality of supply events like

power on/off, over/under voltage, over

current ( 50 events)

Setting of Under/ Over Voltage and Over

current shall be configurable.

The Tamper Events shall be provided as per the Event Compartments defined in DMS IS 15959 Part 3 Standard. You are requested to accept the same.


IS

251. The OBIS Codes are not available for Over Voltage, Under Voltage & Over Current Events in dlms IS 15959 Part 3 Standard. You are requested to provide the same

Suggestion accepted


Page 76 of 84


or accept the OBIS codes provided by us.

252. Volume-II


phase CT operated




metering) – Other

Specifications - Load

Survey/Interval Data)

…..Instantaneous Voltage, Instantaneous

Current and Instantaneous Power Factor

have to read for every 15 minutes as

part of Interval data.

Load survey is average value of

Interval period as per DLMS, so

average values for every 15 minutes

will be read. Please clarify


IS

253. Volume-II

Annexure C (C3) (Three phase CT operated alternating current smart meter Of Accuracy Class 0.5S (with/ without net-metering) – Other Specifications - LED/ LCD Indicators)

LED indicator for pulse/kWh. LED/ LCD

indicator for tamper, disconnection, current

reversal (not for net-metering).

'Disconnection' is not applicable for LT CT Operated Smart Meter. You are requested to remove this

requirement from the specification.


No. 2 to RfP.

254. Volume-II


phase CT operated




metering) – Other

Specifications -

Tamper/Event recording)

As per IS 15959 Part-I. 200 events shall

be stored in local memory of meters

For Smart LT CT Operated Meters applicable standard is IS 15959 Part 3. This seems to be typographical error

and you are requested to replace 'IS

15959 Part 1' with 'IS 15959 Part 3'.


No. 2 to RfP.

255. Volume-II

Alarm for power on/ off (on restoration

of power), Under Voltage, Over Voltage,

As per IS 15959 part 2 and part 3,

diagnostic are not part of any event


No. 2 to RfP.


Page 77 of 84



phase CT operated




metering) – Other

Specifications - Alarm)

Over Current, malfunctioning of

diagnostic events shall be generated and

communicated to the HES immediately

profile

256. Volume-II


phase CT operated




metering) – Other

Specifications -

Measuring Elements)

Meter should have four measuring

elements - three in phases and one in

neutral path.


following:

“Meter should have three measuring

element - one in each phase and also

shall have neutral sensing element for

detection and analysis purpose.”


No. 2 to RfP.

257. Volume-II


phase CT operated




metering) – Other

Specifications - Anti-

Tamper features)

The meter shall continue recording

energy under any tamper condition and

would log the event and send alarm at

Head End System after detection of the

defined theft features as per IS 15959

Part 2.

Optional test as per requirement of utility:

The Meter shall be immune under external

magnetic influences as per CBIP 325.

Meter shall be tested for high voltage

discharge (Spark) up to 35 KV as per

CBIP 325.

For LT CT Operated Smart Meters the applicable dlms Standard is IS 15959 Part 3. You are requested to kindly replace IS

15959 Part 2 with IS 15959 Part 3.


No. 2 to RfP.

258. Volume-II


The port for local communication and

baud rate shall be as per IS 15959. In

addition to this the meter will have a

We recommend only plug and play

modular design. Field replaceable

communication module will help the Utility

Communication module

has to be modular and plug

& play type for all meter


Page 78 of 84


phase CT operated




metering) – Other

Specifications -

Communication)

provision for an Integral modular plug in

type OR built in type Communication

Module for NAN (Neighbourhood Area

Network) i.e. from Meter to router/ access

points/ data collector or directly for WAN

(Wide Area Network).

in field analysis and solutions. types

259. Volume-II

Annexure F (F2) (Data

Requirement Sheet -

Three Phase Whole

Current Smart Meter -

Data Display Facility

(Manual/ Automatic))

… Current month MD in kVAh… It has been mentioned 'kVAh' instead of 'kVA' for Maximum Demand at different places in specifications. This seems to be typographical error

and we request you to kindly amend

as KVA Maximum Demand (MD)

accordingly.


No. 2 to RfP.

260. Volume-II


Requirement Sheet -

Three Phase CT

Operated Smart Meter -

Parameters With net-

metering))

Instantaneous parameters: As per

category C1 meters according to IS

15959: Part-3: 2017

Billing parameters: As per category B

meters according to IS 15959: Part-3:

2017.….

Category shall be D3 for Smart LT CT Operated Meter. This seems to be typographical error and you are requested to replace 'C1' with 'D3'.

Suggestion accepted

261. ‘Category B’ is not applicable for Smart LT CT Operated Meters and not available in IS 15959 Part 3. This seems to be typographical error and you are requested to replace 'Category B' with 'Category D3' in the specification.

262. Volume-II


Requirement Sheet -

Three Phase CT


Logging of quality of supply events like

power on/off, over/under voltage, over

current (50 events)….

Events shall be provided as per Event

Compartments defined in IS 15959

Part 3. Please clarify

The OBIS Codes are not available for Over Voltage, Under Voltage & Over Current Events in dlms IS 15959 Part 3

The events would be as per

IS.

However, the suggestion on

OBIS codes accepted


Page 79 of 84


Power Quality

Information)

Standards. You are requested to provide the same

OR accept the OBIS codes provided

by us.

263. Volume-II


Requirement Sheet -

Three Phase CT


LED/LCD Indicators)

LED indicator for pulse/kWh. LED/LCD

indicator for tamper, disconnection,

current reversal (not for net-metering).

The 'Disconnection' feature is not applicable for LT CT Operated Smart Meter. You are requested to remove this

requirement of Disconnection from the

LT CT Operated Meter Technical

Specification.


No. 2 to RfP.

264. Volume-II


Requirement Sheet -

Three Phase CT



As per IS 15959 Part-I. 200 events shall

be stored in local memory of meters

For Smart LT CT Operated Meters applicable Standard is IS 15959 Part 3. This seems to be typographical error and you are requested to replace 'IS 15959 Part 1' with 'IS 15959 Part 3' and amend the clause.


No. 2 to RfP.

265. Volume-II


Requirement Sheet -

Three Phase CT



The meter shall continue recording

energy under any tamper condition and

would log the event and send alarm at

Head End System after detection of the

defined theft features as per IS 15959

Part 2…

For LT CT Operated Smart Meters the applicable dlms Standard is IS 15959 Part 3. So, we request you to kindly replace IS

15959 Part 2 with IS 15959 Part 3 and

amend the clause.


No. 2 to RfP.

266. Volume-II


Requirement Sheet -

Data Concentrator Unit

(DCU) (If Applicable))

…… The DCU shall ensure the appropriate

backhaul for secure transfer of data to

HES either via GPRS 3G/4G or Fiber

Optic communication. In case of

GPRS/3G/4G backhaul, it shall support

SIM card with dynamic IP from any

service provider. It shall have Wide Area


following:

“… The DCU shall ensure the appropriate

backhaul for secure transfer of data to

HES either via GPRS 3G/4G or Fiber

Optic communication. In case of

GPRS/3G/4G backhaul, it shall support


No. 2 to RfP


Page 80 of 84


Network (WAN) connectivity to the HES

through suitable means

APN based SIM card with dynamic IP

from any service provider. It shall have

Wide Area Network (WAN) connectivity to

the HES through suitable means.”

267. ….. DCU shall be able to communicate

with meters either on RF mesh

(Unlicensed or Licensed frequency band

as permitted by WPC) or PLC

Please remove PLC as the same is not

applicable


No. 2 to RfP

268. Volume-II

Annexure G (G1)

(System Sizing

Requirement – Sizing

Parameter)

…. The system shall be suitably sized

based on data to be captured from

1,35,000 nodes with 20% expansion….

Please amend the Scope of Licence as

current scope is 1.5 Lakh Meters.

The system shall be

suitably sized based on

data to be captured from

the no. of nodes as per

Price Bid Format (Annexure

17) with 20% expansion for

project area. However, the

bidder has to develop the

overall AMI architecture in

such a manner that it meets

the scaling up requirements

of entire HPSEB in future to

the extent mentioned in the

RfP.

269. Volume-II

Annexure G (G2)

(System Sizing

Requirement –

Configuration

requirement for

Hardware & Software)

S. No.

Description No of Nodes Future

requirement

1 Head End System (HES)*

1,35,000 20% Expansion

2 Meter Data Management System (MDM)*

1,35,000 20% Expansion

Please clarify the Quantity of Meters for

sizing of Cloud.

The no. of nodes would be

as per Price Bid Format

(Annexure 17) with 20%

expansion for future

requirement for project

area. However, the bidder

has to develop the overall

AMI architecture in such a

manner that it meets the

scaling up requirements of

entire HPSEB in future to


Page 81 of 84


the extent mentioned in the

RfP.

270. Volume-II

Annexure H (Display

Parameters for 3-Phase

CT Operated Smart

Meters)

In the RfP, Auto Scroll mode as well as

manual push mode scroll parameters list

given separately

Under Auto mode i.e. Mode 1, two

separate display list cannot be given for

auto as well as manual with press of push

button.

For manual push mode parameters,

separate mode is given as mentioned in

mode 2.


shall prevail.

271. Volume-II

Annexure H (Display


CT Operated Smart

Meters - Parameters of

this mode should display

manually on up & down

scrolling using push

button)

Sr. No. of Meters - UTP The requirement of 'UTP' is not clear. The numeric Meter Serial Number can be provided on Meter Display in line with the number of Display Digit requirement. We request you to kindly accept the

Meter Serial number.

Suggestion accepted

272. 24 hrs apparent energy derived from

Vectorial summation of total (fund+

Harm.) active energy and reactive (lag

only) energy

As meters record energy as a cumulative

parameter, the requirement for 24 hrs

should be deleted.

Same shall be applicable for all energy

mentioned in Annexure H.

For consumption of last 24 hrs, utility

can refer daily survey/ profile and

consumer can get last 24 hours

apparent energy in Mobile App.


shall prevail.

273. Volume-II

Annexure H (Display


CT Operated Smart

Meters - Parameters of

this mode should

MD Kvar after last billing – (24 Hrs)

Cumm KVARH-lag for (Zone-upto 8)

The OBIS Codes are not available for

'MD kVAr' and Zone wise kVArh Lag in

dlms IS 15959 Part 3 Standard.

Please remove these lines as Reactive

MD and Reactive energy TOD zone wise

is not a requirement as per IS15959 part


shall prevail.


Page 82 of 84


display manually up &

down scrolling using

push button under

Mode-2)

3.

274. - - The requirement of external CT and its

Ratio has not been defined in the RfP.

Please define the CT ratio & accessories

to be supplied with Box.

The CT operated meters

have to be supplied and

installed by replacing the

existing meters and there is

no requirement of supply of

CT and box.


Page 83 of 84

Annexure-I

Data Type Changes Suggested by Bidder for Performance Requirement Reply/ Clarification

1. Scheduled Interval data readings at a fixed periodicity during the day as decided by utility Please refer Amendment No. 2 to RfP

Periodic collection of the 30 minute interval load profile data after 4 hours / 8 hours / 12 hours

From 90% of meters within next periodic packet is scheduled.

From 95% of meters before next consecutive periodic packet is scheduled.

2. Scheduled daily meter readings (as per IS 16444/15959)

Daily collection of the previous day’s interval energy data and total accumulated energy

From 90% of meters within 8 hours after midnight; and

From 95% of meters within 24 hours after midnight

3. Scheduled billing/ load profile data for bill period

Collection of billing/load profile data for the bill period for entire installed population

From 90% of meters within 24 hours after midnight; and

From 95% of meters within 48 hours after midnight

4. On-Demand Remote reads of meters

Collection of 7 days of interval energy data and the current total accumulated energy from a group of 1000 AMI meters

Action performed at 85% of meters within 1 Hour; and

Action performed at 90% of meters within 2 hours; and

Action performed at 95% of meters within 6 hours

Collection of 7 days of interval energy data & current total accumulated energy from a selected individual meter

Action performed within 10 mins

5. Updating of data on consumer portal/ app

Updating of individual consumer data on portal/ app after receiving the data in MDM

Action performed for active consumers within 5 minutes after receiving the data in MDM

Action performed at 99.5% of meters within 2 hours after receiving the data in MDM.

6. Ping Response with acknowledgement/ response for selected meters

For a group of 1000 communicating meters Action performed at 90% of meters within 5 minute; and

For an individual communicating meter Action performed within 5 seconds

7. Remote load control commands for selected meters with acknowledgement/ response for selected meters

For a group of maximum of 5000 AMI meters Action performed at 85% of meters within 5 minutes; and

Action performed at 90% of meters within 10 Minutes

For an individual meter Action performed within 1 mins

8. For remote connect/disconnect with acknowledgement/ response for selected meters

For a group of maximum of 5000 communicating Action performed at 85% of meters within 5 minutes; and


Page 84 of 84

AMI meters Action performed at 90% of meters within 10 minutes; and

Action performed 95% of meters within 20 minutes

For an individual communicating meter Action performed within 1 minute

9. Meter loss and restoration of supply

Receiving of alert for all affected AMI meters spread across the project area

Alert to be received within 5 minutes for 60% of meters

10. Meter Tamper Alerts

Receiving of alert for an individual meter Alert to be received within 5 minutes

11. Power Quality Alerts

Receiving of alert for an individual meter Alert to be received within 5 minutes

12. Remotely altering settings in meter/ firmware upgrade with acknowledgement/ response for selected meters

For a group of 1000 AMI meters Action performed at 90% of meters within 15 days; and

Action performed at 95% of meters within 30 days

13. Remotely read events logs

For reading the full event log for a group of 1000 AMI meters

Action performed at 85% of meters within 30 minutes; and

Action performed at 90% of meters within 1 hour; and

Action performed at 95% of meters within 6 hours.

14. AMI Network (all hardware, software, smart meters, Cloud Infrastructure and field equipment) Uptime

95% on Monthly basis. Penalty will be 1% of the FMS Charges per month for every 1% or part there of decrease in availability under 95%). Penalty will be calculated separately for Hardware and Software Availability. The maximum deduction shall be limited to FMS charges paid for that particular period.

15. Cloud Infrastructure uptime 99%

16. Recovery Point Objective for AMI MDM and HES System

4 Hours

17. Recovery Time Objective for AMI MDM and HES System

12 Hours

Documents

Date: November 15, 2019 E- Tender No. Smart Metering ... · including smart meters (with/without net-metering) with Pre-paid configuration, communication infrastructure along with