eFashion SAP Business One Implementation Project Plan

This project plan outlines the implementation of the SAP Business One ERP system for eFashion Pty Ltd., a boutique with multiple stores in Australia. The plan addresses the need for an efficient system to manage the business, including online sales, home delivery, and customer service. It details the project scope, business case, schedule, resources, budget, risks, and communication plan. The document includes a Gantt chart illustrating the project timeline and key milestones.

VUIS CONSULTING PTY LTD.
PROJECT PLAN
eFashion SAP Business One Implementation
14 may 2018
[Name]
[INSERT AUTHOR JOB TITLE HERE]
[INSERT AUTHOR EMAIL HERE]

Table of Contents
Glossary...................................................................................................................................... 2
Introduction.................................................................................................................................. 3
Project scope............................................................................................................................... 3
Business Case............................................................................................................................. 5
Project Schedule and Approach (Rollout Strategy)......................................................................6
Gantt chart of project is:............................................................................................................... 9
Resources................................................................................................................................. 10
Budget:...................................................................................................................................... 11
Risk........................................................................................................................................... 11
Communication.......................................................................................................................... 12
Summary................................................................................................................................... 13
Glossary
Terminologies Definitions
Resources It can be either human or material. They are useful for completion
and success of project
Budget It is the estimation that how the spend is done to complete the
project
SAP System, Applications, Products
ERP Enterprise Resource Planning
Table 1 Project scope table
Table 2 Resource table
Table 3 Budget table
Table 4 Risk table
Table 5 Communication table

Introduction
For eFashion, the business system of SAP project plan is discussed which describe the
required processes that are used to develop the project scope. All action that is required for the
project plan for objective attaining for which project started is illustrated. Major roles &
responsibilities of project team are described in the project planning part. The project planning
phase also details the budget and the resources required for eFashion system are discussed.
With the help of project planning the team is guided so that objects are attained for the eFashion
system. To increase the business and the sales of the eFashion system, the project plan detail
is done about the deliverables that are important for it. The system of ERP of business one has
the functional benefits that include the home delivery and the online purchasing of the service.
The call centre of eFashion is situated in the Melbourne which is giving its help in solving the
queries of customer, chat support, Complaint resolving, tracking of orders & technical errors of
website record.
With the help of project plan, the detail of the risk associated to design the eFashion system
which provides the dangerous effects on the system can be discussed in the report. These risks
are made available by me in detail in the risk register. This project plan is also used for
communication matrix purpose. Through this, the interaction with the sponsors and the
communication team associated with the project can be identified in an easy manner. In project
planning the summary is also included so the phases which are important to the system are
discussed. The phases which are important in eFashion system are Installation of server,
integration & conversion of data.
Project scope
The objective & aim of project is implementing the “SAP business one system of ERP” for
eFashion. The new project is helping the eFashion to purchase online, to provide the home
delivery feature for the product that are selling the products online. With the implementation of
the system online it will help to increase the sale in the business & also meet the trends that are
used in Australia in modern times. The call centre feature of the system is also available for the
customer to solve their complaints.
The key deliverables that are included for ERP are new hosting server’s, reformed server
rooms, conversion of data, documentation & the proper training environment for the staff of New
York.

Table 1: Project scope table
Key Deliverables Criteria of quality Measurement methods
Charter of project It will follow project scope,
objective & achievement.
Work handy for the clients. It
will show the different
versions of charter until the
best one is illustrated.
Risk register of system All available risk is illustrated. The risk is involved in project
are using the checklist.
Planning of project It explains the project scope,
resources & schedules,
communication, risk registers
& overview and the summary.
Work handy for the clients, It
will show the different
versions of charter until the
best one are illustrated.
Training Training is going to be
provided by taking the help of
quality manuals.
Surveys & feedbacks.
Business one implementation
of SAP
Expected results are going to
be drawn when project is
finished.
The VUSIC team of project
have tested the system before
it comes the using.
User manuals User guides & manuals are
developed that how to handle
the system.
To improve the manual the
feedback is taken from the
employees.
Report of the status of project The ongoing processes & the
achieved milestones are
documented for the system.
On the ongoing process of
project and the time which is
spent is going to be the
measurement factor.
Installed servers All the compatible server has
to store the information of the
organisation in a secure
manner.
Testing of the server is going
to be done by installing the
data over the servers.
Assumptions
 The assumption is made, that the technicians are having the sufficient skills for project
