Skip to main content
O
olliecampbell1-Visitor
1-Visitor
May 3, 2019
Question

Drawing templates: Historic up-issue

  • May 3, 2019
  • 2 replies
  • 5066 views

Hello,

 

I've seen, maybe with other CAD packages, a way that the drawings keep a log of historic up-issue's. How does everyone manage that here? At the moment I'm creating new drawings, saving it with a different file name and only including the modification that required the up-issue for that one drawing. Ideally I'd like to keep a log of the modifications from initial drawing through to the current iteration.

 

I hope that makes sense?

2 replies

D
DaveMartin16-Pearl
16-Pearl
May 20, 2019

What's an up-issue? I'm not familiar with that term.

O
olliecampbell1-VisitorAuthor
1-Visitor
May 21, 2019

Hi Dave,

 

It's an increment of an issue number on a drawing. Maybe slang that I've gotten used to using!

 

Thanks

D
DaveMartin16-Pearl
16-Pearl
May 30, 2019

I don't know what an issue number is... that might be a process or terminology specific to an industry or companies I haven't worked for.

Is that like a revision number?

 

joe_morton
18-Opal
joe_morton18-Opal
18-Opal
June 17, 2019

Are you using Windchill to manage your files? Windchill keeps the history of the drawing, so there's no need to change the filename. We keep a manual table on ours for the engineer to enter information on what changed in that particular revision

O
olliecampbell1-VisitorAuthor
1-Visitor
June 18, 2019

Hi,

 

No I'm not using Windchill.

 

It was that table that I was trying to find an automated method of updating after each change. I'm guessing it's a manual process.

D
DaveMartin16-Pearl
16-Pearl
June 18, 2019

Aside from the revision, we are in the process of removing anything from the drawing that can be found in Windchill, like the revision block and signature block. It doesn't make sense anymore for us to be duplicating that information on a drawing sheet when all the information and more resides in our PLM system.

    Terms & ConditionsCookie settingsAccessibility statement