12.02.2013 Views

Industrialised, Integrated, Intelligent sustainable Construction - I3con

Industrialised, Integrated, Intelligent sustainable Construction - I3con

Industrialised, Integrated, Intelligent sustainable Construction - I3con

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SUSTAINABLE CONSTRUCTION HANDBOOK 2<br />

Partial Collaboration<br />

In contrast, partial collaboration implies that some members of the project team have the choice to<br />

adopt other methods against being compliant to BIM concepts and technologies, even though the<br />

project exemplifies contemporary design systems. This is most likely when a section of the industry<br />

adopts BIM and others who are not yet compliant take part in object-oriented CAD (o-o CAD) and<br />

allied applications. While the BIM-compliant party creates and shares digital data with other team<br />

members who are not BIM-compliant, the latter will struggle with some limitations, including<br />

organizational friction, inadequacies in technical processes and software compatibility problems<br />

(Dean and McClendon 2007; Zamanian and Pittman 1999). This phenomenon cannot but have<br />

particular implications for project development processes, and this has been exemplified in case<br />

studies that have reported on partial adoption (Aranda-Mena et al. 2008b). Figure 2 shows the<br />

information transfer process in a typical partial collaboration phenomenon.<br />

Figure 2. Typical partial collaboration phenomenon<br />

Non Collaboration<br />

Some authors (Baiden et al. 2003; Cheng 2003; Egbu et al. 2001; Gameson and Sher 2002) have used<br />

different case scenarios to demonstrate poor tolerance or non collaboration as a possibility in<br />

construction systems and their impacts on project delivery. Although, the authors reported the unique<br />

role of IT in promoting team spirit, it is impossible to rule out the fact that there are team players who<br />

are either yet to understand the role of IT and how to adopt what strategic tool and when, or have<br />

major challenges in adopting the ethos of team spirit that underlie integrated systems. Therefore,<br />

viewing non collaboration in technical and sociological contexts, there are two possibilities: (1) team<br />

members use entity-based CAD applications or analogue tools that have inconsequential or no<br />

relationship with integrated systems (Gross et al. 1998). (2) there are delibrate decisions by<br />

stakeholders to reject collaboration for strategic purposes (Parker and Skitmore 2005). These<br />

situations have far-reaching implications on project delivery; information flow will be marred by<br />

inconsistency, conflict, errors and delay in service delivery as team members are fragmented with<br />

technological bias against structured digital information management systems.<br />

Depending on circumstances and contexts of use, non collaboration implies that members are more<br />

likely to take deliberate actions that defy team spirit, not just because software and other system<br />

dynamics are not compatible, but because they are commited to their actions and outputs being in<br />

constant conflict with other members of the team. According to Kolarevic et al (2000), members of a<br />

project team who engage in tools that support or dedicated to fragmented processes will have tough<br />

challenges with the ethos of collaboration in integrated systems, if not practically impossible, unless<br />

they adopt some changes that re-position the systems with which they operate. Moreover, Gruneberg<br />

and Hughes (2006) suggested that it is difficult to enforce thorough collaboration in project teams,<br />

including with clients, unless all stakehoders are committed to the dynamics of effective risk<br />

allocation that can overcome self interests. The same study underpinned the relevance of gaming in<br />

construction collaboration, in the light of team players’ actions and the consequences of such actions.<br />

100<br />

BIM<br />

compliant<br />

Data exchange<br />

interface<br />

Non-BIM<br />

compliant

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!