Your SlideShare is downloading. ×
ERP And Enterprise Architecture
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ERP And Enterprise Architecture

14,948
views

Published on

Models and description regarding ERP And Enterprise Architecture

Models and description regarding ERP And Enterprise Architecture

Published in: Education, Technology, Business

3 Comments
5 Likes
Statistics
Notes
No Downloads
Views
Total Views
14,948
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
599
Comments
3
Likes
5
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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
    EA
    Enterprise
    Architecture
    Enterprise Architecture and ERP
  • 11. ERP
    Enterprise
    Resource
    Planning
    EA
    Enterprise
    Architecture
    Developing the Right Perspective is Critical!
    Targeted Interest
    Shared Interest
    • Enterprise perspective
    • Migration path to move toward target architectures
    • ConsistentEA methodology statewide
  • 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.
    • 15. Delivers a more manageable, agile IT environment.
    • 16. Aligns IT initiatives to business imperatives so that business benefits justify the costs.
    • 17. Allows IT to stay ahead of the curve with respect to the underlying technologies and infrastructure to support business applications.
  • 18. Integrated System ERP Program
    Legacy
    Application
    Legacy
    Application
    Legacy
    Application
    Integrated System
    Core ERP
    Finance
    HRIS
    Enterprise Application Interfaces
    Procurement
    Authoritative
    Data Source
  • 19. Traditional View & Transitional View
  • 20. 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)
  • 21.
  • 22. Conclusion: ERP Architecture

×