MDMS - Technical - Agreement - For - 11 Lacs - Smart - Meters

Technical Specification and Scope of Work for
Meter Data Management System

Technical Specification of Meter Data Management System
(MDMS) for 11 Lacs Smart Meters on PAN India Basis
Abbreviations
Sl. No. Abbreviation Full Forms

1. MDMS Meter Data Management System
2. HES Head End System
3. CIS Consumer Information System
4. RMS Revenue Management System
5. GIS Geographical Information System
6. NOMC Network Operation cum Monitoring Centre
7. VEE Validation, Estimation and Editing
8 AMC Annual Maintenance Cost
9 ATS Annual Technical Services
10 NMS Network Management System
11 API Application Programming Interface
12 FIIT Field Installation and Integration Testing
13 SAT Site Acceptance Testing
14 HLD High Level Design
15 LLD Low Level Design
16 CSP Cloud Service Provider
Page 1 of 35
Table of Contents
Abbreviations ............................................................................................................................ 1
1 Scope of Work ....................................................................................................................... 3
2 Price Schedule....................................................................................................................... 6
Appendix – A: Software Licenses BoQ..................................................................................... 10
Appendix – B: Cloud IT Infrastructure Sizing and Guidelines ............................................... 13
Appendix – C: Technical, Functional and Integration Requirements and its compliances . 15
Appendix - D: Testing, Training and Operational Acceptance .............................................. 19
Appendix- E: Implementation Approach & Timelines ........................................................... 25
Appendix- F: Operations, Maintenance and Support Services post Operational

Acceptance 27
Appendix – G: Service Level Agreement (SLA) ....................................................................... 30
Page 2 of 35
1 Scope of Work
The Scope of this contract:
a) Supply of Meter Data Management with Pre-paid billing application Software along with ATS for
the contract period. *(Please see the note below)
b) Implementation Services: Design, Build, Test and Deploy the supplied Application on the provisioned
cloud environment provided by IntelliSmart, configuration, customization, business process/
systems integration (HES, workforce management, Utility Billing and customer care and other
Applications, Consumer Portal, Prepayment consumer mobile app …etc) and commissioning (FIIT,
UAT/SAT)
c) Development of analytics reports and SLA dashboard (data availability at MDM).
d) Operation, Maintenance and Support Services of the deployed system along with the customizations
and upgrades for the entire project period on 24x7 basis AMS as per SLA
* Note: The Software licenses will be in the name of DISCOMs and will be perpetual, non‐
exclusive, non-transferable, irrevocable, royalty‐free license without restriction.
Unless otherwise stipulated in the contract, the Scope of Work shall include all such items not
specifically mentioned but that can be reasonably inferred as being required for comprehensive,
successful, and satisfactory implementation of the Solution.
The entire project as mentioned under the scope of works section must be completed timely in phased
manner. The entire scope i.e., deployment of the MDMS with prepaid system on the Cloud Infrastructure
with full configuration and the integration with all operational business eco-systems in production
environment followed by SAT and Operational acceptance must be completed in all respect within the
stipulated timeline.
The Operation, Maintenance and Support services period for deployed MDMs with prepaid solution for this
project shall be for (a) period of 102 months (approx.) from the date of operational acceptance of the
solution or (b) expiry of total meter-months of operating the AMI system after Operational acceptance of
AMISP contract of IntelliSmart with DISCOMs.
In this offer, the partner shall carryout the above-mentioned works as part for the below AMISP projects in
multiple DISCOMs (the name of DISCOMs shall be shared with the successful Partner(s)).
Projects Total Meters (Approx)
Project -1 5 Lacs
Project-2 3 lacs
Project -3 3 lacs
Note:
1) IntelliSmart reserves the right to make Quantity variation of -30% to +50% for the
numbers of meters for each project.
2) These projects in DISCOMs will be implemented in nearly same time schedule.
Separate Work Order (WO)/Purchase Order (PO)/Letter of Award (LOA) shall be
given for each of the projects.
Page 3 of 35
1. The below attached appendices are integral part of the scope of work of this contract.
Appendix - A: Software Licenses BoQ
Appendix - B: Cloud IT Infrastructure Sizing and Guidelines
Appendix - C: Functional, Technical and Integration Requirements and compliance
Appendix C1
Appendix C2
Appendix C3
Appendix - D: Testing, Training and Operational Acceptance
Appendix – E: Implementation Approach & Timelines
Appendix - F: Operations, Maintenance and Support Services post Operational Acceptance
Appendix - G: Service Level Agreement (SLA)
2. Other requirements:
i) The Proposed MDMs solution shall be scalable and perform to meet the SLA. The partner
/OEM should submit performance test report for at least 5 million interval meters for the
proposed solution. Test report shall be submitted in this regard at the time of signing of the
contract agreement.
ii) The partner/OEM should submit details of the proposed solution for describing, scalability
up to minimum 5 million smart meters (per month) on one instance with 15 min / 30 min
interval read data processed daily along with Prepaid billing. A Self- Certification shall also
be submitted in this regard at the time of responding to this RFQ.
iii) Partner has to offer OEM’s perpetual license along with eight (8) year’s Annual
Technical Support (ATS) from the date of operational acceptance. During the
implementation & ATS period OEM shall provide all the technical updates/support,
service packs, any version upgrades without any additional cost.
iv) Partner shall provide Operations and Application Maintenance Services (AMS) of the
implemented system for the period of 8 (eight) years from the date of operational
acceptance.
v) Partner should also provide the required training to the users for operating, developing
system and administrative training to selective persons for running system after support
period free of cost.
vi) Partner must provide all the overarching 3rd party software which it deploys for operation
of the system free of cost till the AMS period.
vii) The Partner shall be responsible for software updates, upgrades, patches are supplied,
installed, and commissioned during the contract period. Including Training to IntelliSmart /
DISCOM employees on new version of software from the OEM or OEM’s certified training
partner shall be arranged by the partner.
viii) Partner shall Support in migration of the VMs, data, backups, content, and any other assets
to a new environment created by IntelliSmart /DISCOMs on alternate CSP /Data Center (to
be onboarded by IntelliSmart) to enable successful deployment and running of the Partner’s
solution.
ix) We may request partner to White Label the Meter Data Management called “Full White
Labeling- MDM”, IntelliSmart Trademark and Branding shall appear on the Meter Data
Management. IntelliSmart specifies “Full White Label” shall mean that IntelliSmart is
authorized to use the Meter Data Management without displaying all the partner
Trademarks and branding and/or including any picture, logo, company name etc. This would
be an exclusive arrangement between Partner and IntelliSmart to deploy and support the
Meter Data Management for DISCOM during the project implementation and support phase.
x) IntelliSmart agrees that it will not sell, offer for sale, or assist third parties (including
Affiliates) in selling partner’s Meter Data Management except to DISCOM for Project 1, 2 and
3. IntelliSmart and partner shall have a separate agreement in case of new customer
onboarding.
Page 4 of 35
3. Partner’s Responsibilities and Obligations

Partner’s Responsibilities and obligations include, but are not limited to, the following:
a. The Partner has the overall responsibility to deliver the product and/or services that meets the
functional and performance requirements of this Contract.
b. It shall be the obligation of partner that all the systems, sub-systems, and equipment’s/devices
in their scope along with its interfaces with other systems shall conform in all respect to high
standards of engineering, design and workmanship, and shall be capable of performing
continuous commercial operation as per best industry standards.
c. In the event of the Partner(s) going bankrupt or issues which prevent the Partner(s) from
fulfilling the obligations during the tenure of the contract, the Partner(s) must adhere to Escrow
principles for ensuring seamless operation. Adherence to such an Escrow arrangement is a pre-
condition of award of contract to Partner(s).
d. The cloud server sizing, network bandwidth, storage, OS, database, load balancer,
network equipment, backup and archiving policy, cloud native and managed services,
IaaS, and PaaS etc. shall be proposed by MDM partner for complete duration of project.
Any variation in proposed architecture and sizing shall be sole responsibility of MDM
partner. Any financial impact due to increase in cloud server sizing to meet the
performance by MDM implementation partner during project shall be borne by MDM
partner only. MDM partner shall submit the Self-declaration certificate in this regard at
the time of contract signing (MDM partner can use their own formats for each project
separately).
e. The Partner must carry out the due diligence on his part and collect the required data
/information for the objective of this contract. Any associated works/ items not described in the
Scope of work, Technical Specifications & BoQ but are required for a viable and fully functional
system is the responsibility of Partner.
f. The Partner shall appoint key personnel with relevant experience for the project and keep the
IntelliSmart informed about these resources along with their CV post award LOA.
g. Attend progress review meeting (daily/weekly/fortnightly/monthly) with IntelliSmart &
DISCOMs at appropriate level, as required.
h. Co-ordination & Collaboration with the other Contractors appointed by IntelliSmart and/or
DISCOMs in executing the project in an amicable environment.
i. The Partner shall submit an exit management plan.
j. The Partner shall submit a list with the details of the Assumptions & Exclusions taken with the
submission of his offer towards this contract.
k. The Partner shall submit the SLA reports on monthly basis separately for each project in
compliance with Appendix – G: Service Level Agreement (SLA). The penalty, if any, shall be
deducted/computed on the monthly charges based on the SLA certification by IntelliSmart
Project Manager.
Page 5 of 35
2 Price Schedule
A.1 Schedule: Project -1
Price Total
Sl. Duration Total with GST
Item Description Unit Quantity per unit (Basic)
No. (Months) (@18%) (INR)
(INR) (INR)
1 Supply of Meter Data Management with Pre-paid billing application Per meter per 5,00,000 93
Software along with ATS for 93-meter months month
Note – Invoicing shall commence after the operational acceptance

