Rollout project

Question

hi friends,
can somebody explain in a rollout project
what will happen to entp structure?
what will happen to blue print ie as is and to be
what will happen to document types will it be all the same
whether the same team will be there
what are all mandatory things in a rollout project
if it is all same, we only do the configuration for the particular country related configurations or how
thanks for answering

Answer 1

Varada,
In RollOut Also The ASAP methodology covers 5 stages namely:
Stage 1: Project Preparation
Stage 2: Business Blueprint
Stage 3: Realization
Stage 4: Final Preparation
Stage 5: Go Live & Support (Rollout)
Stage 1-Project preparation
The core activities of this project include:
• Establish project teams
• Conduct kick-off meeting to confirm the project scope
• Develop Project Charter
• Perform review on all technical requirements of the project
Stage 2-Business Blueprint
The objective of this stage is to obtain a clear precise understanding of the detail
functional requirements
The major activities during this stage are as follows:
• Develop System functional requirements
• Develop System‘s data conversion and authorization strategy
• Identify training needs
• Determine reporting requirements
• Determine interface requirements
• Initiate change readiness Assessment
Stage 3: Realization
The project teams are focusing on the configuration of the SAP modules using agreed functional requirements. The core activities that are being carried out at this stage include:
• Configure SAP modules/develop customized modules
• Develop forms, reports and interfaces
• Establish profiles for authorization
• Implement data conversion and migration plan
• Setup training environment
• Conduct awareness program
• Develop change infrastructure; conduct change management activities relating to
communication and role definition
Stage 4: Final Preparation
Among the core activities to be carried out at this stage include:
• Develop cut-over and go-live plan
• Develop standard operating procedures
• Develop offline procedures
• Conduct end-user training for users at the pilot site
• Complete the preparation of the production environment
• Conduct communication and acceptance program
Stage 5: Go Live & Support (Rollout)
The final stage of the project relates to the roll out.. ie nothing but GO Live..
The last phase of the implementation project is concerned with supporting and optimizing the operative R/3 System, both the technical infrastructure and load distribution as well as the business processes. Activities such as the following are carried out:
Production support facilities are defined, for example, checking system performance on a daily basis
Validation of business processes and their configuration
Follow-up training for users
Signoffs, etc.
=====
Rollout Roadmap
The Rollout Roadmap has as its goal the creation of a local productive reference system and, in the case of distributed systems, the provision of a link to a central productive system in order to, for example, set up and maintain R/3 master records.
The Rollout Roadmap speeds up the implementation process in the local units, so that – depending on the enterprise's requirements – entire implementation series can be carried out. Redundant project activities can thus be pinpointed and avoided. The advantages of this roadmap are:
The realization of groupwide implementation standards, through an efficient rollout in the local units
A rollback procedure for the exchange of general experiences, which can then be incorporated into the template. In this way the changes are passed on to the local units quickly and comprehensively.
refer to the links below...
http://www.sapfans.com/sapfans/asap/be_08_e.htm
http://www.edgewater.com/Industries/Manufacturing/ManufacturingCaseStudies/caseStudies_finePaper.htm
REAWRD IF U FINDS HIS AS USEFUL..
Regds
MM