implementations.
 It will be assumed that the project is finished within the estimated project to meet all
requirements.
 It will be assumed that the manager of the project keeps monitoring the complete project
with ability & ongoing process are taken into care.
 It will be assumed that the project is completed under the time frame that is estimated and
no extra time is required for the design.
 It is assumed that the all necessary cooperation with the parties associated with eFashion
staff & vendors, etc.
Business Case
The eFashion Pty Ltd is the boutique that is situated in the Melbourne, Australia. In Australia,
they have many offices & the stores are widespread. But, there is not having the system that is

efficient to manage the business. No connection in between in any store and the office they all
working independently. That’s why the reason is that the eFashion is not catching up the market
requirements. They are not having the notify feature. If any of the new arrivals arrive then it
does not notify customers, & they are also not using the latest and modern trends of fashion in
the whole nation. To solve this issue and expand the business and sales of eFashion the SAP
one business system is required for expanding the business.
Scenario of the eFashion currently:
 Call centre is not present
 Online selling of product is not available.
 Chatting on wen is not available.
 Home delivery is not available.
To achieve the business expansion, the ERP system of eFashion are working in following
areas:
1. Sales:
 Sales are increasing in selling the product online.
 All stores are connected with each other so the customer can from any of the stores
they have changed it to any store.
 The multiple stores are available for buying the products.
2. Customer service:
 Special offers are provided to the customer whose information is stored in the
database.
 Call centre for solving the issue of customer.
 The feedback is taken that will improve the quality of service of the system.
3. Marketing:
 Customers get the new and exciting offers.
 The new product is notified by the advertisement.
 The image of the company is going to be improved.
Some associated disadvantages with the project outcome are:
 The quality does not meet in few of the features such as image is not real as the real
product actually looks.
 Sometimes the difficulty is facing the customers for using the software for buying the
product online & to process the issue.
Project Schedule and Approach (Rollout Strategy)
The description of the task is as follow:
 Planning Phase: In this, I have to plan for the project that what is a need for the project.
In this how each part is creating success in this time frame & the cost is estimated for
the project the time and cost are minimized.

Figure 1 Planning phase
 The procurement phase: In this phase, the demand and of the project and how it will
monitor are discussed.
Figure 2 Procurement phase
 Modification/cabling phase: In this if any changes are made to the project are done.
Figure 3 Modification phase
 Testing phase: In this, all the system is tested and check should meet the scope and the
requirement.
Figure 4 Testing phase
 Server installation phase: In this phase, the new server is installed so that the business
is expanded. In this, the system always responds the users.

Figure 5 Server installation phase
 Data extraction phase: In this, the data are extracted and it is tested that the new data
are improved with the old data.
Figure 6 Data extraction phase
 Data importing and system integration phase: In this phase, the new things are added
which make better and useful system of ERP.
Figure 7 Data importing and system integration phase
 The documentation phase: In this, the documentation is created for a simplified design,
briefs, and handbooks so anyone can easily understand the system.
Figure 8 documentation phase
 The training phase: In this skilled person are teaching those who are new to the system
and the knowledge are provided to them.
Figure 9 Training phase

 The acceptance testing phase: It is the last phase in which if the entire pre-analysis
phase requirement is checked with the current result output.
Figure 10 Acceptance testing phase
 The project control phase: In this, the requirement and the scope of the system are
tested that it should either meet all the requirements or not.
Figure 11 Project control phase

