Modern ERP Select Implement and Use Today's Advanced Business Systems Author Marianne Bradford

May 28, 2016 | Author: Pramila Nagaraj | Category: Types, Presentations
Share Embed Donate


Short Description

Modern ERP Select Implement and Use Today's Advanced Business Systems...

Description

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition

Chapter 1: Introduction to Enterprise Resource Planning System

ERP Background • Introduction of PC led to narrowly focused information systems • Duplicate data across the enterprise not shared between departments • Mid – late 1990’s many large companies implemented Enterprise Resource Planning (ERP) which would integrate the data across the enterprise and replace outdated systems (legacy systems).

Legacy Systems:  The case for not changing • The system works fine and the company sees no reason for changing it. • The costs of redesigning or replacing the system are prohibitive because it is large, monolithic, and/or complex. • Retraining on a new system would be costly in lost time and money, compared to the anticipated appreciable benefits of replacing it (which may be zero). • The system requires near-constant availability, so it cannot be taken out of service, and the cost of designing a new system with a similar availability level is high. Examples include systems to handle customers' accounts in banks, computer reservation systems, air traffic control, energy distribution (power grids), nuclear power plants, military defense

What is ERP?  • An ERP system is an integrated suite of information technology applications that support the operations of an enterprise from a process perspective. – Cross-Functional – serves many functions – Process-Centered – organized around processes

• Built upon relational database systems

– There is one data store, one source of the truth

• Sold in modules

ERP­Supported Business Processes

* Core ERP Processes

Typical Modules in an ERP System Operations (Core) · Bills of Material · Scheduling · Process Manu. · Quality Control · Discrete Manu. · Shop Floor Mgmt. · Order Entry · Purchasing · Supply Chain · Supplier Planning Scheduling · Demand · Sourcing Management Financials (Core) · General Ledger · Cash Management · Accounts Payable · Accounts Receivable · Fixed Assets · Controlling Projects · Project Costing · Project Billing · Time and Expense · Activity · Resource Availability · Project Contracts Management Human Resources (Core) · Human Resources · Payroll · Training · Time & Attendance · Benefits · Recruiting Customer Relationship Management · Sales and Marketing · Commissions · Service · Customer Contact · Call Center Support · Analytics Plus: Various Self-Service Interfaces for Customers, Suppliers, and Employees · Engineering · Capacity · Cost Management · Inventory · Product Configuration · Quality Control

Who Uses/Needs to know about ERP? • End User – Purchasing – Manufacturing – Sales – Accounting/Finance – Human Resources – etc

• Internal/external auditor – Verify that the ERP system is secure and maintains privacy over individuals. Also has proper segregation of duties (SoD).

• Consultant – Assist in implementation and or maintenance of ERP systems

• Developers – Customize the system

ERP Value – Integration  The value of ERP is the opportunity to integrate an entire organization by having a single point of entry and sharing of data across the enterprise. • ERP becomes the authoritative data source: a recognized or official data production source with a designated mission statement to publish reliable and accurate data for subsequent use by users. Creates less need to reconcile data and rekey which causes inefficiencies and delays Inefficient business processes that were disjointed become much more efficient.

Before and After ERP

•Legacy systems (islands of automation) may be connected with enterprise application integration (EAI) - the process of linking such applications within a single organization together in order to simplify and automate business processes to the greatest extent possible, while at the same time avoiding having to make sweeping changes to the existing applications or data structures. Not as optimal as having an integrated system, common database, and common technical infrastructure.

ERP Diffuses Best Practices • ERP systems are based on best practices • For instance, SAP has thousands of best practices embedded in their applications. – This means that any firm that installs has access to a wide range of best practices. • Further, business practices are being added all of the time. As new best practices are found and embedded in particular applications, they can become available for inclusion in new versions of software. • As a result, there is a cycle of finding best practices, building them into the software

ERP Facilitated Adoption of Client  Server Computing • In the early 1990’s ,client server computing became available and offered many advantages over existing mainframe solutions. • Client/server describes the relationship between two computer programs in which one program, the client, makes a service request from another program, the server, which fulfills the request. • ERP became one of the dominant, initial corporate applications of client server computing.

Technical ERP System Benefits   • • • • • •

Integrated processes and information systems More effective and efficient business processes Enables organizational standardization Eliminates information asymmetries Provides on-line and real-time information Facilitates intra- and inter-organization communication and collaboration • Can reduce complexity of application and technology portfolios

ERP System Benefits – Integrate financials – Have one view of the customer – Standardize manufacturing processes – Reduce inventory/better visibility into inventory – Standardize information such as HR and Customer data there are others……depends on company

ERP System Disadvantages • Standardized way of conducting business can be a disadvantage too because levels the playing field somewhat between companies • Lack of employee/user acceptance • Complex solution • Maintenance of hardware and software • Costly and time consuming implementations

Implementation Issues • Employee resistance – They develop “work arounds” – Sabotage implementation process – Caused by lack of training (“how”) or understanding of organization’s motivation for adoption (“why”) – Need Change Management to lower resistance

• Technical Issues – Complex system to implement – configuration issues and possible

ERP Evolution • Roots are in Manufacturing Requirements Planning (MRP) & Manufacturing Resource Planning (MRP II) – Addressed needs of just the manufacturing environment – ERP manages resources for entire enterprise

• With Y2K looming, companies began implemented new state of the art systems (ERP) that ran on client server technology • Now many companies outsource called Software as a Service (SaaS) – Multi-tenancy – serve many clients from a single instance via the Internet

• Open Source ERP systems are evolving – where’s the help desk though!?

ERP Market • Billion dollar industry and growing – 10% growth rate through 2012

• Growth drivers – Globalization – Centralization – Competition – Best practices etc

Figure 1-2: ERP Application Revenue Estimate 2007-2012 in Billions

Source: AMR research

ERP Tiers multi-site, multi-national corporations, government entities with 1000 or more employees

• Tier 1 Vendor – “Enterprise Space” -

– #1 SAP • Stands for Systems, Applications and Products in Data processing • Formed by 5 former IBM engineers in 1972 in Walldorf Germany • SAP AG, SAG UK, SAP North America etc • Nearly 200,000 customers, over 50,000 employees • Service over 20 different industries

– #2 Oracle • More than 380,000 customers—including 100 of the Fortune 100 —and with deployments across a wide variety of industries in more than 145 countries around the globe, • In 2003 acquired PeopleSoft, Hyperion and Siebel

ERP Tiers • Tier 2 Vendors – Market towards medium sized companies, few sites, 100-999 employees – Largest of all ERP tiers in number of potential customers – Tier 1 vendors moving into this area and below by reducing prices and simplifying product – Some vendors – QAD and SSA

• Tier 3 Vendors – Market towards small, single site, family run corporations, sales under $40 million and less than 100 employees – Vendors – Microsoft Dynamics GP, NetSuite, Made-2-Manage, SAP Business by Design, SAP Business All in One

• Tier 4 Vendors – Market towards small companies that can manage with basic accounting software – Vendors – Peachtree, Accpac, Quickbooks, SAP Business One, SAP Business by Design

An Enterprise System ­ Reality

In reality, an ERP implementation is usually just one part of a more complex environment, including bolt-ons, legacy applications retained, possible data warehouse(s), enterprise application integration (EAI) solutions and connections to

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition

Chapter 2: ERP Technology

IT Infrastructure for ERP • Early systems mainframe based • 1990’s client server, three-tier – Client – fat client/thin client – Application (business logic) – Database Figure 2-1: Three-Tier Architecture

ERP Interface • With ERP software, the GUI can take the form of a dashboard customized to suit the needs and preferences of a set of users or a specific user. • Can include: – Business process activity based on production or logistics information. – Tasks, reminders and other notifications. – Calendaring and scheduling resources. – Messaging including email, instant messaging and telephone traffic. – Official communications from designated sources.

SAS Portal 

Figure 2-2: SAS Institute Dashboard

Source: SAS Institute, Inc.

Back Office/Front Office • Back-office software (Core ERP) –HR, Financials, and Operations • Front-office software integrates with customers and suppliers – supply chain management and customer relationship management • Bolt-ons are used to integrate more functionality to Core ERP Figure 2 -3: Core ERP and ERP Bolt-Ons

Relational Database Terminology • Tables are relations – Tables and forms (visuals of tables) show up on screens in ERP menus.

• Fields are attributes in the table (in columns) • Records are instances in the table (in rows) • Each table has a primary key that is the unique. – Usually the primary key is some sort of code. – Can not be null or empty – Entity integrity rule

Entity­Relationship Diagram  • ERDs are a type of system diagramming that show relationships between tables. – Relationships are rules that show how tables relate to one another.

• Types of relationships – One-to-one: the primary key of one table is associated with only one record in another table – One-to-many: the primary key of one table is associated with more than one record in another table – Many-to-many: the primary key in one table is associated with more than one record in a second table and the primary key in the second table is associated with more than one record in the first table

Relational Database Example

Figure 2-4: Relational Database Overview

Database Query and Manipulation • A query is a question asked of the database. Again, ERP systems have many standard queries coded into the software in the form of menus. Menus can be customized to add/change/delete queries. – Structured Query Language (SQL) is a database querying language • Simple Query – returns a response without changing the database • Update Query – changes records in a database

