Introduction: Data Management Challenge in Smart Grid 3 6 • Taking long time to perform a data analysis • Mismatch between the database model and the programming model • Difficult to m
Trang 1TOWARDS A FEDERATIVE POLYGLOT ARCHITECTURE FOR MANAGING SMART GRID DATA
Supervisor: Professor Christine Collet
Professor Christophe Bobineau Professor Binh Minh Nguyen Postdoctoral Researcher Houssem Chihoub
Performed at: Grenoble Computer Science Laboratory (LIG)
HADAS Team
Presented by: NHU QUYNH NGUYEN
20112648 – SIC PFIEV 56
1
Trang 3I Introduction: What is the Smart Grid?
Many Definitions – But One VISION
Trang 4I Introduction: Data Management Challenge in
Trang 5I Introduction: Data Management Challenge in
Smart Grid (2)
• Five separate classes of smart grid data, each with
its own unique characteristics
5
Trang 6I Introduction: Data Management Challenge in
Smart Grid (3)
6
• Taking long time to perform a data analysis
• Mismatch between the database model and the
programming model
• Difficult to modify a relational schema
• Increasing the amount of data
Trang 7II Polyglot Solution: Concept
Trang 8II Polyglot Solution: Architecture of proposed system
8
Trang 9II Polyglot Solution: Data layer (1)
Meter
Data
Weather Data GeographicData
9
Trang 10II Polyglot Solution: Data layer (2)
Why using PostgreSQL for Client data?
• Client data stores contact details of customers
such as first name, last name, address
• Client data requires concurrency control
strategies, data uniqueness, data security and
read-only access
• A relational database provides more control and
guarantees over data
• PostgreSQL is powerful, a open source
object-relational database system
• PostgreSQL supports CSV file, more reliability,
can run in Linux, BSD, Windows…
10
Trang 11II Polyglot Solution: Data layer (3)
Why using Cassandra for Meter data
• Meter data stores measurements of customers
are recorded by smart meters, time series data
• Data arrives from many locations, requires read
and write scalability
• Cassandra is an excellent fit for handling data in
sequence regardless of datatype or size
• Cassandra is highly performant with tables
that have thousands of columns
11
Trang 12II Polyglot Solution: Data layer (4)
Why using MongoDB for Weather and Geographic data
• Geographic data: stores location of smart meters,
geospatial queries, simple model
• Weather data: stores weather conditions such as wind
speed, dry bulb temperature…
• MongoDB: provides scale-out capabilities along with
smoother and faster data access
Trang 13III Architecture Implementation: Technologies
comprehensive infrastructure support for developing Java
applications
comprehension tool based on the concept of a project object model (POM)
based web services and uses HTTP Protocol for data
communication.
13
Trang 14III Architecture Implementation: Data layer (1)
Client data modeling and loading
14
Trang 15III Architecture Implementation: Data layer (2)
Configuration PostgreSQL
15
Trang 16Architecture Implementation: Data layer (3)
Meter data modeling and loading
16
Trang 17III Architecture Implementation: Data layer (4)
Configuration Cassandra
17
Trang 18III Architecture Implementation: Data layer (5)
Geographic and Weather data modeling and
loading
18
Trang 19III Architecture Implementation: Data layer (6)
Configuring MongoDB
19
Trang 20III Architecture Implementation: Benchmarking
Queries (1)
Query 1: Search highest electricity consuming
measured by smart meter of client that have
registered a specific address in the city of Lyon
20
Trang 21III Architecture Implementation: Benchmarking
Queries (2)
21
Query 2: Calculate the total amount of electricity
consumption by clients in Lyon at minimum
temperature below than an input temperature
Trang 22III Architecture Implementation: Benchmarking
Queries (3)
22
Query 3: Calculate the electric bill using during one month of electricity consumption based on a specific meter ID of client
Trang 23IV Conclusion and Future work
23
and storage data with high-performance – Polyglot
solution
model simulation for Smart Grid management system
Trang 2424