Where used publishing

[SimonHeath]

Dear All,

We have been asked to create a workflow robot to navigate up a structure and publish the where used of a item. The rationale for the client is they make some changes that do not affected the form, fit and function and so do not change the part number but want to re-publish the where used items, one reason is to ensure the visualisations and tech pubs are upto date (apparently they have issues that the manuals are sometimes out-of-date). Technically it is not difficult to do but clearly this might, in some cases, create alot of publishing jobs and before we implement a technical solution I just wanted opinions on if this is a sensible thing to do, or the client should re-evaluation their processes.

Simon

[DarrenStorey]

Simon

The default config for publishing is “as stored” so I doubt the where used representations would even be marked out of date by Windchill. Also if an interchangeable change has occurred, then by definition the ‘form’ should be the same, so would the change even be noticeable in the parent assembly? Are the child part revisions stated on the documentation? As you say there is certainly potential for an explosion in publish jobs.

Purely in terms of publishing efficiency, the publishing strategy that CAT presented at PTC Live 2013 was interesting. Using positioning assemblies’ throughout, publish models “latest” and drawings “as stored”.

Regards Darren