1 / 34

ENV-e-CITY A short presentation

ENV-e-CITY A short presentation. www.env-e-city.org Nicolas Moussiopoulos Aristotle University Thessaloniki, Greece. ENV-e-CITY background. Compliance of city authorities with EU environmental legislation

rasia
Télécharger la présentation

ENV-e-CITY A short presentation

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. ENV-e-CITY A short presentation www.env-e-city.org Nicolas Moussiopoulos Aristotle University Thessaloniki, Greece

  2. ENV-e-CITY background • Compliance of city authorities with EU environmental legislation • Need for efficient environmental assessments; these are only possible on the basis of sufficient and reliable environmental information. • Need to inform the citizen on the state of the environment • Support of environmental professionals, e.g. those involved in impact assessment studies

  3. ENV-e-CITY project goals • Ultimate goal of project: • To create an internet-based brokerage infrastructure for public sector environmental information, available as a “turn-key” application via docking. • Relationship to other projects: • Innovative project acting as an extension of existing, “information production” projects (APNEE, IRENIE, AIR-EIA, APPETISE, etc.)

  4. The ENV-e-CITY consortium

  5. InternetAccess Added Value Services Added Value Services Basic Services Basic Services Basic Services Common Meta Model Export Import Data Sources System architecture

  6. Thematic areas • Emissions • Air quality • Meteorology • Topography Overall scientific background: the SATURN project, the “urban” subproject of EUREKA/EUROTRAC-2 (http://lhtee.meng.auth.gr/saturn)

  7. SATURN: Studying atmospheric pollution in urban areas Objective: To substantially improve our ability of establishing source-receptor relationships at the urban scale.

  8. Topography • Data exploring “web-worms” • Digital Elevation Maps • On-line available info (Land use + Topography) (http://edcdaac.usgs.gov/glcc/globdoc1_2.html) • Topography data on demand

  9. Emissions • Data exchange Module for Emissions • City Emissions Estimator • using fuel consumption data, • based on traffic data, • overall vehicle usage, • analytical traffic network estimation.

  10. Meteorology • Easy meteorological assessment • Pre-processors • Data selection wizard • Personalized weather info • EIA studies • Suggest tools • Provide links • Support on-line submission of data and retrieval of results

  11. Air quality • Easy air quality assessment • Gaussian models (from emissions to AQ) • Model selection via MDS • Data requirements list based on assessment needs • Assessment method suggestion (on-line expert system) • Personalized Air Quality Indicators • EIA studies • Suggest tools • Provide links • Support on-line submission of data and retrieval of results

  12. Technology • System architecture • Some component examples • Web-based application examples • WebGIS example

  13. InternetAccess Added Value Services Added Value Services Basic Services Basic Services Basic Services Common Meta Model Export Import Data Sources System architecture

  14. Internet Access Administration & Service Interfaces Added Value Services Basic Services Export Import Admin Common Service & Data Model Base ENV-e-CITY Base Service & Data Provider Components

  15. WebGIS example

  16. € € Business model draft User/Customer User/Customer User/Customer User/Customer User/Customer User/Customer Price of Service & Data Service Portfolio ENV-e-CITY Broker System Broker Operator & Hosting Price Price of Service & Data License Price ENV-e-CITY Data & Service Provider ENV-e-CITY Data & Service Provider ENV-e-CITY Data & Service Provider ENV-e-CITY Data & Service Provider

  17. Competitive analysis • Competitors • City and national authorities, but will become users and providers! • Strengths • Long IT experience in relevant projects and unique scientific skills in consortium • Weaknesses • Innovation vs. pragmatism: how to overcome the momentum of a “sleeping market?”

  18. Exploitation aspects • Involvement of major “clients” from the beginning of the project: • EEA’s Topic Centre on Air and Climate Change • Eurocities • EIA community  high viability potential after the project end. • Leading institutions with strong academic background, AND very strong commercial contacts via the consortium. • ENV-e-CITY partners already provide commercially exploited products.

  19. Self standing viability • ENV-e-CITY to become the core for a European Centre of excellence for the Urban Environment. • E-content & environmental information is a promising business opportunity. • Evidence regarding the viability of the idea: Environmental information are among the top of P.S.I. data costs in Europe and U.S., and can easily be combined with brokerage architectures. • ENV-e-CITY is an immaterialisation project, taking advantage of current trends regarding the sustainable information society (http://aix.meng.auth.gr/eurosustain/) .

  20. Project co-ordinator

  21. Partner: ESS

  22. Partner: FAW

  23. Partner: FMI

  24. Partner: IER

  25. Partner: LOH

  26. Partner: NILU

  27. Partner: NORGIT

  28. Partner: RIVM

  29. Partner: TNO

  30. Broker architecture (draft) 1/2 • Meta model of data and services • formats, reference/call, semantics, prising scheme, access type... • Docking station for services • basic services: no or low costs • added value services: prised services • hosting and operating costs of broker • service and provider fees • service chains for combined services • requires detailed interface specification

  31. Broker architecture (draft) 2/2 • Type of services • request for (pre-generated) data • images, animations, maps, tables, infos, etc. • request for individual services • call of specific function (online or by order, result returned by email, ftp,...) • chaining of services • if possible: service and data providers maintain their own data and service store • depends on execution time, Internet bandwidth and local resources

More Related