ERP [Compatibility Mode]

36
1 Enterprise Resource Planning Systems

Transcript of ERP [Compatibility Mode]

Page 1: ERP [Compatibility Mode]

1

Enterprise Resource Planning Systems

Page 2: ERP [Compatibility Mode]

Problems with NonSystems

In-house design limits connectivity outside the company

Tendency toward separate IS’s within firmlack of integration limits communication within the

company

Strategic decision-making not supportedLong-term maintenance costs highLimits ability to engage in process reengineering

2

Problems with Non-ERP Systems

house design limits connectivity outside the

Tendency toward separate IS’s within firmlack of integration limits communication within the

making not supportedterm maintenance costs high

Limits ability to engage in process reengineering

Page 3: ERP [Compatibility Mode]

Traditional IS Model: Closed Database Architecture

Similar in concept to flatdata remains the property of the applicationfragmentation limits communications

Existence of numerous distinct and independent databasesredundancy and anomaly problems

Paper-basedrequires multiple entry of datastatus of information unknown at key points

3

Traditional IS Model: Closed Database Architecture

Similar in concept to flat-file approachdata remains the property of the applicationfragmentation limits communications

Existence of numerous distinct and independent databases

redundancy and anomaly problems

requires multiple entry of datastatus of information unknown at key points

Page 4: ERP [Compatibility Mode]

Order EntrySystem

Manufacturingand

DistributionSystem

CustomerSales

Account Rec

ProductionSchedulingShipping

Customer Database Manufacturing Database

Business Enterprise

Customer

Products

Orders

Traditional Information System with Closed Database Architecture

Manufacturingand

DistributionSystem

ProcurementSystem

ProductionSchedulingShipping

VendorAccts PayInventory

Manufacturing Database

Procurement Database

Business Enterprise

SupplierPurchases

Materials

Traditional Information System with Closed Database Architecture

Page 5: ERP [Compatibility Mode]

What is ERP?

Those activities supported by multiapplication software that help a company manage the important parts of its business in an integrated fashion.

Key features include:Smooth and seamless flow of information

across organizational boundariesStandardized environment with shared

database independent of applications and integrated applications

5

What is ERP?

Those activities supported by multi-module application software that help a company manage the important parts of its business in an integrated fashion.

Smooth and seamless flow of information across organizational boundariesStandardized environment with shared database independent of applications and integrated applications

Page 6: ERP [Compatibility Mode]

Data Warehouse

On-Line Analytical Processing(OLAP)

Sales&

Distribution

BusinessPlanning

Customers

Operational DatabaseCustomers, Production,Vendor, Inventory, etc.

Core Functions [On-Line Transaction Processing (OLTP)]

ERP System

Business EnterpriseERP System

Bolt-On Applications(Industry Specific Functions)

Shop FloorControl Logistics

Suppliers

Operational DatabaseCustomers, Production,Vendor, Inventory, etc.

LegacySystems

Line Transaction Processing (OLTP)]

ERP System

Business Enterprise

Page 7: ERP [Compatibility Mode]

Two Main ERP ApplicationsCore applicationsa.k.a. Online Transaction Processing (OLTP)transaction processing systemssupport the day-to-day operational activities of

the businesssupport mission-critical tasks through simple

queries of operational databases include Sales and Distribution, Business

Planning, Production Planning, Shop Floor Control, and Logistics modules

7

Two Main ERP Applications

Online Transaction Processing (OLTP)transaction processing systems

day operational activities of

critical tasks through simple queries of operational databasesinclude Sales and Distribution, Business Planning, Production Planning, Shop Floor Control, and Logistics modules

Page 8: ERP [Compatibility Mode]

Two Main ERP ApplicationsBusiness analysis applicationsa.k.a. Online Analytical Processing (OLAP)decision support tool for management

through analytical investigation of complex data associations

supplies management with “realpermits timely decisions to improve performance and achieve competitive advantage

includes decision support, modeling, information retrieval, ad-hoc reporting/analysis, and whatanalysis

8

Two Main ERP ApplicationsBusiness analysis applications

Online Analytical Processing (OLAP)decision support tool for management-critical tasks through analytical investigation of complex data

supplies management with “real-time” information and permits timely decisions to improve performance and achieve competitive advantage includes decision support, modeling, information

hoc reporting/analysis, and what-if

Page 9: ERP [Compatibility Mode]

OLAPSupports management-

