1. Information Systems Infrastructure (IS3314) 3 rd year BIS 2006 / 2007 Fergal Carton Business Information Systems

2. Last week Basic flows of information –Manufacturing (material availability, capacity) –Sales (revenue & customers) –Finance (cost & revenue targets, performance) Collaboration / conflict –Different views of the same data Sample Business Decisions (D 0 to D 6 ) Integration

3. This week ERP implementations Data issues with ERP implementations

4. A distribution view of systems Because we’re going on our merry way, making decisions, and we don’t realise that the information we are looking at is 2, 3 hours old. And it just causes havoc because people then physically go to do something and they’re like, what drives? The drives, they’re showing on the system, they should be right there! I tell ya, I just went out there, there’s nothing there! Wait a minute!

5. A manufacturing view of distribution The kind of thing that we would sometimes like them to do, would be, to take the product, that mightn’t be the easiest to work on, but if they were to wait one or two days, there might be a product coming through that might be more suitable.

6. Integration example: Bank branch Look at design and setup of bank branch –What does integration mean in a bank perspective? Customer services Customer data Transaction processing Data model How should usage increase of the lowest cost channel (internet), while complementing face to face services?

7. Deliver CustomerMakeSupplier Integration example: inventory Raw materials Finished goods Plan, buy Bill of materials

8. Integration example: factory

9. Parameters in ERP implementations Integration –Application –Services Standardisation –Business practices Centralisation –Decision making Control Acceleration –Information flows –Business process steps Cost reduction And the two levels at play are: Top management Users of ERP system: Managers at local level Operators HQ Local

10. The core of the problem This is how the system works This is how we do business This is how business and software will work together

11. ERP projects: resources required Users / power users User management Steering Committee Functional analysts Application expert DBA’s / Sys Admin Project team Process leads Project Managers Technical Project Business process

12. ERP projects: resources required Software vendor Hardware vendor Users / power users User management Steering Committee Functional analysts Application expert DBA’s / Sys Admin Project team Process leads Project Managers Systems Integrator Technical Project Business process

13. Resources : Financial Controller Having seconded the AP manager to the project for 18 months … –Just after go-live, lost the AP manager –Basic functionality missing Statutory reports for countries Unmatched receiver report arguments over Break-Fix vs. Enhancement –Lost understanding of why things were done in a certain way Knowledge of application Knowledge of business processes in the US –Worse: lost ability to get things fixed! Prioritisation of SIRs (System Investigation Requests) Reports written by end-users (eg. AP Manager) Local IS or global IS now working to gobal requirements Can’t customise the application

14. Resources : process Process lead Functional analyst Power users Application specialist Users …

15. Process issues … Ensuring key process issues are resolved Do we invoice customers on shipment or on delivery? Who should open the new accounting period for Purchasing? Receivables are coming through from a legacy system, but it’s impossible to identify the country of origin Sales orders being received in Euros are giving “Unrecognised currency” errors and halting the interface job Currency exchange rates updated during month and skewing month-end results, who should troubleshoot? Revenue from Professional Services is having to be manually shipped at month-end : no legacy system …

16. Resources : project Project Team Lead Process Leads Project Managers Functional Co-ordinators Steering Committee …

17. Project issues Availability of team members / users Decision making processes Developing workarounds Timeline too tight to allow resolution of issues Massive learning curve for team Expectation management Retaining ownership of process related decisions

18. Resources : Technical (data) Data clean-up team Data conversion team Data conversion programmer Legacy data team Data quality testing and maintenance …

19. PPARS project Governance Complexity –Job title –Responsibilities –No payscale –Bonuses –Overtime –Link roster to payroll? Resources Business process change, not system issue

20. Data issues … Getting and maintaining clean data –When creating a new customer, who has control? –42 occurrences of Siemens in your customer database, what do you do? –Customers exist in ERP core database, but also in several legacy systems. How do you make sure they are in synch? –…

21. Resources : Technical (IT ops) Database administrator Systems administrator Operators : core apps Server operators Storage technicians HelpDesk …

22. Database issues … Guaranteeing “high availability” How often should Test be refreshed? How many environments should I have –Test –Production –Development –Training –Business Simulation –… If I implement a change to Production, do I need to implement the same change across all environments? 20 programmers developing / testing new code every day: how do I track releases to production? …

23. Systems admin issues … Ensuring system access for users New users Changes to existing profiles System downtime for maintenance Forcing users out of system Tracking source of corrupt data to user profile …

24. HelpDesk issues … Calls arriving at HelpDesk are either : Forgotten password New user Changes to user profile Printing problems Connectivity problems Response time problems System crashes System error messages PC problems I need more training …

25. HelpDesk issues … …or : Functionality questions (how do I transact an invoice?) Process questions (when should I post to GL?) Reporting (I need a revenue report)

26. Project handover to HelpDesk Prior to go-live, implement procedures for : –Logging calls such that it will be routed to the right person and tracked, reported on and escalated –Training for HelpDesk to be able to ask the right questions concering an application issue –Troubleshooting application issues to be able to deal with simple “fixes” –Ongoing consultation with application team regarding new functionality being rolled out, common errors, planned outages, …