Common Data environments or CDEs have become popular with engineering companies in the last few years, but choosing the right CDE software for your project can be daunting. In this post, I will lay out the top three things to keep in mind while selecting a CDE software solution.
First of all, a CDE solution must check all the boxes when it comes to functionality. What do I mean by that mean? I mean, the CDE solution must contain all the functionality YOU require in YOUR project.
Not all CDEs are created equal. Most CDE software comes with certain basic functionalities, and it is tempting to just assume those basic functionalities will be sufficient for your needs so go for one that seems ‘good enough’. But I would argue that with so many options available and constantly improving technology tools why settle for good enough? Why not pick a solution that gives you exactly what you need?
But what features and functionality should you look for in your CDE? This can be a difficult question to answer beforehand, so to figure this out, try asking yourself and your team these questions: “Is this CDE solution compatible with the file formats we use including native files?”, “Does it provide configurable access rights ie can it cater to different levels of stakeholders without impacting either our efficiency or our security?”. “Does it have plugins that will let us connect smoothly with our other software applications?” Also consider factors like the ease of access; ideally your CDE should be accessible from a variety of devices (even without a network connection) and should have workflows built-in to manage quality by ensuring everybody follows the protocols for compliance.
The more advanced CDE solution will have dashboards with analytics and these will be a big advantage during your project execution, so keep that in mind as well when evaluating a CDE’s functionality.
The second point to consider: is the CDE easy to use? Will everybody involved in the project be able to learn and use it in a reasonable amount of time?
Ease of Use is an underrated parameter when it comes to project management software even though it makes a huge difference to outcomes.
The fact is, if people aren’t comfortable using software, they just won’t use it, or they’ll use it inefficiently. And as the saying goes, a chain is only as strong as its weakest link. So you need to make ease-of-use a priority when selecting a common data environment. Consider factors like whether the software can be used by someone not familiar with BIM, and whether adds-ons and plug-ins can be installed quickly and easily without additional support. Consider whether the user interface is intuitive enough to cater to all your teams and third parties without needing to rely on extensive (and potentially expensive) recurrent training sessions and other handholding. If your project involves multiple offices across multiple time zones and cultures, it would be wise to consider how well the CDE would align with such a team as well.
Thirdly, do keep in mind the many options available in CDE Pricing and Service. Many companies start with this but that would be a mistake because just as the right CDE software can benefit your project outcome the wrong one can affect it negatively and with significant damage to the profit margin.
Here I will say that in today’s market landscape, the exact feature set you require and the number of users will be key factors in determining the price, so it is good to freeze those factors before you begin checking out pricing options. The good news is that these days there are several ways to purchase – monthly vs yearly pricing, subscription models vs outright purchase, pay per user vs pay per project, and so on. Also keep in mind that almost all these aspects can usually be negotiated, depending on the software provider.
You will also want to check out value-added services like training, whether it comes bundled or is a separate costed item, whether it is per person or project, and also whether there are other ways your team can get support and help if needed (which can be a significant factor if dealing with offshore teams). Also consider how scalable your CDE is, and how it will handle new stakeholders being added during the project, as sometimes happens, and how it will handle users being moved from one location to another.
After all this don’t forget to check out the type of support provided in your Common Data Environment platform or solution; is it email? A ticketing system, a hotline? Will there be a dedicated support manager assigned to you from the provider? Sorting out these support-related issues can be crucial to how effective your CDE is in real life.
Know More: How to get started with common data environment for BIM