SAP Implementation Project Plan For Dai-Ichi Corporation Oceania Division

Background of the Project

Discuss about the IT Management for SAP Implementation for Dai-Ichi.

SAP is an enterprise resource planning software that provides a very new dimension to the large scale business organizations who seek efficient and integrated business platforms. There are several methods of implementation for SAP – it can either be implemented in the internal database of an organization where it integrates all the various working features of the system or it can be integrated with the cloud platform. In this case of integration with cloud, it uses the cloud storage interface to execute all operations and store and manage all types of business data.

In this report, a project plan has been developed for the implementation of SAP in the Oceania division of Dai-Ichi Corporation.

This background of the project involves implementation of SAP in the business system of Oceania division of Dai-Ichi Corporation. It is an international business organization that has extensive networks over all major countries. Furthermore in the European headquarter of the company, SAP has already been implemented and the business processes in all of Europe have been integrated together. Now, the management team has decided to implement SAP in the Oceania division as well, which will very soon commence in Australia. Furthermore, in order to avoid the problems arising due to time differences between Australia and Europe, it has been decided that the SAP instance will be deployed in the cloud platform making it easier to be managed from various time zones. Accordingly, contract has been agreed with Amazon for getting access to the AWS Cloud Platform for the implementation of the SAP. Further planning and requirement analysis are required in order to proceed with the actual part of the project.

The objectives of the project are as follows.

• To gain access to a cloud computing service
• To develop a platform for SAP implementation
• To implement SAP in the existing business system
• To connect the database server with the SAP system
• To host the SAP system in the cloud computing service procured

Some of the high level technical requirements for this project are as follows.

Database Server – This server will be required to create a central database for the company where all the relevant business information will be stored and updates according to the changes.

Application Server – This server is needed to run the entire software system according to the pre set requirements. Each application or function of the system cannot be run unless there is an application server for supporting the functions.

Web Services Layer Server – This server is needed to add specific functions or features of the system on a particular platform. Furthermore, it can be integrated with various web services like xml, html and others so that the specific functions can be added to the overall desired system.

X 86 Images – These images will be required in various parts of the overall cloud infrastructure. These images will add to the visual aspect of the system as well as make the system more informative and helpful.

JIRA – JIRA is a software that will be utilized for various functions like tracking of a bug, issue and others whereas it can also be utilized for various functions related to project management.

SAP Cloud Instance – SAP Cloud Instance will be the actual system that will be implemented for the company. Before implementation, it will be needed to gain a site license in Australia.

Objectives of the Project

There are a number of tools suitable for the project management controls to be used in this project. Some of the most suitable tools to be utilized are as follows.

Cost Benefit Analysis – This tool is to be utilized to analyze the actual cost benefits that can be gathered from the project. This will also help to estimate the baseline costs and estimated profit percentages to be expected from the outcome of the project.

Critical Path Analysis – This tool can be utilized to determine the shortest time period within which the project can be completed. Furthermore, it also helps to determine different phases of the project can be executed together since they are not interdependent on each other.

The resources of the project are shown as follows.

Resource Name	Type	Max. Units	Std. Rate
Project Manager	Work	100%	$2,000.00/day
SAP Expert (Paulo)	Work	100%	$2,000.00/day
Cloud Architect	Work	100%	$7,500.00/mon
SAP Expert (June)	Work	100%	$7,500.00/mon
LAMP Stack Specialist	Work	100%	$3,500.00/mon
Linux Administrator	Work	100%	$3,250.00/mon
X 86 Image	Work	100%	$2,750.00/mon
SAP Cloud Instance	Material		$200,000.00
JIRA	Material		$50.00
Travel and Accommodations for Paolo	Work	100%	$10,000.00/mon

The budget of the project as per the duration of the tasks is shown in the following table.

