customization of WTParts & EPMDoc revisions - PDMLink9.1

[ptc-218373]

We're working at integrating WC with our ERP system, and we have it set up so that WTParts are created automatically with EPMDoc creation and revisions, and so their revisions match. We're now discussing the possibility of customizing the WTPart of assemblies to match the bom structure required for manufacturing, and so the 2 items will have different structure. What happens when the EPMDoc is revised, and a new WTPart is created that will replace the customized one? How do you handle this?

Thanks in advance,

Dave Tate
Peerless Trailers,
Penticton, BC

[AL_ANDERSON]

You may need a picture and be more specific.

EPMDocs can be drawing, assembies, or parts, each with links to the
others, and each with version control.

WTParts are version controlled, but they can also have View Versions that
allow for branching, which complicates the version control. EPMDocs
cannot do View Version branching. You can even make "one-off versions" in
addition to normal versions and branching view versions.

There are 5 different kinds of EPMDoc to WTPart links that each have
different uses.

WTDocuments are version controlled, only, so they are a little easier,
except that you have two different types of WTPart to WTDocument links to
choose from: Described by and References.

To answer your question, you need a picture of which EPMDoc to what part
view with what WTDocuments (if any).

I strongly suspect that there is no "right answer" for you. You will have
to understand the software options, and model something that meets your
business requirement using the options that you like the best.

Al