Skip to main content

Currently, we have our Control Plans for Manufacturing setup for 1hr interval time triggers. I’m finding that this may cause more harm than good. I’ve been experimenting over the last few days, and it seems that time triggers will continue to run, even if there is no associate clocked into the Shop Order. An instance of this would be an associate completing the Setup step. The Op status will change to Partially Reported, and the time trigger will continue to run and generate Analysis every hour. It appears the only way to stop this behavior is to select Interrupted. If an associate has selected Start Production, and then stopped production with the status Partially Reported, the time trigger appears to stop.

If my understanding is correct, this is simply how time triggers behave. I believe this may cause issues with generation of Analysis when associates would not be expecting to see them. Given that a Shop Order cannot be completed/closed without all Planned Analysis Cancelled or Completed, I see this as a potential disruption to the shop floor. 

Now I’m considering moving to manual generation of Analysis to avoid potentially being unable to close numerous Shop Orders if time triggers are generated throughout a shift. Is my understanding of Time Triggers correct? Once a Shop Order is started, triggers will continue to generate analysis on the set time interval while in setup until the SO is moved to production or set to interrupted? When production is started, the trigger will only stop when production is stopped, interrupted or completed?

UPDATE - We have moved away from using time triggers and will manually generate all Analysis checks in IFS. 

@cjohnson  Do you still not use time triggers today? Or did you ever find a solution better than just manual creation of Analysis Results?

I am trying to find a way to manually generate Analyses at the start of the operation and then never again. We have been playing around with time interval =10 years, but the time interval is still very finicky generating multiple Analyses or none at all

@SidneyIFS640 No, we do not use time triggers. We use the create analysis at the start of the SO along with the QA controls (Mandatory Control Plan, Mandatory Analysis, and an event to auto park the SO in the event of a failed QA inspection submission). 

We still require our associates to manually create inspections at this point, but the controls we have deployed improved the robustness of the QA system. 

@cjohnson okay, good to know. Thank you for sharing!

Do you use MRBs? We do not, so I really like the SO park idea. Thank you!

@SidneyIFS640 You’re welcome. Yes, we use MRB all the time. 

I am leveraging the Interruption workflow for the SO parking. So, in the event of a failed analysis, the QA interruption workflow triggers parking, downtime, and moves associates to an indirect code. An event action notifies associates at the Site of the failed inspection via email.

Reply


Terms & ConditionsCookie settings