InterviewSolution
| 1. |
What Is Known As The ‘go-live Check’? |
|
Answer» The ‘Go-Live Check’ is done just before you cut over to ‘live’ (production) operation in a project. This is to test whether the system is properly configured to meet the requirements of the business. The check includes DETECTING problems in the
First, the Go-live Check involves an analysis of the major system components of the R/3 installation with regard to system consistency and reliability. For this, SAP experts log on to your R/3 system VIA a remote connection, inspect the configuration of individual system components, and PROVIDE valuable recommendations for system optimization. By analyzing the individual system components before production start up, SAP can considerably improve the availability and performance of the customer’s live system. In addition, the technical application analysis provides information on how to speed up the core processes within R/3. Secondly, the transactions with high resource consumption are searched for and necessary adjustments are made. Thirdly, the changes from the two prior sessions are validated. This check is PERFORMED in the productive operation system. After a system GOES live, some fine tuning and eliminating of potential bottlenecks is still necessary. This is carried out four weeks after ‘going live’ with the R/3 System. The ‘Go-Live Check’ is done just before you cut over to ‘live’ (production) operation in a project. This is to test whether the system is properly configured to meet the requirements of the business. The check includes detecting problems in the First, the Go-live Check involves an analysis of the major system components of the R/3 installation with regard to system consistency and reliability. For this, SAP experts log on to your R/3 system via a remote connection, inspect the configuration of individual system components, and provide valuable recommendations for system optimization. By analyzing the individual system components before production start up, SAP can considerably improve the availability and performance of the customer’s live system. In addition, the technical application analysis provides information on how to speed up the core processes within R/3. Secondly, the transactions with high resource consumption are searched for and necessary adjustments are made. Thirdly, the changes from the two prior sessions are validated. This check is performed in the productive operation system. After a system goes live, some fine tuning and eliminating of potential bottlenecks is still necessary. This is carried out four weeks after ‘going live’ with the R/3 System. |
|