Wednesday, June 18, 2008

Day 1 Learnings from OnurO


-ERP is a database platform on which modules work to solve certain functional problems and uses this single database which has cross functional nature to do these.

-ERPs also integrate geographically, i.e. manufacturing plants which are geographically dispersed. SAP supports multiple languages and currencies.

-Most of the time business processes should be re-engineered to adapt ERP system, this is also about "best practice". Analysis of bottlenecks through ERP implementation is possible since the problematic areas will not probably adapt.

-For some cases, though, ERP itself should be customizable to adapt to organization. In-house coded ERPs are more costly to build but more useful in assessing bottlenecks.

-ERPs stemmed from MRPs and MRP-IIs which were concentrated on materials, inventory and manufacturing mostly. In ERPs, though, several support modules are available in an integrated manner. These modules include applications in finance, HR, CRM etc.

-Most of ERP projects fail due to required budget, time, capability of personnel to use and/or dissatisfaction with the performance of system.

-ERP vendors can be classified into four categories including major players such as SAP, Oracle etc; small one which are local or specialized; open source ERPs such as OFBiz, Compiere etc. and on-demand ERP like SAAS.

-Each category of source has its own pros/cons. Major players have greater support and contain less bugs, smaller ones have more specialized or customizable traits; open source ERP is free or cheaper to implement and a successful alternative but support is not available most of the time. On-demand systems have low initial costs but may encounter speed and consistency problems as it is directly downloaded.

-The implementation of ERP should involve a team of IT people, someone from top management, consultants and champion to pioneer to additional resources. During the implementation and business process revision phase someone within that particular area may be useful.

-SAP is a three tier architecture, multi language/currency, highly modular (i.e. presentation, data storage and functional applications are all separate.) and frequently upgraded type of ERP. It has an audit trail system to track what is done by who.

-Data interpretation-this is important s’nce ERP is just an information tool, it does not do analysis on itself.

Data Mining: Drawing conclusions from patterns in data. You do not have anything in mind but hoping to obtain some pattern.

Data warehouse: This requires that you know what to look. It is module that draws graphs etc. about certain variables via 3-D cubes.

No comments: