## 3 Proposed Approach
### Prototype System Development  
Once the processes and information requirements were established, the aim was to test the processes on a system to automate/semi-automate the flow of information based on project-specific information requirements. To undertake this system development stage of the research, a Design Science (DS) approach was used. The DS methodology focuses on creating and evaluating IT artefacts intended to solve organisational problems. The stages within the methodology used in this research project were developed based on previous methodology variations and are summarised in Figure 4. The stages within the methodology were broken down with their corresponding actions and components that were to be developed [44; 45; 46]. The core methodology that was adopted for this research considered a combination of both a theoretical and applied approach to the DS methodology. This hybrid approach was used to bridge the gap between what was proposed by the standards (that were relatively new at the time) and the application of these new standards on real-life projects. Stage 1 focused on identifying and specifying the applied problem and was facilitated by the first two stages of this research (defined in Sections 3.1 and 3.2). This was carried out both by reviewing the existing literature and by receiving the expert feedback. The actions and components of this stage (Stage 1) were derived from the need to capture the complexity of the problem. As a result, a hybrid approach was used for this stage, where the researchers completed a comprehensive review of the state of the art while also applying the techniques to a real-life project to identify the main problems. \begin{table}
\begin{tabular}{c c c c} \hline
**Aspect** & **Evidence-Based** & **Workshops** & **Interviews** \\ \hline Objectivity & High & Medium-high & Medium-high \\ Richness & Medium & High & High \\ Time consumption & Low-medium & Medium & Medium \\ Immediately of feedback & Low & High & High \\ \hline \end{tabular}
\end{table} 
Table 1: Relative strengths and weaknesses of discovery methods [43]. Stage 2 of the research involved defining the objectives, which involved describing the system requirements and structuring information requirements. Then, finally, the processes that corresponded with the system and information requirements set out were defined. This stage was mainly shaped by referring to work carried out in the field of Information Systems to develop, deploy and improve artefacts within the field. Due to the need to constantly refine the process and improve the system, this stage went through multiple iterations, as defined in Figure 4.  
Stage 3 involved developing the system itself and getting the various components of the proposed system to work with each other. This involved using the endpoints of the BIM server in a process management system that contained and executed the defined processes. Once the system was developed, it was given to a project team working on an airport project in the UK to test it (Stage 4). This allowed them to provide their project-specific information requirements and then evaluate the system (Stage 5). Several iterations between Stages 3, 4, and 5 were made in collaboration with the project team before finalising the prototype system. Based on previous research carried out, the expected outcome of the first stage of the research was a graphical model along with non-graphical information and a breakdown of this information model. Based on these outcomes, a system was developed to tackle the bottleneck caused by handover (time savings) and the challenges faced by producing information that is not compatible with existing asset management systems (compatibility).