INTEROPERABILITY SOLUTION ENERGY METERS Presentation by Madhur Kumar

INTEROPERABILITY SOLUTION ENERGY METERS Presentation by Madhur Kumar Srivastava MIOS forum under IEEMA 1

Agenda • • Why Interoperability? Interoperable Solution About MIOS – Objective, Concept & Model MIOS – System Architecture About CFW & API’s Features of MIOS Proven Concept - A Case Study 2

Why Interoperability ? • Ability to perform following operations with existing infrastructure for multiple make of meters: – Read meters of various manufacturers purchased time-to-time (as per tender specification) – Read meter using CMRI (as per CBIP 111) – Download CMRI data into the BCS – Provide data in common standardized format for further billing/analysis purpose • Ability to get the multiple manufacturer’s meters 3

Interoperable solution • A common solution for present installed base meters & future purchases also. • Preferably hardware independent interoperable solution. • Flexible to adopt “diverse customer” and “customers’ diverse” needs. • Easy portability of data to existing and developing billing systems. 4

Interoperable solution • Retention of data security and integrity. • Minimum cost of transition and administration. Above all, utilities wants to have a common & practical system keeping their investment made in metering & IT (infrastructure & software) and also security features intact. 5

About MIOS • Meter Inter-Operability Solution (MIOS) is a forum under IEEMA, working on Interoperability standards for energy meters. • MIOS provides interoperability solution to harness the information from existing and future metering assets. • MIOS is having two committees as given below: – Core Committee – Technical Committee 6

MIOS - Objective The objective of the forum is to provide possible way for utilities to use common IT infrastructure to gather information from meters of different manufacturers in use and also to ensure vendor independent integration of meter data to utility business processes through Interoperability. 7

MIOS – A Concept PC Application software MIOS is like a Driver Protocol in a Printer. (Runs on a powerful Meter (Has an internal language) Convert to PC’s language (Protocol) operating system) You can connect any Printer to Your PC following any Protocol provided have the driver Protocolyou Model Meter (Has an internal language) Convert to PC’s language (API) C D F PC Application software (Runs on a powerful operating system) MIOS Model 8

MIOS - Model • Similar to Microsoft Windows applications which supports different printer drivers. • Solution suggests software in two parts – Common Framework software (3 rd party) – Meter manufacturer’s program (APIs). • Solution provides interface for: – – Reading meter through AMR Supports reading / download through CMRI Data conversion in international acceptable format (XML). XML can directly be used for integrating with billing software. 9 Contd. .

MIOS System Architecture Mfr 01 API #1 Meters Mfr 02 API #1 Mfr 03 API #2 HHU (CMRI) Mfr 01 API #3 Mfr 02 API #3 Mfr 03 API #3 Common Data exchange format (XML) Media Software Applications ·Billing ·Revenue protection ·Tariff design ·Engineering analysis ·Load profile analysis Proprietary formats 10

Common Framework Software • CFW is master program & each manufacturer specific API is a slave (passive) module. • CFW is the user interface and initiate actions to perform specific task. • Maintain and execute meter reading schedule • CFW will link to other application programme and database 11

API types • API 01 - Read API – Initiate and read session from the meter – Save data in mfg specific format • API 02 – CMRI API – Read data from CMRI – Store data in mfg specific format • API 03 – Convert API – Convert data from mfg specific format to XML CDF (Common Data Format) 12

Features of MIOS • Supports existing installed base of meters and future purchases also. • Single data collection software for different make / model / protocol supported meter • No changes in existing CMRI solution • Supports all prevailing telecommunication interface, media independent 13 Contd. .

Features of MIOS • Flexibility to adopt continuously evolving requirements. • Flexibility to adopt diverse customer needs & customer’s diverse needs • Allows third party to collect metering data & integrate with utility’s IT system. • Futuristic & Scalable system 14

Specification Documents • Specification document of back end software to invoke API - MIOS Universal Meter Reading & Common Format (MUMRCF) (Published version 1. 17) • XML tag list document - MIOS CDF Tag List • API compliance document - MIOS API Test Procedure • API test case document – MIOS Test cases for APIs 15

API Procurement Process • API procurement process is a two step process – Step I • Become member of MIOS forum • Membership ID will be allotted • Provide concern person’s name & contact details – Step II • MIOS forum will provide requisite API • MIOS Technical Committee members / member meter manufacturer will provide support time-totime, as required. 16

Proven Concept-Case Study • One utility in northern India has developed their own meter reading software as per MIOS standard. • Utility is reading around 22000 HT & LT meters through AMR. • These meters are of different manufacturer make & model. • The common software is independent of communication port / media. 17

Proven Concept-Case Study • Read data made available in common format i. e. XML. • This data in XML is further taken into the billing software. • Simultaneously, the same data also taken to other data analysis software. 18

Present Scenario • Eight major player in India are member of this forum. • Meter manufacturers have written APIs for meter reading & data conversion. • Specification has been defined & made public & getting refined regularly. • Many system integrator has shown keen interest to adopt this concept. • Many utilities have come forward with the same specifications. 19

MIOS Member • Easun Reyrolle Limited • Elster • Genus • HPL Socomec • L&T • Omni Agate • Secure Meters Limited • ECE Industries Limited • more are in pipeline. . . EASUN REYROLLE 20

Thank you for your attention. Any questions? 21

Mfr 01 API #1 Mfr 01 API #3 Mfr 02 API #1 Mfr 02 API #3 Media Mfg specific data security system Common Data exchange format (XML) Meters Data Security System Software Applications ·Billing ·Revenue protection ·Utility data base. Private Public key Security system 22