topic Stop Orders in Windchill

Stop Orders

rhart — Tue, 22 Feb 2022 16:44:02 GMT

When we have a change request pending and the parts are being made we need to stop manufacturing/procurement until the changes are resolved. In the past we used paperwork called a Stop Order, to let the planners/buyers know, and so they could put things on hold.

How do you deal with these scenarios in Windchill?

Re: Stop Orders

MikeLockwood — Tue, 22 Feb 2022 16:50:18 GMT

Two suggestions.

1. A Buyer / Planner group could be subscribed to "New Change Request" objects. They would need to take action and coordinate.

2. A Report could be created for "New Change Request" (or a Change Request reaching a certain approval state), and then a Data Monitor set up to run automatically daily and distribute the result to any number of users. The Data Monitor should have a threshold of 1, so it wouldn't run if there are none on any given day.

There could be a process within Windchill (possibly using a workflow) that the buyer / planners used to coordinate.

Could also have the buyer/planners use Action Items associated with Change Requests (which can be reassigned), to track / ensure the needed actions on each.

fun puzzles 🙂

Re: Stop Orders

rhart — Tue, 22 Feb 2022 17:29:00 GMT

Good answers, thank you

Re: Stop Orders

ZY_10202372 — Fri, 18 Mar 2022 03:26:35 GMT

Good day,

In my understanding stopping orders should be managed in ERP, not Windchill.

My questions:

1. What ERP does your company use?

2. How did you define the ECN participants?

I think it can be like this:

a. Make sure manufacturing and supply chain can have access to Windchill ECN, when change requests come out they'll be notified via mail automatically.

b. Maybe procurement and manufacturing should be included in change related Windchill tasks.

c. Who controls the ERP master data? When change comes out, someone should change ERP master data so that sales orders / procurement / manufacturing orders can be blocked.