## 4 Results and Discussion
### Underlying Hindrance Groupings  
In this study, exploratory factor analysis (EFA) was conducted to obtain a manageable set of hindrance groupings. Such groupings should well represent the 21 critical hindrances to BIM implementation. The appropriateness of performing EFA with the data collected in this study was assessed. The Kaiser-Meyer-Olkin value was 0.911, suggesting that the critical hindrances had a high common variance. The value of the test statistic (chi-square) for Bartlett's sphericity was 1265.756, with a \(p\)-value of 0.000, indicating that sufficient correlations existed among the hindrances to proceed with EFA. Thus, the data were appropriate for EFA. The EFA process was terminated after meeting its widely-used threshold values: (1) 0.60 for cumulative percentage of variance (CPV), indicating that all the extracted hindrance groupings together should explain at least 60% of the variance of all the critical hindrances; (2) 0.50 for communalities of all the critical hindrances; and (3) \(\pm\)0.40 for factor loadings of all the hindrances to be significant [54; 55]. The communality of a critical hindrance presents the total amount of variance that this critical hindrance shares with the rest critical hindrances, and the factor loadings of a critical hindrance refer to the correlation between this hindrance and the hindrance groupings. EFA was conducted using the software IBM SPSS Statistics 20 and the results indicated a well-defined three-factor structure, as shown in Table 4. The CPV explained from the three extracted groupings was 64.070%. Additionally, all the factor loadings of the hindrances were above 0.40 and the communalities above 0.50, indicating a robust EFA. The hindrance groupings were named as \"lack of collaboration and model integration\", \"lack of continuous involvement and capabilities\", and \"lack of executive vision and training\", respectively. \begin{table}
\begin{tabular}{c c c c c} \hline \hline \multirow{2}{*}{**Code**} & \multirow{2}{*}{**Hindrances to BIM Implementation**} & \multirow{2}{*}{**Communality**} & \multicolumn{2}{c}{**Hindrance Grouping**} \\ \cline{3-5}  & & **1** & **2** & **3** \\ \hline \multicolumn{5}{c}{_Grouping 1: Lack of Collaboration and Model Integration (LCM)_} \\ \hline H34 & BIM model issues (such as ownership and management) & 0.757 & 0.948 & — \\ \hline H09 & Lack of sufficient evidence to warrant BIM use & 0.515 & 0.707 & — \\ \hline H36 & OSM requires design to be fixed early using BIM & 0.701 & 0.707 & — \\ \hline H45 & Difficulty in multi-discipline and construction-level integration & 0.512 & 0.657 & — \\ \hline H35 & Poor understanding of OSM process and its associated costs & 0.712 & 0.646 & — \\ \hline H46 & Technical needs for multiuser model access in multi-discipline integration & 0.587 & 0.545 & — \\ \hline H33 & Lack of standard contracts to deal with responsibility/risk assignment and BIM ownership & 0.727 & 0.524 & — \\ \hline H27 & Contractual relationships among stakeholders and need for new frameworks & 0.649 & 0.516 & — \\ \hline H28 & Traditional contracts protect individualism rather than best-for-project thinking & 0.574 & 0.463 & — \\ \hline H43 & Interoperability issues such as software selection and insufficient standards & 0.594 & 0.431 & — \\ \hline \multicolumn{5}{c}{_Grouping 2: Lack of Continuous Involvement and Capabilities (LCIC)_} \\ \hline H12 & Need for all key stakeholders to be on board to exchange information & 0.673 & — 0.780 & — \\ \hline H07 & Entrenchment in 2D drafting and unfamiliarity to use BIM & 0.712 & — 0.760 & — \\ \hline H14 & BIM operators lacking field knowledge & 0.676 & — 0.739 & — \\ \hline H42 & Costly investment in BIM hardware and software solutions & 0.630 & — 0.652 & — \\ \hline H32 & Assignment of responsibility/risk to constant updating for broadly accessible BIM information & 0.568 & — 0.600 & — \\ \hline H31 & Firms’ unwillingness to invest in training due to initial cost and productivity loss & 0.555 & — 0.557 & — \\ \hline \hline \end{tabular}
\end{table}