We are pleased to share this blog post from our Partner Autodesk.
Throughout
the course of any project requires the creation and sharing of untold data
during the lifecycle of the project. Unfortunately, a lot of teams have trouble
successfully managing and distributing this knowledge. Companies without a
framework will unfortunately suffer from bad management, resulting to errors,
rework, missed deadlines, cost overruns, bruised feelings and even litigation. Alternatively,
there are ways to resolve construction’s data overload, including creating
a standardised way of structuring data and collaboration, or more specifically,
by adopting a common data environment (CDE) with Autodesk
Construction Cloud.
The below
infographic explains what a common data environment is and why you should care:
Defining
a Common Data Environment
Autodesk
Construction Cloud brings together all your construction project data,
workflows, and teams into one common data environment. ‘The common data environment (CDE), is the single
source of information used to collect, manage and disseminate documentation,
the graphical model and non-graphical data for the whole project team,’ explains the BIM Wiki.
‘Creating this single source of information facilitates collaboration between
project team members and helps avoid duplication and mistakes.’
To put it
in another way, a common data environment is a digital hub where information
comes together as part of a typical building information modelling (BIM) workflow.
It was originally created and made well known as part of the UK BIM Level 2
standards. It now goes beyond BIM data and information, and it can incorporate
anything from project contracts, schedule, change orders and more.
Basically,
if it incorporates information produced during a project, it is accessible to
everyone who is granted permission. However, there are
certain significant obstacles that make it difficult for companies to develop a
CDE for their projects and businesses.
Current
Challenges in Today’s Construction Software Ecosystems
The thought
of a shared data environment is enticing; however, most construction teams
often find their working conditions to be less than optimal. Due to several
current obstacles, execution of projects without silos and with seamless
collaboration across specialties is harder to achieve. These include:
·
Technologies that don’t talk to each other: To achieve
the common good, different pieces of software must work together, however that
doesn't happen all too often on construction projects. While each piece of
software could have a different purpose or benefit, they don't matter much if
the information is not shared and integrated across platforms or channels.
·
No central hub: Without
a central hub, a project information becomes unreliable and unactionable when
software systems aren’t integrated. Without a single source of truth, information
can become muddled, opinions might start to outweigh facts, and a project would
end up going over budget and behind schedule.
·
Loss of data: Project information must be transmitted from team to team and from
phase to phase. These goes without carrying several risks, including the
potential of file incompatibility, loss of detail, and mistakes due to manual
processes. For these reasons, it is clear why more than 95% of project data captures
is being wasted.
- Inconsistent workflows and processes: Processes
and workflows are frequently decided upon by individual project teams and
stakeholders. As a result of the fact that different jobs usually require
different workloads and processes, the problem is made worse when systems
cannot communicate with one another. Misinformation, confusion, and
potential conflicts are the results of all of this.
- No standardisation: When
workflows and procedures are different, the standards by which they are
carried out and evaluated also vary. Leading to siloed standardisation,
which in turn means that some departments may deem a project to be
successful, while others may disagree.
· Disconnect with the company culture: Large-scale technology and data initiatives that lack direction
and buy-in from leadership frequently fail. A foundation for connected
construction must be established within a company’s culture to thrive,
including shared processes, workflows, standards, and data access.
· Lack of trust: Confusion,
duplication, and missing information can be frustrating, resulting to people
looking for someone to blame. This eventually leads to blaming the software
when there is no one to blame.
A common data environment, fortunately, goes a long way toward solving many of these challenges.
Why adopt a common
data environment?
Built by the leader
in design software, Autodesk
Construction Cloud brings all project data starting in design into
one common data environment. Including model and asset data that can be used
for design reviews, identify constructability problems and to jumpstart
building operations. There are many other compelling reasons to implement a
common data environment on construction projects including:
- Enhances collaboration: When utilised
properly, digital technologies may improve collaboration. This implies
that all project data and information need to flow into and be updated in
one centralised system. Leading to improved coordination and teamwork,
both internally and across teams as a result of this.
- Creates a single source of truth: Do not
underestimate the power of one single source of truth on a project.
One reliable place for team members to access real-time plans, changes and
data leads to better decision-making and insight across projects.
- Improves efficiency and quality: The
chance of input errors and data loss is reduced by eliminating the need to
manually recreate data, common data environments. This results in teams
having better access to information throughout the entire company.
- Lowers risk: CDE can lower risks with better
transparency and understanding of the full project landscape. This
eventually makes it possible for ongoing improvement and predictability.
- Strengthens security: Administrators
and IT specialists have better control over data and information with a CDE,
which creates more security.
Attributes of a Common Data Environment
It is
critical to know how to spot a common data environment. Some construction
companies believe they have a common data environment; however it can be
lacking important features that are needed to reap the benefits of CDE’s.
An
effective common data environment has the following attributes:
- Easy to Use: An essential component of a common data
environment is user experience. To be effective, it needs to be easy to
use.
- Accessible: Cloud-based implies that anyone who needs the information may
access it - whether they are in the office or out on a jobsite.
- Integrated: A CDE must work with current systems and processes. The objective
is to break down silos and boost overall collaboration.
- Standardised and Scalable: Businesses
of any scale should be able to standardise workflows and procedures with a
CDE.
- Secure: Data is never compromised in a well-functioning common data
environment. A CDE is secure for confidential business documents and
information.
Questions to Ask When Considering Implementing a CDE
It is
crucial to not just jump blindly into a new system. When implementing a common
data environment, it is important to consider the following:
·
How do you build company buy-in?: To ensure the success of your business and
projects, it is important to address this question before establishing a common
data environment. Consider areas and projects where you might execute trial
programmes to demonstrate their efficacy if getting staff buy-in seems
difficult. Remember that selecting a CDE that is simple to use will enhance the
technology's uptake.
· Where should you start the rollout?: It is challenging to deploy a new technology or system fully at once, however doing so can cause conflict. Therefore, it's crucial to consider whether this starts at the leadership level or the field level for your business. The greatest strategy is to take things one step at a time.
- How are you going to standardise?: A common data
environment cannot be introduced without standards. Which workflows and
processes will you introduce first and where can standardisation be most
useful and powerful? These questions are crucial to build a successful foundation
on CDE.
- Will there be an administrator to manage
this?: Start establishing roles within your business
before you consider creating a CDE.
- What does your roadmap look like?: Creating a CDE helps in laying the groundwork for the future. It's
important to address things like how you define success and what your
long-term goals are.
A common data environment for today and tomorrow
Make sure
that no data is overlooked. By enabling your team to optimise and use the
information when it matters most, a common data environment puts your business and
projects in the best possible position for success. Even better, reliable data
may accelerate project delivery by enabling future technologies like AI and
machine learning. To ensure that your approach to projects and collaboration stays
robust from design through operations, adopt a common data environment with Autodesk
Construction Cloud.
Want to learn more about how you can develop a CDE with Autodesk Construction Cloud to benefit your business? Please get in touch with us at Symetri by emailing us at info@symetri.co.uk or call us on 0345 370 1444.