Task Name	Duration	Start	Finish	Resource Names	Cost
SAP Implementation for Dai-Ichi Corporation	60 days	Mon 09-04-18	Fri 29-06-18		$267,228.13
Project Initiating	6 days	Mon 09-04-18	Mon 16-04-18		$16,021.88
Management Meeting and Discussions	0.25 days	Mon 09-04-18	Mon 09-04-18	Cloud Architect, LAMP Stack Specialist, Linux Administrator, Project Manager, SAP Expert (June),SAP Expert (Paulo)	$1,271.88
Reach a Proposed Outcome Decision	0.25 days	Mon 09-04-18	Mon 09-04-18	Project Manager	$500.00
Get Opinion from Company CEO	0.25 days	Mon 09-04-18	Mon 09-04-18	Project Manager	$500.00
Start the Project after Approval	0.25 days	Mon 09-04-18	Mon 09-04-18	Project Manager, Travel and Accommodations for Paolo	$625.00
Determine the Scope of the Project	1 day	Tue 10-04-18	Tue 10-04-18	SAP Expert (June), SAP Expert (Paulo)	$2,375.00
Make Assumptions regarding Certain Factors	0.5 days	Wed 11-04-18	Wed 11-04-18	SAP Expert (June), SAP Expert (Paulo)	$1,187.50
Find Cost Constraints	0.5 days	Wed 11-04-18	Wed 11-04-18	SAP Expert (June), SAP Expert (Paulo), Project Manager	$2,187.50
Find Constraints Related to Schedule	0.5 days	Thu 12-04-18	Thu 12-04-18	SAP Expert (June), SAP Expert (Paulo),  Project Manager	$2,187.50
List the High Level Requirements	0.5 days	Thu 12-04-18	Thu 12-04-18	SAP Expert (June), SAP Expert (Paulo)	$1,187.50
Create the Team for the Project	2 days	Fri 13-04-18	Mon 16-04-18	Project Manager	$4,000.00
Project Planning	2 days	Tue 17-04-18	Wed 18-04-18		$4,593.75
Develop the Project Charter	1 day	Tue 17-04-18	Tue 17-04-18	Project Manager	$2,000.00
Estimate Budget for Project	0.25 days	Wed 18-04-18	Wed 18-04-18	Project Manager	$500.00
Estimate Schedule for Project	0.25 days	Wed 18-04-18	Wed 18-04-18	SAP Expert (June), SAP Expert (Paulo),  Project Manager	$1,093.75
Approve Budget and Schedule	0.25 days	Wed 18-04-18	Wed 18-04-18	Project Manager	$500.00
Minor Modifications on the Plan	0.25 days	Wed 18-04-18	Wed 18-04-18	Project Manager	$500.00
Project Design and Testing	43 days	Thu 19-04-18	Mon 18-06-18		$226,125.00
Procure Budget and Resources	2 days	Thu 19-04-18	Fri 20-04-18	Project Manager	$4,000.00
Role Allocation to the Respective Stakeholders	1 day	Mon 23-04-18	Mon 23-04-18	Project Manager	$2,000.00
Duty Allocation to Team Members	1 day	Tue 24-04-18	Tue 24-04-18	Cloud Architect	$375.00
Work on Hardwares	2 days	Wed 25-04-18	Thu 26-04-18	Linux Administrator	$325.00
Prepare Development Platform	2 days	Fri 27-04-18	Mon 30-04-18	Cloud Architect, Linux Administrator	$1,075.00
Gain Access to Amazon AWS	2 days	Tue 01-05-18	Wed 02-05-18	SAP Cloud Instance[1], Cloud Architect	$200,750.00
Implement Cloud Infrastructure	10 days	Thu 03-05-18	Wed 16-05-18	Cloud Architect, JIRA[10]	$4,250.00
Implement SAP on the Cloud	10 days	Thu 17-05-18	Wed 30-05-18	Cloud Architect, LAMP Stack Specialist	$5,500.00
Initial Testing on the System	10 days	Thu 31-05-18	Wed 13-06-18	LAMP Stack Specialist, Linux Administrator, X 86 Image	$4,750.00
Identify Risks and Issues	1 day	Thu 14-06-18	Thu 14-06-18	LAMP Stack Specialist	$175.00
Solve and Address Issues	1 day	Fri 15-06-18	Fri 15-06-18	LAMP Stack Specialist	$175.00
Final Testing of the System	1 day	Mon 18-06-18	Mon 18-06-18	Cloud Architect, SAP Expert (June), SAP Expert (Paulo)	$2,750.00
Go Live	1 day	Tue 19-06-18	Tue 19-06-18		$1,562.50
Run Demo Version	0.25 days	Tue 19-06-18	Tue 19-06-18	Cloud Architect	$93.75
Connect Database with Cloud	0.25 days	Tue 19-06-18	Tue 19-06-18	Cloud Architect	$93.75
System Go Live	0.25 days	Tue 19-06-18	Tue 19-06-18	SAP Expert (June), SAP Expert (Paulo), Cloud Architect	$687.50
System Handover to Project Manager	0.25 days	Tue 19-06-18	Tue 19-06-18	SAP Expert (June), SAP Expert (Paulo), Cloud Architect	$687.50
Project Closing	8 days	Wed 20-06-18	Fri 29-06-18		$18,925.00
Review and Appraisal	2 days	Wed 20-06-18	Thu 21-06-18	Project Manager	$4,000.00
Documentation	2 days	Fri 22-06-18	Mon 25-06-18	Cloud Architect	$750.00
Sign off by Stakeholders	2 days	Tue 26-06-18	Wed 27-06-18	Cloud Architect, LAMP Stack Specialist, Linux Administrator, Project Manager, SAP Expert (June),SAP Expert (Paulo)	$10,175.00
Official Closing	2 days	Thu 28-06-18	Fri 29-06-18	Project Manager	$4,000.00