• Data Manipulation – operations alter the database – Inserting new rows into tables – Updating existing rows – Deleting rows from tables

Configure vs. Customize ERP • Configuration involves “setting switches” during implementation that determine how the system will execute business processes. – Example of configuring: reporting relationships, options having to do with how business processes work, auditing mechanisms, organizational structure. • Customization is changing software code. – This is expensive and time consuming. – Only do if necessary and believed to lead to a competitive advantage. – Don’t customize because you feel your employees will resist a new way of work….that is the point of ERP!

– Vanilla is not customizing the software.

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition Chapter 3: ERP and Business Process Reengineering

Business Process Reengineering  • Concept coined by Michael Hammer Reengineering the Corporation… • Business Process Reengineering is the fundamental, radical, redesign in business processes to achieve dramatic improvements in key measures of performance such as cost, quality, speed, and service • The focus of BPR is not on how a process is done, but WHY it is done

Benefits vs. Challenges of BPR Benefits • Cost Reductions • Improved Customer Satisfaction • Improved Agility • Increased Profitability and Reputation

Risks

• Resistance from employees • Cost • Job losses • Tradition and culture • Time requirements • Lack of management support • Risks to managers • Retraining

Types of Reengineering  • Clean Slate Reengineering – Process design starts with a clean slate – Also referred to as “starting from scratch” – Theoretically, no limits

• Technology-Enabled Reengineering – A particular technology (or portfolio of technologies) is chosen as a tool to facilitate reengineering – The technology drives the reengineering

Clean Slate Reengineering  Advantages: • Not constrained by a particular tool • Not constrained to a limited set of processes • Evolution is not limited by a particular technology • Can result in unique processes (which gives a competitive advantage) • Encourages a free flow of ideas

Disadvantages:  Costly  Excess time and resources (makes it difficult for smaller companies in an industry to afford)

Technology­Enabled Reengineering  Advantages: • ERP provides the tool and structure to facilitate change

– Roadmaps lead to less time • ERP bounds the design which eliminates difficult decisions • Design is feasible and we know it works (it’s been proven)

– Less risk

Disadvantage  Constrained by a technology, evolution limited by that technology, limited by certain best practices in that technology  Not unique – no competitive value perhaps (which incidentally is why orgs may customize); other companies have access to the design

Business Process Reengineering Principles  • Have those who use the output of the process, perform the process • Empower workers • Treat geographically dispersed resources as though they were centralized • Link parallel activities instead of integrating their results • Organize around processes, not tasks or functional areas • Self service • Put the decision point where the work is performed and build controls into the process

Targets for Reengineering  • Process as Part of a Core Competency – A core competency is a company’s process that transforms generic inputs into uniquely developed products or services that provide it with a competitive advantage – Key Performance Indicators - allow the company to compare its performance to industry best practices

• High Volume, Low Margin Activities • High Defect, High Reward Activities – Quality Controls – reduce error rate, but can be costly

• High Skill, Time Intensive Activities • High Complexity, Specialized Resource Activities – “KISS” or “keep it simple stupid”

• Process Built around Obsolete or Changing Technology

Lessons Learned through BPR • Low cost labor • Scalability – both up and down • Think outside the functional box – using BPR techniques to connect silos • Look at other companies for similar solutions to similar processes • Recognize that a process is just one aspect of success • Deliver sooner rather than later – setting and meeting more short-term goals

Reengineering Challenges • • • • • • • •

Resistance from employees Cost Job losses Tradition and culture Time requirements Lack of management support Risks to managers Retraining

Constituents for Reengineering  • • • • • • • •

Customers Employees Information Technology Staff Business Partners Upstream Supply Chain Auditors Regulators Interested Parties

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition Chapter 4: ERP: Systems Diagramming and the Process Map

Systems Documentation  • Basic Purposes for Systems Documentation 1. Describing business processes 2. Assessing internal control procedures 3. Evaluating, designing, or changing information systems

• Systems Diagram – a graphical representation of systems –. Flowcharts –. ER Diagrams –. Other techniques

Importance of Systems Diagramming • A recent study found that 72% of private and 82% of public companies have increased emphasis on reading or preparing systems documentation since the passage of the Sarbanes-Oxley Act of 2002 • A 2006 research study found that: – The ability to read systems diagrams was “very important” or “somewhat important” – 77% – The ability to prepare systems diagrams was “very important” or “somewhat important” – 66%

Process Maps • A process map, also known as a cross-functional flowchart, is used by many organizations seeking to document, analyze, streamline, and redesign business activities • Benefits: – Defining the “as is” business process and clarifying the changes necessary to transform the present process into the “to be” process – Determining whether “as is” measures are appropriate – Promoting awareness of employees’ responsibilities – Showing the impact a certain role’s performance has on upstream and downstream activities in the process – Highlighting workflow inefficiencies – Identifying opportunities to streamline and improve processes – Pinpointing internal controls that need to be tested during an audit

Process Map Symbols  • Activities (or events): transform inputs into outputs • Decision points: yes/no (positive/negative) outcome that depicts the alternatives • Process flow lines: connect symbols and are labeled with the type of information flowing into or out of the activities • Data stores: support the process • Termination: points at which the process ends • On-page connector: reduce clutter on a page • Off-page connector: when processes span multiple pages

Gathering Information for a Process Map • Group interview method – all people involved in the process are interviewed as a group – Employs a skilled facilitator to promote and focus the discussions, questioning conventional wisdom and providing an unbiased, objective point of view

• One-on-one interview method – each person involved in the process is interviewed separately – Less effective than the group interview method

• Walkthrough – physically reviewing a process in scope – To confirm if a documented process is accurately

Guidelines to Developing a Process Map  • Have a defined purpose for mapping a process and explain it to those participating • Identify the scope of the process • Determine the roles participating in the process – Roles become horizontal bands called swim lanes

• Determine the trigger, the event that must occur to get the process started – The trigger should be in the first swim lane

• Events should move left to right/top to bottom to indicate the passage of time • The information being exchanged is entered on the process flow lines • Decision descriptors should end with a question mark, and the process flow lines coming out of the decision are labeled with outcomes • The last swim lane is reserved for the information systems that support the process

Process Map Example Figure 4 – 2: Electric City Order Fulfillment Process Map

Hints for Constructing Process Maps  • Make sure every area of the map contains approximately the same amount of effort • Start with a high level process map, then use a detailed documentation worksheet to back up activities • Take notes while mapping and create a glossary of acronyms • Use humps when flow lines intersect on the process map • Allow swim lanes to retain the same role throughout the map even if the map spans multiple pages • Terminate the process in the swim lane where the process ends

Advanced Process Map Example Figure 4 – 3: Monster Furniture Process Map (Page 1)

Advanced Process Map Example Figure 4 – 4: Monster Furniture Process Map (Page 2)

Process Problems to Uncover • Handoffs – transferring of responsibility from one role to another – Provides the opportunity for mistakes, miscommunications, and delay

• Bottlenecks – a number of process flows lead to a single activity – Limit the performance or capacity of the entire system, delaying or completely stopping the process

• Rework – people spending time fixing errors or remediating problems • Role ambiguity – people not knowing what they are responsible for and others do – Eliminating confusion among the participants in the process

• Data duplication – flows that point to and from information systems can be analyzed, to identify the extent to which the necessary data and the activities that create or use the data can be shared among the organization’s many processes

Process Problems to Uncover Issues  • Cycle time – the time consumed during process flow from start to finish..how long is it and how long should it be? – Should be at the heart of performance measurement

• Flow time – time between activities can be measured to identify substantial contributors to delay and underutilization • Non value-added steps – looking at processes from the customer’s point of view provides focus on roles or activities that add little or no value – Unnecessary or repetitive steps – process flows that dead end with suboptimal results or wind back around to the same event or role a number of times

Process Decision Issues to Uncover • Authority ambiguity –clearly defines who owns the decision – Eliminate a potential source of confusion

• Decision necessity – when decision point output flows lead toward the same or similar events, the process may include unnecessary decisions that may generated unwarranted delays • Decisions too early – when decision point output flows continue for a long time before encountering subsequent events, the decision point may, in fact, be made too early – Leads to unnecessary downstream complications

• Decisions too late – when decision point output flows lead to errors or rework, decision points might need to be moved to earlier to provide quality assurance or confirmation of customer

Developing the “To­be” Process – Who is the customer? What is the customer willing to pay for? What does the customer receive? – What level of performance does the customer expect? How well are we satisfying the customer? How can we increase customer satisfaction? – What is our first interaction with the customer that starts the process? Where do our processes end and which endings are optimal? – What are the most important value-added steps? – What activities are in scope that we can change and what activities are out of scope that we cannot change?

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition Chapter 5: ERP Life Cycle: Planning and Package Selection

Why Change Information Systems  • • • • • • • •

Obsolescence High operational costs Lack of vendor support Lack of compliance Changing business model Different or enhanced functionality Lack of scalability Too many business problems and unanswered questions • More

The ERP Life Cycle  • Planning (Chapter 5) • Package Selection (Chapter 5) • Implementation (Chapter 6) • Maintenance (Chapter 6)

ERP Life Cycle: Planning  • Need a rationale grounded in a business case (high level reason why a company undertakes an ERP implementation) • Types of rationales: – Technology rationale – IS are failing, desperately need new technology. • Too expensive to patch and maintain old, outdated systems, need better visibility of data.

– Competitive rationale – adopting a system because the competition has it, need to keep up – Strategic rationale – reasons why ERP is needed to support the organization’s strategic direction

• Drive growth, support mergers and acquisitions, market diversification, globalization – Business process rationale – benefits in key processes (KPIs)

• Attain targeted, specific, and measureable performance improvements

ERP Life Cycle: Planning  • Executive Leadership – rally support, distribute resources, and delegate management of implementation to team – CEO, CFO, or other high level sponsor should take ownership of the project and be actively involved in its activities . – This is not a technical project, so CIO not the top sponsor.

• Project Scope – project team should determine the scope and the procedures to enforce against the “never ending project” syndrome – Project scope includes: business processes that will be included in the implementation, the ERP functionality that will support these business processes, the divisions or business units that will be included in the roll-out, and the technical infrastructures that will be replaced – Scope management – define and control what is and what is not included in the project; guard against scope creep – changes to the scope of the project.

ERP Life Cycle: Planning  • Project Team – Given the discretion to make all important decisions regarding the implementation – Consists of key process owners, end users, managers, IT people, and executives who span functional boundaries, business units, and organizational  Project Manager levels Understand both technology and business

processes Knowledge of the effect of ERP on the business Work with professionals to organize a smooth transition from the “as is” state to the “to be” state Envision the end results and make tough decisions

ERP Costs • Total cost of ownership (TCO) – total costs that will likely be incurred throughout the system’s life cycle that are influenced by: – Transaction volume – Number of users – Functionality

• Application license – govern the software’s use – Named users – company identifies the total number of users who will access the system – Site license – blanket contract covering the use of the ERP system at a particular location – Concurrent users – maximum number of users who would potentially access the system at a given time – Heavy users – those who use more of the systems functionality and may be charged a higher license fee than casual users who may only view reports or run occasional queries

ERP Costs • Database License – based on the number of simultaneous users that will log into the system or the number/type of database servers required • Hardware – varies depending on the scope of implementation and platforms – Will need database and application servers, storage systems, network components, wiring, power, user workstations, and redundancy

• Implementation Services – often a multiplier of software license costs – Ratio of services to software costs provides an indication of a system’s ease of implementation or support for more advanced or custom functionality

• Internal HR Costs – varies among companies and projects – Full time equivalents

• Ongoing Maintenance – typically 20 – 30% of the software license costs per year • Hidden Costs – scope creep, training, customization, data conversion, and developing interfaces between the ERP system and other systems

ERP Benefits  • Integrate financial information – creates one version of the truth, which can not be questioned because everyone uses the same system • Integrate customer order information – customer order travels from the salesperson through credit, picking, packing, shipping, invoicing and cash receipt • Standardize and speed up manufacturing processes • Reduce inventory – help manufacturing process flow more smoothly, improving visibility of the order fulfillment process • Standardize human resource information – consolidates employee information into a single system and provides self-service accessibility to manages and employees

ERP Life Cycle: Package Selection  • Package selection presumes that a highlevel organizational group has approved funding based on the business case outlined by the project team • Choosing the “best” application for a company is based on: functionality, affordability, userfriendliness, customizability, and vendor support

 Key steps in selecting

an ERP system: Market Survey Request for

Information Narrowing Down the Choices Site Survey Requirements Analysis Request for Proposal Demo Days Reference Visits Fit-Gap Analysis Implementation Methodology Discussion 

ERP Life Cycle: Package Selection  • Market Survey – to determine which vendors’ systems might be potential alternatives – Websites, industry magazines, trade exhibits, suppliers, competitors, etc.

• Request for Information – issue a request for information to the vendors indentified in the market survey – Request for information (RFI) – vendors supply written information about the capabilities of their solutions and the skills they offer

• Narrowing Down the Choices – project team should narrow down the ERP vendor candidates based on criteria important to them

ERP Life Cycle: Package Selection  • Site Survey – invitation for each of the prospective vendors to meet with the project team on-site so that the vendor’s sales team can better understand the buyer’s functional requirements and the peculiarities of their business • Requirements Analysis – detailed analysis to determine all the functionalities they need and desire • Request for Proposal – formal document developed by the potential buyer that details requirements in order to seek vendor offerings – Enables the requestor to evaluate and compare various proposal fairly

ERP Life Cycle: Package Selection  • Demo Days – vendor must “walk the walk” and “talk the talk” – Must be detailed, showing how key business process work Figure 5-2: ERP Weighted Score Sheet using the prospective customer’s own data Vendor  

 

 

ERP Selection Criteria

Manufacturing Functionality Planning Functionality Distribution Functionality Financials Functionality Ease of use Customizability Compatibility with Existing Applications Matched to Our Growth Pricing Structure Implementation Costs & Time Single Source - Total Solution Integration with Third Party Applications Commonly Used in Our Industry Quality, Accessibility & Cost of Support Partnership Potential Understands Our Business Understands Our Processes Business Stability R & D Resources Implementation & Training Resources

 

A

B

C

I m p or ta nc e (1 3) 3 2 2 3 3 1

R at in g (1 1 0) 8 6 6 4 6 5

W ei gh te d Ra tin g 24 12 12 12 18 5

R at in g (1 1 0) 10 7 5 7 9 9

W ei gh te d Ra tin g 30 14 10 21 27 9

R at in g (1 1 0) 7 8 4 6 3 6

W ei gh te d Ra tin g 21 16 8 18 9 6

2

6

12

7

14

8

16

3 2 3 2

4 6 2 6

12 12 6 12

6 5 8 7

18 10 24 14

5 4 6 8

15 8 18 16

1

4

4

6

6

8

8

2

8

16

5

10

3

6

3

3

9

5

15

7

21

1 3 3 2 1

3 7 5 5 5

3 21 15 10 5

8 7 9 8 8

8 21 27 16 8

10 2 4 9 7

10 6 12 18 7

3

4

12

8

24

10

30

Totals:

23 2

 

32 6

 

26 9

Table 5-2: 10 Rules to Make an ERP Demo as Smooth as Possible Use the same team to view all vendor demonstrations Agree the agenda with vendor well in advance and stick to it Confirm the “must haves” first and then the “nice to haves” and lastly the “bells and whistles” Compare fits and identify gaps Focus on the system’s operation avoiding the influence of freebies, a flashy appearance, and slick suits

Notice their culture Allow the vendors to share their new ideas Leave enough time for a post-demo Q&A Use a weighted score sheet for scoring and ranking vendors Cover implementation and support/maintenance separately

ERP Life Cycle: Package Selection  • Reference Visits – visit to a “like” customer site of the final short-lived vendors – Before making a decision the project team should visit one or more of the vendor’s customer sites to observe how the ERP system works in real life – Issues to discuss with “like” customers include:

Satisfaction with functionality and performance Satisfaction with look and feel of the system Implementation time and cost Impression of the vendor as an implementation partner Local vendor support Lessons learned from issues that were not anticipated but arose after the implementation began • Fit-Gap Analysis – used to compare the company’s requirements with what the ERP systems under consideration offer • • • • • •

– The more functionality “gaps” the less attractive a system is to the customer; however process gaps are opportunities to reengineer to best practices

ERP Life Cycle: Package Selection  • Implementation Methodology Discussion – discussion of the understanding of implementation needs – Project and implementation teams should agree on project scope, roles and responsibilities of customer and implementation team, implementation methodology and defined deliverables that will be used to guide the project and gauge its success

• Proposal – includes the recommended modules for the defined scope, annual fees for support and software assurance, a high level project plan, and the defined hardware, network, and software requirements necessary to support the new ERP systems • Decision and Negotiations – the team should discuss all critical information obtained from demos and reference visits, then rate each vendor, a

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition

r 6: ERP Life Cycle: Implementation and Operation and Maintena

ERP Life Cycle Stages  – Planning (Chapter 5) – Package Selection (Chapter 5) – Implementation (Chapter 6) – Operation and Maintenance (Chapter 6)

ERP Life Cycle: Implementation  • Installation – mechanics from changing from one software package to another while keeping problems at a minimum – ERP software cannot be installed until there is an instance to run it – Sandbox instance (or development instance) – where configuration testing and the development of customizations happens (even after go live) – Testing instance (where testing/QA happens) – Production instance – live system

ERP Life Cycle: Implementation  • Configuration – business and functional settings in the ERP system are changed to make the “out of the box” software support the customer’s business needs

• Does not make changes to the core software code but instead uses configuration tables that enable a company to tailor a particular aspect of the system to the way it chooses to do business – Allows the company to specify thousands of options for business process and organizational setup:

• Pricing methods

ERP Life Cycle: Implementation  – alterations to support a business process that may be unique or provide them with a competitive advantage

• Customization

– May be necessary due to compliance, regulatory, reporting, or legislative requirements that the software does not meet -requires programming – Alternative to vanilla implementation, or the use of only the default options in the ERP system and the best practices built into the software – Two main types of customization:

• Enhancement – used to add a field, change the look of the screen, or add and extra step to the process • Modification – change to the core code

ERP Life Cycle: Implementation  • Testing – confirms that the software behaves as expected and customer expectations are met – A dedicated development instance is used for testing – The production instance will run the firm’s operations – Conference room pilot (CRP) – sessions where conference rooms are designated as temporary locations to support development and testing, and employees can execute transactions with the proposed system configurations – Specific types of testing include:

