cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Best Practice for dealing with multiple revisions of Customer Geometry?

Highlighted
Level 12

Best Practice for dealing with multiple revisions of Customer Geometry?

Hi Guys,

I was wondering what are your best practices concerning receiving multiple sets of  the same customer geometry (just revised) over time?

For example:

  1. Working with Best Customer, new project.
  2. Customer Engineer sends an assembly of their design.  (STEP files or other "neutral" data types.)
    1. Our design has to integrate into their design.
  3. Our work begins. 
    1. Import or Open Customer Geometry
    2. Use customer supplied geometry to design our product.
  4. Time passes, days or weeks.
  5. Customer sends a revision to their design.
    1. New revision might have new parts.
    2. New revision might just be revised parts.
    3. Changes might be obvious when reviewing.
    4. Changes might NOT be obvious.
    5. File names may or may not have been changed.
  6. We have to review and integrate the customer's revision into our design to make sure we are compensating for all the changes they sent.
    1. Save new revision into a new directory.
    2. Save As and add an identifier.
      1. Could be *-01, 02, 03, etc.
      2. Could be date based.  *_20170609,  *_20170801, etc.
    3. Open old revision and new revision and compare  (optional)
    4. Work new version into our existing design.

So how do you handle such a situation to minimize fuss and still get the job done quickly?

-marc

CAD / PLM Systems Manager

TriMark Corporation, New Hampton, Iowa

2 REPLIES 2

Re: Best Practice for dealing with multiple revisions of Customer Geometry?

Besides getting a new customer?

It takes work. No matter what, anyone who dumps data over the wall without explanation is going to find a way to slip something past.

The way I have handled such a thing is via structures and groups. I make the overall updated assembly structures the same as the previous one and then group components in the new version based on the old one. This finds the items that are new, and finds items that are omitted. The groups are set such as a plate is grouped with the fasteners that hold the plate in place; nuts, bolts, washers. If I can see 8 holes and 8 nuts, 8 bolts, and 8 washers all in proximity of the holes in the plate, I am very sure this is correct. It also cuts down on stupid things. Example. I've seen cases where  a ref-pattern fails. Since the user didn't bother to group the fasteners with the item, it looks at a glance, like only one fastener is present. So they manually assemble replacements into the holes. End result - 8 fasteners in one hole, and 7 new fasteners for a total of 15. Not cool.Interference checks could find this, but the fasteners get flagged for interfering with the nuts, so unless one is counting carefully, that won't help (and failing to count carefully is how it got this way to begin with.)

A quick run at a mass-properties report should find noticeable shape changes, though it's possible for mutually cancelling changes to be made, I find it unlikely they will be a perfect match. This should find all items where shape dimensions changed. It won't find cases such as shifted holes; changes that can't affect the volume.

If you haven't got a PDM system, I would create a search path and create separate folders for the various versions, searching the latest one first and working back. You can do this in advance and create as many empty folders as exceeds your expectation for revisions. Then put the newest work you do in the associated folder so you can tell at what point you had to make a change to accommodate their revision. I would not rename with a suffix; I would probably rename what they sent, to match what they sent before; keep a spreadsheet of those name changes. It shouldn't matter much as you always have their STEP file to verify what their name for the item was in any version they sent. I think the rename is recorded in the part history.

Try to get an inside contact with the customer. Someone should be keeping track of what is changing and why. I've been burned before by too many intermediate layers of people who have no idea how CAD/CAE works and assume it is as complicated as Notepad.

Re: Best Practice for dealing with multiple revisions of Customer Geometry?

Interesting,  I like your approach.

What about with a PDM system?   We do have Windchill, and the engineers that are dealing with this are reluctant to let Windchill manage the files as it was designed to do.  (Hence the suffixes.)

I think that there is a fair amount of preparatory work no matter if you use PDM or not, and I don't really see a magic bullet to solve that.

-marc