1) An ERP system provides integrated management of core business processes through a single system. It aims to integrate all departments and functions across a company onto a single computer system that can serve all those different departments' particular needs.
2) Companies implement ERP systems to support business goals like integrated and online processes, elimination of fragmented legacy systems, improved integration and lower costs.
3) A successful ERP implementation requires the right mix of people, processes, and technology. Key steps include project planning, design, building the system, transitioning to the new system, and ongoing production support.
10. Typical architectural components CRM Foundation Marketing Sales eCommerce Business Applications Interaction History Universal Work Q 1-to-1 Fulfillment Assignment Engine Escalations TCA Installed Base Tasks Notes Resources Calendar Territories OSS HR E-business Platform Tech Stack Web Internet Mobile Wireless e-Mail Call Center ICM/Telephony Interaction Channels Common Data and Object Models, Security, Interfaces, Globalisation E-Business Foundation Marketing Intelligence Sales Intelligence Customer Intelligence Call Center Intelligence Analytical Applications
11. Tech Stack - Internet Computing Architecture X 2 Tier 3 Tier Database Application Application Application Application Application Application Browser Browser Java Application Server Application Application
Me and where I am from This presentation has been put together based on my experiences I have had whilst implementing systems over the last 8 years and it is my hope that by relating some of these experiences to you I can help you implement your systems more effectively.
Point 1 Enterprise means organisation wide Resource refers to all the resources at your disposal – customers Planning means looking at the long term view rather than just current and
Perhaps mention best of breed.
Move from 2 tier two three tier architecture. Simplified Deployment Other advantages of this architecture become apparent when we look at application deployment. In client server environments, you would need to install the application on each desktop. If you add new users, you need to install the application. If you want to upgrade.... you need to install the application. If we’ve learned one thing from Y2K compliance, it’s that upgrading 100’s or 1000’s of desktops is a challenge best avoided. The true, three-tier architecture avoids this pitfall. By storing the application on the middle tier, the ICA requires you to upgrade only the servers. Clients upgrade themselves. As soon as the browser detects that a new application version exists, it’s downloaded automatically. Even some “web” tools use plug ins that load windows components as opposed to IC architecture. These can be as difficult to uninstall as typical windows applications.
Point 1 There must be a value proposition, return on investment, total cost of ownership. Point 2-4 Often these can be part of your business goals as well.
It’s all really about control, it’s about aligning your people process and technology so that they master the raging waters of your high volume transactional system. People who have experienced Process You have to row in a certain way Technology You have to have a decent boat