Product data management PDM http:www'inf'vtt'fipdftiedotteet2000T2042'pdf

1
Product data management (PDM)(http//www.inf.vtt
.fi/pdf/tiedotteet/2000/T2042.pdf)
--------------------------------------------------
------------ Jukka Kääriäinen Tel.
358 8 551 2191 VTT Electronics
Mobile [phone] P.O.Box 1100
Email Jukka.Kaariainen_at_vtt.fi FIN-90571
Oulu, Finland -------- VTT - Technical Research
Centre of Finland ----------
2
Embedded product data management - research
group -

• RM
• tools and technology
• for requirements
• management

http//www.vtt.fi/ele/research/soh/tut/index.htm
3
PDM / SCM lectures content
3.3.2003
Terminology
Background/benefits
Design data management requirements
Traditional PDM functionality
10.3.2003
Management of SW product
SCM system functionality
SCM vs. PDM

Unified management
SCM/PDM integration
4
Terminology
5
Terminology

• Product data management (PDM)
• Product Data Management system is used within an
  enterprise to organise, access and control all
  data related to its products, and manage the
  lifecycle of those products
• Product data
• Set of data which defines a product (include
  requirement specs, designs, source code,
  CAD-files, instructions )
• PDM can be partly automated and also contain
  traditional non-computer systems
• This presentation emphasises PDM as management
  system, but it is worth to notice that it
  requires also product data management
  practices/processes

6
Terminology

• Product Data Management synonyms
• Engineering Document Management (EDM),
• Product Information Management (PIM),
• Technical Data Management,
• Technical Document Management (TDM),
• Technical Information Management (TIM).
• Terminology unstable

7
Some related terms

• CAD Computer Aided Design
• MCAD Mechanical Computer Aided Design
• Computer-based tools for designing and
  analysing mechanical products and components.
• ECAD Electronic Computer Aided Design
• The use of computer applications to design and
  analyse electronic and electrical products,
  parts, and components.
• ERP systems Enterprise Resource Planning
  -systems Control a companys production chains
  operations e.g. manufacturing, purchase,
  materials management, etc.

8
Literature / further information

• CimData (www.cimdata.com)
• The Product Data Management Information Center
  (PDMIC)(www.pdmic.com)
• Peltonen, Martio Sulonen PDM - Tuotetiedon
  hallinta, 2002
• Kääriäinen, Savolainen, Taramaa Leppälä
  Product Data Management (PDM). Design, exchange
  and integration viewpoints, 2000, VTT Research
  Notes
• Halttunen Hokkanen Tuotetiedonhallinta -
  Taustaa ja ratkaisuvaihtoehtoja, 1995, VTT
  Tiedotteita

9
Background
10
Challenges for PDM

• Global design several sites, sub-contracting,
  cooperation
• Products are getting more complex (also several
  design disciplines (e.g. SW, electronics,))
• Product customisation
• Competition requires faster time-to-market
• Shortened product life cycles
• Competition requires lower costs and better
  quality
• Huge amount of data in various formats
  (electronic, paper,) in different systems

gt these issues create challenges for companys
PDM activities
11
Levels of complex product (example)(Buckley
(1996))

• Parts
• Subassemblies
• Assemblies
• Units
• Groups
• Sets
• Subsystems
• Systems

12
How PDM can support product development?
(examples)

• Information sharing in global environment
• information is managed by one system
• searching data gt data instantly available when
  needed
• user does not have to know where data resides
  (PDM hides location)
• Data integrity and security
• Implementing concurrent engineering practices
• Better process control (workflow definition,
  execution, traceability, history, )
• Better system integration (PDM as integrator
  between e.g. ERP, CAD, MRP (Material Resource
  Planning) systems)

13
PDM benefits examples (CimData)

• Direct cost benefits
• reduced time and cost to execute changes
• users can concentrate to their primary functions
  (not information search, etc)
• Time-to-market benefits
• getting product to the market in a shorter period
  of time (e.g. shorter design-to-manufacturing
  cycle)
• Quality benefits
• improved customer satisfaction (better product
  quality)
• less rework (e.g. right information available)
• Other benefits
• reduced training costs
• catalyst for cultural changes
• more optimised use of computing resources

14
Why product data management is needed? Design
data management viewpoint
15
Products design as part of manufacturing system
Design interacts with production
16
Systems development process
Modified according to Keller Shumate (Keller
M., Shumate K. Software specification and
design, A Disciplined approach for real-time
systems, John Wiley Sons, 1992)

• Data management is needed throughout
  products life cycle

17
Engineering Change process
Manages how changes are proposed, evaluated,
approved,and implemented into a product and its
documentation (controlled changes to the product
(data))
Proposal
Prepare proposal. E.g. describe
problem/enhancement, areas affected,...
Evaluation
Costs, impacts of solution, etc... Evaluates and
approves/disapproves for implementation
Implementation
Implementation control. Schedule, actual
costs,...

18
Design processes (embedded product)

• Contains discipline specific processes
• Software engineering
• Electronics engineering
• Mechanical engineering
• Interfaces / interactions between disciplines
  require coordination (e.g. integrated change
  management / maintenance)
• Co-design
• Co-design is defined to be an engineering
  methodology, which aims at designing the system
  as a whole and achieving shared functionality and
  performance goals
• Product data should be available even after
  decades
• Mechanical/Electronics engineering design/operate
  with physical product gt interactions with e.g.
  production, purchasing, and materials management
  functions

19
Standards

• STEP
• standard to enable organisations to share product
  data between different computer systems and
  environments
• contains currently many application protocols
  (e.g automotive industry)
• not widely in use in PDM systems (complicated,
  different application protocols,) (Peltonen
  Martio Sulonen (2002))
• SGML / XML originally for description of
  structured documents gt suits also for the
  description of other kinds of structural
  information (Peltonen Martio Sulonen (2002))
• CDIF family of standards which can be used to
  exchange information between two CASE tools

20
Design data management dimensions (Van Den Hamer
P., Lepoeter K. Managing Design data The Five
Dimensions of CAD Frameworks, Configuration
Management, and Product Data Management,
Proceedings of the IEEE, 841(1996), pp 42-56)

• Dimensions are common for all design disciplines
  (e.g. SW design, electronics design, mechanical
  design,)
• Versions
• Views
• Hierarchy
• Status
• Variants
• In practice several dimensions should be
  considered simultaneously

21
Design data management dimensions / Versions

• Information modification creates new versions
• e.g. controlled way to add functionality or steps
  to correct mistakes
• Version information should be stored
• Information should be available for many years

22
Design data management dimensions / Views

• Complex products design require more than single
  presentation gt levels of abstraction
• Linked to the development process steps
• Management of needed corresponding views

Data needed for production
Electrical schematic
Layout diagram
23
Design data management dimensions / Hierarchy

• Complex products design require decomposition gt
  design data has a hierarchical structure
• E.g electrical schematics contain blocks,
  mechanical design contain sub-assemblies
• Provides possibility to the reuse of components

24
Design data management dimensions / Status

• Indicates organisations decision about the
  maturity of design data
• Ensure that data meets certain requirements
  before next action (e.g. is design ready for test
  ?)
• Can provide also e.g. access criteria for design
  data

25
Design data management dimensions / Variants

• Terms Version and Variant are often confused
  with each other
• Variant relate to the development of families
  of related products
• Variants appear similar but they are not
  identical gt management of commonalities and
  differences (common parts, options, substitute
  parts,)

26
Design data management dimensions / Several
dimensions (Example 1)
27
Design data management dimensions / Several
dimensions (Example 2)
28
Traditional PDM functionality
29
PDM functionality

• Product data management features occur also in
  team level systems and design systems
• First PDM solutions were created to support the
  engineering by Data vault -functionality
• Today, these functions cover e.g. workflow
  management, product structure management, and
  communication in addition to data vault
