1 / 25

SUSTAINABLE PLACES 2014, October 1-3 2014, Nice, France

Institute of Construction Informatics, Prof. Dr.-Ing. Raimar J. Scherer. Building Requirements as Basis for a Key Point controlled Design Method Prof. Dr.-Ing. Raimar Scherer Romy Guruz. SUSTAINABLE PLACES 2014, October 1-3 2014, Nice, France. Basis interdependencies of the Key Points.

tatyana-clemons
Download Presentation

SUSTAINABLE PLACES 2014, October 1-3 2014, Nice, France

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. Institute of Construction Informatics, Prof. Dr.-Ing. Raimar J. Scherer Building Requirements as Basis for a Key Point controlled Design MethodProf. Dr.-Ing. Raimar SchererRomyGuruz SUSTAINABLE PLACES 2014, October 1-3 2014, Nice, France

  2. Basis interdependencies of the Key Points

  3. Definition “Key Point controlled Design Method” decision values DV control in decision making level key performance indicators KPI control in simulation/ analysis level key design requirements KDR control in experts domain level

  4. Levels of decision making based on aggregated requirements and templates extension Result Pattern 3 Decision making Decision Values (DVs) Pattern 2 Simulation/Analysis Key Performance Indicators (KPIs) Key Design Requirements (KDR) Pattern 1 Domain task Knowledge based support Requirements Aggregation Requirements The purpose of the KPI methodology is to guide us through the numerous design options and help us to choose the best one as fast as possible (in the minimum time)

  5. Step-wise Requirements Aggregation

  6. 1. Aggregation: Building Requirements toKey Design Requirements • Based on the client, regulatory, site requirements (etc.) and all involved design partners • building requirements need to be translated, developed and reported in a structured way • each participating design partner is involved • RESULTs: Key Design Requirements (KDRs) • To verify compliance with the design objectives and specifications the requirements should be translated to Key Design Requirements (KDRs). • As part of this process step, the KDRs are also finally checked and matched within the participating domains.

  7. 2. Aggregation: Key Design Requirements toKey Design Parameters • The KDRs guide the design, by inclusion (build it this way) or exclusion (don't build it this way), • They are used for ruling out different design options • In the domain task level, where all domains start their iterating working cycles, the KDR are used as target values for verification of the alternatives, for tracking the design process. • KDRs represent the mandatory requirements and usually have a limited value. • RESULTs: Key Design Parameters (KDPs) • The plan values, which are to be introduced by the domains after this working step, are expressed in Key Design Parameters (KDPs).

  8. 3. Aggregation: Key Design Parameters toKey Performance Indicators • The third aggregation takes place during the simulation and analysis tasks • KDPs are used for comparing and ranking the simulation results, which are defined as Key Performance Indicators (KPIs • For elaborated comparisons, the simulation, Life Cycle Assessment (LCA) and Life Cycle Costing (LCC) experts develop based on the requirements their KDPs to evaluate the performance in their field of expertise. • With KPIs alone it is possible to make a statement how good a design alternative target specific goals. RESULTs: Key Performance Indicators (KPIs) • KPIs offer the possibility to quantify the performance of measurable indicators as well as of qualitative indicators. They are defined relative deviations from before-hand agreed KDRs.

  9. 4. Aggregation: Key Performance Indicators toDecision Values • The last aggregation is in higher decision making. For weighted evaluation the KPIs have to be aggregated to Decision Values (DVs). The preferences of the decision-makers vary, so they need the possibility to prioritise KPI with a weighting factor. The DVs comprise the weighted ecological (final energy, primary energy, etc.), socio-cultural (temperature over-/underruns, etc.) and economic (investment, maintenance and energy costs) KPI regarding their priority for the project. • RESULTs: Key Design Parameters (KDPs) • The plan values, which are to be introduced by the domains after this working step, are expressed in Key Design Parameters (KDPs).

  10. Building Requirements to Key Points

  11. Criteria for using building requirements In general, three types of requirements can be distinguished: a) Requirements that are difficult to formalize (because they describe, e.g. an impression like “relations of different views”) b) Requirements that allow drawing direct conclusions, such as space use, furniture concept etc., and c) Requirements that can be formalized as facts (values, value ranges, rules, fixed algorithms). This has influence on the scope of the potential key points in respect of the verifiability.

  12. Criteria for using building requirements

  13. Aggregations and Pattern - Decision Making Pyramid Design goal Design check Project Goal Decision Value 4. Aggregation/ Pattern • Key Performance Indicator Key Performance Indicator 3. Aggregation/ Pattern • Key Design Parameter Key Design Requirement Key Design Parameter 2. Aggregation/ Pattern Key Design Requirement 1. Aggregation Building Requirements

  14. PATTERN BASIS: Key Design Requirement VERIFICATION KDRs are used for verification Process Task Verify results Key Design Requirement A Key Design Parameter A

  15. Pattern 1 “Domain Tasks” 1. INPUT CONDITIONS 3. Decision making 2. Process Task 4. OUTPUT CONDITIONS

  16. PATTERN BASIS: KPI domain related decision making KPIs are used for domain related decision making Simulation domain related decision making Key Design Parameter A • Key Performance • Indicator A

  17. Design Pattern 2 “Simulation/ Analysis” 1. INPUT CONDITIONS 3. Decision making 2. Process Task 4. OUTPUT CONDITIONS

  18. PATTERN BASIS: Decision Values for overall decision making Decision Values are used for overall decision making Priorization overall decision making FINAL ALTERNATIVE “A” • Key Performance • Indicator A Decision Value A

  19. Design Pattern 3 “Decision Making” 1. INPUT CONDITIONS 3. Decision making 2. Process Task 4. OUTPUT CONDITIONS

  20. Example for Key Points in Use Case “Urban Design”

  21. Example for Key Design Parameter

  22. Example for Key Performance Indicator

  23. Example for Decision Value

  24. eeEmbedded Project European FP7 Project eeEmbedded = Optimised design methodologies for energy-efficient buildings integrated in the neighbourhood energy systems • Duration: • 4 years (10/2013-09/2017) • Partners: • 1 University, 1 Research Institute • 9 Software vendors • 1 BIM consultant • 4 End-users • Budget: • 11,1 M€ DDS Data Design Systems Granlund Oy, Finland EPM Technology BAM Utiliteitsbouw b.v. BAM Deutschland AG - INSTITUTE OF CONSTRUCTION INFORMATICS (COORDINATOR) - INSTITUTE FOR BUILDING ENERGY SYSTEMS AND HEAT SUPPLY Nemetschek, Slovakia STRABAG

  25. eeEmbedded Introduction Concept of the Collaborative Holistic Design Lab embracing the 3 domains: BIM, ESIM and BACS

More Related