- 4Implementation processes
Introduction[edit]
Overview[edit]
Concept | Definition |
---|---|
CHANGE MANAGEMENT | Activities involved in (1) defining and installing new values, attitudes, norms, and behaviors within an organization that support new ways of doing work and overcome resistance to change; (2) building consensus among customers and stakeholders on specific changes designed to better meet their needs; and (3) planning, testing, and implementing all aspects of the transition from one organizational structure or business process to another. (www.gao.gov) |
CHANGE MANAGEMENT DOCUMENTATION. | All documentation that is required and being delivered whilst performing change management, e.g. the functional test cases and all the other documents a new end-user of SAP requires and the various tools and approaches used to manage change by the TSO. (Anderson, 2003) |
COST OF OWNERSHIP ANALYSIS | Determination of where and when the costs are inquired within the context of the SAP solution stack and ongoing operations. The analysis addresses all internal and external costs, both one-time as well as recurring (Anderson, 2003) |
CUTOVER | The process of transitioning from one system to a new system |
DATA CENTER | A data center is a facility used for housing a large amount of electronic equipment, typically computers and communications equipment. |
DATA CENTER REQUIREMENT | A requirement for the SAP data center, i.e. a physical requirement like power requirements, a rack requirement, a network infrastructure requirement or a requirement to the network server. (Anderson, 2003) |
DISASTER RECOVERY (DR) REQUIREMENT | Requirement that focuses on downtime that lasts many hours to days or even weeks (Anderson, 2003) |
FUNCTIONAL TEST CASE | A set of conditions or variables under which a tester will determine if a certain business process works |
HIGH AVAILABILITY (HA) REQUIREMENT | Requirements that describes the amount of time that the system needs to be available to satisfy the needs of the users. (Anderson, 2003) |
INSTALLATION DOCUMENTATION | All documentation related to the installation of an end-to-end SAP solution (Anderson, 2003) |
OPERATIONS MANUAL | The collection of current state system documentation, day-to-day and other regularly scheduled operations tasks, various installation and operations checklists and how-to process documents. (Anderson, 2003) |
SAP | SAP SE is Europe's biggest software company. The head office is in Walldorf, Germany. SAP was founded in 1972 as Systemanalyse and Programmentwicklung ('Systems Analysis and Program Development') by five former IBM employees in Mannheim, Germany. |
SAP IMPLEMENTATION PROJECT PLAN | A comprehensive project plan that contains all products that are delivered whilst performing an SAP implementation project (Anderson, 2003) |
SOLUTION STACK | Set of software subsystems or components needed to deliver a fully functional solution, e.g. a product or service. |
SOLUTION STACK PARTNERS LIST | A list of all vendors that deliver the products that make up the SAP solution stack (Anderson, 2003) |
SOLUTION VISION | A vision of the future-state of the SAP solution (Anderson, 2003) |
STRESS TEST PLAN | A test plan that is focused at determining the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. |
TEST PLAN | A detail of how the test will proceed, who will do the testing, what will be tested, in how much time the test will take place, and to what quality level the test will be performed. (IEEE 829) |
TRAINING | The acquisition of knowledge, skills, and attitudes as a result of the teaching of vocational or practical skills and knowledge that relates to specific useful skills (www.practicalsap.com) |
TRAINING PLAN | Consisting of training units, a training plan is the result of hierarchical decompositions of a training goal, tailored according to the learning preferences and prior knowledge of the trainee. A plan is the means by which the trainee satisfies the goal. (www.ece.eps.hw.ac.uk/) |
TSO | Technical Support Organization. The people that are committed to implementation and management of SAP. (Anderson, 2003) |
TSO CHART | A chart that depicts the structure of the TSO. (Anderson, 2003) |
Activity table[edit]
Activity | Sub-Activity | Description |
---|---|---|
Project preparation | Craft solution vision | Refine and communicate a SOLUTION VISION of the future-state of the SAP solution, to sketch a design that meets both business and financial requirements. The focus should be on the company's core business and how the SAP solution will better enable that core business to be successful. Some of the guidance and key requirements for how to put together an ERP and SAP business case for ROI, business benefit, and success includes focusing on competitive pressures, value propositions, and how the solution enables success. |
Design and initially staff the SAP TSO | Design and staff the key positions of the SAP Technical Support Organization (TSO), the organization that is charged with addressing, designing, implementing and supporting the SAP solution. | |
Sizing and blueprinting | Perform cost of ownership analysis | Perform a COST OF OWNERSHIP ANALYSIS to determine how to get the best business solution for the least money i.e. to determine where and when the costs are incurred within the context of the SAP solution stack. |
Identify high availability and disaster recovery requirements | Determine all HIGH AVAILABILITY and DISASTER RECOVERY REQUIREMENTS, to plan what to do with later downtime of the SAP system | |
Engage SAP solution stack vendors | Select the best SAP hardware and software technology partners for all layers and components of the SAP SOLUTION STACK, based on a side-by-side sizing comparison | |
Staff TSO | Staff the bulk of the TSO, i.e. fill the positions that directly support the near-term objectives of the implementation, which are to develop and begin installation/implementation of the SAP data center. | |
Execute training | Train the various members of the SAP TSO, like data center specialists, high availability specialist and network specialists and train the end-users to give all the required SAP knowledge and skills | |
Setup SAP DATA CENTER | Build a new SAP DATA CENTER facility or transform the current data center into a foundation capable of supporting the SAP SOLUTION STACK | |
Perform installations | Install the (My)SAP components and technological foundations like a web application server or enterprise portal. | |
Round out support for SAP | Identify and staff the remaining TSO roles, e.g. roles that relate to help desk work and other such support providing work. | |
SAP functional development | Address Change Management | Develop a planned approach to the changes in the organization. The objective is to maximize the collective efforts of all people involved in the change and minimize the risk of failure of implementing the changes related to the SAP implementation. |
Address SAP systems and operations management | Create a foundation for the SAP systems management and SAP computer operations, by creating a SAP OPERATIONS MANUAL and by evaluating SAP management applications. | |
Perform functional, integration and regression tests | Test the SAP business processes, by executing functional tests to ensure that business processes work, integration tests to ensure that the organization's business processes work together with other business processes and regression tests to prove that a specific set of data and processes yield consistent and repeatable results. | |
Final Preparation | Perform systems and stress tests | Plan, script, execute and monitor SAP STRESS TESTS, to see if the expectations of the end users, defined in service level agreements, will be met. |
Prepare for cutover | Plan, prepare and execute the CUTOVER, by creating a CUTOVER PLAN that describes all cutover tasks that have to be performed before the actual go-live | |
Go Live | Turn on the SAP system for the end-users |
Implementation processes[edit]
Project preparation[edit]
Business Process Procedure Template
Sizing and blueprinting[edit]
- SAP Network Specialists
- SAP Database Administrators
- SAP Security specialists
- Documentation specialists
- Et cetera
- Physical requirement like power requirements
- Rack requirement
- Network infrastructure requirement or
- Requirement to the network server.
- R/3 Enterprise — Transaction Processing
- mySAP BI — Business Information Warehouse
- mySAP CRM — Customer Relationship Management
- mySAP KW — Knowledge Warehouse
- mySAP PLM — Product Lifecycle Management
- mySAP SCM — Supply Chain Management
- mySAP SEM — Strategic Enterprise Management
- mySAP SRM — Supplier Relationship Management
- mySAP HCM — Human Capital Management
Realization[edit]
- End-user requests
- End-User regular activities
- Data center team
- DBA group
- Functional testing: to test using functional use cases, i.e. a set of conditions or variables under which a tester will determine if a certain business process works
Final preparation[edit]
- Review and update all systems-related operations procedures like backup policies and system monitoring
- Assign ownership of SAP's functional processes to individuals
- Let SAP SE do a GoingLive check, to get their blessing to go live with the system
- Lock down the system, i.e. do not make any more changes to the SAP system
Go live & Support[edit]
Critical success factors[edit]
See also[edit]
References[edit]
- Lui, Kim Man (2008). 'Rescuing Troubled Software Projects by Team Transformation: A Case Study With an ERP Project'. IEEE Transactions on Engineering Management 55 (1): 171 - 184. doi:10.1109/TEM.2007.912933.
- Anderson, G.W. (2003). SAP Planning: Best Practices in Implementation. Sams Publishing
- Francalanci, C. (2001). Predicting the implementation effort of ERP projects: empirical evidence on SAP/R3. Journal of information technology, Vol. 16, Issue 1, pp33–48.
- Hirt, S. G., Swanson, E. B. (1999). Adopting SAP at Siemens Power Corporation. Journal of Information Technology, Vol. 14, Issue 3, pp243–251.
- Krumbholz, M., Maiden, N. (2001). The implementation of enterprise resource planning packages in different organisational and national cultures. Information systems, Vol. 26, Issue 3, pp185–204.
- Sankar, C.S., and Rau, K-H., (2006). Implementation Strategies for SAP R/3 in a Multinational Organization, Cybertech Publishing, Hershey, PA, 2006.
- Xue, Y., Liang, H., Boulton, W.R., Snyder, C.A. (2005) ERP implementation failures in China: Case studies with implications for ERP vendors. International journal of production economics, Vol. 97, Issue 3, pp279–295.
- Yusuf, Y., Gunasekaran, A., Abthorpe, M.S. (2004). Enterprise information systems project implementation: A case study of ERP in Rolls-Royce. International journal of production economics, Vol. 87, Issue: 3, pp251–266.
- Hackett, Mike (2017) 'How to Know It's Time to Replace Your SAP Implementation Partner'. https://clarkstonconsulting.com/insights/switching-sap-implementation-partners/
![Business Process Procedure Template Sap Center Business Process Procedure Template Sap Center](/uploads/1/2/4/7/124784922/501599294.jpg)
Process diagrams are visualizations of any sort of step-by-step process. They are usually created as flowcharts, with shapes that represent steps in the process connected by arrows that indicate the next step.
Visio has a lot of process diagram templates, but they all can be put into one of two categories:
General purpose process diagrams
If you want to diagram a process and you don’t have a specific methodology you want to follow, one of these three templates should work well: Cara google book idm key.
- Basic Flowchart
- Cross Functional Flowchart
- Work Flow Diagram
To find these templates:
- Click the File tab.
- Click New.
- Click Flowchart.
Basic Flowchart
The Basic Flowchart template is useful for a broad range of business processes, where each step can be represented using simple geometric shapes.