Hi!
We’ve run a number of tests but we can’t work out why we’re losing our resource groups in our job operations (Scheduled Resources in Job Entry. This can happen at any time during the day. Does anyone have any ideas to help us with our research?
1 Like
Welcome @audrey !!
My assumption is that the Job is being scheduled and a resource that exists in the resource group is being selected. Resource Groups just contain a list of resources that the operation can use and is not actually selected as a resource. Instead, the scheduling engine will look at all of the resources and determine what it thinks is best to put the operation on.
2 Likes
Thanks John!
Our problem is mainly that our resource groups disappear on all the operations of a job after there is a change. Is it normal that the resource groups disappear and that we have to re-schedule after a change in the job?
1 Like
I think I will need some screen shots of the before and after. I want to make sure I am understanding what is happening correctly.
I have never seen resource groups disappear on a job. unless someone is manually removing them.
Question… are you using “Capabilities” in your structure? do you callout specific Resources instead of a resource group?
1 Like
Can you also provide a screen shot of what is lost?
I’m having the same problem and our consultants are not helping me much. We are manually overriding this on dozens of jobs daily.
When I change a job and reschedule it, I’m now getting in the habit of checking the scheduling resources tabs before exiting out of the job. Sometimes I have to run the scheduling process multiple times for the resources to properly load via capabilities. You can verify it’s linked correctly by navigating to the Operations > Scheduling Resources tab > Scheduled Resources tab
I’m finding that locking jobs we are actively working on after we make changes prevents anything from magically screwing the job up in the background over again.
Expand the tree view on your screen shot in your example above.
Does anything show there.
Turn on change logs for the JobOper, JobOpDtl tables to pin down exactly what is changing that drives this.
The screencap I gave was from a consultant. There’s nothing else in that tree. It was a fake job. In general, it will show 2 resource lines under the operation itself, one for an operator and one for a machine. But when you drill into the scheduled resources, it will show nothing is actually scheduled and prevent an operator from clocking in via MES. Despite not actually being scheduled, the job itself will still show a scheduled due date on the main job entry like everything is peachy keen and perfect. It’s super frustrating.
We have change log turned on and there is no useful information in the change logs to help us with this. All of the changes show this:
kriley 13:14:31
JobEngineered: True → False
kriley 13:14:31
JobEngineered: False → True
I didn’t actually undo or redo the engineered check box on this job, so I have no idea why it even says I did.
Temporarily add most all the fields in the change log tables I mentioned. Your just getting the JobHead.Engineered field. We need to see JobOper and JobOpDtl fields.
You don’t want all the fields logged as a general rule because it will create a huge table but for debugging you need to see exactly when it happens. That may shed light on the issue.
You can removed them when finished with the issue.