of the deployed system
2 Implementation services of MDM with prepayment system including Lumpsum - 1
Integration
3 Development of analytics, reports, and SLA dashboard Lumpsum - 1
4 Training Lumpsum
5 Operation, Application Maintenance and Support Services (AMS) Per meter per 5,00,000 96
after completion of operational acceptance (Refer Note 1) month
Sub-Total of A.1
Note 1: The price quoted shall not be less than 15 % of the total cost under items 1+2
Price Total
(INR) (INR)
Note – Invoicing shall commence after the operational acceptance of the

deployed system
Integration
4 Training Lumpsum
5 Operation, Application Maintenance and Support Services (AMS) after Per meter per 3,00,000 96
completion of operational acceptance (Refer Note 2) month
Sub-Total of A.2
Page 6 of 35

Price Total
(INR) (INR)
Note – Invoicing shall commence after the operational acceptance of the

deployed system
Integration
4 Training Lumpsum
5 Operation, Application Maintenance and Support Services (AMS) after Per meter per 3,00,000 96
completion of operational acceptance (Refer Note 1) month
Sub-Total of A.3
B. Manpower cost for change management

Unit Total Total with GST
Sl. No. Fee Components Quantity* Price per unit (INR)
Man months (Basic) (INR) (@18%) (INR)
1 Blended cost (man months) for Sr. 20
Technical resources like:
• Solution Architect
• Business Analyst
• Development leads
2 Blended cost (man months) of Jr 20
Resources
Total cost
*The Partners may propose the quantity of resources based on their assessment.
Total Cost: A.1 + A.2 + A.3 + (B x 3) = INR _________________________________________ (In Figures)

Rupees _____________________________________ (In words)
Page 7 of 35
5.1 The price shall be all inclusive for the cost of below Systems and/or Services.
a) Solution Design: Application & Cloud Sizing and BoQ, Business Process & Solution deign /
documentation - HLD, LLD, Server deployment architecture, networking, security, bandwidth
requirements, test plan, test schedule, UAT/SAT etc.
b) Supply of Application software Licenses with ATS.
c) System deployment on the provisioned cloud data centre (DC, DR).
d) Configuration, Customization, Integration, and testing of solution.
e) Training, Site Acceptance Testing (SAT) for operational acceptance.
f) Monthly Operations and Application Maintenance & Support of the deployed system.
g) Any other cost required to meet the requirement of scope of work.
5.2 The price shall be all inclusive for the costs/expenses for the scope of supplies and services for the
finished product, costs and expenses of whatsoever nature (whether direct, indirect or ancillary)
incurred by or imposed on the partner including its subcontractors and suppliers in the performance
of the work, all profit, license, royalty, technical specification, inspection, testing, warranty,
maintenance etc. and of the costs of the Freight and Transportation, loading/unloading, packaging and
forwarding, transit insurance, handling, for and including transfer to and delivery at site (if any ) etc.
and of all applicable taxes, duties, tariffs, fees, levies, insurance premiums, etc.
5.3 Milestones and Payment Schedule

The implementation duration for the deployment of the solution is three (3) months from the date of
Work Order/ Purchase Order/ Letter of Award (LOA) for each of the projects. Please refer Annexure
E. Post successful implementation and acceptance of the system the Operational, maintenance
and Support services phase will commence. The payment shall be made as per the below schedule:
5.3.1 Payment of Quarterly MDMs Software Licenses

Item 1 of price schedule A1, A2, and A3: Quarterly payment for the deployed Meter Data
Management with Pre-paid billing application Software along with ATS, shall be released based on
the number of smart meters successfully completed SAT for the calendar month on the deployed
system. The payment shall be released subject to the SLAs certification by IntelliSmart project
manager and the penalty (if any). Refer Appendix – G: Service Level Agreement (SLA).
5.3.2 Payment for the implementation Charges for MDM with prepayment system
For Item 2 & 3 of price schedule A1, A2, A3: payment shall be released at the below milestone on
completion of the Deliverables / tasks:
Payment
Deliverable /Task Payment (%)
Milestones
AS IS Study and Analysis of requirements Item 2:
including Interfaces with the existing 10(Ten) % of Implementation
systems & Submission of “TO BE” design Charges
1. Initiation &
document
Design
Item 2:
Approval of TO BE design document 10 (Ten) % of Implementation
Charges
Deployment of the MDMs with prepayment Item 2 -
billing with configuration and integration 30 (Thirty) % of
2. Deployment of
interfaces in production environment with Implementation Charges
MDMS in
stage -1 functionality*
production
Item 3-
Completion of
Approval of report and dashboard format / 30 (Thirty) % of development
Stage 1
templates / UI for analytics, reports, and Charges
SLA dashboard (data availability at MDM)
Deployment of the MDMs with prepayment Item 2 -
billing with configuration and integration 30 (Thirty) % of
interfaces in production environment with Implementation Charges
stage -2 functionality*
Page 8 of 35
Payment
Deliverable /Task Payment (%)
Milestones
3 Completion of - Configuration / customization of the Item 3-
SAT /UAT and MDMs application for advance features, 30 (Thirty) % of development
Operational reporting, analytics, and SLA Charges
acceptance by Dashboard /Reports
DISCOM - User Training to users
- Successful completion of SAT/UAT &
Availability test
4 After Three Three months of Post Operational Item 2 -
months of Acceptance support and Evaluation of the 20 (Twenty) % of
Operational functional and technical functionalities Implementation Charges
Acceptance on deployed and fixing of gap if any Fixing of
Completion of defects / bugs identified. Item 3-
stabilization 40 (forty) % of development
phase Tuning the system to meet the SLA target. Charges
Update reports, UI, Dashboard, user
manuals and other relevant documents
* Refer Appendix – E: Implementation Approach & Timelines
5.3.3 Payment towards Training and Manpower

For Item 4 of price schedule A1, A2, A3 and Price Schedule B: payment shall be released as per
the actual number of sessions and the man days consumed based on the approval of IntelliSmart
Project Manager.
5.3.4 Payment of Monthly MDMs Services

Item 5 of price schedule A1, A2, A3: The Quarterly payment towards Operations, Application
Maintenance and Support Services (AMS services) shall be paid at the end of each quarter (3
months) after certification by IntelliSmart Project Manager for satisfactory services. The payment
shall be released subject to the SLAs certification by IntelliSmart Project Manager and the penalty
(if any). Refer Appendix – G: Service Level Agreement (SLA)
Page 9 of 35
Appendix – A: Software Licenses BoQ