analytical investigation of complex data associations captured in data warehouses:Consolidation is the aggregation or roll

of data.Drill-down allows the user to see data in

selective increasing levels of detail.Slicing and Dicing

examine data from different viewpoints often performed along a time axis to depict trends and patterns.

9

OLAP-critical tasks through

analytical investigation of complex data associations captured in data warehouses:

is the aggregation or roll-up

allows the user to see data in selective increasing levels of detail.

enables the user to examine data from different viewpoints often performed along a time axis to depict trends

Page 10: ERP [Compatibility Mode]

ERP System Configurations:Client-Server Network Topology

Two-tiercommon server handles both application and

database duties used especially in LANs

10

ERP System Configurations:Server Network Topology

common server handles both application and

used especially in LANs

Page 11: ERP [Compatibility Mode]

Server

Applications

First Tier

Second Tier

Two-Tier Client Server

Database

User Presentation Layer

Application and Database Layer

Tier Client Server

Server

Page 12: ERP [Compatibility Mode]

ERP System Configurations:Client-Server Network Topology

Three-tierclient links to the application server which

then initiates a second connection to the database serverused especially in WANs

12

ERP System Configurations:Server Network Topology

client links to the application server which then initiates a second connection to the

used especially in WANs

Page 13: ERP [Compatibility Mode]

Three-Tier Client Server

Applications

Database

First Tier

Second Tier

Third Tier

Tier Client Server

User Presentation Layer

Application Layer

Database Layer

Application Server

Database Server

Page 14: ERP [Compatibility Mode]

ERP with OLTP and OLAP Client Server using Data Warehouse

OLTP Server

OLTPApplications

Operations Database

Server

OperationsDatabase

First Tier

Second Tier

Third Tier

ERP with OLTP and OLAP Client Server using Data Warehouse

User Presentation Layer

Application Layer

Database Layer

OLAP Server

OLAPApplications

DataWarehouse

Server

Data Warehouse

Page 15: ERP [Compatibility Mode]

ERP System Configurations:Databases and Bolt

Database Configurationselection of database tables in the thousandssetting the switches in the system

Bolt-on Softwarethird-party vendors provide specialized

functionality softwareSupply-Chain Management (SCM)

vendors, carriers, thirdcompanies, and information systems providers

15

ERP System Configurations:Databases and Bolt-Ons

Database Configurationselection of database tables in the thousandssetting the switches in the system

party vendors provide specialized functionality software

Chain Management (SCM) links vendors, carriers, third-party logistics companies, and information systems

Page 16: ERP [Compatibility Mode]

What is a Data Warehouse?

A relational or multi-dimensionalconsume hundreds of gigabytes or even terabytes of disk storageThe data is normally extracted periodically from operational

database or from a public information service. A database constructed for quick searching, retrieval,

ad-hoc queries, and ease of use An ERP system could exist without having a data

warehouse. The trend, however, is that organizations that are serious about competitive advantage deploy both. The recommended data architecture for an ERP implementation includes separate operational and data warehouse databases

16

What is a Data Warehouse?

dimensional database that may consume hundreds of gigabytes or even terabytes of

The data is normally extracted periodically from operational database or from a public information service.

A database constructed for quick searching, retrieval, hoc queries, and ease of use

An ERP system could exist without having a data warehouse. The trend, however, is that organizations that are serious about competitive advantage deploy both. The recommended data architecture for an ERP implementation includes separate operational and data

Page 17: ERP [Compatibility Mode]

Data Warehouse Process

The five essential stages of the data warehousing process are:

Modeling data for the data warehouse Extracting data from operational databases Cleansing extracted data Transforming data into the warehouse model Loading the data into the data warehouse

database

17

Data Warehouse Process

The five essential stages of the data warehousing process are:

Modeling data for the data warehouseExtracting data from operational databasesCleansing extracted dataTransforming data into the warehouse modelLoading the data into the data warehouse

Page 18: ERP [Compatibility Mode]

Data Warehouse Process:Stage 1

Modeling data for the data warehouseBecause of the vast size of a data

warehouse, the warehouse database consists of de-normalized data. Relational theory does not apply to a data

warehousing system.Wherever possible normalized tables pertaining to

selected events may be consolidated into denormalized tables.

18

Data Warehouse Process:Stage 1

Modeling data for the data warehouseBecause of the vast size of a data warehouse, the warehouse database consists

normalized data. Relational theory does not apply to a data

