Project Brief: Migrating ServiceNow to SAP for Giga's ERP System

This project brief outlines Giga's plan to migrate its Enterprise Resource Management (ERP) system from ServiceNow to SAP. It presents a comprehensive business case, detailing the reasons for the migration, including the benefits of cloud services like ease of use, data modernization, and future innovation readiness. The brief explores various migration options and expected benefits, such as improved integration and optimized inventory management. It also identifies potential risks, including security vulnerabilities like hard-coded SAP user accounts and insecure gateways, along with estimated costs and timelines. The scope statement defines project objectives, product deliverables (like system configuration documents and business process strategies), acceptance criteria, exclusions, constraints, and assumptions. The project aims to streamline business processes, enhance decision-making through data analysis, and align with company growth objectives. This document provides a detailed overview of the project's planning, execution, and potential challenges, offering a valuable resource for understanding the complexities of large-scale ERP migrations.

PROJECT BRIEF:
POSTER
Migrating from ServiceNow ERP to SAP
System for GIGA

Introduction
Businesses are going through several kinds of changes
nowadays and have been using the technological
advancements for this as well. With time, the technology
is advancing at several levels and so has been its
influence on the business as well (Jones and Soper 2015).
Business organizations have also been using the
technological advancements for their business systems as
technology is providing all kinds of positive impacts to the
business organizations in making the most effective and
economic solutions to the impending business problems
and providing the effortless solutions as well. This is the
same reason why Giga, an organization that mostly
specializes in providing services to the customers related
to internet are trying to create a new SAP system and also
engage the Software Development team at it. This poster
would enable the implementation plan followed by a
developed business case, scope management and the
organogram related to the development plan as well.
Organization Brief
Giga happens to be an organization that specializes in the IT related
products and services for its customers. This also includes a large
search engine that the organization provides to the customers. The
organization also has a workforce of about 200,000 employees
working at the same time and 421 offices operating all around the
world. The IT requirements of the organization is supported by the
Information Technology Asset Lifecycle Management Department or
the ITALM Department of the organization. They now want their
resources to imbibe the changes that are required to transform
their Enterprise Resource management System directly to the SAP
system that would be supported by the changing of the
environment from ServiceNow to SAP.
The organization is thinking about making SAP tools handle all the
departments within the organization, including the Finance,
Procurement and the Equipment Maintenance Team and the
inventory management of the organization.
SAP
IMPLEMENTATION

Reasons
The following can be the options that can be considered for
the migration of the ServiceNow systems to the SAP
systems for the inventory management in several
departments in Giga:
– Blocked stock to stock in quality inspection
– Blocked stock to unrestricted-use stock
– Stock in quality inspection to unrestricted-use stock
Benefits
The primary reasons why Giga would like to move to the
cloud services is due to the supporting factors that might
make the business gain all the benefits that the
organization possesses prior to the application. The
supporting factors would be as follows:
– The simplicity of use of the application structure
– The ease of use as provided by the interface of the
application running on a modern format based on
the internet and the innovative UI with modern
designs especially made for the enhanced user
experience.
– Modernization of data that would provide enhanced
value to the business
– The implementation has the potential of adding
value to the business by preparing it further for the
innovations to occur in future.
– The ease of transitioning to the on-premise cloud
Following are the expected benefits that can be gathered by the
migration of the ServiceNow systems to the SAP systems for the
inventory management in several departments in Giga:
– It would enable a complete integration of the
organization
– It would help the distributors in optimizing the
operations for the inventory and the warehouse (Fleig
and Maedche 2017)
– It just not provides the positivity and benefits to the
business, but also to the customers of the organization
as well
– This service would help the organization in providing a
detailed visibility of the supply chain for the entire
organization
– It would be the ultimate solution for both the
organization and the executives of the business handling
the organizational operations to provide an economic
strategy for the benefit of the organization as a whole by
Options

Risk
■There are 9 major risks that are present in the system. In case of
implementing ServiceNow to SAP will also be leading to
occurrence of major issues that are present in the system. The
risks are as follows: -
■Hard Coded SAP User is Active
■It is seen that if the malicious user connects a log in mechanism
of the SAP system as per the SAP GUI, it affects the user in a
direct manner. The main reason of this attack affecting the
functional process includes the imposters gaining access to the
hard coded username (SAP*) and password for gaining SAP_ALL
which will be privileging full control of the entire system.
■Insecure Gateway
■In this case the malicious user with the network connection in
the SAP system will be easily executing the arbitrary commands
that are present in the operating system. This will also be
ensuring the fact that proper assessment of the attackers that
will be used for sabotaging of the service might be acting as a
major risk. Hence wise installing malware and penetrate SAP
landscape can be performed.
■Critical Patches are not present
■In this case, the security researchers has been constantly
discovering and reporting vulnerabilities that are critical in
nature. In case the SAP releases the security patch, imposters
who use malicious software reads the corresponding SAP note
and hence wise they get to know to exploit the vulnerabilities
that are present in the system. In case the patch is not properly
installed the main aspect that is considered is that the system
will be at very high risk.
■Default passwords are provided
■It is seen that in case of SAP implementation, the main issue
that is seen is that most of the passwords that are provided are
default in nature. In this case the main aspect that is considered
is that it gets easier for the imposters to gain access to the data
that are present. With the help of the well-known credentials
and passwords, it will be getting easier for the imposters to gain
a complete control over the scenario.
■Users with the S_RFC*Authorization
■In this case the main aspect that can be considered includes the
fact that S_RFC* authorization is performed with the help of the
34,000 remote enabled function and hence wise critical
functional module will allow the user to create proper control of
the custom code. This will lead to high security risk in the SAP
server.

