Scheduling frequency problem 1

[cima]

Hii all,

When our planner section want to modify/create new Maintenance Scheuling Task(MST) we encounter a problem with schedule frequency.
The error message is:
NOT AN EVEN MULTIPLE OF LOWER SCHEDULE FREQUENCY

Does anyone have any idea why this error come out and how to solve it.

 

[Calator]

Make sure that the scheduled frequency of the task being created is an exact multiple of the scheduled frequency of any other existing lower frequency tasks (see mso700.cbl, search on error code 6727)
Eg
if creating task 9210 with frequency 180 days, mims checks for all existing tasks with task number like '92%' and strictly greater than '9210'.
Say it finds tasks 9220 with scheduled frequency 30 days. It divides 180/30 = 6 and this is ok. But if it finds task 9220 with frequency 91, the error will be generated. The error is generated if remainder of division is not zero, or if the result is < 2.

Suggest to check frequency of associated tasks, eg using Corvu:
select SCHED-FREQ-1 from msf700
WHERE REC-700-TYPE = my_type and
EQUIP-NO = my-EQUIP-NO and
COMP-CODE = my-COMP-CODE and
COMP-MOD-CODE = my-COMP-MOD-CODE and
MAINT-SCH-TASK LIKE first 2 char of my-MAINT-SCH-TASK and
MAINT-SCH-TASK LIKE > my-MAINT-SCH-TASK

if all such tasks have scheduled frequency that can exactly divide the current task's frequency, then MIMS may have a bug.

 

[Rabl]

If you are using a 9000 series scheduling,
Remove the frequency from all of the series and then go back in and enter the new correct frequencies.
Be aware as the error stated they must be multiples of each other (ie 250 Hr, 500 Hr, 1000 Hr)

 

[Ozgipsy]

Hi Cima,

When using the 9000 series people often do get the basic suppression and numbering principles. However when they try to implement it I have found that the following occurs.We will take a very simple 90 day and 180 day cycle.

They create the first task which may be 9120 with a frequency of 180 days

Then they create the next task which is 9130 with a frequency of 90 days

According to logic tghis should work. 9130 is a higher number within the set, therefore lower in priority, (91**) and 180 is a multiple of 180.

However within MIMS it is looking at this from the task priority perspective. That is to say it is saying that 90 is not a multiple of 180.

Try entering the 9000 series from the lowest frequency/ lowest priority task first. This usually overcomes this issue.

Cheers

Oz...