Maintenance Job Scheduling

Kinetic ERP
1

Hey Friends!

We are starting our implementation of preventative maintenance in Kinetic and have some questions about how maintenance jobs are factored into global scheduling with normal jobs. I’ve set up various test scenarios where a maintenance job is being performed on a certain piece of equipment, and that piece of equipment belongs to a resource group that is used by the normal job. The maintenance job is set to a locked schedule with a very high priority. We are seeing that global scheduling is still scheduling jobs with that resource at the same time as the maintenance job. My thought would be global would schedule the jobs after the maintenance job. I know there are tons of configuration options with scheduling, any obvious things to check for?

image
image1238×358 22.4 KB

2

Are you doing finite or infinite scheduling? If you are doing infinite scheduling, it will continue to schedule jobs on that resource even if it is already being used (in this case, by the maintenance job)

1 Like
3

Hi Todd,
We are running global scheduling with the finite load option selected, would there be another place to check for finite scheduling?

4

Did you link the Equipment record to the Resource?

3 Likes
5

2 places that can interfere are on resource group, make sure the finite horizon is greater than zero.

image
image1070×240 13.4 KB

And make sure on the resource itself that finite capacity is checked:

image
image1083×234 13.7 KB

2 Likes
6

Hi John,
Just the resource group, does a resource need to be specified as well?

7

Yes. In order for the schedule to know that the machine is down, you have to link the Resource to the Equipment.

2 Likes
8

Thank you,

The resources within the group do have finite checked, but the horizon is 0. I’ll tweak these and re run global.

9

Great thanks! I’ll try tweaking this!

10

I showed the horizon on the resource group but that is the default if it is not set specifically on the resource. On the resource it’s right under the finite capacity checkbox.

And as John pointed out, it must point to the specific resource.

1 Like
11

Did you run ‘Calculate Global Scheduling Order’ and then run ‘Global Scheduling’?

12

I think the way our resources and equipment was initially implemented is off. If a specific resource is needed for the equipment for this to work.

We have 6 resource IDs created (6 machines), but only 1 equipment record for the 6 machines. I assume we will need to create additional equipment records to accommodate the resources 1:1, correct?

13

Correct

1 Like
14

Hmm I added a horizon and set the specific resource, ran global, and the jobs did not push out. :thinking:

1 Like
15

You may potentially have the jobs locked. You can override it on all jobs using the checkbox on global scheduling:

image

Alternatively, on each job you can check here:

image
image1042×461 23.1 KB

1 Like
16

Is the Finite Horizon in Site Maintenance set to the same as your resources?

If the jobs were created before you made these changes, you might have to remove all jobs from the schedule and re-schedule. Scheduling is very particular in the setup and creation of the parameters for it to work.

I would also review the scheduling log to see what it says.

1 Like
17

Thanks for all your help guys, I appreciate it.

The jobs are not locked, but the finite horizon on each resource was different than the one in site maintenance, I just made them the same.

Do I always have to wait for global to finish? Or if I manually schedule the individual job at the time of the maintenance job will it still push out?

18

You always have to global schedule. All the job schedule does is schedule that one job, it does not factor in all of the other jobs. You also have to run the Generate Shop Capacity and Global Scheduling Order before you run global scheduling.

1 Like