1 / 9

Requirements as aspects of regionalization solutions

Requirements as aspects of regionalization solutions. A contribution to the discussion from the GaBi Group as a professional software provider Tabea Beck, Martin Baitz , Jan Paul Lindner, Bastian Wittstock , Thorsten Volz. Regionalization in day-to-day business.

shima
Download Presentation

Requirements as aspects of regionalization solutions

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. Requirements as aspects of regionalization solutions • A contribution to the discussion from the GaBi Group as a professional software provider • Tabea Beck, Martin Baitz, Jan Paul Lindner, Bastian Wittstock, Thorsten Volz

  2. Regionalization in day-to-day business • Regionalization of inventories: country specific data • Regionalization of impacts (adapted CFs) • No automated (consistent, standardized) method available • But regionalization (specific characterization and interpretation) is done already since years • …either on LCI and LCIA level… • Main problem is not missing method….. • …but aspects that come up if methods are applied in daily practice by thousands of users (consistency)

  3. Requirements from a software provider`s point of view • Solution to address different spatial resolution necessary for different impact categories (GWP needs other resolution than TOX) • Regionalization information has to withstand aggregation procedure • But detailed regionalized information may not always and anywhere in the calculation needed (smart solution needed) • Flexibility of choice of impact assessment method for user of aggregated data (data handling (granularity) must not limit later interpretation) • Regionalization needs to provide significantly better results without increasing uncertainty and without severely increasing data acquisition and modeling effort • Results still have to be interpretable for industry clients  Added value for users leading to enhanced decision support has to be incentive for development

  4. Importantaspectfrom a softwareprovider`spointofview High amount of data, computing power and storage capacity required independent of database system: • How to handle this with view into future developments ? We are still a the beginning ! • Data mass is drastically increasing ! Is comprehension of LCA user bottleneck ? • Is the quality of the results also drastically increasing ? 5000 * 600* 3 * 10* 200* 8 byte= 144 GByte Amount ofscopes Averageno. oflocations No. ofrolled-upprocesses Averageno. of in- andoutputflows Averageno. ofcompart-ments Storage capacityforfloatingnumber

  5. Idea • Physically decoupling of (technical) from (regional) information • Communication over interfaces (standard) PossibleEffects • Maintenance / Updates better focused on specific needs • Storage capacity decoupled • Development of regional information (new) independent from technical (established) information (continuity) • Failure of new methods does not influence technical data

  6. Potential Solution Inter-face GIS asdatabase forRegionalized Characterization Factors Process Inventorydata Process Regionalizedimpacts Coordinates Regionalized CF Output SO2Regio-Equivalents parallel aggregation

  7. Summary and Future Requirements • Regionalization must provide added value for user in practice and academia • Regionalization should be possible for any impact method • Results still have to be (easily) interpretable • Storage capacity / speed is a topic for any software / database. Avoid data explosion. • Keep technical information like it is • Regionalization data must not influence the technical reality • Idea: Separate technical information and regionalized impact information • Need: Regionalized Characterization factors for consistent GIS datasets (e.g. format shapefiles) needed • Goal: Meaningful regionalized datasets in applicable format for professional use.

  8. Messages toenspirediscussion • Message to all We are open to any idea and solution pathway. • Message to method developers: Better roughly right than exactly wrong ! • Message to software / database providers: Smart and flexible methods based on existing data needed ! • Message to users: Only use regionalization data, if it improves the quality of your results (see goal and scope) !

  9. Two quotes from Einstein When the number of factors coming into play in a phenomenological complex is too large scientific method in most cases fails. You do not really understand something unless you can explain it to your grandmother !

More Related