Hi Steve,
To me, this seems you are asking the same question as before, but in a different way. Content Management (Windchill Updates Reflecting in XML Content )
Mine and Jeff's answers still stand. You can link Windchill parts into Arbortext via Parts Lists, 2D Illustrations, or 3D Illustrations.
Perhaps what you are asking is can Windchill automatically raise change requests for any and all affected service data after engineering changes are made? The answer to that, is no. I think you could do this via customisation, the mechanisms that come to mind:
- Use tagging in the authored XML data to keep lists of related parts.
- Use Windchill "related objects" feature to link related parts on each DynamicDocument service data object.
- As #2, above, but the other way around. Have links on each part to all related service data objects.
Once you have those relationships in place, then a process could run after a part changes and mark the relevant service data objects as possibly affected and in need of review. I don't know enough of the implementation details to advise how much effort that would take, but our company could certainly advise (www.gpsl.co).
Does that help frame the problem for you?
-Gareth