A Proposal of Common Information Model for HEMS

A Proposal of “Common Information Model” for HEMS domain Group Name: MAS WG Source: Yoshihisa Ito, Takefumi Yamazaki, NTT(ito. yoshihisa@lab. ntt. co. jp) 　　　　　Nick Yamasaki, KDDI (nr-yamasaki@kddi. com) Meeting Date: 2015 -01 -19 Agenda Item: TBD

Motivation / Background < Our view about the current release. 1 specs > • Concrete resource mapping rules are not defined yet corresponding to various application domains. • If a globally common application domain is decided and the resource mapping rules with Rel. 1 specs are provided, it will lead to value one. M 2 M standard based platforms. < Domestic situations in Japan (especially HEMS domain) > • HEMS (Home Energy Management System) is currently promoted nationwide with the unified device protocol “ECHONET Lite”. • Various kinds of services with HEMS data (ex. visualization, AAL, etc. ) are expected to be developed in the future. • Thus, such services can be strongly promoted if any one. M 2 M standard based platform is available.

Related project at one. M 2 M • Our proposal is related to the concept shown in TR-0007 “ Study of Abstraction and Semantics Enablements ”. • We also think that the definition of the “Common Information Models” for various M 2 M domains is essential to specify APIs.

Home Energy Management System • • Home Energy Management System (HEMS) is one of typical M 2 M service domains. HEMS data was accumulated through gateway devices and sent to the remote management server to realize various applications. (see the below example) one. M 2 M-REQ-2012 -0072 Use Case Home Energy Management System (HEMS)

Architecture • The components for HEMS can be mapped onto the architecture of one. M 2 M. • M 2 M platform can provide services with HEMS data through APIs. • APIs can be defined based on common information model for HEMS. Service APIs Server M 2 M Platform Access Network GW GW GW HEMS Power network in the home Smart Meter HEMS Power Sensor HEMS wired wireless

An example of resource mapping for HEMS • According to one. M 2 M Rel. 1, resource mapping for HEMS data can be described as follows. Amount of electric power selling / buying on smart meter Content=2. 1 k. Wh Content=0. 8 k. Wh

Various patterns for HEMS data: (Japanese use case) • Power consumption data at many possible places can be measured at HEMS. • Resources mapping for the corresponding data must be considered. Power Network Gas Network Breaker Solar power genelation Cogeneration Breaker Main Breaker Charger for EV Device Smart Meter Breaker Whole house Breaker Box Living Dining Kitchen Room Bath Room Toilet Bed room Device Light HVAC TV Light HVAC Microwave Light Water heater Light

Expected Results / Effects • From the global standard point of view, M 2 M platform should provide the Unified APIs. • To realize such APIs, resource mapping rules at HEMS domain should also be common globally. Service Developer (Energy Domain) Fragmented APIs M 2 M PF Unified　 APIs M 2 M PF HEMS 【region-X】 【region-Y】

Summary • After Rel. 1, we propose a new work item called “Common Information Model for Home Energy Management System”. • In order to establish such a work item, we would like to have your comments and supports regarding future actions. • We will share our consideration results about concrete resource mapping for the target use cases in the coming TPs.

Point of Comment 1. What is best target work program. 2. How to use management function. – There is Control function (ex. setting device’s power-limitation). – It should be ? – Which one is better? 3. How to collaborate with semantic approach. 4. When propose to TP.