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.
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.
 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.
EA Supports Agency Requirements Gathering
Integrated Data and Information from As-Is through “To Be State”

Using the
FEA-DRM

Finance

Chart of Accounts

Human Resources Other Central

Personnel Management
Services Functions…

Procurement

Procurement Management
ERP Architectures
Two most commonly employed architectures are :
Two-tier Architecture.
Three-tier Client/Server Implementation
Architecture.
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.
Two-tier ERP 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.
Three-tier Client/Server
Implementation Architecture
Enterprise Architecture and ERP

• Define AS-IS & TO-BE

EA functions for ERP
- Human Resources Enterprise
Enterprise
Resource
Architecture - Finance Planning
- Procurement

Sustainable Business Architecture for Decisions

• Alignment of EA to business needs.
• A Repeatable EA framework
• Architecture is visible across state agencies
 Developing the Right Perspective is Critical!

Shared Targeted
Interest Interest
• Enterprise • Informed by
perspective
EA ERP EA
• Rich Reqts
• Migration path Enterprise
to move Enterprise • Stake
toward target Architecture Resource
Holders
architectures Planning
• Consistent EA • Implement
methodology Bulletproof
statewide

Opportunities and Stewardship for:

- Improved performance
- Introduction of new capabilities
- Expanded responsibilities
- Reduced costs
- Leverage new technology
 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.

Integrated System ERP Program
Integrated System

Enterprise Application Interfaces

Legacy
Core ERP Application
Finance

HRIS Legacy
Application

Procurement
Legacy
Application

Authoritative
Data Source
Traditional View & Transitional View
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)
Conclusion: ERP Architecture
Click icon
to add pic
ture