A.1. Partner shall be responsible for supplying all required licenses of the Meter Data Management with
Pre-paid billing application Software and any other software, database required for deployment of
the Meter Data Management Solution for Smart Meters in prepaid mode for this contract in Production
(DC & DR) and non-production environments (Development, Test / Training) along with Application
Technical Support (ATS) for the entire duration of project.
A.2. All the licenses shall be full use perpetual including Platform Licenses (DB, Middleware, Virtualization
technology etc.)
A.3. The partner shall provide detailed BoQ of the Application Software, Database Licenses for each
instance of deployment as per the below table for the complete numbers of meters project wise:
Project -1 Quantity
Non-
Primary Production
Disaster
OEM Name Part No Part Description Metrics Data (Development
Recovery
Center /Testing,
Training)
Project -2 Quantity
Non-
Primary Production
Disaster
Recovery
Center /Testing,
Training)
Project -3 Quantity
Non
Primary Production
Disaster
Recovery
Center /Testing,
Training)
A.4. On reaching the operational acceptance and at the completion of the implementation phase of each
project, Partner shall submit deployment details, Software inventory list - Name of Software, OEM /
supplier, pertinent documents, language and libraries, metrics and qty of licenses deployed, all custom
codes for each deployment.
A.5. The Solution deployed by the Partner shall have unrestricted license allowing IntelliSmart /DISCOMs
utilizing the functionality to the maximum.
A.6. Partner shall provision licenses for both Primary (Active) and Data Recovery (Passive) sites.
A.7. Partner shall deploy and manage the application instances for Web, Batch, Reporting, database and
Page 10 of 35
storage of the MDMs with prepayment solution on the Cloud Infrastructure provisioned through
IntelliSmart Cloud partner.
A.8. The partner shall refer the below information, data for estimating most optimal BoQ for Software
Licenses, Deployment Architecture, Sizing, and phased production deployment on cloud for DC & DR
including nonproduction environments. Cloud Infrastructure shall be provisioned by IntelliSmart for
these deployments in progressive manner as per the sizing and services requirement given by the
partner and agreed by IntelliSmart through its Cloud Service Provider (VMs, Compute, Memory,
Storage, OS, DB services, Web Application Firewall (WAF), Networking requirements, Load Balancer,
Connectivity bandwidth etc.
Important Note:
1) Partners are advised to give the best optimised IT Infrastructure requirements for their solution.
IntelliSmart shall evaluate the offers from the partners on the Total cost of ownership including
the cost of the IT Infrastructure requirements from its Cloud services partners.
2) Partner shall be responsible for the SLA performance for the deployed solution on the
provisioned cloud as per agreed sizing. Any additional IT Infrastructure required for the
performance of agreed scope of work shall be at the cost of the partner.
Table -II
Years of Online Data Retention 2 Years
Data in Archive mode 8 years
Table-III
Environments Required High Availability
Production Yes Yes
Disaster Recovery Yes Yes
Development /Test Yes No
Training Optional No
Table-IV
Interval based meter Number of Interval Usage Number of Daily & Monthly
Configurations Channels per meter Scalar Channels per meter
Interval Device Config 1 3 kWh import, 6 kWh Import,
(Single Phase Whole kVAh import, kVAh Import,
Current Smart Meter)- Voltage, MD kW,
Interval Frequency 30 MD kW date and time
Minutes MD kVA
MD kVA- date and time
(Single Phase Whole kVAh import, kVAh Import,
Current Smart Meter kWh export, kWh Export,
with Net Metering)- kVAh export, kVAh Export,
Interval Frequency 30 Voltage, MD KW,
Minutes MD KW date and time
MD kVA
MD KVA- date and time
(Three Phase Whole kVAh import, kVAh Import,
Current Smart Meter)- Voltage-R, MD kW,
Interval Frequency 30 Voltage-Y, MD kW date and time
Minutes Voltage-B, MD kVA
Current-R, MD KVA- date and time
Current-Y,
Page 11 of 35
Interval based meter Number of Interval Usage Number of Daily & Monthly
Configurations Channels per meter Scalar Channels per meter
Current -B
(Three Phase Whole 0 kVAh import, kVAh Import,
Current Smart Meter kWh export, kWh Export,
with Net Metering)- kVAh export, kVAh Export,
Interval Frequency 30 Voltage-R, MD kW,
Minutes Voltage-Y, MD kW date and time
Voltage-B, MD kVA
Current-R, MD kVA- date and time
Current-Y,
Current -B
Interval Device Config 5 kWh import, kWh Import,
(LTCT Smart Meter with 1 kVAh import, 13 kVAh Import,
Net Metering- Category 4 kWh export, kWh Export,
D3) kVAh export, kVAh Export,
Interval Frequency 30 kVarh Q1 kVarh Q1
Minutes kVarh Q2 kVarh Q2
kVarh Q3 kVarh Q3
kVarh Q4 kVarh Q4
Voltage-R, MD -kW,
Voltage-Y, MD kW date and time MD
Voltage-B, kVA
Current-Y, Billing Power ON
Current -B Duration in Minutes
kWh import, kWh Import,
Interval Device Config 1 kVAh import, 13 kVAh Import,
6 4 kWh export, kWh Export,
(HT Smart Meter with kVAh export, kVAh Export,
Net Metering- Category kVarh Q1 kVarh Q1
D4) kVarh Q2 kVarh Q2
Interval Frequency 30 kVarh Q3 kVarh Q3
Minutes kVarh Q4 kVarh Q4
Voltage-R, MD -kW,
Voltage-Y, MD kW date and time MD
Voltage-B, kVA
Current-Y, Billing Power ON
Current -B Duration in Minutes
Page 12 of 35
Appendix – B: Cloud IT Infrastructure Sizing and Guidelines

Partner shall be responsible for overall deployment designing, including sizing for- VMs, Compute cores,
memory, storge, network, backups etc.
The partner shall collaborate with the CSP/MSP partners (to be onboarded by IntelliSmart), System /
Security Auditors in compliance to the best industry practices and manners. The partner along with Project
CSP/MSP (to be onboarded by IntelliSmart) partner shall conduct all necessary activities for - provisioning,
configuring of Cloud Environment for application deployment and thereafter operate, maintain, and
support the deployed application for the entire duration of the contract period and meet the SLA
requirement for performance, availability, business continuity, storage, and cyber / data security
management at application level.
Pls note that the deployed Cloud infrastructure for these projects shall be compliant to the CSP key
requirement of the SBD version 4.
B.1 Application Deployment Approach

i. The MDMs with prepayment application deployment architecture shall necessarily deliver the
required functions in a secure, scalable, fault tolerant manner for the projects in a cloud Primary
Data Centre & a DR Data Centre.
ii. The deployment architecture shall be simple, scalable architecture with no Single-Points-Of-
Failure (SPOFs) with Distinct application, database, and storage tiers to simplify operational
processes / flexibility such that tiers can be dynamically configured/upgraded / scaled to meet
demand with minimal impact on other tiers. The application deployment should preferably be in
stable active-active high availability configuration with effective load balancing such to ensures
that the application is always in operation and accessible with desired response time.
iii. The application deployment shall ensure that the capabilities and performance of DR are the same
as DC. The secondary Disaster Recovery (DR) site shall be used to support failover operation. While
DC is operating normally, data shall be replicated from DC to DR. If DC fails, DR can start operating
in its place, without any reliance on DC.
iv. Regular backups and archives shall be done for rapid intra-site restore and recovery following
accidental or malicious misconfiguration or deletion. Care shall be taken to ensure database
backups are restorable. Backups shall be regularly restored to a pristine server and verified to
ensure the integrity and efficacy of the backup-restore function.
v. The Partner shall submit a high-level deployment architecture with writeup along with this
contract. Technical details of the other clouds and communication Infrastructure shall be provided
by IntelliSmart to the successful Partner during design/deployment phase.
B2. Sizing Inputs

The Partner shall provide estimated Cloud Infrastructure and data connectivity requirements
for the deployment in staged manner.
IntelliSmart shall provisioned the cloud in progressive manner as per the sizing and services
requirement given by the partner and agreed by IntelliSmart through its Cloud Service Provider.
The sizing for the cloud shall be furnished in a format for each project to operate the estimated numbers
of meters in each of the project for DC setup in the excel sheet attached.
B 3. Recommended Guidelines
While sizing the infrastructure requirement the partner shall take in consideration the below good
industry practices and guidelines
i. Application shall support latest version of operating systems. Licensed OS shall be considered:
a. Windows
b. Linux (RHEL)
In case OS is in considered as part of licence package of the application then the support of OS shall
remain in the part of the partner
Page 13 of 35
ii. Open-source database shall not be considered. If it is considered, then support enterprise level
license must be taken by the implementation partner.
iii. MDM application shall support virtualisation and auto scaling and dynamic computing capabilities
and cloud agnostic.
iv. The maximum size to be considered for each VM shall never exceed the below mentioned
parameters:
a. CPU: 112 vCPU
b. RAM: 800 GB (Ideally should be a multiplier of 4)
c. VM Per Drive space: 4 TB
d. Maximum IOPs: 4000 Per TB
e. Shared Storage: 600 TB
v. Load Balancer: L4 in case of separate appliance, in case Load balancer configuration if done at VM
level, shall be sized for sufficient number of transactions per seconds.
vi. VM Zoning shall be done considering all security measures for application, databases, and other
servers, preferably all servers should be in MZ zone.
vii. Overlaying security architecture would be of CSP but underlaying application-level security has to
be maintained by the partner as per industry best practices.
viii. The partner shall specify the cloud native services and cloud managed services requirements
separately.
ix. The proposed deployment architecture shall be envisaged with separate subnets for application
and database workloads.
x. The proposed solution shall be easily integrable with the CSP AD solution.
Page 14 of 35
Appendix – C: Technical, Functional and Integration Requirements and

its compliances
C1. General:
The MDMS with Pre-paid system shall generally support functionalities in alignment to the latest “Model
Standard Bidding Document” SDB version 4 with amendment for appointment of Advanced Metering
Infrastructure Service Provider (AMISP) under RDSS issued by the REC Limited (REC) in August 2022.
Further to SBD document reference, in this section there is further elaboration of the Technical, Functional,
Integration requirements essential for successful and satisfactory deployment of this vital component of
the AMI application landscape.
Partner shall refer to attached file “Appendix C_MDM Compliance Sheet” to this contract and shall submit
clause wise compliance with justification / remarks for Appendices C1 to C3 attached to this contract. The
following guideline shall be adopted for indicating compliance against each of the features mentioned in
this section.
Compliance Guidelines Response
Standard The specific requirement or process is a standard feature of the S
Proposed MDMs and can be realized without significant
development work
Customization The requirement can be realized by writing a set of custom codes C
Third Party The specific requirement can be realized through a third-party T
application / New application or a new application / module development
development
Not Possible The requirement is not possible or not part of the proposed N
solution
C2. High Level Solution overview

IntelliSmart intend to deploy smart meters in its AMI project as per the high-level solution architecture
depicted in Figure 1. The smart meters shall communicate over RF mesh and/or Cellular network and shall
support Reconnection/ Disconnection command and on demand readings. The meters and the
Communication solution shall meet all mandatory requirements of the IS16444, IS15959 and DLMS/
COSEM standard.
The MDMS application components must follow common data model as much as possible and must follow
SOA principles wherever required for cloud integration to provide specific services using well defined
interfaces. The MDMS application design shall be based on cross-functional components or subsystems and
shall be implemented in such a way that there is an opportunity for reuse. The integration architecture
shall be based on the concept of a cloud service, so all the applications of the MDMS application are able to
integrate without any complexity.
MDMS system is envisaged as a Service driven architecture at the core of it. MDMS system features can be
accessed via any user interface (internal or 3rd party applications) which shall work on top of these
Services. Adoptions of open standards are of paramount importance for the robust and scalable MDMS
system. Data access must be always through services, no application will access MDMS data directly from
the storage layer or data access layer. For every internal data access also (access between various modules)
there will be services and no direct access will be there to ensure the MDMS system is scalable and secure.
The MDMS shall have the ability to receive data through a data push or a data pull mode from the meters
thru respective head end system (HES)
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, reporting, etc.
MDM and its integration with utility/DISCOM system is the mission critical application in the AMISP project
eco-system. The conceptual integrated architecture for MDM with other systems is depicted in the
following diagram.
Page 15 of 35
The MDM shall have the ability to manage 15-minute, 30-minute interval data, billing and along with non-
billing parameters.
The proposed MDMs with prepaid system must be designed and deployed to manage and perform with
massive data sets and should be inherently scalable as data sources and volumes expand throughout Meter
Deployment ramp up in the project.
The Proposed MDMS and Prepaid Solution shall have role based and secure, user-friendly interface (GUI)
and users can be accessed via a standard web browser, such as Internet Explorer, Mozilla Firefox, or Google
Chrome.
MDM should support the future requirement of utility by way integration with other smart grid/AMI
functionalities as and when implemented by utilities/discoms.
The MDM shall have the ability to selectively choose which data to be maintained and which to be purged
or archived.
C3. High Availability, Load Balancing & Scalability

The MDMs with prepayment application shall be deployed in the cloud DC & DR provided by IntelliSmart.
The deployment of MDMs with prepayment application shall have adequate redundancies so as to have no
single point of failure. The MDMs with prepayment application must support virtualized 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.
The application shall be scale both vertically and horizontally to support more number of meters without
compromising performance using additional hardware. Adequate data base and security features for
storage of data need to be ensured.
Partner shall propose the backup & restoration strategy however following metrices will be considered for
SLA in case of disaster for application availability, recovery point objective (RPO) and recovery time
objective (RTO)
All Projects Application Availability 99.5%

All Projects Recovery Point Objective (RPO) 0.5 Hour (30 minutes)
Page 16 of 35
Recovery Time Objective (RTO) 1 Hour
Partner shall provide a comprehensive detail on the below:

i) Application Architecture showcasing the individual application modules, their interactions, and
relationships to the core business processes.
ii) Technical architecture of MDMS and Pre-payment system as well as the integrations with other AMI
applications as well as utility billing system (as applicable)
iii) Proposed Deployment Architecture to support high availability, performance and business continuity,
vertical & Horizontal scalability, backup /archival requirements.
iv) Security architecture describes the proposed approach on cyber/ data security.
v) Support for Containerization of the customized product/application(s) in the Cloud.
C4. Solution Integration

• The data exchange models and interfaces shall comply with CIM-XML-IEC 61968-9 / IEC 61968-
100 / Web Services / MultiSpeak v3.0.
• The integration middleware should be based on Service Oriented Architecture (SOA) and other
forms of Application Program Interfaces (API) and use publish / subscribe mechanism.
• The integration middleware to be an open architecture based.
• MDM partner shall develop and implement the push APIs for profiles, events, alerts etc from
multiple HES. These APIs shall be consumed by HES to push the required data to MDM. In case HES
partner missed to push the data from HES, there should be a provision to pull the required missed
data from HES.
• The integration middleware/interface must validate the Data to be integrated.
• It must maintain integration logs that confirm the success or otherwise of the interface, complete
with control totals.
• 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.
Below figure depicts a typical information flow and use case for AMI System interface with the enterprise.
Beside the multiple HES systems and Workforce management Application (WFM) of IntelliSmart, NOMC
Monitoring Dashboards, Consumer Portal, Consumer mobile Apps & Portal of the AMI landscape; MDMs
with prepayment system shall also interface with DISCOMs system like Billing system, Revenue
Management Systems, GIS, Customer Information system, Customer care – 1912, SMS & Email Gateways,
National Feeder Management system, SCADA etc.
AMI System landscape for the projects:

HES Multiple HESs system (3- 4 no’s)
RF Mesh
Page 17 of 35
Cellular based
Unified (RF+ Cellular),
WFM (SMO) Smart Meter Operation of IntelliSmart. This application is a Work force
management solution that is used for day-to-day field operations like
CI/MI/regular updates on field.
Monitoring Dashboard This is an application for regular monitoring of IT Infrastructure,
(NOMC) Communication network, SLA KPIs, Realtime pendency monitoring, status
of CI/MI/ and other operational aspects of day-to-day project ops.
Consumer App/ portal BeSMA - A customer facing mobile application of (IntelliSmart)
HHU/ Mobile App for These HHU/Mobile devices will send collect data locally from meter optical
local / manual reading port and export to MDM in XML /MIOS format
Access management, SSO MDMs must integrate with the Access management and single sign-on of
application the AMISP project
The integration interface scope mentioned herein is based on the current understanding and the SBD
version 4 with amendment. During the AS-IS Study / solution design document / actual during
implementation phase, partner must engage with DISCOMs and other project teams and any change in
requirements shall be dealt with by partner without any additional cost or timeline extension.
For those IT/OT systems which the DISCOMs may planned in future, the MDMS implementation Partner
shall publish document on available standard interfaces to enable their integration.
C4. Data Analytics and Reports

The proposed MDMs shall include as standard, embedded Analytics module to provide an operational
overview of performance and the status of key business processes by simple MIS, Reports and Dashboards.
The primary objective is to ensure that the huge volumes of data generated by the smart meters renders
unambiguous and insightful results aimed at driving actions for BaU as well future scenarios, thereby
improving performance and bringing value to both customers and operations.
The analytics module shall use Data-driven Analytics reports by leveraging AI/ML based technologies.
Page 18 of 35
Appendix - D: Testing, Training and Operational Acceptance

The below activities before Operational acceptance shall be carried out by the partner to ensures that
MDMS with the prepayment system is successfully deployed and integrated with other key business eco-
systems of DISCOMs and IntelliSmart.
i) Field Installation and Integration Test (FIIT),
ii) User Acceptance Test (UAT) / Site Acceptance Test (SAT).
iii) System Availability Test
iv) Delivery of Training Obligation
D.1 FIIT Use-cases:
As mentioned in “Clause 9.3 Field Installation and Integration Test (FIIT)” of Section 6. Project
Requirements of the SBD Version 4 with amendment the partner in consultation with IntelliSmart and the
other partners of the AMISP project to devise the FIIT tests regime.
The key objective is to achieve the integration and configure the system for successful demonstration of use
cases that ensures integration is complete. This is a general requirement to confirm that FIIT is complete
as far as integration is concern. Please note that these are illustrative list of use cases only and is not an
exhaustive list. Further please note that all IS Standards shall be applicable.
The partner shall refer to the attached use case list under Sheet “Appendix C3_Use Case” of Excel file
“Appendix C_MDM Compliance Sheet.Xls”.
(Note: Use cases where either Source or Destination is MDM, is covered under the scope)
D.2 User Acceptance Test (UAT) & Site Acceptance Test (SAT)
The final tests (Entry – exit criteria) to be carried out for UAT / SAT. Test Scenarios shall be prepared in
consultation with IntelliSmart/ DISCOM and listed in the site-testing document by the Partner’s team.
Among others, the site testing document shall include the following minimum performance tests:
These performance test shall be done during SAT process for the 1st lot of meters (5% of the total
project quantity or 25,000 meters) and subsequently monthly for the new meters installed in the
project. The Successful completion of SAT process for the 1st LOT of Smart meters is one of the Key
Criteria for Operational Acceptance.
The below SLA requirements for conducting SAT is dependent on HES to get the meter data from field
devices, data availability at MDM shall be seen in conjunction of HES. If the meter data is not available at
HES that shall be excluded from MDM SLA calculations. It shall be responsibility of partner to reconcile the
meter data between MDM and HES and ensure all the data available in HES shall reach to MDM.
The SLA compliance at MDM is subject to data availability at HES. Partner shall justify the data non-
availability at HES in case of any deviation from below SLA parameters in MDM using data logs, reporting.
Sl. No. Head Description Criteria Remarks
1 Load Profile Data One-month block From 98% of the MDMS Scope – MDMS shall
Read load profile for meters in 12 sync the load profile data from
installed meters hours after the respective HES systems in
midnight some periodic interval to
ensure maximum possible
syncing for meeting this SAT
criteria.
2 Billing Profile Billing profile data From 98% of the MDMS Scope – MDMS shall
Data Read for installed meters in 12 sync the billing profile data
meters hours after the from respective HES systems in
midnight periodic interval to ensure
Page 19 of 35
maximum possible syncing for

