Implementation

Roadmap
Expectations Setting
What will not happen
• Some of the flexibilities you had in your Accounting Software(like
Tally) will not be there in ERP
• Deletion
• Matching Report Formats may not be feasible
• 100% process Match may not happen
• You have to be willing to adopt newer processes/Workarounds
• Some processes will become lengthy and some will be shorter
• Some Customizations/processes may not be configurable on ERP
• Not all issues will be because of Software
• Network/Internet issues
• Viruses
• Data entry mistakes
Be open to
• A more disciplined way of working
• Change existing processes/Newer processes/Adopting workarounds
• New Report Formats
• Sometimes hearing “Not feasible”
• People enabled with information
• Transformation
Important Do’s and Don'ts
• Involve your key users
• Key to success – give less priority to exceptions
• Minimize Change Requests
Teams and Preparations
Team structure
ESS and Partner Client
Escalation Management
Contact Representative

Regional Steering
Head Team

Project Manager Client Co-ordinator

(ESS/Partner’s (Client’s SPOC)
Support Group
SPOC)
• Functional Experts
• System Architects
• Developers Departmental
• Hardware Experts Implementation Teams
• Database Specialists
Consultant(s)
• QA Auditors
• Change Management
Preparation at ESS/Partner’s end
• Review of Contract
– Scope of Delivery
– Commitments given
– Timeline
• Team Orientation and Ramp-up
– Understanding of business domain
– Assigning of Project manager
– Assigning of Functional Consultants
Planning
• Preparation of Project Plan
• Sharing of pre-requisites with the customer
• Hardware details
• Single Point of Contact (SPOC)
• Master data formats (including COGs/COAs/Item Profile etc.)
• Workflow/Organization Chart
• Business Test Scenarios
• Business Test Cases
• Schedule
• Review of standard Questionnaire with respect to the domain of the
customer
• Orientation of functional consultants on implementation
process/checklists/standards relating to current implementation
Implementation
Methodology
Process Finalization Document Process
Finalization
Document
• Understand the existing processes(AS-IS) from
Users(Client Discovery) Configuration
and
• The meetings can be recorded(Audio). The recording Customization
will also be provided to Client.
Training
– Serves as a Reference for ESS when creating the Document
– Revisiting of the recordings in case of a confusion User
• Analyzing the existing processes and mapping Acceptance
Testing(UAT)
• The AS-IS to Standard ebizframe functionality
Go-Live
• Acceptable workarounds(Allow faster Go-Live) Preparations
• Customizations – Feasible and unfeasible
• Schedule Customizations delivery schedule
Configuration/Customization Process
Finalization
Document
• To be done by ESS team offsite(ESS office in India)
• Configurations and agreed Customizations are done Configuration
and
• Modular Release/Functionality wise Release Customization

Training

User
Acceptance
Testing(UAT)

Go-Live
Preparations
Training Process
Finalization
Document
• Training at a Central Venue
• Types of training Configuration
and
– Champion Users/End Users Training Customization
– Senior Management/Manager’s Training
– Administrator Training Training

User
Acceptance
Testing(UAT)

Go-Live
Preparations
UAT(User Acceptance Testing) Process
Finalization
Document
• Users to do the UAT as per the Test Cases
• Rework/Retraining after UAT, if any. Configuration
and
• UAT Sign-off – Completion of Delivery Customization

Training

User
Acceptance
Testing(UAT)

Go-Live
Preparations
Go-Live preparations Process
Finalization
Document
• Go-Live Checklist-Hardware, Network, Software,
People Configuration
and
• Partial Go-Live/Big-Bang Rework/Retraining after Customization
UAT, if any.
Training

User
Acceptance
Testing(UAT)

Go-Live
Preparations
Go-Live
• Teething troubles
• Stabilization
• Handholding
Reviews and Sign-offs at various stages
• Periodical reviews
– With Agenda
– Minutes for assigning and tracking actionables
• Regular Reviews and Reviews with MR
• PFD
• Installation Certificate
• User Training Sign-off
• UAT Sign-off
• Database Backup Training Sign-off
• Project Sign-off
Client’s Responsibilities-Refresher
 A Project Coordinator(SPOC)
 Agree on Project Governance Model
 Availability of Users and Key Stakeholders
 Supporting Software/Hardware
 Environment(Production and Test Environment)
 Champion User Identification
 Office facilities
 Test Data/Test Cases for testing Software Deliveries
 Sign-offs
 Remote access to Servers(Static IP Based) - For support and upgrades.
 Remote Access to Desktops(TeamViewer) - To remotely analyze User issues
BE READY TO TRANSFORM