Presentation on theme: "Building Requirements as Basis for a Key Point controlled Design Method Prof. Dr.-Ing. Raimar Scherer Romy Guruz Institute of Construction Informatics,"— Presentation transcript:
Building Requirements as Basis for a Key Point controlled Design Method Prof. Dr.-Ing. Raimar Scherer Romy Guruz Institute of Construction Informatics, Prof. Dr.-Ing. Raimar J. Scherer SUSTAINABLE PLACES 2014, October , Nice, France
eeEmbedded Basis interdependencies of the Key Points
eeEmbedded Definition “Key Point controlled Design Method” DV control in decision making level KPI control in simulation/ analysis level KDR control in experts domain level decision values key performance indicators key design requirements
eeEmbedded Requirements Aggregation Levels of decision making based on aggregated requirements and templates extension Requirements Key Design Requirements (KDR) Key Performance Indicators (KPIs) Decision Values (DVs) Result Pattern 3 Decision making Pattern 2 Simulation/ Analysis Pattern 1 Domain task 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) Knowledge based support
eeEmbedded Step-wise Requirements Aggregation
eeEmbedded 1. Aggregation: Building Requirements to Key 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.
eeEmbedded 2. Aggregation: Key Design Requirements to Key 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).
eeEmbedded 3. Aggregation: Key Design Parameters to Key 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.
eeEmbedded 4. Aggregation: Key Performance Indicators to Decision 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).
eeEmbedded Building Requirements to Key Points
eeEmbedded 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.
eeEmbedded Criteria for using building requirements
eeEmbedded PATTERN BASIS: Key Design Requirement VERIFICATION KDRs are used for verification Key Design Requirement A Verify results Process Task Key Design Parameter A
eeEmbedded Pattern 1 “Domain Tasks” 1. INPUT CONDITIONS 2. Process Task 3. Decision making 4. OUTPUT CONDITIONS
eeEmbedded PATTERN BASIS: KPI domain related decision making KPIs are used for domain related decision making domain related decision making Simulation Key Design Parameter A Key Performance Indicator A
eeEmbedded Design Pattern 2 “Simulation/ Analysis” 1. INPUT CONDITIONS 2. Process Task 3. Decision making 4. OUTPUT CONDITIONS
eeEmbedded PATTERN BASIS: Decision Values for overall decision making Decision Values are used for overall decision making FINAL ALTERNATIVE “A” overall decision making Priorization Key Performance Indicator A Decision Value A
eeEmbedded Design Pattern 3 “Decision Making” 1. INPUT CONDITIONS 2. Process Task 3. Decision making 4. OUTPUT CONDITIONS
eeEmbedded Example for Key Points in Use Case “Urban Design”
eeEmbedded Example for Key Design Parameter
eeEmbedded Example for Key Performance Indicator
eeEmbedded Example for Decision Value
eeEmbedded eeEmbedded Project eeEmbedded = Optimised design methodologies for energy-efficient buildings integrated in the neighbourhood energy systems European FP7 Project Duration: 4 years (10/ /2017) Partners: 1 University, 1 Research Institute 9 Software vendors 1 BIM consultant 4 End-users Budget: 11,1 M€ - INSTITUTE OF CONSTRUCTION INFORMATICS (COORDINATOR) - INSTITUTE FOR BUILDING ENERGY SYSTEMS AND HEAT SUPPLY DDS Data Design Systems EPM Technology STRABAG Granlund Oy, Finland BAM Utiliteitsbouw b.v. BAM Deutschland AG Nemetschek, Slovakia
eeEmbedded eeEmbedded Introduction Concept of the Collaborative Holistic Design Lab embracing the 3 domains: BIM, ESIM and BACS