on 04-15-2011 12:52 PM
What is the offset and lead float in days and follow up float in days of maintenance strategy?
Hi James,
I might have given intrepretation in wrong way.
Actually call horizon will be used for whole strategy. Its not package based.
For example, monthly package should be called 3 days in advance & yearly package should be called 36 days in advance, etc., then call horizon can be defined. As all the packages are having same % of call object advancement (90 %), that percentage can be defined in call horizon.
But in some case, monthly package 3 days advancement is acceptable to plan the resources. But for yearly packages, 36 days advancement in unneccessary. That will keep the outstanding orders list for long time. Thus when we dont have common % for call object advancement, instead of call horizon, these offsets can be defined in packages.
Like for monthly package, define offset as 3 days. For yearly package, define offset as 10 days. So call object will be created in advance with reference to offset.
In this case, call horizon is not required.
I hope I am clear now,
Regards,
Maheswaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Its not like over ride of Call Horizon. If both are mentioned, both will be taken in to account.
Based on Call Horizon, dates will be advanced. Then based on float, start date in order will be advanced again.
For example, actual call date with 100 % call horizon is 21.05.2011.
If you give call horizon as 80 %, then date would be 15.05.2011. If lead float is 3 days, then order start date will be 12.05.2011.
I hope now this is clear.
Regards,
Maheswaran.
Hi,
Offset => For example, you have maintenance package of 3 months (Quarterly) once, but first call needs to be created in another 2 months & subsequent calls can be created with the frequency of 3 months, then offset would be 2 months.
Lead Float => This is almost same like Call horizon. Based on Call horizon %, call objects will be created in advance. If you maintain 90%, for monthly frequency, call object will be created 3 days before. But as this call horizon is applicable for yearly frequency as well, yearly call object will be created 36 days advance which is not required. So that, for each package, based on the period of resource planning, days will be mentioned, so that call object will be created in advance based on the package but based on whole strategy.
Follow-up float => This is to postpone the call object end date in terms of days. This is to provide some Cushion on completion of activity.
Regards,
Maheswaran.
Edited by: Maheswaran.K on Apr 15, 2011 2:05 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
7 | |
7 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.