PROJECT OVERVIEW, USE CASES & ARCHITECTURE

21/05/2012 FIWARE Educational Week - Zurich

FI PPP program

OUTLINE

• Project Overview• Development process• Use cases• Functional architecture• Design architecture

PROJECT MOTIVATION AND OBJECTIVES

• OUTSMART contributes to the sustainability of resources by • establishing a Future Internet enabled eco-system for

cities, and • supporting the creation of innovative services with

real value to European economy and citizens

• OUTSMART addresses five essential Smart City services:• Water and Sewage• Smart Metering and Street Lighting• Waste Management• Water and Environment• Sustainable Urban Transport

PROJECT ECO-SYSTEM

FI-ware

wastemanagement

water and

sewage

environment

and transport

smar

t met

ers

stre

et li

ghtin

g

water and

environment

dom

ain

spec

ific

domain specific

domain

specific

domain specific

domain

specific

Business innovationapplications and services

Domain specific requirements

Technology transfer

Technology foundation

Clusterleaders

Future Internetexperts

Domain experts

Transversalpartners

CLUSTERS & PARTNERS

Special role

Cluster

FI common technology partner

UniSTID

ALU

EYU

Fraunhofer

ENG

ATOS

ELSTERWOS

LETI

ULAI

UC CN

AV

AMPLEX

BSRBSR

AMY CI3

AMY

EMCSAN

EONTTI

BIMDEN

FT

BSAN

Domain specificservice provider

FI Technology expert

Domain specifictechnology provider

GER

DK

ESIT

UK

ARCHITECTURE DEVELOPMENT PROCESS

FIWAREarchitecture

IoT-A reference architecture

THE IDENTIFIED USE SCENARIOS

• Water and Sewage (Aarhus)• WIRELESS OIL-WATER SEPARATOR ALARM SERVICE• THE WATER AND ENERGY NEXUS• SMART AND SOCIAL WATER METERING• KNOW YOUR WATER

• Waste Management (Berlin)• INTELLIGENT PUBLIC WASTE BASKETS• SUBSURFACE WASTE CONTAINERS• MANAGEMENT OF USER INFORMATION

THE IDENTIFIED USE SCENARIOS

• Sustainable Urban Transport (Birmingham)• INCENTIVE BASED MULTIMODAL TRANSPORT MANAGEMENT

AND INFORMATION

• Smart Metering and Street Lighting (Santander)• CITY LIGHT MAP• AUTOMATIC ADAPTABILITY OF LUMINOUS INTENSITY• PUBLIC LIGHTING AS AN INFORMATION SYSTEM• ILLUMINATION IN INTERACTION WITH USERS• OPTIMIZE ILLUMINATION NEARBY THE CITY

• Water and Environment (Trento)• WATER INJECTION CONTROL TO OPTIMISE PRESSURE IN THE

WATER DISTRIBUTION SYSTEM• ACTIVE LEAKAGE DETECTION SERVICE

BERLIN- INTELLIGENT PUBLIC WASTE BASKET

BIRMINGHAM - SUSTAINABLE PUBLIC TRANSPORT

BIRMINGHAM - SUSTAINABLE PUBLIC TRANSPORT

Time

Carbon

Footprint

Time

Carbon

Footprint

SANTANDER - CITY LIGHT MAP

FIWARE/IOT-A REFERENCE ARCHITECTURES

Trust and Security

Interface to the Network

Internet of Things Sevices Enablement

Appli/Serv Ecosystem and delivery framework

Service Provisioning Framework

Process Execution and Service Orchestration

Virtual Entity and Information

IoT Services and Resources

Device Connectivity and Communication

Security

Management

Cloud Hosting Data/Context Management

Development Tools

External Interfaces

FIWARE

IoT-A

OUTSMART BACKLOG ENTRIES(AS OF JAN. 2012)

• 1 is already supported by the current FIWARE platform•  5 have been taken into account for future releases of

the FIWARE platform• 25 are analyzed by FIWARE and the conclusion of this

analysis is still pending• 11 have been returned to the issuer for more information

and the answer from the issuer is still pending• 3 won’t be taken into account by FIWARE (should be

implemented by OUTSMART)• 18 don’t have any ticket associated (and then haven’t

been considered at all)

