Default behavior when revising objects

[JeffHoracek]

All,

Currently when our users create a new revision of an object, they need to collect all the other associated objects to the one they're revising. Sometimes they forget to collect the WTPart or one of the other EPM Documents. Associations are then broken. We have one site that they estimate up to 20% of the objects have improper/missing associations.

It was suggested by the local admin., that if the default behavior when creating a new revision would be that Windchill automatically defaults to create new revisions of the other objects associated to the one being revised as a more safe approach. This way everything is captured and if someone does not want to revise one of the associated objects, they will be making a definitive decision regarding this.

The preference here is that all the objects have the same revision level whenever possible whether they are changing or not.

Is there a setting/configuration that can somewhat easily be performed to change what I consider the default behavior? I'm not the system administrator, but if this possibility exists, can someone please provide that information so that I can forward it to our admin.?

WF4 M220
Windchill 9.1 M020

Regards,

Jeff Horacek

Engineering Change Management Specialist/
Global CAD Administrator

[cid:image003.jpg@01CE104C.E3A03790]
STERIS Corporation
5960 Heisley Rd.
Mentor, OH 44060
P (440)392-7721
F (440)392-8954

[MikeIbosh]

Jeff,
Yes, there are preferences at the Org and Site level for the collectors (revise, save as, etc.) that can be setup to collect all dependents, drawings, WTParts etc.

Mike Ibosh

[HugoHermans]

The collector preferences Michael mentions work very well when the revise action is performed starting in Windchill. When started from a CADdocument in ProE session (File > Checkout and Revise, or in-the-fly), they are of no use. Since this option can't be removed from ProE, there still is a chance to get bad associated objects.

Best Regards,

Hugo.

[cc-2]

Hi

I agree with Mike and Hugo.

I do not see a problem with the limitation in ProE. First, I think user should never be able to revise on the fly. Revising means an official change and someone how managed via the change management process.

If CM is implemented the CN should revise all the impacted object automatically. That is, when the user receive the task to apply the change the data is ready for him to check out.

If CM is not implemented, I personnally recommend to use Windchill to revise.

What are your best practices depending on if CM process is available or not ?

Best regards

[avillanueva]

True, this is a good practice. I think it falls down in certain environments where changes are done first then structured on a CN. I see this as the difference between traditional engineering supporting long term, mass production and fast paced, project/program centric, development where your output is a single unit. Of course there are models across the spectrum but when constructing our change process, the question of when do the drawings actually get touched was a central question, one that radically changes the workflow itself.

[JeffHoracek]

Thanks to Mike and Hugo.

I always instruct the users here not to use the Revise and Checkout option within Pro/E. We also have our system set to utilize the change process within Windchill. I've been instructing people to create their new revisions within an ECN, since they will need to create the ECN at the end to route the new versions of the objects for E-Sig's. Like everywhere else, there are a few users that just won't listen.

Thanks again guys.

Regards,

Jeff Horacek
Global CAD Administrator/
Engineering Change Management Specialist
[cid:image002.png@01CE10D7.C931A4D0]
STERIS Corporation
5960 Heisley Rd.
Mentor, OH 44060
P (440)392-7721
F (440) 392-8954

[JeffHoracek]

Antonio,

We use the change management as well as the ECN. I do instruct the users to create all their new revisions within the ECN, but not all do. The revise on the fly has caused issues for us in the past, so I instruct not to use it.

Jeff