erp and enterprise architecture

19
ERP And Enterprise Architecture Presented by 08-SE-10 08-SE-62

Upload: university-of-engineering-and-technology-taxila

Post on 01-Nov-2014

14.046 views

Category:

Education


5 download

DESCRIPTION

Models and description regarding ERP And Enterprise Architecture

TRANSCRIPT

Page 1: ERP And Enterprise Architecture

ERP And Enterprise Architecture

Presented by 08-SE-1008-SE-62

Page 2: ERP And Enterprise Architecture

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.

Page 3: ERP And Enterprise Architecture

ERP ApplicationsAre 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.

Page 4: ERP And Enterprise Architecture

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.

Page 5: ERP And Enterprise Architecture

ERP ArchitecturesTwo most commonly employed architectures

are :Two-tier Architecture.Three-tier Client/Server Implementation

Architecture.

Page 6: ERP And Enterprise Architecture

Two-tier ImplementationsThe 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.

Page 7: ERP And Enterprise Architecture

Two-tier ERP Architecture

Page 8: ERP And Enterprise Architecture

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.

Page 9: ERP And Enterprise Architecture

Three-tier Client/Server Implementation Architecture

Page 10: ERP And Enterprise Architecture

ERPEnterpriseResourcePlanning

Enterprise Architecture and ERP

EAEnterprise

Architecture

Page 11: ERP And Enterprise Architecture

Developing the Right Perspective is Critical!

ERPEnterpriseResourcePlanning

EAEnterprise

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

Page 12: ERP And Enterprise Architecture

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.

Page 13: ERP And Enterprise Architecture
Page 14: ERP And Enterprise Architecture

Integrated System ERP Program

Finance

HRIS

Procurement

Core ERP

LegacyApplication

LegacyApplication

LegacyApplication

Enterprise A

pplication Interfaces

Integrated System

AuthoritativeData Source

Page 15: ERP And Enterprise Architecture

Traditional View & Transitional View

Page 16: ERP And Enterprise Architecture

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)

Page 17: ERP And Enterprise Architecture
Page 18: ERP And Enterprise Architecture

Conclusion: ERP Architecture

Page 19: ERP And Enterprise Architecture

Click icon to add picture