Information Delivery Manual Work within HESMOS A descriptive approach to defining Information Delivery Manuals

Transcription

1 Information Delivery Manual Work within HESMOS A descriptive approach to defining Information Delivery Manuals Liebich, T.; Stuhlmacher, K.; Guruz, R. AEC3 Deutschland GmbH, TU Dresden

2 page 2/10 1 OVERVIEW HESMOS is a research project funded by the EU-Seventh Framework Programme with the title "Holistic Energy Efficiency Simulation and Lifecycle Management Of Public Use FacilitieS" and has the following objectives: Providing decision makers with advanced simulation capabilities during the whole life-cycle of buildings, taking into account energy savings, investment and life-cycle costs; Integrating a Virtual Laboratory that connects CAD and energy efficiency Tools in order to enhance building industry actors' energy efficiency competences; Closing the gap between Building Information Modeling (BIM) and Building Automation Systems (BAS) to enable economical decision making (energy & cost related) in all phases of a building's life-cycle; Integrating related topics extending current BIM to energy enhanced BIM (eebim): For developing the HESMOS eebim framework, reusable and adaptable for different practical configurations, a methodology was needed, that could be used to document new processes and to describe the associated information that have to be exchanged between parties. It was of importance that the output would be able to be used afterwards to specify a more detailed specification that would form the basis for a software development process. Thus Information Delivery Manual (IDM) was chosen, developed within buildingsmart International as the standard for processes and later published as ISO Within HESMOS it was extended and adapted for the specific objectives of life cycle modeling, the definition of a generalized multi-model framework based on, but not limited to, a single standardized BIM (currently IFC2x3), and the derivation of information and processing (workflow) requirements for the components of an integrated virtual energy laboratory (IVEL). The overall use of the IDM methodology includes the above and: identify the actors and their roles, identify the life-cycle phases, and the level of details imposed, where information flows for energy and cost related simulations are required, identify the main software application types used by the actors during the various life-cycle phases, identify the exchange protocols used with these software application types, identify the detailed information requirements for the exchanges (exchange requirements), map these exchange requirements to the exchange protocols and document the gaps, and identify the external databases and libraries to be used, e.g. for climate data and others.

3 page 3/10 By applying the IDM to HESMOS, some shortcomings of the current IDM methodology and explanatory material were experienced, predominately that no easily understandable and comprehensive manual was available. To be able to explain the IDM process to the HESMOS team, a new HESMOS IDM chart was set up and an IDM workshop had been organized. 2 GENERAL HESMOS IDM APPROACH The general HESMOS workflow chart (Figure 1) had been developed to easily explain the various components. It greatly helped to achieve a common understanding among the partners, comprising architects, engineers, energy consultants, software developers, information specialists and researchers. It is recommended to include such, or similar, overviews also into the official IFM methodology. Within the next sections, each step in the overall methodology is explained and examples on how it has been approached and resolved in HESMOS are provided.

4 page 4/10 Figure 1: General process of Information Delivery Manual

5 page 5/ Define main interactions Following the standardized process first the exchanges were sorted. The whole building life cycle, with focus on private-public-partnership PPP contract scenarios, had been analysed, and the main interactions among the project participants had been identified, see Figure 2. Figure 2: Discovering Processes and Actors The main actors, defined by their roles, are symbolized by the swim lanes [A, B, C] in Figure 1 and defined as main rows in Figure 2. The main interactive processes that require exchanges are symbolized as small ellipses in Figure 1 and illustrated as rectangles and illustrative symbols in Figure 2. This task has been carried out for the as-is processes and for the to-be processes. All further developments on the IDM then concentrated on the to-be scenario. 2.2 Localize exchanges Based on the general previous step, a process map has been developed for each of the critical interactions. The selection had been made on the importance, impact and general scope and in effect it helps to stay focused. Figure 3 shows one of the process maps, developed using the Building Process Modelling Notation BPMN.

6 page 6/10 Each map is specific to a life-cycle phase identified in the previous step. The main swim lanes reflect the actors, and the exchanges are shown by the document icon placed in small interaction swim lanes within the BPMN diagram show in Figure 3. Some project specific colour coding had been added, the blue exchange describes the way BIM based data is utilized, the green exchanges show the additional external data sources. The overview diagram in Figure 1 symbolizes the exchanges as small red circles in separate interactive lanes. Figure 3: Identifying Exchanges 2.3 Sort and specify the exchanges The required exchanges are then further analyzed in terms of the information required by the follow-on processes. Hereby several exchanges having similar exchange requirements are combined into a common exchange requirement (ER). Figure 4 shows the main exchange scenarios in HESMOS:

7 page 7/10 life cycle Space Programming Arch + HVAC BIM-based Design Monitoring and Controlling BIM to Energy Energy Issue report Device Data Climate Data Material Data eebim eebim to Energy 1a 1b Link & Transform 2 3 Energy Results to Operational Costs BIM to Investment Costs BIM to Operational Costs (non energy related) Energy Simulation Energy Simulation Results Lifecycle costs Investment + Operational Cost Results Figure 4: Common exchange requirements identified in HESMOS In Figure 1 this is symbolized as several exchanges being small red circles resulting into one exchange requirement. Each of the exchange requirements are then specified in detail based on an interactive and iterative process between domain experts and information specialists. The exchange requirements are documented in an exchange requirement table (Figure 4) that had been defined as an improvement of the original table that forms part of ISO So far, a lowtech approach, using spreadsheets, is chosen to not create a technology barriers for the domain experts driving the process.

8 page 8/10 Figure 5: Creating Exchange Requirements 2.4 Map to exchange formats For each of the main exchange requirements identified in the previous step the target exchange format has been chosen, it includes IFC for the main exchanges, but also other formats, including BCF and specific XML based exchanges. See Figure 6 for the exchange formats selected. Based on the target exchange format, the mapping of the data requirements to its representation in the exchange format specification, such as the IFC schema specification, is developed. These Gaps, where no target definition in the exchange format yet exists, are identified, and extensions are proposed. When choosing IFC, those extensions are mainly realized by defining extra property sets.

9 page 9/10 life cycle Space Programming Arch + HVAC BIM-based Design Monitoring and Controlling BIM to Energy IFC2x3 CV2.0 Energy Issue report BCF Device Data XML Climate Data XML Meta data Material Data XML Meta data eebim eebim to Energy IFC2x3/IFC4 + link model 1a 1b Link & Transform 2 3 Energy Results to Operational Costs BIM to Investment Costs BIM to Operational Costs (non energy related) Energy Simulation Energy Simulation Results Lifecycle costs Investment + Operational Cost Results Figure 6: Deciding on exchange formats for common exchange scenarios The outcomes of this step are the Exchange Requirement Models (ERM) that are based on the Exchange Requirement (ER) tables with additional rows showing the mapping to the data exchange formats (Figure 7). Currently the work is done and documented by information modelling specialists using spreadsheets, but it is anticipated that proper tools that provide easy access to the available definitions within the chosen exchange format (such as the class/attribute and property set/property structure of IFC) could help to speed up this step in future. 2.5 Define model views At this point in the HESMOS project the methodology has been explained and the IDM has been completed. The creating of a model view definition is ongoing and it will be based on the latest developments within buildingsmart. The new mvdxml framework is being used in this process, and the ifcdoc tool, a software supporting the IFC documentation and MVD filtering process is going to be explored. In addition, the ViewEdit tool, that allows to extract automatically a valid MVD subschema out of the general IFC schema will be used. In Figure 1 this is symbolized by showing an MVD as a subset out of the total set of IFC. The work of defining model views is carried out by the information modelling specialists with consultation of the software engineers that will later implement it in actual software interfaces.

10 page 10/10 Figure 7: Extending to Exchange Requirements Models 3 EXPERIENCES FROM USING IDM IN HESMOS In general, the IDM methodology could have been applied successfully in HESMOS. The main obstacle at the beginning had been the lack of easy to understand literature that in particular would have informed the domain experts about the required steps. Therefore HESMOS developed a more easy to use guideline and tested it for the IDM development within the project. The Figure 1 was fund as instrumental to getting a basic and common understanding of the overall process. Now the HESMOS consortium intends to contribute it back to the international community in buildingsmart and ISO/TC184/SC13. Therefore the work on an improved methodology for IDM (ISO ) is going to be contributed back to the international standardization community, ISO/TC59/SC13 "Organization of information about construction works" and buildingsmart, and the actual IDM for energy enhanced BIM is going to be submitted to buildingsmart International for consideration as an international template for similar exchange scenarios.