Toward Open Facility Networking: Semantics Management for HigherLevel Interoperability

1
Toward Open Facility NetworkingSemantics
Management for Higher-Level Interoperability

• Hideya Ochiai Hiroshi Esaki
• The University of Tokyo / NICT
• Asia Future Internet in Jeju, 25th Aug 2009.

2
Outline

• Introduction
• Ubiquitous Directory
• Three-Tiered Facility Networking
• Application Domain Modeling
• Implementation
• Evaluation
• Summary

3
Introduction

• Facility networking for energy control
• Dense installation
• Flexibility configuration changes
• Openness to invite energy
• management experts
• Technical Problems
• Interoperability
• Access confliction
• Access control
• Interoperability to enhance the Openness

Building automation
4
Open Facility Networking
Company D
Energy Usage Optimizer
Air Conditioner
Motion Detector
Power Distribution Board
Light
Company A
Company B
Company C
5
Semantic Information

• Background information needed to actually use the
  data
• To make the system open, these information should
  be exported (or shared), so that another domain
  systems can make decisions.

The sensor is in room 101.
The air in room 101 is dry !!
The air is dry
The sensor reads humidity.
sensor
15
power on
Domain B
humidifier
Domain A
6
Approach and Goal

• For improvement of the semantics level
  interoperability
• Description-based approach
• It might increase the operational cost
• Evaluation of the feasibility
• with real testbed in Green UT project

7
Outline

• Introduction
• Ubiquitous Directory
• Three-Tiered Facility Networking
• Application Domain Modeling
• Implementation
• Evaluation
• Summary

8
Ubiquitous Directory (UD) on three-tiered
facility networking
Application Domain Models
9
Three-tiered facility networking
10
Three Levels of Interoperabilityand the Role of
UD
Actuator A wants to get energy usage
information of the light at the entrance area of
the room 102B1 in kWh.
Sensor X provides energy usage
information of the light at the entrance area of
the room 102B1 in kWh.
operable
Ubiquitous directory
Data Semantics Level
Actuator A
Application Protocol Level e.g., oBIX, BACnet/WS
Sensor X
Three-tiered facility networking
Network Level e.g., TCP/IP
11
Application Domain Models in UD
"targetObject" Domain
"location" Domain
"measurementType" Domain
12
Ubique ID Tree-based data structure
13
Semantics Description
Semantic Information
Ubiquitous Directory
Sensor (id"ABCDE")

• location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
  /102/
• measurementType/energy/Wh/absolute/
• operator"/UT/HideyaOchiai/"
• targetObject/eDevice/kitchen/microwaveOven/

Data
() These entities are managed by
application domains in the UD.
ltsensor id "ABCDE"gt ltvalue time"...1200"gt25.
2lt/valuegt ltvalue time"...1210"gt25.3lt/valuegt
ltvalue time"...1220"gt25.4lt/valuegt lt/sensorgt
14
Data format presented for applications
Ubiquitous Directory
Sensor (id"ABCDE")
Semantic Information
Data

• location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
  /102/
• measurementType/energy/Wh/absolute/
• operator"/UT/HideyaOchiai/"
• targetObject/eDevice/kitchen/microwaveOven/

ltsensor id "ABCDE"gt ltvalue time"...1200"gt25.
2lt/valuegt ltvalue time"...1210"gt25.3lt/valuegt
ltvalue time"...1220"gt25.4lt/valuegt lt/sensorgt
Semantic Information
Data
ltsensor id "ABCDE" location/jp/tokyo/bunkyo
/hongo/7-3-1/EngBld2/10F/102/
measurementType/energy/Wh/absolute/
operator"/UT/HideyaOchiai/"
targetObject/eDevice/kitchen/microwaveOven/
gt ltvalue time"...1200"gt25.2lt/valuegt
ltvalue time"...1210"gt25.3lt/valuegt ltvalue
time"...1220"gt25.4lt/valuegt lt/sensorgt
() Application programs get data
in this format
15
Outline

