Professional Documents
Culture Documents
5. Beyond ERP 6. IT Infrastructure 7. Data & Analytics 8. SDLC & Agile Assignment 3
12. Wrap-Up
Business Information Systems
Issues Issues Issues
What will we cover today?
Slide
ERPs basics
What? Why? How?
What are ERPs?
5
Why ERPs?
6
Are there different types of ERPs?
Local and internally hosted ERP (1990-2010) ‘In Cloud’ ERP (2010 onwards)
Organisation buys their own copy of an ERP product and hosts and ERP solutions are hosted in Cloud environments
maintains it themselves
Full ERP, all modules without the management overhead
Supports key business functions:
Vendor: patches, upgrades, administers, secures platform
Corporate: Finance/ Accounting, warehousing/ inventory
management Software as a Service (SaaS) products
Operations: Manufacturing production, Retail, Subscription/ leasing modelCompanies often running hybrid ERP
solutions: on-premise and in-cloud
Still going abd vendors continue to produce
For the purposes of illustrating two different types of ERP solutions i.e., On-premise, internally
hosted vs. Cloud based ERP
11
12
Oracle
SAP
Infor
Microsoft
Sage
..,.
https://www.forbes.com/sites/louiscolumbus/2014/05/12/gartners-erp-market-share-update-shows-the-
future-of-cloud-erp-is-now/?sh=81711591fae9
14
Expensive - one of the key limitations of Enterprise Resource Planning (ERP) systems is that they
can be extremely costly to buy and maintain\
ERPs were internally hosted and organisations had to build teams of people to administer and
maintain their ERP systems
ERPs added to the diversity of organisational application portfolios and were difficult to integrate
with existing systems
Critical functions were supported by ERPs and organisations had to invest in adding additional
data and infrastructure security, data storage and disaster recovery planning
17
Some organisations customized their ERP to meet existing business processes and rules
Sometimes these customizations were so extensive they voided vendor and product warranties
or made vendor patches and upgrades unworkable
In some extreme cases, organisations re-wrote the source code and tried to make their ERP do
what is was NOT natively designed to do
HR systems became student administration!
Financial systems became data analytics platforms
Learning Curve - it was difficult for organisations to become proficient and self-reliant in the use
of their ERP systems
Implementation Times – the time it took organisations to implement their ERPs could be 18
months – 2/3 years resulting in a lot of waste and missed business opportunities
Business were not ready for ERP - inter-connectivity between various departments in an
organization was a key driver, but if there were inefficiencies in one department this lead to
inefficiencies in other departments
19
Business also had issues on what to do with the data and the add-on platforms/ applications –
like data warehouses, data marts, data analytics tools, data cleansing processes and tools that
were used to support data analytics
Legacy ERP Solutions were very difficult to scale and integrate with more modern applications
and platforms
Merger and acquisition activities also become very difficult i.e, integrating new businesses or
decouple existing businesses
23
Earlt ERPs were difficult to integrate with other business applications and platforms and could
not give organisations end-to-end views of their business processes
Quote-to-Cash (QTC)
Order-to-Cash (OTC)
Procure-to-Pay (P2P)
Organisations now want a 360-degree end-to-end view of the customer journey for key processes
…
Want to have visibility of process bottlenecks, points where processes are falling over
Goes from beginning of the customer interaction, to the very end and delivers a product/service
to a customer.
Example is Order-to-Cash: “is the entirety of a company’s order processing system. It begins the
moment a customer places an order. Everything before that time is related to some function of
branding, marketing, or sales. It’s important to note, however, that branding, marketing, and
sales functions do not immediately cease when a customer places an order”
The contract systems is linked quotation systems, linked to ordering linked to product,
purchasing, payments, scheduling, transport, customer service and complaints systems
ERPs need to connect: Contract systems, quotation systems, ordering, product, purchasing,
payments, scheduling, transport, customer service, complaints and customer communications
systems
https://www.salesforce.com/products/cpq/resources/what-to-know-about-order-to-cash-process
Customer
Scenario: An end
customer of Company A
orders directly from
Company A.
Customer
2 Generation
nd
Purpose, parts and problems
27
ERP products have now standardised around the three cloud services providers
AWS, Azure or SAP (e.g., Salesforce hosted on Azure)
Organisations purchase a cloud instance of an ERP and arrange with vendor to host on AWS,
Azure, SAP DC
Maturity and greater connectivity within cloud environments supports greater connectivity to a
range of different ERP solutions
API connections
SAP and Salesforce and scheduling applications
SAP and data analytics platforms – Power BI, Business Objects
32
Customer
Customer
Representative
Azure
SAP D/C
SAP Commerce (Retail Front End)
SAP C4C (interrnal Portal)
API
Response
Customers Orders Payments Invoicing Inventory Delivery Service call
Customer Account
Comms Inventory Marketing
Service Mgt Analysts
API
Call
AWS
Response
Response
Call
We covered…
Enterprize Resource Planning (ERP) systems are and why you need to know about them
Why ERPs emerged and became so embedded as organisational information systems
The 2 generations of ERPs in terms of strengths and weaknesses
Explored what is coming next with ERPs and what that means for business, and you
What next?
Assignment 1 – Stay tuned for results
Assignment 2 – Submission is coming!
Slide
Thanks.
Questions