meeting this SAT criteria.
3 On-Demand Collection of 7 days Within 2 minutes Meters to be sampled for
Remote reads of of interval energy performance measurement -
meters data and the Sample size of 100 meters shall
current total be selected systematically from
accumulated a population of meters from
energy from a each LOT of meters offered for
selected individual SAT.
meter MDMS Scope – MDMS shall
have the provision to initiate
the on-demand read request
for selected meter(s) and store
and display the responses
received from respective HES
systems for meeting this SAT
criteria.
4 Remote connect / Action to response Less than 3 mins MDMS Scope – MDMS shall
disconnect for individual initiate the RC/DC requests for
meter selected meter(s) and store
and display the responses
criteria.
5 Updating of data Updating of Action MDMS need to share data
on consumer individual performed for immediately that are required
portal/ app consumer data on active consumer by consumer portal or app so
portal/ app after on portal within that the same can be updated in
receiving the data 5 minutes after respective apps.
in MDM receiving the
data in MDM
6 Ping Response For installed Action MDMS Scope – MDMS shall
with meters performed at initiate the on-demand ping
acknowledgemen 98% of meters requests for selected meter(s)
t/ response for within [5] and store and display the
selected meters minute responses received from
respective HES systems for
meeting this SAT criteria.
7 Ping Response For an individual Action MDMS Scope – MDMS shall
with meter performed initiate the on-demand ping
acknowledgemen within 3 seconds request selected meter and
t/ response for store and display the responses
selected meters received from respective HES
criteria.
8 Meter loss and Receiving of alert Alert to be MDMS Scope – MDMS shall
restoration of for all affected AMI received within store and display the alerts
supply meters 3 minutes for received from respective HES
60% of meters systems as and when available
and compare the same with the
meter event data for meeting
this SAT criteria.
Page 20 of 35
9 Meter Tamper Receiving of alert Alert to be MDMS Scope – MDMS shall

Alerts for an individual received within store and display the alerts
meter 3 minutes received from respective HES
systems as and when available
and compare the same with the
this SAT criteria.
10 Power Quality Receiving of alert Alert to be MDMS Scope – MDMS shall
Alerts for an individual received within store and display the alerts
meter 5 minutes received from respective HES
systems as and when available
compare the same with the
this SAT criteria.
11a Firmware For installed AMI Action MDMS Scope – MDMS shall
upgrade with meters (for a batch performed at initiate the on-demand
acknowledgemen of at least 20% of 99% of meters firmware upgrade request for
t/ response for installed base) within [18] selected meters, store and
selected meters hours; display the responses received
from respective HES systems
for meeting this SAT criteria
11b Firmware For installed AMI Action MDMS Scope – MDMS shall
upgrade with meters (for a batch performed at initiate the on-demand
acknowledgemen of at least 20% of 99.9% of meters firmware upgrade request for
t/ response for installed base) within [24] selected meters, store and
selected meters hours; display the responses received
from respective HES systems
for meeting this SAT criteria
12a Remotely altering For installed AMI Action MDMS Scope – MDMS shall
settings in meter meters (for a batch performed at initiate one selected on-
of at least 20% of 99% of meters demand configuration change
installed base) within [8] hours request for selected meters,
store and display the responses
criteria
12b Remotely altering For installed AMI Action MDMS Scope – MDMS shall
settings in meter meters (for a batch performed at initiate one selected on-
of at least 20% of 99.9% of meters demand configuration change
installed base) within [24] request for selected meters,
hours store and display the responses
criteria
13 Remotely read For reading the full Action MDMS Scope – MDMS shall
events logs event log for performed for initiate process to on demand
installed AMI • 90% of read event logs from selected
meter meters meter (s) and store and display
within [30] the alerts received from
minutes; and respective HES systems as and
• 99% of when available for meeting this
meters SAT criteria.
within [1]
hour; and
Page 21 of 35
• 99.9% of
meters
within [6]
hours.
14 VEE processing For all installed Action MDMS scope to demonstrate
meters performed in the completion of VEE activities
[15] mins within the stipulated time for
the LOT of meters under SAT
15 Computation of For all installed Action MDMS scope to demonstrate
Billing meters performed in [2] the completion of billing
Determinants hour determinant calculation
activities within the stipulated
time for the LOT of meters
under SAT
16 Prepaid Recharge Payment success to Within 5 mins MDMS scope is to receive the
consumer payment information with time
acknowledgement stamp from the different
payment avenues for this
project and sending
acknowledgement to mobile
App , Consumer portal
,SMS/Email gateway within the
stipulated time for the LOT of
meters under SAT
The overall objective is to meet
the performance timeline in
conjunction with the integrated
AMI ecosystem
17 Prepaid Recharge Payment success to • From 90% of MDM scope:
meter update meters within As and when payment details
(From MDM to HES 30 minutes are received from payment
to Meter) • From 99% of avenues the MDMs shall
meters within compute the balance and send
1 (one) hour recharge /balance update for
the meters meter to HES as well
to the Consumer mobile APP,
Portal, SMS /Email gateway
18a Utility User Manual data entry Less than 6 secs MDMS scope
Interface of new value
appears on screen
18b Utility User Acknowledgement Within 3 secs MDMS scope
Interface of any action
request
18c Utility User Display update 2 secs MDMS scope
Interface rate
19a Disaster Recovery Recovery Time [1 hour] as MDMS Partner scope
Capability Objective (RTO) agreed
19b Disaster Recovery Recovery Point [30 Min] as MDMS partner scope
Capability Objective (RPO) agreed
20 On-Demand Collection of 7 days 95% complete MDMS Scope – MDMS shall have
Remote reads of interval energy within 2 hrs the provision to initiate the on-
meters data and the demand read request for
current total 100% complete selected meter(s) and store and
accumulated within 4 hrs display the responses received
Page 22 of 35
energy from a from respective HES systems

group of 10% of for meeting this SAT criteria
installed base of
meters
(configurable)
D3. Training Obligations
Partner is required to organize following training for the IntelliSmart and DISCOM personnel during
course of solution implementation for each of the projects.
a) Professional Training - This training shall be organised for the Utility/Discom’s and IntelliSmart
operational team. Each member would be trained in the relevant function/ module. This Training
would be required to be given to approximately [25] personnel. Standard curriculum shall be
designed and agreed with IntelliSmart/ Utility. This training shall preferably be organized in
virtual and on-site model.
b) End User Training – The implementation partner shall conduct these training in "Train the
Trainer" basis. These training sessions will be required to be conducted on sites. The
recommended training material can be in paper / electronic media.
The training modules shall include but not be limited to followings:

Sessions Total Onsite - Onsite -
Sl. No. Training area (Indicative)
(Tentative) DISCOM IntelliSmart
1 MDMS functionality and operational aspects 20 15 5
• MDMs & Prepayment solution overview
• MDM & Prepayment Functionality
• Business process and integration
• Users and Roles
2 Database, Report and Analytic 10 5 5
3 MDMS Administration & Configuration, 5 2 3

maintenance, troubleshooting
4 MDMs functionality and Operations 25 15 10
5 Cyber Security related Training 5 2 3
65
Partner shall build training modules and Schedule in consultation with IntelliSmart for the project
as part of the design documentation.
D4. System Availability Test

After UAT/ SAT a system Availability test shall be conducted as per the test plan given by IntelliSmart. This
test shall be performed for a continuous 120 hrs of the deployed system and shall meet the system
availability as defined below:
Sl. No. System Minimum System Availability Requirements
1. MDM 99.5%
2. User Interface 99.5%
D. 5 Operational Acceptance
The Operational Acceptance of the deployed MDM with prepaid system shall be considered as complete on
a) Completion of training obligations
b) Successful Integration of MDMS with prepaid system with other business application of AMI project
eco-systems and DISCOM (FIIT)
c) Successful completion of UAT/SAT for the first LOT of Smart Meters.
d) Successful completion of system availability test for 120 (one hundred twenty) hours after first
successful SAT
Page 23 of 35
e) Independent third-party cyber security audit of the cloud setup
D. 6. Policy and other Documentation

Partners will have to develop, document, and implement the following related with their scope:
a) Data Backup, Archival and Retention Policy
b) Security Policy
c) Business Continuity and Disaster Recovery Policy
All the policy and procedure which will always ensure availability and security, these policies have to be
updated every six months (twice a year) or as per requirements of project.
Design of Information Security Policy shall necessarily include but not limited to the following policies to
ensure IT security:
a) IT Risk Management Policy
b) Information Classification Policy
c) Access Control Policy
d) User ID and Password Management Policy
e) Internet Access Policy
f) Asset Management Policy
g) Incident Management Policy
h) E-mail Security Policy
Documentation requirements
a) Data Privacy Approach
b) Cyber Security Approach
c) Risk Planning
d) Governance Framework
e) Solution Architecture
f) Deployment Architecture
g) Low Level Design Document
h) High Level Design Document
i) An approach paper documenting the interfaces for integration with existing and future
applications based on the information provided by IntelliSmart/DISCOM
j) Project Team Structure
k) Quality Assurance/Quality Control of the program
Page 24 of 35
Appendix- E: Implementation Approach & Timelines

To meet the design requirements, the MDM with the prepaid system will retrieve data from multiple
Headend systems (HES), process commands as well as expose the master and transaction data to the
upstream business application of DISCOM –billing system, Customer portal and Mobile app etc.
The Scope of MDMS with the prepaid system shall be completed in two stages to support the smart meter
deployment and DISCOM’s Business as Usual (BaU) operations.
a) Implementation Stages
Stage -1:
In first stages the basic core application will be configured and integrated with the HES and DISCOM
billing application to support the smart meter deployment on ground and keep the DISCOM on ongoing
billing activities continuing.
Partner along with IntelliSmart shall workout with DISCOM on the minimum core functionalities, FIIT
use cases to be deployed at this stage.
Below table is an indicative prioritization of the minimum use case implementation during stage 1
Sl. No. Use Case Activity Description
1 Collection of Daily Meter Profile
2 Monthly Billing profile collection
3 Remote Meter disconnection
4 Remote Meter Reconnection
5 Detects tampering at consumer site
6 Consumer connection outage/restoration event
7 Outage/restore event recorded by meter is sent to HES as and when event occurs
8 Outage / Restoration Notification
9 Prepaid Consumer Recharge
10 Calculate credit balance for prepaid consumer & update prepaid meter
11 Demand read of meters from consumer premises
12 Access to MDMs web page
Stage -2:
In second stage, the balance functional requirement and other advance features and report, analytics,
SLA Dashboard, Prepayment and related integration shall be delivered to meet the Final FIIT use case
Demonstrations, its acceptance from IntelliSmart and successful execution of the SAT activities for the
first LOT of meters for the project
b) Implementation Timelines & Milestones
Time is essence for this project. Below table is key milestones and timelines to achieve these critical
deliverable/ tasks. Within 6 weeks the system shall be made operational with stage 1 functionality
and shall achieve successful SAT for the 1st LOT of meters within 3 Months. Partner needs to adhere
to the given timelines and provide detailed project plan for implementation and deliverable
milestones as part of its design documentation.
Milestones Deliverable / Task Timelines
AS IS Study and Analysis of requirements including 1 week from the date of

1. Initiation & Design Interfaces with the existing systems & Submission of LOA
“TO BE” design document
Page 25 of 35
Approval of design document and business process 2 weeks from the date of
related to MDMs scope. LOA
Provisioning of the development environment on cloud 2 weeks from the date of
2. Development
for MDMs and deployment on MDMs software for LOA
environment setup
development / configuration
3a. Implementation / Integration of the MDMs solution for the use cases for 4 weeks from the date of
Development stage 1 LOA
Stage 1 Configuration / customization of the MDMs application
for core feature
Deployment of the MDMs with configuration and the 6 weeks from the date of
3b. Deployment of
integration interfaces in production environment of LOA
MDMS in production
with stage -1 functionality
Completion of Stage 1
4. Completion of SAT / Integration of the MDMs solution for the use cases for 8 weeks from the date of
UAT and Operational Stage 2 LOA
acceptance Integration of MDMs with AMI project application
landscape (HESs, Customer Portal, Smart Mobile app ,
ware house& workforce management) and DISCOM’s
legacy applications
- Configuration / customization of the MDMs
application for advance features, reporting &
Dashboard, and analytics.
- Training to users
- Deployment of the MDMs with completed
configuration and the integration interfaces in
production environment
Successful completion of SAT, UAT & Availability test
5. Operational 12 weeks from the date of
Operation Maintenance and support Resource
Acceptance and & Start LOA
availability.
of Operations and
SoPs for the Operations and Maintenance, Support
Maintenance, Support
services.
services
Software Inventory
c) Stabilization Phase
There shall be a stabilization phase of three months from the of Operational Acceptance of the system.
In this period Partner shall provide support to stabilization of the implemented MDMs system. As part
of this, following activities will be carried out:
i) Deploy all relevant functional and technical implementation team during the stabilization
period.
ii) During stabilization, if complete solution is not working or performing as per the IntelliSmart /
DISCOM requirements, Partner will rectify, reconfigure / tune the MDMs solution to comply the
same.
iii) Fixing of defects / bugs identified
iv) Partner will update user manuals and other relevant documents if there is any change in the
process or solution.
v) SLA will be monitored during this period and Partner will be responsible for compliance of the
same.
Page 26 of 35
Appendix- F: Operations, Maintenance and Support Services post

Operational Acceptance
After successful completion of UAT and SAT, Solution Operations Maintenance and support period will
commence. The broad scope these operations services are as below:
A) MDM with Prepaid Services

The scope under operation services related to MDM and prepaid system shall include (not limited to)
a. Comprehensive management of all the software (including licensing and annual technical support
cost) under scope of this contract.
b. Any bug fixing, Fine tuning of All in-scope applications, business processes/ databases,
Implementation of OEM released patches in defined maintenance/ downtime window after testing
the same in non-production environment.
c. Support, enhancement, upgrade of: UI, Integration interfaces, workflows, reports/Dashboards
(existing / new ) and the analytics .
d. Day to day operations of the deployed MDM with prepaid system under supervision and authority
of the IntelliSmart /DISCOM. These shall include among others,
i) Changeover of consumer meters from post-paid to prepaid mode and vice versa.
ii) Ensuring completion of recharge cycle of prepaid consumer meters
iii) Connecting, disconnecting, or reducing consumer’s sanctioned load under approval from the
DISCOM
iv) Ensuring availability of BP, LP, interval data and event notifications from meters in time
schedules as agreed
v) Ensuring scheduled completion of billing determinant calculations
vi) Ensuring daily / monthly reports from the MDMs system as per agreed list, and are made
available to IntelliSmart / DISCOM
vii) Ensuring smooth data exchange traffic between the MDM system, other AMI applications
like HESs, Consumer mobile app, portal, WFMs and DISCOM systems
viii) Patch management of applications at cloud data centre
ix) Provide reports, dashboard and backup data to support various SLA
x) Carry out performance checks of various functions as per agreed schedule or on demand.
e. As part of their Operation and Maintenance responsibilities, the partner shall develop a
compendium of Operation and Maintenance Manuals. These manuals shall be kept updated as
often as necessary to reflect best practices being employed in the project.
f. The partner has to hand hold the DISCOM /IntelliSmart team to take over operation, maintenance,
and support services after completion of contract period. The project/ system devices should
allow their functionalities to be upgraded without disruption to the existing functionalities by
downloading new software and configuration information under their scope.
g. Software maintenance, debugging and support throughout the contract period.
B) Operations and support Manpower

For the Operations Maintenance and support of the project, Partner shall provide MDMs with prepaid
system & Cloud operations services and deploy necessary functional and technical resources
(Dedicated / Shared / Onsite/Offsite) as per the project/contract need.
Partner shall submit a list of resources which they will deploy for Operation, Application Maintenance
and Support Services after completion of Implementation phase till the end of the Support and O&M
period. IntelliSmart reserves the right to evaluate the skills and performance of resources and ask for
replacement if not found satisfactory.
Sl. No. Resource Type Count Location (Onsite/ Off Site / Hybrid)
Beside the adequate and proficient /skilled resources deployed at partner’s backend facilities for
Page 27 of 35
delivering of the services, Partner shall position following man-power resources at each projects
NOMC/Site for the project duration.
a) [One] number of operations staffs for monitoring of MDM system & Cloud
b) [One] MDM product & Integration specialist (5+ years’ experience in relevant area)
c) [One] Data Analyst (5+ years’ experience in relevant area)
Maintenance and Support activity

