erp implementation

21
ERP Implementation

Upload: facts-computer-software-llc

Post on 11-Apr-2017

21 views

Category:

Software


0 download

TRANSCRIPT

Page 1: Erp implementation

ERP Implementation

Page 2: Erp implementation

Talent wins games, but teamwork and intelligence wins championships. Michael Jordan

Page 3: Erp implementation

Comments • Lack of product Knowledge

• Lack of Domain Knowledge

• Providing improper solutions

• Improper Consultation

• Not following procedures

• Stay out of Responsibility

• Lack of communication with customer

• Ineffective use of Knowledgebase

• Re usability

• Improper resource allocation

• Lack of planning

• Lack of Knowledge transfer

• Lack of Guideline

Page 4: Erp implementation

Lack of product Knowledge

Understand the Process flow and structure than features and advanced options of the product.

• FactsBMS is the first learning point.

FactsBMS having less features and advanced options but process flow and structure is strong.

FactsBMS easy to understand.

• Table structure and fields.

Understanding of this makes life easy.

- For migration

- For report layout changes.

Page 5: Erp implementation

Inventory

Important knowledge points.

1. Inventory Costing

2. Impact on transaction tables (stock UP or down)

3. Knowledge about inventory reports

• Accounts

Import knowledge points

1. Accounting effect on documents (Debit – credit)

2. Knowledge about accounting reports.

3. Allocation, Reconciliation, Aging, Closing JV etc.

Lack of product Knowledge

Features of FactsERP, Usage of Each Options – Refer corresponding Documentation

Page 6: Erp implementation

Lack of Domain Knowledge

Core Areas to concentrate more :

1. Accounts.

2. Inventory costing.

Apart from FactsERP, study the basic accounting, costing, different types of business activities. (From books, Web, or from experienced people)

We can collect this knowledge from clients itself –

- Visit the client site to see their activities (Eg. Factories, warehouse etc). Observe/ask what they doing (from employees)

Page 7: Erp implementation

Providing improper solutions

Don’t use shortcuts • Refer Primary study documents (SRS)

• If it is difficult to solve – Take time (But there is a cut of date)

• Solutions don’t do it in the client site

• Refer all referral points – Documents, from experienced engineers etc.

• Communication with the team.

• KB, learning Videos

Page 8: Erp implementation

I m p r o p e r C o n s u l t a t I o n

1.Ask the queries to concerned person.

2.Make use of Knowledge base

3.Avoid delay to clearing the queries.

4.Document in KB (If not there).

Page 9: Erp implementation

Not following procedures

1. Follow the procedures

- Discuss with Team

- Follow the check list

- Follow the SRS

Page 10: Erp implementation

Stay out of Responsibility

When you do what you have promised, people see

you as a responsible and reliable person. This is

quite admirable, as many people won’t deal with individuals who are irresponsible. They will give

their trust to friends they can count on, and give

their business to companies they admire. A

responsible person is one who can be trusted to act

without needing strict supervision, because they

are accountable for their own behavior. Keep doing

it, and you’ll soon develop a reputation It’s not rocket science, being responsible simply requires you to follow a certain set of guidelines, in every action you do. Get all of these in order, and you’ll be a very responsible person

Page 11: Erp implementation

Lack of communication with customer Always keep contact with customers, don’t be idle.

- If possible make friendship with customers

- Don’t give false promises

• Talk confidently.

• Don’t tell other referral points to customer (Eg. I need to ask somebody (name of the person),

Instead of that always tell that discuss with team, check with R&D department or I will check the internal database

Don’t use sorry, in words or mail, instead of that, if necessary, can use Apologies

Page 12: Erp implementation

Ineffective use of Knowledgebase Always use the knowledgebase

Add value editions to Knowledgebase.

Place local copy of KB in all databases. (Prime responsibility)

Page 13: Erp implementation

Re usability

- Incorporate all new enhancements (That done for a new client/existing client ) in demo - Lan with the help of demo-Lan custodians.

- Demo Lan acts a Showcase of all features – So we can refer/check its already done or not

Page 14: Erp implementation

Improper resource allocation

- All resource are eligible to allocate anything related with implementation.

- All are specialists.

- Important how we make the execution, its totally dependent on the execution plan .

Page 15: Erp implementation

Lack of planning Totally dependent on Project Managers.

Don’t Plan anything in last movement

Always follow the PDS.

Page 16: Erp implementation

Lack of Knowledge transfer - Don’t hesitate to ask doubts/queries

- Make use of KB

- Watch the videos

- Read documentations.

- Attend daily refreshment session

Page 17: Erp implementation

Lack of Guideline - SRS is the reference point of the project implementation.

- PDS – Follow the PDS milestone .

- Additional points are change order and this is a core revenue point for the company..

Page 18: Erp implementation

Summary

Page 19: Erp implementation

After dealing with customer ..

Should not be like this Should be like this

Page 20: Erp implementation

Always Remember, Happy Customers are our future…

Be thankful customer who complain .. You still have the opportunity to make them happy..

One customer taken care of could be more valuable

than $10000 advertising .

Page 21: Erp implementation