## 2 Methodology for Defining a Workflow
### Step 2: Using of MVD for Structuring BIM Requirements  
The MVD standard was applied after the implementation of the IDM standard, as presented on the right of Figure 1. IDM was used to model the processes and the high-level information exchange requirements, as explained in Section 2.2. On top of that, the MVD approach was essentially considered to determine a subset of the IFC schema that was needed to fulfill the identified EIR.  
After finalizing the definition of the high-level EIR, the current step foresaw the detailing and structuring of the collected information, for instance with the help of the BIMQ tool [71] as displayed in Figure 7. BIMQ follows the IDM/MVD methodology from buildingSMART and thus brings all pieces together, namely the actors, phases, use cases, exchange requirements (broken down into object and properties) and, last but not least, its representation in the OpenBIM IFC standard or, if needed, to other data formats. Figure 7 shows, for instance, the definition of Key Performance Indicators (KPIs) [72], a special type of property that is used to compare and evaluate renovation scenarios. Those KPIs include a mapping definition of IFC, in that case, to user-defined properties, and are then assigned to elements and domain models representing the EIR, as discussed with domain or discipline experts. This essentially means to extract detailed and checkable information from the EIR-tables of the domain experts, who normally do not know the details about how to encode such requirements in a data structure such as IFC. This step follows simple rules and differentiates four main categories:  
Figure 6: BPMN data object.  
* Discipline models such as an architectural model, structural model, plumbing model, or electrical model. Such models group a set of information that is typically linked to a specific type of actor who is responsible for delivering the data.
* Element types such as a wall, slab, window, boiler, etc., typically with a position and geometrical representation. Besides being classified according to well-known structures, they can be characterized by further parameters carrying important design information, properties, and geometrical detailing.
* Properties of elements such as name, fire rating, thermal transmittance, etc. They represent a piece of information that is typically defined by a single-value property but could also play a more complex part in the data structure such as a relationship, a time-series, or other structured data.
* Geometry of elements, which is basically a description of the expected level of geometrical detail. This should include information such as that specified in CEN 17412 (LOIN standard) [73], such as dimensionality, appearance, parametric behavior, etc. These data will help to conduct further evaluations, such as clash detection, visualization, calculation of quantities, etc.
* Accordingly, such specifications require a joint effort between domain experts and technical experts who know all details about a particular data format such as IFC, gbXML, or others that are of interest to be used for requested data exchange.  
In summary, the IDM and MVD/IFC View Definition were adopted to map the information requirements to the relevant IFC schema elements targeted at streamlining the renovation process. This exercise enables the codification of these requirements into  
Figure 7: Screenshot from BIMQ showing the structuring and detailing of EIRs.  
the software tools that will realize the information exchange, enforcing the BIM technical interoperability perspective.