Engineering Change Management in Enovia VPM

1
Engineering Change Management in Enovia VPM

• March 7, 2001
• Dassault Systems Korea
• Namchul Do
• dnc_at_hotmail.com

2
Contents

• Introduction
• A product structure representation in VPM
• Related organizations and systems
• EC Processes
• VPM Actions in EC Processes and Procedures
• Problem identification (ECR)
• Research and change (ECN)
• Change review
• EC implementation (ECO)
• Conclusion
• Lesson learned
• Considerations for Action implementation

3
Introduction
4
A product structure representation in VPM
EXT
EXT
IS BELONG TO
EXT
EXT
EXT
EXT
EXT
EXT
5
Example of the product structure representation
MODEL B
MODEL A
OPTION X
OPTION 1100
OPTION 1000
1999.1.1 - ?
EG XA
EG AB
EG AA
1 -?
1-9
1999.1.1 - ?
10-?
100-?
1-99
PART 5 ---
PART 1 --A
PART 1 ---
1-?
1-?
1-?
1999.1.1 - ?
10-?
1-?
1-9
100-?
1-99
PART 6 ---
PART 2 ---
PART 3 ---
PART 4 ---
CS Modif Eff
No Eff
PART 4 ---
PART 4 ---
6
Related organizations and systems

• Design and engineering departments
• Production control team (ERP)
• Part planning team, Customer support company
• Technical publication team, Customer support
  company
• ERP systems for production in manufacturing
  company
• ERP systems for part business in customer support
  company
• Info systems of technical publishing in customer
  support company

7
EC Processes
8
VPM Actions in EC Processes and Procedures
9
Problem identification

• In this process, EC Requests (ECRs) can be issued
  by Engineering, Manufacturing, Customer support
  and Marketing departments
• Determine EC cause attribute
• Need paper works and management of engineering
  knowledge and customer requirements
• Not yet related to Actions but needs to link them
  to the ECR management system
• Need interface tools to other information systems
  ( e.g. CS ECR management system)

10
Research and change

• In this process, designers review and update
  products to satisfy ECR
• Designers create Actions for ECs
• What is the criteria of new action creation?
  EG, Design group or amount of ECs
• How to use sub actions ?
• What is the meaning of the product of Action ?
• Designers update product structure with the
  add, cut and replace operations (see the
  fig in the next page)
• Version up operations copy a product with
  interoperability info.
• Replace operations need interoperability info.
• Record the changes in Action at the end of design
  session
• Apply the EC to multiple products (Replace where
  used with Different Actions ?)

11
Research and change (continued)
Option 1000
Option 1100
(2)
(1)
(4)
(3)
1650010 ---
1650010 --A
(2)
(4)
Effectivites on Edges (1) 1 - 99 (2) 100 -
current (3) 1 - 149 (4) 150 - current
(1)
(3)
1650030 --A
1650020 ---
1650030 ---
(2)
(4)
(1)
(3)
1650040 ---
1650100 ---
1650200 ---
Types of Changes Version Up Replace
12
Research and change (continued)

• Update Part master
• version up 1650010 --- to 1650010 --A
• version up 1650030 --- to 1650030 A
• Update Product structure
• replace 1650030 --- with 1650030 --A (under
  1650010 --A)
• replace 1650100 --- with 1650200 --- (under
  1650030 --A)
• Apply the EC to Products
• replace 1650010 --- with 1650010 --A (under
  option 1000)
• replace 1650010 --- with 1650010 --A (under
  option 1100)

13
Research and change (continued)
14
Change review

• Drop an action into 4 step Action flow
• Drawer, Review, Check and Approve stages
• Need additional action steps for administrative
  purpose
• EXIT programs runs for maturity control and
  signature on drawings
• Web Based ECN system enables all the related
  departments (even overseas dept.) to access the
  EC information (see fig)
• Poor Action history browsing window
• Synchronized with Action history file
• Old/New part comparison format and additional
  information
• Web Extensions for other purpose CS/Assy
  Process

15
Change review (continued)
16
EC Implementation

• Complete the modif effectivities
• Assembly parts are also Variants
• Whole sub tree is a hard work in an integrated
  BOM system
• ECs of shared assembly parts between Models
• Interface to Manufacturing ERP system
• Part master update New parts in Action
• Product structure update Some mapping functions
  are needed
• Interface to Part business ERP system
• Filtering CS parts add CS object information
• Interface to Technical publication system (Part
  catalog)
• Asynchronous interfaces to technical publication
  systems
• Synchronize E-BOM and Integrated BOM for tech pub
• Feedback from ERP

17
Conclusion
18
Lesson learned

• Too complex and strict management of Product
  Structure Changes
• How about separations of History recording and
  effectivity definition
• Too simple product model for the integrated
  product structure
• Design, manufacturing and customer support
• Poor action browsing window
• History recording on the assembly level
• If history is needed, set the assembly
  configurable
• Record level history access API
• Room for additional information objects
  associated to Action
• Interfaces to other information systems
  document management systems

19
Considerations for Action implementation

• Review needs of EC history and configurable
  assemblies
• Set a rule for EC and Child EC creation
• Set a simple process for EC
• Consider long duration transaction and nested EC
  problems
• Consider check in check out and complete of
  actions
• Extend Action database to satisfy various user
  requirements
• Consider interfaces to other systems (e.q. ERP)