• Traditionally PDM systems have focused on
  mechanical product data
• Nowadays also interfaces with electronic CAD
  (ECAD) environments
• Interfaces with SW development are not common in
  traditional PDM systems

30
Product Data Management (PDM) Design, exchange
and integration viewpoints

• Product data management were considered from HW
  and SW viewpoints
• Three product data management systems were
  introduced
• Metaphase
• Windchill
• PVCS Dimensions (SCM system)

31
PDM support for design data management
EPDM
Team-PDM
Team-PDM
Design tool
Design tool
Design tool
Design tool
Design tool
Design tool
32
PDM systems architecture (Peltonen Martio
Sulonen (2002))

• Typically use relational databases
• Usually client-server architecture
• Attribute information is stored in PDM database
  and product data documents are stored in files
  which can be accessed through PDM system
• Usually there can be simple web-based user
  interface for information readers
• In large organisations there can be central PDM
  system or separate independent product
  information management systems (in latter case
  the management of data consistency is more
  difficult)

33
Traditional PDM functionality (functionalities
are used in conjunction) (Miller, E., MacKrell
J., Mendel A. PDM Buyer's Guide - Product Data
Management Systems for Improving Processes and
Products, (6th edition), Volume1, CIMdata, 1997,
Michigan, USA)

• Data Vault and Document Management,
• Workflow and Process Management,
• Product Structure Management,
• Classification and Retrieval,
• Program Management,
• Communication and Notification,
• Data Transport,
• Data translation,
• Image Services, and
• Administrator services.

34
Data Vault and Document Management (DVDM)

• Secure data storage for items and files
• Item definitions life cycle definitions
• Access control
• Check in/out
• Version management
• Meta-data management

35
Data Vault and Document Management (example)
Item ID D001 Version 0.0.2 Filename
file.xls Author JMM


PDM
36
Workflow and Process Management (WPM)

• Tools for define and implement
• change processes and
• other processes based on company-specific
  business rules
• life cycle management (in cooperation with DVDM)
• Works in conjunction with DVDM
• WPM ensures that processes are executed according
  defined rules

37
Workflow process (example)
Notification
Task / function
State
Refused
Task 1
Task 2
Draft
Task 3
Ready
Approved
38
Product Structure Management (PSM)

• Part and structure definitions
• Optional and alternate part definition
• Part and relationship information
• Incorporation of data (e.g. CAD documents) to the
  parts and structures
• Part lists

39
Structure with elements (example) (modified
according Metaphase PDM systems brochure)
40
Classification and Retrieval

• Attribute association to the product data so that
  similar items can be related gt easier to find or
  reference
• Information search according attributes
• Information organisation
• Allow item libraries

41
Classification and Retrieval (example)
Component category 1
Comp1.1
Comp1.2
Component category 2
Comp2.1
Comp2.2
Comp2.3
42
Program Management (PM)

• Project management
• Possibility to create and modify Work Breakdown
  Structure (WBS) (major tasks, sub-tasks,)
• Responsibities and expenditures can be assigned
  to each WBS
• Allow
• user to relate detailed WBS tasks with PDM
  controlled elements
• search WBS task related product data
• Not well supported in current PDM systems

43
Communication and Notification

• Important feature in concurrent engineering
• Possibility to manual and automatic notification
• Increase communication e.g. between teams

Notification
44
Data Transport

• Isolates user from the network and operating
  system commands
• Isolates user to know where any specific data
  item resides
• E.g. user locates data from PDM and PDM system
  handles data transfer to users workspace

Data translation

• Heterogeneous environment requires data
  translation (different systems and applications)
• PDM can invoke translator when it is needed (e.g.
  during process execution)

45
Image Services (IS)

• View capability to documents for users without
  having access to the application which created it
• Red-line, mark-up capabilities
• Improve communication e.g. between managers,
  reviewers, designers,...

Administrator services

• User authorisation
• Manage archives
• Meta-data definition
• Tailor system to meet the enterprises particular
  needs