Skip to main content
  • Community
  • Aerospace & Defense
  • IFS Maintenix
  • Managing Tasks requiring accomplishment with a defined Minimum and Maximum Usage window. Tasks that must be accomplished after but before a defined schedule parameter
Question

Managing Tasks requiring accomplishment with a defined Minimum and Maximum Usage window. Tasks that must be accomplished after but before a defined schedule parameter

  • 15 July 2024
  • 1 reply
  • 32 views

Southwest Airlines would like to know how other operators manage Tasks that require accomplishment after a minimum usage but before a maximum usage.   Plan after but Before a specified scheduling parameter. 

 

example: 

Task must be accomplished after 10 flight cycles (FC) and before 25 flight cycles after initialization.  

 

Task must be accomplished 4 times and then terminate: 

  1. Accomplished between 50-100 FC
  2. Accomplished between 150-200 FC
  3. Accomplished between 250-300 FC
  4. Accomplished between 350-400 FC terminates 
  5. Terminates after 4th accomplishment 

 

1 reply

Robert Bellemare
Rank
Userlevel 5
Badge +10

Hi Michele,

You could accomplish a version of this business requirement by using a deviation/extension on the scheduling rule of the baseline task. Your task would be defined as having 50 FC interval with a deviation of 50 FC. There wouldn’t be any direct way to prevent someone from accomplishing the task prior to the soft deadline. The first three instances could be handled by a recurring task. The last task a non-recurring version having a scheduling interval of 350 with 50 deviation, and a TERMINATE link to the recurring task.

Reply


Terms & ConditionsCookie settings