Request for Proposal

For

Appointment of Advanced Metering

Infrastructure Service Provider for
Smart Prepaid Metering in
BSES YAMUNA POWER LTD BSES

on DBFOOT basis

NIT NO.: CMC/BY/24-25/RS/SKS/APT/37

Due Date for Submission: 07.10.2024, 11:30Hrs

BSES YAMUNA POWER LTD.

Corporate Identification Number: U40109DL2001PLC111525

Website: [Link]

NIT NO.: CMC/BY/24-25/RS/SKS/APT/37

SUMMARY

Volume I – BIDDING PROCEDURES AND REQUIREMENTS

Section 1: Request for Proposals (RFP) Notice

This Section includes Request for [Link] Section also contains information regarding
specific eligibility and qualification requirements applicable for prospective bidders to be
considered for further evaluation of their proposal.

Section 2: Instructions to Bidders and Bid Data Sheet

This Section consists of two parts: “Instructions to Bidders” and “Bid Data Sheet”. “Bid Data Sheet”
contains information specific to selection and corresponds to the clauses in “Instructions to
Bidders” that call for selection-specific information. This Section provides information to help
prospective bidders prepare their proposals. Information is also provided on submission, opening
and evaluation of proposals, selection of successful bidder and award of contract.

Section 3: General Terms and Conditions

All the Bids shall be prepared and submitted in accordance with instructions provided in Section 3
of this RFP document

Section 4: Code of Conduct

This Section includes Vendor Code of Conduct (the "Code") for Purchaser’s Vendors. This Code
BSES

encourages Vendors to go beyond legal compliance, drawing upon internationally recognized

standards, in order to advance social and environmental responsibility.

Section 5: Special Conditions of Contract

This section includes all the activities that are to be undertaken by the bidder to realize the
contractual deliverables completeness as per Scope of Work.

Section 6: Project Requirements - Scope of works

This Section describes the background information of the Project, Scope, of Work, System
Requirement, Specifications, Quality Requirements, Service Level Agreement (SLA), Standards,
Activities and Tasks, Plans, Deliverables, Documentation, and other requirements/ details related
to and/or connected with the Project.

Section 7: Price Format

This Section includes the financial forms that are to be completed by the prospective bidders,
including the bidders’ costing and pricing, which are to be submitted in accordance with the
requirements in this RFP document.

Page 2 of 473
Volume II – Bidding and Contract Forms
Section 8: Forms- Technical and Financial Proposal

This Section includes the forms for Technical and Financial Proposal that are to be completed by
the prospective bidders and submitted in accordance with the requirements of this RFP Document.

Section 9: Contract Related Forms

This Section includes the form used to notify Award of the Contract to the successful bidder and
the form for Performance Security to be furnished by the bidder.

BSES

Page 3 of 473
LIST OF ABBREVIATIONS
S. No. Acronym Term
1. ACI Available Capital for Investment
2. AMI Advanced Metering Infrastructure
3. AMISP Advanced Metering Infrastructure Service Provider
4. BG Bank Guarantee
5. BIS Bureau of Indian Standards
6. BoM Bill of Material
7. C&I Commercial and Industrial
8. CAIDI Consumer Average Interruption Duration Index
9. CAIFI Consumer Average Interruption Frequency Index
10. CEA Central Electricity Authority
11. CERT-In Indian Computer Emergency Response Team
12. CIM Common Information Model
13. CIS Consumer Information System
14. CMMI Capability Maturity Model Integration
15. CPU Central Processing Unit
16. CRM Consumer Relationship Management
17. CT Current Transformer
18. CUM Cumulative
19. CV Curriculum Vitae
20. DBMS Database Management System
21. DBFOOT Design Build Finance Own Operate and Transfer
22. DCU Data Concentrator Unit
23. DMZ Demilitarized Zone
24. DT Distribution Transformer
BSES

25. EC Energy Charges

26. ED Energy Data
27. EII Enterprise IT Infrastructure
28. EOB End of Billing
29. ERM Enterprise Release Management
30. ESB Enterprise Service Bus
31. FAT Factory Acceptance Test
32. FC Fixed Charges
33. FOR Freight on Road
34. GIS Geographic Information System
35. GPS Global Positioning System
36. GST Goods and Services Tax
37. GUI Graphical User Interface
38. HES Head-End System
39. HHU Handheld Unit
40. IBMS Integrated Building Management Systems
41. IDS Intrusion Detection Systems
42. IEC International Electrotechnical Commission
43. IP Internet Protocol
44. IPR Intellectual Property Rights
45. IPS Intrusion Prevention Systems
46. IS Indian Standard
47. ISO International Organization for Standardization
48. ISP Internet Service Provider
49. IT Information Technology
50. IVRS Interactive Voice Response System

Page 4 of 473
S. No. Acronym Term
51. kVA kilo Volt-Ampere
52. kW kilo Watt
53. LAN Local Area Network
54. LCD Liquid Crystal Display
55. LED Light Emitting Diode
56. LP Load Profile
57. LT Low Tension
58. M&V Monitoring and Verification
59. MCB Miniature Circuit Breaker
60. MD Maximum Demand
61. MDAS Meter Data Acquisition System
62. MDMS Meter Data Management System
63. MDCC Material Dispatch Clearance Certificate
64. MICC Material Inspection Clearance Certificate
65. MMC Monthly Minimum Charges
66. NAN Neighborhood Area Network
67. NIC Network Interface Card
68. NMS Network Management System
69. NTP Network Time Protocol
70. OEM Original Equipment Manufacturer
71. OS Operating System
72. OSF Open Software Foundation
73. P&L Profit & Loss
74. PCI Payment Card Industry
75. PMS Project Management System
76. PO Purchase Order BSES

77. PON Power Outage Notification

78. PRN Power Restoration Notification
79. PT Potential Transformer
80. PV Photovoltaic System
81. QA Quality Assurance
82. QC Quality Control
83. QR Qualification Requirement
84. RAM Random Access Memory
85. RC-DC Remote Connect-Disconnect
86. RDBMS Relational Database Management System
87. RF Radio Frequency
88. RFP Request for Proposal
89. RPO Recovery Point Objective
90. RTC Real Time Clock
91. RTO Recovery Time Objective
92. SAIDI System Average Interruption Duration Index
93. SAIFI System Average Interruption Frequency Index
94. SAN Storage Area Network
95. SAT Site Acceptance Test
96. SCADA Supervisory Control and Data Acquisition
97. SEBI Securities and Exchange Board of India
98. SI System Integrator OR System Integration
99. SLA Service Level Agreement
100. SNMP Simple Network Management Protocol
101. SOA Service Oriented Architecture
102. SPBM Smart Prepaid Billing Module

Page 5 of 473
S. No. Acronym Term
103. SQL Structured Queried Language
104. TCP Transmission Control Protocol
105. TOD Time of Day
106. TOU Time of Use
107. UDP User Datagram Protocol
108. UPS Uninterrupted Power Supply
109. VEE Validation Estimation and Editing
110. VM Virtual Machine
111. VoIP Voice over Internet Protocol
112. WAN Wide Area Network
113. WFMS Workforce Management System
114. WO Work Order
115. WPC Wireless Planning & Coordination Wing
116. XML Extensible Mark-up Language

BSES

Page 6 of 473
TABLE OF CONTENT

Volume 1: BIDDING PROCEDURES AND REQUIREMENTS ................................. 17

Section 1: Request for Proposal Notice.................................................................... 18
1. Request for Proposal ..................................................................................... 20
2. Qualification Criteria ...................................................................................... 22
3. Eligibility Requirements for Consortium ......................................................... 22
4. Qualification and Financial Requirements ..................................................... 25
1. 29
5. Bidding and Award Process .......................................................................... 32
6. Award Decision.............................................................................................. 34
7. Contact Information ....................................................................................... 34
Section 2: Instructions to Bidders and Bid Data Sheet ............................................. 35
1. General .......................................................................................................... 35
2. Scope of Work ............................................................................................... 35
3. Disclaimer ...................................................................................................... 35
4. Cost of Bidding .............................................................................................. 35
5. Bidding Documents ....................................................................................... 36
BSES

6. Amendment of Bidding Documents ............................................................... 37

7. Preparation / Language of Bids ..................................................................... 37
8. Documents Comprising the Bid ..................................................................... 37
9. Bid Form ........................................................................................................ 37
10. Earnest Money Deposit (EMD) ...................................................................... 38
11. Bid Prices ...................................................................................................... 38
12. Bid Currency .................................................................................................. 38
13. Period of Bid Validity ..................................................................................... 38
14. Alternative Bid ............................................................................................... 38
15. Format and Signing of Bid ............................................................................. 39
16. Submission of Bids ........................................................................................ 39
17. Deadline for Submission of Bid...................................................................... 40
18. One Bid Per Bidder........................................................................................ 40
19. Late Bid ......................................................................................................... 40
20. Modification and Withdrawal of Bid................................................................ 40
21. Evaluation of Bid............................................................................................ 40
22. Clarification of Bids ........................................................................................ 40
Page 7 of 473
23. Preliminary Examination of Bids / Responsiveness ....................................... 40
24. Evaluation and Comparison of Bids............................................................... 41
25. Contacting the Purchaser .............................................................................. 41
26. Award of Contract .......................................................................................... 41
27. Letter of Intent ............................................................................................... 42
28. Purchaser’s Right to Accept or Reject any or all Bids.................................... 42
29. Market Integrity .............................................................................................. 42
30. Bidder Confidentiality ..................................................................................... 42
31. Specifications and Standards ........................................................................ 42
32. Quantity Variation .......................................................................................... 42
Section 3: General Terms and Conditions............................................................... 43
1. General Terms and Conditions ...................................................................... 43
2. Definition of Terms ........................................................................................ 43
3. Interpretations................................................................................................ 47
4. Priority of Contract Documents: ..................................................................... 47
5. Packing, Packing List & Marking (wherever applicable) ................................ 48
6. Shelf Life of Goods (wherever applicable) ..................................................... 48
7. Shipping, Inspection and Dispatch Shipping (wherever applicable) .............. 48
BSES

8. Price Validity .................................................................................................. 50

9. Contract cum Performance Security Bank Guarantee (CPBG): .................... 50
10. Warranty/Defects Liability Period................................................................... 51
11. Return, Replacement or Substitution ............................................................. 51
12. Rights, Title and Interest to AMI System and Equipment .............................. 52
13. Intellectual Property ....................................................................................... 52
14. SLAs and SLA Audit ...................................................................................... 53
15. Time – The Essence of Contract ................................................................... 53
16. Contract Commencement date ...................................................................... 54
17. Contract Completion Date ............................................................................. 54
18. Contract Period /Time .................................................................................... 54
19. Contract Execution Completion Date ............................................................. 54
20. Contract Execution Period/Time .................................................................... 54
21. Applicable Laws and Jurisdiction of Contract ................................................ 54
22. Events of Default ........................................................................................... 55
23. Consequences of Default .............................................................................. 55
24. Force Majeure ............................................................................................... 55

Page 8 of 473
25. Severability .................................................................................................... 57
26. Sub-Contracting / Sub-Letting ....................................................................... 57
27. Recoveries..................................................................................................... 58
28. Waiver ........................................................................................................... 58
29. Indemnification .............................................................................................. 58
30. Termination of Contract ................................................................................. 58
31. Termination for BYPLS’s Convenience- Stands Deleted ................................ 59
32. Change Order ................................................................................................ 59
33. Confidential Information ................................................................................. 61
34. Documentation .............................................................................................. 62
35. Limitation of Liability ...................................................................................... 62
36. Acceptance .................................................................................................... 62
37. M.S.M.E ......................................................................................................... 62
38. Safety Code ................................................................................................... 63
39. Statutory Obligations ..................................................................................... 63
40. Human Resources Issues ............................................................................. 64
41. Workman Compensation ............................................................................... 66
42. Group Personal Accidental Insurance policy ................................................. 66
BSES

43. Staff and Workman ........................................................................................ 66

44. Third Party Insurance .................................................................................... 67
45. Security ......................................................................................................... 67
46. Environmental, Health & Safety Plan ............................................................. 67
47. Risk & Cost .................................................................................................... 68
48. Cleanliness & Precautions Instructions ......................................................... 68
49. Guidelines regarding inspection & maintenance of PITS/DUGS while
doing work at site in BYPL Area ............................................................................... 69
Section 4: Vendor Code of Conduct ........................................................................ 70
1. Vendor Code of Conduct ............................................................................... 70
2. Labor and Human Rights ............................................................................... 70
3. Health and Safety .......................................................................................... 71
4. Environmental................................................................................................ 72
5. Ethics............................................................................................................. 72
6. Management System ..................................................................................... 73
Section 5: Special Conditions of Contract ............................................................... 74
1. Rules of Interpretation ................................................................................... 74
2. Scope of Work ............................................................................................... 74
Page 9 of 473
3. Good Receipt (If and as applicable) .............................................................. 74
4. Billing Process: .............................................................................................. 75
5. Terms of Payment ......................................................................................... 75
6. Payment Security Mechanism ....................................................................... 79
7. Direct Debit Facility........................................................................................ 81
8. Contract Performance Bank Guarantee / Security ......................................... 81
9. Transit Insurance (Wherever applicable) ....................................................... 82
10. Liquidated Damages...................................................................................... 82
11. Penalty .......................................................................................................... 82
12. Completion Period ......................................................................................... 82
12.1. Access to Site ................................................................................................ 83
13. Termination of Contract ................................................................................. 83
14. Exit Management........................................................................................... 89
15. Transfer of Assets/ AMI Solution ................................................................... 90
16. Quality Assurance and Inspection ................................................................. 90
17. Test Certificate and Quality Assurance ......................................................... 91
18. Commissioning Spares .................................................................................. 91
19. Tools and Test Equipment ............................................................................. 91
BSES

20. Training ......................................................................................................... 91

21. Upgrades and Enhancements ....................................................................... 91
Section 6: Project Requirements and Scope of Work .............................................. 93
1. Introduction .................................................................................................... 93
2. Key drivers for Smart metering program ........................................................ 93
3. AMI Project Area ........................................................................................... 95
4. Indicative Smart Meter Roll out Plan ............................................................. 96
1. 96
1. 96
5. Overview of the AMISP Scope of Work ......................................................... 97
6. Overall System design principle and Architecture ....................................... 100
7. Responsibilities of the BYPL ....................................................................... 103
8. Supply, Installation, integration, testing and commissioning of: ................... 104
8.1 Smart Meters............................................................................................................104
8.2 Communication Infrastructure ...............................................................................105
8.2.1 Provisions of Cellular Network Services .....................................................106
8.3 General Requirements ...........................................................................................106
8.4 Unified Head End System (UHES) .......................................................................109

Page 10 of 473
 8.5 Meter Data Management System (MDMS) .........................................................116
8.6 Smart Prepaid Billing Module (SPBM) .................................................................140
8.7 Consumer Portal/ App ............................................................................................146
8.8 Smart Meter Operation Centre (SMOC) & WFMS .............................................149
8.9 System Software, Cloud and Database Requirements .....................................154
9. AMI System Integrations ............................................................................. 171
9.1 MDMS Integrations with BYPL IT/OT Systems ..................................................172
9.2 Unified HES Integrations with Field Devices ......................................................172
9.3 Integrated Network Management System ...........................................................173
9.4 SPBM Integration with MDMS, CIS and Gateway .............................................173
9.5 Integration with national level reporting platform ...............................................173
10. Consumer Engagement ............................................................................... 173
11. Advanced data Analytics and Reports ......................................................... 174
11.1 Database Software and Licenses ................................................................174
11.2 Minimum Functional Requirement ...............................................................174
11.3 Solar Data Analytics.......................................................................................175
11.4 Event Data Analytics ......................................................................................175
11.5 Analytics including Energy Audit..................................................................176
BSES

Daily, Monthly and User Selectable Time Period with configurable near real time
alerts 180
12. Smart Meters Installation ............................................................................. 181
12.1 Scope of Meter Installation / Replacement ...........................................181
12.2 Meter Inventory Management ...................................................................182
12.3 Site Survey for Communication Technology Selection ....................182
12.4 Meter Installation..........................................................................................183
13. Operation and Maintenance ........................................................................ 190
13.1 Scope and period ...........................................................................................190
13.2 AMISP's Responsibilities under Operation & Maintenance Services ....191
13.3 Maintenance Practices ..................................................................................191
13.4 Monitoring ........................................................................................................192
13.5 Meter Accuracy Tests ....................................................................................192
13.6 Physical Maintenance....................................................................................192
14. Service Level Agreement (SLA) .................................................................. 193
15. Training Requirements ................................................................................ 199
15.1 Training Categories........................................................................................199
15.2 Training modules ............................................................................................199
15.3 Training Schedules ........................................................................................200
Page 11 of 473
 15.4 General Requirements ..................................................................................200
16. Tests, Inspections and Management of the Quality Assurance / Quality
Control Program ..................................................................................................... 201
16.1 Responsibility of Tests and Inspection .......................................................201
16.2 In-Process Inspection ....................................................................................201
16.2.1 Type Testing and Data Exchange Protocol Testing ....................201
16.2.2 Quality Assurance and Quality Control Program .........................202
16.2.3 Scope and Duties of QA/QC Program Manager ............................203
[Link] Test Plans & Procedures ................................................................203
[Link].1 Test Plans............................................................................................203
[Link].2 Test Procedures ................................................................................204
[Link].3 Test Records ......................................................................................204
[Link].4 Reporting of variances ....................................................................204
[Link].5 Test Initiation......................................................................................205
[Link] Test Completion ................................................................................206
16.2.4 FAT (Factory Acceptance Test) .........................................................206
[Link] Factory Test Requirements ............................................................206
[Link] Sample Routine & Acceptance Tests for Smart Meter............207
[Link] Hardware Integration Tests ............................................................208
[Link] Functional Performance Test ........................................................208
16.2.5 Integrated System Test .......................................................................208
[Link] Unstructured Testing .......................................................................209
[Link] Dispatch of Material to Site ............................................................209
16.3 Field Installation and Integration Test (FIIT) ..............................................210
BSES

16.4 Site Acceptance Test (SAT) .........................................................................210

16.5 User Acceptance Test ...................................................................................212
16.6 System Availability Test ................................................................................215
16.6.1 Downtime .........................................................................................................216
16.6.2 Hold time..........................................................................................................216
16.6.3 Test Duration and Criteria for Acceptance .................................................216
[Link] Criteria for successful operation ..................................................................216
16.7 Operational Go Live .......................................................................................217
16.7.1 Conditions to Be Met for Operational Go Live ..............................217
16.7.2 Certification of Operational Go Live ................................................217
17. Project Management ................................................................................... 217
17.1 Project Implementation Plan would cover the following: ..........................218
17.2 Key Personnel.................................................................................................218
17.3 Progress Report .............................................................................................219
17.4 Transmittals .....................................................................................................219
17.5 Review Meeting ..............................................................................................219
17.6 Document Review and Approval Rights .....................................................219

Page 12 of 473
18. Document Requirements ............................................................................. 220
19. Project Implementation Schedule ................................................................ 221
Appendixes for Smart Meters ................................................................................. 224
Appendix 1: RF Mesh Solution Details .................................................................. 224
Appendix 2: Technical Specifications for Whole Current A.C. Single Phase
Smart Energy Meter ............................................................................................... 237
Appendix 3: Technical Specifications for Whole Current A.C. Three Phase
Smart Energy Meter ............................................................................................... 261
Appendix 4: Technical Specification for LT-CT Smart Meters ........................... 287
1.0 Scope of Supply .......................................................................................... 287
2.0 Codes & standards ...................................................................................... 287
3.0 Service Conditions....................................................................................... 288
4.0 Distribution System Data ............................................................................. 288
5.0 Electrical and Accuracy Requirement .......................................................... 288
6.0 Construction ................................................................................................ 292
7.0 Functional Requirement .............................................................................. 295
8.0 Meter Display............................................................................................... 300
9.0 Data and communication protocol/ HES/Integrations/ Software .................. 300
10.0 Name Plate .................................................................................................. 301
BSES

11.0 Component Specification ............................................................................. 302

12.0 Quality Assurance, Inspection and Testing ................................................. 303
13.0 Packing, Marking, Shipping, Handling and Storage ..................................... 305
14.0 Deviations .................................................................................................... 306
15.0 Drawing Submission .................................................................................... 306
16.0 Delivery ....................................................................................................... 307
APPENDIX 4A- GUARANTEED TECHNICAL PARTICULARS ............................. 307
APPENDIX 4B- RECOMMENDED ACCESSORIES / SPARES ............................ 307
APPENDIX 4C- DEVIATION SHEET ..................................................................... 308
APPENDIX 4D- TAMPER AND FRAUD DETECTION/ EVENTS ........................... 308
APPENDIX 4E- TECHNICAL SPECIFICATION OF LTCT BOX ............................ 312
Appendix 5: Technical Specification of DT Smart Meter ................................... 314
1.0 Scope of Supply .......................................................................................... 314
2.0 Codes & standards ...................................................................................... 314
3.0 Service Conditions....................................................................................... 315
4.0 Distribution System Data ............................................................................. 315
5.0 Electrical and Accuracy Requirement .......................................................... 315

Page 13 of 473
6.0 Construction ................................................................................................ 319
7.0 Functional Requirement .............................................................................. 322
8.0 Meter Display............................................................................................... 327
9.0 Data and communication protocol/ HES/Integrations/ Software .................. 328
10.0 Name Plate .................................................................................................. 329
11.0 Component Specification ............................................................................. 329
12.0 Quality Assurance, Inspection and Testing ................................................. 331
13.0 Packing, Marking, Shipping, Handling and Storage ..................................... 332
14.0 Deviations .................................................................................................... 334
15.0 Drawing Submission .................................................................................... 334
16.0 Delivery ....................................................................................................... 335
APPENDIX 5A- GUARANTEED TECHNICAL PARTICULARS ............................. 335
APPENDIX 5B- RECOMMENDED ACCESSORIES / SPARES ............................ 335
APPENDIX 5C- Deviation Sheet ............................................................................ 336
APPENDIX 5D- TAMPER AND FRAUD DETECTION/ EVENTS ........................... 336
Appendix 6: Technical Specifications of HT Smart Meters ................................ 341
1.0 Scope of Supply .......................................................................................... 341
2.0 Codes & standards ...................................................................................... 341
BSES

3.0 Service Conditions....................................................................................... 342

4.0 Distribution System Data ............................................................................. 342
5.0 Electrical and Accuracy Requirement .......................................................... 342
6.0 Construction ................................................................................................ 346
7.0 Functional Requirement .............................................................................. 349
8.0 Meter Display............................................................................................... 354
9.0 Data and communication protocol/ HES/Integrations/ Software .................. 355
10.0 Name Plate .................................................................................................. 356
11.0 Component Specification ............................................................................. 356
12.0 Quality Assurance, Inspection and Testing ................................................. 358
13.0 Packing, Marking, Shipping, Handling and Storage ..................................... 359
14.0 Deviations .................................................................................................... 361
15.0 Drawing Submission .................................................................................... 361
16.0 Delivery ....................................................................................................... 362
APPENDIX 6A- GUARANTEED TECHNICAL PARTICULARS ............................. 362
APPENDIX 6B- RECOMMENDED ACCESSORIES / SPARES ............................ 363
APPENDIX 6C- DEVIATION SHEET ..................................................................... 363

Page 14 of 473
APPENDIX 6D- TAMPER AND FRAUD DETECTION/ EVENTS ........................... 363
Appendix 7: Technical Specifications for Polycarbonate Security Seals ........... 368
Appendix 8: Technical Specifications for Hologram Security Seals and TF
Seals 373
Appendix 9: List of PPE & TOOLS ......................................................................... 377
Appendix 10: Bidder Store Management................................................................ 378
Appendix 11: Standards, Specifications and Compliances .................................... 379
20. Annexure ..................................................................................................... 385
Annexure A System Sizing Requirement ...................................................................385
Annexure B Details of ESB Architecture...................................................................387
Annexure C Conditions/protocols for auto-disconnections .......................................388
Annexure D AMI system availability.........................................................................389
1. 391
Annexure E Schedule of Billing Data Collection for different Consumer Category .393
Annexure F Integration Interface of Existing Enterprise Applications .....................394
Annexure G High Level Deployment (envisioned) of SMOC & WFMS ..................395
Annexure H Project Execution Plan ...........................................................................396
Annexure I Existing BSES Applications ......................................................................398
BSES

Section 7. Price Format ......................................................................................... 399

A. Price Schedule A ......................................................................................... 399
B. Price Schedule B ......................................................................................... 400
C. Format of Financial Bid ................................................................................ 404
Volume II: BIDDING AND CONTRACT FORMS .................................................... 406
Section 8: Forms- Technical and Financial Proposal ............................................ 407
Checklist of Required Forms .......................................................................................407
Form 1: List of Consortium Members/ Sub-Contractor(s).......................................409
Form 2: Bidder Information ..........................................................................................410
Form 3: Project Implementation Plan.........................................................................411
Form 4: Bidder’s Representative and Key Personnel .............................................412
Form 5: Resume and Declaration...............................................................................413
Form 6: Format of Bank Guarantee for Bid Security ...............................................415
Form 7: Format of Covering Letter by Lead Consortium Member/ Sole Bidder for
Submission of Bid....................................................................................................417
Form 8: Format of Consortium Agreement to be entered amongst all Members of a
Bidding Consortium.................................................................................................420

Page 15 of 473
 Form 9: Format of Power of Attorney by Consortium Member in favour of Lead
Consortium Member ...............................................................................................424
Form 10: Format of Power of Attorney by Lead Consortium Member / Sole Bidder
authorizing an Individual Designated Representative for the Consortium .....426
Form 11: Format of Letter of Consent by Sole Bidder/ Consortium Member
reviewing each element of the Bid .......................................................................428
Form 12: Format of Summary of Audited Financial Statements ...........................430
Form 13: Record of Similar Work Done.....................................................................432
Form 14: List of Material and Services ......................................................................433
Form 15: Table of Compliance ....................................................................................436
Form 16: Format for Technical & Financial Requirement- Relationship & Details
of Equity Shareholding ...........................................................................................437
Form 17: Authorization from Parent / Affiliate of Sole Bidder / Member of
Bidding Consortium Whose Technical / Financial Capabilities has been used by
the Sole Bidder / Member of Bidding Consortium ..............................................439
Form 18: Format of Undertaking by Technically / Financially Evaluated Entity /
Ultimate Parent Company ......................................................................................440
Form 20: Format for EMD Bank Guarantee ..............................................................445
Form 21: Acceptance Form for Participation in Reverse Auction Event –
Stands Deleted ........................................................................................................446
Form 22: Commercial Terms and Conditions ...........................................................447
BSES

Form 23: Bid Form ........................................................................................................448

Form 24: Litigation History ...........................................................................................449
Form 25: Financial Data ...............................................................................................450
Form 26: Checklist / Document to be submitted ......................................................451
Form 27: Submission before Commencement of Work ..........................................452
Form 28: Check List- Documents ...............................................................................453
Form 29: List of safety Gears and Tools and Tackles.............................................454
Form 30: Non-Disclosure Agreement ........................................................................455
Form 31: Schedule of Deviations ...............................................................................461
Form 32 – Format for Manufacturer Authorization Form (MAF) ............................462
Form 33: Format of Sending Pre-Bid Queries to BYPL ..........................................463
Section 9. Contract Related Forms ........................................................................ 464
A. Format for Direct Debit Facility..............................................................................464
B. Form of Contract.......................................................................................................467
Form 1: Format of Performance Security ..................................................................471
Form 2: Format of Letter of Award .............................................................................473

Page 16 of 473
 Volume 1:
BIDDING
BSES

PROCEDURES
AND
REQUIREMENTS

Page 17 of 473
Section 1: Request for Proposal Notice

“Appointment of Advanced Metering Infrastructure Service

Provider for Smart Prepaid Metering in BSES Yamuna Power
Limited on DBFOOT basis”
PROCUREMENT NOTICE

OPEN COMPETITIVE PROCUREMENT

Contract Title: “Appointment of Advanced Metering Infrastructure Service
Provider for Smart Prepaid Metering in BSES Yamuna Power Ltd
on DBFOOT basis’’

Request for Proposal (RFP)/ Tender Number: CMC/BY/24-25/RS/SKS/APT/37

Issued on: 17.09.2024

BSES Yamuna Power Ltd. (hereinafter also referred to as ‘BYPL’) invites Proposals for
“Appointment of Advanced Metering Infrastructure Service Provider for Smart Prepaid
Metering in BSES YamunaPower Ltd on DBFOOT basis”. Bidders are advised to note the
clauses on Eligibility and Qualification Requirements in Section 1: Request for Proposals
Notice and Evaluation Criteria in Section 2: Instructions to Bidders and Bid Data Sheet of the
RFP Document for evaluation of Proposals.
BSES

Bidding for selection of AMI Service Provider will be conducted through open competitive
procurement, as set out in this RFP.

The RFP Document is available online on [] from [17.09.2024] to [07.10.2024] on payment of cost of
document (Rs 11,800/- incl. GST) as indicated in the clause 1.2 in this section. The prospective
Bidders would be responsible for downloading the RFP Document and ensuring that any addenda/
corrigendum/ amendment/ clarification there to available on the website is also downloaded and
incorporated.

The bidding shall be conducted under Single Stage Three-Envelope Bidding processas
specified in Section 2: Instructions to Bidders and Bid Data Sheet.

Under the Single Stage Three-Envelope Bidding process, the Bidder shall not quote, disclose, or
submit its price in the First Envelope (Tender Fee & EMD)–I, Second Envelope (Techno-
commercial Bid))or in any other manner, whatsoever, except as part of the Third Envelope
(Financial Bid )). In case of any non-compliance in this regard, the Proposal shall be
outrightly/summarily rejected.

An incomplete and/or ambiguous and/or conditional Proposal and/or Proposal submitted late is
liable to be ignored/ summarily rejected, unless specifically permitted.

The Proposal must be submitted in accordance with this RFP as per Procurement/ Tendering
process specified in Section 2: Instructions to Bidders and Bid Data Sheet. Any Proposal or
modifications to Proposal received outside the Procurement/ Tendering system will not be
considered, unless otherwise specified in Section 2. BYPL shall not be held liable for any delays
due to Procurement/ Tendering system failure beyond its control. Even though the Procurement/
Tendering system will attempt to notify the Bidders of any bid updates, BYPL shall not be liable for

Page 18 of 473
any information not received by the Bidder, who shall remain vigilant in this regard. It is the
Bidders’ responsibility to obtain the latest information related to this RFP and keep itself updated.

Important dates, amounts and other details pertaining to this RFP including submission and
opening of Proposal, cost of documents/ Tender Fee, address for communication, etc., are given in
clause 1.2&1.3 of this section.

If BYPL office happens to be closed on the specified date of opening of the Proposals, the
Proposals/ bids will be opened on the next working day at the same time and venue or as may be
notified by BYPL.

Other details can be seen in the RFP document.

BSES

Page 19 of 473
1. Request for Proposal

1.1. Event Information

BSES Yamuna Power Ltd (BYPL), Delhi invites sealed tenders in 3 envelopes for the
following scope of work:
Delivery &
Description Qty.
Installation
“Appointment of Advanced Metering Infrastructure As per Price Delhi, Sites
Service Provider for Smart Prepaid Metering in BSES Format in
Yamuna Power Ltd on DBFOOT basis’’ Section 7

The Bidder must qualify the tender requirements as specified in clause 2.0 stated below
and as otherwise specified in this RFP.

Bids shall be Three (03) Part Bids:

I. PART-A shall contain Tender Fee & EMD in a sealed envelope.
II. PART-B shall contain Techno-Commercial Bid in a sealed envelope.
III. PART-C shall contain Price Bid in a sealed envelope.

All envelopes shall be duly super scribed “Appointment of Advanced Metering

Infrastructure Service Provider for Smart Prepaid Metering in BSES Yamuna Power
Ltd on DBFOOT basis”- NIT No. with Due Date of submission

All three envelopes shall be packed & sealed inside another big envelope superscribing
“NIT No., Due Date of submission and should bear the Name and Address of the Bidder
and marking for the Original and Copy.
BSES

1.2. The RFP/ tender documents & detail terms and conditions shall be downloaded from the
website i.e. [Link] by paying tender fee of ₹11,800/- (Inclusive of GST)
online. Please refer detailed guidelines available on website for the same.
1.3. Bids (Part A, Part B and Part C) will be received up to 07.10.2024, 15:30 HRS at the
address given below:

It is the sole responsibility of the bidders to ensure that the bid documents reach this office
on or before the due date and time for bid submission in sealed envelope:

HEAD OF DEPARTMENT
CONTRACTS & MATERIALS DEPARTMENT
BSES YAMUNA POWER LTD
SHAKTI KIRAN BUILDING
KARKARDOOMA, DELHI 110032

1.4. Part A (Tender Fee and EMD) of the Bid shall be opened on 07.10.2024, 12:00 HRS
1.5. Part B (Techno-Commercial Bid) of the Bid shall be opened on 07.10.2024, 12:30 HRS
1.6. Part C (Price Bid) of the Bid will be opened only of the Techno-Commercially Qualified
Bidders and the date and time of opening of same shall be intimated in due course.
1.7. BSES Yamuna Power Ltd reserves the right to accept/reject any or all Tenders without
assigning any reason thereof including in the following events:
1.7.1. Earnest Money Deposit (EMD) of value ₹ 6 Cr is not deposited in the form of Bank
Guarantee in prescribed format/Bank Fixed Deposit (Lien marked in favor of BSES
Yamuna Power Ltd. Delhi) BSES Yamuna Power Limited.
1.7.2. The Bid does not contain prices indicating break-up towards all taxes & duties in
prescribed format
1.7.3. Complete Technical Specification etc. are not enclosed.

Page 20 of 473
1.7.4. Tender is received after due date and time of submission
1.7.5. Techno-Commercial bids contain any price detail
1.7.6. Quoted Prices are not FIRM and subject to Price Variation
1.7.7. EMD not in prescribed format
1.7.8. Failure to submit Documentary evidence in support of qualifying criteria
1.7.9. Non availability of Details of Qualified Manpower & Organization Chart
1.7.10. Not providing testing facility details
1.7.11. Non submission of Copies of Orders, Execution /Performance Certificate & Other
supporting Documents to support the Qualification Criteria as per clause 2.0
(Qualification Criteria) of Section 1. Request for Proposal Notice.
1.7.12. Original Tender documents not duly stamped & signed on each page as token of
acceptance
1.7.13. Non adherence to Commercial Terms and Conditions viz Delivery period, Payment
terms, PBG etc.

Notwithstanding anything stated in this RFP, BYPL shall be well within rights to seek further
documents/ clarification from all/ any of the bidders or to extend time line defined in this
document.

BSES

Page 21 of 473
2. Qualification Criteria

2.1. The Bid can be submitted by a Sole Bidder as an individual entity or a Consortium of
firms/companies (specific requirements for Consortium are given under Clause 34
Qualification and Financial Requirements for Consortium below).

2.2. A Sole Bidder can, if it emerges as the successful bidder (“Selected Bidder”), form a
Special Purpose Vehicle under the Companies Act, 2013 (“SPV”) for the purposes of
executing the Project. The SPV so incorporated shall comply with all the obligations of the
Sole Bidder under this Tender, as also any Contract(s) that maybe executed pursuant
thereto. All obligations in this Tender in respect of an SPV formed by a Consortium, shall
also apply to the SPV formed by the Sole Bidder.

2.3. If at any stage of the bidding, any order/ ruling is found to have been passed in the last 1
(one) year preceding the Bid submission deadline by a competent Court of Law or any
appropriate Commission or any Arbitral Tribunal against the Sole Bidder/ Lead member of
Consortium/ any Consortium Members or its Affiliates for breach of any Contract awarded
by any Government agency/department/ Utility, then Bids from such Bidders shall be liable
to be rejected.

2.4. All Bidders shall confirm in accordance to Form 7: Format of Covering Letter by Lead
Consortium Member/ Sole Bidder for Submission of Bid given in Section 8 that no
such order(s)/ ruling(s) have been passed by a competent Court of Law or an appropriate
Commission against it or its Affiliates. In case of any such order/ ruling, it is the duty of the
Bidder to inform BYPL for the same during the Bid submission.

2.5. Technically qualified Bidders shall continue to maintain compliance with the Eligibility and
BSES

Qualification Requirements specified herein. Failure to comply with the aforesaid

requirements shall make the Bid from such Bidders liable for rejection at any stage of the
bidding process.

2.6. The Bidder, participating in the bid as a Sole Bidder, or any of the members of a
Consortium Member or as Lead Consortium Member of a Bidding Consortium, and its Sub-
Contractor(s) should not be blacklisted/debarred/ banned/ suspended as on date of bid
submission:.
a) due to conviction of an offence
(i) under the Prevention of Corruption Act, 1988; or,
(ii) Bhartiya Nyaya Sanhita or any other law for the time being in force, for
causing any loss of life or property or causing threat to public health as part
of execution of a public procurement contract
b) through any order/ list issued by Department of Expenditure (DoE), Ministry of
Finance (MoF)
c) due to breach of code of integrity as per Rule 175 of GFRs 2017 in any Govt.
Organization or regulatory agencies or Govt. undertaking.
d) by any Ministry/ Department/ Organization under any State Govt. in India. .

This clause shall be interpreted in-line with Rule 151 of GFRs, 2017 along with any
guidelines/ amendment issued by DoE, MoF.

3. Eligibility Requirements for Consortium

3.1 Members of the Consortium shall enter into a binding Consortium Agreement, in the form
specified at Form 8: Format of Consortium Agreement to be entered amongst all
Members of a Bidding Consortium (the “Consortium Agreement”) given in Section 8:

Page 22 of 473
 Forms- Technical and Financial Proposal of RFP document, for the purpose of
submitting Bid.

The Consortium Agreement, to be submitted along with the Bid, shall, inter alia:
(a) convey the intent to comply with the terms and conditions of the AMISP Contract in the
event selected to undertake the Project; and
(b) clearly outline the proposed roles and responsibilities, if any, of each of the Consortium
Members.

3.2 In the event Selected Bidder is a bidding Consortium, except in the case when a Central
Public Sector Enterprise (CPSE) / Public Sector Undertaking (PSU) or its Subsidiary/ Joint
Venture of a CPSE/ PSU is the lead consortium member, then the members of the
Consortium shall be required to form an appropriate Special Purpose Vehicle, incorporated
under the Companies Act 2013 (the “SPV”), to execute the AMISP Contract and implement
the Project (for the avoidance of doubt, it is clarified that a sole bidder may, at its discretion,
but subject to prior intimation to BYPL, form an appropriate special purpose vehicle
incorporated under the Companies Act, 2013 to execute the AMISP Contract and
implement the Project).

3.3 The members of the consortium may dilute their share holding in SPV after the expiry of
two years after Operational Go-Live milestone whereas members of the consortium shall
continue to hold not less than 51% for the entire balance term of the AMISP Contract;

3.4 The Lead Consortium Member shall hold at least 51% (fifty-one per cent) of the issued and
subscribed equity share capital of the SPV at all times until 2 (two) years from Operational
Go-Live Milestone as per the AMISP Contract and 26% thereafter for the remaining term of
the AMISP Contract.
BSES

3.5 If equity is held by the Affiliates, Parent Company or Ultimate Parent Company, then
subject to this Clause, such Affiliate, Parent Company or Ultimate Parent Company shall be
permitted to transfer its shareholding in the SPV to another Affiliate or to the Parent
Company / Ultimate Parent Company/to a financial partner who will hold shares in the SPV.
If any such shareholding entity, qualifying as an Affiliate / Parent Company / Ultimate
Parent Company, is likely to cease to meet the criteria to qualify as an Affiliate / Parent
Company / Ultimate Parent Company, the shares held by such entity shall be transferred to
another Affiliate / Parent Company / Ultimate Parent Company.

Provided that in case the Lead Member is holding equity in SPV through Affiliate's, Ultimate
Parent Company or Parent Company, such restriction shall apply to such entities.

Provided further, that except in case where financial partner has been inducted the
aggregate equity share holding of the Bidding Consortium in the issued and paid-up equity
share capital of the SPV shall not be less than hundred percent (100%) up to a period of
two (2) years after Operational Go-Live Milestone and the lead Consortium Member shall
have the equity share holding not less than fifty one percent (51%) for 2 years after
Operational Go-Live. In case the Selected Bidder is a Bidding Consortium, then after two
(2) years Operational Go-Live, any Member (other than the Lead Member) of such Bidding
Consortium shall be allowed to divest its equity whereas the Lead member shall
mandatorily required to hold minimum equity as specified above.

The Selected Bidder may invest in the equity share capital of the SPV through its Affiliate(s)
or Ultimate Parent Company or Parent Company. If the Selected Bidder so invests through
any Affiliate(s) or Ultimate Parent Company or Parent Company, the Selected Bidder shall
be liable to ensure that minimum equity holding limits as specified in Clause 3.2-3.5 above.

Page 23 of 473
 For computation of effective Equity holding, the Equity holding of the Selected Bidder or its
Ultimate Parent Company in such Affiliate(s) or Parent Company and the equity holding of
such Affiliate (s) or Ultimate Parent Company in the SPV shall be computed in accordance
with the example given below:

3.6 If the Parent Company or the Ultimate Parent Company of the member of Selected
Consortium directly holds thirty percent (30%) of the equity in the SPV, then holding of
member of Selected Consortium in the SPV shall be thirty percent (30%);

3.7 If Selected Bidder A holds thirty percent (30%) equity of the Affiliate and the Affiliate holds
fifty percent (50%) equity in the SPV, then for the purposes of ascertaining the minimum
equity/equity lock-in requirements specified above, the effective holding or Bidder A in the
SPV shall be fifteen percent (15%). (i.e., 30%*50%);Every Consortium Member shall
provide consent to the Lead Consortium Member and make itself aware of all the
proceedings of the bidding process and Project implementation through legally enforceable
Consortium Agreement, power of attorneys, legal undertakings, etc. (if applicable) entered
amongst; all members of that Bidding Consortium including but not limited to those as
prescribed in Form 8: Format of Consortium Agreement to be entered amongst
all Members of a Bidding Consortium, Form 9: Format of Power of Attorney by
Consortium Member in favour of Lead Consortium Member and Form 11:
Format of Letter of Consent by Sole Bidder/ Consortium Member reviewing each
element of the Bidgiven in Section 8: Forms- Technical and Financial Proposal. In the
absence of duly executed formats, the Bid shall not be considered for evaluation and shall
be rejected.

3.8 Other Requirements BSES

3.8.1 The Lead member/Sole Bidder shall have a registered office (under the Companies Act
1956/2013 with Registrar of Companies) in India at the time of submission of the Bid. In
case of Award of Contract, other Consortium Members and SPV shall also be required to
have a registered office (under the Companies Act 1956/2013 with Registrar of Companies)
in India.

3.8.2 Bidder should submit a self-undertaking signed by its authorized signatories for the same
as per the format prescribed in Form 7: Format of Covering Letter by Lead
Consortium Member/ Sole Bidder for Submission of Bid given in Section 8: Forms-
Technical and Financial Proposal."

3.8.3 The Lead Consortium Member/ Sole Bidder shall submit the Bid after submitting the Tender
Fees and Bid Security as per the various terms, schedules and formats prescribed in this
RFP. Further, The Lead Consortium Member shall be the point of contact for the
Consortium during the Bid process before award of the Project to the AMISP, and BYPL
shall communicate directly to the contact person appointed through the Power of Attorney
as per Form 10: Format of Power of Attorney by Lead Consortium Member / Sole
Bidder authorizing an Individual Designated Representative for the Consortiumgiven
in Section 8: Forms- Technical and Financial Proposal.

3.8.4 The Bidder may seek qualification on the basis of technical and financial capability of its
Parent(s) and/ or its Affiliate(s) as defined in Section 1 for the purpose of meeting the
qualification requirements. Authorization for use of such technical or financial capability
shall have to be provided from its Parent(s) and/or Affiliate(s). The technical and financial
capability of a particular entity, including its Parent(s) and/or Affiliate(s), shall not be used
by more than one Bidder.

Page 24 of 473
3.8.5 The determination of the relationship of Parent(s) and/or Affiliate(s) with the Bidder shall be
on the date 7 (seven) Days prior to the Bid Submission Deadline. Documentary evidence to
establish such relationship shall be furnished by the Bidder along with the Technical Bid.

3.8.6 If the Technically Evaluated Entity and/or Financially Evaluated Entity i.e., the Affiliate of the
Bidder on whose capabilities the Bidder is relying, is an entity other than the Sole Bidder or
a Member in a Bidding Consortium, the Sole Bidder or Member relying on such Technically
Evaluated Entity and/or Financially Evaluated Entity will have to submit a legally binding
undertaking supported by a board resolution from the Technically Evaluated Entity and/or
Financially Evaluated Entity or its Ultimate Parent Company, that all the equity investment
obligations of the Sole Bidder or the Member of the Consortium shall be deemed to be
equity investment obligations of the Technically Evaluated Entity and/or Financially
Evaluated Entity or its Ultimate Parent Company, and in the event of any default the same
shall be met by such evaluated entity or by or the Ultimate Parent Company. The Sole
Bidder or the Consortium Member shall have to provide information and documents relating
to its relationship with such Technically Evaluated Entity and or Financially Evaluated Entity
including details about the equity shareholding between them as per Form 16: Format
for Technical & Financial Requirement- Relationship & Details of Equity
Shareholding provided in Section 8: Forms- Technical and Financial Proposal.

3.8.7 The Technically Evaluated Entity may be the Sole Bidder or the Lead Member of a
Consortium or an Affiliate or Parent of such Sole Bidder or the Lead Member, as the case
may be.

3.8.8 The Qualified Bidder(s) will be required to continue to maintain compliance with the
Qualification Requirements throughout the bidding process and till execution of the AMISP
Contract. Where the Technically Evaluated Entity and/or the Financially Evaluated Entity is
BSES

not the Sole Bidder or a Member in a Bidding Consortium, as the case may be, the Sole
Bidder or Member shall continue to be an Affiliate of the Technically Evaluated Entity and/or
Financially Evaluated Entity till the execution of the AMISP Contract. Failure to comply with
the aforesaid provisions shall make the Bid liable for rejection at any stage.

4. Qualification and Financial Requirements

4.1 Bidder Qualification Requirements:

Sr. No. Requirements Supporting Documents

Technical Requirement
1 Sole/Lead Bidder must have either: a) References along with requisite
contract/ Purchase Order (PO)/
Paid for, or received payments for, Work Order (WO). The
construction of Eligible Project(s); references should indicate client
Or name, scope of work, Project
Paid for development of Eligible start date;
Project(s)
In case non-disclosure
in the infrastructure sector in the last 7 agreement (NDA) is signed with
(seven) Financial Years with aggregate the client, Bidder shall provide
project value of not less than: INR 600 an undertaking for the NDA and
Crores. shall also provide a client
2 Sole/Lead Bidder/any other Consortium certification as proof of
Member must have experience of experience along with Client
integration of head-end system with Name/ Email Address/ Contact

Page 25 of 473
Sr. No. Requirements Supporting Documents
MDM on standard interfaces and data no. / designation etc.
exchange models for at least 20,000
consumers / end points (cumulatively) in b) Documentary evidence of
an Indian/ Global Utility (power/ water/ completion of the Project or
natural gas/ telecom) in the last 7 (seven) completion of Go-live status
years which are in operation for at least 1 (i.e., Go-live certificate, UAT
(one) year. testing certificate etc.) of the
respective project as per the
Or definition of Go-Live/ UAT
specified therein or other
Sole/Lead Bidder/ any other Consortium documentary evidence
Member should have installed, indicating completion (e.g.,
integrated, tested, and commissioned proof of payment received/
control center hardware (or on cloud) and proof of asset capitalized in
application software/ implementation of books of accounts (as
prepaid metering for at least 50,000 applicable) and client certificate
endpoints (cumulatively) in an Indian/ for supply of material or similar
Global Utility (power/ water/ natural gas/ proofs) along with contact
telecom)in last 7 (seven) years which are details of the client;
in operation for at least 1 (one) year c) Any other documentation for
implementation performance/
operation
Financial requirements
3 The Bidder shall have positive net worth Audited Annual financial
for each of the last three financial years. statements, Balance Sheet and
The Net worth of the Bidder should be at P&L Account for the respective
least Financial Years as per the format
BSES

prescribed in Form 12: Format of

INR 400 Crores in any of the last three Summary of Audited Financial
Financial Years Statements given in Section 8:
Forms- Technical and Financial
Or Proposal.

Bidder shall have a minimum ACI of

INR 400 Crores at the close of the

preceding financial year

[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].

[ACI means minimum investible funds

(i.e., immediately available funds for
investment and callable capital) subject
to the limits of investment in a single
investee entity (in the relevant jurisdiction
for a Foreign Investment Fund, or the
maximum permissible investment limit for

Page 26 of 473
 Sr. No. Requirements Supporting Documents
an AIF) (as per the SEBI (AIF)
Regulations, 2012, as may be amended
from time to time), as applicable].

Please note:
a. In case a Bidder and/(or) it’s
Parent(s)/ Affiliate(s) has issued any
fresh equity capital during the current
financial year, the same shall be
permitted to be added to the Bidder’s
Net Worth subject to the statutory
auditor of the Bidder certifying to this
effect.
b. In case a Bidder and/(or) it’s
parent(s)/ Affiliate(s), being a SEBI
registered AIF or Foreign Investment
Fund, has received any fresh capital
commitment available for the
immediate deployment during the
current financial year, the same shall
be permitted to be added to the
Bidder’s ACI subject to the statutory
auditor of the Bidder certifying to this
effect.

4.2 The Sole bidder/ Lead member of the Consortium would have to clearly include and
mention the details of the solution / component providers given below. However, such
BSES

solution/component provider may or may not necessarily be included as a part of the

Bidding Consortium. For avoidance of doubt, it is clarified that the sole bidder/ any member
of the bidding consortium can also be a solution/ component provider, provided that they
meet the relevant qualification requirements as mentioned below. The Sole bidder/ Lead
member of the Consortium has to mandatorily mention at least one vendor for each of the
solution/ component providers given below in Form 1: List of Consortium Members/ Sub-
Contractor(s) of Section 8: Forms- Technical and Financial Proposal:

a) Smart Meter Manufacturer(s)

b) Head End System(HES) solution provider
c) Meter Data Management System (MDMS) solution provider
d) System Integrator
e) RF Communication Provider (if applicable)

Accordingly, in addition to the requirements provided in clause 4.1, the solution / component
providers should also separately meet the following requirements as on date of bid
submission or as on date of replacement of solution/ component provider post award of
contract, subject to necessary approval in writing from the BYPL. The component providers
shall sign an agreement with the Sole bidder/ Lead member, provided the solution/component
provider is not the Sole bidder/ Lead member, in the format as specified in MAF as per Form
32 – Format for Manufacturer Authorization Form (MAF), clearly mentioning:

a) their intent to comply with the terms and conditions of the Contract Agreement in the event
the solution/ component provider is selected to undertake the Project, and to be party to
the Contract Agreement (thereby rendering it a tripartite arrangement);

Page 27 of 473
b) their willingness to work with the said Sole bidder/ Lead member of the Consortium;
c) and their proposed roles and responsibilities;
S. No. Requirements Supporting Documents
A. Meter Manufacturer –Technical Requirements
A1. Option 1: a) References along with requisite
Should have manufactured and contract/ Purchase Order (PO)/ Work
supplied minimum 1,00,000 nos. of Order (WO). The references should
Smart meters (cumulative) in indicate client name, scope of work,
Indian/Global Power Distribution Project start date (as per the format
Utility in the last 7 (seven) years. prescribed in Form 13: Record of
Similar Work Done given in Section
Option 2: 8);
Should have manufactured and
supplied minimum 20,00,000 nos. of In case Non-Disclosure agreement
static electricity meters (NDA) is signed with the client, Bidder
(cumulative) in Indian/Global Power shall provide an undertaking for the
Distribution Utility in the last 7 (seven) NDA and shall also provide a client
years. certification as proof of experience
along with Client Name/ Email
Option 3: Address/ Contact no./ designation etc.
Any meter manufacturer who doesn’t
satisfy Option 1 & 2 but satisfies all b) Documentary evidence of completion of
the conditions A2, A3, A4 & A5 below, the Project or other documentary
can also be eligible to participate in evidence indicating completion of
the bid as a meter manufacturer. supply (e.g. proof of payment received/
proof of asset capitalized in books of
BSES
accounts (as applicable) and client
certificate for supply of material or
similar proofs) along with contact details
of the client;
c) Any other documentation for
implementation performance/ operation
A2 Smart Meters shall have all the valid Valid BIS and type-test certificate to be
test certificates (issued within the last submitted.
5 years) and BIS certificate compliant
to IS 16444 Part-1*

Note: *At the time of supply of only Documentary evidence for submission of
LT-CT operated Meters, the smart application for LT-CT operated meters to
meters shall have all the valid test be submitted.
certificate and BIS Certificate,
compliant to IS 16444 Part-2.
A3 OEM of the equipment offered, having Bidder shall furnish the Self Declaration for
service, technical support and lab in “Service technical support and lab facility in
India for Smart Meters. India”.
A4 The Meter Manufacturer must Copies of valid ISO 9001, ISO14001, ISO-
possess valid ISO 9001, ISO 14001, 27001, certificates.
ISO 27001 certificates.
A5 The Meter Manufacturer should have Valid certificate copy
in-house NABL accredited Laboratory
for acceptance test for the relevant IS.
B. Head End System (HES) Solution Provider–Technical Requirements
B.1 The proposed HES solution should Certificate / report issued by Client / MDMS

Page 28 of 473
S. No. Requirements Supporting Documents
have been successfully integrated OEM / solution provider.
with at least 2 (two) different MDMS/
other Utility IT Solution in Indian/ In case the HES solution provider, has
Global Utility(ies) (power/ water/ integrated with their own MDMS, or is
natural gas/ telecom) in last 7 (seven) covered under NDA, then a self-
years certification shall be provided.
C. Meter Data Management System (MDMS) Solution Provider–Technical
Requirements
C.1 The proposed MDM solution should a) References along with requisite
have been successfully in operation contract/ Purchase Order (PO)/ Work
for at least 1 million smart meters Order (WO). The references should
(gas/water/electricity) and integrated indicate client name, scope of work,
with at least 2 (two) nos. of different Project start date (as per the format
HES solutions in Indian/ Global prescribed
Utility(ies) (power/ water/ natural gas/
telecom) in last 7 (seven) years. In case non-disclosure agreement
C.2 The proposed MDM solution should (NDA) is signed with the client, Bidder
have been successfully integrated shall provide an undertaking for the
with at least 2 (two) nos. of different NDA and shall also provide a client
Billing Systems in Indian/ Global certification as proof of experience
Utility(ies) (power/ water/ natural gas/ along with Client Name/ Email Address/
telecom) or with Billing/ Other IT Contact no./ designation etc.
systems of 2 (two) different Indian/
Global Utility(ies) in last 7 (seven) b) Documentary evidence of completion of
years the Project or completion of Go-live
BSES
status (i.e., Go-live certificate, UAT
testing certificate etc.) of the respective
project as per the definition of Go-Live/
UAT specified therein or other
documentary evidence indicating
completion (e.g., proof of payment
received/ proof of asset capitalized in
books of accounts (as applicable) and
client certificate for supply of material or
similar proofs) along with contact details
of the client
c) Certificate / report issued by Client /
HES OEM/ solution provider. In case
the MDMS solution provider, has
integrated with their own HES, then a
self- certification shall be provided.
d) Any other documentation for
implementation performance/ operation.
D. System Integrator–Technical Requirements
D.1 Should have experience of integration Certificate / report issued by Client / Billing
of HES/MDMS etc. with at least 2 system solution provider.
(two) billing/ other Utility IT systems in
Indian/ Global Utility(ies) (power/
water/ natural gas/ telecom) in last 7
(seven) years, in which the meters
are in operation for at least 1 (one)
year.
D.2 Should have IEC/ ISO 27001 Copy of valid certificate

Page 29 of 473
S. No. Requirements Supporting Documents
certification or CMMi Level 3 (or
above)
E. RF Technology/Solution Provider–Technical Requirements (If applicable)
E.1 The proposed RF technology/ a) References along with requisite
Solution provider should have contract/ Purchase Order (PO)/ Work
implemented project/(s) with at least Order (WO). The references should
50,000 (cumulatively) modules / indicate client name, scope of work,
endpoints involving Radio Frequency Project start date (as per the format
(RF) mesh in an Indian/ Global Utility prescribed in Form 13: Record of
(power/ water/ natural gas/ telecom) Similar Work Done given in Section
in the last 7 (seven) years. 8);
In case non-disclosure agreement
(NDA) is signed with the client, Bidder
shall provide an undertaking for the
NDA and shall also provide a client
certification as proof of experience
along with Client Name/ Email
Address/ Contact no./ designation etc.

b) Documentary evidence of completion of

the Project or completion of Go-live
status(i.e., Go-live certificate, UAT
testing certificate etc.) of the respective
project as per the definition of Go-Live/
UAT specified therein or other
BSES
documentary evidence indicating
completion (e.g., proof of payment
received/ proof of asset capitalized in
books of accounts (as applicable) and
client certificate for supply of material or
similar proofs) along with contact details
of the client;
c) Any other documentation for
implementation performance/ operation.
E.2 The RF Technology/Solution provider a) Certificate of Incorporation and
should have been in the Registration certificate along with
communications network installation/ Memorandum & Articles of Association.
maintenance services business for b) Copy of valid Licenses (In case of RF,
the last 1 (one) year in India. Valid certificate issued by Wireless
Planning & Coordination (WPC)
OR Wing of the Ministry of Communications,
GOI) as on date of bid
The RF Technology/ Solution provider submission
should have been in the
communications network installation/
maintenance services business for
the last 3 (three) years outside of
India.
E.3 The RF Technology/ Solution provider Signed agreements/ MoUs for integration
have successfully integrated their of NIC module or Certificate of successful
NIC/ Communication module with at integration.
least 3 (three) different makes of
smart meters in India or Outside of

Page 30 of 473
 S. No. Requirements Supporting Documents
India.

4.3 For the purpose of satisfaction of Technical Requirement, the following shall apply:
a) Eligible Projects, as referred in Technical Requirement, shall mean works contracts for
developing asset/ facility in India or abroad which involve building/ installing, and
commissioning/ go-live such asset/facility but shall not include any assignment where
the scope is limited to only (i) supply of goods or (ii) supply of manpower.
b) Projects that have achieved completion/or have achieved commissioning/ go-live as
identified in the Project document(s) at least 7 (seven) Days prior to the Bid
Submission Deadline shall be considered.
c) The Technically Evaluated Entity must have either executed itself/paid for such
projects or must own at least 26% of the shareholding in the company that has
executed the project(s) up to the date of commissioning of such project.
d) For the purpose of clause 4.1 above, Infrastructure sector is defined under Definitions
in Section 3: General Terms and Conditions. In reference to this, Energy efficiency
projects in Electricity Distribution sector shall also be considered.
e) For the purpose of clause 4.1 & 4.2 (A) to (E) above, the Eligible Project(s) in the:
i. Power Sector shall mean projects relating to generation or transmission or
distribution of electricity;
ii. Water Sector shall mean projects relating to water treatment including
desalinationorwatersupply(ruralorurban)orwastewater/sewerageordrainage or
water pipelines;
iii. Natural Gas Sector shall mean projects relating to natural gas transmission or
distribution; and
iv. Telecom Sector shall mean projects relating to infrastructure cabling or
communication systems for setting up Wide Area Network (WAN) or Local Area
BSES

Network (LAN) or Internet Services or VOIP solutions, etc.

v. Transport and Logistics Sector shall mean projects relating to Roads and
Bridges, Ports, Shipyards, Inland Waterways, Airport.

4.4 For the purposes of satisfaction of Financial Requirement, the following shall apply:
a) In the event Bidder is a Consortium, the financial requirement shall be met individually
or collectively by all the Members in the Bidding Consortium. In the event, the financial
requirement is to be met entirely by any Member other than the lead member of the
Bidding Consortium:
i. such member shall hold not less than 51% of the issued and subscribed equity
share capital of the SPV at all times until 2 (two) years from Operational Go-Live
as per the AMISP Contract; and
b) Power Utilities/ Distribution Licensees can use financial and technical qualifications of
their Affiliates in India / Abroad.
c) The Bidders using Parental Credentials need to submit ‘Undertaking from CEO/
Designated official with POA of the company/bidder, duly declaring/confirming surety
for the credentials documents of the parent company/affiliate. .
d) For credentials which are under non sharing NDAs, Bidder (s) may provide self-
certification signed by authorized signatory. BYPL reserves the right to contact client to
ascertain authenticity. The credentials of OEM Products where the projects are already
handed over to Customers shall also be suitably considered.
e) Notwithstanding anything stated above, BYPL reserves the right to assess bidder’s
capability to perform the contract, assess the capability and installed capacity of the
Bidder for carrying out the supplies, should the circumstances warrant such
assessment in the overall interest of BYPL. In this regard the decision of BYPL is final.
f) Note: Any bidder and Consortium members from countries sharing a land border with
India will be eligible to bid in any procurement whether of goods, services (including

Page 31 of 473
 consultancy services and non-consultancy services) or works (including turnkey
projects) only if the bidder is registered with the Competent Authority. The Competent
Authority for registration will be the Registration Committee constituted by the
Department for Promotion of Industry and Internal Trade (DPIIT). Political and security
clearance from the Ministries of External and Home Affairs respectively will be
mandatory.

5. Bidding and Award Process

5.1. Bidders are requested to submit their questions regarding the RFP or the bidding process
after review of this RFP. BYPL response to questions/queries raised by various bidders will
be distributed to all participating bidders through an RFP update/corrigendum or raised their
queries, if any, during pre-bid meeting and the same shall be responded by BYPL
appropriately.

5.2. Bidders are requested to submit their offer strictly in line with this tender document. In case
of any major deviation, deletion or addition which bidder may feel is relevant to this project &
for its safe operation and completion of works; Bidder may clearly highlight and communicate
the same to BYPL with his bid and same shall furnish in deviation format provided as Form
31: Schedule of Deviations in Section 8: Forms- Technical and Financial Proposal.

5.3. The Bid shall be submitted in the following three parts:

PART-B
PART-A PART-C
Sr. Techno-Commercial Bid
Tender Fee and Price Bid Contains below
No Contains Below Documents/
EMD details
Details
BSES

1. EMD in prescribed Price strictly in the Format

format enclosed indicating Break up
2. Non-refundable of basic price, taxes & duties,
tender fees i.e. transportation etc.
Eleven Thousand
Eight Hundred
(Rs. 11,800/-) inc.
GST
3. Power of Attorney Documentary evidence in
support of qualifying criteria
4. Details of Qualified Manpower
available & Organization Chart
5. Affidavit, declaration and
copies of approvals, to support
the QC as per clause
Qualification Criteria
6. Original Tender documents
duly stamped & signed on
each page as token of
acceptance
7. Acceptance to Commercial
Terms and Conditions viz
Delivery period, Payment
terms, PBG etc.
8. 01 Original + 1 Duplicate
01 Original Copy of Price Bid
Copies of above documents
9. The bidder shall quote the

Page 32 of 473
 PART-B
PART-A PART-C
Sr. Techno-Commercial Bid
Tender Fee and Price Bid Contains below
No Contains Below Documents/
EMD details
Details
prices strictly in the price
format/item description /
content. The bid shall be
liable for rejection, if bidder
failed to do so. If at any
stage, the content is found to
be changed from the given
price format, the content as
per the given price format will
prevail and bidding on the
bidder.

Bids shall be Three (03) Part Bid:

I. PART-A shall contain Tender Fee & EMD in a sealed envelope.
II. PART-B shall contain Techno-Commercial Bid in a sealed envelope.
III. PART-C shall contain Price bid in a sealed envelope.

5.4. All envelopes shall be duly super scribed “Appointment of Advanced Metering
Infrastructure Service Provider for Smart Prepaid Metering in BSES Yamuna Power Ltd
on DBFOOT basis”- NIT No. with Due Date of submission.

5.5. All these envelopes shall be packed & sealed inside another big envelope superscribing NIT
No. with Due Date of submission and should bear the Name and Address of the Bidder and
marking for the Original and Copy.
BSES

5.6. Time Schedule

The bidders should complete the following within the dates specified as under:
S. No. Steps Date
1 Start date of sale of bid documents 17.09.2024
2 Last date of Queries, if any 19.09.2024
3 Pre-Bid meeting 23.09.2024
4 Issue of clarifications, amendment or revised RFP, if
27.09.2024
any
5 Last date of sale of bid documents 07.10.2024
6 Due date & Time for Bid Submission 07.10.2024 11:30
HRS
7 Date & time of opening of tender – Part A & B 07.10.2024 12:00
HRS
8 Date & Time of opening of tender – Part C To be communicated
separately to bidder(s)

The Bidder shall submit their pre-bid queries in XLS format on the email id as
mentioned in the tender document as per Form 33, Format of Sending Pre-Bid
Queries to BYPL.

5.7. REVERSE AUCTION: The Reverse auction won’t be part of this tender.

5.8. BIDS RECEIVED AFTER DUE DATE AND TIME WILL SUMMARILY BE REJECTED

Page 33 of 473
6. Award Decision

6.1. Purchaser intends to award the Project on a lowest bid basis to one or more bidders on
competitiveness, so bidders are encouraged to submit the bids that are competitive. The
decision to place Purchase Order/LOI solely depends on BYPLon the cost competitiveness
across multiple lots, quality, delivery and Bidder‘s capacity, in addition to other factors that
Purchaser may deem relevant.

6.2. In the event of bid being selected by BYPL, and subsequent DEFAULT on bid; Bidder will be
required to pay BYPL an amount equal to the difference between his bid and the next lowest
bid on the quantity declared in NIT/RFP.

6.3. In case performance of any supplier/service provider is found unsatisfactory during the
delivery process, the award will be cancelled and BYPL reserves the right to award to other
suppliers at their (bidder) risk & cost.

6.4. The letter of award (LOA) shall be placed only after due approval of Project from Hon’ble
Delhi Electricity Regulatory Commission (DERC).

7. Contact Information

Technical clarification, if any, as regards this RFP shall be sought in writing and sent by
post/courier/mail to following address.

Particulars Technical Commercial

Mr. Ashish Joshi BSES

Mr. Robin Sebastian -BYPL

Contact Person Mr. Puneet Duggal Mr Santosh Singh -BYPL
Mr. Gaurav Sharma
BSES Yamuna Power Ltd, Shakti BSES Yamuna Power Ltd, Shakti
Address Kiran Building, Karkardooma, Delhi Kiran Building, Karkardooma,
110032 Delhi 110032
[Link]@[Link] [Link]@[Link]
[Link]@[Link] m
Email
[Link]@[Link] [Link]@relianceada.
com
Landline No. 011-41247125

Page 34 of 473
Section 2: Instructions to Bidders and Bid Data Sheet

Instructions to Bidders
1. General
BYPL is desirous of implementing various system improvement/repair &maintenance works
at their respective licensed area in Delhi. BYPL has now floated this tender for Appointment
of Advanced Metering Infrastructure Service Provider for Smart Prepaid Metering in
BSES Yamuna Power Limited on DBFOOT basis as notified earlier in this bid documents.

2. Scope of Work
AMISP shall Design, Build, Finance, Integrate, Own, Operate and Transfer the Advance
Metering Infrastructure (AMI) Project in BYPL, Delhi AMI Project Area. The AMISP shall
implement the project including Smart Meter & AMI Solution supply, installation,
implementation, provisioning of cloud hosting and 4G / NBIoT data services, testing,
Commissioning and O&M of entire solution to operate as defined in this Contract and
thereafter transfer the operation of the entire system including all the hardware, software
along with its valid licenses, and any data collected during the Project to the BYPL at the end
of the Contract Period to facilitate seamless operation of BYPL businesses. BYPLshall make
payments to the AMISP in accordance with the terms and conditions of this Contract.

3. Disclaimer

3.1 This Document includes specification/ details to be referred here, which reflect various
assumptions, which may or may not be correct. Each Bidder should conduct its own
estimation and analysis and should check the accuracy, reliability and completeness of the
BSES

information in this Document and obtain independent advice from appropriate sources in
their own interest.

3.2 Neither Purchaser nor its employees will have any liability whatsoever to any Bidder or any
other person under the law or contract, the principles of restitution or unjust enrichment or
otherwise for any loss, expense or damage whatsoever which may arise from or be incurred
or suffered in connection with anything contained in this Document, any matter deemed to
form part of this Document, provision of Services and any other information supplied by or on
behalf of Purchaser or its employees, or otherwise a rising in any way from the selection
process for the Supply.

3.3 Though adequate care has been taken while issuing the Bid document, the Bidder should
satisfy itself that Documents are complete in all respects. Intimation of any discrepancy shall
be given to this office immediately.

3.4 This Document and the information contained herein are Strictly Confidential and are for the
use of only the person(s) to whom it is issued. It may not be copied or distributed by the
recipient to third parties (other than in confidence to the recipient‘s professional advisors).

4. Cost of Bidding
The Bidder shall bear all cost associated with the preparation and submission of its Bid and
Purchaser will in no case be responsible or liable for those costs.

Page 35 of 473
5. Bidding Documents
The Scope of Work, Bidding Procedures and Contract Terms are described in the Bidding
Documents. In addition to the covering letter accompanying Bidding Documents, the Bidding
Documents include:

S. No. Particular Section

1. Request for Proposal Notice Section 1
2. Instructions to Bidders and Bid Data Sheet Section 2
3. General Terms and Conditions Section 3
4. Vendor Code of Conduct Section 4
5. Special Conditions of Contract Section 5
6. Project Requirements Section 6
7. Price Format Section 7
8. Forms- Technical and Financial Proposal Section 8
9. Contract related Forms Section 9

S. No. Particular Form

1. List of Consortium Members/ Sub-Contractor(s) (as applicable) Form 1
2. Bidder Information Form 2
3. Project Implementation Plan Form 3
4. Bidder’s Representative and Key Personnel Form 4
5. Resume and Declaration Form 5
6. Bid Security in the form of Bank Guarantee or Demand Draft Form 6
7. Covering Letter by Lead Consortium Member/ Sole Bidder for Form 7
Submission of Bid
8. Consortium Agreement to be entered amongst all Members of a Form 8
Bidding Consortium BSES

9. Power of Attorney by Consortium Member in favour of Lead Form 9

Consortium Member
10. Power of Attorney by Lead Consortium Member / Sole Bidder Form 10
authorizing an Individual Designated Representative for the
Consortium
11. Letter of Consent by Sole Bidder/ Consortium Member reviewing Form 11
each element of the Bid
12. Summary of Audited Financial Statements Form 12
13. Record of Similar Work Done Form 13
14. List of Material and Services Form 14
15. Table of Compliance Form 15
16. Technical & Financial Requirement- Relationship & Details of Form 16
Equity Shareholding
17. Authorization from Parent / Affiliate of Sole Bidder / Member of Form 17
Bidding Consortium Whose Technical / Financial Capabilities has
been used by the Sole Bidder / Member of Bidding Consortium
18. Undertaking by Technically / Financially Evaluated Entity / Form 18
Ultimate Parent Company
19. Board Resolutions – Stands Deleted Form 19
20. EMD Bank Guarantee Form 20
21. Acceptance Form for Participation in Reverse Auction Event – Form 21
Stands Deleted
22. Commercial Terms and Conditions Form 22
23. Bid Form Form 23
24. Litigation History Form 24
25. Financial Data Form 25

Page 36 of 473
 S. No. Particular Form
26. Checklist / Document to be submitted Form 26
27. Submission before Commencement of Work Form 27
28. Check List- Documents Form 28
29. List of safety Gears and Tools and Tackles Form 29
30. Non-Disclosure Agreement Form 30
31. Schedule of Deviations Form 31
32. Manufacturer Authorization Form (MAF) Form 32
33. Sending Pre-Bid Queries to BYPL Form 33

The Bidder is expected to examine the Bidding Documents, including all Instructions, Forms,
Terms and Specifications. Failure to furnish all information required by the Bidding
documents or submission of a Bid not substantially responsive to the Bidding Documents in
every respect will may result in the rejection of the Bid.

6. Amendment of Bidding Documents

At any time prior to the deadline for submission of Bids, the Purchaser may for any reasons,
whether at its own initiative or in response to a clarification requested by a prospective
Bidder, modify/alter/amend the Bidding Documents by way of an Amendment.

The Amendment shall be part of the Bidding Documents, pursuant to Clause 5 Section-1,
and it will be notified in writing through e-mail to all the Bidders who has purchased the
Tender Documents and confirmed their participation to Bid, and will be binding on them.

In order to afford prospective Bidders reasonable time to take the Amendment into account in
preparing their Bids, BYPL may, at its discretion, extend the deadline for the submission of
Bids. BSES

7. Preparation / Language of Bids

The Bid prepared by the Bidder, and all correspondence and documents relating to the Bid
exchanged by the Bidder and the Purchaser, shall be written in the English Language. Any
printed literature furnished by the Bidder may be written in another Language, provided that
this literature is accompanied by an English translation, in which case, for purposes of
interpretation of the Bid, the English translation shall govern.

8. Documents Comprising the Bid

The Bid prepared and submitted by the Bidder shall comprise the following components:
a. Bid Form, Price & other Schedules (strictly as per format) and Technical Data Sheets
completed in accordance with Clause 11.0, 12.0, 13.0, 14.0, 15.0, 16.0 of Section 2:
Instructions to Bidders and Bid Data Sheet and Technical Specification as
mentioned in Section 6: Project Requirements;
b. All the Bids must be accompanied with the required EMD as mentioned in the Clause
10.0 of Section 2: Instructions to Bidders and Bid Data Sheet against each tender.
c. Power of Attorney indicating that the person(s) signing the Bid have the authority to sign
the Bid and thus that the Bid is binding upon the Bidder during the full period of its validity,
in accordance with Clause 13 and 15of Section 2: Instructions to Bidders and Bid
Data Sheet.

9. Bid Form
The Bidder shall complete one “Original” and another one “Copy“ of the Bid Form (Form 23:
Bid Form) and the appropriate Price & Other Schedules and Technical Data Sheets.

Page 37 of 473
10. Earnest Money Deposit (EMD)
The bidder shall furnish, as part of its bid, an EMD amounting to ₹6 Crores (Rupees Six
Crores only) as specified in the RFP.

The EMD is required to protect the Purchaser against the risk of Bidder‘s conduct which
would warrant forfeiture.

The EMD shall be denominated in any of the following form:

i. Bank Fixed deposit (lien marked in favor of BSES YAMUNA POWER LTD.) or Bank
Guarantee valid for One Hundred Eighty (180) days from due date of submission or
amended due date of submission whichever is later, drawn in favor of BSES Yamuna
Power Ltd, Shakti Kiran Building, Karkardooma, Delhi 110032 by any Indian bank /
foreign bank having service branch in India.

The EMD may be forfeited in case of:

i. The Bidder withdraws its bid during the period of specified bid validity
OR
ii. a successful Bidder, if the Bidder does not

1. Accept the Purchase Order,

OR
2. Furnish the required Contact Performance Bank Guarantee

11. Bid Prices

a. Bidders shall quote for the entire Scope of Supply/Work with a break-up of prices for
individual items and Taxes & Duties as per price format (Section 7: Price Format)
b. The total Bid Price shall also include all the Supplier's obligations as mentioned in or
BSES

reasonably to be inferred from the Bidding Documents, in respect of Design, Supply,

Testing, Installation, Commissioning and Transportation to site, all in accordance with
the requirement of Bidding Documents for successful execution of the contract.
c. The Bidder shall complete the appropriate Price Schedules included herein, stating the
Unit Price for each item & total Price with taxes, duties & freight up to destination as
specified by purchaser.
d. Prices quoted by the Bidder shall be “Firm” and not subject to any price adjustment
during the performance of the Contract. A Bid submitted with an adjustable price/ Price
Variation Clause will be treated as non -responsive and rejected.
e. The quantity break-up shown else-where in Price Schedule is tentative. The bidder shall
ascertain himself regarding material required for completeness of the entire work. Any
item not indicated but is required to complete the job, shall be deemed to be included in
the prices quoted.

12. Bid Currency

Prices shall be quoted in INR Only (₹).

13. Period of Bid Validity

a. Bids shall remain valid for 180 days from the due date of submission of the Bid or
subsequent corrigendum/amendment/extension of due date of submission whichever is
later.
b. Notwithstanding to above clause, the Purchaser may solicit the Bidder‘s written consent
to an extension of the Period of Bid Validity.

14. Alternative Bid

Bidders shall submit Bids, which comply with the Bidding Documents. Alternative Bids will
not be considered. The attention of Bidders is drawn to the provisions regarding the rejection

Page 38 of 473
 of Bids in the terms and conditions, which are not substantially responsive to the
requirements of the Bidding Documents as mentioned in Clause 1.7 of Section-1: Request
for Proposal.

15. Format and Signing of Bid

15.1 The original Bid Form and accompanying documents, clearly marked "Original" and “Copy”
must be received by the Purchaser at the date, time and place specified pursuant to Clauses
16and 17of Section 2: Instructions to Bidders and Bid Data Sheet In the event of any
discrepancy between the original and the copy, the original shall govern.
15.2 The original and copy of the Bid shall be typed or written in indelible ink and shall be signed
by the Bidder or a person or persons duly authorized to sign on behalf of the Bidder. Such
authorization shall be indicated by written Power-of-Attorney accompanying the Bid.
15.3 The Bid shall contain no interlineations, erasures or overwriting except as necessary to
correct errors made by the Bidder, in which case such corrections shall be initialed by the
person or persons signing the Bid.

16. Submission of Bids

Sealing and Marking of Bid

Bid submission: One original and one copy (hard copies) of all the Bid Documents shall be
sealed and submitted to the Purchaser before the closing date & time for submission of the
bid.

Bids shall be Three (03) Part Bid:

 PART-A shall contain Tender Fee & EMD in a sealed envelope.
 PART-B shall contain Techno-Commercial Bid in a sealed envelope.
 PART-C shall contain Price Bid in a sealed envelope.
BSES

All envelopes shall be duly super scribed “Appointment of Advanced Metering

Infrastructure Service Provider for Smart Prepaid Metering in BSES Yamuna Power
Limited on DBFOOT basis”- NIT No. CMC/BY/24-25/RS/SKS/APT/37 with Due Date of
submission as 07.10.2024.

All these envelopes shall be packed & sealed inside another big envelope superscribing NIT
No. CMC/BY/24-25/RS/SKS/APT/37 with Due Date of submission as 07.10.2024 and should
bear the Name and Address of the Bidder and marking for the Original and Copy.

The Bidder shall submit the hard copy of tender documents in person at:

Tender Room – 3rd Floor, BSES Yamuna Power Ltd., Shakti Kiran Building, Delhi,
110032.

Bids submitted by Email/Telex/Telegram/Fax/Courier/Airlines/Cargo Agents will not be

acceptable.

The Successful Bidder will be asked to submit commencement samples of each type of
meter (One Smart Meter sample with box) along with detailed QAP, GTP & Drawings and
temper logics). The sample should clearly indicate (i) Name of the bidder (ii) Tender No., (iii)
Group & Item Sr. No. etc. The samples shall not be returned back to the bidder.

Page 39 of 473
 The Bidder shall also provide soft copy (Pen drive) of bid (Only Technical Proposal) in
password protected PDF format which shall be communicated to BYPL contact mentioned in
Clause 7 of Section 1: Request for Proposal.

No price bid shall be submitted in Pen drive. The Pen drive should be owned by bidder. The
bidder shall ensure that the pen drive is free from all viruses/malware. The Pen drive once
submitted shall not be returned.

17. Deadline for Submission of Bid

17.1 The original Bid, together with the required copies, must be received by the Purchaser at
the address specified earlier, on or before due submission date & time as mentioned in
Clause 1.3 of Section 1: Request for Proposal.
17.2 The Purchaser may, at its discretion, extend the deadline for the submission of Bids by
amending the Bidding Documents, in which case all rights and obligations of the Purchaser
and Bidders previously subject to the deadline will thereafter be subject to the deadline as
extended.

18. One Bid Per Bidder

Each Bidder / Consortium shall submit only one Bid by itself. No Joint Venture/Consortium
member should be member in more than one bid. A Bidder / Consortium member who Bidder
submits or participates in more than one Bid will cause all those Bids to be rejected. If the
Bidder / Consortium is - Meter Manufacturer / System Integrator /OEM/ Cloud Service
Provider/ Telecom Service provider for any part, may participate as - Meter Manufacturer /
System Integrator /OEM/ Cloud Service Provider/ Telecom Service provider in one or more
bid (s).
BSES

19. Late Bid

Any Bid received by the Purchaser after the deadline for submission of Bids prescribed by
the Purchaser, pursuant to Clause 17 of Section 2: Instructions to Bidders and Bid Data
Sheet, will be declared "Late" and shall be rejected and returned unopened to the Bidder.

20. Modification and Withdrawal of Bid

The Bidder is not allowed to modify or withdraw its Bid after its submission. Purchaser
reserve the right to forfeit the EMD submitted against tender in case of default by bidder.

21. Evaluation of Bid

Information relating to the examination, clarification, evaluation and comparison of Bids and
recommendations for the award of a contract shall not be disclosed to Bidders or any other
persons not officially concerned with such process. Any effort by a Bidder to influence the
Purchaser's processing of Bids or award decisions may result in the rejection of the Bidder's
Bid.

22. Clarification of Bids

To assist in the examination, evaluation and comparison of Bids, the Purchaser may, at its
discretion, ask the bidder for a clarification of its Bid. All responses to requests for
clarification shall be in writing and no change in the price or substance of the Bid shall be
sought, offered or permitted.

23. Preliminary Examination of Bids / Responsiveness

23.1 Purchaser will examine the Bids to determine whether they are complete, whether any
computational errors have been made, whether required sureties have been furnished,
whether the documents have been properly signed, and whether the Bids are generally in

Page 40 of 473
 order.
23.2 Arithmetical errors will be rectified on the following basis:
a. If there is a discrepancy between the unit price and the total price per item that is
obtained by multiplying the unit price and quantity, the unit price shall prevail and the total
price per item will be corrected.
b. If there is a discrepancy between the Total Amount and the sum of the total price per item,
the sum of the total price per item shall prevail and the Total Amount will be corrected.
23.3 Prior to the detailed evaluation, Purchaser will determine the substantial responsiveness of
each Bid to the Bidding Documents including product capability and acceptable quality of the
Goods/Services offered. A substantially responsive Bid is one, which conforms to all the
terms and conditions of the Bidding Documents without material deviation.
23.4 Bid determined as not substantially responsive will be rejected by the Purchaser and shall
not subsequently be made responsive by the Bidder by correction of the non -conformity.

24. Evaluation and Comparison of Bids

24.1 The evaluation of Bids shall be done based on the delivered cost competitiveness basis.
24.2 The evaluation of the Bids shall be a stage-wise procedure. In the first step the submitted
documents would be verified for completeness in accordance with Clause 1.7 of Section-1:
Request for Proposal. Thereafter, Techno-commercial evaluation of bids complete in all
aspect shall be carried out. Financial Proposals along with Supplementary Financial
Proposals, if any, of the Techno-commercially qualified Bidders shall be considered for final
evaluation.

25. Contacting the Purchaser

From the time of Bid submission to the time of contract award, if any Bidder wishes to
contact the Purchaser on any matter related to the Bid, it should do so in writing.
BSES

Any effort by a Bidder to influence the Purchaser and/or in the Purchaser ‘s decisions in
respect of Bid evaluation, bid comparison or Contract Award, will result in the rejection of the
Bidder ‘s Bid along with forfeiture of EMD.

26. Award of Contract

The Purchaser may award the Contract to the successful Bidder whose Bid has been
determined to be the lowest-evaluated responsive bid after negotiation as may be
necessary, provided further that the Bidder has been determined to be qualified to
satisfactorily perform the Contract. The Purchaser reserve the right to ask the component
wise costing breaks up from techno- commercially qualified bidders during finalization
process. Purchaser reserves the right to award order to other qualified bidders in the tender
provided it is required for timely execution of project.
a. Purchaser intends to award the business on a lowest bid basis, so bidders are
encouraged to submit the bid competitively. The decision to place purchase order/LOI
solely depends on purchaser on the cost competitiveness across multiple lots, quality,
delivery and bidder‘s capacity, in addition to other factors that Purchaser may deem
relevant.
b. In the event of bid getting selected by BYPL and subsequent DEFAULT on part of
bidder. Bidder will be required to pay BYPL an amount equal to the difference between
bidder’s bid and the next lowest bid on the quantity declared in NIT/RFP.
c. In case of any bidder’s performance is found unsatisfactory during the delivery process,
the award will be cancelled and BYPL reserves the right to award at bidder’s risk & cost
to other bidder’s who are found fit.

Page 41 of 473
27. Letter of Intent
The letter of intent (LOI) shall be issued to the successful Bidder whose bids have been
considered responsive, techno-commercially acceptable and evaluated to be the lowest (L1).
The successful Bidder shall be required to furnish a letter of acceptance within seven (07)
days of issue of the letter of intent by Purchaser.

28. Purchaser’s Right to Accept or Reject any or all Bids

The Purchaser reserves the right to accept or reject any Bid and to annul the Bidding
process and reject all Bids at any time prior to award of Contract, without thereby incurring
any liability to the affected Bidder or Bidders or any obligation to inform the affected Bidder or
Bidders of the grounds for the Purchaser ‘s action. EMD shall be returned to bidders in
occurrence of such an event.

29. Market Integrity

We have a fair and competitive marketplace. The rules for bidders are outlined in the Terms
& Conditions. Bidders must agree to these rules prior to their participation in tender. In
addition to other remedies available, we reserve the right to exclude a bidder from
participating in future tenders due to the bidder’s violation of any of the rules or obligations
contained in the Terms & Condition. A bidder who violates the marketplace rules or engages
in behavior that disrupts the fair execution of the marketplace will be restricted from
participation in future tenders of BYPL to length of time as decided by BYPL depending upon
the seriousness of the violation. Examples of violations include, but are not limited to:
- Failure to honor prices submitted to the market place.
- Breach of the terms published in the Request for Proposal/NIT.

30. Bidder Confidentiality

BSES

30.1 All information contained in this RFP is confidential and shall not be disclosed, published or
advertised in any manner without written authorization from BYPL. This includes all bidding
information submitted.
30.2 All RFP documents shall remain the property of BYPL and all Bidders are required to return
these documents to BYPL upon request
30.3 Bidders who do not honor these confidentiality provisions will be excluded from participating
in future bidding events of BYPL.

31. Specifications and Standards

As defined under Section 6: Project Requirements.

32. Quantity Variation

32.1 The purchaser reserves the rights to vary the quantities under AMI Contract subject to the
limit of –30% (thirty percent) up to +30% (thirty percent) of the tender quantity without any
change in the unit prices or other terms and conditions of the AMISP Contract and the Bid.

Page 42 of 473
Section 3: General Terms and Conditions
1. General Terms and Conditions

1.1. All the Bids shall be prepared and submitted in accordance with these instructions.
1.2. Bidder shall bear all costs associated with the preparation and delivery of their Bid, and the
Purchaser will in no case shall be responsible or liable for these costs.
1.3. The Bid should be submitted by the Bidder who has purchased the tender document online by
paying the tender fees. Under no circumstances tender document shall be transferred /sold to
the other bidder/party/company.
1.4. The Purchaser reserves the right to request for any additional information/document component
wise cost break up and also reserves the right to reject the proposal of any Bidder, if in the
opinion of the Purchaser, the data/detail in support of RFP requirement is incomplete.
1.5. The Bidder is expected to examine all instructions, forms, terms & conditions and specifications
in the Bid Documents. Failure to furnish all information required in the Bid Documents or
submission of a Bid not substantially responsive to the Bid Documents in every respect may
result in rejection of the Bid. However, the Purchaser’s decision in regard to the responsiveness
and rejection of bids shall be final and binding without any obligation, financial or otherwise, on
the Purchaser.

2. Definition of Terms

2.1. “Authorized Person” means such Person as may be authorized in writing by the BYPL to
exercise any rights or perform and fulfill any obligations of the BYPLunder this contract.
BSES

2.2. “BYPL” shall mean BSES Yamuna Power Limited (BYPL).

2.3. “Bidder” shall mean an entity submitting the bid in response to this RFP in accordance with
the provisions of this tender.
2.4. “Codes and Standards” shall mean all the applicable codes and standards as indicated in
the Technical Specification & Tender documents.
2.5. “Contract / Agreement” means collectively Letter of Intent (LOI) and/or Letter of Award
(LOA)(as the case may be), General Conditions of Contract (GCC) ,Special Condition of the
Contract (SCC), the Technical Specifications together with all of the Appendices attached
hereto, Purchase/Work Order, any special conditions to be incorporated as a part of LOA
and Appendices, written agreements, Tender Documents, all annexes, schedules,
enclosures and Documentation attached hereto or thereto, or incorporated herein or therein
as may be amended, modified or supplemented or superseded from time to time which are
signed between successful bidder and the Purchaser, valid under the Law.
2.6. “Contract Period” shall mean the period during which the “Contract” shall be valid /
enforceable as agreed between the Supplier and the Purchaser in the Contract and the
same is inclusive of extended contract period.
2.7. “Contract Value/Price” shall mean, the fixed lump sum value including Goods and Service
Tax (GST), tax collection at source (TCS) under Income Tax Act 1961, duty, cess, royalty,
statutory charges, local levies, stamp duty or fees imposed by Central or and State Govt or
local body or by municipal as set out in the Contract and Contract Price shall be adjusted or
varied as per Change in Law
2.8. “Dispute” means any dispute, difference or disagreement of any kind whatsoever between
Purchaser and the Vendor/Supplier in relation to or connection with or arising out of this
Contract, including, without limitation, any Dispute or difference concerning the existence,
validity or enforceability of the Contract or any provision hereof.

Page 43 of 473
2.9. “Infrastructure Sector” shall mean such sectors notified by Department of Economic
Affairs in its Gazette Notification no. 13/1/2017 – INF dated 26th April 2021 and as amended
from time to time.
2.10. “Letter of Award”/work order shall mean the official notice issued by the Purchaser
notifying the Supplier that his proposal has been accepted and it shall include amendments
thereto, if any, issued by the Purchaser. The “Letter of Award” issued by the Purchaser shall
be binding on the “Supplier”.
2.11. “Meter Commissioning” shall mean installation of meter, communication established
with backend system and data transferred to MDMS Successfully.
2.12. “Month” shall mean the calendar month and “Day” shall mean the calendar day.
2.13. “Offer Sheet” shall mean Bidder’s firm offer submitted to BYPL in accordance with the
specification.
2.14. “Purchaser” shall mean BSES Yamuna Power Limited, on whose behalf this bid enquiry is
issued by its authorized representative / officers.
2.15. “SCC” means ‘Special Conditions of Contract forming part of the Tender/ Contract /
Agreement.
2.16. “Specification” shall mean collectively all the terms and stipulations contained in those
portions of this bid document known as RFP, Scope of Work / Supply, Commercial Terms &
Condition, and Instructions to Bidders, Technical Specifications and the Amendments,
Revisions, Deletions or Additions, as may be made by the Purchaser from time to time.
2.17. “Supplier/Contractor or Supplier or Contractor” shall mean the successful Bidder and/or
Bidders whose bid has been accepted by the Purchaser and on whom the “Letter of
Intent/Award” is placed by the Purchaser and shall include his heirs, legal representatives,
successors and permitted assigns wherever the context so admits.
2.18. “Scope of Supply” shall mean the scope of supply as described in bid document.
2.19. “Tender/ Bid” means the Vendors’ final proposal (including the commercial or price
proposal) as accepted by the Purchaser pursuant to the invitation issued by the Purchaser
to the bidder for formal offers for the Execution of the Works including amendments if any.
BSES

2.20. “Scope of Work” shall mean scope of work defined under this Contract.
2.21. “Acceptance” shall mean and deemed to include one or more of the following as will be
stipulated in the specification:
i. Material dispatch clearance certificate (MDCC) of material issued by purchaser after the
inspection of material at supplier/ contractor works.
ii. Acceptance of material at Purchaser site / stores after its receipt and due inspection/
testing and release of Goods Receipt Note (GRN).
iii. Where the scope of the contract defined under section 6 includes supply, installation
and commissioning, acceptance shall mean implementation and delivery of required
services
2.22. “Latent Defect” shall mean a defect, inherently lying within the Goods/Equipment or arising
out of design deficiency, which do not manifest themselves and/or was not reasonably
discoverable / discovered up to the end of Defect Liability Period.
2.23. “Penalty” means amount payable to the Purchaser by the Vendor / Supplier under this
Contract / Agreement or under combination of other contracts / agreements with the same
Vendor / Supplier which may amounts to damages / compensation / interest or any other
additional charges due to breach of any conditions or terms during execution of the Works
towards due performance of the Contract.
2.24. “Liquidated Damages” shall mean reasonable predetermined/pre-agreed recoveries that
shall be initiated for any delay in actual Delivery as compared to scheduled Delivery and
includes any recovery due to any deviations in performance parameters as set out in the
Contract \ Tender Document. Liquidated Damages is an actionable claim which Supplier
shall pay to the Purchaser due to default or breach of obligations under the Contract.
Liquidated Damages includes GST amount.
2.25. “Communication” means instruction or information or written notice issued on letter head
or through electronic mail exchange between Parties and excludes verbal or short

Page 44 of 473
 messaging services (SMS). The notice shall be served by delivering a copy by electronic
mail, or registered post/speed post etc. Unless otherwise stated in the agreement, all
communications to be given under the Contract shall be in writing. Communication may be
sent to competent authority or authority delegated to such officer/employee. Communication
shall be on letter head of Party signed by competent authority/authorized signatory of the
Party.
2.26. “Delivery” unless and otherwise stated in the Contract, Delivery shall mean on FOR BYPL
Store basis.
2.27. “Advanced Metering Infrastructure” or “AMI” means an integrated system of Smart
Meters, communication networks and meter data management systems that enables two-
way communication between the utilities and consumer premises equipment. The functional
blocks of AMI typically include Unified HES — Head End System, WAN — Wide Area
Network, NAN — Neighborhood Area Network, DCU — Data Concentrator Unit / Gateway
and HAN — Home Area Network
2.28. “Advanced Metering Infrastructure Service Provider” or “AMISP”, means the
responsible implementation agency named in SCC appointed by BYPL for designing,
building, Integrate, operating and transferring the AMI Project in its area of operation upon
execution of the Contract subsequent to the Letter of Award referred to in SCC
2.29. “Affected Party” means any of the AMISP or the BYPL whose performance has been
affected by an event of Force Majeure or Force Majeure Event
2.30. “Affiliate” means, in relation to any Person, any entity Controlled, directly or indirectly by
that Person, any entity that Controls, directly or indirectly, that Person, or any entity under
common Control with that Person or, in case of a natural Person, any relative of such
Person. A holding or subsidiary company of any entity shall be deemed to be an Affiliate of
that entity. The Affiliate shall also include a Parent Company and an Ultimate Parent
Company.
2.31. “AMISP Service Charge” means the payment to be made by the BYPL to the AMISP in
Indian Rupee (INR) per meter per month for each category of meter as indicated in RFP;
BSES

2.32. “Applicable Laws” shall mean the laws and any other instruments having the force of law in
India as they may be issued and in force from time to time
2.33. “Bid” means the bid submitted by the Bidder(s) in response to the RFP and shall include the
Technical Bid and the Financial Bid
2.34. “Bidder(s)” means individual entity or consortium of entities bidding in response to the RFP
2.35. “Consortium Member” Any member of the bidding consortium other than the Lead
Consortium Member
2.36. “Control” means the power to direct the management and policies of an entity whether
through the ownership of voting capital, by contract or otherwise.
2.37. “AMISP Contract” or “Contract” shall mean this Contract entered into between, the
Selected Bidder (represented by the Lead Member acting for and on behalf of the
consortium if the Selected Bidder is a consortium) and the BYPL for undertaking the AMI
Project and is the legally binding written agreement signed by the Parties.
2.38. “Day” means a calendar day unless indicated otherwise
2.39. “Exit Management Period” shall mean the transition period encompassing the time from
the date of termination of the Contract or end of the Contract Period until the date upon
which all transition activities/ services are completed by the AMISP
2.40. “GCC” means these General Conditions of Contract.
2.41. “Goods” means any good(s)/solution supplied or to be supplied as apart I Solution by the
AMISP
2.42. “Independent Valuer” shall mean a qualified valuer duly registered under Companies
(Registered Valuers and Valuation) Rules, 2017 for Plant and Machinery and jointly
appointed by the Parties in the event of termination prior to Installation Milestone
2.43. “Month” means a calendar month unless indicated otherwise
2.44. “Operational Period” means the period from the Operational Go-Live till the end of the
Contract Period

Page 45 of 473
2.45. “Person” means any natural person, limited or unlimited liability company, corporation,
partnership, proprietorship, Hindu Undivided family, trust, union or any other entity that may
be treated as a Person under applicable law.
2.46. “Project or AMI Project” means the BYPL’s AMI Project defined in recital clause in the
Contract Form
2.47. “SCC” means the Special Conditions of Contract by which the GCC may be amended or
supplemented.
2.48. “Service(s)”or “Related Service(s)” means any service(s) performed or to be performed as
apart of the Solution by the AMISP
2.49. “SLA Default Notice” means notice to be issued by the BYPL in the event AMISP fails
meet any of the criteria specified in the SLA for cumulatively 3 (three) months in past 6 (six)
months so as to entitling levy of maximum penalty for such criteria
2.50. “Smart Meter” shall mean and is an ac static watt-hour meter with time of use registers,
internal connect and disconnect switches with two-way communication capability. It is
designed to measure flow of forward (import) or both forward (import) and reverse (export),
store and communicate the same along with other parameters defined in this standard. It
shall be remotely accessed for collecting data/events, programming for select parameters
(as defined in IS 16444 including any amendments or modifications to the same from time
to time)
2.51. “Solution” shall mean the AMI system implemented in its entirely including but not limited to
the designing, supply of hardware, software, transportation, installation, integration, testing,
commissioning, operation, maintenance, training and other services by the AMISP
2.52. “BYPL” shall have the same meaning as ascribed to it in the recital clause of the Form of
Contract.
2.53. “Meter-months”: At any point of time, meter-months of the AMI system is calculated as the
sum of number of months from operational on of the meter or Operational Go-Live,
whichever is later, for all meters installed and commissioned by the AMISP, taking into
account all Change Orders issued by the BYPL.
BSES

2.54. “Total Meter-months”: Total Meter-months of the AMI system is calculated as the product
of total number of smart meters installed, integrated and operationalized in the Project (by
taking into account all Change Orders issued by the BYPL) and 90 (ninety) months
commencing from Operational Go-Live
2.55. “Documents”/”Documentation” means all material, technical data, instructions,
descriptions, manuals including original equipment manufacturer manuals & operational
manuals, other Documents (whether recorded in writing or on electronic storage media)
related to the design, certificates, forms, manufacture, development, installation,
configuration, optimization, operation, maintenance, management, administration or
Interoperability of the Goods, training and operations, including factory tests
reports/Acceptance Test reports, and Vendor's standard Technical Documentation to be
provided by the Vendor under the Agreement or which may be necessary to support
Purchaser’s business requirements (such as testing, operating, and troubleshooting). It
shall also include following such as,
a. All Drawings furnished by the Purchaser
b. All Drawings submitted by the Supplier/Vendor with its bid proposal which have been
accepted in writing by the Purchaser
c. All Drawings in the Technical Specifications
d. Supplementary drawings furnished by the Purchaser to clarify and/or to define in
greater detail the intent of this Contract
e. L1 Drawings furnished by the Purchaser to the Supplier/Vendor during the progress of
the Work
f. Engineering data and drawings submitted by the Supplier/Vendor during the progress
of the Work which have been accepted in writing by the Purchaser and any other
Documents, manuals and instructions furnished by the Purchaser pertaining to the
design, engineering, procurement, construction, erection, installation, testing,

Page 46 of 473
 completion, commissioning, performance testing and achievement of Acceptance
Certificate.
2.56. “Parent(s) Company” shall mean an entity that is either (i) a Company or an AIF or a
Foreign Investment Fund that holds at least twenty six percent (26%) of the –paid - up
equity capital directly or indirectly in the Bidder, as the case may be; or (ii) an AIF or
Foreign Investment Fund that has the power to direct the management and policies by
operation of law or contract;
2.57. "Ultimate Parent Company" shall mean an entity which owns at least twenty six percent
(26%) equity in the Sole Bidder or Member of a Consortium, (as the case may be) and in
the Technically Evaluated Entity and/or Financially Evaluated Entity (as the case may be)
and such Sole Bidder or Member of a Consortium, (as the ease may be) and the
Technically Evaluated Entity and/or Financially Evaluated Entity (as the case may be)
shall be under the direct control or indirectly under the common control of such entity.

3. Interpretations

In the interpretation of this Contract, unless the context otherwise requires:

i. BYPL, the Selected Bidder, and the AMISP/ Contractor shall individually be referred to
as “Party” and collectively as “Parties”.
ii. Unless otherwise specified a reference to an Article number is a reference to all of its
sub-articles
iii. Unless otherwise specified a reference to a clause, sub-clause or section is a reference
to a clause, sub-clause or section of this Contract including any amendments or
modifications to the same from time to time.
iv. A word in the singular includes the plural and a word in the plural includes the singular.
v. A word importing a gender includes any other gender.
vi. A reference to a person includes a partnership and a body corporate.
vii. A reference to legislation includes legislation repealing, replacing or amending that
BSES

legislation.
viii. Where a word or phrase is given a particular meaning, it includes the appropriate
grammatical forms of that word or phrase which has a corresponding meaning.
ix. In the event of an inconsistency between the terms of the RFP, Bid submitted by the
Selected Bidder and the subsequent Contract, the terms of the Contract hereof shall
prevail.
x. Whenever a material or article is specified or described by the name of a particular
brand, manufacturer or trademark, the specific item shall be understood as establishing
type, function and quality desired. Products of other manufacturers may also be
considered, provided sufficient information is furnished so as to enable BYPL to
determine that the products are equivalent to those named.
xi. No amendment or other variation of this Contract shall be valid unless it is in writing, is
dated, expressly refers to this Contract, and is signed by a duly authorised
representative of both BYPL and the AMISP thereto.
xii. An illustration of the methodology for determining the ‘Total Meter-Months’ as well as
‘Operation and Maintenance Period of the AMI system’ is provided in SCC.

4. Priority of Contract Documents:

The several documents forming the Contract are to be taken as mutually explanatory of one
another, but in case of ambiguities or discrepancies, the same shall be explained and adjusted
by the Purchaser, who shall thereupon issue to the Contractor, instructions thereon. In such
event, unless otherwise provided in the Contract, the priority of the documents forming the
Contract shall be as follows:
1. The Contract Agreement including all terms & condition of Contract.
2. Acceptance of the Letter of Intent/Award.
3. Agreed Minutes of the Tender Negotiation Meetings.

Page 47 of 473
 4. Agreed Minutes of the Tender Technical Meetings.
5. The Priced Bill of Quantities.
6. The Technical Specifications / Scope of work
7. Corrigendum the latest taking precedence.
8. The Tender document, including all Appendices and/or Addenda,

In the event of any conflict between the above-mentioned documents, the more stringent
requirement or conditions which shall be favorable to the BYPL shall govern and the decision of
BYPL shall be final and binding upon the parties/Bidder.

5. Packing, Packing List & Marking (wherever applicable)

a. Packing: Supplier shall pack or shall cause to be packed all Commodities in
crates/boxes/drums/containers/cartons. And otherwise in such a manner as shall be
reasonably suitable for shipment by road or rail to BYPL, Delhi/New Delhi stores/site
designated for the purposes of this Project without undue risk of damage in transit. All the
packaging materials as prescribed shall be supplied preferably with bio-degradable packing-
materials.
b. Packing List: The contents of each package shall be itemized on a detailed list showing the
exact weight, extreme outside dimensions (length, width & weight) of each
container/box/drum/carton, Item SAP Code, PO No & date along with Bar code having details
of meter serial number. One copy of the packing list shall be enclosed in each package
delivered. Further the package shall comply the provisions of Legal Metrology (Packaged
Commodity) Rules, as amended upto date.

6. Shelf Life of Goods (wherever applicable)

a. The Shelf Life of any Goods or its parts means the same as assured by the Vendor /
Supplier/ original manufacturer to perform for the purpose it is supplied under the Contract to
the Purchaser which includes the guaranteed period of such Goods, after expiry of such
BSES

period, the Goods has to be replaced. Upon Delivery of such Goods at Purchaser’s/Owners’
designated premises, the Shelf Life of Goods must be performed 100% or optimum level as
prescribed / guaranteed. The Vendor shall submit the original manufacturer’s certificate
towards its Shelf Life against each of such Goods Delivered.

b. Any Delivery of Goods at Purchaser’s designated premises having Shelf Life less than the
Shelf Life mentioned above shall be subjected to prior written approval of Owner/Purchaser
and such Goods may be accepted or rejected at the absolute discretion of Owner/
Purchaser. If any Goods are delivered, whose Shelf Life does not conform to the above
requirements, it shall promptly be replaced by the Vendor at its own cost within Fifteen (15)
working days upon being notified by the Purchaser. Such replaced Goods must have the
Shelf Life, at least for the balance period of the original replaced Goods. The expenses/cost
of replacement of such Goods along with all other ancillary costs including taxes, duties and
cess etc., shall be borne by the Vendor and the Purchaser shall in no way bear any cost,
expenses, charges, interest, Compensation etc., towards such replacement.

7. Shipping, Inspection and Dispatch Shipping (wherever applicable)

7.1 Pre-Inspection Communication

As soon as Goods are ready for inspection, Supplier must communicate to Purchaser/
indicating the details of Goods that will be offered for inspection.

7.2 Post-Inspection Communication

Supplier shall advise the Purchaser the details of Goods that have been cleared for dispatch
with Contract reference details to enable the Purchaser to issue dispatch instructions.

Page 48 of 473
7.3 Dispatch of Goods
a. Supplier shall, at its own cost, be responsible for transportation and dispatch of the goods,
including Loading/Unloading, Storage at AMISP storage, and shall notify the Purchaser
when Goods are ready for dispatch but shall not affect dispatch until instructed by
Purchaser in writing.
b. Should Goods be dispatched prior to receipt of written instruction, Purchaser reserves the
right to return Goods to Supplier’s or Sub-Vendor’s works at Supplier’s Risk and Cost.
Irrespective of whether Goods are so returned or not, payment will be deferred until
Purchaser accepts Goods for their intended use. Such an acceptance will be subject to
the satisfactory fulfillment of Purchaser’s requirement, which may include alternative
examination, testing and inspection, additional guarantees and other compensations, all at
Supplier’s cost.
c. Supplier shall be liable for any additional cost (including taxes, duties and other charges if
any) to be incurred by the Purchaser resulting from Supplier’s failure to comply with
Purchasers’ requirements for documentation, certification, packing, marking, shipment
and place of Delivery under the Contract. Any cost incurred by the Purchaser due to
submission of incorrect Documentation by the Supplier, shall be to the account of the
Vendor.

7.4 Receipt of Goods (As applicable)

On receipt of the Goods at designated premises as stipulated in the Contract, Purchaser shall
acknowledge the receipt of the Goods under terms and conditions of the Contract. It is
Supplier’s responsibility to deliver at designated place, the AMISP assumes all Risk and Cost
due to any issues including of incorrect or incomplete Documentation, till Goods/Equipment is
duly accepted by BYPL in terms of the Contract.
BSES

7.5 Unloading and Storage (Wherever Applicable)

The Supplier shall, at its own cost, upon Delivery to the designated Store/Site store, be
responsible for unloading, handling and storage of Goods including expediting, receiving,
inspection and documentation.

The Supplier shall open and maintain warehousing facility for storage at Site store along with
watch and ward, if required (in accordance with manufacturers’ recommendations and taking
into account climatic and other relevant conditions at the warehousing Site) for all
Goods/Equipment.

All Goods / Equipment’s shall be (i) stored at appropriate location approved in advance by
Purchaser, and ii) properly tagged and identified for segregated from other goods. The
Supplier shall arrange and be responsible for security of all the Goods / Equipment’s to be
incorporated in or forming part of the facilities and tools, tackles spares and other items, which
are required to be delivered to the Purchaser under the Contract till acceptance of such items,
as the case may be, by the Purchaser.

7.6 Price Basis

a) Bidder to quote their prices on Landed Cost/ FOR BYPL store basis and separate price for
each item.
b) FIRM prices for supply to AMISP’s Delhi/New Delhi stores inclusive of packing, forwarding,
loading at manufacturer’s premises, payment of all taxes, GST, Freight, unloading any other
local charges etc.
c) The above supply prices shall also include unloading at AMISP’s Delhi/New Delhi
stores/site.

7.7 Taxes & Duties:

Page 49 of 473
 a. Prices shall be inclusive of all taxes and duties including Labour cess (Except GST).
However, IT as per applicable rate will be deducted from your bills as Tax Deduction at
Source (TDS).
b. GST at actual shall be paid extra on submission of GST Registration and self-declaration
on your letter head stating that you have deposited/or will deposit the Tax as per the
applicable GST laws. You shall furnish your GST registration number.
c. Any statutory variations i.e. increase/decrease in Taxes / Duties introduces by Central
Govt. / State Govt. of shall be reimbursed/recovered to/from Contractor against
documentary evidence and proof.
d. As Per Notification No. 39/2021 # Central Tax dated 21st December, 2021 w.e.f
01/01/2022 registered person (i.e., Recipient/Purchaser) can avail tax credit on those
invoices only which have been reflected in GSTR 2A or GSTR 2B (it means 100%
matching of invoice is required). Also, GST has to be deposited by Supplier/Contractor by
filing of GSTR- 1 and GSTR-3B.
e. In view of above, if the same is not complied with by the supplier/Contractor and the
Recipient/Purchaser is not in position to avail / utilize Input Tax Credit due to non-
compliance or non-filing of GSTR-1 and GSTR-3B for the month/quarter (as applicable) in
which the supply was made, then Recipient/Purchaser has right to hold 100% GST
amount from next payment due of the subsequent month till the time default is not cured.
f. For releasing of the payment kept on hold on account of GST supplier shall submit
payment proof i.e., GST Portal screenshot reflecting name of Recipient/Purchaser along
with GSTR-1 and GSTR-3B for month/quarter (as applicable) in which the same has been
discharged. Payment shall not be released, till the time proof of payment of GST as
mentioned above is not submitted.
g. Further, the recipient/purchaser shall also be entitled to recover any financial loss incurred
(including tax, interest and penalty) due to non-compliance or non-filing of GSTR-1 and
GSTR-3B by the supplier.
h. In case where delivery of goods is being made on FOR site basis, the Supplier is
BSES

responsible to comply with rules applicable for E-way bill. Any violation in provision of E-
way Bill will attract penalty and seizure of Transit Material. Any Penalty and Pre-Deposit
due to violation of rules/provision shall be paid and borne by Supplier. Also, Supplier is
responsible for releasing of goods from Authority whether CGST/SGST. Delay in supply
due to seizure of goods shall attract liquidated damages as per Order / Agreement
provisions."
i. Purchase Order value shall not be subject to any variation on account of variation in
Exchange rate(s).
j. Taxes & Duties on raw materials & bought out components:
Taxes & Duties on raw materials & bought out components procured indigenously /
imported are included in Order Value and are not subject to any escalation or variation for
any reason whatsoever.

8. Price Validity

8.1 Bids shall remain valid & open for acceptance for a period of 180 days from due date of
submission or amended due date of submission whichever is later,
8.2 Notwithstanding Clause 8.1 above, the Company may solicit the Bidder‘s consent to an
extension of the Period of Bid Validity and the bidder shall be liable to extend the same at the
sole cost and consequences of the bidder and no claim from the company in this regard shall
be maintainable.

9. Contract cum Performance Security Bank Guarantee (CPBG):

i. AMISP shall furnish the CPBG in the prescribed format within 28 days from the date of issue
of LOI / Work Order/LOA for due performance of the provisions of Work Order/Agreement.

Page 50 of 473
 The CPBG shall be of 3% of total contract value inclusive of taxes & duties and shall be
valid till agreement period, plus three (3) months or latest RBI guidelines (if any) whichever
is higher towards claim period, if not otherwise specified for other tenure in agreement. This
amount shall remain fixed during the currency of the agreement.
ii. The CPBG shall be issued from any nationalized / scheduled bank as per company format.
iii. The Company shall reserve the right to invoke the CPBG unconditionally and without
recourse to the Contractor, if there is failure to perform any part of the Agreement for
whatsoever reason. This clause is pertaining to performance of contractual obligations and
the decision of Company shall be final in this regard.
iv. Contract Performance Bank Guarantee established under Clause 8 of section 5 shall
contain a statement that it shall be automatically and unconditionally forfeited without
recourse and payable against the presentation by BYPL of this Performance bank
guarantee, to the relevant bank referred to above, together with a simple statement that
AMISP has failed to comply with any term or condition set forth in the Contract.
v. In the event of any claim or any other outstanding Contractual obligations remaining
unfulfilled, AMISP shall be required to extend the CPBG till the settlement of all claims and
completion of all Contractual obligations at the cost and consequences of AMISP.
vi. In the event, in Company’s sole judgment, the AMISP has fulfilled all its obligations under
this Agreement, The CPBG shall be released, without any interest, after the expiry of CPBG
and its claim period as mentioned above on recommendation of Engineer In-charge.
vii. If the CPBG becomes invalid for any reason (other than its expiry), AMISP shall immediately
notify BYPL and obtain within five (5) days a replacement CPBG in the form set out in the
Contract/Agreement.
viii. No later than sixty (60) Business Days before the expiry of the CPBG, AMISP shall, upon
request of the BYPL obtain extension of the validity of such CPBG for the period stated in
such request by the BYPL and provide a copy of such renewed guarantee.
ix. It is AMISP’s responsibility to incur charges / cost to maintain and for extension of CPBG
BSES

without claiming reimbursement from the BYPL.

10. Warranty/Defects Liability Period

AMISP do hereby guarantee BYPL about the services/material provided, against any defect /
failure, which arise due to faulty services/materials/workmanship/design for the entire defects
liability period. The Defect liability period shall be additional 6 months from the completion of
contract period. If during the Guarantee period any materials / items/ Services are found to be
defective, these shall be replaced/installed/Corrected, free of cost by the bidder at its own cost
as per DERC norms from the date of receipt of intimation. The root cause analysis of the
defect within Guarantee period shall be provided by AMISP to BYPL.

The Supplied Smart Meters including NIC card, Meter Boxes & accessories shall be
guaranteed for a period of One Hundred Twenty Months (120) from the date of the installation
& commissioning or One Hundred Twenty Six Months (126) from the date of receipt of material
at site/stores whichever is earlier and for Software, warranty/support period shall be valid till
the Contract Execution Period/Contract Period.

BYPL shall provide the meter serial number details to AMISP before the manufacturing. For
defective smart meters under warranty, replacement of meter has to be provided by AMISP.
The replacement meters shall have different Meter Serial Numbers. The process/terms shall
be mutually agreed between the AMISP & BYPL. The smart meters and seals to be scrapped
as per BYPL standard operating process.

11. Return, Replacement or Substitution

BYPL shall give notice to AMISP of any defective Commodity promptly after becoming aware
thereof. BYPL shall in its discretion elect to return defective Commodities to AMISP for

Page 51 of 473
 replacement, free of charge to BYPL, or may reject such Commodities and purchase the same
or similar Commodities from any third party. In the latter case BYPL shall furnish proof to
AMISP of the cost of such substitute purchase. In later case, all costs of any replacement,
substitution, shipping, labour and other related expenses incurred in connection with the return
and replacement or for the substitute purchase of a Commodity hereunder should be for the
account of AMISP. BYPL may set off such costs against any amounts payable by BYPL to
AMISP or to recover through any other method provided under this contract.

12. Rights, Title and Interest to AMI System and Equipment

12.1 The ownership, benefits, tangible and intangible rights of whatsoever or howsoever nature
and title to the AMI system and other equipment installed by AMISP for operation of the
AMI system pursuant to this agreement shall vest with BYPL and BYPL shall have right to
alter/amend, modify, display such system/material to any third party for any further
commercial use or otherwise.
12.2 AMISP hereby, without any further consideration, irrevocably assigns to BYPL, its
successors and assigns, all rights, title and interest in AMI System and other equipment
so developed/deployed by AMISP under this Agreement, free and clear of all liens and
encumbrances, which shall be the sole property of BYPL.
12.3 Notwithstanding such transfer of title, the AMISP shall continue to be responsible for
installation, implementation and provisions of cloud hosting and 4G/ NBIoT data services,
Testing, Commissioning and O&M of the entire system in accordance with the Contract/
Agreement.

13. Intellectual Property

13.1 The original source code of the product software delivered by OEM/Service Provider/
BSES

AMISP under the agreement shall be the property of the OEM/Service Provider/ AMISP,
whereas OEM/Service Provider/ AMISP shall, in perpetuity and at all times be liable to
provide all assistance to BYPL using the said source code specific to the needs of BYPL,
without any additional cost, according to the provision of the agreement. Whereas in case
of change of management of OEM/Service Provider/ AMISP in case of following defaults, it
shall be the responsibility of OEM/Service Provider/ AMISP to transfer the original source
code to BYPL before such corporate event and BYPL shall have charge over the same in
such circumstances:
a) cessation of business or dissolution of the supplier,
b) cessation of marketing of the software subject to the contract before the end of the
contract and/or cessation of maintenance of the software under the contract
c) termination of the contract for failure of the provider to meet its contractual obligation
d) liquidation of the provider by mutual agreement or by court order.

It is however clarified that all further development & customization after the delivery of the
Base product by OEM/Service Provider/ AMISP to BYPLunder the agreement, including
the source code of the developments specific to the needs of BYPLwill be disclosed to
BYPLafter a period of 8 years and such customized version of the product shall be
property of BYPLand BYPLshall be free to use the same in any manner whatsoever.

AMISP acknowledges and agrees that AMISP has been specifically engaged by BYPLto
deliver the services as detailed in this agreement. AMISP further acknowledges and
agrees that the work product inclusive of materials having Intellectual Property
Rights/copyright/mark/design (including but not limited to all Source code, Object code,
records, reports, designs, application configurations, data and written material, products,
specifications, reports, drawings and other documents) conceived, made, developed
and/or created by AMISP specifically to the needs of BYPL, either solely or jointly with

Page 52 of 473
 others pursuant to this Agreement, is, and shall, for all intents and purposes, be deemed a
“work made for hire” for copyright purposes, with all intellectual property rights vesting and
accruing therein shall be owned by BYPL as per Clause 13.1.

Should BYPL be unable to secure AMISP’s signatures on any document necessary to

apply for, prosecute, obtain, or enforce any trade mark, copyright, or other right or
protection relating to the work so developed by AMISP, whether due to AMISP’s incapacity
or any other cause, AMISP hereby irrevocably designates and appoints BYPL and each of
its duly authorized directors, officers and agents as AMISP’s agent and attorney in fact, to
act for and on AMISP’s behalf and stood and to execute and file any such document, and
to do all other lawfully permitted acts to further the prosecution, issuance, and enforcement
of trademarks, copyrights, or other rights or protections with the same force and effect as if
executed and delivered by AMISP pursuant to this agreement.

AMISP shall ensure that while it uses any software, hardware, processes, document or
material in the course of performing the Services, it does not infringe the Intellectual
Property Rights of any person and the AMISP shall keep BYPL its
officers/employees/directors indemnified, in full,/compensate/make good of losses suffered
against all costs, expenses and liabilities howsoever including litigation cost, arising out
any illegal or unauthorized use or in connection with any claim or proceedings relating to
any breach or violation of any permission/license terms or infringement of any Intellectual
Property Rights by the AMISP or its personnel during the course of performance of the
Related Services.

In case of any legal proceedings/claims/disputes or other proceedings citing/alleging IPR

infringement by the AMISP, AMISP shall solely be responsible to handle/defend all such
proceedings/disputes with the power to settle such disputes, without affecting BYPLin any
manner. BSES

Notwithstanding anything above, no liability of BYPLshall arise in this respect, and any
costs, damages, expenses, compensation payable by BYPLin this regard to a third
party/parties, arising from a legal proceeding/s or otherwise, and the same shall be
recoverable from AMISP.

14. SLAs and SLA Audit

14.1 The AMISP shall be liable to penalties in the event of non-compliance of Service Level
Agreements as specified in Section 6: Project Requirements and Scope of Work.
14.2 A designated team/ person from BYPL may review the system generated SLA
performance report of AMISP each month. The review/audit report will form basis of any
action relating to imposing penalty on or breach of Contract of the AMISP.

15. Time – The Essence of Contract

The time and the date of completion of the work as stipulated in the Letter of Intent /
Purchase Order issued to the AMISP shall be deemed to be the essence of the
“Contract”. The supply, installation, testing and commissioning has to be completed not
later than the aforesaid Schedule and date of completion.

AMISP shall be responsible for performance of work under contract in accordance with
the specified schedule. if at any time, AMISP is falling behind the schedule for reasons
attributable to it, AMISP shall take necessary action to make good for such delays by
increasing its work force or by working overtime or otherwise to accelerate the progress of
the work and to comply with schedule and shall communicate such actions in writing to

Page 53 of 473
 BYPL, satisfying that AMISP’s action will compensate for the delay. AMISP shall not be
allowed any extra compensation for such action.

16. Contract Commencement date

The date of issue /award of contract shall be the effective date of contract or contract
commencement date.

17. Contract Completion Date

The date of expiry of Guarantee/Warranty Period shall be deemed as the Contract

Completion date.

18. Contract Period /Time

Total contract period shall be of 120 months from the date of contract commencement date.
Initial 30 Months from Contract Commencement Date shall be considered as Execution
period. Thereafter the period of 90 meter Months, for each installation, shall be considered
as O&M Period. The period from Contract Commencement Date to Contract Completion
Date shall be deemed as the Contract Period /Time.

19. Contract Execution Completion Date

The stipulated date for completing the execution and delivery of all items in the schedule of
quantities (Supply, Service and or both as applicable) shall be deemed as the Contract
Execution Completion Date.
BSES

20. Contract Execution Period/Time

The Period from Contract Commencement Date to Contract Execution Completion Date
shall be the Contract Execution Period/Time. Timely Completion of Works/Timely Delivery
of Materials is the essence of the contract. The period from contract commencement date to
the date stipulated for completion of delivery of all items/completion of all the
works/services, as per schedule of quantities of the contract is defined as contract execution
completion time. The Delivery of Materials /The Completion of Works, as applicable, should
be achieved in all respects as per schedules of quantities and all the terms and conditions
of the contract, in the contract execution time. Any revision/amendment in the originally
stipulated contract execution time has to be approved by authorized representative of
BYPL.

21. Applicable Laws and Jurisdiction of Contract

21.1 The relationship between the parties will be governed and construed in accordance with
THE LAWS OF INDIA.

21.2 Arbitration
To the best of their ability, the parties hereto shall endeavor to resolve amicably between
themselves all disputes arising in connection with the proposed Agreement. If the same
remain unresolved, within fifteen (15) days of the matter being raised by either party, either
party may refer the dispute for settlement by arbitration. The arbitration to be undertaken by
sole arbitrator to be Jointly Appointed by the parties. The decision of the arbitrator shall be
final and binding upon both the parties. The arbitration proceeding shall be conducted in
accordance with the provisions of the Indian Arbitration & Conciliation Act, 1996 and the

Page 54 of 473
 venue and seat of such arbitration shall be New Delhi only. The language of Arbitration shall
be English Language. The cost of Arbitration shall be equally shared between the parties
unless otherwise directed by the sole arbitrator.

21.3 The courts at New Delhi shall have exclusive jurisdiction in all matters relating to or arising
between the parties relating to this bid document.

22. Events of Default

22.1 Each of the following events or occurrences shall constitute an event of default ("Event of
Default") under the Contract:
i. AMISP fails or refuses to pay any amounts/charges/dues/penalty due under the
Contract;
ii. AMISP fails or perform services/deliver product/equipment as per the terms of
agreement / specifications, or fails to perform services/deliver product/equipment
within the time period specified in P.O./Agreement or any extension thereof
iii. AMISP becomes insolvent or unable to pay its debts when due, or commits any act of
bankruptcy, such as filing any petition in any bankruptcy, winding-up or
reorganization proceeding, or acknowledges in writing its insolvency or inability to pay
its debts; or AMISP's creditors file any petition relating to bankruptcy of AMISP;
iv. AMISP otherwise fails or refuses to perform or observe any term or condition of the
Contract and such failure is not remediable or, if remediable, continues for a period of
15 days after receipt by the Supplier of notice of such failure from BYPL.

23. Consequences of Default

23.1 If an Event of Default occur and be continuing, BYPL may forthwith terminate the
BSES

Contract by written notice.

23.2 In the Event of Default, BYPL may, without prejudice to any other right granted to it by
law, or the Contract, take any or all of the following actions;
i. Present for encashment to the relevant bank the Contract Performance Bank
Guarantee;
ii. Purchase the same or similar Commodities from any third party; and/or Recover any
losses and/or additional expenses BYPL may incur as a result of AMISP's default.
iii. Debar AMISP for at least for three (03) years from participating in all future tenders
of BYPL and all its Group/associates companies.

24. Force Majeure

24.1 General
An "Event of Force Majeure" shall mean any event or circumstance not within the
reasonable control, of the Party affected, but only if and to the extent that:

(i) Such event or circumstance, despite the exercise of reasonable diligence, could not
have been prevented, avoided or reasonably foreseen by such Party
(ii) Such event or circumstance materially and adversely affects the ability of the affected
Party to perform its obligations under this agreement, and the affected Party has
taken all reasonable precautions, due care and reasonable alternative measures in
order to prevent or avoid the effect of such event on the affected party's ability to
perform its obligations under this Agreement and to mitigate the consequences
thereof. For the avoidance of doubt, if such event or circumstance would not have
materially and adversely affected the performance of the affected party had such
affected party followed good industry practice, such event or circumstance shall not
constitute force majeure.

Page 55 of 473
 (iii) Such event is not the direct or indirect result of the failure of such Party to perform
any of its obligations under this Agreement and
(iv) Such Party has given the other Party prompt notice describing such events, the effect
thereof and the actions being taken in order to comply the relevant clause.

24.2 Specific Events of Force Majeure

Subject to the provisions of the agreement, Events of Force Majeure shall include only the
following to the extent that they or their consequences satisfy the above requirements:
1. The following events and circumstances:
a. Effect of any natural element or other acts of God, including but not limited to
storm, flood, earthquake, lightning, cyclone, landslides or other natural disasters,
and\
b. Explosions or fires or flood
2. Public disorder, insurrection, rebellion, sabotage, riots or violent demonstrations of a
local character
3. Declaration of the Site as war zone.
4. Any order, regulation, directive, requirement from any Governmental, legislative,
executive or judicial authority

24.3 Notice of Events of Force Majeure

If a force majeure event prevents a party from performing any obligations under the
Agreement in part or in full, that party shall:
i) Immediately notify the other party in writing of the force majeure events within 2
working days of the occurrence of the force majeure event
ii) Be entitled to suspend performance of the obligation under the Agreement which is
affected by force majeure event for the duration of the force majeure event
BSES

iii) Use all reasonable efforts to resume full performance of the obligation as soon as
practicable
iv) Keep the other party informed of all such efforts to resume full performance of the
obligation on a regular basis
v) Provide prompt notice of the resumption of full performance or obligation to the other
party.

24.4 Mitigation of Events of Force Majeure:

AMISP shall:
(i) Make all reasonable efforts to prevent and reduce to a minimum and mitigate the
effect of any delay occasioned by an Event of Force Majeure, including applying
other ways in which to perform the agreement
(ii) Use its best efforts to ensure resumption of normal performance after the
termination of any Event of Force Majeure and shall perform its obligations to the
maximum extent practicable as agreed between the Parties; and
(iii) Keep the Company informed at regular intervals of the circumstances concerning
the event of Force Majeure, with best estimates as to its likely continuation and what
measures or contingency planning it is taking to mitigate and or terminate the Event
of Force Majeure.

24.5 Burden of Proof

In the event that the Parties are unable in good faith to agree that a Force Majeure event
has occurred to an affected party, the parties shall resolve their dispute in accordance
with the provisions of this agreement. The burden of proof as to whether or not a force

Page 56 of 473
 majeure event has occurred shall be upon the party claiming that the force majeure event
has occurred and that it is the affected party.

24.6 Termination for Certain Events of Force Majeure.

If any obligation of any Party under the Agreement is or is reasonably expected to be

delayed or prevented by a Force Majeure event for a continuous period of more than 1
(one) month during the Term of the Agreement, the Agreement shall be terminated at the
discretion of the Company and neither Party shall be liable to the other for any
consequences arising on account of such termination.

Notwithstanding anything stated in this agreement, BYPL may terminate the agreement
after giving 7 (seven) days’ notice, if any of following occurs:
i. AMISP fails to complete execution of works within the approved schedule of works,
terms and conditions.
ii. AMISP commits any Act of Insolvency, or adjudged insolvent.
iii. AMISP has abandoned the Agreement.
iv. AMISP has failed to commence work or has suspended the progress of works
v. AMISP has failed to proceed the works with due diligence and failed to make such
due progress

24.7 Limitation of Force Majeure Event.

The AMISP shall not be relieved of any obligation under the Contract solely because cost
of performance is increased, whether as a consequence of adverse economic
consequences or otherwise.

24.8 Extension of Contract Period due to Force Majeure Event.

BSES

The Contract period may be extended by mutual agreement of Parties by

way of an adjustment on account of any period during which an obligation of either Party
is suspended due to a Force Majeure event.

24.9 Effect of Events of Force Majeure.

Except as otherwise provided herein or may further be agreed between the Parties,
either Party shall be excused from performance and neither Party shall be construed to be
in default in respect of any obligations hereunder, for so long as failure to perform such
obligations shall be due to an event of Force Majeure."

25. Severability

If any provision of this Agreement is or becomes invalid or unenforceable by the courts of

any jurisdiction to which it is subject, such invalidity or unenforceability shall not prejudice
the remaining provisions of this Agreement, which shall continue in full force and effect.

26. Sub-Contracting / Sub-Letting

26.1 AMISP shall not assign or transfer the whole or any part of this agreement or any other
benefits accruing there from, nor shall it subcontract the whole or any part of the Works
without the prior written consent of BYPL.
26.2 The AMISP shall be permitted to appoint subcontractor(s) so as to meet its obligations
under the Contract with the Utility, provided they ensure that any person engaged by AMISP
are not blacklisted/ debarred/banned/ suspended as on the date (as defined in Clause 5

Page 57 of 473
 under Section 2 of this RFP)." As condition precedent to Contract signing, the AMISP shall
seek approval of BYPL to appoint selected implementation partner(s)/subcontractors(s) with
respect to Meter, HES, MDMS, Prepaid Solution, Cloud Service and System Integrator. Any
change in such implementation partner(s)/subcontractors(s) during the course of Project
Execution shall entail approval from BYPL.
26.3 In the event the AMISP assigns this Contract to any Sub-vendor/Contractor after due
approval of Purchaser, AMISP's assignees/Sub-Contractor shall also be bound by the terms
and conditions of this Contract (including Statutory compliance, Safety standards & Codes
of conduct) and shall, if deemed necessary by BYPL at the time of such assignment,
undertake in writing to be so bound by this Contract.
26.4 Notwithstanding the subcontracting of any portion of the works, AMISP shall remain wholly
responsible for the carrying out, completion and satisfactory execution of Works in all
respects in accordance with this Contract, specification, approved drawings and data
sheets. AMISP shall be solely responsible for all the acts, deeds and contractual obligation
and consequences thereof of its sub-contractor.
26.5 AMISP shall submit the agreement copy of subcontract, past experience and financial
capability and statutory documents of subcontractors with BYPL review and approval.

27. Recoveries

Whenever under this contract any money is due/recoverable from and payable by AMISP,
BYPL shall, notwithstanding any provision to the contrary included in the contract, be
entitled to recover such sum by appropriating in part or in whole by deducting from any
sum due or which any time thereafter may become due from AMISP whether related to
this contract or other contracts against AMISP. Should the sum be not sufficient to cover
the full amount recoverable, AMISP shall pay to BYPL on demand the balance amount.

28. Waiver
BSES

No delay or forbearance/failure by BYPL in exercising/to enforce any right/condition or

power under this Agreement/contract shall be construed as a waiver of such right or
power, nor shall any single or partial exercise of such right or power preclude any further
exercise of such right of power.

29. Indemnification

29.1 AMISP shall indemnity, defend, save and hold harmless all directors, BYPL and its
employees against any and all suits, proceedings, actions, demands and third-party
claims for any loss, damage, cost and expense suffered by BYPL on account of the
negligence, act or omission inaction by AMISP or its employees under this Agreement.
AMISP shall also wholly indemnity and compensate BYPL against any theft,
misappropriation, fraudulent act or omission, any collusion with customer/s, intentional
recording of incorrect reading/DATA, or any other offence under the applicable laws or
breach of obligation under the present agreement, and would also render itself liable to
appropriate legal action being initiated against it BYPL.
29.2 AMISP shall also be responsible and liable to BYPL for any loss or damage caused to
BYPL for any negligence or inaction, damage to the property of BYPL caused by AMISP
or its employees.

30. Termination of Contract

30.1 BYPL may, without prejudice to any of its other rights or remedies under the Contract or in
law, terminate the whole or any part of this Contract by giving 90 days written notice to
AMISP, if in the opinion of BYPL, the work under the order is not being performed

Page 58 of 473
 satisfactory/ the performance of AMISP not found satisfactory or AMISP commits a breach
of any of the provisions of this Contract including but not limited to any of the following:
i. Failing to complete execution of work within the terms specified in the Contract.
ii. Failing to complete works in accordance with the approved schedule of works.
iii. Failing to meet requirements of specifications, drawings, and designs etc as approved
by BYPL.
iv. Failing to comply with any reasonable instructions or orders issued by BYPL in
connection with the works.
v. Failing to comply with any of the terms or conditions of this Contract.
vi. AMISP repudiates this order or otherwise evidences intention not to be bound by this
order.
vii. AMISP assigns, mortgages, or charges or purports to assign, mortgage, or charge any
of its obligations or rights in contravention to the provisions of the order; or, transfers or
negates any of its obligations in contravention to the provisions of the order.
viii. AMISP breaches the Secrecy Clause/Confidentiality obligations.
ix. If at any stage during the tenure of the work order, AMISP or its officials or
subcontractors is found to be involved or indulging or even attempting illegal, unlawful
action or activities or some fraudulent or even trying to take or ask bribe from any
customer or to give bribe official/staff or misuse or abuse any meter of BYPL.

30.2 In the event BYPL terminates this Contract, in whole or in part, on the occurrence of any
event of default, BYPL reserves the right to engage any other subcontractor or agency to
complete the work or any part thereof, and the same shall be in addition to any other right
BYPL may have under the contract or in law including without limitation the right to penalize
for delay under clause 8, Section 5 of the contract. AMISP shall be liable to BYPL for any
additional costs/expenses/charges that may be incurred by Purchaser for the execution of
the Work. Further on receipt of notice of termination, AMISP shall immediately stop all
activities related to the work terminated, subject to post termination obligations and shall
BSES

hand over BYPL all drawing/documents prepared for this contract up to the date of
cancellation of order.

31. Termination for BYPLS’s Convenience- Stands Deleted

32. Change Order

32.1 Change Notes / Change Order to Alter Number of Meters to be Installed

32.1.1 Necessity of Change Notes arises due to change in the number of meters against the
numbers agreed for the project. Negative variation is permissible only up to the
“Installation Milestone”. Positive variation is however possible at any time during the
Contract Period. The variation allowed cannot be more than the minimum and maximum
numbers.
32.1.2 Change Notes shall be generated and maintained by the AMISP based on a written
communication from the authorised officer(s) of the BYPL. The AMISP shall receive the
AMISP Service Charges for additional meters installed and made operational through the
means of Change Notes.
32.1.3 To establish the revised Total Meter-Months for the project due to additional meters
installed, the BYPL shall convert all such Change Notes to Change Orders any time
before the Total Meter-Months are completed.
32.1.4 In the event a Smart Meter is shifted from one node to another, AMISP shall be entitled to
receive the Monthly AMISP Service Charges for such meters as if such smart meter has
not been shifted. In other words, this will not increase the total number of meters installed
by the AMISP.

Page 59 of 473
32.1.5 In the event a Change Note / Change Order causes an increase or decrease in the time
required for, the AMISP’s performance of any provisions under the Contract, an equitable
adjustment shall be made in the Project Implementation Schedule as provided in Clause
15 of Section 6 and the Contract shall accordingly be amended. Any claims by the AMISP
or the BYPL for adjustment under this Article must be asserted within 28 (twenty-eight)
days from the date of the AMISP’s receipt of the Change Note / Change Order. The
Parties agree that any change in the delivery and Project Implementation Schedule shall
result in a proportional change in the Term of the Contract.
32.1.6 An institutional mechanism will be set up for taking decisions regarding requests for
changes or New Requirements. The BYPL will set up a Change Control Committee with
members from the BYPL and the AMISP. If it is unable to reach an agreement, the
decision of the BYPL will be final.
32.1.7 In the case of additional meters installed through Change Notes maintained by the
AMISP, the BYPL shall convert all such Change Notes to Change Orders any time before
the Total Meter-Months are completed.

32.2 Change Request/Change Order for New/Enhancements to Software Applications

32.2.1 Another form of change may arise when the BYPL discovers the need to have
enhancements in the delivered software applications and/or entirely new functional
requirements in the applications (“New Requirements”), subject to clause 32.2.6 of this
Contract.
32.2.2 At any point in time the BYPL may raise a Change Request to include New Requirements
in the AMI system application. This Change Request shall include the following:
 Identification and documentation of the need for the change
 Functional details of the change
 Information related to initiator, initiation date and
BSES

 Priority of the change

32.2.3 The AMISP will analyse and evaluate the Change Request to come up with the estimate of
the effort involved in terms of man-days required (in respective skill areas) and time
schedule as per agreed priority and document the same. BYPL will use the estimated effort
of the new requirements made by the AMISP and together with the quoted man-month rates
arrive at a cost estimate. For all technical resources, the quoted man-month rate shall be
used. Efforts of support staff shall not be taken into consideration for this purpose.
32.2.4 Based on the agreed cost estimate, the BYPL shall raise a “Change Order”. The AMISP
shall undertake the development of the New Requirements only after securing express
consent of the BYPL. If the consent of BYPL is not received, then the change will not be
carried out. The change will be implemented in accordance to the agreed cost, effort, and
schedule by the AMISP and the change will be verified by the BYPL on completion of
implementation.
32.2.5 If the Change Order for New Requirements agreed to herein causes an increase or
decrease in cost of, or the time required for, firm’s performance of any provisions under the
Agreement, equitable adjustments shall be made in the Agreement Price or Delivery
Schedule, or both, and the Agreement shall accordingly be amended. Any claims by firm for
adjustment under this must be asserted within 30 (thirty) days from the date of AMISP
receiving the change order.
32.2.6 The following categories of Change Requests shall not be treated as “New Requirements”
and the AMISP is expected to deliver these Change Requests as per agreed schedule
without any commercial implications.
• All bug fixes
• All upgrades of the licensed platforms
• Changes made to report templates
• New reports not exceeding [x] numbers

Page 60 of 473
 • Integration with national level systems like NFMS etc.
• Minor changes not requiring more than 10 man-days
• Aspects already covered under existing scope of work provided in this Contract
32.2.7 In the case of New Requirements in Software Applications, BYPL may at any time, by a
written Change Request seek changes to be implemented within the general scope of the
Agreement provided this does not constitute unrelated work and that it is technically
practicable, taking into account both the state of advancement of the Solution and the
technical compatibility of the change envisaged with the nature of the Solution as
specified in the Contract
32.2.8 The Change Request/New Requirement management procedure will follow the following
steps: -
a. Identification and documentation of the need for the Change Request/New
Requirement - The information related to initiator, initiation date and details of
Change Request/New Requirement and priority of the change/New Requirement will
be documented by the BYPL.
b. Analysis and evaluation of the Change Request/New Requirement - Impact of the
change/ new requirement in terms of the estimated effort, changed schedule, cost
and the items impacted will be analyzed and documented by the AMISP.

33. Confidential Information

33.1 The technical information, data and other related documents forming part of order and the
information obtained during the course of investigation under this order/agreement shall
be the Company's (BYPL) exclusive property and shall not be used for any other purpose
except for the execution of the agreement. The technical information drawing, records and
other document shall not be copied, transferred, or divulged and/or disclosed to third party
in full/part, not misused in any form whatsoever except to the extent for the execution of
BSES

this order/contract.
33.2 This technical information, drawing and other related documents shall be returned to
BYPL with all approved copies and duplicates including data/drawing/plans as are
prepared by AMISP during the executions of this contract, if any, immediately after they
have been used for agreed purpose.
33.3 That any information concerning the BYPL which is confidential or designated in writing as
proprietary and confidential, AMISP shall not publish or otherwise disclose it to others.
33.4 AMISP shall, at all times use their best endeavor to keep confidential all information.
Accordingly, AMISP shall not disclose the same to any other person/other entity, provided
that the provisions of this section shall not apply to information which:
a. was furnished prior to the signing of Agreement / issuance of this tender document,
without restriction
b. is or becomes knowledge available within the public domain (other than by breach of the
foregoing obligation of confidentiality)
c. is received by either the BYPL or AMISP from a third party provided that (i) nothing
herein shall limit the right of the BYPL to provide any information regarding AMISP to any
other person, who has executed a confidentiality undertaking with BYPL covering AMISP
confidential information that is substantially similar to the provision of this section or
otherwise with AMISP’s consent; and (ii) AMISP may provide to their employee any
information necessary to carry out the services.
33.5 In the event of any breach of this provision, AMISP shall indemnify BYPL against any loss,
cost or damage or claim by any party in respect of such breach.
33.6 AMISP shall not use the name/logo/emblem of BYPL in any manner either for credit
arrangement or otherwise and it is agreed that BYPL shall not in any way be responsible
for the debts, liabilities or obligations of AMISP and/or his employees.

Page 61 of 473
33.7 AMISP hereby covenant that AMISP shall be responsible for theft/breach of
confidentiality, if any committed, by his staff and AMISP shall indemnify BYPL from and
against all claims, demands, actions, suits and proceedings, whatsoever that may be
brought or made against BYPL by or on behalf of any person, body, authority whatsoever
and whomsoever and all duties, penalties, levies, taxes, losses, damages, costs, charges
and expenses and all other liabilities of whatsoever nature which BYPL may be liable to
pay, incur or sustain by virtue of or as a result of the performance or non- performance or
observance or non- observance by AMISP of any of the terms and conditions of this
agreement. BYPL shall have full power and rights at its discretion to pay or defend or
compromise any suits, claims or demands brought or made, whether pending or
threatened touching upon this agreement as it may consider necessary or desirable and
shall be entitled to recover from AMISP all sums of money including all legal costs,
charges and expenses incurred by virtue of any such compromises which shall not be
called into question by AMISP but shall be final and binding on AMISP.
33.8 AMISP shall execute NDA document on 100 Rupees stamp paper as per Form 30: Non-
Disclosure Agreement.

34. Documentation

34.1 The AMISP’s shall procure all equipment & components of meter and associated
accessories from BYPL approved sources as per attached specifications. The Bidder’s
shall submit 5 copies of Material/Type Test Certificates, O&M Manuals and GTP etc. The
Bidder’s shall ensure for the strict compliance to the specifications and Field Quality
Procedures issued by BYPL Engineer in-charge. All the above documents shall be
submitted both hard & soft copy (preferably in Pen drive or External hard disk).

35. Limitation of Liability BSES

The AMISP's liability (except Third Party Liability; covered under the agreement and
addendums thereto) for all damages, losses, acts or omissions, howsoever occasioned,
shall not, at any time exceed an amount equivalent to Contract Value.

Notwithstanding anything stated in the agreement, the limitation of Liability shall not be
available/applicable in case of willful default/breach/negligent act/misconduct on the part
of AMISP and/or its employees.

36. Acceptance

Acceptance of this order implies and includes acceptance of all terms and conditions
enumerated in this work order/Contract in the technical specification and drawings made
available to AMISP consisting of general conditions, detailed scope of work, complete
scope of work and the AMISPs and BYPL's contractual obligation are strictly limited to the
terms set out in the order/contract. No amendments to the concluded order shall be
binding unless agreed to in writing for such amendment by both the parties. BYPL
reserves the right to instruct to change the Engineer, Supervisor, skilled / unskilled worker
in case the workmanship or speed of work is not satisfactory and such request for change
shall mandatorily be adhered by AMISP in strict adherence of the timelines provided by
BYPL

37. M.S.M.E

37.1 AMISP shall provide to BYPL the proof of classification of its enterprise and filing
memorandum with the authorities concerned under the Micro, Small & Medium
Enterprises Development Act, 2006 (hereinafter referred to as "the Act").

Page 62 of 473
37.2 If AMISP is covered under the purview of the said Act, it shall declare and confirm within
one week of receipt of the Contract of its status, failing which it will be presumed that
AMISP is not` covered under the said Act, AMISP further declares and give undertaking to
intimate the BYPL of any change in its status or constitution under this section from time
to time. AMISP must provide MSME registration number along with PAN card and GST
registration number on Tax Invoice failing which AMISP shall not claim any benefit under
the MSMED Act.

38. Safety Code

38.1 The AMISP shall ensure adequate safety precautions at site as required under the law of
the land to facilitate safe working, during the execution of work under agreement/work
order and shall be entirely responsible for the complete safety of their workman as well as
other workers at site and premises during performance of work under agreement. AMISP
shall not deploy any worker below the age of 18 years.
38.2 AMISP shall observe the safety requirements as laid down in the contract and in case of
sub-contract (only after written approval of BYPL); it shall be the responsibility of main
Bidder/AMISP that all safety requirements are followed by the employees and staff of the
sub-contractor.
38.3 AMISP employing two hundred employees or more, including contract workers, shall have
a safety coordinator in order to ensure the implementation of safety requirements of the
contract and a Bidder with lesser number of employees, including contract workers, shall
nominate one of his employees to act as safety coordinator who shall liaise with the safety
officer on matters relating to safety and his name shall be displayed on the notice board at
a prominent place at the work site.
38.4 AMISP shall be responsible for non-compliance of the safety measures, implications,
injuries, fatalities and compensation arising out of such situations or incidents.
38.5 In case of any accident, AMISP shall immediately submit a statement of the same with
BSES

BYPL and the safety officer, containing the details of the accident, any injury or
causalities, extent of properly damage and remedial action taken to prevent recurrence
and in addition, AMISP shall submit a monthly statement of the accidents to the owner at
the end of each month.

39. Statutory Obligations

39.1 AMISP shall ensure the due compliance all the statutory acts applicable, including but not
limited to the following acts, where special attention of AMISP is required to be drawn
towards the compliance of provision (along with the latest
amendments/additions)including any statutory approval required from the Central/State
Governments, Ministry of Labour.
- The Child Labour (Prohibition and Regulation) Act, 1986.
- The Agreement Labour (Regulation and Abolition) Act, 1970.
- The Employee's Pension Scheme, 1995.
- The Employee's Provident Funds and miscellaneous provisions Act, 1952.
- The Employees State Insurance Act, 1948.
- The Industrial Disputes Act, 1947.
- The Maternity Benefit Act 1961.
- The Minimum Wages Act, 1948.
- The Payment of Bonus Act, 1965.
- The Payment of Gratuity Act, 1972.
- The payment of Wages Act, 1936.
- The Delhi Shops & Establishment Act, 1954.
- The Workmen's Compensation Act. 1923.
- The Company's Liability Act, 1938.

Page 63 of 473
 - THE SEXUAL HARASSMENT OF WOMEN AT WORKPLACE (PREVENTION,
PROHIBITION AND REDRESSAL) ACT, 2013
- The Delhi Preservation of Trees Act 1994
- DERC compensation Rule 2024

39.2 Further AMISP shall be liable to comply with all the amendment in existing acts /
upcoming new comprehensive labour acts/codes related to applicable labour laws.
39.3 AMISP shall, prior to commencement of the jobs under this agreement, furnish with BYPL
the permanent Provident Fund Code numbers and ESI of its employees.
39.4 AMISP shall bear the entire responsibility, liability and risk relating to coverage of its
workforce under different statutory regulations including Workman's Compensation Act,
ESI Act, Factories Act, 1948, the Agreement Labour (Regulation and Abolition) Act 1970,
as amended from time to time, and any other relevant laws/regulations as the case may
be. AMISP shall also be solely responsible for the payment of all benefits such as
Provident Fund, Bonus, Retrenchment Compensation, Leave etc. applicable as per the
various statutory laws/regulations and shall keep the Company indemnified in this regard
against any claim. BYPL shall entitled to deduct from any money due to or to become due
to AMISP any money paid or payable by way of compensation as aforesaid or cost or
expenses in connection with any claims thereto and AMISP shall abide by the decision of
BYPL to the sum payable by AMISP under the provisions of this clause.
39.5 AMISP shall obtain all registration/permissions licenses etc., which are/may be required
under any labor or other legislations for providing the services under this Agreement.
39.6 AMISP shall take insurance policy under the Workmen Compensation Act to cover
workers, not covered under ESI Act 1948, engaged by it and Accident Liability Insurance
for its employees for payment of compensation on account of injury, fatal or otherwise due
to accident during service. Copies of these insurance policies will be submitted to
company for reference and records and these insurance policies shall be kept valid at all
times. BSES

39.7 In case it is desired by any Labour authorities to produce the records with respect to
salary/ PF/ESI/EDIL/Bonus etc, the said record/register will be made available by AMISP.
39.8 AMISP shall also be responsible to take third party Insurance Policy, of adequate sum,
before start of work and to comply the terms an Electrical license issued by Govt. of Delhi.
(In case scope of work includes Installation of equipment’s/meters)
39.9 The AMISP shall comply with all Applicable Laws in the performance of its obligations
under this Contract Agreement, including, without limitation, any and all applicable rules
regulations and guidelines as may be issued by appropriate commission and/ or authority
under the Electricity Act, 2003 (and as may be amended, modified, supplemented,
extended or re-enacted from time to time).

40. Human Resources Issues

40.1 AMISP would execute the works under agreement/contract through its own resources.
40.2 AMISP shall bear all expenses/cost to be incurred towards salary, allowances, perks,
traveling allowances, advances, insurance, safety measures, annual increment, security,
transportation, conveyance reimbursement, telephone expenses, leave pay and all other
misc. expenses etc. of their employees/ workmen during the tenure of contract. Also,
AMISP shall be sole responsible for making payment for Out-patient department,
Hospitalization, Compensation thereof in case of any accident, injury or death.
40.3 AMISP shall issue Identity Cards to their employees deployed for execution of the
assigned works in the Division with the consent of BYPL.
40.4 AMISP to deploy its manpower immediately for carrying out the work as specified under
contract/work order.
40.5 AMISP shall ensure that there are no disputes regarding service, payment etc. of the
persons engaged by it, anytime during the execution of the contract. At no point of time

Page 64 of 473
 during the currency of contract, AMISP's employees shall insist upon BYPL for
employment, wages, and allowances or any other related matter, payment etc.
40.6 AMISP shall not deploy the manpower below the age of 18 years or above the age of 58
years.
40.7 AMISP shall not deploy the female manpower between 7 PM to 6 AM.
40.8 AMISP shall be directly responsible for any / all disputes arising between AMISP and its
persons and shall keep the BYPL indemnified against all losses, damages, costs,
penalties and claims including litigation cost arising thereof. AMISP shall resolve all
dispute of its manpower. All the legal dues of the manpower of AMISP is to be paid on
due date or within 8 days on the termination of manpower.
40.9 All safety wears required for AMISP's manpower during the execution of work such as
safety shoes, safety helmets, hand gloves, safety belt, goggles etc. must be provided by
AMISP at his own cost and AMISP shall ensure that its employees regularly use all such
safety gears, as applicable depending upon the task, while performing the task under
contract.
40.10 AMISP shall be responsible for discipline of its manpower and shall ensure that the
personnel deputed should adhere to the disciplinary procedure set by the BYPL. AMISP
will ensure that none of the manpower engaged by it will demonstrate before the offices of
BYPL in any manner whatsoever. In case any of the manpower engaged by AMISP is
found indulging in such activities, the same shall be termed as breach of the terms of
contract and annexures thereto and AMISP will take suitable action against such of its
employees and submit the ATR with BYPL. BYPL shall be at liberty to object to the
presence of any representative or employees of AMISP at the site, if in the opinion of the
BYPL such manpower has done any act of misconduct or negligence or otherwise
undesirable, then AMISP shall remove such a person objected to and provide a
competent replacement immediately. BYPL reserve the right to take action as defined in
code of conduct.
40.11 AMISP shall ensure that it has complied with the following:
BSES

40.11.1 Timely payment of wages (not less than minimum wages) to its manpower as per the
rate notified from time to time by the Government of National Capital Territory of Delhi.
40.11.2 Bidder shall disburse the salary of his staff through ECS only.
40.11.3 Compliance with all other relevant PF, ESI and Insurance laws as applicable per statute.
40.11.4 To retain Challans/Receipt issued by Statutory Authorities like Regional Provident Fund
Commissioner (RPFC)/including its own Pension Provident Fund Trust for previous
month & proof of payment towards compliance of other statutory provisions like
E.S.I.,GST etc
40.11.5 AMISP will also produce challan/receipt with respect to payment of GST as a proof for
such statutory payment before the same is released by BYPL.
40.12 BYPL reserves the right to demand the AMISP's services on holidays as well as beyond
the normal working hours. No extra payment shall be paid by BYPL in lieu of such
services on holidays.
40.13 AMISP shall ensure that none of its associate/personnel is engaged in any unlawful
activities or any other activity subversive of BYPL's interest, failing which the same shall
be termed as breach of the terms of contract and annexures thereto and suitable action
may be taken against AMISP as per the terms & conditions of the contract..
40.14 AMISP shall be liable for payment of all taxes and duties as applicable, to the State/
Central Govt. or any local authority.
40.15 AMISP's employees shall not be treated as BYPL employees / persons for any purpose
whatsoever & facilities/ benefits applicable to the BYPL employees shall not be applicable
to AMISP's employees. If due to any reasons whatsoever the BYPL is made liable to meet
any obligation under any of the laws & enactment etc., for any reason whatsoever the
same shall be recovered from AMISP or from any of the bills payable to him or failing
which it shall be recovered as per law.

Page 65 of 473
40.16 AMISP shall comply with provisions of the Payment of Wages Act 1936, Minimum wages
Act-1948, Employee’s Provident Fund & Miscellaneous Provision Act 1952, ESI Act 1948,
Company's Liability Act 1936, Industrial Dispute Act 1947, Maternity Benefit Act 1961,
Contract Labour (Regulations & abolition) Act 1970, Delhi Shops & Establishment Act or
any modification thereof, THE SEXUAL HARASSMENT OF WOMEN AT WORKPLACE
(PREVENTION, PROHIBITION AND REDRESSAL) ACT, 2013 or any other Act relating
to rules made hereunder from time to time. For the said purpose AMISP shall get itself
covered under the Employee's Provident Fund & Miscellaneous provision Fund 1952 &
ESI directly with the appropriate Regional Provident Fund Commissioner, if not done so
far and shall intimate to the Company the Code No. allotted by the RPFC & ESI
Authorities within one month from the date of commencement of the work under contract

41. Workman Compensation

41.1 Before Commencement of Work, AMISP shall take insurance policy of adequate sum
under the Workman Compensation Act to cover such workers who are not covered under
ESI and PF and are engaged to undertake the jobs covered under this order/contract and
a copy of this insurance policy will be given to BYPL for reference and records. The said
insurance policy shall be kept valid at all times. In case there are no worker involve other
than those who are covered under ESI and PF by the Bidder, the Bidder shall certify for
the same in writing to BYPL.
41.2 AMISP shall keep the BYPL indemnified at all times, against all claims of compensation
under the provision of Workmen Compensation Act 1923 and as amended from time to
time or any compensation payable under any other law for the time being workman
engaged by AMISP/sub-contractor/sub-agent in carrying out the job involved under this
work order and against costs and expenses, if any, incurred by the BYPL in connection
therewith and without prejudice to make any recovery.
41.3 BYPL shall be entitled to deduct from any money due to or to become due to AMISP,
BSES

moneys paid or payable by way of compensation as aforesaid or cost or expenses in

connection with any claims thereto and AMISP shall abide by the decision of the BYPL as
to the sum payable by AMISP under the provisions of this clause.

42. Group Personal Accidental Insurance policy

Before commencing the execution of the work AMISP shall take Group Personal
Accidental Insurance Policy for the staff engaged/deployed by it for this work under
contract to insure against any loss of life / disablement, which may occur during the
contract for the work of the BYPL. The policy shall have GPA coverage of Rs.15 Lakh
(Table C- Death cover + Permanent Total Disability + Permanent Partial Disability).
Permanent Total Disability coverage shall be 125% of basic sum insured of Rs.15 Lakh.
AMISP shall be responsible for on the spot same day claim settlement with the victim's
legal heirs without waiting for settlement by insurance claim without any liability on BYPL.
The premium amount for such life cover policy shall be borne by AMISP. AMISP shall
furnish copy of policy as and when demanded by BYPL.

43. Staff and Workman

It shall be responsibility of AMISP-

43.1 To obtain Contract Labour License from the concerned authorities and maintain proper
liaison with them. Necessary Forms for obtaining Labour License would be issued by
BYPL, if applicable. However, AMISP will bear all expenses for obtaining Labour license
and registration in PF Department for scope of work under this contract. AMISP will
deposit PF of staff/labour each month and all related documents should be furnished to
BYPL.

Page 66 of 473
43.2 To obtain workman insurance cover against deployment of workers etc.
43.3 To maintain, proper records relating to workmen employed, in the form of various
Registers, namely,
1. Register of workmen.
2. Register of muster roll.
3. Register of overtime.
4. Register of wages.
5. Any other register as per latest amendment Labour Act.
43.4 The records shall be in the mutually agreed formats only,if not prescribed statutorily.
43.5 To disburse monthly wages to the workers/ supervisors in time as per the mandate under
law. To maintain proper liaison with the Project authorities, local police and all other
government and local bodies.
43.6 To pay the workmen at least not less than the minimum prescribed wages as per
state/Central Labour laws as may be, applicable. AMISP shall, be responsible for
compliance of all the provisions of minimum Wages Act, PF, ESIC Act Workmen
Compensation Act and Contract Labour Regulation & Abolition Act, THE SEXUAL
HARASSMENT OF WOMEN AT WORKPLACE (PREVENTION, PROHIBITION AND
REDRESSAL) ACT, 2013 the rules made there under. In case of non- compliance of the
statutory requirements, BYPL would take necessary action at the risk and cost of AMISP.
43.7 To employ required number of skilled/semi-skilled and unskilled workmen as per site
requirement to complete the entire project as per schedule. To provide safety shoes,
safety helmets, safety belts, gloves etc. to the worker/staff as per requirement during
erection work.
43.8 To employ necessary engineering and supervisory staff for completion of the Project in
time. While day-to-day management of the site and supervision of the works shall be the
responsibility of AMISP Engineer - In charge, he will report to BYPL Engineer in charge to
assist him to discharge the overall responsibility of the execution of the project.
BSES

44. Third Party Insurance

Before commencing the execution of the work AMISP shall take third party insurance
policy of an adequate value, at his own cost and expenses to insure against any damage
or loss or injury which may occur to any property / public property or to any person or any
employee or representative of any outside Agency/ the BYPL engaged or not engaged for
the work of the BYPL, by or arising out of the execution of the work or temporary work or
in carrying out of this Agreement. For third party insurance policies, AMISP shall be
responsible for settlement of claims with the underwriters without any liability on BYPL
and will arrange replacements / rectification expeditiously without awaiting settlement by
insurance claim at AMISP’s own cost and consequences.

45. Security

Adequate number of trained Security Guards shall be deployed at the Site stores to
prevent theft and pilferage of material and accessories. All security rules and safety rules
enforced at site by BYPL shall be strictly observed.

46. Environmental, Health & Safety Plan

AMISP will ensure that the Environment, Health & Safety (EHS) requirements are clearly
understood and faithfully implemented at all levels at site as per instruction of BYPL.
Bidders must comply with these requirements:
i. Comply with all of the elements of the EHS Plan and any regulations applicable to the
work

Page 67 of 473
 ii. Comply with the procedures provided in the interests of Environment, Health and
Safety
iii. Ensure that all of their employees designated to work are properly trained and
competent
iv. Ensure that all network and equipment they bring on to site has been inspected and
serviced in accordance with legal requirement and manufacturer’s or BYPL’
instructions
v. Make arrangements to ensure that all employees designated to work on or visit the
site present themselves for site induction prior to commencement of work Provide
details of any hazardous substances to be brought onsite
vi. Ensure that a responsible person accompanies any of their visitors to site

All personnel deputed by AMISP under agreement shall be’ staff is accountable for the
following:
a. Use the correct tools and equipment for the job and use safety equipment and
protective clothing supplied, e.g. helmets, goggles, ear protection, etc. as instructed
b. Keep tools in good condition
c. Report to the Supervisor any unsafe or unhealthy condition or any defects in plant
or equipment
d. Develop a concern for safety for themselves and for others
e. Prohibit horseplay
f. Not to operate any item of network unless they have been specifically trained and
are authorized to do so. Before commencement of work, bidder shall ensure to take
prior shut down approval from BYPL.

47. Risk & Cost

If the Bidder fails to execute the work as per specification / as per the direction of
BSES

Engineer In-change within the scheduled period or even after the extended period, the
contract shall get cancelled and Purchaser reserves the right to get the work executed
from any other source/vendor at the Risk & Cost of AMISP. The Extra Expenditure so
incurred shall be debited to AMISP and BYPL shall be entitled to recover the same from
AMISP by way of encashment of BG, retention/setoff of outstanding sum due to AMISP
and/or recovery through other medium.

48. Cleanliness & Precautions Instructions

AMISP has to take precaution while doing work at site to ensure cleanliness and prevent
dust pollution:

48.1 All debris shall be removed and disposed of at assigned areas on daily basis. Surplus
excavated earth shall be disposed of in an approved manner. In short, AMISP shall be
fully responsible for keeping the work site clean at all times. In case of non- compliance,
Purchaser shall get the same done at AMISP’s risk and costs.

48.2 While carrying out any civil work including road/ pit digging, plinth/ fence making, road
restoration etc. AMISP shall adhere to below mentioned guidelines.
i. No construction material/ debris shall be stored on metalled road.
ii. Wind breakers of appropriate height on all sides of ear marked area using CGI
sheets shall be raised to ensure that no construction material dust fly outside ear
marked area.
iii. The construction material i.e. coarse sand, stone aggregates, excavated earth,
cement and any other material to and from the site shall be transported under wet

Page 68 of 473
 and covered condition to ensure their non-slippage en-route to avoid air
contamination.
iv. AMISP shall provide mask and helmet to every worker working on the construction
site and involved in loading/unloading and carriage of construction material and
construction debris to prevent inhalation of dust particles.
v. Over loading of vehicles shall be strictly prohibited
vi. The construction material at site shall be stored under wet and covered condition.
vii. The dumping sites for temporarily storing the excavated earth shall be properly
leveled, watered and rehabilitated by plantation to avoid flying of dust.
viii. The worker at the site shall be sensitized to adopt / observe the dust controlled
measures in true spirit.
ix. If any C&D waste is generated at site the same will be transported to the C&D
waste site only and the record for the same will be maintained by the agency.
x. Wet jet in grinding and stone cutting is being permitted at site.
xi. The necessary record for dust control is being maintained by the department on day
to day basis and being monitored regularly.
xii. AMISP shall ensure that no tree shall be harmed and no tree roots shall be
destroyed/cut while performing the task under contract.
xiii. AMISP shall comply with the provisions of The Delhi Preservation of Trees Act
1994.

48.3 AMISP shall be responsible for all the preventive and protective environmental steps as
per guidelines. Any violations from the above guidelines have been viewed very seriously
by the authorities. AMISP shall be liable for the penalties / other action by the authorities,
AMISP shall indemnify BYPL/its employees/officers/directors from all liabilities on this
account.

49. Guidelines regarding inspection & maintenance of PITS/DUGS while doing

BSES

work at site in BYPL Area

49.1 The contractor shall ensure strict compliance of the following directions:
i. The sites of all manholes, pits, holes, tanks or any other opening in the ground of
any kinds shall be regularly inspected and maintained.
ii. Schedule and protocols of inspections and maintenance shall be drawn up and
notified to BYPL.
iii. These sites shall be cordoned off to render them inaccessible to the public.
iv. The existence of these sites shall be clearly & visibly marked by the display of
signboards/ signages.
v. If they are required to be covered, it shall be ensured that the covers are in place.
vi. If required, as per law, prior permission from authorities shall be secured before the
commencement of work.
vii. AMISP shall follow all law of the land and prevailing borders issued by various Govt
departments like Dept of Power / DERC /NGT/ Dept of forest /Dept of
environment/DPCB/Court Orders etc.

AMISP shall be responsible for all the preventive and protective environmental steps as
per guidelines. Any violations from the above guidelines have been viewed very seriously
by the authorities. AMISP shall be liable for the penalties / other action by the authorities,
AMISP shall indemnify BYPL/its employees/officers/directors from all liabilities on this
account

Page 69 of 473
Section 4: Vendor Code of Conduct
1. Vendor Code of Conduct

Purchaser is committed to conducting its business in an ethical, legal and socially responsible
manner. To encourage compliance with all legal requirements and ethical business practices,
Purchaser has established this Vendor Code of Conduct (the "Code") for Purchaser’s Vendors.
For the purposes of this document, "Vendor" means any company, corporation or other entity
that sells, or seeks to sell goods or services, to Purchaser, including the Vendor's employees,
agents and other representatives. Fundamental to adopting the Code is the understanding that
a business, in all of its activities, must operate in full compliance with the laws, rules and
regulations of the countries in which it operates. This Code encourages Vendors to go beyond
legal compliance, drawing upon internationally recognized standards, in order to advance social
and environmental responsibility.

2. Labor and Human Rights

Vendors must uphold the human rights of workers, and treat them with dignity and respect as
understood by the international community.
1. Fair Treatment - Vendors must be committed to a workplace free of harassment. Vendors
shall not threaten workers with or subject them to harsh or inhumane treatment, including
sexual harassment, sexual abuse, corporal punishment, mental coercion, physical
coercion, verbal abuse or unreasonable restrictions on entering or exiting company
provided facilities.
2. Antidiscrimination - Vendors shall not discriminate against any worker based on race,
colour, age, gender, sexual orientation, ethnicity, disability, religion, political affiliation,
union membership, national origin, or marital status in hiring and employment practices
BSES

such as applications for employment, promotions, rewards, access to training, job

assignments, wages, benefits, discipline, and termination. Vendors shall not require a
pregnancy test or discriminate against pregnant workers except where required by
applicable laws or regulations or prudent for workplace safety. In addition, Vendors shall
not require workers or potential workers to undergo medical tests that could be used in a
discriminatory way except where required by applicable law or regulation or prudent for
workplace safety.
3. Freely Chosen Employment - Forced, bonded or indentured labour or involuntary prison
labour is not to be used. All work will be voluntary, and workers should be free to leave
upon reasonable notice. Workers shall not be required to hand over government-issued
identification, passports or work permits as a condition of employment.
4. Prevention of Under Age Labour - Child labour is strictly prohibited. Vendors shall not
employ children. The minimum age for employment or work shall be 15 years of age, the
minimum age for employment in that country, or the age for completing compulsory
education in that country, whichever is higher. This Code does not prohibit participation in
legitimate workplace apprenticeship programs that are consistent with Article 6 of ILO
Minimum Age Convention No. 138 or light work consistent with Article 7 of ILO Minimum
Age Convention No. 138.
5. Juvenile Labour - Vendors may employ juveniles who are older than the applicable legal
minimum age for employment but are younger than 18 years of age, provided they do not
perform work likely to jeopardize their health, safety, or morals, consistent with ILO
Minimum Age Convention No. 138.
6. Minimum Wages - Compensation paid to workers shall comply with all applicable wage
laws, including those relating to minimum wages, overtime hours and legally mandated
benefits. Any disciplinary wage deductions are to conform to local law. The basis on which
workers are being paid is to be clearly conveyed to them in a timely manner.

Page 70 of 473
 7. Working Hours - Studies of good manufacturing practices clearly link worker strain to
reduced productivity, increased turnover and increased injury and illness. Work weeks are
not to exceed the maximum set by local law. Further, a work week should not be more
than 60 hours per week, including overtime, except in emergency or unusual situations.
Workers should be allowed at least one day off per seven-day week.
8. Freedom of Association - Open communication and direct engagement between
workers and management are the most effective ways to resolve workplace and
compensation issues. Vendors are to respect the rights of workers to associate freely and
to communicate openly with management regarding working conditions without fear of
reprisal, intimidation or harassment. Workers’ rights to join Labour unions, seek
representation and or join worker’s councils in accordance with local laws should be
acknowledged.

3. Health and Safety

Vendors must recognize that in addition to minimizing the incidence of work-related injury and
illness, a safe and healthy work environment enhances the quality of products and services,
consistency of production and worker retention and morale. Vendors must also recognize that
ongoing worker input and education is essential to identifying and solving health and safety
issues in the workplace.

The health and safety standards are:

1. Occupational Injury and Illness - Procedures and systems are to be in place to prevent,
manage, track and report occupational injury and illness, including provisions to: a)
encourage worker reporting; b) classify and record injury and illness cases; c) provide
necessary medical treatment; d) investigate cases and implement corrective actions to
eliminate their causes; and e) facilitate return of workers to work.
2. Emergency Preparedness - Emergency situations and events are to be identified and
BSES

assessed, and their impact minimized by implementing emergency plans and response
procedures, including: emergency reporting, employee notification and evacuation
procedures, worker training and drills, appropriate fire detection and suppression equipment,
adequate exit facilities and recovery plans.
3. Occupational Safety - Worker exposure to potential safety hazards (e.g., electrical and
other energy sources, fire, vehicles, and fall hazards) are to be controlled through proper
design, engineering and administrative controls, preventative maintenance and safe work
procedures (including lockout/tagout), and ongoing safety training. Where hazards cannot be
adequately controlled by these means, workers are to be provided with appropriate, well-
maintained, personal protective equipment. Workers shall not be disciplined for raising safety
concerns.
4. Machine Safeguarding - Production and other machinery is to be evaluated for safety
hazards. Physical guards, interlocks and barriers are to be provided and properly maintained
where machinery presents an injury hazard to workers.
5. Industrial Hygiene - Worker exposure to chemical, biological and physical agents is to be
identified, evaluated, and controlled. Engineering or administrative controls must be used to
control overexposures. When hazards cannot be adequately controlled by such means,
worker health is to be protected by appropriate personal protective equipment programs.
6. Sanitation, Food, and Housing - Workers are to be provided with ready access to clean
toilet facilities, potable water and sanitary food preparation, storage, and eating facilities.
Worker dormitories provided by the Participant or a labour agent are to be maintained clean
and safe, and provided with appropriate emergency egress, hot water for bathing and
showering, and adequate heat and ventilation and reasonable personal space along with
reasonable entry and exit privileges.

Page 71 of 473
 7. Physically Demanding Work - Worker exposure to the hazards of physically demanding
tasks, including manual material handling and heavy or repetitive lifting, prolonged standing
and highly repetitive or forceful assembly tasks is to be identified, evaluated and controlled.

4. Environmental

Vendors should recognize that environmental responsibility is integral to producing world class
products. In manufacturing operations, adverse effects on the environment and natural
resources are to be minimized while safeguarding the health and safety of the public.

The environmental standards are:

1. Product Content Restrictions - Vendors are to adhere to applicable laws and
regulations regarding prohibition or restriction of specific substances including labeling
laws and regulations for recycling and disposal. In addition, Vendors are to adhere to all
environmental requirements specified by Purchaser.
2. Chemical and Hazardous Materials -Chemical and other materials posing a hazard if
released to the environment are to be identified and managed to ensure their safe
handling, movement, storage, recycling or reuse and disposal.
3. Air Emissions - Air emissions of volatile organic chemicals, aerosols, corrosives,
particulates, ozone depleting chemicals and combustion by-products generated from
operations are to be characterized, monitored, controlled and treated as required prior to
discharge.
4. Pollution Prevention and Resource Reduction -Waste of all types, including water and
energy, are to be reduced or eliminated at the source or by practices such as modifying
production, maintenance and facility processes, materials substitution, conservation,
recycling and re-using materials.
5. Wastewater and Solid Waste - Wastewater and solid waste generated from operations,
industrial processes and sanitation facilities are to be monitored, controlled and treated as
BSES

required prior to discharge or disposal.

6. Environmental Permits and Reporting - All required environmental permits (e.g.
discharge monitoring) and registrations are to be obtained, maintained and kept current
and their operational and reporting requirements are to be followed.

5. Ethics

Vendors must be committed to the highest standards of ethical conduct when dealing with
workers, Vendors, and customers.
1. Corruption, Extortion, or Embezzlement - Corruption, extortion, and embezzlement, in
any form, are strictly prohibited. Vendors shall not engage in corruption, extortion or
embezzlement in any form and violations of this provision may result in immediate
termination as an Vendor and in legal action.
2. Disclosure of Information - Vendors must disclose information regarding its business
activities, structure, financial situation, and performance in accordance with applicable
laws and regulations and prevailing industry practices.
3. No Improper Advantage - Vendors shall not offer or accept bribes or other means of
obtaining undue or improper advantage.
4. Fair Business, Advertising, and Competition - Vendors must uphold fair business
standards in advertising, sales, and competition.
5. Business Integrity - The highest standards of integrity are to be expected in all business
interactions. Participants shall prohibit any and all forms of corruption, extortion and
embezzlement. Monitoring and enforcement procedures shall be implemented to ensure
conformance.

Page 72 of 473
 6. Community Engagement - Vendors are encouraged to engage the community to help
foster social and economic development and to contribute to the sustainability of the
communities in which they operate.
7. Protection of Intellectual Property -Vendors must respect intellectual property rights;
safeguard customer information; and transfer of technology and know-how must be done
in a manner that protects intellectual property rights.

6. Management System

Vendors shall adopt or establish a management system whose scope is related to the content
of this Code. The management system shall be designed to ensure (a) compliance with
applicable laws, regulations and customer requirements related to the Vendors’ operations and
products; (b) conformance with this Code; and (c) identification and mitigation of operational
risks related to this Code. It should also facilitate continual improvement.

The management system should contain the following elements:

1. Company Commitment - Corporate social and environmental responsibility statements
affirming Vendor’s commitment to compliance and continual improvement.
2. Management Accountability and Responsibility - Clearly identified company
representative[s] responsible for ensuring implementation and periodic review of the
status of the management systems.
3. Legal and Customer Requirements - Identification, monitoring and understanding of
applicable laws, regulations and customer requirements.
4. Risk Assessment and Risk Management - Process to identify the environmental, health
and safety and labour practice risks associated with Vendor’s operations. Determination of
the relative significance for each risk and implementation of appropriate procedural and
physical controls to ensure regulatory compliance to control the identified risks.
5. Performance Objectives with Implementation Plan and Measures - Areas to be
BSES

included in a risk assessment for health and safety are warehouse and storage facilities,
plant/facilities support equipment, laboratories and test areas, sanitation facilities
(bathrooms), kitchen/cafeteria and worker housing /dormitories. Written standards,
performance objectives, targets and implementation plans including a periodic
assessment of Vendor’s performance against those objectives.
6. Training - Programs for training managers and workers to implement Vendor’s policies,
procedures and improvement objectives.
7. Communication - Process for communicating clear and accurate information about
Vendor’s performance, practices and expectations to workers, Vendors and customers.
8. Worker Feedback and Participation - Ongoing processes to assess employees’
understanding of and obtain feedback on practices and conditions covered by this Code
and to foster continuous improvement.
9. Audits and Assessments - Periodic self-evaluations to ensure conformity to legal and
regulatory requirements, the content of the Code and customer contractual requirements
related to social and environmental responsibility.
10. Corrective Action Process - Process for timely correction of deficiencies identified by
internal or external assessments, inspections, investigations and reviews.
11. Documentation and Records - Creation of documents and records to ensure regulatory
compliance and conformity to company requirements along with appropriate confidentiality
to protect privacy.
The Code is modeled on and contains language from the Recognized standards such as
International Labour Organization Standards (ILO), Universal Declaration of Human
Rights (UDHR), United Nations Convention against Corruption, and the Ethical Trading
Initiative (ETI) were used as references in preparing this Code and may be useful sources
of additional information.

Page 73 of 473
Section 5: Special Conditions of Contract
1. Rules of Interpretation
Capitalized terms used in this SCC unless defined elsewhere in this SCC shall have the
respective meanings ascribed to them in the GCC.

2. Scope of Work

2.1 All the activities that are to be undertaken by the bidder to realize the contractual deliverables
completeness as per Scope of Work. (Refer Section 6: Project Requirements and Scope of
Work). The bidder shall satisfy himself and undertake fully the technical/commercial
requirements of items to be supplied as listed in the Schedule of Quantities/BOM together with
the tests to be performed /test reports to be furnished before dispatch, arrangement of stage
and final inspections during manufacturing as per terms and conditions of contract, technical
parameters & delivery terms and conditions to be met in order to fully meet BYPL
requirements.
2.2 Completeness: Any supplies and services which might have not been specifically mentioned
in the Contract but are necessary for the scope mentioned or completeness of the works at the
highest possible level, including any royalties, license fees & compensation to be paid, whether
incurred by the bidders or by a third party for the work covered in the scope, regardless of
when incurred, shall be supplied/provided by the bidder without any extra cost and within the
time schedule for efficient, smooth and satisfactory operation and maintenance of the works at
the highest possible level under Indian conditions (but according to international standards for
facility of this type), unless expressly excluded from the scope of supplies and services in this
Contract.
2.3 BYPL have the right, during the performance of the Contract, to change the scope and/or
technical character of the Project and/or of the supplies and services stipulated in the Contract
BSES

by submitting a request in writing to the Bidder. The Bidder shall, within fifteen days of receipt
of such request from the BYPL, provide Purchaser with a reasonably detailed estimate of the
cost of the change outlined in the request, if applicable.
2.4 In the event, BYPL requests a change, the Contract price and time shall be adjusted upwards
or downwards, as the case may be and shall be mutually agreed to. The Bidder shall not be
entitled to any extension of time wherein the delay is on the account of bidder default.
2.5 The Bidder shall not proceed with the changes as requested till adjustment of contract price
and time schedule where so applicable in terms of or otherwise directed by the BYPL.
2.6 The Framework agreement will be executed for 2 Million Smart Meters with committed number
of 4 Lakhs Meters in Phase 1, BYPL will issue Notice to Proceed (NTP) for Phase 2 beyond 4
Lakhs as and when required.

3. Good Receipt (If and as applicable)

3.1 Goods Receipt Note (GRN): Supplier shall maintain the records of received material at
designated stores and submit( whenever required) the same alongwiththe following
documents as listed below:
a. Inspection Report.
b. Copy of Material Dispatch Clearance Certificate (MDCC).
c. Copy of Purchase/work Order.
d. Copy of Original Tax invoice.
e. Lorry Receipt.
f. E-way bill.
g. Packing List.
3.2 AMISP Security personnel shall make an entry in the Inward Register at the gate of the store.

Page 74 of 473
3.3 AMISP Store-in-charge shall carry out physical checking of quantity/packing list of material
with reference to challan and purchase order.
3.4 AMISP Store-in-charge shall give Acknowledgement duly signed and stamped to the Supplier
on the copy of the challan.
3.5 AMISP Store-in-charge shall prepare Goods Received Note (GRN) .
3.6 Material shall be rejected in the following cases and the same shall be intimated to the
supplier.
I. Damaged material
II. Material of bad quality as per visual inspection.
III. Specification mismatching from the order.
3.7 BYPL team shall be visiting and may inspect the available stock of the material/staking and
storage conditions/goods entry register maintain/any other relevant record.

4. Billing Process:

For payment against supplies, vendor shall submit the Invoice along with following
documents duly certified by BYPL Project-in-charge at vendor support cell (VSC):
1. Consignee copy of LR (Wherever applicable)
2. Detailed invoice showing commodity description, quantities, units & total price,
3. Original certificate issued by BYPL confirming acceptance of Milestone.
4. Guarantee Certificate.
5. GRN (Wherever applicable)

For payment against installation, vendor shall submit the following documents duly certified
by Project-in-charge:
1. Bill/ Invoice No.& Date (Duly certified & stamped by competent authority of AMISP)
2. Purchase/Work Order No. with Copy
3. Labour license (Above 20 Labours)
BSES

4. Copy of Electrical License

5. Copy of PF & ESIC Challan for the work execution period
6. Minimum Wages Letter
7. Declaration of GST Letter
8. Employee Payment Sheet
9. ECS Employee Payment Proof
10. Copy of third-party insurance policy
11. Copy of workmen Comp. policy
12. Check List as per Form 28: Check List- Documents.

5. Terms of Payment

i) The payments for different cost heads/components (Except AMISP Charges) shall be
released to the AMISP as tabulated below, within 60 days of receipt of the AMISP Tax
invoice at BYPL office with all the requisite respective documents signed and stamped
by BYPL’s EIC/authorized representative. Each invoice shall have the Tax, etc.
registration document’s photocopy annexed to it.

Part A: Upfront payment for Critical IT Deployment and initial Meter Supply.

S. No. Payment Schedule Milestones

1. 25% of Total Project Cost of 4 Lacs Meters. Supply of 2.4 Lacs Meters.

BYPL has the option to make payment on

Pro-rata basis on supply of each 40 K
Meters.

Page 75 of 473
 S. No. Payment Schedule Milestones
2. 5% of Total Project Cost of 4 Lacs Meters. On Operational Go Live as defined under
clause 16.7.1 of Section 6.

*Note
i. All above payments to be released subject to Acceptance of LoA, Contract signing and
submission of PBG.
ii. Total Project cost for 20 Lac Meters is as calculated under Price Schedule A
iii. NTP*(s) shall be issued to AMISP for area and number of Meters to be replaced.

*NTP _ Notice to proceed

Part B: Applicable for monthly payable under Price Schedule A - To be paid on per Meter
Per Month basis as ‘AMISP Service Charge’

S. No. Deliverable Payment

1. I. Monthly documentation/ records/ test AMISP Service Charge (as per
certificates/ etc. during Post-Operational Table- Bill of Materials and Services
Go-Live Phase for Smart Meters in Form 14: List of
a. Monthly progress report briefing the Material and Services given in
status of installation of meters, meter Section 8: Forms- Technical and
boxes on pro-rata basis, including Financial Proposal) X total number
problems that arise with the installed of meters in operation and
AMI system (if any) as well any maintenance phase at the end of
cyber security related issues and each month Post-Operational Go-
corrective action taken by AMISP for Live
the same;
b. Change Notes
BSES

c. Reports as mentioned in this Plus

Contract which includes but not
limited to the following: Agreed rate for replacement of
i. Service Level Agreement meters X Number of meters replaced
(SLA)performance report; due to vandalism, theft, etc
ii. Energy Audit report;
iii. Other reports as applicable in
accordance with Clause 16 of the
Section 6;
2. II. Quarterly documentation/ records/ test <To be made on every third month of
certificates/etc. during Post- Operational each quarter of the Contract Period
Go-Live Phase as defined by the BYPL>
a. As-Built Drawings; = AMISP Service Charge X total
b. Updated consumer indexing as per number of meters in operation and
the implemented AMI system; maintenance phase at the end of
each month Post-Operational Go-
Live
Plus
Agreed rate for replacement of
meters X Number of meters replaced
due to vandalism, theft, etc
3. III. Annual Documentation/ records/ test/ <To be made on every last month of
certificates/ etc. during post operational each year of the Contract Period as
Go Live Phase defined by the BYPL>
a. Cyber Security Audit = AMISP Service Charge X total
b. Data Privacy Audit Report number of meters in operation and

Page 76 of 473
 S. No. Deliverable Payment
c. Updated Exit Management Plan maintenance phase at the end of
each month Post-Operational Go-
Live
Plus
Agreed rate for replacement of
meters X Number of meters replaced
due to vandalism, theft, etc

Notes:
I. AMISP needs to ensure completion of all works as per project plan before submitting the
invoice. This includes supply of required software/licenses and services as per define scope
of work and acceptance from the concerned officer.
II. In case of delay in project solely due to AMISP, the entire cost and/or time over-run shall be
the responsibility of the AMISP and shall be borne by him only.
III. Power to withhold: Notwithstanding anything contained in the payment schedule mentioned
above, if in the opinion of the BYPL, any work done or supply made or service rendered by
AMISP is deficient in any manner in comparison to the prescribed standards, BYPL shall be
at liberty to withhold a reasonable portion of the payments due to the AMISP(s), till such
work/ supply/ service is made conforming to the prescribed standards. These powers to
withhold payments shall be without prejudice to any other power/ right of the BYPL under
this contract.
IV. AMISP shall obtain completion certificate for each milestone from the BYPL and raise an
invoice against the same.
V. All undisputed payments shall be made by BYPL, within Sixty (60) days after submission of
invoice duly approved by Project in-charge, in favour of the Lead Consortium Member.
VI. The release of payments shall be progressive and performance/ output-based as per the
given Payment Schedule, where the payments shall be made for measured deliverables
BSES

and outputs on acceptance by BYPL.

VII. If any excess payment has been made by BYPL due to difference in quoted price in
proposal and AMISP’ invoice, BYPL may without prejudice to its rights recover such
amounts by other means after notifying the AMISP or deduct such excess payment from
any payment subsequently falling due to the AMISP(s).
VIII. The currency in which payment shall be made to the AMISP under this contract is Indian
Rupees (INR).
IX. No invoice for extra work/change order on account of change order will be submitted by the
Supplier unless the said extra work /change order has been authorized/approved by the
BYPL in writing.
X. BYPL reserves the right, at its sole discretion to waive any penalty being imposed on the
bidder(s) in case the bidder(s) fails to meet milestones / agreed service level due to a valid
reason beyond the control of bidder or upon BYPL’s request. Waiver shall be granted on
merit and only as an exception by BYPL Officials. Any Delay on account of meter supplier
(meter supplier selected though other RFP) not making the systems available and failure to
install the meters would not be attributable to the bidder(s) and would not lead to imposing
penalty on bidder(s), BYPL may waive the penalty in such a scenario.
XI. BYPL reserves the right, at its sole discretion to stagger the implementation of AMI solution.
Any such action will be discussed with bidder(s). Bidder(s) shall be informed of the same in
writing. Penalty related to delivery of meter may be waived by BYPL if cause of such delay
is not in bidder’s control or the delay is due to BYPL request for staggered delivery. Penalty
shall be adjusted in case BYPL approves such waiver. The penalty recovered shall be
adjusted in the subsequent payment and no interest shall be paid on this amount.

At the time of payment of bills, the income tax, if any, shall be deducted at source as per
Government rules and guidelines as may be prevailing at the time of payment. Further, for

Page 77 of 473
 availing the benefit of lower income tax rates supplied from outside India, AMISP shall
provide Income Tax Clearance Certificate (ITCC)/ Tax Residency Certificate from
concerned tax authorities for claiming lower tax deduction, if any.

If some of the expenditures for the Related Services are to be incurred in India, such
expenditures shall be expressed in the Bid and shall at the discretion of BYPL be payable in
INR.

The payment schedule for this project is mentioned in table on the next page.

The AMISP shall note the following:

1. The AMISP shall provide the all relevant documents at the time of invoice submission:
2. All documents to be duly certified by the EIC/representative, and by the End
User/Customer Representative.
3. The payment shall be processed only after receipt of following: -
i. Acceptance of LOA and signing of Contract Agreement.
ii. Submission of Contract Performance Guarantee (CPG).
4. Interest shall not be paid on the bank guarantee submitted by AMISP.

Following are to be considered for understanding

User Acceptance Testing – User Acceptance testing is the phase of software testing
process before final installation of AMI system software at BYPLs and when following
prerequisites are met
 Business Requirements must be available
 Application Code shall be fully developed
 Unit Testing, Integration Testing & System Testing shall be completed
 No Show stoppers, or High or Medium defects in the System Integration Test Phase
BSES

 Regression Testing shall be completed with no major defects

 All the reported defects shall be fixed and tested
 Traceability matrix for all testing shall be completed
 UAT Environment must be ready
 Sign off mail or communication from System Testing Team that the system is ready for
UAT execution
 During the test scenarios definition, for each of the business scenario, an acceptance
criterion is defined. Acceptance criteria include expected behavior of the s/w component
and the expected results (data). Expected results form a part of the Exit Criteria. In
addition to expected result and behaviors, some conditions are also specified in the exit
criteria. They can be:
 Number of bugs to be discovered for a functional module. This depends on size of the
functionality and is an indicator of amount of testing done.
 If any medium or low-priority errors are outstanding - the implementation risk must be
signed off as acceptable by BYPL and AMISP
 All High Priority errors from System Test must be fixed and tested
Installation and configuration: The BYPLs are able to view the basic functionalities of the
AMI system viz. communication establishment with smart meters and data availability in HES
etc.

Installation and commissioning: All AMI systems and related components are successfully
installed, configured, integrated and successfully deployed in Cloud by the AMISP with all
features and functionalities

Page 78 of 473
 Payment shall be released within 60 days after receipt of original invoice (duly approved by
concerned departments of BYPL) at BYPL with receipt acknowledged, signed and stamped
by BYPL authorized representative at designated project location.

6. Payment Security Mechanism

Payment Mechanism

The payment shall be made to the AMISP in Indian Rupees (INR) only.

The payment to the AMISP shall commence only one month after Operational Go-Live as
defined in Section 6: Project Requirements and Scope of Work;

The payments due to the AMISP from the BYPL shall be paid on monthly basis as per the
payment structure specified in SCC.

Except in case of Change Order in accordance with Clause 32 of Section 3: General

Terms and Conditions, the sum total of all payments made to the AMISP shall not exceed
the Contract Price quoted in Section 7: Price Format

The actual payment shall be net of any applicable liquidated damages and/or penalty due to
noncompliance of SLAs by the AMISP.

AMISP will raise and deliver the invoice and the Deliverables mentioned above to the BYPL
for the monthly payments within first 5 (five) working days of every month. AMISP shall also
raise a supplementary invoice for the agreed amount towards software change requests/new
requirements completed in the previous month, in accordance with Clause 32.2 of Section
3: General Terms and Conditions. BYPL will review the AMISP invoice raised by the
BSES

AMISP and the Deliverables including the SLA performance report, in accordance with
Clause 14 of Section 3: General Terms and Conditions, within 5 (five) working days from
the invoice and SLA performance report delivered by the AMISP. BYPL may dispute the
amount payable and shall pay the undisputed amount of the payment due via direct debit
facility (as specified in Clause 7) from the 11th (Eleventh) working day of every month till the
10th(tenth) working day of succeeding month. The disputed amount, (related to actual
number of meters installed, integrated and operationalized, penalty imposed due to non-
compliance of SLAs, and liquidated damages), shall be dealt separately by jointly deciding
among the committee containing the members of AMISP and BYPL. The BYPL shall, as a
condition precedent to the award of the contract to the selected bidder, establish a Direct
Debit Facility for the entire online consumer payments to ensure recovery of the amount due
to be paid to the AMISP including amount due to be paid towards supplementary invoice. In
this regard, the BYPL shall create a separate facility compatible with all online payment
options such as Net Banking, Credit/ Debit Card, Mobile Wallets, UPIs, etc. This facility shall
be configurable for direct debit of 100% (hundred percent) of the monthly payment due to the
AMISP from all recharges and bill payments by Consumers. For the avoidance of doubt, it is
expressly acknowledged that the Direct Debit Facility shall not be restricted to the area
where the AMISP is providing services but for the entire area of supply of the BYPL.

The Direct Debit Facility would include a bucket filling approach whereby all consumer
recharges and bill payments from the 11th (eleventh) working day of every month up to 10th
(tenth) working day of the immediately succeeding month will be routed directly to the
AMISP’s bank account till such time the undisputed amount of the payment due including
amount due towards with supplementary invoice issued by AMISP is recovered in its entirety.
Once the entire undisputed amount of the payment due including amount due towards with
supplementary invoice is recovered, the Direct Debit Facility shall no longer transfer any

Page 79 of 473
 money to the AMISP. In the event the overall monthly amount due to the AMISP (i.e. 100%
of undisputed amount due to be paid including any amount due to be paid towards
supplementary invoice issued by AMISP) as the sum of the consumer payments is not
reached till 10thworking day of the next month, the shortfall/ deficit amount shall be paid along
with the undisputed amount due to be paid including any amount to be paid towards
supplementary invoice issued by AMISP for the immediately succeeding month. An
illustration of the aforementioned Direct Debit Facility is provided in with Clause 7 of Section
5: Special Conditions of Contract.

While establishing the direct debit facility and to ensure adequate funds for timely payment to
the AMISP, the BYPL shall ensure the direct debit facility so created, has an average
monthly inflow of at least 5 (five) times the estimated monthly payment to the AMISP.
Average monthly inflow shall be calculated for the last six calendar months from the date of
letter of award.

In the event the AMISP fails to meet a particular performance criterion as mentioned under
the Service Level Agreement (SLA) specified in Clause 14 of Section 6: Project
Requirements and Scope of Work for cumulatively 3 (three) months in past 6 (six) months,
resulting in the maximum penalty for the particular performance criterion, BYPL may issue an
SLA Default Notice to the AMISP directing it to take steps within 90 days to comply with the
performance criterion specified in the SLA1.

In the event a Smart Meter supplied and installed by the AMISP is damaged for reasons not
attributable to the AMISP such as theft, vandalism, burning, etc. or as a result of Force
Majeure Event, the AMISP shall not be liable for such damage. In such cases, upon receipt
of Notice from the BYPL, the AMISP shall repair or replace the damaged Smart Meters.
AMISP shall be required to replace the Smart Meter no later than 15 days of notification by
the BYPL. Upon replacing the Smart Meter, AMISP shall be entitled to raise a supplementary
BSES

invoice for the amount mutually agreed between AMISP and the BYPL. The Supplementary
Bill shall be paid along with the amount due to be paid towards AMISP Service Charges, for
the immediately succeeding month.

For the avoidance of doubt:

(i) a damaged meter(s) shall be excluded from the total numbers installed and
operational smart meters while conducting the SLA audit of the AMI system in
accordance with clause 14 of Section 3: General Terms and Conditions; and
(ii) in the event, AMISP replaces the Meter within 15 days of request by the BYPL or
BYPL directs to continue operations without replacing the damaged Meter, the
AMISP Service Charge qua such meter(s) shall be paid as if such damaged meter
complies with the SLA prescribed in this AMISP Contract.

1
For example, in the event AMISP fails to meet the norm specified for “Availability of AMI System
per month” for cumulatively 3 (three) months in past 6 (six) months leading to levy of maximum
penalty thereof.

Page 80 of 473
7. Direct Debit Facility

8. Contract Performance Bank Guarantee / Security

I. AMISP shall furnish the CPBG in the prescribed format within 28 days from the date of
BSES

issue of LOA/Work Order for due performance of the provisions of LOA/Work Order .

i. The CPBG shall be of 3% of total contract value inclusive of taxes & duties and shall
be valid till agreement period, plus three (3) months or latest RBI guidelines (if any)
whichever is higher towards claim period, if not otherwise specified in agreement.
This amount shall remain fixed during the currency of the agreement.

II. The CPBG shall be issued from any nationalized / scheduled bank as per company
format.
III. The Company shall reserve the right to invoke the CPBG unconditionally and without
recourse to the Contractor, if there is failure to perform any part of the Agreement for
whatsoever reason. This clause is pertaining to performance of contractual obligations
and the decision of Company shall be final in this regard.
IV. Contract Performance Bank Guarantee established under Clause 6 of section 5 shall
contain a statement that it shall be automatically and unconditionally forfeited without
recourse and payable against the presentation by BYPL of this Performance bank
guarantee, to the relevant bank referred to above, together with a simple statement that
AMISP has failed to comply with any term or condition set forth in the Contract.
V. In the event of any claim or any other outstanding Contractual obligations remaining
unfulfilled, AMISP shall be required to extend the CPBG till the settlement of all claims
and completion of all Contractual obligations at the cost and consequences of AMISP.
VI. In the event, in Company’s sole judgment, the AMISP has fulfilled all its obligations
under this Agreement, The CPBG shall be released, without any interest, after the
expiry of CPBG and its claim period as mentioned above on recommendation of
Engineer In-charge.

Page 81 of 473
 VII. If the CPBG is or becomes invalid for any reason (other than its expiry), AMISP shall
immediately notify BYPL and obtain within five (5) days a replacement CPBG in the
form set out in the Contract/Agreement.
VIII. No later than sixty (60) Business Days before the expiry of the CPBG, AMISP shall,
upon request of the BYPL obtain extension of the validity of such CPBG for the period
stated in such request by the BYPL and provide a copy of such renewed guarantee.
IX. It is AMISP’s responsibility to incur charges / cost to maintain and for extension of
CPBG without claiming reimbursement from the BYPL.

9. Transit Insurance (Wherever applicable)

The AMISP shall take a comprehensive insurance policy for marine cum storage cum
erection (MSE) for all the goods supplied and installed under the contract.

10. Liquidated Damages

Except in case of Force Majeure or where the delay in delivery of the Solution is caused due
to any delay or default of BYPL, if the Installation Milestone is delayed by more than 30
(thirty) months from Contract Commencement Date, the AMISP shall be liable to pay
liquidated damages as per the rates specified below.

BYPL shall without prejudice to all its other remedies under the Contract, deduct from the
amount due to be paid, as liquidated damages, 50% of AMISP Service Charge for each
delayed meter for each completed month of delay for a maximum period of 12 (twelve)
months.

<For example, in case AMISP delays installation of say 100 similar type of meters by say 5.5 months
out of a total meter installation of 1000 meters assuming AMISP Service Charges as Rs.
50/meter/month for such meter. Liquidated Damages would be worked as 5*50*100*50%=
BSES

Rs.12,[Link] Liquidated Damages that can be deducted in case of delay of say 13 months is
limited to 12 months i.e., 12*50*100*50%= Rs. 30,000. Further, Liquidated Damages will be levied as
per the delay of Goods i.e., if 80 meters are implemented after 5 months of delay and rest 20 meters
are implemented after 12 months of delay, then LD would be 5*80*50*50%+12*20*50*50% = Rs.
16,000. In the event more than one type of meter are delayed, the LD would be calculated for each
category of the meter on basis of their respective AMISP Service Charge>

11. Penalty

The penalty shall be levied as defined in Clause 14 of Section 6: Project Requirements

and Scope of Work, in case of default in supply/ services rendered by bidder.

12. Completion Period

Bidder shall ensure completion of work within 30 months of the award of the contract/LOI.
Deployment of systems shall commence within 3 months from date of award of contract /
LOI. The performance of the system shall be evaluated and after successful sign-off future
quantities shall be intimated as per rollout plan for installation and commissioning. Total
Contract period shall be of 120 MONTHS, the indicative phases are as follows:

Meters to be
Phase Targeted Activities Time line
Deployed
Implementation Phase – 30 Months
 AS-IS and System Study
Phase 1(a)  Cloud Deployment ~90,000 ~6 Months
 TSP Engagement

Page 82 of 473
 Meters to be
Phase Targeted Activities Time line
Deployed
 Meter Integration
 Applications Integration
 UAT
 Meter Installation on selected
consumers
 Rollout at High Loss divisions
Phase 1(b) ~3,10,000 ~3 months
 Smart Grid Application
 Full Scale MI Ramp up
Phase 2 ~16,00,000 ~21 months
 New Consumers
Operation Phase – 90 Months
 O&M /FMS
 ATS/AMS
90 Months
 Cloud Hosting
 Data / Network

12.1. Access to Site

BYPL shall, at no additional cost to the AMISP, make available to the AMISP suitable
space (which shall be mutually identified by BYPL and AMISP) within the BYPL Area for
the purpose of undertaking the scope of work, subject to the condition that AMISP shall
be solely responsible for security of the space so provided.

13. Termination of Contract

BSES

13. Termination
(a) AMISP Event of Default

13.1. AMISP Event of Default means and includes any of the following events arising out of
any acts or omission of AMISP, its representative, sub-contracts, employees and
which have not occurred solely as a result of any breach of this Contract by the BYPL
or due to Force Majeure, and where AMISP has failed to remedy these events within
a period of 90 (ninety) days of issuance of a notice by BYPL requiring AMISP to
remedy such event.
a. AMISP has failed to procure and arrange requisite finances for the
implementation of the Project;
b. AMISP abandons the implementation of the Project or repudiates this Contract or
otherwise takes any action, or evidences or conveys an intention not to be bound
by the Contract;
c. AMISP, in the judgment of BYPL has engaged in corrupt, fraudulent, collusive, or
coercive practices, in competing for or in executing the Contract; or
d. AMISP is adjudged bankrupt or insolvent, or if a trustee or receiver is appointed
for AMISP or for the whole or material part of its assets that has a material
bearing on its ability to implement the Project;
e. AMISP has been, or is in the process of being liquidated, dissolved, wound-up,
amalgamated or reconstituted in a manner that in the reasonable opinion of
BYPL would adversely affect AMISP’s ability to implement the Project;
f. A resolution for winding up of AMISP is passed, or any petition for winding up of
AMISP is admitted by a court of competent jurisdiction and a provisional
liquidator or receiver is appointed and such order has not been set aside within
90 (Ninety) days of the date thereof or AMISP is ordered to be wound up by a
court of competent jurisdiction;

Page 83 of 473
 g. In the event AMISP fails to cure the default as indicated in the SLA Default Notice
within the time period specified therein;
h. Failure of AMISP to furnish Performance Security in accordance with the
provisions of this Contract;
i. Failure or inordinate delay by AMISP to provide Solution as per Contract;
j. Any representation or warranty made by the AMISP during the term of the
Contract is found to be false and/or misleading;
k. Failure on account of AMISP to abide by Applicable Laws and regulations;
l. The shareholding of the AMISP ceases to be in accordance with the provisions of
this Contract;
m. In the event equipment installed or proposed to be installed by the AMISP is
found to have any embedded malware/ trojans/ cyber threat;
n. AMISP fails to comply with the local content requirement as specified in the Bid
Submission;
o. AMISP fails to comply with any of its material obligations under this Contract.
p. In the event the Solution supplied do not meet the minimum specifications as per
the Contract, and the same is not replaced/ modified by the AMISP to meet the
requirements within 14 (fourteen) working days of being informed by BYPL, or as
mutually decided between BYPL and AMISP.

(b) BYPL Event of Default

13.2. BYPL Event of Default means any of the following events, unless such event has
occurred as a consequence of the AMISP Event of Default or a Force Majeure event
and where BYPL has failed to remedy these events within a period of 90 (ninety) days
of issuance of a notice by AMISP requiring BYPL to remedy such event:
a. Clause 5.2 should be read as Clause 5 of Section 5 i.e. Terms of Payment ;
b. BYPL is adjudged bankrupt or insolvent, or if a trustee or receiver is appointed for
BSES

BYPL or for the whole or material part of its assets that has a material bearing on
its ability to perform its obligations under this Contract;
c. BYPL has been, or is in the process of being liquidated, dissolved, wound-up,
amalgamated or reconstituted in a manner that in the reasonable opinion of
AMISP would adversely affect BYPL’s ability to perform its obligations under this
Contract;
d. A resolution for winding up of BYPL is passed. The breach by BYPL of its
obligations under this Contract which has an adverse effect on the performance
of AMISP’s obligations under this Contract.

13.3. TERMINATION FOR AMISP EVENT FOR DEFAULT

(c) Termination for AMISP Event for Default

13.3.1. Without prejudice to any other right or remedy which BYPL may have in
respect thereof under this Contract, upon the occurrence of AMISP Event of
Default, BYPL shall be entitled to terminate this Contract in the manner
provided in Clause 13.3.2.
13.3.2. BYPL shall issue a Preliminary Notice to AMISP providing 90 (Ninety) Days, or
such extended period as the BYPL may allow, to cure the underlying Event of
Default. If AMISP fails to cure the underlying Event of Default within such
period allowed, BYPL shall be entitled to terminate this Contract by issuing a
termination notice to AMISP.

13.4. TERMINATION FOR BYPL EVENT FOR DEFAULT

Page 84 of 473
(d) Termination for BYPL Event of Default
13.4.1. Without prejudice to any other right or remedy which AMISP may have in
respect thereof under this Contract, upon the occurrence of a BYPL Event of
Default, AMISP shall be entitled to terminate this Contract in the manner
provided in Clause.
13.4.2. AMISP shall issue a Preliminary Notice to BYPL providing 90 (Ninety) Days, or
such extended period as the AMISP may allow, to cure the underlying Event
of Default. If BYPL fails to cure the underlying Event of Default within such
period allowed, AMISP shall be entitled to terminate this Contract by issuing a
termination notice to BYPL.

13.5. CONSEQUENCES OF TERMINATION

(e) Consequences of Termination

Upon Termination of the Contract, the AMISP shall:
13.5.1. Notwithstanding anything to the contrary contained in this Contract, any
termination of this Contract pursuant to its term shall be without prejudice to
accrued rights of any Party, including its right to claim and recover damages
and other rights and remedies which it may have in law or contract. All
accrued rights and obligations of any of the Parties under this Contract, shall
survive the termination of this Contract to the extent such survival is necessary
for giving effect to such rights and obligations.
13.5.2. Following issuance of the Termination Notice by BYPL or AMISP, BYPL take
possession and control of AMISP’s control room and call centre and the
exclusivity granted to AMISP under Clause 12 of Section 3: General Terms
and Conditions will come to an end.
13.5.3. Upon termination of this Contract by BYPL or AMISP on account of AMISP’s
Event of Default (in accordance with Clause 13.1), or termination of this
BSES

Contract on account of BYPL’s event of default (in accordance with Clause

13.2), AMISP shall be entitled to a termination payment subject to proper
transfer of the installed AMI System, as agreed mutually upon, basis the
following criteria:
a. In case termination of this Contract is on account of AMISP’s event of
default: Termination payment to AMISP after Installation Milestone has
been declared shall be 60% (Sixty percent), of the termination payment
Value as determined in terms of this Contract.
b. In case termination of this Contract is on account of BYPL’s event of
default: Termination payment to AMISP after Installation Milestone has
been declared shall be 100% (hundred percent), of the termination
payment Value as determined in terms of this Contract.
c. In case termination of this Contract is prior to Installation Milestone the
Termination payment shall be equal to:
i. 60%(Sixty percent) , of the value of the assets proposed to be handed
over to the BYPL as certified by an independent valuer in the event
termination is on account of AMISP event of default–and
ii. 100% (hundred percent), of the asset values shall be paid to the
AMISP in the event termination is on account of BYPL event of default
For the avoidance of doubt, it is clarified that in the event lumpsum
payment in terms of Clause 11 of Section 2: Instructions to Bidders
and Bid Data Sheet has been made then such payment shall be reduced
from the amount determined in accordance with this Clause13.5.3.(c)
d. In case termination of the Contract is prior to the Installation Milestone-
The Goods that are complete and ready for shipment within 28 (twenty-
eight) days after the AMISP’s receipt of the Notice of termination shall be

Page 85 of 473
 taken into account while determining value of the assets proposed to be
handed over to the BYPL.
e. In the event of termination prior to Installation Milestone, BYPL may
request the AMISP to complete any part of the Solution. The cost of such
works shall be agreed between the Parties. In the event Parties deem it
appropriate the cost may be determined by the Independent Valuer.

Upon termination of this Contract by BYPL or AMISP on account of

AMISP’s Event of Default (in accordance with Clause 13.1), or termination
of this Contract on account of BYPL’s event of default (in accordance with
Clause 13.2), AMISP shall be entitled to raise a supplementary invoice for
an amount which is equal to the termination payment. The Supplementary
invoice shall be paid separately by the BYPL within 30 (thirty) days from
the date of such invoice, subject to compliance of related terms by
AMISP.

13.5.4. The Termination payment value would be calculated basis the following
mechanism:
a. The present value of the receivables for the AMI system installed shall be
calculated by multiplying the outstanding meter-months of operating the
AMI system with percentage of total meters installed, integrated and
operationalized as on the date of termination, and AMISP Service Charge,
and discounting the same as on date of termination at 10.50% (Ten point
Five percent) (“Present Value”).
b. All amounts due, but not paid by the BYPL, including the aggregated
amount due to be paid including amount due to be paid towards
supplementary invoice, but not paid or recovered from the BYPL, for the
AMI system operations and maintenance as defined in the RFP by the
BSES

AMISP, shall be calculated and factored in to arrive at the net outstanding

receivables of the AMISP (“Outstanding Receivables”);
c. All amounts due, but not paid by the AMISP, including the aggregated
applicable liquidated damages and/(or) penalties due to non-compliance of
SLAs by the AMISP, but not paid or recovered from the AMISP, for the
AMI system operations and maintenance as defined in the RFP by the
AMISP, shall be calculated and factored in to arrive at the net outstanding
payables by the AMISP (“Outstanding Payables”);
d. Termination Payment Value shall be equal to the sum of Net Present
Value and Outstanding Receivables as per Clause 13.5.4.(a) and (b);
reduced by Outstanding Payables as per Clause 13.5.4.(c) and the sum of
insurance proceeds received by the AMISP for the AMI system, (if any).
13.5.5. Upon Termination of the Contract or expiry of the contract period, the AMISP
shall prepare and present a detailed Exit Management Plan within 5 (five)
working days of termination notice receipt to the BYPL (“Exit Management
Plan”) in accordance with Clause 13.6.
13.5.6. The BYPL or its nominated agency will review the Exit Management plan. If
approved, AMISP shall start working on the same immediately. If the plan is
rejected, AMISP shall prepare alternate plan within2 ( two) working days. If the
second plan is also rejected, BYPL will provide a plan for AMISP and it should
be adhered by in totality.
13.5.7. The Exit Management Plan should cover at least the following:
a. Execute all documents that may be necessary to effectively transfer the
ownership and title, including OEM warranties in respect of all equipment;
b. Handover all developed codes, related documentation and other
Configurable Items, if any in his possession;

Page 86 of 473
 c. Handover the list of all IT Assets, passwords at all locations to BYPL.
13.5.8. The AMISP and the Authorized personnel from BYPL will sign a completion
certificate at the end of successful completion (all points tracked to closure) of
the Exit Management Plan.

13.6. Exit Management

(f) Exit Management

13.6.1. Exit Management

In case the Contract with the BYPL ends or is terminated before the expiry date of
Contracts, the Parties shall agree at that time whether, and if so during what period,
the provisions of this Exit Management Plan shall apply. The Parties shall ensure
that their respective associated entities carry out their respective obligations set out
in this Exit Management Plan. The exit management shall be done in such a
manner that operations should continue without any restriction on access/usage of
any kind of functionality. At the end of the Contract period, AMISP shall provide
necessary handholding and transition support to the BYPL or its agency for
maintaining the system post the Contract with the AMISP. This includes (but not
limited to):
a. Conducting detailed walkthrough and demonstrations for the AMI Solution;
b. Handing over of AMI Solution, BYPL’s data and all other relevant documentation
including updated detailed bill of quantities for materials and services provided
under the Contract;
c. Addressing the queries/clarifications of the designated staff / new agency with
respect to the working / performance levels of the infrastructure;
d. Conducting training sessions; BSES

e. Knowledge Transfer;
f. Any other activity, over and above these, as may be deemed necessary to meet
the service levels and requirements specified in the RFP.

13.6.2. Transfer of Assets / AMI Solutions

a. BYPL shall be entitled to serve notice in writing on the AMISP at any time during
the Exit Management Period requiring the AMISP and/or its sub-contractor to
provide the BYPL with a complete and up to date list of the Assets within 30
(thirty) days of such notice. BYPL shall also be entitled to serve notice in writing
on the AMISP at any time prior to the end of the Exit Management Period
requiring the AMISP to transfer to the BYPL or its nominated agencies in
accordance with Clause 13.
b. In case of contract being terminated by BYPL, BYPL reserves the right to ask
AMISP to continue running the project operations for a period of 3 months after
termination orders are issued. In case of contract being terminated by AMISP,
BYPL reserves the right to ask the AMISP to continue running the project
operations for a period of 6 (six) months after termination notice is served by
AMISP. In such case, payments during the Exit Management Period shall be
made in accordance with the Clause 6 of Section 5: Special Conditions of
Contract (as the case may be).
c. Upon service of a notice under this Plan, the following provisions shall apply:
i. All title to the assets including licenses/permission as per the updated
detailed bill of quantities for materials and services provided under the
Contract shall be transferred to BYPL, on or before the last day of the Exit
Management Period.

Page 87 of 473
 ii. Payment to the outgoing AMISP shall be made to the tune of last set of
completed Services / deliverables, subject to SLA requirements.

13.6.3. Cooperation and provision of information

During the Exit Management Period:
a. AMISP will facilitate / allow the BYPL or its nominated agency access to
information reasonably required to define the then current mode of operation
associated with the provision of the services to enable the BYPL to assess the
existing services being delivered;
b. Promptly on reasonable request by the BYPL, the AMISP shall provide access
to and copies of all information held or controlled by them which they have
prepared or maintained in accordance with this Contract relating to any material
aspect of the services (whether provided by the AMISP or sub-contractors
appointed by the AMISP) to the BYPL or its nominated agency. Such
information shall include details pertaining to the list of assets as per updated
detailed bill of quantities for materials and services provided under the Contract,
services rendered and other performance data. AMISP shall permit the BYPL or
its nominated agencies to have reasonable access to its employees and
facilities to understand the methods of delivery of the services employed by the
AMISP and to assist appropriate knowledge transfer; and
c. In the event of Termination prior to Installation Milestone, AMISP and BYPL
shall jointly appoint an Independent Valuer to certify the value of assets, as per
the updated detailed bill of quantities for materials and services provided under
the Contract, proposed to be handed over to the BYPL upon termination. The
cost of Independent Valuer shall be paid by the AMISP.

13.6.4. Confidential information, security and data

AMISP shall promptly on the commencement of the Exit Management Period supply
BSES

to the BYPL or its nominated agency the following:

a. information relating to the list of assets as per the updated detailed bill of
quantities for materials and services provided under the Contract, current
Services rendered and consumer and performance data relating to the
performance of sub-contractors in relation to the Services;
b. documentation relating to the Project’s Intellectual Property Rights;
c. documentation relating to sub-contractors;
d. all current and updated data as is reasonably required for purposes of BYPL or
its nominated agencies transitioning the services in a readily available format;
e. all other information (including but not limited to documents, records and
agreements) relating to the services reasonably necessary to enable BYPL or its
nominated agencies, to carry out due diligence in order to transition the
provision of the Services to BYPL or its nominated agencies, (as the case
maybe).

13.6.5. Transfer of Certain Agreements

On request by the BYPL or its nominated agency, the AMISP shall affect such
assignments, licenses and sub- licenses as BYPL may require in favor of the BYPL
or its nominated agency reasonably necessary for the carrying out of replacement
services. These agreements may include equipment lease, maintenance or service
provision agreement between selected AMISP and third- party lessors, service
providers, and any other agreements related to the Services.

13.6.6. General Obligations of the AMISP during exit management period

a. The AMISP shall provide all such information as may reasonably be necessary
to effect as seamless a handover as practicable in the circumstances to the

Page 88 of 473
 BYPL or its nominated agency and which the AMISP has in its possession or
control at any time during the Exit Management Period.
b. For the purposes of this Schedule, anything in the possession or control of the
AMISP or associated entity, or sub-contractors is deemed to be in the
possession or control of the AMISP.
c. The AMISP shall commit adequate resources to comply with its obligations
under this Exit Management Schedule.

13.6.7. Exit Management Process

The AMISP shall prepare an Exit Management Plan for transfer of operations to the
BYPL or its nominated agency, in the event of termination or expiry of the contract
with the BYPL, without affecting services to stakeholders adversely. AMISP shall
get this process approved by BYPL. The Plan shall include, but not be limited to, the
following-
a. A detailed program of the transfer process including details of the means to be
used to ensure continuing provision of the Services throughout the transfer
process or until the cessation of the Services and of the management structure
to be used during the transfer;
b. Plans for the communication with such of the AMISP’s subcontractors, staff,
suppliers, customers and any related third party as are necessary to avoid any
material detrimental impact on the BYPL’s project operations and AMI Services
to other stakeholders as a result of undertaking the transfer;
c. Plans for provision of contingent support to BYPL or its nominated Agency for a
reasonable period after transfer.
d. The Exit Management Plan including all updates shall be presented by the
AMISP to and approved by the BYPL or its nominated agencies.
e. During the Exit Management Period, the AMISP shall use its best efforts to
deliver the services. BSES

f. Payments during the Exit Management Period shall be made in accordance with
the Clause 6and 13.5Section 5: Special Conditions of Contract (as the case
may be)
g. The Exit Management plan shall be furnished in writing to the BYPL or its
nominated agencies within 90(ninety) days from date of execution this AMISP
contract
h. The AMISP shall re-draft the Exit Management Plan annually thereafter to
ensure that it is kept relevant and up to date. The updated plan shall be
furnished in writing to the BYPL or its nominated agencies within 15 days from
the end of such period.

14. Exit Management

To be read in conjunction with Clause 13.6 of this section.

In case the Contract with the BYPL ends or is terminated before the expiry date of Contracts,
the Parties shall agree at that time whether, and if so during what period, the provisions of this
Exit Management Plan shall apply. The Parties shall ensure that their respective associated
entities carry out their respective obligations set out in this Exit Management Plan. The exit
management shall be done in such a manner that operations should continue without any
restriction on access/usage of any kind of functionality. At the end of the Contract period,
AMISP shall provide necessary handholding and transition support to the BYPL or its agency
for maintaining the system post the Contract with the AMISP. This includes (but not limited to):
i) Conducting detailed walkthrough and demonstrations for the AMI Solution
ii) Handing over of Complete AMI Solution along with Software Licenses (Licenses shall be
Enterprise wide full use, perpetual without any restriction on access/usage of any kind of

Page 89 of 473
 functionality), BYPL’s data and all other relevant documentation including updated
detailed bill of quantities for materials and services provided under the Contract
iii) Addressing the queries/clarifications of the designated staff/ new agency with respect to
the working/ performance levels of the infrastructure
iv) Conducting training sessions
v) Knowledge Transfer
vi) Any other activity, over and above these, as may

15. Transfer of Assets/ AMI Solution

To be read in conjunction with Clause 13.6 of this section.

15.1 BYPL shall be entitled to serve notice in writing on the AMISP at any time during the Exit
Management Period requiring the AMISP and/ or its sub contract or to provide the BYPL with a
complete and up to date list of the Assets within 30 (thirty) days of such notice. BYPL shall also
be entitled to serve notice in writing on the AMISP at any time prior to the end of the Exit
Management Period requiring the AMISP to transfer to the BYPL.
15.2 In case of contract being terminated by BYPL, BYPL reserve the right to ask AMISP to
continue running the project operations for a defined period (as decided by BYPL
management) after termination orders are issued.
15.3 BYPL reserves the right to engage with Meter Manufacturer(s)/ OEM (s)/ Cloud & Telecom
Service provider (s) engaged under this contract for direct operational services to BYPL. The
bidder shall be obliged to facilitate such engagements through suitable mechanism, which will
be mutually decided.

16. Quality Assurance and Inspection

16.1 The bidder shall submit its QAP (Quality Assurance Plan) along with bid containing detailed
BSES

quality assurance plan/test procedure identifying the various stages of manufacture, quality
checks performed at each stage, raw material inspection and the Customer hold points. The
document shall also furnish details of method of checking, inspection and acceptance
standards / values and get the approval of Purchaser before proceeding with manufacturing.
However, Purchaser shall have right to review the inspection reports, quality checks and
results of suppliers in house inspection department which are not Customer hold points and the
supplier shall comply with the remarks made by purchaser or his representative on such
reviews with regards to further testing, rectification or rejection, etc. The successful bidder shall
get approval of QAP from BYPL before commencement of supplies. In case of standard items,
BYPL shall forward the standard QAP which is to be followed by vendor during development
and implementation. Clause 16 of Section 6: Project Requirements and Scope of Work of
this document to be referred for validation plan, factory and site acceptance testing.
16.2 Witness and Hold points are critical steps in development, inspection and testing where the
supplier is obliged to notify the Purchaser in advance so that it may be witnessed by the
Purchaser. Final inspection is a mandatory hold point. The supplier to proceed with the work
past a hold point only after clearance by purchaser or a witness waiver letter from BYPL.
16.3 The waiver of QA activity by Purchaser at any stage of development and implementation does
not relieve the supplier of any obligation to perform in accordance with and meet all the
requirements of the procurement documents and also all the codes & reference documents
mentioned in the procurement document nor shall it preclude subsequent rejection by the
purchaser.
16.4 On completion of manufacturing the items can only be dispatched after receipt of dispatch
instructions issued by the Purchaser.
16.5 All in-house testing and inspection shall be done without any extra cost. The in-house
inspection shall be carried out in presence of BYPL representative or their authorized third-
party inspection agency. Cost of Futile/abortive visit(s) shall be debited from the invoices.

Page 90 of 473
16.6 Purchaser reserves the right to send any material being supplied to any recognized laboratory
for testing, wherever necessary and the cost of testing shall be borne by the Bidder. In case
the material is found not in order with the technical requirement / specification, the charges
along with any other penalty which may be levied is to be borne by the bidder. To avoid any
complaint, the supplier is advised to send his representative to the stores to see that the
material sent for testing is being sealed in the presence of bidder’s representative.

17. Test Certificate and Quality Assurance

The Bidder shall procure all equipment from genuine sources as approved by the Purchaser
specifications. The Bidder shall submit all the test certificates and joint inspection reports
related to major equipment wherever applicable. The Bidder shall ensure for the strict
compliance to the specifications and Field Quality Procedures issued by Purchaser.

18. Commissioning Spares

Commissioning Spares shall be deemed to be included in the quoted prices as per scope of
work defined in Section 6: Project Requirements and Scope of Work.

19. Tools and Test Equipment

The Supplier agrees, at no cost or expense to Purchaser, to provide all tools and test
Equipment along with their accessories and consumables required for the installation,
commissioning, and testing services of Goods and all tools and test Equipment required for
completion of work as per scope. Upon Acceptance of the Goods, Supplier may remove only
such tools and test Equipment that will not be required to keep the Goods running in
conformance with the Technical Specifications and Documentation at no cost to Purchaser.
BSES

20. Training

Supplier shall provide training to Purchaser’s personnel according to a mutually agreed

training program. Such training courses shall be carried out at Purchaser’s facilities / Site.
Such training services shall be provided at no additional cost. The scope and nature of the
training services shall be agreed between the Parties.

Supplier shall also provide study material relating to Goods being supplied.

Supplier shall organize training for Purchaser’s representative for Goods which require
specialized storage and installation.

21. Upgrades and Enhancements

Upgrades shall be in the form of

a. Major Version a hardware or software package which provides substantial operational

and performance improvement over the previous version as well as adds additional
features (whether basic, optional, or otherwise) and services, plus Enhancement/s,
accumulation of minor releases, Maintenance Releases and Patch/es issued since the
previous major release Enhancement” shall mean the modification or improvement
over the previous version that improves the performance, functionality, or capacity of
the Goods.
b. Minor Version contains minor elements of new functionality, enhancements,
performance or features, plus accumulation of maintenance releases and patches
issued since the previous minor release.

Page 91 of 473
 c. Maintenance Release contains fixes to several problems, plus accumulation of patches
issued since the previous maintenance release; may include one or more minor
enhancements to existing functionality, performance or features.
d. Patch a fix to one or more specific problems, defect, and/or enhancements. Upgrades
are identified by a version number A.B.C.D in which

1. “A” is the Major Version number

2. “B” is the Minor Version number
3. “C” is the Maintenance Release number
4. “D” is the Patch number

An Upgrade, which is renamed for any reason whatsoever, will however continue to be
covered hereunder as “Upgrade”. Further, all variants of the Goods that perform
substantially similar functions as the Goods, shall be deemed to be Upgrades.

20.1 The Supplier will make available to Purchaser, at such times as they become generally
available to other customers, all Upgrades and Enhancements for any Goods that
Purchaser has purchased pursuant to the terms of the Agreements. The Supplier shall give
Purchaser no less than three (3) months’ prior written notice of the introduction of any
Enhancement. In addition, on half yearly basis in each year during the Term, as a part of
the technology planning process, the Supplier shall provide Purchaser with a forecast of
future Upgrades and Enhancements then currently being developed by Supplier or any
supplier Affiliate. The Supplier shall at all times take all reasonable measures to ensure
that Upgrades and Enhancements will not introduce or release any Malicious Code or
Disabling Code into any part of the Purchaser network.

20.2 Software and firmware Upgrades and Software and firmware Enhancements shall be
provided and appropriately installed by Supplier
BSES

(i) at no charge, during the Warranty Period; and

(ii) subject to the purchase of the Goods at no additional charge.

With respect to any Software or firmware Upgrade, Enhancement or Combined Release,

Purchaser shall not be responsible for bearing the cost of any additional hardware that
may be required to support the same. Additionally, Purchaser shall not be obligated to pay
any amount for any features contained in any Upgrade.

20.3 In the event that any Upgrade or Enhancement supplied by the Supplier has the effect of
preventing the Purchaser network or any part thereof from satisfying, or performing in
accordance with the Technical Specifications or otherwise adversely affects the
functionality or features of the Purchaser network or any part thereof, the Supplier shall
promptly retrofit or take such other corrective action (including the installation of any
additional Products, at the Supplier’s sole cost and expense) as may be necessary to
assure that the Purchaser network or any such affected part thereof, as modified to include
each such Upgrade or Enhancement, shall satisfy and perform in accordance with the
Technical Specifications, and restore all pre-existing functionality and features, in each
case without any cost or expense to Purchaser. Failing this, the Supplier shall promptly
and at no cost to Purchaser, remove such Upgrade and/or Enhancement from the
Purchaser network, restoring the Purchaser network to its pre-existing state, and refund to
Purchaser all Charges paid for the same. Following such removal, Supplier shall perform
all necessary corrective actions in and upon such Upgrades and/or Enhancements and
shall re-test and re-deploy the same no later than thirty (30) days from the date of initial
introduction into the Purchaser network.

Page 92 of 473
Section 6: Project Requirements and Scope of Work
1. Introduction

1.1 BYPL is a joint venture of Reliance Infrastructure Limited and the Government of National
Capital territory of Delhi. Utilities are among the few technologically advanced electricity
distribution utilities in India and is constantly upgrading infrastructure to cater to the
consumer needs. BYPL have successfully reduced their Aggregate Technical and
Commercial (AT&C) losses from over 63% in 2002, to 6.85% in [Link] utilities,
over the years, have ensured reliable and quality power supply to its 1.9+ million
customers spread over ~160 sq km. The utilities are serving its customers through 14
divisions spread across East & Parts of Central Delhi. BYPL has successfully met peak
demands during summers where peak demand has touched 1882 MW for BYPL with
Delhi’s peak demand reaching ~8,000MW during summer of 2024.

1.2 In year 2004, BYPL Started “Mass Meter Modernization Plan”, in which induction type
meters were replaced with Static meters. Appreciating the power of meter data, BYPL is
electronically downloading meter data of all consumers using Handheld Unit (HHU) since
2006 or reading meter through Automatic Meter Reading (AMR). Meter data is not only
used for bill generation as per Regulatory framework, but data is also analyzed to know
consumption behavior, consumer demand curve, theft detection, loading of assets, etc. All
Extra High Voltage (66, 33 kV) and High Voltage (11 KV) feeder are metered and are AMR
enabled, while work is in progress for 100% AMR on Distribution transformers meters.
Data is used for network optimization and planning, to know asset loading, technical loss
reduction, Preventive maintenance planning, Energy audit, etc.

1.3 BYPL has leveraged SCADA system to manage all Grid Substation operations and all
BSES

assets are mapped on Geographical Information System (GIS). BYPL has strong Energy
Audit system to map energy flow and energy gap in the complete Value chain. BYPL have
developed various applications to enhance operational efficiency, CAPEX and OPEX
reduction, Revenue protection, enhanced customer services. BYPL believes in importance
of technology up-gradation and of late, is working on implementation of smart metering
and Advanced Distribution Management System (ADMS) for its entire customer base.

2. Key drivers for Smart metering program

2.1 In general, meter reading, billing, loss reduction, revenue collection (prepaid mode) are
few major reasons for adopting smart metering system by utilities. However, BYPL have
some additional objectives and has plans to leverage multiple benefits by analyzing the
data by providing smart metering system.
2.2 BYPL is downloading consumer meter data electronically since Year 2006. Further, HT
Feeders are already on AMR and DT meters will shortly be AMR enabled. There are
multiple other drivers for adoption of smart metering program for BYPL, discussed below.

The Ministry of Power on 23rdMay 2022, has notified new timeline for replacement of
existing meters with smart meters with prepayment feature. As per the notification all
consumers (other than agricultural consumers) in areas with communication network, shall
be supplied electricity with Smart Meters working in prepayment mode.
 All Union Territories, all electrical divisions with high AT&C Loss, Industrial and
Commercial consumers, all Government offices at Block level and above, shall be
metered with smart meters, with prepayment mode, by 31st December, 2023:

Page 93 of 473
 Provided that these areas shall also be covered for smart Distribution Transformer (DT)
metering by the Advanced Metering Infrastructure Service Provider ( AMISP), on a
priority basis, by 31st March, 2023.

 All other areas shall be metered with smart meters, with prepayment mode, by 31st
March, 2025:
Provided that in these areas smart Distribution Transformer (DT) metering shall be
completed by 31st December, 2023
 All feeders shall be metered by 31st December, 2022;
 All the feeder meters shall be made communicable under National Feeder Monitoring
System (NFMS) by 31st December, 2022 and shall have Automatic Meter Reading
(AMR) facility or shall be covered under Advanced Metering Infrastructure (AMI).

Further all consumer connections, having current carrying capacity beyond that
specified in relevant IS, may be provided with meters with smart meters having AMR
facility.

The Distribution Transformers (DTs) and High Voltage Distribution System (HVDS)
transformers having a capacity of less than 25 kVA and DTs feeding only agricultural
consumers may be excluded from the above timelines.

2.2.1 In future BYPL may enhance scope of smart metering – smart home, other neighborhood
end points, ADMS.
2.2.2 Various other smart applications to be developed to leverage maximum benefit from smart
metering system and data as follows:

[Link] Business Value Realization

i. T&D Loss reduction BSES

ii. Early Revenue realization

iii. Near real time Theft/ Tamper detection
iv. Improved energy auditing
v. Consumer engagement and enhanced services

[Link] Network Optimization

i. Load balancing
ii. Effective outage management
iii. Reactive energy monitoring and optimization
iv. Asset optimization and early failure detection

[Link] Demand Curve Management

i. Demand response
ii. Demand side management
iii. Load management

[Link] Future of Energy

i. Distributed Energy Management
ii. Energy Transition
iii. Domestic Electric Vehicle
iv. Renewable- PM Surya Ghar Yojana
v. Time of Use
vi. Upcoming Technologies
vii. Integration with neighborhood end points

Page 94 of 473
3. AMI Project Area

The AMI Project shall be implemented in the Project Area comprising contiguous electrical
locations (which will be ring fenced with boundary meters by BYPL as and when required)
where all consumers, DTs, feeders, shall be metered with AMI/AMR communication to
enable complete energy accounting with zero manual intervention and non-contiguous
electrical locations where dispersed metering for certain Industrial, Commercial and
Government consumers shall be done.

List of Integration for the Field Devices and not limiting to:
 Consumer meters
 Network meters like DT meters, grid meters, interface meters etc.
 Substation / FSS automation
 DA devices
 APFC, switching capacitors
 Switchgears, FPI etc.
 Sensors with FRTU, air quality, temperature sensors etc.
 Streetlight meter/ streetlight points
 Electric vehicle
 Distributed generation
 Net meter for solar generation
 Storage devices
 Neighborhood devices

BYPL intend to select and deploy IPv6 based communication network technology solution
that shall meet all the BYPL requirements while providing scalability and certain level of
future proofing. Any bidder making a proposal must demonstrate compliance to the
BSES

applicable IS standards and Government of India directives.

Project area key details include following:

A) Electrical Locations:

a) Meter Details
Type of Meters Unit BYPL
Single phase whole current Meters Nos. 1926539
Three phase whole current Meters Nos. 56864
Total Nos. 1983403

b) Total number of consumers by category

Consumer Type Unit BYPL
Domestic Nos. 1553232
Industrial Nos. 7695
Commercial Nos. 422508
Agriculture/Mushroom Nos. 38
Others Nos. 5332
Total Nos. 1988805

c) Electrical Network Details

Electrical Network Details Unit BYPL

Page 95 of 473
 Electrical Network Details Unit BYPL
EHV Grid Substations Nos. 55
EHV - 66kV, 33kV Feeders Nos. 180
HV - 11kV Feeders Nos. 970
Distribution Transformers Nos. 4028

d) Key Performance Indicators

AT&C Peak Demand Consumer Growth
BYPL
(FY-23-24) (June 2024) (Yearly)
BYPL 6.85% 1882 MW 2.83%

4. Indicative Smart Meter Roll out Plan

BYPL plans implementation of 2 million Smart Meters across the license area in phased
manner. BYPL has prepared a roadmap for implementation of smart meters as per
Government and Regulatory directives. This Smart Metering program is the cornerstone of
advancing BYPL as a Smart BYPL. The performance of the AMI system is dependent on
the seamless integration of the existing system, Distributed Automation capability and
futuristic third party Home Area Network (HAN) along with support and interoperability of
multiple communication technologies. Above functionalities will be the deciding factor for
mass implementation. Project execution plan to referred in Annexure I

BYPL shall partner with vendors during various development and deployment stages such
that there are tangible and intangible gains for all stakeholders. The program shall be
undertaken in 3 phases with staggered deployment.
BSES

Meters to
Phase Targeted Activities be Time line
Deployed
Implementation Phase
 AS-IS and System Study
 Cloud Deployment
 TSP Engagement
Phase 1(a)  Meter Integration ~90,000 ~ 6 Months
 Applications Integration
 UAT
 Meter Installation on selected consumers
 Rollout at High Loss divisions
Phase 1(b) ~3,10,000 ~ 3 months
 Smart Grid Application
 Full Scale MI Ramp up
Phase 2 ~16,00,000 ~21 months
 New Consumers
Operation & Maintenance Phase
 O&M /FMS
 ATS/AMS
90 Months
 Cloud Hosting
 Data / Network

The details of Phase 1 Consumers are as given below;

S No. Description Qty. Area
1 Single phase whole current Smart 383793 Daryaganj, Chandni

Page 96 of 473
 S No. Description Qty. Area
Meter with Box Chowk & Yamuna
2 Three phase whole current Smart 6852 Vihar
Meter with Box LT CT, DT and HT
3 Three phase LT CT Operated 4771 Meter will be spread all
Smart Meter with Box and without over Licensed areas
CT – Consumer Meter
4 Three phase LT CT Operated 39994
Smart Meter with Box and without
CT – DT Meter
5 Three phase CT PT Operated 590
Smart Meter with Box and without
CT – HT Meter

5. Overview of the AMISP Scope of Work

AMISP shall Design, Build, Integrate, Operate and Transfer the Advance Metering
Infrastructure (AMI) Project in Delhi AMI Project Area. All product licenses and field
devices shall be owned by BYPL, the AMISP shall be responsible for implementation and
maintaining the O & M as prescribed under scope of work, the supply of Smart Meters
(Cellular, RF), Gateway /DCU etc. is included in the AMISP Scope. The AMISP shall
implement the project including supply, installation, implementation, provisioning of cloud
and 4G / NBIoT data services, testing, Commissioning and O&M of entire solution and
compliance to SLA to operate as defined in this Contract and thereafter transfer the
Operation of the entire system including all the hardware, software along with its valid
licenses, and any data collected during the Project period to the BYPL at the end of the
Contract Period to facilitate seamless operation of BYPL businesses. BYPL shall make
BSES

payments to the AMISP in accordance with the terms and conditions of this Contract.

5.1 The AMI system should be designed such that all the required hardware, software, and
firmware with upgrades satisfy the AMI system requirements and service level agreements
as specified in this Contract while considering technical obsolescence over the operating
life of the system and suitability for future scale up. AMISP is free to decide upon the best
solution out of all the available options. However, the entire responsibility of fully functional
AMI system shall rest with the AMISP in order to meet the performance levels as given in
the Contract. The AMISP shall ensure that the Solution complies with the Applicable Law,
technical specifications and other provisions of the Contract.

5.2 Brief Scope of Work:

The Framework agreement will be executed for 2 Million Smart Meters with committed
number of 4Lac Meters in Phase 1, BYPL will issue Notice to proceed for Phase 2 beyond
4 Lacs as and when required.

The AMISP shall be responsible for overall execution of AMI project including timely supply
of Meters and approvals from BYPL, Supply of Meters is included in the AMISP Scope.
The Scope of work of AMISP shall also include site survey to ascertain communication
technology feasibility, planning, designing, engineering, supply, storage, installation,
integration, testing, commissioning, demonstration for acceptance, training, maintenance,
SLA compliance, operation and documentation of various AMISP components given
below:

A. Supply, Installation, Integration, Testing and Commissioning of

Page 97 of 473
 a. Smart Prepaid Meters (Supply of Smart Meters, DCU and Gateway is within
the scope) as per Clause 8.1of this section. AMISP shall submit MAF from
more than one qualified smart meter manufacturers as per Form 32 – Format
for Manufacturer Authorization Form (MAF). AMISP shall demonstrate
interoperability &integrate for at least 2 of the submitted make of smart
meters. AMISP to ensure installation and commissioning of approved quantity
of Smart Meter by BYPL for other make (MAF submitted) by AMISP with the
Bid.
b. Unified Head End System (UHES) and deployment on cloud as per Clause
8.4of this section
c. Meter Management System (MDMS) with prepaid functionality as integrated
facility using separate Smart pre-paid billing application (SPBM) module and
deployment on cloud as per Clause 8.5of this section
d. Smart Pre Paid Billing Module (SPBM) and deployment on cloud as per
Clause 8.6 of this section
e. Consumer Portal and Mobile application as per Clause 8.7of this section;
f. Advance data analytics System as per Clause 11 of this section
g. Smart Meter Operation centre along with work Force Management application
tool with suitable backend communication infrastructure hardware and Power
supply as per Clause 8.8of this section
h. AMI System Integration as per Clause 9 of this section
i. All other necessary software along with valid licences relevant to the Project
(as per Clause 8.9 of this section)

B. Communication Infrastructure:
a. RF and / or Cellular Communication Infrastructure to ensure the performance
levels provided in this Contract as per Clause 8.2of this Section.
BSES

C. Cloud and Cyber Security:

a. Cloud services as per Clause 8.9.
b. Deployment of Production, UAT and QA environment during project lifecycle
shall be arranged by AMISP.
c. Cyber Security and Data confidentiality of complete system.

D. Communication Network Survey and Meter Installation:

a. Site Survey for finalization of Communication technology in each area as per
Clause 12.3 of this Section.
b. Installation, Commissioning of Smart Meters with Cellular Communication as
per Clause 12.4 of this Section.

E. Consumer Engagement:
a. Development of a comprehensive consumer engagement plan (as per Clause
8of this Section) related to different stages of implementation (Pre, during and
post installation phases of smart metering) in consultation with BYPL and
implement its part of its activities as per the developed plan. The plan at the
minimum should include consumer engagement activities to be undertaken at
BYPL’s headquarter, division and sub-division level as well as communication
and media plan.
F. Energy Accounting Support and MIS:
a. Generation of automated energy accounting reports (DT level/ Feeder level /
Sub-division level/ Division level/ Circle) in contiguous electrical locations and
other MIS reports as per Clause 11 of this Section

G. Operation, Maintenance and SLA Compliance :

Page 98 of 473
 a. Operation, maintenance, and support services after the successful completion
of the Operational Go-Live of the system as per Clause 13 of this Section;
b. Compliance of SLA (as per Clause 14) and identification of defects and its
resolution.

H. User Training:
a. Training of BYPL personnel, as required for efficient, viable and fully
functional system as per Clause 15 of this Section.

I. Others:
a. Verification of capability and capacity of RF solution deployed on field
b. All other necessary software along with valid licenses relevant to the Project
c. Any other software/hardware/services for the project
d. Validation and Integration with Smart Meter supplied as per BYPL
requirement
e. The bidder is expected to submit detailed implementation methodology,
technical solution and project plan for this project along with the bid including
names and profiles of the resources being deployed. The implementation
methodology should include the enhancement requirements of SAP ISU and
other integrated systems.

J. Software and Firmware Licenses:

a. Bidder shall ensure that all System Software Licenses offered shall be
purchased under the name of purchaser. For this project, the Licenses shall
be Enterprise wide full use, perpetual without any restriction on access/usage
of any kind of functionality during the Guarantee/ maintenance support period,
post completion of contract and handover all Software Licenses (latest
version deployed) to purchaser.
BSES

5.3 General Guidelines and Documentation:

i. Guidelines for testing, inspection, approval of test records and in general,
management of the Quality Assurance / Quality Control program of the AMI project
as given in Clause 16 of this Section shall be generally adhered.
ii. Guidelines for project management as given in Clause 17 shall generally be
adhered.
iii. The AMISP shall be required to submit project documentation describing the system
operations for information/ approval as per Clause 18 to the BYPL.
iv. Unless otherwise stipulated in the RFP or Contract, the scope of work shall include
all such items not specifically mentioned in the Contract but that can be reasonably
inferred from the Contract as being required for comprehensive, successful and
satisfactory implementation of the Solution as if such items were expressly
mentioned in the Contract. The same may be mutually enlisted and agreed upon by
BYPL and AMISP without any additional financial impact to BYPL. ;
v. Wherever references are made in the RFP to codes and standards in accordance
with which the Solution shall be executed, the edition or the revised version of such
codes and standards shall be those specified in the scope of work;
vi. The systems which are at a risk of technical obsolescence over the operating life of
the system should be identified; AMISP shall be responsible to identify such
systems/applications and give prior intimation to BYPL (mutually agreed time). During
this period AMISP shall be responsible to enduser no loss of functionality defined in
the scope. BYPL shall not be responsible for any financial implications due to such
obsolescence. This should include end-of-sale and end-of-support policies governing
the proposed technologies. Forward and backward compatibility need to be

Page 99 of 473
 considered and mitigation option shall be indicated in detail and shall not be limited to
periodic update from OEM/System supplier.

6. Overall System design principle and Architecture

Flexibility

Functional configurability
a. Bidder to ensure that the AMI System should have the capability to design and
develop new business requirements and reports with minimum customization.
b. AMI System should allow use of a robust metadata-driven design for adapting the
user interface and navigation without programming.
c. The AMI System should have a built-in mechanism (like API layer) for ease of
integration with 3rdparty solutions.
d. Design should enable ease of migration with-in and outside Cloud Service Provider
(CSP)
e. Enhanced interoperability.

Core/local division
a. Easy division between core functionalities and local/specific features.
b. The platform architecture should be built keeping in mind multi-tenancy (If required).

Scalability

Infrastructure-Scalability

a. The AMI System should allow the -infrastructure to be scaled up or down to meet the
BSES

varying demands, website traffic, application development or production needs, new

applications, load tests etc.
b. Enable automated provisioning or de-provisioning when load balancer thresholds are
met.

Data Scalability

a. Support scale of input sources both in terms of number of source Systems and
transaction / event volume of each source System.
b. Solution should contain capabilities to scale horizontally without disturbing the base
architecture or requiring System downtime.

Application Scalability

a. The design of the AMI SYSTEM should ensure that new applications can be added
without major impact on overall System.
b. Application design principle should ensure it can be scaled easily for new capacity
augmentation (like increase in number of application user).

Performance Stability

a. The design of the AMI System should consider, various workloads and data access
patterns and have clear logical boundaries to perform storage, compute and
balanced workloads.
b. The scalability design should ensure that the query response time(s) / time(s) for
analysis / transformation does not get negatively impacted with scale.

Page 100 of 473

 c. The Bidder should provide scalability of the proposed technology also keeping in
mind new technologies emerging for catering to future needs.

Modularity

Infrastructural Independency
a. The AMI System architecture should be modular and component-based to allow the
existing components to be used to design new functionality or to interface other
solutions.
b. Bidder to ensure that AMI System, modules should be easily migrated (Whenever
required) to a new infrastructure without impacting other interfacing modules.

Functional Independency
a. Bidders are free to implement the solutions using best optimal solutions available.
b. The solution should be capable of migration on another cloud System in case of Exit
/ Performance and contractual issues.

Agility

Provisioning Agility
a. The Cloud solution of AMI System is expected to possess agility in order to fulfil the
BYPL’s expectations by minimizing the Order to Activation (O2A) cycles for
provisioning of infrastructure, applications etc.
b. The deployment and testing of new applications and infrastructure should be done
through automation and minimal human inputs requirement.
c. Allocation & re-allocation of resources should be done through automation and
simple web-based consoles, APIs etc.
BSES

Functional Agility
a. Shorter cycle time and incremental deployment of architecture services.
b. The solution should get quick response, take least processing time and provide
higher availability of data required for ad-hoc query purpose or for report generation.
c. Fast software upgrades and access to quality and tested software.

Reliability & High Availability

Correctness
a. The AMI System should be enabled for exact point-in-time recovery of files or
directories in the cluster from accidental deletions or corruption due to user or
application error.
b. The solution should also maintain incremental and differential copies.
c. While building AMI System on commodity hardware/appliance, failure handling
should be a design characteristic.

Stability
a. There should be tool(s) that can notify, alert and if possible, predict node, disk or
application failure.
b. Necessary corrective action should be in place for each failure. Failure of node, disk
or any network component should not affect the functionality of the AMI System.
c. Failure tolerance is not restricted only to server and application failure. Failure of
network, hardware, software or nodes are considered failure scenarios in scope.

High Availability

Page 101 of 473

 a. Standard practices of configuring AMI System for high availability should be
implemented. Data should be stored in block storages / data nodes. Configurations
should be done to manage federated clusters of block storages.

High Volume Data Flow

a. The AMI System should enable fast streaming data pipeline development with low
data latency
b. The data flow should incorporate the various aspects of distributed parallel
processing like automated partitioning and distribution, auto scaling and dynamic
work rebalancing

Sustainable solution based on micro service architecture

a. To drive the AMI functionalities in seamless manner, the AMISP should design
infrastructure and application deployment on predefined (by OEM) micro – services
based containerised architecture such that micro – services based capabilities can
be used to flexibly manage various micro- services load through scale – up / down of
containers and policy based traffic control. Accordingly, AMISP should design a
sustainable solution based on micro service based architecture considering but not
limited to following principles:
b. Services should have single responsibility
c. Services should be designed using ‘domain driven design’ policy
d. Services to maintain location transparency and should not directly be exposed to
users
e. Services should be loosely coupled
f. Services should be independently deployable
g. Services should use standardized and widely adopted interface mechanism(s)
h. Services should preferably be stateless
i. It should have minimal amount of database tables and tables shouldn’t be shared
BSES

with other services

j. Services should work as ‘single source of truth’
k. Should have capability to operate in multi tenent / multi instance architecture.

Integration and Openness

a. The solution should have ability to integrate and interoperate with other applications
using open standards and integration methods.
b. In terms of the openness of the technology architecture, applications should be able
to operate on multiple operating Systems and database platforms.

6.1 Overall System Architecture and Design Principle

BYPL intends to deploy Advanced Metering Infrastructure (AMI), on predefined (by OEM)
micro – services based containerised architecture in Project service areas as per the high
level solution architecture (cloud based) depicted in the Figure below. The smart meters
supplied by the meter suppliers shall communicate with the Unified Head End System
(UHES) using Cellular/RF networks module. The communications module shall be of
pluggable-type and shall be capable of servicing Cellular/RF technology compliant with
IPv6 & IPV4. AMI solution comprising the Unified Head End System (UHES), Meter Data
Management System (MDMS) and other applications envisaged to be deployed for this
project shall be hosted on a cloud. AMI applications shall communicate to existing BYPL
application like HES / AMI / Handheld for receiving data from other sources and SAP / Non
SAP (other) systems to fulfil business requirements of BYPL.

Page 102 of 473

 Figure: Architecture Diagram

The above architecture is indicative in nature and recommended by BYPL, the AMISP may
propose alternate architecture by its own, which will be evaluated by BYPL for its merit
over proposed architecture. On approval from BYPL, the AMISP can implement the
alternate architecture. BSES

6.2 Exclusion from Scope of Work: Following shall be excluded from AMISP’s scope of
work
a. Construction of building for AMI SMOC (Smart Meter Operation Centre)
b. Lighting system for AMI SMOC
c. Interior and Integrated Building Management System (IBMS) of building for AMI SMOC
d. Air conditioning and ventilation for AMI SMOC
e. Firefighting system for AMI SMOC
f. A.C. input power and back-up supply for AMI SMOC
g. Service cable including electrical neutral connectivity to the transformer, wherever
applicable
h. Any modifications required in the existing system of the BYPL (Billing, Website, etc.).

7. Responsibilities of the BYPL

The CEO of BYPL or any other person designated by the CEO of BYPL shall act as the
nodal point for the implementation of the Contract and for issuing necessary instructions,
approvals, acceptance certificates of work completed, payments etc. to the AMISP. The
BYPL shall
a) Whenever implementation of any component of the Solution requires that the AMISP
obtain permits, approvals, and import and other licenses from local public authorities, if
so required by the AMISP, make its best effort to assist the AMISP in complying with
such requirements in a timely and expeditious manner;
b) Erection of requisite structure for installation of boundary meters and corresponding ring
fencing (wherever required) of Project Area
c) Review all such documents submitted by AMISP required for completion of Pre-
Operational Go-Live Phase, in accordance with this Section, Approval of the documents

Page 103 of 473

 within 30 (Thirty) working days from the date of submission of such documents or
response to AMISP on deficiencies.
d) Provide on AMISP’s request, particulars/ information / or documentation that may be
required by the AMISP within 30 (thirty) days from date of execution of the Contract to
enable preparation of the Project Implementation plan by the AMISP;
e) Provide existing database of consumer indexing (if available) and physical & IT
infrastructure as available with the BYPL. BYPL shall provide all required data to the
AMISP to identify all the consumers connected on the identified sub-stations, feeder
lines and transformers of the AMISP Project area;
f) Review and approval of AMISP’s Project Implementation Plan;
g) Provide drawings and office space for SMOC building Provide necessary inputs for
developing a comprehensive consumer engagement plan;
h) Provide necessary approvals for shutdowns as required for implementing the AMI
System;
i) Coordinate with AMISP for disposal of replaced old meters
j) Implement consumer engagement plan with support of AMISP. This would include
running media campaign to raise awareness and countering myths around smart
metering prior to installation, providing SOPs for smart meter installation to AMISP,
etc.;
k) Providing support and access to facilities at the sites, including consumer premises;
l) Arrange for necessary shutdowns and work permits;
m) Provide the required integration interface details of the existing billing enterprise and
related information required for Operational Go-Live of the AMI system
n) Provide reasonable support to the AMISP for the Operational Go-Live in terms of the
provisions of this Contract;
o) Participate in periodic review meetings as per the project requirement and shall
support with the required interventions requested;
p) Permit AMISP to perform the project activities during working hours, and also after
BSES

working hours as necessary, to meet the requirements of Project Implementation Plan;

q) Appoint and notify to AMISP of the names and contact details of the BYPL
representative and its dedicated staff for the Project.
r) Certify Installation Milestone in accordance with the provisions of this Contract.
s) Release payments to AMISP as per agreed terms;
t) At its own cost, replace or repair existing equipment (other than AMI systems), such as
poles, cables including consumer service lines, and transformers etc. where necessary
to make the AMI system operational and/ or safe from hazards and maintain in proper
working condition all portions of all facilities that are not included in the AMISP’s scope
of maintenance;
u) Provide all other necessary support as may be required time to time.

8. Supply, Installation, integration, testing and commissioning of:

8.1 Smart Meters

I. The Bidder shall supply Single Phase & Three Phase Whole Current Smart Meters
with postpaid, prepaid and net metering functionality [as per latest relevant Indian
Standards and requirement of BYPL] along with communication module, boxes and
associated accessories as per the specifications mentioned in this document.
II. Supply of LTCT (consumer & DT meter) & HTCT smart meter with 4G/NB IOT
pluggable module.
III. Supply & Integration of Smart Meters with Cellular Communication – The Bidder
shall supply Smart Meters with pluggable Network Interface Card (4G /NB IOT) with
provision for e-SIM as per latest Indian Standards. The bidder shall share protocols
and all necessary technical information with BYPL. The Pluggable NIC module shall
be replaceable.

Page 104 of 473

 IV. Supply & Integration of Smart Meters with RF Mesh Communication – The Bidder
shall supply Smart Meters with pluggable Network Interface Card (RF Mesh
communication module), accessories and gateways for WAN communication.
Further, for RF Mesh solution, detailed scope shall be as per Appendix – I.
V. Bidders proposing both Cellular and RF Mesh solution –The meters of same make
shall be interoperable for both RF Mesh & Cellular communication without any
modification in hardware.
VI. Bidder shall ensure that pin configuration of all future NIC modules shall remain
same to ensure plugin communication (NAN/WAN) NIC module shall fit snugly
inside the same smart meter, so that the same IP class of the meter is maintained.
VII. The Supplied Smart meters, Meter box, accessories and Software shall be
guaranteed for a period of 126 month from the date of supply or 120 months from
date of installation whichever is earlier along with operational/ service support.
VIII. Bidder shall ensure that all System Software Licenses offered shall be purchased
under the name of purchaser. For this project, the Licenses shall be Enterprise wide
full use, perpetual without any restriction on access/usage of any kind of
functionality during the Guarantee/ maintenance support period post completion of
contract and handover all Software Licenses (latest version deployed) to purchaser.
IX. Bidder shall provide Exit plan / Handover along with the bid document. Purchaser
representative along with designated team will review the Exit plan and suggest
modifications if required or acceptance for the same. Bidder will be responsible for
handing over all required documents, software code licenses etc as mutually
agreed.

Detailed Specifications for all type of Smart Meters are given at Appendix(s):
for Smart Meters at Clause 0: Appendixes for Smart Meters of Section 6.
 Appendix 2: Technical Specifications for Whole Current A.C. Single
Phase Smart Energy Meter
BSES

 Appendix 3: Technical Specifications for Whole Current A.C. Three Phase

Smart Energy Meter
 Appendix 4: Technical Specification for LT-CT Smart Meters
 Appendix 5: Technical Specification of DT Smart Meter
 Appendix 6: Technical Specifications of HT Smart Meters

8.2 Communication Infrastructure

The communication infrastructure should be based on combination of RF and 4G / NBIoT

Cellular network. Communication network shall provide reliable medium for two-way
communication between various nodes (Smart Meter, Gateway/Router/Access Point/ DCU
(wherever applicable)) & HES. The engagement of network service provider would be in
the scope of AMISP to meet the project performance level as defined under Service Level
Agreement.

The responsibility to maintain performance SLAs shall be of AMISP, accordingly, the

AMISP shall conduct the Site survey as described under clause 12.3 to ascertain feasibility
of Communication technology in a particular area / sub division. Based on feasibility report,
AMISP shall provision Meter Supply either on RF or Cellular Technology.

The systems including communication technologies, which are at a risk of technical

obsolescence over the next few years and over the operating life of the system shall be
identified, reported and AMISP has to provide mitigation plan for the same. This may also
include end-of-sale and end-of-support policies governing the proposed technologies. The
compatibility between the various elements of the system need to be considered and

Page 105 of 473

 mitigation options, not be limited to periodic update from OEM/system supplier/AMISP,
shall be indicated in detail.

8.2.1 Provisions of Cellular Network Services

a. The network links (Meter to Head End System through Cellular (4G / NBIoT technology
compliant with IPv6) will be provided by AMISP. BIDDER shall manage and monitor the
network links and the AMISP shall perform all activities or services, necessary to
implement and execute the Project and provide authorization for Bidder to monitor the
network links.
b. The AMISP shall not use the establishments, equipment and services installed under
this Agreement for organizations other than BYPL.
c. The AMISP needs to provide MPLS connectivity at the DC, DR of the AMI and BYPL
Locations.
d. Details of BYPL/BYPL Offices are –
1) Nehru Place, New Delhi (BYPL)
2) Karkardoma, New Delhi (BYPL)
3) Panvel (Mumbai)
4) BIDC, Okhla, New Delhi
5) SMOC Center

8.3 General Requirements

The AMISP shall design a reliable, interference free & robust communication network
keeping in view the site conditions. It shall be flexible in terms of providing communication
in variable terrain & urban density.

During designing, suitable consideration shall be kept for future expansion as per
requirement of BYPL. Before designing the communication network, the AMISP shall do
BSES

the site survey. The operational testing of all the network elements has to be demonstrated
by the bidder to the satisfaction of the BYPL.

The network solution offered by the bidder shall have disaster recovery mechanism in
place. The redundancy mechanism of HES and MDMS and their disaster recovery plan
shall also be described by the Bidder. DC-DR drill shall be conducted at-least once in a
year or as per BYPL requirement.

The quality of installation of the various equipment & power supply wiring to all field
equipment shall be as per standards/ regulations/prevailing practices of the BYPL. The
supply of electricity needed for operation and maintenance of entire AMI system shall be
the provided by the BYPL free of cost.

A suitable cellular network management system (NMS) shall be provided to monitor the
performance of the communication network round the clock. The NMS (RF and Cellular)
shall provide monitoring of Network status, Ping response and Service status at each
network point within project area. A suitable digital platform (cloud-based application) and
mobile apps could be provided to support field installation and capture field related
activities and to manage the field operation & maintenance activity during the contract
period. This platform shall manage project life cycle.
 NMS shall be able to manage, monitor and control network by way of receiving
parameters viz. terminal status, device status, next hop information, signal strength,
Hardware/software version numbers, logs, events etc. cetera.
 NMS should be able to perform ping & trace-route to an individual and a group of
Smart Meters.

Page 106 of 473

  NMS shall have remote configuration and remote firmware upgrade feature where an
individual and a group of devices be upgraded with its latest firmware. Updated
firmware shall always be backward compatible to all its previous versions.
 NMS shall support self-discovery and self-registration of meters upon deployment and
establishment of communication. System should allow provisioning of parameters as
defined in specifications and shall allow inputs via manual data entry or data files for
the necessary meter provisioning data.
 Notification: NMS shall routinely check the logged in status of the meters and its
availability in the network for data exchange. In case of failure to get the alive
message from the from devices, it shall mark and notify the node as logged -out
 The NMS shall have to capability to trigger a restart of a network to trigger a hardware
reset / restart of the node.
 Monitoring: The NMS shall support collecting and storing monitoring profiles from
meters and network devices for monitoring, performance evaluation, and
troubleshooting purposes. The collected data / information shall be available for later
retrieval and analysis by back-end systems (using standard reporting & data mining
tools).
 Time Distribution: NMS shall manage time distribution to ensure that meters always
have an accurate RTC using NTP servers. The time distribution mechanism shall take
into account the network latencies.
 NMS shall have set of KPIs regarding network performance. AMI Implementation
Partner shall provide document mentioning set of KPIs.
 NMS shall have real time and historical information logs.

8.3.1 Network Protection & Security

The AMI Network shall have adequate cyber security measures not limited to the measures
as described below. The network security would be extended to all the interfaces also.
BSES

a) Secure Access Controls: The system shall include mechanisms for defining and
controlling user access to the operating system environment and applications. Best
practices from enterprise security including password strength, password aging,
password history, reuse prevention etc. must be followed for access control.
b) Authorization Controls: A least-privilege concept such that users are only allowed to
use or access functions for which they have been given authorization shall be
available.
c) Logging: Logs must be maintained for all attempts to log on (both successful and
unsuccessful), any privilege change requests (both successful and unsuccessful), user
actions affecting security (such as password changes), attempts to perform actions not
authorized by the authorization controls, all configuration changes etc. Additionally, the
access to such logs must be controlled in accordance to the least-privilege concept
mentioned above, so that entries may not be deleted, accidentally or maliciously.
d) Hardening: All unnecessary packages must be removed and/or disabled from the
system. Additionally, all unused operating system services and unused networking
ports must be disabled or blocked. Only secure maintenance access shall be permitted
and all known insecure protocols shall be disabled.
e) Malicious Software Prevention: Implementation of anti-virus software and other
malicious software prevention tools shall be supported for all applications, servers, data
bases etc.
f) Network Security: The network architecture of the HES must be secure with support
for firewalls and encryption. The system shall also allow host-based firewalls to be
configured, as an additional layer of security if the network firewall were to fail.

The bidder may select more than one Telecommunication Service Providers (TSP) for
the providing cellular based network connectivity to and from smart meters. The cellular
based communication network shall be capable of servicing 4G / NBIoT fallback on 2G

Page 107 of 473

 or RF (fallback to be decided by AMISP)Communication Technology compliant with
IPv6 operating in the frequency bands allocated by Government of India. The cellular
based network between smart meters and HES shall be a VPN-based secure tunnel.
The SIM cards must be capable of Short Messaging Service (SMS).

The AMISP shall be solely responsible for the governance of its TSP (s)and shall make
payment directly to TSP.

The overall cyber security policy and implementation shall account for:
a) Prevent unauthorized users from reading or writing data or files, executing
programs or performing operations without appropriate privileges.
b) Document all user sign on procedure
c) Record all network traffic for detecting unauthorized activity, unusual activity and
attempts to defeat system security (AMISP to propose and document what
constitutes normal activity/traffic)
d) A user authentication scheme consisting of at least a user identification and
password shall be required for the user to request a connection to any network
node.
e) GUI to provide role-based access based on user identity and user role. Shall have
following types of users:
i. Administrator
ii. Operator
iii. Field staff
iv. Viewer/Guest

8.3.2 SIM Card Management

The Bidder shall ensure the availability, insertion and management of the SIM cards to be
BSES

used in communication module of smart meters, Gateways/ Routers/Access points.

I. Bidder shall be responsible for supply of SIM cards to meter OEMs and field O&M
work.
II. The Bidder shall be responsible for management of SIM inventory including but not
limited to total installed, in-stock, replaced and rejected/suspended/terminated SIMs.
III. The Bidder shall ensure that communication module is properly sealed after SIM
Insertion before installation as well as during Operation and Maintenance phase.
IV. Replacement of faulty SIM cards to meet the SLA.
V. The Bidder shall have to ensure timely suspension, termination; activation,
deactivation and reactivation of SIMs and the process shall comply with the
prevailing regulations of DoT/ TRAI. AMISP shall be responsible for any revenue
loss due to untimely deactivation.
VI. Bidder shall ensure that the SIM information is available in the Head End System
before physical installation is carried out
VII. Bidder shall ensure quality aspect of physical SIMs from TSP along with the
maintenance of buffer stock of SIMs & their activation - deactivation.
VIII. Bidder shall ensure timely deactivation, suspension, termination, activation and re-
activation of SIMs and the process shall comply to the prevailing regulations of DoT /
TRAI & shall be approved by BYPL.
IX. Bidder need to monitor the usage, alarm, events and connectivity of TSP core
components for the SIM cards used in AMI solution.
X. SIMs needs to be preconfigured for activation before meter installation begins and SI
shall work in close coordination with Telecom service Providers.
XI. Provide daily, real-time project status updates of installations to BYPL.
XII. Weekly MIS for SIM card inventory and the status.

Page 108 of 473

 Detailed specifications for RF Mesh Communication are given at Appendix 1: RF
Mesh Solution Details at Clause 0: of Section 6

8.4 Unified Head End System (UHES)

The main objective of Unified HES is to acquire meter data automatically by using any
communication mode RF / Cellular / PLC avoiding any human intervention and monitor
parameters acquired from meters.

The AMISP shall provide a Unified HES which is suitable to support the collection and
storage of data as per performance level for a defined no. of Smart Meters with facility of
future expansion as per the requirement specified in this document.

Unified HES shall be responsible for discovery of all Smart Meters once deployed in the
field, the periodic collection of all meter data as well as the processing of all alarms and
commands such as connect/disconnect for those meters.
Unified HES would perform all the requisite functions as per the defined functionalities of
AMI and it is the responsibility of the AMISP to supply the requisite software and hardware
to achieve the defined functionalities of AMI. Unified HES shall ensure data integrity
checks, for example, checksum, time check, pulse, overflow, etc. on all metered data.

Unified HES shall be developed on open platform based on distributed architecture for
scalability without degradation of the performance using additional hardware. The
scalability shall ensure the ability to handle applicable workloads including the following:

a) Up to 2 Million numbers of meters installed (shall be capable of handling 4lakh meters

initially and scalable upto 10 Million metering points)
b) 15 mins interval meter reads, in many cases data can be even for 5 mins
BSES

c) 100 users requesting data from meters

d) Other events and statuses coming from meters.

The Unified HES shall be cloud enabled and support deployment with high availability
clustering and automatic load balancing that ensure hardware as well as application
failover. Adequate database and security features for storage of data at Unified HES need
to be ensured.

The suggested functions of Unified HES (not exhaustive) may be:

8.4.1 Functional Requirements of Unified HES

a) On power up after installation, Smart Meter shall register itself automatically into the
Unified HES along with its metering profile. The Unified HES shall store meter profile
status by meter type, hardware & software versions, device IDs, logged in / logged out
details etc.
b) Upon deployment and establishment of communication, it shall be possible for field
level end device nodes (NAN/WAN) like Router/Gateway, Access Point, DCU, Smart
Meter to have self-discovery and registration.
c) Unified HES shall control devices and read meter data by interfacing with additional
HES is in place (in case of additional HES deployed for RF / PLC communication and
HES for existing AMR/Smart Meters)
d) On registration of meter in HES / Unified HES, it shall be ensured to change meter
security Keys for first time immediately after meter installation and maintain unique
authentication Keys for each meter. Key rotation shall be performed on BYPL defined
time period.

Page 109 of 473

 e) Acquisition of meter data on demand & at user selectable periodicity. On demand
meter read may be for single meter (unicast) or for a group of meters (multicast).
f) Unified HES shall have the ability to synchronize with the meter master data available
in MDMS as the meters are installed, replaced or removed and validate the correct
configuration and operation of the meters.
g) Two-way communication with meter/ DCU
h) UHES shall support integration and data exchange from group metering (multiple
meters having common communication module)
i) Signals for connect & disconnect of switches present in end points such as meters.
This facility shall be provided for both single meter as well as for a group of meters.
Maximum number of meters in a group shall be configurable in case of Disconnect.
System shall has provision to configure priority (e.g. priority for reconnection
command)
j) Audit trail and Event & Alarm Logging
k) Ability to redirect messages including configuration commands from the MDMS in
order to reach the desired meter
l) Maintain time sync with DCU / meter
m) Store raw data for defined duration (minimum 3 days, however AMISP shall ensure no
loss of data). Unified HES shall hold the data before it is transferred to the MDMS
n) Data visualization and download option for individual and multiple meters
o) Handling of Control signals / event messages on priority
p) Manage time distribution to ensure that nodes / meters always have an accurate RTC
using NTP servers. The time distribution mechanism shall take into account the
network latencies.
q) Setting of Smart Meter configurable parameters
r) Critical and non-critical event configuration and reporting functionality
s) Device management functionality to get periodic updates from devices on health
check, hardware & firmware version, location mapping etc.
BSES

t) Unified HES shall have provision for First Breath (Power On) and Last gasp (Power
off) condition detection and communication with Smart Meters. Unified HES shall
provide these outage detection and power restoration notifications to MDMs on real
time to support enhanced outage management.
u) Unified HES shall have the ability to categorize the meter under various drop-down
menus like zone / substation / feeder / DT / Consumer category (HT , Domestic,
Commercial, Net-meter, Open access).
v) Consumer Phase identification (in case of PLC)
w) Unified HES shall maintain identification of meters / field devices for each HES and
redirect commands to relevant HES (if more than one HES deployed/integrated)
x) Import data to Unified HES from BYPL existing HES / AMR or directly read existing
Smart Meters (to be decided during implementation)
y) Application shall support system security as mentioned under Clause 8.4 &8.5

8.4.2 Configuration
It shall be possible to update / change configuration of the meters in both Unicast (one to
one) and in Multicast fashion (Group of meters), Unified HES shall facilitate GET and SET
configuration of following minimum AMI parameters in :
a) Load profile capture period
b) Demand integration period
c) Setting of parameters for TOU billing
d) Prepaid / post-paid configuration
e) Net metering
f) Billing date / month-to-date for prepaid meters
g) Clock setting/time synchronizations
h) Load curtailment limit

Page 110 of 473

 i) Event setting for connect/disconnect
j) Number of auto reconnection attempt
k) Time interval between auto reconnection attempt
l) Lock out period for endpoint (meter) relay
m) Remote firmware update: It shall be also possible to have remote firmware upgrade
for an individual and a group of nodes (Meter, NAN/WAN, Routers/Gateways/ NIC/
Access Point, DCU).
n) Password setting
o) Push and/or Pull schedule
p) Setting threshold limits for monitored parameters
q) Alarm settings
r) Record temperature, generate alert and provision for disconnection if above threshold
value (configurable)
s) Configuration of Smart Meters based on difference in neutral and phase current to
ensure disconnection in case difference is more than the threshold value
(configurable) to ensure safety
t) Meter should send alerts for only those events that are configured. All events shall be
configurable (time, electrical parameters in percent or absolute value)
u) Smart meters shall support configuration for special category/essential services such
as hospitals, police stations etc so that supply should not be disconnected. For
disconnecting such consumers special command duly authorized will be required.
Audit trail of such commands shall be maintained along with login id, date, time, IP etc
and alert to be sent
v) Configuration of events threshold like Voltage, Current, PF etc.

The AMISP may suggest more parameters as per the requirement.

In addition to above, Unified HES shall also provide application level configurations for
BSES

following requirements but not limited to :

i. New meter make and type configuration through UI
ii. Add/Remove of data parameters by selecting individual OBIS code / group of OBIS
codes
iii. Mass Management: It shall support mass/ group management of meters for
functionality like On -Demand operations, configuration update, firmware upgrade
to manage large number of meters. Meter / Device group creation based on
multiple filter criteria like Office, Sub Station, Feeder, DT, Consumer Category,
Load, Meter Make, Meter Type, Meter Firmware etc. or custom group by
adding/uploading list of meters. These groups shall be accessible for creating
reading schedules, configurations schedules and On-Demand.
iv. Meter Firmware files to stored and maintained for each Meter Make/Type and
applicable old firmware, only relevant meters firmware file to be sent to meter
during Firmware upgrade process. In case of failure of firmware up-gradation, HES
shall ensure meter functional on the old firmware and there shall be no loss of
meter data.

8.4.3 Key Management System

The UHES shall have functionality to securely store and manage the security
information/ certificates related to Smart Meters. This includes Device Security keys and
asset information for processing further business flow. Appropriate Security algorithm
shall be put in use for storing such keys in the database. The UHES software must have
a Smart meter Key Management system, which shall allow to generate unique key for
individual meter and configure all or selective security keys. The Key Management

Page 111 of 473

 system of UHES shall ensure no loss of keys if there is failure in response or
communication issue during key change process.

Smart meter Key Management System

Sr. Re-
Key/Secret Application
No programmability
1 Low Level Secret (LLS) – Used for reading meter data Yes
MR
2 High Level Secret (HLS) Used for reading and Yes
– US reprogramming meter setting
3 High Level Secret (HLS) Used for Remote Firmware Yes
– FU upgrade
4 Encryption Key (EK)* Used for data encryption Yes
5 Authentication Key (AK)* Used for data authentication Yes

The UHES shall able to share the stored keys in secure way with other applicable in
encrypted/ decrypted form and encryption/ decryption methodology shall be share to
other application to use rotated key/ Secret (password).

For smooth functioning of the 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 BYPL only in case of default or contract
termination

8.4.4 Communication
BSES

The following communication functions with network devices shall be supported:

a) The communication interface of Unified HES shall be Telecom Service Provider
agnostic and have ability to support hybrid communication technologies viz NBIoT,
4G, 2G, RF, PLC and any upcoming communication technology based on field
conditions.
b) Unified HES shall communicate with DCUs/access points using WAN technology
c) Unified HES shall encrypt data for secure communication
d) Unified HES shall be able to accept data according to IS 15959 part-2 /part 3 and
latest amendments
e) Unified HES shall automatically retry for missed data; the number of retry attempts
shall be configurable
f) Unified HES shall retry (configurable attempts) before declaring command as failure
g) To receive confirmation on successful execution of a command
h) Shall have the ability to accept input, process, store, and analyse billing meter data
Register reads, Load profile, and Events / Alarms.
i) Shall have the ability to accept input, process, store, and analyse non-billing meter
data such as voltage, current, power quality data.
j) Unified HES shall have the flexibility to adopt pull and, or push mechanism to
acquire meter data for scheduled reads
k) Unified HES shall support meter energization checks (on-demand pings) for
meter/customer or batch of meters/customers.
l) Validate meter name plate details with Unified HES master mapping to ensure valid
meter data is processed in case of NIC / SIM replaced on field. Meter Serial no. to
be validated every time meter data (Billing Profile, Daily Billing, Instant, Load
Profile, Event etc.) read from the meters.

Page 112 of 473

 m) Shall have the ability to remotely diagnose and troubleshoot the communication
module of the meter like no power to NIC, meter to NIC link status, NIC faulty, NIC
hanged, NIC firmware not working
n) Unified HES shall maintain last data received timestamp of each profile (ED, LP,
EOB etc.) and schedule data polling to start from last collected data timestamp to
avoid duplicate data polling and efficient use of bandwidth.
o) Unified HES shall record and provide reason of failure in case of command
execution failed
p) The Unified HES shall have the Authentication, Authorization and Accounting
module. The Unified HES security mechanisms and communication protocols shall
be based on open standards. The system shall be designed with complete focus on
security and data integrity. The communication solution must be scalable in volume
and the Unified HES shall have built-in reserve capacity to allow memory and
processes to be upgraded with new functionality over time.
q) Shall facilitate issuing commands from MDMS – to acquire specific, instantaneous
or historical data. The commands can be to individually selectable meters or a
collection of meters (user defined) or all meters within a zone/ division / substation /
feeder / DT The Unified HES shall have the ability to perform these tasks and
respond the data back to the MDMS. The commands shall be typically (not limited
to)
 Meter reading (Load profile, registers, status flags)
 Meter events / Alarms
 Meter diagnostic (ping, load side voltage, switch status)
 On demand readings (registers and load profile)
 Meter connect / disconnect
r) Unified HES shall ensure data integrity checks, for example, checksum, time check,
pulse, overflow, etc. on all metered data
BSES

8.4.5 Database Software and Licenses

AMISP shall provide relevant database software for UHES and Licenses as per the
defined project requirements and timelines, following conditions to be considered
a. UHES database will store all profile data for minimum (3) days (period may be
change by BYPL as per future need and shall not exceed 7 days)

8.4.6 Integration

a. MDMS Integration
i. Shall have the ability to send the metering data in a specific format as
required for integration with the MDMS.
ii. Shall have the ability to respond to all the commands received from MDMS
iii. Shall have audit trail functionality for managing and storing all the records of
activities performed between HES and MDMS.

b. Telecom Service Provider (TSP) Integration

i. Shall have the ability to onboard Telecom Service Provider’s M2M platforms
for deriving the operation and management of SIM.
ii. Shall facilitate SIM management like active SIMs, Suspended SIMs, Data
consumed by each SIM

c. Integration with BYPL Existing HES / AMR

i. Unified HES should integrate with existing HES / AMR to collect meter
readings and execute commands (if possible)

Page 113 of 473

 d. Integration with additional HES provided for RF / PLC (if applicable)
e. UHES shall integrate with minimum5 meter makes and their types of existing smart
meters or new meters to be supplied in future.(new meter integration shall be
completed within 1 months after intimation by BYPL)
f. Integration with WFMS for meter ping
g. Integration with Mobile app supplied by meter vendors (Meter security keys not to
be stored in the WFMS/HHU/Mobile app for field operation activity.)
i. Meter reading through app
ii. Connect / Disconnect through app
iii. Key exchange with app to perform field operations

8.4.7 UHES Architecture

BSES

8.4.8 Monitoring and Reporting Capability

Unified HES shall have critical and non-critical reporting functionality. The critical & non-
critical information generated from this reporting functionality shall be made available to
MDMS at user configurable periodicity.

[Link] Dashboards

System shall able to generate real time dashboards based on Network / Office Area
selection
a) Count of total meters installed and active meters
b) Meter Communication and Non Communication along with aging
c) Data availability and Non availability (data profile wise)
d) SLA dashboards

[Link] Critical Reporting

Page 114 of 473

 Unified HES shall have alarms and keep record of following events:
a) Event log for node’s (meter) events such as tamper/power failures etc.
b) Data not received from nodes/end points
c) Relay does not operate for connect / disconnect
d) Communication link failure with nodes/end points
e) Network Failure
f) Power Failure
g) History of Audit Trail
h) Search/list of meters based on Configuration, Firmware, Switch status etc.
i) Transaction report for each command sent with response and exception
j) NIC / SIM change
k) Signal strength at each field device
l) SLA reports

[Link] Non-Critical Reporting

Unified HES shall report and keep record of following communication failure events:
a) Retry attempts
b) Missed periodic reading
c) Failure to connect

Unified HES shall support reporting of communication failure history of

nodes/routers/access points etc. and give an exception report for nodes/routers/access
points not communicating for last 0 – 24 hours (the reporting period shall be on user
configurable period).

Unified HES shall provide daily, weekly and monthly performance reports tracking
BSES

equipment failures, communications failures, and data latency for all customer and
equipment classes. It shall have the ability to categorize the meter under various drop-
down menus like office / substation / feeder / DT / Consumer category (HT, Domestic,
Commercial, Pre-paid, Net-meter, Open access) and depict the signal strength for user
definable period.

[Link] System Security

Unified HES shall have adequate security measures but not limited to given below
a. Secure Access Controls: The system shall include mechanisms for defining and
controlling user access to the operating system environment and applications. Best
practices from enterprise security including password strength, password ageing,
password history, reuse prevention must be followed for access control.
b. Authorization Controls: A least-privilege concept such that users are only allowed to
use or access functions for which they have been given authorization
c. Logging: Logs must be maintained for all attempts to log on (both successful and
unsuccessful),any privilege change requests, user actions affecting security (such
as password changes), attempts to perform actions not authorized by the
authorization controls, all configuration changes.
d. Secure upgrade process for hardware and software
e. Provide an environment sufficient to warrant the confidentiality of information to
ensure that data is not exposed to unauthorized persons, processes (interfaces),
and/or devices
f. Role-based security for database and application administration, application
operations and execution, read-only privileges
g. AES-256 (or better) bit encryption for persisting sensitive data at rest

Page 115 of 473

 [Link] Technical requirements
a. Unified HES shall easily integrate to different applications using industry standard
interfaces and shall comply with CIM / XML / IEC 61968/IS15959/ Indian
Companion Specification/ any other open standard. HES solution shall be Service
Oriented Architecture (SOA) enabled
b. Shall have sufficient data processing performance to maintain required SLA
c. The choice of OS shall be such that the HES application should functionally serve
for 10 years. However if the opted OS becomes obsolete and HES might not
function on the new version of OS, the bidder shall provide a free upgrade &
version compatible with the new OS.

8.5 Meter Data Management System (MDMS)

The Meter Data Management system (MDMS) shall support storage, archiving, retrieval &
analysis of meter data and various other MIS along with validation & verification
algorithms. The MDMS shall be a scalable and COTS product. It shall act as a central data
repository with interactive dashboard. MDMS shall have capability to import raw or
validated data in defined formats and export the processed and validated data to various
other systems sources and services in the agreed format. It shall provide validated data for
upstream systems such as billing, analytics, reporting, etc.

As mentioned in Clause 3 & 4 of this Section, MDMS should support the future
requirement (During contract period currency) of BYPL by way integration with other smart
grid functionalities as listed in Clause 3in this Section as and when implemented by BYPL.
In this effort, the methodology as outlined in the approach paper shall be followed.

Role-based security for database and application administration, application operations

BSES

and execution to be supported by MDMS. The details RBAC structure for cross functional
access shall be defined by successful bidder post award and will be submitted for approval
of BYPL.

The key use cases to be enabled by AMISP are provided below. Please note that these
are illustrative list of use cases only and are not an exhaustive list. Further please note that
all IS Standards shall be applicable.

S. No. Use Case Activity Description Source Destination Info Exchanged

1. Collection of Daily Meter Profile
1.1 At scheduled frequency HES should Meter Number, reading date &
pull the Daily Meter Data from Smart time, kW, kVA, kWh, kVAh,
HES Meter
Meter over communication Channel PF, Non-critical Event Code /
Date
1.2 Meter should send the data to HES.
Provision for retrial should be there if
Meter data is not collected within Meter Number, reading date &
time. Consumption details including time, kW, kVA, kWh, kVAh,
Meter HES
non-critical events will be in 15 PF, Non- critical Event Code /
min/30 min block data, and data Date
could be incremental to what was
sent by meter in preceding instance
1.3 HES should send the data t MDM Meter Number, reading date &
HES MDM time, kW, kVA, kWh, kVAh,
PF
1.4 MDM should send the required Prepaid Meter Number, reading date &
MDM
parameter to Prepaid system for daily Engine time, kW, kVA, kWh, kVAh,

Page 116 of 473

S. No. Use Case Activity Description Source Destination Info Exchanged
charge calculation at least once on PF, Non- critical Event Code /
daily basis Date
2. Monthly Billing Profile Collection
Command from Billing system Meter Number, reading date &
triggered and send to MDM / HES for Billing time, kW, kVA, kWh, kVAh,
2.1 MDM / HES
collection of Monthly billing Data System PF, Non- critical Event Code /
Date
HES should pull the monthly meter Meter Number, reading date &
data from Smart Meter over the time, kW, kVA, kWh, kVAh,
2.2 HES Meter
communication channel PF, Non-critical Event Code /
Date
Meter should send the data to HES. Meter Number, reading date &
Provision for retrial should be there if time, kW, kVA, kWh, kVAh,
2.3 Meter HES
Meter data is not collected within PF, Non-critical Event Code /
time. Date
HES should decrypt and validate the Meter Number, reading date &
data collected and send to MDM time, kW, kVA, kWh, kVAh,
2.4 HES MDM
PF, Non-critical Event Code /
Date
MDM should send the required Meter Number, reading date &
parameter to Billing system for Billing time, kW, kVA, kWh, kVAh,
2.5 MDM
Monthly Bill Calculation Engine PF, Non-critical Event Code /
Date
3. Remote Meter Disconnection
Meter disconnect operation Prepaid
Meter Number, group of
command after wallet balance Engine/
3.1 BSES

MDM meters, instruction to close

calculation Billing
switch
system
Disconnection alert sent to Meter Number, group of
Billing
3.2 Consumer MDM meters, instruction to close
System
switch
Meter disconnection operator Meter number, action
3.3 MDMS HES
command (disconnect)
3.4 Consumer meter disconnection HES Meter Meter Number, switch status
3.5 Disconnection Status Update Meter HES Meter Number, switch status
3.6 Disconnection Status Update HES MDM Meter Number, switch status
4. Remote Meter Reconnection
Meter reconnect operation command Billing Meter Number, group of
4.1 after wallet recharge Billing System / MDM meters, instruction to close
Prepaid switch
Meter reconnect operation Meter Number, group of
4.2 Command MDM HES meters, instruction to close
switch
Consumer meter reconnection Meter Number, action
4.3 HES Meter
(reconnect)
4.4 Reconnection Status Update Meter HES Meter Number, switch status
4.5 Reconnection Status Update HES MDM Meter Number, switch status
5. BYPL detects tempering at consumer site
High priority events captured by
Meter Number, event date &
5.1 Meter sent to HES as and when Meter HES
time, event Code /description
occurred
5.2 High priority events reach MDM for HES MDM Meter Number, event date

Page 117 of 473

S. No. Use Case Activity Description Source Destination Info Exchanged
further action. &time, event Code
/description
Share with WFM to Notify BYPL Consumer number, Meter
5.3 personnel for site inspection MDM WFM Number, Tamper code,
address
On analysis and detection of valid Consumer number, meter
tamper event or malfunction, the number, action to be triggered
5.4 Meter HES/MDM
tamper event must be sent / pushed (disconnect), action date &
by the meter to the HES /MDM time
HES sends disconnect command to Meter Number, action
5.5 HES Meter
meter (disconnect)
Tamper event shared with CIS/CRM.
Meter Number, event date &
5.6 Billing determinants are updated for MDM CIS/CRM
time, event Code /description
tamper invoicing
Meter re-connection order once Meter number, action
5.7 MDM HES
tamper issue is resolved (reconnect)
HES sends re-connect command to Meter Number, action
5.8 HES Meter
meter (reconnect)
6. Missed Interval Reading
On identifying missed interval, HES Meter Number, from date &
6.1 will re-acquire data for the missing HES Meter time, to date & time (for which
period from meter data is missing)
On receiving data request command, Meter Number, reading date &
6.2 Meter HES
meter will send data to HES time, kW, kVA, kWh, kVAh
Missed Interval and Reads Data Meter Number, readings with
6.3 HES MDM
acquired by MDM BSES
date & time
7. Consumer Connection outage / restoration event
Outage/restore event recorded by Meter Number, Outage /
7.1 meter is sent to HES as and when Meter HES restoration Date / Time,
event occurs Power On or Off count
Outage / Restoration Notification Meter Number, Outage /
7.2 HES MDM restoration Date / Time,
Power On or Off count
Sharing Outage / Restoration Meter Number, Outage /
OMS/CIS-
7.3 Notification MDM restoration Date / Time,
CRM
Power On or Off count
Meter read request from OMS to MDM 
7.4 OMS Meter Number,
identify service outage / restoration HES
Meter responds to event poll from Meter number, Status
7.5 Meter HES
HES (live/dead)
8. Remote Firmware upgrade / meter configuration change
8.1 Remote firmware upgrade HES Meter Firmware
Configuration Commands: Change
Meter number, tariff
tariff parameters, Synchronize clock,
8.2 HES Meter parameters, registers status,
Registers reset (status, max,
event type and priority
tampering)
Status update of Firmware /
8.3 Meter HES
Configuration
9. Load Monitoring at demand side
When there is a load violation event
HES  Meter Number, max demand,
9.1 recorded in the meter, the Meter
MDM date & time of load violation
information is sent to the CC

Page 118 of 473

S. No. Use Case Activity Description Source Destination Info Exchanged
10. Time Synchronization
Synchronizing RTCs of meters / HES DCU/Meter Time Setting
10.1
DCUs/ACP
11. Metering Network Changes
Change / new installation in Meter / Meter / Network identification info
11.1 HES
DCU Network Hierarchy DCU including DCUs
Change / new installation in Meter / Network identification info
11.2 HES MDM
DCU Network Hierarchy including DCU
12. New Consumer Connection
Receive verified pre & post- paid CIS- MDM
Consumer name, address.
12.1 new consumer requests CRM/
Connection request etc
Billing
12.2 Generate meter installation order MDM WFM Consumer ID & details
Receive meter installation report WFM MDM Meter number, DT no, Feeder
12.3
& reading
Requesting instant, interval & events MDM HES  Meter Number, Reading date
12.4 data from meters Meter & time, reading params (kWh,
kVAh, kWetc )
Acquire instant, interval / events data Meter Number, Reading date
12.5 from meter by HES which then HES MDM & time, reading params (kWh,
reaches MDM system. kVAh, kW etc )
Once new meter remote read MDM Billing / CIS- Consumer ID, Consumer
12.6 verification is over, confirm new CRM address, Meter Number, initial
connection with other applications reading etc.
13. Migrate Post Paid Consumers to Prepaid Mode
Receive migration request CIS-
Migration request for post-
BSES

13.1 CRM/ MDM

paid consumer with profile
Billing
Setup prepaid consumer profile in
Prepaid
13.2 prepaid engine. If no change in MDM Prepaid consumer profile
Engine
meter is required, skip next two steps
Generate prepaid meter installation
13.3 MDM WFM Consumer ID & details
order if required
Receive meter installation report Meter number, DT no, Feeder
13.4 WFM MDM
& reading
Enable prepaid mode in meter Prepaid HES 
13.5 Engineering token
Engine Meter
13.6 Receive activation confirmation HES MDM Activation Status
Request instant, interval & events Meter Number, Reading date
HES 
13.7 data from meter MDM & time, reading params (kWh,
Meter
kVAh, kW etc.)
Acquire instant, interval / events data Meter Number, Reading date
13.8 from meter by HES which then HES MDM & time, reading params (kWh,
reaches MDM system. kVAh, kW etc.)
Once meter remote read verification
CIS-CRM/
13.9 is over, share migration request MDM Prepaid Consumer Profile
Billing
completion detail with other modules
14. Migrate Prepaid Consumer to Postpaid Mode
Receive migration request Migration request for prepaid
14.1 CIS-CRM MDM
consumer with profile
Request meter data HES 
14.2 MDM Meter Number, Consumer ID
Meter

Page 119 of 473

S. No. Use Case Activity Description Source Destination Info Exchanged
Acquire instant, interval / events data Meter Number, Reading date
from meter by HES which then & time, reading params (kWh,
14.3 HES MDM
reaches MDM system. kVAh, kW etc.) with balance
credit
Send meter disconnect command HES 
14.4 MDM
Meter
14.5 Receive connection status HES MDM Disconnection Status
Enable post-paid mode in meter HES 
14.6 MDM Engineering Token
Meter
Receive activation of post- paid
14.7 HES MDM Activation Status
mode
Request instant, interval & events HES  Meter Number, Consumer
14.8 MDM
data from meter Meter ID
Acquire instant, interval / events data Meter Number, Reading date
14.9 from meter by HES which then HES MDM & time, reading params (kWh,
reaches MDM system. kVAh, kW etc.)
Once meter remote read verification Post-paid consumer profile
14.1 Billing / CIS-
is over, share migration request MDM and meter data along with
0 CRM
completion detail with other modules credit balance
15. Consumer Registration in Consumer Portal/ App
Consumer clicks on new user on
Portal/ Request for registration with
15.1 consumer portal/ App, provides RMN CIS/CRM
App RMN/email ID
or email ID and submits data
BYPL receives request for Email/
15.2 registration and sends OTP after CIS/ CRM Message OTP
verification BSES
Gateway
Consumer submit OTP Portal/
15.3 CIS/CRM
App
Consumer receive registration details Email Login ID and Default
15.4 CIS/ CRM
Gateway Password
Consumer Submit first log request Portal/
15.5 CIS/CRM
App
15.6 System Seek password change CIS/ CRM Portal/App
Consumer changes default password Portal/
15.7 CIS/CRM
App
16. Consumer Access to Consumption, Billing & Profile Data
Consumer logs in to Portal/ App Portal/
16.1 MDM
App
Consumer Profile for Portal/ App MDM Name, Account, Address,
16.2 CIS-CRM
Portal/App Service Points, K Number
Consumption Data Portal/App
16.3 MDM Consumption profile
 UI
Billing (post-paid) / Credit Balance Post-paid Billing history/
Billing 
16.4 (prepaid) Portal / App Current Bill, Prepaid
MDM
Recharge history
17. Prepaid Consumer Recharge
Consumer logs into Portal / Mobile Mob App
17.1 UI Login
App Portal
Consumer fills-in required detail in UI UI
Payment Consumer ID, Recharge
17.2 and requests recharge Prepaid
Gateway amount
App
17.3 Consumer selects payment method Payment Net banking

Page 120 of 473

S. No. Use Case Activity Description Source Destination Info Exchanged
Gateway /Credit Card
/ Wallet etc.
Consumer receives payment Prepaid
Payment
17.4 acknowledgement AppPortal
Gateway
 UI
Calculate credit balance for prepaid Prepaid Consumer credit balance
17.5 HESMeter
consumer & update prepaid meter App (virtual token)
Notify credit balance to consumer Prepaid Email / SMS
17.6 Credit Balance
App Gateway
18. Postpaid consumer bill payment
Consumer logs into Portal / Mobile Mob App
18.1 UI Login
App / Portal
Consumer is presented with Billing BillingM Portal / App
18.2 Outstanding Bill
history and current outstanding Bill DM UI
Consumer requests bill payment. UI Payment
18.3
Option to download bill Billing Gateway
Consumer selects payment method Net banking
Payment
18.4 /Credit Card
Gateway
/ Wallet etc.
Consumer receives payment Billing
Payment
18.5 acknowledgement Portal/
Gateway
AppUI
Payment acknowledgement through Email/SMS
18.6 Billing Payment acknowledgement
email/SMS gateway
19. Customer Service Request
Consumer logs in to Portal/ App Portal/
19.1 BSES

CIS/CRM
App
19.2 Consumer requests for service UI CIS/CRM Service Request
System assigns SRN & sends Portal/
acknowledgement App→ UI,
19.3 CIS/CRM
Email/SMS
Gateway
System resolves request & updates Portal/
19.4 consumer records CIS/ CRM 1. App→ UI,
2. CIS/ CRM
System closes SRN Email/SMS
19.5 CIS/CRM
Gateway
20. Customer Complaint
Consumer logs into Portal/ App Portal/
20.1 CIS/CRM
App
20.2 Consumer registers complaint UI CIS/CRM Specific Complaint
System assigns CRN & sends Portal/
acknowledgement App→UI,
20.3 CIS/ CRM
Email/SMS
Gateway
System assigns resolution based on CIS / OMS /
20.4 CIS/ CRM
nature of complaint WFM
Target system reports completion of OMS/
20.5 CIS/CRM
complaint WFM
System updates records and CIS,
20.6 closes CRN CIS/CRM Email/SMS
Gateway

Page 121 of 473

S. No. Use Case Activity Description Source Destination Info Exchanged
21 Demand Read of Meters from consumers premise
Requesting instantaneous, interval, Meter Number, Reading date
21.1 load profile & events data from MDM HES Meter & time, reading params (kWh,
meters kVAh, kW etc.)
Acquire instant, interval, load profile Meter Number, Reading date
Meter 
21.2 & events data from meters by HES MDM & time, reading params (kWh,
HES
which then reaches MDM system. kVAh, kW etc.)
22 Staff user access to BYPL portal
User Logs in to portal Login with appropriate
22.1 Portal MDM
credentials
22.2 User select available function MDM Portal  UI
User Logs out Portal 
22.3 MDM
UI

In Addition to above use case MDMS shall integrated to following existing and future
proposed systems of BYPL –

Existing systems: Proposed in future (but not limited to):

a. SAP- IS-U (CS, DB, Billing and FICA a. PLM
module) b. OMS
b. SAP- BIW c. DSM/DR
c. SAP- PI (MRO and Meter Readings) d. PQM
d. SAP- R/3 e. Grid Analytics
e. Existing AMR/HES f. Load Forecasting
f. BESS (Battery Energy Storage System) g. Any Other System
g. GIS BSES

h. EV

The AMISP shall specify and deliver an initial system that supports the collection and
storage of data for meeting the performance level for Meters scope provided in project
area details in Clause 3 of this section with facility of future expansion.

The MDMS shall have the ability to selectively choose which data to be maintained
and which to be purged or archived [as per requirement of BYPL (user selectable)]

HES shall preferably be interfaced with MDMS 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.

HES shall export all meter data to MDMS and pass control commands from MDMS.

HES should conform to IEC 61968-9/ CIM 2.0 / Multi Speak v3.0 / SOA Architecture.
and shall integrate with MDMS 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. In Case of SOA
architecture then HES should be allowed to interface on SOA Architecture; the data
exchange to and from HES shall be through this ESB.

8.5.1 Asset Management

Page 122 of 473

 a) The MDMS shall maintain information and relationships between the current
installed meter location (apartment, shop, industry/ address etc.), Consumer
information (Name etc.), Consumer account no, Meter ID, Type of Meter (type
of consumer, 1 phase/ 3phase, with or without relay, etc.), Meter configuration
(Demand integration period, Load profile capture period etc.), GIS supplied
information (longitude, latitude, connection with feeder/ transformer/ pole etc.)
etc.
b) The software should support tracking the status of meters and communication
equipment from the date when they are installed in the field. The history of in-
service asset location is maintained throughout the device life with start and
end dates associated with each in-service location reference.
c) Ability to report and log any damage / deterioration in the meter attributable to
consumer /BYPL.
d) The MDMS shall also support device lifecycle management from device
registration, installation, provisioning, operations and maintenance to
decommissioning etc
e) This information should be maintained at the MDMS. The AMISP may have an
operational responsibility to access and provide the information but not from
the HES, but from the MDMS.
f) AMISP shall design mobile app for managing field operations such as
replacement of meter, new meter installation etc. & Inventory Management.
The workflow and parameters shall be discussed with the BYPL.

8.5.2 AMI Installation Support

a) The MDMS shall also support device lifecycle management from device
registration, installation, provisioning, operations and maintenance to
decommissioning etc. The MDMS shall generate exceptions for meter or
modules not delivering the correct meter data after installation.
BSES

b) The MDMS shall provide a reconciliation report that identifies the meters that
have been installed but not communicating for a designated (configurable)
period. MDMS shall generate reports on the number of meters installed in
comparison to the number of meters successfully communicating.
c) The MDMS should provide a view of the devices in the form of a network
hierarchy and allow managing the view to add/ delete / modify with complete
audit trail.
d) Ability to report and log any damage / deterioration in the meter attributable to
consumer /BYPL.

8.5.3 Security

MDMS shall ensure of the security requirements in the following areas

1. Role Based Access control (RBAC)
2. Database security

RBAC Functionality shall restrict Application access based on assigned user

permissions, which differ according to the user’s role within BYPL different
departments. RBAC enables to control access of the Application permissions to
the users. Each module within MDMS shall have its own permissions; users can
belong to respective Modules to ensure they have access to exactly the
permissions they need.

Database Security shall be defined as system or process by which the

confidentiality and availability of application data as well as database. DB Security
to provide controlled and protected access to the users.

Page 123 of 473

 A user may have several forms of authorization on parts of the database. The
following are the authorization rights.
 Read authorization allows reading, but not modification of data.
 Update authorization allows modification, but not deletion of data.
 Insert authorization allows insertion of new data, but not modification of
existing data.
 User doesn’t have Delete & Drop authorizations.

8.5.4 Meter Data

a) The MDMS shall accept input, process, store, and analyse Meter data from
HES and meter data collected through handheld meter reading instruments
and manual meter reads. In case of manual reads, provision should be there
to insert associated notes such as assessed energy, etc. It would be
responsibility of AMISP for manual meter reading in case of any
communication failure, etc. with seven (7) days of such failure.
b) The MDMS should accept input, process, store, and analyse non-billing meter
data such voltage and power quality data (such as under/over voltage, out of
band frequency, etc.) as they are available from HES. The MDMS should also
support schedule and on-demand meter reads and pinging of meter energized
states by authorized users and by other BYPL systems.
c) The MDMS shall provide storage and retrieval of collected Meter Data, events
and alarm. It shall have capacity of storing 5 years data (Billing, Daily Energy
Data and Critical Events) or more (as required by the BYPL) via archiving.
d) The MDMS shall provide storage and retrieval of all collected Meter Data,
events and alarm. It shall have capacity of storing 1 year data (Load Profile,
Alarm, and Instantaneous profile) and more (as required by the BYPL) via
transfer of data to separate DB as specified under Advanced Data Analytics
clause 11.
BSES

e) The archiving of data should be done at a frequency decided by the BYPL

during implementation phase. AMISP’s solution should describe the process of
archiving and restoration from the archive.
f) Correctly track & resolve energy usage across meter changes with no loss of
individual meter data.
g) Provide complete history and audit trail for all data collected from meters
including commands sent to meters and other devices for 30 days
(configurable period).
h) Execute on-demand read processes.
i) Handle special metering configurations such as net metering/pre-paid
metering/multiple meters at same premises.
j) The MDMS shall have the ability to manage at a minimum 5-minute interval
data.
k) The AMISP shall ensure data integrity checks on all metered data received
from data collection systems.
l) The MDMS should allow maintain business entities relate to meters in synch
with CIS data from SAP ISU.
m) The MDMS should identify and maintain the source of the meter data i.e. HES
or handheld etc.
n) The MDMS shall have the ability to track and maintain service point
information (e.g. device changes, device sets, multiplier changes, unit of
measure, communication module info, network address and connectivity, load
transfers etc.) by effective dates and time of the changes. This information
may be obtained from various sources like CIS, GIS, OMS etc.

Page 124 of 473

o) The MDMS shall store both general device information and communication
module information, if applicable. (e.g., serial number, purchase date,
manufacturer information, test data, size, location, etc.).
p) When applicable, the MDMS shall maintain the relationship between
communication module information and the device (serial number,
install/remove dates, association/disassociation dates, battery dates, all device
characteristics etc.) where it is installed.
q) The MDMS shall track and maintain history of the relationship, both static and
dynamic, between devices and transformers via interface of the information
from other systems like GIS, OMS, DMS etc.
r) The MDMS shall have the ability to track device sets and changes by
interfacing with CIS and/or the device tracking system like DMS , GIS (as
appropriate).
s) The MDMS shall be able to handle updates on a daily basis of device and AMI
network information during deployment and ongoing operations.
t) The MDMS shall maintain information related to the account/service
point/meter/device relationship within the system, including historical lookup.
For example, the MDMS shall make it possible to easily determine total usage
for a particular service point over time through multiple device change-outs or
customers.
u) The MDMS shall keep track of whether each device read stored is an actual
read, an estimate, or a manually edited read. This status code must be
available to other systems.
v) The MDMS shall provide a mechanism for updating missing or estimated
reads with actual read data if it is available at a later point in time. Based on
user defined parameters, the system must automatically send out updated
data to applicable systems.
w) The MDMS shall have the ability to identify and store information associated
BSES

with customer owned devices if any.

x) The MDMS shall have the ability to receive, process, and store device data
from electric meter both time interval and cumulative or scalar data. The time
series data could be 15 mins load survey and from 15 min, 30 min, 60 min,
daily, monthly billing data.
y) The MDMS shall date-time stamp the data for each interval represented. The
interval time stamp shall be the time at the end of the interval.
z) The MDMS shall be capable of loading usage data from "hand-held" systems
(details will be provided by BYPL).
aa) The MDMS shall maintain read schedules within the system. This shall include
the ability to handle the coordination of a single schedule that includes multiple
sources of data (e.g. handhelds, Cellular, RF, PLC , etc.).
bb) The MDMS shall have the ability to install a check meter at a premise along
with the actual meter and should provide the variance report.
cc) The MDMS shall have the ability to export electric validated usage to external
clients.
dd) The MDMS shall have the ability to export un-validated device reads to
external clients.
ee) The MDMS shall have the ability to process certain event messages in a real-
time manner.
ff) The MDMS shall have the ability to receive commands from associated
systems (such as CIS) and issue a command to the device to complete the
command according to a user configurable priority.
gg) The MDMS should support on demand meter reads and “pinging” of the
meters on requests from other systems of BYPL like OMS, CRM etc.
hh) The MDMS shall have the ability to automatically initiate commands (such as
on-demands reads) to the AMI devices.

Page 125 of 473

 ii) The MDMS shall have the ability to send messages (e.g. Demand Side
Management event data) to HAN-enabled meters.
jj) The MDMS shall have the ability to receive acknowledgement messages from
the HAN-enabled appliances.

8.5.5 Data Validation, Estimation, and Editing (VEE)

MDMS shall have provision of UI based configurable VEE rules where authorised
user can enable or disable any predefined VEE rules, system shall also have
identification of Soft Check or Hard Check against each rule based on data can be
rejected or processed into main database. Rejected data as per Hard check failure
shall be maintain into temporary database for configurable period.
a) The validation and estimation of metered data shall be based on standard
estimation methods (such as max/avg. of past three days, max/avg. of past X
number of similar weekdays, max/avg. of similar blocks of past X numbers of
similar weekdays, etc.). The MDMS should also support and maintain
following data-
i. Registered Read Data including register reads, daily billing cycle, as
well as derived billing determinants such as TOU
ii. Interval Data channels with variable intervals and variable units of
measure
iii. Calculated Data that is derived or computed such as billing
determinants and aggregated loads.
iv. Event data storage of all collected event and alarm data from meters,
network equipment, and MDMS itself
b) MDMS shall flag, alarm and trigger an estimating process including but not
limited to when the following anomalies occur in the cumulative (“CUM”)
register reads BSES

i. CUM decrements within a billing cycle (except net-metering)

ii. CUM reads increments more than configurable threshold
iii. Future or old read dates
iv. Number of digits exceeds number of meter dials
c) MDMS shall detect, flag, alarm and trigger an estimating process including but
not limited to when the following anomalies occur in Time of Use (TOU)
register reads
i. Register decrements (except net-metering)
ii. Resets (to zero) (except net-metering)
iii. CUM reads increments more than configurable threshold
iv. Future or old read dates
v. Erratic compared to CUM read (sum of TOU reads minus CUM read)
d) MDMS shall detect, flag, alarm and trigger an estimating process including but
not limited to when the following anomalies occur in Demand register reads
i. Do not reset on cycle
ii. Do not reset coincident with consumer move-out or move-in
iii. Reset off cycle inappropriately
iv. Too high
e) MDMS shall detect, flag, alarm and trigger an estimating process including but
not limited to when the following anomalies occur in Interval reads
i. Long Interval
ii. Short Interval
iii. Interval Missing Check
f) MDMS shall detect, flag, alarm and trigger an estimating process including but
not limited to when the following anomalies occur
i. Usage to Inactive Meters

Page 126 of 473

 ii. Meter Identification
iii. Invalid date / Time
iv. Abnormal consumption
v. Stop Meter / Zero consumption
vi. KVArh Check

g) All data shall be transferred to billing system after meter data validation and
estimation including transformer / feeder station wise energy audit.
h) MDMS shall estimate usage for non-metered service points such as
streetlights, farm lights, traffic signals, etc.
i) The MDMS shall maintain both the original received raw data in a non-
manipulated state, in addition to VEE data.
j) The MDMS shall have the ability to estimate interval data and profile reads in
conformance with configurable rules.
k) The MDMS shall have the ability to identify and report the algorithm that is
used to calculate an estimate.
l) The MDMS should provide various estimations like profile based estimation,
linear interpolation, interval estimation, averages etc. for the missing values.
m) The MDMS shall have the ability to manually override automatic VEE intervals
and profile reads (Manually overridden data should have an audit trail).
n) The MDMS shall maintain meter identification flag against each meter and
meter data received against unidentified meters (not received from SAP as
valid meter but data received from HES) are to be stored for defined period as
non validated data and as and when meter becomes identified/authorised than
data to be reprocessed through VEE and to be stored in main database.
o) Notwithstanding the latency of data collection via the AMI system, once the
MDMS receives meter read data, the VEE process occurs in real-time and the
post-VEE data is then immediately available to user or external systems.
BSES

p) The MDMS shall be able to automatically flag data changes from manual
edits, VEE (Validating, Editing and Estimating) rules and data source
corrections and electronically generate audit trail with timestamps and user-
ids.
q) The VEE Engine shall support parameter-based validation and estimation
algorithms, user-defined validation and estimation algorithms, and editing of
individual values and statuses in the MDMS embedded user interface.

8.5.6 Billing Determinants Calculations

The MDMS-
a) Shall allow configuring multiple TOU options (e.g., the number and duration of
TOU rate periods) by consumer type, tariffs and day type (weekend,
weekdays, and holidays) and by season.
b) Shall support the processing of interval data into billing determinants to include
the following at a minimum:
i. Total Reading and Consumption
ii. Reading and Consumption in different time blocks for ToU billing
(Monthly and Daily both)
iii. Maximum Demand (in kW and kVA)
iv. Number of tamper counts
v. Average power factor
vi. Net-Metering data
c) Shall process interval data and frame it into the appropriate TOU periods for
consumption and demand; for example, roll up 15/30-minute data intervals into
hourly data.
d) Shall have the ability to properly account for special metering situations such
as check metering, sub metering, prepaid metering, net metering and open
Page 127 of 473
 access when calculating billing determinants and sending them to billing and
other systems.
e) Shall have the ability to properly account for special situations including, but
not limited to, curtailment requests, demand response scenarios when
calculating billing determinants and sending them to billing software.
f) Shall have the ability to facilitate implementation of automatic compensation
payments by BYPL to consumers for sustained outages when requested.
Compensation calculations would require cross checking with billing and
consumer balance information to ensure that disconnection is not construed
as a no supply event.
g) The MDMS shall be able to process data into billing determinants from interval
meter/device or consumption data (e.g. kWh, kW, kVAR usage, kVARh, kVAR,
kVA, power factor, load factor etc.) for all types of meters with BYPL in the
required time period.
h) The MDMS shall be able to calculate billing determinants should support all
type of BYPL tariff requirements.
i) The MDMS shall be able to calculate billing determinants from monthly reads
for both time interval meters and cumulative or scalar meter data.
j) The MDMS shall be able to calculate billing determinants from hourly/ half
hourly/ 15 mins and daily reads for both time interval and cumulative or scalar
meter data.
k) The MDMS shall be able to calculate billing determinants from special rate
scheduled reads, e.g. TOD, CPP, RTP etc. with facility for settlements.
l) The MDMS shall use previously calculated billing determinants and estimated
values, whenever required.
m) The MDMS should be capable of handling device changes occurring during
the billing period while calculating bill determinants.
n) The MDMS shall factor changes to the billing interval length while calculating
BSES

bill determinants.
o) The MDMS shall be able to handle multiple events in a given bill period
(device change out, equipment cycles, tariff changes, etc.).
p) MDMS shall be able to receive data and transmit data to and from a third party
or handheld devices.
q) The MDMS shall have the ability to process billing determinants for re-bills for
multiple billing periods.
r) The MDMS shall have the ability to handle Bill Period changes, with or without
change in interval level usage.
s) The MDMS should have the ability to re-calculate estimated intervals/reads
upon receipt of actual data.

8.5.7 Net Metering

MDMS shall flag, alarm and trigger an estimating process including but not limited
to when the following events occur:
a) CUM decrements of forward energy within a billing cycle
b) Register decrements for Time of Use (ToU) of forward energy
c) Power generated(exported) by any net-metering consumer more than the
installed capacity of solar PV rooftop system
d) Energy exported in any given day by any net-metering consumer more than
the programmable threshold value
e) Site inverters to be integrated to fetch information from inverters and establish
two-way communication to provide control command to inverters as well.

8.5.8 Exception Management

Page 128 of 473

 a) Ability to capture and log data exceptions, problems and failures and to
generate management reports, provide trend analysis, automate generation of
service requests and track corrective actions.
b) Ability to group, prioritize, filter and send system generated alarms and events
to predetermined email addresses, cellular text messages to phone
numbers/SMS/consumer care etc. Alternatively, these alarms/alerts may be
routed to BYPL’s WFMS.
c) The MDMS should have facility to apply validations/exceptions automatically
or on demand.
d) The MDMS should have flexibility to apply specific rules or a set of rules to a
specific customer or a class of customers.
e) The MDMS will provide VEE and exception handling for all types of meters
like- consumer meters, transformer meters, feeder meter and border meters in
BYPL.
f) The MDMS should provide proper work flow functionality for VEE and
Exceptional Handling.
g) Exception Generation - MDMS shall generate exceptions based on
configurable business rules including but not limited to the following:
i. Meter tamper alerts
ii. Communication module health alerts for meter/DCU
iii. If the consumption is less/more than pre-defined average consumption
iv. Negative Consumption (not for net-metering)
v. Power outage indications received from the Smart Meter
vi. Main and Backup meter reading comparison
vii. Comparison of parameters
viii. Time drift
ix. Meter re-programmed
BSES

8.5.9 Remote Disconnect/Connect

a. The MDMS shall have the ability to recognize if the installed device is
capable of remote connect / disconnect regardless of a meter's
configuration.
b. The MDMS shall be able to remotely issue generated connect / disconnect
service commands for an effective date/time to the appropriate customer
meter(s) or group of customers based on conditions like- default, fraud,
tech failure, construction works, manoeuvring, release of selective loads,
inability to access, shutoff by customer request etc. BYPL shall provide the
details of customers with such capabilities at an appropriate time.
c. MDMS should handle the prepayment metering by receiving meter connect
from smart prepaid billing system or CIS and issue a meter disconnect
when the customer credit demand is reached.
d. The MDMS shall be able to read and process response data associated
with remotely issued CIS connect / disconnect events to customer meters.
e. The MDMS shall have the ability to receive and respond to a connect /
disconnect command to facilitate to implement programs like DR, DSM,
RTP, pEV, Selective load release, New Customer Activation, Urgent
Interruption etc. by MDMS package or BYPL systems responsible.
f. The MDMS shall have the ability to receive and respond to a command
from BYPL systems to cancel all, or a subset of (e.g. Field Service Offices)
connects / disconnects orders.
g. The MDMS shall have the ability to schedule connect / disconnect orders
by date, time and other factors. Users shall be able to configure the
scheduling algorithm.

Page 129 of 473

 h. The MDMS shall check for cancellation requests prior to initiating connect /
disconnect command to the device.

8.5.10 Service Orders

a) The MDMS shall generate service orders based on configurable rules for
various events and alarms such as stop meter, tampers, problem in
communication networks and exception conditions defined by BYPL, etc.
b) MDMS shall send service orders via SMS, email, etc. with the email
addresses / phone numbers being configurable. MDMS shall receive
feedback on action taken on the service order and track the status of service
orders until resolution.
c) Service order tickets could be generated by MDMS but processed and closed
under jurisdiction of the HES-NMS combine.
d) MDMS shall transfer auto/ individual tickets to SMOC for field verification and
operational activity. It shall receive response and store against each ticket
created.
e) The MDMS shall have the ability to schedule field orders for any device
service and prioritize those orders by type, date, time and other factors. Users
shall be able to configure the prioritization algorithm.
f) The MDMS shall have the ability to receive and respond to a command from
the associated system to stop all, or a subset of orders (e.g. Field Service
Offices). Users shall be able to configure the subset of orders to be stopped.

8.5.11 Revenue Protection Support

a) Ability to analyse meter tampering flags, power outages, usage trends and
usage profiles to identify potential energy diversion situations, and produce
daily reports, monthly reports and service order requests for investigation.
b) The business rules for revenue protection alerts shall be configurable via a
BSES

user-friendly interface.
c) The MDMS shall filter out revenue protection alerts that may be caused by
field activities if the field activity information is provided to the MDMS.
d) The MDMS shall support the analytics/investigation (i.e., view current and
historical usage patterns) to validate suspected revenue protection issues.

8.5.12 Configuration
MDMS shall have provision of configurations as per following requirement (not
limited to) :
a) Meter/Field device configuration command shall be provisioned to be initiated
from MDMS to HES for all configurable parameters in Meter/Field device.
b) Threshold configuration for all configurable parameters.
c) Reading scheduler configuration (including missing read)
d) Meter & Consumer master data configurations through UI (as fallback
mechanism if integration not working)
e) Alarm notification configuration for enabling SMS/E-Mail notification to
authorised BYPL staff / relevant BYPL staff belongs to area of meter where
alarm generated.
f) VEE rule configuration (enabling and disabling of VEE rules)
g) Disconnection holiday calendar / disconnection window timing configuration
h) Configuration of consumer alert parameter / threshold and scheduler as per
requirement specified in this section

8.5.13 Demand Response / Demand Control Support

Page 130 of 473

Bidder shall describe how its MDMS supports Smart Grid Demand Response
programs involving Demand Response (DR) systems as part of PLM. The solution
shall support the following analysis:
a) Totalling the actual consumption during DR event
b) Totalling the actual consumption of different groups that participated in the DR
event.
c) Comparing the actual to baseline consumption for the groups above

The MDMS shall support the tracking, monitoring and managing of Smart Meter
and events, and monitors customer response to facilitate payment of customer
incentives

Demand Response Use Cases:

The objective of the Demand Response iterated in the RFP is to optimal utilization
of energy resources by uniform distribution of load across the day, to save
additional investment in capacity addition within the BYPL, improved access of
power to rural areas, reduction in technical losses, enhanced consumer satisfaction
by load curtailment in place of load shedding. Following are few functional
requirements (but not limited to) for demand response:

S. Functional
Description of Functional requirement
No. requirement
1 Load Curtailment event System will determine based on day ahead
in place of Load schedule for available generation capacity and load
Shedding forecasting the load curtailment events. Advance
notice will be sent to a group of consumers affected
by this load curtailment. DR system will send the
BSES

load curtailment command to the MDMS. The

MDMS will forward this command to the appropriate
AMI Head-End.
2 DR Program Once the consumer is set up with all the devices
Commencement necessary, the consumer details will be sent to DR
system. Premium charges for assured power supply
with SLA and / or Rebates and incentives can be
given to consumers who participate in DR programs.
3 Real time Pricing BYPL shall be able to send real-time pricing signals
to end consumers/AMI system
4 Curtailment due to BYPL limits consumers load due to reasons like
Contract Violation exceeding contract Load
Alarms (visual and audio) shall be provided in case
of load violation (in home device, Email, SMS etc.).
The billing system shall be notified of the load
violation, and the corresponding charges shall be
applied to consumer (based on tariff rules).
5 Demand side In every 15-minute interval Meter data should be
Management captured, Confirmation of action taken for demand
response should be mentioned as well as
monitoring of historical Consumer Load Profile
should be done.
6 Load Monitoring at Daily Meter Reading, Status and associated details
Demand side capturing for records of consumer consumption
data, TOU details, real time trends and Load profile
Details. Along with this whenever there is a load

Page 131 of 473

 S. Functional
Description of Functional requirement
No. requirement
violation event recorded in the meter, the
information is sent to the control center
7 Initiate Direct Load BYPL calls a Direct Load Control Event using the
Control Event Peak Load Management (PLM) Application and
executes through head-end by sending a load
control signal to Smart Appliances thru HAN / Smart
Meter or other means

8.5.14 OMS Support

MDMS shall support Smart Grid OMS system as per the requirement of the BYPL.,
MDMS shall support the interfacing with OMS software for providing AMI meter
data needed for fault location identification and other requisite services like
updating the data after attending the fault etc

MDMS shall also support the interfacing of other smart grid functionalities like
Distribution Transformer Health Monitoring system, self-healing system, electric
vehicle etc. as and when implemented by the BYPL

Functional requirement thorough MDMS for OMS (not limited to):

a. The MDMS should be able to log and trigger alerts on receiving events
from meters such as tamper, outages etc.
b. The MDMS should be able to process outage notification event (last gasp)
and outage restoration (first gasp) of the meters. Such events should be
filtered against the known service orders (including declared outages from
OMS) before passing it to OMS.
BSES

c. The MDMS should have ability to differentiate fictitious and momentary

outages from meters before passing to OMS.

8.5.15 EV Support
MDMS shall maintain identification of EV Station connection with no. of charging
points connected and capacity of each charging point. MDMS shall support EV
System as per the requirement of BYPL, MDMS shall support the interfacing with
EV System installed across the project area. There are three type of EV charging
stations are installed
i. Public charging stations
ii. Private charging stations
iii. Battery swapping stations

Functional Requirements through MDMS for Electric Vehicle Charging:

a. Information recording on sudden change in Power (3-5KW, 15-30KW)
b. Record for Instantaneous Change in Demand with time stamp
c. Record of day wise peak demand, average consumption during day
d. Remote Disconnection and reconnection for direct load control (DSM)
e. Voltage and Power factor monitoring.
f. Analytics on general electrical parameters to track failure of charger
g. Automatic Complaint Registration/Trigger in event of Power Failure

A. Public Charging & Swapping Station

i. Analytics on consumption pattern to track misuse (Constant load for long
period, non standard demand etc.)
ii. Consumption study to track theft of electricity in PCS/E-Rickshaw
Connections (Consumption against per KW of Sanctioned Load)

Page 132 of 473

 iii. Recording of Power factor and reactive consumption to assess grid
impacts (Feasibility can be explored for Harmonics)
iv. Capability for Vehicle to Grid energy data recording

B. Private Charging
i. Analytics on Consumer Charging Pattern
ii. Analytics on consumption pattern to track misuse (Constant load for long
period, non standard demand pattern etc.)
iii. ToD alert to Consumer while start of charging session

C. Integration and data management

i. Session - Start & Stop (Timings & Duration)
ii. Instantaneous current flow to EV (required only for DC-001)
iii. Instantaneous AC supply voltage (required only for DC-001)
iv. Instantaneous active power imported by EV. (W or kW)
v. Instantaneous reactive power imported by EV. (var or kvar)
vi. Instantaneous power factor of total energy flow
vii. SoC - State of charge of charging vehicle in percentage, wherever
applicable
viii. Location
ix. Provision for On/Off charger through mobile app using Smart Meter by
integration of CPO-CMS Platform

8.5.16 Communication Prioritization and Management

a) The MDMS shall have the ability to prioritize commands sent to devices.
Prioritization shall be user-configurable.
b) The MDMS shall have the ability to delay commands, based on user
BSES

configuration, in order to manage AMI communication network activity when

necessary.
c) The MDMS shall have the ability to set a specified time for a command to be
executed.
d) The MDMS shall have the ability to set a specified delay prior to certain
commands being sent to the device based on business requirements.
e) The MDMS shall allow commands to be sent to groups of devices.
f) The MDMS shall have the ability to send commands based on a pre-set
schedule.
g) The MDMS shall have the ability to manage and balance alternate (non-daily,
e.g. hourly) device read schedules.
h) The MDMS shall have the ability to store / maintain a record history of all
commands sent to the devices and verify completion of the command(s) sent
to and received from the devices (e.g. verify successful disconnect).

8.5.17 Consumer/Device Grouping

a) The MDMS shall allow specified users to create a group of devices by

individually selecting devices from the overall pool of devices.
b) The MDMS shall allow specified users to create a group of devices by
importing device identifiers using common desktop tools such as Excel.
c) The MDMS batch commands may contain multiple, individual commands (i.e.
a message to the customer as well as an updated hourly device schedule).
d) The MDMS shall allow groups to be created utilizing information / criteria from
interfacing systems.

Page 133 of 473

8.5.18 Audit Logging

a) The MDMS shall support auditing for all logical data entities.
b) The MDMS shall record that events have occurred, e.g. Demand Response
events.
c) The MDMS shall maintain a record of all data that is modified. The record of
modifications is referred to below as an audit log.
d) When data is modified, the MDMS shall include the following information in an
audit log record: the user or system id making the change, a date-time stamp,
reason code, whether the new value is actual, estimated, or edited as well as
the new data value.
e) When data is modified, the MDMS shall maintain the previous data value and
audit record attributes. For example, user or system id, date-time stamp,
reason code, whether the data is actual or estimated, etc.
f) The list of valid reason codes must be maintained in a configurable table
accessible by an authorized administrator.
g) The MDMS audit log shall provide a mechanism to easily search and review
entries.
h) The MDMS shall not allow users to edit or update entries in the audit log.
i) The MDMS shall allow super-users to copy or archive an audit log.
j) The MDMS shall have the ability to self audit to ensure possible errors or
regulatory / rule violations do not occur, or when violations have occurred to
have the ability to notify users.
k) The system must provide a mechanism to easily see the history of a particular
data item as well as any changes that are made to that item.
l) Logs up to 3 Months in active mode and archival post 3 Months (retrieval of
archived data to be ensured within 1 Hr as and when required.)
BSES

8.5.19 Analysis

The MDMS shall have analysis capability based on configurable business rules
including but not limited to the following:
a) Display consumption/load profiles by configurable period (15/30 min, hour,
day, month, year etc.) day type (weekday, weekend, holiday, festival wise
etc.) and by tariff, customer type, or any user specified collection of meters.
b) Generate peak & off-peak load patterns by aggregating all loads of
DT/Feeder/consumer group.
c) Perform DT/feeder/Sub-Station wise energy accounting.
d) Perform load analysis for different groups and categories of consumers.
e) Ability to provide the data to load forecasting, load research or demand
response applications and perform error management like: Missed reads and
intermittent meter reads before taking into forecasting, load research or
demand response
f) Ability to configure the system to effectively visualize consumption trends,
identify unusual patterns, and visualize load analysis to understand which
assets are being over utilized.
g) Analyzing data to identify new patterns of usage, setting fraud alert /
transformer overload alerts / demand – supply gap alert etc.
h) Ability to receive and store outage and restoration event data from smart
meters and outage systems and to log all such events for analysis.
i) Ability to map consumers over electrical network hierarchy and update the
network hierarchy based on changes in GIS system, representation of energy
loss, consumption analysis, exception reporting on selection of network
hierarchy.

Page 134 of 473

 j) 360 degree view of consumer data through single UI for each data profile
(daily/ monthly consumption, events, outages, LP, PF, power quality etc.) and
history of changes on consumer/meter master.
k) Provision to validate consumer indexing or proposing of consumer indexing
based on correlation of outage event of Network point Vs Consumers.

8.5.20 BYPL User Interface

User interface for BYPL shall have ability for at least the following functionality:
a) Compare total energy costs on one rate schedule vs. one or many alternative
rates.
b) Enable the user to see how different options within a rate affect costs.
c) Enable the user to see how adjusting load or consumption levels or shifting
them to different time periods influences costs.
d) Display meter data at a user defined configurable cycle that allows authorized
users to view energy usage patterns and the data behind them for selected
consumers.
e) Allow authorized users to view metered data, initiate and view reports, modify
configurations, and initiate and update service requests.
f) Display the energy usage profile for a single meter or group of meters. The
load profile shall illustrate energy consumption and peak demand in user
defined intervals for a user-specified time period.
g) Display the energy usage profile for a single meter or group of meters
according to Time of Use (ToU) tariff.
h) The UI shall support a configurable BYPL dashboard for Operations and BYPL
Management
i) Access to a minimum of three (5) years (configurable) of historical energy
usage and meter reads through the UI.
j) Clearly and visually distinguish between metered, estimated, allocated and
BSES

substituted data.
k) User management with roles and access rights
l) GUI to provide role-based access based on user identity and user role. Shall
have following types of users:
i. Administrator
ii. Operator
iii. Field staff
iv. Viewer/Guest
m) Configure the look, feel, and functionality of the MDMS in accordance with
business needs, business processes, and business conventions. (E.g., GUI,
content, look and feel of screens, validation rules, exception handling, etc.).
n) Ability to set up alarm and event notifications that can be directed to a
combination of configurable email addresses, cellular text messages.
o) UI shall enable viewing of the credit amount updated in MDMS for prepaid
consumers.
p) Option to send marketing messages and notification to select consumers or
selected category of consumers
q) Facility to enable or disable existing functionalities/sections of App/Portal for
consumers use.
r) Consumer views to be available to BYPL consumer Service Executive also
except payment card/bank information.
s) Authorised representative to be enabled for consumer engagement analytics.
The analytics to be configurable/ generated with minimal database skill and nil
programming requirements.
t) Representative to be able to generate various reports at different intervals the
various reports required by BYPL. It shall be also possible to export the report
data in multiple formats such as XLS, CSV format, etc.
Page 135 of 473
 u) Provide consumer interactions history to enable efficient consumer complaints
and queries resolution with consumer information in single screen.
v) The MDMS shall provide user and system interfaces for the definition of
channel configuration by meter class, group or type.
w) The MDMS shall provide user and system interfaces to define an override
channel configuration for individual meters.
x) The MDMS shall have an easily accessible, fully integrated on-line help
function. Help functionality shall include an index, general search and
advanced search capabilities, Help contents shall be customizable.

8.5.21 Database Software and License

AMISP shall provide relevant database software for MDMS and Licenses to be
provides as per the scope defined, following conditions to be considered
I. MDMS database will store meter profile data based on configurable period
defined by BYPL for each meter data profile (like Energy Data, Billing Profile,
Events, Alarms etc.)
II. MDMS database will integrate with database of Analytics software and data
flow between these two databases shall happen as per the requirement on
periodicity required to fulfil business requirement. Data profiles like Load
Profile, Non Critical Event, Non Critical Alarms etc. shall be stored centrally
in Analytics database and will be accessed by MDMS for the features
required these data.
III. Data warehouse tables to be designed for consumption data storage for
different period (daily/weekly/monthly/yearly)

8.5.22 Integrations with CIS & Other Systems

MDMS should support/ compliment initiatives of BYPL like- CIS Billing with SAP
BSES

ISU, Work Management, Data Warehouse, Net Metering, Prepaid Billing, OMS,
Mobile Apps, Website Customer Portal, Online Energy Accounting, Network
Planning, Demand Response, EV Charging, Virtual Metering etc.

Following are few integration points but not limited to (refer clause 9.1 for list of
systems to be integrated with MDMS

i. Customer Information System (CIS)-SAP

a. The MDMS shall have the capacity to prepare, initiate and send daily
reads, interval data, and usage data to CIS.
b. The MDMS shall be able to receive and process CIS issued 'on-demand'
device commands.
c. The MDMS shall be able to send CIS the responses from the on-demand
device commands.
d. The MDMS shall be able to communicate, in real time or in batch, with
BYPL’s CIS billing system.
e. The MDMS shall be able to receive and respond to system commands for
bill cycle routes from the CIS system.
f. The MDMS shall be able to respond to, in real-time or in batch, and
satisfy system commands for billed usage data from the CIS system.
g. The MDMS shall be able to request and process billable reads from the
CIS environment.
h. The MDMS shall be able to provide the CIS application with the latest
read for use in service order processing.
i. The MDMS shall be able to receive meter/device class and individual
meter channel configurations from CIS or other systems.

Page 136 of 473

 ii. Geographical Information System (GIS)

a. The MDMS shall be able to receive incremental updates for the electric
distribution network sent by GIS on daily basis, especially network
hierarchy.
b. The MDMS shall allow users the ability to customize routine and ad hoc
reports for engineering purposes (e.g. highest demand each month over
the last 12 months) to access through GIS.
c. The MDMS shall have the ability to track and automatically send pre-
defined reports on a routine basis for quality control to GIS.

iii. Outage Management System (OMS)

a. The MDMS should maintain the grid hierarchy structure from OMS / GIS
and has data synchronizing facility at-least once in a day.
b. The MDMS shall be able to create, update, complete, and cancel all
outage notifications and send them to an Outage Management System
with configurable filters.
c. The MDMS shall be able to receive and process (planned and
unplanned) outage notifications and real-time circuit switching
information sent by OMS and filter the outage notifications from meter
data back to the OMS.
d. The MDMS shall have the ability to receive outage status from an OMS.
e. The MDMS shall have the ability to receive commands (e.g. ping) from
OMS.
f. Distribution Management System (DMS)
g. The MDMS shall be able to create, update, complete, and cancel all
BSES

outage or energy quality notifications and send them to DMS.

h. The MDMS shall have the ability to receive commands (e.g. ping) from
DMS.

iv. HHU/AMR & Existing HES

a. The MDMS shall have the ability to interface with existing handheld
devices, HES and AMR systems operational in BYPL to capture meter
reading, to meet any emergency need. It will be the responsibility of the
AMISP to ensure that the existing Hand Held devices, AMR and HES
are integrated to the MDMS. Mobile app will be considered as HHU
(hand Held Unit) Software

8.5.23 Reporting

The MDMS shall have robust reporting capabilities supporting the generation of
vendor supplied (standard), user generated and 'query based' reports on a
scheduled, event based, or manual basis across the users defined by BYPL. The
reports types supported should be - configurable parameter reports, comparative
reports, and exception reports [Link] solution shall include a list of the standard
reports that are provided with the MDMS including but not limited to following:
 Daily data collection report
 Usage exceptions
 VEE validation failures
 Missing interval Read date and times (on hourly, daily, weekly & monthly
basis)

Page 137 of 473

  Physical meter events (install, remove, connect, disconnect) & meter reset
report
 Meter flags
 Meter inventory
 defective meters
 AMI performance measurements
 Threshold Exception

The solution shall support users modifying standard reports to better meet specific
reporting requirements.
a. The MDMS shall enable the BYPL to deliver reports in standard digital format
such as PDF, Excel, CSV etc.
b. Ability for GUI (Graphical User Interface) to set up or change report delivery to
configurable email addresses, network file directories, ftp sites or printer
systems without modifying source program code and without any proprietary
language skills.
c. Provision for query builder/query executor where user can write own query or
queries shall be generated through user driven drop down menu in GUI. The
Bidder shall provide example queries to support internal report generation
needs.
d. Ability to provide daily & weekly interface exception reports between MDMS
and other subsystems e.g. billing, outage, etc.
e. In case more than one technology of AMI deployed in the field, the MDMS shall
generate report on the performance and availability of data being delivered per
AMI technology.

Through the usage of MDMS, following list of indicative reports are desired. BYPLS
reserve the right to add to the list in consultation with the AMISP without any
BSES

additional financial liability to the BYPLS.

[Link]. Report Name Report description Frequency

Ability to collect energy flow data from the
Collection of energy
metering module. The manual entry of data
1 flow data from Daily
shall not be allowed except in the exceptional
metering module
circumstances.
Ability to check energy balance between HV
Calculation of Bus
side and LV side of any Substation to ensure
bar and Weekly &
2 all the meters are working properly and can
transformation Monthly
calculate bus bar losses and transformation
losses
losses in the substation
Ability to balance 11 KV feeder flow against
Calculation of HT consumption of HT consumers and DTs in Weekly &
3
losses the feeder through integration with system Monthly
meter data acquisition module
Ability to add consumptions of all the
consumers connected to a particular DT and
the consumptions of all the DTs in an 11 KV
Calculation of DT
4 feeder. The necessary data for this regard Monthly
losses
will be available from the customer indexing
and asset codingdatabase and billing data
base.
Ability to enable the performance of HT and
Performance of
5 LT consumers’ revenue report on monthly, Monthly
revenue report
quarterly etc. basis.

Page 138 of 473

[Link]. Report Name Report description Frequency
Ability to generate report of energy
accounting indicating areas where high
Generation of report
technical losses and high commercial losses
6 of energy accounting Monthly
are taking place. This shall able to generate
and graphical
graphical of losses over a period for HT and
LT consumers.
Ability to enable monitoring for bill
Bill
correction/amendment manually to
7 correction/amendme Daily, Monthly
update/modify the customer billing database,
nt
with a reason for the same.
Change of billing Ability to know the change billing cycle of a
8 Daily, Monthly
cycle HT/LT customer.
Linking consumer to Ability to identify the customer link to the
9 Daily, Monthly
appropriate tariff tariff/rate applicable to his category.
Ability to enable monitoring of customer
performance based on contract demand
Contract demand
10 violation. In case of customer grievance, Daily
violation
report will use to check the load violated with
respect to sanctioned load.
Ability to enable monitoring of customer
performance based on peak (on/off) load
On Peak/Off Peak
11 violation. In case of customer grievance, Daily
load violation
report will use to check the load violation
during the peak hours and off-peak days.
Ability to enable monitoring of tampering.
Report provides the log of event containing
12 Tamper counts Daily; Monthly
the cause of tamper and total number of
BSES

tamper counts for the particular period.

Monitoring of Ability to know the health of the Feeder or
13 Daily
average power factor DTR or HT Consumer or LT Consumer
Assessed readings
Ability to enable monitoring of consumption or
14 for stopped meter Monthly
accessed readings for stopped meter(s).
cases
Comparative for
average historical Ability to detect low consumption cases by
Weekly &
15 consumption with comparing average historical consumption
Monthly
actual consumption with actual consumption data.
data
Ability to do the performance check with the
Monitoring of Load
16 help of load factor calculations for S/S or Daily; Monthly
factor
Feeder or DTR or HT Consumer
Monitoring of Power Ability to know the performance of the Feeder
17 Daily; Monthly
Factor or DTR or HT Consumer or LT Consumer
Monitoring of Ability to monitors performance check of
18 Daily; Monthly
Utilization factor feeder
Ability to monitor various load duration curves
Load duration
19 for HT consumer or LT consumer such as Daily; Monthly
curves
voltage vs current, power vs time etc.
Ability to compare consumption between pre-
Pre-paid vs postpaid Weekly &
20 paid and postpaid meters for optimum usage
(if present) Monthly
of energy.
Remote Meter Data Ability to provide the details of meters which Weekly &
21
Reading at requires schedule or on-demand readings for Monthly

Page 139 of 473

 [Link]. Report Name Report description Frequency
configurable particular period.
intervals (push / pull)
Remote Connection/ Ability to provide the details of remote
disconnection atconnection/disconnection based on Weekly &
22
defined/on demand defined/on-demand conditions for a particular Monthly
conditions period.
Net energy metering Ability to provide the details of net metering Weekly &
23
(for accurate billing) for HT customers, LT customers Monthly
Missing readsAbility to provide missing reads/consumption
24 Daily; Monthly
(interval/scalar) details for HT customers, LT customers
Ability to identify the details of defective
25 Defective meter Monthly
meters.
Ability to monitor data availability for current
26 Data Availability Daily; Monthly
and history dates for each data profile
Ability to generate events snapshot report for
27 Event Analysis Daily; Monthly
individual or group of meters
Ability to generate SMS/Email notification
28 Notifications Daily; Monthly
report
Ability to provide Load Profile report as per Interval, Daily,
29 Load Profile configured period and provision to convert LP Weekly, and
data into hourly, weekly, monthly Monthly
Ability to provide Peak Load details at each
30 Peak Load Report network points (SS/Feeder/DT) for selectable Daily; Monthly
period
Transaction Data ODR or Scheduled transaction data report
31 Daily; Monthly
Report with success and failure response
BSES

Validation Failure Ability to provide detailed report of each

32 Daily; Monthly
Reports validation failure
Ability to compare consumption of LP , Daily,
Monthly as per given selection criteria
a) Group of consumers (same building, Interval, Daily,
33 Comparison Reports consumer type, same category / load, Weekly, and
same network etc.) Monthly
b) DT Vs Consumer Tagged
c) Feeder Vs DT/HT
Interval, Daily,
Signal Strength analysis on individual meter
34 Signal Strength Weekly, and
or group of meter i.e. Office, DT, Feeder etc.
Monthly

8.6 Smart Prepaid Billing Module (SPBM)

Smart Prepaid application will ensure pre-payment meter functions. Smart Prepaid
system will be capable of supporting Smart Pre-Payment Meter functionality along will
full capability to manage conventional pre-payment with token recharge capability.
Smart prepaid system will have flexible tariff, rate, slab, rules, taxes and credit
management capability for all kinds of meters. Smart Prepaid will send alerts to
consumer via SMS and App notifications for recharge and low balance etc. Smart
prepaid system should have capability to send analytics based customer/society
engagement communications via SMS/App or any public communication platform

Smart prepaid system manages all (Smart) prepaid energy meters for Discom’s. All
functions relating to usage, tariff and recharge are performed centrally. Balance
related display parameters are transmitted back to the meter display. Consumer can

Page 140 of 473

 anytime access their information on demand basis via smart energy app. All
customers’ related alerts are communicated by smart prepaid system via app to the
consumer

The System envisaged should provide all the features required for complete Smart
Prepaid system without having any dependency with the BYPL required integration for
existing Systems of BYPL. Once the BYPL onboarding integration and is done and all
the data along with business rules are configured in the system, the system should
take care of the complete smart prepaid functionalities including enablement of
consumer recharge, Balance Management etc

Conventional Token based recharge capability is excluded from this scope.

The Meter Data Management System along with Smart Prepaid functionality will
supports storage, archiving, retrieval & analysis of meter data and validates
consumption and then convert it into prepaid credits.

The System should provide Adapters for various aspects of the system so that all
depend systems can interact with this system, required data exchange to be
standardized and Adapters should be used to build Mobile Apps, Web Portal, BOTs
and APIs to Meter installation and commissioning, Consumer Queries and interactions
and BYPL workflows and reporting needs

BSES

8.6.1 Prepaid functionality

The MDMS with the help of the corresponding HES, should be able to switch the
Smart Meter between prepaid and post-paid modes by a simple change in
configuration of the Smart Meter firmware remotely. The following prepaid
functionality shall apply
a. MDMS shall use consumer attributes from Consumer Care System (CCS)
and/or BYPL Billing system to,
i. enrol and setup new prepaid/ post-paid consumers
ii. migrate existing post-paid consumers to prepaid mode and vice versa

Page 141 of 473

b. An appropriate pre-payment application engine shall support the pre-payment
metering capability through the delivered system
c. The prepayment system shall ensure that payment and connection
parameters are stored centrally, and the details are updated to CIS-
CRM/MDMS through consumer portal/ app as per Clause 8.7 of this Section.
Information required by consumer’s Mobile App and web portal are shared in
near real time.
d. Pre-paid system allows consumer to pay/recharge their account through
online. The system should be capable enough to support utilities existing
billing collection counter to be worked as recharge centers. And also there
should be possibility of anytime anywhere recharge system. The system must
be enable consumers to recharge over the multiple systems options like BYPL
billing centers, BYPL websites, third party websites, mobile apps using
credit/debit cards/internet banking and payment wallets.
e. Prepaid consumers shall be provided facility to recharge their account by
logging on to the consumer portal/app as per Clause 8.7 of this Section.
i. The user interface shall be integrated with the present online payment
gateway of the BYPL. Additional payment gateways shall be implemented
if required
ii. The payment gateways shall facilitate payments through on-line banking,
credit cards and payment wallets
f. A prepaid mobile application functionality shall be provided as a recharge
option for android OS and iOS. The consumer portal/ app, shall enable
consumers to recharge as well as view recharge history, existing balance,
daily usage etc
g. Pre-paid system will have close integration with the existing billing system
from beginning. A close integration of MDMS and the existing billing system is
also crucial for smooth transition. Following are the details
BSES

i. When meter is replaced by AMI installation field workforce last reading

is taken and recorded in the WFMS App. This data is submitted to the
existing Billing System for last bill generation. If post paid to pre paid
conversion to be performed on same smart meter, system may consider
last reading date of postpaid bill as effective date of prepaid conversion
and pending days bills to be generated in Smart prepaid module.
ii. Provision for security adjustment conversion into credit balance.
iii. This is the last post-paid bill before meter switch and customer should
clear it as-is. Bidder should suggest better ways to ensure collection of
this last bill dues with any previous credits linked with the old meter. A
zero credit at change from post-paid to pre-paid is idle
iv. Prepaid system should be able to manage the situation of credits getting
transferred from post-paid billing system to new pre-paid billing system
and net metering calculations. It should be possible to convert the
amount into installments for consumer ease and should be updated in
mobile app also.
v. At every recharge this fixed amount (arrear dues installment) will be
deducted towards the pending bill payment till the number of
installments. Provision for charging installments on daily / monthly basis
in prepaid system should be available.
vi. System should be able to provide analytics reports related to recharge
and usage consumer wise. If the BYPL has capability to support the
above analytics in the existing system, pre-paid system would provide
all the required data exchange to enable the same.
vii. Provision for synchronization / reconciliation of billing data with SAP/CIS
system on periodic basis.

Page 142 of 473

h. The system shall periodically monitor the energy consumption of prepaid
consumer and decrease the available credit based on consumption. For this
purpose, the MDMS shall fetch billing data (kWh/kVAh consumption and MD)
at configured intervals2 from the prepaid meter. ToU consumption shall also
be considered if ToU based tariff is applicable to the consumer. The raw billing
data shall be subjected to standard VEE rules before being used to update
recharge balance with the help of applicable tariff slabs. The credit balance is
updated into meter atsuccessful re-charge time.
i. The prepayment application shall use determinants such as minimum fixed
charges, TOU tariffs, slab rates, duties & surcharge while calculating
consumer credit/balance. Fixed charge shall be deducted on daily basis
irrespective of the consumption, even after disconnection of supply and
adjusted in the next transaction.
j. The prepayment system must have native ability to enforce prepaid specific
business rules through implemented rule engine and configuration
management dashboard by administrator without the need for custom
programming or modifications. The tariffs will be implemented by configuring
the various rules in Rule Engine. The Rule Engine must ensure that:
o The tariff is implemented as accurately as is the case for conventionally
billed customers.
o Customers are not restricted to the amount and frequency of Recharges.
o The rule engine must allow for frequent changes in tariff rates and/or
structures without costly logistics and/or inaccurate application of the
tariffs.
k. The rule engine shall operate according to the rates specified in the tariff
l. The prepayment application should be able to automatically apply different
TOU tariffs for future date lines, while calculating consumer credits
m. Intraday (BYPL defined time schedule) meter read processing and updating
BSES

customer account balances

n. Slab tariffs which can be aggregated configurable in day, week, month, bill
cycle
o. Fine granular tariff management (eg. supporting 15min intervals) and real time
rating & charging & updated customer balance also INTRA day
p. The system should send connect/disconnect command based on available
credit as per notified rules & regulations
q. If meter is in non communication from longer period and Interval/Daily read
not available than system shall have provision to consider monthly billing
reads once data is received to the system.
r. System shall have provision to consider different data profiles for billing based
on the requirement
a. Load Profile / Interval Reads (for Intraday billing)
b. Daily Read Profile or Current Billing Profile (for daily billing or Load Profile
data not available)
c. Monthly Billing Profile (for non communicating meter and calculating
monthly special charges like demand charge, Power Factor surcharge
etc.)
s. System shall manage retry attempts for Connection and Disconnection during
allowed window. It should be possible that disconnection schedule can be
managed at MDMS/HES end once command is initiated from Prepayment
module. If in case disconnection is in queue and recharge is done by the
consumer then command should be cancelled and restore order should be
created in parallel.

Page 143 of 473

 t. Priority for reconnection commands shall be higher than disconnection
commands.
u. Prepaid billing module shall have Bill adjustment and Payment cancellation
facility through authorized user login.
v. System shall have provision to restore the disconnected meters in special
situation.
w. Prepaid module shall initiate notifications to consumers on below minimum
conditions
o Low balance notifications
o Disconnection notifications
o Reconnection notifications
o Recharge notifications
o High usage notifications
x. Solution must support a software-only, meter independent prepaid solution (no
tokens or prepaid top-up hardware required at each site)
y. Solution must support revenue assurance/ debt assist services for period
agreed by BYPL and will be configurable across BYPL or specific to the
account / meter
z. Solution must support for sending customer alerts, data processing and
collection of data as per solution requirement
aa. Bidder should have provision for Net Metering/Rooftop Solar and ability to
configure tariffs separately by the BYPL
bb. Bidder must Integrate required BYPL systems as per project required into the
prepay solution such as but not limited to :
a. AMI Head End (AMI/HES)
b. Meter Data Management System(MDMS)
c. Customer Information System (CIS)
d. others BSES

cc. Mobile app shall support integration with Voice controlled device/Smart Home
Devices.
dd. Provide training on system for the BYPL users and training materials for the
BYPL customers

8.6.2 Proposed Prepaid Architecture

Page 144 of 473

8.6.3 Database Software and Licenses

AMISP shall provide relevant database software for Smart Prepaid Billing Module
(SPBM) and Licenses to be provides as per the scope defined, following conditions
to be considered
I. SPBM shall receive consumption / reading details from MDMS / Analytics
Database
II. SPBM database will store consumer wise billing data, recharge information
and transactions performed by SPBM

8.6.4 Prepaid Configurations

a. The system should send low-credit notifications to the consumer when

their balance approaches a pre-configured threshold. Alerts shall initiate on
every recharge, low credit and load connection/disconnection. The alerts
shall be posted on the consumer web Portal/ App in real time and sent
through SMS and email. Consumer should also be alerted through other
mechanisms such as one-time alarm / beep from the meter, LED blinking,
message, etc
b. System shall have UI based tariff configurator,where user can configure
slab wise Electricity Charges, Fixed Charges, Power Factor Charge,
Demand Charges, Monthly Minimum Charges and other taxable
components effective from old and future dates.
c. System shall capable to import tariff configurations from SAP/Billing
application of BYPL.
d. System shall have capability to configure charges to be billed as a whole or
split into preconfigured time period. For example: Demand change or
Power Factor surcharge applicable on last day bill of the month can be
BSES

charged on first day or split into next 30 days.

e. System shall have ability to handle the billing involving retroactive tariff
changes.
f. It shall be possible to configure an “emergency” credit limit in INR as well
as day terms. This emergency credit shall be used as reserved amount
that is consumed when consumer credit is exhausted. The credit amount
shall be adjusted in next recharge transaction Emergency credit can be
configured to individual consumer as well as group of consumer (i.e.
category, sub-category etc.)
g. It shall be possible to configure certain prepaid consumers where auto-
disconnections shall not happen due to negative credit.
h. The pre-payment function shall also have a facility to configure arrear
recovery mechanism to recover arrears from a consumer. Some of the
indicative mechanism to recover the same can be recovery of [X]% from
every recharge amount while the rest goes as charging amount till all the
arrears are recovered. Alternately the arrears may be settled in next [X]
installments as decided by BYPL such that not more than 50% of any
installment shall be adjusted towards arrear
i. System shall have provision to configure holiday calendar and happy hours
to avoid disconnection during specific time window or any day.
j. System shall have provision to configure maximum disconnection
threshold based on total consumer base.
k. System shall have ability for test mode to prevent accidental
disconnections of the meters.
l. System shall have ability for test mode to prevent accidental alerts to the
consumers.

Page 145 of 473

 m. System shall have ability to configure disconnection threshold period for
individual consumer after credit balance goes into negative
i. Number of threshold days of balance in negative
ii. Negative balance value (Emergency Credit) – configurable at consumer
category or individual connection

8.6.5 Prepaid dashboards and reporting features

MIS reports and analytical dashboards including but not limited to following reports:

a. Billed / Unbilled dashboard/report

b. Unbilled with aging
c. Billing exception report (reasons of unbilled)
d. Master data report
e. Amount adjustment report
f. Billing and payment details
g. Disconnected consumers
h. List of Negative balance consumers
i. Pending for connect / disconnect
j. SMS Notification history
k. Audit logging report
l. Inactive consumers report
m. Notification reports
n. Report for consumer having login
o. Consumer risk analysis report

8.7 Consumer Portal/ App BSES

Consumer portal and mobile application shall cover all consumer categories and
category specific features as applicable prior to operational Go-Live. These apps shall
have provision to enable features required to facilitate consumer participation in
Demand Response programs which the BYPL may choose to roll out in future. The
consumer web portal and the mobile application (for smartphone and tablet devices
using latest and commonly available browsers and operating systems and platforms)
shall provide consumers, ready access to features extended by MDMS. The Solution
shall integrate via a user-friendly graphical interface. It shall facilitate self service
capabilities such as usage management, billing, service requests, participation in
energy efficiency programs etc. It shall be noted that the Consumer Portal / App acts
as the bridge between the consumers touch point and the existing BYPL Customer
Care and Billing Systems. It does not replace these legacy systems in place.
Following features shall be supported by Portal / Mobile app:
a) The mobile app and web portal shall support all device form factors such as
mobile, tablet, desktop etc. by recognising the device details automatically.
b) It shall be OS agnostic to operating system and devices (iOS, Android, etc.)
c) It shall work on all standard browsers such as Internet Explorer (IE), Chrome,
Safari, Firefox etc.
d) The application should be modular and scalable a COTS product.
e) The application should support localisation for better user experience.
f) It shall support multiple languages viz Hindi, English and local language(s). Also,
notifications should be sent to consumers in local languages.
g) The user experience of the citizen on the Portal and App shall be similar in terms
of look and feel, navigation, menu and access to preferences and other data.

Page 146 of 473

 h) Menu should have navigation options, not limited to, Home, Settings, Recharge,
notification preferences, usage rates, change password, terms and conditions,
privacy policy, sign out.
i) It shall have search functionality across all the pages.

Software patches, updates, and version upgrades, when they become available for
general release. AMISP should follow industry standard testing and deployment
practices, should be part of ongoing support and maintenance services.

8.7.1 Functional Requirements of Consumer Portal/ App

Web portal and Mobile app for consumers should have minimum following
functionalities:
a) The consumer portal/app shall have a landing Home page. This page shall
provide a brief description about the BYPL, any promotional features or
advertisement for special programs can be placed in this page. Login
Component is provided, and registered users may login using their username
and password. New Users can also register by clicking on the First Time
Users Register link. The Forgot Password link helps the user to retrieve their
password. New users can register by providing their personal information and
setting up of security answers. Forgot passwords can be retrieved or reset
using OTP through registered mobile number or through email address. The
registered users can change their password and account information as well
as registered mobile number through OTP feature.
b) The consumer portal/app shall provide consumers with access to consumer
ID, meter ID, meter type and name plate details, besides other account
information such as account name, address, balance, due, status etc. Any
status message pertaining to the account/s viz. alerts/actions shall be
BSES

displayed here. It shall also provide current and historical consumption in

graphical formats for at least 12 months. A more detailed analysis can be
provided in a tabular format listing meter reading date, reading, consumption,
charges, selected period etc. Consumers shall be able to view interval data,
outage flags, voltage, power quality indications, existing tariffs and incentives
for selected period. Information about different consumer engagement
programs shall also be displayed here.
c) The portal/app shall have the ability to provide option for registering in
online/paper billing to the consumer. There shall be a bill summary page that
shall display bill information in summary and also option for detailed view and
download in pdf format if required by consumer. The use shall be able to pay
bill for single and multiple accounts.
d) The portal/app shall be integrated with existing helpdesk of the BYPL and
have the ability to provide option for recording service requests/complaints
lodged by the consumer as new connection, disconnection, load change,
category change, meter shifting etc. The user can view the service request
status. The user can register complaints viz. power failure, faulty meter,
streetlight outage etc. There shall be option to track status of service requests.
e) Mobile App and Web Portal shall facilitate Chat-bot functionality of the BYPL’s
Help Desk. The portal/ App shall support configuration of notification types via
email/ SMS/ message/ automated call (through BYPL IVRS), of configured
alarms & events.
f) The information on consumer identification no., meter ID, name plate details,
make, type i.e., 1 Phase or 3 Phase, etc. (as per requirement of BYPL) shall
be updated in HES, MDMS, and the consumer portal/app.
g) The consumer Portal/ App shall have the ability to provide the consumer near
real time online views of both usage and cost differentiating high energy usage
Page 147 of 473
 periods, helping consumers to understand electricity usage and cost
information, alerts and notifications and energy savings tips with different
levels of detail. The Portal/ App shall support the view for past electricity
usage, last week’s, yesterday’s, current days or other period etc. as per
selection as well as voltage and power quality indications. The portal/ app
shall provide user friendly access to consumer for their data via graphs and
charts and can download the data into a spreadsheet.
h) The portal/app shall also provide platform for implementation of peak load
management functionality by providing existing tariff & incentives rates,
participation options etc. The portal/app shall also provide consumers interval
data, flags, voltage, power quality indications etc. Show outage information in
map view.
i) There should be different UI and landing pages for different type of consumers
as per the need of BYPL.
j) The Portal/App shall have admin login through which configurable parameters
can be defined like Events/Alerts to be displayed to consumers, banners,
home page content, theme, bulk popup messages to consumers etc.
k) There should be provision to enable system alerts to consumers through
MDMS/SPBM with enable/disable feature in consumer portal/app, consumer
shall have provision for following minimum alertsthrough SMS, E-Mail, In-app,
Push Notifications and On-Screen popups.
i. Demand violation / Demand crossing defined threshold percentage
ii. Daily consumption > 150% (configurable) of last 30 days average
iii. Peak hour consumption > 20% (configurable) of last month peak
consumption
iv. Peak hour consumption > 50% (configurable) of previous day peak
consumption
v. Slab cross over (reaching non subsidized range)
BSES

vi. Consumption > consumer defined range during non occupancy period
vii. Low PF, Earth load event occurrence
l) User interface to consumer Portal/ App to access consumer’s data from
MDMS and Prepaid Billing Module for all authorized consumers shall have
ability for the following functionality but not limited to:
i. View metered data, monthly average usage, current daily/monthly
consumption, maximum demand and other reports
ii. View data according to Time of Use (ToU), day, week, month, year and
season etc.
iii. Update profile information such as mobile number/email etc.
iv. Guest user account/multi-user account access facility for consumer
convenience
v. Initiate request for connection/disconnection
vi. Initiate request to switch between pre-paid and post-paid mode
vii. Initiate service requests for maximum demand updating, meter checking
etc.
viii. Initiate complaints such as Meter not working, supply off etc.
ix. In case on net-metering consumers, user can view data for both import
& export data for user selectable period
x. Can view recharge history, present balance, next possible recharge
date and amount etc.
xi. Historical energy consumption and energy charges during the desired
time period
xii. Facility to recharge their account through the payment gateway
facilitated by the BYPL.
xiii. Estimated consumption and estimated bill amount for the month.
xiv. Comparison with peer consumers

Page 148 of 473

 xv. Average and Max consumption for Daily / Monthly on consumption
pattern
xvi. Download Load survey data in PDF/XLS/CSV
xvii. Power quality pattern for date range with Max/Avg parameters
xviii. On demand reading of Instantaneous data (rate limiting)
xix. Prepaid billing ledger

8.7.2 AMI Solutions for Enhanced Customer Service

BSES

8.8 Smart Meter Operation Centre (SMOC) & WFMS

The Smart Meter Operation Center (SMOC) shall form the fulcrum for AMI deployment
and Operation, accordingly the design, usages, interface integrations with multiple
modules & GUIs and scalability of the System shall be taken care by the AMISP. The
Smart Meter Operation Monitoring Centre shall cater to the needs of the,
 Project Management Team and the
 AMI network operations team

The Smart Meter Operation centre shall be created in the BYPL premises by the
AMISP, for which suitable built-up space shall be provided by the BYPL. The built-up
space to be arranged by the BYPL, shall be properly air conditioned, illuminated, and
adequate for at least five operator workstations and one cabin for a supervisor.

The AMISP is required to suggest a suitable architecture for the Smart Meter
Operation Centre, taking care of the security requirements as described in this
document. AMISP shall establish connectivity between the workstations located at the
Page 149 of 473
 SMOC with that of the cloud-based MDMS-HES system. In addition, the AMISP shall
establish connectivity between the cloud-based MDMS system with BYPL’s existing
Billing system. This will necessitate creation of a VPN tunnel between the two unless it
is decided to migrate the Billing system to the same cloud data centre.

The AMISP must submit the details of the supplied hardware along with the Bid. The
AMISP shall assess the adequacy of hardware specified in the List of Material and
Services& if any additional hardware or higher end hardware configurations are
required to meet all the requirements of the Technical Specifications, the same shall
be included in the offer.
8.8.1 General Requirements for SMOC Applications

SMOC system shall support centralized management and monitoring of activities

like Consumer Indexing, Meter Installation & O&M activity, It is envisaged that this
solution shall use the power of a GIS platform which will further support correct
data collection, workflow optimization and visualization of information / data and
analysis for improved control and accuracy, refer Annexure G for diagram indicates
a high-level deployment (envisioned) of the proposed applications and the users

The proposed Smart Metering Operation Software should have following features
(not limited to):
 The proposed software should have proactive identification of processes,
resource and infrastructure capacity bottlenecks to support business plans for
smart meter rollout. It should also give near real time deeper insights of
Network health and demographic view of Alerts and Events along with RPA
enabled platform catering to volume of Meter Events
 The proposed SMOC software should get seamlessly integrated with Work
BSES

Force Management System to manage the Smart Meter deployment and

Operations in time-bound manner.
 The centralized Monitoring of Smart Meter Operations should have atleast
following dashboards and reporting:
 AMI deployment planning dashboard
 Capacity Plan and automated Ramp up plan
 Alerts and Events Management
 Network Health Monitoring
 Customer Profiling
 Consumption analysis
 SLA Management
 Security Event Management
 Consumer and Consumption analytics
 Prepaid Billing dashboards
 HES and MDMS data availability comparison
 Live MIS reports for quick action based on escalation matrix
 Monitoring of daily Remote Connect/Disconnect
 Representation of Non Communication over map view
 Representation of Power Outages over map view
 Enterprise release management
 AMI solution Cloud infrastructure monitoring (Infra, Server uptime, system
utilization etc)
 AMI application monitoring (HES, MDMS, Analytic, Helpdesk etc)
 End to End monitoring of Smart installation on field
 Daily field operation activity (Faulty meter, Non & never communicating
resolution)
 Network monitoring of Smart Meters connectivity

Page 150 of 473

  Apart from that monitoring of AMI solution critical application webservice and
scheduler
 SMOC application shall be featured with RBAC (Role based access control) to
assign different roles to users

The SMOC will also have the centralized ticketing system to handle the helpdesk
operations from single location and interface with Workforce Management System
(WFMS) and initiate field visit (Installation and operational), allocation of task to
crew member and track response of field activity. Ticking source for SMOC can be
consumer call to call center, ticket created through consumer portal/app, MDMS
auto / individual ticket orinitiated through existing BYPLWSS/helpdesk.

SMOC application shall support following features (not limited to) for ticketing :
 Integrate with CIS/SAP system to receive field activity request initiated from
CIS/SAP and sync changes back after completion of field activity.
 Integrate with MDMS / Mobile App / Existing helpdesk tool / WSS for request
of field visit and sync status / changes back after completion of field activity.
 Creation of different Field Crew members and mapping of job expertise for
each crew
 Assignment of Field Job to appropriate Crew member based on expertise
required for Job
 Verification of Job Status
 Review Job and Reassignment if not approved by Supervisor at SMOC
 Prioritization of Job (in case of multiple jobs assigned to crew)
 Monitoring of Crew Location
 Crew performance reporting
 Job search based on consumer/meter/ticket id
 Tracking history of Jobs at each consumer/meter
BSES

 Job type wise reporting

8.8.2 General Requirements for SMOC Hardware

All hardware shall be manufactured, fabricated, assembled and finished with
workmanship of the highest production quality and shall conform to all applicable
quality control standards of the original manufacturer and the AMISP. All hardware
components shall be new and suitable for the purposes specified.

All workstations and network equipment (routers, firewall etc.) shall be compatible
for remote monitoring using secure Simple Network Management Protocol
(SNMP) Ver. 3.0. All hardware shall support IPv6 simultaneously.

The AMISP shall ensure that at the time of final approval of hardware
configuration and List of Material and Services, all the hardware is as per the
current industry standard models and that the equipment manufacturer has not
established a date for termination of its production. Any hardware changes, except
version upgrade in same series, proposed after contract agreement shall be
subject to the following:
a) Such changes/updates shall be proposed, and approval obtained from the
BYPL along with the approval of Drawings/documents.
b) The proposed equipment shall be equivalent or with better features than the
equipment included in the Contract.
c) Complete justification along with a comparative statement showing the original
and the proposed hardware features/parameters including brochures shall be
submitted to the BYPL for review and approval.
d) Changes/updates proposed will be at no additional cost to the BYPL.

Page 151 of 473

 e) The porting of software shall be at no additional cost in case of replacement of
hardware during the contract period.

8.8.3 Minimum Technical Requirements for SMOC Hardware

The smart meter operation centre shall be equipped with the following minimum
hardware components:

S. No. Item Name Qty. UoM

1 46 inches full HD (1920*1080) resolution professional
8 Lot
large format LED Video Wall display panel
2 4*4 Seamless Matrix Switcher / Multi-scalar 2 Lot
3 HDMI Audio De-Embedder 2 Lot
4 Powered Sound Bar with noise cancellation features 2 Lot
5 Room Media Controller 2 Lot
6 Mobile / Tablet for wireless controlling 2 Lot
7 Cables, accessories and connector 2 Lot
8 Push-Pull video wall mount kit for 46-inch display 8 Lot
9 Design, engineering, supply, installation,
documentation and one-time user orientation charges 1 Lot
for two (2) video walls
10 17'' Operator Workstations 6 Lot
11 1 Gbps dual redundant local area network 1 Lot
12 Internet router with at least 48 no’s 1 Gbps LAN ports
and redundant at least 2 Gbps internet ports 1 Lot
supporting IPsec, and SSLVPN capability
13 A3/A4 size laser jet B/W printer with LAN interface 1 Lot
14 A4 size ink jet colour printer with LAN interface
BSES
1 Lot
15 Dual redundant online UPS to support the load of the
above-mentioned equipment with minimum 2 hours 1 Lot
backup
16 Any other item required for successful Operation and
commissioning of the Display structure (to be
1 Lot
corroborated with proper documentation and
approval of BYPL)
17 Firewall and intrusion protection system.

8.8.4 Security Operation Center (SOC) for AMI System

AMISP to setup, operate and manage Security Operations Center (SoC) including
supply and commission of relevant technologies / tools required. The selected
vendor will be responsible for providing comprehensive, proactive security services
for AMI Infrastructure provided under this contract.

[Link] SOC Services Scope

A. 24x7 Monitoring and Incident Response:
 The SOC must provide round-the-clock monitoring of the organization's IT
infrastructure, applications, network, and security assets.
 Continuous real-time detection and response to cyber security incidents,
threats, and vulnerabilities.

B. Threat Intelligence and Analytics:

 Access to global threat intelligence feeds and proactive threat hunting.

Page 152 of 473

  Integration of threat intelligence with the organization's security information
and event management (SIEM) solution.
 Trend analysis of potential threat vectors and emerging risks.

C. Vulnerability Management:
 Regular scanning and assessment of vulnerabilities within the
environment.
 Recommendations for remediation and patch management.

D. Security Incident Management:

 Incident management processes including detection, analysis,
containment, eradication, and recovery.
 Timely and coordinated response to security incidents including internal
and external communications.

E. Event Log Collection and Analysis:

 Centralized collection and correlation of security event logs.
 Retention and analysis of logs to identify security incidents or trends.

F. Compliance Monitoring:
 Monitoring and reporting on compliance with industry-specific standards
and regulations
 Support for audits and regulatory compliance requirements.

G. Forensic Capabilities:
 Ability to conduct digital forensics and investigation in case of data
breaches or incidents. BSES

 Preparation of comprehensive forensic reports.

8.8.5 Workforce Management System (WFMS)

Field app shall be made available to enable the crew member to install the app on
his device.

The log-in credentials will be assigned to crew member for authorized login and
OTP based validation to be enabled. The Crew member shall be able to
synchronize the jobs assigned to him through SMOC. Based on the Job Type
corresponding fields shall be rendered in the device with clear segregation
between the Read-Only Fields, Mandatory fields and Optional fields to be entered
by the crew member for changing the status of the Job. If the device is online, the
status can be communicated directly into the server or there shall be a batch Sync-
Out Process where once the Crew reaches a location where he has the required
signal strength, he can push the status of his jobs to the server.
Other Device Specific Features are
1) The App shall have the ability to save offline Map Views during the Sync-In
Process.
2) The App shall have OTP based Authentication mechanism as an option.
3) The App shall have the ability to send a Remark against a Job without change
in any status of the job. Such Remarks shall appear as special messages to the
Supervisor in SMOC.
4) The App shall support process for Meter Installation and operational activity like
(Meter replacement, NIC replacement, SIM replacement, Non Communication
verification etc.)
5) The App shall support Meter Installation as requirement mentioned in Clause
12 of this section and capture location coordinate.

Page 153 of 473

 6) The App shall support Operations and Maintenance as requirement mentioned
in Clause 13 of this section.
7) The App shall provide feature to ping meter by interfacing HES so that during
site installation/operational activity Crew can validate network status.
8.9 System Software, Cloud and Database Requirements

This section describes the standards and characteristics of system software such as
operating system, database and support software (compilers, DBMS, display
development, network utilities, report generation, diagnostics and backup utilities)
provided by AMISP and the original software manufacturer as necessary to support the
functioning of AMI Applications systems. All the system software to be used for the
present scope of work shall have valid license(s).

8.9.1 Software Standards

All software provided by the AMISP under this RFP, including the operating system,
database and support software, shall comply with the industry-accepted software
standards. In areas where these organizations have not yet set standards, the
software shall comply with those widely accepted de-facto open standards put forth by
industry consortiums, such as Open Software Foundation (OSF) and X/Open. The
AMISP shall commit to meet the "open systems" objective promoted by industry
standards groups.

[Link] Design and Coding Standards for AMI Applications and Utilities

These provisions are applicable for both software applications and operating systems
and would address program features that must be contained in software for the
BSES

product to meet the standards.

a) When software is designed to run on a system that has a keyboard, product
functions shall be executable from a keyboard where the function itself or the result
of performing a function can be distinguished textually.
b) A well-defined on-screen indication of the present focus shall be provided that
moves among interactive interface elements as the input focus changes.
c) Applications shall not override user selected contrast and colour selections and
other individual display attributes.

When animation is displayed, the information shall be displayable in at least one non-
animated presentation mode at the option of the user

[Link] Applications

All components of AMI application system shall be maintainable by owner using the
supplied software utilities and documentation. The software design and coding
standards of the system shall address the followings:
a) Expansion: Software shall be dimensioned to accommodate the size of AMI
application system as given in List of Material and Services (as mentioned in
this RFP) and AMI project areas under clause 3 of Section 6.
b) Modularity: Software shall be modular i.e. functionally partitioned into discrete,
scalable, reusable modules consisting of isolated self-contained functional
elements and designed for ease of change. The system shall make maximum
use of common industry standards for interfaces.
c) User-Directed Termination: Functions taking long execution times shall
recognize and process user requests to abort the processing.

Page 154 of 473

 d) 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 Relational Database Management Systems (RDBMS)
including Oracle, Microsoft SQL Server and MySQL.
e) Programming Languages: The software shall be written using high level ISO or
ANSI standard programming languages.
All applications shall be designed with sufficient background logs which capture
various level of errors encountered (warning, fatal, informational) while executing, so
that the same can be reviewed and attended to.

[Link] 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.

In order to facilitate cyber security requirements including patch management,

common operating system is preferable to be used by all server nodes within the AMI
application including MDMS/HES servers. This is also to minimize the maintenance.
All licenses for Operating System and other application software shall be supplied by
the AMISP and shall be valid throughout the contract period.

[Link] Time and Calendar Feature

The AMI application & other servers shall maintain time and calendar for use by
various software applications. The internal clocks of all servers and workstation
BSES

consoles shall be automatically synchronized on Network Time Protocol (NTP)

protocol. The calendar shall be customizable for working hours, holidays, weekends
etc. The holidays, including type of days, shall be entered for each year at the
beginning of the year and shall be recognized by all applications.

[Link] Remote Diagnostic

Remote Diagnostic facility with necessary hardware as required shall be provided for
communication between the AMI application system at the cloud data centre and the
SMOC for the diagnosis of hardware & software problems. The login shall be protected
by a username & password entry. An automatic logging and intimation shall be
provided to inform authorized person from AMISP/BYPL on such events of remote
access and diagnosis.

[Link] Development System as a Test Bench

A Development system independent of the production environment shall be defined at
the cloud data centre which shall provide testing facility for integration of
changes/modifications of the AMI application and new field devices before putting it
online with Real-time system. This Development system shall be on a VLAN separated
from the production VLAN and shall be self-sufficient to carryout testing of changes/
modifications.

[Link] Network Communication

The network communications software shall use a standard network protocol such as
TCP/IP, UDP etc. and shall support IPv6. The software shall link dissimilar hardware

Page 155 of 473

 nodes such as local and remote workstations and peripheral devices into a common
data communication network allowing communications among these devices. The
network communication software shall includenetwork security, security management,
patch management and network services of the AMI system. Network communication
software shall have scalability feature as envisaged.

8.9.2 Cloud Service Providers (CSP)

This section mentions key requirements from the Cloud Service Provider (CSP).
AMISP shall be responsible to provide the services of CSP.

[Link] General Conditions

The cloud data centre shall have to comply with requirements of tier III category
which applies to a concurrently maintainable site infrastructure with redundant
capacity components and multiple independent distribution paths serving the
critical environment. All IT equipment shall be dual powered. The following general
conditions will apply:
a) Only GI (MeghRaj) cloud services or MeiTy empanelled Cloud services should
be used.
b) One of the most critical issues in the Cloud Service implementation is the
security of the data. It is the responsibility of the AMISP to define the security
services that need to be implemented for their workloads depending on the
nature of the applications / data hosted on the cloud.
c) AMISP need to ensure that the CSPs facilities/services are compliant to
various security standards and should be verified by third party auditors.
d) CSP should suitably address all the potential risks and issues in cloud
implementation including data security and privacy, increased complexity in
integration with existing environments, vendor lock-in, application portability
BSES

between different platforms, exit management / Transition-Out Services etc.

e) The AMISP shall be responsible for providing the cloud data centre services. It
shall be up to the AMISP, to identify the critical service agreements with the
concerned cloud data centre provider in order that the AMISP can meet and
sustain the SLA for the AMI project as per Clause 14of this Section.
f) The AMISP shall be primarily responsible for services delivered by CSP or its
MSP.
g) All Services including data should be hosed in India
h) Exit Management / Transition-Out Services -The responsibilities of the CSP
during the Exit Management Period need to be agreed upon with the BYPL
and they should assist the BYPL in migrating the data etc.
i) The responsibilities of CSP include migration of the data, content and any
other assets to the new environment or on alternate cloud service provider’s
offerings and ensuring successful deployment and running of the BYPL’s
Solution on the new infrastructure
j) The ownership of the data generated upon usage of the system, at any point of
time during the contract or expiry or termination of the contract, shall rest
absolutely with the BYPL.

The AMISP may also choose to procure the following Managed Services (O&M –
Cloud Services) from a Managed Service Provider (MSP) in addition to the cloud
services to handhold the department in managing the operations on the cloud. The
scope of MSP may include:
a) Migration of Existing Applications to Cloud / Deploying of new applications;
b) Operations & Maintenance Services on Cloud (e.g., Resource Management,
User Administration, Security Administration & Monitoring of Security Incidents,

Page 156 of 473

 Monitoring Performance & Service Levels, Backup, Usage Reporting and
Billing Management)
c) Exit Management & Transition-out Services, etc.

[Link] MeitY’s Guidelines and Compliances

While the security, storage, data and compliance tools are provided by the CSP, it
is the AMISP’s responsibility to ensure that the CSPs facilities/services are certified
to be compliant to standards.
In the MeitY’s guidelines to Government Departments on Adoption / Procurement
of Cloud Services, the following are included as essential certification by CSP.
AMISP also needs to ensure that the CSPs facilities/services are certified to be
compliant to the following standards (indicative list provided below):
a) Only GI (MeghRaj) cloud services or Meity empanelled Cloud services should
be used.
b) ISO 27001 - Data Center and the cloud services should be certified for the
latest version of the standards towards information security management
system
c) ISO/IEC 27017:2015-Code of practice for information security controls based
on ISO/IEC 27002 for cloud services and Information technology
d) ISO 27018 - Code of practice for protection of personally identifiable
information (PII) in public clouds.
e) ISO 20000-1 – Information Technology service management system
requirements
f) TIA942 A/B &/or Uptime Tier III or higher – Telecommunication infrastructure
standard for Data Centre
g) Payment Card Industry (PCI) DSS - compliant technology infrastructure for
storing, processing, and transmitting credit card information in the cloud.
h) Cloud Service provider should be TISAX certified and ISO 27018 (Info Sec in
BSES

Cloud) TISAX: Trusted Info Sec Security Exchange.

i) The CSP should be compliant to IT Act 2000 and Amendments, Data Privacy
(Whenever released, Cyber Security Guideline issued by CEA\MoP.

[Link] Functional Requirements of the CSP

[Link].1 Operational Management

a) CSP should provide access of cloud virtual machines either by SSH in case
of Linux and RDP in case of Windows servers.
b) CSP should enable BYPL to get console access of cloud virtual machine
from portal and perform operations. There should be facility to view
resource type-wise (VM, database, storage etc.) quota usage. It should be
possible to configure automated alerts when the threshold of estimated
quota is reached.
c) CSP should upgrade its hardware time to time to recent configuration to
delivery expected performance for this Project.
d) Investigate outages, perform appropriate corrective action to restore the
hardware, operating system, and related tools.
e) CSP should manage their cloud infrastructure as per standard ITIL
framework in order to delivery right services to Project.
f) The CSP should allow different users with different level of access on CSP
portal. For example, billing user should not be able to provision resources
or delete any resources.
g) The CSP should allow quota management for each department/ISV/Group.
The resources to specific department/group/ISV should be as per allocated
quota only. If there is any request for more than quota request, then it
should be sent as request to admin.
Page 157 of 473
 h) The AMISP should propose Disaster Recovery Data Center site which lie in
different physical locations (100 KM Apart) that of the proposed data center
OR AMISP should propose DC_DR from different physical locations
supporting Active – Active (Synchronous) Arrangement. The AMISP shall
be fully responsible for ensuring services in case of natural and or any
disaster supporting contractual RTO/ RPO requirement.

[Link].2 Compatibility Requirements

a) CSP must ensure that the Virtual Machine (VM) format is compatible with
other cloud provider.
b) CSP should give provision to import cloud VM template from other cloud
providers.
c) CSP should ensure connectivity to and from cloud resources used for this
project is allowed to/ from other cloud service providers if required.
d) The CSP should offer a native integration with Home Area Network
Devices or applications (like Alexa/Google Devices/Apple Devices etc.)

[Link].3 Cloud Network Requirement

a) CSP must ensure that the non-production and the production environments
are in separate VLANs in the cloud so that users of the two environments
are separated.
b) CSP must ensure that cloud VM are having private IP network assigned.
c) CSP must ensure that all the cloud VMs are in same network segment
(VLAN) even if they are spread across multi data centres of CSP.
d) CSP should ensure that cloud VMs are having Internet and Service
Network (internal) vNIC cards.
e) 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
BSES

communication.
f) In case of scalability like horizontal scalability, the CSP should ensure that
additional require network is provisioned automatically of same network
segment.
g) CSP must ensure that public IP address of cloud VMs remains same even
if cloud VM gets migrated to another data centre due to any incident.
h) CSP must ensure that public IP address of cloud VMs remains same even
if cloud VM network is being served from multiple CSP data centres.
i) CSP must ensure that the public network provisioned for cloud VMs is
redundant at every point.
j) CSP must ensure that cloud VMs are accessible from BYPL private
network if private links P2P/MPLS is used by BYPL
k) CSP must ensure that there is access to cloud VMs if BYPL requires to
access it using IPSEC/SSL or any other type of VPN.
l) CSP should ensure that cloud VM network is IPV6 compatible.
m) CSP should ensure use of appropriate load balancers for network request
distribution across multiple cloud VMs.

[Link].4 Cloud data centre specifications

a) All the physical servers, storage and other IT hardware from where cloud
resources are provisioned for this project must be within Indian data
centres only.
b) Selection of DC-DR site architecture shall be in accordance with applicable
laws including but not limited to the “Disaster Recovery Best Practices”
guidelines issued by the Ministry of Electronics & Information Technology
(MEITy) and as amended from time to time”.
c) The CSP data centres should have adequate physical security in place.

Page 158 of 473

 d) The Data Centre should conform to at least Tier III standard (preferably
certified under TIA 942 or Uptime Institute certifications by a 3rd party) and
implement tool-based processes based on ITIL standards.

[Link].5 Cloud Storage Service Requirements

a) CSP should provide scalable, dynamic and redundant storage.
b) CSP should offer provision from self-provisioning portal to add more
storage as and when require by respective Utilities.
c) 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.
d) CSP should have block disk offering as well as file/object disk offering to
address different kind of Project needs.
e) The CSP should retain AMI data for 5 years and data more than 5 years to
be archived

[Link].6 Cloud Security Requirements

a) CSP should ensure there is multi-tenant environment and cloud virtual
resources of this project are logically separated from others.
b) CSP should ensure that any OS provisioned as part of cloud virtual
machine should be patched with latest security patch.
c) In case, the CSP provides some of the System Software as a Service for
the project, CSP is responsible for securing, monitoring, and maintaining
the System and any supporting software.
d) CSP should implement industry standard storage strategies and controls
for securing data in the Storage Area Network so that clients are restricted
BSES

to their allocated storage

e) CSP should deploy public facing services in a zone (Secure DMZ) different
from the application services. The Database nodes (RDBMS) should be in
a separate zone with higher security layer.
f) CSP should give ability to create non-production environments and
segregate (in a different VLAN) non-production environments from the
production environment such that the users of the environments are in
separate networks.
g) CSP should have built-in user-level controls and administrator logs for
transparency and audit control.
h) CSP cloud platform should be protected by fully managed Intrusion
detection system using signature, protocol, and anomaly-based inspection
thus providing network intrusion detection monitoring.

[Link].7 Data Management

a) CSP should clearly define policies to handle data in transit and at rest.
b) CSP should not delete any data at the end of agreement without consent
from BYPL.
c) In case of scalability like horizontal scalability, the CSP should ensure that
additional generated data is modify/deleted with proper consent from
BYPL.

[Link].8 Managed Services

a) Network and Security Management:

Page 159 of 473

 i. Monitoring & management of network link proposed as part of
thisSolution. Bandwidth utilization, latency, packet loss etc.
ii. Call logging and co-ordination with vendors for restoration of links, if
need arises.
iii. Addressing the ongoing needs of security management including, but
not limited to, monitoring of various devices / tools such as firewall,
intrusion protection, content filtering and blocking, virus protection,
and vulnerability protection through implementation of proper patches
and rules.
iv. Ensuring that patches / workarounds for identified vulnerabilities are
patched / blocked immediately
v. Ensure a well-designed access management process, ensuring
security of physical and digital assets, data and network security,
backup and recovery etc.
vi. Adding/ Changing network address translation rules of existing
security policies on the firewall
vii. Diagnosis and resolving problems related to firewall, IDS/IPS.
viii. Managing configuration and security of Demilitarized Zone (DMZ)
Alert / advise BYPL(s) about any possible attack / hacking of
services, unauthorized access / attempt by internal or external
persons etc.
b) Server Administration and Management:
i. Administrative support for user registration, User ID creation,
maintaining user profiles, granting user access, authorization, user
password support, and administrative support for print, file, and
directory services.
ii. Installation/ re-installation of the server operating systems and
operating system utilities
BSES

iii. OS Administration including troubleshooting, hardening, patch/

upgrades deployment, BIOS & firmware upgrade as and when
required/ necessary for Windows, Linux or any other O.S proposed
as part of this solution whether mentioned in the RFP or any new
deployment in future.
iv. Ensure proper configuration of server parameters, operating systems
administration, hardening and tuning
v. Regular backup of servers as per the backup & restoration
vi. Managing uptime of servers as per SLAs.
vii. Preparation/ update of the new and existing Standard Operating
Procedure (SOP) documents on servers & applications deployment
and hardening.

[Link].9 Business Continuity Plan & Backup Services

As part of a business continuity plan, the BYPL has made a business impact
analysis in the event of loss of AMI applications running in the cloud and
consequent loss of data to come up with a management plan for the associated
risk to business operations. Central to this risk management strategy, the BYPL
has defined the following target objectives:
a) Recovery Time Objective (RTO): Duration of time and a service level
within which a business process must be restored after a disruption in order
to avoid unacceptable consequences associated with a break in continuity
of service. The RTO of [4 hours] shall be met by infrastructure redundancy
and failover.
b) Recovery Point Objective (RPO): Interval of time that may pass during a
disruption before the quantity of lost data during that period exceeds the
business continuity plan’s maximum allowable threshold. The RPO of [2

Page 160 of 473

 hours] shall be met by a suitable backup and replication strategy of
operational data / application. The RPO shall define how fast the replicated
data / application can be made available to the target system after a
disruption strikes.
With these two objectives, the CSP shall provide the following:
a) CSP must provide backup of cloud resources. The backup tool should
be accessible
b) To perform backup and restore management as per policy &
procedures for backup and restore, including performance of daily,
weekly, monthly, quarterly and annual backup functions (full volume
and incremental) for data and software maintained on the servers and
storage systems using Enterprise Backup Solution.
c) Backup and restoration of Operating System, application, databases
and file system etc. in accordance with defined process / procedure /
policy. Monitoring and enhancement of the performance of scheduled
backups, schedule regular testing of backups and ensure adherence to
related retention policies
d) Ensuring prompt execution of on-demand backups & restoration of
volumes, files and database applications whenever required.
e) Real-time monitoring, log maintenance and reporting of backup status
on a regular basis. Prompt problem resolution in case of failures in the
backup processes.
f) Media management including, but not limited to, tagging, cross-
referencing, storing (both on-site and off-site), logging, testing, and
vaulting in fireproof cabinets if applicable.
g) Generating and sharing backup reports periodically
h) Coordinating to retrieve off-site media in the event of any disaster
recovery BSES

i) Periodic Restoration Testing of the Backup

j) Maintenance log of backup/ restoration
k) CSP should provide network information of cloud virtual resources.
l) CSP must offer provision to monitor network uptime of each cloud VM.

[Link].10 Web Application Firewall (WAF) as Service

a) Cloud platform should provide Web Application Filter for OWASP Top 10
protection
b) CSP WAF should be able to support multiple website security.
c) CSP WAF should be able to perform packet inspection on every request
covering the 7th layers.
d) CSP WAF should be able to block invalidated requests.
e) CSP WAF should be able to block attacks before it is posted to website.
f) CSP WAF should have manual control over IP/Subnet. i.e., Allow or Deny
IP/Subnet from accessing website.
g) The attackers should receive custom response once they are blocked.
h) CSP must offer provision to customize response of vulnerable requests.
i) CSP WAF should be able to monitor attack incidents and simultaneously
control the attacker IP.
j) CSP WAF should be able to Grey list or Backlist IP/Subnet.
k) CSP WAF should be able to set a limit to maximum number of
simultaneous requests to the web server & should drop requests if the
number of requests exceed the threshold limit.
l) The WAF should be able to set a limit to maximum number of simultaneous
connections per IP. And should BAN the IP if the threshold is violated.
m) CSP WAF should be able to set a limit to maximum length of path to URL.
n) CSP WAF should be able to limit maximum size of request to Kilobytes.

Page 161 of 473

 o) CSP WAF should be able to limit maximum time in seconds for a client to
send its HTTP request.
p) CSP WAF should be able to BAN an IP for a customizable specified
amount of time if the HTTP request is too large.
q) CSP WAF should be able to limit maximum size of PUT request entity in
MB
r) The WAF should be able to close all the sessions of an IP if it is ban.
s) CSP WAF should be able to ban IP on every sort of attack detected and
the time span for ban should be customizable. There should be a custom
response for Ban IP.
t) The Customizable Dashboard should show a graphical representation not
limited to following :
i. Top 5 Attacked Websites.
ii. Top 5 Attacking IP.
iii. Top 5 Attack types.
iv. Top 5 Attacked URLs.
u) For analysis purpose the customizable Dashboard should contain following
information:
i. Number of requests to web server.
ii. Number of attacks.
iii. Number of Attackers.
iv. Types of error messages and on. of error messages sent to the
users.
v. Total Bytes sent during transaction

[Link].11 Database Support Service

a) Installation, configuration, maintenance of the database (Cluster &
Standalone). BSES

b) Regular health check-up of databases.

c) Regular monitoring of CPU & Memory utilization of database server, Alert
log monitoring & configuration of the alerts for errors.
d) Space monitoring for database table space, Index fragmentation monitoring
and rebuilding.
e) Performance tuning of Databases.
f) Partition creation & management of database objects, Archiving of
database objects on need basis.
g) Patching, upgrade & backup activity and restoring the database backup as
per defined interval.
h) Schedule/review the various backup and alert jobs.
i) Configuration, installation and maintenance of Automatic Storage
Management (ASM), capacity planning/sizing estimation of the Database
setup have to be provided and taken care by the AMISP.
j) Setup, maintain and monitor the ‘Database replication’ / Physical standby
and Assess IT infrastructure up-gradation on need basis pertaining to
databases

[Link] Security

Further, commercial CSPs offer cloud services to multiple consumers. In such an

environment, the security controls and compliance to various standards (Including
ISO 27001, ISO 27017, and ISO 27018) should be verified by third party auditors.
Third-party certifications and evaluations provide assurance that effective physical
and logical security controls are in place.

Page 162 of 473

Although, the Cloud Service Providers (CSPs) offer assurances of effective
physical and logical security controls through the third-party certifications such as
ISO 27001, ISO 27017, ISO 27018, etc. and also may provide a host of security
services such as encryption, web application firewall, etc., it is the responsibility of
the AMISP to define the security services that need to be implemented for their
workloads depending on the nature of the applications / data hosted on the cloud.

Now a days, CSPs offer tools and features to help consumers to meet their
security objectives concerning visibility, audit ability, controllability, and agility.
These tools and features provide basic but important security measures such as
Distributed Denial of Service (DDoS) protection and password brute-force
detection on CSP’s accounts.
However, the following basic security features should be ensured by any CSP-
a) Strong encryption capabilities for data in transit or at rest
b) Firewalls – instance and subnet levels
c) Identity and Access Management (IAM): Control users' access to cloud
services. Create and manage users and groups, and grant or deny access
d) Managed Threat Detection: Managed threat detection service that provides
you with a more accurate and easy way to continuously monitor and protect
your cloud accounts and workloads
e) Managed DDoS Protection: Managed Distributed Denial of Service (DDoS)
protection service that safeguards web applications running on cloud.
f) Web Application Firewall: Helps protect your web applications from common
web exploits that could affect application availability, compromise security, or
consume excessive resources.
g) Key Management Service (KMS): Managed service that makes it easy for you
to create and control the encryption keys used to encrypt your data
h) Certificate Manager: Easily provision, manage, and deploy Secure Sockets
BSES

Layer/Transport Layer Security (SSL/TLS) certificates.

i) Cloud HSM: Meet regulatory compliance requirements for data security by
using dedicated Hardware Security Module (HSM) appliances within the
Cloud.
j) Inspector: Automated security assessment service that helps improve the
security and compliance of applications deployed on cloud
k) Organizations: Policy-based management for multiple consumer accounts.
With Organizations, you can create groups of accounts and then apply policies
to those groups.

CSPs also offers access to additional third-party security tools (e.g., IDS / IPS,
SIEM) to complement and enhance the consumers’ operations in the Cloud. The
third-party security tools complement existing Cloud services to enable consumers
to deploy a comprehensive security architecture. These security tools on cloud are
equivalent and identical to the existing controls in an on-premises environment.

The AMISP needs to review and validate the security configurations, review the
notifications and patches released by the CSP and validate that the same is being
taken into consideration during operations, confirm that the audit trails (e.g., who is
accessing the services, changes to the configurations, etc.) are captured for
supporting any downstream audits of the projects by the finance or audit
organization such as STQC.
Cyber Security

Page 163 of 473

[Link] Reporting

Further, the AMISP should insist on the following regular reporting by CSP during
the contract:
a) Availability of the cloud services being used
b) Summary of alerts that are automatically triggered by changes in the health of
those services.
c) Summary of event-based alerts, providing proactive notifications of scheduled
activities, such as any changes to the infrastructure powering the cloud
resources
d) Reports providing system-wide visibility into resource utilization, application
BSES

performance, and operational health through proactive monitoring (collect and

track metrics, collect and monitor log files, and set alarms) of the cloud
resources
e) Auto-scaling rules and limits
f) In case of any un-authorized access, the Agency should provide logs of all user
activity within an account, with details including the identity of the API caller, the
time of the API call, the source IP address of the API caller, the request
parameters, and the response elements returned by the cloud service. This is
required to enable security analysis, resource change tracking, and compliance
auditing
g) Report of all the provisioned resources and view the configuration of each.
h) Summary of notifications, triggered each time a configuration changes
i) Incident Analysis in case of any un-authorized configuration changes.
j) Summary of alerts with respect to security configuration gaps such as overly
permissive access to certain compute instance ports and storage buckets,
minimal use of role segregation using Identity and Access Management (IAM),
and weak password policies
k) Summary of security assessment report that identifies the possible
improvements (prioritized by the severity) to the security and compliance of
applications deployed on cloud
l) Report on upcoming planned changes to provisioning, either possible
optimizations, if any, indicating how the underutilized services can be reduced
to optimize the overall spend, or required enhancements (e.g., upgrade to
additional storage) to meet the service levels defined in the RFP.

8.9.3 Database
[Link] Initial Database Generation

Page 164 of 473

 Development Tools
The AMISP shall provide all necessary software tools for the development and
maintenance of the databases required for AMI application.

This tool shall be capable of managing the entire system database. The
database development software tool delivered with the system shall be used to
generate, integrate and test the database. The system must support export of
data into XML format.

The database development tool shall facilitate exchange of both incremental

and full data in standard exchange format. The product should have facility to
export and import databases from different vendors applications.

[Link] Management
The database manager shall locate order, retrieve, update, insert, and delete
data; ensure database integrity; and provide backup and recovery of database
files. The database manager shall generate and modify all AMI application data
by interfacing with all database structures. In systems with a distributed
database, the database manager shall have access to all portions of the
database wherever stored.
Execution of the database manager in any server of the system shall not
interfere with the on-line functions of AMI applications including the normal
updating of each server's real-time database. In a primary server, database
editing shall be limited to viewing functions, database documentation functions
and functions that change the contents but not the structure of the database.
Editing the on-line database shall not affect the operation of the primary/backup
configuration. BSES

The database manager shall include the mechanisms, in both interactive and
batch processing modes, to perform the following functions:
a) Add, modify and delete database items and data sources such as data
links, and local I/O.
b) Add, modify and delete application program data
c) Create a new database attribute or new database object
d) Resize the entire database or a subset of the database
e) Redefine the structure of any portion of the database.

The AMISP shall be required to provide whether they require or impose any
particular hardware and database management techniques to achieve above
functionality.

[Link] Tracking Changes

The database manager BYPL shall maintain Audit trail files for all changes
made by all users (both online/off-line). The audit trails shall identify each
change including date and time stamp for each change and identify the user
making the change. Audit trail of past [1] year edit operations shall be
maintained.

[Link] Integration
The System should support exchange of data from BYPL’s computerized billing
& collection, consumer indexing and asset mapping systems residing at
different servers.

Page 165 of 473

8.9.4 Display Generation, Management and Integration (Display Management
and Reporting)

The AMISP shall provide necessary software tools preferably browser based for
the generation, management and Integration of AMI application displays.

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

Displays shall be generated in an interactive mode. The user shall be able to

interactively:
a) Develop display elements
b) Link display elements to the database via symbolic point names
c) Establish display element dynamics via database linkages
d) Define linkages to other displays and programs
e) Combine elements and linkages into display layers
f) Combine display layers into single displays.
All workstation features and all user interface features defined in this
specification shall be supported by the display generator software.

The display generator shall support the addition, deletion and modification of
BSES

segments, including the merging of one segment with another to create a new
segment.

Displays shall not be limited by the size of the viewable area of the screen.

The displays shall be constructed from the display elements library. The display
definition shall allow displays to be sized to meet the requirements of the AMI
application for which they are used. The display generation software shall allow
unbroken viewing of the display image being built as the user extends the size
of the display beyond the screen size limits.

The display generator shall support the integration of new and edited displays
into the active display library. During an edit session, the display generation
software shall allow the user to store and recall a partial display. To protect
against loss of display work when a server fails, the current work shall be
automatically saved every five minutes (user adjustable) to an auxiliary
memory file.

The display generator shall verify that the display is complete and error-free
before integrating the display into the active display library. It shall not be
necessary to regenerate any display following a complete or partial system or
database generation unless the database points linked to the display have
been modified or deleted.

The system shall generate reports for all the modules in user-defined formats.
The system will have a graphical user interface with a capability for generating
customized reports, apart from the regular ones mentioned above, as per the

Page 166 of 473

 requirement of management and operations staff. Display of statistical data
shall be presented additionally in graphical formats such as bar- graph/pie
diagram etc. for convenience of analysis.

8.9.5 Software Utilities

AMISP shall supply all software utilities used to develop and maintain these
software, whether or not specifically described by this Specification. The
software utilities shall operate on-line (in background mode) without
jeopardizing other application functions running concurrently. BYPL software
shall be accessible from workstations, processor terminals and servers.

8.9.6 Auxiliary Memory Backup BYPL

Software BYPL, to take back-up of auxiliary memory files of server and
workstation onto a user- selected archival device such as SAN, shall be
installed. Backup shall be maintained for the entire duration of contract period.
The backup BYPL shall allow for user selection of the files to be saved based
on:
a) Server and workstation
b) File names (including directory and wildcard designations)
c) File creation or modification date and time
d) Whether or not the file was modified since the last backup.

Further a BYPL for taking image backup of auxiliary memory files of the
Servers and workstations shall be provided. The BYPL shall allow restoration of
the servers/workstation from this image backup without requiring any other
software. An image backup of the as built system of each of the Servers and
workstations shall be provided on a user-selected archival device such as SAN,
which shall be used to restore the system. Automatic full or incremental back
BSES

up capability of selected systems at user defined intervals shall be provided. It

should be possible to restore or recover any software/system at a selected time
from backup.

[Link] On-Line Monitoring Diagnostics BYPL

On-Line monitoring diagnostic programs shall be provided for verifying the
availability of the backup equipment and for limited testing of devices without
interfering with on-line operations of AMI application system or the failover
capability of the devices.

Redundant communication line interface equipment shall be tested by

periodically retrieving data over these lines and checking for the ability to
communicate with the redundant channel for any errors.

Designated backup server(s) and associated auxiliary memories shall be

automatically tested for proper operation to ensure they are ready if needed for
a failure over contingency. Any failure to perform diagnostic functions correctly
shall cause an alarm to be issued.

[Link] Data Exchange Utilities

Facility of data export and import between this system and external systems
shall be provided through web services.

[Link] Other BYPL Services

AMI Application management shall include the following BYPL services:
a) Loading and storage of information from labelled portable media storage
units as dictated by the requirements of this specification.

Page 167 of 473

 b) Preparation of .pdf output for the displays/reports available in the AMI
Application system. It should also be possible to export all the reports to
any MS-Office format.
c) Displays and Reports for Web server -The AMISP shall provide utilities for
preparing displays and reports suitable for Web publishing. These utilities
shall be used to generate, all required displays and reports from the system
displays and reports, automatically (without requiring rebuilding).
d) Online access to user and system manuals for all software products (e.g.,
Operating System and Relational Database Software) and AMI applications
shall be provided with computer system
e) Antivirus Software - All computers and firewalls shall be provided with the
latest antivirus software as on date of supply. The antivirus software shall
have the capability of having its virus definitions updated from time to time.
The AMISP shall be responsible for the maintenance & update of the
antivirus software during the contract period.
f) Software Upgrade-The AMISP shall be responsible for the maintenance &
update of the patches and signatures of operating system, applications
(AMI Applications) system and Web based System up to the contract
period.
g) Automated patch management and anti-virus tools shall be provided to
expedite the distributions of patches and virus definitions to the system
using an orchestration facility.
h) These tools should consider the possibility to use standardized
configurations for IT resources.

8.9.7 Cyber Security – General Guidance

Cyber security governance problems are unique as well as evolving therefore, they
BSES

cannot be dealt with a traditional approach. For establishing secure and resilient
Smart Meter systems, a standardized cybersecurity framework should be adopted
by the AMISP in consultation with the BYPL and relevant stakeholders. The key
elements of the cyber security framework must include:
a) Differentiation of stakeholders into broad categories to aid in proper
distribution of responsibilities among stakeholders and avoid overlapping
b) Defined set of responsibilities for each stakeholder group. As a result, the
decision-making process is streamlined, and proper management hierarchy is
established for handling the reported cyber-attacks. The roles and
responsibilities are divided into two groups:
i. Cyber – strategy and governance: The responsibilities under this group
relates to the policy and decision-making aspects of cyber security
framework
ii. Cyber security – risk, operations and compliance:This group comprises
of responsibilities relating to the operational parts of implementing cyber
security policies
c) Standardization of security practices and abundant guidance from knowledge
bodies while implementing security controls and processes. There are multiple
global security standards and Indian standards that are relevant in context of
underlying technologies used in smart meters:
i. National Institute of Standards and Technology (NIST) has developed a
framework for Cyber Physical Systems (CPS). The Framework provides
a taxonomy and organization of analysis that allow the complex process
of studying, designing, and evolving CPS to be orderly and sufficiently
encompassing.
ii. Department of Electronics and Information Technology (DeitY),
Government of India has developed a National Cyber Security Policy. It

Page 168 of 473

 aims at protecting the public and private infrastructure from cyber-
attacks. The policy also intends to safeguard "information, such as
personal information (of web users), financial and banking information
and sovereign data”.
d) Cyber security incident management: The ISO/IEC Standard 27035 outlines a
five-step process for security incident management, including:
i. Prepare for handling incidents.
ii. Identify potential security incidents through monitoring and report all
incidents.
iii. Assess identified incidents to determine the appropriate next steps for
mitigating the risk.
iv. Respond to the incident by containing, investigating, and resolving it
v. Learn and document key takeaways from every incident

Notwithstanding the measures suggested above, the following guidelines/strategies

shall be taken care of by the AMISP for making the entire AMI system including the
SMOC immune to Cyber Attacks.
a) All the Hardware, OS and application software shall be hardened.
b) Application, scanning and hardware scanning tools shall be provided to
identify vulnerability & security threats.
c) Data shall be encrypted at system/device/technology level.
d) Network Zoning shall be implemented as per the proposed architecture.
However, the AMISP may suggest other methods of network architecture
without compromising the security of the System.
e) Internal user shall be allowed to access all adjacent zones. However, they will
not have access to remote network zone.
f) While procuring cyber security items testing must be done and the system
must be secure by design. BSES

g) Residual information risk shall be calculated by AMISP and same shall be

submitted to the BYPL for approval.
h) All default user id & passwords shall be changed.
i) All log in/out and cable plugs in/ out shall also be logged in Central Syslog
server.
j) Penetration & Vulnerability assessment test from CERT-IN certified auditors
during SAT& Operations and Maintenance period.
k) Auditing by third party during SAT and annually during operations and
maintenance period shall be in the scope of AMISP.
l) As the computer system in SMOC has access to external environment the
AMISP shall document and implement Cyber Security Policy/Plan in
association with the BYPL to secure the system.
m) Latest Cyber Security Guidelines issued by CERT-In specified at
[Link] Ministry of Power (including “Testing of all
equipment, components, and parts imported for use in the power Supply
System and Network in the country to check for any kind of embedded
malware /trojans/ cyber threat and for adherence to Indian Standards –
Regarding” vide Order No. No.9/16/2016-Trans-Part(2) published by Ministry
of Power, Government of India dated 18 November 2020 and amended from
time to time) or any other competent authority shall be followed.
n) AMISP shall adhere with the appropriate security algorithm for encryption and
decryption as per established cyber security guidelines. For smooth
functioning of the entire system, it is essential that the AMISP shall provide in
the form of a document enough details of such algorithm including the
mechanism of security key generation to the BYPL. In case of proprietary or
secret mechanism, the same shall be kept in a secured escrow account.

Page 169 of 473

8.9.8 Additional Security Requirement
a. SIM used for Smart Meter / Gateway should be white listed.
b. User Mobile Application shall be hosted at app store (Android & Apple) and
developed on respective native platform
c. API and portal should have SSL connection i.e https
d. Network - Recommend use of dedicated interconnect connection to connect
on-premise to cloud. (wherever applicable)
e. Network - Any use of VPC (Virtual private Cloud) firewall with rules, to access
cloud.
f. Network - Use of private IP address to access cloud API, for any integration
(On-premise \ 3rd party) wherever applicable
g. Key Mgmt - Use of cloud KMS to access storage or wherever required. (REST
API that can use a key to encrypt, decrypt, or sign data )
h. Logs shall be made available for forensic use and connectivity to SIEM (SOC)
hosted at BYPL.
i. Logs shall be retained for min 2 Yrs (6month live and 1.5 Yr archive, subject to
change as guideline provided by BYPL). Check regulatory compliance
applicable.
j. Access Control (Authentication & Authorization)- Use of following systems for
cloud:
I. Active Directory Control should be used in Cloud
II. Two factor authentication
III. Identity Mgmt, single Sign-On
k. Communication ports (Server & firewall) shall be defined. Rest shall be closed.
l. SSL (public Application & VPN) - shall be used for secure connection between
client and server.
m. Network - System shall be protected by Next gen firewall having capabilities
like Deep packet inspection, IPS\IDS etc.
BSES

n. Use of 256 AES (Advance Encryption system) for data encapsulation.

o. Sever Hardening shall be done to secure system. Patches shall be applied at
periodic interval.
p. BYPL has right to conduct security audit on-premise to conformance of ISO
27001:2013, 27018:2019. AMISP shall provide all relevant data and evidence
for audit.
q. In case of any cyber incident \ attack, AMISP& Cloud Service Provider
I. Shall have Cyber Insurance
II. Shall born penalty raise to BYPL raised by regulator.
r. Data transmission shall be encrypted and should not be in clear text format.
s. OS - Responsibility of AMISP\CSP to apply OS patches, hardening and its
upgradtion. Any dependency on application shall be closed by AMISP\CSP.
t. Server shall be maintained in HA Mode.

8.9.9 Data Privacy

AMISP should describe ensure that the system is compliant with the applicable
provisions of the “Reasonable security practices and procedures and sensitive
personal data or information Rules, 2011 (IT Act)” as well as shall be committed to
work with BYPL for compliance to Personal Data Protection requirements. In this
regard, the general elements of the data privacy framework may include:
a) The BYPL shall be the sole custodian of the Smart Meter data. The AMISP
and its contracted vendors will have limited need basis access to the data. In
case of pre-mature termination or at the end of contract, the AMISP and the
contracted vendors should relinquish all access to the data and transfer the
same to the BYPL.

Page 170 of 473

 b) AMISP is required to prepare and submit a “Privacy by Design” document to
the BYPL which details out all the policies, practices, processes and
technologies employed to manage, and process the Smart Meter data in a
secure manner. This should also include the details on methods of
anonymization applied to the personal Smart Meter data based on data types
defined below:
i. Aggregated Data: No identification individually and at neighborhood level
unless explicitly required to report
ii. Anonymized Data: A data set which has individual Smart Meter data but
without any personally identifiable information like consumer name,
account number, address etc.
iii. Personal Data: A data set with Smart Meter data tagged with personally
identifiable information.
c) AMI system should enable the BYPL to get the consumer consent on sharing
and processing of Smart Meter data based on following criteria
i. Consumer consent not required
1) If any type of Smart Meter data is processed by the BYPL or a third
party on behalf of BYPL for the purpose of generating bills,
identifying theft, network planning, load forecasting or any related
activities that can enable the BYPL to fulfil its duty as a licensee.
2) If any type of Smart Meter data is requested by the law enforcement
agencies.
3) If aggregated or anonymized data is shared with not-for-profit
academics, policy research, civil society entities for research that can
benefit the sector in general.
ii. Opt-out consumer consent
1) If any type of smart meter data is shared with or processed by any
third-party commercial entity to provide services other than as
BSES

enabled by regulation. In this case, the AMI system should enable

the BYPL to conduct the following consumer consent process
 Consumer should be notified and given a time to opt-out
 Consumer should have the right to change his/her option through
the app/web account/direct communication to BYPL.
d) AMI system should enable following Data sharing protocol
i. Data should be shared by providing finite and secure access to the
system. The access can be modified or terminated as need be.
ii. Sharing of part/full database shall be subject to review and consent of
BYPL.
e) All data sharing shall be recorded and periodically submitted to BYPL for
review / regulatory requirement
f) AMISP should have a data breach response plan and should communicate to
the BYPL and consumers in case of any data breach from AMI system
g) AMISP is responsible to conduct 3rd party data privacy audit at least once
every year based on evaluation criteria pre-identified by the BYPL in
consultation with data experts. The audit report should be made available to
BYPL. AMISP to take necessary actions on audit observations in consultation
with the BYPL.
h) The CSP shall adhere to follow Privacy policy of BYPL.

9. AMI System Integrations

The AMISP’s core deliverables are the MDMS, the Unified HES, the NMS, Prepaid
Billing Module, Mobile App ). Hence the system integrations shall comprise of the
following,
i. Unified HES with field devices (DCUs/Routers and smart Meters)

Page 171 of 473

 ii. Smart Prepaid Billing Module with MDMS, CIS and Payment Gateway
iii. MDMS with
a. HES
b. Billing and CIS
c. SMS and E-Mail gateway
d. Other legacy IT/OT systems as required by the BYPL
e. National level Reporting Platform to come up in future

9.1 MDMS Integrations with BYPL IT/OT Systems

The MDMS will act as the bridge to integrate the AMI system with other BYPL IT/OT
systems. These IT/OT systems may be already existing or those which the BYPL have
planned. The IT/OT systems may include but not be limited to the following:
a) Billing, CIS, IVRS, CRM systems
b) Legacy Data Collection Systems
c) AMR / HHU/CMRI or manual reading system etc.
d) Consumer Portal/ App
e) GIS
f) SCADA, OMS
g) PLM, DRMS
h) Asset Management System
i) Work Force Management System
j) DT Monitoring System
k) EVSE
l) BESS
m) Lead Tracking Module
n) Third party application for Home area network (HAN) control

The details of the existing integration infrastructure, including specificity in

BSES

implementation, interface and services available for each of the existing enterprise
applications which the AMISP has to integrate with the AMI system, has been provided
in Clause 8.5& 9 of MDMS.

For those IT/OT systems which the BYPL have planned in future, the AMISP shall
publish document on available standard interfaces to enable their integration. AMISP
shall ensure testing including Integrations before and after any patch upgrade take
place on the system.

It will be necessary to integrate the MDMS with the BYPL IT/OT systems following
robust industry standard mechanisms.

MDMS shall interface with these IT/OT systems on standard interfaces. The data
exchange models and interfaces shall comply with CIM-XML-IEC 61968-9 / IEC
61968-100 / Web Services / MultiSpeak v3.0. MDMS solution shall be ESB-SOA
enabled.

The aim of the above interface standards is to ensure generic two-way interfacing of
the MDMS with other applications. This effort shall be guided by the methodology
whose details are outlined in the approach paper set out in Project Implementation
Plan.
MDMS shall provide details to consumer portal/app as per Clause 8.7.

9.2 Unified HES Integrations with Field Devices

Unified HES shall export all meter data to MDMS and pass control commands from
MDMS. Unified HES should conform to IEC 61968-9 as well as support CIM 2.0 /
MultiSpeak v3.0 standards. It may use any other standard interfaces as outlined in the
Page 172 of 473
 approach paper, submitted as part of project implementation plan, for integrating with
the MDMS. In case, BYPL has implemented or implement in future any Service
Oriented Architecture (SOA)/ Enterprise Service Bus (ESB) architecture, the data
exchange to and from Unified HES shall be through this ESB.

The Unified HES shall follow the integration protocol established by IS 15959 (DLMS-
COSEM) and make use of ACSE and DLMS services to communicate with
southbound field devices (DCUs and Smart Meters) irrespective of the physical
communication layer.

9.3 Integrated Network Management System

The Network Management function specific to the Unified HES shall be integrated with
overall Data Centre level NMS module for easy monitoring, analysis and reporting

9.4 SPBM Integration with MDMS, CIS and Gateway

a) Smart Prepaid Billing Module (SPBM) shall integrate with MDMS to receive
prepaid consumer / meter details once consumer converted / installed as prepaid
b) SPBM shall integrate with MDMS to receive required interval reading /
consumption for bill generation.
c) SPBM shall integrate with Payment Gateway to receive consumer recharge details
d) SPBM shall integrate with CIS/SAP for billing data sync and monthly reconciliation
e) SPBM shall integrate with CIS/SAP for receiving payment details if payment made
on collection counter or any other source.
f) SPBM shall integrate with MDMS to initiate Connection & Disconnection request.
g) SPBM shall provide all the information required for Consumer portal /app under
section [Link] (l)

9.5 Integration with national level reporting platform

BSES

The AMI system put in place should provide a seamless exchange of data with a
national level data portal without any manual interface including NFMS. In this regard,
the MDMS shall have an out-bound interface to facilitate data transfer through API-
based model/ service bus to a central platform as and when made available. An
indicative data list will be provided by the BYPL for sharing with the national level
reporting platform during contract period. The technical interface (such as web
services, published APIs, DB table schemas etc.) for enabling this integration, will be
defined accordingly. However, the AMISP needs to ensure the following:
a) Any reports / analytics / graphics from system would provide opportunity to
anonymize/ remove traceability to individual consumers to maintain privacy
b) Reports/data made available in the public domain for public consumption should
be always sufficiently aggregated/ anonymized so as to protect consumer privacy.

10. Consumer Engagement

10.1 AMISP shall develop a consumer engagement plan for smooth implementation of
AMI system. The plan at the minimum should include consumer engagement
activities to be undertaken at BYPL’s headquarter, division and sub-division level as
well as communication and media plan for the same. The plan should include
educating consumers about the pre-paid recharge mechanism, benefits of pre-paid
meters, potential usage of Smart Meters data for consumers, etc;
10.2 BYPL shall provide necessary inputs for developing a comprehensive consumer
engagement plan;
10.3 The BYPL shall implement consumer engagement plan with support of AMISP. This
would include running media campaign to raise awareness and counter myths around
smart metering prior to installation, etc.

Page 173 of 473

 11. Advanced data Analytics and Reports
AMISP shall provide Analytics to BYPL for strategic, tactical and operational decision
making which must be data driven through various models such as predictive,
prescriptive and forensic analytics of data. Analytics will serve as one of the critical
success factors in ensuring the successful implementation of the AMI system at
BYPL. The primary objective is to ensure that the huge volumes of data generated by
the smart meters installed at BYPLs render unambiguous and insightful results that
become an action point for the BYPLs either in ‘Day in Life’ or future scenarios, aimed
at driving decisions to take corrective actions thereby improving performance and
bringing value to both customers and operations. For example, the BYPLs would be
obtaining energy consumption data from the smart meter. Using analytics, It shall be
possible to derive trends of regular usage as per the season and to single out cases
for investigations in cases where usage is abnormal.

Billing efficiency improvement and theft reduction are two major concerns of BYPLS.
The AMISP shall ensure that the insights produced by analytics are effectively
consumed by the BYPLS to enhance their billing efficiency and reduce theft/losses
through expeditious measures viz: prompt action for reconnection and disconnection,
reduction of outage rate thereby increasing supply, prompt detection of theft and
tamper through events and alarms etc.

11.1 Database Software and Licenses

AMISP shall provide relevant database software for Analytics and Licenses to be
provides as per the scope defined, following conditions to be considered
I. Analytics database will store meter profile data based on configurable period
defined by BYPL for meter data profile (like Load Profile, Non-Critical Events,
Alarm and Instantaneous etc.)
II. MDMS database will integrate with database of Analytics software and data flow
BSES

between these two databases shall happen as per the requirement on periodicity
required to fulfil business requirement. Data profiles like Load Profile, Non Critical
Event, Non Critical Alarms etc. shall be stored centrally in Analytics database
and will be accessed by MDMS for the features required these data.

11.2 Minimum Functional Requirement

The BYPLS shall be able to reap tangible benefits through the deployment of analytics
which would be integratedwith other enterprise applications of BYPLS to ensure;
a. Plotting of PQ parameters in correlation with other device status information
b. Loss and theft reduction
c. Optimum customer experience by performing analytics on events like last gasp
and power restore to identifyfield outages and take proactive action even before
consumer calls.
d. Consumer analytics to determine consumer usage pattern, payment behavior etc.
e. Revenue analysis and insights for example pre and post audit of meter reading
f. Benefit Analysis for AMI Deployment(pre and post)
g. Device/area wise power quality related information
h. Reporting of KPIs based on smart meter data example (peak load, billing
efficiency, reliability indices,Transformer failure rate etc.)
i. Static and dynamic reporting based on flexible rules/algorithm
j. Operations and distribution network optimization analytics,
k. Analytics of historical and real time data for fault analysis to take corrective
measures

Page 174 of 473

 l. Analytics shall support special reads and associated analysis, such as momentary
outage counters, sustained outage counters, voltage sags, voltage spikes, etc.,
that comes back to the Analytics.
m. Analytics should have ability to process the events such as demand thresholds,
voltage high/low in the form of a trigger to other systems in BYPL or alerts to
designated users in the form of workflow.
n. Analytics shall be able to distinguish between: 1) legitimate zero energy values
when no energy is used, 2) zero values based on power outages, 3) missing data.
o. Analytics should interpret the validations, events, alarms, flags etc. From meter
data and correlate and filter with other systems data such as OMS before opening
actions in workflow.

11.3 Solar Data Analytics

a) Detailed view of generation and consumption patterns to enable better supply
planning.
b) Day-ahead and Intra-day forecasting of generation from RTSPV plants
c) Inter-site analytics for performance comparison across sites, equipment types, etc.
d) Quicker identification of breakdowns and underperforming assets
e) Various technical, Operation and Maintenance (O&M), and performance parameters
such as Performance Ratio (PR), Capacity Utilization Factor (CUF), real time
performance graph, etc. to be displayed.
f) Real-time alerts to be generated in case performance parameters are below to a
certain threshold levels to reduce loss of generation due to loss in productivity
caused by soiling, shading, panel degradation and others.
g) Instantaneous parameters such as voltage, current, active power, reactive power,
power factor, start and stop time of inverter.
h) Graphical report on actual vs predictive data
i) Cost benefit analysis and payback period report
BSES

j) Integration/Compliance with PM Surya Ghar: Muft Bijli Yojana by Govt. of India.

k) The Consumer Dashboard of Solar connections should enable stepwise tracking of
the DISCOM, Subsidy and application’s processes.
l) Separation of Auxiliary Consumption of Battery Energy Storage System from overall
loss of the system while calculating feeder loss
 Auxiliary consumption to be separated out from input energy while calculation
of feeder loss.
 Calculation of performance parameters such as round-trip efficiency of the
system, reactive power support vs active power consumption, lifetime energy
consumed for charging / discharging, no. of cycles left.
m) Technical Feasibility for integration of Rooftop Solar based on loading pattern of
Distribution Transformer
 Set dynamic limits for solar penetration based on the day-time peak loading of
DT. Higher the loading on DT, higher the amount of solar can be allowed in
order to relieve the DT load during solar hours.
 Upstream network till DT should be traced out and based on peak day-time
loading of DT (For Peak day loading, historical data shall be referred), solar
penetration may be decided on that particular DT.

11.4 Event Data Analytics

Events generated by streaming event analytics engine from various tamper/load profile
attributes of Smart meters as per AMI and Project requirement

Since volume, variety & velocity of events differ in both types, the processing of events
would need different set of correlation rules, filtering rules, retention rules, alarm
creation rules, application of AI/ML logic, SLA expectation. Bidder shall deploy
instances of event management capable of handling the requirements for Smart Meter

Page 175 of 473

 Event Mgmt., for which please refer below indicative diagram wherein the Bidder/BYPL
can add further event related management rules

Additional functional requirement for Event Data Processing (not limited to):

a) The MDMS shall have a processing engine that provides automated as well as
manual handling of events (based on configuration rules) described in VEE section.
b) The MDMS processing engine shall be configurable to support business rules
without IT programming (e.g. VEE failures, non-responding meters, meter and
network alerts, etc.).
c) The MDMS shall allow an administrator to set event thresholds to limit the sending
of work flow or other notifications.
BSES

d) The MDMS shall allow an administrator to define rules for collecting notifications
and sending them in batches.

11.5 Analytics including Energy Audit

The MDMS shall have analysis capability based on configurable business rules
including but not limited to the following:
a) Energy Audit: Perform DT/Feeder/ Sub-Division/ Division/ Circle wise energy audit
for configurable period. These energy audit reports shall clearly bring out the
technical and commercial losses through detailed analysis of supply side energy
data and corresponding aggregated consumption data of connected consumers. In
this analysis it must factor in data of energy export from net-metered consumers.
The automated audit should include but not limited to:
I. A daily automatic feeder loss (Feeder Head reading minus summation of all
DT meters readings)
II. Automatic LT Energy loss (DT meter reading minus summation of readings
of all those consumer meters served by the selected DT) would be reported
III. Billing and collection efficiency
IV. Identify the top [X] best as well as worst performing feeders and DTs
b) Display consumption/load profiles by configurable period (15/30 min, hour, day,
month, year etc.) day type (weekday, weekend, holiday, festival wise etc.) and by
tariff, consumer type (hospitals, schools, govt. offices, multiplexes, commercial,
residential, industrial etc.), or any user specified collection of meters.
c) There shall be separate DB for storing Load Profile, Alarms, non Critical events,
Power outage, Instantaneous data for more than one year (configurable as per
BYPL defined retention period) and shall be accessed for requirement defined
under Analytics or as and when data required by BYPL.

Page 176 of 473

d) System shall be able to integrate with SAP billing system, Meter data or other
secondary data sources like meter data of consumer, DT, Network mapping data,
Billing, Enforcement, RCM data, Event/alert data etc and shall be able to run
custom defined logics on such data points
e) Asset connectivity should be visible in Network Hierarchy view along with export
facility
f) Assets should be visualized on GIS maps & SLD. Complete hierarchy of assets
should be visible on map
g) Ability to handle and display different time series data as 15/30/60 minutes.
h) Different color should be available for different Asset / Meter / Network types such
as PTR, Feeder, DT and customer meters (Smart, Prepaid, Postpaid etc)
i) Asset details along with Real-time data should be visible by clicking any asset /
customer on Map
j) Availability of Geographical hierarchy such as BYPL> Circle> Division> Subdivision
> Sub-cluster for viewing data on Map
k) Enhance visualization tools for more focused data aggregation and analysis.
Capable of integrating multiple data sources and parameters and graphical
visualization
l) Shall perform complex interval data calculations supporting: addition, subtraction,
negative values and multiplication by a different constant based on magnitude
m) Ability to group / clustering different Assets/ customers (need based or permanent
based) and compare their consumption in tabular and graphical form for different
period
n) Generate interactive charts, heat maps and so on that toggle between interval,
hourly, daily and monthly usage for inferences
o) Loss analysis for different groups and categories of consumer on
daily/weekly/monthly basis
p) T&D loss calculation on monthly basis.
BSES

q) Generate peak & off-peak load patterns by aggregating all loads of consumer
group/consumer type/DT/Feeder over configurable period/day type.
r) Perform load analysis for different groups and categories of consumers in different
weather conditions.
s) Ability to provide the data to load forecasting, load research or demand response
applications and perform error management such as missed reads and intermittent
meter reads before sharing data with load forecasting, load research or demand
response
t) Ability to configure the system to effectively visualize consumption trends, identify
unusual patterns, and visualize load analysis to understand which assets are being
over utilized.
u) Analysing data to identify new patterns of usage, Setting fraud alert / transformer
overload alerts / demand – supply gap alert etc.
v) Ability to receive and store outage and restoration event data from Smart Meters
and outage systems and to log all such events for analysis and also support
calculation of compensation payments for sustained outages. Five reliability indices
shall be calculated,
i. System Average Interruption Duration Index (SAIDI), which is sum of all
consumer interruption durations in a given period over total number of
consumers served.
ii. System Average Interruption Frequency Index (SAIFI), which is the total
number of sustained interruptions in a given period over total number of
consumers served.
iii. Consumer Average Interruption Duration Index (CAIDI), which is sum of all
consumer interruption durations in a given period over the total number of
sustained interruptions in that given period

Page 177 of 473

 iv. Consumer Average Interruption Frequency Index (CAIFI), which is the total
number of sustained interruptions in a given period over the total number of
distinct consumers interrupted in that given period
v. Momentary Average Interruption Frequency Index (MAIFI), which is the total
number of consumer interruptions less than the defined time (1 or 5 minutes)
over the total number of consumers served
These reliability indices shall be calculated for each month, for individual feeders
and aggregated annually for the whole BYPL. The source data for outage shall be
last gasp / first breath messages from DT/Feeder level meters or the power
outage/restoration events logged by these meters. These computations shall be
independent of similar computations made by any OMS application.
w) Ability to alerts on DT/ Feeder level overvoltage & back-to normal event and under-
voltage and back-to-normal events. Based on these alerts the system should
calculate the duration in which the DT/Feeder remained outside the nominal zone
of defined voltage. Similar calculations should be allowed for power factor and
current unbalance.
x) Identify & visualize poor performing assets such as feeder/DT on multiple criteria
such as energy losses, outage duration etc. through appropriate colour coding
depending on severity thresholds.
y) Analyse data of net-metering consumers to identify patterns of energy export to
grid on hourly/weekly/monthly/yearly basis.
z) Provision for detailed analysis of consumption trend, time series data analysis,
grouping of time series data, user defined analysis based on different Time
zones/TOD, consumer category, Weekday/Weekend, day/night consumption
analysis
aa) Integration and analysis of Technical and Business data such as Metering event/
time series data with Enforcement and RCM exceptions
bb) Energy accounting features such as :
BSES

i. End-to-end Energy Accounting based on mapped metering points at each

voltage level (Transco STU Grid to Consumer level) on Real-time and
historical basis
ii. Capable of computing distribution loss at each voltage level
iii. Grid Balancing
iv. Exception and Loss reporting
cc) Forecasting requirement :
i. Demand and Energy Forecasting tools for network planning and system
monitoring
ii. Predictive Modeling tools for ascertaining the exceptions in Assets / Meters
based on Data Pattern
dd) Network Health Monitoring :
i. Dashboard for real time monitoring of circuit wise energy, Loading, Voltage,
Power factor
ii. Exceptional reports (No CT, No PT, Low PT, Unbalance & Low pf)
iii. Daily AMR communication status
iv. Daily input energy forecasting feeder/sub-division/division/company wise
v. Alarm Report and highlight events based on various parameters such as
Voltage, Current, Power, pf etc available in Feeder/ DT/ Consumer with user
defined frequency and threshold
vi. Identification of Individual peak and coincident peak loading / pf at Feeder
and DT level
vii. Voltage profile comparison 11kV Vs DT Vs Consumer wrt corresponding
Loading Trend on GIS
viii. PTR, Feeder and DT health report
 Overload/unbalance/low pf/voltage report based on selective
period/selective feeder/threshold and combination
Page 178 of 473
  Power off report
ee) GIS based IOMS system shall be integrated for Outages and corresponding
analytics
ff) Network hierarchy of BYPL electrical network shall be imported from GIS system
and any change shall be updated with no delay.
gg) Alert Mechanism :
a. Dashboard for different Alerts and events based on user-defined threshold
such as Power Outage, Low voltage with defined persistent time, High
Voltage with defined persistent time, Phase missing
b. Overloading with defined persistent time, Critical Load Un-balancing (based
on Neutral current) with defined persistent time
c. Provision for identification and visualization of alerts on various metering
points

11.5.1 Following high level reports for BYPL Management shall be generated
automatically at specified frequencies to help management with business
decisions. <Below is an example of reports that may be generated. These reports
should be defined and agreed by the BYPL

Category Report Frequency

Energy Audit Report (DT/ Feeder / Sub-
Division/ Division/ Circle wise) in
contiguous electrical locations:
 A daily automatic feeder loss report
(Feeder Head reading minus
summation of all DT meters Daily, Monthly and User
readings) Selectable Time Period with
 Automatic LT Energy loss report (DT
BSES

Energy Audit configurable near real time

meter reading minus summation of alerts for exceeding defined loss
readings of all those consumer threshold
meters served by the selected DT)
would be reported
 Billing and collection efficiency
 Identify the top [X] best as well as
worst performing feeders and DTs
SAIFI and SAIDI; CAIFI and CAIDI;
MAIFI of the feeder(s) and connected
Reliability consumers would be tracked to Daily, Monthly and User
Indices measure the improvement in the same Selectable Time Period
overtime and establishing reference
levels
Daily, Monthly and User
DT Loading (Categorize DT as
Selectable Time Period with
overloaded, optimally loaded, near
configurable near real time
optimal, under loaded)
alerts
Load Load recording (Consumers): Actual Daily, Monthly and User
Management consumption recorded higher than the Selectable Time Period with
sanctioned load identifying the top [X] configurable near real time
consumers alerts
Load Management Report (Identify top Monthly and User Selectable
overloaded DTs) and load rise trend Time Period
Daily, Monthly and User
Power Voltage Deviation Index and Frequency
Selectable Time Period with
Quality Deviation Index (DT/ Feeder)
configurable near real time

Page 179 of 473

 Category Report Frequency
alerts
Daily, Monthly and User
Selectable Time Period with
Low Power Factor (DT/ Feeder)
configurable near real time
alerts

Daily, Monthly and User

Meter Current Unbalance (DT/ Feeder) Selectable Time Period with
configurable near real time
alerts
Tamper Alert: as per IS 15959 Part 2
Comparison Consumption (system used
Daily, Monthly and User
to detect & track theft suspects)
Loss Selectable Time Period with
Consumption lower than the expected
Analytics configurable near real time
pattern (pattern of previous year applied
alerts
to the monthly average) or monthly
average
Summary report on top [X] high loss
DTs/ Feeders, top overloaded DTs/
Management Feeders, Top feeders/ DTs with most
Summary outages (number and duration), Top <Monthly and User Selectable
Report feeders with most power quality issues Time Period>
(Dashboards) (over voltage, under voltage, current
unbalance, out of band frequency), DTs
with high failure rate

11.5.2 BYPL interface should have ability to generate reports on critical and non-critical
BSES

information received from the Unified HES to the MDMS as per requirementof this
Section.
11.5.3 BYPL interface shall have feature to generate report related to SLAs being
mentioned in Clause 14of this Section.
11.5.4 Ability to generate various analytics reports as per Clause 11.5.6 of this Section.
11.5.5 Graphical representation of all results and export facility in pdf/excel/CSV/text
formats
11.5.6 AMISP shall submit a detailed report on data being shared as per BYPL
requirements on a yearly basis. AMISP shall submit detailed report on any
exception in general data sharing on monthly basis. Further, AMISP shall also
submit a detailed report for any other time period as requested by BYPL
11.5.7 Routine reports required from Analytics :

S. No Reports Name Timelines

1 Daily Demand Analysis Daily
2 Division Wise Input Energy Monthly
3 Load Summary BYPL Daily
4 Energy Summary of BYPL Daily
5 Monthly Issues/Faults Monthly
6 Feeder Wise Input Summary Monthly
7 Division Wise Input Summary Monthly
8 Slot Wise Feeder Load Survey Monthly
9 ITD Import Monthly
ITD Export
10 Grid Alarm Reports Daily
11 NO PT Report Daily

Page 180 of 473

 S. No Reports Name Timelines
12 ABT Day wise Summary Feeder Monthly
13 NPP Data Monthly
14 Feeder Master On demand
AMR Vs SCADA VS GIS Mapping
AMR & SCADA Avg Load Mapping
15 Local TX Energy Monthly
16 Power Outage Reports- DT and HTC up to sub-division Monthly
level
17 Prepaid Meter Exceptions Monthly
18 Abnormal Voltage – 3ph Consumer level Monthly
19 Enforcement Leads related to Energy assessment or As per event
Theft
20 Revenue Leakage Cases other than theft As per event
21 Street Light meters analysis report Monthly
22 Analytical based Division & Sub-Division Level Loss Monthly
reports Calculation
23 HT Loss Calculation at Division Level Monthly
24 HT Feeder Loss Calculation Monthly
25 LT loss Calculation @ FL/SC Level Monthly
26 JJ Loss Calculation at Division,Sub-Division & Area Monthly
level
27 Specific Area Loss Calculation Monthly
28 Complete DT Health Monthly
29 DT+ HVDS Energy Monthly
30 DT-HVDS Master Finalization Monthly
31 DT Sensor Report BSES
Daily
32 AMR Dashboard Daily
33 MRD File download Status Report Fortnightly
34 Exception reports based on MRD download Fortnightly
35 DT Unbalancing Monthly, Daily
36 PF of DT for APFC Panel Monthly, Daily
37 Peak Loading of DTs Monthly, Daily
38 Energy Audit Report as per BEE Formats Monthly/
Quarterly/ Yearly

12. Smart Meters Installation

The AMISP shall install, integrate and commission smart meters of different types, the
estimated number of which is given in the Project Areadetails. The BYPL shall provide
details of new locations, consumer premises, Distribution transformers, feeders,
boundary locations, etc. in the Project Area, where meters are to be installed from time
to time.

After meter installation, details of consumer connections, such as consumer

identification no., meter ID, its hardware & software configuration, name plate details,
make, type i.e., 1 Phase or 3 Phase shall be updated in the system. The information
would be captured through meter installation Application supplied by AMISP and to be
updated in SAP / MDMS / HES on same day with proper validations.

12.1 Scope of Meter Installation / Replacement

The scope of Smart Meter installation (All Types of Meters) work shall include the cost
of all labour (electrical, civil, and others), materials, tools, MI application and other
incidental expenses in connection with additional labour requirement.

Page 181 of 473

12.2 Meter Inventory Management
Meter management and installation shall be the responsibility of the bidder once meter
installation is approved by BYPL. AMISP shall open and maintain a warehousing
facility for storage of the smart meters in warehouse for the project duration. AMISP
shall maintain the inventory of all the meters in designated warehouse, maintenance
and security including full responsibility for protection from theft and fire. Meter
Inventory Management and Warehousing to be maintained by AMISP on real-time
basis. Any physical damages including fire and theft and damages not covered by
OEM shall be the responsibility of the Bidder.
a. Warehouses are located at strategic locations in the project area. Warehouses
receive Smart Meter’s, Meter boxes, and security seal, Barcodes stickers/ Tags ,
consumable (clamps, cables ) from various suppliers (eg Meter Manufacturer’s,
BYPLs , Consumable suppliers)
b. Warehouse module has the facility to create inventory items with information like –
Item Name, Brief description/rating, Supplier, Make, Model) for both serialized (e.
g. Meters, Seals , Communication modules , SIMs, etc) and non-serialized (e.g.
boxes , clamps , cables , other consumables) items . Photograph, manual/Tech
details can be tagged with the items (JPEG, PDF). Each item shall be identified
with a unique code generated by the system
c. Once the fresh stock of materials is received at warehouse, it will be taken in stock
after due verification and stock register is updated. Beside the user interface for
material inwards / issue, the warehouse module shall have the facility to
• Uploads excel file for material inwards or issue
• Upload the items details by scanning bar code/QR code with the help of a
mobile app during both inwards & issue process
d. On issue of the meters and associated materials for installation from Warehouse,
there shall be an UI for the Project In charge to generate the list of issued meters
BSES

with SIM numbers with feature to approve for Meters/SIMs for TSP activation. The
SIM activation approval can be done by selection of individual meter or in bulk.
e. The Application shall have the facility for issued material return from the agency
and update the stock.
f. MI agency will returns the replaced old Meters fixed with a QR code/ barcoded tag /
sticker to Warehouse along with a copy Meter Change Record (MCR) (If in
Hardcopy) and a digital file which contains the Tag /sticker barcode / QR code
number, Consumer details (consumer Account number/name and last read ).
g. The module shall have facility to read the barcode/QR code on the replaced meters
with the help of a mobile application and validate with the uploaded digital file
before taking in stock of the replaced meters in warehouse. The warehouse in
charge may also put his verification remarks for such receipts.
h. The warehouse module shall also have a user interface for the BYPL official,
wherein at the time to accepting the replaced meters, they can access the MCR
records and accept the old meters
i. The WHM module shall have a Dashboard showing the Stock position – Project /
Warehouse wise and other relevant data. The Dashboard shall have drill down
facility
j. The Application shall have reporting facility for the selected duration and sorted for
project /warehouse location / supplier/ MI agency / material type /make for Stock
Inward, Stock Issue , Stock Ledger , Material Return Report , old meter
inward/outward report .Reports can be exported in CSV / Excel formats

12.3 Site Survey for Communication Technology Selection

The smart meter implementation agency shall conducts area/sub-cluster wise survey
to obtain network feasibility details along with Service provider wise and Technology
wise signal strength, dark spots to ensure and provide feasibility details of

Page 182 of 473

 communication network (RF/Cellular) for individual area for successful deployment of
Smart meter in the defined project areas.
a. AMISP shall be responsible for Area Survey of the area allocated by BYPL and
submit report of Cellular Network availability/strength and areas not feasible on
cellular network.
b. Cellular network report shall contain information about TSP (Telecom Service
Provider) wise status of signal strength and recommendation of TSP for each area
/ sub cluster
c. The Network survey team shall capture Lat/Long details of the locations during
Survey.
d. Network survey does not absolveAMISP in delivery SLA in any project area where
a particular communication technology is proposed by [Link] responsibility of
BYPL would be limited to ensuring supply of Cellular meters. After receipt of
Communication network survey report with details of low network or dark spots,
AMISP has to implement RF solution as per the suitability. AMISP to coordinate
with alternate RF communication technology provider to ensure SLA between
meter and HES. AMISP are advised to ensure the capability and capacity of such
RF Technology provider before installation.
e. Capturing details of newly installed Smart Meters. Post completion of Smart Meter
installation, it will be the responsibility of the AMISP to ensure that the master data
of the Smart Meter system is in sync with that of the BYPL billing system
f. Capturing details of newly installed Smart Meters, RF details for the locations
where installation done by BYPL vendor for RF.
12.4 Meter Installation
12.4.1 Bidder’s Scope
Installation of 1Ph and 3Ph electronics Smart Energy Meters and associated
accessories such as Network Interface Card, SIM Card, Meter Box, Isolators/MCBs,
BSES

Saddles, Sealing, as per SOP of BYPL at consumer premises. All Materials like
meters and its accessories etc. shall be transported and delivered by AMISP at
warehouse.
a. The bidder shall prepare a SOP (Standard Operating Procedure) document for
meter installation in consultation with BYPL and Meter installation activity shall
adhere to this document. Installation services shall be performed in a professional
and courteous manner, from initial appointment setup to final installation of the
meter. Customer service, effective project team and customer communication are
of the utmost importance to this project. All site installation personnel employed on
this project will be subject to background checks and shall, at all times, carry a
suitable Govt. issues photo ID (such as Driving License, Voter Card, Aadhaar) for
identification. Police verification shall be submitted to BYPL field nodal officer,
before putting personal in field.
b. Scope of Bidder shall include:
1. The meter replacement/installation as defined under BOQ line item shall be
considered under bidders scope in following conditions:
i. Replacement of Non-Smart to Smart in all categories
ii. New Service Connection with Smart Meter
iii. Load Enhancement / Reduction of Existing Smart Meter
iv. Category change of Existing Smart Meter consumer
2. Removal of Old Meter & capture the meter reading
3. Installation of new Smart Meters with NIC card. Installation of Isolators/MCBs.
4. Install SIM Card in the meter & activate / register new meters with HES &
MDMS
5. Transfer Old & new meter data to the BYPL Billing Software online through MI
Application.
6. Sealing & Resealing of Energy Meter / Bus-bar /Meter Box.
Page 183 of 473
 7. Pasting of sticker on new meter box with information of Installation Agency
Name, CA Number, Date of installation. Dismantled meter shall be labeled with
CA Number, Meter Number, Final meter reading, and replacement date and
agency name
8. Provide or capture meter location through GPS.
9. Generate Meter Change Report (MCR)in pre-printed and printable formats
10. Digital photograph of meter reading of New Meter and Old Meter.
11. Train the BYPL /Nominated agency of BYPL installation personnel
12. Provide daily, real-time project status updates of installations.
13. Integration with any third party/existing BYPL application.
14. All type of transportation for movement of material and teams required for
execution of work under this contract shall in the scope of Bidder.
15. Supply of meter installation accessories & tools like Saddles Plastics Gitti,
Screws, Insulation Tape, screw driver, pliers, Fastners, Nut-Bolt & any other
petty items are in the scope of Bidder. These materials shall be provided as per
the specification of BYPL. The cost of such materials supplied by the Bidder
shall be included in the rate contact of each item of this contract & shall not be
compensated separately.
16. Return of all type of scrap generated from site/left over material (including any
2/4 core cable / copper cable removed from site, Bus Bars, Meter boxes,
Terminal covers & screws, Site Removed seals etc) & old meter with/without
gunny bags to the assigned BYPL stores
17. Reconciliation of Meters, DCU, Cables, Meter Seals, , MCR Books, NIC Cards,
SIM Cards & Lab Testing Notice formats, and all other related material within
defined timelines by Engineer In-charge / department SOPs.
18. Site visit for quality check and other work related to Metering including but not
limited to attending non communication cases (New Installation), meter
mismatch cases, interchange cases etc.
BSES

19. Rectify defects immediately noticed by BYPL representative during installation

or verification & inspection and rectify the data if it found incorrect & submit
ATR to QC in-charge offline or online with photographs. Bidder shall not be
compensated for expenses incurred, if any, for such Rectification /modifications
/ corrections/QA work. Person found doing wrong installations practices shall
not be allowed to work again until he attends compulsory training program.
20. Bidder shall provide Mobile, Printers & Thermal papers (for onsite printers) to
each team working at site for all metering activities & maintain their Quality If
any Mobile/Tab/Printer gets damaged, it shall be replaced immediately by
Bidder without affecting work.
21. SIM management and Coordination with TSP for supply and network problems
22. Delivery of SIMs to Meter OEM to ensure supply of meters with pre-inserted
SIM and factory file.
c. The bidder shall adhere to DERC Regulations and BYPL Standard practices on
“Installation and Operation of Meters’.
d. BYPLs shall provides existing consumer information comprising consumer nos.,
consumer name, consumer address, contact nos., present meter information,
connection type etc., sorted vis a vis specific Distribution Transformer, Feeder,
Substation and Subdivision/ Division. The BYPL data (CSV,Excel, XML) shall be
considered for installation planning. The authorized project person groups the data
based on Sub-Cluster / Distribution area
e. It shall be noted that for replacement or relocation of meters, clamps and any other
accessories required to install and energize power supply shall be provided by the
bidder.
f. The MI (Meter Installation) application (Android) shall be provided by AMISP and
application shall have the facility to register/deregister meter Installation agencies
and their teams.

Page 184 of 473

g. Installation team can download/install the MI Mobile application (Android) after
registration and approvals from the backend system. A link to download the
application shall be sent over registered mobile number (SMS) or on the registered
email ID. The Application is installed on mobile device and shall be operational
after validation through a secure OTP sent over SMS/email.
h. The MI activity shall be carried out using the GIS enabled Mobile Application and
Lat/ Long as well as meter / premise image shall be captured in coordination
i. The Backend application shall push a pre-downloaded map ( eg Google maps )
and the BYPL data of the area under installation to the allocated field engineer
mobile application.
j. Once the map/ data is uploaded to the mobile device, the mobile application shall
keep operating also without internet connectivity to the backend system. The
Mobile application should synchronize with backend system on regular interval
whenever there is good internet connectivity. There shall also be facility to
download the data from the mobile device by connecting it with a Desktop/ Laptop
k. The data exchange between the backend system and the mobile application
should be secure and the mobile device users shall not be able to access or alter
the data stored (except input parameters) in the mobile
l. The Application shall have the feature to view existing electrical network data and
corrections in the data / information with the help of integrated mobile application
and store basic attribute data of the electrical network elements on the GIS
map/image showing: Primary substation (33/11kV), 11 kV feeder, Distribution
Transformers (DT) , LT Network with notation for LT poles/supply pillars, and tag
the customer premises / meters with the electrical network with minimal efforts.
With the above process, complete electrical network hierarchy could be viewed on
the GIS Map from Feeder to DT to Consumers/meters. Corrections/Modifications
proposed by MI team for electrical network shall be submitted to BYPL in desired
format for further verification and update in master.
BSES

m. When authorized installation personnel visit a Consumer premise, they shall

search the consumer details on Mobile Application using CA number, Meter
number, customer phone/mobile number. They recheck the consumer information
as well as old meter information and add GPS Co-ordinates of consumer premises
based on GPS built in the mobile phone or by dropping the pin on the GIS map.
n. The SMOC or MI application shall have user interface from where the authorized
person can allocate the approved location/s to the installation agency/team.
Allocation for installation can be done by selecting the locations one-by-one or in
bulk based on Sub-Cluster/Distribution Area.
o. There shall be a user interface for the MI agency, where their authorized planner
can login and access the list of their registered supervisors / installers. The planner
can select /group and push the data to the Supervisor / Installers MI App for
installation. They shall also push the GIS map for the area to the mobile app.
p. The MI agency planner shall have the facility to cancel / modify the installation list
till the meter is not installed for the location.
q. The Supervisor shall have the facility to reassign the work other installer in his
team or cancel the installation activity for a location. Once for any location
installation is cancelled, the planner can reissue that location again for installation.
r. The Supervisor /Installer shall login to the Mobile app as per their role using
password/ OTP
s. The mobile application shall be automatically send the location co-ordinate
(lat/long) of the Supervisor/ Installer at a predefined regular interval after login to
the app. Their location can be viewed in the backend application (SMOC) on the
GIS map.
t. It shall be possible to push short messages on the mobile app of the Supervisor/
installer from the backend application. The Supervisor/ installer can also send
short messages from their application to backend application.

Page 185 of 473

u. The supervisor / Installer can search from a dropdown list or search by CA number
/ Mobile number to locate a consumer for installation. They can also locate the
customer location on the GIS map on the mobile app. They can also copy the
location lat/long for using it in Google Maps for finding direction.
v. The after reaching to a customer premise, the Installer can search the consumer
details on Mobile Application using CA number, Meter number, customer
phone/mobile number. BYPL provided electrical network mapping data shall be
displayed for the consumer location and related information is displayed on the
mobile application. The Installer’s mobile app shall have the facility to update some
of the variable records like location, DT/Feeder, Lat/Long , Mobile number , details
of the meters if different than the meter details captured from BYPL’s data.
w. The installer shall enter the meter reading, other details in the mobile app in the
format and take photograph of existing meter. After dismantling the existing meter,
a QR code/barcoded Tag/ sticker is placed on the replaced meter. Installer shall
enter the barcode detail / scan the barcode with the mobile app.
x. A new Smart Meter (1 phase / 3 phase/LTCT ) is installed with meter box as per
the allocation.
y. After Installation the Installer shall fill in records / status of new meter in a format
with mobile app like –meter Sr No. , new meter Reading , SIM ,Details of the
security seals used , qty of consumable used ( clamps , cable ) , Meter
Communication status (single strength , error code) , put his signature in the
mobile app and take a photograph of the new installation.
z. Meter Change Report (MCR): Installer shall generate a MCR after installation as
per the BYPL practice.
aa. Preprinted format MCR – The details are entered in a preprinted format with
unique serial number. After Filling and signing the format, the serial number shall
be entered in the mobile app and a photo of the report is taken and saved along
with the other installation details. A copy of the report is given to the customer.
BSES

bb. MCR On site Printing: The mobile app shall have the facility to generate the meter
change report in a printable format, which can be printed locally using a mobile
Bluetooth printer paired with the mobile device.
cc. The mobile application shall have the facility to capture signature of customer
digitally at the end of the installation process, which can be printed on the onsite
printed MCRs.
dd. Once the Installation is completed the data is synced to the backend server and
the information is updated in the system in real time including pushing the
installation information to the respective supervisors mobile application.
ee. The backend system shall send the field installation record to the HES, MDMS
application of the project at a regular interval for provisioning and starting the
reading activity.
ff. Post completion of Smart Meter installation, it will be the responsibility of the
Bidder to ensure that the master data of the Smart Meter system is in sync with
that of the BYPL billing system
gg. MI application shall have facility to ping meter after installation to validate meter in
communication before leaving site.
hh. At the end of the installation program for the day, the supervisor returns the old
replaced meters to the MI agency office and update the status in his mobile
application interface.
ii. The MI Agency in-charge will return the Old meters to the Warehouse in LOTs with
a file containing detail of the meters being returned. The warehouse in-charge will
upload the file, validate and accept the old meters.
jj. The MI Application shall have facility to Carrying out QA/QC on the collected MI
[Link] application shall have facility to configure the QA parameters.
kk. The authorized project person, shall approve the MI data after QA/QC process for
the next step

Page 186 of 473

 ll. MCO/Meter Advising: After provisioning / commissioning of meter in system
(First read by HES and meter creation in MDMS along with first read) the
process for MCO / Meter advising is initiated from the MI application module by
exporting the agreed data in a file to the BYPL’s billing system (SAP). This
process is indicated by the Project In charge.
mm. When the installer is installing the smart meter against a Service Connection
Order (SCO), the Mobile app shall allow to capture the consumer/ location
detail and other– Name, Mobile No. , SCO No and date , Feeder /DT , Lat/Long
, Signal Strength

12.4.2 BYPL’s Scope of Work

a) Cable, Isolators/MCBs, MCR Books (if required) required for performing work at
site shall be issued against SAP based Material requisition slip to Bidder’s
authorized representative from designated BYPL stores on free of cost basis.
b) Support in case of AMISP failing to receive smart meters delivery from OEM even
after timely request.
c) BYPL shall provide in advance the list of consumers where work of smart meter
installation and required network survey etc is to be performed under this
contract.

12.4.3 Manpower
a. Bidder shall depute trained, qualified and skilled manpower (One Lineman and One
Helper per team) & Supervisor/Engineer at site. Supervisor / Engineer shall have
minimum technical qualification & valid electrical certification to undertake electrical
work & Experience of 3 Years in the field of Meter installation.
b. All newly joined manpower of Bidder shall attend mandatory training & assessment
test in BYPL before performing any kind of job at site. Only those manpower that
pass assessment test post training, will be allowed to work at site.
BSES

c. Bidder shall deploy adequate number of teams / staff /workmen/ employees

(manpower) fully trained and equipped for the purpose of providing services under
this contract as per agreed installation plan.
d. Bidder shall also not employ any person who is blacklisted by BYPL or elsewhere.
Bidder must exercise due diligence to ensure that no blacklisted Bidder employee
gets recycled through another Bidder.
e. Bidder shall also depute a Safety Officer to monitor assigned work of meter
installation. Manpower deputed must follow safety procedures and guidelines while
performing assigned work at site. Manpower deputed must be proficient to execute
work, filling of MCR / Lab format / Quality report / Notices and entry / updating of
data through Mobile APP. Bidder shall provide a declaration on Monthly basis for
Safety Officer deputed at site & work getting executed considering all safety
procedures & norms.
f. Bidder shall submit details of employees engaged in the work. Bidder employees
shall not represent themselves as BYPL employee in any manner.
g. Its Bidder’s responsibility to prohibit / restrict its employees from involving in
misconduct / malpractices at site. Bidder shall conduct preliminary enquiry
/investigation against complaints received and share report with Engineer In-
charge. Bidder shall refund full amount of money (if any) taken from consumer
illegally by his employees for carrying out metering activities at site.
h. Bidder shall send their employees for investigation required in any case by BYPL.
The decision taken by BYPL involving Bidder’s employees shall be implemented by
the Bidder.
i. Bidder employees shall not offer any paid service to consumer for consumer wiring
or any other work pertains to consumer at site.
j. Bidder shall be held responsible for any liability arises from any accident to his
employees while performing work under this contract. An immediate intimation

Page 187 of 473

 followed by reporting shall be provided by Bidder to MMG Coordinator and Central
MMG office and to concern dept. MCS, DDA Etc. A FIR shall be logged
immediately if the case is of criminal nature citing such Risk an insurance of the
employee for such unforeseen circumstances shall be part of Bidder’s scope.
k. Bidder shall make all payments and contributions if any which may have to be
made in regard to the workmen employed by the Bidder in relation to wages or
other emoluments of such workmen under any statute or rules or regulations or
otherwise howsoever and indemnify BYPL against such payments

12.4.4 Uniform
[Link] Bidder shall provide proper uniforms to all manpower working for them, with “Red”
Colour logo of the Bidder.
[Link] Specifications of uniforms to be finalized with Head-MMG & In accordance with the
specifications provided by BYPL. Specification of uniform may change during the
course of contract period.

12.4.5 Store Management

[Link] Bidders shall manage their store as per the SOP of BYPL.
[Link] Bidder shall inform the details of store address. The Bidder shall provide adequate
security at store and will be responsible for material issued to him.
[Link] Store Upkeep by Bidder / Proper Racking: Bidder shall ensure Material Display
Board for Stock Display and undertake daily revisions. In order to manage the items
proper racking shall be undertaken. This shall cover proper stocking of new and old
material. Physical stock at last day of the month shall be submitted to BYPL on
monthly basis.
[Link] Bidder shall depute separate store supervisor to manage store & material
movement on day to day basis. Daily Inventory stock & Issuance of materials to field
team to be maintained in specified formats / Registers / Soft Data as per the
BSES

requirement & SOP of BYPL.

[Link] Bidder shall provide proper storage facility for storing material issued form BYPL
stores. Material stored in open or dusty location must be covered with suitable
weatherproof and flameproof covering material as applicable. Bidder shall also
provide indoor storage facilities to store all items/ material that require indoor
storage. Meters should be kept in lockable room.
[Link] Bidders shall not give/ transfer any Meter, Seal, Cable or other material issued to
them (related to MMG) to other Vendors of BYPL under any circumstances.
Similarly Meter, Seal, Cable or any other material related to other vendors of BYPL
shall not be used by Bidders under any circumstances. In very critical situations if it
is required, then it should be done with the approval of BYPL and proper
handing/taking over documents are required to be maintained & produced whenever
& wherever required.
[Link] Bidder shall install Weighing Machine with measuring capacity of 100 kg in their
store to check weight of scrap to be returned to BYPL stores.
[Link] Bidder shall manage its store in line with the prescribed guidelines of BYPL& Bidder
has to keep one computer with required number of accessories to keep the record
of incoming & outgoing material.
[Link] If available, Bidder shall be allocated a space for Store, in the respective division /
sub division to manage activities and store material under this contract. Allocation
shall be done by respective division in-charge and Bidder shall take proper
electricity connection and pay energy bills regularly.
[Link] Bidder shall open and maintain a site office in the area.

12.4.6 Vehicle

Page 188 of 473

[Link] Transportation of meter/material from BYPL Store / Office to Bidder store and
Bidder store to site & vice-versa shall be in the scope of Bidders.
[Link] Loading, unloading & transporting of all free issue material will be done by Bidder
from any BYPL store /any location to any location & vice versa.
[Link] Bidder shall provide four wheelers / E-Rickshaws as applicable and as per
requirement of project.

12.4.7 Other Terms and Conditions

[Link] Bidder shall be responsible for any loss of or damage to any Goods; to be read in
conjunction with relevant penalty clause.
[Link] Bidder shall install meters as per agreed installation plan and shall meet the project
time lines. Meter installation plan shall be on sub-cluster level of BYPL. Bidder shall
complete at least 90% of the Meters in the planned sub-cluster.
[Link] Bidder shall manage SIM Card installation & Its change management.
[Link] Meter installation shall be considered for billing only when its data are available on
HES after installation.
[Link] Bidder shall report the defective meters, tamper meters and theft cases detected
during installation to BYPL and follow the instruction given by BYPL for replacement
of such meters.
[Link] Bidder shall reconcile all material issued form BYPL stores for execution of Jobs
under this contract in specified formats by BYPL. Bidder shall maintain record of
material issued and consumed and same shall be produced for verification at the
discretion of engineer-in-charge.
[Link] Bidder shall collect old Meter, Meter box, Base Plates, T-Covers, Brass Screws,
Cables, removed seals etc. removed from site. These material recovered from site
on daily basis should be deposited in the designated BYPL Stores as per time line
specified by Engineer In-charge from time to time. The Old Meters (with and without
BSES

gunny bags) should be accompanied with Meter change Report (MCR), Lab Testing
Notice, Measurement Sheet and Meter Return Docket (MRD) duly filled in Soft and
Hard copies.

12.4.8 Safety
[Link] Bidder shall provide proper tools, tackles and associated paraphernalia as maybe
required for carrying out the meter installation.
[Link] Bidder shall provide all safety gears including but not limited to Helmets with visor &
live line sensor, safety belts, Insulated floor mat, ladders, safety shoes, Safety
Gloves, Safety Goggles, first aid box with required medicine and rain wears to their
personnel.
[Link] Bidder shall depute safety officer having required qualification for implementation of
safety guidelines and practices among their manpower while performing work at
site. Organize safety talk fortnightly or as decided by engineer in-charge and submit
record of safety talk on monthly basis to BYPL. Arrange all safety equipments for
their employees as per the details given in Form 29.
[Link] Bidder shall ensure safety oath by their employees on daily basis before start of the
work.
[Link] Bidder shall ensure that their employees shall execute work with 100% safety
precautions at site. Bidder supervisor shall avail shut-down for carrying out any work
in co-ordination with respective MMG Co-coordinator / SDO-O&M of BYPL. Bidder
shall ensure that their manpower uses all Safety PPE and T&P while performing Job
at site. Any manpower found violating safety guidelines shall attract penalty.
[Link] Shutdown required for installation of meters shall be planned in one day advance on
daily basis in specified format and information shall be shared with respective MMG
Co-coordinator & SDO-O&M of BYPL.

Page 189 of 473

13. Operation and Maintenance
13.1 Scope and period
The operation, maintenance, and support services start after the successful completion
of the operational go-live of the system as per Clause 16.7of this Section. Operation,
maintenance and support services shall extend up to end of 84-months from
Operational Go-Live. The scope of work under operation and maintenance services
shall include,
a) Comprehensive maintenance of all the software (including licensing, version
upgrades if any and annual technical support cost)
b) Comprehensive maintenance of all hardware at the Operation and Monitoring
Centre, along with field devices (like Smart Meters, DCUs etc.)
c) Comprehensive maintenance of all equipment under leased service like cloud data
centre, MPLS band width etc.
d) Comprehensive maintenance of NAN / WAN communication infra between field
devices and the cloud data centre.
e) Replacement of all hardware (like Meter, DCU, SIM, NIC etc.) comes under
responsibility of AMISP in all conditions.
f) Day to day operations of the AMI system under supervision and authority of the
BYPL. These shall include among others,
i. New meter installation
ii. Changeover of consumer meters from post-paid to prepaid mode and vice
versa
iii. Firmware update and configurations of remote devices (Meters and DCUs) as
required
iv. Incorporate changes in meter data model proposed in future by BYPL and
make necessary changes in UHES / MDMS as and when required.
v. Update of tariff slabs
vi. Ensuring completion of recharge cycle of prepaid consumer meters
BSES

vii. Connecting, disconnecting or reducing consumer’s licensed load under

approval from the BYPL
viii. Initiating resolution of consumer trouble tickets raised by BYPL CCS
ix. Ensuring availability of BP, LP, interval data and event notifications from
meters in time schedules as agreed with the BYPL
x. Ensuring scheduled completion of billing determinant calculations
xi. Ensuring daily reports from the AMI system as per agreed list, are made
available to BYPL
xii. Ensuring Consumer Portal is kept updated
xiii. Ensuring smooth data traffic between the MDMS and BYPL systems
xiv. Patch management of AMI applications at cloud data centre
xv. Provide backup data to support SLA and AMISP invoicing
xvi. Configuration changes required in all AMI applications (as and when
required)
xvii. Tariff configuration and their updations (as and when required by BYPL /
Regulators) to be done by AMIP in Smart Prepaid Billing Module (SPBM)
xviii. Carry out performance checks of various functions as per agreed schedule or
on demand

As part of their Operation and Maintenance responsibilities, the AMISP shall develop a
compendium of Operation and Maintenance Manuals covering the areas mentioned in
this section. These manuals shall be kept updated as often as necessary to reflect best
practices being employed in the project.

The AMISP is to handhold the BYPL team to take over operation, maintenance and
support services after completion of contract period. The project/ system devices

Page 190 of 473

 should allow their functionalities to be upgraded without disruption to the existing
functionalities by downloading new software and configuration information.

13.2 AMISP's Responsibilities under Operation & Maintenance Services

The AMISP shall make available the following man-power resources at the BYPL’s
SMOC,
a) One resident Project Manager cum Supervisor,
b) [Three] numbers operations staff
c) [One] support engineer for each category of hardware supplied and
d) [One] software specialists for each domain (can be placed at backend).
The above-mentioned operation and support staff shall be made available as required
to meet the SLA and system availability requirements. Re-distribution of any support
engineer/specialist at the cloud Data Centre shall be at the discretion of the AMISP.

It shall be the responsibility of the AMISP to collect meter data through handheld meter
reading instruments for the balance meter data reads not fulfilled by the automated
remote reading process. Similarly, if the remote connect / disconnect facility fails, it
shall be the AMISP’s responsibility to manage the function locally.

13.3 Maintenance Practices

For all third-party equipment (Hardware & Software) AMISP shall have back-to-back
support along with supply of spare with appropriate response time from OEM/OEM
Authorized representatives. AMISP shall be responsible for coordination with the OEM
for all matter related to equipment.
The maintenance practice followed by AMISP shall be in accordance with best industry
practices and must include the following:
a) Scheduled preventive maintenance, performance monitoring, system backup,
hardware & software maintenance and update, field & network devices firmware
BSES

update, emergency response and troubleshooting etc.

b) Maintaining adequate spares for maintenance.

13.3.1 Preventative Maintenance Activity

The preventive maintenance activities shall be performed by the AMISP to keep
the system running at optimum level by diagnosis and rectification of all hardware
and software failures and would broadly include:
a) Repair / replacement of defective equipment
b) Configuration of the replaced hardware and software, periodic routine
checking as part of a preventive maintenance program
c) Monitoring of the performance of the system and doing necessary tuning for
optimum performance to accommodate any changes such as addition of new
components
d) Providing all necessary assistance to the BYPL for addition and modification of
BYPL user interface, consumer Portal/ App displays, and Database
e) Ensure Backup of the system at regular interval which is mutually decided
during system design
f) Restoration of the systems upon its failure and to restore the functioning of the
various application / systems at the cloud data centre. Towards this, the RPO
and RTO shall have to be measured no less than once a month.

13.3.2 Integration of Equipment

All future services, protocol emulations and configuration support for integration of
Smart Meters/ nodes, routers, access points, network devices, web services,
integration with other offline applications etc. shall be the responsibility of AMISP
and shall be part of the maintenance activities.

Page 191 of 473

 13.3.3 Spares inventory
As part of project implementation plan, the AMISP shall detail the spares inventory
that shall be maintained for the AMI Project. These spares shall be used as and
when required by the AMISP for the project and no separate charges shall be
payable. The AMISP shall decide the items and components to be maintained as
spare.

Spare quantity of meters and NIC modules(required of faulty replacement) shall be

supplied by meter OEM and AMISP has to timely coordinate with Meter OEM /
BYPL to maintain buffer quantity.

13.4 Monitoring
The operation and performance of the various systems shall be monitored on a
continuous basis. The AMISP shall conduct at least the following monitoring:
a) MDMS / Unified HES system error history logs or selected day
b) Field & Network device failure – rate and trends
c) Availability of various communication links
d) Missing meter data – rate and trend
e) Reviewing resource information
f) Cyber Security
During monitoring if any defect/ abnormality is found, the AMISP shall undertake
corrective maintenance for the same. The BYPL’s UI shall be kept updated with a
summary of such monitored data

13.4.1 System Cyber Security Monitoring

The AMISP shall also be responsible for monitoring of the system from cyber security
BSES

perspective. The logs of the system shall be analysed for exceptions and the possible
incident of intrusion/trespass shall be informed to the BYPL and analysed to discover
root cause. The monitoring shall encompass all cyber security devices installed at the
cloud data centre as well as at the SMOC such as firewalls, all types of Intrusion
prevention system, routers etc.

The Cyber security system shall also be subjected to Annual Security Audit from
CERT-In listed auditors at the cost of the AMISP during the contract period. AMISP
shall share with BYPL such audit reports and implement the
recommendations/remedial actions suggested by the Auditor.
13.5 Meter Accuracy Tests
In case a Consumer complains about meter accuracy post operational go-live and
same isn’t reasonably resolved through past consumption trend, Transformer Energy
Audit, Check Meter (by BYPL), etc. AMISP will be obliged to facilitate the meter
testing. In this regard, AMISP shall handover the meter for testing to CPRI Lab/ BYPL
Lab/ NABL accredited Lab and install a temporary meter till the period of removal and
replacing meter, if found inaccurate or reinstall if found accurate.

13.6 Physical Maintenance

The AMISP shall undertake physical maintenance of all equipment/modules under the
scope of this contract, in accordance with the schedule as indicated by AMISP in
project implementation plan. The physical maintenance shall include cleaning, dusting,
inspection of equipment for loose connections, damage to insulation, pest infections
etc. Equipment shutdown during preventive maintenance shall be deemed as
available.

Page 192 of 473

14. Service Level Agreement (SLA)
Service Level Agreement (SLA) shall be monitored as mentioned in the following
table. It is expected that the AMI system shall meet the minimum threshold of service
defined against each level. Any degradation below this minimum threshold will attract
penalties as per bands of service level met. The idea is that it triggers a proper review
of any defect / failure / performance that had been agreed upon for the project, and to
find resolutions in keeping with the highest standards of service excellence. The total
penalties under SLA categories are capped at [20%] of AMISP Service Charge.
AMISP shall ensure that the data collection and computation for the purpose of SLA
penalties (as mentioned in the following table) should be automated and visualized in
BYPL Interface as per clause 11 and Clause 8.5.20 of this Section.

For this purpose, each of the designated scheduled tasks in the following table, shall
signal3 the SLA computation application to record the start time. The same designated
tasks shall generate mile-stone signals4 in order that the SLA application is able to
record times when various thresholds (as indicated in the table) of meter population
have responded. For system level availability, the SLA computation application shall
offer a ticketing system which shall be used by the BYPL&/or AMISP to raise an
incident against any line item at corresponding severity level. The incident originator
shall select the severity level followed by selecting the incident description (as per
Annexure J) available as a drop-down list within the SLA application. The ticketing
system shall follow a process flow such that,
a) The AMISP’s response along with time of response are recorded. This ‘response’
may be a simple acknowledgement of the incident or a rejection of the incident as
not being part of its ‘scope of work’ with adequate explanation.
b) BYPL’s acknowledgement or rejection of AMISP ‘response’ along with time are
recorded. If BYPL acknowledges the incident to be irrelevant to AMISP’s scope of
work, then the incident is immediately closed, and no further records are
BSES

maintained for this incident5.

c) Resolution &/or workarounds are recorded and submitted by AMISP along with
time
d) In case of enhancements and change requests, AMISP’s Plan of Action (POA)
and schedule are recorded
e) AMISP’s POA and schedule (for enhancements and change requests) are
approved by BYPL
f) Resolution as submitted by AMSIP is approved by BYPL and the incident closed.
In case of rejection of resolution, the incident shall remain live and shall have to
be re-worked by the AMISP.
g) All submittals, acknowledgements, approvals/agreements shall have system
generated time stamps by default. There shall be also provision for a separate
manual entry of time stamps.
h) AMISP shall develop web-based SLA tool for monitoring of the SLAs with the
facility to download the SLA in XLS and/or PDF format.

3
This signal shall be always automated, and the SLA Application would know precise number of meters
involved.
4
Alternate provision may be kept for manual entry of time for such mile-stone signals but with proper
backup monitoring report made available.
5
The first two process steps in the ticketing system of the SLA App shall ensure complete agreement
between Utility and AMSIP, before an incident is accepted for resolution.

Page 193 of 473

 Performance
Requirement SLA Penalty
Data Type Penalty
(Averaged over a Calculation
month)[1]
A. Scheduled Tasks
1. Scheduled Interval data readings
Periodic collection of Deduction of 0.2% of Maximum Penalty of
the interval load From 95% of meters AMISP Service Charge 1% if action takes
profile data for the within 8 hours for every 1% or part there place for <91% of
day[2] of capped at 1% penalty meters
2. Scheduled Interval data readings
Periodic collection of Deduction of 0.2% of Maximum Penalty of
the interval load From 98% of meters AMISP Service Charge 1% if action takes
profile data for the within 12 hours for every 1% or part there place for <94% of
day[3] of capped at 1% penalty meters
3. Scheduled daily meter readings
Previous days’[4] Deduction of 0.2% of Maximum Penalty of
From 99.5% of meters
interval energy and AMISP Service Charge 2% if action takes
within 24 hours after
total accumulated for every 1% or part there place for <90.5% of
midnight
energy of capped at 2% penalty meters
4. Scheduled billing profile data for the bill period
From 100% of meters
within 72 hours of the Deduction of 0.5% of
Maximum Penalty of
scheduled periodic AMISP Service Charge
Collection of billing 3% if action takes
collection/ end of the for every 0.5% or part
data for the bill period place for <97.5% of
billing period. Please there of capped at 3%
meters
refer to Annexure K for penalty
the billing schedule
BSES

5. Firmware Upgrade and Rollback

95% of individual assets
to be modified (updated Deduction of 0.2% of Maximum Penalty of
Actions related to
or rollback) within 10 Bidder Service Charge 2% if action takes
Firmware upgrade or
days of scheduled date for every 1% or part there place for <86% of
rollback activity
(update) or requested of capped at 2% penalty meters
date (rollback) and
99% of individual assets
to be (updated or Deduction of 0.2% of Maximum Penalty of
Actions related to
rollback) within 15 days Bidder Service Charge 2% if action takes
Firmware upgrade or
of scheduled date for every 1% or part there place for <90% of
rollback activity
(update) or requested of capped at 2% penalty meters
date (rollback)
6. Scheduled energy audit and reliability indices report[5] (DT wise)
Deduction of 0.1875% of
Generation of monthly Maximum Penalty of
From 100% of DT AMISP Service Charge
energy audit and 1.5% if action takes
installed meters within for every 1% or part there
reliability indices place for <93% of
384 hours (16 days) of capped at 1.5%
report meters
penalty
7. Scheduled energy audit and reliability indices report[6] (Feeder wise)
Deduction of 0.25% of
Generation of monthly Maximum Penalty of
From 100% of installed AMISP Service Charge
energy audit and 1.5% if action takes
Feeder meters within for every 0.5% or part
reliability indices place for <97.5% of
384 hours (16 days) there of capped at 1.5%
report meters
penalty
B. Remote Actions / tasks performed by AMI System

Page 194 of 473

 Performance
Requirement SLA Penalty
Data Type Penalty
(Averaged over a Calculation
month)[1]
8. For remote connect/disconnect with acknowledgement/ response for selected meters
Deduction of 0.5% of Maximum Penalty of
Remote connect / Action performed at 90% AMISP Service Charge 2.0% if within 5
disconnect of the AMI of meters within for every 0.5% or part minutes, delivery
meters 5minutes there of capped at 2.0% takes place for
penalty <88.5% of meters
9. For remote connect/disconnect with acknowledgement/ response for selected meters
Deduction of 0.25% of Maximum Penalty of
Remote connect / Action performed 99.5% AMISP Service Charge 1.0% if within 15
disconnect of the AMI ofmeterswithin15 for every 0.5% or part minutes, delivery
meters minutes there of capped at 1.0% takes place for <98%
penalty of meters
C. System Availability
10. Availability of AMI System per month
Deduction of 0.4% of
AMISP Service Charge Maximum penalty of
Availability of AMI for every 0.5% or part 4% shall be deducted
≥99.5%
System per month there of reduction in when system
availability capped at availability is <95.0%
4.0% penalty
D. On Demand Actions
11. On Demand Read and Actions
Deduction of 0.25% of
BSES
Maximum Penalty of
Bidder Service Charge 1.0% if within 15
Action performed 95% of
On Demand actions for every 0.5% or part minutes, delivery
meters within 15 minutes
there of capped at 1.0% takes place for
penalty <93.5% of meters
Deduction of 0.25% of Maximum Penalty of
Action performed 99.5% Bidder Service Charge 1.0% if within 30
On Demand actions of meters within 30 for every 0.5% or part minutes, delivery
minutes there of capped at 1.0% takes place for <98%
penalty of meters
E. Push Data
12. Push Alarms
Deduction of 0.5% of Maximum Penalty of
Bidder Service Charge 2.0% if within 5
Availability of Alerts 95% submitted to HES
for every 0.5% or part minutes, delivery
and Notification in 5 Min of Occurrence
there of capped at 2.0% takes place for
penalty <93.5% of meters
Deduction of 0.25% of Maximum Penalty of
Bidder Service Charge 1.0% if within 15
Availability of Alerts 99.5% submitted to HES
for every 0.5% or part minutes, delivery
and Notification in 15 Min of Occurrence
there of capped at 1.0% takes place for <98%
penalty of meters
F. Programmable Parameters
13. Configurable Parameters
Predefined Scheduled Deduction of 0.1% of Maximum Penalty of
Actions (changing Action performed 90% of Bidder Service Charge 1% if action takes
configurable meters within 24 hrs for every 1% or part there place for <81% of
parameters) of capped at 1% penalty meters

Page 195 of 473

 Performance
Requirement SLA Penalty
Data Type Penalty
(Averaged over a Calculation
month)[1]
Predefined Scheduled Deduction of 0.1% of Maximum Penalty of
Actions (changing Action performed 99% of Bidder Service Charge 1% if action takes
configurable meters within 72 hours for every 1% or part there place for <90% of
parameters) of capped at 1% penalty meters
G. MDMS SLA
14. Meter Data Management System (MDMS)
Capability of MDMS to
process meter data
received from UHES /
multiple Head end Deduction of 0.5% of
Maximum Penalty of
Systems (HES) with monthly annual charges
For 99.9% of meters in 3% if action takes
BYPL defined reading for every 0.5% or part
predefined schedule. place for <97.4% of
frequency ranging there of capped at 3%
meters
from 15 min, 30 min, penalty
60 min, daily, monthly
– for different types of
meters.
H. Prepaid Billing SLA
15. Service Level for Smart Prepaid Billing Module
Average time to <20% of total Prepaid
generate bills in a Meter- 30 Mins
Deduction of 0.2% of Maximum Penalty of
Batch window for <50% of total Prepaid
monthly annual charges 1% if action takes
number of meters on Meters – 2 Hrs
for every 1% or part there place for <98% of
a pro-rata basis
BSES

<99% of total Prepaid of capped at 1% penalty meters

(applicable on any or
Meters – 4 Hrs
all criteria)
Updating of Billing
logic as per revised Deduction of 0.2% of
Supply Code and monthly annual charges Maximum Penalty of
Within 1 week of
State Regulatory for every 1 day delay 1% if action takes
publishing of revised
Commission after 1 month or part place for more than 4
Tariff order
guidelines time to time there of capped at 1% days
during the period of penalty
service.
Deduction of 0.2% of
Maximum Penalty of
Up-dation of customer monthly annual charges
1% if action takes
ledger within the Within 10 Seconds for every 1% or part there
place for <98% of
Billing system. of Meters not updated,
meters
capped at 1% penalty
Delivery of top up
amount/ credit
Deduction of 0.5% of Maximum Penalty of
recharge in case of
99.9% meters within 10 AMISP Service Charge 3.0% if within 30
prepayment post
minutes (delivered and for delay of every 0.5% or minutes, delivery
successful transaction
intimated to consumer) part there of capped at takes place for
from payment
3.0% penalty <97.4% of meters
gateway up to
consumer interface[7]

[1]
Local intervention allowed to achieve SLAs

Page 196 of 473

[2]
Assuming interval of 30 minutes. <In case, BYPL aims to change the interval, accordingly the
performance requirement may need to be changed>
[3] Assuming interval of 30 minutes. <In case, BYPL aims to change the interval, accordingly the
performance requirement may need to be changed>
[4] All previous days from the last billing cycle

Notes:
1. Maximum Penalty out of the above shall be restricted at 20% of AMISP Service Charge. The deduction
shall be computed as AMISP Service Charge X penalty % as computed in above table
2. The penalty, as mentioned above, shall be computed as per the performance deviated from the
performance requirement. For instance, for SLA “Periodic collection of the interval load profile data for the
day”, if within 8 hours, data is received from only 94.6% meters which means deviation of 0.4%, then the
penalty shall be computed as = 0.1%.
3. Averaged over a month means weighted average performance from meter population over a predefined
time interval. For instance,
th
a. Assuming on i day or event, action was done on yi% of total meters and within stipulated time,
data was received from zi% of yi% meters. So, the average SLA over the month shall be
∑ 2× 2
computed as /∑ 2
b. For system availability, the availability is computed as Where THM is
total hours in the month when power supply to AMI system is available, S1/S2/S3 is the total non-
available hours in Severity Level-1/Level-2/ Level-3. Please refer to Annexure-I for more details
on the same.
4. AMISP shall submit AMI generated reports for cases mentioned above based on data available in Unified
HES/MDMS
5. Exclusions: Power Outages, Meter bypass by consumers, Local Temporary/ Permanent disconnection by
Utilities, Meter burnt shall be excluded from above SLA calculations. For these cases, joint visit of AMISP
and BYPL officials shall be carried out and field inspection report shall be submitted by AMISP to BYPL for
suitable action.
6. For the purpose of joint visit, AMISP shall put a request to BYPL who should allocate manpower for joint
visit within 1 working day. In case of non-allocation/ non-availability of manpower from BYPL, the report
BSES

submitted by AMISP shall be final and actionable by BYPL.

7. The penalties would be computed on the basis of performance of AMISP for a calendar month.
8. AMISP shall be responsible for collection of billing data for all Smart Meters within a week of the
scheduled periodic collection/ end of the billing period.
9. AMISP shall be responsible for reading all meter data through hand held device (HHD) for non-
communicating meters. Although, manual reading for such meters shall not be more than one month.

14.1 Duties of BYPL and AMISP during Operations and Maintenance Phase

The table in this section provides a summary definition of the roles and responsibilities
of the AMISP and the BYPL during operation and maintenance phase of the AMI
Project.
Legend:
P: This indicates who has primary responsibility to perform this function
A: This indicates who will provide assistance
F: Feedback

Item Task BYPL AMISP

1.0 Problem Identification
Root cause analysis to determine whether the fault is
1.1 F P
attributable to Hardware or Software.

Page 197 of 473

Item Task BYPL AMISP
Resolution of problems involving third party maintainer
1.2 where there is uncertainty whether the root cause is A P
hardware or software.
Issues arising out of AMI System Software Product,
1.3 Solution, Cloud, Telecom Service or RF Technology F P
partner engaged by AMISP
2.0 Software Problem Resolution
2.1 Report problem and assist with problem identification F P
Provide or recommend corrections, temporary patches,
2.2 P
workaround or other fixes to system problems F
Install and test corrections, temporary patches,
2.3 P
workarounds or other fixes to system problems F
Routine Software (including MDMS, Unified HES, BYPL
3.0
Interface, Consumer app/portal)Support
3.1 Build and maintain database, displays and reports F P
3.2 Perform system back-ups F P
3.3 Restore or reinstall software from back-ups F P
3.4 Monitor system logs (part of remote monitoring ervice) F P
3.5 Maintain system logs F P
3.6 Maintain user accounts BSES
A P
Hardware (including meter, DCUs, routers, network
4.0 operation and monitoring center etc.) Problem
Resolution
4.1 Report problem and assist with defining problem A P
Troubleshoot problem to diagnose if it is software-
4.2 related or P
F
hardware-related
Identify failed component, replace failed components in
4.3 P
the system using parts from spares inventory F
4.4 Restore operation of repaired/replaced equipment A P
5.0 Hardware Spare Parts
5.1 Manage local spares inventory F P
5.2 Replenish local spares inventory F P
6.0 Integration and Database Work At SMOC End
6.1 Field Device Integration A P
6.2 Other System Integration A P
7.0 Cyber Security Monitoring
7.1 Patch Updates F P
7.2 Cyber Security Monitoring F P

Page 198 of 473

Item Task BYPL AMISP
7.3 Annual Audits F P
7.4 Implementation of Recommendations during Audit F P
Manual Meter Read Through HHU In Case of Non-
8. A P
Communication of Smart Meters

15. Training Requirements

15.1 Training Categories

The AMISP is required to organize following categories of training for the BYPL
personnel:
a) Professional Training - This is the training for the core group of implementation
team of the BYPL. This team will comprise of members from all the Business
Functions and IT sections. Each member would be trained in the relevant function/
module. This Training would be required to be given to approximately [X]
personnel. It is the responsibility of AMISP to deliver this training. Standard
curriculum designed and agreed by the BYPL for hardware, software and network
preferably shall be arranged by the AMISP for each group. The BYPL will prefer if
a portion of the training is conducted on-site.
b) End User Training - The AMISP will provide training to the owner’s team on a
"Train the Trainer" basis. The BYPL’s team so trained will then train all of the
BYPL’s end users. It is estimated that this training will require around [X] groups,
with each group comprising of around [X] persons. These training sessions will be
required to be conducted at any of the sites. The recommended training material
can be in paper / electronic media with courses on Business Process Automation
software fundamentals, business process overview, job activity training, and
BSES

delivery options being on-line, CBTs, instructor led classrooms, etc.

15.2 Training modules

The training modules shall include but not be limited to:
a) AMI Administration & Configuration
b) AMI Installation and troubleshooting
c) Application Management and Operations
d) Database and Data Analysis Reports
e) Cyber Security
f) Smart Meter and communication technology
g) SMOC and WFMS Operations

An indicative list of training is as provided below.

Duration in weeks Total Man-weeks
Item No. of At At At At
Description
No. Trainees BYPL’s AMISP’s BYPL’s AMISP’s
facility facility facility facility
Smart Grid components
1 Hardware and Software 30 1 1 30 30
Course
Database, Report and Analytic
2 10 1 1 10 10
Building Course
3 Application Software 20 1 2 20 40
Operator training &
4 40 1 0 40 0
Maintenance course
5 Smart Meter & Communication 15 1 0 15 0

Page 199 of 473

 Duration in weeks Total Man-weeks
Item No. of At At At At
Description
No. Trainees BYPL’s AMISP’s BYPL’s AMISP’s
facility facility facility facility
network
Cyber Security Training
6 5 0 1 0 5
course
Total 120 5 5 115 85

15.3 Training Schedules

As part of the project implementation plan (refer Annexure I of this Section), the AMISP
shall draw up a training schedule in consultation with the BYPL. This will enable the
BYPL representatives gain knowledge and understanding of the activities during the
following stages of the project implementation, so that they may discharge effective
oversight and witness capabilities.
1. Pre-FAT
2. Pre-Operation Go-Live
3. Operation and Maintenance
4. End of Contract
The training modules as described in Clause 12.2 shall be distributed among these
phases of the training schedule and mutually agreed.

15.4 General Requirements

General requirement for training to be imparted is as follows:
a) Training shall be conducted by AMISP personnel who are experienced instructors
and speak understandable.
b) The AMISP shall provide training to various user groups nominated by the BYPL.
BSES

The AMISP shall provide the Training Approach in the response

c) All necessary training material shall be provided by the AMISP. Each trainee shall
receive individual copies of documents used for training. Training material shall be
organized by functional process that will serve as the training documentation for a
particular functional area.
d) Training materials, including the documents provided to the trainees as well as
handouts, shall become the property of the BYPL. The BYPL reserves the right to
copy such materials, but for in-house use only.
e) The schedule, location, detailed contents, for each course shall be finalized during
detail engineering. The number of participants in the training program may undergo
change. However, all the training courses shall preferably be conducted in single
batch. Training shall be done in batches comprising of Introduction, Basic and
Advanced categories.
f) The training will consist of a curriculum of courses to address the issues of system
operation, system troubleshooting, business-wide application, changed business
processes and general use of the new system.
g) Representatives from the AMISP, BYPL’s project management teams will be
involved throughout in the development of training strategy, training material design
and development, standards and training delivery to ensure that change
management issues are incorporated, and that training strategies and materials are
aligned to the requirements of the project and as business-specific as possible.
h) Two Engineer’s from the BYPL shall be stationed at the AMISP’s works during
development/customization of solution as per the RFP. The deputed BYPL
engineers shall be involved with the project till its completion.

Page 200 of 473

16. Tests, Inspections and Management of the Quality Assurance / Quality
Control Program

16.1 Responsibility of Tests and Inspection

Test and inspections are in the complete purview of the AMISP and its sub-vendors. It
shall be ensured that there are no conflicts in roles played between AMISP personnel
carrying out tests / inspections, and those assigned responsibilities of quality
assurance (QA) and quality control (QC).
The QA/QC organization of the AMISP shall be an independent administrative and
functional structure reporting via its manager to the AMISP’s top management. The
QA/QC manager(s) shall have the authority within the delegated areas of responsibility
to resolve all matters pertaining to quality when actual quality deviates from that stated
in the Work Statement. The personnel performing QA/QC functions shall have well-
defined responsibility, authority, and organizational freedom to identify and evaluate
quality problems and to initiate, recommend, or provide solutions during all phases of
the Contract.
The QA/QC Manager designate for the project shall be the custodian of all inspection
and test records/certificates. QA/QC Manager either directly or through its authorized
representative shall be responsible for all witness testing, approval of test records and
in general, management of the QA/QC program of the project.

The responsibility for inspections and tests is borne by the Inspections and Tests
Manager. This team is responsible for creating the various inspection and test
procedures and under the general supervision of the QA/QC Manager, conducts the
tests.

In the event any imports are required for the purposes of this AMISP Contract, such
BSES

imports shall be in accordance with all applicable laws including those issued by
Ministry of Power (Order No. No.9/16/2016-Trans-Part(2) dated 18 November 2020; as
amended and/ or modified from time to time) for testing of imports including those from
prior reference countries.

16.2 In-Process Inspection

16.2.1 Type Testing and Data Exchange Protocol Testing

Type Tests shall be defined as those tests which are to be carried out to prove the
design, process of manufacture and general conformity of the product as per BIS
standards .The Data Exchange Protocol Tests are defined as those tests which
establish compliance with DLMS/COSEM application layer. The Type Testing and the
Data Exchange Protocol Testing shall comply with the following general conditions.
a) The QA/QC Manager shall document, within scheduled period as per project plan,
copies of test reports and certificates for all the Type Tests that are specified in
the specifications and that have previously been performed. These certificates
shall apply to items and equipment that are essentially identical to those due to be
delivered under the Contract and test procedures and parameter values shall be
identical to those specified in this specification. The type tests shall be carried out
at nationally/Internationally accredited labs and type test certificates shall not be
more than three years old.
b) Type Tests shall be performed for all equipment types for which certification is not
provided as required above. If any of the type tests are required to be carried out,
the same shall be carried out by the AMISP.

Page 201 of 473

 c) For direct connected Smart Meters, the Type Tests shall follow IS 16444 read in
conjunction with IS 13779. The test schedule adopted for running the Type Tests
along with the sampling criteria and the criteria for conformity shall follow IS
13779.
d) For transformer operated Smart Meters, the Type Tests shall follow IS 16444
(Part 2) read in conjunction with IS 14697. The test schedule adopted for running
the Type Tests along with the sampling criteria and the criteria for conformity shall
follow IS 14697.
e) For pluggable NIC modules, the type tests shall be carried out with the NIC
module integrated in the field device that is meters and DCUs being supplied
under the project.
f) Type Tests and Data Exchange Protocol Tests shall be certified or performed by
nationally/internationally reputed laboratories using material and equipment data
sheets and test procedures that have been developed for the project. The test
procedures shall be formatted as in the specifications and shall include a
complete list of the applicable reference standards before commencement of test
(s).
g) The AMISP shall prepare a detailed schedule for performing all specified type
tests.
h) The AMISP shall ensure that all type tests can be completed within the time
schedule offered in its Technical Proposal.
i) In case of failure during any type test, the AMISP shall follow the conformance
criteria as laid out in corresponding standard (refer serial number c and d above)
j) For direct connected Smart Meters, the Data Exchange Protocol Tests shall follow
IS 16444 (Part 1) read in conjunction with IS 15959 (Parts 1 & 2). The sampling
criteria for running these tests shall be [one per one lakh] smart meters under
production.
k) For transformer operated Smart Meters, the Data Exchange Protocol Tests shall
BSES

follow IS 16444 (Part 2) read in conjunction with IS 15959 (Parts 1 & 3). The
sampling criteria for running these tests shall be [one per one lakh] smart meters
under production.
l) Documentation for all factory, field, and availability tests that apply to the AMI
system shall be provided in accordance with the requirements defined in this
section of specification

16.2.2 Quality Assurance and Quality Control Program

The QA/QC Manager shall maintain a Quality Assurance/Quality Control (QA/QC)
program that provides that equipment, materials and services under this specification
whether manufactured, designed or performed within the AMISP’s plant, in the field, or
at any sub-contractor’s source shall be controlled at all points necessary to assure
conformance to contractual requirements.

The program shall provide for prevention and ready detection of discrepancies and for
timely and positive corrective action. The QA/QC Manager shall document objective
evidence of quality conformance.

Instructions and records for quality assurance shall be controlled and maintained at the
system levels. The AMISP shall outline its QA/QC program plan along with any
supporting documents in the Technical Proposal and update the QA/QC program
document following site the survey.
A Quality Assurance Program of the AMISP shall cover but not be limited to the
following:
a) The organization structure for the management and implementation of the
proposed Quality Assurance Program
b) Documentation control system

Page 202 of 473

 c) Qualification data for key personnel
d) The procedure for purchase of materials, parts/components and selection of Sub-
contractors’ services including vendor analysis, source inspection, incoming raw
material inspection, verification of material purchases, etc.
e) System for shop manufacturing including process controls
f) Control of non-conforming items and system for corrective action
g) Control of calibration and testing of measuring and testing equipment
h) Inspection and test procedure for manufacture
i) System for indication and appraisal of inspection status
j) System for quality audits
k) System for authorizing release of manufactured product
l) System for maintenance of records
m) System for handling, storage and delivery
n) A Quality Plan detailing out the specific quality control procedure adopted for
controlling the quality characteristics of the product.

The QA/QC Manager shall be required to make available to the Inspection and Testing
Team, all the Quality Assurance Documents as stipulated in the Quality Plan at the
time of inspection of equipment/materials.

16.2.3 Scope and Duties of QA/QC Program Manager

The QA/QC Manager of the AMI Project shall have the right to carry out Quality Audit
and Quality Surveillance of the systems and procedures of the AMISP’s/his vendor's
Quality Management and Control Activities. The scope of the duties of the QA/QC
Manager, pursuant to the Contract, will include but not be limited to the following:
a) Review of all the AMISP’s drawings, engineering data etc.
b) Witness or authorize its representative to witness tests at the manufacturer's
works or at site, or at any place where work is performed under the Contract.
BSES

c) Inspect, accept or reject any equipment, material and work under the Contract in
accordance with the specifications.
d) Issue certificate of acceptance
e) Review and suggest modification and improvement in completion schedules from
time to time; and
f) Monitor the Quality Assurance program implementation at all stages of the works.

[Link] Test Plans & Procedures

Test plans shall be provided by the QA/QC Manager, for all tests to ensure that each
factory and field test is comprehensive and verifies all the features of the equipment
are tested.

The Inspection and Test Manager in AMISP shall prepare detail testing procedure in
line with specification. The procedure shall be modular to the extent possible, which
shall facilitate the completion of the testing in the least possible time.

During the development of test plans and test procedures for the system, emphasis
shall be placed on testing each conditional logic statement, checking error conditions,
and documenting the simulation techniques used. The test plans and test procedures
shall be modular to allow individual test segments to be repeated as necessary.

[Link].1 Test Plans

The test plans shall describe the overall test process, including the responsibilities
of individuals and the documentation of the test results. The following shall be
included in the test plans:
a) Test schedule on a day-by-day basis
b) Responsibilities of test engineer and QA/QC personnel

Page 203 of 473

 c) Record-keeping assignments, procedures, and forms
d) Procedures for monitoring, correcting, and retesting variances
e) Procedures for controlling and documenting all changes made to the hardware
and software after the start of testing
f) Block diagrams of the hardware test configuration, the external communication
channels, and any test or simulation hardware.

[Link].2 Test Procedures

The test procedures shall describe the individual tests segments and the steps
comprising each segment, particularly the methods and processes to be followed.
The test procedures in general shall include the following items:
a) Name of function to be tested;
b) References to the functional, design, user, and any other documents
describing the function;
c) List of test segments to be performed and the purpose of each test segment;
d) Set-up conditions for each test segment, including descriptions of the test
equipment;
e) Descriptions, listings, and instructions for test software tools and displays if
any;
f) Step-by-step descriptions of each test segment, including user actions for
each test step;
g) Expected results for each test segment, including pass/fail criteria;
h) Descriptions of the techniques and scenarios to be used to simulate system
field inputs and controlled equipment;
i) Copies of any certified test data to be used in lieu of testing.

[Link].3 Test Records

The complete record of all factory and field acceptance tests results shall be
BSES

maintained by the designated QA/QC Manager of AMISP. The records shall be

maintained in a logical form and shall contain all the relevant information. The test
reports shall be signed by the inspection & testing engineer and the QA/QC
representative witnessing the tests. The records shall be keyed to the test
procedures. The following items shall be included in the test records:
a) Reference to appropriate test procedure
b) Date of test
c) Description of any test conditions, input data, or user actions differing from that
described in the test procedure
d) Test results for each test segment including a pass/fail indication
e) Identification of AMISP’s test engineer and QA/QC representative.
f) Provision for comments by test engineer and QA/QC representative
g) Copies of any variance reports generated
h) Copies of reports, display copies, and any other hardcopy generated as part of
the test.

[Link].4 Reporting of variances

Starting from the dry run test period, a variance report shall be prepared by the
inspection and testing engineer each time a deviation from the requirements of this
Specification is detected in areas such as system functions, design parameters,
performance, documentation, test plans, and test procedures. Record of all such
variances and their resolution shall be maintained by the QA/QC Manager.

However, at any stage if QA/QC Manager feels that quality of variances calls for
suspension of the testing the testing shall be halted till satisfactory resolution of
variances, which may involve retesting.

Page 204 of 473

 The report shall include a complete description of the variance, including:
a) Sequential identifying number assigned to the variance
b) Date and time the variance was detected
c) Appropriate references to the test procedures and this Specification
d) Description of test conditions at the time the variance was detected
e) Identification of testing and QA/QC representatives
f) Estimated date and time when variance is expected to be fixed
g) Description of the corrective actions taken (to be completed as part of the
variance resolution process
h) Dated signature lines for the QA/QC and test representatives to signify
reporting and correction of the variance.
Each variance shall be assigned to one of three classes defining the action to
be taken to resolve the variance:
a) Class 1: Testing will immediately stop and the AMISP will evaluate and
correct the variance before testing is resumed
b) Class 2: Testing will continue, and the variance will be evaluated and
corrected by the AMISP at the end of the current session but prior to
further testing
c) Class 3: Testing will continue, and the variance will be evaluated and
corrected at a mutually agreed upon time between QA/QC Manager and
the Inspection and Testing Manager.

The class shall be assigned by the QA/QC representative.

The QA/QC Manager shall maintain and periodically distribute a variance

summary that lists for each variance the report number, a brief description of the
variance, its class, and its current status (open or resolved).
BSES

All actions taken to correct variances shall be documented on the variance report
by the AMISP. Sufficient information shall be recorded to enable QA/QC
representative to determine the need for and extent of retesting, the need for
testing interactions of the correlation with any previously tested hardware or
software, and the need for updating appropriate documentation. A variance shall
be deemed resolved after retesting has been performed satisfactorily and the test
engineer and QA/QC representatives have acknowledged correction of the
variance on the variance report.

[Link].5 Test Initiation

The following conditions must be satisfied before starting any test
a) All test plans and procedures for the test shall be available.
b) All hardware and software engineering design change orders shall be
incorporated into the system under test.
c) All relevant documentation including drawings, lists of deliverables, and
software functional and design documents, and user manuals shall be
available.
d) A complete regeneration of the software under test shall be performed
immediately prior to the start of factory testing.
e) All operating system parameters, files, and configuration information shall be
saved to archive media so that the AMI systems operating environment can be
recreated starting with an un-initialized system. The existence and
completeness of this data shall be demonstrable.
f) All database, display, and report definitions shall be saved to archive media so
that the databases, displays, and reports can be recreated if necessary.
g) The image backup of all applications of AMI Systems shall be taken on the
archive media so that AMI systems software can be regenerated if necessary.

Page 205 of 473

 h) A complete dry run of each factory test (excluding the integrated system test)
shall be conducted by the AMISP using the test plans and test procedures.

[Link] Test Completion

A test shall be deemed to be successfully completed only when:
a) All variances have been resolved
b) All test records have been documented and issued
c) QA/QC acknowledges, in writing, successful completion of the test.

16.2.4 FAT (Factory Acceptance Test)

The factory tests shall be conducted on all the equipment to be supplied under the
project. FAT6 shall include, but not be limited to the following, appropriate to the
equipment being tested:
a) Verification of all functional characteristics and requirements specified.
b) Inspection and verification of all construction, wiring, labelling, documentation and
completeness of the hardware.

Arrangements shall be made to carry out the tests for pluggable NIC modules
integrated into three different meter makes, including the make(s) of meter being
supplied by the AMISP. The slot for plugging the NIC modules in the meter shall
conform to this specification. The FAT shall be carried out on the meter and/or DCU
integrated with the NIC modules. If any on-line communication failover has been
agreed between the Utility and the AMISP, tests shall be carried out to check a
seamless failover of communication. The three makes of meters shall be checked with
NIC modules for all type of communication technologies selected for the project.

Before the start of factory testing, the QA/QC Manager shall verify that all changes
BSES

applicable to the equipment have been implemented, type test certificates and Data
Exchange Protocol Certificates (as per sampling criteria specified) are available. As a
part of the factory tests, unstructured testing shall be performed to enable proper
verification of operation of the equipment under conditions not specifically tested in the
above structured performance test. All special test facilities used during the structured
performance test shall be made available for use during unstructured testing. On the
approval of the QA/QC Manager, The Project Manager of the AMISP to inform the
schedule of PAT to Utility as soon as finalised, with changes, if any. If the Utility so
desires, it may choose to witness the FAT at its own cost.

[Link] Factory Test Requirements

a) The database displays and the report formats developed for the central system
by the AMISP shall be demonstrated and verified at the start of factory testing.
b) b) All Field Device, AMI functions, communication & networking systems as well
as performance shall be tested and demonstrated.
c) The AMISP shall also carry out testing of the standard protocol implementation
for successful integration before the FAT starts.

6
It is expected that the FAT for equipment supplies shall happen in phases of delivery. For this a test cum
development system environment shall have to be created for the AMI system, with the HES, MDM and
Database application servers installed in the target cloud data centre. This test / development system
environment shall be separate from the production environment and shall continue to serve the purpose of
development system beyond the FAT phase, for the total duration of the project.

Page 206 of 473

 It is expected that the FAT for equipment supplies shall happen in phases of delivery.
For this a test cum development system environment shall have to be created for the
AMI system, with the HES, MDM and Database application servers installed in the
target cloud data centre. This test / development system environment shall be
separate from the production environment and shall continue to serve the purpose of
development system beyond the FAT phase, for the total duration of the project
a) All hardware and software associated with AMI Systems shall be staged and
completely tested with simulated data at the AMISP's facility.
b) For smart meters, the FAT shall be governed by the Routine and Acceptance
tests as laid out in IS 13779 and IS 14697.
c) The Tests and Inspection Manager of the AMISP is responsible for conducting all
factory tests.
d) Each of the factory tests described below (i.e., Routine & Acceptance Test of
Smart Meters, the hardware integration test, the functional performance test, and
the integrated system test, unstructured tests) shall be carried out under factory
test stage.

[Link] Sample Routine & Acceptance Tests for Smart Meter

a) These tests for Smart Meters are in addition to the Type Test requirements
specified under clause 9.2.1 and the Routine and Acceptance tests that the
AMISP will carry out as a part of their FAT procedure.
b) The sample Routine and Acceptance tests as per IS 13779 and IS 14697 shall be
performed in a third-party NABL accredited laboratory. The Utility shall have the
authority of selecting the samples (in accordance with IS 13779 and IS 14697) for
carrying out the Routine and Acceptance Tests. The AMISP shall be obliged to
undertake these tests at their own cost. The conformity requirement shall follow IS
13779 and IS 14697 as the case may be.
c) The AMISP shall be responsible for packing, handing over the material to the
BSES

respective labs and ensuring transportation of the material directly from the
manufacturer's location to the Labs for testing and delivering the material to site
after successful test results are obtained. The AMISP shall be obliged to
undertake all expenditures that shall be incurred towards packing, transport,
inspection, testing charges etc.
d) The lot wise testing shall be as per following methodology:
I. Sample Routine & Acceptance Tests shall mandatorily be carried out for the
1st lot through NABL Accredited Lab, before installation commencement.
and thereafter the same can be done at discretion of utility on subsequent
lots on random basis not exceeding a total of 6 times (i.e. 1 random sample
test per 10,000 lot).
II. In addition to the above, the utility reserves the right to carry out accuracy
tests, in line with the above guidelines, in their own Meter testing Laboratory
for each lot. The sample size for such test would be [5%] of the smart
meters of each lot.
e) The material clearance for installation / commissioning of the lots under the
inspection shall only be issued post successful test results from the labs are
provided to the Utility by the AMISP.
f) Failure of lnspection/Testing
I. In case a meter fails in the test, the whole offered lot would be rejected and
complete lot of meters under inspection will be required to be replaced by
the AMISP, at its own cost.
II. If in subsequent inspection of the new lot, the meter again fails the
inspection, then the meter shall be rejected, and vendor/sub-vendor shall
also be blacklisted.

Page 207 of 473

[Link] Hardware Integration Tests

The hardware integration test shall confirm that the computer hardware conforms to
this Specification and the AMISP-supplied hardware documentation. The hardware
integration test shall be performed when the computer hardware has been installed
in the AMISP's factory. The operation of each item shall be verified as an integral
part of the system. Applicable hardware diagnostics shall be used to verify that each
hardware component is completely operational and assembled into a configuration
capable of supporting software integration and factory testing of the system.
Equipment expansion capability shall also be verified during the hardware integration
test.

[Link] Functional Performance Test

The functional performance test shall completely verify all features of the AMI
Systems hardware and software. This shall mean the suit of application software
shall be made to run on the actual CSP infrastructure integrated with the field level
hardware components, using selected communication paths. As a minimum, the
following items shall be included in the functional performance test:
a) Inspection of all equipment for conformance to drawings/document and
satisfactory construction and appearance
b) Testing of the proper functioning of all software, including test cases with normal
and exception user-entered inputs and responses
c) Simulation of local error and failure conditions
d) Verification that ultimate expansion requirements are met
e) Verification of data link interfaces with other Central systems
f) Verification of Field Device communication interfaces (with failover if any) and
data link interfaces with other central systems. This shall include the tests of
BSES

three makes of meters with different types of NIC modules.

g) Simulation of Field Device and data link communication errors and channel
failures, including incorrect check codes and random channel noise bursts
h) Testing of all user interface functions, including random tests to verify correct
database linkages
i) Simulation of hardware failures and input power failures to verify the reaction of
the system to server and device failure
j) Demonstration of all features of the database, display, and report generators and
all other software maintenance features. These shall include but not be limited to
functional features like pre-payment calculations, billing determinants, tariff
settings, energy audit, generation of NMS reports, data base maintenance
functions etc.
k) Demonstration of the software utilities, libraries, and development tools
l) Verification that the computer system meets or exceeds performance
requirements
m) Verification of the accuracy of hardware and software documentation via random
tests
n) Sample check of meter calibration accuracy and testing of spare parts.

16.2.5 Integrated System Test

The integrated system test shall verify the stability of the system hardware and
software after the functional performance test has been successfully completed.
During the integrated system test, all functions shall run concurrently and all AMISP-
supplied equipment shall operate for a continuous 100-hour period. This minimum
level of activity may be augmented, by other activities that represent normal day-to-day

Page 208 of 473

 operation of the system as long as these activities are conducted in accordance with
the documentation provided with the system. These other activities may include, but
shall not be limited to, database, display, and report modifications, software
development activities, configuration changes (including user-commanded server and
device failovers), and the execution of any function described in this Specification.

The integrated system test shall ensure that the computer system is free of improper
interactions between software and hardware while the system is operating as an
integrated unit. In case during the 100-hour period testing, un-commanded functional
restart or server or device fail occurs the test shall be extended by 24 hours each time
such a failure over occurs. Further the test shall not be conducted with the failed
device.

[Link] Unstructured Testing

Periods of unstructured testing shall be allocated to allow AMISP to verify proper

operation of the systems under conditions not specifically included in the test
procedures. Unstructured testing shall be conducted in compliance with the following
conditions:
a) A minimum of 25 percent of the actual test period shall be reserved for
unstructured test of the system
b) The AMISP's Tests & Inspection Manager along with the QA/QC representative
shall be present during unstructured test periods
c) All simulation software, test cases, and other test facilities used during the
structured portions of the factory tests shall be available for use during
unstructured testing
d) Unstructured testing shall not begin prior to the start of the functional
performance test
BSES

e) Unstructured testing shall be allowed at the discretion of QA/QC Manager both at

the end of a structured test segment and after completion of the functional
performance test.

[Link] Dispatch of Material to Site

The Material Inspection Clearance Certificate (MICC) for all hardware shall be issued
by Utility only after successful completion of FAT as per specification. For this the
QA/QC Manager of the AMISP is obliged to submit a comprehensive FAT clearance
report to the Utility. At least IO Field Devices for each protocol shall relate to each
central system and the remaining Field devices shall be simulated in the factory test
environment. The data exchange between central systems shall also be simulated in
the factory test environment.

All Equipment Suppliers/OEMs to the project shall make use of categorized Interim
Inspection Reports (CIP Clearance) from Utility to ship materials to site after
completion of FAT. CIP shall be issued by the Utility subject to specific FAT report
carried out under the responsibility of the QA/QC Manager. Categorized Interim
Inspection Report with the lowest category would mean a complete failure of FAT and
hence rejection of material. A category between the lowest and the highest, shall
mean pending actionable points of minor nature, but material deemed fit for dispatch
to site. The category of CIP shall be authorized by the QA/QC Manager and issued
by the Utility. In case where CIP is authorized by the QA/QC Manager with the
highest category (with no pending actionable points in FAT), the Utility shall issue a
Material Inspection Clearance Certificate (MICC)

Page 209 of 473

16.3 Field Installation and Integration Test (FIIT)

Before the start of the FIIT, the following steps have to be completed:

a) Sample Routine & Acceptance Tests for Smart Meters

These tests for Smart Meters may be repeated at the discretion of the BYPL on
lots received in the warehouse of the AMISP at site.

The sample Routine and Acceptance tests as per IS 13779 and IS 14697 shall be
performed in a third-party accredited laboratory. The BYPL shall have the authority
of selecting the samples (in accordance with IS 13779 and IS 14697) for carrying
out the Routine and Acceptance Tests. The AMISP shall be obliged to undertake
these tests at their own cost. The conformity requirement shall follow IS 13779 and
IS 14697 as the case may be.
b) All field level hardware which has undergone FAT shall be installed at the site and
the installation report signed off.
c) Before the installation of the first lot of field devices (meters/DCUs etc.),
a. The production hardware (servers, WS, LAN/Routers, FW, etc.) and software
shall be provisioned at the cloud data centre.
b. The IT hardware shall be installed and made functional at the SMOC with
requisite connectivity to the cloud data centre.
d) The installed field hardware shall be configured and registered in the production
environment of the cloud data centre.
e) It shall be ensured that the smart meter deployment follows a contiguous area
coverage plan. This is to mean for each installation of DT meter, attempt shall be
made to prioritize deployment of all downstream consumer meters and for each
installation of feeder meter, similar effort shall be made to prioritize deployment of
all downstream DT/Boundary meters. However, this requirement of contiguous
BSES

area coverage plan may exclude dispersed metering for certain industrial,
commercial and government consumers at non-contiguous electrical locationsas
per the scope of work

It shall be the responsibility of the AMISP to devise the FIIT tests regime. The tests
regime so developed shall be shared with the BYPL at the time of submittal of the
QA Plan. Any comments received from the BYPL shall be addressed within the
FIIT. At the minimum the following tests shall be performed.
a) Proper registration of the incoming population of field devices
b) Checking of user interface linkages with database
c) Remote configuration downloads and reading of profiles
d) If required checking of new meter readings with existing meter readings.
e) Forced event creation and communication of such events
f) Performance tests of device communication links
g) Device communication link failover

Integration tests with the MDMS in line with a use case table to be drawn up by the
AMISP. A use case table is provided in Clause 8.5of this Section for reference
purpose. Appropriate notice shall be sent to the BYPL by the QA/QC Manager
before the start of the FIIT test regimes to enable the BYPL to witness the same.

16.4 Site Acceptance Test (SAT)

Once the AMISP finalizes the SAT schedule, the QA/QC Manager shall invite the
BYPL to witness the tests as per their convenience.

SAT shall be carried out with Smart Meters/DCUs in lots as these are delivered and
passes through the Field Installation and Integration tests. The first lot to be subjected

Page 210 of 473

 to SAT shall consist of the complete cloud data centre and its hardware and software
components along with supply, installation & integration of a minimum of [5%] Smart
Meters/ DCUs (along with its related hardware and software equipment). The SAT for
remaining meter population shall be staged on monthly basis based on the monthly
supply, installation and integration of Smart Meters (along with its related hardware
and software equipment).

The AMISP shall start up and check the performance of the equipment of field
locations. All hardware shall be aligned and adjusted, interfaces to all inputs and
outputs installed, operation verified, and all test readings recorded in accordance with
the AMISP’s recommended procedures. The SAT shall exhibit generally all functions
of the equipment and duplicate factory test. All variances must be corrected prior to
the start of the SAT. The list of final tests to be carried out in the field shall be listed in
the site-testing document by the AMISP. Among others, the site testing document shall
include the following minimum performance tests:

Data Type Performance Requirement

Load Profile Data Read7
One-month block load profile for installed From 98% of the meters in 12 hours after
meters the midnight
Billing Profile Data Read8
From 98% of the meters in 12 hours after
Billing profile data for installed meters
the midnight
On-Demand Remote reads of meters
Collection of 7 days of interval energy data and
the current total accumulated energy from a From 90% of the meters in 2 minutes
selected individual meter
Remote connect / disconnect
BSES

Action to response for individual meter Less than 3 mins

Updating of data on consumer portal/ app
Action performed for active on portal
Updating of individual consumer data on portal/
consumers within 5 minutes after
app after receiving the data in MDMS
receiving the data in MDMS
Ping Response with acknowledgement/ response for selected meters
Action performed at 99.9% of meters
For installed meters
within [1] minute; and
For an individual meter Action performed within 3 seconds
Meter loss and restoration of supply
Alertto
Receiving of alert for all affected AMI meters bereceivedwithin3minutesfor60%of
meters
Meter Tamper Alerts
Receiving of alert for an individual meter Alertto bereceivedwithin 3minutes
Power Quality Alerts
Receiving of alert for an individual meter Alertto bereceivedwithin5minutes
Firmware upgrade with acknowledgement/ response for selected meters
Actionperformed at99%of meterswithin
[1] hour; and
For installed AMI meters
Actionperformedat 99.9%of meterswithin
[2]hours
Remotely altering settings in meter

7
This performance test shall be done during SAT, from second lot of meters onwards
8
This performance test shall be done during SAT, from second lot of meters onwards

Page 211 of 473

 Data Type Performance Requirement
Actionperformedat99%of meterswithin
[30] minutes; and
For installed AMI meters
Actionperformedat 99.9%of meterswithin
[1]hour
Remotely read events logs
Actionperformedat 90% ofmeters within
[30] minutes; and
For reading the full event log for installed AMI Action performed at 99% of meters within
meter 1 hour; and
Action performed at 99.9% of meters
within [6] hours.
VEE processing
For all installed meters Action performed in [15] mins
Computation of Billing Determinants
For all installed meters Action performed in [2] hours
Prepaid Recharge
Payment success to consumer
Within 5 mins
acknowledgement
Payment success to meter update Within one hour
BYPL User Interface
Manual data entry of new value appears on
Less than 6 secs
screen
Acknowledgement of any action request Within 3 secs
Display update rate 2 secs
Disaster Recovery Capability (Refer to [Link].9of this Section for details)
Recovery Time Objective (RTO) BSES [4 hours] as agreed
Recovery Point Objective (RPO) [2 hours] as agreed
On-Demand Remote reads of meters
Collection of 7 days interval energy data and
the current total accumulated energy from a
Action performed within 2 hours
group of 10% of installed base of meters
(configurable)

Interim inspection reports shall be generated if the SAT is unsuccessful at any stage
and all variances shall have to be corrected and recorded. On successful completion of
each lot of SAT a clear SAT Report shall be issued for the benefit of the BYPL. These
SAT reports shall be signed by both the Inspection and Tests Manager and the QA/QC
Manager.

16.5 User Acceptance Test

The User Acceptance test for the AMI System shall be carried out as explained below:
1. In the Implementation and Go Live Phase post integration with all AMI applications
and before Go live of the entire set of Applications hosted in the Cloud for AMI S
with all integrations.

User Acceptance testing before final Go-Live and Operation of solution would be
considered as completed when the prerequisites including but not limited to the
following are met:
a. General Conditions for both AMI System applications UAT to be completed
include, but are not limited to:
 Upgrade, customization, Service pack rollout.

Page 212 of 473

  Container image Registry and Repository upgrade with automatic upgrade of
SCC with minimum possible shutdown or downtime
 Auto security patch upgrade
 BUG fix rollout on SCC with minimum possible downtime and shutdown
 Quick deployment of Applications on Cloud for AMI System.

b. Conditions for MDMS specific UAT to be completed include, but are not limited to:
 Integration of MDMS with HES deployed on the Cloud for AMI System and
orchestration of devices by MDMS through HES.
 Integration of MDMS with Data Analytics through event streaming service bus.
 Integration of MDMS with SMOC through event streaming service bus
 Integration of MDMS with Prepaid Billing Module through event streaming
service bus
 Integration of MDMS with CIS, billing systems and other BYPL legacy systems.
Data flow from Smart Meter->HES->MDMS-> Billing System ->Data Analytics-
>SMOC including asset and key management and two-way communication
with Smart Meters
 Integration of MDMS with other IT systems of BYPL(S) (as available and
Applicable in the first deployment) such as Asset Management Systems,
Outage Management System, AMR, SCADA, customer portals and mobile
applications
 Integration of MDMS with Work Force management tool (including Material
Management System, Asset management system, PMS and inventory
management as applicable) used for AMI deployment projects demonstrating
new meter installation, consumer indexing, GIS tagging and meter
replacement activities.
BSES

c. Conditions for Prepaid Billing Module specific UAT to be completed include, but are
not limited to:
 Demonstration of entire Meter to Cash workflow
 New prepaid consumer onboarding/lifecycle for smart prepaid meters
 Recharge cycle demonstration
 Alerts showcasing for low balance and recharge
 Disconnection rules use cases
 Multiple tariff and slab managements
 Tax change rollout for selective/specific/all consumers
 Integration of Prepaid Billing Module through event streaming bus service with
MDMS
 Integration of Prepaid Billing Module with the CRM through the BYPL billing
system
 Integration of Prepaid Billing Module through event streaming bus service with
CIS & Billing system and other legacy BYPL systems
 Consumer arrears management for use case of consumers migrated from
postpaid to prepaid
 Balance management workflow for Non-communicating meters
 Customer ledger management and reconciliation management
 Integration with consumer/customer portal and payment gateways for all
existing and future use cases
 Failed recharge management
 Fraudulent practices management
 Recharge
 Tampering
 Actual Load usage as compared to Contract Demand

Page 213 of 473

d. The AMISP shall prepare the readiness environment for UAT before commencing
the UAT. The UAT shall be conducted in accordance with the test scripts approved
by BYPL. The AMISP, with support from the Bidder and BYPL, shall develop the
necessary test cases for Unit Testing, Integration Testing & System Testing and as
may be necessary and up to the satisfaction of BYPL. The Bidder shall provide the
test scripts.
e. The AMISP shall prepare the readiness environment for Stress UAT before
commencing. The Stress UAT shall be conducted in accordance with the test
scripts approved by BYPL. The AMISP, with support from the Bidder and BYPL,
shall develop the necessary test cases for Stress UAT. The Bidder shall provide
the test scripts. The Stress testing boundaries include:
 Smart Meters - 2 million for phase 1 and 10 million for phase 2
 Interval data for 15 min
 8 years of data
 All billing and reconciliations

f. All test scripts will be submitted by the Bidder and approved by BYPL before
commencing the UAT.
g. The AMISP shall be responsible for the testing processes such as such as
planning (includes preparing test plans and defining roles and their
responsibilities), preparation (consists of preparing test specification, test
environment and test data) and execution (includes testing at various levels like
unit level, integration level, system level and production etc.).
h. The AMISP shall complete Regression Testing with no major defects before
commencing the UAT. There should be no showstoppers, or high or medium
defects in the applications along with its integration at test phase. Only cosmetic
errors are acceptable before UAT.
BSES

i. During the test scenarios, for each of the business scenario, an acceptance
criterion shall be defined. Acceptance criteria include expected behaviour of the
system and its component and the expected results. Expected results form a part
of the Exit Criteria. In addition to expected result and behaviours, some conditions
should also be set true. They can be:
 Number of bugs to be discovered for a functional module. This depends on
size of the functionality and is an indicator of amount of testing done.
 If any medium or low-priority errors are outstanding - the implementation risk
must be signed off as acceptable by BYPL.
 All High Priority errors from System must be fixed and tested before Go-Live.
j. The AMISP shall also complete installation testing, security/ penetration testing
and recovery / error testing.
 Installation Testing - Testing full, partial, or upgrade install/uninstall processes.
The installation test for a release will be conducted with the objective of
demonstrating production readiness. This test is conducted after the
application has been migrated to the site. It will encompass the inventory of
configuration items and evaluation of data readiness, as well as dynamic tests
focused on basic system functionality. When necessary, a sanity test will be
performed following the installation testing. After installation, if any bug is
reported or there is non-compliance to requirements then a proper procedure
shall be followed. Any Change Request shall be reported to the supervisor
about the bug that will in turn get forwarded to Project Manager (PM). PM will
forward the List of change request to Implementing Partner After the bug is
fixed, it shall be reflected in the production copy after testing it.
 Security/Penetration Testing - How well the offered AMI applications, Cloud
system and end to end solution protects against unauthorized internal or

Page 214 of 473

 external access, wilful damage, etc. This type of testing may require
sophisticated testing techniques as per NCIIPC, Cert-IN, STQC Guidelines.
 Recovery/Error Testing - Testing how well a system recovers from crashes,
hardware failures, or other catastrophic problems.

k. The AMISP may give a notice to BYPL requesting the issue of a User Acceptance
Certificate after conducting the UAT as per the requirement of these Technical
Specifications.
l. After receipt of the AMISP’s notice, BYPL shall within a reasonable period of time
issue a User Acceptance Certificate; or notify, both the AMISP and the Bidder, in
writing of any defect for deficiencies, objection to any system development or other
reason for the failure of the UAT which in BYPL’s opinion is not in accordance with
the scope of work.
m. The AMISP shall use all reasonable endeavours to promptly remedy any defect
and/or deficiencies and/or other reasons for the failure of the UAT. Once the
AMISP has made such remedies, it shall notify BYPL, and BYPL, with the full
cooperation of the AMISP and the Bidder, shall carry out re-testing (UAT) of the
AMI Systemalong with its integration with smart meters and other (existing)
system(s).
n. Upon the successful conclusion of the UAT including successfully complying all
integration touch points, the AMISP shall notify BYPL of its request for User
Acceptance Certification for complete system along with its integration with smart
meters and existing systems at BYPL(s). BYPL shall issue the User Acceptance
Certification (singed by respective owner), in accordance with RFP or notify the
AMISP of further defects, deficiencies, or other reasons for the failure of the User
Acceptance Test. The procedure set out in this RFP shall be repeated, as
necessary, until a User Acceptance Certificate is issued.
o. Go Live shall not commence prior to the formal sign-off of User Acceptance
BSES

Testing.

16.6 System Availability Test

QA/QC Manager will be responsible for oversight of the conduct of the availability test.
The test shall consist of normal AMI Systems operations without special test
equipment or procedures.

Test records defined in the availability test plan and procedures will be maintained by
QA/QC Manager. AMISP will operate and maintain the system according to
procedures described in the AMISP documentation. QA/QC Manager shall raise
incident reports for every incident that is encountered and closed with response time,
resolution time and hold times.

AMI systems maintenance on an on-call basis shall be provided by the AMISP during
the availability test period. When on-site maintenance support is needed, qualified
AMISP personnel shall arrive at the site within maximum four (4) hours of notification
and shall keep records of the progress in problem resolution. For availability purposes,
this service response time and the associated on-site maintenance time shall be taken
into account as defined in sections of “Downtime” and “Hold time”.

The AMISP shall maintain an inventory of spare parts, which may be required to
achieve the specified availability. These spares shall be in addition to the mandatory
spares. All spare parts used during the availability test shall be drawn from AMISP’s
inventory.

Page 215 of 473

16.6.1 Downtime
Downtime occurs whenever the criteria for successful operation defined in Clause
[Link] of this Section are not satisfied. Downtime shall be measured from the start of
diagnostic procedures until full service is restored. In the event of multiple failures, the
total elapsed time for repair of all problems (regardless of the number of maintenance
personnel available) shall be counted as downtime. For onsite response the delay in
response time (more than four hours) shall be added to downtime.

16.6.2 Hold time

During the availability test, certain contingencies may occur that are beyond the control
of any stake holder. These contingencies may prevent successful operation of the
system but are not necessarily valid for the purpose of measuring AMI systems
availability. Such periods of unsuccessful operation may be declared "hold time”.
Specific instances of hold time contingencies are:
a) Scheduled Shutdown: During scheduled shutdowns, or if an equipment failure
occurs while its backup device is scheduled out-of-service, the resulting system
outage shall be hold time, provided that service can be restored according to
AMISP-specified procedures within 30 minutes.
b) Power Interruption and Environmental Excursion: Loss of power or manual
shutdown in the event of loss of environmental control shall be considered hold
time. If the system is operated during periods of power or environmental conditions
beyond those specified, any resultant downtime shall also be considered hold time.
c) Intermittent Failure: Periods during which an intermittent, recurring software or
hardware failure is experienced will be considered hold time, provided that the
AMISP is engaged in remedial action and normal functions can be restored by
AMISP-defined procedures whenever the failure occurs. Instead of accounting for
the actual intermittent downtime, one hour of downtime shall be counted for each
24 hours of otherwise successful operation while the problem persists.
BSES

d) Service Response Time: A maximum four (4) hours of hold time will be allowed for
the AMISP to respond to each call for maintenance support.
e) Corrected Design Defect: Hold time may be declared to ensure against similar
future occurrences if a failure occurs due to a defect in system design for which the
AMISP defines and implements corrective measures. In such a case, hold time
shall be allowed in increments of 24 hours to allow verification of the corrective
action.

16.6.3 Test Duration and Criteria for Acceptance

After the elapse of [120 hours] of cumulative test time, the availability shall be
calculated. Should availability falls short of specified percentage as defined in Clause
16.4of this Section, the AMISP may either (a) Continue the test by moving the starting
time of the test forward and continuing the test until the consecutive hours have been
accumulated and the specified availability has been achieved subject to maximum of 5
days, Or (b) the AMISP may restart the test for 120 hours.

To establish that all failures have been satisfactorily repaired prior to the end of the
availability test, no downtime, intermittent (hold time) failures, or more than one un-
commanded fail over shall have occurred within 48 hours of the test's conclusion.

16.6.3.1Criteria for successful operation

The AMI system shall be designed to meet the system availability as defined below:
Minimum System
[Link]. System
Availability Requirements
1. Smart Meters 99.5%
2. DCU/ AP 99.5%

Page 216 of 473

 Minimum System
[Link]. System
Availability Requirements
3. MDMS 99.5%
4. Unified HES 99.5%
5. SMOCHardware such as UPS, Router, etc. 99.5%
6. BYPL and Consumer User Interface 99.5%

The total operational time shall not include the hold time. The system shall be
considered available as long as all the requirements defined under Clause 16.6 are
available.

16.7 Operational Go Live

16.7.1 Conditions to Be Met for Operational Go Live
The Operational Go Live of the AMI system shall be considered as completion of the
SAT for [5%] or [25,000] of Smart Meters whichever is less (along with its related
hardware and software equipment) supplied installed and integrated. AMISP’s
obligations for Operational Go Live of the system shall be deemed to be met when the
following milestones are achieved:
a) Completion of training obligations pre-Operational Go-Live;
b) Installation & integration of [5%] or [25,000] Smart Meters of the respective project
as per the definition of Go-Live/ UAT specified therein whichever is less (along with
its related hardware and software equipment);
c) Successful completion of SAT for the quantity of Smart Meters as mentioned in
serial no (b) above;
d) Successful completion of system availability test for 120 (one hundred twenty)
hour. This shall be conducted on supplied systems under normal day-to-day
operating conditions. The test shall verify the reliability and integrity of the Field
devices, Central Systems, Communication & networking systems, database,
BSES

displays, report, and all communication interfaces.

e) Independent third-party cyber security audit
The Availability Test mentioned in Clause 16.6 is meant for the initial supply. For
the subsequent lots of Smart Meters along with associated equipment, only up to
SAT will be required for operationalizing the lot.

16.7.2 Certification of Operational Go Live

Following the successful completion of System Availability Tests as per Clause 16.6of
this Section, the AMISP has to submit the following documentation to the BYPL Project
Manager:
a. BYPL certification of training obligations pre-Operational Go-Live
b. SAT and resolved variance reports of initial installation phase co-signed by the
QA/QC Manager and the Inspection and Test Manager.
c. Availability and resolved incident reports of System Availability Test signed by
QA/QC Manager
d. Initial third-party Cyber Security Audit Report
e. UAT completion and signoff as per clause 16.5 of this section.

Based on these submittals the BYPL shall check for the completeness and accuracy of
the submittals and issue Operational Go Live certificate to the AMISP in not more than
[3] days from the date of submittal. Commercial operation shall be effective from the
date mentioned in this certificate.

17. Project Management

Page 217 of 473

 Prior to AMI Project Implementation, the AMISP will prepare and submit a detailed
project implementation plan, in consultation with the BYPL, to ensure smooth takeover
of existing BYPL systems and any ongoing services under the scope of the AMI
Project.

17.1 Project Implementation Plan would cover the following:

i. Understanding of BYPL and its requirement with respect to Project
implementation;
ii. Overall system architecture and system philosophy capable of scale-up;
iii. Details of proposed methodology;
iv. Schematic Diagram of Proposed System Configuration
v. Strategy for deployment of feeder-wise smart meters and communication
infrastructure
vi. Detailed bill of quantities for materials and services (including any special
equipment) necessary to meet the technical specifications, functional &
performance requirements
vii. An approach paper documenting the interfaces for integration with existing and
future applications based on the information provided by BYPL
viii. Project team structure;
ix. Line of Credit / Source of funding and supporting documents;
x. Governance framework;
xi. Resource planning and estimation;
xii. Risk planning;
xiii. Quality Assurance/ Quality Control of the Program (including Testing and
Inspection);
xiv. Data Privacy Approach
xv. Cyber Security Approach;
xvi. Site Survey result; BSES

xvii. Documents, Data Requirement Sheet, Drawing submission and approval;

xviii. Installation & Field update schedule;
xix. Repair and Maintenance Schedule including details on Spares Management;
xx. Training schedule;

17.2 Key Personnel

The AMISP shall appoint at least the following personnel dedicated for the AMI Project
a) Project Manager: She / he shall have the authority to make commitments and
decisions that are binding on the AMISP. BYPL will designate a Nodal officer to
coordinate all project activities. All communications between the BYPL and the
AMISP shall be coordinated through the project manager and nodal officer. The
project manager should be an expert in AMI Implementation including metering and
related aspects, installation and management of Smart Meters, communication
network, last mile connectivity, Unified HES and MDMS. The project managers
shall be responsible for all communications between other members of the project
staffs including sub-contractors, if any.
b) System Integration Expert: An expert in System Integration covering application
software, hardware and network installation, integration design and ability to
manage multiple partners with different skill sets in different technology domains.
c) Cyber Security Expert: An expert in cyber security related aspects covering
planning and implementing high level system security requirements, managing
data privacy and confidentiality, information flow through adequate authorizations,
threat modelling and security testing
d) Communication Protocol Expert: An expert in communication protocols and in
implementing applications using different communication technologies and
ensuring communication inter-operability across applications/functionalities

Page 218 of 473

 e) Circle In-charge: Implementation and O&M In-charge in 4 Circles of BYPL (to be
deployed as per the rollout plan for each circle)

The project manager shall be responsible for bringing in the Cyber Security expert and
Communication Protocols expert at the appropriate stage in the project as and when
required.

17.3 Progress Report

A progress report shall be prepared by the AMISP for each month against the activities
listed in the project schedule. The report shall be made available to BYPL on a
monthly basis on a mutually agreed schedule, e.g., the 5th day of each month. The
progress report shall include all the completed, ongoing and scheduled activities and
transmittals issued and received for the month. The progress report will also highlight
the risks to the project and plan for risk mitigation.

17.4 Transmittals
Every document, letter, progress report, change order, and any other written
transmissions exchanged between the AMISP and the BYPL shall be assigned a
unique transmittal number. The AMISP shall maintain a correspondence index and
assign transmittal numbers consecutively for all AMISP documents. The BYPL will
maintain a similar correspondence numbering scheme identifying documents and
correspondence that the BYPL initiates.

17.5 Review Meeting

Progress meetings shall be scheduled by the BYPL and attended by the AMISP each
reporting period to review progress of the project. Progress meetings shall be used to
review the progress report, written correspondence exchanged since the last meeting,
and open action items. The review meeting will also be used to discuss upcoming
BSES

milestones, support needed from the BYPL, risk identified by the Program team, risk
mitigation strategies and to make decisions for path forward.

The AMISP shall also attend technical meetings as and when required by the BYPL to
discuss technical aspects of the project and to review BYPL comments on documents.
When appropriate, these technical meetings shall be conducted as extensions to the
progress meetings.

17.6 Document Review and Approval Rights

To ensure that the proposed systems conform to the specific provisions and general
intent of the Specification, the AMISP shall submit documentation describing the
systems to the BYPL for review and approval.

The BYPL will respond with written comments to the AMISP within Fifteen (15)
calendar days after receipt of the documents. Documents requiring correction must be
resubmitted by the AMISP to the BYPL within fifteen (15) calendar days. The BYPL
will respond to resubmitted documents within seven (7) calendar days after receipt of
the document. No Project Implementation Schedule relief is to be implied for
documents requiring correction and resubmission to the BYPL.

The BYPL shall have the right to require the AMISP to make any necessary
documentation changes at no additional cost to the BYPL to achieve conformance with
the Specification.

To help the BYPL manage the review and approval of documents during any given
period, the AMISP shall stagger the release of documents over the time allocated in

Page 219 of 473

 the project schedule. The number and size of documents shall be factored into the
document release schedule.

18. Document Requirements

List of documents to be provided by the AMSIP to the BYPL over the entire Contract
period has been provided below. The timelines for submission along with requirement
of BYPL approval (if required) have also been provided herewith:

S. No. Documentation to be submitted Frequency Purpose9

A Pre-Operational Go-Live Phase (from the date of execution of the
Contract till the date of achievement of the Operational Go-Live of the
AMI system)
1 A checklist of all documents on which approvals Once I
from BYPL or other agencies may be required;
2 Consumer engagement plan; Once I
3 Detailed Project Implementation Plan including Once A
verification of all integrations with external
systems as mentioned in this Contract and
delineated in the approach paper created for
the purpose
4 Exit Management Plan Once A
5 Document/ drawings to indicate the following: Once I
i. Tentative location of devices/equipment for
setting up communication network with
power plan;
ii. Confirmation of adequacy of space and AC
power supply requirements.
BSES

iii. Additional items required for interconnection

with the existing/owner provided
equipment/facilities;
iv. Requirement of modification to existing
earthing arrangement of SMOC and
locations where communication equipment /
devices etc. are to be installed, if any.
6 As-Built Drawings Updated 3. I
7 Quality Assurance Plan including the test plans Once A
for each stage of Testing.
8 Type test reports Once I
9 Data Exchange Protocol Test Certificate [one Once I
per one lakh] smart meters
10 Notice to BYPL to witness Factory Acceptance Periodic I
Test
11 Acceptance Test Reports with category if any Periodic I
12 Notice to BYPL to witness Field Installation and Once I
Integration Test
13 Field Installation and Integration Test Reports Periodic I
14 Notice to BYPL to witness Site Acceptance Periodic I
Tests
15 Site Acceptance Test Reports Periodic I
16 Progress report briefing the status of installation Monthly I

9
I: Informational, no approval required from Utility, A: Approval required from Utility based on signed
documents submitted by AMISP,

Page 220 of 473

 S. No. Documentation to be submitted Frequency Purpose9
of meters and key challenges faced if any
17 Notice to BYPL to witness System Availability Once I
Test
18 System Availability Test Once I
19 Certification for Operational Go Live with Once A
following documentation:
SAT & resolved Variance Reports
Availability & resolved incident Reports
Completion of Training certificate
Third party Cyber Security Audit
Document detailing security algorithm and
security key generation method
20 High Level Design Document for all AMI Once A
applications, Network and Cloud.
21 Low Level Design Document for all AMI Once A
applications, Network and Cloud.
22 Final Scope Document Once A
23 UAT test cases for all AMI applications, Network Once A
and Cloud.
B Post-Operational Go-Live Phase (after the Operational Go-Live of the
AMI system till the end of Contract Period)
1 Monthly progress report briefing the status of Monthly I
installation of meters and key challenges faced
if any
2 Reports as mentioned in this Contract which Monthly A
includes but not limited to the following:
BSES

i. Service Level Agreement (SLA)

performance report;
ii. Monthly progress report including
problems that arise with the installed
AMI system (if any) including any cyber
security related issues and corrective
action taken by AMISP for the same.
iii. Reports mentioned in Clause 8.5 & Monthly I
Clause 11 of the Section 6
iv. Cyber Security Audit Yearly I
v. Data Privacy Audit report; Yearly I
3 Change Requests / Change Notes Periodic A
4 Change Orders Yearly A
5 Operation and maintenance manual Updated I
6 Exit Management Plan Updated A

19. Project Implementation Schedule

The Project Implementation Schedule for AMI system establishment and timelines for
Related Services milestones from date of execution of the Contract are given below:

S. No. Milestone Timeline (in months)

1 Submission of detailed Project Within [60] days from Contract
Implementation Plan giving the compliance Commencement date
sheet along with the make and model of
various infrastructure, hardware & software
that are proposed for delivery and
Page 221 of 473
 S. No. Milestone Timeline (in months)
operations incl.:
 Specification of System
 Architecture and Software Solution
2 Approval of detailed Project Within [15] days from the date
Implementation Plan by BYPL of submission of Project
Implementation Plan.
3 Installation, integration and as per phased wise plan
operationalization of 100% of Meters each specified in Clause 4 in
with related hardware, software and Section 6
equipment as per phased wise plan
specified in Clause 4 in Section 6.
4  Delivery, site installation and As per Annexure H
commissioning of Network Operations
cum Monitoring Centre with related
hardware, software and equipment;
and
 Delivery, site installation, integration
and operationalization of [5%] of Smart
Meters each with related hardware,
software and equipment and
successful operational go-live
5 Delivery, site installation, integration and As per Annexure H
operationalization of 50% of Smart Meters
each with related hardware, software and
equipment
6 Installation Milestone BSES
Within [30] months from
Contract Commencement date
7 Operational period of the AMI system From Operational Go-Live till
end of the Contract Period
8 Transfer of AMI system to the BYPL At the end of Term of the
Contract in accordance with
Exit Management Plan
provided in Clause 13.6 of
SCC in Section 5

Installation Milestone

The “Installation Milestone” is defined as the milestone when installation and

operationalisation is completed for the number of smart meters envisaged for the
project. The AMISP is expected to complete this Installation Milestone as per the table
given above. The number of smart meters envisaged may change through negative
variations provided for in the Contract as mentioned in clause 32 given in Section 6:
Project Requirements and Scope of Work. If the AMISP completes the “Installation
Milestone” ahead of schedule, then the revised date shall be accepted as the date of
achievement of “Installation Milestone”.

The BYPL shall provide necessary clearance/ approval/ permits that are to be issued
by it for initial 20% of contiguous electrical locationsfor Smart Meter deployment along
with related documentation within 6 (six) months from date of execution of this
Contract. Furthermore, the BYPL shall provide necessary clearance/ approval/ permits
to be issued by it for remaining contiguous electrical locationsas well as non-
contiguous electrical locationsfor Smart Meter deployment along with related
documentation on quarterly basis. The BYPL shall issue a Notice no later than 7 days

Page 222 of 473

of expiry of time period specified above confirming the actual number of meters for
which clearance/ approval/ permits is available. If the BYPL fails to issue the
necessary clearance and approvals or if the BYPL acknowledges that no further
consumer/feeder locations are available for deployment within the allotted time, then
the meter population for which clearance/ approval/ permits is available shall be
assumed as the number required for meeting the “Installation Milestone”.

As and when the “Installation Milestone” is achieved by the AMISP, the BYPL shall be
obliged to certify the milestone through a written communication giving the date and
the meter population installed and operationalised.

BSES

Page 223 of 473

Appendixes for Smart Meters

Appendix 1: RF Mesh Solution Details

RF Mesh Communication Solution Requirement

The engagement of RF Mesh Communication Service Provider for defined quantity of RF

Mesh Meters is in the scope of Bidder to meet the performance level as given in this RFP
document.

The selected Bidder shall implement a reliable RF Mesh communication network to create
coverage to connect smart meters in the project area. In this type of communication network,
smart meters installed in an area shall interconnect with each other using RF Mesh network
and they shall communicate with nearby Gateway/Router/Access Points to transfer data to the
backend system. In such communication network, if any Gateway/Router/Repeaters/Access
Points fails, then meters connected on that device shall automatically reconfigure the mesh
with available nearby nodes.

The solution components shall be standard based and shall conform to High degree of
information & Cyber security norms. The system security mechanisms and communication
protocols shall be based on open standards and industry standard protocols.

The RF Mesh Communication Service provider shall Design, Supply, Install, Test, and
Commission a RF Mesh Communication Infrastructure for seamless data transfer from Smart
Meters to backend AMI system.
(i) Gateway/Routers/Repeater/Access Points shall be deployed across project area to
provide RF Mesh coverage for end devices incorporating the communication nodes.
BSES

(ii) The communication network shall operate in unlicensed frequency band subject to
WPC/DOT compliance in India with valid Equipment Type Approvals (ETA) for India and
shall be remotely reprogrammable to accommodate different frequencies in the event
larger bandwidth is made available in the unlicensed band in future.
(iii) RF Mesh meters nodes shall be connected to a Gateway/ Routers/ Access Point.
(iv) In case of RF Mesh communication devices shall manage mesh network and meters
nodes and shall function as a bridge between end devices and backend applications. If
gateway/ Router/Access Point is down, then mesh nodes shall be able to connect to
adjacent available Meter node/ Gateway/ Router/ Access Point. Communication network
should be scalable, reliable, self-healing and self-configuring.
(v) Communication network shall be based on open standards with provision to send/
receive IPv6 traffic between Gateway/Routers and Head-end System.
(vi) It shall possible to send/receive traffic on IPv4 protocol between
Gateway/Routers/Access Points and NMS/HES if IPv6 support is not available.
(vii) Successful Bidder shall provide a test setup comprising of all the elements such as
gateway/ router, mesh terminals, software for testing the system during technical
evaluation. The FAT and SAT testing of all the network elements shall be demonstrated
by the Bidder to the satisfaction of the BYPL.
(viii) Bidder shall supply network management system (NMS) to monitor the performance of
the communication network. The NMS shall provide viewing of all the networking
elements deployed at site and enable configuration & parameterization of the networking
devices and the nodes.
(ix) The Bidder shall ensure that the solution offered is designed to have 100% success rate
in case of OTA firmware up-gradation on bulk smart meters simultaneously and the
Gateway/Access points shall have more than adequate memory capacity for the
Firmware upgrades and revert back to previous firmware version in case of failure
without any loss of meter data.

Page 224 of 473

(x) The quality of installation of the various equipment & power supply wiring to all field
equipment shall be as per standards/ regulations/prevailing practices of the BYPL. The
supply of electricity needed for operation and maintenance of entire Communication
system shall be the provided by BYPL.

RF Mesh Communication Network Infrastructure for Smart Meters

The RF communication network infrastructure should be based on IPV6 compliant RF mesh

network. The Communication network shall provide reliable medium for two-way
communication between network element nodes, Smart Meters & backend system. RF based
network should use license free frequency band (865-867 MHz) available in India. The
communication network shall be based on suitable standards from
ITU/IEC/IEEE/CEN/CENELEC/ETSI for NAN Technology.

The RF Communication Devices shall comply to the following standards: IEEE 802.15.4 –
IEEE standard for Information Technology – Telecommunications and Information Exchange
between Systems – Local and Metropolitan Area Networks – Specific Requirements Part 15.4:
Wireless Medium Access Control (MAC) and Physical layer (PHY); IEEE 802.15.4g – IEEE
Standard or any other equivalent standard/alliance.

The proposed RF mesh solution must have highest degree of Scalability and interoperability.
The solution components shall be standard based and shall conform to High degree of
information & Cyber security norms. The system security mechanisms and communication
protocols shall be based on open standards and industry standard protocols. Bidder shall
provide / detail out these aspects in their technical proposal:
a) Availability: The radio mesh technology shall insure an Always ON (24x7) network
which can penetrate difficult to reach locations and provide Non-Line of Sight (NLoS)
coverage through obstructions / built environment for large meter concentration.
BSES

b) Scalable Architecture: The communication architecture shall be variant -1 as defined

under IS 16444.
c) RF Mesh network shall use license free frequency band (865-867 Mhz) available in
India for smart metering application. The communication NAN modules, Gateway/Router
shall be approved by DoT/WPC and shall have desired Equipment Type Approvals (ETA)
for India.
d) Future ready and Low Life Cycle Cost: The RF NAN modules and the network element
equipment must have built-in reserve capacity to allow memory and processes to be
upgraded with new functionality over time.
e) End to End Security: The system shall be designed with a focus on security and data
integrity. The system security mechanisms and communication protocols shall be based
on open standards and protocols.
 Shall support standard security protocols and shall be compliant to the cyber security
standards and manage end to end security and data encryption. Data must be
encrypted with AES128/256 so as no tampering is possible.
 Shall support for provision of a unique certificate / key in each RF Mesh NAN Module
for mutual authentication with back-end system
 User Authorisation controls & loggings

General Requirement of RF Mesh Communication Network

a) The RF NAN modules and network devices shall register automatically to the RF Mesh
Network and reconfigure dynamically to give self-forming and self-healing capability.
b) The RF Mesh network elements like Gateway/Routers/Access Points shall simply acts as
a network passage and the meters shall dialogue directly with HES servers.

Page 225 of 473

c) Standards: The RF Mesh Communication Network solution shall be based on open
standards and comply relevant IEEE / BIS standards, Internet Engineering Task Force
(IETF) RFCs, DoT/WPC regulations:
I RF Band: It shall Operate in Unoccupied License free Spectrum (865-867
MHz)
II IEEE 802.15.4g - Standard for smart metering DISCOM networks
III IP traffic between the HES and Gateway/Router shall be IPv6 (RFC2460,
RFC6282, RFC4443)
IV IP traffic over Radio Mesh networks - 6LoWPAN (RFC6775)
V Mesh Routing: IPv6 RPL- RFC 6550 and associated RFC of Internet
Engineering Task Force (IETF)
VI Application Layer - IS 15959 Part 2 & 3 and Constrained Application Protocol
CoAP (RFC7252)
VII Transport Layer – TCP/UDP
VIII Data Security over internet - TLS / DTLS (RFC 4347 and associated)
IX The RF Network Communication NAN module and other network elements
like Gateways/ Routers / Access Point shall comply to the DoT/ WPC
regulation and must have Equipment Type Approval (ETA) from WPC. Radio
output power shall be adaptive and as per WPC recommendations. It shall not
exceed 1W.
d) The number of Smart Meters per Gateway/Routers depends upon the technology
solution/ architecture, and on level of resiliency and overall quality expected for a specific
deployment. Bidder shall indicate this number in their solution.
e) RF Mesh Technology Upgradation: The Bidder shall ensure the possibility of up-
gradation of the proposed RF Mesh Communication Infrastructure from time to time to
meet the increasing demand of the system in operation / overcoming system limitations /
bugs. The Bidder shall also ensure incorporation of new hardware (communication
BSES

devices etc.), if required, in future. The Bidder therefore shall ensure that all such
upgrades shall seamlessly fit into the existing end to end system in operation and shall
be backwardly compatible to the earlier generation devices / software / Firmware in
operation to guard against obsolescence at no cost to BYPL during the contract period.

High Availability, Load Balancing & Scalability

a) HES/NMS shall be deployed in the cloud DC & DR provided by Bidder. The HES/NMS
application shall have adequate redundancies so as to have no single point of failure.
b) The HES/ NMS must support virtualised cloud data centre environment and High-
Availability clustering for 24x7x365 availability with automatic load balancing and backup
that ensure failover and disaster recovery. System shall have the ability to recover from a
hardware or application failure. The system shall support recoverability feature using
commonly available and industry standard backup & archival applications.
c) Bidder shall ensure that the application shall be scalable both vertically and horizontally to
support more number of meters and users without compromising performance using
additional hardware.
d) Adequate data base and security features for storage of data at HES/NMS need to be
ensured.
e) Bidder shall provide a comprehensive detail on the proposed deployment architecture,
Security, scalability, and availability features. It should be noted that the Recovery Point
objective (RPO) shall be less than or equal to 2 hours and Recovery Time Objective
(RTO) shall be less than or equal to 4 hours.

Backend System (HES /NMS) Requirement

Page 226 of 473

A. System Requirements
The HES/NMS application shall be part of the RF Communication Network Infrastructure to
enable two-way communication, data collection, support/ monitoring / control of RF smart
meters automatically. The HES/NMS solution shall be suitable to support the collection
and storage of Billing profile, Daily Profile, Event data along with 15-minute interval data
for defined number of smart meters in the project area for up to 35 days. The Bidder will
require to provide technical architecture, cloud sizing required for defined no. of smart
meters. Bidder shall provide sizing of their system in staggered manner.

HES/NMS solution and shall be responsible for the establishment and management of all
radio mesh networks elements, discovery of meters, Gateways/Routers/Access points
once deployed, overall system monitoring as well as security management of underlying
network elements HES/ NMS software solution shall be able to operate with multiple
operating systems like Windows, Linux, and on multiple hypervisors.

Adequate data base and security features for storage of data need to be ensured and
industry standard database platforms like Oracle/ MS SQL/ MY SQL, etc shall be
deployed. HES database shall be accessible from application through business processes
and managed APIs.
The backend application shall support Single Sign-on and LDAP for user authentication
and authorization and shall support role-based user access. There has to be audit trail
functionality for managing and storing all the records of activities performed by
authorized/unauthorized users. The complete solution for RF smart metering Infrastructure
shall comply with stringent norms of cyber security.

B. Functional requirements
HES/NMS shall have capabilities such as Communication Network/Routing Management,
Field / End Device Management, Application Profiles, Data Management, Dashboard,
BSES

Analysis & Reporting, Data/Cyber Security, Notification Management and Audit trail.

It shall support on-demand connectivity as well as scheduled readings, power outage

event handling, alarm processing, work status monitoring and near real-time data
processing
The HES/NMS shall discover all smart meters once deployed in the field, the periodic
collection of all meter registers as well as the processing of all alarms and commands such
as connect/disconnect for those meters

The meter collection mechanism shall be robust to ensure no loss of data at application
level. It shall support collection of missing data to ensure 100% data availability
irrespective of communication connectivity challenges between backend application and
meter. Data download schedule frequency with number of retries and priority shall be
configurable for different type of meter reads / parameter set.

The HES / NMS shall support meter configuration / update for (not limiting to)

Load profile capture period

 Load/demand Limitation Configuration
 Time of Use (TOU) Configuration
 Load /demand interval Configuration
 Prepayment /Post payment Configuration
 Billing date
 Clock setting/time synchronization
 Net metering
 Meter Security Key setting
 Push and / or Pull Schedule

Page 227 of 473

 Meter Firmware Upgrade: The HES/ NMS application shall support updating of the
firmware of the meters both Unicast (one to one) and in Multicast fashion (Group of meter).

Mass Management: It shall support mass/ group management of meters for functionality
like On -Demand operations, configuration update, firmware upgrade to manage large
number on meters

The HES/ NMS shall be able to manage, monitor and control mesh network, nodes and
Routers /Gateways/ Access Points by way of receiving parameters viz. end device, RF
mesh hops, RF signal strength, Hardware/software version numbers, logs, events etc.
cetera. It shall support self-discovery and self-registration of meters upon deployment and
establishment of communication.

HES/ NMS application shall have facility to visualise Network topology of all RF mesh
meters and network element preferably on a GIS map

The RF must securely store and manage the security information related to Smart Meters.
This includes Meters Security keys and asset information for processing further business
flows. If required, meters keys to be transferred to BYPL.

The proposed RF Communication Network infrastructure system shall manage security

keys and certificates. System shall be able to report any security breach or unauthorized
communication devices logged in on the network.

It shall have security features to avoid all cyber threats like DDoS, spoofing, malwares etc.

IT must have a comprehensive built-in user authentication mechanism . The backend

BSES

systems must have user management facility, including password management. It shall be
possible to assign different user roles with specific permission for each role to access to
specific operation.
The backend system of RF Mesh Communication Network Infrastructure shall have
dashboards to monitors the performance of the underlying communications links shall
provide reports on the overall performance of the network, utilization and performance of
individual elements. There shall be an analysis window where dynamic reports can be
extracted based on logic by the system administrator or users. It shall be possible to export
the report data in a XLS, CSV format.

Bidder shall provide High Level Technical design/ deployment architecture of their
application and database including Compute, Memory, Storage, Network, security and
other requirement for deployment Infrastructure (Production, Test/development) in a
Private Cloud Infrastructure (BYPL’s Cloud service provider).

Bidder shall ensure that the backend application supports user management, authorization
and audit trail functionality for managing and storing all the transactions. The complete
solution for RF Mesh smart metering Infrastructure shall comply with stringent norms of
cyber security.

Communication Network Planning

 Bidder for RF communication service provider shall design, conduct network survey for
deployment location of Gateways/ Router/ Access points, plan, install & commission the
RF Mesh full-fledged communication network for capacity and coverage and to achieve
reliable connectivity to meter even inside building, hard to reach locations.

Page 228 of 473

 Bidder shall select most optimum locations with reliable power connection for
Gateways/Routers/Access Points to ensure maximum signal strength. The entire
infrastructure like poles & associated civil works required for installation & commission of
equipment/devices like repeaters, routers & access points shall be in the scope of Bidder.
 Mounting of Gateways/Routers/Access Points can be on wall or distribution poles, or
separate supporting structure based on the requirement. Pole mounting/wall mounting
shall be done with proper galvanized iron flats/strip to pole designed for weight of that
equipment/device. It shall be locked/sealed and protected for secured access of
authorised staff only. Field equipment/device must be protected against ingress of
water/moisture/dust/insect and weather conditions.
 Bidder for RF Mesh Communication service provider shall tune / readjust the location of
the field devices to get best performance and coverage if required at their own cost.

Solution Deployment and Integration

 Bidder shall Supply, Design, Deploy, configure, integrate and validate the offered solution
and software (HES/NMS) with MDMS and other applications as required by BYPL on the
Cloud Data Centres (DC & DR) preferably on SOA layer through API integration to ensure
two way data flow from HES/ Network Management System to UHES / MDMS / Billing
system/Other applications and vice versa.
 The backend system of RF Mesh Communication Network Infrastructure (HES/NMS) shall
support integration through APIs to exchange data with UHES/MDMS. The data exchange
models and interfaces shall comply with CIM/XML/ IEC 61968/62056.
 The integration mechanism adopted must have minimal impact on the existing systems.
The access to data will only be through applicable business rules i.e. the applications will
not access data directly without going through APIs managed by business
rules/validation/workflow.

BSES

It is envisaged that in this project the integration architecture within the solution
applications and with external system (UHES, MDMs, Billing/RMS) is be driven by open
standard based API interfaces. The system features and data shall be accessed via user
interfaces which shall work on top of these APIs. The integration mechanism/
methodology adopted must have minimal impact on the existing systems and the
interfaces shall be managed by business rules/ workflows.
 During the project duration, BYPL may ask Bidder to migrate the deployed solution
applications, database, Interfaces from the ongoing CSP’s environment to cloud
environment of another CSP. Bidder shall share the methodology, prerequisites and the
timeline for such migration in their offer.

Functional Requirements for Gateway/ Router/Access Point

a) It shall support on demand read and ping of individual/group of meters. It shall be possible
to get IPv6 ICMP request/ response and IPv6 Trace-route from the Server to any Gateway/
Routers/AP.
b) It shall push events like tamper, power off etc. to HES immediately on occurrence/receipt
from field devices/meters.
c) It shall be able to acquire and send data to HES for full capacity (as per designed for no. of
meters/field devices) to ensure the performance level
d) Device Management: It shall have device management and monitoring feature. It should
periodically upload the logs to the backend system like
 Login and Logout with Communication network,
 Firmware version,
 Alerts for events, communication failure,
 Remote firmware upgrade remote configuration etc.

Page 229 of 473

e) After power Interruption, on restoration of power supply, it shall establish communication
with underlying devices as well as upstream system (HES) automatically.
f) It shall support remote firmware upgrading as well as remote configuration.
g) The Gateway/ Router/Access Points shall have an RTC which shall maintain the time and
date information for the entire life cycle of the device, synced via Network Time Protocol
(NTP) to sub second accuracy.
h) It shall have self- diagnostic feature for logging and reporting failure of RTC, memory,
battery, communication module (NAN,WAN) etc.

Electrical/ Power Supply Requirements for Gateway/ Router/Access Point

a) Gateway/ Router shall have suitable power supply arrangement. It shall operate on three
phase or single-phase AC 50 Hz supply in Indian distribution grid condition.
b) In case of three phase supply, the operating voltage range i.e., Input of the power supply
shall be 85 V AC P-P to 500 V AC P-P. For Single phase supply the device shall operate in
range from 160V AC P-N to 370 V AC P-N. Phase Neutral interchange shall not affect the
functionality of the Gateway/ Router in any manner.
c) The Power chord shall be of at least 3 metres length and 1.2KV insulation.
d) Gateway/ Router shall be capable of withstanding surges & voltage spikes of 10 KV in the
Indian LV power condition.
e) There shall have Battery/Super Capacitor for backup for at least 4 hours to continue
operation in case of power supply failure. The life expectancy of battery shall be 126
months or more. The Battery shall be of replaceable type.

Constructional/Mechanical Requirements for – Gateway/ Router/Access Point

a) The Field network elements like Gateway/ Router/AP shall have Weather resistant outdoor
enclosure, for longer life and greater durability. The enclosure shall be Metallic/ Plastic
BSES

Casing with power supply enclosed inside. In case of plastic, it should be engineering
polymer PC/PBT with UL-VO rating.
b) Gateways/ Routers/Access Points cover and body shall have arrangements for sealing.
c) It shall have safety against fire and shall not be ignited by thermal overload or by live parts
in contact.
d) Water and dust proofing for Gateways/Routers/Access Points shall be provided and
enclosure shall be IP65 compliant. 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.
e) The Gateways/Routers/Access Points enclosure shall be fitted with one set of RF Mesh &
Cellular Antenna and shall have provision for connecting external RF Mesh and cellular
Antenna. It shall Ethernet port also.
f) Gateways/Routers/Access Points shall have the provision for visible status indicator to
provide visual indication of GW function
a. Power ON
b. Connected to RF Mesh Network
c. Data Transmission
g) Gateways/Routers/Access Points shall have suitable fixing arrangement for mounting on
the BYPL pole or light pole, as well wall mounting.

Environmental/ Operational requirements for Gateways/Routers/Access Points

a) Operating Temperature: -20 0C to +65 Deg C.
b) Storage Temperature: -40 0Cto +80 Deg C.
c) Humidity: up to 95% RH (Non-Condensing).
Testing of the Gateways/ Routers/ Access Points

Page 230 of 473

 Gateways/ Routers/Access Points shall be tested for the following:
Test Standard
Radio interference measurement CIS PR 22
Surge test IEC 610004-5
Fast transient burst test IEC 61000-4-4
Test of immunity to electrostatic discharges IEC 61000-4-2
Test of immunity to electromagnetic HF field IEC 61000-4-3
Ingress Protection for Enclosures IP-65

RF Mesh NAN Module or RF Mesh Network Interface Card (NIC)

a) RF Mesh NAN Module or NIC for the meters shall comprise of RF Mesh node with
Antenna and a Meter Interface board. It shall be the enabler for data exchange between
Smart Meter,/Gateways/ Routers/AP and back-end systems.
b) RF Mesh NAN module shall run IPv6/ 6LoWPAN communication firmware stack and shall
be assigned a unique IPv6 address to enable bi-directional IP connectivity between that
Smart Meters and HES.
c) For DLMS enabled meters (IS16444), the RF Mesh NAN module shall run the DLMS stack
for communicating and access to the full range of DLMS capabilities supported by the
meter. The data received by the RF Mesh NAN module shall be transmitted over the radio
network securely up to the HES.
d) The RF Mesh NAN module shall be designed with suitable dimension to fit in meter
pluggable slot and shall operate in the same environment as of meter. The NAN module
shall interface through compatible connector within the host smart meter
e) The RF Mesh NAN module must have necessary hardware support to deliver first breath
and last gasp as defined in IS16444 and IS15959 part 2 & 3.
BSES

f) It shall have design life twice that of warranty period.

Functional Requirements for RF Mesh NAN Module

a) RF Mesh NAN Module (NIC) shall support communication protocols as mentioned in

IS16444 and shall be interoperable at smart meter (IS16444) level for multiple make and
model.
b) NAN Module shall have persistent RF Mesh network connectivity throughout and shall
connect to RF Mesh network automatically.
c) RF Mesh NAN Module shall support two-way communications between smart meter &
Backend System for data exchange, configuration parameters exchange, alarms,
operational commands, firmware upgrade as defined in IS16444 and IS15959.
d) The NAN module shall support on-demand/ schedule (15/30 minutes, Daily, Monthly)
reading, connect/disconnect, time sync/set, configuration and over the air firmware
upgrade from the head-end system.
e) It shall support push services, alarms services of the smart meter as defined in IS16444
and IS15959 part 2 and 3.
f) NAN module shall recover from any deadlock situation immediately on its own and shall
have remote Device Management Capability such as Reset, Configuration, Log Check,
Ping, and over the air Firmware upgrade for the NIC as well interfaced meter.
g) It shall provision of a unique certificate/ key in each RF NAN Module for mutual
authentication with the NMS for security point of view. It shall support standard security
protocols and shall be compliant to the cyber security standards. Data must be encrypted
with AES 128/256.

Electrical / Power Supply Requirements for RF Mesh NAN Module

Page 231 of 473

a) RF Mesh NAN Module must be capable of operating on the power drawn from the smart
meter as defined in BIS standard of Smart meter IS 16444.
b) The power consumption of RF NAN module shall be optimal to meet the requirement of
BYPL and confirm to relevant IS.
c) There must be proper protection and isolation between smart meter and NAN module
power supply.
d) NIC module shall have LED for visual indication for Power ON, Traffic status. Antenna
interface and LED visualization should be without removing the card from the smart meter
slot.
e) The Power supply / backup requirement for RF Mesh NAN module for Last Gasp shall be
drawn from Smart Meter.
f) The RF Mesh NAN module must not exceed maximum power requirement of 7W in any
case and it shall be in line with the smart meter standard as per IS16444.

Constructional and Operational Requirement for RF NAN module

a) It shall work with PCB antenna which shall be placed inside the Plug-in module enclosure.
Antenna placement shall not interfere with smart meter functionality in any manner.
b) It shall be fitted with LED for visual indication for Power ON, Traffic status. Antenna
interface and LED visualization should be without removing the card from the smart meter
slot.
c) Environmental Operating conditions is similar to Smart meters
 Operating Temperature: -10 0Cto +60 0C.
 Storage Temperature: -20 0Cto + 70 0C.
 Humidity: up to 95% RH (Non-Condensing)

Smart Meters with RF Mesh NAN Communication Module:

BSES

The smart meter shall be fitted with a pluggable RF Mesh Communication module (NAN)
(Connectivity C2 -IS 16444). The meters fitted with RF Mesh module (NAN) NIC, shall support
RF Mesh communication technology for connectivity to HES with multiple RF Mesh meters
and RF Mesh Gateways/Routers/Access Points. The Gateways/Routers/Access Point shall be
equipped with 4G / NBIoT fallback on 2G or RF (fallback to be decided by AMISP)
Communication Technology cellular modem and Ethernet Link as back-haul connectivity with
backend HES server.
a) The HES/NMS shall provide Web Services/ API to integrate with upstream systems
(MDMS / Billing System) and other applications to retrieve data and perform all necessary
AMI operations.
b) The Bidder shall design the RF Mesh Communication Infrastructure in such a way that it
should provide the coverage for 100% RF Mesh smart meters to be installed in the project
geographical area as selected by BYPL or System Integrator.
c) The Bidder shall ensure up-gradation of the Firmware/ software in the communication
modules/ devices from remote from time to time to meet the increasing demand of the
system in operation/ overcoming system limitations/ bugs. The Bidder shall also ensure
incorporation of new hardware (communication devices, meter, NAN Module etc.), if
required, in future. The Bidder therefore shall ensure that all such upgrades shall
seamlessly fit into the existing end to end system in operation and shall be backwardly
compatible to the earlier generation devices/ software/ Firmware in operation to guard
against obsolescence at no cost to Purchaser duringthe contract period.
d) The Bidder shall ensure that the solution offered is designed to have a high success rate in
case of OTA firmware up-gradation on number of meters/communication devices
simultaneously and the Gateway/ Router/ Access points & Nodes shall have more than
adequate memory capacity for the Firmware upgrades to happen smoothly, and securely,

Page 232 of 473

 as well as, avoiding overwriting operations during the Firmware upgrades, thus avoiding
obsolescence of the hardware installed at site in quick time.
e) All network communications equipment shall support local (on-site) and remote (RF Mesh
system head end application) non-intrusive diagnostics capable of detecting any abnormal
operating parameters including, but not limited to, network communications, memory
failure, power supply failure, firmware/software problems etc.
f) The offered items shall be designed to operate in varying environments. Adequate
measures shall be taken to provide protection against contaminants, pollutants, rainwater
& moisture, lightning & short circuit, vibration and electro-magnetic interference etc. The
Bidder shall demonstrate the specified level of performance of the offered items during
well- structured factory and field tests. All equipment provided shall be designed to
interface with other equipment and shall be supporting all present requirements and spare
capacity requirement identified in the technical specifications.
g) The Bidders are advised to visit sites (at their own expense), prior to the submission of the
proposal, and make surveys and assessments as deemed necessary for proposal
submission. The successful Bidder shall be required to visit project area for detailed site
surveys for performing the design and implementation functions.

Installation of Smart Meters, Gateways/Access Points/Routers

Bidder will undertake installation work in the project area as specified by BYPL.

 The entire infrastructure & associated civil works required for installation & commissioning
of equipment/devices such as DCUs, repeaters, routers & access points etc. shall be in
the scope of the Bidder. Transportation, Storage, Installation & Commissioning of Smart
Meter with Box and accessories. All type of transportation for movement of Meter, material
and teams required for execution of work under this contract shall in the scope of Bidder.
Transportation shall include issuance of materials form designated BYPL stores, Return of
BSES

removed meters, Scrap, Movement of Field teams for installation of Meters.

 Mounting of Gateways/Routers/Access Points can be on wall or distribution poles, or
separate supporting structure based on the requirement of communication technology.
Pole mounting/wall mounting shall be done with proper galvanized iron flats/strip to pole
designed for weight of that equipment/device. It shall be locked and protected for secured
access of DISCOM staff only. Field equipment/device must be protected against ingress
of water/moisture/dust/insect and weather conditions.
 The smart meter installation shall be done by the Bidder as per the meter installation
guidelines of the BYPL and Standard Operating Procedure to be provided by BYPL. The
bidder shall carry out Meter Installation activities in the field as per defined scope of work,
wherever applicable, as per the direction of BYPL.
 Verification of meter communication with HES/NMS system.
 Removal of old meter and its return to the BYPL warehouses and Submission of Meter
Change Records in both hard and soft forms.
 The Supplied Smart meter, Meter box & Gateway/Router/Access point, Software
Applications (HES/NMS) shall be guaranteed for a period of 126 months from the date of
supply, along with operational/ service support.
 All the System Software Licenses offered by the Bidder shall be purchased under the
name of BYPL. For this project, the Licenses shall be Enterprise wide full use, perpetual
without any restriction on access/usage of any kind of functionality during the Guarantee/
maintenance support period to BYPL post completion of contract and handover all
Software Licenses (latest version deployed) to purchaser.
 Bidder to ensure relocation of gateway devices depending upon coverage
requirement/site conditions, without any cost implication to BYPL
 In future, it would be Bidder’s responsibility to integrate new meter makes having same RF
Mesh NAN Module onto the communication network infrastructure deployed under this

Page 233 of 473

 RFP if asked by BYPL. Bidder shall ensure minimum 2 makes of Meters to be integrated
and Data shall be made available on same Communication Infrastructure and system.
 Migration & Integration of Bidder’s proposed HES and/or NMS in future to a cloud
environment and HES/MDM provided by BYPL.

Key Management System of the smart meters

The HES/NMS shall have functionality to securely store and manage the security information/
certificates related to Smart Meters. This includes Device Security keys and asset information
for processing further business flow. Appropriate Security algorithm shall be put in use for
storing such keys in the database. The HES/NMS software must have a Smart meter Key
Management system, which shall allow to generate and configure all or selective security
keys.
Re-
Sr. No Key/Secret Application
programmability
1 Low Level Secret (LLS) – MR Used for reading meter data Yes
2 High Level Secret (HLS) – Used for reading and re- Yes
US programming meter setting
3 High Level Secret (HLS) – Used for Remote Firmware Yes
FU upgrade
4 Encryption Key (EK)* Used for data encryption Yes
5 Authentication Key (AK)* Used for data authentication Yes

Communication OEM/Technology Support Escrow

Continuous availability of the offered products and the maintenance are critical for Smart
Metering system’s seamless operations for its life. In case the RF Mesh communication
BSES

solution/ Technology offered in this RFP is from a RF Mesh Communication OEM/ Technology
Provider, the OEM/Technology provider must assure BYPL for their unconditional support for
the entire duration of the project and shall agree to adhere to the Escrow principles so that the
provision, maintenance, and support of Product/ Technology is available, in case RF Mesh
OEM/ Technology provider fails to fulfill its obligations or if the RF Mesh OEM/Technology
company does not remain in business.

For this purpose the RF Mesh Communication OEM/ Technology provider shall deposit the
proprietary technology including source codes of firmware, application software, security
algorithms, key/ key generation mechanism, complete hardware reference design along with
bill of materials including schematics, Gerber files and all information deemed necessary for
manufacturing the RF Mesh communication devices employed for the solution and other
materials to an escrow account with internationally recognized Escrow Agency.

SLA for RF Mesh Solution

Performance SLA Penalty

Requirement Calculation (For
Data Type Penalty
(Averaged over a understanding
month) purpose only)
A. Scheduled Tasks
1. Scheduled Interval data readings
Periodic collection From 98% of meters Deduction of 0.2% of Maximum Penalty of

Page 234 of 473

 Performance SLA Penalty
Requirement Calculation (For
Data Type Penalty
(Averaged over a understanding
month) purpose only)
of the interval load within 8 hours Bidder Service Charge 1% if action takes place
profile data for the for every 1% or part for <91% of meters
day there of capped at 1%
penalty
2. Scheduled Interval data readings
Deduction of 0.2% of
Periodic collection
Bidder Service Charge Maximum Penalty of
of the interval load From 99.9% of meters
for every 1% or part 1% if action takes place
profile data for the within 12 hours
there of capped at for <94% of meters
day
1%penalty
3. Scheduled daily meter readings
Deduction of 0.2% of
Previous days
From 99.5% of meters Bidder Service Charge Maximum Penalty of
interval energy and
within 24 hours after for every 1% or part 2% if action takes place
total accumulated
midnight there of capped at 2% for <90.5% of meters
energy
penalty
4. Scheduled billing profile data for the bill period
From 100% of meters Deduction of 0.5% of
Collection of billing within 48 hours of the Bidder Service Charge Maximum Penalty of
data for the bill scheduled periodic for every 0.5% or part 3% if action takes place
period collection/ end of the there of capped at 3% for <97.5% of meters
billing period. penalty
5. Firmware Upgrade and Rollback BSES

95% of individual
assets to be modified Deduction of 0.2% of
Actions related to (updated or rollback) Bidder Service Charge Maximum Penalty of
Firmware upgrade within 10 days of for every 1% or part 2% if action takes place
or rollback activity scheduled date there of capped at 2% for <90% of meters
(update) or requested penalty
date (rollback) and
99% of individual
assets to be (updated Deduction of 0.2% of
Actions related to or rollback) within 15 Bidder Service Charge Maximum Penalty of
Firmware upgrade days of scheduled for every 1% or part 3% if action takes place
or rollback activity date (update) or there of capped at 2% for <95% of meters
requested date penalty
(rollback)
B. Remote Actions / tasks performed by AMI System
6. For remote connect/disconnect with acknowledgement/ response for successful
recharge
Remote connect of Action performed Deduction of 0.5% of Maximum Penalty of
the AMI meters 100% of meters within Bidder Service Charge 2.0% if within 5
upon successful 5minutes for every 0.5% or part minutes, delivery takes

Page 235 of 473

 Performance SLA Penalty
Requirement Calculation (For
Data Type Penalty
(Averaged over a understanding
month) purpose only)
recharge there of capped at place for <98% of
2.0% penalty meters
7. For remote connect/disconnect with acknowledgement/ response for selected
meters
Deduction of 0.25% of Maximum Penalty of
Remote Action performed Bidder Service Charge 1.0% if within 15
connect/disconnect 100% of meters within for every 0.5% or part minutes, delivery takes
of the AMI meters 5 minutes there of capped at place for <98% of
1.0% penalty meters
8. Remotely top-up amount (for pre-paid application only)
Delivery of top up
amount/ credit
recharge in case of Deduction of 0.5% of Maximum Penalty of
99.9% meters within
prepayment post Bidder Service Charge 3.0% if within 30
15 minutes (delivered
successful for delay of every 0.5% minutes, delivery takes
and intimated to
transaction from or part there of capped place for <97.4% of
consumer)
payment gateway at 3.0% penalty meters
up to consumer
interface
C. Push Data
9. Push Alarms
Deduction of 0.5% of Maximum Penalty of
Availability of Bidder Service Charge 2.0% if within 5
90% submitted to HES
Alerts and for every 0.5% or part minutes, delivery takes
BSES

in 5 Min of Occurrence
Notification there of capped at place for <88.5% of
2.0% penalty meters
Deduction of 0.25% of Maximum Penalty of
Availability of Bidder Service Charge 1.0% if within 15
95% submitted to HES
Alerts and for every 0.5% or part minutes, delivery takes
in 5 Min of Occurrence
Notification there of capped at place for <98% of
1.0% penalty meters
D. System Availability
10. Availability of AMI System per month
Deduction of 0.4% of
Bidder Service Charge Maximum penalty of 4%
Availability of AMI for every 0.5% or part shall be deducted when
≥99.9%
System per month there of reduction in system availability is
availability capped at <95.0%
4.0% penalty
E. On Demand Actions
11. On Demand Read and Actions
Deduction of 0.25% of Maximum Penalty of
Action performed 95% Bidder Service Charge 1.0% if within 15
On Demand
of meters within 15 for every 0.5% or part minutes, delivery takes
actions
minutes there of capped at place for <90% of
1.0% penalty meters
On Demand Action performed Deduction of 0.25% of Maximum Penalty of

Page 236 of 473

 Performance SLA Penalty
Requirement Calculation (For
Data Type Penalty
(Averaged over a understanding
month) purpose only)
actions 99.5% of meters within Bidder Service Charge 1.0% if within 30
30 minutes for every 0.5% or part minutes, delivery takes
there of capped at place for <95% of
1.0% penalty meters

Appendix 2: Technical Specifications for Whole Current A.C. Single Phase Smart
Energy Meter

1. Scope of Supply

This specification covers the following for Single Phase Smart Meters of accuracy class 1.0 with
plug in communication modules suitable for cellular communication module and integrated load
control switches.
A. Design, manufacture, testing at manufacturer works before dispatch, packing, delivery
submission of all documentation.
B. Any accessories / hardware required for installation and operation for the meter.

2. Codes & standards

Materials, equipment and methods used in the manufacturing of above mentioned equipment
shall conform to the latest edition/ of following
SL Standard Number Title BSES

2.1. Indian Electricity Act IE Act 2003

CEA Metering
2.2. With latest amendments
Regulations
CBIP Manual (Pub
2.3. Standardization of AC Static Electrical Energy Meters
no.-325)
AC Static Transformer Operated Watt-hour Smart Meters, Class
2.4. IS- 16444 (Part 1)
1.0 and 2.0 Part 1 Specification
2.5. IS- 13779 AC Static Watt-hour Meters, Class 1 and 2 – Specification
Data Exchange for Electricity Meter - Reading Tariff and Load
2.6. IS-15959 (Part 1)
Control - Companion Specification
Data Exchange for Electricity Meter - Reading Tariff and Load
2.7. IS-15959 (Part 2)
Control (Part 2)- Companion Specification for smart meter
2.8. IS- 11448 Application guide for AC Electricity meters
2.9. IEC 62056-1-0 Smart metering standardisation framework
2.10. IEC 62056-3-1 Use of local area networks on twisted pair with carrier signalling
2.11. IEC 62056-4-7 DLMS/COSEM transport layer for IP networks
2.12. IEC 62056-5-3 DLMS/COSEM application layer
2.13. IEC 62056-6-1 Object Identification System (OBIS)
2.14. IEC 62056-6-2 COSEM interface classes
Mapping between the Common Information Model message
2.15. IEC 62056-6-9 profiles (IEC 61968-9) and DLMS/COSEM (IEC 62056) data
models and protocols
Wired and wireless M-Bus communication profiles for local and
2.16. IEC 62056-7-3 neighbourhood networks
2.17. IEC 62056-7-5 Local data transmission profiles for Local Networks (LN)

Page 237 of 473

 Materials, equipment and methods used in the manufacturing of above mentioned equipment
shall conform to the latest edition/ of following
The 3-layer, connection-oriented HDLC based communication
2.18. IEC 62056-7-6
profile
2.19. IEC 62056-9-7:2013 Communication profile for TCP-UDP/IP networks
2.20. IEC 62056-21:2002 Direct local data exchange
2.21. DLMS- White Book Glossary of DLMS/COSEM terms
2.22. DLMS- Blue Book COSEM meter object model and the object identification system
2.23. DLMS- Green Book Architecture and protocols to transport the model
2.24. DLMS- Yellow Book Conformance testing process
In the event of direct conflict between various order documents, the precedence of authority of
documents shall be as follows-
I Guaranteed Technical Particulars (GTP)
Ii Specification including applicable codes & standards
Iii Approved Vendor Drawings
Iv Other documents

3. Service Conditions
a. Operation range: -10 Deg C to 55 Deg C
3.1 Temperature Range b. Limit range of operation: -25 to 60 Deg C
c. Limit range of storage / transport : -25 to 70 Deg C
3.2 Relative Humidity 0 to 96 %

4. Distribution System Data

4.1 Supply 1 Phase AC, 2 wire
BSES

4.2 Voltage 240 V ± 6%

4.3 Frequency 50 Hz ± 5%
4.4 System Neutral Solidly Earthed

5. Electrical and Accuracy Requirement

1-Phase, 2 wire Static Watt-hour& Vah- hour Smart Meter
5.1 Meter Type
fitted in polycarbonate box.
5.2 Connection Direct / whole current
240V (phase to neutral) as per relevant IS. However, meter
5.3 Rated Voltage
should withstand the maximum system voltage.
5.4 Rated Current Ib -10A and Imax- 60 A
5.5 Starting current 0.2 % of base current
5.6 Rated Frequency 50Hz (+/- 5%)
1.0 for both kWh & kVAh measurement
5.7 Accuracy Class
(IS16444 Part 1 applies for both accuracy requirements)
5.8 Power Consumption As per IS 16444 (Part 1)
Imp/ unit for both kWh & kVAh measurement
5.9 Meter constant
(Bidder to specify meter constant)
Meter shall be software calibrated at factory and
5.10 Calibration modification in calibration shall not be possible at site by
any means or external influence.
5.11 Insulation Level As per IS 16444 (Part 1)
5.12 Influence of supply voltage As per IS 16444 (Part 1)
5.13 Short time over current As per IS 16444 (Part 1)
Influence of Self Heating As per IS 16444 (Part 1)
Influence of Heating As per IS 16444 (Part 1)

Page 238 of 473

 a. As per IS 16444 (Part 1)
b. Meter shall remain immune to electrostatic discharge
(upto and including 35KV) along with NIC
Electromagnetic c. The meter shall be designed in such a way that
compatibility conducted or radiated electromagnetic disturbances as
well as electrostatic discharge do not influence the
meter.
d. Meter shall be type tested for electromagnetic
compatibility.
Meter shall work within guaranteed accuracy as per IS
13779/ CBIP 325 under and after influence of following :-
a. Current Variation
b. Ambient Temperature variation
c. Voltage variation
d. Frequency variation
e. 10% third harmonic in current
f. DC and even harmonics in AC current circuit
g. Continuous (DC) “stray”magnetic induction of 67mT+/-
5%.
Limits of error due to h. Continuous (DC)“abnormal” magnetic induction of
5.18
influence quantities 0.27T+/-5%.
i. Alternating (AC) “stray’ magnetic induction of 0.5mT+/-
5%
j. Alternating (AC) “abnormal’ magnetic induction of 10mT.
k. External magnetic field 0.5 T
l. Electromagnetic HF fields
m. Radio frequency interference
BSES

n. DC immunity test
Note: BSES reserves the right to formulate any other test
method to check magnetic immunity/ logging of meter.
Meter with logging provision will be preferred.

6. Construction
6.1 General Construction of meters shall confirm to the IS 16444 (Part 1)
Material – Opaque and UV stabilized polycarbonate of grade
6.2 Base Body LEXAN 143/943 or equivalent with flammability level FV0 as per
IS 11731 (Part-2).
a. Material –Transparent / Opaque and UV stabilized
polycarbonate of grade LEXAN 143/943 or equivalent with
flammability level FV0 as per IS 11731 (Part-2).
6.3 Top Cover b. Top cover and base should be Ultrasonically/Chemically
welded.
c. Mechanism shall be provided to log event in case of top cover
is opened. Bidder shall explain its mechanism.
6.4 Terminal Block As per IS 16444 (Part 1)
a. Short terminal cover with U cut suitable for entry of 2CX25
sqmm cable.
b. Material - Transparent and UV stabilized polycarbonate of
6.5 Terminal cover grade LEXAN 143/943 or equivalent with flammability level FV0
as per IS 11731 (Part-2).
c. Provision of sealing through sealing screws.
d. The sealing screws shall be held captive in the terminal cover.

Page 239 of 473

 e. Terminal cover should have provision for cable entry from
bottom.
f. Diagram of external connections should be embossed on
terminal cover. Sticker is not acceptable.
g. Mechanism shall be provided to record an event with
occurrence and restoration in case of terminal cover is opened.
Bidder shall explain its mechanism.
a. Terminals shall be suitable upto 25 Sqmm aluminium stranded
cable& as per IS16444 (Part-1).
b. Two no’s flat head screws per terminal shall be provided
c. Material of terminals, screws and washers should be brass or
6.6 Terminals tinned copper. Terminals shall be tested for continuous current
of 120 % Imax.
d. Terminals shall be clearly marked for phase / neutral / outgoing
etc.
e. Clearances and creep age shall be as per IS 13779.
6.7 Ingress Protection IP 51 w/o Box & IP55 with Box.
Meter should have flashing LED visible from the front to represent
6.8 Test Output device energy recording, configurable for kWh &kVAh output in field /
remotely.
6.9 RTC As per IS 16444 part 1.
a. Lithium ion battery with guaranteed design life of 10 years.
6.10 Battery b. In case battery removal or total discharge, it should not affect
the working & memory of the meter except in case of single
wire power condition.
Nonvolatile memory independent of battery backup, memory
6.11 Memory
should be retained up to 10 year without any auxiliary power.
BSES

Meter shall have self-diagnostic for the following

a. Date and RTC.
Self-Diagnostic
6.12 b. Battery.
feature
c. Nonvolatile memory.
d. Display
a. Smart meter shall be equipped with integrated load control
switches to control flow of electricity to the load at the instance
of connect/ disconnect commands as per functional need of the
system.
b. Load switch for connect/ disconnect purpose shall be mounted
inside the meter with suitable arrangement.
6.13 Load Control Switch c. Load Switches shall be provided in both phase and neutral
d. The rating of switches used shall be in line with meter rating.
e. Utilization category of the load switch shall be UC1 as per IS
15884.
f. All load switches shall operate simultaneously.
g. Bidder to provide details of load switch (make, type) with
technical document.
Meter shall have an optical port with a rust resistance coated
metal ring to hold magnet of downloading probe. Optical port
6.14 Optical port
shall comply with hardware specifications provided in IEC-62056-
21.
a. Meter shall have mechanism to log communication module
Communication
6.15 removal as an event in its memory with date and time stamp.
Module
b. Communication module shall be held in a casing, which can be

Page 240 of 473

 directly plugged in the meter. Sealing screw shall be provided.
c. Module shall be hot swappable on field.
d. Communication module shall be configurable for IPV6 with
backward compatibility with IPV4
Meter shall have super capacitors to provide power supply for
communication module in the absence of power failure for last
6.16 Super capacitor gasp signal. The Super capacitor rating should be suitable for
supply power to communication module without the use of battery
backup.
a. Sealing should be in accordance with IS and CEA metering
regulations with latest amendments.
b. Sealing arrangement shall be such that sealed parts shall not
be opened without breaking the seal or sealed part itself. There
should be clear evidence of the breaking in case sealed parts
shall be opened without breaking the seal.
c. Approval shall be taken from purchaser for location of seals
and number of seals.
Meter Sealing d. Record of all seals shall be forwarded to purchaser with each
6.17
Arrangement lot.
e. Meter Body : 1 plastic seal and Hologram seal as per BSES
specs & 1 seal of meter manufacturer
f. Meter Terminal cover : 1 Plastic seal as per BSES specs
g. Meter Box : 2 plastic seal as per BSES Specifications
(All above seals provided by AMISP as per the serial no
provided by BSES )
h. Record of all seals shall be forwarded to purchaser with each
lot. BSES

a. Meter should have clearly visible, indelible and distinctly

marked name plate in accordance with IS 16444 (Part 1) &
Name Plate and
6.18 clause no. 9.0 of this specification.
marking
b. All markings and details shall be printed by laser only.
c. Paper stickers are not allowed for name plate.
Resistance against
6.19 As per IS 16444 Part 1
heat and fire
As per Appendix-2D.
6.20 Meter Enclosure
Meter shall be factory fitted in meter enclosure.
a. 10.5 years from the date of dispatch or 10 year from date of
commissioning, whichever is earlier
b. Manufacturer shall undertake a guarantee to replace meter up
6.21 Guarantee to a period of 10 Year from the date of supply. The meters
which are found defective/inoperative within the guarantee
period, these defective/inoperative meters shall be replaced
within one month of receipt of report for such
defective/inoperative meters.

7. Functional Requirement
7.1 Meter category Smart meter comply with D1 category of IS 15959 (Part 2).
It should be possible to configure meters in following modes of
metering:
7.2 Mode of metering
a. Forwarded Only: In this mode any export active energy shall
be treated as import energy and shall be recorded in forward
only register. Apparent energy calculation shall be as per
tariff basis mentioned in clause '7.4'

Page 241 of 473

 b. Bidirectional: Both Import and export energy recording shall
be applicable in this mode of metering and relevant registers
shall be updated.
Any change in metering mode shall be logged in events with
date and time stamp.
Default mode of metering shall be forwarded only until specified
otherwise.
a. Lag only: kVAh is computed based on kVArh and KWH
value. If PF=1, or leading, then kVAh = kWh. At no
instance kVAh< kWh.
7.4 kVAh Calculation
b. If required provision should be there to modify apparent
energy calculation lag + lead, same should be possible
through FOTA
Block window with default demand integration period of 1800 s
configurable to 900 s as per requirement. Meter should be
7.5 MD calculation configurable for block window at the time of manufacturing. This
change should not be possible in the field. Extended register
shall be used for MD recording.
a. Meter shall be capable of doing TOD metering in minimum 4
tariff rate registers programmable for minimum 8 time zones
and 3 seasonal profiles.
b. TOD metering shall be implemented by the activity colander
method of IS 15959 Part 1 clause 9/ DLMS UA-1000-1
c. Default TOD programming shall be as per latest DERC
guidelines. Prior approval shall also be taken from BSES for
7.6 TOD Metering the same.
d. Tariff rate registers shall be as follow
BSES

R1: Rate register for Peak

R2: Rate register for Normal
R3: Rate Register for Off Peak

Note : Meter should have provision for Special day

programming and 4 season profile if required through FOTA
All the parameters as per IS 15959 (Part 2) along with following
Instantaneous additional parameters shall be supported by meter:
7.7
Parameters a. kVAh while active import and export both in case of Net
meter
7.7.1 Association rights As per IS 15959 (Part 2).
a. Billing parameters shall be generated at the end of each
billing cycle and stored in memory as per IS 15959 (Part 2).
b. 6 no’s billing cycle parameters shall be remain in meter
memory along with current cycle parameters and shall be
available for reading as well as profile as per IS 15959 (Part
7.8 Billing data 2).
c. All the parameters mentioned in table ‘A4’ of IS 15959 (Part
2) shall be supported by meterwith following additional
parameters shall be supported by meter:
i. kVAh forwarded / while active import and export along
with TOD values
7.8.1 Association Rights As per IS 15959 (Part 2).
Support for selective access shall be provided for billing
7.8.2 Selective access
parameters as per IS 15959 (part 1).
7.8.3 Billing period reset/ 00:00 Hrs of Ist of every month

Page 242 of 473

 MD reset
Billing period reset
7.8.4 As per IS 15959 (Part 1)
mechanism
Billing period Cumulative billing period counter since installation and available
7.8.5
counter billing periods shall be provided as per IS 15959 (Part 1).
a. Load survey parameters shall be measured and recorded at
the end of each profile capture period for last 35 Power ON
days as per IS 15959.
b. All the parameters mentioned in IS 15959 (Part 2) shall be
Load survey
7.9 supported by meter along with following additional
Parameters
parameters:
a. Average Neutral Current
b. kVAh forwarded/ while active import and active export
c. Average Signal Strength
7.9.1 Association Rights As per of IS 15959 (Part 2)
Support for selective access shall be provided for billing
7.9.2 Selective Access
parameters as per IS 15959 (part 1).
Profile capture
7.9.3 Default 1800 s programmable to 900 s.
period
a. Daily load profile parameters shall be measured and recorded
at each midnight i.e. 00:00 hrs for last 35 Power ON days.
7.10 Daily load profile
b. All the parameters mentioned in table ‘A3’ of IS 15959 (Part 2)
shall be supported by meter as Daily load profile parameters.
General Purpose Following parameters shall be provided in Non Volatile memory
7.11
Parameters (NVM) of the meter as per IS 15959 (Part 2).
As per IS 15959 (Part 2) with following additional parameters.
7.11.1 Name Plate Detail
a. Month of manufacturing.
BSES

[Link] Association rights As per IS 15959 (Part 2).

a. These parameters can be programmed remotely by HES
and locally by Mobile App via proper access writes. Every
transaction shall be logged in non volatile memory of the
Programmable meter with date and time stamp.
7.11.2
parameters b. Programming of any of the parameters shall increment the
‘Cumulative programmable count’ value.
c. All the parameters mentioned in IS 15959 (Part 2) shall be
supported by meters.
[Link] Association rights As per IS 15959 (part 2)
a. Smart meter is able to automatically notify data, event, and
messages to a destination client system in an unsolicited
manner (without a request from a client) as per clause no 6
of IS 15959 (Part 2).
b. Randomization: Data from different endpoints shall be
7.11.3 Push Services pushed intelligently on the network in order to avoid
excessive traffic on the network for example in case all the
endpoints will push load survey data simultaneously, then it
may result in network choking or inefficient performance.
Therefore with the help of intelligent techniques such field
scenarios shall be handled effectively.
Meter shall be able to push following instantaneous parameters
Periodic push to HES at predefined intervals.
[Link] (Smart meter to I Device ID
HES) Ii Push setup ID
Iii Real Time clock- Date and time

Page 243 of 473

 Iv Voltage
V Phase current
Vi Neutral Current
Vii Signed Power factor
Viii Apparent power KVA
Ix Active power KW
X Cumulative Energy, KWH (Forwarded/ Import)*
Xi Cumulative energy KVAH (Forwarded/ Import)*
* In case of net meter both import and export energy shall be
provided

Other attributes as per IS 15959 (Part 2) i.e. Send Destination,

Communication window, Randomization time interval, number of
retries and repeat delay shall be decided in the event of
manufacturing.
a. Meter is able to report HES, the status change of any of the
identified events mapped in to event status word (ESW) of
size 128 bits by pushing following objects to HES.
i. Device ID
ii. Push Setup ID
iii. Real time clock- Date and Time
iv. Event Status Word 1 (ESW 1).
Event Push (Smart b. Each of the bits in ESW shall reflect the current state of the
[Link]
meter to HES) event and are mapped against each of the identified events.
c. An event status word filter (ESWF) of 128 bit shall also be
provided to configure events for event push. Events which
are supported in meter shall only be configured for event
BSES

push. Bit value 1 in ESWF shall indicate that the event is

supported and value 0 indicates that event is not supported
for event push. Position of the event bit in ESWF shall be
same as in ESW.
Event status Bit
[Link] As Per IS 15959 (Part 2)
mapping
a. Smart meter shall support remote firmware upgrade feature
for meter firmware without loss of any data and metrology.
b. Firmware upgrade shall use the Image transfer classes and
mechanisms specified in IEC62056-6-2 and IEC62056-5-3.
c. Broad cast facility shall be supported in HES for
simultaneously upgrading the firmware of a group of meters
installed in field.
7.12 Firmware upgrade d. Firmware upgrade feature shall be provided with proper
security. The design shall take into account field scenarios
such as power failure during F/W upgrade.
e. Once the firmware is upgraded, meter shall send an
acknowledgment to HES. It shall also log it as an event in its
memory.
f. The execution time of the change of the firmware within the
meter should be below 1 minute
a. The Smart meter shall support disconnection (all the
switches shall operate simultaneous) on the following
Disconnection
7.14 conditions as per IS 16444 (Part 1):
mechanism
i. Over current (105 % of Imax in any element for
predefined persistence time.)

Page 244 of 473

 ii. Load control limit (Programmable )
iii. Pre-programmed tamper conditions (Factory
programmed)
iv. Disconnection signal from Head end system.
v. Pre paid function for prepayment mode.
b. Meter shall use the disconnection control object as defined
in IS 15959 (Part 2).
a. Meter shall be able to reconnect load switches locally only
Local reconnection for Overload and load control limit disconnections as per IS
7.15
Mechanism 16444 (Part 1)
b. out and wait for 30 minutes.
a. Reconnection shall be done from HES except for over
current and load control limit. In case of failure of
[Link], reconnection shall be possible through
Reconnection
7.16 Hand Held Device (Mobile App) locally via proper security.
mechanism
Tool shall be provided for reconnection of meter locally.
b. Reconnection in case of prepayment meter shall be as per
prepayment profile.
a. Indication of status of relay i.e. connected/ disconnected
Status of load should be available on display as well as through
7.17
switch communication to HES.
b. Connection and disconnection should be logged as events.
a. Status indication of switch i.e. connected/ disconnected
should be available on display as well as through
communication to HES.
First breath and
b. In Last Gasp endpoint shall send the power outage
7.18 notification with Time Stamp. In case of power failure meter
BSES

last gasp
communication module shall not draw power from the
backup battery.
c. For the purpose of sending the Last Gasp, meter shall have
proper power backup (like a super capacitor).
7.19 Security Advanced security outlined IS 15959 (Part 1) shall be provided.
Encryption for data
7.19.1 As per 15959 (Part 2)
communication
Encryption/
7.19.2 Authentication for As per IS 15959 (Part 2)
data transport
Key requirement
7.19.3 As per IS 15959 (Part 2)
and handling
IP communication Meter shall support TCP-UDP/ IP communication profile for
7.20
profile support smart meter to HES. Please refer IS 15959.
The meter shall continue to record forward energy under any
one or combinations of the following conditions:
a. I/C & O/G Interchanged
b. Phase & Neutral Interchanged
c. I/C Neutral Disconnected, O/G Neutral & Load Connected
Connection/ To Earth.
7.22
Tamper Conditions d. I/C Neutral Disconnected, O/G Neutral Connected To Earth
Through Resistor & Load Connected To Earth.
e. I/C Neutral connected, O/G Neutral Connected to Earth
through Resistor & Load Connected to Earth.
f. I/C (Phase & Neutral) Interchanged, Load Connected To
Earth.

Page 245 of 473

 g. I/C & O/G (Phase or Neutral) Disconnected, Load
Connected To Earth.
During bidirectional mode for condition mentioned at sl no. ‘a’
meter shall record in export registers
Meter shall detect and log any exceptional/ fraud/ tamper
conditions in its memory as an event. In addition to this all
Event and tamper
7.23 transactions and control shall also be recorded as an event in
detection
meter memory. Each event type shall be identified by an event
ID as defined in IS 15959.
Each event shall be available to download as per following
association rights.
a. Public Client: No access
7.23.1 Association Rights b. Meter Reader: Read only
c. utility Settings: Read only
d. Push Services: Read Only for identified events as per
ESWF
a. Meter shall be able to log events in following compartments
i. Voltage Related Events
ii. Current Related Events
iii. Power Related Events
iv. Others Events
v. Non Roll Over Events
vi. Transaction related events
Compartments of vii. Control Events
7.23.2 b. Occurrence and Restoration of Voltage Related, current
events
related, power related and other events shall be logged in
meter memory as per IS 15959 (Part 2). Please refer
BSES

Appendix 2A for description of events, Event ID, Logics of

events and threshold values of events.
c. Threshold values shall be factory programmable.
d. Selective access shall be provided as per IS 15959 (Part 1).
e. For each occurrence event captured, the cumulative tamper
count shall be incremented.
Parameters mentioned below are to be captured when event
occurrence and restoration is logged:
a. Date and time of event
b. Event code
c. Current (Phase and Neutral)
Parameter
7.23.3
Snapshot
d. Voltage
e. Power factor
f. Cumulative energy- kWh (Forwarded/import, Export
g. Cumulative Energy kVAh (Forwarded/ active import, export)
Captured parameters are to be captured at the time of logging of
event occurrence and restoration
The meter shall log minimum 100 tamper events (ensuring at
7.23.4 Event Logging
least 20 events for each Tamper).
Appropriate Indications/Icons for all tampers should appear on
7.23.5 Tamper Indication
the meter display either continuously or in auto display mode.
a. Reading and writing data into meter memory via optical and
remote communication port shall be through DLMS security
7.24 Security
keys only.
b. Bidder shall ensure to safeguard high security keys used for

Page 246 of 473

 configuring parameters into meter.
c. Once the meter memory is locked during manufacturing
process, only parameters mentioned in IS 15959 shall be
configurable even in factory. It should not be possible to
configure any other parameters.
d. Please note that there shall be no other mechanism/ method
to interface with meter through optical and remote
communication port except mentioned in IS 15959, even for
manufacturer.
e. It should not be possible to change data stored in meter
memory even after accessing meter memory physically. In
case of any change in memory data, a flag/alert shall be
generated. Flag/Alert shall be indicated over display and in
remote communication also.

8. Meter Display
8.1 LCD Type STN/ HTN Liquid crystal with backlit
Viewing a. Minimum 120 Degree.
8.2 b. The display visibility should be sufficient to read the Meter mounted at
angle
height of 0.5 m as well as at the height of 2 m.
8.3 Size of LCD Minimum 10 mm X 5 mm
8.4 LCD Digits Total 6 +1 digits, Rollover should be at 9,99,999 units only .
LCD
8.5
language English
Following parameters should be displayed in Auto scroll with programmable
interval BSES

1. Meter Sr. No. - 5 Sec

2. Date - 5 Sec
3. Real time - 5 Sec
4. Current balance in INR (for prepaid mode) - 5 sec **
5. Current balance Date & Time - 5 sec **
6. Balance at Last Recharge (In Rupees) - 5 sec **
7. Last Recharge Amount in INR - 5 sec **
8. Last Recharge Date and time - 5 sec **
9. Cumulative kWh - 10 sec
10. Cumulative Export kWh* - 10 sec
Display 11. Net kWh* - 10 Sec
8.6 12. Cumulative kVAh - 10 Sec
mode
13. Cumulative Export kVAh* - 10 sec
14. Current month MD kW - 5 Sec
15. Current month MD kVA - 5 Sec
16. Instantaneous Voltage - 5 Sec
17. Instantaneous phase current - 5 Sec
18. Neutral current (Instantaneous value) - 5 Sec
19. Instantaneous PF - 5 Sec
20. Instantaneous kW - 5 Sec
21. Instantaneous KVA - 5 Sec
22. High Resolution value (kWh, KVAh) - 10 sec.
23. High resolution Export (kWh , KVAh)* - 10 sec
24. Top cover open date & time - 5 sec
25. Mode (Prepaid/Post-paid/Net) - 5 sec

Page 247 of 473

 26. Signal Strength - 5 sec
27. Error code - 5 sec

Note :
a. Meter with push button for manual display shall not be acceptable.
Touch button can be acceptable.
b. LCD size shall be minimum 10 mm X 5 mm with total 6+1 digits for
energy.
c. *When meter is configured in net metering mode then only these
parameters should appear otherwise these display parameters
should be disable and shall not appear on display
d. **When meter is configured in prepayment mode then only these
parameters should appear otherwise these display parameters
should be disable and shall not appear on display
Display Appropriate indications/flags for all tampers and self diagnostic features
8.7
indications should be provided (including signal strength)

9. Data and communication protocol/ HES/Integrations/ Software

a. Meter should comply Indian companion of data exchange
and tariff control specification IS 15959 (Part 2).
b. In case of additional requirement from IS 15959 (part 2),
they shall be as per DLMS standards/ IEC DLMS protocols
suite (62056).
Data Exchange
9.1 c. Bidder shall explain in detail the additional parameters/
protocol
services/ methods used in meters from IS 15959 (part 2) and
its reference to DLMS books/ IEC.
d. Prior to manufacturing of meters bidder shall provide a
BSES

detailed specification explaining all parameters/ services/

methods used in meter in addition to IS 15959 (Part 2).
Base computer
9.3 Bidder shall provide BCS software for lab testing
software (BCS)
a. The manufacturer has to provide Mobile App for
downloading all the data stored in meter memory through
optical port.
b. Mobile App should have option for selection of parameters to
be downloaded from meter
c. Meter data consisting of all parameters and complete load
survey for all parameters shall be read by HHU (Mobile App)
and data transferred to HES in minimum possible time (not
more than 5 minutes).
Hand Held Unit
9.4 Software (Mobile d. Mobile App should have option to initiate command for relay
App) connect or disconnect through optical port, this functionality
should have system control and action to be initiated only for
those meters which are scheduled / triggered from back
end application (HES/MDMS/Prepaid).
e. Mobile App should have option to initiate configuration and
firmware upgrade actions locally for non-communicated
meters as per the schedule initiated from back end
applications (HES/MDMS)
f. Mobile App should ensure the meter security keys are stored
in encrypted form and not accessible to users.
Manufacture shall impart training to BSES personnel for usage
9.5 Training
of software

Page 248 of 473

10. Name Plate
Meter Serial number shall be of 8 digits. Serial number shall be printed in black colour.
10.1
Embossing is not acceptable.
10.2 Size of the digit shall be minimum 5X3mm
10.3 Bar code shall be printed along with serial number
10.4 BIS registration mark (ISI mark)
10.5 ‘BSES’ insignia shall be printed above LCD display.
10.6 BSES PO No. & date
10.7 Manufacturers name and country of origin
10.8 Model type / number of meter
10.9 Month and Year of manufacturing
10.10 Reference voltage / current rating
The number of phases and the number of wires for which the meter is suitable.
10.11
Graphical symbol as per IS 12032 can be used.
10.12 Meter constant in Imp/ kWh and Imp/ kVAh
10.13 Class index of meter
10.14 Reference frequency
10.15 Warranty period
10.16 Symbol of load switch
Name plate of NIC
a. Serial no of NIC along/ IMEI no/MAC address with bar code
b. Name of purchaser’s
10.17
c. Communication technology with carrier frequency
d. Manufacturing year and month.
e. Warranty period.
BSES

11. Component Specification

a. The components used by manufacturer shall have
“Minimum Life” more than the 10 years.
b. Bidder should specify component specification along with
Component make and model used in offered meters in submitted
11.1 Specification technical bid documents.
c. Manufacturer should have complete tracking of material
used in meter. BSES reserve the right to carry out audit of
inventory/ manufacturing process at manufacturer’s works
and sub vendor’s work.

12. Quality Assurance, Inspection and Testing

Vendor's Quality
12.1 To be submitted for Purchaser's approval.
Plan (QP)
Sampling Method for quality checks shall be as per relevant IS/
12.2 Sampling Method IEC/ CBIP guidelines and Purchaser's prior approval shall be
taken for the same.
Inspection Hold-
12.3 To be mutually identified, agreed and approved in Quality Plan.
Points
a. The meter shall be of type tested quality including all tests
specified in this specification which are beyond IS / IEC or
CBIP.
12.4 Type Tests b. Type test conducted from CPRI/ ERDA/ or any other lab
specified by BIS/ CEA for smart meter testing will be treated
as valid.
c. Type test certificate should be submitted along with offer for
Page 249 of 473
 scrutiny.
d. Any other component supplied in addition to meter shall
also be type tested as per IS /IEC if applicable.
e. Complete type test as per IS 16444 (Part 1) shall be carried
out on sample selected from BSES lot from NABL and BIS
approved labs without any price implication.
f. Type test report shall not be older than 5 years from the
date of tender submission.
12.5 Routine tests All test marked “R” as per table 20 of IS 13779.
a. All tests marked “A” as per table 20 of IS 13779.
b. Smart meter functional tests as per IS 16444 Table 1
c. Test of load switch as per clause 10.4 of IS 16444 (Part 1)
d. Test for data exchange protocol as per clause 10.5 of IS
16444.
e. Test for Smart meter communicability as per clause no. 10.6
of IS 16444 (Part 1).
f. All the routine and acceptance tests shall be carried out as
per relevant standards.
g. Following tests in addition to IS shall be conducted during
lot inspection.
12.6 Acceptance Tests
I) Dimensional and drawing verification.
II) Display parameters/ sequence.
III) Data Downloading from handheld and PC and HES
IV) Tamper/ fraud detection/logging features as per
approved documents. Tamper conditions will be
simulated at varying load up to Imax. Accuracy will
also be checked during tamper simulation.
BSES

V) Burn in chamber test.

VI) Component verifications.
h. Purchaser reserves the right to formulate any other test
method to verify guaranteed parameters of Meter.
ESD and magnetic interference test will be conducted at Samir
ESD and Magnetic
12.7 lab, Chennai/ CPRI/ ERDA/ or any other lab specified by BIS/
Interference test
CEA for smart meter testing will be treated as valid.
a. Purchaser reserves the right to inspect /witness all tests on
the meters at Seller’s works at any time, prior to dispatch, to
verify compliance with the specification/ standards.
b. Manufacturer should have all the facilities/ equipments to
conduct all the acceptance tests as per relevant standards/
12.8 Inspection
this specification and tampers logics as per approved GTP.
All the equipments including tamper logs kits/ jigs should be
calibrated.
c. In-process and / or final inspection call intimation shall be
given in advance to purchaser.

13. Packing, Marking, Shipping, Handling and Storage

a. Each meter must be packed, together with its terminal cover, in a
separate environmental friendly cardboard box, which can be opened
and re-closed without needing adhesives.
13.1 Packing b. The box shall prevent, as much as possible, penetration of dust
during long storage periods.
c. The packaging will protect the meters against shock and vibration,
preventing damage due to the road conditions during transport and

Page 250 of 473

 distribution in the field. The electrical and mechanical properties shall
not be affected by these disturbances.

Packing for
Robust wooden non returnable packing case with all the above protection
13.2 accessories
& identification Label.
and spares
On each group box and pallet, following details are required both on front
(wide side) and top:
a. BSES logo.
b. Meter serial number range along with bar code.
c. Unique number of box/ pallet.
d. Purchaser’s name
e. PO number (along with SAP item code, if any) & date with bar code
f. Equipment Tag no. (if any)
13.3 Marking g. Destination
h. Manufacturer / Supplier’s name
i. Address of Manufacturer / Supplier / it’s agent
j. Type , rating and other description of equipment
k. Country of origin
l. Month & year of Manufacturing
m. Case measurements
n. Gross and net weights in kilograms
o. All necessary slinging and stacking instructions
Test
13.4 Routine test report to be provided with each meter
reports
BSES

The seller shall be responsible for all transit damage due to improper
13.5 Shipping
packing.
Manufacturer instruction shall be followed. Detail handling & storage
Handling
13.6 instruction sheet /manual to be furnished before commencement of
and Storage
supply.

14. Deviations
a. Deviations from this specification can· be acceptable, only where the
Seller has listed in his quotation the requirements he cannot, or does
not, wish to comply with and which deviations the Buyer has agreed to
14.1 Deviations in writing, before any order is placed.
b. In the absence of any list of deviations from the Seller, it will be
assumed by the Buyer that the Seller complies with the Specification
fully.

15. Drawing Submission

Drawing submission shall be as per the matrix given below. All documents/ drawing shall be
provided on A4 sheet in soft copy with separators for each section. Language of the documents
shall be English only. Deficient/ improper document/ drawing submission may liable for rejection
Pre
SL Detail of Document Bid Approval
Dispatch
1 Guaranteed Technical particulars (GTP) Required Required
2 Deviation Sheet, if any Required Required
3 Tamper Sheet Required Required
4 Display Parameters Required Required

Page 251 of 473

 GA / cross sectional drawing of Meter showing
5 Required Required
all the views / sections
6 Samples of each type and rating offered. 2 no's 4 no's
Environment for testing sample meters with
7 head end system to be install at BSES Required Required
premises.
Any software and accessories required for
8 Required Required
installation/ operation of meter
Manufacturer's quality assurance plan and
9 Required Required
certification for quality standards
10 Type Test reports of offered model/ type/ rating Required
11 BIS certificate Required
12 Complete product catalogue and user manual. Required
13 Customer Reference List Required
14 Recommended list of spare and accessories Required
Specification documents containing all
15 parameters, Services, Methods in addition to Required
companion specification of IS 15959 (part 2).
16 Program for production and testing (A) Required Required
Detailed installation and commissioning
18 Required Required
instructions
19 As Built Drawing Required Required
Operation and maintenance Instruction as well
20 Required Required
as trouble shooting charts/ manuals
Inspection and test reports, carried out in
21 Required
manufacturer’s works
22 Routine Test certificates BSES
Required
23 Test certificates of all bought out items Required
24 Meter Seal data Required

16. Delivery
Dispatch of Material: Vendor shall dispatch the material, only after
the Routine Tests/Final Acceptance Tests (FAT) of the material
16.1 Delivery
witnessed/waived by the Purchaser, and after receiving written
Material Dispatch Clearance (MDC) from the Purchaser.

APPENDIX 2A- GUARANTEED TECHNICAL PARTICULARS

Bidder shall furnish the GTP format with all details against each clause of this specification.
Bidder shall not change the format of GTP or clause description.
Bidder to submit duly filled GTP in hard copy format with company seal.

Clause No. Clause Description Manufacturer’s Reply

1
2
3
4
5

Bidder / Vendor seal / signature ---------------------------

Page 252 of 473

Name of the bidder
Address of the bidder
Name of contact person
Telephone number and email id

APPENDIX 2B- RECOMMENDED ACCESSORIES / SPARES

SL Description of spare part Unit Quantity

1 No
2 No

BSES

Page 253 of 473

APPENDIX 2C- TAMPER AND FRAUD DETECTION EVENTS

1. Voltage Related Events:

Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
Meter should log high voltage event if voltage is
Over Voltage (occurrence/ Occurrence: If Vpn>110% Vref Occurrence: 5 Min
7/8 above a threshold value. Threshold value is
restoration) Restoration: If Vpn<=110% Vref Restoration: 5 Min
factory programmable.
Meter should log low voltage event if voltage is
Low Voltage (occurrence/ Occurrence: If Vpn<75% Vref Occurrence: 5 Min
9/10 below a threshold value. Threshold value is
Restoration) Restoration: If Vpn<=75% Vref Restoration: 5 Min
factory programmable.

2. Current Related Events:

Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
Meter should log the event of reversal of flow of
active Power Meter should register energy Occurrence: If Ip = -ve direction
Power Reverse Occurrence: 5 Min
consumed correctly with any one, two or all
BSES

Restoration: If Ip=+ve direction

51/52 (occurrence/ Restoration) Restoration: 5 Min
three current coils reversed. This event shall not Current threshold 5%Ib
be valid in bidirectional mode of metering.
Over current (occurrence/ If the current exceeds the specified threshold Occurrence: If Ip>Imax Occurrence: 5 Min
67/68 restoration) current, meter should log over current event. Restoration: If Ip<=Imax Restoration: 5 Min
Meter shall able to detect and log of earth
loading condition if difference in phase and
neutral current found more than a specified % of
Earth Loading (occurrence/ Occurrence: If |Ip-In|>10% Ib Occurrence: 5 Min
basic current rating of meter for a specified time
69/70 restoration) Restoration: if |Ip-In|<=10% Ib Restoration: 5 Min
threshold value. This event will be restored if
this difference remain less than the specified
threshold value for a specified restoration

3. Power Related Events:

Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
Power OFF (occurrence/ Meter shall detect power OFF in case of voltage Occurrence: 5 Min
101/102
restoration) is absent.. Restoration: 5 Min

Page 254 of 473

4. Other Events:
Event Logic Expression/
Description of event Logic Of Event Persistence Time
ID Threshold values
a. Meter should either be immune or should log the
events of attempt of tampering by external magnetic
field as per relevant IS13779/ CBIP 325 with latest
amendments.
b. If the working of meter gets affected under the
influence of external magnetic field, meter should
Abnormal External record energy at Vref, Imax,UPF. Meter should not
Occurrence: 15 Sec
Magnetic Influence compute MD during this period. The meter shall As per IS 13779/ CBIP 325
201/202 Restoration: 15 Sec
(Occurrence/ Restoration) record energy as per actual load once the magnetic
field is removed.
c. Meter shall comply magnet test as per CBIP325
and shall immune to 0.5T permanent magnet test. In
case meter is not immune to 0.5T permanent
magnet test than meter shall log tamper event and
BSES

record energy at Vref*Imax*UPF load.

Neutral Disturbance- HF,
Meter should log the event when AC/DC/ Pulsating As per manufacturing Occurrence: 5 Min
DC and Alternating
203/204 voltage is injected in neutral circuit. standard. Restoration: 5 Min
(occurrence/ restoration)
Meter shall able to detect and log the low PF event if
power factor of the load found between 0.2 to 0.5 for Occurrence: 0.2<|PF|<=0.5
a load above than a % threshold value for a and Iphase >10%Ib Occurrence: 5 Min
Low Power Factor
205/206 threshold time value. Event shall restore if PF factor Restoration: (|PF|>0.5) and Restoration: 5 Min
of load remain out of range 0.2 to 0.5 for a load Iphase>10%Ib
above than % threshold value
Single Wire Operation In case of single wire power is detected, event shall If Ip or In>500 mA and Occurrence: 5 Min
207/208 (occurrence/ Restoration) be logged. Vpn<10% vref. Restoration: 5 Min
Plug in Communication Meter should log the removal of communication
module removal card. Meter should also log insertion of
209/210 (Occurrence/ Restoration) communication card. By NC switch/ sensor
Configuration change to Meter should log the change in payment mode
211/212 post-paid mode/ pre-paid configuration.

Page 255 of 473

 Event Logic Expression/
Description of event Logic Of Event Persistence Time
ID Threshold values
mode
Configuration change to
“Forwarded” only" mode/ Meter should log the change in metering mode
213/214 “Bidirectional” mode configuration.
Overload (Occurrence/
215/216 Restoration) Meter should able to log the status of overload in KW
HV Spark (Occurrence/ Meter shall remain immune/log event to electrostatic
On detection of HV
restoration) and Jammer discharge (upto and including 35KV) along with NIC
spark
test.
Meter shall log event of snapshot at a programmable When RTC =programmable
Snapshot NA
time time

5. Non roll over Events:

Event ID Event Description
251 Occurrence of cover open BSES

Relay weld - Relay contacts permanently weld

6. Transaction Events:
Event ID Detail of Transaction
151 Real Time Clock- Date and Time
152 Demand Integration Period
153 Profile Capture Period
154 Single Action schedule for billing date
155 Activity calendar for time zones
157 New firmware activated
158 Load Limit (kW) Set
159 Enable Load Limit Function
160 Disable load limit function
161 LLS secret (MR) change

Page 256 of 473

 Event ID Detail of Transaction
162 HLS key (US) change
163 HLS key (FW) change
164 Global key change
165 ESWF change
166 MD reset

7. Control Events:
Event ID Event Description
301 Load Switch Status- Disconnected
302 Load Switch Status- Connected

BSES

Page 257 of 473

APPENDIX 2D- METER ENCLOSURE
SL Clause Clause Description
Flush type with Completely transparent top cover and base with
1.0 Meter Box Type Incoming and Outgoing cable entry and data downloading
arrangement.
2.0 Design Meter box shall comply following requirement.
The meter box shall be designed in such a way that no access to
General the meter body, terminals and hardwired port of the meter shall be
2.1
Requirement possible after installation and sealing of the box without breaking
the box itself.
a. Meter box shall be theft proof i.e. meter box cannot be opened
without breaking the seals or meter itself.
2.2 Theft Protection
b. On breaking of the box, clear evidence of the physical
tempering shall be visual.
a. The meter box shall be designed in 02 parts i.e. base and top
cover.
b. Meter shall be mounted inside the base on fixed moulded
pillars by unidirectional screw.
2.3 Parts of the box
c. Meter top cover should be hinge type.
d. Cable glands and earthing bolt shall be provided at the base
as per construction requirement.
e. Proper stiffeners shall be provided in the body of the base and
top cover to provide mechanical strength against
transportation and installation vibrations.
The meter box shall be completely dust and vermin proof. Ingress
2.4 Ingress protection
protection rating of the box shall be minimum IP55.
a. A 'U' shaped groove shall be provided in the collar of the base
BSES

body, in which UV stabilized rubber 'O' shall be installed. The

design of lining shall be such that it provides proper sealing
between the cover & base of box to avoid penetration of dust
Collar of base and
2.5 and ingress of water.
cover
b. All around projection provided inside the cover periphery which
keeps the ‘O’ ring pressed.
c. An outside collar shall also be provided, which shall cover
outer surface of the collar.
a. Rubber ‘O’ Ring should be fixed with suitable adhesive so that
the same does not get removed.
2.6 Fixing of 'O' ring b. Rubber 'O' ring shall be fixed in a single piece without any gap
between open ends. Open end of the 'O' ring shall be provided
at the bottom side only.
3.0 Material The material shall be as follow:
a. The material of meter box shall be flame retardant with
inflammability level V0 having good dielectric and mechanical
strength.
b. The top Cover and Base of the box shall be made out of
3.1 Box material transparent polycarbonate with minimum 90% visibility so as to
ease installation and monitoring of box against any tampering.
The material shall be ‘UV’ stabilized to ensure that the
moulded meter box should not change in colour, shape, size or
should not get brittle after exposure to UV rays.
All the metal hardware including hinges, U latches, mounting
3.2 Hardware screws, downloading port ring etc shall be of rust proof stainless
steel.

Page 258 of 473

SL Clause Clause Description
3.3 Cable glands Polyamide Nylon-66
a. Meter box shall be constructed by moulding of polycarbonate
4.0 Construction material as specified in clause no. 3.1
b. Thickness of meter box shall be minimum 2.0 mm.
The box shall be made through Injection Moulding or better
4.1 Moulding
method.
Meter shall be factory fitted inside base body using unidirectional
screws, on fixed mounting pillars, moulded in to the base of
4.2 Base
sufficient strength, so that removing of meter shall not possible
without breaking the meter box or meter itself.
4.3 Top cover Hinge type
a. Minimum 02 no's concealed / internal hinges, not visible or
accessible from outside the box without breaking the box itself.
4.3.1 Hinge type
b. Minimum 02 no's U latches shall be provided to closed the box
with sealing arrangement at each U latch.
c. After closing the U latches no play/ gap shall exist between
base and top cover.
5.0 Padlocking The box shall also have padlocking facility.
a. 02 no's as incoming and outgoing at the 45 Deg Chamfer
bottom corners suitable for 2CX25 Sqmmarmoured aluminum
cable.
b. Cable entry must be at the bottom diagonal ends of the meter
box. Appropriate clearance shall be provided between the
6.0 Cable entry
cable entry and position of meter terminals for proper cable
bending and connection.
c. Minimum 60 mm vertical space shall be provided from the
BSES

terminals of meter to centre of cable gland to provide sufficient

bending radius and working space.
a. Two nos. of Elbow shaped glands made out of Polyamide
Nylon-66 suitable for 2CX10 / 2CX25
sqmmaluminiumarmoured cable shall be provided on both
cable entries in the box.
6.1 Cable Gland
b. Glands shall be designed in such a manner that the same
cannot be unscrewed / removed from the box from outside.
Manufacturer may either supply two nos. of check nuts or any
other alternate design to meet this requirement.
a. Earthing bolt of M6 with nut and washer shall be provided on
left side of the body of meter box.
7.0 Earthing bolt
b. The arrangement shall be such that one earth point shall be
available for customer and external earthing provided by BSES
can be terminated.
c. Necessary symbol shall be provided for earth terminal.
8.0 Mounting
a. Fixed type, moulded in to the base body as per the
Meter mounting requirement of meter mounting holes.
8.1
pillars b. Stiffnners shall be provided at the base of the mater mounting
pillars.
a. Four (4) nos. fixing holes of 6 to 6.5 mm diameter at the back
surface of box shall be provided to fix the same on flat wall.
8.2 Meter box mounting
b. Mounting holes shall not be obstructing by Incoming or
Outgoing cables.
8.3 Box Mounting 04 no's, 25 mm minimum mounting spacer moulded at the

Page 259 of 473

SL Clause Clause Description
spacers mounting holes of back surface of the meter box in order to provide
space between meter back surface and wall.
Long pan head self taping SS screws and washers shall be
Box Mounting
8.4 provided by the supplier with every box. 4 no’s plastic fixing plugs
accessories
suitable for self tapping screws shall also be provided.
a. Option 1: Slot for optical head with non removable corrosion
ferromagnetic metal ring.
b. Data downloading shall not be affected by scratches on data
downloading port or with ageing of box.
c. Data downloading shall not be affected by visible light
conditions.
d. Option 2: DB9 RS232 connector shall be provided at the top
Data Downloading
9.0 cover of box to download meter as specified in clause no. 9.1
arrangement
e. Meter shall be downloadable without opening of the box/
breaking of seals.
f. This arrangement shall not de-rate the IP rating of meter box.
g. A Top hinges and bottom sealable cover shall be provided on
the data downloading slot.
h. Data downloading shall not be affected by visible light
conditions.
Optical reader with 9 pin D-type female connector cable shall be
provided in each meter box. Push fit type protective cover with
Optical to RS232
sealing arrangement for data downloading port on the cover of the
9.1 cable (If option 2 as
meter box has to be provided. The optical meter reader with 9 pin
per clause no. 9.0
D-type female connector cable of all the meter boxes (100%) shall
be tested for meter downloading before dispatch.
BSES

Following marking shall be provided on both top cover and base by

indiligible laser printing/ screen printing or embossed from inside of
the box.
a. BSES insignia shall be embossed on the base & cover of
meter box.
10.0 Marking b. Meter serial no. (Both on base and cover of meter box)
c. Purchaser's PO no. and date.
d. Purchaser's Name.
e. Name or trade mark of seller
f. Any other detail required at the time of approval.

Page 260 of 473

Appendix 3: Technical Specifications for Whole Current A.C. Three Phase Smart
Energy Meter

1. Scope of Supply
This specification covers the following for Three Phase Whole current smart meters of accuracy
class 1.0 with plug in communication modules) and integrated load control switches.

A. Design, manufacture, testing at manufacturer works before dispatch, packing, delivery and
submission of all documentation.
B. Any accessories / hardware required for installation and operation for the meter.

2. Codes & standards

Materials, equipment and methods used in the manufacturing of above mentioned equipment shall
conform to the latest edition/ of following
S
Standard Number Title
No.
2.1. Indian Electricity Act IE Act 2003
CEA Metering
2.2. With latest amendments
Regulations
CBIP Manual (Pub
2.3. Standardization of AC Static Electrical Energy Meters
no.-325)
AC Static Direct Connected Watt-hour Smart Meters, Class 1.0
2.4. IS- 16444 (Part 1)
and 2.0 Part 1 Specification
2.5. IS- 13779 AC Static Watt-hour Meters, Class 1 and 2 – Specification
Data Exchange for Electricity Meter - Reading Tariff and Load
2.6. IS-15959 (Part 1)
Control - Companion Specification
BSES

Data Exchange for Electricity Meter - Reading Tariff and Load

2.7. IS-15959 (Part 2)
Control (Part 2)- Companion Specification for smart meter
2.8. IS- 11448 Application guide for AC Electricity meters
2.9. IEC 62056-1-0:2014 Smart metering standardization framework
2.10. IEC 62056-3-1:2013 Use of local area networks on twisted pair with carrier signaling
2.11. IEC 62056-4-7:2014 DLMS/COSEM transport layer for IP networks
2.12. IEC 62056-5-3:2017 DLMS/COSEM application layer
2.13. IEC 62056-6-1:2017 Object Identification System (OBIS)
2.14. IEC 62056-6-2:2017 COSEM interface classes
Mapping between the Common Information Model message
2.15. IEC 62056-6-9:2016 profiles (IEC 61968-9) and DLMS/COSEM (IEC 62056) data
models and protocols
Wired and wireless M-Bus communication profiles for local and
2.16. IEC 62056-7-3:2017 neighborhood networks
2.17. IEC 62056-7-5:2016 Local data transmission profiles for Local Networks (LN)
The 3-layer, connection-oriented HDLC based communication
2.18. IEC 62056-7-6:2013 profile
2.19. IEC 62056-9-7:2013 Communication profile for TCP-UDP/IP networks
2.20. IEC 62056-21:2002 Direct local data exchange
2.21. DLMS- White Book Glossary of DLMS/COSEM terms
2.22. DLMS- Blue Book COSEM meter object model and the object identification system
2.23. DLMS- Green Book Architecture and protocols to transport the model
2.24. DLMS- Yellow Book Conformance testing process
In the event of direct conflict between various order documents, the precedence of authority of
documents shall be as follows-

Page 261 of 473

Materials, equipment and methods used in the manufacturing of above mentioned equipment shall
conform to the latest edition/ of following
S
Standard Number Title
No.
I Guaranteed Technical Particulars (GTP)
Ii Specification including applicable codes & standards
Iii Approved Vendor Drawings
Iv Other documents
Order of precedence between different standards shall be as follow:
i. Indian Standards Issued By BIS until other specified in specification or approved GTP
ii. IEC standards
iii. Other standards like CBIP, DLMS ANSI etc.

3. Service Conditions
 Operation range: -10 Deg C to 55 Deg C
3.1 Temperature Range  Limit range of operation: -25 to 60 Deg C
 Limit range of storage / transport : -25 to 70 Deg C
3.2 Relative Humidity 0 to 96 %

4. Distribution System Data

4.1 Supply 3 Phase AC, 4 wire
4.2 Voltage 415 V ± 6%
4.3 Frequency 50 Hz ± 5%
4.4 System Neutral Solidly Earthed

5. Electrical and Accuracy Requirement BSES

3- ø, 4 wire Static Watt-hour and Var- Hour Smart Meter fitted in

5.1. Meter Type
polycarbonate box.
5.2. Connection Direct / whole current
240V (phase to neutral). However, meter should withstand the
5.3. Rated Voltage
maximum system voltage.
5.4. Rated Current Ib -20A and Imax- 100 A
5.5. Starting current 0.2 % of base current
5.6. Rated Frequency 50Hz +/- 5%
1.0 for both kWh & kVAh measurement
5.7. Accuracy Class
(IS16444 Part 1 applies for both accuracy requirements)
5.8. Power Consumption As per IS 16444 (Part 1)
Imp/ unit for both kWh & kVAh measurement
5.9. Meter constant
(Bidder to specify meter constant) .
Meter shall be software calibrated at factory and modification in
5.10. Calibration calibration shall not be possible at site by any means or external
influence.
5.11. Test Output Device Separate kWh & kVAh/kVArh Flashing LED visible from the front
5.12. Process Technology Surface Mounting Technology or better
5.13. Insulation Level As Per IS 16444 Part 1
Influence of supply
5.14. As Per IS 16444 Part 1
voltage
Short time over
5.15. As Per IS 16444 Part 1
current
Immunity to phase
5.16. As Per IS 16444 Part 1
and earth fault

Page 262 of 473

 Influence of Self
5.17. As Per IS 16444 Part 1
Heating
5.18. Influence of Heating As Per IS 16444 Part 1
a. As per IS 16444 (Part 1)
b. Meter shall remain immune to electrostatic discharge (upto
and including 35KV) along with NIC
Electromagnetic
5.19. c. The meter shall be designed in such a way that conducted or
compatibility
radiated electromagnetic disturbances as well as electrostatic
discharge do not influence the meter.
d. Meter shall be type tested for electromagnetic compatibility.
Meter shall work within guaranteed accuracy as per IS 13779/
CBIP325 (most stringent standard to be followed) under and after
influence of following :-
a. Current Variation
b. Ambient Temperature variation
c. Voltage variation
d. Frequency variation
e. 10% third harmonic in current
f. Reversed phase sequence
g. Voltage unbalance
h. Harmonic components in current and voltage circuit
i. DC and even harmonics in AC current circuit
Limits of error due to j. Odd harmonics in AC current circuit.
5.20. influence quantities k. Sub harmonics in AC current circuit
l. Continuous (DC) “stray” magnetic induction of 67mT+/-5%.
m. Continuous (DC) “abnormal” magnetic induction of 0.27T+/-
BSES

5%.
n. Alternating (AC) “stray’ magnetic induction of 0.5mT+/-5%
o. Alternating (AC) “abnormal’ magnetic induction of 10mT.
p. External magnetic field 0.5 T
q. Electromagnetic HF fields
r. Radio frequency interference
s. DC immunity test
Note: BSES reserves the right to formulate any other test method
to check magnetic immunity/ logging of meter. Meter with logging
provision will be preferred.

6. Construction
Material - Opaque and UV stabilized polycarbonate of grade
6.1 Base Body
LEXAN 143/ 943 or Equivalent with V0 inflammability level.
a. Material: Transparent/Opaque and UV stabilized
polycarbonate of grade LEXAN 143/ 943 or Equivalent with
V0 inflammability level. It should so be designed so as the
internal components should not be visible.
6.2 Top Cover
b. Top cover and base should be Ultrasonically/Chemically
welded.
c. Meter shall have mechanism to detect and log a event in case
top cover is opened.
a. Material - Flame retardant glass filled polycarbonate of grade
500 R or equivalent.
6.3 Terminal Block
b. Terminal block shall form Integral part of the meter base
c. Terminal block shall be capable of passing the tests as per

Page 263 of 473

 ISO-75 for a temperature of 135C and pressure of 1.8MPa.
The terminals shall be designed so as to ensure adequate
and durable contact such that there is no risk of loosening or
undue heating.
a. Material - UV stabilized transparent/Opaque Short terminal
cover with U cut suitable for entry of 2CX25 sqmm cable.
b. Material - Transparent and UV stabilized polycarbonate of
grade LEXAN 143/943 or equivalent with flammability level
FV0 as per IS 11731 (Part-2).
c. Provision of sealing through sealing screws.
d. The sealing screws shall be held captive in the terminal
6.4 Terminal cover cover.
e. Terminal cover should have provision for cable entry from
bottom.
f. Diagram of external connections should be embossed on
terminal cover. Sticker is not acceptable.
g. Mechanism shall be provided to record an event with
occurrence and restoration in case of terminal cover is
opened. Bidder shall explain its mechanism.
a. Terminals shall be suitable upto 50 Sqmm aluminium
stranded cable& as per IS16444 (Part-1).
b. Two no’s flat head screws per terminal shall be provided
c. Material of terminals, screws and washers should be brass
6.5 Terminals or tinned copper. Terminals shall be tested for continuous
current of 120 % Imax.
d. Terminals shall be clearly marked for phase / neutral /
outgoing etc.
BSES

e. Clearances and creep age shall be as per IS 13779.

6.6 Ingress Protection IP 51 w/o Box & IP55 with Box.
Meter should have flashing LED visible from the front to represent
6.7 Output device
energy recording for both kWh and kVAh
a. The meter shall have internal real time crystal clock to set
date and time.
b. Drift in time of this clock shall not be more than ±5minutes/
year at a reference temperature of 27°C.
6.8 RTC c. Meter should have capability of Time synchronization through
optical port/ remote communication.
d. Meter RTC shall be corrected automatically by the system in
synchronization to the network RTC.
e. HES will sync RTC at least once a day.
c. Lithium ion battery with guaranteed design life of 10 years.
In case battery removal or total discharge, it should not affect the
6.9 Battery
working & memory of the meter except in case of single wire
power condition.
Nonvolatile memory independent of battery backup, memory
6.10 Memory
should be retained up to 10 year without any auxiliary power.
Meter shall have self diagnostic for the following
a. Date and RTC.
Self Diagnostic
6.11 b. Battery.
feature
c. Non volatile memory.
d. Display
6.12 Load Control Switch
a. Smart meter shall be equipped with integrated load control
switches to control flow of electricity to the load at the
Page 264 of 473
 instance of connect/ disconnect commands as per
functional need of the system.
b. Load switch for connect/ disconnect purpose shall be
mounted inside the meter with suitable arrangement.
c. Load Switches shall be provided for all phases and neutral
d. The rating of switches used shall be in line with meter
rating.
e. Utilization category of the load switch shall be UC2 as per
IS 15884.
f. All the switches shall operate simultaneously.
g. Bidder shall provide details of load switch (make, type).
Meter shall have an optical port with a metal ring to hold magnet
6.13 Optical port of probe. Optical port shall comply with hardware specifications
provided in IEC-62056-21.
a. Meter shall have mechanism to log communication module
removal as an event in its memory with date and time
stamp.
b. Communication module shall be held in a casing, which
Communication
6.14 can be directly plugged in the meter. Sealing screw shall
Module
be provided.
c. Module shall be hot swappable on field.
d. Communication module shall be configurable for IPV6 with
backward compatibility with IPV4
Meter shall have super capacitor to provide power supply for
communication module in the absence of power failure for last
6.15 Super capacitor gasp signal. The Super capacitor rating should be suitable for
supply power to communication module without the use of battery
BSES

backup.
i. Sealing should be in accordance with IS and CEA metering
regulations with latest amendments.
j. Sealing arrangement shall be such that sealed parts shall not
be opened without breaking the seal or sealed part itself. There
should be clear evidence of the breaking in case sealed parts
shall be opened without breaking the seal.
k. Approval shall be taken from purchaser for location of seals
and number of seals.
Meter Sealing l. Record of all seals shall be forwarded to purchaser with each
6.16
Arrangement lot.
[Link] Body : 1 plastic seal and Hologram seal as per BSES
specs & 1 seal of meter manufacturer
n. Meter Terminal cover : 2 Plastic seal as per BSES specs
o. Meter Box : 2 plastic seal as per BSES Specifications
(All above seals provided by AMISP as per the serial no
provided by BSES )
p. Record of all seals shall be forwarded to purchaser with each
lot.
6.16.3 Seal record Record of all seals shall be forwarded to purchaser with each lot.
a. Meter should have clearly visible, indelible and distinctly
marked name plate in accordance with IS 16444 (Part 1) &
Name Plate and
6.17 clause no. 9.0 of this specification.
marking
b. All markings and details shall be printed by laser only.
c. Paper stickers are not allowed for name plate.
6.18 Resistance against As per IS 16444 (Part 1)

Page 265 of 473

 heat and fire
a. 10.5 years from the date of dispatch or 10 year from date of
commissioning, whichever is earlier
b. Manufacturer shall undertake a guarantee to replace meter up
6.19 Guarantee to a period of 10 Year from the date of supply. The meters
which are found defective/inoperative within the guarantee
period, these defective/inoperative meters shall be replaced
within one month of receipt of report for such
defective/inoperative meters.

7. Functional Requirement
7.1 Meter category Smart meter shall comply D2 category of IS 15959 (Part 2).
It should be possible to configure meters in following modes of
metering:
a. Forwarded Only: In this mode any export active energy shall
be treated as import energy and shall be recorded in forward
only register. Apparent energy calculation in this mode shall
be as per clause no. 7.4.
7.2 Mode of metering b. Bidirectional: Both Import and export energy recording shall
be applicable in this mode of metering and relevant registers
shall be updated.
Any change in metering mode shall be logged in events with date
and time stamp.
Default mode of metering shall be forwarded only untill specified
in tender requirement otherwise.
It should be possible to configure meter in following modes of
payment: BSES

a. Post payment mode

b. Prepayment Mode
7.3 Payment Mode Any change in payment mode shall be logged in events with date
and time stamp.
Prepayment facility shall be achieved by server / HES.
Default mode of metering shall be post payment until specified in
tender requirement otherwise.
c. Lag only: kVAh is computed based on kVArh and KWH
value. If PF=1, or leading, then kVAh = kWh. At no
7.4 kVAh Calculation instance kVAh< kWh.
d. If required provision should be there to modify apparent
energy calculation lag + lead (configurable remotely)
Block window with default demand integration period of 1800 s
configurable to 900 s as per requirement. Meter should be
7.5 MD calculation
configurable for block window at the time of manufacturing.
Extended register shall be used for MD recording.
a. Meter shall be capable of doing TOD metering in minimum 4
tariff rate registers programmable for minimum 8 time zones
and 3 seasonal profiles.
b. Meter shall be capable of doing TOD metering for kWh,
kVARh, kVAh. Reactive parameter should be recorded
7.6 TOD Metering
separately for Lag and Lead.
c. TOD programmable on site through mobile App or remotely.
d. At Display TOD values shall be shown as per cumulative
values of TOD Zones of respective registers.
e. TOD metering shall be implemented by the activity colander

Page 266 of 473

 method of IS 15959 Part 1 clause 9/ DLMS UA-1000-1
f. Special Day table shall be defined as per IEC/ DLMS UA-
1000-1
g. Default TOD programming shall be as per latest DERC
guidelines. Prior approval shall also be taken from BSES for
the same.
h. Tariff rate registers shall be as follow
R1: Rate register for Peak
R2: Rate register for Normal
R3: Rate Register for Off Peak

Note : Meter should have provision for Special day

programming and 4 season profile if required through FOTA
All the parameters mentioned in IS 15959 along with following
additional parameters should supported by meter.
Instantaneous
7.7 a. Neutral Current
Parameters
b. Voltage angles for displaying phasors.
c. TOD values.
Association
7.7.1 As per IS 15959 (Part 2).
Rights
a. Billing parameters shall generate at the end of each billing
cycle and stored in memory as per provisions provided in IS
15959 (Part 2).
b. 6 no’s billing cycle parameters shall be remain in meter
memory along with current cycle parameters and shall be
7.8 Billing data
available for reading as well as profile and or ‘by entry’ for
selective access.
BSES

c. All the parameters mentioned in IS 15959 (Part 2) along with

following additional parameters shall be supported by meter:
i. TOD values.
Association
7.8.1 As per IS 15959 (Part 2).
Rights
Support for selective access shall be provided for billing
7.8.2 Selective access
parameters as per IS 15959 (part 1).
Billing period
7.8.3 00:00 Hrs of Ist of every month
reset/ MD reset
Billing period
7.8.4 As per IS 15959 (Part 1)
reset mechanism
Billing period Cumulative billing period counter since installation and available
7.8.5
counter billing periods should be provided as per IS 15959 (Part 1).
a. Load survey parameters shall be measured and recorded at
the end of each profile capture period for last 35 Power ON
days.
7.9 Load survey Data b. All the parameters mentioned in IS 15959 (Part 2) along with
following additional parameters shall be supported by meter:
i. Average Neutral Current
ii. Average Signal Strength
Association
7.9.1 As per IS 15959 (Part 2)
Rights
Profile capture
7.9.2 Default 1800 s programmable to 900 s.
period
Support for selective access shall provided for billing parameters
7.9.3 Selective Access
as per IS 15959 (part 1).

Page 267 of 473

 a. Daily load profile parameters shall be measured and recorded
at each midnight i.e. 00:00 hrs for last 35 Power On days.
7.10 Daily load profile
b. All the parameters mentioned in IS 15959 (Part 2) shall be
supported by meter as Daily load profile parameters.
7.10.1 Association rights As per IS 15959 (Part 2).
General Purpose Following parameters shall be provided in Non-Volatile memory
7.11
Parameters (NVM) of the meter as per IS 15959 (Part 2).
Name Plate As per IS 15959 (Part 2) with following additional parameters.
7.11.1
Detail a. Month of manufacturing.
7.11.2 Association rights As per IS 15959 (Part 2).
i. These parameters can be programmed remotely by HES and
locally by mobile App via proper access writes. Every
transaction shall be logged in non volatile memory of the
Programmable meter with date and time stamp.
7.11.2
parameters ii. Programming of any of the parameters shall increment the
‘Cumulative programmable count’ value.
iii. All the parameters mentioned in IS 15959 (Part 2) shall be
supported by meters.
[Link] Association rights As per IS 15959 (part 2)

a. Smart meter is able to automatically notify data, event, and

messages to a destination client system in an unsolicited
manner (without a request from a client) as per clause no 6 of
IS 15959 (Part 2).
b. Randomization: Data from different endpoints shall be pushed
7.11.3 Push Services intelligently on the network in order to avoid excessive traffic
on the network for example in case all the endpoints will push
BSES

load survey data simultaneously, then it may result in network

choking or inefficient performance. Therefore, with the help of
intelligent techniques such field scenarios shall be handled
effectively.

Meter shall be able to push following instantaneous parameters

to HES at predefined intervals.
i Device ID
ii Push setup ID
iii Real Time clock- Date and time
iv R phase Voltage
V Y Phase Voltage
Vi B Phase Voltage
Vii R Phase Current
Periodic push Viii Y Phase Current
[Link] (Smart meter to ix B Phase Current
HES) vi Neutral Current
vii Three Phase Power Factor
Frequency
viii Apparent power KVA
ix Signed Active Power KW (+ Forward, - reverse)
Signed Reactive Power KVAR (+ for lag and –
for Lead)
x Cumulative Energy, KWH (Forwarded/ Import)
xi Cumulative energy KVAH (Forwarded/ Import)
xii Cumulative Energy KVAH (While Active Export)

Page 268 of 473

 xiii Cumulative Energy KVAH (While Active Export)
Other attributes as per IS 15959 (Part 2) i.e. Send Destination,
Communication window, Randomization time interval, number of
retries and repeat delay shall be decided in the event of
manufacturing.
Meter is able to report HES, the status change of any of the
identified events mapped in to event status word (ESW) of size
128 bits by pushing following objects to HES.
i Device ID
ii Push Setup ID
iii Real time clock- Date and Time
Event Push iv Event Status Word 1 (ESW 1).
[Link] (Smart meter to Each of the bits in ESW shall reflect the current state of the event
HES) and are mapped against each of the identified events.
An event status word filter (ESWF) of 128 bit shall also be
provided to configure events for event push. Events which are
supported in meter shall only be configured for event push. Bit
value 1 in ESWF shall indicate that the event is supported and
value 0 indicates that event is not supported for event push.
Position of the event bit in ESWF shall be same as in ESW.
Following events shall be pushed through event push
Bit no. Event ID Event Description
5 7/8 Over Voltage
4 9/10 Low Voltage
11 67/68 Over Current
51 69/70 Earth Loading
Influence of permanent magnet or
81 BSES

201/202
Ac/ DC electromagnet
82 203/204 Neutral disturbance- HF, DC or AC
83 251 Meter cover opening
Event status Bit Meter load Disconnected/ meter
[Link] 84 301/302
mapping load connected
85 Occurrence Last Gasp
86 Restoration First Breath
Manual reset Increment in billing
87
counter
The unused bits in ESW shall be left for future use.
Bits associated with events which are not applicable shall always
be set to ‘0’.In case of event ids the odd number is for occurrence
and even number is for restoration.
Other events to be mapped in ESW shall be intimated in the
event of approval.
a. Smart meter shall support remote firmware upgrade feature
for meter firmware without loss of any data and metrology.
b. Firmware upgrade shall use the Image transfer classes and
mechanisms specified in IEC62056-6-2 and IEC62056-5-3.
Firmware
c. Broad cast facility shall be supported in HES for
7.12 simultaneously upgrading the firmware of a group of meters
upgrade
installed in field.
d. Firmware upgrade feature shall be provided with proper
security. The design shall take into account field scenarios
such as power failure during F/W upgrade.
e. Once the firmware is upgraded, meter shall send an

Page 269 of 473

 acknowledgment to HES. It shall also log it as an event in its
memory.
f. Meter shall support capability to self-register the meter with
new firmware.
g. The execution time of the change of the firmware within the
meter should be below 1 minute
The Smart meter shall support disconnection (all the switches
shall operate simultaneous) on the following conditions as per
clause 11 of IS 16444 (Part 1):
a. Over current (105 % of Imax in any element for predefined
persistence time.)
Disconnection
7.14 b. Load control limit (Programmable )
mechanism
c. Pre-programmed tamper conditions (Factory programmed)
d. Disconnection signal from Head end system.
e. Pre-paid function for prepayment mode.
Meter shall use the disconnection control object as defined in
clause 10 of IS 15959 (Part 2).
Local
7.15 reconnection a. As per IS 16444 (Part 1)
mechanism
a. Reconnection shall be done from HES except for over
current and load control limit. In case of failure of
communication / HES, reconnection shall be possible
Reconnection
7.16 through Hand Held Device (Mobile App) locally via proper
mechanism
security.
b. Reconnection in case of prepayment meter shall be as per
prepayment profile.
BSES

a. Indication of status of relay i.e. connected/ disconnected

Status of load should be available on display as well as through
7.16
switch communication to HES.
b. Connection and disconnection should be logged as events.
a. Status indication of switch i.e. connected/ disconnected
should be available on display as well as through
communication to HES.
First breath and
b. In Last Gasp endpoint shall send the power outage
7.17 notification with Time Stamp. In case of power failure meter
last gasp
communication module shall not draw power from the backup
battery.
c. For the purpose of sending the Last Gasp, meter shall have
proper power backup (like a super capacitor).
7.18 Security As per IS 15959 (Part 2)
Encryption for
7.18.1 data As per IS 15959 (Part 2)
communication
Encryption/ As per IS 15959 (Part 2)
7.18.2 Authentication for
data transport
Key requirement As per IS 15959 (Part 2)
7.18.3
and handling
IP communication Meter shall support TCP-UDP/ IP communication profile for smart
7.19
profile support meter to HES. Please refer clause 8 of IS 15959.
Event and tamper Meter shall detect and log any exceptional/ fraud/ tamper
7.20
detection conditions in its memory as an event. In addition to this all

Page 270 of 473

 transactions and control shall also be recorded as an event in
meter memory. Each event type shall be identified by an event
ID.
Each event shall be available to download as per following
association rights.
Association a. Public Client: No access
7.20.1
Rights b. Meter Reader: Read only
c. Utility Settings: Read only
d. Push Services: Read Only for identified events as per ESWF
Meter shall be able to log events in following compartments
a. Voltage Related Events
b. Current Related Events
c. Power Related Events
d. Others Events
e. Non Roll Over Events
f. Transaction related events
g. Control Events
Occurrence and Restoration of Voltage Related, current related,
Compartments of power related and other events shall be logged in meter memory
7.20.2 as per IS 15959 (Part 2). Please refer Appendix 3A for
events
description of events, Event ID, Logics of events and threshold
values of events.
Threshold values shall be factory programmable.
Selective access shall be provided as per clause 11.3 of IS
15959 (Part 1).
For each of the events a certain list of parameters shall be
captured as per clause 'a'
BSES

For each occurrence event captured, the cumulative tamper

count shall be incremented.
Following parameters mentioned above are to be captured when
Parameter
7.20.3 event occurrence and restoration is logged as per IS 15959 (Part
Snapshot
2) along with neutral current
The meter shall log minimum 100 tamper events (ensuring at
7.20.4 Event Logging
least 20 events for each tamper).
Appropriate Indications/Icons for all tampers should appear on
7.20.5 Tamper Indication
the meter display either continuously or in auto display mode.
a. Reading and writing data into meter memory via optical and
remote communication port shall be through DLMS security
keys only.
b. Bidder shall ensure to safeguard high security keys used for
configuring parameters into meter.
c. Once the meter memory is locked during manufacturing
process, only parameters mentioned in IS 15959 shall be
configurable even in factory. It should not be possible to
7.21 Security
configure any other parameters.
d. Please note that there shall be no other mechanism/ method
to interface with meter through optical and remote
communication port except mentioned in IS 15959, even for
manufacturer.
e. It should not be possible to change data stored in meter
memory even after accessing meter memory physically. In
case of any change in memory data, a flag/alert shall be

Page 271 of 473

 generated. Flag/Alert shall be indicated over display and in
remote communication also.
As per CEA regulation billing energy shall be measured and
Harmonic
7.21 recorded with and without harmonic (fundamental) contents and
Energies
available in all data profiles.

8. Meter Display
8.1 LCD Type STN/ HTN Liquid crystal with backlit
8.2 a. Minimum 120 Degree.
b. The display visibility should be sufficient to read the Meter
Viewing angle mounted at height of 0.5 m as well as at the height of 2 m.
8.3 Size of LCD Minimum 10X5mm
8.4 LCD Digits Total 6 +1 digits. Rollover should be at 9,99,999 units only.
8.5 LCD language English
8.6 a. Auto Mode
b. Manual Mode
c. Sub active mode
 Auto Scroll
1. Meter Sr. No. 5 Sec
2. Display Check 5 Sec
3. Date and Time 5 Sec
4. Current balance in INR (for prepaid mode) 5 sec **
5. Current balance Date & Time 5 sec **
6. Balance at Last Recharge (In Rupees) 5 sec **
7. Last Recharge Amount in INR 5 sec **
8. Last Recharge Date and time 5 sec **
BSES

9. Cumulative kWh 10 sec

10. Cumulative Export kWh* 10 sec
11. Net kWh* 10 Sec
12. Cumulative kVAh 10 Sec
13. Cumulative Export kVAh* 10 sec
14. Net kVAh *
Display modes 15. Current month MD kW 5 Sec
16. Current month MD kVA 5 Sec
17. Current month average Power Factor 5 Sec
18. Instantaneous phase wise voltage 5 Sec
19. Instantaneous phase wise current 5 Sec
20. Instantaneous phase wise PF 5 Sec
21. Instantaneous average Power Factor 5 Sec
22. Instantaneous Load kW and kVA 5 Sec

 Scroll with Push-button

All Parameters mentioned under Auto-Scroll mode should be
displayed. Additionally, the following Parameters shall also be
displayed:
1. Internal diagnostics (display check)
2. Cumulative Energy in kVArh Lag/ Lead with legend
3. Cumulative Active Energy kWh ToD wise with legends.
4. Cumulative Apparent Energy kVAh ToD wise with legends.
5. Last month cumulative kWh with legends
6. Last month cumulative kVAh with legends
7. Last month MD in kW with legends
Page 272 of 473
 8. Last month MD in kVA with legends
9. Last month Average Power Factor
10. High Resolution value (kWh, KVAh, kvarh-Lag, kvarh-Lead)
11. High resolution Export (kWh , KVAh)*
12. Top cover open date & time
13. Mode (Prepaid/Post-paid/Net)
14. Signal Strength - 5 sec
15. Error code - 5 sec

*When meter is configured in net metering mode then only these

parameters should appear otherwise these display parameters
should be disable and shall not appear on display

**When meter is configured in prepayment mode then only these

parameters should appear otherwise these display parameters
should be disable and shall not appear on display

Note:- LCD size shall be minimum 10 mm X 5 mm with total 6+1

digits for energy.

The meter’s display should return to default display mode

(continues auto scroll) if push button is not operated for more than
30 second.
8.7 Display Appropriate indications/flags for all tampers and self diagnostic
indications features should be provided.

9. Data and communication protocol/ HES/Integrations/ Software

BSES

9.1 a. Meter should comply Indian companion of data exchange and

tariff control specification IS 15959 (Part 2).
b. In case of additional requirement from IS 15959 (part 2), they
shall be as per DLMS standards/ IEC DLMS protocols suite
(62056).
Data Exchange
protocol c. Bidder shall explain in detail the additional parameters/ services/
methods used in meters from IS 15959 (part 2) and its reference
to DLMS books/ IEC.
d. Prior to manufacturing of meters bidder shall provide a detailed
specification explaining all parameters/ services/ methods used
in meter in addition to IS 15959 (Part 2).
9.3 Base computer
Bidder shall provide BCS software for lab testing
software (BCS)
9.4 a. The manufacturer has to provide Mobile App for downloading all
the data stored in meter memory through optical port.
b. Mobile App should have option for selection of parameters to be
downloaded from meter
c. Meter data consisting of all parameters and complete load
Hand Held Unit survey for all parameters shall be read by HHU (Mobile App) and
Software(Mobile data transferred to HES in minimum possible time (not more
App) than 5 minutes).
d. Mobile App should have option to initiate command for relay
connect or disconnect through optical port, this functionality
should have system control and action to be initiated only for
those meters which are scheduled / triggered from back end
application (HES/MDMS/Prepaid).

Page 273 of 473

 e. Mobile App should have option to initiate configuration and
firmware upgrade actions locally for non-communicated meters
as per the schedule initiated from back end applications
(HES/MDMS).
f. Mobile App should ensure the meter security keys are stored in
encrypted form and not accessible to users.
9.5 Manufacture shall impart training to BSES personnel for usage of
Training
software

10. Name Plate

Meter Serial number shall be of 8 digits. Serial number shall be printed in black colour.
10.1
Embossing is not acceptable.
10.2 Size of the digit shall be minimum 5X3 mm Laser printing shall be preferred.
10.3 Bar code shall be printed below serial number
10.4 BIS registration mark (ISI mark)
10.5 ‘BSES’ insignia shall be printed above LCD display. With Property of BSES
10.6 BSES PO No. & date
10.7 Manufacturers name and country of origin
10.8 Model type / number of meter
10.9 Month and Year of manufacturing
10.10 Reference voltage / current rating
The number of phases and the number of wires for which the meter is suitable.
10.11
Graphical symbol as per IS 12032 can be used.
10.12 Meter constant in Imp/ kWh and Imp/ kVAh
10.13 Class index of meter
10.14 Reference frequency
10.15 Warranty period BSES

10.16 Communication technology with carrier frequency

10.17 Symbol of load switch

11. Component Specification

a. The components used by manufacturer shall have “Minimum
Life” more than the 10 years.
b. Bidder should specify component specification along with make
Component and model used in offered meters in submitted technical bid
11.1 Specification documents.
Manufacturer should have complete tracking of material used in
meter. BSES reserve the right to carry out audit of inventory/
manufacturing process at manufacturer’s works and sub vendor’s
work.

12. Quality Assurance, Inspection and Testing

Vendor's Quality
12.1 To be submitted for Purchaser's approval.
Plan (QP)
Sampling Method for quality checks shall be as per relevant IS/
12.2 Sampling Method IEC/ CBIP guidelines and Purchaser's prior approval shall be
taken for the same.
Inspection Hold-
12.3 To be mutually identified, agreed and approved in Quality Plan.
Points
a. The meter shall be of type tested quality including all tests
specified in this specification which are beyond IS / IEC or
12.4 Type Tests
CBIP.
b. Type test conducted from CPRI/ ERDA/ or any other lab

Page 274 of 473

 specified by BIS/ CEA for smart meter testing will be treated
as valid.
c. Type test certificate should be submitted along with offer for
scrutiny.
d. Any other component supplied in addition to meter shall
also be type tested as per IS /IEC if applicable.
e. Complete type test as per IS 16444 (Part 1) shall be carried
out on sample selected from BSES lot from NABL and BIS
approved labs without any price implication.
f. Type test report shall not be older than 5 years from the
date of tender submission.
12.5 Routine tests All test marked “R” as per table 20 of IS 13779.
a. All tests marked “A” as per table 20 of IS 13779.
b. Smart meter functional tests as per IS 16444 Table 1
c. Test of load switch as per clause 10.4 of IS 16444 (Part 1)
d. Test for data exchange protocol as per clause 10.5 of IS
16444.
e. Test for Smart meter communicability as per clause no. 10.6
of IS 16444 (Part 1).
f. All the routine and acceptance tests shall be carried out as
per relevant standards.
g. Following tests in addition to IS shall be conducted during
lot inspection.
12.6 Acceptance Tests
VII) Dimensional and drawing verification.
VIII) Display parameters/ sequence.
IX) Data Downloading from handheld and PC and HES
X) Tamper/ fraud detection/logging features as per
BSES

approved documents. Tamper conditions will be

simulated at varying load up to Imax. Accuracy will
also be checked during tamper simulation.
XI) Burn in chamber test.
XII) Component verifications.
h. Purchaser reserves the right to formulate any other test
method to verify guaranteed parameters of Meter.
ESD and magnetic interference test will be conducted at Samir
ESD and Magnetic
12.7 lab, Chennai/ CPRI/ ERDA/ or any other lab specified by BIS/
Interference test
CEA for smart meter testing will be treated as valid.
a. Purchaser reserves the right to inspect /witness all tests on
the meters at Seller’s works at any time, prior to dispatch, to
verify compliance with the specification/ standards.
b. Manufacturer should have all the facilities/ equipment has to
conduct all the acceptance tests as per relevant standards/
12.8 Inspection
this specification and tampers logics as per approved GTP.
All the equipment is including tamper logs kits/ jigs should
be calibrated.
c. In-process and / or final inspection call intimation shall be
given in advance to purchaser.

13. Packing, Marking, Shipping, Handling and Storage

Page 275 of 473

 a. Each meter must be packed, together with its terminal cover, in a
separate environmental friendly cardboard box, which can be opened
and re-closed without needing adhesives.
b. The box shall prevent, as much as possible, penetration of dust
13.1 Packing during long storage periods.
c. The packaging will protect the meters against shock and vibration,
preventing damage due to the road conditions during transport and
distribution in the field. The electrical and mechanical properties shall
not be affected by these disturbances.
Packing for
Robust wooden non returnable packing case with all the above protection
13.2 accessories
& identification Label.
and spares
On each group box and pallet, following details are required both on front
(wide side) and top:
a. BSES logo.
b. Meter serial number range along with bar code.
c. Unique number of box/ pallet.
d. Purchaser’s name
e. PO number (along with SAP item code, if any) & date with bar code
f. Equipment Tag no. (if any)
13.3 Marking g. Destination
h. Manufacturer / Supplier’s name
i. Address of Manufacturer / Supplier / it’s agent
j. Type , rating and other description of equipment
k. Country of origin
l. Month & year of Manufacturing
m. Case measurements
BSES

n. Gross and net weights in kilograms

o. All necessary slinging and stacking instructions
Test
13.4 Routine test report to be provided with each meter
reports
The seller shall be responsible for all transit damage due to improper
13.5 Shipping
packing.
Manufacturer instruction shall be followed. Detail handling & storage
Handling
13.6 instruction sheet /manual to be furnished before commencement of
and Storage
supply.

14. Deviations

a. Deviations from this specification can· be acceptable, only where the

Seller has listed in his quotation the requirements he cannot, or does
not, wish to comply with and which deviations the Buyer has agreed
14.1 Deviations to in writing, before any order is placed.
b. In the absence of any list of deviations from the Seller, it will be
assumed by the Buyer that the Seller complies with the Specification
fully.

15. Drawing Submission

Drawing submission shall be as per the matrix given below. All documents/ drawing shall be
provided on A4 sheet in soft copy with separators for each section. Language of the documents
shall be English only. Deficient/ improper document/ drawing submission may liable for rejection
SL Detail of Document Bid Approval Pre Dispatch
1 Guaranteed Technical particulars (GTP) Required Required

Page 276 of 473

 2 Deviation Sheet, if any Required Required
3 Tamper Sheet Required Required
4 Display Parameters Required Required
GA / cross sectional drawing of Meter
5 Required Required
showing all the views / sections
As per bid
6 Samples of each type and rating offered. 4 no's
Requirement
Environment for testing sample meters
7 with head end system to be install at Required Required
BSES premises.
Any software and accessories required
8 Required Required
for installation/ operation of meter
Manufacturer's quality assurance plan
9 Required Required
and certification for quality standards
Type Test reports of offered model/ type/
10 Required
rating
11 BIS certificate Required
Complete product catalogue and user
12 Required
manual.
13 Customer Reference List Required
Recommended list of spare and
14 Required
accessories
Specification documents containing all
parameters, Services, Methods in
15 Required
addition to companion specification of IS
15959 (part 2).
16 Program for production and testing (A)
BSES
Required Required
Detailed installation and commissioning
18 Required Required
instructions
19 As Built Drawing Required Required
Operation and maintenance Instruction as
20 Required Required
well as trouble shooting charts/ manuals
Inspection and test reports, carried out in
21 Required
manufacturer’s works
22 Routine Test certificates Required
23 Test certificates of all bought out items Required
24 Meter Seal data Required
Other documents:
a. Completely filled-in Technical
Parameters
b. General arrangement drawing of the
meter
c. Rating plate
25 d. Terminal Block dimensional drawing Required Required
e. Mounting arrangement drawings
f. Meter box drawing and dimensions
g. Display parameter
h. PIN configuration of Optical to RJ11
connector
i. Manual and SOP/DWI for operation

16. Delivery
16.1 Delivery Dispatch of Material: Vendor shall dispatch the material, only after

Page 277 of 473

 the Routine Tests/Final Acceptance Tests (FAT) of the material
witnessed/waived by the Purchaser, and after receiving written
Material Dispatch Clearance (MDC) from the Purchaser.

APPENDIX 3A- GUARANTEED TECHNICAL PARTICULARS

Bidder shall furnish the GTP format with all details against each clause of this specification.
Bidder shall not change the format of GTP or clause description.
Bidder to submit duly filled GTP in hard copy format with company seal.

Clause No. Clause Description Manufacturer’s Reply

1
2
3
4
5

Bidder / Vendor seal / signature ---------------------------

Name of the bidder

Address of the bidder
Name of contact person
Telephone number and email id

APPENDIX 3B- RECOMMENDED ACCESSORIES / SPARES

SL Description of spare part Unit Quantity

BSES

1 No
2 No
3

Page 278 of 473

APPENDIX 3C- TAMPER AND FRAUD DETECTION/ EVENTS

1. Voltage Related Events:

Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
R Phase Voltage Missing
1/2 Absence of potential on any phase should be
(Occurrence/ Restoration) Occurrence: If Vpn<10% Vref and
logged. Restoration of normal supply shall
Y Phase Voltage Missing Ip>10% Ib Occurrence: 5 Min
3/4 also be recorded. The threshold value of
(Occurrence/ Restoration) Restoration: If Vpn>=10% Vref and Restoration: 5 Min
voltage should be programmable at factory
B Phase Voltage Missing Ip>10% Ib
5/6 end
(Occurrence/ Restoration)
Over Voltage (occurrence/ Meter should log high voltage event if voltage Occurrence: If Vpn>10% Vref Occurrence: 5 Min
7/8
restoration) in any phase is above a threshold value. Restoration: If Vpn<=10% Vref Restoration: 5 Min
Meter should log low voltage event if voltage
Low Voltage (occurrence/ Occurrence: If Vpn<75% Vref Occurrence: 5 Min
9/10 in any phase is below a threshold value.
Restoration) Restoration: If Vpn<=75% Vref Restoration: 5 Min
Threshold value if factory programmable.
Meter should log voltage imbalance event
Occurrence: If Vmax-Vmin>30%
when the difference between minimum and
BSES

Voltage Unbalance Vref Occurrence: 5 Min

maximum phase voltage is more than a
11/12 (Occurrence/ Restoration) Occurrence: If Vmax-Vmin<=30% Restoration: 5 Min
threshold value. Threshold value if factory
Vref
programmable.

2. Current Related Events:

Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
Current Reverse :R Phase Current Meter should log the event of current
51/52 Reverse (occurrence/ Restoration) reversal of polarity.
Y Phase Current Reverse Meter should register energy consumed
Occurrence: If Ip = -ve direction
53/54 (occurrence/ Restoration) correctly with any one, two or all three Occurrence: 5 Min
Restoration: If Ip=+ve direction
current coils reversed. This event shall Restoration: 5 Min
Current threshold 5%Ib
B Phase Current Reverse not be valid in bidirectional mode of
55/56 (occurrence/ Restoration) metering.

R Phase Current Open (Occurrence/ Meter should log the event of current Vector Sum(IR+IY+IB+IN)>20% Ib Occurrence: 5 Min
57/58 Restoration) coil open. Threshold value of current and I<10% Ib Restoration: 5 Min

Page 279 of 473

Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
Y Phase Current Open (Occurrence/ should be programmable at factory end. Vector Sum(IR+IY+IB+IN)>20% Ib
59/60 Restoration)
B Phase Current Open (Occurrence/
61/62 Restoration)
Meter should log the event of current
Current Unbalance (Occurrence/ Current (Maximum – Minimum) Occurrence: 5 Min
unbalance. Threshold value of current
63/64 Restoration) > 30% of Average current Restoration: 5 Min
should be programmable at factory end.
Meter should log the event of current
Vector Sum(IR+IY+IB+IN)>20% Ib
Current Bypass (Occurrence/ coil shorting/bypass. Threshold value of
and I (any Phase) >5% Ib
65/66 Restoration current should be programmable at
Vector Sum(IR+IY+IB+IN)>10% Ib
factory end.
If the current in any phase exceeds the
Over current (occurrence/ Occurrence: If Ip>Imax Occurrence: 5 Min
specified thershold current, meter
67/68 restoration) Restoration: If Ip<=Imax Restoration: 5 Min
should log overcurrent event.

BSES

3. Power Related Events:

Event Description of
Logic Of Event Logic Expression/ Threshold values Persistence Time
ID event
Meter shall detect power OFF if all phase
Power OFF voltages are absent. This event shall be
Occurrence: 5 Min
(occurrence/ recorded at the time of each power OFF.
101/102 Restoration: 5 Min
restoration) At the same time power ON event shall be
recorded.

4. Other Events:
Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
a. Meter should either be immune or should log
Abnormal External Occurrence: 15
the events of attempt of tampering by external
Magnetic Influence Sec
magneticfield as per relevant IS13779/ CBIP As per IS 13779/ CBIP 325
201/202 (Occurrence/ Restoration: 15
325 with latest amendments.
Restoration) Sec
b. If the working of meter gets affected under the
Page 280 of 473
 Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
influence of external magnetic field, meter
should record energy at Imax. Meter should not
compute MD during this period. The meter shall
record energy as per actual load once the
magnetic field is removed.
c. Meter shall comply magnet test as per CBIP325
and shall immune to 0.5T permanent magnet
test. In case meter is not immune to 0.5T
permanent magnet test than meter shall log
tamper event and record energy at
Vref*Imax*UPF load.
Neutral Disturbance-
Meter should log the event when AC/DC/ Pulsating Occurrence: 5 Min
HF, DC and Alternating As per manufacturing standard.
203/204 voltage is injected in neutral circuit. Restoration: 5 Min
(occurrence/ restoration)
Meter shall able to detect and log the low PF event
if power factor of the load found between 0.2 to 0.5
BSES

Occurrence: 0.2<|PF|<=0.5 and

for a load above than a % threshold value for a Occurrence: 5 Min
Low Power Factor Iphase >10%Ib
205/206 threshold time value. Event shall restore if PF Restoration: 5 Min
Restoration: (|PF|>0.5) and
factor of load remain out of range 0.2 to 0.5 for a
Iphase>10%Ib
load above than % threshold value
Plug in Communication
module removal Meter should log the removal of communication
(Occurrence/ card. Meter should also log insertion of
209/210 Restoration) communication card. By NC switch/ sensor
Configuration change to
post-paid mode/ pre- Meter should log the change in payment mode
211/212 paid mode configuration.
Configuration change to
“Forwarded” only" mode/
“Import and Export” Meter should log the change in metering mode
213/214 mode configuration.
Overload (Occurrence/ Meter should able to log the status of overload in
215/216 Restoration) KW

Page 281 of 473

 Event Logic Expression/ Threshold
Description of event Logic Of Event Persistence Time
ID values
Meter shall remain immune/log event to
HV Spark (Occurrence/
electrostatic discharge (upto and including 35KV) On detection of HV
restoration) and Jammer
along with NIC spark
test.
Occurrence: If IN > 50% of
Meter should log event of high neutral current if
average phase current Occurrence: 5 Min
High neutral Current measured neutral current should be more than
Restoration: If IN < 50% of Restoration: 5 Min
predefined threshold value.
average phase current

5. Non Roll over events:

Event ID Event Description
251 Occurrence of cover open
Relay weld : Relay contacts permanently weld
BSES

6. Transaction Related Events:

Event ID Detail of Transaction
151 Real Time Clock- Date and Time
152 Demand Integration Period
153 Profile Capture Period
154 Single Action schedule for billing date
155 Activity calander for time zones
157 New firmware activated
158 Load Limit (Kw) Set
159 Enable Load Limit Function
160 Disable load limit function
161 LLS secret (MR) change
162 HLS key (US) change
163 HLS key (FW) change

Page 282 of 473

 Event ID Detail of Transaction
164 Global key change
165 ESWF change
166 MD reset

7. Control Events
Event ID Event Description
301 Load Switch Status- Disconnected
302 Load Switch Status- Connected

BSES

Page 283 of 473

APPENDIX 3D: Meter Enclosure
SL Clause Clause Description
Flush type with Completely transparent top cover and base with
1.0 Meter Box Type Incoming and Outgoing cable entry and data downloading
arrangement.
2.0 Design Meter box shall comply following requirement.
The meter box shall be designed in such a way that no access to the
General meter body, terminals and hardwired port of the meter shall be
2.1
Requirement possible after installation and sealing of the box without breaking the
box itself.
a. Meter box shall be theft proof i.e. meter box cannot be opened
without breaking the seals or meter itself.
2.2 Theft Protection
b. On breaking of the box, clear evidence of the physical tempering
shall be visual.
a. The meter box shall be designed in 02 parts i.e. base and top
cover.
b. Meter shall be mounted inside the base on fixed moulded pillars
by unidirectional screw.
2.3 Parts of the box
c. Meter top cover should be hinge type.
d. Cable glands and earthing bolt shall be provided at the base as
per construction requirement.
e. Proper stiffeners shall be provided in the body of the base and top
cover to provide mechanical strength against transportation and
installation vibrations.
Ingress The meter box shall be completely dust and vermin proof. Ingress
2.4
protection protection rating of the box shall be minimum IP55.
a. A 'U' shaped groove shall be provided in the collar of the base
BSES

body, in which UV stabilized rubber 'O' shall be installed. The

design of lining shall be such that it provides proper sealing
between the cover & base of box to avoid penetration of dust and
Collar of base
2.5 ingress of water.
and cover
b. All around projection provided inside the cover periphery which
keeps the ‘O’ ring pressed.
c. An outside collar shall also be provided, which shall cover outer
surface of the collar.
a. Rubber ‘O’ Ring should be fixed with suitable adhesive so that the
same does not get removed.
2.6 Fixing of 'O' ring b. Rubber 'O' ring shall be fixed in a single piece without any gap
between open ends. Open end of the 'O' ring shall be provided at
the bottom side only.
3.0 Material The material shall be as follow:
a. The material of meter box shall be flame retardant with
inflammability level V0 having good dielectric and mechanical
strength.
b. The top Cover and Base of the box shall be made out of
3.1 Box material transparent polycarbonate with minimum 90% visibility so as to
ease installation and monitoring of box against any tampering.
The material shall be ‘UV’ stabilized to ensure that the moulded
meter box should not change in colour, shape, size or should not
get brittle after exposure to UV rays.
All the metal hardware including hinges, U latches, mounting screws,
3.2 Hardware
downloading port ring etc shall be of rust proof stainless steel.
3.3 Cable glands Polyamide Nylon-66 with flammability class FV0

Page 284 of 473

 SL Clause Clause Description
a. Meter box shall be constructed by moulding of polycarbonate
4.0 Construction material as specified in clause no. 3.1
b. Thickness of meter box shall be minimum 2.0 mm.
4.1 Moulding The box shall be made through Injection Moulding or better method.
Meter shall be factory fitted inside base body using unidirectional
screws, on fixed mounting pillars, moulded in to the base of sufficient
4.2 Base
strength, so that removing of meter shall not possible without breaking
the meter box or meter itself.
4.3 Top cover Hinge type
a. Minimum 02 no's concealed / internal hinges, not visible or
accessible from outside the box without breaking the box itself.
4.3.1 Hinge type
b. Minimum 02 no's U latches shall be provided to closed the box
with sealing arrangement at each U latch.
c. After closing the U latches no play/ gap shall exist between base
and top cover.
5.0 Padlocking The box shall also have padlocking facility.
a. 02 no's as incoming and outgoing at the 45 Deg Chamfer bottom
corners suitable for 4CX50 Sqmm armoured aluminum cable.
b. Cable entry must be at the bottom diagonal ends of the meter box.
Appropriate clearance shall be provided between the cable entry
6.0 Cable entry and position of meter terminals for proper cable bending and
connection.
c. Minimum 60 mm vertical space shall be provided from the
terminals of meter to centre of cable gland to provide sufficient
bending radius and working space.
a. Two nos. of Elbow shaped glands made out of Polyamide Nylon-
BSES

66 suitable for 4CX25 / 2CX50 sqmm aluminium armoured cable

shall be provided on both cable entries in the box.
6.1 Cable Gland b. Glands shall be designed in such a manner that the same cannot
be unscrewed / removed from the box from outside. Manufacturer
may either supply two nos. of check nuts or any other alternate
design to meet this requirement.
a. Earthing bolt of M6 with nut and washer shall be provided on left
side of the body of meter box.
7.0 Earthing bolt
b. The arrangement shall be such that one earth point shall be
available for customer and external earthing provided by BSES
can be terminated.
c. Necessary symbol shall be provided for earth terminal.
8.0 Mounting Mounting arrangement shall be as follow
a. Fixed type, moulded in to the base body as per the requirement of
Meter mounting meter mounting holes.
8.1
pillars b. Stiffeners shall be provided at the base of the mater mounting
pillars.
a. Four (4) nos. fixing holes of 6 to 6.5 mm diameter at the back
Meter box surface of box shall be provided to fix the same on flat wall.
8.2
mounting b. Mounting holes shall not be obstructing by Incoming or Outgoing
cables.
04 no's, 25 mm minimum mounting spacer moulded at the mounting
Box Mounting
8.3 holes of back surface of the meter box in order to provide space
spacers
between meter back surface and wall.
Box Mounting Long pan head self taping SS screws and washers shall be provided
8.4
accessories by the supplier with every box. 4 no’s plastic fixing plugs suitable for

Page 285 of 473

SL Clause Clause Description
self tapping screws shall also be provided.
a. Option 1:
a. Slot for optical head with non removable corrosion
ferromagnetic metal ring.
b. Data downloading shall not be affected by scratches on data
downloading port or with ageing of box.
c. Data downloading shall not be affected by visible light
conditions.
Data b. Option 2:
9.0 Downloading a. DB9 RS232 connector shall be provided at the top cover of
arrangement box to download meter as specified in clause no. 9.1
b. Meter shall be downloadable without opening of the box/
breaking of seals.
c. This arrangement shall not de-rate the IP rating of meter box.
d. A Top hinges and bottom sealable cover shall be provided on
the data downloading slot.
e. Data downloading shall not be affected by visible light
conditions.
Optical reader with 9 pin D-type female connector cable shall be
Optical to RS232 provided in each meter box. Push fit type protective cover with sealing
cable (If option 2 arrangement for data downloading port on the cover of the meter box
9.1
as per clause has to be provided. The optical meter reader with 9 pin D-type female
no. 9.0 connector cable of all the meter boxes (100%) shall be tested for
meter downloading before dispatch.
Following marking shall be provided on both top cover and base by
indiligible laser printing/ screen printing or embossed from inside of the
BSES

box.
a. BSES insignia shall be embossed on the base & cover of meter
box.
10.0 Marking b. Meter serial no. (Both on base and cover of meter box)
c. Purchaser's PO no. and date.
d. Purchaser's Name.
e. Name or trade mark of seller
f. Any other detail required at the time of approval.

Page 286 of 473

Appendix 4: Technical Specification for LT-CT Smart Meters

1.0 Scope of Supply

This specification covers the design, manufacture, assembly, inspection, testing and delivery of
Smart CT operated 3 phase 4 wire, Accuracy Class 0.5s, 3 x 240 V and -/5 A meter with plug in
communication module (Cellular) and accessories required for successful operation of the meter
in post paid mode or special application such as bidirectional net meters (configurable remotely).

A. Design, manufacture, testing at manufacturer works before dispatch, packing, delivery and
submission of all documentation.
B. Any accessories / hardware required for installation and operation for the meter.

2.0 Codes & standards

Materials, equipment and methods used in the manufacturing of above mentioned equipment
shall conform to the latest edition of following
S No. Standard Number Title
2.1 Indian Electricity Act IE Act 2003
2.2 CEA Metering
With latest amendments
Regulations
2.3 CBIP Manual (Pub no.-
Standardization of AC Static Electrical Energy Meters
325)
2.4 IS- 16444 (Part 2) AC Static Transformer Operated Watt-hour And Var-hour
Smart Meters, Class 0.2 S, 0.5 S And 1.0 S Part 2
Specification Transformer Operated Smart Meters
2.5 IS- 14697 ac Static Transformer Operated Watt-hour and Var-hour
Meters, Class 0.2 S and 0.5 S
2.6 IS-15959 (Part 1) Data Exchange for Electricity Meter - Reading Tariff and
Load Control - Companion Specification
BSES

2.7 IS-15959 (Part 2) Data Exchange for Electricity Meter - Reading Tariff and
Load Control (Part 2)- Companion Specification for smart
meter
2.8 IS-15959 (Part 3) Data Exchange For Electricity Meter Reading, Tariff And
Load Control-Companion Specification Part 3 Smart Meter
(Transformer Operated Kwh And KVARh Class 0.2 S, 0.5 S
And 1.0 S
2.9 IS- 11448 Application guide for AC Electricity meters
2.10 IEC- 62052-11 Electricity metering equipment (AC) - General requirements,
tests and test conditions - Part 11: Metering equipment
2.11 IEC- 62053-21 Electricity metering equipment (A.C) - Particular
requirements - Part 21: Static meters for active energy
(classes 1 and 2)
2.12 IEC- 62053-52 Electricity metering equipment (AC) - Particular requirements
- Part 52: Symbols
2.13 IEC 62053-61 Electricity metering equipment (A.C.) - Particular
requirements - Part 61: Power consumption and voltage
requirements
2.14 IEC 62058-11 Electricity metering equipment (AC) - Acceptance inspection
- Part 11: General acceptance inspection methods
2.15 IEC 62058-31 Electricity metering equipment (AC) - Acceptance inspection
- Part 31: Particular requirements for static meters for active
energy (classes 0,2 S, 0,5 S, 1 and 2)
2.16 IEC 60736 Testing Equipment for electrical Energy meter
2.17 IS/IEC/TR 62051:Part Electricity Metering — Data Exchange For Meter Reading,
1:2004 Tariff And Load control — Glossary Of Terms Part 1 Terms

Page 287 of 473

 Related To Data Exchange With metering Equipment Using
DLMS/ COSEM
2.18 IEC 62056-1-0:2014 Smart metering standardisation framework
2.19 IEC 62056-3-1:2013 Use of local area networks on twisted pair with carrier
signalling
2.20 IEC 62056-4-7:2014 DLMS/COSEM transport layer for IP networks
2.21 IEC 62056-5-3:2017 DLMS/COSEM application layer
2.22 IEC 62056-6-1:2017 Object Identification System (OBIS)
2.23 IEC 62056-6-2:2017 COSEM interface classes
2.24 IEC 62056-6-9:2016 Mapping between the Common Information Model message
profiles (IEC 61968-9) and DLMS/COSEM (IEC 62056) data
models and protocols
2.25 IEC 62056-7-3:2017 Wired and wireless M-Bus communication profiles for local
and neighbourhood networks
2.26 IEC 62056-7-5:2016 Local data transmission profiles for Local Networks (LN)
2.27 IEC 62056-7-6:2013 The 3-layer, connection-oriented HDLC based
communication profile
2.28 IEC TS 62056-8-20:2016 Mesh communication profile for neighbourhood networks
2.29 IEC TS 62056-9-1:2016 Communication profile using web-services to access a
DLMS/COSEM server via a COSEM Access Service (CAS)
2.30 IEC 62056-9-7:2013 Communication profile for TCP-UDP/IP networks
2.31 IEC 62056-21:2002 Direct local data exchange
2.32 DLMS- White Book Glossary of DLMS/COSEM terms
2.33 DLMS- Blue Book COSEM meter object model and the object identification
system
2.34 DLMS- Green Book Architecture and protocols to transport the model
2.35 DLMS- Yellow Book Conformance testing process
BSES

2.36 IEEE 802.15.4 Standard for Local and metropolitan area networks.
2.37 IEEE 802.15.4u Standard for Local and metropolitan area networks (Use of
the 865 MHz to 867 MHz Band in India)
Order of precedence between different standards shall be as follow:
i Indian Standards Issued By BIS
ii IEC standard
Iii Other standards like CBIP, DLMS etc.

3.0 Service Conditions

Operation range: -10 Deg C to 55 Deg C
3.1 Temperature Range Limit range of operation: -25 to 60 Deg C
Limit range of storage / transport : -25 to 70 Deg C
3.2 Relative Humidity 0 to 96 %

4.0 Distribution System Data

4.1 Supply 3 Phase AC, 4 wire
4.2 Voltage 415 V ± 6%
4.3 Frequency 50 Hz ± 5%
4.4 System Neutral Solidly Earthed

5.0 Electrical and Accuracy Requirement

5.1 Meter Type a. 3- ø, 4 wire static Transformer Operated Smart Meter
without LTCT box.
b. 3- ø, 4 wire static Transformer Operated Smart Meter
with LTCT box as per Appendix 4E
5.2 Connection Current Transformer Operated
5.3 Rated Voltage 240V (phase to neutral) with variation of +30% & -40%.

Page 288 of 473

 However meter should withstand the maximum system
voltage.
5.4 Rated Current Ib -5A and Imax- 10 A
5.5 Power factor range Zero lag – Unity – Zero lead
5.6 Starting current 0.1 % of base current
5.7 Rated Frequency 50Hz +/- 5%
5.8 Accuracy Class 0.5s (IS14697 applies for accuracy requirements)
5.9 Power Consumption As per IS 16444 (Part 2)
Meter with lowest power consumption shall be preferred.
5.10 Meter constant Imp/ unit (Bidder to specify meter constant)
5.11 Calibration Meter shall be software calibrated at factory and
modification in calibration shall not be possible at site by
any means or external influence.
5.12 Test Output Device Separate kWh & kVAh/kVArh Flashing LED visible from the
front
5.13 Process Technology Surface Mounting Technology or better
5.14 Insulation Level Meter shall withstand an insulation test of 4 KV and impulse
test at 8 KV
5.15 Influence of supply voltage As per IS 14697
5.16 Short time over current As per IS 14697
5.17 Immunity to phase and
As per IS 14697
earth fault
5.18 Influence of Self Heating As per IS 14697
5.19 Influence of Heating As per IS 14697
5.20 Electromagnetic a. Meter shall remain immune to electrostatic discharge
compatibility (upto and including 35KV), electromagnetic HF field and
fast transient burst.
BSES

b. The meter shall be designed in such a way that

conducted or radiated electromagnetic disturbances as
well as electrostatic discharge do not influence the
meter.
c. Meter shall be type tested for electromagnetic
compatibility.
d. Meter shall comply requirement of IS 14697
5.21 Limits of error due to Meter shall work within guaranteed accuracy as per IS
influence quantities 14697/ IEC62053-21/ CBIP325 (most stringent standard to
be followed) under and after influence of following :-
a. Current Variation
b. Ambient Temperature variation
c. Voltage variation
d. Frequency variation
e. 10% third harmonic in current
f. Reversed phase sequence
g. Voltage unbalance
h. Harmonic components in current and voltage circuit
i. DC and even harmonics in AC current circuit
j. Odd harmonics in AC current circuit.
k. Sub harmonics in AC current circuit
l. Continuous (DC) “stray” magnetic induction of 67mT+/-
5%.
m. Continuous (DC) “abnormal” magnetic induction of
0.27T+/-5%.
n. Alternating (AC) “stray’ magnetic induction of 0.5mT+/-

Page 289 of 473

 5%
o. Alternating (AC) “abnormal’ magnetic induction of
10mT.
p. External magnetic field 0.5 T
q. Electromagnetic HF fields
r. Radio frequency interference
s. DC immunity test
Note: BSES reserves the right to formulate any other test
method to check magnetic immunity/ logging of meter.
Meter with logging provision will be preferred.
5.22 Other features Mid night data: The meter should record midnight
Cumulative kWh & kVAh, kVARh lag and kVARh lead
reading for last min 45 days load survey data.
Total Harmonic Distortion: Meter to record harmonic
components in both current and voltage circuits. And should
be available in on demand display. Meter to record events
in case harmonic component in both V&I if it exceeds
threshold limits (configurable).
5.23 Display Sequence for the i. Default Display (Auto Mode)
parameters ii. LCD test
iii. Meter serial no.
iv. Date
v. Real time
vi. Cumulative kWh
vii. Cumulative Export Active Energy*
viii. Net Active energy*
ix. Cumulative kvarh Q1/Lag
BSES

x. Cumulative kvarh Q2/Lead

xi. Cumulative kvarh Q3*
xii. Cumulative kvarh Q4*
xiii. Cumulative kVAh
xiv. Cumulative Apparent Energy (active export)*
xv. Net Apparent energy*
xvi. Instantaneous load in kW, kVArh & kVA
xvii. TOD MD for kWh and kVAh
xviii. Phase wise voltage and current (R, Y, B phases)
xix. Power factor
xx. Neutral current
xxi. TOD Total Active Forward Energy Register(Reg
1)
xxii. TOD Total Active Forward Energy Register(Reg
2)
xxiii. TOD Total Active Forward Energy Register(Reg
3)
xxiv. TOD Total Active Forward Energy Register(Reg
4)
xxv. TOD Total Active Forward Energy Register(Reg
5)
xxvi. TOD Total Active Forward Energy Register(Reg
6)
xxvii. TOD Total Active Forward Energy Register(Reg
7)

Page 290 of 473

 xxviii. TOD Total Active Forward Energy Register(Reg
8)
xxix. TOD Apparent Forward Energy Register(Reg 1)
xxx. TOD Apparent Forward Energy Register(Reg 2)
xxxi. TOD Apparent Forward Energy Register(Reg 3)
xxxii. TOD Apparent Forward Energy Register(Reg 4)
xxxiii. TOD Apparent Forward Energy Register(Reg 5)
xxxiv. TOD Apparent Forward Energy Register(Reg 6)
xxxv. TOD Apparent Forward Energy Register(Reg 7)
xxxvi. TOD Apparent Forward Energy Register(Reg 8)
xxxvii. Temperature
xxxviii. Total tamper count
xxxix. Status of communication module
xl. Mode (Net/Forward)
xli. Signal strength in RSSI
xlii. Error code

Display (On demand)

After using pushbutton the following parameters should be
displayed.
i. LCD test
ii. Meter serial no.
iii. Date
iv. Real Time
v. Cumulative kWh
vi. Cumulative Export Active Energy*
BSES

vii. Net Active energy*

viii. Cumulative kvarh Q1/Lag
ix. Cumulative kvarh Q2/Lead
x. Cumulative kvarh Q3*
xi. Cumulative kvarh Q4*
xii. Cumulative kVAh
xiii. Cumulative Export Apparent Energy*
xiv. Net Apparent energy*
xv. Current MD in kW
xvi. Current MD in kVA
xvii. MD in kVAR
xviii. TOD MD for kW and kVA
xix. TOD MD occurrence for kW and kVA
xx. Instantaneous Power factor
xxi. Instantaneous voltage R phase
xxii. Instantaneous voltage Y phase
xxiii. Instantaneous voltage B phase
xxiv. Instantaneous current R phase
xxv. Instantaneous current Y phase
xxvi. Instantaneous current B phase
xxvii. Last month billing Date
xxviii. Last month billing kWh reading
xxix. Last month billing kVARh reading
xxx. Last month billing kVAh reading
xxxi. Last month billing Maximum Demand in kW

Page 291 of 473

 xxxii. Last month billing Maximum Demand in kW
occurrence Date
xxxiii. Last month billing Maximum Demand in kW
occurrence Time
xxxiv. Last month billing Maximum Demand in kVA
xxxv. Last month billing Maximum Demand in kVA
occurrence Date
xxxvi. Last month billing Maximum Demand in kVA
occurrence Time
xxxvii. THD for both Voltage and Current
xxxviii. Total Active Energy, Apparent Energy
xxxix. Fundamental Reactive Lag and Fundamental
Reactive Lead Energy
xl. High Resolution value (kWh, KVAh)
xli. High resolution Export Active Energy (kWh ,
KVAh)*
xlii. Neutral Current
xliii. Temperature
xliv. Battery status
xlv. PT/CT status
xlvi. Self diagnostic flag
xlvii. Connection check (Phase sequence)
xlviii. Cumulative Tamper count
xliii. Cumulative Power off hours
xliv. Signal strength in RSSI
xlix. Error code
l.
BSES

Phase association (ok/ Not ok)

* When meter is configured in net metering mode then only
these parameters should appear otherwise these display
parameters should be disable and shall not appear on
display
Note:
1. The meter display should return to Default Display mode
(mentioned above) if the ‘push button’ is not operated
for more than 6 seconds. Provision for scroll lock by
pressing for 15 sec and sent to normal after 5 minutes.
2. Sequence of display parameter and parameter subject
to change and to be finalized before supply.

6.0 Construction
Material - Opaque and UV stabilized polycarbonate of
6.1 Base Body grade LEXAN 143/ 943 or Equivalent with V0 inflammability
level.
a. Material: Transparent/Opaque and UV stabilized
polycarbonate of grade LEXAN 143/ 943 or Equivalent
with V0 inflammability level.
6.2 Top Cover b. Top cover and base should be Ultrasonically/Chemically
welded.
c. Top cover should be designed so as the internal
components should not be visible.
a. Material - Flame retardant glass filled polycarbonate of
6.3 Terminal Block grade 500 R or equivalent.
b. Terminal block shall form Integral part of the meter base
Page 292 of 473
 c. Terminal block shall be capable of passing the tests as
per ISO-75 for a temperature of 135C and pressure of
1.8MPa. The terminals shall be designed so as to ensure
adequate and durable contact such that there is no risk
of loosening or undue heating.
a. Material - UV stabilized transparent/Opaque
polycarbonate cover of grade LEXAN 143A/943AA or
equivalent.
b. Provision of sealing at two points through sealing screw.
c. The sealing screws shall be held captive in the terminal
cover.
d. The terminal cover shall be extended type with baffle
6.4 Terminal cover wall above the cable entry base wall so that access to
the terminals is not possible (even with thin metallic wire)
without breaking the seal. Terminal cover should have
provision for cable entry from bottom.
e. Diagram of external connections should be embossed on
terminal cover. Sticker is not acceptable.
f. Mechanism shall be provided to record an event with
occurrence and restoration in case of meter enclosure/
terminal cover is opened.
a. Terminals shall be suitable for 6 Sqmm copper wire.
b. Two no’s grub screws per terminal shall be provided
c. Material of terminals, screws and washers should be
brass or tinned copper. Terminals shall be tested for
6.5 Terminals
continuous current of 150 % Imax.
d. Terminals shall be clearly marked for phase / neutral /
BSES

outgoing etc.
e. Clearances and creepage shall be as per IS 14697.
a. SMC meter enclosure and LTCT’s as per Appendix 4E’
may be provided with meter.
6.6 Meter Enclosure b. Mechanism shall be provided to record an event with
occurrence and restoration in case of meter enclosure is
opened.
6.7 Ingress Protection IP 51 or better, but without suction in the meter.
Meter should have flashing LED visible from the front to
represent energy recording. Resolution shall be such that
6.8 Output device satisfactory accuracy test can be conducted at the lowest
load in less than 5 minutes and starting current test in less
than 10 minutes.
a. The meter shall have internal real time crystal clock to
set date and time.
6.9 RTC b. Drift in time of this clock shall not be more than
±5minutes/ year at a reference temperature of 27°C.
c. HES will sync RTC at least once a day (configurable).
Lithium ion battery with guaranteed design capacity of 15
years. Lithium thioyl Chloride battery will be preferred. In
case battery removal or total discharge same should not
affect the working & memory of the meter.
6.10 Battery
Meter should have two separate batteries.
One for RTC and one for back up
Incase battery voltage reduced below threshold value then
need to generate alert

Page 293 of 473

 Non volatile memory independent of battery backup,
6.11 Memory memory should be retained up to 10 year without any
auxiliary power.
Meter shall have self diagnostic for the following
a. Date and RTC.
b. Battery.
6.12 Self Diagnostic feature
c. Non volatile memory.
d. Display
e. Status of Communication card
Meter shall have an optical port with a metal ring to hold
6.13 Optical port magnet of probe. Optical port shall comply with hardware
specifications provided in IEC-62056-21.
a. Meter should have the provision for 01 no’s modular
and pluggable communication module compatible with
Cellular (4G).
b. Meter shall have mechanism to log communication
module removal and insert as an event in its memory
with date and time stamp.
6.14 Communication c. Meter shall have separate indications on display/ for
remote and local communication.
d. Communication module shall held in a casing which
can be directly plugged in the meter. Sealing screw
shall be provided.
e. Communication module shall be configurable for IPV6
with backward compatibility with IPV4
In Last Gasp endpoint shall send the power outage and
power restoration notification with Time Stamp. In case of
BSES

power failure meter communication module shall not draw

6.15 First breath and last gasp power from the backup battery.
For the purpose of sending the Last Gasp, communication
module shall have proper power backup (like a super
capacitor).
a. Sealing should be in accordance with IS and CEA
metering regulations with latest amendments.
b. Sealing arrangement shall be such that sealed parts
shall not be opened without breaking the seal or sealed
part itself. There should be clear evidence of the
breaking in case sealed parts shall be opened without
breaking the seal.
c. Approval shall be taken from purchaser for location of
seals and number of seals.
Meter Sealing
6.15 d. Record of all seals shall be forwarded to purchaser with
Arrangement
each lot.
e. Meter Body : 1 plastic seal and Hologram seal as per
BSES specs & 1 seal of meter manufacturer
f. Meter Terminal cover : 2 Plastic seal as per BSES specs
g. Meter Box : 2 plastic seal as per BSES Specifications
(All above seals provided by AMISP as per the serial no
provided by BSES )
h. Record of all seals shall be forwarded to purchaser with
each lot.
Record of all seals shall be forwarded to purchaser with
6.15.3 Seal record
each lot.

Page 294 of 473

 6.16 Insulation As Per IS 16444 Part 1
a. Meter should have clearly visible, indelible and distinctly
marked name plate in accordance with IS 16444 (Part
2) & clause no. 10.0 of this specification.
b. All markings and details shall be printed by laser only.
6.17 Name Plate and marking
c. Name plate shall have QR code having meter
information like meter [Link]., month and year of
manufacturing, type of meter, OEM, Rating etc
d. Paper stickers are not allowed for name plate.
The terminal block and Meter case shall have safety against
Resistance against heat
6.18 the spread of fire. They shall not be ignited by thermal
and fire
overload of live parts in contact with them as per IS 14697.
a. 10.5 Years from the date of dispatch or 10 Year from
date of commissioning, whichever is earlier
6.19 Guarantee b. The meters which are found defective/inoperative
within the guarantee period shall be replaced as per
meter service level agreement.

7.0 Functional Requirement

7.1 Meter category Smart meter comply with D3 category of IS 15959 (Part 3).
It should be possible to configure meters in following modes of
metering:
a. Forwarded Only: In this mode any export active energy shall
be treated as import energy and shall be recorded in forward
only register. Apparent energy calculation in this mode shall
be as per clause no. 7.3.
7.2 Mode of metering b. Bidirectional: Both Import and export energy recording shall
BSES

be applicable in this mode of metering and relevant registers

shall be updated.
Any change in metering mode shall be logged in events with date
and time stamp.
Default mode of metering shall be forwarded only untill specified
in tender requirement otherwise.
Lag only: KVAh is computed based on KVArh and KWH value. If
PF=1, or leading, then KVAh = KWH. At no instance KVAh <
7.3 kVAh Calculation
KWh.
Lag+Lead shall be configurable using FOTA if required in future.
Block / sliding window with default demand integration period of
1800 s configurable to 900 s as per requirement. Meter should be
configurable for block/ sliding window at the time of
7.4 MD calculation manufacturing. This change should not be possible in the field.
Extended register shall be used for MD recording.
It should be possible to reset MD automatically at the defined
date (or period) or through CMRI
a. Meter shall be capable of doing TOD metering in minimum 4
tariff rate registers programmable for minimum 8 time zones
and 4 seasonal profiles.
b. TOU metering shall be implemented by the activity colander
7.5 TOU Metering method of IS 15959 Part 1 clause 9/ DLMS UA-1000-1
c. Special Day table shall be defined as per IEC/ DLMS UA-
1000-1
d. Default TOU programming shall be as per latest DERC
guidelines. Prior approval shall also be taken from BSES for

Page 295 of 473

 the same.
e. Tariff rate registers shall be as follow
R1: Rate register for Peak
R2: Rate register for Normal
R3: Rate Register for Off Peak
All the parameters mentioned in table ‘1’ of IS 15959 (Part 3)
along with following additional parameters shall be supported by
meter.
a. Neutral Current (IN)
b. % TDH in R phase Voltage
Instantaneous c. % THD in Y Phase Voltage
7.6
Parameters d. % THD in B Phase Voltage
e. % THD in R phase Current
f. % THD in Y Phase Current
g. % THD in B Phase Current
h. Signal Strength in RSSI
i. Voltage angles for displaying phasors.
7.6.1 Association Rights As per Clause 11.1.1 of IS 15959 (Part 3).
a. Billing parameters shall be generated at the end of each
billing cycle and stored in memory as per provisions provided
in clause no. 14 of IS 15959 (Part 3).
b. 12 no’s billing cycle parameters shall be remain in meter
memory along with current cycle parameters and shall be
available for reading as well as profile and or ‘by entry’ for
7.7 Billing data
selective access.
c. All the parameters mentioned in table ‘4’ of IS 15959 (Part 3)
shall be supported by meter.
BSES

d. Cumulative power interruption count in all monthly history

data
e. Monthly Power off duration in all history data.
7.7.1 Association Rights As per clause 14 of IS 15959 (Part 3).
Support for selective access shall be provided for billing
7.7.2 Selective access
parameters as per clause no 11.3 of IS 15959 (part 1).
Billing period reset/
7.7.3 00:00 Hrs of Ist of every month
MD reset
Billing period reset
7.7.4 As per clause 10 of IS 15959 (Part 1)
mechanism
Cumulative billing period counter since installation and available
Billing period
7.7.5 billing periods shall be provided as per clause 11.2 of IS 15959
counter
(Part 1).
a. Load survey parameters shall be measured and recorded at
the end of each profile capture period for last 45 Power ON
days for 30min IP.
b. All the parameters mentioned in table ‘15’ of IS 15959 (Part
3) along with following additional parameters shall be
supported by meter:
7.8 Load survey Data % THD in R phase Voltage
% THD in Y Phase Voltage
% THD in B Phase Voltage
% THD in R phase Current
% THD in Y Phase Current
% THD in B Phase Current
Phase wise Voltage and Current with instant and average

Page 296 of 473

 value.
All three phase active, reactive (lag and lead) and apparent
power and energy.
Power-off time integration period
Neutral Current
Average Signal Strength
Profile capture
7.8.1 Default 1800 s programmable to 900 s.
period
Support for selective access shall be provided for billing
7.8.2 Selective Access
parameters as per clause no 11.3 of IS 15959 (part 1).
7.8.3` Association Rights As per clause no.18 of IS 15959 (Part 3)
Daily load profile parameters shall be measured and recorded at
each midnight i.e. 00:00 hrs for last 45 Power ON days.
7.9 Daily load profile
All the parameters mentioned in table ‘3’ of IS 15959 (Part 3)
shall be supported by meter as Daily load profile parameters.
7.9.1 Association Rights As per clause no. 13 of IS 15959 (Part 3)
General Purpose Following parameters shall be provided in Non Volatile memory
7.10
Parameters (NVM) of the meter as per clause 16 of IS 15959 (Part 3).
7.10.1 Name Plate Detail As per Table ‘12’ of IS 15959 (Part 3).
7.10.2 Association Rights As per clause no. 16.1 of IS 15959 (Part 3)
 These parameters can be programmed remotely by HES and
locally by HHU (mobile App) via proper access writes. Every
transaction shall be logged in non volatile memory of the
meter with date and time stamp.
Programmable
7.10.3
parameters  Programming of any of the parameters shall increment the
‘Cumulative programmable count’ value.
 All the parameters mentioned in table ‘13’ of IS 15959 (Part
BSES

3) shall be supported by meters with following additional

parameters as mentioned in specification
7.10.4 Association rights As per Clause no. 16.2 of IS 15959 (Part 3).
a. Smart meter is able to automatically notify data, event, and
messages to a destination client system in an unsolicited
manner (without a request from a client) as per clause no 6
of IS 15959 (Part 2).
b. Randomization: Data from different endpoints shall be
pushed intelligently on the network in order to avoid
excessive traffic on the network for example in case all the
endpoints will push load survey data simultaneously, then it
may result in network choking or inefficient performance.
Therefore with the help of intelligent techniques such field
7.11 Push Services scenarios shall be handled effectively.
c. It shall also be possible to configure push services for all
profiles i.e. instantaneous, billing, load survey, daily energy
and events. Bidder should explain its capability to configure
push services. However following push services shall be
available by default.
i. Load survey profile data at after every 4 hours
configurable to any predefined interval.
ii. Mid night data at 00:00 hrs of every day.
iii. Billing profile data on occurrence of billing.
Periodic push a. Meter shall be able to push instantaneous parameters to
7.11.1 (Smart meter to HES at predefined intervals. Parameters required for push
HES) shall be intimated during detailed engineering in the vent of

Page 297 of 473

 order.
b. Other attributes as per IS 15959 (Part 3) i.e. Send
Destination, Communication window, Randomization time
interval, number of retries and repeat delay shall be decided
in the event of manufacturing.
a. Meter is able to report HES, the status change of any of the
identified events mapped in to event status word (ESW) of
size 128 bits by pushing following objects to HES.
i. Device ID
ii. Push Setup ID
iii. Real time clock- Date and Time
iv. Event Status Word 1 (ESW 1).
Event Push (Smart b. Each of the bits in ESW shall reflect the current state of the
7.11.2
meter to HES) event and are mapped against each of the identified events.
c. An event status word filter (ESWF) of 128 bit shall also be
provided to configure events for event push. Events which
are supported in meter shall only be configured for event
push. Bit value 1 in ESWF shall indicate that the event is
supported and value 0 indicates that event is not supported
for event push. Position of the event bit in ESWF shall be
same as in ESW.
Event status Bit
7.11.3 As Per IS 15959 (Part 3)
mapping
a. Smart meter shall support remote firmware upgrade feature
for meter firmware without loss of any data and metrology for
a part or complete firmware of meter.
b. Firmware upgrade shall use the Image transfer classes and
BSES

mechanisms specified in IEC62056-6-2 and IEC62056-5-3.

c. Broad cast facility shall be supported in HES for
simultaneously upgrading the firmware of a group of meters
installed in field.
d. Firmware upgrade feature shall be provided with proper
security. The design shall take into account field scenarios
such as power failure during F/W upgrade.
e. Once the firmware is upgraded successfully, meter shall
send an acknowledgment to HES. It shall also log it as an
7.12 Firmware upgrade
event in its memory with date and time stamping.
f. Meter shall support capability to self register the meter with
new firmware.
g. The execution time of the change of the firmware within the
meter should be below 1 minute
h. Meter shall support auto resume firmware upgrade in case
file transfer stops due to any reason like power supply failure.
There shall not be any corruption in data during transfer of
firmware.
i. In case of wrong firmware file, meter shall be able to identify
the same and suspend FOTA activity
j. Meter shall support NIC FOTA through HES
k. NIC firmware file size should be less than meter firmware file
Meter shall support connection less messaging services of DLMS
Support for to support broadcast messages for a group of meters for
7.13
broadcast message following actions:
a. Gap reconciliations.

Page 298 of 473

 b. Firmware upgrade.
c. On demand readings
d. Updating of Programmable parameters
a. Advanced security outlined in clause 7.1.2 of IS 15959 (Part
1) shall be provided.
b. Reading and writing data into meter memory via optical and
remote communication port shall be through DLMS security
keys only.
c. Bidder shall ensure to safeguard high security keys used for
configuring parameters into meter.
d. Once the meter memory is locked during manufacturing
process, only parameters mentioned in IS 15959 shall be
7.14 Security configurable even in factory. It should not be possible to
configure any other parameters.
e. Please note that there shall be no other mechanism/ method
to interface with meter through optical and remote
communication port except mentioned in IS 15959, even for
manufacturer.
f. It should not be possible to change data stored in meter
memory even after accessing meter memory physically. In
case of any change in memory data, a flag/alert shall be
generated. Flag/Alert shall be indicated over display and in
remote communication also
Encryption for data
7.15 As per clause 7.1 of IS 15959 (Part 2)
communication
Encryption/
7.151 Authentication for As per clause 7.2 of IS 15959 (Part 2)
BSES

data transport
Key requirement and
7.15.2 As per clause 7.3 of IS 15959 (Part 2)
handling
a. Proper security at end points as well as network level shall
be present to prevent unauthorized hacking of the end points
or the network itself.
b. The meter password is required to open a session between
NIC and meter and is required to gain clearance from the
meter to perform requested operation.
7.15.3 NIC Security c. If clearance not gains, the meter locks out local
communication for 1 minute. The meter maintain counter for
monitoring of unsuccessful attempts of performing meter
operations and alerts to HES. The counter is incremented
each time a password clearance operation fails.
Up to 3 no’s unsuccessful attempts are allowed, after which the
port is locked out until authenticated from system administrator.
IP communication Meter shall support TCP-UDP/ IP communication profile for smart
7.15.4
profile support meter to HES. Please refer clause 8 of IS 15959 (Part 3).
Meter shall detect and log any exceptional/ fraud/ tamper
conditions in its memory as an event. In addition to this all
Event and tamper
7.16 transactions and control shall also be recorded as an event in
detection
meter memory. Each event type shall be identified by an event
ID.
Each event shall be available to download as per following
7.17 Association Rights association rights.
a. Public Client: No access

Page 299 of 473

 b. Meter Reader: Read only
c. Utility Settings: Read only
Push Services: Read Only for identified events as per ESWF
Meter shall be able to log events in following compartments
a. Voltage Related Events
b. Current Related Events
Compartments of c. Power Related Events
7.18
events d. Others Events
e. Non Roll Over Events
f. Transaction related events
g. Control Events
a. Occurrence and Restoration of Voltage Related, current
related, power related and other events shall be logged in
meter memory as per IS 15959 (Part 3). Please refer
Appendix 4A for description of events, Event ID, Logics of
events and threshold values of events.
b. Threshold values shall be factory programmable.
Compartments of c. Selective access shall be provided as per clause 11.3 of IS
7.18.1 events 15959 (Part 1).
Parameter Snapshot d. For each of the events a certain list of parameters shall be
captured as per clause 'a'
h. For each occurrence event captured, the cumulative tamper
count shall be incremented.
i. Meter shall capture all the parameters mentioned in table ‘24’
of IS 15959 (part 3) when event occurrence and restoration is
logged
The meter shall log minimum 200 tamper events (ensuring at
BSES

7.18.2 Event Logging

least 20 events for each tamper).
Appropriate Indications/Icons for all tampers should appear on
7.18.3 Tamper Indication
the meter display either continuously or in auto display mode.
Phasor Meter shall support parameters required to develop phasors of
7.18.4
Representation current and voltage at HES.
All the energies measured and recorded with and without
7.19 Harmonic Energies
harmonics.

8.0 Meter Display

8.1 LCD Type STN Liquid crystal with backlit
a. Minimum 120 Degree.
8.2 Viewing angle b. The display visibility should be sufficient to read the Meter
mounted at height of 0.5 m as well as at the height of 2 m.
8.3 Size of LCD Minimum 10X5mm PIN Type
8.4 LCD Digits Total 10 digits
8.5 LCD language English
a. Auto Mode
b. Manual Mode
8.6 Display modes c. Sub active mode
Display list shall be finalized during detailed engineering in the
event of order.
Appropriate indications/flags for all tampers and self diagnostic
8.7 Display indications
features should be provided.

9.0 Data and communication protocol/ HES/Integrations/ Software

9.1 Data Exchange a. Meter should comply Indian companion of data exchange
Page 300 of 473
 protocol and tariff control specification IS 15959 (Part 2).
b. In case of additional requirement from IS 15959 (part 2),
they shall be as per DLMS standards/ IEC DLMS protocols
suite (62056).
c. Bidder shall explain in detail the additional parameters/
services/ methods used in meters from IS 15959 (part 2)
and its reference to DLMS books/ IEC.
d. Prior to manufacturing of meters bidder shall provide a
detailed specification explaining all parameters/ services/
methods used in meter in addition to IS 15959 (Part 3).
Base computer
9.3 Bidder shall provide BCS software for lab testing
software
a. The manufacturer has to provide Mobile App for
downloading all the data stored in meter memory through
optical port.
b. Mobile App should have option for selection of parameters
to be downloaded from meter
c. Meter data consisting of all parameters and complete load
survey for all parameters shall be read by HHU (Mobile
Hand Held Unit
9.4 App) and data transferred to HES in minimum possible time
Software (Mobile App)
(not more than 5 minutes).
d. Mobile App should have option to initiate configuration and
firmware upgrade actions locally for non-communicated
meters as per the schedule initiated from back end
applications (HES/MDMS).
e. Mobile App should ensure the meter security keys are
stored in encrypted form and not accessible to users.
BSES

Manufacture shall impart training to BSES personnel for usage

9.5 Training
of software

10.0 Name Plate

Meter Serial number shall be of 10 digits. Serial number shall be printed in black colour.
10.1
Embossing is not acceptable.
Size of the digit shall be minimum 5 X 3mm. Details shall be printed by laser printing
10.2
preferably.
10.3 Bar code shall be printed below the serial number
10.4 BIS registration mark (ISI mark)
10.5 ‘BSES’ insignia shall be printed above LCD display.
10.6 BSES PO No. & date and Property of BSES
10.7 Manufacturers name and country of origin
10.8 Model type / number of meter
10.9 Month and Year of manufacturing
10.10 Reference voltage / current rating
The number of phases and the number of wires for which the meter is suitable.
10.11
Graphical symbol as per IS 12032 can be used.
10.12 Meter constant Impulse/kWh Impulse/kVAh/kVArh
10.13 Class index of meter
10.14 Reference frequency
10.15 Warranty period
Name plate of NIC
a. Serial no of NIC along/ IMEI no/MAC address with bar code
10.16
b. Name of purchaser’s
c. Communication technology with carrier frequency

Page 301 of 473

 d. Manufacturing year and month.
e. Warranty period.

11.0 Component Specification

Current The Meters should be with the current To meet accuracy
11.1
Transformers transformers as measuring elements. requirement
The Measurement or computing chips
Analog Devices, Cyrus
Measurement or used in the Meter should be with the
11.2 Logic, Atmel, Phillips,
computing chips Surface mount type along with the
SAMES ,NEC,TEXAS
ASICs.
The memory chips should not be Atmel, National
affected by the external parameters Semiconductors, Texas
11.3 Memory chips
like sparking, high voltage spikes or Instruments, Phillips,
electrostatic discharges. ST, Hitachi, Compiled
a. The display modules should be
well protected from the external
UV radiations. Hongkong: Genda
b. The construction of the modules Singapore: Bonafied
should be such that the displayed technologies
11.4 Display modules
quantity should not disturbed with Korea: Advantek
the life of display (PIN Type). China: Success
c. It should be STN type industrial Japan: Hitachi, Sony
grade with extended temperature
range min 70 ºC.
The mechanical construction of the USA: National
port should facilitate the data transfer. Semiconductors, HP
11.5 Optical port
Communication shall not disturbed by
BSES
Holland/ Korea: Phillips
external light. Japan: Hitachi, Ligitek
The power supply should be with the
capabilities as per the relevant
standards. The power supply unit of
11.6 Power Supply the meter should not be affected in SMPS Type
case the maximum voltage of the
system appears to the terminals due
to faults or due to wrong connections.
The active & passive components
should be of the surface mount type & USA: National
are to be handled & soldered by the Semiconductors, Atmel,
state of art assembly processes. Phillips, Texas
Electronic The PTH components should be Instruments.
11.7
components positioned such a way that the leads Japan: Hitachi, Oki,
of components should not be under AVX or Ricoh
stress and not touching the internal Korea: Samsung
wires.
LED Everlight, Agillent
a) The internal electrical components
should be of electrolytic copper &
should be protected from corrosion,
rust etc.
11.8 Mechanical parts
b) The other mechanical components
should be protected from rust,
corrosion etc. by suitable
plating/painting methods.
11.9 Battery Lithium with guaranteed life of 15 Texcell, SAFT, Varta,

Page 302 of 473

 years Tedirun, Sanyo
USA: Philips, Dallas
RTC & Micro The accuracy of RTC shall be as per Atmel, Motorola,
11.10
controller relevant IEC / IS standards Microchip, TEXAS,
Japan: NEC, Oki
Glass Epoxy, fire resistance grade
11.11 P.C.B. (BBT test is must)
FR4, with minimum thickness 1.6 mm
a. The components used by
manufacturer shall have “Minimum
Life” more than the 10 years.
b. Incase vendor want to use other
make components; same shall be
approved by BSES before use.
c. Even for existing supplier – fresh
11.12 Note approval is needed for all
deviations.
d. Manufacturer should have
complete tracking of material used
in meter. BSES reserve the right
to carry out audit of inventory/
manufacturing process at
manufacturer’s works and sub
vendor’s work.

12.0 Quality Assurance, Inspection and Testing

Vendor's Quality
12.1 To be submitted for Purchaser's approval.
Plan (QP) BSES

Sampling Method for quality checks shall be as per relevant IS/

12.2 Sampling Method IEC/ CBIP guidelines and Purchaser's prior approval shall be
taken for the same.
Inspection Hold-
12.3 To be mutually identified, agreed and approved in Quality Plan.
Points
a. The meter shall be of type tested quality including all tests
specified in this specification which are beyond IS / IEC or
CBIP.
b. Type test conducted from CPRI/ ERDA/ or any other lab
specified by BIS/ CEA for smart meter testing will be
treated as valid.
12.4 Type Tests
c. Type test certificate should be submitted along with offer for
scrutiny.
d. Any other component supplied in addition to meter shall
also be type tested as per IS /IEC if applicable.
e. Complete type test as per IS 16444 (Part 2) shall be carried
out on sample selected from BSES lot.
12.5 Routine tests All test marked “R” as per table 20 of IS 14697.
a. All tests marked “A” as per IS 14697.
b. Smart meter functional tests as per IS 16444 (Part 2).
c. Test for data exchange protocol as per IS 16444 (part 2).
12.6 Acceptance Tests d. Test for Smart meter communicability as per clause no.
10.6 of IS 16444 (Part 2).
e. All the routine and acceptance tests shall be carried out as
per relevant standards.
f. Following tests in addition to IS shall be conducted during

Page 303 of 473

 lot inspection.
I) Dimensional and drawing verification.
II) Display parameters/ sequence.
III) Data Downloading from CMRI and PC.
IV) Tamper/ fraud detection/logging features as per
approved documents. Tamper conditions will be
simulated at varying load up to Imax. Accuracy will
also be checked during tamper simulation.
V) Burn in chamber test.
VI) Component verifications.
g. Purchaser reserves the right to formulate any other test
method to verify guaranteed parameters of Meter.
ESD and Magnetic ESD and magnetic interference test will be conducted at Samir
12.7
Interference test lab, Chennai or CPRI.
a. Purchaser reserves the right to inspect /witness all tests on
the meters at Seller’s works at any time, prior to dispatch,
to verify compliance with the specification/ standards.
b. Manufacturer should have all the facilities/ equipments to
conduct all the acceptance tests as per clause 14.3
12.8 Inspection
relevant standards and tampers logics as per approved
GTP. All the equipments including tamper logs kits/ jigs
should be calibrated.
c. In-process and / or final inspection call intimation shall be
given in advance to purchaser.
a. The internal potential links should be in closed position
or link less meters will be preferred and there shall not
be any external link.
BSES

b. Deliverable with Meters.

i. Hard copies for Routine test certificates with each
meter till alternate is provided by vendor and
approved BSES.
ii. Terminal cover should be fixed on the meter before
dispatch.
iii. Report of seal & initial reading record. (soft copy as
per BSES format)
c. Box number, meter serial number, type, rating should be
mentioned on cases / cartons.
General d. Meters shall be suitably packed with environmental
12.8 friendly material in order to avoid damage or disturbance
Requirements
during transit or handling and to prevent in grace of
moisture and dust. Also refer CEA Metering Regulation
2006.
e. In case battery removal/ total discharge same should not
affect the working & memory of the meter.
f. The bidder shall maintain a web site where routine test
results of all meter supplied against these tender will be
maintained and will be accessible to buyer/ buyer
representative.
g. The supplier shall give 15 day advanced intimation to
enable BSES to depute representative for lot inspection.
h. Vendor shall ensure that patch required for HHU/CMRI
shall be provided within 4 weeks. Vendor shall also
ensure to deliver solution to meet DERC mandate within

Page 304 of 473

 mutually agreed timeline.
i. Delivery of software for reading through HHU/CMRI
before meter delivery is required.
j. For any false events recorded in meter, vendor shall
depute their representative for field visit within one week
and provide the root cause analysis in 4 weeks time.

13.0 Packing, Marking, Shipping, Handling and Storage

a. Each meter must be packed, together with its terminal
cover, in a separate environmental friendly cardboard box,
which can be opened and re-closed without needing
adhesives.
b. Up to 4 to 5 three-phase meters must be packed together
with their terminal covers in a group cardboard box, which
can be opened and re-closed without needing adhesives.
c. The box shall prevent, as much as possible, penetration of
dust during long storage periods. The box must be
designed for multiple use and be robust, with wall
thickness of at least 4 mm.
d. Maximum weight of a group meter box shall not be more
than 25 Kg.
e. The packaging will protect the meters against shock and
vibration, preventing damage due to the road conditions
13.1 Packing during transport and distribution in the field. The electrical
and mechanical properties shall not be affected by these
disturbances.
f. For shipping the boxed meters will be close packed by
BSES

stockpiles of suitable quantities on pallets. The meters

numbers sequence (without partition) shall be kept in each
pallet. A pallet will be protected against moisture by a
polyethylene hood, covered with a cardboard cover (hood),
and fixed onto the pallet by parallel polypropylene bands,
using protection angle bars at the corners. The hood shall
be marked – on the front (wide side), on the narrow side
and on the top as per clause 13.3.
g. Visual indications (stickers) shall be attached to the
cardboard hood of several pallets in each container/
transport truck, to warn of possible rough handling during
shipment, transport and storage.
Packing for
Robust wooden non returnable packing case with all the above
13.2 accessories and
protection & identification Label.
spares
On each group box and pallet, following details are required
both on front (wide side) and top:
a. BSES logo.
b. Meter serial number range along with bar code.
c. Unique number of box/ pallet.
13.3 Marking d. Purchaser’s name
e. PO number (along with SAP item code, if any) & date with
bar code
f. Equipment Tag no. (if any)
g. Destination
h. Manufacturer / Supplier’s name

Page 305 of 473

 i. Address of Manufacturer / Supplier / it’s agent
j. Type , rating and other description of equipment
k. Country of origin
l. Month & year of Manufacturing
m. Case measurements
n. Gross and net weights in kilograms
o. All necessary slinging and stacking instructions
13.4 Test reports Routine test report to be provided with each meter
The seller shall be responsible for all transit damage due to
13.5 Shipping
improper packing.
Manufacturer instruction shall be followed. Detail handling &
Handling and
13.6 storage instruction sheet /manual to be furnished before
Storage
commencement of supply.

14.0 Deviations
a. Deviations from this specification can· be acceptable, only where the
Seller has listed in his quotation the requirements he cannot, or does
not, wish to comply with and which deviations the Buyer has agreed to
in writing, before any order is placed.
14.1 Deviations
b. In the absence of any list of deviations from the Seller, it will be
assumed by the Buyer that the Seller complies with the Specification
fully.
c. Refer Annex C for deviation

15.0 Drawing Submission

Drawing submission shall be as per the matrix given below. All documents/ drawing shall be
provided on A4 sheet in box file with separators for each section. Language of the documents
BSES

shall be English only. Deficient/ improper document/ drawing submission may liable for rejection
SL Detail of Document Bid Approval Pre Dispatch
1 Guaranteed Technical particulars (GTP) Required Required
2 Deviation Sheet, if any Required Required
3 Tamper Sheet Required Required
4 Display Parameters Required Required
GA / cross sectional drawing of Meter showing all
5 Required Required
the views / sections
Detail of network interface i.e. pin out, standard,
6 Required Required
voltage level etc and its integration requirement.
Samples of each type and rating offered along
7 with box (Highest rating offered) and 2 no's 1 no's
communication.
Any software and accessories required for
8 Required Required
installation/ operation of meter
Manufacturer's quality assurance plan and
9 Required
certification for quality standards
10 Type Test reports of offered model/ type/ rating Required
11 BIS certificate Required
12 Complete product catalogue and user manual. Required
13 Customer Reference List Required
14 Recommended list of spare and accessories Required
Specification documents containing all
15 parameters, Services, Methods in addition to Required
companion specification of IS 15959 (part 2).
16 Program for production and testing (A) Required Required

Page 306 of 473

 17 Makes of components Required Required
Detailed installation and commissioning
18 Required Required
instructions
19 As Built Drawing Required Required
Operation and maintenance Instruction as well as
20 Required Required
trouble shooting charts/ manuals
Inspection and test reports, carried out in
21 Required
manufacturer’s works
22 Routine Test certificates Required
23 Test certificates of all bought out items Required
24 Meter Seal data Required
Mapping of meter serial no to Communication
25 Required
card.
Other documents:
a. Completely filled-in Technical Parameters
b. General arrangement drawing of the meter
c. Rating plate
d. Terminal Block dimensional drawing
26 e. Mounting arrangement drawings Required Required
f. Meter box drawing and dimensions
g. Display parameter
h. PIN configuration of Optical to RJ11
connector
i. Manual and SOP/DWI for operation

16.0 Delivery
Dispatch of Material: Vendor shall dispatch the material, only after the
BSES

Routine Tests/Final Acceptance Tests (FAT) of the material

16.1 Delivery
witnessed/waived by the Purchaser, and after receiving written Material
Dispatch Clearance (MDC) from the Purchaser.

APPENDIX 4A- GUARANTEED TECHNICAL PARTICULARS

Bidder shall furnish the GTP format with all details against each clause of this specification.
Bidder shall not change the format of GTP or clause description.
Bidder to submit duly filled GTP in hard copy format with company seal.
Clause No. Clause Description Manufacturer’s Reply
1
2
3
4
5

Bidder / Vendor seal / signature ---------------------------

Name of the bidder

Address of the bidder
Name of contact person
Telephone number and email id

APPENDIX 4B- RECOMMENDED ACCESSORIES / SPARES

SL Description of spare part Unit Quantity

Page 307 of 473

 1 No
2 No
3

APPENDIX 4C- DEVIATION SHEET

Clause No. Clause Description Deviation Details Manufacturer’s Reply
1
2
3
4
5

APPENDIX 4D- TAMPER AND FRAUD DETECTION/ EVENTS

1. Voltage Related Events:
Logic Expression/ Persistence
Description of
Logic Of Event Threshold values Time
event
(Configurable) (Configurable)
R Phase Voltage
Missing
(Occurrence/ Absence of potential on
Restoration) any phase should be
Y Phase Voltage logged. Restoration of Occurrence: If Vpn<10% Occurrence: 5
Missing normal supply shall also Vref and Ip>10% Ib Min
(Occurrence/ be recorded. The threshold Restoration: If Vpn>=10% Restoration: 5
Restoration) value of voltage should be Vref and Ip>10% Ib Min
B Phase Voltage programmable at factory
Missing end
BSES

(Occurrence/
Restoration)
Meter should log high Occurrence: If Vpn>10% Occurrence: 5
Over Voltage
voltage event if voltage in Vref Min
(occurrence/
any phase is above a Restoration: If Vpn<=10% Restoration: 5
restoration)
threshold value. Vref Min
Meter should log low
voltage event if voltage in Occurrence: If Vpn<75% Occurrence: 5
Low Voltage
any phase is below a Vref Min
(occurrence/
threshold value. Threshold Restoration: If Vpn<=75% Restoration: 5
Restoration)
value if factory Vref Min
programmable.
Meter should log voltage
imbalance event when the
difference between Occurrence: If Vmax- Occurrence: 5
Voltage Unbalance
minimum and maximum Vmin>30% Vref Min
(Occurrence/
phase voltage is more than Restoration: If Vmax- Restoration: 5
Restoration)
a threshold value. Vmin<=30% Vref Min
Threshold value should be
factory programmable.
R Phase high Meter should log
Voltage Harmonics occurrence of high voltage Occurrence: If % THD in Occurrence: 5
Y Phase high harmonic event when % Vpn>5% of fundamental. Min
Voltage Harmonics THD in voltage of phase Restoration: If % THD in Restoration: 5
B Phase high will be more than threshold Vpn<5% of fundamental. Min
Voltage Harmonics value. Threshold value

Page 308 of 473

 should be factory
programmable.
2. Current Related Events:
Current
Reverse/ R
Phase Current
Reverse
(occurrence/ Meter should log the event of
Restoration) reversal of C.C polarity.
Y Phase Meter should register energy Occurrence: If Ip = -ve Occurrence:
Current consumed correctly with any direction 5 Min
Reverse one, two or all three current Restoration: If Ip=+ve Restoration:
(occurrence/ coils reversed. This event shall direction 5 Min
Restoration) not be valid in bidirectional
B Phase mode of metering.
Current
Reverse
(occurrence/
Restoration)
R Phase
Current Open
(Occurrence/
Restoration) Occurrence :Vector
Y Phase Meter should log the event of Sum(IR+IY+IB+IN)>20% Ib and Occurrence:
Current Open current coil open. Threshold I<10% Ib 5 Min
(Occurrence/ value of current should be Restoration : Vector Restoration:
Restoration) programmable at factory end. Sum(IR+IY+IB+IN)< 20% Ib and 5 Min
B Phase I>5% Ib
BSES

Current Open
(Occurrence/
Restoration)
Current
Unbalance
(Occurrence/
Restoration)
Meter should log the event of
Occurrence : Vector
current coil shorting/bypass.
Current Bypass Sum(IR+IY+IB+IN)>20% Ib and
Threshold value of current
(Occurrence/ I (any Phase) >5% Ib
should be programmable at
Restoration Restoration : Vector
factory end and also
Sum(IR+IY+IB+IN)>5% Ib
configurable through HES.
If the current in any phase Occurrence:
Over current
exceeds the specified threshold Occurrence: If Ip>Imax 5 Min
(occurrence/
current, meter should log over Restoration: If Ip<=Imax Restoration:
restoration)
current event. 5 Min
R Phase high
Current
Meter should log occurrence of
Harmonics
high voltage harmonic event Occurrence: If % THD in Occurrence:
R Phase high
when % THD in voltage of IP>5% of fundamental. 5 Min
Current
phase will be more than Restoration: If % THD in IP Restoration:
Harmonics
threshold value. Threshold <5% of fundamental. 5 Min
R Phase high
value should be factory
Current
Harmonics

Page 309 of 473

3. Power Related Events:
Meter shall detect power OFF if
all phase voltages are absent.
Power OFF
This event shall be recorded at
(occurrence/
the time of each power OFF. At
restoration)
the same time power ON event
shall be recorded.
If meter micro detect power off
Abnormal whereas phase voltage is Occurrence: If voltages at
Power Off present than abnormal power meter power supply<10%
NA
(Occurrence/ will be recorded. Meter sall Vref and Vp>20% vref.
restoration) continue to record energy as Restoration:
per phase voltage and current.
4. Other Events:
a. Meter should either be
immune or should log the
events of attempt of tampering
by external magnetic
field as per relevant IS14697/
CBIP 325 with latest
Abnormal amendments.
External b. If the working of meter gets
Magnetic affected under the As per IS
As per IS 14697/ CBIP 325
Influence influence of external magnetic 14697
(Occurrence/ field, meter should
Restoration) record energy at Imax. Meter
should not compute
MD during this period. TheBSES

meter shall record

energy as per actual load once
the magnetic field is
removed.
Neutral
Disturbance- Bidder shall
Meter should log the event
HF, DC and As per manufacturing define
when AC/DC/ Pulsating voltage
Alternating standard. threshold
is injected in neutral circuit.
(occurrence/ values
restoration)
Meter shall able to detect and
log the low PF event if power
factor of the load found in
between 0.2 to 0.5 for a load
Low Power above than a % threshold value 10% of I
Factor for a threshold time value. basic
Event shall restore if PF factor
of load remain out of range 0.2
to 0.5 for a load above than %
threshold value for
Plug in
Communication Meter should log the removal of
module removal communication card. Meter
(Occurrence/ should also log insertion of
Restoration) communication card. By NC switch/ sensor
Configuration Meter should log the change in

Page 310 of 473

 change to metering mode configuration.
“Forwarded”
only" mode/
“Import and
Export” mode
Overload
Meter should able to log the
(Occurrence/
status of overload in KW
Restoration)
Meter with communication card
HV Spark
should be immune or log the
(Occurrence/
event in the case of application Immediately NA
restoration)/
of ESD upto and including 35
Jammer
KV.
Meter should log event of high
Occurrence: If IN > 50% of Occurrence:
neutral current if measured
High neutral average phase current 5 Min
neutral current should be more
Current Restoration: If IN < 50% of Restoration:
than predefined threshold
average phase current 5 Min
value.
Meter shall log the event if Occurrence:
difference between 5 Min
Distorted PF
displacement PF and actual PF Restoration:
is more than a predefined value 5 Min
Meter shall log voltage, current,
Time Based
PF and energy consumption on As per predefined time NA
Event Stamp
a predefined time
If temperature is more than
Temperature 60deg C. Meter has to log as - -
an event and sent alertBSES

5. Non Roll over events:

Event Description
Occurrence of cover open
6. Transaction Related Events:
Detail of Transaction
Real Time Clock- Date and Time
Demand Integration Period
Profile Capture Period
Single Action schedule for billing date
Activity calendar for time zones
New firmware activated
Load Limit (Kw) Set
Enable Load Limit Function
Disable load limit function
LLS secret (MR) change
HLS key (US) change
HLS key (FW) change
Global key change
ESWF change
MD reset

Note:
1. Event ID’s shall be defined as per BSES specification/ IS 155959 (part 2). Approval shall be
taken from BSES prior to manufacturing for Event ID’s
2. Programming of threshold values should be possible from remote via proper authentications.

Page 311 of 473

 3. Logics of tampers can be changed/ upgraded via firmware up gradation from remote via
proper authentication.
4. All the programming changes/ firmware up gradations shall be logged along-with date and
time stamp in meter as well as on HES.

APPENDIX 4E- TECHNICAL SPECIFICATION OF LTCT BOX

Requirement Data by
S No. Parameters
Supplier
1 Manufacturer name
2 Nominal/Highest system voltage 415V/660V
3 Box details
3.1 Material SMC
3.2 Base Opaque, dark grey
3.3 Top cover Transparent
3.4 Overall dimensions As per Appendix 4C
3.5 Marking of terminations To be provided
Suitable Arrangement for modem To be provided
3.6
installation
Rating Plate Two nos. (one each on box
3.7
and CT block)
Connection diagram To be provided on rating
3.8
plate mounted on CT block
3.9 Protection Class IP55
3.10 Sealing arrangement BSES
To be provided on all corners
3.11 Nuts & Bolts For I/C & O/G connections
3.12 Mounting channel MS (HDG)
3.13 Fasteners for Installation 4 nos.
3.14 Gland Plate 200 x 100mm, MS (HDG)
3.15 Cable Gland To be provided
4 CT Details
4.1 Reference standard IS 16227
4.2 Type of CT Resin cast
4.3 Class of accuracy 0.5s
4.4 ISF <=10
4.5 Burden 5 VA
Transformation Ratio 400/5 A /200/5 A/100/5 A as
4.6
per purchaser’s requisition
4.7 Frequency 50 Hz
4.8 Insulation level 660V / 3KV
4.9 Insulation class E
4.10 Short time current rating for 1 sec. 20 times the rated current
4.11 Primary winding type Bar
4.11.1 Material of conductor Aluminium
4.11.2 Size of conductor 1A/Sqmm
4.12 Secondary winding Wound
4.12.1 Material of conductor Copper
4.12.2 Size of conductor

2.0 LTCT Box layout and CT Detail

Page 312 of 473

BSES

Page 313 of 473

Appendix 5: Technical Specification of DT Smart Meter

1.0 Scope of Supply

This specification covers the design, manufacture, assembly, inspection, testing and delivery of
supply of Accuracy Class 0.5S (Active & Reactive), 3 x 240 V and 5-10 A static smart energy
meter for DT with plug in communication module (Cellular (4G)) and accessories required for
successful operation of the meter.

A. Design, manufacture, testing at manufacturer works before dispatch, packing, delivery and
submission of all documentation.
B. Any accessories / hardware required for installation and operation for the meter.

2.0 Codes & standards

Materials, equipment and methods used in the manufacturing of above mentioned equipment shall
conform to the latest edition of following
S No. Standard Number Title
2.1 Indian Electricity Act IE Act 2003
CEA Metering
2.2 With latest amendments
Regulations
CBIP Manual (Pub no.-
2.3 Standardization of AC Static Electrical Energy Meters
325)
AC Static Transformer Operated Watt-hour And Var-hour Smart
2.4 IS- 16444 (Part 2) Meters, Class 0.2 S, 0.5 S And 1.0 S Part 2 Specification
Transformer Operated Smart Meters
ac Static Transformer Operated Watt-hour and Var-hour
2.5 IS- 14697 BSES

Meters, Class 0.2 S and 0.5 S

Data Exchange for Electricity Meter - Reading Tariff and Load
2.6 IS-15959 (Part 1)
Control - Companion Specification
Data Exchange for Electricity Meter - Reading Tariff and Load
2.7 IS-15959 (Part 2)
Control (Part 2)- Companion Specification for smart meter
Data Exchange For Electricity Meter Reading, Tariff And Load
Control-Companion Specification Part 3 Smart Meter
2.8 IS-15959 (Part 3)
(Transformer Operated Kwh And KVARh Class 0.2 S, 0.5 S
And 1.0 S
2.9 IS- 11448 Application guide for AC Electricity meters
Electricity metering equipment (AC) - General requirements,
2.10 IEC- 62052-11
tests and test conditions - Part 11: Metering equipment
Electricity metering equipment (A.C) - Particular requirements -
2.11 IEC- 62053-21
Part 21: Static meters for active energy (classes 1 and 2)
Electricity metering equipment (AC) - Particular requirements -
2.12 IEC- 62053-52
Part 52: Symbols
Electricity metering equipment (A.C.) - Particular requirements -
2.13 IEC 62053-61
Part 61: Power consumption and voltage requirements
Electricity metering equipment (AC) - Acceptance inspection -
2.14 IEC 62058-11
Part 11: General acceptance inspection methods
Electricity metering equipment (AC) - Acceptance inspection -
2.15 IEC 62058-31 Part 31: Particular requirements for static meters for active
energy (classes 0,2 S, 0,5 S, 1 and 2)
2.16 IEC 60736 Testing Equipment for electrical Energy meter
Electricity Metering — Data Exchange For Meter Reading, Tariff
IS/IEC/TR 62051:Part
2.17 And Load control — Glossary Of Terms Part 1 Terms Related
1:2004
To Data Exchange With metering Equipment Using DLMS/

Page 314 of 473

 COSEM
2.18 IEC 62056-1-0:2014 Smart metering standardisation framework
2.19 IEC 62056-3-1:2013 Use of local area networks on twisted pair with carrier signalling
2.20 IEC 62056-4-7:2014 DLMS/COSEM transport layer for IP networks
2.21 IEC 62056-5-3:2017 DLMS/COSEM application layer
2.22 IEC 62056-6-1:2017 Object Identification System (OBIS)
2.23 IEC 62056-6-2:2017 COSEM interface classes
Mapping between the Common Information Model message
2.24 IEC 62056-6-9:2016 profiles (IEC 61968-9) and DLMS/COSEM (IEC 62056) data
models and protocols
Wired and wireless M-Bus communication profiles for local and
2.25 IEC 62056-7-3:2017
neighbourhood networks
2.26 IEC 62056-7-5:2016 Local data transmission profiles for Local Networks (LN)
The 3-layer, connection-oriented HDLC based communication
2.27 IEC 62056-7-6:2013
profile
IEC TS 62056-8-
2.28 Mesh communication profile for neighbourhood networks
20:2016
Communication profile using web-services to access a
2.29 IEC TS 62056-9-1:2016
DLMS/COSEM server via a COSEM Access Service (CAS)
2.30 IEC 62056-9-7:2013 Communication profile for TCP-UDP/IP networks
2.31 IEC 62056-21:2002 Direct local data exchange
2.32 DLMS- White Book Glossary of DLMS/COSEM terms
2.33 DLMS- Blue Book COSEM meter object model and the object identification system
2.34 DLMS- Green Book Architecture and protocols to transport the model
2.35 DLMS- Yellow Book Conformance testing process
2.36 IEEE 802.15.4 Standard for Local and metropolitan area networks.
Standard for Local and metropolitan area networks (Use of the
2.37 IEEE 802.15.4u BSES

865 MHz to 867 MHz Band in India)

Order of precedence between different standards shall be as follow:
i Indian Standards Issued By BIS
ii IEC standard
Iii Other standards like CBIP, DLMS etc.

3.0 Service Conditions

Operation range: -10 Deg C to 55 Deg C
3.1 Temperature Range Limit range of operation: -25 to 60 Deg C
Limit range of storage / transport : -25 to 70 Deg C
3.2 Relative Humidity 0 to 96 %

4.0 Distribution System Data

4.1 Supply 3 Phase AC, 4 wire
4.2 Voltage 415 V ± 6%
4.3 Frequency 50 Hz ± 5%
4.4 System Solidly Earthed
Neutral

5.0 Electrical and Accuracy Requirement

5.1 Meter Type a. 3- ø, 4 wire static Transformer Operated Smart Meter
5.2 Connection Current Transformer Operated
240V (phase to neutral) with variation of +30% & -40%.
5.3 Rated Voltage However meter should withstand the maximum system
voltage.
5.4 Rated Current Ib -5A and Imax- 10 A

Page 315 of 473

5.5 Power factor range Zero lag – Unity – Zero lead
5.6 Starting current 0.1 % of base current
5.7 Rated Frequency 50Hz +/- 5%
5.8 Accuracy Class 0.5s (IS14697 applies for accuracy requirements)
As per IS 16444 (Part 2)
5.9 Power Consumption
Meter with lowest power consumption shall be preferred.
5.10 Meter constant Imp/ unit (Bidder to specify meter constant)
Meter shall be software calibrated at factory and
5.11 Calibration modification in calibration shall not be possible at site by
any means or external influence.
Test Output Device Separate kWh & kVAh/kVArh Flashing LED visible from the
5.12
front
5.13 Process Technology Surface Mounting Technology or better
Meter shall withstand an insulation test of 4 KV and impulse
5.14 Insulation Level
test at 8 KV
5.15 Influence of supply voltage As per IS 14697
5.16 Short time over current As per IS 14697
Immunity to phase and
5.17 As per IS 14697
earth fault
5.18 Influence of Self Heating As per IS 14697
5.19 Influence of Heating As per IS 14697
a. Meter shall remain immune to electrostatic discharge
(upto and including 35KV), electromagnetic HF field and
fast transient burst.
b. The meter shall be designed in such a way that
Electromagnetic conducted or radiated electromagnetic disturbances as
5.20
compatibility well as electrostatic discharge do not influence the
BSES

meter.
c. Meter shall be type tested for electromagnetic
compatibility.
d. Meter shall comply requirement of IS 14697
Meter shall work within guaranteed accuracy as per IS
14697/ IEC62053-21/ CBIP325 (most stringent standard to
be followed) under and after influence of following :-
a. Current Variation
b. Ambient Temperature variation
c. Voltage variation
d. Frequency variation
e. 10% third harmonic in current
f. Reversed phase sequence
g. Voltage unbalance
Limits of error due to h. Harmonic components in current and voltage circuit
5.21
influence quantities i. DC and even harmonics in AC current circuit
j. Odd harmonics in AC current circuit.
k. Sub harmonics in AC current circuit
l. Continuous (DC) “stray” magnetic induction of 67mT+/-
5%.
m. Continuous (DC) “abnormal” magnetic induction of
0.27T+/-5%.
n. Alternating (AC) “stray’ magnetic induction of 0.5mT+/-
5%
o. Alternating (AC) “abnormal’ magnetic induction of
10mT.

Page 316 of 473

 [Link] magnetic field 0.5 T
[Link] HF fields
[Link] frequency interference
[Link] immunity test
Note: BSES reserves the right to formulate any other test
method to check magnetic immunity/ logging of meter.
Meter with logging provision will be preferred.
Other features Mid night data: The meter should record midnight
Cumulative kWh & kVAh, kVARh lag and kVARh lead
reading for last min 45 days load survey data.
Total Harmonic Distortion: Meter to record harmonic
5.22
components in both current and voltage circuits. And should
be available in on demand display. Meter to record events
in case harmonic component in both V&I if it exceeds
threshold limits (configurable).
i. Default Display (Auto Mode)
ii. LCD test
iii. Meter serial no.
iv. Date
v. Real time
vi. Cumulative kWh
vii. Cumulative Export Active Energy*
viii. Net Active energy*
ix. Cumulative kvarh Q1/Lag
x. Cumulative kvarh Q2/Lead
xi. Cumulative kvarh Q3*
xii. Cumulative kvarh Q4*
BSES

xiii. Cumulative kVAh

xiv. Cumulative Apparent Energy (active export)*
xv. Net Apparent energy*
xvi. Instantaneous load in kW, kVArh & kVA
xvii. TOD MD for kWh and kVAh
Display Sequence for the xviii. Phase wise voltage and current (R, Y, B phases)
5.23 xix. Power factor
parameters
xx. Neutral current
xxi. TOD Total Active Forward Energy Register(Reg
1)
xxii. TOD Total Active Forward Energy Register(Reg
2)
xxiii. TOD Total Active Forward Energy Register(Reg
3)
xxiv. TOD Total Active Forward Energy Register(Reg
4)
xxv. TOD Total Active Forward Energy Register(Reg
5)
xxvi. TOD Total Active Forward Energy Register(Reg
6)
xxvii. TOD Total Active Forward Energy Register(Reg
7)
xxviii. TOD Total Active Forward Energy Register(Reg
8)
xxix. TOD Apparent Forward Energy Register(Reg 1)

Page 317 of 473

 xxx. TOD Apparent Forward Energy Register(Reg 2)
xxxi. TOD Apparent Forward Energy Register(Reg 3)
xxxii. TOD Apparent Forward Energy Register(Reg 4)
xxxiii. TOD Apparent Forward Energy Register(Reg 5)
xxxiv. TOD Apparent Forward Energy Register(Reg 6)
xxxv. TOD Apparent Forward Energy Register(Reg 7)
xxxvi. TOD Apparent Forward Energy Register(Reg 8)
xxxvii. Temperature
xxxviii. Total tamper count
xxxix. Status of communication module
xl. Mode (Net/Forward)
xli. Signal strength in RSSI
i. Error code

Display (On demand)

After using pushbutton the following parameters should be
displayed.
i. LCD test
ii. Meter serial no.
iii. Date
iv. Real Time
v. Cumulative kWh
vi. Cumulative Export Active Energy*
vii. Net Active energy*
viii. Cumulative kvarh Q1/Lag
ix. Cumulative kvarh Q2/Lead
BSES

x. Cumulative kvarh Q3*

xi. Cumulative kvarh Q4*
xii. Cumulative kVAh
xiii. Cumulative Export Apparent Energy*
xiv. Net Apparent energy*
xv. Current MD in kW
xvi. Current MD in kVA
xvii. MD in kVAR
xviii. TOD MD for kW and kVA
xix. TOD MD occurrence for kW and kVA
xx. Instantaneous Power factor
xxi. Instantaneous voltage R phase
xxii. Instantaneous voltage Y phase
xxiii. Instantaneous voltage B phase
xxiv. Instantaneous current R phase
xxv. Instantaneous current Y phase
xxvi. Instantaneous current B phase
xxvii. Last month billing Date
xxviii. Last month billing kWh reading
xxix. Last month billing kVARh reading
xxx. Last month billing kVAh reading
xxxi. Last month billing Maximum Demand in kW
xxxii. Last month billing Maximum Demand in kW
occurrence Date
xxxiii. Last month billing Maximum Demand in kW

Page 318 of 473

 occurrence Time
xxxiv. Last month billing Maximum Demand in kVA
xxxv. Last month billing Maximum Demand in kVA
occurrence Date
xxxvi. Last month billing Maximum Demand in kVA
occurrence Time
xxxvii. THD for both Voltage and Current
xxxviii. Total Active Energy, Apparent Energy
xxxix. Fundamental Reactive Lag and Fundamental
Reactive Lead Energy
xl. High Resolution value (kWh, KVAh)
xli. High resolution Export Active Energy (kWh ,
KVAh)*
xlii. Neutral Current
xliii. Temperature
xliv. Battery status
xlv. PT/CT status
xlvi. Self diagnostic flag
xlvii. Connection check (Phase sequence)
xlviii. Cumulative Tamper count
xlii. Cumulative Power off hours
xliii. Signal strength in RSSI
xlix. Error code
l. Phase association (ok/ Not ok)
* When meter is configured in net metering mode then only
these parameters should appear otherwise these display
parameters should be disable and shall not appear on
BSES

display
Note:
1. The meter display should return to Default Display mode
(mentioned above) if the ‘push button’ is not operated for
more than 6 seconds. Provision for scroll lock by
pressing for 15 sec and sent to normal after 5 minutes.
2. Sequence of display parameter and parameter subject
to change and to be finalized before supply.

6.0 Construction
Material - Opaque and UV stabilized polycarbonate of grade
6.1 Base Body
LEXAN 143/ 943 or Equivalent with V0 inflammability level.
a. Material: Transparent/Opaque and UV stabilized
polycarbonate of grade LEXAN 143/ 943 or Equivalent
with V0 inflammability level.
6.2 Top Cover b. Top cover and base should be Ultrasonically/Chemically
welded.
c. Top cover should be designed so as the internal
components should not be visible.
a. Material - Flame retardant glass filled polycarbonate of
grade 500 R or equivalent.
b. Terminal block shall form Integral part of the meter base
6.3 Terminal Block c. Terminal block shall be capable of passing the tests as
per ISO-75 for a temperature of 135C and pressure of
1.8MPa. The terminals shall be designed so as to ensure
adequate and durable contact such that there is no risk of

Page 319 of 473

 loosening or undue heating.
a. Material - UV stabilized transparent/Opaque
polycarbonate cover of grade LEXAN 143A/943AA or
equivalent.
b. Provision of sealing at two points through sealing screw.
c. The sealing screws shall be held captive in the terminal
cover.
d. The terminal cover shall be extended type with baffle wall
6.4 Terminal cover above the cable entry base wall so that access to the
terminals is not possible (even with thin metallic wire)
without breaking the seal. Terminal cover should have
provision for cable entry from bottom.
e. Diagram of external connections should be embossed on
terminal cover. Sticker is not acceptable.
f. Mechanism shall be provided to record an event with
occurrence and restoration in case of meter enclosure/
terminal cover is opened.
a. Terminals shall be suitable for 6 Sqmm copper wire.
b. Two no’s grub screws per terminal shall be provided
c. Material of terminals, screws and washers should be
brass or tinned copper. Terminals shall be tested for
6.5 Terminals
continuous current of 150 % Imax.
d. Terminals shall be clearly marked for phase / neutral /
outgoing etc.
e. Clearances and creepage shall be as per IS 14697.
a. Polycarbonate meter enclosure and LTCT’s as per
Appendix 5E’ may be provided with meter.
BSES

6.6 Meter Enclosure b. Mechanism shall be provided to record an event with

occurrence and restoration in case of meter enclosure is
opened.
6.7 Ingress Protection IP 51 or better, but without suction in the meter.
Meter should have flashing LED visible from the front to
represent energy recording. Resolution shall be such that
6.8 Output device satisfactory accuracy test can be conducted at the lowest
load in less than 5 minutes and starting current test in less
than 10 minutes.
a. The meter shall have internal real time crystal clock to
set date and time.
6.9 RTC b. Drift in time of this clock shall not be more than
±5minutes/ year at a reference temperature of 27°C.
c. HES will sync RTC at least once a day (configurable).
a. Lithium ion battery with guaranteed shelf life of 10 years
and capacity life of 15 years. Lithium thioyl Chloride
battery will be preferred. In case battery removal or total
discharge same should not affect the working & memory
6.10 Battery of the meter.
b. Meter should have two separate battery.
c. One for RTC and one for back up
d. Incase battery voltage reduced below threshold value
then need to generate alert
Non volatile memory independent of battery backup,
6.11 Memory memory should be retained up to 10 year without any
auxiliary power.

Page 320 of 473

 Meter shall have self diagnostic for the following
a. Date and RTC.
b. Battery.
6.12 Self Diagnostic feature
c. Non volatile memory.
d. Display
e. Status of Communication card
Meter shall have an optical port with a metal ring to hold
6.13 Optical port magnet of probe. Optical port shall comply with hardware
specifications provided in IEC-62056-21.
a. Meter should have the provision for 01 no’s modular and
pluggable communication module compatible with
Cellular (4G).
b. Meter shall have mechanism to log communication
module removal and insert as an event in its memory
with date and time stamp.
6.14 Communication c. Meter shall have separate indications on display/ for
remote and local communication.
d. Communication module shall held in a casing which can
be directly plugged in the meter. Sealing screw shall be
provided.
e. Communication module shall be configurable for IPV6
with backward compatibility with IPV4
a. In Last Gasp endpoint shall send the power outage and
power restoration notification with Time Stamp. In case
of power failure meter communication module shall not
6.15 First breath and last gasp draw power from the backup battery.
b. For the purpose of sending the Last Gasp,
BSES

communication module shall have proper power backup

(like a super capacitor).
a. Sealing should be in accordance with IS and CEA
metering regulations with latest amendments.
b. Sealing arrangement shall be such that sealed parts
shall not be opened without breaking the seal or sealed
part itself. There should be clear evidence of the
breaking in case sealed parts shall be opened without
breaking the seal.
c. Approval shall be taken from purchaser for location of
seals and number of seals.
Meter Sealing d. Record of all seals shall be forwarded to purchaser with
6.15
Arrangement each lot.
e. Meter Body : 1 plastic seal and Hologram seal as per
BSES specs & 1 seal of meter manufacturer
f. Meter Terminal cover : 2 Plastic seal as per BSES
specs
g. Meter Box : 2 plastic seal as per BSES Specifications
(All above seals provided by AMISP as per the serial no
provided by BSES )
h. Record of all seals shall be forwarded to purchaser with
each lot.
Record of all seals shall be forwarded to purchaser with
6.16.2 Seal record
each lot.
Insulation A meter shall withstand an insulation test of 4 KV and
6.16.3
impulse test at 8 KV

Page 321 of 473

 a. Meter should have clearly visible, indelible and distinctly
marked name plate in accordance with IS 16444 (Part
2) & clause no. 10.0 of this specification.
b. All markings and details shall be printed by laser only.
6.17 Name Plate and marking
c. “DT Meter” should be BOLDLY marked on name plate.
Design of Name plate will be approved by BSES.
d. Name plate shall have QR code having meter
information like meter [Link]., month and year of
manufacturing, type of meter, OEM, Rating etc
e. Paper stickers are not allowed for name plate.
The terminal block and Meter case shall have safety
Resistance against heat against the spread of fire. They shall not be ignited by
6.18
and fire thermal overload of live parts in contact with them as per
IS 14697.
a. 10.5 Years from the date of dispatch or 10 Year from
date of commissioning, whichever is earlier
6.19 Guarantee b. The meters which are found defective/inoperative within
the guarantee period shall be replaced as per meter
service level agreement.

7.0 Functional Requirement

7.1 Meter category Smart meter comply with D4 category of IS 15959 (Part 3).
It should be possible to configure meters in following modes of
metering:
a. Forwarded Only: In this mode any export active energy shall
be treated as import energy and shall be recorded in forward
BSES

only register. Apparent energy calculation in this mode shall be

as per clause no. 7.3.
7.2 Mode of metering b. Bidirectional: Both Import and export energy recording shall be
applicable in this mode of metering and relevant registers shall
be updated.
c. Any change in metering mode shall be logged in events with
date and time stamp.
d. Default mode of metering shall be forwarded only until
specified in tender requirement otherwise.
7.3 kVAh Calculation Lag+lead
Block / sliding window with default demand integration period of
1800 s configurable to 900 s as per requirement. Meter should be
configurable for block/ sliding window at the time of manufacturing.
7.4 MD calculation This change should not be possible in the field. Extended register
shall be used for MD recording.
It should be possible to reset MD automatically at the defined date
(or period) or through CMRI
a. Meter shall be capable of doing TOD metering in minimum 4
tariff rate registers programmable for minimum 8 time zones
and 4 seasonal profiles.
b. TOU metering shall be implemented by the activity colander
7.5 TOU Metering method of IS 15959 Part 1 clause 9/ DLMS UA-1000-1
c. Special Day table shall be defined as per IEC/ DLMS UA-
1000-1
d. Default TOU programming shall be as per latest DERC
guidelines. Prior approval shall also be taken from BSES for

Page 322 of 473

 the same.
e. Tariff rate registers shall be as follow
R1: Rate register for Peak
R2: Rate register for Normal
R3: Rate Register for Off Peak
All the parameters mentioned in table ‘14’ of IS 15959 (Part 3)
along with following additional parameters shall be supported by
meter.
a. Neutral Current (IN)
b. % TDH in R phase Voltage
c. % THD in Y Phase Voltage
d. % THD in B Phase Voltage
Instantaneous
7.6 e. % THD in R phase Current
Parameters
f. % THD in Y Phase Current
g. % THD in B Phase Current
h. Temperature
i. Signal Strength in RSSI
j. Voltage angles
Method of Measurement for harmonic parameters at sl no. ‘b’ to ‘g’
shall confirm to the IEEE 519, 2014.
7.6.1 Association Rights As per Clause 17.1 of IS 15959 (Part 3).
a. Billing parameters shall be generated at the end of each billing
cycle and stored in memory as per provisions provided in
clause no. 20 of IS 15959 (Part 3).
b. 12 no’s billing cycle parameters shall be remain in meter
memory along with current cycle parameters and shall be
7.7 Billing data available for reading as well as profile and or ‘by entry’ for
BSES

selective access.
c. All the parameters mentioned in table ‘17’ of IS 15959 (Part 3)
shall be supported by meter.
d. Cumulative power interruption count in all monthly history data
e. Monthly Power off duration in all history data.
7.7.1 Association Rights As per clause 20 of IS 15959 (Part 3).
Support for selective access shall be provided for billing
7.7.2 Selective access
parameters as per clause no 11.3 of IS 15959 (part 1).
Billing period
7.7.3 00:00 Hrs of Ist of every month
reset/ MD reset
Billing period reset
7.7.4 As per clause 10 of IS 15959 (Part 1)
mechanism
Cumulative billing period counter since installation and available
Billing period
7.7.5 billing periods shall be provided as per clause 11.2 of IS 15959
counter
(Part 1).
a. Load survey parameters shall be measured and recorded at
the end of each profile capture period for last 45 Power ON
days for 30min IP.
b. All the parameters mentioned in table ‘15’ of IS 15959 (Part 3)
along with following additional parameters shall be supported
7.8 Load survey Data by meter:
% THD in R phase Voltage
% THD in Y Phase Voltage
% THD in B Phase Voltage
% THD in R phase Current
% THD in Y Phase Current

Page 323 of 473

 % THD in B Phase Current
Phase wise Voltage and Current (Line, Active, Reactive) with
instant and average value.
All three phase active, reactive (lag and lead) and apparent
power and energy.
Power-off time integration period
Neutral Current
Average Signal Strength
Profile capture
7.8.1 Default 1800 s programmable to 900 s.
period
Support for selective access shall be provided for billing
7.8.2 Selective Access
parameters as per clause no 11.3 of IS 15959 (part 1).
7.8.3` Association Rights As per clause no.18 of IS 15959 (Part 3)
Daily load profile parameters shall be measured and recorded at
each midnight i.e. 00:00 hrs for last 45 Power ON days.
7.9 Daily load profile
All the parameters mentioned in table ‘3’ of IS 15959 (Part 3) shall
be supported by meter as Daily load profile parameters.
7.9.1 Association Rights As per clause no. 13 of IS 15959 (Part 3)
General Purpose Following parameters shall be provided in Non Volatile memory
7.10
Parameters (NVM) of the meter as per clause 16 of IS 15959 (Part 3).
7.10.1 Name Plate Detail As per Table ’25’ of IS 15959 (Part 3).
7.10.2 Association Rights As per clause no. 26.1 of IS 15959 (Part 3)
These parameters can be programmed remotely by HES and
locally by HHU via proper access writes. Every transaction shall be
logged in non volatile memory of the meter with date and time
stamp.
Programmable
7.10.3 Programming of any of the parameters shall increment the
parameters
‘Cumulative programmable count’ value.
BSES

All the parameters mentioned in table ‘26’ of IS 15959 (Part 3)

shall be supported by meters with following additional parameters
as mentioned in specification
7.10.4 Association rights As per Clause no. 26.2 of IS 15959 (Part 3).
a. Smart meter is able to automatically notify data, event, and
messages to a destination client system in an unsolicited
manner (without a request from a client) as per clause no 6 of
IS 15959 (Part 2).
b. Randomization: Data from different endpoints shall be pushed
intelligently on the network in order to avoid excessive traffic
on the network for example in case all the endpoints will push
load survey data simultaneously, then it may result in network
choking or inefficient performance. Therefore with the help of
intelligent techniques such field scenarios shall be handled
7.11 Push Services effectively.
c. It shall also be possible to configure push services for all
profiles i.e instantaneous, billing, load survey, daily energy and
events. Bidder should explain its capability to configure push
services. However following push services shall be available
by default.
i. Load survey profile data at after every 4 hours
configurable to any predefined interval.
ii. Mid night data at 00:00 hrs of every day.
iii. Billing profile data on occurrence of billing.
7.11.1
Periodic push a. Meter shall be able to push instantaneous parameters to HES
(Smart meter to at predefined intervals. Parameters required for push shall be

Page 324 of 473

 HES) intimated during detailed engineering in the vent of order.
b. Other attributes as per IS 15959 (Part 3) i.e. Send Destination,
Communication window, Randomization time interval, number
of retries and repeat delay shall be decided in the event of
manufacturing.
a. Meter is able to report HES, the status change of any of the
identified events mapped in to event status word (ESW) of size
128 bits by pushing following objects to HES.
i. Device ID
ii. Push Setup ID
iii. Real time clock- Date and Time
Event Push iv. Event Status Word 1 (ESW 1).
7.11.2 (Smart meter to b. Each of the bits in ESW shall reflect the current state of the
HES) event and are mapped against each of the identified events.
c. An event status word filter (ESWF) of 128 bit shall also be
provided to configure events for event push. Events which are
supported in meter shall only be configured for event push. Bit
value 1 in ESWF shall indicate that the event is supported and
value 0 indicates that event is not supported for event push.
Position of the event bit in ESWF shall be same as in ESW.
Event status Bit
7.11.3 As Per IS 15959 (Part 3)
mapping
a. Smart meter shall support remote firmware upgrade feature for
meter firmware without loss of any data and metrology for a
part or complete firmware of meter.
b. Firmware upgrade shall use the Image transfer classes and
mechanisms specified in IEC62056-6-2 and IEC62056-5-3.
BSES

c. Broad cast facility shall be supported in HES for

simultaneously upgrading the firmware of a group of meters
installed in field.
d. Firmware upgrade feature shall be provided with proper
security. The design shall take into account field scenarios
such as power failure during F/W upgrade.
e. Once the firmware is upgraded successfully, meter shall send
an acknowledgment to HES. It shall also log it as an event in
7.12 Firmware upgrade
its memory with date and time stamping.
f. Meter shall support capability to self register the meter with
new firmware.
g. The execution time of the change of the firmware within the
meter should be below 1 minute
h. Meter shall support auto resume firmware upgrade in case file
transfer stops due to any reason like power supply failure.
There shall not be any corruption in data during transfer of
firmware.
i. In case of wrong firmware file, meter shall be able to identify
the same and suspend FOTA activity
j. Meter shall support NIC FOTA through HES
k. NIC firmware file size should be less than meter firmware file
Meter shall support connection less messaging services of DLMS
Support for to support broadcast messages for a group of meters for following
7.13 broadcast actions:
message a. Gap reconciliations.
b. Firmware upgrade.

Page 325 of 473

 c. On demand readings
d. Updating of Programmable parameters
a. Advanced security outlined in clause 7.1.2 of IS 15959 (Part 1)
shall be provided.
b. Reading and writing data into meter memory via optical and
remote communication port shall be through DLMS security
keys only.
c. Bidder shall ensure to safeguard high security keys used for
configuring parameters into meter.
d. Once the meter memory is locked during manufacturing
process, only parameters mentioned in IS 15959 shall be
7.14 Security configurable even in factory. It should not be possible to
configure any other parameters.
e. Please note that there shall be no other mechanism/ method to
interface with meter through optical and remote communication
port except mentioned in IS 15959, even for manufacturer.
f. It should not be possible to change data stored in meter
memory even after accessing meter memory physically. In
case of any change in memory data, a flag/alert shall be
generated. Flag/Alert shall be indicated over display and in
remote communication also
Encryption for
7.15 data As per clause 7.1 of IS 15959 (Part 2)
communication
Encryption/
7.151 Authentication for As per clause 7.2 of IS 15959 (Part 2)
data transport BSES

Key requirement
7.15.2 As per clause 7.3 of IS 15959 (Part 2)
and handling
a. Proper security at end points as well as network level shall be
present to prevent unauthorized hacking of the end points or
the network itself.
b. The meter password is required to open a session between
NIC and meter and is required to gain clearance from the
meter to perform requested operation.
7.15.3 NIC Security c. If clearance not gains, the meter locks out local communication
for 1 minute. The meter maintain counter for monitoring of
unsuccessful attempts of performing meter operations and
alerts to HES. The counter is incremented each time a
password clearance operation fails.
d. Up to 3 no’s unsuccessful attempts are allowed, after which
the port is locked out until authenticated from system
administrator.
Meter shall support TCP-UDP/ IP communication profile for smart
IP communication meter to HES. Please refer clause 8 of IS 15959 (Part 3).
7.15.4
profile support Communication module shall be configurable for IPV6 with
backward compatibility with IPV4
Meter shall detect and log any exceptional/ fraud/ tamper
Event and tamper conditions in its memory as an event. In addition to this all
7.16
detection transactions and control shall also be recorded as an event in
meter memory. Each event type shall be identified by an event ID.
Each event shall be available to download as per following
7.17 Association Rights association rights.
a. Public Client: No access
Page 326 of 473
 b. Meter Reader: Read only
c. Utility Settings: Read only
Push Services: Read Only for identified events as per ESWF
Meter shall be able to log events in following compartments
a. Voltage Related Events
b. Current Related Events
Compartments of c. Power Related Events
7.18
events d. Others Events
e. Non Roll Over Events
f. Transaction related events
g. Control Events
a. Occurrence and Restoration of Voltage Related, current
related, power related and other events shall be logged in
meter memory as per IS 15959 (Part 3). Please refer Appendix
5A for description of events, Event ID, Logics of events and
threshold values of events.
b. Threshold values shall be factory programmable.
Compartments of
c. Selective access shall be provided as per clause 11.3 of IS
events
7.18.1 15959 (Part 1).
Parameter
Snapshot d. For each of the events a certain list of parameters shall be
captured as per clause 'a'
e. For each occurrence event captured, the cumulative tamper
count shall be incremented.
f. Meter shall capture all the parameters mentioned in table ‘24’
of IS 15959 (part 3) when event occurrence and restoration is
logged
The meter shall log minimum 200 tamper events (ensuring at least
BSES

7.18.2 Event Logging

20 events for each tamper).
Appropriate Indications/Icons for all tampers should appear on the
7.18.3 Tamper Indication
meter display either continuously or in auto display mode.
Phasor Meter shall support parameters required to develop phasors of
7.18.4
Representation current and voltage at HES.
Harmonic All the energies measured and recorded with and without
7.19
Energies harmonics.
Additional feature a) Meter should measure Voltage between Earth and Neutral and
(Mandatory) for the same have an additional terminal which can be connected
7.20 to earth potential. The VNE can be part of inst parameter group.
b) When ever meter experiences a sudden change in load i.e.
sudden reduction by 30%, it should log last 10 such events.
Digital Output a) Meter should have 2 no. of Digital Output (DO) ports to remotely
(DO), connect/ disconnect the load via suitable mechanism.
7.21 Digital Input (DI) , b) Meter should have 2 no. of Digital Input (DI) and 2 no. of AI
Analog ports for measurement of various sensor parameters like ambient
Input (AI) temperature, oil temperature, oil level etc.

8.0 Meter Display

8.1 LCD Type STN Liquid crystal with backlit

a. Minimum 120 Degree.
b. The display visibility should be sufficient to read the
Meter mounted at height of 0.5 m as well as at the
8.2 Viewing angle height of 2 m.
8.3 Size of LCD Minimum 10X6mm PIN Type

Page 327 of 473

 8.4 LCD Digits Total 10 digits
8.5 LCD language English
a. Auto Mode
b. Manual Mode
8.6 Display modes c. Sub active mode
Display list shall be finalized during detailed engineering
in the event of order.
Appropriate indications/flags for all tampers and self
8.7 Display indications diagnostic features should be provided.

9.0 Data and communication protocol/ HES/Integrations/ Software

a. Meter should comply Indian companion of data exchange

and tariff control specification IS 15959 (Part 2).
b. In case of additional requirement from IS 15959 (part 2),
they shall be as per DLMS standards/ IEC DLMS protocols
suite (62056).
Data Exchange
9.1 c. Bidder shall explain in detail the additional parameters/
protocol
services/ methods used in meters from IS 15959 (part 2)
and its reference to DLMS books/ IEC.
d. Prior to manufacturing of meters bidder shall provide a
detailed specification explaining all parameters/ services/
methods used in meter in addition to IS 15959 (Part 3).
a. Bidder shall work with BSES IT team/ BSES designated
system integrator to integrate its meter with BSES HES
system.
9.2 Integration with HES
b. Bidder shall prepare detailed documents as mentioned
BSES

in above clause and submit it for BSES approval and

integration with HES.
Base computer Licensed Software with the following features should be
9.3
software supplied for free to download meter through optical port.
9.3.1 Operating System BCS should be compatible for latest Windows operating system.
System shall be password protected where user can login only if
login ID is provided by administrator. BCS shall have rights
9.3.2 Security
management system so that access rights can be provided as
per requirement to maintain security.
BCS shall maintain master database according to desired area,
9.3.3 Database
location, and region etc.
a. BCS shall have option of user defined report generation in
format of Excel, Word and CSV, XML, PDF etc.
b. BCS shall have capability to export data in ASCII, CSV and
9.3.4 Reporting XML format at desired location so that the same could be
integrated with our billing data for processing.
c. All the data available in the meter shall be convertible to
user defined ASCII, CSV and XML file format.
BCS and communication ports should support data transfer rate
9.3.5 Data transfer rate
of 9600 bps (minimum).
a. The manufacturer has to provide Mobile App for
downloading all the data stored in meter memory through
Hand Held Unit optical port.
9.4
Software b. Mobile App should have option for selection of parameters
to be downloaded from meter
c. Meter data consisting of all parameters and complete load

Page 328 of 473

 survey for all parameters shall be read by HHU (Mobile
App) and data transferred to HES in minimum possible time
(not more than 5 minutes).
d. Mobile App should have option to initiate configuration and
firmware upgrade actions locally for non-communicated
meters as per the schedule initiated from back end
applications (HES/MDMS).
e. Mobile App should ensure the meter security keys are
stored in encrypted form and not accessible to users.
Manufacture shall impart training to BSES personnel for usage
9.5 Training
of software

10.0 Name Plate

Meter Serial number shall be of 10 digits. Serial number shall be printed in black colour.
10.1
Embossing is not acceptable.
Size of the digit shall be minimum 5 X 3mm. Details shall be printed by laser printing
10.2
preferably.
10.3 Bar code shall be printed below the serial number
10.4 BIS registration mark (ISI mark)
10.5 ‘BSES’ insignia shall be printed above LCD display.
10.6 BSES PO No. & date and Property of BSES
10.7 Manufacturers name and country of origin
10.8 Model type / number of meter
10.9 Month and Year of manufacturing
10.10 Reference voltage / current rating
The number of phases and the number of wires for which the meter is suitable.
10.11 BSES

Graphical symbol as per IS 12032 can be used.

10.12 Meter constant Impulse/kWh Impulse/kVAh/kVArh
10.13 Class index of meter
10.14 Reference frequency
10.15 Warranty period
Name plate of NIC
a. Serial no of NIC along/ IMEI no/MAC address with bar code
b. Name of purchaser’s
10.16
c. Communication technology with carrier frequency
d. Manufacturing year and month.
e. Warranty period.

11.0 Component Specification

The Meters should be with the

To meet accuracy
11.1 Current Transformers current transformers as measuring
requirement
elements.
The Measurement or computing
Analog Devices, Cyrus
Measurement or chips used in the Meter should be
11.2 Logic, Atmel, Phillips,
computing chips with the Surface mount type along
SAMES ,NEC,TEXAS
with the ASICs.
The memory chips should not be Atmel, National
affected by the external parameters Semiconductors, Texas
11.3 Memory chips
like sparking, high voltage spikes or Instruments, Phillips,
electrostatic discharges. ST, Hitachi, Compiled
11.4 Display modules a. The display modules should be Hongkong: Genda

Page 329 of 473

 well protected from the external Singapore: Bonafied
UV radiations. technologies
b. The construction of the modules Korea: Advantek
should be such that the China: Success
displayed quantity should not Japan: Hitachi, Sony
disturbed with the life of display
(PIN Type).
c. It should be STN type industrial
grade with extended
temperature range min 70 ºC.
The mechanical construction of the USA: National
port should facilitate the data Semiconductors, HP
11.5 Optical port
transfer. Communication shall not Holland/ Korea: Phillips
disturbed by external light. Japan: Hitachi, Ligitek
The power supply should be with
the capabilities as per the relevant
standards. The power supply unit of
the meter should not be affected in
11.6 Power Supply SMPS Type
case the maximum voltage of the
system appears to the terminals due
to faults or due to wrong
connections.
The active & passive components
should be of the surface mount type USA: National
& are to be handled & soldered by Semiconductors, Atmel,
the state of art assembly processes. Phillips, Texas
Electronic The PTH components should be Instruments.
11.7
components positioned such a way that the leads
BSES

Japan: Hitachi, Oki,

of components should not be under AVX or Ricoh
stress and not touching the internal Korea: Samsung
wires.
LED Everlight, Agillent
a) The internal electrical
components should be of electrolytic
copper & should be protected from
corrosion, rust etc.
11.8 Mechanical parts
b) The other mechanical
components should be protected
from rust, corrosion etc. by suitable
plating/painting methods.
Lithium with guaranteed life of 15 Texcell, SAFT, Varta,
11.9 Battery
years Tedirun, Sanyo
USA: Philips, Dallas
RTC & Micro The accuracy of RTC shall be as Atmel, Motorola,
11.10
controller per relevant IEC / IS standards Microchip, TEXAS,
Japan: NEC, Oki
Glass Epoxy, fire resistance grade
11.11 P.C.B. FR4, with minimum thickness 1.6 (BBT test is must)
mm
a. The components used by
manufacturer shall have
11.12 Note “Minimum Life” more than the 10
years.
b. Incase vendor want to use other

Page 330 of 473

 make components; same shall
be approved by BSES before
use.
c. Even for existing supplier – fresh
approval is needed for all
deviations.
d. Manufacturer should have
complete tracking of material
used in meter. BSES reserve
the right to carry out audit of
inventory/ manufacturing
process at manufacturer’s works
and sub vendor’s work.

12.0 Quality Assurance, Inspection and Testing

Vendor's Quality
12.1 To be submitted for Purchaser's approval.
Plan (QP)
Sampling Method for quality checks shall be as per relevant IS/
12.2 Sampling Method IEC/ CBIP guidelines and Purchaser's prior approval shall be
taken for the same.
Inspection Hold-
12.3 To be mutually identified, agreed and approved in Quality Plan.
Points
a. The meter shall be of type tested quality including all tests
specified in this specification which are beyond IS / IEC or
CBIP.
b. Type test conducted from CPRI/ ERDA/ or any other lab
specified by BIS/ CEA for smart meter testing will be
BSES

treated as valid.
12.4 Type Tests
c. Type test certificate should be submitted along with offer for
scrutiny.
d. Any other component supplied in addition to meter shall
also be type tested as per IS /IEC if applicable.
e. Complete type test as per IS 16444 (Part 2) shall be carried
out on sample selected from BSES lot.
12.5 Routine tests All test marked “R” as per table 20 of IS 14697.
a. All tests marked “A” as per IS 14697.
b. Smart meter functional tests as per IS 16444 (Part 2).
c. Test for data exchange protocol as per IS 16444 (part 2).
d. Test for Smart meter communicability as per clause no.
10.6 of IS 16444 (Part 2).
e. All the routine and acceptance tests shall be carried out as
per relevant standards.
f. Following tests in addition to IS shall be conducted during
12.6 Acceptance Tests lot inspection.
I) Dimensional and drawing verification.
II) Display parameters/ sequence.
III) Data Downloading from CMRI and PC.
IV) Tamper/ fraud detection/logging features as per
approved documents. Tamper conditions will be
simulated at varying load up to Imax. Accuracy will
also be checked during tamper simulation.
V) Burn in chamber test.

Page 331 of 473

 VI) Component verifications.
g. Purchaser reserves the right to formulate any other test
method to verify guaranteed parameters of Meter.
ESD and Magnetic ESD and magnetic interference test will be conducted at Samir
12.7
Interference test lab, Chennai or CPRI.
a. Purchaser reserves the right to inspect /witness all tests on
the meters at Seller’s works at any time, prior to dispatch,
to verify compliance with the specification/ standards.
b. Manufacturer should have all the facilities/ equipments to
conduct all the acceptance tests as per clause 14.3
12.8 Inspection
relevant standards and tampers logics as per approved
GTP. All the equipments including tamper logs kits/ jigs
should be calibrated.
c. In-process and / or final inspection call intimation shall be
given in advance to purchaser.
a. The internal potential links should be in closed position or
link less meters will be preferred and there shall not be any
external link.
b. Deliverable with Meters.
i. Hard copies for Routine test certificates with each
meter till alternate is provided by vendor and approved
BSES.
ii. Terminal cover should be fixed on the meter before
dispatch.
iii. Report of seal & initial reading record. (soft copy as
per BSES format)
c. Box number, meter serial number, type, rating should be
BSES

mentioned on cases / cartons.

d. Meters shall be suitably packed with environmental friendly
material in order to avoid damage or disturbance during
transit or handling and to prevent in grace of moisture and
General dust. Also refer CEA Metering Regulation 2006.
12.8
Requirements e. In case battery removal/ total discharge same should not
affect the working & memory of the meter.
f. The bidder shall maintain a web site where routine test
results of all meter supplied against these tender will be
maintained and will be accessible to buyer/ buyer
representative.
g. The supplier shall give 15 day advanced intimation to
enable BSES to depute representative for lot inspection.
h. Vendor shall ensure that patch required for HHU/CMRI
shall be provided within 4 weeks. Vendor shall also ensure
to deliver solution to meet DERC mandate within mutually
agreed timeline.
i. Delivery of software for reading through HHU/CMRI before
meter delivery is required.
j. For any false events recorded in meter, vendor shall depute
their representative for field visit within one week and
provide the root cause analysis in 4 weeks time.

13.0 Packing, Marking, Shipping, Handling and Storage

13.1 Packing a. Each meter must be packed, together with its terminal

Page 332 of 473

 cover, in a separate environmental friendly cardboard box,
which can be opened and re-closed without needing
adhesives.
b. Up to 4 to 5 three-phase meters must be packed together
with their terminal covers in a group cardboard box, which
can be opened and re-closed without needing adhesives.
c. The box shall prevent, as much as possible, penetration of
dust during long storage periods. The box must be
designed for multiple use and be robust, with wall
thickness of at least 4 mm.
d. Maximum weight of a group meter box shall not be more
than 25 Kg.
e. The packaging will protect the meters against shock and
vibration, preventing damage due to the road conditions
during transport and distribution in the field. The electrical
and mechanical properties shall not be affected by these
disturbances.
f. For shipping the boxed meters will be close packed by
stockpiles of suitable quantities on pallets. The meters
numbers sequence (without partition) shall be kept in each
pallet. A pallet will be protected against moisture by a
polyethylene hood, covered with a cardboard cover (hood),
and fixed onto the pallet by parallel polypropylene bands,
using protection angle bars at the corners. The hood shall
be marked – on the front (wide side), on the narrow side
and on the top as per clause 13.3.
g. Visual indications (stickers) shall be attached to the
cardboard hood of several pallets in each container/
BSES

transport truck, to warn of possible rough handling during

shipment, transport and storage.
Packing for
Robust wooden non returnable packing case with all the above
13.2 accessories and
protection & identification Label.
spares
On each group box and pallet, following details are required
both on front (wide side) and top:
a. BSES logo.
b. Meter serial number range along with bar code.
c. Unique number of box/ pallet.
d. Purchaser’s name
e. PO number (along with SAP item code, if any) & date with
bar code
f. Equipment Tag no. (if any)
13.3 Marking
g. Destination
h. Manufacturer / Supplier’s name
i. Address of Manufacturer / Supplier / it’s agent
j. Type , rating and other description of equipment
k. Country of origin
l. Month & year of Manufacturing
m. Case measurements
n. Gross and net weights in kilograms
o. All necessary slinging and stacking instructions
13.4 Test reports Routine test report to be provided with each meter
13.5 Shipping The seller shall be responsible for all transit damage due to

Page 333 of 473

 improper packing.
Manufacturer instruction shall be followed. Detail handling &
Handling and
13.6 storage instruction sheet /manual to be furnished before
Storage
commencement of supply.

14.0 Deviations

a. Deviations from this specification can· be acceptable, only where the

Seller has listed in his quotation the requirements he cannot, or does
not, wish to comply with and which deviations the Buyer has agreed
to in writing, before any order is placed.
14.1 Deviations
b. In the absence of any list of deviations from the Seller, it will be
assumed by the Buyer that the Seller complies with the Specification
fully.
c. Refer Annex C for deviation

15.0 Drawing Submission

Drawing submission shall be as per the matrix given below. All documents/ drawing shall be
provided on A4 sheet in box file with separators for each section. Language of the documents
shall be English only. Deficient/ improper document/ drawing submission may liable for rejection
SL Detail of Document Bid Approval Pre Dispatch
1 Guaranteed Technical particulars (GTP) Required Required
2 Deviation Sheet, if any Required Required
3 Tamper Sheet Required Required
4 Display Parameters Required Required
GA / cross sectional drawing of Meter
5 BSES

Required Required
showing all the views / sections
Detail of network interface i.e. pin out,
6 standard, voltage level etc and its integration Required Required
requirement.
Samples of each type and rating offered
7 along with box (Highest rating offered) and 2 no's 1 no's
communication.
Any software and accessories required for
8 Required Required
installation/ operation of meter
Manufacturer's quality assurance plan and
9 Required
certification for quality standards
Type Test reports of offered model/ type/
10 Required
rating
11 BIS certificate Required
Complete product catalogue and user
12 Required
manual.
13 Customer Reference List Required
14 Recommended list of spare and accessories Required
Specification documents containing all
15 parameters, Services, Methods in addition to Required
companion specification of IS 15959 (part 2).
16 Program for production and testing (A) Required Required
17 Makes of components Required Required
Detailed installation and commissioning
18 Required Required
instructions
19 As Built Drawing Required Required
20 Operation and maintenance Instruction as Required Required

Page 334 of 473

 well as trouble shooting charts/ manuals
Inspection and test reports, carried out in
21 Required
manufacturer’s works
22 Routine Test certificates Required
23 Test certificates of all bought out items Required
24 Meter Seal data Required
Mapping of meter serial no to Communication
25 Required
card.
Other documents:
a. Completely filled-in Technical
Parameters
b. General arrangement drawing of the
meter
c. Rating plate
26 d. Terminal Block dimensional drawing Required Required
e. Mounting arrangement drawings
f. Meter box drawing and dimensions
g. Display parameter
h. PIN configuration of Optical to RJ11
connector
i. Manual and SOP/DWI for operation

16.0 Delivery

Dispatch of Material: Vendor shall dispatch the material, only

after the Routine Tests/Final Acceptance Tests (FAT) of the
16.1 Delivery
material witnessed/waived by the Purchaser, and after receiving
BSES

written Material Dispatch Clearance (MDC) from the Purchaser.

APPENDIX 5A- GUARANTEED TECHNICAL PARTICULARS

Bidder shall furnish the GTP format with all details against each clause of this specification.
Bidder shall not change the format of GTP or clause description.
Bidder to submit duly filled GTP in hard copy format with company seal.
Clause No. Clause Description Manufacturer’s Reply
1
2
3
4
5

Bidder / Vendor seal / signature ---------------------------

Name of the bidder

Address of the bidder
Name of contact person
Telephone number and email id

APPENDIX 5B- RECOMMENDED ACCESSORIES / SPARES

SL Description of spare part Unit Quantity
1 No
2 No

Page 335 of 473

 SL Description of spare part Unit Quantity
3

APPENDIX 5C- Deviation Sheet

Clause No. Clause Description Deviation Details Manufacturer’s Reply
1
2
3
4
5

APPENDIX 5D- TAMPER AND FRAUD DETECTION/ EVENTS

1. Voltage Related Events:

Logic Expression/ Persistence
Description of
Logic Of Event Threshold values Time
event
(Configurable) (Configurable)
R Phase
Voltage Missing
(Occurrence/
Absence of potential on any
Restoration)
phase should be logged.
Y Phase Occurrence: If Vpn<10% Occurrence: 5
Restoration of normal supply
Voltage Missing Vref and Ip>10% Ib Min
shall also be recorded. The
(Occurrence/ Restoration: If Vpn>=10% Restoration: 5
threshold value of voltage
Restoration) Vref and Ip>10% Ib Min
should be programmable at
B Phase
factory end
Voltage Missing BSES

(Occurrence/
Restoration)
Occurrence: If Vpn>10% Occurrence: 5
Over Voltage Meter should log high voltage
Vref Min
(occurrence/ event if voltage in any phase is
Restoration: If Vpn<=10% Restoration: 5
restoration) above a threshold value.
Vref Min
Meter should log low voltage
Occurrence: If Vpn<75% Occurrence: 5
Low Voltage event if voltage in any phase is
Vref Min
(occurrence/ below a threshold value.
Restoration: If Vpn<=75% Restoration: 5
Restoration) Threshold value if factory
Vref Min
programmable.
Meter should log voltage
imbalance event when the
Voltage Occurrence: If Vmax- Occurrence: 5
difference between minimum
Unbalance Vmin>30% Vref Min
and maximum phase voltage is
(Occurrence/ Restoration: If Vmax- Restoration: 5
more than a threshold value.
Restoration) Vmin<=30% Vref Min
Threshold value should be
factory programmable.
R Phase high
Meter should log occurrence of
Voltage
high voltage harmonic event
Harmonics Occurrence: If % THD in Occurrence: 5
when % THD in voltage of
Y Phase high Vpn>5% of fundamental. Min
phase will be more than
Voltage Restoration: If % THD in Restoration: 5
threshold value. Threshold
Harmonics Vpn<5% of fundamental. Min
value should be factory
B Phase high
programmable.
Voltage

Page 336 of 473

Harmonics
2. Current Related Events:
Current
Reverse/ R
Phase Current
Reverse
(occurrence/ Meter should log the event of
Restoration) reversal of C.C polarity.
Y Phase Meter should register energy Occurrence: If Ip = -ve Occurrence:
Current consumed correctly with any direction 5 Min
Reverse one, two or all three current Restoration: If Ip=+ve Restoration:
(occurrence/ coils reversed. This event shall direction 5 Min
Restoration) not be valid in bidirectional
B Phase mode of metering.
Current
Reverse
(occurrence/
Restoration)
R Phase
Current Open
(Occurrence/
Restoration) Occurrence :Vector
Y Phase Meter should log the event of Sum(IR+IY+IB+IN)>20% Ib and Occurrence:
Current Open current coil open. Threshold I<10% Ib 5 Min
(Occurrence/ value of current should be Restoration : Vector Restoration:
Restoration) programmable at factory end. Sum(IR+IY+IB+IN)< 20% Ib and 5 Min
B Phase I>5% Ib
Current Open
BSES

(Occurrence/
Restoration)
Current
Unbalance
(Occurrence/
Restoration)
Meter should log the event of
Occurrence : Vector
current coil shorting/bypass.
Current Bypass Sum(IR+IY+IB+IN)>20% Ib and
Threshold value of current
(Occurrence/ I (any Phase) >5% Ib
should be programmable at
Restoration Restoration : Vector
factory end and also
Sum(IR+IY+IB+IN)>5% Ib
configurable through HES.
If the current in any phase Occurrence:
Over current
exceeds the specified threshold Occurrence: If Ip>Imax 5 Min
(occurrence/
current, meter should log over Restoration: If Ip<=Imax Restoration:
restoration)
current event. 5 Min
R Phase high
Current
Meter should log occurrence of
Harmonics
high voltage harmonic event Occurrence: If % THD in Occurrence:
R Phase high
when % THD in voltage of IP>5% of fundamental. 5 Min
Current
phase will be more than Restoration: If % THD in IP Restoration:
Harmonics
threshold value. Threshold <5% of fundamental. 5 Min
R Phase high
value should be factory
Current
Harmonics
3. Power Related Events:

Page 337 of 473

 Meter shall detect power OFF if
all phase voltages are absent.
Power OFF
This event shall be recorded at
(occurrence/
the time of each power OFF. At
restoration)
the same time power ON event
shall be recorded.
If meter micro detect power off
Abnormal whereas phase voltage is Occurrence: If voltages at
Power Off present than abnormal power meter power supply<10%
NA
(Occurrence/ will be recorded. Meter sall Vref and Vp>20% vref.
restoration) continue to record energy as Restoration:
per phase voltage and current.
4. Other Events:
a. Meter should either be
immune or should log the
events of attempt of tampering
by external magnetic
field as per relevant IS14697/
CBIP 325 with latest
Abnormal amendments.
External b. If the working of meter gets
Magnetic affected under the As per IS
As per IS 14697/ CBIP 325
Influence influence of external magnetic 14697
(Occurrence/ field, meter should
Restoration) record energy at Imax. Meter
should not compute
MD during this period. The
meter shall record BSES

energy as per actual load once

the magnetic field is
removed.
Neutral
Disturbance- Bidder shall
Meter should log the event
HF, DC and As per manufacturing define
when AC/DC/ Pulsating voltage
Alternating standard. threshold
is injected in neutral circuit.
(occurrence/ values
restoration)
Meter shall able to detect and
log the low PF event if power
factor of the load found in
between 0.2 to 0.5 for a load
Low Power above than a % threshold value 10% of I
Factor for a threshold time value. basic
Event shall restore if PF factor
of load remain out of range 0.2
to 0.5 for a load above than %
threshold value for
Plug in
Meter should log the removal of
Communication
communication card. Meter
module removal By NC switch/ sensor
should also log insertion of
(Occurrence/
communication card.
Restoration)
Configuration Meter should log the change in
change to metering mode configuration.

Page 338 of 473

 “Forwarded”
only" mode/
“Import and
Export” mode
Overload
Meter should able to log the
(Occurrence/
status of overload in KW
Restoration)
Meter with communication card
HV Spark
should be immune or log the
(Occurrence/
event in the case of application Immediately NA
restoration)/
of ESD upto and including 35
Jammer
KV.
Meter should log event of high
Occurrence: If IN > 50% of Occurrence:
neutral current if measured
High neutral average phase current 5 Min
neutral current should be more
Current Restoration: If IN < 50% of Restoration:
than predefined threshold
average phase current 5 Min
value.
Meter shall log the event if Occurrence:
difference between 5 Min
Distorted PF
displacement PF and actual PF Restoration:
is more than a predefined value 5 Min
Meter shall log voltage, current,
Time Based
PF and energy consumption on As per predefined time NA
Event Stamp
a predefined time
If temperature is more than
Temperature 60deg C. Meter has to log as - -
an event and sent alert
5. Non Roll over events: BSES

Event Description
Occurrence of cover open
6. Transaction Related Events:
Detail of Transaction
Real Time Clock- Date and Time
Demand Integration Period
Profile Capture Period
Single Action schedule for billing date
Activity calendar for time zones
New firmware activated
Load Limit (Kw) Set
Enable Load Limit Function
Disable load limit function
LLS secret (MR) change
HLS key (US) change
HLS key (FW) change
Global key change
ESWF change
MD reset
Note:
1. Event ID’s shall be defined as per BSES specification/ IS 155959 (part 2). Approval shall be
taken from BSES prior to manufacturing for Event ID’s
2. Programming of threshold values should be possible from remote via proper authentications.
3. Logics of tampers can be changed/ upgraded via firmware up gradation from remote via
proper authentication.

Page 339 of 473

4. All the programming changes/ firmware up gradations shall be logged along-with date and
time stamp in meter as well as on HES.

BSES

Page 340 of 473

Appendix 6: Technical Specifications of HT Smart Meters

1.0 Scope of Supply

This specification covers the design, manufacture, assembly, inspection, testing and delivery
of Smart CT operated 3 phase 4 wire, Accuracy Class 0.2s/ 0.5s 3 x 63.5V and Current rating:
-/5 A (Imax: 10A) & -/1A (Imax: 2A) meter with plug in communication module (Cellular (4G)
and accessories required for successful operation of the meter in post paid mode or special
application such as bidirectional net meters (configurable remotely).

Design, manufacture, testing at manufacturer works before dispatch, packing, delivery and
A.
submission of all documentation.
B. Any accessories / hardware required for installation and operation for the meter.

2.0 Codes & standards

Materials, equipment and methods used in the manufacturing of above mentioned equipment shall
conform to the latest edition of following
S
Standard Number Title
No.
2.1 Indian Electricity Act IE Act 2003
CEA Metering
2.2 With latest amendments
Regulations
CBIP Manual (Pub no.-
2.3 Standardization of AC Static Electrical Energy Meters
325)
AC Static Transformer Operated Watt-hour And Var-hour Smart
2.4 IS- 16444 (Part 2) Meters, Class 0.2 S, 0.5 S And 1.0 S Part 2 Specification
Transformer Operated Smart Meters
BSES

ac Static Transformer Operated Watt-hour and Var-hour

2.5 IS- 14697
Meters, Class 0.2 S and 0.5 S
Data Exchange for Electricity Meter - Reading Tariff and Load
2.6 IS-15959 (Part 1)
Control - Companion Specification
Data Exchange for Electricity Meter - Reading Tariff and Load
2.7 IS-15959 (Part 2)
Control (Part 2)- Companion Specification for smart meter
Data Exchange For Electricity Meter Reading, Tariff And Load
Control-Companion Specification Part 3 Smart Meter
2.8 IS-15959 (Part 3)
(Transformer Operated Kwh And KVARh Class 0.2 S, 0.5 S
And 1.0 S
2.9 IS- 11448 Application guide for AC Electricity meters
Electricity metering equipment (AC) - General requirements,
2.10 IEC- 62052-11
tests and test conditions - Part 11: Metering equipment
Electricity metering equipment (A.C) - Particular requirements -
2.11 IEC- 62053-21
Part 21: Static meters for active energy (classes 1 and 2)
Electricity metering equipment (AC) - Particular requirements -
2.12 IEC- 62053-52
Part 52: Symbols
Electricity metering equipment (A.C.) - Particular requirements -
2.13 IEC 62053-61
Part 61: Power consumption and voltage requirements
Electricity metering equipment (AC) - Acceptance inspection -
2.14 IEC 62058-11
Part 11: General acceptance inspection methods
Electricity metering equipment (AC) - Acceptance inspection -
2.15 IEC 62058-31 Part 31: Particular requirements for static meters for active
energy (classes 0,2 S, 0,5 S, 1 and 2)
2.16 IEC 60736 Testing Equipment for electrical Energy meter
IS/IEC/TR 62051:Part Electricity Metering — Data Exchange For Meter Reading, Tariff
2.17
1:2004 And Load control — Glossary Of Terms Part 1 Terms Related

Page 341 of 473

 To Data Exchange With metering Equipment Using DLMS/
COSEM
2.18 IEC 62056-1-0:2014 Smart metering standardisation framework
2.19 IEC 62056-3-1:2013 Use of local area networks on twisted pair with carrier signalling
2.20 IEC 62056-4-7:2014 DLMS/COSEM transport layer for IP networks
2.21 IEC 62056-5-3:2017 DLMS/COSEM application layer
2.22 IEC 62056-6-1:2017 Object Identification System (OBIS)
2.23 IEC 62056-6-2:2017 COSEM interface classes
Mapping between the Common Information Model message
2.24 IEC 62056-6-9:2016 profiles (IEC 61968-9) and DLMS/COSEM (IEC 62056) data
models and protocols
Wired and wireless M-Bus communication profiles for local and
2.25 IEC 62056-7-3:2017
neighbourhood networks
2.26 IEC 62056-7-5:2016 Local data transmission profiles for Local Networks (LN)
The 3-layer, connection-oriented HDLC based communication
2.27 IEC 62056-7-6:2013
profile
2.28 IEC TS 62056-8-20:2016 Mesh communication profile for neighbourhood networks
Communication profile using web-services to access a
2.29 IEC TS 62056-9-1:2016
DLMS/COSEM server via a COSEM Access Service (CAS)
2.30 IEC 62056-9-7:2013 Communication profile for TCP-UDP/IP networks
2.31 IEC 62056-21:2002 Direct local data exchange
2.32 DLMS- White Book Glossary of DLMS/COSEM terms
2.33 DLMS- Blue Book COSEM meter object model and the object identification system
2.34 DLMS- Green Book Architecture and protocols to transport the model
2.35 DLMS- Yellow Book Conformance testing process
2.36 IEEE 802.15.4 Standard for Local and metropolitan area networks.
Standard for Local and metropolitan area networks (Use of the
2.37 IEEE 802.15.4u BSES

865 MHz to 867 MHz Band in India)

Order of precedence between different standards shall be as follow:
i Indian Standards Issued By BIS
ii IEC standard
Iii Other standards like CBIP, DLMS etc.

3.0 Service Conditions

Operation range: -10 Deg C to 55 Deg C
3.1 Temperature Range Limit range of operation: -25 to 60 Deg C
Limit range of storage / transport : -25 to 70 Deg C
3.2 Relative Humidity 0 to 96 %

4.0 Distribution System Data

4.1 Supply 3 Phase AC, 4 wire
4.2 Voltage 11KV, 33KV & 66kV
4.3 Frequency 50 Hz ± 5%
4.4 System Neutral Solidly Earthed

5.0 Electrical and Accuracy Requirement

5.1 Meter Type 3- ø, 4 wire static Transformer Operated Smart Meter.

5.2 Connection Current Transformer Operated
63.5 V (phase to neutral) with variation of +30% & -40%.
5.3 Rated Voltage
However meter should withstand the maximum system

Page 342 of 473

 voltage.
a. Ib -5A and Imax- 10 A
5.4 Rated Current
b. Ib -1A and Imax- 2 A
5.5 Power factor range Zero lag – Unity – Zero lead
5.6 Starting current 0.1 % of base current
5.7 Rated Frequency 50Hz +/- 5%
0.2s (IS14697 applies for accuracy requirements) and 0.5 s
5.8 Accuracy Class
as per tender requirement.
As per IS 16444 (Part 2)
5.9 Power Consumption
Meter with lowest power consumption shall be preferred.
5.10 Meter constant Imp/ unit (Bidder to specify meter constant)
Meter shall be software calibrated at factory and
5.11 Calibration modification in calibration shall not be possible at site by
any means or external influence.
Test Output Device Separate kWh & kVAh/kVArh Flashing LED visible from the
5.12
front
5.13 Process Technology Surface Mounting Technology or better
5.14 Insulation Level As per IS 14697
5.15 Influence of supply voltage As per IS 14697
5.16 Short time over current As per IS 14697
Immunity to phase and
5.17 As per IS 14697
earth fault
5.18 Influence of Self Heating As per IS 14697
5.19 Influence of Heating As per IS 14697
a. Meter shall remain immune to electrostatic discharge
(upto and including 35KV), electromagnetic HF field and
fast transient burst.
BSES

b. The meter shall be designed in such a way that

Electromagnetic conducted or radiated electromagnetic disturbances as
5.20
compatibility well as electrostatic discharge do not influence the
meter.
c. Meter shall be type tested for electromagnetic
compatibility.
d. Meter shall comply requirement of IS 14697
Meter shall work within guaranteed accuracy as per IS
14697/ IEC62053-21/ CBIP325 (most stringent standard to
be followed) under and after influence of following :-
a. Current Variation
b. Ambient Temperature variation
c. Voltage variation
d. Frequency variation
e. 10% third harmonic in current
f. Reversed phase sequence
Limits of error due to
5.21 g. Voltage unbalance
influence quantities
h. Harmonic components in current and voltage circuit
i. DC and even harmonics in AC current circuit
j. Odd harmonics in AC current circuit.
k. Sub harmonics in AC current circuit
l. Continuous (DC) “stray” magnetic induction of 67mT+/-
5%.
m. Continuous (DC) “abnormal” magnetic induction of
0.27T+/-5%.
n. Alternating (AC) “stray’ magnetic induction of 0.5mT+/-

Page 343 of 473

 5%
o. Alternating (AC) “abnormal’ magnetic induction of
10mT.
p. External magnetic field 0.5 T
q. Electromagnetic HF fields
r. Radio frequency interference
s. DC immunity test
Note: BSES reserves the right to formulate any other test
method to check magnetic immunity/ logging of meter.
Meter with logging provision will be preferred.
Other features Mid night data: The meter should record midnight
Cumulative kWh & kVAh, kVARh lag and kVARh lead
reading for last min 45 days load survey data.
Total Harmonic Distortion: Meter to record harmonic
5.22
components in both current and voltage circuits. And should
be available in on demand display. Meter to record events
in case harmonic component in both V&I if it exceeds
threshold limits (configurable).
i. Default Display (Auto Mode)
ii. LCD test
iii. Meter serial no.
iv. Date
v. Real time
vi. Cumulative kWh
vii. Cumulative Export Active Energy*
viii. Net Active energy*
ix. Cumulative kvarh Q1/Lag
BSES

x. Cumulative kvarh Q2/Lead

xi. Cumulative kvarh Q3*
xii. Cumulative kvarh Q4*
xiii. Cumulative kVAh
xiv. Cumulative Apparent Energy (active export)*
xv. Net Apparent energy*
xvi. Instantaneous load in kW, kVArh & kVA
Display Sequence for the xvii. TOD MD for kWh and kVAh
5.23
parameters xviii. Phase wise voltage and current (R, Y, B phases)
xix. Power factor
xx. Neutral current
xxi. TOD Total Active Forward Energy Register(Reg
1)
xxii. TOD Total Active Forward Energy Register(Reg
2)
xxiii. TOD Total Active Forward Energy Register(Reg
3)
xxiv. TOD Total Active Forward Energy Register(Reg
4)
xxv. TOD Total Active Forward Energy Register(Reg
5)
xxvi. TOD Total Active Forward Energy Register(Reg
6)
xxvii. TOD Total Active Forward Energy Register(Reg
7)

Page 344 of 473

 xxviii. TOD Total Active Forward Energy Register(Reg
8)
xxix. TOD Apparent Forward Energy Register(Reg 1)
xxx. TOD Apparent Forward Energy Register(Reg 2)
xxxi. TOD Apparent Forward Energy Register(Reg 3)
xxxii. TOD Apparent Forward Energy Register(Reg 4)
xxxiii. TOD Apparent Forward Energy Register(Reg 5)
xxxiv. TOD Apparent Forward Energy Register(Reg 6)
xxxv. TOD Apparent Forward Energy Register(Reg 7)
xxxvi. TOD Apparent Forward Energy Register(Reg 8)
xxxvii. Temperature
xxxviii. Total tamper count
xxxix. Status of communication module
xl. Mode (Net/Forward)
xli. Signal strength in RSSI
xlii. Error code

Display (On demand)

After using pushbutton the following parameters should be
displayed.
i. LCD test
ii. Meter serial no.
iii. Date
iv. Real Time
v. Cumulative kWh
vi. Cumulative Export Active Energy*
BSES

vii. Net Active energy*

viii. Cumulative kvarh Q1/Lag
ix. Cumulative kvarh Q2/Lead
x. Cumulative kvarh Q3*
xi. Cumulative kvarh Q4*
xii. Cumulative kVAh
xiii. Cumulative Export Apparent Energy*
xiv. Net Apparent energy*
xv. Current MD in kW
xvi. Current MD in kVA
xvii. MD in kVAR
xviii. TOD MD for kW and kVA
xix. TOD MD occurrence for kW and kVA
xx. Instantaneous Power factor
xxi. Instantaneous voltage R phase
xxii. Instantaneous voltage Y phase
xxiii. Instantaneous voltage B phase
xxiv. Instantaneous current R phase
xxv. Instantaneous current Y phase
xxvi. Instantaneous current B phase
xxvii. Last month billing Date
xxviii. Last month billing kWh reading
xxix. Last month billing kVARh reading
xxx. Last month billing kVAh reading
xxxi. Last month billing Maximum Demand in kW

Page 345 of 473

 xxxii. Last month billing Maximum Demand in kW
occurrence Date
xxxiii. Last month billing Maximum Demand in kW
occurrence Time
xxxiv. Last month billing Maximum Demand in kVA
xxxv. Last month billing Maximum Demand in kVA
occurrence Date
xxxvi. Last month billing Maximum Demand in kVA
occurrence Time
xxxvii. THD for both Voltage and Current
xxxviii. Total Active Energy, Apparent Energy
xxxix. Fundamental Reactive Lag and Fundamental
Reactive Lead Energy
xl. High Resolution value (kWh, KVAh)
xli. High resolution Export Active Energy (kWh ,
KVAh)*
xlii. Neutral Current
xliii. Temperature
xliv. Battery status
xlv. PT/CT status
xlvi. Self diagnostic flag
xlvii. Connection check (Phase sequence)
xlviii. Cumulative Tamper count
xlix. Cumulative Power off hours
l. Signal strength in RSSI
li. Error code
lii.
BSES

Phase association (ok/ Not ok)

* When meter is configured in net metering mode then only
these parameters should appear otherwise these display
parameters should be disable and shall not appear on
display
Note:
1. The meter display should return to Default Display
mode (mentioned above) if the ‘push button’ is not
operated for more than 6 seconds. Provision for scroll
lock by pressing for 15 sec and sent to normal after 5
minutes.
2. Sequence of display parameter and parameter subject
to change and to be finalized before supply.

6.0 Construction
Material - Opaque and UV stabilized polycarbonate of grade
6.1 Base Body
LEXAN 143/ 943 or Equivalent with V0 inflammability level.
a. Material: Transparent/Opaque and UV stabilized
polycarbonate of grade LEXAN 143/ 943 or Equivalent
with V0 inflammability level.
6.2 Top Cover b. Top cover and base should be Ultrasonically/Chemically
welded.
c. Top cover should be designed so as the internal
components should not be visible.
6.3 Terminal Block
a. Material - Flame retardant glass filled polycarbonate of
grade 500 R or equivalent.

Page 346 of 473

 b. Terminal block shall form Integral part of the meter base
c. Terminal block shall be capable of passing the tests as
per ISO-75 for a temperature of 135C and pressure of
1.8MPa. The terminals shall be designed so as to ensure
adequate and durable contact such that there is no risk of
loosening or undue heating.
g. Material - UV stabilized transparent/Opaque
polycarbonate cover of grade LEXAN 143A/943AA or
equivalent.
h. Provision of sealing at two points through sealing screw.
i. The sealing screws shall be held captive in the terminal
cover.
j. The terminal cover shall be extended type with baffle wall
6.4 Terminal cover above the cable entry base wall so that access to the
terminals is not possible (even with thin metallic wire)
without breaking the seal. Terminal cover should have
provision for cable entry from bottom.
k. Diagram of external connections should be embossed on
terminal cover. Sticker is not acceptable.
l. Mechanism shall be provided to record an event with
occurrence and restoration in case of meter enclosure/
terminal cover is opened.
a. Terminals shall be suitable for 6 Sqmm copper wire.
b. Two no’s grub screws per terminal shall be provided
c. Material of terminals, screws and washers should be
brass or tinned copper. Terminals shall be tested for
6.5 Terminals
continuous current of 150 % Imax.
BSES

d. Terminals shall be clearly marked for phase / neutral /

outgoing etc.
e. Clearances and creepage shall be as per IS 14697.
6.6 Ingress Protection a. IP 51 or better, but without suction in the meter.
Meter should have flashing LED visible from the front to
represent energy recording. Resolution shall be such that
6.7 Output device satisfactory accuracy test can be conducted at the lowest
load in less than 5 minutes and starting current test in less
than 10 minutes.
a. The meter shall have internal real time crystal clock to
set date and time.
6.8 RTC b. Drift in time of this clock shall not be more than
±5minutes/ year at a reference temperature of 27°C.
HES will sync RTC at least once a day (configurable).
Lithium ion battery with guaranteed shelf life of 10 years and
capacity life of 15 years. Lithium thioyl Chloride battery will
be preferred. In case battery removal or total discharge
same should not affect the working & memory of the meter.
6.9 Battery
Meter should have two separate battery.
One for RTC and one for back up
a. In case battery voltage reduced below threshold value
then need to generate alert
Non volatile memory independent of battery backup,
6.10 Memory memory should be retained up to 10 year without any
auxiliary power.
6.11 Self Diagnostic feature Meter shall have self diagnostic for the following

Page 347 of 473

 a. Date and RTC.
b. Battery.
c. Non volatile memory.
d. Display
e. Status of Communication card
Meter shall have an optical port with a metal ring to hold
6.12 Optical port magnet of probe. Optical port shall comply with hardware
specifications provided in IEC-62056-21.
a. Meter should have the provision for 01 no’s modular and
pluggable communication module compatible with
Cellular (4G).
b. Meter shall have mechanism to log communication
module removal and insert as an event in its memory
with date and time stamp.
6.13 Communication c. Meter shall have separate indications on display/ for
remote and local communication.
d. Communication module shall held in a casing which can
be directly plugged in the meter. Sealing screw shall be
provided.
e. Communication module shall be configurable for IPV6
with backward compatibility with IPV4
In Last Gasp endpoint shall send the power outage and
power restoration notification with Time Stamp. In case of
power failure meter communication module shall not draw
6.14 First breath and last gasp power from the backup battery.
For the purpose of sending the Last Gasp, communication
module shall have proper power backup (like a super
BSES

capacitor).
a. Sealing should be in accordance with IS and CEA
metering regulations with latest amendments.
b. Sealing arrangement shall be such that sealed parts
shall not be opened without breaking the seal or sealed
part itself. There should be clear evidence of the
breaking in case sealed parts shall be opened without
breaking the seal.
c. Approval shall be taken from purchaser for location of
seals and number of seals.
d. Record of all seals shall be forwarded to purchaser with
Meter Sealing
6.15 each lot.
Arrangement
e. Meter Body : 1 plastic seal and Hologram seal as per
BSES specs & 1 seal of meter manufacturer
f. Meter Terminal cover : 2 Plastic seal as per BSES
specs
g. Meter Cubical : 2 plastic seal as per BSES
Specifications
h. (All above seals provided by AMISP as per the serial no
provided by BSES )
i. Record of all seals shall be forwarded to purchaser with
each lot.
Record of all seals shall be forwarded to purchaser with
6.15.3 Seal record
each lot.
6.16 Insulation As per IS 16444 (Part 2)
6.17 Name Plate and marking a. Meter should have clearly visible, indelible and distinctly

Page 348 of 473

 marked name plate in accordance with IS 16444 (Part 2)
& clause no. 10.0 of this specification.
b. All markings and details shall be printed by laser only.
c. Name plate shall have QR code having meter information
like meter [Link]., month and year of manufacturing, type of
meter, OEM, Rating etc
Paper stickers are not allowed for name plate.
The terminal block and Meter case shall have safety against
Resistance against heat
6.18 the spread of fire. They shall not be ignited by thermal
and fire
overload of live parts in contact with them as per IS 14697.
a. 10.5 Years from the date of dispatch or 10 Year from
date of commissioning, whichever is earlier
6.19 Guarantee b. The meters which are found defective/inoperative within
the guarantee period shall be replaced as per meter
service level agreement.

7.0 Functional Requirement

7.1 Meter category Smart meter comply with D3 category of IS 15959 (Part 3).
It should be possible to configure meters in following modes of
metering:
a. Forwarded Only: In this mode any export active energy
shall be treated as import energy and shall be recorded in
forward only register. Apparent energy calculation in this
mode shall be as per clause no. 7.3.
7.2 Mode of metering b. Bidirectional: Both Import and export energy recording shall
be applicable in this mode of metering and relevant
BSES

registers shall be updated.

Any change in metering mode shall be logged in events with
date and time stamp.
Default mode of metering shall be forwarded only untill specified
in tender requirement otherwise.
Lag only: KVAh is computed based on KVArh and KWH value.
7.3 kVAh Calculation If PF=1, or leading, then KVAh = KWH. At no instance KVAh <
KWh.
Block / sliding window with default demand integration period of
1800 s configurable to 900 s as per requirement. Meter should
be configurable for block/ sliding window at the time of
7.4 MD calculation manufacturing. This change should not be possible in the field.
Extended register shall be used for MD recording.
It should be possible to reset MD automatically at the defined
date (or period) or through CMRI
a. Meter shall be capable of doing TOD metering in minimum
4 tariff rate registers programmable for minimum 8 time
zones and 4 seasonal profiles.
b. TOU metering shall be implemented by the activity colander
method of IS 15959 Part 1 clause 9/ DLMS UA-1000-1
7.5 TOU Metering
c. Special Day table shall be defined as per IEC/ DLMS UA-
1000-1
d. Default TOU programming shall be as per latest DERC
guidelines. Prior approval shall also be taken from BSES for
the same.
e. Tariff rate registers shall be as follow
R1: Rate register for Peak

Page 349 of 473

 R2: Rate register for Normal
R3: Rate Register for Off Peak
All the parameters mentioned in table ‘1’ of IS 15959 (Part 3)
along with following additional parameters shall be supported by
meter.
a. Neutral Current (IN)
b. % TDH in R phase Voltage
c. % THD in Y Phase Voltage
d. % THD in B Phase Voltage
Instantaneous
7.6 e. % THD in R phase Current
Parameters
f. % THD in Y Phase Current
g. % THD in B Phase Current
h. Temperature
i. Signal Strength in RSSI
j. Voltage angles for displaying phasors.
Method of Measurement for harmonic parameters at sl no.
‘b’ to ‘g’ shall confirm to the IEEE 519, 2014.
7.6.1 Association Rights As per Clause 11.1.1 of IS 15959 (Part 3).
a. Billing parameters shall be generated at the end of each
billing cycle and stored in memory as per provisions
provided in clause no. 14 of IS 15959 (Part 3).
b. 12 no’s billing cycle parameters shall be remain in meter
memory along with current cycle parameters and shall be
available for reading as well as profile and or ‘by entry’ for
7.7 Billing data
selective access.
c. All the parameters mentioned in table ‘4’ of IS 15959 (Part
3) shall be supported by meter.
BSES

d. Cumulative power interruption count in all monthly history

data
e. Monthly Power off duration in all history data.
7.7.1 Association Rights As per clause 14 of IS 15959 (Part 3).
Support for selective access shall be provided for billing
7.7.2 Selective access
parameters as per clause no 11.3 of IS 15959 (part 1).
Billing period reset/
7.7.3 00:00 Hrs of Ist of every month
MD reset
Billing period reset
7.7.4 As per clause 10 of IS 15959 (Part 1)
mechanism
Cumulative billing period counter since installation and available
7.7.5 Billing period counter billing periods shall be provided as per clause 11.2 of IS 15959
(Part 1).
a. Load survey parameters shall be measured and
recorded at the end of each profile capture period for
last 45 Power ON days for 30min IP.
b. All the parameters mentioned in table ‘15’ of IS 15959
(Part 3) along with following additional parameters shall
Load survey be supported by meter:
7.8 % THD in R phase Voltage
Data
% THD in Y Phase Voltage
% THD in B Phase Voltage
% THD in R phase Current
% THD in Y Phase Current
% THD in B Phase Current
Phase wise Voltage and Current (Line, Active, Reactive)

Page 350 of 473

 with instant and average value.
all three phase active, reactive (lag and lead) and
apparent power and energy, Power-off time integration
period and Neutral Current
Average Signal Strength
7.8.1 Profile capture period Default 1800 s programmable to 900 s.
Support for selective access shall be provided for billing
7.8.2 Selective Access
parameters as per clause no 11.3 of IS 15959 (part 1).
7.8.3` Association Rights As per clause no.18 of IS 15959 (Part 3)
Daily load profile parameters shall be measured and recorded
at each midnight i.e. 00:00 hrs for last 45 Power ON days.
7.9 Daily load profile
All the parameters mentioned in table ‘3’ of IS 15959 (Part 3)
shall be supported by meter as Daily load profile parameters.
7.9.1 Association Rights As per clause no. 13 of IS 15959 (Part 3)
General Purpose Following parameters shall be provided in Non Volatile memory
7.10
Parameters (NVM) of the meter as per clause 16 of IS 15959 (Part 3).
7.10.1 Name Plate Detail As per Table ‘12’ of IS 15959 (Part 3).
7.10.2 Association Rights As per clause no. 16.1 of IS 15959 (Part 3)
These parameters can be programmed remotely by HES and
locally by HHU via proper access writes. Every transaction shall
be logged in non volatile memory of the meter with date and
time stamp.
Programmable
7.10.3 Programming of any of the parameters shall increment the
parameters
‘Cumulative programmable count’ value.
All the parameters mentioned in table ‘13’ of IS 15959 (Part 3)
shall be supported by meters with following additional
parameters as mentioned in specification
7.10.4 Association rights As per Clause no. 16.2 of IS 15959 (Part 3).
BSES

a. Smart meter is able to automatically notify data, event,

and messages to a destination client system in an
unsolicited manner (without a request from a client) as
per clause no 6 of IS 15959 (Part 2).
b. Randomization: Data from different endpoints shall be
pushed intelligently on the network in order to avoid
excessive traffic on the network for example in case all
the endpoints will push load survey data simultaneously,
then it may result in network choking or inefficient
performance. Therefore with the help of intelligent
7.11 Push Services techniques such field scenarios shall be handled
effectively.
c. It shall also be possible to configure push services for all
profiles i.e instantaneous, billing, load survey, daily
energy and events. Bidder should explain its capability
to configure push services. However following push
services shall be available by default.
i. Load survey profile data at after every 4 hours
configurable to any predefined interval.
ii. Mid night data at 00:00 hrs of every day.
iii. Billing profile data on occurrence of billing.
a. Meter shall be able to push instantaneous parameters to
HES at predefined intervals. Parameters required for
Periodic push (Smart
7.11.1 push shall be intimated during detailed engineering in
meter to HES)
the vent of order.
b. Other attributes as per IS 15959 (Part 3) i.e. Send

Page 351 of 473

 Destination, Communication window, Randomization
time interval, number of retries and repeat delay shall be
decided in the event of manufacturing.
a. Meter is able to report HES, the status change of any of
the identified events mapped in to event status word
(ESW) of size 128 bits by pushing following objects to
HES.
i. Device ID
ii. Push Setup ID
iii. Real time clock- Date and Time
iv. Event Status Word 1 (ESW 1).
Event Push (Smart b. Each of the bits in ESW shall reflect the current state of
7.11.2
meter to HES) the event and are mapped against each of the identified
events.
c. An event status word filter (ESWF) of 128 bit shall also
be provided to configure events for event push. Events
which are supported in meter shall only be configured
for event push. Bit value 1 in ESWF shall indicate that
the event is supported and value 0 indicates that event
is not supported for event push. Position of the event bit
in ESWF shall be same as in ESW.
Event status Bit
7.11.3 As Per IS 15959 (Part 3)
mapping
a. Smart meter shall support remote firmware upgrade
feature for meter firmware without loss of any data and
metrology for a part or complete firmware of meter.
b. Firmware upgrade shall use the Image transfer classes
BSES

and mechanisms specified in IEC62056-6-2 and

IEC62056-5-3.
c. Broad cast facility shall be supported in HES for
simultaneously upgrading the firmware of a group of
meters installed in field.
d. Firmware upgrade feature shall be provided with proper
security. The design shall take into account field
scenarios such as power failure during F/W upgrade.
e. Once the firmware is upgraded successfully, meter shall
send an acknowledgment to HES. It shall also log it as
7.12 Firmware upgrade
an event in its memory with date and time stamping.
f. Meter shall support capability to self register the meter
with new firmware.
g. The execution time of the change of the firmware within
the meter should be below 1 minute
h. Meter shall support auto resume firmware upgrade in
case file transfer stops due to any reason like power
supply failure. There shall not be any corruption in data
during transfer of firmware.
i. In case of wrong firmware file, meter shall be able to
identify the same and suspend FOTA activity
j. Meter shall support NIC FOTA through HES
k. NIC firmware file size should be less than meter
firmware file
Support for Meter shall support connection less messaging services of
7.13
broadcast message DLMS to support broadcast messages for a group of meters for

Page 352 of 473

 following actions:
a. Gap reconciliations.
b. Firmware upgrade.
c. On demand readings
d. Updating of Programmable parameters
a. Advanced security outlined in clause 7.1.2 of IS 15959
(Part 1) shall be provided.
b. Reading and writing data into meter memory via optical
and remote communication port shall be through DLMS
security keys only.
c. Bidder shall ensure to safeguard high security keys used
for configuring parameters into meter.
d. Once the meter memory is locked during manufacturing
process, only parameters mentioned in IS 15959 shall be
7.14 Security configurable even in factory. It should not be possible to
configure any other parameters.
e. Please note that there shall be no other mechanism/
method to interface with meter through optical and
remote communication port except mentioned in IS
15959, even for manufacturer.
f. It should not be possible to change data stored in meter
memory even after accessing meter memory physically.
In case of any change in memory data, a flag/alert shall
be generated. Flag/Alert shall be indicated over display
and in remote communication also
Encryption for data
7.15 As per clause 7.1 of IS 15959 (Part 2)
communication BSES

Encryption/
7.151 Authentication for As per clause 7.2 of IS 15959 (Part 2)
data transport
Key requirement and
7.15.2 As per clause 7.3 of IS 15959 (Part 2)
handling
a. Proper security at end points as well as network level
shall be present to prevent unauthorized hacking of the
end points or the network itself.
b. The meter password is required to open a session
between NIC and meter and is required to gain
clearance from the meter to perform requested
operation.
7.15.3 NIC Security c. If clearance not gains, the meter locks out local
communication for 1 minute. The meter maintain counter
for monitoring of unsuccessful attempts of performing
meter operations and alerts to HES. The counter is
incremented each time a password clearance operation
fails.
d. Up to 3 no’s unsuccessful attempts are allowed, after
which the port is locked out until authenticated from
system administrator.
IP communication
a. Meter shall support TCP-UDP/ IP communication profile
7.15.4 for smart meter to HES. Please refer clause 8 of IS
profile support
15959 (Part 3).
Event and tamper Meter shall detect and log any exceptional/ fraud/ tamper
7.16
detection conditions in its memory as an event. In addition to this all

Page 353 of 473

 transactions and control shall also be recorded as an event in
meter memory. Each event type shall be identified by an event
ID.
Each event shall be available to download as per following
association rights.
a. Public Client: No access
7.17 Association Rights
b. Meter Reader: Read only
c. Utility Settings: Read only
Push Services: Read Only for identified events as per ESWF
Meter shall be able to log events in following compartments
a. Voltage Related Events
b. Current Related Events
Compartments of c. Power Related Events
7.18
events d. Others Events
e. Non Roll Over Events
f. Transaction related events
Control Events
a. Occurrence and Restoration of Voltage Related, current
related, power related and other events shall be logged
in meter memory as per IS 15959 (Part 3). Please refer
Appendix 6A for description of events, Event ID, Logics
of events and threshold values of events.
b. Threshold values shall be factory programmable.
Compartments of c. Selective access shall be provided as per clause 11.3 of
7.18.1 events IS 15959 (Part 1).
Parameter Snapshot d. For each of the events a certain list of parameters shall
be captured as per clause 'a'
BSES

g. For each occurrence event captured, the cumulative

tamper count shall be incremented.
h. Meter shall capture all the parameters mentioned in
table ‘24’ of IS 15959 (part 3) when event occurrence
and restoration is logged
The meter shall log minimum 200 tamper events (ensuring at
7.18.2 Event Logging
least 20 events for each tamper).
Appropriate Indications/Icons for all tampers should appear on
7.18.3 Tamper Indication
the meter display either continuously or in auto display mode.
Phasor Meter shall support parameters required to develop phasors of
7.18.4
Representation current and voltage at HES.
All the energies measured and recorded with and without
7.19 Harmonic Energies
harmonics.

8.0 Meter Display

8.1 LCD Type STN Liquid crystal with backlit

a. Minimum 120 Degree.
b. The display visibility should be sufficient to read
the Meter mounted at height of 0.5 m as well as at
8.2 Viewing angle the height of 2 m.
8.3 Size of LCD Minimum 10X6mm PIN Type
8.4 LCD Digits Total 10 digits
8.5 LCD language English

Page 354 of 473

 a. Auto Mode
b. Manual Mode
8.6 Display modes c. Sub active mode
Display list shall be finalized during detailed engineering
in the event of order.
Appropriate indications/flags for all tampers and self
8.7 Display indications diagnostic features should be provided.

9.0 Data and communication protocol/ HES/Integrations/ Software

a. Meter should comply Indian companion of data

exchange and tariff control specification IS 15959 (Part
2).
b. In case of additional requirement from IS 15959 (part 2),
they shall be as per DLMS standards/ IEC DLMS
Data Exchange protocols suite (62056).
9.1
protocol c. Bidder shall explain in detail the additional parameters/
services/ methods used in meters from IS 15959 (part 2)
and its reference to DLMS books/ IEC.
d. Prior to manufacturing of meters bidder shall provide a
detailed specification explaining all parameters/ services/
methods used in meter in addition to IS 15959 (Part 3).
a. Bidder shall work with BSES IT team/ BSES designated
system integrator to integrate its meter with BSES HES
system.
9.2 Integration with HES
b. Bidder shall prepare detailed documents as mentioned
in above clause and submit it for BSES approval and
BSES

integration with HES.

Base computer Licensed Software with the following features should be
9.3
software supplied for free to download meter through optical port.
9.3.1 Operating System BCS should be compatible for latest Windows operating system.
System shall be password protected where user can login only if
login ID is provided by administrator. BCS shall have rights
9.3.2 Security
management system so that access rights can be provided as
per requirement to maintain security.
BCS shall maintain master database according to desired area,
9.3.3 Database
location, and region etc.
a. BCS shall have option of user defined report generation
in format of Excel, Word and CSV, XML, PDF etc.
b. BCS shall have capability to export data in ASCII, CSV
9.3.4 Reporting and XML format at desired location so that the same
could be integrated with our billing data for processing.
c. All the data available in the meter shall be convertible to
user defined ASCII, CSV and XML file format.
BCS and communication ports should support data transfer rate
9.3.5 Data transfer rate
of 9600 bps (minimum).
a. The manufacturer has to provide Mobile App for
downloading all the data stored in meter memory through
optical port.
Hand Held Unit
9.4
Software
b. Mobile App should have option for selection of parameters
to be downloaded from meter
c. Meter data consisting of all parameters and complete load
survey for all parameters shall be read by HHU (Mobile

Page 355 of 473

 App) and data transferred to HES in minimum possible time
(not more than 5 minutes).
d. Mobile App should have option to initiate configuration and
firmware upgrade actions locally for non-communicated
meters as per the schedule initiated from back end
applications (HES/MDMS).
e. Mobile App should ensure the meter security keys are
stored in encrypted form and not accessible to users.
Manufacture shall impart training to BSES personnel for usage
9.5 Training
of software

10.0 Name Plate

Meter Serial number shall be of 10 digits. Serial number shall be printed in black colour.
10.1
Embossing is not acceptable.
Size of the digit shall be minimum 5 X 3mm. Details shall be printed by laser printing
10.2
preferably.
10.3 Bar code shall be printed below the serial number
10.4 BIS registration mark (ISI mark)
10.5 ‘BSES’ insignia shall be printed above LCD display.
10.6 BSES PO No. & date and Property of BSES
10.7 Manufacturers name and country of origin
10.8 Model type / number of meter
10.9 Month and Year of manufacturing
10.10 Reference voltage / current rating
The number of phases and the number of wires for which the meter is suitable.
10.11
Graphical symbol as per IS 12032 can be used.
BSES

10.12 Meter constant Impulse/kWh Impulse/kVAh/kVArh

10.13 Class index of meter
10.14 Reference frequency
10.15 Warranty period
Name plate of NIC
a. Serial no of NIC along/ IMEI no/MAC address with bar code
b. Name of purchaser’s
10.16
c. Communication technology with carrier frequency
d. Manufacturing year and month.
e. Warranty period.

11.0 Component Specification

The Meters should be with the

To meet accuracy
11.1 Current Transformers current transformers as measuring
requirement
elements.
The Measurement or computing
Analog Devices, Cyrus
Measurement or chips used in the Meter should be
11.2 Logic, Atmel, Phillips,
computing chips with the Surface mount type along
SAMES ,NEC,TEXAS
with the ASICs.
The memory chips should not be Atmel, National
affected by the external parameters Semiconductors, Texas
11.3 Memory chips
like sparking, high voltage spikes or Instruments, Phillips,
electrostatic discharges. ST, Hitachi, Compiled

Page 356 of 473

 a. The display modules should be
well protected from the external
UV radiations.
Hongkong: Genda
b. The construction of the modules Singapore: Bonafied
should be such that the
technologies
11.4 Display modules displayed quantity should not
Korea: Advantek
disturbed with the life of display
China: Success
(PIN Type).
Japan: Hitachi, Sony
c. It should be STN type industrial
grade with extended
temperature range min 70 ºC.
The mechanical construction of the USA: National
port should facilitate the data Semiconductors, HP
11.5 Optical port
transfer. Communication shall not Holland/ Korea: Phillips
disturbed by external light. Japan: Hitachi, Ligitek
The power supply should be with
the capabilities as per the relevant
standards. The power supply unit of
the meter should not be affected in
11.6 Power Supply SMPS Type
case the maximum voltage of the
system appears to the terminals due
to faults or due to wrong
connections.
The active & passive components
should be of the surface mount type USA: National
& are to be handled & soldered by Semiconductors, Atmel,
the state of art assembly processes. Phillips, Texas
Electronic The PTH components should be Instruments.
BSES

11.7
components positioned such a way that the leads Japan: Hitachi, Oki,
of components should not be under AVX or Ricoh
stress and not touching the internal Korea: Samsung
wires.
LED Everlight, Agillent
a) The internal electrical
components should be of electrolytic
copper & should be protected from
corrosion, rust etc.
11.8 Mechanical parts
b) The other mechanical
components should be protected
from rust, corrosion etc. by suitable
plating/painting methods.
Lithium with guaranteed life of 15 Texcell, SAFT, Varta,
11.9 Battery
years Tedirun, Sanyo
USA: Philips, Dallas
RTC & Micro The accuracy of RTC shall be as Atmel, Motorola,
11.10
controller per relevant IEC / IS standards Microchip, TEXAS,
Japan: NEC, Oki
Glass Epoxy, fire resistance grade
11.11 P.C.B. FR4, with minimum thickness 1.6 (BBT test is must)
mm
a. The components used by
manufacturer shall have
11.12 Note
“Minimum Life” more than the
10 years.

Page 357 of 473

 b. Incase vendor want to use other
make components; same shall
be approved by BSES before
use.
c. Even for existing supplier – fresh
approval is needed for all
deviations.
d. Manufacturer should have
complete tracking of material
used in meter. BSES reserve
the right to carry out audit of
inventory/ manufacturing
process at manufacturer’s works
and sub vendor’s work.

12.0 Quality Assurance, Inspection and Testing

Vendor's Quality
12.1 To be submitted for Purchaser's approval.
Plan (QP)
Sampling Method for quality checks shall be as per relevant IS/
12.2 Sampling Method IEC/ CBIP guidelines and Purchaser's prior approval shall be
taken for the same.
Inspection Hold-
12.3 To be mutually identified, agreed and approved in Quality Plan.
Points
a. The meter shall be of type tested quality including all tests
specified in this specification which are beyond IS / IEC or
CBIP. BSES

b. Type test conducted from CPRI/ ERDA/ or any other lab

specified by BIS/ CEA for smart meter testing will be
treated as valid.
12.4 Type Tests
c. Type test certificate should be submitted along with offer for
scrutiny.
d. Any other component supplied in addition to meter shall
also be type tested as per IS /IEC if applicable.
e. Complete type test as per IS 16444 (Part 2) shall be carried
out on sample selected from BSES lot.
12.5 Routine tests All test marked “R” as per table 20 of IS 14697.
a. All tests marked “A” as per IS 14697.
b. Smart meter functional tests as per IS 16444 (Part 2).
c. Test for data exchange protocol as per IS 16444 (part 2).
d. Test for Smart meter communicability as per clause no.
10.6 of IS 16444 (Part 2).
e. All the routine and acceptance tests shall be carried out as
per relevant standards.
12.6 Acceptance Tests f. Following tests in addition to IS shall be conducted during
lot inspection.
I) Dimensional and drawing verification.
II) Display parameters/ sequence.
III) Data Downloading from CMRI and PC.
IV) Tamper/ fraud detection/logging features as per
approved documents. Tamper conditions will be
simulated at varying load up to Imax. Accuracy will
also be checked during tamper simulation.

Page 358 of 473

 V) Burn in chamber test.
VI) Component verifications.
g. Purchaser reserves the right to formulate any other test
method to verify guaranteed parameters of Meter.
ESD and Magnetic ESD and magnetic interference test will be conducted at Samir
12.7
Interference test lab, Chennai or CPRI.
a. Purchaser reserves the right to inspect /witness all tests on
the meters at Seller’s works at any time, prior to dispatch,
to verify compliance with the specification/ standards.
b. Manufacturer should have all the facilities/ equipments to
conduct all the acceptance tests as per clause 14.3
12.8 Inspection
relevant standards and tampers logics as per approved
GTP. All the equipments including tamper logs kits/ jigs
should be calibrated.
c. In-process and / or final inspection call intimation shall be
given in advance to purchaser.
a. The internal potential links should be in closed position or
link less meters will be preferred and there shall not be any
external link.
b. Deliverable with Meters.
i. Hard copies for Routine test certificates with each
meter till alternate is provided by vendor and approved
BSES.
ii. Terminal cover should be fixed on the meter before
dispatch.
iii. Report of seal & initial reading record. (soft copy as
per BSES format)
BSES

c. Box number, meter serial number, type, rating should be

mentioned on cases / cartons.
d. Meters shall be suitably packed with environmental friendly
material in order to avoid damage or disturbance during
transit or handling and to prevent in grace of moisture and
General dust. Also refer CEA Metering Regulation 2006.
12.9
Requirements e. In case battery removal/ total discharge same should not
affect the working & memory of the meter.
f. The bidder shall maintain a web site where routine test
results of all meter supplied against these tender will be
maintained and will be accessible to buyer/ buyer
representative.
g. The supplier shall give 15 day advanced intimation to
enable BSES to depute representative for lot inspection.
h. Vendor shall ensure that patch required for HHU/CMRI
shall be provided within 4 weeks. Vendor shall also ensure
to deliver solution to meet DERC mandate within mutually
agreed timeline.
i. Delivery of software for reading through HHU/CMRI before
meter delivery is required.
j. For any false events recorded in meter, vendor shall depute
their representative for field visit within one week and
provide the root cause analysis in 4 weeks time.

13.0 Packing, Marking, Shipping, Handling and Storage

Page 359 of 473

 a. Each meter must be packed, together with its terminal
cover, in a separate environmental friendly cardboard
box, which can be opened and re-closed without
needing adhesives.
b. Up to 4 to 5 three-phase meters must be packed
together with their terminal covers in a group cardboard
box, which can be opened and re-closed without
needing adhesives.
c. The box shall prevent, as much as possible, penetration
of dust during long storage periods. The box must be
designed for multiple use and be robust, with wall
thickness of at least 4 mm.
d. Maximum weight of a group meter box shall not be
more than 25 Kg.
e. The packaging will protect the meters against shock
and vibration, preventing damage due to the road
13.1 Packing conditions during transport and distribution in the field.
The electrical and mechanical properties shall not be
affected by these disturbances.
f. For shipping the boxed meters will be close packed by
stockpiles of suitable quantities on pallets. The meters
numbers sequence (without partition) shall be kept in
each pallet. A pallet will be protected against moisture
by a polyethylene hood, covered with a cardboard
cover (hood), and fixed onto the pallet by parallel
polypropylene bands, using protection angle bars at the
corners. The hood shall be marked – on the front (wide
side), on the narrow side and on the top as per clause
BSES

13.3.
g. Visual indications (stickers) shall be attached to the
cardboard hood of several pallets in each container/
transport truck, to warn of possible rough handling
during shipment, transport and storage.
Packing for
Robust wooden non returnable packing case with all the above
13.2 accessories and
protection & identification Label.
spares
On each group box and pallet, following details are required
both on front (wide side) and top:
a. BSES logo.
b. Meter serial number range along with bar code.
c. Unique number of box/ pallet.
d. Purchaser’s name
e. PO number (along with SAP item code, if any) & date
with bar code
13.3 Marking f. Equipment Tag no. (if any)
g. Destination
h. Manufacturer / Supplier’s name
i. Address of Manufacturer / Supplier / it’s agent
j. Type , rating and other description of equipment
k. Country of origin
l. Month & year of Manufacturing
m. Case measurements
n. Gross and net weights in kilograms

Page 360 of 473

 o. All necessary slinging and stacking instructions
13.4 Test reports Routine test report to be provided with each meter
The seller shall be responsible for all transit damage due to
13.5 Shipping
improper packing.
Manufacturer instruction shall be followed. Detail handling &
Handling and
13.6 storage instruction sheet /manual to be furnished before
Storage
commencement of supply.

14.0 Deviations

a. Deviations from this specification can· be acceptable, only

where the Seller has listed in his quotation the
requirements he cannot, or does not, wish to comply with
and which deviations the Buyer has agreed to in writing,
14.1 Deviations before any order is placed.
b. In the absence of any list of deviations from the Seller, it
will be assumed by the Buyer that the Seller complies with
the Specification fully.
c. Refer Annex C for deviation

15.0 Drawing Submission

Drawing submission shall be as per the matrix given below. All documents/ drawing shall be
provided on A4 sheet in box file with separators for each section. Language of the documents
shall be English only. Deficient/ improper document/ drawing submission may liable for rejection
Pre
SL Detail of DocumentBSES
Bid Approval
Dispatch
1 Guaranteed Technical particulars (GTP) Required Required
2 Deviation Sheet, if any Required Required
3 Tamper Sheet Required Required
4 Display Parameters Required Required
GA / cross sectional drawing of Meter showing all
5 Required Required
the views / sections
Detail of network interface i.e. pin out, standard,
6 Required Required
voltage level etc and its integration requirement.
Samples of each type and rating offered along with
7 2 no's 1 no's
box (Highest rating offered) and communication.
Any software and accessories required for
8 Required Required
installation/ operation of meter
Manufacturer's quality assurance plan and
9 Required
certification for quality standards
10 Type Test reports of offered model/ type/ rating Required
11 BIS certificate Required
12 Complete product catalogue and user manual. Required
13 Customer Reference List Required
14 Recommended list of spare and accessories Required
Specification documents containing all parameters,
15 Services, Methods in addition to companion Required
specification of IS 15959 (part 2).
16 Program for production and testing (A) Required Required

Page 361 of 473

 17 Makes of components Required Required
18 Detailed installation and commissioning instructions Required Required
19 As Built Drawing Required Required
Operation and maintenance Instruction as well as
20 Required Required
trouble shooting charts/ manuals
Inspection and test reports, carried out in
21 Required
manufacturer’s works
22 Routine Test certificates Required
23 Test certificates of all bought out items Required
24 Meter Seal data Required
25 Mapping of meter serial no to Communication card. Required
Other documents:
a. Completely filled-in Technical Parameters
b. General arrangement drawing of the meter
c. Rating plate
d. Terminal Block dimensional drawing
26 e. Mounting arrangement drawings Required Required
f. Meter box drawing and dimensions
g. Display parameter
h. PIN configuration of Optical to RJ11
connector
i. Manual and SOP/DWI for operation

16.0 Delivery
BSES

Dispatch of Material: Vendor shall dispatch the material, only

after the Routine Tests/Final Acceptance Tests (FAT) of the
16.1 Delivery
material witnessed/waived by the Purchaser, and after receiving
written Material Dispatch Clearance (MDC) from the Purchaser.

APPENDIX 6A- GUARANTEED TECHNICAL PARTICULARS

Bidder shall furnish the GTP format with all details against each clause of this specification.
Bidder shall not change the format of GTP or clause description.
Bidder to submit duly filled GTP in hard copy format with company seal.
Clause No. Clause Description Manufacturer’s Reply
1
2
3
4
5

Bidder / Vendor seal / signature ---------------------------

Name of the bidder

Address of the bidder
Name of contact person
Telephone number and email id

Page 362 of 473

APPENDIX 6B- RECOMMENDED ACCESSORIES / SPARES
SL Description of spare part Unit Quantity
1 No
2 No
3

APPENDIX 6C- DEVIATION SHEET

Clause No. Clause Description Deviation Details Manufacturer’s Reply
1
2
3
4
5

APPENDIX 6D- TAMPER AND FRAUD DETECTION/ EVENTS

1. Voltage Related Events:

Persistence
Logic Expression/
Description of Time
Logic Of Event Threshold values
event (Configurable
(Configurable)
)
R Phase
Voltage Missing
(Occurrence/
Absence of potential on any
Restoration)
phase should be logged.
Y Phase Occurrence: If Vpn<10% Occurrence: 5
Restoration of normal supply
Voltage Missing Vref and Ip>10% Ib Min
BSES

shall also be recorded. The

(Occurrence/ Restoration: If Vpn>=10% Restoration: 5
threshold value of voltage
Restoration) Vref and Ip>10% Ib Min
should be programmable at
B Phase
factory end
Voltage Missing
(Occurrence/
Restoration)
Occurrence: If Vpn>10% Occurrence: 5
Over Voltage Meter should log high voltage
Vref Min
(occurrence/ event if voltage in any phase is
Restoration: If Vpn<=10% Restoration: 5
restoration) above a threshold value.
Vref Min
Meter should log low voltage
Occurrence: If Vpn<75% Occurrence: 5
Low Voltage event if voltage in any phase is
Vref Min
(occurrence/ below a threshold value.
Restoration: If Vpn<=75% Restoration: 5
Restoration) Threshold value if factory
Vref Min
programmable.
Meter should log voltage
imbalance event when the
Voltage Occurrence: If Vmax- Occurrence: 5
difference between minimum
Unbalance Vmin>30% Vref Min
and maximum phase voltage is
(Occurrence/ Restoration: If Vmax- Restoration: 5
more than a threshold value.
Restoration) Vmin<=30% Vref Min
Threshold value should be
factory programmable.
R Phase high Meter should log occurrence of Occurrence: If % THD in Occurrence: 5
Voltage high voltage harmonic event Vpn>5% of fundamental. Min
Harmonics when % THD in voltage of Restoration: If % THD in Restoration: 5
Y Phase high phase will be more than Vpn<5% of fundamental. Min

Page 363 of 473

 Voltage threshold value. Threshold
Harmonics value should be factory
B Phase high programmable.
Voltage
Harmonics
2. Current Related Events:
Current
Reverse/ R
Phase Current
Reverse
(occurrence/ Meter should log the event of
Restoration) reversal of C.C polarity.
Y Phase Meter should register energy Occurrence: If Ip = -ve Occurrence:
Current consumed correctly with any direction 5 Min
Reverse one, two or all three current Restoration: If Ip=+ve Restoration:
(occurrence/ coils reversed. This event shall direction 5 Min
Restoration) not be valid in bidirectional
B Phase mode of metering.
Current
Reverse
(occurrence/
Restoration)
R Phase
Current Open
(Occurrence/
Restoration) Occurrence :Vector
Y Phase Meter should log the event of Sum(IR+IY+IB+IN)>20% Ib and Occurrence:
Current Open current coil open. Threshold I<10% Ib 5 Min
BSES

(Occurrence/ value of current should be Restoration : Vector Restoration:

Restoration) programmable at factory end. Sum(IR+IY+IB+IN)< 20% Ib and 5 Min
B Phase I>5% Ib
Current Open
(Occurrence/
Restoration)
Current
Unbalance
(Occurrence/
Restoration)
Meter should log the event of
Occurrence : Vector
current coil shorting/bypass.
Current Bypass Sum(IR+IY+IB+IN)>20% Ib and
Threshold value of current
(Occurrence/ I (any Phase) >5% Ib
should be programmable at
Restoration Restoration : Vector
factory end and also
Sum(IR+IY+IB+IN)>5% Ib
configurable through HES.
If the current in any phase Occurrence:
Over current
exceeds the specified threshold Occurrence: If Ip>Imax 5 Min
(occurrence/
current, meter should log over Restoration: If Ip<=Imax Restoration:
restoration)
current event. 5 Min
R Phase high Meter should log occurrence of
Current high voltage harmonic event Occurrence: If % THD in Occurrence:
Harmonics when % THD in voltage of IP>5% of fundamental. 5 Min
R Phase high phase will be more than Restoration: If % THD in IP Restoration:
Current threshold value. Threshold <5% of fundamental. 5 Min
Harmonics value should be factory

Page 364 of 473

 R Phase high
Current
Harmonics
3. Power Related Events:
Meter shall detect power OFF if
all phase voltages are absent.
Power OFF
This event shall be recorded at
(occurrence/
the time of each power OFF. At
restoration)
the same time power ON event
shall be recorded.
If meter micro detect power off
Abnormal whereas phase voltage is Occurrence: If voltages at
Power Off present than abnormal power meter power supply<10%
NA
(Occurrence/ will be recorded. Meter sall Vref and Vp>20% vref.
restoration) continue to record energy as Restoration:
per phase voltage and current.
4. Other Events:
a. Meter should either be
immune or should log the
events of attempt of tampering
by external magnetic
field as per relevant IS14697/
CBIP 325 with latest
Abnormal amendments.
External b. If the working of meter gets
Magnetic affected under the As per IS
As per IS 14697/ CBIP 325
Influence influence of external magnetic 14697
(Occurrence/ field, meter should
BSES

Restoration) record energy at Imax. Meter

should not compute
MD during this period. The
meter shall record
energy as per actual load once
the magnetic field is
removed.
Neutral
Disturbance- Bidder shall
Meter should log the event
HF, DC and As per manufacturing define
when AC/DC/ Pulsating voltage
Alternating standard. threshold
is injected in neutral circuit.
(occurrence/ values
restoration)
Meter shall able to detect and
log the low PF event if power
factor of the load found in
between 0.2 to 0.5 for a load
Low Power above than a % threshold value 10% of I
Factor for a threshold time value. basic
Event shall restore if PF factor
of load remain out of range 0.2
to 0.5 for a load above than %
threshold value for
Plug in Meter should log the removal of
Communication communication card. Meter
module removal should also log insertion of By NC switch/ sensor

Page 365 of 473

 (Occurrence/ communication card.
Restoration)
Configuration
change to
“Forwarded”
only" mode/
“Import and Meter should log the change in
Export” mode metering mode configuration.
Overload
(Occurrence/ Meter should able to log the
Restoration) status of overload in KW
Meter with communication card
HV Spark
should be immune or log the
(Occurrence/
event in the case of application Immediately NA
restoration)/
of ESD upto and including 35
Jammer
KV.
Meter should log event of high
Occurrence: If IN > 50% of Occurrence:
neutral current if measured
High neutral average phase current 5 Min
neutral current should be more
Current Restoration: If IN < 50% of Restoration:
than predefined threshold
average phase current 5 Min
value.
Meter shall log the event if Occurrence:
difference between 5 Min
Distorted PF
displacement PF and actual PF Restoration:
is more than a predefined value 5 Min
Meter shall log voltage, current,
Time Based
PF and energy consumption on As per predefined time NA
Event Stamp
a predefined time
BSES

If temperature is more than

Temperature 60deg C. Meter has to log as - -
an event and sent alert
5. Non Roll over events:
Event Description
Occurrence of cover open
6. Transaction Related Events:
Detail of Transaction
Real Time Clock- Date and Time
Demand Integration Period
Profile Capture Period
Single Action schedule for billing date
Activity calendar for time zones
New firmware activated
Load Limit (Kw) Set
Enable Load Limit Function
Disable load limit function
LLS secret (MR) change
HLS key (US) change
HLS key (FW) change
Global key change
ESWF change
MD reset
Note:
1. Event ID’s shall be defined as per BSES specification/ IS 155959 (part 2). Approval shall be
taken from BSES prior to manufacturing for Event ID’s

Page 366 of 473

2. Programming of threshold values should be possible from remote via proper authentications.
3. Logics of tampers can be changed/ upgraded via firmware up gradation from remote via
proper authentication.
4. All the programming changes/ firmware up gradations shall be logged along-with date and
time stamp in meter as well as on HES

BSES

Page 367 of 473

Appendix 7: Technical Specifications for Polycarbonate Security Seals

1. Scope of Supply

The scope of supply includes Design, Engineering, Manufacturing, Inspection & Testing at
manufacturer’s work before dispatch, packing and delivery of material to BSES stores and
submission of documents to purchaser.

2. Standards & Codes

Polycarbonate seals shall be designed, manufactured and tested in accordance with the latest
edition of following standards
S No. Standard Title of the Standard
1 Latest Edition Indian Electricity Act 2003
2 Latest Edition CEA regulations on Installation and Operation of Meters
3 IS14434 Polycarbonate moulding and extrusion materials
4 IS15707 Testing, Evaluation, Installation and Maintenance of AC
electricity meters– Code of practice
5 IS9792 Guide for testing, calibration and maintenance of AC
electricity meters
6 IS6528 Stainless Steel Wire
7 ASTMD792 Specific Gravity Test
8 ASTMB117 Salt Spray Test

3. Service Conditions
Polycarbonate seals to be supplied against this specification shall be suitable for satisfactory
operation under the following conditions-
S No. Standard BSES
Title of the Standard
3.1 Average grade Heavily polluted, Dry
atmosphere
3.2 Maximum altitude 1000M
above sea level
3.3 Relative Humidity 100%
Ambient air Highest 50 Deg C
3.4 temperature Average 40 Deg C
Minimum0DegC
3.5 Operating temperature 0 Deg C – 50 Deg C
3.6 Rainfall 750mmconcentratedinfour months

4. Construction & Design Features

Compliance
S No. Parameters Technical Requirements by BSES
by Bidder
4.1 Seal type a. The seals shall be anchor type, suitable for
effectively sealing the meters, meter boxes and
other enclosures.
b. The seals shall be suitable for outdoor
application.
c. Seal should be weather and UV resistant
d. It should not be possible to tamper seal before
and after installation.
e. Application: Security sealing of energy meters
and enclosures.
4.2 Material of Virgin Polycarbonate
Seal

Page 368 of 473

 Compliance
S No. Parameters Technical Requirements by BSES
by Bidder
4.3 Melting Minimum 280 Deg C to 295 Deg C
Temperature
4.4 Seal design a. The seals shall be of padlock type design, easy
to install without use of any tool.
b. Once installed it shall not be possible to open
forcibly without completely destroying/breaking
the body of the seal.
c. Once opened, it shall not be re-used.
d. In the event any attempt is made to open the
seals forcibly, a visual damage shall occur on
body of seal.
4.5 Housing and a. Housing of the seal shall be of polycarbonate.
locking b. Corrosion resistant stainless steel shall be used
in the locking mechanism system.
c. These materials shall be suitable for use in
humid tropical conditions as stipulated in Clause
3.0.
d. Collar of Male part should be of smaller size & sit
4.6 Colour of a. Seals shall be transparent (See through type),
seal which shall give complete visualization of its
fixing mechanism and shall show clear indication
if tempered or coloured seals as per instruction
and approval of BSES
b. Female part of the seal shall be colourless and
male part of the seal shall be coloured in Blue,
Orange, Pink, Green, Yellow as per BSES
BSES

requirement.
4.6.1 Blue Seal Seal sent to meter manufacturer for Sealing meter
body
4.6.2 Orange, Seal will be utilized for following applications:
Pink, Green,
a. T Cover
Yellow Seal
b. Meter
c. Box/Enclosure
d. Busbar Box
e. Metering Cubicle
f. Other sealing applications
4.7 Marking on a. Ten-digit serial number shall be laser printed on
seal both male and female portion of the seal.
b. BSES & PO No. shall be moulded on one side
and Manufacturing month and year to be
moulded on the other side of seal.
c. In addition to above marking a paper sticker
shall be provided on seal with following
information:
- Seal Serial No
- QR Code
- (BYPL/BYPL)
4.8 Sealing wire a. Non corrosive non-magnetic stainless steel
twisted wire shall be used.
b. Grade of stainless steel shall be SS-304.
4.9 Length of
sealing wire

Page 369 of 473

 Compliance
S No. Parameters Technical Requirements by BSES
by Bidder
4.9.1 Blue Seal 160mm
4.9.2 Orange Seal 225mm
4.10 Diameter of The diameter of each individual strand
SS wire wire shall be 0.45mm+ 0.01 mm and overall diameter
of seal wire shall be 0.9mm+0.05mm, so that it can
easily inserted into the female portion where the
diameter of the hole shall be 1.0mm+0.1mm.
4.11 Locking Two Anchor type for Blue, Orange, Green, Pink and
arrangement Four Anchor type for yellow seal (Pre temper feature
shall be referred) Double locking with two wire holes
for two times wire passing the seal.
4.12 Seal wire The seal wire used for the above size of seals shall
application be in built in connecting male and female part of the
seal. The application of the seal wire is to insert seal
wire and through the hole via female part and insert
the male part into female part by applying thumb
Pressures to lock the seal.
4.13 Seal The Seal shall be made in such a way that, it can be
installation & easily locked with the help of finger and thumb
security pressing and no tools shall be required to close the
seal in the laboratory or at site.
After inserting the seal wire through female part, the
cap of the male part shall be fitted in the female part
in such a way that it should not leave any space to
avoid insertion of any sharp tools for opening of seal
body of the Female part in hot or cold condition.
BSES

4.14 Patent a. The manufacturer should have a legal valid

requirement patent certificate (seal from the manufacturer
who has official right to manufacture the seal) as
on date of tender submission in accordance with
the provisions of the Patents Act, 1970 and as
per CEA regulation for manufacturing of the seal
as per CEA regulation.
b. Documentary proof for the above shall be
forwarded along with the offer
c. In case of patent revocation supplier shall
intimate BSES immediately in writing.

5. Construction & Design Features

5.1 Type test The type test reports for below mentioned tests as per IS / IEC/ASTM
standards shall be submitted. Type test reports shall not be older than
5 years. Type test conducted either from CPRI/ERDA will be treated
as valid.
a. Visual Inspection of whole lot.
b. Dimensional Verification.
c. Tensile Strength
d. Pull Out Test
e. Chemical Test
f. Heat Resistance Test
g. Identification of Base Polymer
h. Melting Point
i. Temperature Withstand Test

Page 370 of 473

 j. Salt Spray Test
k. Specific Gravity

If valid type test reports are not available with the bidder, then they
shall arrange to carry out all the type tests as per relevant IS on
randomly selected sample from our lot from CPRI/ERDA without any
price implication.
5.2 Routine test Raw material certificates and Routine test certificates in accordance
with relevant IS, shall be submitted during the inspection.
5.3 Acceptance Sampling & following acceptance tests in accordance with relevant
Tests IS/ASTM shall be conducted during the inspection at manufacturer’s
works:-
a. Visual Inspection of whole lot.
b. Dimensional Verification.
c. Tensile Strength
d. Pull Out Test
e. Chemical Test
f. Heat Resistance Test
g. Identification of Base Polymer
h. Melting Point
i. Test for exposure to UV radiation

In case the facility to conduct any of the above mentioned tests is

not available at manufacturing works, the same shall be conducted
at NABL accredited laboratory without any price implication

6. Packing, Shipping, Handling & Site Support

6.1 Packing Protection Against corrosion, dampness, heavy rains, breakage
BSES

And vibration
6.2 Packing for Seals 50 no's seals in small transparent packet Two packets of
50 seals shall be packed in hard board boxes of 100nos
seals
The serial numbers of the seals shall be clearly indicated
on the box. Robust non returnable packing case with all
the above protection & identification
Label
6.3 Packing Identification On each packing case, following details are required:
Label
6.3.1 Individual serial number
6.3.2 Purchaser’s name
6.3.3 PO number (along with SAP item code, if any) & date
6.3.4 Equipment Tag no.(if any)
6.3.5 Destination
6.3.6 Manufacturer /Supplier’s name
6.3.7 Address of Manufacturer/Supplier/it’s agent
6.3.8 Month & year of Manufacturing
6.3.9 Case measurements
6.3.10 Gross and net weights in kilograms
6.3.11 All necessary slinging and stacking instructions
6.4 Shipping The seller shall be responsible for all transit damage due
to improper packing.
6.5 Handling and Storage Manufacturer instruction shall be followed.
6.6 Detail handling & storage instruction sheet/manual to be furnished before

Page 371 of 473

 commencement of supply.

7. Document & Sample Submission

The seller has to submit the following documents and sample along with technical bid:
7.1 Completely filled GTP as per clause Appendix 7A of this specification
7.2 Clause wise compliance sheet as per BSES specification
7.3 Detailed reference list of customers using the offered product during the last 3
years with similar design and rating
7.4 GA/cross sectional drawing of seal showing all the views/sections/parts
7.5 Manufacturer’s quality assurance plan and certification for quality standards
7.6 Five numbers of non-returnable samples of the seal shall also be submitted with
the offer for evaluation of the product.

8. Deviation

List of deviations shall be stated in writing with the tender by reference to the Specification clause
/GTP/Drawing. In absence of such a statement, requirements of the Specification shall be
assumed to be met without exception by the vendor.

APPENDIX 7A: GUARANTEED TECHNICAL PARTICULARS OF POLYCARBONATE

SECURITY SEAL

Clause no of Specification Description of Clause Compliances by Bidder

BSES

Page 372 of 473

Appendix 8: Technical Specifications for Hologram Security Seals and TF Seals

1. SCOPE OF SUPPLY
The scope of supply includes Design, Engineering, Manufacturing, Inspection & Testing of
following items at manufacturer’s work before dispatch, packing and delivery of material to BSES
stores and submission of documents to purchaser:
a. Hologram Meter Seal
b. Technical Feasibility Paper Sticker (TF Sticker)

2. STANDARDS & CODES

Hologram and TF seals shall be designed, manufactured and tested in accordance with the latest
edition of following standards-
S
STANDARD TITLE OF THE STANDARD
No.
2.1 Latest Edition Indian Electricity Act 2003
2.2 Latest Edition CEA regulations on Installation and Operation of Meters
2.3 IS 15707 Testing, Evaluation, Installation and Maintenance of AC
electricity meters – Code of practice
2.4 ASTM D 792 Specific Gravity Test
2.5 ASTM B 117 Salt Spray Test

3. SERVICE CONDITIONS
Hologram seals to be supplied against this specification shall be suitable for satisfactory
operation under the following conditions-
3.1 Average grade atmosphere BSES
Heavily polluted, Dry
3.2 Maximum altitude above sea level 1000M
3.3 Relative Humidity 100%
Highest 50 Deg C Average 40
3.4 Ambient air temperature Deg C
Minimum 0 Deg C
3.5 Operating temperature 0 Deg C - 50 Deg C
3.6 Rainfall 750mm concentrated in four
months

4. CONSTRUCTIONAL & DESIGN FEATURES

S No. Parameters Technical Requirements by BSES
4.1 Seal type Hologram Seal: The seals shall be tamper proof type, suitable
for effectively sealing the meters, meter boxes and other
enclosures. The seals shall be suitable for outdoor application.
TF Sticker: This sticker shall be suitable to fix on wall and use in
outdoor conditions.
4.2 Seal design a. The seal must be self-destructive type, suitable for single
Construction - use having security hologram throughout the length.
Hologram Seal b. Seal shall have adhesive of sufficient strength to avoid
pealing off under extreme temperature and environmental
conditions. It must be suitable for all surfaces.
c. Seal must be UV stabilized and suitable for minimum 10
years of service in the temperature range of -5 Deg C to
65 Deg C.
d. An additional feature of electrical continuity line shall also
be provided.
e. The seal shall be designed for a single use only.

Page 373 of 473

 [Link] seals must be constructed in the form of multilayered
combinational films.
g. Each seal will have hologram, continuous serial number,
security codes, bar codes, BSES logo and hidden mark
visible under UV only.
h. The Unique serial number shall have 2 alphabets followed
by 6 digits.
i. Security cuts to be provided to ensure seal tears off when
removed. Please refer Appendix 8B for details.
4.3 Seal Design and a. The seal must be self-destructive type,
Construction- TF b. Seal shall have adhesive of sufficient strength to avoid
Sticker peeling off under extreme temperature and environmental
conditions. It must be suitable for all surfaces.
c. Seal must be UV stabilized and suitable for minimum 10
years of service in the temperature range of -5 Deg C to
65 Deg C.
4.4 Drawing and Please refer enclosed Appendix 8B
Dimensions on
hologram seal
4.5 Patent The manufacturer should also have a legal patent certificate in
Requirement accordance with the provisions of the Patents Act, 1970 and as
(Only for per CEA regulation for manufacturing of the seal. Documentary
Hologram Seal) proof for the above shall be forwarded along with the offer.

5. INSPECTION & TESTING

5.1 Type test The type test reports for below mentioned tests as per IS /
IEC/ASTM standards shall be submitted. Type test conducted
either from CPRI/ERDA/ NABL accredited lab will be treated as
BSES

valid.
i) Visual Inspection of whole lot.
ii) Dimensional Verification.
iii) Chemical Test
iv) Heat Resistance Test
v) Test for exposure to UV radiation
vi) Peeling off test/ Adhesive Test
If valid type test reports are not available with the bidder, then
they shall arrange to carry out all the type tests as per relevant
IS on randomly selected sample from our lot from CPRI/ERDA
without any price implication.
5.2 Routine test Raw material certificates and Routine test certificates in
accordance with relevant IS, shall be submitted during the
inspection.
5.3 Acceptance tests Sampling & following acceptance tests in accordance with
relevant IS/ASTM shall be conducted during the inspection at
manufacturer’s works: -
vii) Visual Inspection of whole lot.
viii) Dimensional Verification.
ix) Chemical Test
x) Heat Resistance Test
xi) Test for exposure to UV radiation
xii) Peeling off test/ Adhesive Test
In case the facility to conduct any of the above mentioned tests
is not available at manufacturing works, the same shall be
conducted at NABL accredited laboratory without any price
implication.

Page 374 of 473

6. PACKING, SHIPPING, HANDLING & SITE SUPPORT
6.1 Packing Protection Against corrosion, dampness, heavy rains, breakage
and vibration
6.2 Packing for Seals Seals will be supplied in roll form.
6.3 Packing Identification Label On each packing case, following details are required:
6.3.1 Serial number
6.3.2 Purchaser’s name
6.3.3 PO number (along with SAP item code, if any) & date
6.3.4 Equipment Tag no. (if any)
6.3.5 Destination
6.3.6 Manufacturer / Supplier’s name
6.3.7 Address of Manufacturer / Supplier / it’s agent
6.3.8 Month & year of Manufacturing
6.3.9 Case measurements
6.3.10 Gross and net weights in kilograms
6.3.11 All necessary slinging and stacking instructions
6.4 Shipping The seller shall be responsible for all transit damage
due to improper packing.
6.5 Handling and Storage Manufacturer instruction shall be followed.
6.6 Detail handling & storage instruction sheet / manual to be furnished before
commencement of supply.

7. DOCUMENT & SAMPLE SUBMISSION

The seller has to submit the following documents and sample along with technical bid:

7.1 Completely filled GTP as per clause Appendix 8A of this specification

7.2 Clause wise compliance sheet as per BSES specification
BSES

7.3 Detailed reference list of customers using the offered product during the last 3 years
with
similar design and rating
7.4 GA / cross sectional drawing of seal showing all the views / sections / parts
7.5 Manufacturer’s quality assurance plan and certification for quality standards
7.6 Five numbers of non returnable samples of the seal shall also be submitted with the
offer for evaluation of the product.

8. DEVIATION
List of deviations shall be stated in writing with the tender by reference to the Specification clause
/ GTP/ Drawing. In absence of such a statement, requirements of the Specification shall be
assumed to be met without exception by the vendor.

APPENDIX 8A: GUARANTEED TECHNICAL PARTICULARS

SL Clause no of Specification Compliances by Bidder

Page 375 of 473

APPENDIX 8B: DRAWING

A. Hologram Seal

B. Hologram Seal

BSES

Page 376 of 473

Appendix 9: List of PPE & TOOLS

Following Standard Personal Protective Equipments (PPE’s) shall be provided by the Bidder &
shall be available with working manpower at any point of time:

I. SAFETY PERSONAL PROTECTIVE EQUIPMENTS (PPE’s)

1. SAFTEY HELMET WITH VISOR & Live Line Detector (IS :2925-1984 , EN : 166 CE
MARKED)
2. GOGGLES
3. SAFTEY SHOES (IS:15298),Composite Toe work ISI marked Boots (Static Proof)
4. INSULATED GLOVES (EN:60903 CE MARKED)
5. LADDER (FOLDABLE TYPE 2/3/4 LAYER)
6. RUBBER MAT (FOR SHOCK RESISTANT UPTO 11KV)
7. REFLECTIVE SAFETY JACKET
8. FIRST AID BOX
9. TOOLS WITH PROPER INSULATION (ISI marked)
10. EARTHING ROD
11. EARTHING CHAINS & SHORTING LEADS

II. Tools: Following Standard Tools & Tackles shall be provided by the Bidder & shall be
available with working manpower at any point of time:

1. INSULATED PLIER
2. WIRE STRIPPING PLIER
3. SCREW DRIVER SET
4. INSULATED SPANNER SET
5. SEAL PUNCHING PLIER BSES

6. CRIMPING TOOL WITH DIE SET

7. CUTTER
8. DRILL MACHINE (HAMMER)
9. DRILLING BIT SET
10. CABLE BENDING TOOL
11. HAMMER
12. PRE DEFINE TORQUE SCREW DRIVER
13. PHASE TESTER
14. TOOL BOX/ BAG
15. DOUBLE TEST LAMP
16. MEASURING TAPE
17. TORCH/ EMERGENCY LIGHT
18. HACKSAW BLADE WITH EXTRA BLADES
19. ALLEN KEY SET
20. SOCKET SET

Page 377 of 473

Appendix 10: Bidder Store Management

1. BYPL issues material to Bidder & which is utilized for executing various orders, the orders
includes the consumer applications and BYPL initiated.
2. The Bidder store is therefore key place for material up keeping and its reconciliation.
3. The mismanagement of the material often converted into loss of material & penalty.
4. It is also advised to maintain first in first out policy for the material issued.
5. Non-moving items also need to be utilized in other projects/return to store.
6. Proper sorting of material, tools and PPE also ascertains on time execution of orders.
7. It also ensures Environmental & Health concerns of the team working there.
8. Displaying the available stock on board also initiated the requirement on time.
9. Labeling the material on stack/rack ensures easy availability.
10. Separate stacking for scrap ensures proper counting of the material.
11. Vehicle management and parking is needed to be ensured at store.
12. Electricity connection (Meter) & water must be maintained in proper way at store.
13. For security of material at stores, Bidder shall install CCTV in their stores with backup storage
data of 1 month.
14. Bidder shall manage Store & Material inventory as per the SOP of BYPL.

BSES

Page 378 of 473

Appendix 11: Standards, Specifications and Compliances

Standards & Specifications for Smart Meters

The functionality and specification of these smart meters, RF Mesh Communication NAN module,
Gateway/Router/Access Points (unless otherwise mentioned in this document) need to be in
accordance with the following standards and/or regulations with latest amendments:
a) IS 16444 (Part 1& 2): A.C. Static Direct Connected Watthour Smart Meter Class 1, 2 & 0.5–
Specification and its amendment.
b) IS15959 (Part 1 & 2): Data exchange for Electricity Meter Reading, Tariff and Load Control & its
latest amendments.
c) CEA Regulations on “Installation and Operation of Meters’, 2006 tobe read in conjunction with
amendments dated 04 June 2010 and 26 November 2014.
d) Smart meter specifications as mentioned in CEA Guidelines on “Functional Requirements of
Advanced Metering Infrastructure (AMI) in India” issued in August 2016.
e) Meter should comply with CBIP 325.
f) Communication Layer Protocol
 Application Layer- IS 15959 (Part 1) and IS 15959 (Part 2)
 Transport Layer- TCP/UDP
 Network Layer- IPv6 RPL
 Adaptation Layer- 6LoWPAN RFC 6282

Certifications and Standards for Communication Technologies

1. Compliance
 Compliance with relevant communication standards including:
 3GPP Standards: Compliance with 3GPP Release 13 and above for NB-IoT
BSES

 The RF Mesh Communication Devices shall comply to the following standards: IEEE
802.15.4 – IEEE standard for Information Technology – Telecommunications and
Information Exchange between Systems – Local and Metropolitan Area Networks –
Specific Requirements Part 15.4: Wireless Medium Access Control (MAC) and
Physical layer (PHY); IEEE 802.15.4g – IEEE Standard for Smart DISCOM Networks
or any other equivalent standard /alliance.
 IETF Standards: Compliance with IETF RFCs for MPLS (e.g. RFC 3031, RFC 4364,
etc)
 Certification in network security standards (e.g., ISO 27001 for information security
management).
 Adherence to local and international regulatory requirements, including TRAI guidelines,
Wireless Planning & Coordination (WPC) Wing of the Ministry of Communications and
Information Technology and DoT regulations in India.
 Comply with the Department of Telecommunications, Ministry of Communications which
prescribes for Mandatory Testing and Certification of Telecommunication Equipment
(MTCTE) for Smart meters from Indian Accredited labs and submit certificate from TEC
before supply or as per latest amendments published by Govt of India as per notification F.
No. 5-2/2024-TC/TEC dated 01.07.2024 issued by Deptt. Of Telecommunication, Govt. of
India.

2. Quality Management
 ISO 9001 certification for quality management systems
 ISO 20000 certification for IT service management

RF Mesh Network Requirements

Page 379 of 473

1. Network Design
 Self – Healing Capability: The network must automatically reroute traffic around failed
nodes, ensuring no single point of failure.
 Scalability: Support for incremental deployment from hundreds to 5 million meters without
significant degradation in performance.
 Range and Coverage: Each RF node should cover a minimum of 1 km in urban
environments, accounting for building density and interference.
 Network Topology: Support for both point-to-point and point-to-multipoint configurations.
 Interference Management: Use of frequency hopping and adaptive modulation to mitigate
interference.
 Network Mapping: Complete network mapping of the deployment area to identify and
resolve dead spots.

2. Performance
 Latency: End-to-end latency should not exceed 100 ms for high-priority messages.
 Reliability: Data delivery success rate of at least 99.9%.
 Throughput: Support for a minimum data rate of 250 kbps per node.
 Energy Efficiency: Optimization for low power consumption to extend the battery life of
smart meters.

3. Security
 Encryption: Use of AES-256 encryption for all RF communications.
 Authentication: Mutual authentication between smart meters and data concentrators using
secure key exchange mechanisms (e.g., PKI).
 Tamper Detection: Immediate alerts for physical tampering or unauthorized access
attempts of cellular modules
 Intrusion Detection: Real-time monitoring and alerts for potential network breaches or
BSES

anomalous behaviour.

4. Management
 Monitoring: Real-time monitoring of network health, performance metrics, and node status
 Diagnostics: Tools for remote diagnostics, fault detection, and performance analysis.
 OTA Updates: Support for secure over-the-air firmware updates and configuration
changes.
 Reporting: Automated generation of performance and health reports, with customizable
reporting intervals.

Cellular Network (4G/NB-IoT with Fall back to be decided by AMISP) Requirements:

1. Coverage and Connectivity

 4G/NB-IoT Coverage: Comprehensive 4G/NB-IoT coverage for all urban and suburban
areas of New Delhi.
 2G Fallback: Automatic fallback to 2G in areas with poor 4G/NB-IoT coverage, ensuring
uninterrupted connectivity.
 Seamless Handover: Support for seamless handover between 4G, NB-IoT, and 2G
networks without packet loss.
 Network Mapping: Pre-deployment site surveys and network mapping to identify dead
spots and ensure optimal placement of cellular towers, boosters, repeaters, etc.

2. Performance and Reliability

 Data Rates:Minimum data rate of 1 Mbps for 4G and 50 kbps for NB-IoT.
 Latency: Maximum latency of 50 ms for 4G and 100 ms for NB-IoT for critical data
transmissions.

Page 380 of 473

  Availability: Network availability of at least 99.95%, with redundancy mechanisms in place.
 Connection Density: Ability to support high connection density, with at least 100,000
devices per square kilometre.
 Redundancy: Multiple carrier support and redundant backhaul connections to ensure
reliability
3. SIM Management
 Centralised Platform: Centralized SIM management platform for provisioning, activation,
deactivation, and monitoring of SIM Cards
 Real-Time Monitoring: Real-time tracking of SIM usage, performance metrics, and
connectivity status.
 Multi-Operator Support: Support for multiple mobile network operators to ensure optimal
coverage and redundancy.
 Lifecycle Management: Full lifecycle management of SIM Cards, including provisioning,
activation, deactivation and replacement
 SIM Security: Secure storage and management of SIM credentials and encryption keys.

4. Security:
 Encryption: Use of IPsec or similar encryption protocols for secure data transmissions over
cellular network
 Authentication: Robust SIM authentication mechanisms such as IMSI and IMEI validation
 Firmware Security: Secure boot and secure firmware update mechanisms for all cellular
modules
 Data Integrity: Mechanisms to ensure data integrity and protection against tampering or
spoofing.

5. Quality of Service (Qos)

 Traffic Prioritization: Support for QoS to prioritize critical data traffic (e.g., outage alerts,
BSES

control commands)
 Bandwidth Allocation: Dynamic bandwidth allocation to ensure optimal performance for
high-priority applications.
 Latency and Jitter Management: Mechanisms to minimize latency and jitter for time-
sensitive applications.

MPLS Connectivity Requirements

1. Network Design
 Redundancy: MPLS infrastructure with redundant paths and automatic failover capabilities.
 Path Diversity: Use of diverse physical paths to ensure resilience against single points of
failure.
 Scalability: Support for scalable bandwidth from 1 Gbps to 10 Gbps, accommodating future
growth.

2. Performance
 Bandwidth Guarantees: Minimum guaranteed bandwidth of 1 Gbps per MPLS Link
 Latency: End-to-end latency not exceeding 10 ms within the MPLS network.
 Jitter: Jitter should not exceed 5 ms to support real-time applications.
 Packet Loss: Packet loss should be less than 0.1%

3. Security
 Encryption: Use of MPLS VPNs with IPsec encryption for secure data transport
 Access Control: Strict access control policies for MPLS endpoints, including ACLs and
firewall protection.

Page 381 of 473

  Traffic Segregation: Logical separation of different types of traffic (e.g., metering data,
control commands) to prevent interference and enhance security.

4. Management
 NMS Integration: Integration with a centralized Network Management System (NMS) for
end-to-end visibility and control.
 Performance Monitoring: Continuous monitoring of MPLS link performance, including
bandwidth utilization, latency, and packet loss.
 Fault Management: Automated fault detection, alerting, and resolution mechanisms.
 Service Level Agreements (SLAs): Monitoring and reporting of SLA compliance, with
penalties for non-compliance.

Network Management System (NMS) Requirements

1. Functionality:
 Centralized Management: Unified NMS for managing all network components (RF mesh,
cellular, MPLS).
 Real-Time Monitoring: Real-time monitoring and visualization of network performance,
connectivity status, and health metrics.
 Alerts and Notifications: Configurable alerts and notifications for critical events and
performance thresholds.

2. Performance and Scalability:

 Scalability: Support for up to 5 million smart meters and associated network devices.
 High Performance: Capable of processing and analysing large volumes of data in real-
time.
 Redundancy: Redundant architecture to ensure high availability and disaster recovery
BSES

capabilities.

3. User Interface:
 Intuitive Interface: User-friendly interface with customizable dashboards and reports.
 Role-Based Access: Role-based access control to restrict access based on user roles and
responsibilities.
 Reporting: Automated generation of detailed performance and health reports, with
customizable reporting intervals.

4. Integration:
 Interoperability: Seamless integration with existing utility systems (e.g. SCADA. OMS,
billing systems)
 APIs: Support for open APIs to enable interoperability with third party tools and platforms
 Data Analytics: Integration with data analytics platforms for advanced data analysis and
reporting

Security Requirements

1. End – to End Security

 Encryption: End-to-end encryption (e.g., TLS, IPsec) for all data transmissions within the
communication network.
 Authentication: Multi-factor authentication (MFA) for network access, including smart meter
authentication.
 Access Control: Role-based access control and least privilege principles for network
administration.

Page 382 of 473

2. Device Security:
 Secure Boot: Ensure all network devices (smart meters, gateways, routers) support secure
boot to prevent unauthorized firmware modifications.
 Firmware Updates: Secure and authenticated firmware update mechanisms to protect
against malicious updates.
 Tamper Resistance: Physical tamper detection mechanisms for all network devices, with
immediate alerts on detection

3. Network Security
 Firewalls and IDS/IPS: Deployment of firewalls and intrusion detection/prevention systems
to protect network perimeters.
 Regular Audits: Regular security audits and vulnerability assessments to identify and
mitigate potential threats.
 Secure Management Protocols: Use of secure management protocols (e.g., SSH, HTTPS)
for network administration.

Operational and Maintenance Requirements

1. Monitoring and Maintenance:

 Continuous Monitoring: 24/7 monitoring of network performance and security
 Field Support: On-site support for troubleshooting and maintenance

2. Support and Training

 24*7 Technical Support: Creation of Help desk to provide round the clock support for all
network related issues
 Comprehensive Training: Undertaking training programs for field staff for on field resolution
and use of network management system (NMS)
BSES

 User Manuals: Utility and on field staff to be provided with detailed user manuals including
SOPs and technical documentations.
 Third Party Audits: Regular third – party audits to verify network performance and security.

Page 383 of 473

Appendix 12: Minimum Specifications for Firewall

Firewall (Unified Threat Management (IPS) Next Gen Firewalls with HA) should have minimum
requirement.

1. Network security appliance should support "Stateful" policy inspection technology. It should
also have application intelligence for commonly used TCP/IP protocols like telnet, ftp etc.
2. The proposed vendor must have a track record of continuous improvement in threat detection
(IPS) and must have successfully completed NSS Labs NGFW Methodology v7.0 testing with a
minimum exploit blocking rate of 99%.
3. OEM should be in leaders quadrant of Gartner’s -- in Enterprise Firewall Magic Quadrant as
per the latest report
4. Appliance shall be ICSA certified for Firewall, IPS & Gateway AntiVirus functionalities
5. Minimum 8 x 1GE RJ45 inbuilt interfaces, 8 x 1GE SFP interface and 2 x 10GE SFP+ interface
slots from day one
6. The Appliance should have USB & Console Ports and dedicated HA ports in addition to
requested data ports
7. The Firewall should be on multiprocessor architecture with minimum support of 7,500,000
concurrent sessions, and 300,000 new sessions per second from day one and Firewall Latency
should not be more than 3 µs
8. Minimum IPS throughput of 5000 Mbps for real world traffic or enterprise mix traffic
9. Minimum Threat Prevention Throughput (measured with Application Control and IPS and Anti-
Malware enabled) of 5000 Mbps for real world traffic or enterprise mix traffic
10. IPSec VPN throughput: minimum 20 Gbps
11. Application control throughput 14Gbps (64K HTTP)
12. Proposed solution must support minimum 6.5 Gbps of SSL Inspection throughput
13. Proposed solution must support minimum 10 virtual firewall from day one
14. Firewall should provide application inspection for LDAP, SIP, H.323, SNMP, FTP,SMTP,
BSES

HTTP, DNS, ICMP, DHCP, RPC,SNMP, IMAP, NFS etc

15. IPv6-enabled inspection services for applications based on HTTP, FTP, SMTP, ICMP, TCP,
and UDP
16. Allows secure deployment of next-generation IPv6 networks, as well as hybrid environments
that require simultaneous, dual stack support of IPv4 and IPv6
17. The firewall should support transparent (Layer 2) firewall or routed (Layer 3) firewall Operation
18. Management & Reporting functionality
19. Other support like- Web-Filtering, Application-Control & Gateway level DLP from day one
20. Anti-Virus & Anti Bot Integrated IPS Features Set

Page 384 of 473

20. Annexure

Annexure A System Sizing Requirement

The system shall be designed as per the technical parameters defined in this specification and as
specified in this Annexure.

The AMI system (MDMS, Historian etc.) shall be suitably sized based on expansion requirements
mentioned in clause 32 given in Section 6: Project Requirements and Scope of Work.

The auxiliary memory and utilization of any of the Servers shall not exceed 30% and 25%
respectively of their delivered capacity at any time even under peak loading conditions involving a
combination of the following -
 400 alarms per minute for 5 minutes.
 30 concurrent display requests from 15 users. Including graphical trends
 Restoration of 100%-meter data after system failure.
 VEE and billing determinant calculations involving 10,000 consumer meters
 System activity alarms.

This memory utilization includes the memory used for storage of data (including expansion
requirement defined in above para) for the defined duration as specified in the Technical
Specification. The system architecture and the network design shall have the ability to handle the
growth with respect to functions, and user as defined.

The AMI system (MDM, Analytics, Prepaid Billing etc.) shall be suitably sized based on expansion
requirements mentioned in RFP.
BSES

CSP should offer auto-scaling of the compute resources based on the defined threshold of
resource utilization. There should be a minimum and maximum limit defined for auto-scaling for a
workload

This memory utilization includes the memory used for storage of data (including expansion
requirement defined in above para) for the defined duration as specified in the Technical
Specification. The system architecture and the network design shall have the ability to handle the
growth with respect to functions, and user as defined.

Indicative total and Concurrent User (excluding the integration, backend users) but not limited to:

1. HES (Total 50 user) Concurrent Max : 20

2. MDMS (Total 350 user) Concurrent Max : 100
3. Analytics (Total 150 user) Concurrent Max : 50
4. SMOC (Total 50 user) Concurrent Max : 20
5. WFM (Total 1500 users) Concurrent Max : 500
6. Consumer Portal (Total 30 L) Concurrent Max : As per industry standard
7. Mobile App (Total 30 L) Concurrent Max : As per industry standard
8. Smart Prepaid Billing (SPBM) (Total 300) Concurrent Max : 100
9. Sizing of Cloud / AMI Solution (Indicative) : Given below

S. No. Parameter Description Value

1 Devices/Assets Meters 5 million Meters
2 Internal Users Number of users Approximately 500 users
3 Network Network Connectivity within IT Minimum 10/100 GBPS
Connectivity Infrastructure of Cloud Services Connectivity between
such as Network, Server, Network, Servers, Storage

Page 385 of 473

S. No. Parameter Description Value
Storage interconnectivity
4 CPU Utilization Utilization upper limits of VM’s Between 60% to 70%
Limit
5 Compliance to Cloud Compliance Standards Compliance to Security
Standards Security Standards of ISO 27001
for Cloud Service Provider
(CSP). CSP shall conform
to the standards specified
by MeitY, Govt. of India as
applicable.
6 Storage 1. Read 1. Read 10000 IOPS
2. Write 2. Write 5000 IOPS
3. Volumes 3. Disc > 1 TB
Media SSD
7 Database Transaction 50000 IOPS
Performance
8 Scalability Upto10 million Meters

BSES

Page 386 of 473

Annexure B Details of ESB Architecture

[Link]. Parameters Description

1 Architecture Design
2 Core Functionalities
3 Implementations

BSES

Page 387 of 473

Annexure C Conditions/protocols for auto-disconnections
a) <BYPL to mention for which consumer categories the protocol for auto-disconnections shall
apply and for which consumer categories the same shall not be applicable.>

b) The auto-disconnection shall not be allowed during gazetted holiday / national holidays and
during night-time

Complete details to be provided with the successful bidder.

BSES

Page 388 of 473

 Annexure D AMI system availability

AMI system issues and availability are flagged at three different severity levels.
a) Severity 1 is the most critical being a complete system level failure or breach of IT policies and
requiring urgent and immediate attention.
b) Coverage under severity 2 are outages that do not cause any immediate disruption but
subsequently may result into severity 1 outage.
c) Severity 3 are those issues / problems / outages which are neither of an emergency nor priority
level as grouped under severity level 1 or 2.

The AMISP shall implement an appropriate online SLA Application (as elaborated in Clause 14of
this Section) for problem/defect reporting and tracking system. This would enable logging and
tracking of outages / defects/non-conformances of all severity levels and get the approval of the
same from the BYPL towards desired resolution. The incidents (15 in number) are categorized as
mentioned in below table.
Category Incident Description10
4. Severity 1– a) Complete loss of AMI system functions11
Urgent b) Partial outage of AMI functions
i. BYPL user interface
ii. Consumer portal
c) Stoppage of data backup at DC/DR
d) Cyber Security issues leading to unauthorized access to
systems/applications
5. Severity 2– a) Outage at Smart Meter Operation Center
Serious i. Complete outage of communication connectivity
ii. Failure of UPS system
iii. Failure of Battery / other auxiliary system)
b) Interruption of data exchange with BYPL enterprise systems
BSES

c) Partial outage of AMI functions

i. Outage of VEE
ii. Billing Determinants
iii. Reports
d) Breach of data privacy
e) Adherence to RPO / RTO12 as mentioned in Clause [Link].9of this Section
6. Severity 3– a) Non-availability of reports as per requirement of this Section during the
Minor Operation Phase
b) Resolution of complaint ticket raised and passed on by CCS [These
complaints shall be registered within the SLA Application and hence shall
have to undergo mutual agreement checks between BYPL/AMISP before
being registered for resolution]
c) Non-availability of required inventory of spares specified in Clause 13.3.3 of
this Section
d) Failure of workstation, printers, LAN etc. at the SMOC
e) Non-availability of designated AMISP’s Manpower at the SMOC

10
Please note that the table provides the different incidents categorized under different severity levels. If any
incident at a higher severity level or order is active, then it shall be understood that a new incident at a lower
severity level or order linked to the one at the higher-level incident, shall not be separately registered. For
instance, when there is an incident “Complete Outage of AMI system functions” under Severity-1, then
“Partial outage of AMI functions” or “Interruption of data exchange with utility enterprise systems” shall not be
registered.
11
A complete outage of AMI functions may happen due to a system level crash or outage of DC/DR infra or
outage of MPLS bandwidth at DC/DR
12
RTO and RPO are expected to be checked once a month for purpose of SLA

Page 389 of 473

J.1Response & Resolution Time

The target times within which the AMISP should respond to support requests for each category of
severity is described in the following table.
a) The Initial Response Time is defined as the period from the initial logging of the support
request (through established systems and/or communications channels) and the
acknowledgment of the AMISP subject to the maximum time defined in the following table. In
case, AMISP doesn’t respond within initial response time, the support shall be deemed
acknowledged by the AMISP.
b) The Action Resolution Time is the period from the acknowledgement of support request to the
AMISP delivering a solution subject to the Maximum time defined in following table.
c) The Action Resolution Time includes investigation time and consideration of alternative
courses of action to remedy the situation.
Initial Maximum Action
Severity Action
ResponseTime Resolution Time
An urgent or emergency situation requiring
1 [15 minutes] [2 hours] Continuous attention from necessary support staff
until system operation is restored.
Attempt to find a solution acceptable to the BYPL
2 [30 minutes] [24Hours] (dependent on reproducibility), as quickly as
practical.
Evaluation and action plan. Resolution time is
3 [2 hours] [10 days] dependent on reproducibility, ability to gather
data, and the BYPL’s prioritization.

J.2 Service Response Requirements

Emergency Support for Severity 1 issues are to be provided 24 hours a day, seven days a week.
The on-call support team shall include all key technical competencies so that any aspect of a
BSES

system failure can be attended to. Severity 1 issues shall be reported by telephone for rapid
response; the key objective is to restore the system to an operational state as quickly as possible.

J.3 System Availability Calculations

System level issues / availability calculation methodology shall be as below:
a) For Severity-1 and 2 level incidents, the non-availability hours for availability calculation
shall be counted from the end of the allowed Action Resolution time for their first instance in a
given month. If any incident, repeats in the same month, the non-availability hours for
availability calculation shall be counted from the end of allowed Initial Response Time.
b) For Severity-3 events, the non-availability hours for availability calculation shall be counted
from the end of the allowed Action Resolution time

A standardized online ticket register shall be maintained, that shall be made available to BYPL
online, containing the following:

Details of each issue reported:

a) Actions taken by AMISP to correct the issue
b) Applicable Severity level
c) Time of reporting to the AMISP support engineer/support
d) Actual vs Allowed response & resolution time as defined in this annexure
e) Review of BYPL’s Engineer-in-charge as well as the AMISP’s support engineer of the site.
In the event of multiple failures at a site, due to a common cause, the first FPR (Field Problem,
Report) logged shall be used for the purpose of system availability calculation. However,
simultaneous multiple outages due to unrelated cause would be counted separately.

Page 390 of 473

Availability computation shall be done on monthly basis in selected area(s) of operation. The
formula to be used for availability computation shall be as under:
Availability per month =
 Where THM is total hours in the month when power supply to AMI system is available
 S1/ S2/ S3 is the total non-available hours in Severity Level-1 /2/3

S1/ S2/ S3 are computed for each event. For instance, S3 for each Severity-3 event would be
number of hours passed beyond the maximum resolution time for which the event is not resolved.
Some examples for the same are provided below

Category Example of computing non-available hours

Severity For incidents happening for the first time in the month, Number of hours beyond
1– Urgent the allowed maximum resolution time for which:
a) Complete loss of AMI system functions
b) Partial outage of AMI functions
i. BYPL user interface
ii. Consumer portal
c) Cyber security issues remain unresolved
d) Data backup at DC/DR remains stopped
For incidents happening for the second or more times in the month, Number of
hours beyond the allowed initial response time for which:
a) Complete loss of AMI system functions
b) Partial outage of AMI functions
i. BYPL user interface
ii. Consumer portal
c) Cyber security issues remain unresolved
d) Data backup at DC/DR remains stopped
BSES

Severity 7. For incidents happening for the first time in the month, Number of hours beyond
2– the allowed maximum resolution time for which:
Serious a) Outage at Smart Meter Operation Center
i. Complete outage of communication connectivity
ii. Failure of UPS system
iii. Failure of Battery / other auxiliary system)
b) Partial outage of AMI functions
i. Outage of VEE
ii. Billing Determinants
iii. Reports etc.
c) Any single event on data privacy breach is not resolved
d) Interruption of data exchange with BYPL enterprise systems remains
unresolved
e) Adherence to RPO / RTO is not ensured

For incidents happening for the second or more times in the month, Number of
working hours beyond the allowed initial response time for which
a) Outage at SMOC
i. Complete outage of communication connectivity
ii. Failure of UPS system
iii. Failure of Battery / other auxiliary system)
b) Partial outage of AMI functions
i. Outage of VEE
ii. Billing Determinants
iii. Reports etc.
c) Any single event on data privacy breach is not resolved

Page 391 of 473

 Category Example of computing non-available hours
d) Interruption of data exchange with BYPL enterprise systems remains
unresolved
e) Adherence to RPO / RTO is not ensured
Severity 8. Number of days beyond 10 days for which (Number of days shall be converted to
3– Minor number of hours by multiplying it with 24)
a) Non-availability of reports as per requirement of this Section during the
Operation Phase
b) Resolution of complaint ticket raised and passed on by CCS [These
complaints shall be registered within the SLA Application and hence shall
have to undergo mutual agreement checks between BYPL/AMISP before
being registered for resolution]
c) Non-availability of required inventory of spares specified in Clause 13.3.3 of
this Section
d) Failure of workstation, printers, LAN etc. at the SMOC
e) Non-availability of designated AMISP’s Manpower at the SMOC

BSES

Page 392 of 473

Annexure E Schedule of Billing Data Collection for different Consumer Category

The schedule for billing for various consumers on which the current AMI system (procured under
this contract) is implemented is provided below:

K.1 Industrial Consumers

<BYPL to add details on schedule for the billing the industrial consumers for which the AMI system
is implemented>

K.2 Commercial consumers

<BYPL to add details on schedule for the billing the commercial consumers for which the AMI
system is implemented>

K.3 Residential consumers

<BYPL to add details on schedule for the billing the residential consumers for which the AMI
system is implemented>

K.4 Agricultural consumers

<BYPL to add details on schedule for the billing the agricultural consumers for which the AMI
system is implemented>

<BYPL to add /delete / modify the above sub-sections for other consumer categories for which the
AMI system is implemented > BSES

Complete details to be provided with the successful bidder.

Page 393 of 473

Annexure F Integration Interface of Existing Enterprise Applications

<BYPL to provide the required integration interface details of each of the existing enterprise
applications which it wants to integrate with the AMI system>

Complete details to be provided with the successful bidder.

BSES

Page 394 of 473

Annexure G High Level Deployment (envisioned) of SMOC & WFMS

BSES

Page 395 of 473

 Annexure H Project Execution Plan
S. Remaining Meter O&M
Activity Name M1 M2 M3 M4 M5 M6
No Installation (M7 to M30) (M31 to M 120)
1 Award of contract to AMISP
2 Project Kickoff
3 Setup Program Governance (Steering Committee & Operations
Committee)
4 Creation of Work plan
5 Establishment of Site Office
6 Carrying out requirement analysis
7 Collection of legacy data
8 Field survey/ Consumer Indexing and designing for communication
system and on premise smart meter installation
9 Finalization of Solution and Technical Architecture
10 Integration Architecture - interfaces with external/third-party
systems BSES

11 Sign Off Implementation Roadmap & implementation plan

12 Test, Development & UAT environment Details
13 Disaster recovery plan
14 Training plan
15 Help desk support and related documents
16 Documentation for meter installation in project areas
17 Document, review & signoff of technical architecture
18 SMOC and WFM readiness
19 Installation and commissioning of first lot of Smart meters. This
includes electrical physical installation metering operation.
20 Primary network bandwidth for cellular based communication
module- cloud hosting data centre (AMISP would need to sign a
contract with NBSP as per TRAI Guidelines for bandwidth)
21 Cloud Environment preparation (Test, Development & UAT
environment )

Page 396 of 473

S. Remaining Meter O&M
Activity Name M1 M2 M3 M4 M5 M6
No Installation (M7 to M30) (M31 to M 120)
22 Provisioning of all resources in the Cloud
23 Provisioning and testing of analytics and reporting functionalities.
24 Installation, testing & commissioning of entire IT infrastructure and
applications (HES, MDMS etc.) hosted on cloud
25 Configuration of Head End &MDMS systems
26 Mechanism in place for data acquisition from meter.
27 Installation, configuration of diagnostic and monitoring tools for alert
based database, application and infrastructure monitoring system.
28 Integration of AMI system with Billing, CRM and other legacy
Systems of BYPL.
29 Deploy HES & MDMS in Production
30 Complete commissioning of installed smart meters and initiation of
data acquisition and reporting.
31 Integration and system testing and satisfactory /user acceptance
test (UAT), Security and performance testing. BSES

32 Complete UAT & update the Code Deployment Document

33 UAT Signoff by the business owners
34 Finish Data Migration related activities
35 Handover Deployment documents- Installation Instructions/Roll-
back steps
36 Provide access to all business users for UAT of full solution
Integration testing by business users using complete test data sets
37 Training of BYPL staff by the AMISP.
38 Certification& Audit – Cert-In / STQC etc
39 Go live of AMI system.
40 Remaining Meter Installation and maintenance of success
performance as per the agreed service levels
41 Operation & Maintenance/FMS implementation and support

Page 397 of 473

Annexure I Existing BSES Applications

BSES

The details given above are indicative and the complete details shall be provided with
the successful bidder.

Page 398 of 473

 Section 7. Price Format
A. Price Schedule A

Meters (each with related meter box, hardware, software and equipment)
Rate per unit
AMISP Service Upfront Total cost for
including all taxes GST
Qty charge (in INR Cost (in each category
Item Description (A) and duties other than Applicable in
S. in Nos. per meter per INR per of Meter (in
GST (in INR / month / %
No. month) Meter* INR).
Meter)
(G)=BX(EX90
(A) (B) (C) (D) (E = CX(1+D%) (F)
months)+F))
1 Single phase whole current Smart Meter 1933572
(with Net-Metering) – Consumer Meter
with Meter Box, Communication, AMI
Solution, and Back-end IT Infra with BSES

associated works and requisite no. of

polycarbonate Seal
2 Three phase whole current Smart Meter 56623
(with Net-Metering) – Consumer Meter
with Meter Box, Communication, AMI
Solution, and Back-end IT Infra with
associated works and requisite no. of
polycarbonate Seal
3 Three phase LT CT operated Smart 5021
Meter (with Net-Metering) – Consumer
Meter with Meter Box, with CTs,
Communication, AMI Solution, and Back-
end IT Infra with associated works and
requisite no. of polycarbonate Seal
4 Three phase LT CT operated Smart 4144
Meter (with Net-Metering) – DT Meter

Page 399 of 473

 with Meter Box, without CTs,
Communication, AMI Solution, and Back-
end IT Infra with associated works and
requisite no. of polycarbonate Seal
5 Three phase CT PT operated Smart 640
Meter (with Net-Metering) – HT Meter
without Meter Box, without CTs,
Communication, AMI Solution, and Back-
end IT Infra with associated works and
requisite no. of polycarbonate Seal
Total per node cost given at (G)

*Upfront cost (F) is total per meter cost including GST, to be filled in by the bidder in the Price Schedule A, based on 30% (Part A of Clause 5 of
Section 5.) cost of Total per Node cost given under Column (G) of Price Schedule A.

B. Price Schedule B
BSES

Base price per unit exclusive

of GST(IGST/CGST/SGST/ GST / Other
Item Name Qty UOM
UGST)(in INR.) on F.O.R. Taxes in %
destination basis
(1) (2) (3) (4) (6)
Part-A: Head End System software License along with requisite Data Base
1 Lot Per Meter
Management System as defined under Scope of Work
Part-B: Meter Data Management System (MDMS) software License along
with requisite Data Base Management System as defined under Scope of 1 Lot Per Meter
Work
Part-C: Pre Paid Module System software License along with requisite Data
1 Lot Per Meter
Base Management System as defined under Scope of Work
Part-D: Advanced Analytics Software License along with requisite Data Base
1 Lot
Management System as defined under Scope of Work
Part-E: Web portal, Consumer Mobile App /Helpdesk License along with
1 Lot
requisite Data Base Management System as defined under Scope of Work

Page 400 of 473

Part-F: Smart Meter Operation Center (SMOC) and Work Force Management
1 Lot
System (WFMS) Software
Part-G: Annual AMC / ATS Charges for Head End System. 1 Lot
Part-H: Annual AMC / ATS Charges for Meter Data Management System. 1 Lot
Part-I: Annual AMC / ATS Charges for Pre-Paid Module System. 1 Lot
Part-J: Annual AMC / ATS Charges for Data Analytics System. 1 Lot
Part-K: Annual AMC / ATS Charges for Consumer Mobile Application
1 Lot
System.
Part-L: Annual Cloud Hosting Charges as per requirement defined under
1 Lot Per Meter
Scope of Work for 2 million Meters
Per Meter
Part-M: 4 G data Charges 1 Lot
Per Month
Per Meter
Part-N: NB IoT data Charges 1 Lot
Per Month
Part-O : Hardware for SMOC (Display wall, Rendering Servers, Sub-Walls and
1 Lot
applications) details as per Clause 8.8.3 in Section 6
Part-P: Annual Network Connectivity Charges (AMISP to provide details of
BSES

1 Lot
MPLS line (…… Mbps x 2) in terms of bandwidth and connectivity)
Total

All Product Software and associated AMC costs are to be quoted as per meter basis in Part A to Part L of price schedule B.
The payment of AMC shall be released as per actual use basis.

Page 401 of 473

Notes applicable to Price Schedule above (shall form part of award evaluation):

1. The Bid will be evaluated on Prices quoted under Section A of Price Schedule for 2 Million
Meters. The initial Firm Order for execution will be for 4 Lacs Meters and will increase
subsequently. The overall evaluation of Bid would be based on Lowest aggregate cost of Price
Schedule A. The award evaluation will be based on lowest bid for Price Schedule – A.
2. The Bidder need to quote Section B for 2 Million Meters as well, the price quoted under this
won’t form the part of award evaluation. Until and otherwise specified 1 Lot means 2 Million.
3. The initial indented Licenses for AMI Modules of BoQ shall be 4,00,000 as per Price Schedule
A and subsequently the increment will be indented in the lot size of 50,000.
4. The bidder (s) may choose to quote all AMI modules separately or some of module in clubbed
suites as per the offering from Bidder(s), details of such variations need to be provided
separately, However the delivery of all modules and functionalities therein is mandatorily to be
ensured.
5. The Bidder should consider the cloud cost considering the project deployment schedule
defined under clause 10 of Section 5 and deployment of Testing, Pre-prod and Production
environments. However, the payment of cloud charges shall be on the basis actual usages
during the Project period on “Pay As You Go” concept. The detailed breakup of Cloud Costing
in terms of Infrastructure, tools and application deployment shall be provided by the bidder
separately before award.
6. All functionalities covered by the individual software mentioned in this BOQ is mandatorily to
deliver. However, the AMISP may quote any additional software (s) that integrates the
functionalities of one or more line items of software(s) mentioned in this BOQ.
7. If there is a discrepancy between the individual unit rates and the total amount, the unit rates
will prevail for evaluation of Total Cost.
8. Bid with variable price(s) will not be accepted.
9. Prices once quoted shall remain firm, and not subject to any escalation, till
completion/execution of the contractual assignments/work and till the contract’s validity’s
BSES

extension, if any.
10. The contractor shall need to be mandatorily registered with the relevant Tax Authority(ies) for
the LOA items (services, where applicable), and furnish photocopy of their tax registration
certificate(s) and PAN along with each Tax invoice.
11. Deposit of all statutory taxes, duties, levies, etc. to government authorities shall be the sole
responsibility of the contractor and the contractor shall indemnify BYPL for any tax
claims/problems, etc. with the statutory authority/Government or State authorities.
12. Income tax, TDS, etc. will be deducted at source by BYPL as per government policies.
13. Benefit of any reduction in taxes & duties during the execution of contract shall be passed on to
BYPL by the implementing partner(s).
14. Applicable taxes, duties, cess, etc. shall be paid on actuals as applicable in the state where the
products are delivered, provided that the bidder(s) is registered with the relevant tax
authorities.
15. The bidder(s) shall comply with all the statutory compliances, specifically pertaining to The
Legal Metrology Act 2009.
16. Further, the bidder(s) must make sure that any compliances, to be ensured by BYPL are
communicated to bidder(s) and if required, BYPL may take assistance from the bidder(s) to
execute such compliance(s) and the bidder(s) shall be reimbursed the statutory fee only, for
performing compliance(s) on behalf of BYPL applicable on BYPL.
17. BYPL have the rights to accept or reject any bid or part without assigning any reason.
18. Prices quoted shall remain firm for the entire project duration.
19. The Quantities mentioned in the price schedule are indicative and subject to change based on
the requirement of the project with capping of - 30% (thirty percent) up to +30% (thirty percent).
The same will be intimated during project award stage and / or during contract period.
20. The indicative sizing consideration for Cloud hosting can be referred under Annexure A
21. All System Software licenses offered in the RFP should be Enterprise wide full use without any
restriction on access/usage of any kind of functionality during the warranty / FMS period.

Page 402 of 473

 Bidders need to quote all the user licenses without any restrictions or limitations for usage
within India. AMI solution must not restrict BYPL / utilities such as number of users or number
of meters etc. The solution should have unrestricted license and in no way restrict BYPL in
utilizing the functionality to the max.
22. The base/unit prices to be quoted in all the Price Bid Tables should be exclusive of GST
(Goods and Services Tax). Accordingly, for both, the Indian as well as International bidders,
the GST component of price bid shall not be a part of bid evaluation. It is further clarified that in
case of International bidder, the cost of Product licenses, execution and O & M services offered
in India shall be quoted in INR inclusive of all Custom duties and Inland services as required,
BYPL shall not be responsible for Custom duty and IGST variations.

BSES

Page 403 of 473

C. Format of Financial Bid
Attached? For Official
# Document
(Yes/ No) Use
1 Financial Bid as per format provided in Form 1

Form 1: Format of Submission of Financial Bid

[IMPORTANT NOTE: THE FINANCIAL BID SHALL ONLY BE SUBMITTED IN HARD COPY]

[On the letter head of each Member of the Consortium including Lead Member/ Sole Bidder]

[Reference No.]

From:
[Address of the Lead Consortium Member/ Sole Bidder]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Sub: Financial Bid for Appointment of Advanced Metering Infrastructure Service Provider for
Smart Prepaid Metering in BSES Yamuna Power Limited on DBFOOT basis.
BSES

Ref: [Tender Details]

Dear Sir/ Madam,

We, the undersigned …....................…. [Insert name of the Lead Consortium Member/ Sole Bidder
‘Party 1’] representing …....................…. [Insert name of the Lead Consortium Member
‘Party 2’], …....................…. [Insert name of the Lead Consortium Member ‘Party 3’], ..., and
…....................…. [Insert name of the Lead Consortium Member ‘Party n’], having read, examined
and understood in detail the RFP for Implementation of [BYPL]’s AMI hereby submit our Financial
Bid. We hereby undertake and confirm that:

A. We have submitted our Financial Bid strictly in accordance with the RFP without any deviations
or condition.

B. Our Financial Bid is consistent with all the requirements of submission as stated in the RFP
and subsequent communications.

C. Price quoted clearly mentions the total cost (basic cost, Goods and Services Tax, or any other
taxes/duties/levies).

D. Under no circumstances shall escalation in prices of this Financial Bid be entertained by BYPL
whether due to factors within or beyond control of the Bidding Consortium such as change in
tax structure, currency value change, etc.

E. The details quoted herein shall stand valid at least for 9 months from the date of submission of
this Financial Bid and for implementation of Project, if awarded, as per the timeframe indicated
in the RFP.

Page 404 of 473

F. Our Total Cost of the Project for the contract period is INR………; and the quoted AMISP
Service Charge will be a fixed for the entire contract duration

G. Our quoted prices are as per the Annexure attached herein.

Dated the ……………. [Insert date of the month] day of ……………. [Insert month, year] at
……………. [Insert place].

Thanking you,

Sincerely yours,

[Insert Signature here]

[Insert Name here]
[Insert Designation here]

BSES

Page 405 of 473

 Volume II:
BIDDING AND
BSES

CONTRACT
FORMS

Page 406 of 473

Section 8: Forms- Technical and Financial Proposal

Checklist of Required Forms

This Checklist shall be filled in and submitted by the bidder along with the Technical Bid. Except
Form 1 given in Section 8 (to be completed and submitted by the Bidder in the Financial Bid) all
other documents/ forms duly filled and complete in all respect are to be submitted by the Bidder in
the Technical Bid.

S. Attached?
Document For Official Use
No. (Yes/ No)
1. Tender Fee
2. List of Consortium Members and Subcontractor(s) (as
applicable) as per the format prescribed in Form 1 given
in Section 8
3. Bidder Information as per the format prescribed in Form 2
given in Section 8
4. Project Implementation Plan as per format provided in
Form 3 given in Section 8
5. Curriculum Vitae of key personnel as per format provided
in Form 4 and Form 5 given in Section 8
6. Bid Security in the form of Demand Draft or Bank
Guarantee as per format prescribed in Form 6 given in
Section 8
7. Covering Letter for Submission of Bid by Sole Bidder /
Lead Consortium Member as per format prescribed in
BSES

Form 7 given in Section 8

8. Consortium Agreement Format entered amongst all
Members of the Bidding Consortium as per format
prescribed in Form 8 given in Section 8
9. Power of Attorney by each Consortium Member in favour
of Lead Consortium Member as per format prescribed in
Form 9 given in Section 8
10. Power of Attorney by Lead Consortium Member/ Sole
Bidder authorizing an Individual Designated
Representative for the Consortium/ Bidder as per the
format prescribed in Form 10 given in Section 8
11. Letter of Consent by each Consortium Member reviewing
each element of the Bid as per format prescribed in Form
11 given in Section 8
12. For Lead Member in case of Consortium Bidding / Sole
Bidder Experience:
i. References along with requisite contract/ Purchase
Order (PO)/ Work Order (WO). The references
should indicate client name, scope of work, Project
start date (as per the format prescribed in Form 13
given in Section 8);
ii. Documentary evidence of Project completion such
as client completion certificate, proof of payment
received and client certificate of delivery of material,
proof of asset capitalized in books of accounts (as
applicable)/ and similar proofs along with contact
details of the client.

Page 407 of 473

S. Attached?
Document For Official Use
No. (Yes/ No)
13. For System Integration Experience [Refer Clause 2 in
Section 1]:

i. References along with requisite contract/Purchase

Order (PO)/ Work Order (WO). The references
should indicate client name, scope of work, Project
start date (as per the format prescribed in Form
13given in Section 8);
ii. Documentary evidence of completion of the Project
or completion of Go-Live status (i.e., Go-live
certificate, UAT testing certificate etc.) or other
documentary evidence indicating completion (e.g.,
proof of payment received and client certificate for
supply of material or similar proofs) along with
contact details of the client;
iii. Client certificate and other documentation for
implementation performance/ operation.
14. For Financial Strength [Refer Clause 2 in Section 1]:
Audited Annual financial statements, Balance Sheet and
P&L Account of all Consortium Members/ Sole Bidder for
the respective Financial Years as per the format
prescribed in Form 12 given in Section 8.
15. List of Material and Services as per format provided in
Form 14 given in Section 8.
16. Table of Compliance as per format provided in Form 15
BSES

given in Section 8.
17. Format for Technical & Financial Requirement-
Relationship & Details of Equity Shareholding (Form 16).
18. Authorization from Parent / Affiliate of Sole Bidder
/Member of Bidding Consortium whose technical /
financial capability has been used by the Sole Bidder /
Member of Bidding Consortium (Form 17).
19. Format of Undertaking by Technically/ Financially
Evaluated Entity (ies) OR Undertaking from the Ultimate
Parent Company for total equity investment commitment,
in the prescribed format in Form 18, to meet any shortfall
in the equity investment by the Selected Bidder in the
BIDDER.
20. Formats for Board Resolutions
21. Copy of this RFP with sign and official seal on every page

Page 408 of 473

Form 1: List of Consortium Members/ Sub-Contractor(s)

■ [The Bidder shall identify below the Consortium Members/ Sub-contractor(s) for major Project
items. For sub-contractor a Letter of Intent must be provided.]
■ The Bidder / Lead Bidder shall identify below the Consortium Members/ JV / Solution Providers
for Project items.]

Solution Type RF Cellular

Proposed Communication Technology

Proposed List of
Compliance to
Consortium Supporting
Major Project Item Nationality PQR (Yes / No/
Member / Sub- Document
Partial / NA)
Contractor(s) Submitted
Meter Manufacturer (s)
Communication Partner
HES Solution
NMS (If Any)
MDMS Solution
Prepaid Solution (if any)
System Integrator
Cloud Service Provider
Advanced Analytics
Solution
BSES

SMOC Application
WFMS Application
Consumer App / Portal
[Other] (if any)

Page 409 of 473

Form 2: Bidder Information
[Sole Bidder/ all Consortium Members must provide all documents required to prove/ substantiate
its Eligibility as required in Eligibility Criteria Clause 2 of Section 1. for each Consortium Member]

S.
Information Requirement Details
No.
1 Company Name and Details
2 Address of its place of business in India
3 List of board of directors or regulating/controlling body
4 Attested copy of Certificate of Registration/Incorporation issued by the
Registrar of Companies
5 Memorandum and Articles of Association or document constituting the
company and regulating its affairs
6 Certificate of Commencement of Business issued by the Registrar of
Companies
7 Copy of the Goods and Services Tax (GST) Registration Certificate
8 Provident Fund (PF) Certificate indicating PF Code
9 Copy of Permanent Account Number (PAN) Card
10 Copy of the Goods and Services Tax (GST) Registration Certificate
11 Audited annual financial statements and financial Net worth for the last three
years
12 Any other papers or documents required by BYPL at a later stage or in future

BSES

Page 410 of 473

Form 3: Project Implementation Plan
The Bidder shall submit a preliminary Project implementation plan along with the Bid which shall
include at least the following activities:

a) Understanding of BYPL and its requirement with respect to Project implementation;

b) Overall system architecture and system philosophy capable of scale-up;
c) Details of proposed methodology;
d) Schematic Diagram of Proposed System Configuration
e) An approach paper documenting the interfaces for integration with existing and future
applications based on the information provided by BYPL
f) Project team structure;
g) Line of Credit / Source of funding and supporting documents;
h) Governance Framework;
i) Resource planning and estimation;
j) Risk planning;
k) Quality Assurance Program;
l) Data Privacy Approach;
m) Cyber Security Approach;
n) Site Survey;
o) Installation & Field update schedule;
p) Repair and Maintenance Schedule including details on Spares Management;
q) Training schedule;

BSES

Page 411 of 473

Form 4: Bidder’s Representative and Key Personnel
[Bidders should provide the names and details of the suitably qualified Contractor’s Representative
and Key Personnel to perform the AMISP Contract. The data on their experience should be supplied
using the Form 5 given in Section 8 below for each candidate.]

1. Title of position: Project Manager

Name of candidate:
Duration of [insert the whole period (start and end dates) for which this position
appointment: will be engaged]
Time commitment: [insert the number of days/week/months/ that has been scheduled for
for this position: this position]

Expected time [insert the expected time schedule for this position (e.g., attach high
schedule for this level Gantt chart]
position:
2. Title of position: [System Integration Specialist]
Name of candidate:
Duration of [insert the whole period (start and end dates) for which this position
appointment: will be engaged]
Time commitment: [insert the number of days/week/months/ that has been scheduled for
for this position: this position]

Expected time [insert the expected time schedule for this position (e.g., attach high
schedule for this level Gantt chart]
position:
3. Title of position: [Cyber Security Specialist]
BSES

Name of candidate:
Duration of [insert the whole period (start and end dates) for which this position
appointment: will be engaged]
Time commitment: [insert the number of days/week/months/ that has been scheduled for
for this position: this position]

Expected time [insert the expected time schedule for this position (e.g., attach high
schedule for this level Gantt chart]
position:
4. Title of position: [Communication Technology Specialist]
Name of candidate:
Duration of [insert the whole period (start and end dates) for which this position
appointment: will be engaged]
Time commitment: [insert the number of days/week/months/ that has been scheduled for
for this position: this position]

Expected time [insert the expected time schedule for this position (e.g., attach high
schedule for this level Gantt chart]
position:

Page 412 of 473

Form 5: Resume and Declaration
Name of Bidder:

Position [#1]: [title of position]

Personnel Name: Date of birth:
information Address: E-mail:
Professional qualifications:
Academic qualifications:
Language proficiency: [language and levels of speaking, reading and writing skills]
Details
Address of employer:
Telephone: Contact (manager / personnel officer):
Fax:
Job title: Years with present employer:

Summarize professional experience in reverse chronological order. Indicate technical and

managerial experience relevant to the Project.
Duration of
Project Role Relevant experience
involvement
[main [role and
[describe the experience relevant to this
project responsibilities on the [time in role]
position]
details] project]

Declaration BSES

I, the undersigned [insert either “Contractor’s Representative” or “Key Personnel” as applicable],

certify that to the best of my knowledge and belief, the information contained in this Form 5
correctly describes myself, my qualifications, and my experience.

I confirm that I am available as certified in the following table and throughout the expected time
schedule for this position as provided in the Bid:

Commitment Details
Commitment to [insert period (start and end dates) for which this Contractor’s
duration of contract: Representative or Key Personnel is available to work on this contract]
Time commitment: [insert period (start and end dates) for which this Contractor’s
Representative or Key Personnel is available to work on this contract]

I understand that any misrepresentation or omission in this Form may:

(a) be taken into consideration during Bid evaluation;
(b) result in my disqualification from participating in the Bid;
(c) result in my dismissal from the contract.

Name of Contractor’s Representative or Key Personnel: [insert name]

Signature: __________________________________________________________

Date: (day month year): _______________________________________________

Countersignature of authorized representative of the Bidder:

Page 413 of 473

Signature: ________________________________________________________

Date: (day month year): ______________________________________________

BSES

Page 414 of 473

Form 6: Format of Bank Guarantee for Bid Security
[To be on non-judicial stamp paper of Rupees One Hundred Only (INR100/-) or appropriate value
as per Stamp Act relevant to place of execution, duly signed on each page. Foreign entities
submitting Bid are required to follow the applicable law in their country]

Reference No. ……………. Bank Guarantee No.……………. Dated: …………….

To:
[BYPL]
[Address]

Dear Sir/ Madam,

WHEREAS……………………… [Insert name of the Sole Bidder/Lead Consortium Member] with

address……………. [Insert address of Sole Bidder /Lead Consortium Member] having its registered
office at……………. [Insert address of the Sole Bidder/Lead Consortium Member] (Hereinafter, the
“Bidder”) wishes to participate in Tender No. [Tender Details] (The “RFP”) issued by [BYPL]
(hereinafter, the “BYPL”) for Engagement of Service Provider for Advance Metering Infrastructure
(AMI)

And WHEREAS a Bank Guarantee for [Amount] valid [Date] is required to be submitted by the
Bidder along with the RFP.

We,…………….[Insert name of the Bank and address of the Branch giving the Bank Guarantee]
having our registered office at…………….[Insert address of the registered office of the Bank]
hereby give this Bank Guarantee No.…………….[Insert Bank Guarantee number]
dated…………….[Insert the date of the Bank Guarantee],and hereby agree unequivocally and
BSES

unconditionally to pay immediately on demand in writing from the BYPL any officer authorized by it
in this behalf any amount not exceeding [Amount] to the said BYPL on behalf of the Bidder.

We ……………. [Insert name of the Bank] also agree that withdrawal of the Bid or part thereof by
the Bidder within its validity or non-submission of Performance Security by the Bidder within the
stipulated time of the Letter of Award to the Bidder or any violation to the relevant terms stipulated
in the RFP would constitute a default on the part of the Bidder and that this Bank Guarantee is
liable to be invoked and encashed within its validity by the BYPL in case of any occurrence of a
default on the part of the Bidder and that the amount is liable to be forfeited by the BYPL.

This Guarantee shall be valid and binding on this Bank up to and inclusive of ……………. [Insert
the date of validity of the Bank] and shall not be terminable by notice or by Guarantor change in the
constitution of the Bank or the firm of the Bidder Or by any reason whatsoever and our liability
hereunder shall not be impaired or discharged by any extension of time or variations or alternations
made, given, conceded with or without our knowledge or consent by or between the Bidder and the
BYPL.

NOTWITHSTANDING anything contained hereinbefore, our liability under this guarantee is

restricted to [Amount]. Our Guarantee shall remain in force till [Date]. Unless demands or claims
under this Bank Guarantee are made to us in writing on or before [Date], all rights of the
Beneficiary under this Bank Guarantee shall be forfeited, and we shall be released and discharged
from all liabilities there under.

[Insert the address of the Bank with [Insert signature of the Bank’s Authorized
complete postal branch code, telephone and Signatory]
fax numbers, and official round seal of the
Bank]

Page 415 of 473

Attested
……………………………. [Signature]
(Notary Public)
Place: …………………………. Date: …………………………….

INSTRUCTIONS FOR SUBMITTING BANK GUARANTEE

1. Bank Guarantee to be executed on non-judicial stamp paper of appropriate value as per
Stamp Act relevant to place of execution. Foreign entities submitting Bids are required to
follow the applicable law in their country.
2. The Bank Guarantee by Bidder shall be given from any Scheduled Commercial Bank.
3. The full address along with the Telex/Fax No. and e-mail address of the issuing bank to be
mentioned.

BSES

Page 416 of 473

Form 7: Format of Covering Letter by Lead Consortium Member/ Sole
Bidder for Submission of Bid
[Covering Letter shall be on the official letterhead of the Lead Consortium Member of the Bidding
Consortium/ Sole Bidder]

[Reference No.]
From:
[Address of the Lead Consortium Member/ Sole Bidder]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Sub: Appointment of Advanced Metering Infrastructure Service Provider for Smart Prepaid
Metering in BSES Yamuna Power Limited on DBFOOT basis

Ref: [Tender Details]

Dear Sir/ Madam,

We, the undersigned ……………. [Insert name of the Lead Consortium Member/ Sole Bidder]
having read, examined and understood in detail the RFP for Appointment of AMISP for Smart
Prepaid Metering on DBFOOT basis hereby submit our Bid comprising of Technical and Financial
Bids. BSES

1. We give our unconditional acceptance to the RFP including but not limited to all its instructions,
terms and conditions, and formats attached thereto, issued by BYPL, as amended. In token of
our acceptance to the RFP, the same have been initialed by us and enclosed to the Bid. We
shall ensure that our Consortium shall execute such requirements as per the provisions of the
RFP and provisions of such RFP shall be binding on us.

2. Fulfilment of Eligibility
We undertake that we fulfill the Eligibility Criteria stipulated in the RFP and fulfill all the eligibility
requirements as the Lead Consortium Member/ Sole Bidder as outlined in the RFP.

We hereby confirm that in accordance with Clause 2 of Section 1 of the RFP, we are herewith
submitting legally binding undertaking supported by a board resolution from the
……………………....[insert name of Technically Evaluated Entity and/or Financially Evaluated
Entity or its Ultimate Parent Company, as the case may be] that all the equity investment
obligations of …………………. [Insert name of the Sole Bidder/ Lead Consortium Member] shall
be deemed to be equity investment obligations of the …………………… [insert name of
Technically Evaluated Entity and/or Financially Evaluated Entity or its Ultimate Parent
Company, as the ease may be] and in the event of any default by……………….…....[insert
name of the Sole Bidder/ / Lead Consortium Member], the same shall be met by
…………………………. [Insert name of Technically Evaluated Entity and/or Financially
Evaluated Entity or its Ultimate Parent Company, as the case may be].

[To be inserted only in ease the Bidder has sought qualification on the basis of technical and
financial capability of its Affiliate(s) and/or its Parent]

3. Bid Security

Page 417 of 473

 We have enclosed a Bid Security of [Amount] in the form of a Bank Guarantee No. …………….
[Insert Bank Guarantee Number] (OR Demand Draft) dated …………….[Insert date of the Bank
Guarantee] as per Form 6 given in Section 4 from …………….[Insert name of Bank providing
Bid Bond] and valid up to [Date].

4. No Deviation
We have submitted our Financial Bid strictly as per terms and formats of the RFP, without any
deviations, conditions and without mentioning any assumptions or notes for the Financial Bid in
the said format.

5. Acceptance
We hereby unconditionally and irrevocably agree and accept that the decision made by BYPL in
respect of any matter regarding or arising out of the RFP shall be binding on us. We hereby
expressly waive any and all claims in respect of Bid process.

We confirm that there are no litigations or disputes against us, which materially affect our ability
to fulfill our obligations with regard to fulfilling our obligations as per the RFP.

6. Familiarity with Relevant Indian Laws and Regulations

We confirm that we have studied the provisions of the relevant Indian laws and regulations as
required to enable us to submit this Bid and execute the RFP Documents, in the event of our
selection as Selected Bidder. We further undertake and agree that all such factors as
mentioned in the AMISP Contract have been fully examined and considered while submitting
the Bid.

7. Compliance with applicable laws/ guidelines for public procurement in India

We confirm that we shall adhere to applicable laws for public procurement in India including the
guidelines issued in Order No. F/No.6/18/2019-PPD by Ministry of Finance, Department of
BSES

Expenditure, Public Procurement Division dated 23 July 2020, Order No No.9/16/2016-Trans-

Part (2) dated 18 November 2020, latest Government of India Guidelines for Make in India,
Domestically manufactured products, Atmanirbhar Bharat and circulars DIPP Office
Memorandum No. P45021/2/2017-PP (BE-II) date:16th Sept. 2020, MeitY Circular
No.1(10)/2017-CLES dated 06.12.2019 and Order No. 11/05/2018-Coord. by the Ministry of
Power dated 17 September 2020 including any amendments or modifications to the same from
time to time.

8. Contact Person
Details of the contact person representing our Bidding Consortium/ Sole Bidder (registered
Company)supported by the Power of Attorney prescribed in Form 10given in Section 4of the
RFP are furnished as under:
Name: ………………………………………………….
Designation: ………………………………………………….
Company: ………………………………………………….
Address: ………………………………………………….
Mobile: ………………………………………………….
Phone: ………………………………………………….
Fax: ………………………………………………….
Email: ………………………………………………….

1. We are submitting herewith the Technical Bid containing duly signed formats, both in
electronic and physical forms, (duly attested) as desired by you in the RFP for your
consideration.

2. We are also submitting herewith the Financial Bid in electronic form only, as per the terms
and conditions in the RFP.

Page 418 of 473

9. It is confirmed that our Bid is consistent with all the requirements of submission as stated in
the RFP and subsequent communications from BYPL.

10. The information submitted in our Bid is complete, strictly as per the requirements stipulated
in the RFP and is correct to the best of our knowledge and understanding. We would be
solely responsible for any errors or omissions in our Bid.

11. We confirm that all the terms and conditions of our Bid are valid for acceptance for a period
of 180 days from the Bid Submission Deadline.

12. We confirm that we have not taken any material deviation so as to be deemed non-
responsive with respect to the provisions stipulated in the RFP.

13. We confirm that no order/ ruling has been passed by any Competent Court or Appropriate
Commission against us or any of our Consortium Members or in the preceding 1 (one) year
from the Bid Submission Deadline for breach of any contract and that the Bid Security
submitted by us or any of our Consortium Members has not been forfeited, either partly or
wholly, in any bid process in the preceding 1 (one) year from the Bid Submission Deadline..

14. We confirm that we are not currently blacklisted/ debarred/banned/suspended by any Govt.
Organization/State Electricity Regulatory Agencies/Govt. Undertaking/BYPL as on the date
of submission of bid.

15. We are registered/ exempt from registering in accordance with applicable laws

16. [Evidence of valid registration by the Competent Authority shall be attached if applicable]
BSES

Dated the ……………. [Insert date of the month] day of ……………. [Insert month, year] at
……………. [Insert place].

Thanking you,
Yours Sincerely,
[Insert Signature here]
[Insert Name here]
[Insert Designation here]

Page 419 of 473

Form 8: Format of Consortium Agreement to be entered amongst all
Members of a Bidding Consortium
[To be on non-judicial stamp paper of Rupees One Hundred Only (INR 100/-) or appropriate value
as per Stamp Act relevant to place of execution, duly signed on each page. Foreign entities
submitting Bid are required to follow the applicable law in their country.]

FORM OF CONSORTIUM AGREEMENT BETWEEN

M/s…........................................ M/s. .........................................., M/s. ..........................................,
AND M/s. .......................................... for bidding for Tender No. [Tender Details] (The “RFP”) dated
[Date] as per its Clause 2 of Section 1.

1. THIS Consortium Agreement (hereinafter referred to as “Agreement”) executed on this..........

[Date] day of.......... [Month],.......... [year] between
2. M/s. .........................................., a company incorporated under the laws of.................... and
having its Registered Office at .........................................., [CIN No.
___________________________] (hereinafter called "Party 1,” or “Lead Consortium Member”
which expression shall include its successors, executors and permitted assigns);
3. M/s. .........................................., a company incorporated under the laws of.................... and
having its Registered Office at .........................................., [CIN No.
___________________________] (hereinafter called "Party 2,” which expression shall include
its successors, executors and permitted assigns);
4. M/s. .........................................., a company incorporated under the laws of.................... and
having its Registered Office at .........................................., [CIN No.
___________________________] (hereinafter called "Party 3,” which expression shall include
its successors, executors and permitted assigns);
BSES

5. M/s. .........................................., a company incorporated under the laws of.................... and

having its Registered Office at .........................................., [CIN No.
___________________________] (hereinafter called "Party n,” which expression shall include
its successors, executors and permitted assigns);

[The Bidding Consortium should list the name, address of its registered office and other details of
all the Consortium Members above.]

WHEREAS the Parties above named are entering into this Consortium Agreement for the purpose
of submitting the Bid in response to the RFP and in the event of selection as Selected Bidder to
comply with the requirements as specified in the RFP and ensure execution of the AMISP Contract
as may be required to be entered into with BYPL.

Party 1, Party 2, Party 3 ... and Party n are hereinafter collectively referred to as the “Parties” and
individually as a “Party.

WHEREAS the RFP stipulates that the Bidders applying as a Bidding Consortium shall submit a
legally enforceable Consortium Agreement in a format specified in the RFP, whereby each
Consortium Member undertakes to be liable for its Roles and Responsibilities, provide necessary
guarantees and pay required fees as required as per the provisions of the RFP, as specified
herein.

WHEREAS any capitalized term in this Agreement shall have the meaning ascribed to such term in
the RFP document.

NOW THEREFORE, THIS AGREEMENT WITNESSTH AS UNDER:

Page 420 of 473

In consideration of the above premises and agreement all the Parties in this Consortium do hereby
mutually agree as follows:

5. In consideration of the selection of the Consortium as the Bidding Consortium by BYPL, we the
Members of the Consortium and Parties to the Consortium Agreement do hereby unequivocally
agree that M/s........................................................... [Insert name of the Lead Member], shall
act as the Lead Member as defined in the RFP for self and agent for and on behalf of M/s.
.........................................., M/s. .........................................., M/s. ..........................................,
and M/s. .......................................... [The names of all the other Members of the Consortium to
be filled in here].

6. The Lead Consortium Member is hereby authorized by the Members of Consortium and Parties
to the Consortium Agreement to bind the Consortium and receive instructions for and on behalf
of all Members. The Roles and Responsibilities of all other members shall be as per the
Annexure to this Agreement. In the event the Consortium is selected pursuant to the Bidding
Process, the shareholding of all each of the Consortium Members in the AMISP shall be as
under:
Name of the Relationship with
Name of the Bidding
Company Sole Bidder/ % of equity
S. Company/ Member in
investing in the Member of the participation in the
No case of a Bidding
equity of the Bidding BIDDER
Consortium
BIDDER Consortium
1. Lead Consortium Members (Not Less than 51%)
2. Consortium Member 1 (Not Less than 10%)
3. Consortium Member 2 (Not Less than 10%)
4. Consortium Member 3 (Not Less than 10%)
5. Consortium Member 4 BSES
(Not Less than 10%)

*In case the Bidder proposes to invest through its Affiliate(s) / Parent Company / Ultimate
Parent Company, the Bidder shall take prior permission from BYPL and declare shareholding
pattern of such Affiliate(s) / Parent Company / Ultimate Parent Company and provide
documentary evidence to demonstrate relationship between the Bidder and the Affiliate(s) /
Parent Company / Ultimate Parent Company. These documentary evidence could be, but not
limited to, demat account statement(s) / Registrar of Companies' (ROC) certification / share
registry book, etc. duly certified by Company Secretary.

7. Each Consortium Member undertakes to be individually liable for the performance of its part of
the Roles and Responsibilities without in any way limiting the scope of collective liability
envisaged in this Agreement in order to meet the requirements and obligations of the RFP. The
Lead Consortium Member shall be liable and responsible for ensuring the individual and
collective commitment of each of the Members of the Consortium in discharging all their
respective Roles and Responsibilities.

8. In case of any breach of any of the commitment as specified under this Agreement by any of
the Consortium Members, the Lead Consortium Member of the Consortium shall be liable to
meet the obligations as defined under the RFP.

9. Except as specified in the Agreement, it is agreed that sharing of responsibilities as aforesaid

and obligations thereto shall not in any way be a limitation of responsibility of the Lead Member
or any other consortium member under these presents.

10. The Members expressly agree to adhere to all the terms and conditions of the RFP and confirm
that they don’t have any Conflict of Interest (as defined in the RFP).

Page 421 of 473

11. This Consortium Agreement shall be construed and interpreted in accordance with the Laws of
India and Courts at [Place] shall have the exclusive jurisdiction in all matters relating thereto
and arising there under.

12. It is hereby agreed that the Lead Consortium Member shall furnish the Bid Security, as
stipulated in the RFP, on behalf of the Bidding Consortium.

13. It is hereby agreed that in case of selection of Bidding Consortium as the AMISP, the Parties to
this Consortium Agreement do hereby agree that they shall furnish the Performance Security
and other commitments to BYPL as stipulated in the RFP and AMISP Contract. The Lead
Member shall be responsible for ensuring the submission of the Performance Security and
other commitments on behalf of all the Consortium Members.

14. It is further expressly agreed that the Consortium Agreement shall be irrevocable and, shall
remain valid over the term of the Project//work awarded by BYPL, unless expressly agreed to
the contrary by BYPL.

15. The Lead Consortium Member is authorized and shall be fully responsible for the accuracy and
veracity of the representations and information submitted by the Consortium Members
respectively from time to time in response to the RFP for the purposes of the Bid. The
representation by the Lead Member shall be deemed to be on behalf of and binding on all
members of the Consortium.

16. It is expressly understood and agreed between the Members of the Consortium and Parties
that the responsibilities and obligations of each of the Members shall be as delineated as
annexed hereto as Annexure-A forming integral part of this Agreement. It is further agreed by
the Members that the above sharing of responsibilities and obligations shall not in any way be
a limitation of responsibilities and liabilities of the Members, with regards to all matters relating
BSES

to the execution of the Bid and implementation of the Project envisaged in the RFP
Documents.

17. It is clearly agreed that the Lead Consortium Member shall ensure performance indicated in the
RFP. In the event one or more Consortium Members fail to perform its/ their respective
obligations, the same shall be deemed to be a default by all the Consortium Members.

18. It is hereby expressly agreed between the Parties to this Consortium Agreement that neither
Party shall assign or delegate or subcontract its rights, duties or obligations under this
Agreement to any person or entity except with prior written consent of BYPL.

19. Notwithstanding anything stated herein, it is agreed that all the members of consortium
including lead member shall jointly and severally be liable to comply the terms of
contract/tender terms. That all the members of consortium including lead member shall jointly
and severally be liable for any breach to terms of contract and shall liable to compensate
BYPL, in full, including the cost/expenses incurred for getting the work done through third party
vendor. That all the members of consortium including lead member shall jointly and severally
be liable to indemnify BYPL from all losses/penalties/compensation/liabilities arising/relating to
the award/execution of work under contract by consortium.

20. This Consortium Agreement:

a) has been duly executed and delivered on behalf of each Party hereto and constitutes the
legal, valid, binding and enforceable obligation of each such Party;
b) sets forth the entire understanding of the Parties hereto with respect to the subject matter
hereof; and

Page 422 of 473

 c) may not be amended or modified except in writing signed by each of the Parties and with
prior written consent of BYPL.

Common Seal of .................................. has For M/s. .......................................... (Party 1)

been affixed in my/ our presence pursuant to [Signature of Authorized Representative]
Board Resolution dated..................... ................................................................
[Name of the Authorized Representative]
[Designation of the Authorized Representative]
Witness 1 Witness 2

[Signature of Witness 1] [Signature of Witness 2]

................................................................ ................................................................
Name: Name:
Designation: Designation:

N. Common Seal of .................................. For M/s. .......................................... (Party N)

has been affixed in my/ our presence [Signature of Authorized Representative]
pursuant to Board Resolution
dated.....................
................................................................
[Name of the Authorized Representative]:
[Designation of the Authorized Representative]:
N.1. Witness 1 N.2. Witness 2
BSES

[Signature of Witness 1] [Signature of Witness 1]

................................................................ ................................................................
Name: Name:
Designation: Designation:

Annexure-A

Role and Responsibility of each Member of the Consortium:

1. Roles and Responsibilities of the Party 1 (Lead Consortium Member):
2. Roles and Responsibilities of the Party 2
3. Roles and Responsibilities of the Party 3
.
.
N. Roles and Responsibilities of the Party N

Page 423 of 473

Form 9: Format of Power of Attorney by Consortium Member in favour
of Lead Consortium Member
[To be provided by each Consortium Member (other than the Lead Consortium Member) in favor of
the Lead Consortium Member]

WHEREAS [BYPL] has issued for Tender No. [Tender Details] (the “RFP”) dated [Date] for inviting
Bids in respect of Appointment of AMISP for Smart Prepaid Metering solution (the “Project”) on the
terms contained in the RFP;

WHEREAS M/s.……………., M/s. ………………., M/s. and M/s. ………………. [Insert names of all
Members of Consortium] the Members of the Consortium are desirous of submitting a Bid in
response to the RFP, and if selected, undertaking the responsibility of implementing the Project as
per the terms of the RFP;

WHEREAS all the Members of the Consortium have agreed under the Consortium Agreement
dated …………. (The “Consortium Agreement”), entered into between all the Members and
submitted along with the Bid to appoint ……….. [Insert the name and address of the Lead
Consortium Member] as Lead Consortium Member to represent all the Members of the Consortium
for all matters regarding the RFP and the Bid;

AND WHEREAS pursuant to the terms of the RFP and the Consortium Agreement, we, the
Members of the Consortium hereby designate M/s ………….. [Insert name of the Lead Member] as
the Lead Consortium Member to represent us in all matters regarding the Bid and the RFP, in the
manner stated below:-

Know all men by these presents, we …………………………………………. [Insert name and

address of the registered office of the Member 1], ………………………………………………….
BSES

[Insert name and address of the registered office of the Member 2],…...,
……………………………………. [Insert name and address of the registered office of the Member
n] do hereby constitute, appoint, nominate and authorize ……………………………… [Insert name
and registered office address of the Lead Consortium Member], which is one of the Members of
the Consortium, to act as the Lead Member and our true and lawful attorney, to do in our name
and on our behalf, all such acts, deeds and things necessary in connection with or incidental to
submission of Consortium’s Bid in response to the RFP issued by BYPL including signing and
submission of the Bid and all documents related to the Bid as specified in the RFP, including but
not limited to undertakings, letters, certificates, acceptances, clarifications, guarantees or any other
document, which BYPL may require us to submit. The aforesaid attorney is further authorized for
making representations to BYPL named in the RFP, and providing information / responses to
BYPL, representing us and the Consortium in all matters before BYPL named in the RFP, and
generally dealing with BYPL named in the RFP in all matters in connection with our Bid, till
completion of the bidding process as well as implementation of the Project, if applicable, in
accordance with the RFP.

We, as Members of the Consortium, hereby agree to ratify all acts, deeds and things done by our
said attorney pursuant to this Power of Attorney and that all acts, deeds and things done by our
aforesaid attorney shall be binding on us and shall always be deemed to have been done by us.

All the terms used herein but not defined shall have the meaning ascribed to such terms under the
RFP.

We, as Members of the Consortium, hereby agree to ratify all acts, deeds and things done by our
said attorney pursuant to this Power of Attorney and that all acts, deeds and things done by our
aforesaid attorney shall be binding on us and shall always be deemed to have been done by us.

Page 424 of 473

All the terms used herein but not defined shall have the meaning ascribed to such terms under the
RFP.

Signed by the within named ………………………………. [Insert the name of the executants
Consortium Member] through the hand of Mr./ Ms./ Dr. ………………………………………. duly
authorized by the Board to issue such Power of Attorney dated this …………………. day of
………….…

Accepted

………………………………
(Signature of Attorney)
[Insert Name, designation and address of the Attorney]

Attested

…………………………………..
(Signature of the executant)
(Name, designation and address of the executant)
…………………………………….
Signature and stamp of Notary of the place of execution

Common seal of ……………… has been affixed in my/our presence pursuant to Board of Director’s
Resolution dated……

1. WITNESS1. ………………………………………………. (Signature)BSES

Name ………………………………………….
Designation...........…………………………..

2. WITNESS2...........…………………………..................... (Signature)
Name ………………………………………….
Designation...........………………………….__

Notes
a. The mode of execution of the power of attorney should be in accordance with the procedure, If
any, laid down by the applicable law and the charter documents of the executants (s).
b. In the event, power of attorney has been executed outside India, the same needs to be duly
notarized by a notary public of the jurisdiction where it is executed.
c. Also, wherever required, the executant(s) should submit for verification the extract of the
charter documents and documents such as a Board resolution/ power of attorney, in favor of
the person executing this power of attorney for delegation of power here under on behalf of the
executant(s).

Page 425 of 473

Form 10: Format of Power of Attorney by Lead Consortium Member /
Sole Bidder authorizing an Individual Designated
Representative for the Consortium
[To be on non-judicial stamp paper of Rupees One Hundred Only (INR 100/-) or appropriate value
as per Stamp Act relevant to place of execution. Foreign companies submitting Bids are required
to follow the applicable law in their country.]

Know all men by these presents, we …………………………………………….[Insert name and

address of the registered office of the Lead Consortium Member of the Bidding Consortium/ Sole
Bidder] do hereby constitute, appoint, nominate and authorize Mr./Ms.
………………………………………………… [Insert name and residential address], who is presently
employed with us and holding the position of ………………………………. as our true and lawful
attorney, to do in our name and on our behalf, all such acts, deeds and things necessary in
connection with or incidental to submission of our Bid in response to Tender No. [Tender Details]
for Appointment of AMISP for Smart Prepaid Metering Solution (the “Project”) issued by [BYPL],
including signing and submission of the Bid and all other documents related to the Bid, including
but not limited to undertakings, letters, certificates, acceptances, clarifications, guarantees or any
other document which BYPL may require us to submit. The aforesaid attorney is further authorized
for making representations to BYPL, and providing information / responses to BYPL, representing
us in all matters before BYPL, and generally dealing with BYPL in all matters in connection with our
Bid till the completion of the bidding process as per the terms of the RFP.

We hereby agree to ratify all acts, deeds and things done by our said attorney pursuant to this
Power of Attorney and that all acts, deeds and things done by our aforesaid attorney shall be
binding on us and shall always be deemed to have been done by us.
BSES

All the terms used herein but not defined shall have the meaning ascribed to such terms under the
RFP.

Signed by the within named........................................... [Insert the name of the executant company]
through the hand of Mr./ Mrs. ……………………………………….duly authorized by the Board to
issue such Power of Attorney dated this ………………………. day of ………

Accepted

……………………………… (Signature of Attorney)

[Insert Name, designation and address of the Attorney]

Attested
…………………………………..
(Signature of the executant)
(Name, designation and address of the executant)

…………………………………….
Signature and stamp of Notary of the place of execution

Common seal of ……………… has been affixed in my/our presence pursuant to Board of Director’s
Resolution dated……

1. WITNESS 1. ………………………………………………. (Signature)

Name ………………………………….

Page 426 of 473

 Designation...........………………….

2. WITNESS 2. ………………………………………………. (Signature)

Name ………………………………….
Designation...........…………………._

________________________________________________________________________
Notes:
a. The mode of execution of the power of attorney should be in accordance with the procedure, if
any, laid down by the applicable law and the charter documents of the executant(s).

b. In the event, power of attorney has been executed outside India, the same needs to be duly
notarized by a notary public of the jurisdiction where it is executed.

c. Also, wherever required, the executant(s) should submit for verification the extract of the
charter documents and documents such as a Board resolution / power of attorney, in favour of
the person executing this power of attorney for delegation of power hereunder on behalf of the
executant(s).
_________________________________________________________________________

BSES

Page 427 of 473

Form 11: Format of Letter of Consent by Sole Bidder/ Consortium
Member reviewing each element of the Bid
[On the letter head of Sole Bidder/ each Member of the Consortium including Lead Member]

[Reference No.]

From:
[Address of the Lead Consortium Member/ Sole Bidder]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Sub: Appointment of Advanced Metering Infrastructure Service Provider for Smart Prepaid
Metering in BSES Yamuna Power Limited on DBFOOT basis

Ref: [Tender Details]

Dear Sir/ Madam,

We, ……................… [Insert name of the undersigned Sole Bidder/ Consortium Member] Sole
Bidder/ Member of Consortium andLead by ……................… [Insert name of the Lead Consortium
Member] have read, examined and understood the RFP and RFP Documents for Appointment of
AMISP for Smart Prepaid Metering Solution.
BSES

We hereby confirm our concurrence with the RFP including in particular the Bid / and Consortium
Agreement submitted by ……................… [Insert name of the Sole Bidder/ Lead Consortium
Member], in response to the RFP. We confirm that the Bid has been reviewed and each element of
the Bid is agreed to including but not limited to the commitment and obligations of our Company.

We hereby confirm that in accordance with Clause 2 of Section 1 of the RFP, we are enclosing
legally binding undertaking supported by a board resolution from the
……………………………………………. [insert name of Technically Evaluated Entity and / or
Financially Evaluated Entity or its Ultimate Parent Company, as the case may be] that all the equity
investment obligations of …………………………..[insert name of the Member] shall be deemed to
be equity investment obligations of the ………………………………………….[insert name of
Technically Evaluated Entity and / or Financially Evaluated Entity or its Ultimate Parent Company,
as the case may be] and in the event of any default…………………………………………………..
[Insert name of the Member], the same shall be met by………………………………………………...
[Insert name of Technically Evaluated Entity and / or Financially Evaluated Entity or its Ultimate
Parent Company, as the case may be]. [Insert if applicable]

Please note further that notwithstanding anything stated in tender document/contract and/or other
document, it is clarified that all the members of consortium including lead member shall jointly and
severally be liable to comply the terms of contract/tender terms. That all the members of
consortium including lead member shall jointly and severally be liable for any breach to terms of
contract and shall liable to compensate BYPL, in full, including the cost/expenses incurred for
getting the work done through third party vendor. That all the members of consortium including
lead member shall jointly and severally be liable to indemnify BYPL from all
losses/penalties/compensation/liabilities arising/relating to the award/execution of work under
contract by consortium.

Page 428 of 473

The details of contact person are furnished as under:
Name :
Designation :
Name of the Company :
Address :
Phone Nos. :
Fax Nos. :
E-mail address :

Dated the ……. day of ……. of 20……

Thanking you,
Yours faithfully,
………………………………..
[Signature, Name, Designation of Authorized Signatory of Consortium Member and Company's
Seal]

Business Address:
[Name and address of principal officer]

BSES

Page 429 of 473

Form 12: Format of Summary of Audited Financial Statements
<This form needs to be submitted by Sole Bidder/ Lead Consortium Member. In case of an AIF or
Foreign Investment Fund using ACI, ACI would be considered as per the certificate issued by
statutory auditor (or such other certificate as filed with the regulator in the relevant jurisdiction) not
older than 1 (one) month prior to the date of Bid Submission>

[Reference No.]

From:
[Address of the Lead Consortium Member/ Sole Bidder]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Sub: Audited Financial Statement for.................. [Insert name of Sole Bidder/Consortium

Member].
Ref: [Tender Details]

Dear Sir/ Madam,

BSES

This is to certify that.................. [Insert name of Sole Bidder/Consortium Member] having its
Registered Office at.......................................... [Insert Registered Address of the Consortium
Member] are in the business of....................................... [Insert briefly the nature of the business],
have recorded the following:

NET WORTH FOR LAST THREE FINANCIALYEARS

Name of Financially Relationship with Financial Year Net worth Amount (In
S. No.
9. Evaluated Entity(ies) Bidder (FY) Indian Rupees)
1.
2.
3.

Or

ACI FOR PRECEDING FINANCIAL YEAR

Name of Financially Relationship Financial Year ACI Amount (In Indian
S. No.
Evaluated Entity(ies) with Bidder (FY) Rupees)
1.
2.
3.

The above Net worth/ ACI are arrived from our Audit Reports for the last three/ preceding13
financial years duly submitted to the Income Tax Department along with our Audit Reports.

13
In case ACI is used to meet the financial requirements

Page 430 of 473

Hence, we certify from the records submitted to us. Thanking you,

Sincerely yours,

Yours Sincerely,
[Insert Signature here]
[Insert Name here]
[Insert Designation here

Date: [Date]

Place: [Place]

BSES

Page 431 of 473

Form 13: Record of Similar Work Done

Confirm
Name of attachment of
No. of PO/ WO Confirm
Technically Relationship with Date of Contract Description of Installation
S. Consumer, Value attachment of
Evaluated Entity the Bidder PO/WO Period Work Milestone/
No. Nodes, etc. (In INR) PO/ WO
(ies) execution
certificate
1.

2.

3.

4.

5.
BSES

Page 432 of 473

Form 14: List of Material and Services
Please Note: The list is indicative only. This needs to be detailed out and customized by [AMISP]
basis Project requirement

Table 1: List of Materials and Services for Smart Meters [Indicative Only. To be defined by
AMISP]

Country of
S. No. Item Description
Origin
1. Installation & Commissioning
1.1 Supply, Installation, Commissioning & Testing & Integration with Existing
System (if any)
1.2
.. ..
2. Other Requirement
2.1 Any other product/ services,if required, along with details.
3. Communications Hardware
3.1 NIC/ Communication Module (price to be quoted only for sourcing
additional quantity if required.
3.2 Data Concentrator Units/Access points
.... ......

Table 2: List of Materials and Services for Software [Indicative Only. To be defined by
AMISP]
BSES

Country
S. No. Item Description
of Origin
1. Application Software
1.1 Meter Data Acquisition Software (MDAS)/Head End System (HES)
1.2 Meter Data Management system (MDMS).....
1.3 Pre-Payment application Module
1.4 Advanced Data Analytics Software
1.5 Consumer Mobile Application / Web Portal
2. Data Archiving Software
2.1 Data Archiving and SAN Management Software
2.2 ....
.. ..
3. Network Management Software
Centralized network management software along with patch
3.1
management & identity management
Antivirus software for all machines in Network Operation cum Monitoring
3.2
Centre
3.3 Access control software with single sign on feature
… ….
.. ..
4. Installation & Commissioning
Supply, Installation, Commissioning & Testing & Integration with
4.1
ExistingSystem (if any)

Page 433 of 473

 Country
S. No. Item Description
of Origin
4.2 ....
.. ..
5. Cellular Data and Cloud Services
5.1 4G / NBIoT data Services as per TPA
5.2 Cloud Hosting Services

Table 3: List of Materials and Services for Hardware [Indicative Only. To be defined by AMISP]

Country of
S. No. ItemDescription
Origin
1. Hardware for Smart Metering Operation Center
1.1 Workstation consoles
1.2 Firewall
1.3 Router
.. ..
2. Mandatory Spares
2.1 X% of Subtotal1
2.2 ....
.. ..
3. Installation& Commissioning
3.1 Supply, Installation, Commissioning & Testing & Integration with Existing
System (if any)
3.2 ....
.. ..
BSES

4. Other Requirement
4.1 Any other product/ services, if required, along with details.

Table 4: List of Materials and Services for Training [Indicative Only. To be defined by AMISP]

S. Country of
Item Description
No. Origin
1. Training at Site
1.1
1.2 HES & MDMS, Protocol, Database, User Interface, Display and
Application software
1.3 Computer System Hardware & Software
1.4 ....
.. ..

Table 5: List of Materials and Services for Operation and Maintenance [Indicative Only. To
be defined by AMISP]

S. Country of
Item Description
No. Origin
1. 10. Operation and Maintenance
1.1 Operation of complete system (during warranty period) including providing
communication link to Network Operation cum Monitoring Center (SMOC)

Page 434 of 473

 S. Country of
Item Description
No. Origin
as well as network connectivity for Cellular services for AMI System

1.2 Maintenance of complete System during AMI operations period

1.3 ....

Table 6: List of Materials and Services for Consumer Engagement Activities [Indicative Only.
To be defined by AMISP]
S. No. Item Description Country of Origin
1. Consumer Engagement Activities
1.1 Consumer engagement plan
1.2 Communication and media plan
1.3 ..
2 Implementation support for consumer engagement activities
as per point 1
2.1 Knowledge Materials/ Tools/ Brochures
BSES

2.2 Social media campaigns

2.3 Press release/ ads/ newsletters
2.4 Videos/ Film
2.5 Consumer Surveys
.. ..

Page 435 of 473

Form 15: Table of Compliance
The Bidder shall submit ‘Clause by Clause’ compliance to the RFP document including the technical
specifications and functional requirements (with amendments, if any) as per the format prescribed in
Form 15.

The Bidder shall annotate the Table of Contents of each section to provide a high-level summary of
compliance status. In all cases, the following symbols, and no others shall be used:

 C - Bid complies with all requirements in the adjacent paragraph.

 A - Bid is not compliant with the requirements in the adjacent paragraph, but a functional
alternative is proposed.
 X - Bid takes exception to the requirements of the adjacent paragraph and no functional
alternative is proposed.
Only one symbol shall be assigned to paragraph and shall indicate the worst-case level of
compliance for that paragraph. This annotation may be handwritten.

The Bidder shall also underline, on the compliance copy, all requirements to which exceptions have
been taken (X) or to which alternatives have been proposed (A).

Each alternative shall be clearly and explicitly described. Such descriptions shall use the same
paragraph numbering as the bid document sections addressed by the alternatives. All alternative
descriptions shall be in one contiguous section of the bidder’s proposal, preferably in the same
volume, and titled "Alternatives." A separate section titled "Exceptions" shall also be provided
containing any discussion or explanation chooses to provide concerning exceptions taken.
Alternatives which do not substantially comply with the intent of the Bid documents will be
considered exceptions. BSES

Any clause which is not included in this compliance table shall be treated as “fully complied” or C.

The BYPL will assess the merits of each alternative and exception and will be the sole judge as to
their acceptance.

Page 436 of 473

Form 16: Format for Technical & Financial Requirement- Relationship &
Details of Equity Shareholding
[Reference No.]
From:
[Address of the Lead Consortium Member/ Sole Bidder]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Sub: Appointment of Advanced Metering Infrastructure Service Provider for Smart Prepaid Metering
in BSES Yamuna Power Limited on DBFOOT basis

Ref: [Tender Details]

Dear Sir/ Madam,

We certify that M/s …………………..[insert name of the Sole Bidder / Consortium Members] have
considered the technical and financial capability of its Parent and / or Affiliates, for the purpose of
meeting Qualification Requirements as per the instructions provided in the RFP. The name of Parent
and / or Affiliate, nature of relationship(s) with such Parent and / or Affiliate and details of equity holding
are as follows:
Name of Type of credentials BSES
Relationship with Sole
Details of equity
Company whose considered Bidder / Consortium
shareholding (refer
credentials (technical and / or Member (Parent /
notes below)
considered financial) Affiliate)
Company 1
………..
………..
………..
………..

NOTES:

i) In case of Parent, the equity holding of the Parent in the Sole Bidder / Member of the Bidding
Consortium, including the Lead Member of the Consortium, need to be specified,
ii) In case of Affiliate under direct control of Bidder, the equity holding of the Sole Bidder / Member
of the Bidding Consortium, including the Lead Member of the Consortium in the Affiliate, needs
to be specified.
iii) In case of Affiliate under common control of Parent, the equity holding of the Parent in the
Affiliate of the Sole Bidder / Member of the Bidding Consortium, including the Lead Member of
the Consortium, needs to be specified.

iv) Relationship Of Parent / Affiliate with Sole Bidder / Member Of Consortium to be at the most
seven (7) days prior to the Bid Deadline (as per Clause 2 of Section 1 of the RFP)

Page 437 of 473

Yours faithfully
………………………………
(Signature and name of the authorized signatory of the Company and stamp)

Name: …………………………….
Date: ………………………………
Place: ………………………………

………………………………
(Signature and Stamp of statutory Auditors of Sole Bidder / each Member ofBidding Consortium)

Name: …………………………….
Date: ………………………………
Place: ………………………………
Date: ………………………………

BSES

Page 438 of 473

Form 17: Authorization from Parent / Affiliate of Sole Bidder / Member of
Bidding Consortium Whose Technical / Financial Capabilities
has been used by the Sole Bidder / Member of Bidding
Consortium

[On the Letter Head of the Parent /Affiliate]

[Reference No.]
From:
[Address of the Parent / Affiliate of Bidder / Member of Bidding Consortium]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Dear Sir,
Sub: Appointment of Advanced Metering Infrastructure Service Provider for Smart Prepaid Metering
in BSES Yamuna Power Limited on DBFOOT basis

We refer to the RFP dated……………………. ('RFP') issued by you for selection of Bidder as
Advanced Metering Infrastructure Service Provider for establishing the AMI System
for"……………………………………[Name of Project]".

We confirm that M/s......................... [insert name of Sole Bidder/ Consortium Member] has been
BSES

authorized by us to use our technical and/or financial capability [strike out whichever is not applicable]
for meeting the Qualification Requirements for"……………………………...[Name of Project]".

We have carefully read and examined in detail the RFP including in particular, Clause 2 of Section 1
of the RFP, and we are also submitting legally binding undertaking supported by aboard resolution
that all the equity investment obligations of M/s.............................. [Insert Name of Sole Bidder /
Consortium Member], shall be deemed to be our equity investment obligations and in the event of any
default the same shall be met by us.
For and on behalf of …………………………… [insert Name of Parent / Affiliated]
………………………………………
[Signature and Name of the authorized signatory of the Company and stamp]

Name: …………………………….
Date: ………………………………
Place: ………………………………
Notes:

1. The above undertaking can be furnished by Ultimate Parent of Technically Evaluated Entity or
Financially Evaluated Entity, as the case maybe, if legally binding undertaking is also
furnished by the Ultimate Parent on behalf of such Financially Evaluated Entity/Technically
Evaluated Entity.

Page 439 of 473

Form 18: Format of Undertaking by Technically / Financially Evaluated
Entity / Ultimate Parent Company
[On the Letter Head of the Technically / Financially Evaluated Entity / Ultimate Parent Company]

[Reference No.]
From:
[Address of the Technically / Financially Evaluated Entity / Ultimate Parent Company]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Sub: Appointment of Advanced Metering Infrastructure Service Provider for Smart Prepaid Metering
in BSES Yamuna Power Limited on DBFOOT basis

Dear Sir,
We refer to the Request for Proposal dated …………….. ('RFP') issued by you regarding setting upof
AMI system for ……………………. [Name of the Project] on design, build, finance, own, operate and
transfer basis.

We have carefully read and examined in detail the RFP and the RFP Project Documents, regarding
submission of an undertaking regarding the investment in the equity share capital of
……………………..[Name of the BIDDER] and provisions for minimum equity holding and equity lock-
BSES

in. We have also noted the amount of the equity investment required to be made
in…………………………[Name of BIDDER] by the ………………………..[insert the name of the
Bidder or the Consortium Member] for the Project.

In view of the above, we hereby undertake to you and confirm that in the event of failure of
……………….....[insert the name of the Bidder or the Consortium Member] to invest in full or in part,
in the equity share capital of ………………………….[Name of BIDDER] as specified in the Bid, we
shall invest the said amount not invested by …………………………………….. [insert the name of the
Bidder or the Consortium Member] in …………………………………… [Name of BIDDER] by purchase
of existing shares or subscribing to the new shares of …………………………… [Name of the
BIDDER], as stipulated by you.

We have attached hereto certified true copy of the Board resolution whereby the Board of Directors
ofour Company has approved issue of this Undertaking by the Company.

All the terms used herein but not defined, shall have the meaning as ascribed to the said terms under
the RFP.
Certified as true.
…………………………………
(Signature and Name of the authorized signatory of the Company and stamp)

Note:
1. Wherever required, extract of the charter documents and documents such as a Board
resolution should be submitted for verification.

Page 440 of 473

Form 19: Formats for Board Resolutions – Stands Deleted

Format 1
Format of the Board resolution for the Sole Bidder / each Member of the Consortium /
investing Affiliate / Parent Company / Ultimate Parent Company, where applicable

[Note: The following resolution no. 1 needs to be passed by the Boards of each of the entity (ies)
making equity investment]

The Board, after discussion, at the duly convened Meeting on ……………………. [Insert date]. With
the consent of all the Directors present and in compliance of the provisions of the Companies Act.
1956/2013 passed the following Resolution:

1. RESOLVED THAT pursuant to the provisions of the Companies Act, Companies Act 2013 and
compliance thereof and as permitted under the Memorandum and Articles of Association of the
company, approval of the Board be and is hereby accorded for investment of ..........% (......per
cent) of the total equity share capital…………………..[Name of BIDDER] representing the entire
amount proposed to be invested by the company for the AMI system for ………………………
[Name of Project], as per the terms of the RFP.

[Note: Equity investment obligations by the Sole Bidder/each Member of the Bidding
Consortium/investing Affiliate or Parent or Ultimate Parent should add up to 100%]

[Note: In the event the Bidder is a Bidding Consortium, the following Board resolution no. 2 also
needs to be passed by the Lead Member of the Bidding Consortium]
BSES

2. RESOLVED THAT approval ofthe Board be and is hereby accorded to contribute such further
amount over and above the ……… percentage (…… %) limit to the extent becoming necessary
towards the total equity share in the ……………….. [Name of BIDDER]. Obligatory on the part of
the company pursuant to the terms and conditions contained in the Consortium Agreement dated
................executed by the company as per the provisions of the RFP.

[Note: In the event, the investing entity is an Affiliate or Parent or Ultimate Parent of the Bidder,
the following Board resolution no. 3 shall also be passed by the Bidder]

3. FURTHER RESOLVED THAT the Board hereby acknowledges the Board Resolution(s) passed
by the.......................... [Name of the Affiliate(s)/ Parent / Ultimate Parent] regarding the investment
of.......... (.... %) of the equity share capital requirements of …………………….[Name of BIDDER],
which is to be invested by the ..................................[Name of the Affiliate(s)/ Parent / Ultimate
Parent] for the …………………….. [Name of BIDDER]. as per the terms of the RFP.

[Note: The following resolution no. 4 is to be provided by the Sole Bidder / Lead Member of the
Consortium only]

4. FURTHER RESOLVED THAT MR/MS ............................................be and is hereby authorized to

take all the steps required to be taken by the Company for submission of the Bid, including in
particular, signing of the Bid, making changes thereto and submitting amended Bid, all the
documents related to the Bid, certified copy of this Board resolution or letter or undertakings etc,
required to be submitted to BYPL as part of the Bid or such other documents as may be
necessary in this regard.

Certified True Copy

Company rubber stamp to be affixed

Page 441 of 473

 [Notes:
1. This certified true copy should be submitted on the letterhead of the Company, signed by the
Company Secretary or any Whole Time Director/ Manager (supported by a specific board
resolution) of the SoleBidder or the Lead Member of Consortium.
2. The contents of the format may be suitably re-worded indicating the identity of the entity
passing the resolution, i.e., the SoleBidder, each Member of the Bidding Consortium.
3. This format may be modified only to the limited extent required to comply with the local
regulations and laws applicable to a foreign entity submitting this resolution. For example,
reference to Companies Act 1956 / Companies Act 2013 (as the case may be) may besuitably
modified to refer to the law applicable to the entity submitting the [Link], in such
case, the foreign entity shall submit an unqualified opinion issued bythe legal counsel of such
foreign entity, stating that the Board resolutions are incompliance with the applicable laws of
the respective jurisdictions of the issuing company and the authorizations granted therein are
true and valid.]

Format 2
Format for the Board resolution of Technically / Financially Evaluated Entity / Ultimate Parent
Company (in case credentials of such TEE/ FEE has been utilized bythe Sole Bidder or Bidding
Consortium)

The Board, after discussion, at the duly convened Meeting on …………………….. [Insert date] with
the consent of all the Directors present and in compliance of the provisions of the Companies Act,
1956 2013. passed the following Resolution:

RESOLVED THAT pursuant to the provisions of the Companies Act, Companies Act, 2013 and
BSES

compliance thereof and as permitted under the Memorandum and Articles of Association of the
company, approval of the Board be and is hereby accorded for issuing an Undertaking to the BYPL, in
the format specified in the RFP issued by the BYPL, draft of which is attached hereto and initiated by
the Chairman whereby the company undertakes to invest ……………………….. percent (……%) of
the total equity share capital of ……………………………..[Name Of BIDDER] representing the entire
amount proposed to be invested by ………………………………….. [ insert name of the Bidder or
Member] for the said Project, in case of failure of …………………………. [Insert the name of the
Bidder or Member] to make such investment".

FURTHER RESOLVED THAT …………………………………….. be and is hereby authorized to take

all the steps required to be taken by the Company, including in particular, signing the said
Undertaking, submitting the same to the BYPL through ………………………………....[insert name of
Sole Bidder / Lead Member of the Consortium] of all the related documents, certified copy of this

Board resolution or letter, undertakings etc. required to be submitted to BYPL as part of the Bid or
such other documents as may be necessary in this regard.

Certified True Copy

Company rubber stamp to be affixed

Note:

Page 442 of 473

 1. This certified true copy should be submitted on the letterhead of the Company, signed by the
Company Secretary or any Whole-time Director/Manager (supported by a specific board
resolution) of Sole Bidder or Lead Member of the Consortium.
2. The contents of the format may be suitably re-worded indicating the identity Of the entity
passing the resolution.
3. This format may be modified only to the limited extent required to comply with the local
regulations and laws applicable to a foreign entity submitting this resolution. For example,
reference to Companies Act 2013 (as the case may be) may be suitably modified to refer to the
law applicable to the entity submitting the resolution. However, in such case, the foreign entity
shall submit an unqualified opinion issued by the legal counsel of such foreign entity, stating
that the Board resolutions are in compliance with the applicable laws of the respective
jurisdictions of the issuing company and the authorizations granted therein are true and valid.

Annexure: Illustration for Applicable Board Resolution Requirements

<Please Note: The list is indicative only. This needs to be detailed out and customized by BYPL basis
project requirement. The quantity of smart meters to be installed should be based upon As-Is
consumer database as well as projected load growth in the selected AMI Project Area during the
Contract Period. Any variation in GST and or cess on the Items specifically mentioned above shall be
on account of the BYPL and not other items including hardware and software that may be necessary
for putting the AMI system in place>

Table: Bill of Materials and Services for Smart Meters. To be filled by AMISP. The Total Quantity of
Smart Meters and Lump sum payment amount to be defined by the BYPL

BSES

Entities (other than

Bidder) whose
Requirement of
Investor in credentials (financial Applicable Board
Undertaking
the AMISP and/or technical) used Resolutions
(Form 18)
by the Bidder for
meeting RFP criteria
Bidder himself a) Format I of Form 19-
for100% None Resolution:1,2and4from the None
equity Meter Bidder
Yes, by either
Technically
a) Format I of Form 19 - /Financially
Resolution: l, 2, and4 from the Evaluated Entity
Bidder (ies) Affiliate(s)
b) Format 2 of Form 19 by either whose credentials
Bidder himself Affiliate and/or Parent Technically/Financially Evaluated have been used,
for100% Company and/or Ultimate Entity (ies) whose credentials or Ultimate Parent.
equity Meter Parent have been used, or Ultimate
Parent. Provided, if the
Provided. If the Bidder himself is Bidder himself is
the Ultimate Parent, then Format the Ultimate
2need not be provided. Parent, then the
undertaking need
not be provided.
Bidder himself a) Format 1 of Form 19 -
11. None 12. None
+others Resolution: 1,2, 3 and4 from the

Page 443 of 473

 Entities (other than
Bidder) whose
Requirement of
Investor in credentials (financial Applicable Board
Undertaking
the AMISP and/or technical) used Resolutions
(Form 18)
by the Bidder for
meeting RFP criteria
(Affiliate Bidder.
and/or Parent b) Format I of Form 19 -
Company Resolution: I from the Affiliate
and/or and /or Parent and /or Ultimate
Ultimate Parent investing in the equity
Parent) in
aggregate
holding100%
equity
a) Format 1 of Form 19 -
Bidder himself Resolution: 1,2, 3 and 4 from the
+ Bidder.
Others
(Affiliate b) Format I of Form 19 -
Yes, by either
and/or Parent Resolution: I from the Affiliate
Affiliate and/or Parent Parent/Affiliate(s)
Company and/or Parent and/or Ultimate
Company and/or Ultimate whose credentials
and/or Parent investing in the equity
Parent have been used,
Ultimate
or Ultimate Parent
Parent) in c) Format 2 of Form 19 by either
aggregate Parent / Affiliate(s)
holding whose credentials have been
100% equity used and /or Ultimate Parent
BSES

investing in the equity

Page 444 of 473

Form 20: Format for EMD Bank Guarantee
(To be issued in a Non-Judicial Stamp Paper of Rs.100/-purchased in the name of the bank)

Whereas [name of the Bidder] (herein after called the “Bidder “) has submitted its bid dated [date of
submission of bid] for the supply/service of [name and/or description of the goods] (here after called
the “Bid”).

KNOW ALL PEOPLE by these presents that WE [name of bank] at [Branch Name and address],
having our registered office at[address of the registered office of the bank](herein after called the
“Bank“),are bound unto BSES Yamuna Power Ltd., with its Corporate Office at Shakti Kiran Building
,Karkardooma, Delhi 110032 ,(herein after called —the “Purchaser“)in the sum of Rs. ……………/-
(Rupees ………………………………. only) for which payment well and truly to be made to the said
Purchaser, the Bank binds itself, its successors, and assigns by these presents.
Sealed with the Common Seal of the said Bank this_____ day of________ 20____.

THE CONDITIONS of this obligation are:

1. If the Bidder withdraws its Bid during the period of bid validity specified by the Bidder on the
Bid Form; or
2. If the Bidder, having been notified of the acceptance of its Bid by the Purchaser during the
period of bid validity:
a. Fails or refuses to execute the Contract Form, if required; or
b. Fails or refuses to furnish the performance security, In accordance with the Instructions to
Bidders/ Terms and Conditions;

We undertake to pay to the Purchaser up to the above amount upon receipt of its first written demand,
without the Purchaser having to substantiate its demand, provided that is its demand the purchaser
will note that amount claimed by it is due to it, owing to the occurrence of one or both of the two
BSES

condition(s), specifying the occurred condition or condition(s).

This guarantee will remain in force up to and including One Hundred Eighty (180) days after the due
date of submission bid, and any demand in respect thereof should reach the Bank not later than the
above date.

(Stamp & signature of the bank)

Signature of the witness

Page 445 of 473

Form 21: Acceptance Form for Participation in Reverse Auction Event –
Stands Deleted
(To be signed & stamped by the bidder along-with bid)

BSES Yamuna Power Ltd (BYPL) intends to use reverse auction through SAP-SRM tool as an
integral part of entire tendering process. All techno-commercially qualified bidders shall participate in
the reverse auction.

The following terms and conditions are deemed as accepted by the bidder on participation in the
bid:-
1. In case of bidding through Internet medium, bidders are advised to ensure availability of all
associated infrastructure as required to participate in the reverse auction event. Inability to bid
due to telephone glitch, internet response issues, software & hardware hangs/failures, power
failures or any other reason shall not be the responsibility of BYPL.
2. In case bidder fails to participate in the reverse auction event due to any reason whatsoever, it
shall be presumed that the bidder has no further discounts to offer and the initial bid submitted
by them as a part of tender shall be considered as bidder’s Final No Regret offer. Any off-line
price bids received from a bidder in lieu of non-participation in the reverse auction event shall
be rejected by BYPL.
3. The bidder is advised to understand the auto bid process to safeguard themselves against any
possibility of non-participation in the reverse auction event.
4. The bidder shall be prepared with competitive price quotes during the day of reverse auction
event.
5. The prices quoted by bidder in reverse auction event shall be on FOR Landed cost BYPL
Store/site basis inclusive of all relevant taxes, duties, levies, transportation charges etc.
6. The prices submitted by the bidder during reverse auction event shall be binding on the
Bidder.
BSES

7. The bidder agrees to non-disclosure of trade information regarding bid details e.g. purchase,
Identity, bid process/technology, bid documentation etc.
8. BYPL will make every effort to make the bid process transparent. However award decision of
BYPL will be final and binding on the bidder.
9. The prices submitted during reverse auction event shall be binding on the bidder.
10. No request for Time extension of the reverse auction event shall be considered by BYPL.
11. BYPL shall provide the user id and password to the authorized representative of the bidder.
Authorization letter in lieu of the same shall be submitted along with the signed and stamped
acceptance form.

The original price bids of the bidders shall be reduced on pro-rata basis against each line item based
on the final all-inclusive prices offered during conclusion of the reverse auction event for arriving at
contract amount.

Page 446 of 473

Form 22: Commercial Terms and Conditions

S. Item BIDDER’S
AS PER BYPL
No. Description CONFIRMATION
1 Validity 180 days from the due date of submission or
amended due date of submission
2 Price basis a) Firm, FOR Delhi store basis. Prices shall be
inclusive of all taxes & duties, freight up to Delhi
stores.
b) Unloading at stores - in vendor's scope
c) Transit insurance in AMISP scope
3 Payment As per Section–5: Special Terms and
terms Conditions,
Clause – 5.0 of NIT Document.
4 Completion Completion Period
time Bidder shall complete phases as per following
timelines from date of award of contract / LOI
and complete phases as below::
a) Phase 1 -9 months from award of contract/LOI
c) Phase 2 – 21 months from award of
contract/LOI
5 Defect Liability One Hundred Twenty months (120) from the
period date of the commissioning or One Hundred
Twenty Six months (126) from the last date of
receipt of material (last consignment) at
site/stores whichever is earlier
BSES

6 Liquidated 50% (Fifty percent) of AMISP Service Charge

Damages for each delayed meter for each completed
/Penalty month of delay for a maximum period of 12
(twelve) months.
7 Contract 3% (Three percent) of the Contract Price valid
Performance up to defect liability period plus 3 months or as
Bank per latest RBI Guidelines, whichever is higher
Guarantee towards claim period.

Page 447 of 473

Form 23: Bid Form
To
Head of Department
Contracts & Material Deptt.
BSES Yamuna Power Ltd
Delhi 110032
Sir,

1. We understand that BYPL is desirous of execution of

……………………………………………………………………………………(Name of work)
2. Having examined the Bidding Documents for the above named works, we the undersigned,
offer to deliver the goods in full conformity with the Terms and Conditions and technical
specifications for the sum indicated in Price Bid or such other sums as may be determined in
accordance with the terms and conditions of the contract. The above amounts are in
accordance with the Price Schedules attached herewith and are made part of this bid.
3. If our Bid is accepted, we undertake to deliver the entire goods as) as per delivery schedule
mentioned in Section V from the date of award of purchase order/letter of intent.
4. If our Bid is accepted, we will furnish a Contract Performance Bank Guarantee for an amount
of 10% (Ten)percent of the total contract value for due performance of the Contract in
accordance with the Terms and Conditions.
5. We agree to abide by this Bid for a period of 180 days from the due date of bid submission &
subsequent corrigendum/amendment/extension of due date of submission. It shall remain
binding upon us and shall be accepted at any time before the expiration of that period.
6. We declare that we have studied the provision of Indian Laws for supply of
equipment’s/materials/services and the prices have been quoted accordingly.
7. Unless and until Letter of Intent is issued, this Bid, together with your written acceptance
thereof, shall constitute a binding contract between us and BYPL.
BSES

8. We understand that BYPL is not bound to accept the lowest, or any bid BYPL may receive.
9. We agree and shall abide with the terms of tender document, in full, including provision for
Resolution of Disputes and Jurisdiction, specified under this Contract.

Dated this............................... day of................................................. 20…..

Signature.............................................. In the capacity of

………………………………..................................................................duly authorized to sign for and

on behalf of

(IN BLOCK CAPITALS)...............................................................................

Page 448 of 473

Form 24: Litigation History

Whether
Cause of Pending as
Details of Details of Court /
Name of Litigation/ Disputed on the date of
Year contract & Current Stage of
client arbitration amount submission
date Case
and dispute of BID
Documents

BSES

Page 449 of 473

Form 25: Financial Data
(Duly Certified by Chartered Accountant with UDIN No)

Parameter Actual in 3 FY
Total assets FY 22-23 FY 21-22 FY 21-20
Current assets
Total Liability
Current Liability
Profit before taxes
Profit after taxes
Sales Turnover

BSES

Page 450 of 473

Form 26: Checklist / Document to be submitted

S.
Description Compliance Page No
No.
1 INDEX YES/NO
2 COVERING LETTER YES/NO
3 BID FORM (UNPRICED) DULY SIGNED YES/NO
4 BILL OF QUANTITY (UNPRICED) YES/NO
DOCUMENTS IN SUPPORT OF QUALIFICATION YES/NO
5
CRITERIA
6 TECHNICAL BID YES/NO
ACCEPTANCE TO COMMERCIAL TERMS AND YES/NO
7 CONDITIONS
8 FINANCIAL BID (IN SEALED ENVELOPE) YES/NO
9 EMD IN PRESCRIBED FORMAT YES/NO
DEMAND DRAFT OF RS 1180/- DRAWN IN FAVOUR OF YES/NO
10
BSES YAMUNA POWER LTD
POWER OF ATTORNEY/AUTHORISATION LETTER FOR YES/NO
11
SIGNING THE BID
12 FINANCIAL DATA IN TABULAR FORMAT YES/NO
LIST OF CURRENT COMMITMENTS/ WORK IN YES/NO
13
PROGRESS
14 BANK SOLVENCY CERTIFICATE YES/NO
15 NO LITIGATION CERTIFICATE YES/NO
16 COMMENTS AS PER ANNEXURES BSES
YES/NO

Page 451 of 473

Form 27: Submission before Commencement of Work

The Bidder must submit the following to Engineer-In-Charge before commencement of work:
a. An Electrical license. (If applicable)
b. PF Code No. and all employees to have PF A/c No. under PF every Act, 1952.
c. All employees to have a temporary or permanent ESI Card as per ESI Act.
d. ESI Registration No.
e. PAN No.
f. Work Contract Tax/GSTN Registration Number.
g. Labour License under Contract Labour Act (R & A) Act 1970 (All Engineer-in-charge
responsible for execution of the job should obtain a copy of Labour License as per guidelines
of HR department before start of the work by the Bidder.)
h. Third party Insurance Policy before start of work.

The Bidder must follow:

a. To follow Minimum Wages Act prevailing in the state.
b. Salary/ Wages to be distributed in presence of Company's representative not later than 7th of
each month.
c. To maintain Wage- cum - Attendance Register.
d. To maintain First Aid Box at Site.
e. Latest P.F. and E.S.I. challans pertaining to the period in which work was undertaken along with
a certificate mentioning that P.F. and E.S.I. applicable to all the employees has been deducted
and deposited with the Authorities within the time limits specified under the respective Acts.
f. Workman Compensation Policy. (If applicable)
g. Labor license before start of work. (If applicable)
BSES

Page 452 of 473

Form 28: Check List- Documents

Remarks By
S. No. Documents
Engineer In Charge
1 Invoice Movement Sheet
2 Work Measurement Sheet
3 Work Summary
4 Meter not return to Store Details
5 Material Reconciliation Statement
6 Material Issued from Store Details
7 Previous Month Material Balance Copy
8 Material Received/Transfer (If any, then copy Required)
9 Complaints Sheet
10 Deductions/Retention Sheet
10 Scrap Declaration with SAP Docket
11 MCR Book & Lab Testing Notice Reconciliation Sheet)
12 Photographs CD with CA No. wise Renaming

BSES

Page 453 of 473

Form 29: List of safety Gears and Tools and Tackles
List of Safety Gears:
1. Rubber Hand Gloves
2. Safety Belts
3. Safety Shoes
4. Helmet with Wiser
5. Safety Rope

Tools & Tackles :

1. Drilling Machine
2. Drilling Bit
3. Measuring Tape
4. Hacksaws
5. Crimping Tool
6. Ball pen Hammer
7. Spanner Set
8. Line Testers
9. Screw driver set (Insulated)
10. Cable Cutters
11. Self Adhesive Tape
12. Combination Pliers

BSES

Page 454 of 473

Form 30: Non-Disclosure Agreement
This Agreement, made this ______ day of ________,20___, at ___________

BETWEEN

BSES Yamuna Power Limited, a power BYPL Company incorporated under the provisions of the
Companies Act, 1956 and having its registered office at Shakti Kiran Building , Karkardooma, New
Delhi 110032 (hereinafter referred to as "BYPL”), which expression shall, unless it be repugnant to the
context or meaning thereof, be deemed to mean and include its successors-in-business and assigns)
and

AND
<Client Company Name>…………………………………….........................…………………, a
Company incorporated under the provisions of the Companies Act, <Year>............ and having its
registered office at <Client Company Address>
......……………………...........................................………………....……………………………………..,
(hereinafter referred to as "<Vendor"), which expression shall, unless it be repugnant to the context or
meaning thereof, be deemed to mean and include its successors-in-business and assigns) of the
Other Part;
WHEREAS:

“BYPL” a power BYPL Company is engaged in the business of Distribution of Electricity

A. “BYPL” requires the services of “<Client Company Name>……………………………………….”
for providing solutions which shall broadly focus on
<purpose>…………………………………………………….. (hereinafter referred to as the
“Purpose”)
BSES

B. B. In the process of providing the services / proof of Concept for the purpose, BYPL
would provide and hand over to the “<Client Company
Name>”………………………………………………………………… the personal, sensitive,
confidential data, and Proprietary Information and Data relating to business operations of
BYPL, its customers and business associates and also technical and technological information
and secrets belonging to BYPL, its customers and business associates

C. BYPL desires to protect the said confidential and proprietary information and data as the
disclosure of confidential information of BYPL to the industry, general public, or third parties
could seriously jeopardize the intellectual property rights/ any other rights of BYPL.

NOW THIS AGREEMENT WITNESSETH AND IT IS HEREBY AGREED BY AND BETWEEN THE
PARTIES HERETO AS FOLLOWS:

1. The term “PERSONAL INFORMATION” and “SENSITIVE PERSONAL DATA” shall have the
meaning as provided in The Information Technology (Reasonable Security Practices and
Procedures and Sensitive Personal Data or Information) Rules, 2011 or as assigned in any
other law in India and as amended from time to time.

2. The term “CONFIDENTIAL INFORMATION” shall include any confidential / proprietary / non-
public information relating to the business of the respective parties, including but not limited to
samples, formulae, manufacturing/development processes, specifications, drawings and
schematics, however, the “Confidential Information” shall mean and include the technical and
technological information and secrets relating to software, computer system, equipment, local
area network and wide area network, network infrastructure and equipment, network
designs/architecture, system passwords, login-ID’s and commercial , marketing, financial and
other information, data, ideas, programs, operations, processes and documents relating to the

Page 455 of 473

 business or technology of (the “BYPL”) or any of its affiliates which is disclosed either prior to
or after the date of this Agreement by parties i) to each other ii) either of its affiliates or iii) a
third party on or behalf of the BYPL or any of its affiliates, to the other party (the “Vendor”)
either in oral or written form, or through any other form of communication, and which was
designated to be confidential and proprietary and shall include this Agreement as well as the
intention of parties to explore the entering into of a business relationship with each other.

3. ACCEPTANCE TO BYPL INFORMATION SECURITY POLICY

i. BYPL (BSES Yamuna Power Limited) has legal ownership of the contents of all files
created, processed, stored on its computers/ network systems as well as the data/ email/
messages transmitted in its network.
ii. BYPL reserves the right to access the information given to the Vendor/ Consultant for
processing without prior notice whenever there is a genuine need.
iii. BYPL may in order to ensure cyber security/ protection of its data/ resources monitor,
access, retrieve and read the information originating/ transmitted/ terminating in its
network irrespective of user.
iv. All the users accessing the network of BYPL are encouraged not to share their personal
information on the computer/ network of BYPL computers, resouces and removable
disks. If Users choose to share such personal information, the information may be
monitored at the risk of Users.
v. All users/vendors/consultants must return or ensure secure destruction of BYPL
information, storage media, documentation, and computer/networking equipment in a
permissible manner, before they leave a particular assignment, either on transfer or on
the end of the contract or resignation.
vi. The undersigned has read the Information security policies and procedures and
understand the policies and procedures of BYPL. The undersigned agreed to abide by
the information security policies and procedures described therein as a condition of
continued employment / contract. The Vendor undertakes to abide by all the rules and
BSES

regulations applicable to Personal/ Sensitive/ Confidential Data under the Information

Technology Act, 2000, or any other law as applicable from time to time and also the
direction issued by the Regulator, Delhi Electricity Regulatory Commission.
vii. The BYPL has all the rights to claim damages for any loss of Personal/ Sensitive/
Confidential data including any liability arising to the third party due to the default/ failure
of the Vendor to protect such data in terms of present agreement. The liability arising out
of such default shall include the litigation cost, liability payable to third party and also any
loss of reputation/ goodwill caused to the BYPL.
viii. That the Vendor agrees that the Non-compliance of the terms of this agreement and/or
any of the policy of BYPL associated with the privacy policy, can result in disciplinary
actions, revocation of systems privileges and includes termination of
agreements/services, if any, claim of damages and such other actions as specified in
other clauses of this agreement or the principle agreement.

1. EXCLUSIONS TO THE CONFIDENTIALITY AGREEMENT:

Notwithstanding anything contained herein, the obligation as to confidentiality herein shall not
apply to the following, provided the VENDOR can establish the same with a competent proof, that:
a) the CONFIDENTIAL INFORMATION was already in the knowledge of the VENDOR, before its
disclosure by the BYPL
b) the CONFIDENTIAL INFORMATION, at the time of its disclosure by the BYPL to the
VENDOR, was in public domain;
c) the CONFIDENTIAL INFORMATION became a part of public domain, after its disclosure by
the BYPL to the VENDOR, either by publication or otherwise, except through the breach of this
Agreement.
d) the CONFIDENTIAL INFORMATION was received by the VENDOR from a third party who
was in possession of the same without violation of the obligation as to confidentiality;

Page 456 of 473

 e) the CONFIDENTIAL INFORMATION was independently developed by the VENDOR, without
the breach of this Agreement;
f) the CONFIDENTIAL INFORMATION was required to be disclosed under the law;

The Information shall not be deemed to be in the public domain merely by the reason that it is
known to a few members of the public to whom it might be of commercial interest. Further, a
combination of two or more parts of the information shall not be deemed to be in the public domain
merely by the reason of each separate part thereof being so available in public domain.

2. OBLIGATIONS OF THE VENDOR

a. The VENDOR shall use the CONFIDENTIAL INFORMATION exclusively for the purposes of
contract awarded/to be awarded and shall not share the same otherwise to any third party,
directly or indirectly, without the express consent of the BYPL (which consent may be withheld
arbitrarily, and shall keep the same strictly confidential.
b. The VENDOR shall ensure that the CONFIDENTIAL INFORMATION is not accessible to
anyone other than those who are required to have such access for the purpose of the
EVALUATION.
c. The VENDOR may disclose the CONFIDENTIAL INFORMATION to such of its employees or
associates as are directly involved for the purpose of fulfilling the business association entered
into between the parties on a need-to-know basis, provided that the VENDOR shall bind
effectively such employees and / or such associates with a corresponding obligation. In any
event, the VENDOR shall be responsible for any breach of this Agreement by any such
employee or associate.
d. The VENDOR shall notify the BYPL upon its becoming aware of the occurrence of any breach
of this Agreement due to any unauthorised use of CONFIDENTIAL INFORMATION.
e. The VENDOR shall not, without the written permission of the BYPL, make copies of the
BSES

CONFIDENTIAL INFORMATION, or any part thereof.

f. In the event the VENDOR becomes legally compelled to disclose any CONFIDENTIAL
INFORMATION, it shall promptly notify the BYPL about the same, so as to enable the BYPL to
obtain appropriate protective order, if any. The VENDOR will exercise its best efforts to obtain
assurance that confidential treatment will be accorded to the CONFIDENTIAL INFORMATION
so disclosed, and shall make best efforts to diminish losses to the BYPL arising out of such
disclosure. In any event, the VENDOR shall disclose only such part of the CONFIDENTIAL
INFORMATION, as is legally mandatory.
g. The Vendor having access to Personal/ Sensitive/ Confidential data of BYPL shall apply
security standards in a manner compatible to reasonable security standards as applied by the
BYPL including ISO 27001 and other security policies and also in terms of Rule 8 of The
Information Technology (ReasonableSecurity Practices and Procedures and Sensitive
Personal Data or Information) Rules, 2011. The Vendors shall be responsible to ensure
adherence to the security standards of all the access by their employees/ consultants etc
h. The Vendor shall securely delete the Personal/ Sensitive/ Confidential data which comes into
its possession by virtue of this agreement and also sanitize the digital media as per the
Security Policy of the BYPL.
i. The Vendor undertakes to acquaint itself with the Information security policies and procedures
and understand the policies and procedures therein which are published in the intranet. The
undersigned agreed to abide by the information security policies and procedures described
therein as a condition of continued engagement/ contract.

3. RETURN OF CONFIDENTIAL INFORMATION

Immediately upon the decision by the VENDOR to not to continue with any arrangement/
agreement or immediately upon the request of the BYPL, the VENDOR shall promptly return
and/or procure the return of the CONFIDENTIAL INFORMATION, and all copies (whether or not
lawfully made or obtained) of the same or any part of thereof, as well as all analysis, computations,

Page 457 of 473

 studies or other documents or information prepared, which is based upon, contains or refers to or
to any part of, the CONFIDENTIAL INFORMATION, to the BYPL or to any party designated by the
BYPL in this behalf, or destroy the same as may be advised by the BYPL , and shall confirm by
way of a written certificate to that effect to the BYPL , and also further confirm that the VENDOR
has not reproduced or retained any samples, originals or copies of any part of the CONFIDENTIAL
INFORMATION; except that the VENDOR could keep a single copy of the CONFIDENTIAL
INFORMATION solely for the purposes of determining compliance with obligations as to
confidentiality hereunder.

4. TENURE OF THE AGREEMENT

The Agreement shall be valid for a period of __________ years from the date thereof, or till parties
enter into definitive Agreement of business relationship arising out of the or any earlier
determination of this Agreement effected by the BYPL by requisitioning the return of the
CONFIDENTIAL INFORMATION, whichever is earlier. The Vendor shall continue to be liable for
any breach of Personal/ Sensitive/ Confidential data given by the BYPL even after the termination
of main agreement. WARRANTY AS TO ACCURACY OR COMPLETENESS OF THE
INFORMATION

The BYPL makes no representation or warranty as to the accuracy or completeness of the

CONFIDENTIAL INFORMATION disclosed to the VENDOR, and accordingly no liability accrues to
the BYPL for any damage, injury or loss resulting from the use of the CONFIDENTIAL
INFORMATION.

5. RELATIONSHIP PRESUMPTIONS

a. The VENDOR understands and acknowledges that nothing herein creates any presumptions
about any proposed transaction or relationship with the BYPL.
BSES

b. This Agreement does not grant to the VENDOR any proprietary rights to the CONFIDENTIAL
INFORMATION or any licence under any patents, trademarks, copyrights or any other
intellectual property, and all right, title and interest in and to the CONFIDENTIAL
INFORMATION shall remain the exclusive property of the BYPL.

c. Nothing in this Agreement shall be construed by implication or otherwise, as establishing any

relationship of principal and agent or employer and employee between the parties hereto, or
creating or authorising any party to create any commitment on behalf of the other party or any
charge on the other party.

6. INJUNCTIVE RELIEF AND SPECIFIC PERFORMANCE

The VENDOR understands and acknowledges that, due to the unique nature of the
CONFIDENTIAL INFORMATION of the BYPL, any unauthorised disclosure of any portion thereof
shall cause irreparable damage / injury to the interest of the BYPL and that monetary relief will not
be adequate or complete remedy to compensate for such damage/injury. Accordingly, the
VENDOR hereby acknowledges that the BYPL shall be entitled to injunctive relief and / or a
remedy of specific performance in the event of any unauthorised disclosure by the VENDOR or by
any of its said employees or the said associates, in addition to whatever remedies it might have in
law or in equity.

7. ENTIRE AGREEMENT

This Agreement represents the intentions of the parties hereto, in entirety, on the subject matter
hereof, and shall supersede anything outside this Agreement relating to the subject matter hereof.

Page 458 of 473

8. SEVERABILITY

If any part of this Agreement becomes or is discovered to be unlawful and / or unenforceable, and
if the remaining Agreement could be separated from such part, then the remaining Agreement shall
be deemed to continue in such reduced form.

Non-assignment - Save as expressly agreed by the parties hereto in writing, no right or obligation
under this Agreement can be assigned to any other party.

Waiver- No waiver or modification of this Agreement will be binding upon the parties unless made
in writing and signed by a duly authorised representative of such parties. Further, failure or delay
in enforcing any right under this Agreement shall not amount to a waiver of such right.

Modifications - This Agreement may not be modified except in writing, signed by the parties
hereto, through their duly authorised representatives.

Jurisdiction & Arbitration - This Agreement shall be governed by and construed in accordance
with the Laws of India (without reference to the rules relating to the conflict of laws), under the
jurisdiction of the Courts at Delhi.

Any dispute or difference with respect to the construction or interpretation of any of the clauses
hereof, or as to the meaning or effect thereof, which could not be resolved amicably between the
parties hereto, shall be referred to arbitration. The arbitration shall be governed by the Arbitration
and Conciliation Act, 1996, as amended upto date. The arbitration proceedings shall be conducted
by the Sole Arbitrator, jointly appointed by the parties. The Venue and seat of arbitration shall be
Delhi. The fees of the arbitrators shall be shared [Link] language of arbitration shall be
English [Link] award of the arbitral panel shall be final and binding on all parties
BSES

Related Party Acts -

a. Any act or omission which if it were an act or omission of the VENDOR would be a breach of
this Agreement on its part, be deemed to be such an act or omission for which the VENDOR is
responsible when done or omitted to be done by a third party, if –
i) such third party is controlled by or controls, the VENDOR, or
ii) both, such third party and the VENDOR, are under the common control of any
other party

Two originals
This Agreement shall be executed in three copies, each of which shall constitute an original, and
both of which together shall constitute one and the same instrument.

IN WITNESS WHEREOF, the parties hereto have executed this Agreement by their duly
authorised representatives, as on the date hereof.

For For <Client Company>

____________________________ ________________________________
_____ ____

____________________________ ________________________________
____ ______
(name & title) (name & title)

Witnesses: Witnesses:

Page 459 of 473

1. 1.

2.
2.

****** End of NDA (Services) ******

BSES

Page 460 of 473

Form 31: Schedule of Deviations
Vendor shall refrain from taking any deviations on this TENDER. Still in case of any deviations, all
such deviations from this tender shall be set out by the Bidder, Clause by Clause in this schedule and
submit the same as a part of the Technical Bid.

Unless specifically mentioned in this schedule, the tender shall be deemed to confirm the BYPL’s
specifications:

Technical Deviations:-

NIT
Clause Details of Clarification/deviation
SL No. Page NIT Clause descriptions
No. with justifications
No.

Commercial Deviations:-

NIT
SL Clause Details of Clarification/deviation
Page NIT Clause descriptions
No. No. with justifications
No.

By signing this document we hereby withdraw all the deviations whatsoever taken anywhere in this
BSES

bid document and comply to all the terms and conditions, technical specifications, scope of work etc.
as mentioned in the standard document except those as mentioned above.

Seal of the Bidder:

Signature:

Name:

Page 461 of 473

Form 32 – Format for Manufacturer Authorization Form (MAF)
NIT No.:

Name of Package/Schedule/Solution offered:

To,
HEAD OF DEPARTMENT
CONTRACTS & MATERIALS DEPARTMENT.
BSES YAMUNA POWER LTD
KARKARDOOMA,
NEW DELHI 11 0032

Sub: Manufacturer Authorization Form (MAF)

Dear Sir,

That……M/s X having its registered office at………………………………………. and factory /

development centre at are manufacturers of….………………. . That having company
at……………………………………. do hereby authorize……………………………………….to submit a
Bid in relation to the Invitation for Bids indicated above, the purpose of which is to provide the
following Products, manufactured by us…………………………………………….and to subsequently
negotiate and sign the Contract. We hereby extend our full warranty in accordance with warranty
clauses mentioned in the RFP and will provide support during contract period as per the requirement,
with respect to the products offered by the above firm in reply to this Invitation for Bids. Note: This
form needs to be filled by all OEMs.

Authorized Signatories BSES

Name of Bidder___________________________________
Address of Bidder: ________________________________
Phone No: _______________________________________
E-Mail: __________________________________________

Page 462 of 473

Form 33: Format of Sending Pre-Bid Queries to BYPL
<Query may be sent in XLS format to BYPL E-mail ID mentioned in the tender document>

[Reference No.]

From:
[Address of the Lead Consortium Member/ Sole Bidder]
[Telephone No., Fax No., Email]
[Date]

To:
[BYPL]
[Address]

Sub: Pre-Bid Queries.

Ref: [Tender Details]

Dear Sir/ Madam,

Please find below our query with respect to the RFP subject to the terms and conditions therein:

Reference
S. No. Page No. Clause Details Query
Clause No.
1. BSES

2.
3.

Sincerely yours,

Yours Sincerely,
[Insert Signature here]
[Insert Name here]
[Insert Designation here

Date: [Date]

Place: [Place]

Page 463 of 473

Section 9. Contract Related Forms
A. Format for Direct Debit Facility
DETAILS

Name of Account Holder: ______________________________________________________

Mr/Mrs/Miss/Ms First Name: ________________________Last Name: _____________

Address: ___________________________________________________________________

Street: ____________________ Suburb: ____________________ Town/City: ____________

Phone Number: ___________________ Account Number: ____________________________

BANKINGDETAILS
Details of the bank account from which you want to pay your account
AUTHORITY
Bank Account Holder’s Name: TO ACCEPT
DIRECT
Account Number: _____________________________________________________ DEBITS
(Does not operateas
If your suffix has only 2 an assignment
oragreement)
digits please insert a zero
Bank/Branch Account Number Suffix in the first box.
Number
BSES

Bank/Branch:
Authorisation
Branch Address: _____________________________________________________ Code
PO Box:
Town/City: ___________________________________________________________

I/We authorise you until further notice in writing to debit my/our account with all amounts which Spark New
Zealand Limited (here after referred to as the Initiator), the registered Initiator of the above Authorisation Code,
may initiate by Direct Debit. I/We acknowledge and accept that the Bank accepts the authority only upon the
conditions below.

PLEASESIGNHERE

Authorised Signature(s): Date:

___/____/_________

Page 464 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

For Bank Use Only

Approved Date Received: Recorded By: Checked By: Bank Stamp:
____________ ____________ ____________ ____________ ____________

Conditions of this Authority to accept Direct Debit

1. The Initiator: 2. The Customer acknowledges that:

BSES

Page 465 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

a. Has agreed to give advance notice of the net amount of each Direct Debit and the due date
of the debiting at least 10 calendar days before(but not more than 2 calendar months) the
date when the Direct Debit will be initiated. This notice will be provided either:
 In writing: or
 By electronic mail where the Customer has provided prior written consent to the initiator.
b. The advance notice will include the following message: “Unless advice to the contrary is
received from you by (date*), the amount of INR._____________will be directly debited to
your Bank account on (initiating date)”.*This date will be at least two(2) days prior to the
initiating date to allow for amendment of Direct Debits.
c. May, upon the relationship which gave rise to this Instruction being terminated, give notice to
the Bank that no further Direct Debits are to be initiated under the Instruction. Upon receipt of
such notice the Bank may terminate this Instruction as to future payments by notice in writing
ome/us.
d. The Customer may:
e. At any time, terminate this Instruction as to future payments by giving written notice of
termination to the Bank and to the Initiator.
f. Stop payment of any Direct Debit to be initiated under this Instruction by the Initiator by
giving written notice to the Bank prior to the Direct Debit being paid by the Bank
g. Request the Bank to reverse any Direct Debits initiated by the Initiator under the Instructions
by debiting the amount of the Direct Debits back to the Initiator through the Initiator’s Bank
where the Initiator cannot produce a copy of the Instructions and/ or Confirmation to me/us
that I/we are reasonably satisfied demonstrate that I/we have authorised my/our bank to
accept Direct Debits from the Initiator against my/our account PROVIDED the request is
made not more than 9 months from the date when the first Direct Debit was debited to
my/our account by the Initiator under the Instructions.
BSES

Page 466 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

B. Form of Contract
THIS Contract (hereinafter referred to as “Contract”) executed on this.......... [Date] day of..........
[Month],.......... [Year]:

BETWEEN

BYPL (hereinafter referred to as “BYPL” which expression shall unless repugnant to the context or
meaning thereof include its successors, assigns and permitted substitutes), a company incorporated
under the extant provisions of Indian Laws and having its registered office at [Address];

AND

……………., <insert the name of Selected Bidder, being the Sole Bidder> having its registered
office at……………. [Registered address of the Company] (hereinafter referred to as the “AMISP”
which expression shall unless repugnant to the context or meaning thereof include its successors,
assigns and permitted substitutes).

WHEREAS the BYPL had invited Bids for Appointment of AMI Service Provider for Smart Prepaid
Metering in India on Design Build Operate Transfer basis (the “Project”) through RFP/Tender No.
[Tender Details]

WHEAREAS after evaluation of the Bids received from the Bidders, the BYPL accepted the Bid of
BSES

the AMISP, and issued its Letter of Award No. [__________] dated [__________] (“LOA”) to the
Selected Bidder, requiring the Selected Bidder, inter alia, to execute this Contract within the time
period prescribed in the RFP.

WHEAREAS the AMISP in accordance with the terms of the RFP, shall undertake and perform the
obligations and exercise the rights under the LOA, including the obligation to enter into this Contract
for Design Build Finance Transfer AMI system in the Project area.

NOW, THEREFORE, in consideration of the foregoing and the respective covenants and
agreements set forth in this Contract, the receipt and sufficiency of which is hereby acknowledged,
and intending o be legally bound hereby, the Parties agree as follows:

1. The following documents attached hereto shall be deemed to form an integral part of this
Contract:

(a) The General Conditions of Contract (including Attachment 1 “Fraud and Corruption”;
(b) The Special Conditions of Contract;
(c) Appendices:

Appendix A: Project Requirements (AMI System Requirements and Service Level

Agreement)

Appendix B: AMISP Service Charge

Page 467 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

(d) Technical and Financial Bid as submitted by the Selected Bidder

In the event of any inconsistency between the documents, the following order of
precedence shall prevail: the Special Conditions of Contract; the General Conditions of
Contract, including amendments thereto […. Insert reference to amendments….];
Appendix A and Appendix B; and Technical and Financial Bid as submitted by the
Selected Bidder. Any reference to this Contract shall include, where the context permits,
a reference to its Appendices also.

IN WITNESS WHEREOF, the AMISP and the BYPL, executed these presents and affixed
common seals of their respective companies on the Day, Month and Year first mentioned above.

1. Common Seal of BYPL has been affixed in my/ our presence pursuant to Board
Resolution dated.....................

For BYPL

[Signature of Authorized Representative]

................................................................
[Name of the Authorized Representative]
[Designation of the Authorized Representative]

BSES

1. Common Seal of ……………. [Name of the Sole Bidder/AMISP], has been affixed in my/ our
presence pursuant to Board Resolution dated.....................
For [Sole Bidder/ AMISP]

[Name of the AMISP/ Sole Bidder],

[Signature of Authorized Representative]

................................................................
[Name of the Authorized Representative]
[Designation of the Authorized Representative]

WITNESS:

1. ………………………………………………. (Signature) Name

……………………………………………….
Designation...........……….………………..

2. ………………………………………………. (Signature) Name

………………………….……………………
Designation...........…………………………

Page 468 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

Attested:

…………………………….
[Signature]
(Notary Public)

Place: …………………………. Date: …………………………….

BSES

Page 469 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

Appendix A – Project Requirements (AMI System Requirements and Service

Level Agreement)

[This Appendix shall include Section 6 of the RFP Document including all amendments/
clarification etc. thereto]

Appendix B - AMISP Charges including AMISP Service Charges

[This Appendix shall include Bill of Material given in Section 5 of the RFP Document and
the charges agreed there for]

BSES

Page 470 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

Form 1: Format of Performance Security

[To be on non-judicial stamp paper of Rupees One Hundred Only (INR 100/-) or appropriate
value as per Stamp Act relevant to place of execution, duly signed on each page.]

Reference No. ……………. Bank Guarantee No. ……….…. Dated: …………….

To:
[BYPL]
[Address]

Dear Sir/ Madam,

WHEREAS……………. [Insert name of the Lead Consortium Member/ Sole Bidder] with address
……………. [Insert address of the Lead Consortium Member/ Sole Bidder] having its registered
office at ……………. [Insert address of the Lead Consortium Member/ Sole Bidder] (Hereinafter,
the “Contractor”), subsequent to participation in Tender No. [Tender Details] (the “RFP”) issued by
[BYPL] (hereinafter, the “Beneficiary”) for Appointment of AMI Service Provider for Implementation
of AMI Project in pre-paid mode, have been issued the Letter of Award as the Selected Bidder. The
Selected Bidder was required to incorporate the AMISP. Further the AMISP was required to furnish
a Performance Security in the form of a Bank Guarantee

And WHEREAS a Bank Guarantee for Rupees ……………. [Insert amount in words equivalent]
(…………….) [Insert amount in figures] valid till……………. [Insert Contract Period] is required to
be submitted by the AMISP as per the terms and conditions of the RFP.
BSES

We,…………….[Insert name of the Bank and address of the Branch giving the Bank Guarantee]
having our registered office at …………….[Insert address of the registered office of the Bank]
hereby give this Bank Guarantee No. …………….[Insert Bank Guarantee number] dated
…………….[Insert the date of the Bank Guarantee], and hereby agree unequivocally and
unconditionally to pay immediately on demand in writing from the Beneficiary any officer authorized
by it in this behalf any amount not exceeding Rupees ……………. [Insert amount in words]
(…………….) [Insert amount in figures] to the said Beneficiary on behalf of the Contractor.

We ……………. [Insert name of the Bank] also agree that non-performance, delayed performance
or violation of any of the terms and conditions of the contract by AMISP would constitute a default
on the part of the Bidder and that this Bank Guarantee is liable to be invoked and encashed within
its validity by the Beneficiary in case of any occurrence of a default on the part of the AMISP or the
Selected Bidder and that the encashed amount is liable to be forfeited by the Beneficiary.

This agreement shall be valid and binding on this Bank up to and inclusive of ……………. [Insert
the date of validity of the Bank] and shall not be terminable by notice or by Guarantor change in the
constitution of the Bank or the firm of the Bidder Or by any reason whatsoever and our liability
hereunder shall not be impaired or discharged by any extension of time or variations or alternations
made, given, conceded with or without our knowledge or consent by or between the Bidder and the
Beneficiary.

NOTWITHSTANDING anything contained hereinbefore, our liability under this guarantee is

restricted to Rupees .......... [Insert amount in words equivalent]. Our Guarantee shall remain in
force till ……………. [Insert the contract period]. Unless demands or claims under this Bank
Guarantee are made to us in writing on or before……………. [Insert contract period], all rights of

Page 471 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

the Beneficiary under this Bank Guarantee shall be forfeited, and we shall be released and
discharged from all liabilities there under.

[Insert the address of the Bank with complete [Insert signature of the Bank’s
postal branch code, telephone and fax numbers, Authorized Signatory]
and official round seal of the Bank]

Attested:

……………………………. [Signature] (Notary Public)

Place: …………………………. Date: …………………………….

_________________________________________________________________________

INSTRUCTIONS FOR SUBMITTING BANK GUARANTEE

1. Bank Guarantee to be executed on non-judicial stamp paper of appropriate value as per Stamp
Act relevant to place of execution.
2. The Bank Guarantee by Bidder shall be given from the Scheduled Commercial Banks.

BSES

Page 472 of 473

 NIT No.: CMC/BR/23-24/RB/PR/SN/2090

Form 2: Format of Letter of Award

Sub:- Bid for Appointment of AMISP for Smart Prepaid Metering Solution

REF: -
1. Request for Proposal for selection of AMISP dated [•] (“RFP”)
2. Your proposal dated [•] (“Proposal”)
3. Your clarification [•]

Dear Sir,

1. This is in reference to your Proposal in relation to the RFP.

2. Pursuant to the evaluations of the Bid, your bid has been found to be most suited.

3. <Applicable in the event the Selected Bidder is a Consortium>you are requested to please
take steps for incorporation of the BIDDER in terms of the RFP for execution of the AMISP
Contract. The execution of the AMISP Contract shall happen only after you have furnished
the performance security in terms of the RFP.

<Applicable in the event the Selected Bidder isa Sole Bidder as an individual entity>you
may at your discretion opt for incorporating an BIDDER as per the terms of RFP, for
execution of the AMISP Contract. In case you intend to do so, you may apply to us within 7
(Seven) Days of receipt this letter for our permission for the same. If permitted by us, you
shall be required to take steps for incorporation of the BIDDER in terms of the RFP for
execution of the AMISP Contract. The execution of the AMISP Contract shall happen only
after you have furnished the performance security in terms of the RFP.
BSES

4. A draft of the AMISP Contract was provided to you along with the RFP. Please note that
there shall be no change whatsoever in the terms and conditions as set out in the draft
Contract.

5. Please note that in the event of failure to comply with any terms and conditions of this Letter
of Award, the entire Bid Security may be forfeited.

6. Any further correspondence in connection with the Project should be addressed to the
[insert details of the appropriate authority •]” with a copy to Chairman/ Managing Director,
till further instructions are issued.

7. The terms and conditions as set out in this Letter of Award shall stand valid until execution
of the AMISP Contract.

8. Please acknowledge the receipt and return the duplicate copy of this Letter of Award after
signing and stamping it in all the pages to the undersigned as a token of acceptance.

Thanking You

Yours truly
[Insert details of the BYPL]

Reference No. ……………. Bank Guarantee No. ……….…. Dated: …………….

Page 473 of 473