Many clients used IP30 to set call horizon. They set call horizon as 100% at individual maintenance plan level and then use the field 'Interval for Call Objects' of IP30 to release the maintenance calls dues for next 'n' days. If you are following such practice, you may need different batch run for daily / monthly maintenance plans.
Due date interval of the work orders generated is also an important parameter for you to decide how many batches of IP30 you need. The example below may explain this better:
1. Daily Maintenance Plan - Generate work orders on every Thursday due next week with SLA (due date interval) of 5 days.
Identify daily maintenance plans with their strategy in IP30, set 'Interval for Call Objects = 10 days, schedule batch job every Thursday with weekly cycle.
2. Monthly and above Maintenance Plan - Generate work order once every month (5 days before end of month) due next 35 days with SLA (due date interval) of 30 days
Identify monthly and above maintenance plans with their strategy in IP30, set 'Interval for Call Objects = 30 days, schedule batch job 5 days before end of every month.