Wherever possible normalized tables pertaining to selected events may be consolidated into de-

Page 19: ERP [Compatibility Mode]

Data Warehouse Process:Stage 2

Extracting data from operational databasesThe process of collecting data from

operational databases, flatexternal data sources.Snapshots vs. Stabilized Data:a key feature of a data warehouse is that the

data contained in it are in a nonstate.

19

Data Warehouse Process:Stage 2

Extracting data from operational

The process of collecting data from operational databases, flat-files, archives, and external data sources.Snapshots vs. Stabilized Data:

a key feature of a data warehouse is that the data contained in it are in a non-volatile (stable)

Page 20: ERP [Compatibility Mode]

Data Warehouse Process:Stage 3

Cleansing extracted dataInvolves filtering out or repairing invalid data

prior to being stored in the warehouse Operational data are “dirty” for many reasons:

clerical, data entry, computer program errors, misspelled names, and blank fields.

Also involves transforming data into standard business terms with standard data values

20

Data Warehouse Process:Stage 3

Cleansing extracted dataInvolves filtering out or repairing invalid data prior to being stored in the warehouse

Operational data are “dirty” for many reasons: clerical, data entry, computer program errors, misspelled names, and blank fields.

Also involves transforming data into standard business terms with standard data values

Page 21: ERP [Compatibility Mode]

Data Warehouse Process:Stage 4

Transforming data into the warehouse modelTo improve efficiency, data is transformed into

summary views before they are loaded.Unlike operational views, which are virtual in

nature with underlying base tables, data warehouse views are physical tables. OLAP, however, permits the user to construct virtual

views from detail data when one does not already exist.

21

Data Warehouse Process:Stage 4

Transforming data into the warehouse modelTo improve efficiency, data is transformed into summary views before they are loaded.Unlike operational views, which are virtual in nature with underlying base tables, data warehouse views are physical tables.

OLAP, however, permits the user to construct virtual views from detail data when one does not already

Page 22: ERP [Compatibility Mode]

Data Warehouse Process:Stage 5

Loading the data into the data warehouse databaseData warehouses must be created and

maintained separately from the operational databases.Internal EfficiencyIntegration of Legacy SystemsConsolidation of Global Data

22

Data Warehouse Process:Stage 5

Loading the data into the data warehouse

Data warehouses must be created and maintained separately from the operational

Integration of Legacy SystemsConsolidation of Global Data

Page 23: ERP [Compatibility Mode]

Current (this weeks) Detailed Sales Data

Sales Data SummarizedQuarterly

Data CleansingProcessOperations

Database

VSAM FilesHierarchical DB

Network DB

Data Warehouse System

Sales Data Summarized Annually

PurchasesSystem

Order Entry

System

ERPSystem

Legacy Systems

Current (this weeks) Detailed

Sales Data Summarized

Data Warehouse System

The Data Warehouse

Sales Data Summarized Annually

Page 24: ERP [Compatibility Mode]

Risks Associated with ERP Implementation

Pace of ImplementationBig Bang--switch operations from legacy

systems to ERP in a single eventPhased-In--independent ERP units installed

over time, assimilated and integratedOpposition to Changes to the Businesses

Culture User reluctance and inertiaNeed of (upper) management support

24

Risks Associated with ERP Implementation

Pace of Implementationswitch operations from legacy

systems to ERP in a single eventindependent ERP units installed

over time, assimilated and integratedOpposition to Changes to the Businesses

User reluctance and inertiaNeed of (upper) management support

Page 25: ERP [Compatibility Mode]

Risks Associated with ERP Implementation

Choosing the Wrong ERPGoodness of Fit: no ERP system is best for all

industriesScalability: system’s ability to grow

Choosing the Wrong ConsultantCommon to use a thirdBe thorough in interviewing potential

consultantsEstablish explicit expectations

25

Risks Associated with ERP Implementation

Choosing the Wrong ERPGoodness of Fit: no ERP system is best for all

Scalability: system’s ability to grow

Choosing the Wrong ConsultantCommon to use a third-party (the Big Five)Be thorough in interviewing potential

Establish explicit expectations

Page 26: ERP [Compatibility Mode]

Risks Associated with ERP Implementation

High Cost and Cost OverrunsCommon areas with high costs:TrainingTesting and IntegrationDatabase Conversion

Disruptions to OperationsERP is reengineering

in how business is done

26

Risks Associated with ERP Implementation