Estimated Cost
The estimated cost of
the project is £ 3 million
Estimated Time scale
The time that might be
required for completion of
the task is 127 days
Investment Appraisal
In this case the investment
that will be made will be
having a proper benefit in
long run. This will lead to the
fact that proper assessment
of the business
management will be getting
better

Scope Statement
■Objectives of the Project
■The primary objectives of ITALM in order to shift to the SAP
system are:
■1. To understand the best kind of software system that would
help in meeting the planning processes of the business.
■2. To increase the growth rate of profits for the company
based on the implementation of SAP and aligning them with
the requirements of the company.
■3. To estimate the data within the organization, analyze them
properly within the software package and making right
decisions for suitability of the company.
■Product Deliverables
■The Giga is considered as a large technology provider
company that mainly specializes in providing a wide range of
services and technical products. In the present system, ITALM,
which is one of the largest workforce of Giga, has planned to
move their existing systems from ServiceNow to SAP systems.
Hence, the certain kind of deliverables that would be included
during the transitioning to the SAP systems are discussed as
follows:
■1. The system developer who would be responsible for
assisting the company to implement SAP systems include a
Key data structure.
■2. A Business Blueprint document would need to be provided
before the development phase would initiate. The preparation
of the document would be planned by the project developer
who would have an entire idea of the cost structure and the
ways in which the transition procedure would begin.
■3. A system configuration document would also be need to be
supported within the deliverables. This document would
identify the type of systems that are present within the
company and their configurations. This document would help
in understanding about the necessary configuration of each
system that would be required before the installation
procedure of the SAP software.
■4. The procedures of the business processes and the strategy
undertaken for implementing the SAP systems would be
presented in a document. User manuals would also be need to
be prepared in order to help users in understanding the
processes in which the new system would need to be used.

Project Scope statement
Acceptance Criteria
The new SAP system would only be accepted only after a proper
kind of approval from the management team of the company.
After a proper implementation of SAP systems, they would be
checked within each system based on proper functioning of the
systems and meeting with business requirements.
■ EXCLUSIONS
■ The significant exclusions that are to be adhered by
the overall management committee of the organization, Giga
which is associated with the implementation of SAP is
considered to be the fact of improper management (Blount et
al., 2016). The improper management in regards to the
implementation procedure will lead to a failure of the overall
job which in turn will not help the organization to cope with
the scope as well as the goals as set by the organization.
Moreover, the ineffective communication among the various
stakeholders that are associated with the overall
implementation procedure will decrease the overall
connections among the different stakeholders associated with
the implementation and this will tend to the implementation
to be failed. In addition to this the support provided in the
user end must also be effective so that the organization may
be able to keep a track of the feedback as well as satisfaction
of the customers that will amplify the business of the overall
organization (Ramdass, 2017). However, there is also a
significant section that is to be excluded within the
implementation procedure that the overall implementation
procedure must align with the requirements as well as the
change of the requirements must also be kept in mind while
executing the implementation procedure. Thus the significant
points that are highlighted in respect to the implementation
of SAP at the organization of Giga.

CONSTRAINTS
■ The noteworthy points that are to be
expected to take into consideration by the
organization of Giga and are to be kept in mind while
implementing SAP are depicted as follows:
■ 1. Resource-Intensive Nature in respect to the
standard form of the ERP: This is the significant
section that identifies that the implementation of
SAP strictly requires appropriate number of workflow
allocation, the training module is to be intensive as
well as the commitment that is made by the higher
authority of the organization (Kalaimani, 2016).
Moreover, there must be significant adherences
which may cope with the customization of the SAP
that may be required at any point of time within the
implementation procedure.
■ 2. Long time frame for implementation: The
significant time frame that is required for the
implementation of SAP requires much more time in
respect to the implementation of any other software
package (Ganesh and Mehta, 2016). The usage of
the resources by the overall management of the
organization of Giga must be carried out effectively
as this may tend to affect the organization in a
negative manner if the resources are used for a
longer period of time.
■ 3. High Cost: The significant implementation of SAP
adheres the fact of high budget in respect to the fact
of the customization, training, resources as well as
some hidden costs. This would require the financial
constraints to play a significant role in respect to the
implementation of SAP at the organization of Giga.
Moreover, the financial constraints adhered by the
various stakeholders is depicted to one of the overall
financial constraint that are to be adhered by the
organization of Giga.
Assumption
■ Assumption 1: SAP will be supported in a proper
manner
■ Assumption 2: The cost that is estimated will be
efficient
■ Assumption 3: Task will get completed within the
deadline