• Unit testing – testing small increments of functionality or a single development object • Integration testing – testing end-to-end business processes • Customer acceptance testing – users test the

ERP Life Cycle: Implementation  • Change Management – body of knowledge that has evolved to address change within the context of an organization • Getting employees from Point A, prior to change, to Point B, where all employees are fully trained and new processes are in operation.

• Change agent – individual designated to lead change in the organization • Someone with clout, conviction, and charisma to make things happen and the keep employees engaged

Top Ten Principles of Change  Management 1. Address the “human side” systematically 2. Start at the top 3. Involve every layer 4. Make the formal case 5. Create ownership 6. Communicate the message 7. Assess the cultural landscape 8. Address culture explicitly 9. Prepare for the unexpected 10.Speak to the individual

ERP Life Cycle: Implementation  • Interfacing with Other Systems – because of time and cost constraints, gaps in functionality, and political issues, there are usually interfaces to other systems that must be developed and maintained • Training – teaching a new set of processes, not just a new software interface – The project team should be prepared to develop a training curriculum – Six Keys to Effective ERP Implementation Training for Employees:

1. Focus on business processes, not transactions 2. Relate new business processes to the existing environment 3. Leverage a multitude of tools for ERP training 4. Use train the trainer approach

ERP Life Cycle: Implementation • Consultants - Assist the project team with various activities including: – – – – – – –

Developing a business case Package selection Process documentation Change management Training Project management Functional knowledge

• When choosing a consultant, the project team should consider: – Do they have experience in the company’s particular industry? – How many successful implementations have the completed? – Do they provide ongoing service and support?

Benefits and Risks of Using Consultants  Table 6-4: Benefits and Risks of Using Consultants Benefits Unbiased and objective - Fixed contracts tend to reduce bias

Risks Biased - Association with particular software vendors and participation in technical communities may result in bias toward favorite packages Knowledge of vendors Lack of knowledge of the client’s Consultants can offer valuable business processes and culture knowledge regarding suitable Consultants must get up to speed software providers and their relative and learn on company time strengths and weaknesses Knowledge of best practices Advocacy of best practices - This Consultants can provide expertise may threaten company designing processes to address best differentiators and competitive practices and to include them in advantage implementation plans Implementation experience Expensive - Consultants with proven Familiarity with technical details track records command market eliminates many potential points of power failure Big picture focus Unaware of process details Innovative - Able to envision Knowledge may not be valuable opportunities to integrate transferred to company company processes with software employees - Inadvertently handing functionality over project ownership to consultants Senior management May hesitate to offer legitimate endorsement criticism of management actions and decisions

Source: strategy+business.com

Implementation Methodologies   • Phased Implementation – ERP system is rolled out by functionality (by module), division, or geographical area – Project team can focus on certain functional areas of the company while remaining areas continue with their normal operations

• Big Bang Implementation – replaces all business processes and/or entire legacy system all at once • Franchising Implementation – independent ERP systems are installed in each business unit, while common processes are linked across the organizations • On-Demand Implementation – uses the hosted Software as a Service (SaaS) model – No software to install on-premise

Comparison of Different ERP Implementation Approaches  Table 6-5: Comparison of Different ERP Implementation Approaches

Approach

Amt Inter Extern of Time nal al ROI   Chang Cost Cost e

Balanced - A Med Med cooperative approach between the company and vendor providing a shared effort for all implementation aspects. Risk: Internal resource capacity

Med

Turnkey - An Low Low High accelerated, delivered solution, reducing internal investment by minimizing customer contribution. Risks: User acceptance, change management

High

High

    Med

Med

Customer Driven - An High High Low Low Med approach that maximizes the customer’s involvement and minimizes involvement from consultants. Risks: Missed opportunities, maintaining momentum over time, internal resource capacity A la carte - Customer High High Low Low Med owns the process, with consultant involved as requested. Risks: Implementation success, lack of control & guidance, missed opportunities, maintaining momentum over time, internal resource capacity

   

 

     

ERP Life Cycle: Operation and Maintenance • The operation and maintenance stage begins with a period of stabilization – Companies will experience a dip in performance due to continued training needs and fine-tuning of “to be” processes – Project team should conduct a “postmortem session”

• Maintenance Activities – Preventative maintenance – regularly scheduled tasks that must be performed to keep the system functioning properly – Emergency maintenance – tasks that must be performed immediately – Software updates – ERP vendors constantly fix bugs, implement new best practices, and incorporate the feedback of customers in their software

Five Ways to Reduce ERP Maintenance and Support Costs

Table 6-6: Five Ways to Reduce ERP Maintenance and Support Costs Negotiate lower software license fees - Ongoing maintenance fees are commonly tied to net license costs, so negotiating less costly ERP licenses can reduce ongoing maintenance and support. Limit software customization during ERP system implementation - Although it may be tempting to customize the software to create an exact fit with business processes, manufacturers should understand that software customization will cause long-term maintenance costs to escalate. Explore third-party support and maintenance options - Software vendors make a good deal of profit on annual maintenance fees. These alternative support options can even provide an alternate price point to consider during negotiations with your vendor. Negotiate lower ongoing professional service rates - Upgrades and other changes to your software over time will typically require additional vendor services, so it is useful to negotiate these rates, which are a source of high margins for vendors. Quantify your total direct and indirect maintenance and support costs - Over time, these costs escalate and consume a significant portion of manufacturer's IT budget.

Source: SearchManufacturingERP

ERP Life Cycle: Operation and Maintenance • Upgrading – applying fixes and updates to the ERP system • Reasons for updating ERP systems: – Competitive advantage – new features and capabilities

• Edge over other competitors – Globalization – features and updates designed to increase the flow of information to customers and business partners

• Increased ability to operate globally – Integration – enhancing the flow of information between the ERP system and other systems within the company

• Increased operational efficiency and improved communications – Best practices – incorporating new best practices • Operate more efficiently – Cost reduction – lowering administrative overhead and improving the support offered by the ERP vendor

• Lower operating costs

Reasons Why Companies Do Not Upgrade Systems 

Figure 6-1: Reasons Why Companies Do Not Upgrade Systems Source: Aberdeen Group

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition Chapter 7: ERP: Sales, Marketing and CRM

ERP Sales Order Processing  • Objective – capture and fulfill the customer order, the document that begins the order fulfillment process • Ways to refer to Sales Order Processing 1. Contact-to-contract-to-cash 2. Quote-to-cash 3. Order-to-cash

Sales Related Activities  • Lead Generation • Contact • Qualification – applicability, affordability, and authority • Opportunity/Inquiry • Quote – estimate with an expiration date • Sales Order – quote that turns into a contract • Customer Order/Order Acknowledgement – confirmation of order receipt • Order Fulfillment – includes pick, pack, and ship activities • Billing – invoice is sent to the customer (A/R) • Cash Collection – payment is received from the customer

Transactions versus Events • Transactions have financial implications (things are debited and credited, so will affect the financial statements directly) • An event, or activity, is any step in the business process and may or may not have financial implications. • Thus, transactions are a subset of events. Event s

Transactions

Customer Relationship  Management

• Customer relationship management (CRM) bolt-on to ERP. Helps an organization with customer demands: – “Know me and know my business” – “Help me solve my business problems” – “Make it easy for me to do business with you” Table 7-1: What is CRM About? Acquiring customers Keeping customers Growing your customers Gaining customer insight Interacting with your customers across all touch points Building lasting relationships with your customers Delivering value to your customers Achieving a sustainable competitive advantage Growing your business

SAP 2007

Where CRM and ERP Meet

Figure 7-2: Where CRM and ERP Meet

Three Elements of a Successful CRM Strategy • People – Company employees, from the CEO to the front-office customer service representatives, sales and marketing, need to buy into and support CRM. • Processes - A company's business processes must be reengineered to reinforce its CRM initiative, often from the viewpoint of “How can this process best serve the customer?” • Technology - Firms must select the right technology to drive the processes, provide high quality data to employees, and be user friendly.

Principles for CRM Success  1. CRM is not a software purchase – it’s a strategy 2. CRM must fit the way you work now and in the future 3. Define measureable CRM business benefits 4. Consider total cost of ownership carefully 5. Think beyond features: pick the right partner

Benefits of CRM •

Knowing your customers better – personalization and segmentation –



Using analytics

Increase revenues by acquiring new customers and retaining current customers Increased customer satisfaction Decrease selling expenses by

• • – – – – –

making fewer yet more productive sales calls speeding data analysis lowering communication and transactions costs eliminating data redundancy reducing personnel headcount

CRM Advanced Analytics • • • • • • • • •

Event monitoring Segmentation Personalization Pricing Trending Advertising Forecasting Profiling Association

CRM: On­Premise vs. On­Demand • On-Premise – installing the software on-site on the company’s own servers – Traditional method of software implementation

• On-Demand – software is hosted by a third party service provider – Software asComparison a Service Table 7-5: of Hosted(SaaS) vs. On-Premise   Systems

Advantages of Hosted Solutions Faster deployment Lower up-front costs Reduced upgrade/maintenance requirement Simpler remote/field support

Advantages of On-Premise Solutions Easier to customize Easier to integrate with other applications and data Generally less-expensive long-term - typically treated (capitalized) as an investment rather than an ongoing expense Easier to use with more complete functionality in disconnected/remote environments

Knowledge Management (KM) and CRM  • Knowledge Management (KM) – directed process of figuring out what information a company has that could benefit others in the company, the devising ways of making it easily available • Companies integrate their CRM systems with KM because they realize that knowledge plays a key role in CRM success. • Creating a Knowledge Management System: – Recognize what employees know, that is valuable and not being shared – Create formal procedures to implement the system – Create a knowledgebase including best practices, expertise directories, and market intelligence – Make the knowledge available to people that need it – Give employees incentives for both sharing their knowledge as well as using others’ knowledge

Identifying Knowledge to Manage  • Skills and knowledge that a company has developed about how to make its goods and services • Individual employees or groups of employees whose knowledge is deemed critical to a company’s continued success • A company’s aggregation of documents about processes, customers, research results, and other information that might have value for a competitor

Reasons for Knowledge Management Systems • Sharing of best practices • Restructuring, downsizing, and outsourcing • Knowledge can command a premium price in the market • Globalization and competition • Successful innovation

Obstacles to Successful Knowledge Management • • • •

Starting too big Relying on technological shortcuts Not modeling the behavior Treating KM as a one-off project or quickwin • Ignoring the power of rewards • Ongoing maintenance

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition Chapter 8: ERP Financials

Financial Accounting  • Objective: to provide the information needed for sound economic decision making

• Must conform to GAAP (Generally Accepted Accounting Principles) Table 8-1: Benefits of ERP Financials

Benefits

Description

Improve corporate performance

The ability to quickly read, evaluate, and respond to changing business conditions strategically – such as defining financial targets, developing a suitable business plan, and monitoring costs and revenue during execution Faster time to close the Streamline consolidation, process scheduling, books workflow, and collaboration Improve corporate Provides broader support of accounting governance and standards, federal regulations, and improved transparency administration of internal controls Shorten days sales Automate dispute, credit, and collections outstanding management including electronic invoicing and payment capabilities that supplement traditional AR and AP functions Optimize global cash Report, analyze, and allocate cash in real time, management and establish in-house banks or payment centers. Improve financial and Report performance by business unit, managerial reporting organization, or cost center Improve process Integrate risk and treasury transactions with core integration between accounting and financial reporting processes finance and treasury Make finance costs more Innovate processes, collaborate with supply chain competitive partners, and establish global shared-service operations

Source: SAP

Financial Accounting  • General Ledger – an accumulation of balances from transactions and postings

• Monthly, quarterly, and yearly financial statements are generated • Parallel accounting – enables a company to keep several GLs simultaneously according to different accounting principles to ensure that local and international reporting requirements are met • Consolidation – enables the combining of financial statements for multiple entities within an organization

Financial Accounting  • Accounts Payable subledger – identifies the balances owed to every vendor calculated from purchases, returns and allowances, purchase discounts, payments, and other adjustments – Information regarding vendor invoicing and payment due dates – Support international methods of payment, track open items, provide account analyses, due date forecasts, and risk assessments – Three-way match – payment authorization whereby the ERP system will attempt to “match” every incoming invoice to a valid purchase order and an approved packing slip or receiver – AP aging report – used to group vouchers by due date in 30-day increments, providing focus on those payable items that may be past due

Financial Accounting  • Accounts Receivable subledger – records all account postings generated as a result of customer sales activity – Identifies the balances owed by customers – Credit management – supports alarm reports for various issues including over credit limit and nonpayments the automatic update of AR balances – AR aging report – groups receivables into 30 day increments, supporting cash flow projections and providing focus on those balances that are oldest

• Cash Management – functionality related to investments, cash flow, and the accounting requirements these cycles generate – Other functionalities: using cash to generate greater returns, cash flow analysis in any currency and in multiple time periods, and capital budgeting

Management Accounting  • Focus: taking revenue and expense items generated through financial accounting and “slicing and dicing” them to add even more meaning for management (does not have to conform to GAAP) – Used for applications including strategic management, risk management and performance management, designing, evaluating and optimizing business processes, budgeting and forecasting, and implementing and monitoring internal controls – Cost accounting – establishes budget and actual costs of operations, processes, departments or product and analyzes variances and profitability

Management Accounting  • Overhead Costing – helps with planning, allocating, and controlling indirect costs, or costs that cannot be directly assigned to a specific product (Direct costs – costs that have true origins and are more easily assigned to the proper product)

• Activity Based Costing – helps to more objectively assign costs by tracing overhead based on the cause and effect of relevant cost drivers, or activities that cause a cost to be incurred • Product Costing – help determine the cost of products manufactured or services provided (using direct materials, direct labor and overhead)

Management Accounting  • Profitability Analysis – considers certain segments of the organization and determines: – – – –

Profit generated by a certain product line Sales made to certain industries Margins supported by specific distribution channels Performance of specific regions, decentralized sales offices, or other semi-automated business units

• Cost/Profit Center Accounting – Cost centers are units in which the manager is responsible only for controlling costs because the unit it is not revenuegenerating. Examples are the accounting, IT or HR departments. – Profit center are units where the manager is responsible for both revenues and costs of the center. Examples of profit centers would be the manufacturing units that produce products for sale to consumers or other businesses.

Asset Management  • Planning – dedicating resources to the project Figure 8-3: Asset Management Life Cycle and establishing expectations about the execution of steps • Approval – sanctioning the project and requesting the budget assignment and approval • Budgeting – ensuring sufficient cash will be available to meet expenses as they arise Source: SAP Consultant, Rick Lombana , North Carolina • Implementation – State University Presentation executing and validating the steps of the PP&E project plan

Asset Management  • Settlement and Capitalization – since the overhaul may have affected the value of the machine, this new value will impact the PP&E account and related future depreciation • Maintenance and Use – maintenance costs associated with that asset are continually monitored • Retirement – provides information for an asset retirement such as its accumulated depreciation, salvage value, and whether the asset could be overhauled and put back in service • Replacing Investment – case to replace an asset is based on maintenance and operation costs

Investment Management  • Investment Management – provides the tools for pre-investment analysis during the planning stage of the asset management life cycle – Cost savings or revenue increases – Enterprise image improvement – Future payoff of the investment (Internal rate of return, payback period, and net present value)

Figure 8-4: Fixed Asset Investment Decisions

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition

pter 9: Human Capital Management, Self-Service and Outsourcin

Human Capital Management  • Human Capital Management (HCM)– methods and strategies embraced to optimize the value of human capital, or the set of skills that employees acquire in their jobs through training and experience which increase their value in the marketplace – Used by the Human Resources Department to facilitate a coherent and strategic approach to the way a firm manages and supports the people that both empower the organizations and burden the organization – Reasons to implement HCM:

• • • •

People Matter HR activities are data intensive HR data is extremely sensitive HR data is valuable to the rest of the organization

– Recruit-to-retire process – management of all aspects of an employee’s relationship, or life cycle collectively

Human Capital Management Modules • Personnel Management Module (PM) – Most legal and financial responsibilities of the whole organization – Captures employee master data – Personnel manager responsibilities:

• Staffing– screening and interviewing applicants, with an eye to placing individuals with the right skill sets into the right position within the company • Overseeing the creation of entry-level training programs as well as continuing education opportunities for existing employees • Determining company policies and procedures as they relate to personnel • Benefits Administration Module – Involves management of benefits for qualified employees – Administer and track employee participation in benefits programs including: health and life insurance plans, flexible spending plans, 401(k) plans, profit sharing plans, stock plans, retirement plans, and leave plans

Human Capital Management Modules • Time and Labor Management Module – Allows workers to submit timecard data online and supervisors to review and approve time online – Helps control costs and time worked, consolidate timecard information, prepare information relevant for the payroll process, and support forecasting of labor requirements and utilization based on forecast demands

• Compensation Module – Automates accounting and preparation of payroll checks for employees, including salaries and wages and benefit deductions – Manages direct deposits, which help minimize security risks associated with issuing paper checks

Human Capital Management Modules • Recruitment Management Module (RM) – Helps convert job candidates into favorable results by supporting the steps along the way that ensure an organization finds the right candidate including:

• Communicating career opportunities to broad, qualified applicant pools • Streamlining application methods for job seekers • Evaluating an applicant’s suitability as an employee • Matching applicants with job descriptions • Onboarding • Talent Management (TM) – Analyze personnel usage within an organization and help retain good employees – Aligning each employee’s contribution with organizational needs – Building a talent database, succession planning – Optimizing employee contribution

Human Capital Management Modules • Employee Performance Management (EPM) – Streamlines employee appraisals from goal planning and coaching to performance assessments and rewards Table 9-1: Ten Things You Cannot Do Without an EPM System Increase Rating Accuracy and Workplace Productivity by Differentiating Employee Performance Enforce Goal Alignment Actually Do Something with Employee Development Plans Enforce Consistent HR Performance Guidelines Provide Enterprise-Wide Access to Performance Information Get Better Data and Better Results Encourage Proactive Communication Beat the "Annual Because it's Manual" Mantra Improve Employee Engagement with "Social Networking" Collaboration Retain Key Contributors

Source: SumTotal Systems

Human Capital Management  Modules • Learning Management (LM)

– Administering employee learning, thereby managing talent and increasing intellectual capital in the organization – Includes: employee training profiles, courses, instructors, on-line scheduling, and course/teacher evaluations

• Environment, Health, and Safety (EHS) – Provides the necessary tools to administer compliance and manage risks associated with health and safety regulations that arise from local, state, and federal agencies – Help overcome the inherent problems of disparate systems, regions, and business units

Employee Self­Service • Employee Self-Service (ESS) – Addresses and minimizes non value-adding activities by allowing employees and managers to enter and update their own employee records and instigate documents and procedures related to them – Accessed via the corporate Intranet – Advantages of ESS:

• Improved service for and communication with employees • Streamline administrative processes and reduced costs for HR • Employee sense of ownership of their personal information and a renewed sense of trust in their employer • Error reduction • More timely updates

Manager Self­Service • Manager Self-Service (MSS) – Empowers managers to make departmental decisions that align with strategic business objectives in areas such as compensation, staffing, budgeting, and cost management

Employee and Manager Self­Service • Travel management – automates the planned trip-to-payment process – Reduces travel costs, centralizes travel planning, and incorporates corporate travel policies

– Includes submitting travel requests, online booking, and submitting and settling travel expenses

Outsourcing Human Capital Management Activities  • Companies choose to outsource HR related functions such as compensation because of the intricacies of keeping up with various country, state, city, and local taxes • Service organizations take on the responsibility for activities such as time and attendance, payroll, payroll tax deposits, GL interface and 401(k) administration • Outsourcing non-core functions allows companies to focus exclusively on their core business, while recognizing significant savings and increased expertise

Outsourcing Human Capital Management Activities 

Table 9-2: Seven Signs That Your Company May Be Ready for HR Outsourcing Spiraling Costs: Rising payroll and benefit costs are primary drivers to outsource HR. Missed Deadlines: If many employees are complaining about getting critical documents late, like W-2s and paychecks, this is a sign that the current system is not working correctly. A service provider may identify the problems and fix them without hiring additional HR employees. System Overloads: If the HR system starts to overwhelm the current IT system, it might be a good idea to rely on an HR outsourcer. Usually, they use their own system, enabling in-house systems to operate more efficiently. Increasing Mistakes: Your organization won't have a perfect HR system, but increasing number of problems could suggest that it’s time to use an outsourcer. Assigning mistake-prone work to an HRO can lower the pressure on in-house staffers. Poor Quality Work: Consistent problems with HR occurring for a long period of time may be a sign that HR is overworked. Instead of hiring new staff, it may be simpler to outsource HR to a third party. Disgruntled HR Workers: An HRO can step in during busy seasons to take on the extra time-consuming tasks that drive up HR workloads and staff discontentment. Competitors' Moves: Ask around and find out what benefits your rivals are gaining from outsourcing HR work. You may discover that these same issues apply to your organization.

Source: HRWorld.com

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition Chapter 10: Manufacturing Systems and Supply Chain

Manufacturing Systems Evolution   • Economic Order Quantity (EOQ) – inventory management technique in which each raw material item is analyzed for its ordering and carrying costs to determine optimum ordering quantities • Materials Requirements Planning (MRP) – computerized production planning and inventory control system used to control ordering and manufacturing processes. Needs following information. – Bill of material (BOM) – full list of raw materials necessary to produce a single item – Master production schedule (MPS) – production schedule for finished goods based on current orders plus forecasted requirements – Inventory status file – contains on-hand inventory balances of every part held in inventory

• Open orders – orders not yet filled • Lead time – time that elapses between placing an order for raw materials and receiving them ©2010 by Marianne Bradford. All rights reserved

128

Material Requirements Planning  • Materials Requirements Planning (MRP) – With the MPS, the BOM, and the Inventory Status Report, MRP systems:

• • • •

Identify raw materials needed Calculate lead times and safety stock levels Determine the most cost-effective order quantities Produce a detailed schedule of accurate purchase orders

– Benefits • Reduce inventory levels, production, and delivery lead times by improving coordination and avoiding delays • Make finished goods commitments to customers more realistic • Increase efficiencies in the raw material procurement process and ensuring production process ©2010 by Marianne Bradford. All rights reserved

12 9

            Production Process 

©2010 by Marianne Bradford. All rights reserved

130

Manufacturing Systems Evolution   • Capacity Planning – uses the planned manufacturing schedule to analyze the requirements that will be placed upon manufacturing work centers such as personnel, machines, and warehouse capacity

• Manufacturing Resource Planning (MRPII) – effectively plans all resources of a manufacturing operation including the operational planning in unites, financial planning in dollars, and a simulation capability to ask “what it” questions

©2010 by Marianne Bradford. All rights reserved

131

ERP Manufacturing Modules  • Production Planning – enables the creation of realistic production plans across multiple manufacturing locations and subcontractors to fulfill demand in a timely manner and according to standards expected by the customer – Production with production orders, repetitive manufacturing, Kanban. Discrete or process manufacturing

©2010 by Marianne Bradford. All rights reserved

132

ERP Manufacturing Modules  • Materials Management– supports inventoryrelated activities such as the tracking and control or raw materials, stocked items, WIP, and finished goods in a single, integrated inventory control environment – Specifies the activities needed to maintain adequate inventory levels – Purchasing and inventory valuation

• Quality Management – assists in configuring specific parameters that define what goods to inspect, when to inspect, and tolerance limits (the extreme values that are considered acceptable – Alerts those responsible when quality deviations occur and specifies what course of action to take – Benefits of quality ©2010 bymanagement Marianne Bradford. All include: 133



rights reserved

ERP Manufacturing Modules  • Plant Maintenance –used by large organizations in capital-intensive industries. – Directs the activities required to maximize the availability and operability of equipment; reduces costs for inspections, repairs, and maintenance – Provide a real-time, detailed view of the costs, reliability, and impact of each piece of equipment on the manufacturing floor – Extend the useful life of fixed assets in the plant – Minimize downtime and maximize uptime of fixed assets in the plant – Support Six Sigma and other quality methods – Increase collaboration between production and maintenance staffs – Monitor equipment performance ©2010 by Marianne Bradford. All rights reserved

134

ERP Manufacturing Modules  • Service Management – manages the lifecycle changes to existing services or installed products after the initial customer order is filled – Goal – optimize service-intensive supply chains – Benefits of employing service management include:

• Lower service costs by integrating the services and products supply chains • Lower service parts inventory levels • Optimize customer service and parts/service quality • Increase service revenue • Improve customer satisfaction • Minimize technician visits • Warehouse Management – automates the flow of ©2010 by Marianne Bradford. All of the warehouse materials into, through, and out 135 rights reserved

ERP Manufacturing Modules  • Lean Manufacturing – philosophy of production that emphasizes the maximizing an enterprise’s resources and attempts to reduce inventory and eliminate waste, the costs that add no value to a product – Just-in-time – materials are supplied just when needed – Reduces or eliminates overproduction, transport, motion, waiting, inventory, over-processing, and defects – Lean planning and operations (LPO) – helps lean manufacturers plan production in smaller batches across volume and mix, handle product transitions efficiently and tightly integrate production activities on the plant floor

• Supplier Relationship Management – enables ©2010 by Marianne Bradford. All 136 rights reserved the relationship between businesses to manage

Supply Chain Management  Enablers • Supply Chain Management (SCM) systems

optimize production to meet, but not exceed, demand for products

• SCM technologies that eliminate much of the guesswork between suppliers, manufacturers, retailers, and consumers by enabling more visibility up and down the supply chain include: – Radio Frequency Identification (RFID) – Electronic Data Interchange (EDI) – Vendor Managed Inventory (VMI) ©2010 by Marianne Bradford. All rights reserved

137

Supply Chain Management Enablers • Radio Frequency Identification (RFID) – use of tiny computer chips and antennas embedded in products and packaging that enable better tracking of objects using wireless networks – Tags – chips and antennas which transmit data – RFID tags do not require line of sight technology, but need only be within range of the reader to be read – RFID can track goods from supplier’s factory floor, through shipment and customer delivery, to the retailer’s store shelves – Two main types of tags:

• Active tags – have an internal battery that allows continuous transmission of data and permits reading from a greater distance • Passive tags – do not have a battery and only transmit data when a transceiver activates them by coming within a certain range ©2010 by Marianne Bradford. All rights reserved

138

Supply Chain Management Enablers • Electronic Data Interchange (EDI) – use of computerized communication to exchange business event data between companies, or trading partners – Allows companies to create electronic documents, transmit them over private networks or the Internet to their customers’ and suppliers’ computers, and receive electronic acknowledgements in return – Generally used for high volume transactions running in batch mode or in situations where critical, just-in-time information is required – Used as a standardized format, or common language, that is read by trading partners’ information systems

• Recognized standard for EDI: ANSIX12 • Developed by the American National Standards Institute (ANSI) – an organization that has served as administrator and coordinator of the United States private sector voluntary standardization system for more than 90 years ©2010 by Marianne Bradford. All rights reserved

139

Supply Chain Management Enablers Table 10-1: Benefits of Electronic Data Interchange

Customer

Supplier

Purchase orders take less time to transmit, lowering required inventory levels

Supplier is relieved of the process of rekeying and verifying orders

Since there is quicker order acknowledgement, Elimination of problems and delays caused by data customers can find an alternative supplier if order entry errors. Errors in order entry mean current supplier cannot provide the desired missed ship dates, shipment of incorrect items or product when needed quantity, and lower customer satisfaction Reduced time spent matching supplier invoices to purchase orders and entering accounts payable information

Time is reduced from invoicing/payment cycle improving the cash flow of the supplier

Reduced back-orders or out of stock situations Inventory reductions

Source: 1EDISource Inc.

©2010 by Marianne Bradford. All rights reserved

140

Supply Chain Management Enablers • Vendor Managed Inventory (VMI) – outsourcing the replenishment of an organizations’ inventory to suppliers – Creates purchase orders based on the demand information sent by the retailer – Backward replenishment model – the supplier does the demand creation and demand fulfillment Table 10-2: Benefits of Vendor Managed Inventory

Retailer Reduced stock-outs because supplier keeps track of inventory movement and takes over responsibility for product availability Increased customer satisfaction and sales due to fewer stock-outs

Supplier Better forecasting because of real-time demand information from customer

Reduced purchase order errors and purchase returns by customer because of fewer mistakes Reduced forecasting and purchasing Improvements in service level agreements activities since supplier knows the need for item and thus orders right product at right time, leading to supply chain cooperation Reduced inventory due to lower safety Reduced inventory because supplier knows stock since the supplier can control how much and when customer is going to lead time better than customer buy

Source: Tata Consulting Service

©2010 by Marianne Bradford. All rights reserved

141

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition Chapter 11: Auditing ERP

What is Internal Control? • Internal Control – includes policies and procedures effected by an organization’s management to monitor assets, prevent fraud, minimize errors, verify the correctness and reliability of accounting data, and promote operational efficiency

• Management uses these policies to provide reasonable assurance that only accurate, complete, and valid information is entered into company systems, and the information in the system is properly processed to produce reliable output • Internal controls meets objectives in the following areas: • Reliability of financial reporting • Effectiveness and efficiency of operations • Compliance with applicable laws and regulations

• The report desired by management is an unqualified audit report that displays a “clean bill of health” from their auditors ©2010 by Marianne Bradford. All rights reserved

143

Internal Control Regulation  • Sarbanes-Oxley Act of 2002 (SOX) – requires management of publically traded companies to: – Establish, document, and maintain internal controls and procedures over financial reporting – Audit their effectiveness of internal controls over financial reporting – Assess the deficiencies to determine the effectiveness of its internal controls over financial reporting

• Public Company Accounting Oversight Board (PCAOB) – private sector, non-profit organization to oversee the auditors of public accounting firms – Auditing Standard No. 5 – states that the objective of an audit of internal controls over financial reporting is “to express an opinion on the effectiveness of the company’s internal control over financial reporting” ©2010 by Marianne Bradford. All rights reserved

144

The Integrated Audit  • Integrated Audit – a holistic approach to auditing that entails more than just testing and verifying the accuracy of the balances in the financial statements – Substantive test – an audit procedure designed to test the validity, accuracy, and completeness of account balances in terms of dollar amounts – Tests of internal controls – are by Marianne Bradford. All looking for ©2010 a yes/no answer as145to rights reserved

IT Application Controls  IT Application Controls – are performed automatically by systems ensuring accurate data entry, processing, and system output. – Programmed controls – automated controls configured within the application such as the three-way match. – IT dependent manual controls procedures that are reliant on output from information systems – Edit Checks – occur at the point of data entry to verify that no errors are present and that the data adheres to specific standards – Transaction numbers – unique for every transaction and provide an audit trail

Table 11 - 1: Examples of Application Controls over Typical Business Processes Purchase to Pay Three-way match of purchase Duplicate vendor invoices order, receiving report and vendor invoice Financial Closing & Reporting Integration with other ERP modules Automated roll-up of financial statements Fixed Assets Depreciation calculation

Gain/loss on fixed asset sale calculations Payroll

Integrated timekeeping with payroll

Payroll deduction calculations Inventory

Monitoring of inventory levels Tolerance limits

Matching of receipt to purchase orders Integration of inventory with shipping Order to Cash

                   

    Automated credit checking Automated pricing of orders   Integration with Electronic Data On-line approval of AR adjustments   Interchange Integration of orders with shipping Invoice and discount calculations   All Processes   On-line edit checks of data entry Sequential numbering of documents   On-line approvals of entries

©2010 by Marianne Bradford. All rights reserved

 

146

IT General Controls  Figure 11 – 2: Relationship between IT General Controls and Application Controls

Typical business processes

Source: Deloitte and Touche

More applicatio n controls

IT General Controls –represent the foundation of the IT control structure. They help ensure the reliability of data generated by IT systems and support the assertion that systems operate as intended and that output is reliable. ITGC support the application controls. They are the first line of defense. However, if they don’t ©2010 by Marianne Bradford. All 147 reserved application controls work. work, then you can’trights assume

Program Change Controls  • Program Change Controls – controls that govern the changes made to information systems and databases. These changes are configuration changes, customizations, patches, minor upgrades etc. We use various instances of ERP to effect these changes • Common deficiencies when making changes to programs: – Program changes are not authorized by ERP steering committee, team, IT managers (depending on what is going on) prior to development – Program changes are not tested prior to moving to production – Program changes are not authorized by management prior to moving to production – The same person or person that developed the change is allowed to move the change to production (bad!) – Insufficient documentation exists to show proper approvals ©2010 by Marianne Bradford. All 148 and procedures in the change control process rights reserved

Program Change Controls  • Program changes initiated only with a valid IT or business justification • An IT manager or management in the business area requesting the program change approves changes prior to development • Application programmers should make changes in the development environment • Once work is completed, programmers (e.g., SAP Basis) move changed programs in the testing area for users or IT staff to test • IT and/or management of business area perform an impact analysis prior to moving the change to production • The change moved to production is scheduled, and users impacted by the change are notified • After testing and sign-off of quality assurance are complete, an IT staff member not involved in the change ©2010 by Marianne Bradford. All 149 moves the change toreserved production rights

Information Security Controls  • Information security controls – help prevent unauthorized access to information systems resources • Common deficiencies in information security controls: – Access to IS resources not properly managed, and rights are granted without adequate justification – Access privileges to IS resources are not monitored to assure that they remain current, complete, and accurate – Improper Segregation ofAllDuties(SoD) is ©2010 by Marianne Bradford. 150 rights reserved

Controls for Information Security  • Authentication – verifying the identity of the users (you are who you say you are)

– Two-factor authentication – combining two forms of ID – Multifactor authentication – combining more than two forms of ID – RSA SecureID – an authentication token that uses a built-in clock and factory encoded random key – Biometric software – links a user’s unique physical attributes to the data they are allowed to access • Proper authorization of the nature and extent of ©2010 by Marianne Bradford. All user access privileges 151 rights reserved

Computer Operations Controls  • Computer Operations Controls – focus on the physical access to IT resources that run a company; designed to protect against both environmental and man-made hazards – Common deficiencies related to computer operations & data centers include: • Poor job scheduling procedures • Insufficient system or back-up and recovery • Unmanaged third party service level agreements ©2010 by Marianne Bradford. All 152 rights reserved backup) (e.g., maintenance,

Computer Operations Controls • Some example controls in a data center are: – Batch computer jobs are monitored by management – Automated job scheduling tools – Automated data retention tools – ERP database is backed up at least once a week or an off-site location – Obtain a SAS 70 for outsourced IS functions – Uninterrupted power source/generator – Minimize entry and exit points ©2010 by Marianne Bradford. All 153 rights reserved – Monitor entry/exit points with

Evaluating Deficiencies in ITGC • • • • • • • •

Nature and significance Pervasiveness of deficiency Complexity of systems environment Proximity of control to applications and data Susceptibility to fraud Cause and frequency of known exceptions History of misstatements Competency of business and IT management ©2010 by Marianne Bradford. All rights reserved

154

Controls over Outsourcing Business  and IT Functions • Types:

– Application outsourcing – contracting for a data center to host a company’s ERP system – Business process outsourcing – service provider performs a function for the company (e.g., outsourcing a company’s HR processes, such as benefits and compensation) – IT outsourcing – outsource maintenance of hardware

• Statement on Auditing Standards No. 70 (SAS 70) – the authoritative guidance for service organizations and mandates that they disclose their internal control activities and processes to their customers in a uniform reporting format – Must identify the applicable data centers, operating environments, and applications ©2010 by Marianne Bradford. All 155 conclusion – Service Auditor’s Report – issued at the rights reserved

Statement on Auditing Standards  No. 70 • Two types of SAS 70 Service Auditor’s Reports:

– Type 1 Service Auditor’s Report – includes the service auditor’s opinion on the description of controls over the outsourced function evident at the service organization and the suitability of the designee of these controls to achieve the specified control objectives • Does not present an opinion on the operating effectiveness of these controls • Can not serve as first hand testing in conjunction with the financial statement audit ©2010 by Marianne Bradford. All rights reserved

156

ISACA Certifications for IT Audit,  Security, and Governance • Certified Information Systems Auditor (CISA) – qualifies an individual as globally proficient in the areas of IS audit, control, and security • Certified Information Security Manager (CISM) – targets the information security management audience and bridges the knowledge gap between business strategy and IT security ©2010 by Marianne Bradford. All rights reserved

157

ISACA Certifications for IT Audit,  Security, and Governance • Certified in the Governance of Enterprise IT (CGEIT) – certification for professionals charged with satisfying the IT governance needs of an enterprise

– What is IT governance? –leadership, organizational structures, and processes that ensure that an organization’s technology sustains and extends the organization’s strategies and objectives; aligns IT with organizational objectives – IT Governance Institute (ITGI) – ISACA formed this to focus on original research, publications, resources, and symposia on IT by Marianne Bradford. All governance©2010 and related topics 158 rights reserved

ISC2 Certification for IT Audit, Security,  and Governance

• What is ISC2 ?- International Information Systems Security Certification Consortium, Inc., (ISC)²®, is the global leader in educating and certifying information security professionals throughout their careers. They administer the CISSP. • Certified Information System Security Professional (CISSP) – certification encompassing information security and assurance tenets of confidentiality, integrity, and availability – More technical than the other certifications ©2010 by Marianne Bradford. All rights reserved

159

COBIT • Control Objectives for Information and related Technology (COBIT) – governance framework and supporting toolset that provides best practices management guidelines for implementing IT governance as required by audits and SOX Section 404 • COBIT is developed by ISACA and ITGI

Figure 11 – 4: COBIT Cube

©2010 by Marianne Bradford. All rights reserved

Source: ISACA

160

COBIT Domains and IT processes •







Plan and Organize – provides management with tactics and strategy concerning how IT can best contribute to the achievement of the business objectives – Examples of Processes: Define a Strategic IT Plan and direction; Define the Information Architecture Acquire and Implement – includes identifying IT requirements, acquiring IT, and implementing IT within the company’s current business processes – Examples of Processes: Acquire and Maintain Application Software; Acquire and Maintain Technology Infrastructure Deliver and Support – focuses on the delivery aspects of IT, as well as the support processes that enable the effective and efficient executing of systems – Examples of Processes: Manage Third-party Services; Manage the Configuration; Ensure Systems Security Monitor and Evaluate – addresses performance management, monitoring of internal controls, regulatory compliance, and governance – Examples of Processes: Monitor and Evaluate Internal Control; Ensure Regulatory Compliance; Provide IT Governance ©2010 by Marianne Bradford. All rights reserved

161

Governance, Risk, and Compliance  • Governance, Risk, and Compliance (GRC) – enables organizations to maximize strategic and operational performance by cost-effectively managing regulatory and policy compliance, while proactively mitigating all types of business risk – Corporate governance – the structure and relationships that dictate how a corporation is directed, administered, and controlled – Risk management – assesses the areas of exposure and potential impacts, – Compliance is the tactical action to mitigate risk; conforming to stated requirements

• GRC provides access control, risk management and regulatory compliance (for audits etc) – User provisioning, de-provisioning, segregation of duties, continuous monitoring of SODs, analysis and management of risks etc ©2010 by Marianne Bradford. All rights reserved

162

MODERN ERP

SELECT, IMPLEMENT & USE TODAY’S ADVANCED BUSINESS SYSTEMS Second Edition

hapter 12: Business Intelligence and Performance Management

Business Intelligence  • Business Intelligence (BI) – a discipline that includes a collection of practices and technologies used to explore raw data extracted from various business systems and data sources in order to reveal meaningful knowledge

– Used to mine customer data and purchasing histories for associations, personalization, segmentation, and forecasting demand – Exposes areas that are most profitable and improve business processes by finding bottlenecks and inefficiencies – Many ERP systems now include BI as a bolt-on

Figure 12-1: Major Business Intelligence Vendor Consolidation

©2010 by Marianne Bradford. All rights reserved

164

Degree of Intelligence in BI Tools Figure 12-2: Reactive vs. Proactive Decision Making Source: SAS Institute, Inc.

©2010 by Marianne Bradford. All rights reserved

165

Types of Business Intelligence  • Ad hoc Querying and Reporting – using a query method users can obtain answers to questions and develop their own reports and graphs • Predefined reports – standard reports and graphs that come defined in the BI tool • Scorecarding – metrics that communicate when business performance is satisfactory or needs attention • Alerts – event notifications • Extract, Transform, Load (ETL) – moves data from one repository to another and uses data cleansing techniques • Data mining – “what you didn’t know you didn’t know” • Analytics – advanced statistical analysis • Predictive analytics – uses data about the past to predict future behavior

• Text mining – uses the computer to explore unstructured text to look for previously unknown information ©2010 by Marianne Bradford. All rights reserved

166

Data Stores for Business Intelligence  • Data Warehouse – a large relational database that combines pertinent data in an aggregate, summarized form suitable for enterprise wide data analysis, reporting, and management decision making Table 12 – 1: Key Characteristics of a Data Warehouse Subject oriented: Organized by subject rather than process; domains are suppliers, customers, projects, sales, etc. Stable, Non-volatile: Once stored, not changed except for compelling reason; batch updates done periodically; different than ERP that processes transactions/events every second Time variant: Reporting over a period of time Integrated: Integrates data including ERP, legacy systems, point of sale (POS) data, economic data-whatever is needed to answer managers' questions

Source: CIO Magazine

Data Mart – a subset of a data warehouse

that is usually designed for a specific set of users ©2010 by Marianne Bradford. All rights reserved

167

Data Governance  • Data Governance –the creation and management of the organizational structures, policies, and processes needed to define, control, and ensure the quality of enterprise data – A sound data governance program includes a data governance committee, which is typically a crossfunctional committee empowered by senior management, a defined set of procedures for data quality, and a plan to execute those procedures.

• Data Cleansing – a process that makes sure data is consistent and complications arising from errors or other inconsistencies in the creation of the original data records are detected and resolved – Techniques applied to correct data within the system:

• • • •

Format the data Enforce data integrity Derive missing data values Eliminate duplicate data

©2010 by Marianne Bradford. All rights reserved

168

Best Practices for Business  Intelligence   • Clearly define business objectives and have a • •

• • • •

business case rationale prior to implementation Standardize and cleanse dirty data Integrate data using the best data structuring alternatives available and avoid subsequent roadblocks resulting from poor data structure, fidelity, and reliability Train users to manipulate the data to get the most meaningful and valuable answers Quickly deliver reports that provide the most value and then tweak them Deploy with the idea that there are answers out there that need to be found and know roughly where the information might be Outline the specific benefits expected to be ©2010 by Marianne Bradford. All 169 achieved, thenrights doreserved a reality check at set intervals

Business Performance Management • Business Performance Management (BPM) – creating, sustaining, and improving processes for successful strategy execution • Consists of various frameworks for organizing, automating, and analyzing business methodologies, metrics, processes, and systems that drive business performance • Bridges the gap between long-tem strategies and day-today operations by aligning business measures with critical success factors identified by management – Business metrics – provide meaningful measures of the company’s performance • KPIs – business metrics tied to users’ roles Table 12-3: Comparison of BI and BPM

Business Intelligence

Business Performance Management

Appeals to operations users and line-ofAppeals to financial applications users. business managers. Embeds metrics analysis within internal Focuses on defined metrics to help users processes to help users make timely improve processes, and manage and increase business decisions, and to enable performance. strategic or tactical planning. Provides data needed to answer Uses scorecarding and dashboarding to essential business issues and to plan measure organizational metrics and to help and act based on the analysis of organizations manage ©2010 by Marianne Bradford. Allperformance. business problems. 170

rights reserved Source: Technology Evaluation Centers

The Balanced Scorecard • The Balanced Scorecard – A structure around the way organizations measure how well they are functioning and how well they might do in the future; entails mapping and translating complex business information into something that understandable to everyone in the organization – Bolt-on to ERP – Is a management system, not merely a measurement system – Focuses attention on the company’s most important goals first, and then makes sure that every organizational and individual action supports these goals.

• Two types of measures/indicators: – Lagging indicators – provide knowledge of past activity and thus, in isolation, provide an incomplete picture of organizational performance – Leading indicators – “balances” financial metrics and sets expectations for future activities ©2010 by Marianne Bradford. All rights reserved

171

Perspectives of  The Balanced  Scorecard • Financial Perspective – “How do we look to shareholders?” • Learning and Growth Perspective – “Can we continue to improve and create value?” • Internal Business Process Perspective – “What can we do better than anyone else?” • Customer Perspective – “How do our customers view us?” Table 12-4: Example Balanced Scorecard KPIs Financial Cash Flow ROI Profit to Earnings Ratio Return on Capital Employed Return on Equity Internal Business Processes Number of Activities Order to Cash Cycle Time Accident Ratios Defect Ratios Inventory Turns

Customer On-time Delivery Rate Return Rate Customer Satisfaction Customer Retention Customer Growth

Learning and Growth

New Patents Pending Absence Rate Internal Promotion Rate Employee Turnover Average Training Hours

©2010 by Marianne Bradford. All rights reserved

172

The Balanced Scorecard • Benefits: – Clarifies strategy throughout the organization – Provides a central source of key information – Creates attention directed to vital issues – Provides advance warning of problems – Aligns organizations around strategy – Yields higher control and flexibility – Prioritizes initiatives – Organizes information – Reduces information overload

 Limitations: Failure of

management to follow through with converting measures to operational performance improvements Will not add value if the company’s initial strategy is not a profitable one Requires companies to alter their mission, ©2010 by Marianne Bradford. vision, and 173 All rights reserved performance

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF