Research Report: How Design Teams Manage Product Data
Research Report: How Design Teams Manage Product Data
com
Research Report:
How Design Teams
Manage Product Data
Table of Contents
1. Executive summary
2. Which design teams use formal PDM systems?
3. What do design teams value in a PDM system?
4. Data management for seven design processes
5. Survey demographics
2
Executive Summary
In May we surveyed 151 product development professionals about how
they manage product data. Our analysis focused on the types of systems
used, how they were used, and the correlation between system types
and common product design failures.
The results of this analysis should provide design and development teams
information to help them benchmark their results relative to the industry.
Here are a few selected insights that we gleaned from the survey data:
• Approximately half (49%) of all respondents do not have a formal
PDM/PLM system.
• Design teams spend a surprising number of hours each week looking for
files and on other non-productive activities.
• Respondents were generally disappointed with their team’s performance
on seven measures of design process control, from sharing data, to ECOs,
to avoiding redesigning the same part.
• Respondents consider it extremely important to have an easy connection
between their CAD systems and their PDM systems.
The data supporting these findings are presented in charts and graphics in
the following pages. I would like to thank the survey participants for
generously sharing their insights.
We hope you find this research useful.
Thanks,
John Hayes
ENGINEERING.com
3
Which design teams use
formal data management
systems?
Almost half of all product design teams do
not have a formal PDM system
There are numerous ways a product design and development team can
track product data. We asked respondents to select from a list of several
possible ways and then recoded that data into various levels of
sophistication.
PLM
13%
49%
38%
PDM No Formal
System
Q: “What type of system does your company primarily use to manage product
data?”
5
Unsurprisingly, larger teams tend to have
more formal data management systems
We asked respondents how many people in their company needed access
to product development data and compared that to the level of
sophistication of their data management systems. What we found isn’t
surprising – the more people who need access, the more sophisticated the
system that is in place to manage the data.
45%
31%
% of Respondents Using a
37% 46% 59% 63%
Formal System
Q: “How many locations in your company need access to product data?” cross
tabulated with “What type of system does your company primarily use to
7
manage product data?” – Percent using formal PDM system shown.
Certain industries, such as aerospace &
defense, have a higher level of PDM
adoption
Shared folders are the most popular product data management technology
amongst respondents, particularly in the consumer products & electronics
and engineering design services industries. Formal product systems are the
most popular amongst general manufacturing and aerospace & defense
manufacturers.
64% 66%
56%
52%
36% 38%
33% 34%
20%
11% 10%
Q: “Which industry sector does your company primarily serve?” cross tabulated
with “What type of system does your company primarily use to manage product
8
data?”
What do design teams
value in a PDM system?
Easy connection to CAD systems is
important or very important to 76% of
design teams
We asked respondents about certain common features of data
management systems. Of all the features mentioned, “easy connectivity to
your primary CAD system” received one of the highest rankings, indicating
that respondents felt that this was a very important attribute.
14%
10%
71%
18%
11%
Q: “How important is the attribute ‘allows easy, secure external data sharing’ of a
data management system to your team?”
11
Respondents rated having a data
management system that is easily
adaptable to their workflows as important
or very important
Although there are general best practices for managing product data, every
company tends to evolve its own workflows to support its unique
processes. Accordingly, 71% of respondents said that it is important or very
important that their data management system be customizable to fit their
workflows without having to bring in an external consultant.
22%
7%
% of Respondents
whose current PDM
Feature Degree of Importance
satisfactorily has the
feature
Easy connection to
CAD systems 76% 69%
Pretty Bad
Rotten So-so
11%
Spectacular 32%
12%
42%
Pretty Good
2.2
Hours Creating a new model because it is
faster than finding an existing one
2.6
8.9 Hours
Hours Reworking a model due to using the
wrong version
2.2
Hours
Looking for a file
1.9
Hours
Q: “How many hours per week does a typical design engineer in your company
spend …?”
15
As product teams grow in size, an
“efficiency gap” emerges between those
teams with a formal data management
system and those without.
Formal product data management systems tend to be more valuable to
larger teams. The example below shows that the average time spent
looking for a file increases with the number of team members, unless
technology and processes are implemented to save that time.
3
Δ = 1.94 hours
2.5
2
Formal system
1.5
0.5
0
1-5 6 - 10 11 - 20 21-50 >50
Number of Team Members
Q: “How many hours per week does a typical design engineer in your company
spend looking for a file?” cross tabulated with “How many people need access to
product data?” and aggregated by, “What type of system does your company
primarily use to manage product data? 16
Data management for
seven design processes
Survey respondents gave their companies
failing grades when asked about sharing
product design data
We asked respondents about their success with several design processes
and issues. Almost half of design teams reported that their teams were
either “Rotten, Pretty Bad or So-so” at sharing product data for the
purposes set out below.
62% 62%
57%
47% 44% 45%
42% 51%
avoiding designing
managing change
the same part
orders
multiple times
57% 55%
implementing /
bringing new users
documenting
up to full fluency on
product
accessing product
development
data
workflows
63%
58%
52% 50%
46%
40% 40% 40%
1-2
>250
17% 7% 3-5
14%
17% 17%
51 - 250
16% 12%
5 - 10
20 - 51
11 - 20
N = 151
23
Job roles of respondents
Survey respondents spanned all job roles you would expect on a design
team, from technician to C Level executives, with the largest pool
representing engineers and senior engineers.
N = 151
24
Formal systems used
For those respondents who reported using a formal data management
system, SOLIDWORKS PDM was the most common, followed by Autodesk
Vault, Autodesk PLM360, PTC Windchill and Siemens Teamcenter.
Windchill
14% SOLIDWORKS PDM
29%
Teamcenter
13%
Omnify
1%
ENOVIA
6%
Autodesk
PLM360
Autodesk Vault 14%
23%
25
Conclusions
Many product teams appear to be dissatisfied with their ability to manage
their design processes.
They report that the average design team member spends almost 9 hours
per week on non-productive activities. Almost half of participants said that
their teams were no better than “so-so” at achieving product launch dates.
As often as not, they gave their teams failing grades on core design
processes.
Thank you for reading. If you found this report useful, please share it with
your colleagues.
Thanks,
John Hayes
ENGINEERING.com
26