1 / 24

Project overview, Use CASES & Architecture

FI PPP program. Project overview, Use CASES & Architecture. 21/05/2012 FIWARE Educational Week - Zurich. Outline. Project Overview Development process Use cases Functional architecture Design architecture. PROJECT MOTIVATION AND OBJECTIVES.

suchin
Download Presentation

Project overview, Use CASES & Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FI PPP program Project overview, Use CASES & Architecture 21/05/2012 FIWARE Educational Week - Zurich

  2. Outline • Project Overview • Developmentprocess • Use cases • Functional architecture • Design architecture

  3. 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

  4. project Eco-system Domain experts Future Internet experts stakeholder group waste management Business innovation applications and services domain specific smart meters street lighting water and sewage Cluster leaders FI-ware domain specific domain specific Technology foundation Transversal partners domain specific domain specific environment and transport water and environment Technology transfer Domain specific requirements

  5. clusters & partners Cluster GER Domain specific service provider BSR BSR Domain specific technology provider FI Technology expert Fraunhofer AMY CI3 DK AV UK ATOS TID AMP LEX AI UniS AMY UL ALU FT EYU Special role BSAN ENG FI common technology partner ELSTER WOS LETI UC CN EMC SAN EON TTI BIM DEN IT ES

  6. Architecture developmentprocess IoT-A reference architecture FIWARE architecture

  7. 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

  8. 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

  9. Berlin- Intelligent Public Waste Basket

  10. Birmingham - Sustainable Public Transport

  11. Carbon Footprint Time Carbon Footprint Time Birmingham - Sustainable Public Transport

  12. Santander - City Light Map

  13. FIWARE/IoT-Areference architectures FIWARE IoT-A

  14. 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 editingprocess

  15. Packages Diagram 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. 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. Provides descriptions of IoT services, historical data and methods for notifying services about events, and monitoring resource data. This component manages information related to virtual and physical devices, such as their capabilities and location, providing discovery mechanisms through searches. Provides functionality for authorization, secure data access, secure messaging, anonymization and encryption Provides functionality for managing resource allocation and controlling the data flow Provides functionality for making sure devices can be part of a network and engage in communications

  16. Design Architecture(underdevelopment) • Initialized by the Santander cluster • Bottom up approach • Application and capillarylayers are UC specific -> FI-WARE shouldtake place in the otherlayers • Interfacing FI-WARE withlegacy components • Definition of the detailedspecifications of the components in progress

  17. Design Architecture : Application layer • User interface info given to/provided by the user • Standard or generic Web Services to beused • Business actorsinvolved in the web service provision • Whowillbedeveloping the application (gadgets/UI/web services)

  18. Design Architecture : Service layer • Gadget tool and environmentspecificrequirements • OutSmart service description • OutSmart information/data description (physicalquantity, units of measurement,…)

  19. Design Architecture : Data provisioning • Sensor and wirelesstechnology • Physicalenvironment data to becollected • Data model • Data provisioning (API, spreadsheet, RSS,…) • Kinds of event to besupported • Duration of historical data keeping

  20. Design Architecture : Management • Existing APIs • Management-specificdatabase • Appropriate FI-WARE GE identified

  21. Design Architecture : Network • Communication technologylikely to beused • Existing network adapters (reusabilityacross clusters?) • Network hardware required (GWs,…) • Appropriate FI-WARE GE identified

  22. Thank You

  23. Birmingham - Sustainable Public Transport

  24. Santander - City Light Map

More Related