Managing Automation :: Technology Solutions for Progressive Manufacturers Sign in or register  |  Advertisers & Press  |  List Product  |   Subscribe to MA Magazine  |  Newsletters  |   My Profile
Ask the Manufacturing Execution Systems (MES) Expert: Scheduling Assistance
Ask the Expert

Sorting Through Revisions

Asked on Mar 7 2007 6:36:09:000PM

Q

Hi, Each time a design change (ECO) is needed, the same question pops up: Is the modified item a rev-up of the old, or a new item? The most common way to answer that question is to find out whether the old and modified items are still interchangeable. When in the design phase, engineers like to release the current state of their design to ease communications. However, these released documents may still need to be changed. So, when in the design phase, the interchangeability criteria don't seem pratical, as most changes are not interchangeable, meaning that a new item number shall be assigned to the modified items most of the time. Do you think it's OK not to use the interchangeability rule while still in design and keep the item numbers unchanged following revision of items? If so, how would you manage prototypes? Would you generate complete product trees for the various prototypes built throughout the design phase? Thanks!

Claude Chevalier, Quebec, QUE
AWhat most people do is have design revisions and then part revisions. In other words, a design undergoes design revisions until it is released (i.e., released outside of the design environment). Then it would undergo part revisions. While in the design revision state, interchangeability rules don't apply. In the released state, interchangeability rules do apply. This also usually means different ECO processes. When a design is in the design state, people often place it in a rather light ECO process. Once in any type of released state, all the information about that part is under a strict ECO process.

As far as dealing with prototypes, most people use different part numbers for prototypes and have them managed in their own revision scheme.

Meet the expert

Kenneth B. Amann

Director of Research, CIMdata Inc

A graduate of Georgia Tech, Mr. Amann has 35 years of experience researching and working with Product Lifecycle Management and Product Data Management architectures, as well as developing computer-based engineering applications and document / information management systems. Mr. Amann has held senior positions in PLM marketing, development, and consulting. His experience includes evaluating corporate engineering and manufacturing operations, managing PLM programs, recommending collaborative and concurrent engineering and product information management solutions, implementing PLM solutions, and developing and evaluating requests for proposals. Prior to joining CIMdata, Mr. Amann was the managing director for PricewaterhouseCoopers' Technology Leadership Group, where he conducted research into and evaluated emerging PLM technologies and vendor products based on these technologies.
Ask your question

Please sign in or registerto ask your question now. As a registered member of Managing Automation, you'll have access to all of our industry experts, the entire Research library and tools such as the Custom Software Comparison and Business Assessment Tool.