Tuesday, June 17, 2008

Lessons Learned 1 by ahmet k

ERP - Enterprise Resource Planning

Realtime, implement business processes according to 'best practices'. This may be problematic since we can't really know what is 'best'

One database, different modules connected. Integrated package, connecting different functions.

Industry spesific solutions: financial services, transportation etc..
Multiple language support
Can work in different currencies, multi-currency environments

Supply chain apps (out)
ERP (in)

3 tier system:
BASIS (spesifics)

Evolution: (From materils planning to manufacturing planning to ERP)

Big companies: SAP, Oracle, BAAN (Expensive, strong support)
Open Source: Compiere, OFBiz, WebERP (you can develop yourself, lack of support)
There are small companies (more flexible, cheap, limited) and web based ERP as well (cheap, less resources used, but security issues).
Businesses and ERP systems change in implementation. Both are problematic. Minimizing # of changes is a good idea.

Core Team:
-Someone who knows workflow/dept, Suppliers (maybe),
-Top management (Dept Directors/Managers),
-IT Managers (Project Manager probably)
-Champion (if additional resources are needed, this person should have the influence to get it, also motivates)

manager - consultant dipole is a basic building block of a project

Political model seems to explain best the decision process of implementation of ERP systems. Others are partially effective.

IT implementation failure: 70% - subjective (criteria are important)
1 - Does it Work? does it meet the requirements?
2- On budget?
3- On time?
4- Usable? Is there resistance to use?

Usually where there is change, there is resistance, and with the implementation of ERP systems, businesses change; hence there is resistance.

SAP Audit Trail: keep track of user actions

Data Warehouse:
3-D database, you know what you want

Data Mining:
Fun, can look at different patterns or try to see correlations. You want to find something valuable.

No comments: