ERP And Enterprise Architecture

Models and description regarding ERP And Enterprise Architecture

1. ERP And Enterprise Architecture Presented by 08-SE-10 08-SE-62

2. What is an ERP System? An ERP system is generally a term used to describe a set of applications that unify database input, processing and retrieval as well as multiple other business functions across a wide array of business units. Operations managers often choose to implement a system of ERP apps when they want to standardize processes and streamline functionality across many varying departments within an enterprise.

3. ERP Applications Are most commonly deployed in a distributed and often widely dispersed manner. While the servers may be centralized, the clients are usually spread to multiple locations throughout the enterprise. ERP Applications generally have three functional areas of responsibilities: The centralized database- central repository. the clients - here raw data gets inputted, requests for information are submitted. application component that acts as the intermediate between the client and the database.

4. Enterprise Architecture The process of translating business vision and strategy into effective enterprise change by creating, communicating and improving key requirements, principles and models that describe the enterprise’s future state and enable its evolution.

5. ERP Architectures Two most commonly employed architectures are : Two-tier Architecture. Three-tier Client/Server Implementation Architecture.

6. Two-tier Implementations The server handles both application and database duties. The clients are responsible for presenting the data and passing user input back to the server. This distribution of processing responsibilities remains the same even in the presence of multiple servers.

7. Two-tier ERP Architecture

8. Three-tier Client/Server implementation Architecture the database and application functions are separated. This is very typical of large production ERP deployments. satisfying client requests requires two or more network connections. the client establishes communications with the application server which then creates a second connection to the database server.

9. Three-tier Client/Server Implementation Architecture

10. ERP Enterprise Resource Planning Enterprise Architecture and ERP EA Enterprise Architecture

11. Developing the Right Perspective is Critical! ERP Enterprise Resource Planning EA Enterprise Architecture Shared Interest Enterprise perspective • Migration path to move toward target architectures Consistent EA methodology statewide Targeted Interest Informed by EA Rich Reqts Stake Holders Implement Bulletproof

12. What is the compelling business need for Enterprise Architecture? Business: Value to the Business Facilitates business transformation throughout the enterprise. Formalizes and captures knowledge about the business that helps identify new opportunities and clarify existing gaps . Provides a set of guidelines, standards, and blueprints that can be used to acquire, build and deploy business solutions . Technology: Value to the IT Organization Makes new initiatives easier to manage because they are designed and implemented according to architecture guidelines . Delivers a more manageable, agile IT environment . Aligns IT initiatives to business imperatives so that business benefits justify the costs. Allows IT to stay ahead of the curve with respect to the underlying technologies and infrastructure to support business applications .

13. Integrated System ERP Program Finance HRIS Procurement Core ERP Legacy Application Legacy Application Legacy Application Enterprise Application Interfaces Integrated System Authoritative Data Source

14. Traditional View & Transitional View

15. Transformational View Impressions: –Separation of Business and IT domains –Work Activities and Information are the domain of the business –App, Data and Technology are the domain of IT –Business Activities drive the Application Architecture –Business Information drives the Data Architecture –Technology Architecture directly enables data and applications (not business process/function and information)

16. Conclusion: ERP Architecture