DEPT OF PDM, PG STUDIES, VTU

CHAPTER-1
PRODUCT DATA MANAGEMENT
1.1 AIM
The aim of this unit is to provide a clear understanding of how product data management
systems help people manage both product data and the product development process.
1.2 OBJECTIVES
By the end of this unit you should;
Understand why it is important to manage data
Understand the main concepts and benefits of product data management
Understand the importance of product data management within the product development
process
Understand how product data management aids concurrent engineering
1.3 RECOMMENDED READING
CIM data, Prod!t Data Ma"a#$%$"t: The Definition An introduction to oncepts!
Benefits and Terminology! http:""www.#$data.com! %eptember &''(.
I%&'$%$"t("# a"d I"t$#rat("# Prod!t Data Ma"a#$%$"t a"d So)t*ar$ Co")(#rat(o"
Ma"a#$%$"t ) *& ) #vica m+ovic Ulf As+lund ) Annita ,ersson Dahl-vist ) Archtech
.ouse ,ublishers.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
1.- INTRODUCTION
The successful development of products has become a comple/ process involving
contributions from a range of different disciplines. 0arely is one individual responsible for
the conception! design! development! manufacture and mar+eting of a new product. Today!
the inherent comple/ity of products! their mar+ets and therefore the processes through which
they are developed! dictates that a number of different people! each with their own roles wor+
together to create the product. %cientists! designers! engineers and mar+eters form the core of
new product development and they are in turn supported by management! purchasing! finance
and -uality personnel.
,roduct Data $anagement 1,D$2 is a tool that helps people manage both product data and
the product development process. ,D$ systems +eep trac+ of the masses of data and
information re-uired to design! manufacture or build! and then support and maintain
products. ,D$ can be used effectively in a multitude of industries e.g. petrochemical!
aerospace! transport! pharmaceutical! automobile etc.
,D$ systems are essential for the integration of product development because they can
control official versions of product data and documents to be shared across wor+groups in the
product development cycle. An optimal use of the system from the view of the team
members would be to store pro3ect data along with the product data! enabling the creation of
an integrated pro3ect and product data model. A model containing all pro3ect and product
documentation will give the pro3ect leader as well as the team members and management a
good overview of the pro3ect status at early stages of the product development process. 4ith
an improved overview! problem areas can be detected at an earlier stage and appropriate
measurements can be ta+en before the entire product development process gets delayed.
#n order to improve communication within the product development process many companies
have introduced ,roduct Data $anagement 1,D$2 systems. ,D$ systems are e/tremely
important for the integration of product development because they provide official versions
of product data and documents to be shared across wor+groups in the product development
cycle. They typically have capabilities! which include vaults! revision control! management!
enhanced security and integration with other applications such as omputer Aided Design
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
1AD2! omputer Aided 5ngineering 1A52! omputer Aided ,rocess ,lanning 1A,,2!
$aterials 0e-uirements ,lanning 1$0,2! 6roup Technology! etc.
The performance of these applications has been limited since the systems act as automated
islands. The systems often form a very good tool for their specific tas+! but no integration
between different systems! in the spirit of integrated product development! has been possible
due to a wea+ e/change of information. The introduction of ,roduct Data $anagement has
given the possibility of an efficient integrated management of product data.
#n principle! all things manufactured or built are products. A product can be a bridge! a car! a
watch! a telephone! a sweatshirt anything that has been built or manufactured. Different types
of services can also be considered products. #n their own way! software applications such as
word processors! operating systems! and computer games are also products. %oftware is
interesting in this conte/t because an increasing number of products previously considered to
be hardware now incorporate software. 5/amples of such are mobile phones! cars! washing
machines! and television sets. 5ven more! for such products! the cost of developing the
software component is a considerable proportion of the total development cost and is
increasing. 7or 5/ample the below figure shows the comparison of hardware and software
development costs in industrial robot industry.
F(# 1.1 So)t*ar$ a"d Hard*ar$ d$.$'o&%$"t !o/t/ (" I"d/tr(a' ro0ot/
7rom the above fig it is clear that the development of cost of software in industrial robot
industry was one third of the total development cost and this trend is e/pected to continue.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
Two things are crucial for proper functioning of product
$anagement of its comple/ity and
,rovision of support during its entire life
The more comple/ the product is! the more comple/ are the procedures for its
development and support during its life.
1.1 PRODUCT 2IFE C+C2E
$any products have a long life. #n order to study the entire life of a product! we must
understand all of the processes involved in the product8s development and operation! and all
activities of the people involved in the processes. The mechanism used to structure these
processes and to identify the ma3or activities is called a product life cycle 3P2C4 model. A
life cycle is divided into several life cycle phases. 5ach phase is characteri9ed not only by its
inputs and final results! but also by its activities! support provided! the roles of the different
people involved in the activities! and the different technologies and techni-ues used in them.
Basically we have si/ generic phases.
F(# 1.2 G$"$r(! P2C P5a/$/
B/("$// Id$a
This phase begins with the perception for new product.
#t helps in assessing mar+et : technology with the identification of +ey
re-uirements of product.
#n this phase all the information is collected about the product to chec+ its
feasibility.
5/. ;ew radar has to be built for the ne/t generation of aircraft and the space
available is one third of that occupied by today8s smallest possible radar. The
feasibility study concludes that it can be done! assuming current trends such
as AD : A%# 1Application specific integrated circuit2 technology.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
R$6(r$%$"t/ %a"a#$%$"t
This phase focuses on further identification of re-uirements! analysis :
specifications.
The result of this phase is a product re-uirements specification.
D$.$'o&%$"t
This phase includes design and implementation activities.
A typical hardware product includes prototypes and all the material
needed for product information.
7or software product the development phase will compete with the
product itself.
The result from this phase is the implementation of all of the artifacts
1Tangible products2 needed for production.
Prod!t(o"
#t is also called as manufacturing phase and is different for software and
hardware products.
#n case of pure software products the phase is automated to a high degree
and very low costs.
7or a product with hardware elements! this is most demanding and most
costly of all phases. Therefore! for hardware products! much effort is
invested in coping with production re-uirements and in +eeping
production costs low.
O&$rat(o" a"d Ma("t$"a"!$
#n this phase the product is used by consumers and specific to this phase.
To ensure correct operation the product re-uires continuous support and
maintenance.
,roducts having shorter life time re-uire no maintenance.
,roducts such as 3ewelry have long life time but re-uire almost no
maintenance.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
<ther products re-uire maintenance for years 5/ .ouses : Bridges.
D(/&o/a'
This is the final phase of the life cycle of product.
4hile disposal different aspects related not to the product but to its
surroundings must be ta+en into consideration.
5/amples of disposal of products are the delivery of a car to 3un+yard where
there is dis)assembly! recovery of recyclable materials! and disposal of
nonrecyclables.
Another e/ample is management of nuclear waste.
1.7 THE DEVE2OPMENT PHASE

6enerally ,= models can be implemented in different ways. .ere we
study development phase for different types of products: pure software products and pure
hardware products.
There are si/ steps of pure hardware development
F(# 1.3 So)t*ar$ a"d 5ard*ar$ d$.$'o&%$"t &ro!$//$/
Development phase is preceded by the detailed requirements management. Although the
re-uirements management phase can be treated separately and independently of how the
product is reali9ed 1e.g.! in hardware or software2! a detailed re-uirement solicitation and
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
specification is closely connected to the development! in particular to t5$ conceptual
development in which the product concepts are generated. At the system-level design, the
architecture of the product is decided! including the identification of subsystems and
components. The components are further designed during the detailed design. Testing and
refinement includes the building of product prototypes to test both the product and the
production system. During the production ramp up! the production system is used for serial
production of the product! beginning at a low rate but then increasing to full production.
The software development process consists of similar phases such as
re-uirements analysis! design 1overall and detailed2! implementation! integration and test! and
finally release. The detailed requirements analysis phase is completed with a re-uirements
specification. This specification is an input to the system design that consists of two steps: the
overall design where the system architecture is designed and the components and their
interfaces are identified! and the detailed design in which the component implementations are
specified. #n the implementation phase! the developers follow the design documentation and
implement the system in the form of algorithms and data structures specified and written in
different programming languages. #f it is possible! components are tested independently. #n
the integration and system test phase! the integrators build the system from the components.
The system is then ready for the system test. The final development phase in this model is the
release management! in which the product is pac+aged in an appropriate form for delivery
and installation at the customer8s premises.
1.8 COMP2E9IT+ IN PRODUCT DEVE2OPMENT
,roducts are becoming increasingly sophisticated and comple/ 1e.g.! the incorporation of
software in different types of products improves the functionality of the products
significantly! but at the cost of increased comple/ity and decrease in robustness2. This is
because software does not follow physical laws! and conse-uently its behavior is less
predictable. omple/ity ma+es it harder! and more e/pensive! to maintain high -uality and is
conse-uently most important to master. There are several parameters that influence
comple/ity:
Complex functionality:
,roducts being developed today have comple/ functionality such as cars!
industrial control systems! computers etc.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
Apart from comple/ functions the products must fulfill large number of
re-uirements 1such as reliability! robustness! availability! testability!
traceability! modifiability etc2 to ma+e the product more usable!
adaptable and attractive.
A large number of re-uirements often incompatible lead to many
difficulties in development process.
Complex structure:
#n order to solve comple/ problems a large problem is divided into many
small problems.
Different principles and methods can be used such as Top)down structural
refinement! ob3ect)oriented approach! data flow analysis! unified modeling
: component based approach.
.ence transforming large problem into small problem leads to comple/ity
between the parts. hanges or replacement in one component can have
significant impact on other components.
Complex operational behavior:
The interaction between a product and its consumers can be comple/
which becomes difficult to predict the behavior of product in its operation.
ustomers want to use the products in particular way or for a particular
purpose which re-uires redesign of the product! which further re-uires
e/tensive service! maintenance or in some cases new development of the
product.
Product and component versions and variants:
A product consists of many components and each component e/ists in
many versions.
As shown in fig below a product consists of three components and each
component e/ists in two versions! by combining all versions of the
components results in eight different versions of the product.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
F(# 1.- Co%&o"$"t .$r/(o"/ a"d &rod!t .$r/(o"/
$athematically! the number of combinations grows n)powered with the
number of components and versions. 7or n components in k versions! we get
k
n
possible versions of the product.
$any of these versions are valid but in some cases the particular combinations
of component versions are impermissible 1 versions are not compatible2.
Complex development process:
4hen the products are comple/! then development process tends to be
comple/.
$any people with different roles are involved in development process!
should be provided access to accurate information.
ommunication between people in a group becomes comple/ when group
grows.
4hen two people communicate directly with each other! there is one
communication link between them; when they are three! there are three lin+s!
and for four people! the number of lin+s grows to si/.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU
F(# 1.1 D(r$!t r$'at(o"/5(&/ 0$t*$$" #ro& %$%0$r/
7or a group of n people! there are n1n>&2"* direct communications lin+s.
7or larger groups! and for processes active under longer periods! there must
e/ist well)defined and efficient ways to access information.
Distributed development and production:

Both development and production may be geographically distributed.
7or software! the developers are often dispersed to several sites! often in
different countries! while developing the same system. The production of
hardware is often outsourced 1i.e.! produced by another company2.
Need for maintenance:
Demand for maintenance and further development of a product means we
must +eep trac+ of the status of all products released.
Products containing both hardare ! softare components:
4hen a product consists of both hardware : software! it is necessary to
understand the problems of hardware : software development! production
: maintenance process.
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT
DEPT OF PDM, PG STUDIES, VTU

ASSIGNMENT :UESTIONS
&. Describe how to analy9e the development phase for two different types of
products.
*. .ow product data management is supporting the product life cycle.
?. 5/plain the principles of product data management with e/amples.
@. Describe how ,= is associated with ,D$ with bloc+ diagram.
A. 5/plain the supporting activities in product development process.
B. Discuss the need of collaboration in product data management with e/amples.
(. Describe briefly the following
a. ,roduct life cycle management
b. 6eneric products
c. #mportance of ,D$
d. Traceability in ,D$ systems
B+ PRASAD RAI,AR, ASSISTANT PROFESSOR
PDM DEPARTMENT