Assignment 2 b
Organogram
Personn
el
Designat
ion
Contac
ting
person
Mode of
communi
cation
Contact
details
Leander
Cooper
Director Directo
r of
softwar
e
busines
s
Mail, Face
to face
Please fill
Rahul
Samuels
Director
of
software
business
Directo
r
Mail,
Phone Call
Please fill
Alisha
Roy
Business
Analyst
Directo
r of
softwar
e
busines
s
Call Please fill
Team Business
Team
Busines
s
Analyst
Face to
face, Mail
Please fill
Communication Plan

Network Diagram

WBS
Activity List
SAP implementation
Project Staring phase
Initiating the project
Planning the project
Sectioning of the
project
Data gathering phase
Gathering the data
Collecting data in
secondary method
Collecting data in
primary method
Implementation phase
SAP implmentatioj
criteria
understanding
Develop system
environment
Perform quality
check
Project ending phase
perform Organization
change management
Busienss process
analysis
Approving the
strategy
SAP Implementation 127 days
Project Staring phase 45 days
Initiating the project 15 days
Planning the project 14 days
Sectioning of the
project 16 days
Data gathering phase 26 days
Gathering the data 8 days
Collecting data in
secondary method 8 days
Collecting data in
primary method 10 days
Implementation phase 42 days
SAP implementation
criteria understanding 12 days
Develop system
environment 12 days
Perform quality check 18 days
Project ending phase 32 days
perform Organization
change management 10 days
Business process
analysis 9 days

Activity Cost
incurred
( £)
Buying license
of SAP
10000000
Storage
Required
5000000
Training 20000000
Total Budget 30000000
Budget Breakdown

Risk Assessment
Number Risk Cell references
R1 Performance Issue: The quality of the SAP
system would not be able to meet with the
expected factors of performance.
D5
R2 Technical Issue: The SAP system would incur
errors and other technical glitches during
working procedures.
C3
R3 Deadline Issue: The SAP system would not be
implemented within the estimated time period
A2
R4 Quality Issue: The SAP system might not be as
per the expectation of the business and thus
they might not be as per proper quality.
D1
Risk Identification D (Certain) C (Likely) B (Moderate) A (Unlikely)
5 (Fatal) R1
4 (Major)
3 (Lost Time) R2
2 (Minor) R3
1 (Trivial) R4
Quality Plan
• The quality plan will be
including the likes of proper
training of the employees who
will be using the likes of SAP
• Security related issues must
have been maintained in a
proper manner

References
Fleig, C. and Maedche, A., 2017. Towards the Design of a Process
Mining-Enabled Decision Support System for Business Process
Transformation. In CAiSE-Forum-DC (pp. 170-178).
Jones, P. and Soper, T., 2015. Implementing SAP Business Planning
and Consolidation. SAP PRESS.
■ Blount, Y., Abedin, B., Vatanasakdakul, S. and Erfani, S., 2016.
Integrating enterprise resource planning (SAP) in the accounting
curriculum: a systematic literature review and case study.
Accounting Education, 25(2), pp.185-202.
■
■ Ramdass, K., 2017, July. An Investigation into the Implementation
of New Versions of Information Systems Implementation. In 2017
Portland International Conference on Management of
Engineering and Technology (PICMET) (pp. 1-5). IEEE.
■
■ Kalaimani, J., 2016. Implementing SAP with ASAP 8 Agile
Methodology. In SAP Project Management Pitfalls (pp. 25-45).
Apress, Berkeley, CA.
■
■ Ganesh, L. and Mehta, A., 2016. Understanding cloud based ERP
implementation in light of conventional ERP implementation at
Indian SMEs: A case study. Available at SSRN 2782244.
■
■ Katona, V. and Hoffer, I., 2018. Examples of SMEs value creation
in Industry 4.0 using VE methodology.
■ (Katona and Hoffer, 2018)
■ Chofreh, A.G., Goni, F.A., Ismail, S., Shaharoun, A.M., Klemeš, J.J.
and Zeinalnezhad, M., 2016. A master plan for the
implementation of sustainable enterprise resource planning
systems (part I): concept and methodology. Journal of cleaner
production, 136, pp.176-182.
■ (Chofreh et al., 2016)
■ Müller, O., vom Brocke, J. and Uhl, A., 2016. The Evolution of SAP
Services. Business Transformation Essentials: Case Studies and
Articles, p.189.
■ (Müller, vom Brocke and Uhl, 2016)
■ Syaiful, B. and Gunawan, W., 2017, January. Assessing Leading
ERP-SAP Implementation in Leading Firms in Indonesia. In Journal
of Physics: Conference Series (Vol. 801, No. 1, p. 012032). IOP
Publishing.
■ (Syaiful and Gunawan, 2017)

THANK
YOU