Common benefits of using model based collaboration project workflows
Improved systematic and visually demonstrative project group communication.
Enables effective co-ordination of de-centralized project workgroups.
Effective use of co-ordinated model on-site for operation, inspection and maintenance throughout project life-cycle.
Substantial reductions in clashes and re-work.
Reduces wasted materials and delays in time schedule.
Visual review model can be used easily and efficiently by all project stake-holders.
Improved control of the project time-schedule and budget.
The Engineering Phase
Model based coordination is performed using a systematic working process.
In terms of work process, the project co-ordinator has a very important role being one of the design engineers, a project manager or his representative, often in the primary design organization. This role is essential to the process.
His duty is to perform aggregation of the CAD-models from different disciplines including any other required data ( e.g. point cloud data), to review the design using real time navigation and by using clash detection, creating saved views, comments, red-lining, and mark-ups and then publishing the model to one single .nwd file.
Engineering team members
The aggregated model is placed to on the project server, which enables access to all engineering teams members to the project model with all relevant views and errors that needs to be corrected.
Selection of a model tag or viewpoint takes the user to appropriate clash location.
Each team member then makes the necessary changes to the native CAD files using the appropriate CAD tools. Team members can also add red-lining and mark-ups to the model which will be saved as their own .nwf files on the project server.
The Project Co-ordinator then merges all the saved .nwf files to the original .nwf file which will then automatically include all updated data from CAD-models that have been modified and corrected as the .nwf file includes links to the original CAD files.
Then the saved clash detection process will be run again to check the modified project model with all red-lining and mark-ups updated.
Finally the Project Co-ordinator releases a new revision of the published .nwd file which includes the updated and corrected clashes with all team member comments.
The on-going process
It is essential that this working method is an on-going process, that continues into the engineering phase from investment planning into detailed engineering and often into on-site operations and maintenance.
In most projects the new revised .nwd is published daily or overnight as regular updates are essential.
This working process is applied slightly differently depending on the size of a project, but using the same principals. In large scale projects each discipline may have it’s own project responsible co-ordinator, who primarily manages models inside his own discipline and ultimately all disciplines will be inspected relative to each other using the same principles.