Gantt chart of project is:
ID Task
Mode
Task Name Duration Start Finish Predecessors
1 sap buisnessone For eFashion57.06 daysMon 4/16/18Wed 7/4/18
2 Planning Phase 8.13 days Mon 4/16/18Thu 4/26/18
3 Analysis of project1 day Mon 4/16/18Mon 4/16/18
4 Analysis for system1 day Mon 4/16/18Mon 4/16/183SS
5 Risk approximation1 day Tue 4/17/18Tue 4/17/184
6 Approximation of project capitals1 day Wed 4/18/18Wed 4/18/185
7 Requirement of project capitals1 day Thu 4/19/18Thu 4/19/186
8 Create schedule1 day Fri 4/20/18 Fri 4/20/18 7
9 Develops Design project charter1 hr Mon 4/23/18Mon 4/23/188
10 Delevlop Design plan2 days Mon 4/23/18Wed 4/25/189
11 Approval from manager1 day Wed 4/25/18Thu 4/26/1810
12 Start the project0 days Thu 4/26/18Thu 4/26/1811
13 procurement 0.38 days Thu 4/26/18Thu 4/26/18
14 Monitoring All Suppliers1 hr Thu 4/26/18Thu 4/26/1812
15 Demand Frida server1 hr Thu 4/26/18Thu 4/26/1814
16 Demand order required cable1 hr Thu 4/26/18Thu 4/26/1815
17 procurement complete0 days Thu 4/26/18Thu 4/26/1816
18 Cabling/Modification5.75 days Thu 4/26/18Fri 5/4/18
19 Build appropriate room for server4 days Thu 4/26/18Wed 5/2/1817
20 Connect cable 6 hrs Thu 5/3/18 Fri 5/4/18 19FS+1 day
21 Modification/Cabling complete0 days Fri 5/4/18 Fri 5/4/18 20
22 Testing 5.5 days Thu 4/26/18Thu 5/3/18
23 Evaluate delivery4 days Thu 4/26/18Wed 5/2/1817
24 Plan testing for server2 hrs Wed 5/2/18Wed 5/2/1823
25 Allocate testing tasks2 hrs Wed 5/2/18Wed 5/2/1824
26 Test the server1 day Thu 5/3/18 Thu 5/3/18 25
27 Testing complete0 days Thu 5/3/18 Thu 5/3/18 26
28 Server installation-platinum0.88 days Fri 5/4/18 Fri 5/4/18
29 Testing Verfies1 hr Fri 5/4/18 Fri 5/4/18 27
30 Changes 4 hrs Fri 5/4/18 Fri 5/4/18 29
31 Arrangement for installation1 hr Fri 5/4/18 Fri 5/4/18 29
32 Connectionof Platinum server5 hrs Fri 5/4/18 Fri 5/4/18 31
33 Connection done0 days Fri 5/4/18 Fri 5/4/18 32
34 H/W Connection completed0 days Fri 5/4/18 Fri 5/4/18 33
35 Data extraction and Conversion6 days Fri 5/4/18 Mon 5/14/18
36 Old Data verification2 days Fri 5/4/18 Tue 5/8/18 34
37 Extract all data1 day Tue 5/8/18 Wed 5/9/1836
38 Test Real data and removed data1 day Wed 5/9/18Thu 5/10/1837
39 Data cleansing1 day Thu 5/10/18Fri 5/11/18 38
40 Data changing 1 day Fri 5/11/18 Mon 5/14/1839
41 Extraction& Changing completed0 days Mon 5/14/18Mon 5/14/1840
42 Data Importing andSystem Integration28 days Mon 5/14/18Thu 6/21/18
43 Evaluation removed Data1 day Mon 5/14/18Tue 5/15/1841
44 Data import into new server13 days Tue 5/15/18Fri 6/1/18 43
45 Website addition with system7 days Fri 6/1/18 Tue 6/12/1844
46 Sale system addition with original system7 days Tue 6/12/18Thu 6/21/1845
47 Addition of data finished0 days Thu 6/21/18Thu 6/21/1846
48 Documentation 2.5 days Thu 6/21/18Tue 6/26/18
49 Analyse Handbooks1 day Thu 6/21/18Fri 6/22/18 47
50 Designed simlified Handbooks1 day Fri 6/22/18 Mon 6/25/1849
51 Document brief Handbooks4 hrs Mon 6/25/18Tue 6/26/1850
52 documentation complete0 days Tue 6/26/18Tue 6/26/1851
53 staff training 1.88 days Tue 6/26/18Thu 6/28/18
54 use simplified Handbooks1 hr Tue 6/26/18Tue 6/26/1852
55 develops training programm6 hrs Tue 6/26/18Wed 6/27/1854
56 Arrange training sessions1 day Wed 6/27/18Thu 6/28/1855
57 Training complete0 days Thu 6/28/18Thu 6/28/1856
58 Acceptance testing &sign-off3.81 days Thu 6/28/18Wed 7/4/18
59 Test Hardware System1 hr Thu 6/28/18Thu 6/28/1857
60 Testing completion modification2 hrs Thu 6/28/18Thu 6/28/1859
61 Monitoring the processes6 hrs Thu 6/28/18Fri 6/29/18 60
62 assign correcting processes to staff1 hr Fri 6/29/18 Fri 6/29/18 61
63 correcting diffi culties11.5 hrs Fri 6/29/18 Mon 7/2/1862
64 Log-off 1 hr Mon 7/2/18Tue 7/3/18 63
65 documentation distrubuted0.5 days Tue 7/3/18 Tue 7/3/18 64
66 payment received0.5 days Tue 7/3/18 Wed 7/4/1865
67 Project completed0 days Wed 7/4/18Wed 7/4/1866
68 project control 1 day Mon 4/16/18Mon 4/16/18
69 Status meeting1 day Mon 4/16/18Mon 4/16/18
70 Status meeting 11 day Mon 4/16/18Mon 4/16/18
71 Status meeting 21 day Mon 4/16/18Mon 4/16/18
72 Status meeting 31 day Mon 4/16/18Mon 4/16/18
73 Status meeting 41 day Mon 4/16/18Mon 4/16/18
project manager
business analyst[25%],clarly(IT support manger
business analyst
jack(marketing manager),business analyst[50%]
project manager[25%],business analyst[75%]
project manager
project manager
project manager
project manager,amanda brightside
4/26
project manager
project manager
project manager
4/26
local constructor
cables[30],quick cables
5/4
project manager
project manager
project manager
5/3
Technichal Officer
technical officer
project manager
platinum server[1],sap business one system[1]
5/4
5/4
database programmer
database programmer
database programmer
database programmer
database programmer
5/14
data entry officer
data entry officer
system integrator
system integrator
6/21
technical writer,project manager
technical writer
technical writer
6/26
trainer
project manager,trainer
trainer
6/28
project manager
administartive officer,project manager
project manager
project manager
project manager,trainer
project manager[25%],amanda brightside
project manager
administartive officer,project manager
7/4
project manager[50%],Technichal Officer [50%]
project manager
project manager,amanda brightside,business analyst
amanda brightside,project manager
M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T
Apr 15, '18 Apr 22, '18 Apr 29, '18 May 6, '18 May 13, '18 May 20, '18 May 27, '18 Jun 3, '18 Jun 10, '18 Jun 17, '18 Jun 24, '18 Jul 1, '18

Figure 12 Gantt chart of project
Resources
The resources tell that all the required necessities of the project are:
Resource sheet is:
Figure 13 Resource sheet
The responsibilities & roles of different team members of project are shown below:
Table 2 Resource table
Name of resource Resources roles
Project Manager It should manage all the activities of project.
Data Entry Officer The new server is installed and the old server room is modified
Technical Writer The coding and the documentation are developed for the project.
Business Analyst The processes associated with the business are analysing in the
project.
Database Programmer In system, the data is created and maintained.
Technical Officer A technical issue in the project is followed.
Systems Integrator The documents are translated technically & the user guides are
produced.
Trainer The new users are providing the training for the system use.

Administrative Office Managing the complete facilitates in the office that is supported by
the project.
Budget:
In project the major costs are shown below:
Table 3 Budget table
Name Cost
Local constructor $10,500.00
Quick cables $330.00
Project manager $25,496.00
Business analyst $3,640.00
Data entry officer $6,720.00
Trainer $3,047.50
System integrator $11,760.00
Database programmer $4,560.00
Technical writer S1,900.00
Administrative officer $300.00
Technical officer $425.00
Assumptions in cost:
 Assume that the cost of cables is as per the market price, no extra cost is taken for that.
 Assuming that the server cost & the software is valid till the completion of project.
Risk
In the project of eFashion, there are different risk that is associated with the system. It will affect
the system/project in a drastic manner. The risk is defined & also identified the associated risk
levels. The reducing risk impacts on the project are:
Table 4 Risk table
ID
No
.
Name of risk Cause /
Descriptions
Impa
ct
Mitigation Probability Owner Sta
tus
R1 Objectives are
unclear
The team of
project are not
clear with the
objective
High The objectives
are defined
clearly in the
charter of
project & plan
Low Project
manager
R2 Risk of market The customer
does not adopt
the new
environment
Medi
um
The customer is
provided with
the details by
advertising and
its benefits.
Medium Business
analyst

R3 Sharing of
resources
Taking sick
leave/
emergency in
any family
High The resources
are added more
if required
Medium Project
manager
R4 Miss-
communication
The
information is
not revealed in
a proper
manner
High The meeting is
held in a proper
manner.
Medium Project
manager
R5 Risk of
communication.
Risk of people
The important
tasks are not
properly
communicated
. It may cause
the
workaround
time in the
members of
team
High Status of the
report is
checked on a
regular basis &
feedbacks
provided
High Project
manager
R6 Does not have
experience of
data entry
In industry the
office for data
entry are new
Low The whole team
are given the
proper training
& contribution
Low Project
manager
R7 Technological
risk
In the system
testing the
CRM software
are giving
some issue
related to
compatibility.
High The update is
gathered for the
system or the
software
compatibles are
taken from the
vendors
Low Business
analyst /
System
Integrator
R8 Consumption of
time in
conversion of
data
Because of
poor using the
storage of data
it may require
more time.
Low The manager of
IT is providing
the document
that is
previously
taken
Medium Database
program
mer
All above risk affects the success of the system and the levels of risk are also varying and for
success the system the risk is reduced.
Communication
In success of the project, the communication in between the team members is must for project
success. The communication is taken and recorder later. The meetings that are held are used to
make any change in the system as well as to resolve the relevant issues in the project are:

Table 5 Communication table
Type of
communicatio
n
Medium Objective Audience Frequency Deliverable Owner
Meeting of
team
Face-To-
Face
The goals,
phases &
the cost
are
discussed.
The staff
which is
working.
At the
need arise
For managing
the hurdles
the method of
documentation
are used.
Project
manager
Meeting for the
project
development
Face-To-
Face
Work plan
is
developed
Team of
project
This will be
done on
weekly
basis until
the project
completion
Plan of project
is done
Project
manager
Project status
report
E-mails The
milestones
are
informed
The
sponsors
and the
team of
project
In need at
any time
Report status
are deliverable
Project
manager
Project status
meeting
Face-To-
Face
All the
current
task status
Team of
project
On weekly
basis
Report status
are the
deliverable
Project
manager
In the communication, all persons are required and should attend the meeting. Also, all the
important communication should take place in a proper manner.
Summary
The project plan steps are discussed that how the SAP business one ERP system is
implemented. It will help to identify the scope of project. In each time what the information is
exactly required are known before process further. In next, the analysing is done in the project
business case. What is the current status and what to do that the current system is improved?
Then after the Gantt chart of the project are developed. This Gantt chart is used to determine all
the task that is required in the system. The time frame is taken into consideration so that all the
task is completed on time. The resources, risks & the budget are identified for the project. In the
end, the communication should take place in which meeting in between the team members so
the issue in the project is discussed and solved.