1. ERP systems evolved from companies initially developing separate financial and inventory applications, then integrating manufacturing applications, and finally software companies integrated all these functions into a single package called ERP with a single database.
2. As ERP companies installed more systems, they learned industry best practices and offered personalization options through switches in the package without modifying software.
3. The history shows the evolution from separate applications to a fully integrated ERP system with a single database and ability to customize using switches rather than reprogramming.
The document is a student paper submission form for a paper titled "PIMS vs. ERP systems: A study based on applications". It includes information about the authors such as their names, education levels, email addresses, and educational affiliations. It also provides contact information for the primary author. The paper analyzes the advantages of Product Information Management Software (PIMS) over larger Enterprise Resource Planning (ERP) systems for small business applications using the example of the Husky Tech Store on the campus of St. Cloud State University.
The document discusses Enterprise Resource Planning (ERP) systems. It defines ERP as software that integrates different business functions like finance, logistics, manufacturing etc. into a single system. The evolution of ERP is described from initial systems that integrated different departmental functions to current Internet-enabled ERP systems that facilitate e-business through integration with CRM and SCM modules. Extended ERP systems use a web interface to connect external modules for customer relationship management and supply chain management.
What is an Enterprise Management System and how can it help your manufacturing business stay sharp in today's ruthlessly competitive environment? Learn all about it in our latest blog post.
#supplychain #mrpeasy #managementsystem #manufacturing #manufacturingsoftware #mrpsoftware #mrpsystem #erpsystem #enterprisemanagementsystem
The document discusses enterprise resource planning (ERP) systems. It provides an overview of what an ERP system is, the scope and costs of implementation. Key points covered include the anatomy of an ERP system with its central database, configuring an ERP system, and the allure of an integrated system. Challenges that can arise when the system and company strategy do not align are also examined. The impact on an organization is streamlined processes and real-time access to information. Successful implementation requires top management involvement and customizing the system to the business.
ERP systems provide opportunities for SMEs to integrate business processes and gain efficiencies. However, implementing ERP presents challenges for both SMEs and vendors. For SMEs, costs can be high while benefits are unclear. Lack of expertise and resources make selection and customization difficult. Vendors face low prices from SMEs and high customization needs, with uncertainty around returns. Successful ERP implementations require addressing these financial and expertise barriers through education, customized solutions, and reasonable costs for both SMEs and vendors.
1) An ERP system provides integrated management of core business processes through a single software system. It aims to integrate all departments and functions across a company onto a single computer system that can serve all those different departments' particular needs.
2) Companies implement ERP systems to support business goals like integrated and online processes, elimination of fragmented legacy systems, improved integration and lower costs.
3) A successful ERP implementation requires the right mix of people, processes, and technology. Key steps include project planning, design, building the system, training users, and go-live support. Adaptation of business processes to the ERP system is also important.
Enterprise resource planning (ERP) systems originated from extensions of manufacturing resource planning and computer integrated manufacturing systems. ERP software provides integrated functionality for at least two business systems, such as payroll and accounting. ERP implementations involve consulting, customization, and support services from ERP vendors or third parties. Successful ERP implementations require significant planning, including identifying data to migrate and generating data templates. ERP systems provide advantages like centralized data and process integration across business functions, but also disadvantages such as high costs, potential rigidity, and security risks from centralized data.
ERP of upcoming industry revolution with benefits of Amazon cloud services it improves the Industrial Revolution and increases the analytics of Data Warehouse and make the CRM and planning
The document is a student paper submission form for a paper titled "PIMS vs. ERP systems: A study based on applications". It includes information about the authors such as their names, education levels, email addresses, and educational affiliations. It also provides contact information for the primary author. The paper analyzes the advantages of Product Information Management Software (PIMS) over larger Enterprise Resource Planning (ERP) systems for small business applications using the example of the Husky Tech Store on the campus of St. Cloud State University.
The document discusses Enterprise Resource Planning (ERP) systems. It defines ERP as software that integrates different business functions like finance, logistics, manufacturing etc. into a single system. The evolution of ERP is described from initial systems that integrated different departmental functions to current Internet-enabled ERP systems that facilitate e-business through integration with CRM and SCM modules. Extended ERP systems use a web interface to connect external modules for customer relationship management and supply chain management.
What is an Enterprise Management System and how can it help your manufacturing business stay sharp in today's ruthlessly competitive environment? Learn all about it in our latest blog post.
#supplychain #mrpeasy #managementsystem #manufacturing #manufacturingsoftware #mrpsoftware #mrpsystem #erpsystem #enterprisemanagementsystem
The document discusses enterprise resource planning (ERP) systems. It provides an overview of what an ERP system is, the scope and costs of implementation. Key points covered include the anatomy of an ERP system with its central database, configuring an ERP system, and the allure of an integrated system. Challenges that can arise when the system and company strategy do not align are also examined. The impact on an organization is streamlined processes and real-time access to information. Successful implementation requires top management involvement and customizing the system to the business.
ERP systems provide opportunities for SMEs to integrate business processes and gain efficiencies. However, implementing ERP presents challenges for both SMEs and vendors. For SMEs, costs can be high while benefits are unclear. Lack of expertise and resources make selection and customization difficult. Vendors face low prices from SMEs and high customization needs, with uncertainty around returns. Successful ERP implementations require addressing these financial and expertise barriers through education, customized solutions, and reasonable costs for both SMEs and vendors.
1) An ERP system provides integrated management of core business processes through a single software system. It aims to integrate all departments and functions across a company onto a single computer system that can serve all those different departments' particular needs.
2) Companies implement ERP systems to support business goals like integrated and online processes, elimination of fragmented legacy systems, improved integration and lower costs.
3) A successful ERP implementation requires the right mix of people, processes, and technology. Key steps include project planning, design, building the system, training users, and go-live support. Adaptation of business processes to the ERP system is also important.
Enterprise resource planning (ERP) systems originated from extensions of manufacturing resource planning and computer integrated manufacturing systems. ERP software provides integrated functionality for at least two business systems, such as payroll and accounting. ERP implementations involve consulting, customization, and support services from ERP vendors or third parties. Successful ERP implementations require significant planning, including identifying data to migrate and generating data templates. ERP systems provide advantages like centralized data and process integration across business functions, but also disadvantages such as high costs, potential rigidity, and security risks from centralized data.
ERP of upcoming industry revolution with benefits of Amazon cloud services it improves the Industrial Revolution and increases the analytics of Data Warehouse and make the CRM and planning
7 signs that show you need to start using an mrp systemMRPeasy
You can see how your organization has significantly grown within the last periods. More staff, more tools and maybe you have incorporated more machinery or new technology.
#mrpsystem #mrpeasy #erpsystem #mrp #erp #manufacturing #manufacturingsoftware #sevensigns #reasonstostart #whymrp #whyerp #saas
An Enterprise Resource Planning (ERP) system integrates core business processes like finance, supply chain, production and human resources into a single system. ERP has evolved from earlier systems like MRP and MRPII. Key reasons for companies to implement ERP include integrating financial and customer order information, standardizing processes, and reducing inventory levels. ERP provides benefits such as improved cost control, faster response to customers, and standardized HR processes. Successful ERP implementation requires careful planning including deciding whether to customize the system or follow its standard processes and whether to use an in-house or outsourced team.
The document traces the evolution of ERP systems from centralized computing systems in the 1960s to modern cloud-based ERP as a service solutions. Early MRP systems focused on inventory management and manufacturing requirements planning. ERP systems first emerged in the 1980s integrating multiple business processes across functions. Into the 2000s, ERP systems expanded with additional modules and became accessible as a service for small and medium enterprises.
This document summarizes an ERP presentation that discusses:
1) The necessity of ERP systems to address business challenges and integrate functions.
2) Characteristics of ERP like integrating all departments and allowing new technologies.
3) Benefits of ERP like reduced costs, improved information accuracy, and better decision making.
4) Major ERP software companies like SAP, Oracle, and PeopleSoft. SAP R/3 is highlighted as the leading ERP software.
Information systems perform four main functions: input, storage, processing, and output. Input involves collecting data that is stored securely in the system. Processing transforms the raw data into useful information by activities like comparing, calculating, and identifying trends. The system then produces an output of the processed information in various formats to support different users and business functions, with feedback also provided to improve future system performance.
SAP is a widely used ERP software package originally developed in Germany. It provides integrated modules for key business functions such as finance, logistics, production, and human resources. The document provides an overview of SAP, describing its origins and components. It explains that SAP has a common database that allows real-time access and integration across different business departments and functions within a company.
Enterprise resource planning (ERP) is business management software that allows an organization to use a system of integrated applications to manage the business.
This document provides information about Management Information Systems (MIS) and Enterprise Resource Planning (ERP). It discusses the evolution and purpose of MIS, including its role in providing managers with information to support decision making. It then covers the evolution of ERP from inventory control and material requirement planning systems to today's enterprise-wide systems. The document shares definitions of ERP and discusses its need, benefits, and common modules/products like SAP. It also includes a case study on the online classifieds company Quikr in India.
What Is ERP
ERP includes "Enterprise Resource Planning". For ERP, we can state that an information system in which all information and organizational procedures are incorporated into a single point. In general, ERP programs include a variety of components, consisting of software and hardware. Many ERP systems utilize a combined database to keep data from various functions that they can integrate within the enterprise.
This document discusses enterprise resource planning (ERP) systems and how they integrate transaction data across various business functions such as accounting, finance, human resources, production, logistics and customer relationship management. ERP systems allow a company to capture transaction data at the source, and share it across departments to facilitate reporting, analysis and improved decision making. The integration of data helps make businesses more efficient by combining operational information.
Enterprise resource planning (ERP) systems have evolved over time from individual business function automations in the 1960s to integrated systems covering all business functions by the early 1990s. ERP systems were developed to integrate various departmental systems like inventory, financials, and human resources on a single database. Initially based on mainframe and MRP technology, modern ERP systems use client-server architecture and integrate additional functions like supply chain management and customer relationship management. ERP systems provide benefits like reduced costs and improved data sharing across the entire organization compared to separate departmental systems.
1. An ERP system manages a company's resources like products, customers, suppliers, employees, facilities, finances, etc. It integrates data across departments for improved communication, productivity and efficiency.
2. Originally, departments used separate information systems like custom programs or spreadsheets. This led to data silos with inefficient exchange of information between departments.
3. The development of local area networks and client-server computing in the late 1980s/1990s allowed departments to connect their systems and exchange data seamlessly, addressing the data silo issue. This paved the way for integrated ERP systems spanning all company resources.
The document discusses the history and evolution of enterprise resource planning (ERP) systems from the 1960s to present. It begins with a brief overview of how ERP systems emerged from earlier systems like inventory control packages in the 1960s, material requirements planning in the 1970s, manufacturing resource planning in the 1980s, and became popular standalone systems in the 1990s. The document then examines key aspects of ERP systems including their definition, benefits to organizations, and issues during implementation.
This document discusses the benefits of implementing an ERP (Enterprise Resource Planning) system. It notes that ERP systems can help companies by reducing costs, improving customer service and inventory management. The document provides examples of how ERP systems can help with sales, logistics, production and financial management. It also lists some common business challenges that ERP systems can help address, such as meeting deadlines, optimizing resource usage, and maintaining profitability. Overall, the document promotes ERP systems as a way for companies to more efficiently manage operations and better achieve their business objectives.
Erp articles compilation by salman hanzalaSalman Hanzala
The document provides information about Enterprise Resource Planning (ERP) software. It defines ERP as software that allows organizations to integrate business processes across departments like manufacturing, sales, accounting, and human resources. The document discusses the history of ERP, outlines common ERP modules like supply chain management, customer relationship management, and financial management. It also examines current ERP technologies like deeper integration between systems, mobile ERP accessible on smartphones and tablets, and the rising popularity of cloud-based ERP systems.
The document discusses how comprehensive training is key to effective implementation of Enterprise Resource Planning (ERP) systems. ERP systems integrate information across different business functions on a single database, but require companies to undergo significant process changes. Often, failed ERP implementations can be blamed on improper training that does not prepare users for these changes. The document proposes an ERP education and training plan that addresses who needs training, when it is needed, and what topics should be covered to maximize the benefits of ERP systems.
Enterprise Resource Planning (ERP) systems aim to integrate all departments and functions across a company onto a single computer system that can serve all those different departments' particular needs. ERP systems evolved from materials requirements planning (MRP) systems used in manufacturing in the 1960s-1970s and were further developed to integrate other functions like finance in the 1980s. In the 1990s, large comprehensive ERP systems like SAP R/3 emerged that integrated key modules for major business functions and processes across an entire organization.
Technology can increase student learning and engagement when used effectively in the classroom. Research shows that technology can (1) increase social skills through more collaboration, (2) prepare students for future jobs by teaching tech skills, and (3) improve motivation and achievement, especially for students with special needs. However, technology will only be effective if teachers receive proper training, have a positive attitude, and use it to supplement the curriculum, not just for drill and practice. With a technology plan that includes teacher training and support for higher-order thinking applications, schools can "hit the bullseye" and see improved student outcomes.
1) Medicare and other insurers will cover routine costs associated with clinical trials, such as standard of care procedures, but not investigational procedures or costs of administering investigational items.
2) A coverage analysis should determine which trial procedures will generate charges to ensure appropriate billing. Coding instructions inform the billing process of coverage.
3) Special circumstances like an absent or limited sponsor require identifying alternate payment sources for non-routine costs to avoid denying coverage of related routine costs.
A presentation given at the Coalition for Networked Information describing efforts undertaken by 3 partnered organizations (UCSF CTSI, UCSF Library, California Digital Library) to support sharing of research data by UCSF investigators
7 signs that show you need to start using an mrp systemMRPeasy
You can see how your organization has significantly grown within the last periods. More staff, more tools and maybe you have incorporated more machinery or new technology.
#mrpsystem #mrpeasy #erpsystem #mrp #erp #manufacturing #manufacturingsoftware #sevensigns #reasonstostart #whymrp #whyerp #saas
An Enterprise Resource Planning (ERP) system integrates core business processes like finance, supply chain, production and human resources into a single system. ERP has evolved from earlier systems like MRP and MRPII. Key reasons for companies to implement ERP include integrating financial and customer order information, standardizing processes, and reducing inventory levels. ERP provides benefits such as improved cost control, faster response to customers, and standardized HR processes. Successful ERP implementation requires careful planning including deciding whether to customize the system or follow its standard processes and whether to use an in-house or outsourced team.
The document traces the evolution of ERP systems from centralized computing systems in the 1960s to modern cloud-based ERP as a service solutions. Early MRP systems focused on inventory management and manufacturing requirements planning. ERP systems first emerged in the 1980s integrating multiple business processes across functions. Into the 2000s, ERP systems expanded with additional modules and became accessible as a service for small and medium enterprises.
This document summarizes an ERP presentation that discusses:
1) The necessity of ERP systems to address business challenges and integrate functions.
2) Characteristics of ERP like integrating all departments and allowing new technologies.
3) Benefits of ERP like reduced costs, improved information accuracy, and better decision making.
4) Major ERP software companies like SAP, Oracle, and PeopleSoft. SAP R/3 is highlighted as the leading ERP software.
Information systems perform four main functions: input, storage, processing, and output. Input involves collecting data that is stored securely in the system. Processing transforms the raw data into useful information by activities like comparing, calculating, and identifying trends. The system then produces an output of the processed information in various formats to support different users and business functions, with feedback also provided to improve future system performance.
SAP is a widely used ERP software package originally developed in Germany. It provides integrated modules for key business functions such as finance, logistics, production, and human resources. The document provides an overview of SAP, describing its origins and components. It explains that SAP has a common database that allows real-time access and integration across different business departments and functions within a company.
Enterprise resource planning (ERP) is business management software that allows an organization to use a system of integrated applications to manage the business.
This document provides information about Management Information Systems (MIS) and Enterprise Resource Planning (ERP). It discusses the evolution and purpose of MIS, including its role in providing managers with information to support decision making. It then covers the evolution of ERP from inventory control and material requirement planning systems to today's enterprise-wide systems. The document shares definitions of ERP and discusses its need, benefits, and common modules/products like SAP. It also includes a case study on the online classifieds company Quikr in India.
What Is ERP
ERP includes "Enterprise Resource Planning". For ERP, we can state that an information system in which all information and organizational procedures are incorporated into a single point. In general, ERP programs include a variety of components, consisting of software and hardware. Many ERP systems utilize a combined database to keep data from various functions that they can integrate within the enterprise.
This document discusses enterprise resource planning (ERP) systems and how they integrate transaction data across various business functions such as accounting, finance, human resources, production, logistics and customer relationship management. ERP systems allow a company to capture transaction data at the source, and share it across departments to facilitate reporting, analysis and improved decision making. The integration of data helps make businesses more efficient by combining operational information.
Enterprise resource planning (ERP) systems have evolved over time from individual business function automations in the 1960s to integrated systems covering all business functions by the early 1990s. ERP systems were developed to integrate various departmental systems like inventory, financials, and human resources on a single database. Initially based on mainframe and MRP technology, modern ERP systems use client-server architecture and integrate additional functions like supply chain management and customer relationship management. ERP systems provide benefits like reduced costs and improved data sharing across the entire organization compared to separate departmental systems.
1. An ERP system manages a company's resources like products, customers, suppliers, employees, facilities, finances, etc. It integrates data across departments for improved communication, productivity and efficiency.
2. Originally, departments used separate information systems like custom programs or spreadsheets. This led to data silos with inefficient exchange of information between departments.
3. The development of local area networks and client-server computing in the late 1980s/1990s allowed departments to connect their systems and exchange data seamlessly, addressing the data silo issue. This paved the way for integrated ERP systems spanning all company resources.
The document discusses the history and evolution of enterprise resource planning (ERP) systems from the 1960s to present. It begins with a brief overview of how ERP systems emerged from earlier systems like inventory control packages in the 1960s, material requirements planning in the 1970s, manufacturing resource planning in the 1980s, and became popular standalone systems in the 1990s. The document then examines key aspects of ERP systems including their definition, benefits to organizations, and issues during implementation.
This document discusses the benefits of implementing an ERP (Enterprise Resource Planning) system. It notes that ERP systems can help companies by reducing costs, improving customer service and inventory management. The document provides examples of how ERP systems can help with sales, logistics, production and financial management. It also lists some common business challenges that ERP systems can help address, such as meeting deadlines, optimizing resource usage, and maintaining profitability. Overall, the document promotes ERP systems as a way for companies to more efficiently manage operations and better achieve their business objectives.
Erp articles compilation by salman hanzalaSalman Hanzala
The document provides information about Enterprise Resource Planning (ERP) software. It defines ERP as software that allows organizations to integrate business processes across departments like manufacturing, sales, accounting, and human resources. The document discusses the history of ERP, outlines common ERP modules like supply chain management, customer relationship management, and financial management. It also examines current ERP technologies like deeper integration between systems, mobile ERP accessible on smartphones and tablets, and the rising popularity of cloud-based ERP systems.
The document discusses how comprehensive training is key to effective implementation of Enterprise Resource Planning (ERP) systems. ERP systems integrate information across different business functions on a single database, but require companies to undergo significant process changes. Often, failed ERP implementations can be blamed on improper training that does not prepare users for these changes. The document proposes an ERP education and training plan that addresses who needs training, when it is needed, and what topics should be covered to maximize the benefits of ERP systems.
Enterprise Resource Planning (ERP) systems aim to integrate all departments and functions across a company onto a single computer system that can serve all those different departments' particular needs. ERP systems evolved from materials requirements planning (MRP) systems used in manufacturing in the 1960s-1970s and were further developed to integrate other functions like finance in the 1980s. In the 1990s, large comprehensive ERP systems like SAP R/3 emerged that integrated key modules for major business functions and processes across an entire organization.
Technology can increase student learning and engagement when used effectively in the classroom. Research shows that technology can (1) increase social skills through more collaboration, (2) prepare students for future jobs by teaching tech skills, and (3) improve motivation and achievement, especially for students with special needs. However, technology will only be effective if teachers receive proper training, have a positive attitude, and use it to supplement the curriculum, not just for drill and practice. With a technology plan that includes teacher training and support for higher-order thinking applications, schools can "hit the bullseye" and see improved student outcomes.
1) Medicare and other insurers will cover routine costs associated with clinical trials, such as standard of care procedures, but not investigational procedures or costs of administering investigational items.
2) A coverage analysis should determine which trial procedures will generate charges to ensure appropriate billing. Coding instructions inform the billing process of coverage.
3) Special circumstances like an absent or limited sponsor require identifying alternate payment sources for non-routine costs to avoid denying coverage of related routine costs.
A presentation given at the Coalition for Networked Information describing efforts undertaken by 3 partnered organizations (UCSF CTSI, UCSF Library, California Digital Library) to support sharing of research data by UCSF investigators
This document summarizes the EngageUC project which aims to establish an efficient, ethical and sustainable system for obtaining biospecimens and data from UC stakeholders. It involves 3 aims: 1) stakeholder engagement to review policies and develop a community informed consent approach, 2) an RCT to evaluate different consent methods, and 3) policy translation to develop harmonized policies based on RCT results. The activities are organized over 3 time periods and include convening stakeholders, developing new consent procedures, an RCT comparing consent types, and establishing updated policies.
This document provides an introduction and overview of enterprise resource planning (ERP) systems and related technologies. It begins by defining ERP and describing its purpose of integrating key business processes. It then discusses the evolution of ERP from earlier systems like MRP and MRP II. Common myths about ERP implementations are addressed. Key ERP modules like finance, HR, and production planning are outlined. Related technologies such as business process reengineering, supply chain management, and data mining are also introduced. The document poses questions and provides answers on topics including decision support systems, enterprise information systems, ERP drivers and benefits, and the typical lifecycle of an ERP implementation project.
This document provides an introduction and overview of enterprise resource planning (ERP) systems and related technologies. It begins by defining ERP and describing its purpose of integrating key business processes. It then discusses the evolution of ERP from earlier systems like MRP and MRP II. Common myths about ERP implementations are addressed. Key ERP modules like finance, HR, and production planning are outlined. Related technologies such as business process reengineering, supply chain management, and data mining are also introduced. The document poses questions and provides answers on topics including decision support systems, enterprise information systems, ERP drivers and benefits, and the typical lifecycle of an ERP implementation project.
Weinberg pims vs erp first place undergrad (1)Allen Ikem
The document is a student paper submission form for a paper titled "PIMS vs. ERP systems: A study based on applications". It includes information about the authors such as their names, education levels, email addresses, and educational affiliations. It also provides contact information for the primary author. The paper analyzes the advantages of Product Information Management Software (PIMS) over larger Enterprise Resource Planning (ERP) systems for small business applications using the Husky Tech Store on the St. Cloud State University campus as a case study.
MBA 5401, Management Information Systems 1 Course Le.docxandreecapon
MBA 5401, Management Information Systems 1
Course Learning Outcomes for Unit III
Upon completion of this unit, students should be able to:
1. Explain the concepts and applications of Enterprise Resource Planning (ERP)
systems.
2. Explain the critical concepts of distributed systems and client/server systems,
including the role of middleware and the distinction between two-tier and
three-tier client/server systems.
3. Describe seven major types of organizational systems in use today.
4. Explain the concept of knowledge management and how it is implemented in
an organization.
5. Describe ten major types of managerial support systems in use today.
6. Differentiate the types of managerial support systems, and how they relate to
the enterprise systems.
Unit Lesson
Just What is ERP?
To answer this question, it helps to look back and consider how companies managed
before enterprise resource planning (ERP). Companies consist of a number of
functions that each work together to earn a profit. These include the creation of a
product, (Research and Development (R&D), the production of a product
(manufacturing), locating clients and offering the product for sale (Sales and
Marketing), shipping the product (warehouse functions), and finally, taking money and
accounting for the sale (Finance and Accounting). Prior to the advent of computer
systems in business, each function carried out their respective jobs on paper, and kept
detailed records in journals, file folders, and filing systems. As the technology became
available, some of these paper functions became computerized in order to make them
more efficient. However, computerization did not solve the fundamental problem of the
paper organization—the difficulty of sharing data.
In a paper organization, accounting kept the books in accounting journals, sales and
marketing made notes of contacts in pocket planners and wrote paper reports—or
perhaps even sent and received faxes. R&D kept records in engineering notebooks,
and finally, the warehouse function kept files and records of incoming and outgoing
transactions. ERP was a response to the problem of the intra-organizational sharing of
Reading
Assignment
Chapter 5:
Enterprise Systems
Chapter 6:
Managerial Support
Systems
Key Terms
1. Batch processing
2. Data mining
3. Data warehousing
4. Decision support
system (DSS)
5. Enterprise resource
planning (ERP)
6. Enterprise systems
7. Executive support
system (EIS)
8. Group support
system (GSS)
9. Groupware
10. Intranet
11. Managerial support
systems
12. Material requirements
planning (MRP)
13. Online processing
UNIT III STUDY GUIDE
Enterprise and Support Systems
MBA 5401, Management Information Systems 2
data that previously resided in a function so that companies could become more
focused and competitive. However, ERP was not born in a day—rather, it started in ...
This document discusses the strengths and weaknesses of enterprise resource planning (ERP) systems. It analyzes the high costs of ERP software, implementation, training, and consultants. Several hidden costs are also examined, including integration, customization, data conversion, analysis, and replacement of staff. Common causes of ERP project failures include lack of change management and training, poor planning, underestimating skills and resources. Overall, ERP can integrate financial and customer information, standardize processes, and reduce inventory, but success depends on staff skills and experience with the system.
In today's competitive world, one has to manage the future of an enterprise more cleverly. Managing the future means managing the information. A large enterprise may generate huge amount of data such as financial data, customer details, purchase details, employee data etc. Only the organization that makes the best possible use of this information can succeed. In this age of information explosion, it is very difficult to manage this huge information by people alone.
Information technology and its related technologies can be used for planning and organizing resources and information of an enterprise. Hence most of the organizations are moving to Enterprise Resource Planning (ERP) packages as a solution to their information management problem.
A detailed presentation related to ERP Systems in Oracle. It is very popular for any firm/organization to work in their platform and solve the business work and provide solution. Software development processes helps to built software using Agile models.
A complete guide of Oracle ERP System. It is the most advanced system of current market scenario. A brief written content with the help of researchers, scientists and engineers. Oracle is targeting the current ERP market and increasing their productivity and providing a better solution for Organizations to improve there business.
Accounts is the main pillar of any business, we provide you with a cloud accounting software that maintains accounts for your business easily. Visit www.arcus-universe.com
- ERP systems originated from the need to integrate inventory control systems in manufacturing in the 1960s and evolved to include more comprehensive organizational integration.
- Common definitions of ERP systems refer to integrated business software and technologies that improve processes, metrics, and performance across business units.
- Market reports show that while no single vendor dominates, SAP, Oracle, and Microsoft consistently have the largest market shares. Satisfaction varies and depends on realistic expectations set during implementation.
This document discusses the importance of senior finance professionals understanding enterprise resource planning (ERP) systems and their financial implications. It covers:
1. ERP systems are typically a company's largest IT investment but their business and financial impacts are often misunderstood.
2. It is important for CFOs and finance teams to understand ERPs because they can help with financial planning, control, and as system users.
3. The lifecycle of an ERP includes evaluation, implementation, upgrades, and ongoing maintenance which impact costs and benefits over 10-15 years.
Enterprise Resource Planning (ERP) systems integrate data and processes across an organization into a unified system using a shared database. ERP aims to standardize, streamline, and integrate diverse operations and information flows. Key benefits include improved productivity, quality, and competitiveness through optimization of resources and processes. However, ERP also faces limitations such as high costs, risk of loss of competitive advantage from process re-engineering, and dependence on proper training and use of staff.
Enterprise Resource Planning (ERP) systems evolved from earlier standalone systems used during the 1960s and 1970s to integrate business functions. Materials Requirement Planning (MRP) systems were first developed in the late 1970s to integrate production planning, procurement, and inventory functions. MRP systems later evolved into MRP II systems to also incorporate distribution planning and forecasting. ERP systems were then introduced in the late 1980s to further integrate additional business functions such as finance, human resources, and supply chain management across the entire organization. Major ERP vendors like SAP, Oracle, and JD Edwards began developing ERP software building upon their earlier MRP products. ERP systems continued to evolve throughout the 1990s by adding new features and
ERP solutions manage a multitude of business processes and enable the flow of information among them. Moreover, by gathering a firm’s shared transactional data from various sources, enterprise planning systems delete data duplication and offer data integrity with a single source of information.
The document discusses a case study of Space Age Furniture Company, which is facing a problem in its manufacturing operations. As the Operations Officer, Coral Snodgrass is responsible for generating value through goods and services while balancing supply and demand. The document examines how operations managers are crucial to running a business efficiently and the challenges faced by Space Age Furniture Company.
Last week, Rippling, raised a $45 million Series A led by Kleiner Perkins. We took an unusual approach in raising our A, starting with the fact that we had no formal Pitch Deck. Instead, the centerpiece of our fundraising materials was an Investor Memo, which laid out our pitch in prose.
Fundraising success is ultimately driven by the business you’re building and the problems you’re solving for customers. The quality of the materials you prepare and tactics you use during the process are a much less important optimization. But we want to share our memo because we think it's a unique fundraising asset that could be useful to other entrepreneurs and could help fundraising proceed more smoothly for both companies and investors.
200 Words-Describe three types of systems used in organizations..docxeugeniadean34240
200 Words-
Describe three types of systems used in organizations. Note the factors that normally lead to adopting the system and requirements that will likely push its future growth of each type.
Discuss an IT system that has transformed the way organizations in at least one field carry out work. Note what requirements drove the system to be developed and what requirements are likely to drive it to change in the future.
Reply with 150 words-
(DO YOU AGREE WITH THE BELOW POST? WHY OR WHY NOT? IF SO WHY? IF NOT WHY NOT?)
Business had changed a great deal in the past fifty years. Businesses used to keep everything on paper and file it in cabinet. Trying to find the information that you needed was a long process that took a lot of man power. Paper files also came with a lot of error and you had to depend on the people writing the data to get accurate information. For large organizations this was a painful and unreliable process and it you couldn't get it right then your business would have a hard time succeeding. There are many systems that can help organize information and place it where it needs to be. One of the information systems that sticks out to me is the ERP system. This system may be costly and may take a lot of training to implement, but if it is done right it can show great results. Take a large manufacturing company for instance. You have a finance and accounting department, an HR department, sales department, and an operations department. Imagine keeping all of that information on paper and relying on hundreds of employees to fill out the paper work correctly. That sounds like a nightmare to me. ERP systems were designed to organize all of the information from each department and accurately make decisions based on that information. ERP systems can be difficult to use and train others on how they work. I believe that ERP systems will become more user friendly and easier to implement into any organization in the future.
Transformational IT technologies transform organizations, as they provide businesses with new opportunities for strategic advantage while challenging previously successful techs. It changes the basic ways that people and departments work and may even change the very nature of the business enterprise. The most important and significant transformational IT system that I can think of that changed the way organizations work was the World Wide Web, or the Web. This multimedia was invented by Sir Tim Berners-Lee, a British computer scientist, in 1989. The Web transformed how business was made worldwide, the interaction between a company and consumer was closer than ever. It allowed organizations to make information instantaneously available throughout the world, targeting more consumers, and all this at a lower cost, saving companies alot of money. Now with the new techs, such as social media and ad revenue, organizations are able to reach people even faster. That is the future, social media, videos, etc..Where compani.
The topic of ERP can sometimes seem complicated and overwhelming, but the ERP experts at MAX are here to help. This eBook covers all the bases, helping manufacturing professionals understand the ins-and-outs of ERP and how they apply to your business. Read on to learn the basics of ERP, what type of companies benefit most and how, the fundamentals of implementation, how to select the right software, and more.
http://max4erp.com/
The document discusses the evolution and history of ERP systems from inventory control packages in the 1960s to extended ERP systems today. It describes how ERP systems evolved from materials requirements planning (MRP) systems in the 1970s to manufacturing resource planning (MRP II) systems in the 1980s to integrated enterprise resource planning (ERP) systems in the 1990s that began to incorporate additional modules. Today's extended ERP systems provide connections to functions like customer relationship management (CRM) and supply chain management (SCM). The document also outlines some of the benefits and challenges of implementing ERP systems for organizations.
Similar to Faculty.babson.edu grossman breeze_erp_erp_printable_version (20)
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3Data Hops
Free A4 downloadable and printable Cyber Security, Social Engineering Safety and security Training Posters . Promote security awareness in the home or workplace. Lock them Out From training providers datahops.com
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
1. 1
F.W. Olin Graduate School of Business
Enterprise Resource Planning Systems
(ERP)
a pre-briefing for the Cisco case
Understanding the Technology and
the Issues of ERP Systems
By Professor Ted Grossman
Welcome to the pre-brief for the Cisco Case: Understanding the Technology, and
the Issues of ERP Systems. Let me take a minute to inform you about the controls
at the bottom of the screen. The right arrow is to advance to the next slide, and the
left arrow is used to reverse one slide. The presentation will not automatically
advance to the next slide at the end of the audio. It will be necessary for you to click
the right arrow to go to the next slide. On the left hand side of the screen is the list
of slides. You may use these as a navigation tool. If for example: you leave the
presentation, and wish to return to a particular slide, click on the slide you wish to
advance to. Lastly, on the bottom of the next slide is a button labeled “printable
version”. If you click on this button, the system will pop up a window with an Adobe
PDF version of the slides which you can print from. Once you have printed the
slides, make sure to close the pop up window, to return to the pre-brief. Now click
on the next slide arrow.
2. 2
F.W. Olin Graduate School of Business
Introduction and Learning Objectives
In this lesson, we will:
• describe the functional modules in an ERP system
• understand the process by which ERP systems are
implemented
• understand the issues that companies have faced
when implementing ERP systems
• provide background for analyzing the experience
encountered by Cisco in its implementation of an
ERP system
printable version
There are several goals that we’re trying to accomplish as a part of this pre-brief.
The first is to help you understand the various functions that are provided as part of
an ERP system. As you’ll learn in this presentation there are numerous functional
modules that come in the ERP system, and it’s important to understand what they
all do, and how they contribute to the success of the ERP system. The second is to
understand the process by which companies implement an ERP system. The third
is to understand the issues that companies face when they implement an ERP
system. As you’ll learn as a part of this presentation there have been numerous
successes, and some highly publicized failures, for small medium and large
companies, in implementing ERP systems, and we need to understand why those
have occurred. Lastly, I want to mention to you, that while this pre-brief is to help
you analyze the Cisco case, we will not be discussing the Cisco case, but it’s
important to understand how ERP systems work, their history, how they’re
implemented, and what their critical success factors are so that you better analyze,
and understand why Cisco did what they did, and why they were successful in their
implementation of an ERP system.
3. 3
F.W. Olin Graduate School of Business
Enterprise Systems Model
Enterprise Resource
Planning
(ERP)
Customer Relationship
Management
(CRM)
Supply Chain
Management
(SCM)
It’s important to understand where an ERP or an Enterprise Resource Planning
system fits into a company’s enterprise system model. We typically think of three
main components, although there are many, many other components in a
company’s IT strategy, and IT architecture. The three main ones we think about are
supply chain management, enterprise resource planning systems, and customer
relation management systems. As you see from this diagram, the ERP system is
really the central focus for the internal functions of the company, with the ERP
system supplying information to the supply chain management system, which
passes information back, and likewise with the CRM system, there is this passing of
information between the customer facing system, the CRM system, and the ERP
system.
4. 4
F.W. Olin Graduate School of Business
Enterprise Systems Model
CustomerImproved Customer
Service
Increased Revenues
Reduced Sales Cost
CRM
Internal
Enterprise
Corporate Efficiency
Reduced Costs
Reduced Inventory
Increased Control
Integrated System
Central Data Repository
Standardized Practices
ERP
SupplierReduced Purchasing Cost
Information Exchange
Collaboration
Reduced Inventory
SCM
FocusValue PropositionSystem
Supply chain management system, focuses on our supplier, and how we exchange information with
that supplier so that we can reduce the purchasing cost of all the materials, be it, direct materials, or
maintenance repair and operation materials, from that supplier. The goal is of course reducing cost,
but also providing a platform for exchanging information and to collaborate with that supplier, and to
reduce the inventory, and the cycle time from when we determine that we need to order additional
inventory, and when we receive it. In an ERP system, our focus is internal within the enterprise or the
corporation. We’re trying to create corporate efficiencies which helps us control our inventory, control
our costs by reducing inventory. We want to increase control over our entire operation, not just over
our inventory, but over our manufacturing, our human resource management, and get better control
over our accounts receivables, and our payables. We do that by having one integrated system; one
central data depository which is integrated where all of these systems feed from this one integrated
data source. Lastly we try to standardize our practices throughout the enterprise. That helps to
provide efficiency and gives us greater control. In a customer relationship management system, a
CRM system, our focus is customer. It is a customer faced system. We’re trying to increase
customer service, increase revenues, and reduce sales cost. As I mentioned in the prior slide, we do
this by feeding data back and forth between our ERP system, and our CRM system, where by our
ERP system provides information about our inventory, and the cost of our materials, so that we can
supply better information to our customers about their orders and when their going to be received
and any problems they might be having with those orders.
5. 5
F.W. Olin Graduate School of Business
ERP History
• Companies initially developed disparate financial
and inventory applications
• They then began applying IT to developing
manufacturing applications (MRP III)
• Software companies integrated all these functions,
including distribution and warehousing, into a single
integrated package called ERP using a single
integrated database. One transaction updates all
applications.
• As ERP companies installed more ERP systems, they
learned “industry best practices” and offered
personalization options (switches – turn on or off) in
the package without having to modify the software.
As options expanded, the number and complexity of
personalization switches increased tremendously
(thousands of switches).
It’s important to understand the evolution behind EPR systems. Initially companies developed financial and inventory
applications. These were considered the low hanging fruit for management information systems back in the 70’s and 80’s, so
the initial applications tended to be accounts receivable, accounts payable, payroll, general ledger, and inventory control.
Then companies started migrating toward order entry. As companies became more sophisticated, they started looking at
manufacturing applications and the first major manufacturing application that was developed was MRP3, which stands for
manufacturing resource planning. In those systems companies said, “Well, what kinds of raw materials do I need to make
this product, and if I know that I have to make 1000 of these widgets, therefore what kinds of components to I need to order
from my suppliers, and what kind of manufacturing schedule to I need to have to accomplish that?” At some point in the late
80’s software companies looked at these financial and inventory applications and manufacturing applications and started
integrating these applications into one package, which ultimately became called ERP systems. As time went on, these
packages became more and more complex, with more functions being added to them, including, distribution, transportation,
warehousing, human resource management, etc. The important thing was that they fed off of one integrated database. In the
past all of those disparate financial applications and manufacturing applications had multiple file systems and multiple
databases so therefore it was possible to have multiple versions of the truth. You could have vendor information in both of
those systems which would differ. In your accounts payable system you would have the names and addresses where you
would be paying a bill, where as in manufacturing system you would have the names and addresses of where you would be
ordering merchandise from, so therefore you ended up with multiple files with differing information, all correct, but multiple
versions of the truth. The goal in the initial applications of ERP systems was to have one single integrated database that all
of these systems would feed from, and also that one transaction would update all of these applications, so it wouldn’t be
necessary to input multiple transactions for the same sale. Entering a sale took care of invoicing the customer, decrementing
the inventory, changing the manufacturing requirements, changing the ordering needs etc. As ERP companies became more
sophisticated, and as they implemented more and more of these systems across a vertical industry they developed what’s
commonly referred to as industry best practices. They learned as they implemented more and more of these systems, and
started to personalize, or create personalization options within their package. Instead of having to reprogram the package, or
to customize the package for each implementation, what they did was they programmed a series of switches, software
switches, which you would either turn on or turn off, which would turn on, or turn off options within that package. Some of
those things would be the kind of printouts that would be available, or what information would show up on the screen, or
whether an item was ordered in each’s, or by the pound, or whether an item had sales tax, or even whether this company
dealt in dollars or in British pounds, or Deutch Marks, or all kinds of options that were available to these packages. The result
of that was that these packages became extremely complex, as the number of personalization switches increased into the
thousands.
6. 6
F.W. Olin Graduate School of Business
ERP History (continued)
• Because ERP packages are tightly integrated,
personalization was the route of preference (installing
vanilla) over modifying (rewriting the programs) the
software.
• As the complexity of the ERP packages increased, ERP
vendors enlisted 3rd party consulting organizations to
help implement the packages at client sites, creating a
major industry in ERP consulting practices.
• The platforms moved from mainframe to client server
to Web enabled.
• ERP vendors have steadily increased the scope of ERP
to include a “soup to nuts” menu, including full
financials, manufacturing, distribution, HRM, analytics,
etc.
• Over the past few years, major consolidation has taken
place in the ERP vendor space.
Because ERP packages are so tightly integrated, and highly complex, it is very difficult to modify the
software, or to rewrite the software. Because there are so many different personalization switches
available as part of the ERP system, the route of preference by most companies was to try to live
with the functionality that was offered within that ERP package, That was referred to as installing
Vanilla, in reference to going out for ice cream and buying a simple flavor, and not an exotic flavor
like Tuty Fruity. Companies tried to stick with the Vanilla software. However these packages are so
complex, and the ERP software developers realized that it takes a long time to implement these
packages, and we’re not talking about implementing them in weeks or months, but in many cases,
over a period of two or three or four or five years, and it requires a tremendous amount of resources
from the ERP software vendor to help the company implement these packages. Realizing that they
didn’t have the resources to do it, ERP systems vendors went out and started to train third party
consulting organizations to help implement the packages at the client sites. This created a major
industry in ERP consulting practices. If you look at most of the large and many of the small consulting
companies in the United States you’ll find that many of them have major consulting practices in
implementing all of the various ERP systems. Historically the initial ERP implementations were on
main frame computers; typically large IBM main frame computers. As we moved into the 90’s that
migrated to client server technology, and many of the companies SAP, JD Edwards, and Oracle
started offering their software in a client server environment. Ultimately as we moved into the late
90’s they changed that to make them web enabled. What you’ll find is that many companies have a
mixture of the technology. They still have some of the stuff on main frame, but most of them have a
mixture of client server, and web enabled ERP systems. ERP vendors have steadily increased their
offerings of modules and have expanded the scope of their ERP systems to include a veritable suit to
nut menus of functionality, including virtually all of the financial, manufacturing, distribution,
transportation, analytics, human resource management, and demand planning and in fact many of
them have now blurred the distinction between CRM and supply chain management, and have
started to offer some of the modules that you would typically think of being CRM, and SCM. Over the
past few years there has been a tremendous consolidation that has taken place over the ERP vendor
space. Just recently, People soft, and JD Edwards merged. A company like Bohn has virtually gone
out of business in the United States, so there have been a number of companies that had major
positions in the 90’s in ERP who are no longer here and others have merged.
7. 7
F.W. Olin Graduate School of Business
ERP Functionality
Source: www.sap.com
This slide, taken from the SAP web site, gives you an example of the suit to nuts
menu that is available within an ERP system. As you can see, on the left hand side
are the major categories of modules that are available within SAP’s ERP offering. It
breaks in to analytics, financials, human capital management, operations, value
generation, support operations, and corporate services. We’re going to take a look
at a couple of those things, but as you look through what’s available there, within
each of those colored blocks, like financial accounting, or financial analytics, or
manufacturing, those break into hundreds and hundreds, of functions and modules
that are available within that particular part of SAP’s offering.
8. 8
F.W. Olin Graduate School of Business
ERP Financials
Source: www.sap.com
It’s important to understand that most companies to not implement all of the
modules that are available within an ERP system. In fact, many companies only
implement the financial modules, or the manufacturing modules. Some companies
start with the financials and then a couple of years later implement the
manufacturing modules etc. This slide, again from SAP, shows you just the
financials that are available within their ERP system. If you look on the left hand
side under financial accounting you’ve got the traditional general ledger, accounts
receivable, accounts payable, fixed assets. Then you move towards the middle and
you get into management accounting, with profit center accounting, and project
accounting, and product cost accounting, and profitability accounting, and transfer
pricing. As we move a little further to the right you get into cash management, and
credit management. As you move all the way to the right you get into a relatively
new area for ERP systems, and that’s corporate governance. That deals with
auditing, and whistle blower. Some of this has come about in fact due to recent
litigations, and changes which have occurred in the laws effecting public companies
specifically the Sarveighn Oxly act which creates all kinds of new requirements on
public companies in terms of how they report, and how they back up their numbers,
and what their obligations are. Companies like SAP saw this as an opportunity to
offer additional modules that they could integrate within their systems.
9. 9
F.W. Olin Graduate School of Business
ERP Sales Orders, Manufacturing,
Transportation, and Procurement
Source: www.sap.com
Financials and what SAP refers to as value generation are probably the two most
important parts of an ERP system. SAP has lumped a whole number of different
functions within this value generation; from procurement, and sales order entry and
management to customer service, inventory and warehouse management,
manufacturing, transportation. As you think about it, this is really the meat of what
an ERP system does. It integrates this entire sales, procurement of raw materials
and finished goods, managing the manufacturing process, managing the inventory
and warehouse replenishment, the transportation. It’s the entire cycle, from when an
order comes in, to how you produce it, how you warehouse it, how you distribute it,
and ship it to customer, how you bill your customer, and then how you provide the
appropriate customer service that is necessary for a successful transaction with
your client. Remember, all of this comes from one transaction, one sales transaction
updating one integrated database, so that there is one source for the transaction,
and one central data repository which provides all of the information for all of the
functions that are listed on this screen.
10. 10
F.W. Olin Graduate School of Business
ERP Analytics
Source: www.sap.com
While the prior two slides focused on those functions that we typically refer to as
operational control systems, those systems that are used by the worker bees of the
organization to run the day to day operations of the company, analytics, those
contained within this slide, are typically used by middle and senior level
management of the company to help make better decisions, in running the medium
term, and long term operations of the company. They provide the exception reports,
and the strategic reports that help manage the direction of the company, and look
for problem areas within the company so that they can better and more efficiently
manage the company. If you look at this menu of modules within it you see things
like strategic planning, or financial statement planning, or overhead cost
management, profitability management. If you think about it, those are the kids of
things that historical data, those pieces of information that bubble up from those
financial systems, and the purchasing and the distribution and inventory and
manufacturing to help consolidate and provide information for management to do
their planning and their budgeting and to make decisions where they need to control
cost or expand, offerings or expand staff, or whatever. Those are the functions that
are available within analytics.
11. 11
F.W. Olin Graduate School of Business
ERP Vendors
• SAP: Click on MySAP Solutions Map to view
previous slides in more detail.
• Oracle
• J.D. Edwards
• PeopleSoft
• Microsoft Great Plains
• Macola
• Others
So who offers these services? Well, there are a number of companies that provide
ERP solutions. The two largest companies, that have been in the business for the
longest period of time are SAP, which is a European based company, and Oracle
which you’ll notice was the company of choice in the Cisco case. They have the
largest market share especially for medium to large companies here in the United
States. Then come companies like J.D Edwards, and PeopleSoft which also have
significant market share within the medium to large company market. Beneath that
you’ve got Microsoft Great Plains and Macola, and a number of other companies
that offer packages that are targeted toward small to medium sized companies.
These distinctions have become blurred as time has gone on. SAP is trying to
provide a scaled down ERP system for smaller companies, Great Planes having
been acquired by Microsoft is trying to make their package more robust and go after
more of the larger marketplace. PeopleSoft has acquired J.D Edwards, where
PeopleSoft was stronger in human resource management, systems, and J.D
Edwards was stronger in the manufacturing side of ERP. They’ve now consolidated
their offering. As you can see the marketplace is getting somewhat blurred as to
who’s stronger in what areas, but it’s clearly gone through consolidation, and the
offerings are growing.
12. 12
F.W. Olin Graduate School of Business
Project Initiation
& Mobilization
Technical
Assessment
&
Business
Process
Redesign
Fit Assessment
& Validation
Rapid
Application
Development
Testing
&
User Training
Implementation
&
Go Live
Information Technology Framework
ERP Implementation Process
As I mentioned earlier, implementing an ERP system is not a trivial process.
As you saw from the prior slides, ERP systems offer modules which impact
all of the various departments within the organization of a company. As a
result, implementing an ERP system requires representation from all of the
user groups to participate in that implementation. The steps that we go
through to implement an ERP system are represented on this slide. And they
start off from project initialization and mobilization, through technical
assessment, fit assessment, rapid application development, testing and
implementation. We’re going to talk at length, and in depth about what each
of those steps mean.
13. 13
F.W. Olin Graduate School of Business
Project Initiation and Mobilization
• Confirm project goals
• Develop detailed project plan
• Establish Steering Committee and
communications plan
• Establish cross functional core team
• Develop training plan and conduct core
team training
Implementing an ERP system requires a tremendous amount of planning in terms of
what your project goals are: What are you trying to accomplish? Drawing a tight box
around what this system needs to accomplish, and what you’re willing to sacrifice as
part of this implementation. You need to develop a detailed project plan: Who’s
going to be doing what? how soon do I need to have it done by? You need to
establish an executive level steering committee, and a communications plan. This is
probably the most important part of any ERP, or in fact system implementation. If
you don’t get the proper level of executive support from within a company, if the
organization doesn’t see the commitment from senior executive management
towards this project, you won’t get the cooperation that you need from the people
who actually have to do the work. The next group that you need to form are those
people who are actually going to determine the functions, test the system, go out
and proselytize the system, and train the entire organization in how to use this
system. This core team needs to have representation from all of the various core
functions within the organization. They will be the ones who will be driving the
planning and the implementation of the ERP system during the entire project.
Lastly, you need to develop a training plan for the core team, and conduct core
team training. They need to understand what this ERP system is capable of doing
so that they can determine how it will fit within the organization.
14. 14
F.W. Olin Graduate School of Business
Technical Assessment and Business
Process Redesign
• Document “As Is” business processes, data
and technology requirements
• Document “To Be” business processes,
data and technology requirements
This next step is really referred to as requirements definition, and it really breaks
down into two or three steps. The first is to understand how the company currently
does business. What are its current business practices? What data and technology
are available, within its current environment? Then you need to understand how the
ERP system, as it is available from the manufacturer with all of its personalization
switches works. What’s available? What functions are available with it? How it can
fit in within your company. What data elements are available within that ERP system
and what its technology requirements are? What kind of hardware does it use and
what kind of network is required to make it work? Then based on understanding
how you’re currently doing business and the way the package is capable of working
you determine where you want to go, or the to be business processes. How are we
going to run our business based on the capabilities of that ERP system, and the
data that’s available within it, and the technology requirements that will be inherent
in this new to be environment?
15. 15
F.W. Olin Graduate School of Business
Fit Assessment and Validation
• Perform “As Is” and “To Be” gap analysis
• Establish and test prototype environment:
conference room pilot (CRP)
• Resolve process and technology gap issues
• Research and acquire “Bolt Ons”
It’s always necessary to reconcile the differences between the “as is”, and the “to be.” This isn’t just
in terms of processes because clearly the new system is going to require that the company change
the way they do business, the way they handle orders, they way they handle materials, or the way
they communicate with their customers, or whatever it is. Those are the business process
reengineering that’s necessary when you implement a new ERP system. However, there are also
organizational changes that go along with the change from the “as is” to the “to be” and that’s part of
this ying and yang that goes on as you implement an ERP system. The next step is to take this “to
be” system, set the switches and establish a prototype environment. We usually refer to this as a
conference room pilot, and it’s called that because what companies to is, they take a conference
room, they set up a series of computer terminals connected to this new technology environment and
hooked up to the ERP system, and they set all the systems, and they prototype how this new system
will work. They bring in people representing the various functions company, and they’ll sit them down,
and say: “try out this screen, how does it work, how does it reconcile with the way you’re doing
business, are you comfortable with it?” It’s very important that you prototype the environment, and
understand the implications on the organization and what processes are going to have to be
changed, and how the organizations going to have to be changed, to fit this new “to be” environment.
Then you have to resolve these differences in processes and in technologies and we usually refer to
these as gaps. Some systems will do a great job in some areas, but will have gaps, and might not
have enough EDI or might not be able to handle multiple kinds of taxes, or multiple kinds of
currencies. The question is how do we adapt the system to do that? Currently what you have to do, is
you have to go out, and find other software packages that you can bolt on, to the ERP system, and
you’ll have to interface those “bolt on’s” to the ERP system, so that they pass the right data back and
forth.
16. 16
F.W. Olin Graduate School of Business
Rapid Application Development
• Identify data conversion sources / data
mapping and data cleansing
• Develop, test, and install data conversion
tools
• Design and develop system interfaces to
legacy systems and “Bolt Ons”
• Develop process documentation and
training material
Once you’ve prototyped the system, the next step is to actually develop and implement the ERP
system. Most people really don’t think about this issue of data conversion however, it’s probably the
one that’s the most difficult to do. You first have to identify what data elements you have within your
legacy systems. Where do I have customer information? Where do I currently have billing
information? Where do I have my accounts receivable, my accounts payable, my current
manufacturing data? Where does it reside, and what does it look like? What are the data
requirements of the new system? Well, if a customer name is 30 characters in the old system and it’s
only 25 characters in the new system, how do I convert that? If I had a 4 line address in the old
system and a 3 line address in the new system, or if I had a 3 line address in the old system, and a 4
line address in the new system how do I map that from one to the other? Also how do I clean my
data? I might have data appearing in my legacy systems in multiple places and multiple sources for
the same data. Which one is the right data? How do I clean my data so that when I bring my data
over to the new system, I know that it’s correct? You have to develop, and test and install those tools
that you’re going to use for converting the data from the old system to the new system. You have to
design and develop the interfaces between the old legacy system, and the new system, and the “bolt
on’s” to the new system. Sometimes these can be very difficult, especially when they have different
kinds of data requirements. Lastly you have to develop documentation, and training manuals. This is
one area that companies frequently skip on. They don’t provide the right amount of training, and if
you don’t train your organization either they’re not going to use the system, or they’re not going to
use it properly, and you’re going to have all kinds of problems when you go live with a new system.
17. 17
F.W. Olin Graduate School of Business
Testing and User Training
• Load production hardware, software, and
interfaces
• Execute conference room pilot and confirm
personalization
• Test system interfaces
• Schedule and conduct end user training
The next step is to test, and to train your users. You have to load the production
hardware, software, and the interfaces. You have to execute your conference room
pilot with the latest of changes, and confirm that everything works the way you want.
You have to test those system interfaces between the legacy systems that will
remain, perhaps your new data warehouse, the “bolt on’s” and you have to schedule
and conduct, end user training. As I mentioned in my last slide, this is the one that
takes the most time. Because every group within the company is impacted by this
system, how do you think about training all those people? Do you train the trainers,
and the trainers go out and train the people within their user groups. There are
different strategies that you can use to provide end user training, especially where
you’ve got multiple geographical user locations, located within the United States, or
in many different countries that are going to be impacted by the system. How do
you get to all those people, how do you train them appropriately? How do you train
them in their particular area, and in some cases in their language? Remember,
many of these people don’t have technical knowledge. Many of them might be
technophobes. How do you train them, so that they become comfortable with
change? Managing change, and getting people to accept change, is very difficult.
18. 18
F.W. Olin Graduate School of Business
Implementation and Go Live
• Load and validate production data
• Develop go-live checklist
• Implement new system and routines
• Stabilize environment
The last step in the process is to implement the system, and to go live. That requires you to load and
validate the production data. We talked earlier about the issues of mapping data, and cleansing data
and coming up with the tools to move the data from your old legacy systems to your new ERP
systems, and that’s all done in advance of going live. In fact, there’s certain static data that we can
move, from the old system to the new system, before we’re ready to go live. Things like customer
data or historical sales data can be moved from the old system to the new system, well in advance of
going live. However, there’s certain dynamic data, like accounts receivable information, or inventory
information which has to be loaded at the last minute. This is information that has to be accurate as
of last night, or just before you turn the system on. While you’ve done all the testing to make sure that
when you go to move the production data that it’s accurate, it has to be done once again, at the very
last minute. You have to develop your go-live check list, you have to implement the new systems and
routines, and make sure that they’re working, and that they’re working correctly, and you’ve got to
stabilize the environment. As you read the Cisco case, you’re going to see that that was one of the
problems that they had when they went live. Their environment wasn’t stabilized, and they had to do
some things to get those computers to have the proper response time. That’s one of the things that
all of these companies have to think about when they’re implementing an ERP system. You can have
all the functionality in the world, and this could be the best system in the world, but if you don’t have
the right kind of response time, if when you go to do an inquiry, or to enter a sales order, it takes five
minutes for the computer to come back to you with a response, that system doesn’t work. It doesn’t
work effectively, and it won’t get used well, so the technical environment must be stabilized so that
the system works appropriately.
19. 19
F.W. Olin Graduate School of Business
Issues in Implementing ERP Systems
Most ERP implementations today result in cost and schedule overruns
Source: Standish Group
The next part of our pre-brief deals with issues in implementing ERP systems, and
there are some interesting statistics that I wanted to share with you today. On the
left hand side of your screen is a pie chart, which has some rather telling
information about ERP implementation results. If you’ll notice, 35% of ERP system
implementations actually get cancelled. 55% of ERP implementations result in
overruns of one sort or another. And only 10% of ERP implementations are
delivered on time, on budget, and as planned. If you look at the chart on the right
hand side of the screen, you’ll notice that the average cost overrun is 178% of
budget. The average schedule overrun is 230% and in fact many systems see less
than 60% of the functionality that was originally planned at the beginning of the ERP
implementation. That should tell you, that for some reason, companies don’t have a
realistic view of what it takes to implement an ERP system. It takes much longer, it
costs much more, and you don’t always get, what you think you’re going to get,
when you started this initial odyssey.
20. 20
F.W. Olin Graduate School of Business
Common Barriers to Success
1. Focusing on technology
2. Ignoring the importance of requirements
definition
3. Jumping from the requirements definition
to the development phase
4. Not performing sufficient due diligence of
the vendor and the software package
5. Data conversion
6. Insufficient training
The most common mistakes of ERP implementations:
There are many mistakes that organizations make in implementing ERP systems. The six on this
slide are the most common ones. The first is focusing on technology. Technology companies
frequently try to push a silver bullet approach to solving problems however there is no evidence,
anywhere in the history of information technology that software alone will solve a business problem.
The second is ignoring the importance of requirements definition. Organizations too often ignore the
need to define an optimal process, and then use the technology as an enabler for that process. In too
many instances organizations try to either adopt a process that is inherent in the ERP solution even if
it doesn’t fit their business requirements, or they to shoehorn their legacy processes into a into a
software package that is not designed to support their processes. In both cases, they sub-optimize
the capabilities of the technology, and don’t take advantage of the opportunity to streamline their
business processes, which is the entire point of technology implementations. In some cases they
give up certain processes that are strategic for them, just because they think that the processes
within the ERP system can be implemented, faster than modifying the existing system. Frequently
they jump from the requirements definition to the development phase too soon. Pressed to deliver a
system against predefined time lines that don’t take into account all of the necessary implementation
steps, organizations frequently rush the process and they neglect to build a solid implementation
plan, and establish a solid agreement across the organization as to what it will take to develop and
implement the solution prior to implementing the technology. Because these systems are so
complex, it’s very important to perform sufficient due diligence of both the vendor, and the software
package before committing to it. This is not a simple process. You can interview the vendor, you can
go through demonstrations of the package, you can request to interview some of the vendor’s
customers although the vendor will certainly not tell you about those customers that have been
unsuccessful, but it’s important that the company perform it’s own due diligence of the package. They
need to get a demo version of the package, and test it to make sure that all of the basic functions that
are necessary for that company are contained within the package. Data conversion and training are
two step children that are not taken into consideration adequately when planning an ERP
implementation. It’s very important that the data elements be available and companies understand
how they’re going to go about cleansing those data elements, and converting them into the new
system, and how they’re going to train the organization to use this new system. Without adequate
training, this system will not work well.
21. 21
F.W. Olin Graduate School of Business
1. Focusing on technology
2. Ignoring the importance of requirements
definition
3. Jumping from the requirements definition
to the development phase
4. Not performing sufficient due diligence of
the vendor and the software package
5. Data conversion
6. Insufficient training
Common Barriers to Success
CULTURE
The most common mistakes of ERP implementations:
All of this translates into culture. How do you get the ERP system to capture the
culture of the organization, and how do you get the culture of the organization to
understand and adapt itself to the processes, and the changing needs of the
organization as a result of implementing this ERP system?
22. 22
F.W. Olin Graduate School of Business
ERP Disasters
• While there have been many successes in
ERP implementations, two well-publicized
problem stories include:
1. Hershey Foods: Click on Hershey to read
about the problems at Hershey.
2. Nestle SA: Click on Nestle to read about
the experience at Nestle.
While there have been many successes in ERP implementations there have also
been several high profile, well publicized disasters. Hershey Foods is an example of
one of them. Hershey Foods rushed their ERP implementation and as a result
missed shipping their merchandise during their busiest time of the year, which is
Halloween, resulting in Hershey Foods having to take a major hit against their
quarterly earnings. Nestle is another example of a troubled ERP implementation.
Click on the links on this page to read about both the Hershey, and the Nestle
problems.
23. 23
F.W. Olin Graduate School of Business
Additional Suggested Readings
• The ABCs of ERP
• The Return of Enterprise Solutions: The
Director’s Cut
• Faster, Cheaper ERP
• Getting ERP Deployments Right the First
Time Around
There are four articles that I’ve provided you here on this page, that provide
additional information about ERP systems. I encourage you to click on the links, and
read the articles, as they will supply you some additional information to better
understand both the implications of implementing it, and some of the results for
companies that have implemented ERP systems.
24. 24
F.W. Olin Graduate School of Business
Conclusion
In this lesson, we:
• described the functional modules in an ERP
system
• understood the process by which ERP
systems are implemented
• understood the issues that companies have
faced when implementing ERP systems
• provided background for analyzing the
experience encountered by Cisco in its
implementation of an ERP system
Let’s recap what we learned in this pre-brief. The first thing we did was we
described the history of ERP systems. We gained an understanding of the
functional modules within an ERP system. We gained an appreciation of the
integrated nature of an ERP system. Then we learned about the processes by
which ERP systems are implemented, the steps that are necessary, the implications
on the organizations, and what must be done to make it work right, and what are the
critical success factors, and the mistakes that are commonly made. Then we looked
at understanding the issues that companies have faced in implementing ERP
systems, and we gained an appreciation for what those are by looking at the
statistics of what percentages are canceled, and the cost overruns, and the time
overruns etc. Hopefully this pre-brief has provided some background for you, so that
you can better analyze the experience that was encountered by Cisco in its
implementation of its ERP system. While Cisco’s ERP implementation appears to
have been a major success that is not typical for most ERP implementations and
you should take that into consideration as you analyze the Cisco case. Thank You.