• difficulty in finding the right level of granularity for describing BL entries

• support for monitoring the BL entries processing• integration of the tickets tracking and BL editing

process

PACKAGES DIAGRAM

Service Provisioning Framework

Process Execution and Service Orchestration

Virtual Entity and Information

IoT Services and Resources

SecurityManagement

Device Connectivity and Communication

External Interfaces

provides the OUTSMART service layer for creating domain specific services, enabling new business scenarios in the U&E domain, involving citizens, municipalities and service providers.Note that this component is not included in the IoT-A reference architecture.

Process Execution handles predefined, non-interactive processes that run over a longer period of time, such as device monitoring. Service Orchestration allocates, resolves and brings together a set of particular services for making up a composite service. Note that this component applies to IoT related services, and acts on a lower layer than the Service Provisioning Framework.

This component manages information related to virtual and physical devices, such as their capabilities and location, providing discovery mechanisms through searches.

Provides descriptions of IoT services, historical data and methods for notifying services about events, and monitoring resource data.

Provides functionality for making sure devices can be part of a network and engage in communications

Provides functionality for authorization, secure data access, secure messaging, anonymization and encryption

Provides functionality for managing resource allocation and controlling the data flow

Provides interaction with systems external to OUTSMART, such as databases, utilities management systems and user messaging.Note that this component is not included in the IoT-A reference architecture.

DESIGN ARCHITECTURE(UNDER DEVELOPMENT)

Service Layer

Cluster-specific Application

“Out

Smar

t” A

pplic

ation

s

Web Services

Service #3 ...Service #2Service #1 Service #n

Application Layer

Service Execution Environment

Service Usage Enabler Service Exposure

Gadget Environment

Service Information Repository

Service Lifecycle Management

Web Gadget Tool

Service Development Tool

WP5

WP6

OUTSMART specific capillary network Proprietary Network Proprietary Network

Device #1 ... Device #n

Capi

llary

net

wor

ksOther Networks

(Source Info)

WP4

Historical data

Data Collection

Data Monitoring

Data Model

Ressource management

Net

wor

k Ba

ckbo

ne

Data provisionning API

AuthenticationRessource resolution

Device management (configuration, software, performance)

OUTSMART Capillary Network Access

Gateway

OUTSMART adapter

OUTSMARTadapter

OUTSMART Adaptation Block for FI-WARE Enablers

……… Proprietary networks ……….

Cluster Access Point

Security certificates

IoT devices MIB

IoT Device/Resource Catalogue

Event Management

Management API

QoS management

Dependency management

Security management

Data ModelNetwork

management

OUTSMART Adaptation Block for FI-WARE Enablers

Enab

ling

tech

nolo

gies

Event/Pattern DB

OutSmartDB

Data Management

Data Processing

OUTSMART adapterData Model

Data Model

WP3

• Initialized by the Santander cluster

• Bottom up approach• Application and capillary

layers are UC specific -> FI-WARE should take place in the other layers

• Interfacing FI-WARE with legacy components

• Definition of the detailed specifications of the components in progress

DESIGN ARCHITECTURE : APPLICATION LAYER

• User interface info given to/provided by the user• Standard or generic Web Services to be used• Business actors involved in the web service provision• Who will be developing the application (gadgets/UI/web

services)

DESIGN ARCHITECTURE : SERVICE LAYER

• Gadget tool and environment specific requirements• OutSmart service description• OutSmart information/data description (physical quantity,

units of measurement,…)

DESIGN ARCHITECTURE : DATA PROVISIONING

• Sensor and wireless technology

• Physical environment data to be collected

• Data model• Data provisioning (API,

spreadsheet, RSS,…)• Kinds of event to be

supported• Duration of historical data

keeping

DESIGN ARCHITECTURE : MANAGEMENT

• Existing APIs• Management-specific

database• Appropriate FI-WARE

GE identified

DESIGN ARCHITECTURE : NETWORK

• Communication technology likely to be used• Existing network adapters (reusability across clusters?)• Network hardware required (GWs,…)• Appropriate FI-WARE GE identified

THANK YOU

BIRMINGHAM - SUSTAINABLE PUBLIC TRANSPORT

SANTANDER - CITY LIGHT MAP