0% found this document useful (0 votes)
104 views10 pages

ERP Implementation Methodology - New

Uploaded by

Rony
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
104 views10 pages

ERP Implementation Methodology - New

Uploaded by

Rony
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

ERP

Implementation
Methodology
SAFAL
ERP
 Initiation Stage
Six Stage (IS)
SRS Stage (SS)
Implementati
on Plan Development Stage (DS)
SAFAL ERP
Testing & Training Stage
(TTS)
Feedback & Review Stage
(FRS)
LIVE Stage (LS)

© Copyright Safal Infosoft Pvt.


Ltd.
• Project Kick-off
• Forming Project Team
• Identify Roles & Responsibilities
• Determine Hardwar
Infrastructur e • Standard
e product
• Draft Project walkthrough
Plan • User
• Project Closure
Requirement
• Cut-over
• Parallel run
Initial Stage Study
• (URS sign-off)
• Post Implementation Go Live (IS) [A]
based on gap
Review
Stage – SRS Stage
Implementati • Hand-over to analysis
• Review &
Support Team (LS) [F] (SS) [B] confirm Project

on Lifecycle Plan
• Hardware setup

SAFAL ERP Feedback Developmen review

Review t Stage (DS) • New


Stage (FRS) Training [C] requirements will
Testing be
• Weekly Review Meetings [E] accommodated
• Progress Sheet Preparation Stage – • Tested functionally
by EDP Department (TTS) [D] at SAFAL End
• Evaluation of
Implementation
Process • Preparation to Go Live
• User Feedback System • Cut over Preparation
• Effective Gathering • Training to Team
of Feedback • Software Configuration
• Test Run & Parallel Run (Internal)
• Training to End Users with Entire
Lifecycle & Dummy Entries. © Copyright Safal Infosoft Pvt.
Ltd.
 Project Kick -
Off:
General overview of SAFAL i.e Methodology, Standards, Planning etc.
 Forming the Project Team:
Identify best resources to form project team from both side who will be key resources
during whole implementation process. They will be used for requirement filtering,
training and implementation purpose.
Initiation  Identify Roles & Responsibilities:

Stage Define roles and responsibility for each team member as mentioned above
Stage 1  Determine the Hardware Infrastructure:
Determine required hardware and software keeping eye on number of end users.
 Draft Project Plan:
Define detailed project plan with timelines like duration of SRS, data migration,
development, testing, UAT and training.

© Copyright Safal Infosoft Pvt.


Ltd.
 Standard Product Walkthrough:
SAFAL Will Provide General Overview Of Product With Actual System, So That End User
Can Be Acquainted With The System And Think More For Missing Requirements.
 Software Requirement Study (SRS):

SRS Detailed Brainstorming Session With Each And Every Departmental Head, End Users For
Their Requirements, Wishes From The ERP System. It Is Basically Gap Analyze Between
Stage AS-IS And TO-BE.
 Review & Confirm The Project Plan.
Stage 2
 Collection Of Report Formats From Various Departments.
 Hardware Procurement & Setup: Take A Look At Proposed Hardware Requirements And
Its Procurement Progress.

© Copyright Safal Infosoft Pvt.


Ltd.
Developme
 Development as per Signed SRS Documents will be Going On During This Phase.
nt Stage  Each Requirement and Modifications Will Be Developed And Tested Functionally At
Stage 3
Our End.
 Report Designing And Development Will Be Done Simultaneously.

 Data Will Be Imported Into The System (Party Master And Item Master).
Testing and  All The Changes & Developments Checked Against SRS Document.
Training  Hardware Setup at Company Premises Verified. Installation Done at Customer

Stage End.
 Master User Training Will be Start from This Stage (SIT – System Integration
Stage 4
Test).
 End Users Will Be Trained And Encouraged For Maximum Dummy Entries And
Testing (UAT – User Acceptance Test)
 Cut Off Date Revised Accordingly
© Copyright Safal Infosoft Pvt.
Ltd.
Feedback &  Weekly Review Meetings. Using This Possibility Client’s Top Management can be
Involve in to Implementation Progress & Suggest their Comments
Review  Progress Sheet Preparation by EDP Department

Stage  Evaluation of Implementation Process by Top Management of Both Ends.


 User Feedback System
Stage 5
 Effective Gathering of Feedback

Live  Parallel Run (Optional): It Is Advisable To Go For Parallel Run For Month Or Two.
Stage  Go Live Date: Customer Can Go Live With All Modules or Some Preliminary
Modules In One Shot (Phase Wise).
Stage 6
 Hand-Over To Support Team
 Project Closure

© Copyright Safal Infosoft Pvt.


Ltd.
Documents  Service Request & Sign-Off
Important During  Change Request & Sign-Off
Implementation
 Issue Logs
 Project Status Report (Monthly)
 Project Meeting Minutes
(Weekly)

Some Key
Factors for  Equal Participation From Client Company.
 Strict Implementation Of Policy Related Changes Upto End
Successful & Users

Timely  Proper Documentation

Implementati  There Should Be Minimum Alteration In Predefined Schedules

on
© Copyright Safal Infosoft Pvt.
Ltd.
Key Quotes for “You can have the best technology in the world, but if you don’t have a community who

Any Change wants to use it and who are excited about it, then it has no purpose.” Chris Hughes Co-
Founder of Facebook.

Implementati The Holy Grail (unwritten rule) of ERP implementation is, synchronizing existing company
practices with the ERP package rather than changing the source code and customizing it to
on suit the company.

SAFAL ERP However an organization can only get the maximum value of these inputs if it
successfully
adopts and effectively uses the system.

© Copyright Safal Infosoft Pvt.


Ltd.
www.safalerp.c
om
Find us here

SAFAL Infosoft Pvt. Ltd.


INDIA: Ahmedabad – Mumbai – Delhi NCR – Hyderabad – Kolkata
OVERSEAS: MALAYSIA – KENYA – TANZANIA

© SAFAL is a registered trademark of Safal Infosoft Pvt. Ltd. All other product names are trademark of the respective manufacturers. This document is intended for
information

You might also like