Some other fields to check are that each plan is active and recurring. I added the EquipPlan.ActionStatus field to a customization for the equipment modules to indicate if there is an open job or if one is about to be generated. The field help for that was useful to me.
We have a weekly Maintenance Planning schedule set up to run weekly. It ran fine and created a new job last week but didn't create a job this week. The Maintenance Process ran complete with no errors. Did the weekly job not get created because it was time to create the bi-weekly job? Is there a hierarchy of how these need to be set up?
thanks
Kim
Kim,
We use it too, and I find that (most of the time) a job does not get created because the previous job is still open. The system will not (schedule)create a job if a job for that piece of equipment is still open.
mike
I agree that ensuring the active job for that equipment's plan must be closed - not sure if you have more than one maintenance plan for the equipment ID. I would also compare the date the plan processor was run to the next execute date less the buffer days.
Thomas
We do have more than one plan for the equipment. But the other plan worked but there wasn't a previous job created for that plan. I am testing it in my training environment..