Reply from LCC352 on Mar 26 at 9:24 AM I think you've asked an extremely broad question, but here are suggestions. It is by no means a complete plan. As many have said, you need to formulate the specific plan for your particular projects, but here are some components you should have:
Communication - All cutover plans I've worked with cover specific communications for the cutover period. These go to end users, business and IT senior management, if appropriate, owners of other systems that touch the SAP system, etc. Decide on who, what, when, where and how.
Checks - I've always had a section that deals with different checks to make. What are these? They're things like making provision for everyone on the teams to have the right level of security in the environments, that all passwords (like DDIC) are known, that SAP is aware of your schedule and is ready to jump in, etc.
Pre-Downtime Items - these include doing anything you can before you absolutely have to take the system offline. It also might include taking snapshots of reports for before/after checks to ensure data integrity. I've worked projects where pre-downtime started 7 days before the actual offline upgrade started.
Downtime activities - these are the steps taken during the downtime itself. In most cases, this part of the plan will be hour-by-hour, and communications are sent at key points during this process. This will also carry the backout procedure - what happens if it all goes bad - as well as when that go/no-go needs to be called. There may actually be several go/no-go points along the way. I've always communicated all go/no-go points to ensure there is adequate knowledge throughout.
Post-Downtime activities - these include the processes required to get everything back up and running normally. Before the users are allowed back in, all the pre-downtime reports that were run will be run again and compared for one last check. If jobs have been held, these get released in some fashion. You might require a speciic plan around that release. Communications go out again to those involved in interfaces and such.
In short, there are lots of things to plan, lots to get circulated to many people, and as I said, the cutover itself should be an hour-by-hour plan to see if you are going to come in on time.
Good luck.
- Lou
| | | ---------------Original Message---------------
From: sziaabbas
Sent: Sunday, March 24, 2013 1:12 PM
Subject: Cutover Strategy and Sequencing
Dear All
We are nearby the final preparation stage for our client. Before we actually move to Cut-Over Strategy, I need your help in identifying the correct strategy.
We are implementing following modules for our client;
FI, CO, MM, SD, PP, PM and QM
It will be great if I can have 'sequencing' of cut over activities along with the correct cutover strategy.
Please suggest
Regards
Saied. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
