No-one can deny that the world of design and build is rapidly changing evolving at an unprecedented rate. The emergence of new technologies and specialised tools can become a challenge when collaborating with different teams on complex projects, all of which drives the need for a Common Data Environment (CDE).
In this series of 5 posts we will explore:
A Common Data Environment – BIM 360 Team
Rapid iterations on ideas and concepts, frequent changes to project parameters, ever tightening timeframes and budgets, as well as multi-office and geo-located teams demands flexibility and scalability, along with immediate access to the most up-to-date information 24/7 – 365, agreed?
Teams need solutions that can make collaboration successful and seamless, that works for everyone, right from the start of the project.
Up to now, Building Information Modelling or BIM to date has mainly revolved around the actual design software used by architects and engineers to design and generate digital representations of a building or structure. The model represents both physical and functional characteristics and allows the designers and engineers to explore and predict how a building will function before it’s built. This is all fantastic stuff of course, and hopefully leads to the client taking ownership of a great performing building, delivered on-time and in-budget, but...
BIM poses the challenge that, due to its very nature, vast amounts of information are produced as well as giving way to an increase in the speed in which changes to the projects parameters take place. The second challenge is that the methods and tools we currently utilise in transferring all this critical information were not built are not designed for the world of design. Furthermore, we tend to make use of multiple data sharing ‘solutions’ e.g. hands up if you currently transfer design information using eMail, Drobox, SharePoint, OneDrive, iCloud and FTP sites?
Yes, I’m fully aware that this is a written document and thus I can’t see your hands up in the air (how many of you actually did raise a hand? Ha) but I would hazard a guess that the majority of you are either mentally raising them, or nodding in confirmation.
This results in having critical project data which is being transferred and held all over the place with no tracking or versioning. Not only that, but once a project stakeholder receives a piece of information, they have to download and view in either the software with in which it was created or one of the various viewing tools.
Here’s another question for you. Think back to a project review meeting you took part in six months ago. Could you access and collate all the various documents, meeting minutes, drawing and model mark-ups, RFI’s etc. from all the project stakeholders within the hour? End of the day? End of the week?
Allow me to introduce you to the Common Data Environment (CDE) with centralised project information, where you can:
What is this voodoo magic you speak of, I hear to shout? No magic. Simply Autodesk BIM 360 Team (part of the Autodesk BIM 360 family) : everyday collaboration for design teams with a simple, easy-to-use UI.
Like the sound of it? Ask us today for a free trial and experience a new age on team collaboration.
Should your company purchase a subscription of BIM 360 Team, a series of steps will have to be followed by your Autodesk Subscription Manager to assign a BIM 360 Team Hub to the subscription contract. These steps will be covered in the next blog post “BIM 360 Team: Contract assignment and Hub setup workflow” which is available now.
If you have any enquiries, pease send us a message: