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

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Examples of Part "References Document" and Part "Described by" document

hvaradharajan-2
1-Newbie

Examples of Part "References Document" and Part "Described by" document

Hi all,

This is a fairly discussed topic, but I don't see good documentation and examples in PTC help on what is recommended for what type of documents.

Iam looking for examples on in what cases we should use the link "References Document" and in what cases we should use "Described by" document.

Recommended option for scenarios A,B,C and recommended option for Scenarios D, E ,F.

I see that usage of "References Document" is OOTB restricted to documents under the type "Reference Documents", but this could be overridden by a preference.

FYI. We are in WC 11.0 are getting close to working part centric.

Thanks!

Hari

3 REPLIES 3

Reference documents are those documents that are supplementary to the main drawing like Material, process, or any other documents that are required to manufacture the part, and are called out in the main drawing.

Described By documents are those documents that are similar to a drawing but as a text formats (the way we call it- Word drawing)

Reference Documents are all kind of international or internal norms and standards.

These documents are valid in general in the latest released state and do not directly describe a part version

.

Any other document like a calculation, checklist, color specification or CAD Drawing where you need to track the version specific changes which describe the part you produce is a describe document.

This is a continual source of confusion for users...

At previous company we finally did the following:

1. Disable the OTB "Document" and "Reference Document" types.  No one has a clue what these mean.

2. Create one or more sub types under these with names that are meaningful to your company.

3. Create document templates with careful naming for each.

4. Encourage (and constantly refresh the encouragement) all users to create all documents from template - the correct type will result from this.

5. Establish procedures for what users need to do with each type when retrieved with a WTPart.  The whole point is - for this WTPart at B.3, here are all the documents (CAD and non-CAD) needed for this Part.  Some are also at Rev B because they directly describe Rev B; others displayed as whatever the latest released Rev is.

Announcements


Top Tags