WindChill Revision Letter/Number

[OldCADPOPro]

Hello All,

I am trying to get a pulse on the WindChill users out there on the Windchill Revision letter/number. Here is some background. Our current drawing revision standards for revisions allow us to use a numeric revision number to release a preliminary part/drawing for things like quoting or vendor coordination. We have mapped these into Windchill by using the Team Issue process. Our releases are then specified by Alpha characters, A,B, and so on. What has been decided to do here is when we have an Alpha release, the Windchill revision is to stay numeric.

The issue becomes the potential disconnect between what Windchill assigns as the revision versus what the drawing indicates ad the actual drawing revision letter. It is not so bad when you simply release a part as the initial release because the Windchill Revision 1 is easy to map with Revision A of the drawing. But if I team issue a couple times and then release, then my Revision A drawing is actually Windchill revision 3 or 4. This gets very confusing when trying find revisions in the system.

So finally to my question/poll. What are other Windchill users doing out there in regards to the Windchill Revision versus the actual Drawing/part revision?

Thanks for participating, this will be valuable information to me.

Richard Andrew

 

[3DDave]

You can make any revision letter sequence you like in Windchill. I think it's described in the Business Guide, but you may also want to ask at the PTC Community.

What I've seen is a sequence 1, 2, 3, ... 99, A, B, C where the transition from numeric to alphabetic is chosen at the New Version choice for releasing to Production.

 

[looslib]

We use alphabetic releases for pre-production and numeric for production. All handled by a Windchill revision table.

In Windchill, you have the revision, which is the A, B, C, 0, 1, 2, etc, sequence.
You also have the iteration of each version that increments everytime you check a file into Windchill.
Combine these into a Windchill Version of B.3 or 1.2, etc.

We keep the Revision of the part, WTpart and drawing together. They all get released and incremented as a group. Never release one without the other 2.
You can jump from revision C to revision 0 whenever the part is moved from pre-production to production.

When you have a released part at say Version B.6 and go to revise it, it will become C.1 or 0.1, depending on the production state. The *.1 file is 100% identical to the prior version part. Open this file in Creo, check it out, modify it, check it back in, you now have C.2.



"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[Korichnevijgigant]

The way we handle it is like this:

Lets say a part is being ECN'd and its currently at Rev C, but it was released at C.5 (so it was iterated 5 times when it went into "design" during a previous ECN)

So you would obsolete Rev C, process the EC to jump the rev to D, then work on it and as it gets bounced from engineer to engineer/drafter and so on it accumulates the .X so it could be at Rev D.150 or Rev D.2

The iteration is really not referenced in our drawings because up until the drawing is released it doesnt matter because it is in a prototype/design state.

Hope this helps.