• Introduction
• Ubiquitous Directory
• Three-Tiered Facility Networking
• Application Domain Modeling
• Implementation
• Evaluation
• Summary

16
Implementation
Viewer
Database
Excel File
Ubiquitous Directory
TCP/IP
GW
GW
GW
GW
GW
DB
IP
IP
IP
IP
Controller
ESP Dragon
GW
GW
BACnet/WS
oBIX
BACnet/WS
BACnet/WS
IP
PLC
Emit
CiMX
BX?
Yamatake
Lonworks
Panasonic
PEW
TOSHIBA
Ubiteq
Yokogawa
17
location Domain in the UD
location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/02F
/
location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
/
location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
/102A1/
location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
/102A2/
location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
/102B1/
location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
/Aisle/
location/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F
/Aisle/EPS1/
114 Entities
UD for location
120 min for construction. there was a data list
? I just summarized into this format
18
measurementType domain in the UD
measurementType/humidity/
measurementType/humidity/RH/
measurementType/humidity/VH/
measurementType/energy/
measurementType/energy/Wh/
measurementType/energy/Wh/absolute/
measurementType/energy/Wh/1hour/
measurementType/energy/Wh/10min/
measurementType/energy/kWh/
133 Entities
UD for measurementType
155 min for construction. there was a data list
? I just summarized into this format
19
Semantics Binding Example
location
measurementType
20
Outline

• Introduction
• Ubiquitous Directory
• Three-Tiered Facility Networking
• Application Domain Modeling
• Implementation
• Evaluation
• Summary

21
ltlt without semantics managementgtgtDescription of
the same room by different operators
All of the points were associated to the room
102B1. But, the description syntax was quite
different.
22
ltlt without semantics management gtgtDescription of
point status by different systems
Expression manner is not generalized.
Yokogawa uses true/false or ON/OFF to describe
the status. Ubiteq uses T/F, and Yamatake uses
??/??.
23
ltlt without semantics management gtgtDifferent
types of data sequences for "energy usage"
24
ltlt With semantics management gtgtQuery by location

• Query by
• location
• "/jp/tokyo/bunkyo/hongo/7-3-1/EngBld2/10F/10
  2B1/"

25
from different operational domains
The same location
for signal processing algorithm selection
26
ltlt With semantics management gtgtAchievement

• Anyone in the network could find intended
  sensors.
• E.g., by location"/jp/tokyo/..../EngBld2/10F/102B
  1/"
• Application programs could identify the types of
  data sequence and choose appropriate algorithms.
• Unsolved items
• Normalization of the output values (e.g., T/F or
  true/false)
• Normalization of the detailed meanings of data
  sequences

27
ltlt Operational Cost gtgtTime spent for UD
configuration
It took about one minute for one entity. ()
There was base data sheets that present location
information and measurement type information
provided by operators.
28
ltlt Operational Cost gtgtTime spent for binding
semantics
() There was base data sheets that present
location information and measurement type
information provided by operators.
29
Outline

• Introduction
• Ubiquitous Directory
• Three-Tiered Facility Networking
• Application Domain Modeling
• Implementation
• Evaluation
• Summary

30
Summary

• Toward open facility networking
• Higher-level interoperability
• UD-based semantics management
• on three-tiered facility networking
• application domain models
• Feasibility evaluation with Green UT testbed
• Probably feasible (its still on going work)
• Open issues
• Normalization of the data value expressions
• E.g., T/F or true/false

31
Appendix
32
Light (Actuator)
Motion Sensor
An example of dense installation
?? ????????
33
An example of flexibility

• Short term deployment for analysis
• Withdraw after proper configuration.

Optimization by PDCA
Server Room
???? ?????? (Deploy)
?????? (Configuration)
?? (Withdraw)
????? (Deploy)
????
??/??
??/??
??/??
Time
6th Mar.
11th Mar.
26th Mar.
30th Mar.
31st Mar.
??????