on 10-17-2015 12:40 PM
Dear Gurus ,
We have a typical requirement.
The user want to create maintenance plans and want that notification should be created on particular days i.e. every first Tuesday .
Or we can say that scheduling should be done based on days of the month.
This requirement is for few equipment s.
Kindly suggest how it is to be configured in the system.
Thanks
Himanshu
Hello Himanshu,
Scheduling plan - Every two months, the third Friday
Search Google for more, I think they are available mostly answered by Sebastian, through Packages as I remembered.
Regards
KJogeswaraRao
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Greetings Himanshu, Jogeswara,
As Jogeswara Rao Kavala mentioned, I'd prefer to use a Strategy-based plan with a specific Strategy and Packages to meet this requirement; the reason being that you avoid making actual changes to the system configuration and you can easily assess and contain the impacts, without any development.
With a Strategy-based plan you must account though, that a calendar month is not a multiple of a week, so sometimes you will have four, sometimes five Tuesdays in a month; So the cycle should effectively sometimes be 28 and sometimes 35 days.
You may either just start 28-day cycled plans and accept that you will periodically need to re-sync your plans to the calendar, or you may use a strategy with many one-off packages where you use offsets to steer into the first Tuesday of each month for scheduling; See the example I put in that thread: Scheduling plan - Every two months, the third F... | SCN
Using a factory calendar is also an option, although to my mind, it is easier to set up a Strategy, than a Factory Calendar just for the purpose of maintaining "few equipments"; If you choose to use this option, however, be aware of the specificity of transporting Factory Calendar settings, see this thread:
Hi Sebastian, Jogeswara
Thanks for your replies
I have done the settings as asked by you for Scheduling plan every first Tuesday of every month.
But when I am doing scheduling in IP 10 i am not getting the dates as attachment attached by you in your link provided.
So kindly guide whether I am doing something wrong in IP10.
Thanks
Himanshu
Can you elaborate which settings you have done, exactly, and how your problem in IP10 looks like?
Please also note, that in the original post you wrote about scheduling for a specific day of the month - for this, it is sufficient to use Key Date scheduling.
The setup you could have for the Strategy, Task List, Maintenance Plan and Schedule for a plan that you wanted to start from today to run every first Tuesday, for example, could look like this:
Note the offsets - first call is in two weeks and then at
subsequent dates after 4 or 5 week incrementing intervals.
Note that all Maintenance Packages are assigned.
Thanks a lot Sebastian,
It worked but still a issue persist.
I created the Plan accordingly and then mapped it in IP 30 and created a scheduler via SM36 to call Auto notification.
The notification should be generated on 02 November but it just called the Plan but do not generate any Notification.
Thanks
Himanshu
Hi Himanshu,
You need to use maintenance plan category only for Notification.
Create a Single Cycle Plan, with cycle / unit -7 days.
On scheduling you need to set the start day when you want to start like Tuesday, similarly system will schedule the calls every week based on the scheduling period you have chosen (6mon,1 year etc)
For Multiple Equipment, if you want to have the Notification generated, then you create maintenance items.
If you want to include in one order, then in the maintenance item you assign the object list.
Regards
Terence
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
100 | |
11 | |
11 | |
6 | |
6 | |
5 | |
4 | |
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.