Applying FIWARE Generic Enablers to Smart Grid Management

Applying FI-WARE Generic Enablers to Smart Grid Management: Electric Car Charging Scenario Dr. Steven Davy Mobile, Middleware, Messaging @ TSSG Mas 2 tering Workshop 17 th October 2014

Overview • • • Introduction Charge Optimisation System EV Integration COS Dash. Board for DSO / TSO API access for SME’s Future Internet GE’s Integration and deployment

Introduction • FI PPP – 5 Year programme funded by the EU to explore how new Internet based technologies can bring benefit to EU Citizens • FINESCE – Applying the concepts and systems developed in the programme to the management of Electricity Distribution scenarios Page 3

Scenario <Author Name, Company>, 30. 05. 2013, Page 4

Charge Optimisation System

Optimisation Service • Optimises charging profiles for available EVs • Optimisation rounds every 15 min • Power generation forecasts from System Operators‘ web sites • Using requestresponse message exchange pattern

COS Dash. Board for DSO / TSO

COS API Support • Supports external access to EVSE data • Supports charging control • Both individual and aggregator level

GE Name (FI-WARE Chapter) Selected for further consideration? testing? Advanced to test integration phase? Data Handling (Security) DB Anonymiser (Security) Cloud Edge (Interface to Networks and Devices) Complex Event Processing (Data/Context Management) Content Based Security (Security) Identity Management GCP (Security) Reason Trial requirements include secure and privacy preserving data handling Trial requirements include anonymized data communication Trial requirements includesecure cloud data handling Trial requirements include historical data aggregation Trial requirements include encrypted data communication Trial requirements include secure authentication with an open source solution.

Identity Management GCP • Authentication and authorisation • using Open. ID and OAuth 2. 0

Data Handling GE • Usage control of user data using Sticky privacy policies: • Notification on the usage conditions of the data • Retention period • Logging and auditing tools • Encryption • PPL (Prime. Life Privacy) Language

DB Anonymizer • Evaluates the adequateness (in maintaining privacy and anonymisation) of a specific disclosure policy to be used to disclose a dataset to a third party. • DB Anonymiser calculates how much of the original content of an anonymised dataset an attacker can reconstruct.

DB Anonymizer

Content Based Security

Thank You • Questions? Page 19