Some critical assumptions made in the project are as follows.

• It has been assumed that this project will be feasible in terms of time and budget.
• It has been assumed that the cost benefit from the project will be sufficient.
• It has been assumed that AWS Cloud infrastructure will help to solve time zone problem and database hosting problem faced by Dai-Ichi.

The main dependencies of the project success are as follows.

• Availability of a reliable cloud platform
• Suitable software support for system design and development
• Proper plan for maintenance of the system post development
• Debugging and troubleshooting

Conclusion

It can be concluded hereby that this report reflects a general project plan that can be further developed with additional components of a project. However, this project plan contains some of the critical components of the project including the high level requirements, estimated schedule, budget, critical path and assumptions. All these factors have been developed as per the requirements of Dai-Ichi as well as feasibility limits of the project.

Abdinnour, S. and Saeed, K., 2015. User perceptions towards an ERP system: Comparing the post-implementation phase to the pre-implementation phase. Journal of Enterprise Information Management, 28(2), pp.243-259.

Almajali, D.A., Masa’deh, R.E. and Tarhini, A., 2016. Antecedents of ERP systems implementation success: a study on Jordanian healthcare sector. Journal of Enterprise Information Management, 29(4), pp.549-565.

Bernroider, E.W., Wong, C.W. and Lai, K.H., 2014. From dynamic capabilities to ERP enabled business improvements: The mediating effect of the implementation project. International Journal of Project Management, 32(2), pp.350-362.

Bintoro, B.P.K., Simatupang, T.M., Putro, U.S. and Hermawan, P., 2015. Actors’ interaction in the ERP implementation literature. Business Process Management Journal, 21(2), pp.222-249.

Galy, E. and Sauceda, M.J., 2014. Post-implementation practices of ERP systems and their relationship to financial performance. Information & Management, 51(3), pp.310-319.

Harwood, S., 2017. ERP: The implementation cycle. Routledge.

Muller, R., 2017. Project governance. Routledge.

Ptak, C.A. and Schragenheim, E., 2016. ERP: tools, techniques, and applications for integrating the supply chain. Crc Press.

Qian, L., Schmidt, E.K. and Scott, R.L., 2015, December. ERP pre-implementation framework for Higher Education Institution: A case study in Purdue University. In Industrial Engineering and Engineering Management (IEEM), 2015 IEEE International Conference on (pp. 1546-1550). IEEE.

Ram, J., Wu, M.L. and Tagg, R., 2014. Competitive advantage from ERP projects: Examining the role of key implementation drivers. International Journal of Project Management, 32(4), pp.663-675.

Tarhini, A., Ammar, H. and Tarhini, T., 2015. Analysis of the critical success factors for enterprise resource planning implementation from stakeholders’ perspective: A systematic review. International Business Research, 8(4), p.25.

Yeh, S.T. and Walter, Z., 2016. Critical success factors for integrated library system implementation in academic libraries: A qualitative study. Information Technology and Libraries (Online), 35(3), p.27.