on 09-18-2015 10:30 AM
Hello,
I've read it is not possible to schedule multiple work modes for systems (workcenter "technical administration" > "work mode management" in solution manager 7.1 SP12). So here's my question: what is the best practice in following example:
In our company:
Work mode "peak business hours" scheduled for all systems,weekly from Monday - Friday from 08:00 to 17:00
Work mode "non peak business hours" scheduled for all systems, weekly from Monday - Friday from 17:00 to 08:00 and Saturday and Sunday from 00:00 to 23:59
Now, if there is a "planned downtime" on Friday from 15:00 to Saturday 08:00 for all systems, what is the best way of planning this work mode "planned downtime" the simplest, fastest, easiest way?
a BIG thanks for any help!
Best regards,
Kenny
Hello,
Everything is OK now. We were managing our work modes in own language (dutch). When logged on in English, everything seems to work the way it should work.
Thanks for all your replies.
Best regards,
Kenny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kenny,
How did you approach managing downtime/maintenance work modes in the end?
Do you delete the existing work modes?
Or do you adjust the times either side, creating a time window gap for a new downtime/maintenance work mode?
It does seem a little strange that we can't just add a maintenance work mode on top of an existing work mode. That would make it so much easier.
Thanks,
Darryl
Hi Darryl,
currently we run Solution Manager 7.1SP12 and scheduling of workmodes work reasonably fine.
Why reasonably? Because we can schedule work modes on top of each other and the last one scheduled gets the upper hand. But solman can only "overrule" an existing work mode if it's not "in process", then we need to remove this one in order to schedule for example a downtime.
OK thanks Kenny.
Yes, I see the same issue with "In Process" work modes.
However, if I delete the "In Process" work mode, then technical monitoring will stop.
This causes an additional headache for me as I've configured work modes for every part of the day.
E.g:
Non-business: 00:01 - 08:59
Normal business hours: 09:00 - 18:00
Non-business: 18:01 - 23:59
So, I've found that I can simply adjust the end-time of the "In Process" work mode, to create a gap (only needs 1 minute gap), into which I can then create a 1 minute downtime work mode, then "Add Phase" to the downtime work mode to extend it accordingly.
The additional phase extends over any other scheduled work modes (as you've found).
So I don't lose any monitoring in the time between the current "In Process" work mode and the start of the downtime work mode.
Darryl
Hi
Go to Technical administration in solman workcenter
Select the Work mode management
Select the technical system
Here you can schedule the workmode or add new phase to planned downtime
Then enter the workmode specific details for date and time etc.
Please check the below link for step by step guide
TechAdm_Overview - Technical Operations - SCN Wiki
Workmode FAQ
http://wiki.scn.sap.com/wiki/display/TechOps/Work+Mode+Management+FAQ's
Thanks
Rishav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rishav,
And if there is already a work mode active for all systems, like "peak business hours". Do we need to remove this work mode "peak business hours" first for ALL systems, reschedule this work mode "peak business hours" for ALL systems, and then add the workmode "planned downtime" for ALL systems??
To me, it looks like this this process is way too complicated and takes a lot of effort? Is there an easier method?
Hi
You can run for multiple systems simultaneously as you can see below
http://help.sap.com/saphelp_sm71_sp05/helpdata/en/62/28c8da113344eaa774f382ac22c53e/content.htm
Hence, first make it as planned downtime and remove the peak business hours for same in the settings.
Thanks
Rishav
User | Count |
---|---|
86 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.