The partner shall carryout the below routine maintenance and support activities for the deployed
system:
Item Routine maintenance & support task

1.0 Problem Identification
Root cause analysis to determine whether the fault is attributable to Software or cloud
1.1
infrastructure
2.0 Software Problem Resolution
2.1 Report problem and assist with problem identification
Provide or recommend corrections, temporary patches, workarounds, or other fixes to
2.2
system problems
Install and test corrections, temporary patches, workarounds, or other fixes to system
2.3
problems
3.0 Routine Software Support
3.1 Build and maintain database, displays and reports - Tuning for optimum performance
3.2 Perform system back-ups & restore or reinstall software from back-ups
3.3 Scheduled and Preventive maintenance activities
3.4 Monitor system logs (part of remote monitoring service)
3.5 Maintain system logs
3.6 Maintain user accounts
4.0 Integration and Database
4.1 Monitoring of System Integration API /Interface for its functioning /performance
5.0 Cyber Security Monitoring
5.1 Patch Updates
5.2 Cyber Security Monitoring
5.3 Annual Audits
5.4 Implementation of Recommendations during Audit
The above-mentioned aspects are not exhaustive and Partner is required to provide all necessary
support to ensure the complete solution is functional as per business requirements without any
additional cost
E) Exit, Handover Transition-Out Responsibilities
Six (6) months before the end of Operations, Application & Maintenance Support Services the Partner
shall prepare and submit a detailed exit plan (“Exit Plan”). IntelliSmart Project Manager along with
designated team will review the Exit plan. If the plan is rejected Partner shall prepare alternate plan
within two (2) working days. lf the second plan is also rejected, IntelliSmart Office Manager will
provide a plan to the Partner, and it should be adhered in totality.
Page 28 of 35
On acceptance of the Exit plan the Partner shall
I. Execute all documents that may be necessary to effectively transfer the ownership and title,
including OEM warranties in respect of all equipment, material, hardware and software,
customised development etc. and escrow licence.
II. Handover all the DISCOM & project related data along with software license in such a manner
that operations of the DISCOMs should continue without any restriction.
III. Handover all developed codes, related documentation, and other Configurable Items if any in
his possession.
IV. Handover the list of all IT Assets, passwords to the IntelliSmart.
The Partner shall design a comprehensive team/organization structure to for IntelliSmart/DISCOMs to

manage the system. The Partner shall carry out an analysis of the skill set requirement for the to manage
system and carry out the training & knowledge transfer.
The Partner and the Authorized personnel from IntelliSmart will sign a completion certificate at the end
of successful completion (all points tracked to closure) of the Exit Plan.
Transition-Out Responsibilities for migration:
Exit Management / Transition-Out Responsibilities

Continuity and performance of the Services at all times including the duration of the Agreement and
post expiry of the Agreement is a critical requirement of IntelliSmart. It is the prime responsibility of
partner to ensure continuity of service at all times of the Agreement including exit management
period and in no way any facility/service shall be affected/degraded.
a. Support IntelliSmart in migration of the VMs, data, content and any other assets to the new
environment created by IntelliSmart or any Agency (on behalf of IntelliSmart) on alternate
cloud service provider’s offerings to enable successful deployment and running of the
IntelliSmart’s solution on the new infrastructure by providing a mechanism to IntelliSmart for
the bulk retrieval of all data, scripts, software, virtual machine images, and so forth to enable
mirroring or copying to IntelliSmart supplied industry standard media.
b. The format of the data transmitted from the cloud service provider to IntelliSmart should
leverage standard data formats (e.g., OVF, VHD…) whenever possible to ease and enhance
portability. The format will be finalized by IntelliSmart.
c. 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 IntelliSmart.
d. Ensure that all the documentation required by IntelliSmart for smooth transition including
configuration documents are kept up to date and all such documentation is handed over to
IntelliSmart during regular intervals as well as during the exit management process.
e. Shall not delete any data at the end of the agreement (for a maximum of 45 days beyond the
expiry of the Agreement) without the express approval of IntelliSmart.
f. Once the exit process is completed, remove the IntelliSmart’s data, content and other assets
from the cloud environment and certify that the VM, Content and data destruction to
IntelliSmart as per stipulations and shall ensure that the data cannot be forensically recovered.
g. There shall not be any additional cost associated with the Exit / Transition-out process.
Page 29 of 35
Appendix – G: Service Level Agreement (SLA)

Partner will ensure the MDM with prepaid solution and cloud infrastructure meet the uptime and
performance SLAs after the Operational acceptance. MDM implementation partner shall be held
responsible for maintaining SLA of data subject to availability in HES. Partner shall showcase reconciliation
report for any shortage in MDM SLA in comparison to data availability at HES. The time duration window
defined below for each SLA includes data availability in HES and MDM both. SLA parameters shall be
monitored on monthly basis as per the individual SLA parameter requirements as below:-
A) System performance:
@ Subject to timely data availability in HESs for MDMs in the SLA time window. The SLA penalties are
capped at 30%
## Subject to actions status availability within the SLA time window
Important Points
i. The maximum Penalty out of the above shall be restricted to 30% of the total monthly charges (Item
1 & 5 of price schedule A.1, A.2, and A.3) for each project separately. If the bidder will attract
penalties at a capping of 30% for 3 consecutive months, will be considered for 100% penalties from
the 4th month onwards and a show cause notice will be issued to Bidder.
ii. If MDM partner has failed to achieve RC/DC and Daily Profile SLA (i.e., less than 90%) in that case
100% penalty shall be imposed on MDM partner.
iii. Exclusions (Non-Operational meters): Power Outages, Meter bypass by consumers, Local
Temporary/ Permanent disconnection by Utilities, and Meter burnt shall be excluded from the above
SLA calculations.
iv. The penalties would be computed on the basis of performance for the calendar month.
Performance
Requirement (MDM)
Performance
Data/performance *Time window is
Requirement Penalty Logic
parameter defined after
(HES)
availability of meter
at HES
1. Scheduled Interval data readings
Periodic collection of the From 97% of From 97% of meters Deduction of 1% Number of
interval load profile data meters within within 1 hours of Monthly operational
for installed meters 7hours charges for meters=N
*Assuming interval of every 0.5% fall
15/30 minutes as per or part thereof Number of
Utility requirement. penalty in SLA. meters with
From 99% of From 99% of meters Deduction of 1% successful
meters within 11 within 1 hours of Monthly 48/96 sample
hours charges for interval
every 0.5% fall data=Y
or part thereof
penalty in SLA. % SLA
From 99.5% of From 99.5% of meters Deduction of 1% Z=(Y/N) *100
meters within 22 within 2 hours of Monthly
hours charges for # Any Meter
every 0.5% fall which has
or part thereof sent<48/96
penalty in SLA. sample
interval will
be considered
out of SLA.
2. Scheduled daily meter read profile
Previous day interval From 97% of From 97% of meters Deduction of 1%
Energy and Total meters within 12 within 1 hours after of Monthly
accumulated Energy midnight charges for
Page 30 of 35
Performance
Requirement (MDM)
Performance
(HES)
at HES
hours after every 0.5 % fall
midnight or part thereof
penalty in SLA.
From 99.5% of From 99.5% of Deduction of 1%
meters within 22 meters within 2 hours of Monthly
hours after after midnight charges for
midnight every 0.5 % fall
or part thereof
penalty in SLA.
3. Scheduled billing profile data for the billing period
Collection of Billing and From 95% of From 95% of meters Deduction of 1%
block profile data for the meters within 36 within 4 hours of the of Monthly
billing period for the hours of the scheduled periodic charges for
entire installed scheduled collection every 0.1 % fall
population periodic collection or part thereof
penalty in SLA.
From 99.5% of From 99.5% of meters Deduction of 1%
meters within 48 within 4 hours of the of Monthly
hours of the scheduled periodic charges for
scheduled collection every 0.1 % fall
periodic collection or part thereof
penalty in SLA.
From 100% of From 100% of meters Deduction of 1%
meters within 160 within 8 hours of the of Monthly
hours of the scheduled periodic charges for
scheduled collection or end of every 0.1 % fall
periodic collection the billing period. or part thereof
or end of the penalty in SLA.
billing period.
4. Scheduled energy audit and reliability indices report (DT wise)
Generation of monthly From 100% of DT Deduction of 1%
energy audit and installed meters
of AMISP Service
reliability indices report within 384 hours (16 Charge for every
days) 0.5 % or part
there off
5. Scheduled energy audit and reliability indices report (Feeder wise)
Generation of monthly From 100% of Deduction of 1 %
energy audit and installed Feeder of AMISP Service
reliability indices report meters within 384 Charge for every
hours (16 days) 0.5% or part
there of
6. Remote connect and disconnect with Success response
On receiving the Connect Action performed Action performed and Deduction of 1%
and Disconnect command at 95% of meters acknowledgment at of Monthly
from MDMS within 10 minutes; 95% of meters within charges for
and 5 minutes; (2 Minutes every 0.5% fall
for initiating the or part thereof
command and 3 penalty in SLA
Minutes for
acknowledgment)
and
Page 31 of 35
Performance
Requirement (MDM)
Performance
(HES)
at HES
Action performed Action performed and Deduction of 1%
99.5% of meters acknowledgment at of Monthly
within 5 hours 99.5% of meters charges for
within 1 Hour; (30 every 0.5% fall
Minutes for initiating or part thereof
the command and 30 penalty in SLA
Minutes for
acknowledgment)
7. Remotely top-up amount (for pre-paid application only)
Update of Current 99.9% meters Current balance and Deduction of 1%
Balance and recharge within 30 minutes recharge information of Monthly
information to the smart (delivered and for 99.9% meters sent charges for
meters in prepaid after intimated to to HES, and mobile every 0.5% fall
receiving the information consumer) app within 5 minutes or part thereof
to the HES system from penalty in SLA.
MDMS
8. Availability of AMI System per month
Availability of the >99.5% ≥99.5% Deduction of 2%
delivered AMI System per of Monthly
month charges for
every 0.1 % fall
or part thereof
penalty in SLA.
B) Application Maintenance Support services

