What you can expect when using Warboard

By Kong Hoang, Information Manager, BIM Technologies

My first experience of Warboard was in the summer of 2016 while working on a high-end office scheme in Central London. The design team were working through finalising the concept, so there was still a lot moving around. Once the design had settled, and the team were gearing up towards planning and detailed design, it seemed an appropriate time in the programme to start looking at clash coordination and issue management.

The project was typical of many traditionally coordinated schemes in that a lot of the coordination was happening via snapshots and mark-ups in emails, and issues were not being tracked and resolved efficiently. The team needed a solution to the problem of issue tracking through the clash coordination process.

Enter BIM Technologies! BIM Technologies were brought onboard by the client to manage clash coordination using Navisworks and introduced Warboard to the team in the first BIM meeting.

It certainly raised a few eyebrows amongst members of the team that were used to coordinating in the usual way, however, as the project progressed and it became apparent that issues were being tracked and closed out much more efficiently than by traditional methods, the team came to see the true value of the workflow. The project was handed over at stage 5 to the construction team with all major design issues cleared from the federated model. This was invaluable in terms of reducing RFI’s, risk, and time which might have been wasted resolving the same clashes on-site.

Now don’t get me wrong, Navisworks is very good at finding issues in BIM models, but not so good at representing the information in a format that is accessible to the entire design team. Some design team members may not have access to Navisworks or only have the capacity to review and comment on 2D CAD and PDFs. What I liked about Warboard was that it empowered the team to take control of the design issues that come out of the clash report through an inclusive and collaborative on-line format.

Due to its cloud-based platform, Warboard is able to collate all of the latest issues in a centralised location within its online project repository, and all members of the team, including the client, can be invited to the project to comment, and crucially, close out issues raised in the report.

Images of the clashes are clearly represented along with their locations. Users can add their own user profiles and descriptions of their roles within the team, and the progress of coordination is graphically tracked and attractively presented on the project dashboard in the form of timeline graphs and charts, which is great for reporting on progress to the client team. The interface is intuitive too and easy to navigate, and the software works with BCF files and issues can also be exported and viewed in Revit and Solibri.

Clash Reports can be easily exported to a smart looking PDF report and issued alongside the .nwd file. Report templates are also customisable to suit office standards. There is even a handy calendar function that can notify the team of the next coordination meeting or model issue.

Because it is web-based, issues can be taken to site and viewed on mobile or tablet devices, or anywhere that there is a viable wi-fi connection making it easy to review and report on model issues on the go.

All in all, the simplicity of use means that design teams are able to start using the software immediately with little or no training and reap the benefits of a faster, more efficient method of issue resolution leading to a more coordinated design with quantifiably better outcomes for site teams, and ultimately, the client.

Now that I’m part of the BIM Technologies team, I use Warbaord on a daily basis, and my clients find it effective and seamless, which means reporting is standardised and the whole project team are kept in the loop and know exactly where we are and what is needed at each stage.

The post What you can expect when using Warboard appeared first on BIMcrunch.

Original Article