Do you still include a Revision History block on drawings?

[sdrzewiczewski]

Does your company still include a Revision History block on their drawings? If so do they include ECN Numbers and descriptions of the changes?

[MichaelMarshall]

We still include a Revision table on our drawings. We reference the EC#, date, who executed the drawing change, and a short description. Though honestly, that short description sometimes is useless compared to the magnitude of changes that my have been executed.

We do this for both our Customer Prints (which for stock items are available to anyone internally or customers upon request), as well as our Manufacturing Prints, which have a considerably smaller access group.

[SarahFord]

Here's what we do.







The current mod text is scaled down and placed near the mod number in
the previous mods list.



Regards



Sarah Ford

CAD Designer / CAD Administrator

Westwind Air Bearings

Tel. 01202 627236

www.gsig.com

[MikeLockwood]

The goal that we have is for this info (the Windchill Change Notice Number) to parametrically populate the Drawing Revision Block (haven't figured out how to do this yet):
[cid:image002.png@01CB2EFB.90C5EB30]

[mlocascio]

Stephen D. and company,



The last few companies that I have take a turn with have not maintained
revision history on their drawings. In fact the last company did not even
have what I would refer to as an ECN system. It seems like most companies
are keeping archived copies of their drawings on some kind of go-between
software. This way they don't need a license from PTC to plot or view their
drawings.



Michael P. Locascio

[mlocascio]

That's pretty cool!

[mlocascio]

Actually, folks, this is the BEST way to use that information (if you can).



Thanks for sharing this with us Mike. Let us know if and when you get it
debugged.



Michael P. Locascio



From: Lockwood,Mike,IRVINE,R&D [

[srector]

We still have the revision history block on our drawings, but we only use it to record the Change Request Number of the current revision.

We're also looking at adding columns for the Life Cycle state and Release Date. The Life Cycle state would be populated by the system attribute. We'd like to do the same thing with the Release Date, but we haven't come up with a good way to pass the CN Resolution Date back to ProE.


In Reply to Stephen Drzewiczewski:

Does your company still include a Revision History block on their drawings? If so do they include ECN Numbers and descriptions of the changes?

[MikeLockwood]

1. Seems that the Change Notice, not the Request number should be used, because the system considers that the Notice is what authorizes the new Revision (see the History, Revision report).

2. Having the state and/or any date populate the actual drawing table can't work. It requires that the object on which the state is changing or against which a date is being recorded be iterated.

a. This is a fundamental concept. Need to have a separate mechanism to show those metadata elements that can change after the drawing is checked in (state and various dates). ProductView watermarks provide this mechanism.

[KevinAlexander]

Though I agree 100% that ProductView is the best way to do this with watermarking, it can definitely work showing state/date info on the drawing. As a Windchill Admin this is exactly what I did. We weren't really "enterprise" with Windchill at the time but I wanted to show the date info on the drawing in Pro/E to always be indicating to designers/engineers what state was. Again, I agree ProductView watermarking approach is best and in retrospect I would have done that. But it CAN work.

The data information never changes, even if a republish occurs, so there are no worries there. But keep in mind that the PTC_WM_CREATED_BY/ON parameters show the date of that specific REV creation, not the initial rev creation. The PTC_WM_MODIFIED_BY/ON show the most recent check-in date. Again those do NOT change through a republish.

The state of course can change, but the property publish.republishonepmdocumentchange=true causes a republish if that happens, therefore the text you see on the drawing for state will show correctly after the republish. This does NOT cause an iteration.



From: Lockwood,Mike,IRVINE,R&D [