Sl. No. Service Parameter Service level Performance-related Penalty
1 Response Average Time taken to Severity 1 For Severity-1 cases Rs 10000 per 30
Time acknowledge and 30 Minutes minutes after allowed maximum
respond once an time to respond
Incident is discovered, Severity 2
or ticket/incident is 1 Hour For Severity-2 & 3 cases
logged. This is
calculated for all Severity 3 Rs 5000 for each additional 1 Hour
tickets/incidents 4 Hours
reported / discovered
within the reporting
month.
2 Time to Time taken to resolve For Severity 1, Rs 1,00,000 per 120 minutes of delay
Resolve - the reported 99% of the after allowed maximum time for
Severity 1 ticket/incident from incidents shall be each incident Reported.
the time of logging. resolved within 4
hours of problem
reporting
3 Time to Time taken to resolve 98% of Severity 2 For Severity 2, Rs 25,000 per 12
Resolve - the reported within 24 hours of hours delay after allowed maximum
Severity 2,3 ticket/incident from problem reporting time for each incident Reported.
the time of logging. AND 95% of
Severity 3 within For Severity 3, Rs 10,000 per day of
10 days problem delay after allowed maximum time
reporting for each incident Reported.
Table: Description of Severity Level
Page 32 of 35
Severity
Description Illustrations (Not limited to)
Level
Environment is down or major 1. Non-availability of production system
malfunction resulting in an in operative infra
condition or disrupts critical business 2. No access to storage, software, or
Severity 1
functions and requires immediate application
(S1)
attention. A significant number of users 3. 50% Users cannot log in.
Serious /
are unable to reasonably perform their 4. Stoppage of data backup at DC/DR
Emergency#
normal activities as essential functions 5. Cyber Security issues leading to
and critical applications are either not unauthorized access to
working or are not available systems/applications
Severity 2 The environment is usable but with 1. Intermittent system behaviour
(S2) severely limited performance /partial 2. Interruption of data exchange with HES
Major outage resulting in 10-50% users being and DISCOMs enterprise systems
unable to perform their normal 3. Breach of data privacy
activities as essential functions and 4. Adherence to RPO / RTO
critical programs are partially available
or severely restricted, risk of significant
data loss, Inconvenient workaround or
no workaround exists. affecting 10-50%
Users
Moderate loss of performance resulting 1.Any other system defect, failure, or
Severity 3 in multiple users impacted in their unexpected operation.
(S3) normal functions. 2. Request for information, technical
Minor configuration assistance, “how to”
guidance, and enhancement requests.
# 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 system failure can be
attendedto. Severity 1 issues shall be reported by telephone for rapid response; the key objective is to
restore the systemto an operational state as quickly as possible.
Note 1: System Availability Calculations

System availability / uptime 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
each 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.
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:
S1/ S2/ S3 is the total non-available hours in Severity Level-1 /2/3 hours passed beyond the
maximum resolution time for which the event is not resolved.
Where THM is total minute in the month, excluding the period for which Head end systems was not
available in that month, planned service (Preventive, Scheduled) downtime *** in that month, service
interruptions due to a Force Majeure Event.
*** Allowable planned service downtime is maximum of 04 hours in a month. Any additional time
requires specific agreement with IntelliSmart. The downtime for scheduled / preventive
maintenance (patch application, upgrades – OS, Database, etc.) would need to be mutually agreed
with IntelliSmart/Utility and to the extent practically possible should be taken up during non /lean
business hours. To reduce this time, various maintenance activities can be clubbed together with
proper planning.
Page 33 of 35
Note:
Partner shall implement an appropriate online Application performance SLA monitoring and a
ticketing system for problem/defect reporting and tracking. This would enable logging and tracking
of outages / defects/non-conformances of all severity levels.
These performance levels shall be checked for conformance monthly. It is expected that the delivered
system shall meet the minimum performance threshold of performance requirement against each
lever. Any degradation below this minimum threshold will attract penalties as per bands of service
level met. The total penalties under SLA categories shall capped at [30%] of the monthly service
charges (Item 1 & 5 of price schedule A.1, A.2, and A.3) for each project separately.
Assumptions & Exclusions

Partner shall provide the assumptions and exclusion list separately considered while working on MDM
proposal. IntelliSmart won’t consider any assumptions & exclusion during the design, development,
implementation, and O&M stage of project stage.
Page 34 of 35

MDMS - Technical - Agreement - For - 11 Lacs - Smart - Meters

Uploaded by

Copyright:

Available Formats

MDMS - Technical - Agreement - For - 11 Lacs - Smart - Meters

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MDMS - Technical - Agreement - For - 11 Lacs - Smart - Meters

Uploaded by

Copyright:

Available Formats

Technical Specification and Scope of Work for

Meter Data Management System

Sl. No. Abbreviation Full Forms

1 Scope of Work ....................................................................................................................... 3

Appendix – A: Software Licenses BoQ..................................................................................... 10

Appendix – B: Cloud IT Infrastructure Sizing and Guidelines ............................................... 13

Appendix – C: Technical, Functional and Integration Requirements and its compliances . 15

Appendix - D: Testing, Training and Operational Acceptance .............................................. 19

Appendix- E: Implementation Approach & Timelines ........................................................... 25

Appendix- F: Operations, Maintenance and Support Services post Operational

Appendix – G: Service Level Agreement (SLA) ....................................................................... 30

3. Partner’s Responsibilities and Obligations

Note – Invoicing shall commence after the operational acceptance

Note – Invoicing shall commence after the operational acceptance of the

A.3 Schedule: Project -3

Note – Invoicing shall commence after the operational acceptance of the

B. Manpower cost for change management

Total Cost: A.1 + A.2 + A.3 + (B x 3) = INR _________________________________________ (In Figures)

5.3 Milestones and Payment Schedule

5.3.1 Payment of Quarterly MDMs Software Licenses

* Refer Appendix – E: Implementation Approach & Timelines

5.3.3 Payment towards Training and Manpower

5.3.4 Payment of Monthly MDMs Services

Appendix – A: Software Licenses BoQ

Appendix – B: Cloud IT Infrastructure Sizing and Guidelines

B.1 Application Deployment Approach

B2. Sizing Inputs

Appendix – C: Technical, Functional and Integration Requirements and

C2. High Level Solution overview

C3. High Availability, Load Balancing & Scalability

All Projects Application Availability 99.5%

Recovery Time Objective (RTO) 1 Hour

Partner shall provide a comprehensive detail on the below:

C4. Solution Integration

AMI System landscape for the projects:

C4. Data Analytics and Reports

Appendix - D: Testing, Training and Operational Acceptance

D.1 FIIT Use-cases:

Sl. No. Head Description Criteria Remarks

maximum possible syncing for

Sl. No. Head Description Criteria Remarks

9 Meter Tamper Receiving of alert Alert to be MDMS Scope – MDMS shall

Sl. No. Head Description Criteria Remarks

Sl. No. Head Description Criteria Remarks

energy from a from respective HES systems

D3. Training Obligations

The training modules shall include but not be limited to followings:

3 MDMS Administration & Configuration, 5 2 3

D4. System Availability Test

e) Independent third-party cyber security audit of the cloud setup

D. 6. Policy and other Documentation

Appendix- E: Implementation Approach & Timelines

b) Implementation Timelines & Milestones

Milestones Deliverable / Task Timelines

AS IS Study and Analysis of requirements including 1 week from the date of

Appendix- F: Operations, Maintenance and Support Services post

A) MDM with Prepaid Services

B) Operations and support Manpower