High Cost and Cost OverrunsCommon areas with high costs:

Testing and IntegrationDatabase Conversion

Disruptions to OperationsERP is reengineering--expect major changes in how business is done

Page 27: ERP [Compatibility Mode]

Implications for Internal Control and Auditing

Transaction AuthorizationControls are needed to validate transactions

before they are accepted by other modules. ERPs are more dependent on programmed

controls than on human intervention.Segregation of DutiesManual processes that normally require

segregation of duties are often eliminated.User role: predefined user roles limit a user’s

access to certain functions and data.

27

Implications for Internal Control and Auditing

Transaction AuthorizationControls are needed to validate transactions before they are accepted by other modules. ERPs are more dependent on programmed controls than on human intervention.

Segregation of DutiesManual processes that normally require segregation of duties are often eliminated.

predefined user roles limit a user’s access to certain functions and data.

Page 28: ERP [Compatibility Mode]

Implications for Internal Control and Auditing

SupervisionSupervisors need to acquire a technical and

operational understanding of the new system.Employee-empowered philosophy should not

eliminate supervision.Accounting RecordsCorrupted data may be passed from external

sources and from legacy systems. Loss of paper audit trail

28

Implications for Internal Control and Auditing

Supervisors need to acquire a technical and operational understanding of the new system.

empowered philosophy should not eliminate supervision.

Corrupted data may be passed from external sources and from legacy systems. Loss of paper audit trail

Page 29: ERP [Compatibility Mode]

Implications for Internal Control and Auditing

Access ControlsCritical concern with confidentiality of

informationWho should have access to what?

Access to Data WarehouseData warehouses often involve sharing

information with suppliers and customers.

29

Implications for Internal Control and Auditing

Critical concern with confidentiality of

Who should have access to what?

Access to Data WarehouseData warehouses often involve sharing information with suppliers and customers.

Page 30: ERP [Compatibility Mode]

Implications for Internal Control and Auditing

Contingency PlanningHow to keep business going in case of

disasterKey role of servers requires backup plans:

redundant servers or shared servers

Independent VerificationTraditional verifications are meaninglessNeed to shift from transaction level to overall

performance level30

Implications for Internal Control and Auditing

Contingency PlanningHow to keep business going in case of

Key role of servers requires backup plans: redundant servers or shared servers

Independent VerificationTraditional verifications are meaninglessNeed to shift from transaction level to overall

Page 31: ERP [Compatibility Mode]

Implications for Internal Control and Auditing

ERP projects may be concurrent with BPR, CRM, Data Warehousing, SCMAll of these increase risk of successful

implementationERP systems impact organizational

structure and internal controlsNew control policies must precede

migration to an ERP system

31

Implications for Internal Control and Auditing

ERP projects may be concurrent with BPR, CRM, Data Warehousing, SCMAll of these increase risk of successful

ERP systems impact organizational structure and internal controlsNew control policies must precede migration to an ERP system

Page 32: ERP [Compatibility Mode]

Implications for Internal Control and Auditing

Gartner Group noted following concerns regarding implementing ERP:

32

Implications for Internal Control and Auditing

Gartner Group noted following concerns regarding implementing ERP:

Page 33: ERP [Compatibility Mode]

Audits of ERPs

Audit could provide assurance covering the areas of …process integrityapplication securityinfrastructure integrityimplementation integrity

33

Audits of ERPs

Audit could provide assurance covering the

infrastructure integrityimplementation integrity

Page 34: ERP [Compatibility Mode]

ERP Products

SAP: largest ERP vendormodules can be integrated or used alonenew features include SCM, B2B, e

XMLJ.D. Edwardsflexibility: users can change features; less of

a pre-set structure than SAP’smodularity: accept modules (bolt

other vendors

34

ERP Products

: largest ERP vendormodules can be integrated or used alonenew features include SCM, B2B, e-commerce,

: users can change features; less of set structure than SAP’s

: accept modules (bolt-ons) from

Page 35: ERP [Compatibility Mode]

ERP Products Oracletailored to e-business focusInternet based vs. client

applications

PeopleSoftopen, modular architecture allows rapid

integration with existing systems

Baanuse of “best-of-class” applications

35

ERP Products

business focusInternet based vs. client-server based

open, modular architecture allows rapid integration with existing systems

class” applications

Page 36: ERP [Compatibility Mode]

this concludes the ERP slide presentation

36

this concludes the ERP slide