Systems Integration


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Systems Integration

  1. 1. <ul><li>How is software best procured? </li></ul>
  2. 2. Custom Software <ul><li>Historically, built used & maintained in-house </li></ul><ul><li>Increasingly outsourced </li></ul><ul><li>Development risks & costs covered by one organisation </li></ul><ul><li>Software matched organisational needs </li></ul><ul><li>Transaction processing easily supported </li></ul><ul><li>Integrated systems difficult to develop </li></ul>
  3. 3. Packaged Software <ul><li>Use of packaged software is growing rapidly. </li></ul><ul><ul><li>Packages meet common business needs. </li></ul></ul><ul><ul><li>Transaction systems are similar across businesses </li></ul></ul><ul><ul><li>Traditionally focus on isolated business function(s). </li></ul></ul><ul><ul><li>Why reinvent the wheel! </li></ul></ul><ul><ul><li>Developed by third parties. </li></ul></ul><ul><li>Packaged applications may be based on best practice. </li></ul>
  4. 4. Issues related to packaged software vs custom software: <ul><li>Which will provide the most effective information system? </li></ul><ul><ul><li>Quality information for better decisions. </li></ul></ul><ul><ul><li>Competitive advantage in rapidly changing environment. </li></ul></ul><ul><li>Which will be the most efficient solution? </li></ul><ul><ul><li>Relates to the cost of creating, implementing, maintaining and operating the orgsnisation’s information system. </li></ul></ul>
  5. 5. Issues relating to purchase: <ul><li>Does the package match the user requirements? </li></ul><ul><li>How reliable is the supplier? </li></ul><ul><li>Is the developer a stable organisation? </li></ul><ul><li>Is the package stable or is it under constant revision? </li></ul><ul><li>How well does it integrate with other software/applications? </li></ul><ul><li>What support is available? </li></ul><ul><li>Are operations staff available? </li></ul>
  6. 6. Issues relating to Implementation and Support: <ul><li>Customisation </li></ul><ul><ul><li>Changes necessary to meet organisational requirements. </li></ul></ul><ul><li>Integration </li></ul><ul><ul><li>How well can they package share information with other systems. </li></ul></ul><ul><li>Upgrades </li></ul><ul><ul><li>How often is the software upgraded? </li></ul></ul><ul><ul><li>How is the upgrade affected by customisation and integration issues? </li></ul></ul>
  7. 7. Customisation includes: <ul><li>Configuration </li></ul><ul><ul><li>Assembling the purchased modules into a system. </li></ul></ul><ul><ul><li>Setting parameters in the package. </li></ul></ul><ul><ul><li>Adjusting user interfaces. </li></ul></ul><ul><ul><li>Integrating with other packages or systems. </li></ul></ul>
  8. 8. Customisation includes: <ul><li>Modification </li></ul><ul><ul><li>Changing the package code to alter existing processing. </li></ul></ul><ul><ul><li>This can cause serious problems when upgrading. </li></ul></ul><ul><ul><li>The vendor may not support modification. </li></ul></ul><ul><ul><li>Original code may be unavailable. </li></ul></ul>
  9. 9. Customisation includes: <ul><li>Enhancement </li></ul><ul><ul><li>Adding functionality to a package. </li></ul></ul><ul><ul><li>Does not alter the original package. </li></ul></ul>
  10. 10. Upgrading <ul><ul><li>Upgrading can be a serious problem if extensive work was required for customisation or integration. </li></ul></ul>
  11. 11. Integrating Packages <ul><li>Packages tend to work separately from one-another, but they need to either use, supply or share data with other systems. </li></ul><ul><li>Organisations try to set up data so that it is accessed in a standardised form in real time. </li></ul>
  12. 12. Non-Integrated Information System:
  13. 13. Integrated Information System:
  14. 14. ERP - Enterprise Resource Planning <ul><li>Using integrated application software to improve effectiveness and efficiency. </li></ul><ul><li>Functionality supplied provides 'Best Practice' </li></ul>
  15. 15. <ul><li>ERP integrates across the entire value chain </li></ul><ul><ul><li>Value chain = all processes that add value to a product or service. </li></ul></ul><ul><ul><li>Data is integrated across the organisation </li></ul></ul><ul><ul><li>Organisational units are integrated </li></ul></ul><ul><ul><li>Capability to integrate with customers & suppliers </li></ul></ul>
  16. 16. Advantages of integration include: <ul><li>Critical data is available for users in real time. </li></ul><ul><li>Integrates the entire value chain. </li></ul><ul><li>Integrates organisation across geographical boundaries. </li></ul><ul><li>Extends boundaries across different businesses. </li></ul><ul><li>ERP integrates TPS, MIS, DSS </li></ul>
  17. 17. Major ERP Vendors: <ul><li>SAP, Peoplesoft, Oracle, J.D.Edwards, Baan </li></ul><ul><ul><li>Originally supplied packages to support: </li></ul></ul><ul><ul><li>Finance, Manufacturing, Human Resources </li></ul></ul>
  18. 18. Vendor Offerings <ul><li>Offerings now include: </li></ul><ul><ul><li>Customer-relationship management </li></ul></ul><ul><ul><li>Supply-chain management </li></ul></ul><ul><ul><li>Sales-force automation </li></ul></ul><ul><ul><li>E-commerce </li></ul></ul><ul><ul><li>Business intelligence </li></ul></ul><ul><ul><li>Total quality management </li></ul></ul>
  19. 19. Customer Relationship management (CRM) <ul><li>The process of meeting the needs of customers from initial inquiry to after sales support. </li></ul>
  20. 20. Supply Chain management (SCM) <ul><li>Managing all resources and processes involved from raw material acquisition to finished goods delivery. </li></ul>
  21. 21. Sales-force automation <ul><li>Processes that make it easier for sales personnel to service customer accounts. </li></ul>
  22. 22. E-commerce <ul><li>The buying and selling of goods and services on the internet (especially the World Wide Web). </li></ul>
  23. 23. Business intelligence <ul><li>The acquisition and use of information designed to improve competitive advantage. </li></ul>
  24. 24. Total quality management (TQM) <ul><li>The process of achieving the highest levels of quality throughout the entire organisation. </li></ul>
  25. 25. The Changing Business Environment <ul><li>Mergers </li></ul><ul><li>Government deregulation </li></ul><ul><li>Globalization </li></ul><ul><li>Business process reengineering </li></ul>
  26. 26. IT Trends <ul><li>Client-server technology </li></ul><ul><li>Object-orientation </li></ul><ul><li>Telecomunications </li></ul><ul><li>Internet </li></ul>
  27. 27. Questions <ul><li>How can custom built legacy systems keep up? </li></ul><ul><li>Can an organisation maintain staff that are expert in so many areas? </li></ul><ul><li>How can an organisation reorganise itself within the limits imposed by legacy software? </li></ul>
  28. 28. Benefits of ERP Systems <ul><li>The adoption of ERP products appears to resolve these problems. </li></ul><ul><li>Reduces workforce in core transaction processing systems by eliminating manual tasks and duplication. </li></ul><ul><li>Supports global business operations. </li></ul><ul><li>Economies of scale achieved by replacing division level systems with corporate level systems </li></ul>
  29. 29. Benefits con’t <ul><li>Reduction of information systems development staff by using packages </li></ul><ul><li>Improves customer service through better logistics based on more complete & accessible information. </li></ul><ul><li>Data integrity is improved through a common database. </li></ul><ul><li>Decision support is improved through more timely reports and better drill down capabilities. </li></ul>
  30. 30. Costs of ERP: <ul><li>$800,000 for a midsize firm ($400k - $2 billion annual sales) </li></ul><ul><li>$3-8,000,000 for a large corporation ($2 billion +) </li></ul><ul><li>Consulting fees may be high due to shortage of staff. </li></ul><ul><li>Payback expected in 6 – 30 months. </li></ul>
  31. 31. ERP Implementations : <ul><li>They are complex, </li></ul><ul><li>They affect the entire organisation </li></ul>
  32. 32. Critical Success Factors: <ul><li>Top management support, an effective & respected champion </li></ul><ul><li>Centralised project management with a business leader in charge (not an IT leader) </li></ul><ul><li>Strong IT management & staff support </li></ul><ul><li>Heavy user involvement in project management & implementation </li></ul><ul><li>BPR to standardise on the software rather than customise the software to match the business. </li></ul><ul><li>Retrain existing IT staff in ERP implementation and maintenance. </li></ul>
  33. 33. CSF’s con’t <ul><li>Use of consultants to lead in implementation & training </li></ul><ul><li>Top-notch analysts with excellent business knowledge and excellent technical skills. Retraining of these analysts throughout the project & beyond. </li></ul><ul><li>Effective & continuous communication among all parties. Sensitivity to user resistance to new systems. Extensive training of end users. </li></ul>
  34. 34. What does this all mean to current students in IS??
  35. 35. Approaches to ERP implementation: Comprehensive Package Fully integrated Some particular needs may not be supported Lack flexibility to rapid change
  36. 36. Best-of-breed Best software chosen for each application Integrate all the applications Often the packages don’t integrate well Middleware (and a skilled systems integrator) used to reduce integration problems
  37. 37. Hybrid Some packages purchased due to desirable functions Comprehensive system provides ‘backbone’ for rest of the system. Reduces problems of integration yet allows customisation in key areas.
  38. 38. Selecting a Comprehensive ERP package
  39. 39. <ul><li>Preliminary evaluation: </li></ul><ul><ul><li>Is critical functionality available? </li></ul></ul><ul><ul><li>The up-front costs of the package. </li></ul></ul><ul><ul><li>The cost of ongoing support, upgrades and add ons </li></ul></ul><ul><ul><li>Viability of the vendor. </li></ul></ul>
  40. 40. <ul><li>Preliminary Evaluation: (cont) </li></ul><ul><ul><li>The fit between the business model of the package and the current processes of the organisation. </li></ul></ul><ul><ul><li>Proven success in the business environment </li></ul></ul><ul><ul><li>Availability of customisation tools. </li></ul></ul><ul><ul><li>Accommodation for the organisation’s management style. </li></ul></ul>
  41. 41. Detailed Evaluation <ul><ul><li>Lower-level managers </li></ul></ul><ul><ul><li>Operating personnel </li></ul></ul>
  42. 42. On-Site Visits <ul><ul><li>Sites using the package are visited </li></ul></ul><ul><ul><li>Sites identified through own reseaches </li></ul></ul><ul><ul><li>Quality of support performance and reliability are determined </li></ul></ul><ul><ul><li>Customisation difficulty studied </li></ul></ul><ul><ul><li>Hardware, software and implementation times are studied </li></ul></ul>
  43. 43. Final Decisions <ul><li>Criteria determined </li></ul><ul><li>Weighting assigned </li></ul><ul><li>Total score for each product is determined </li></ul><ul><li>Any serious faults are noted and may disqualify product </li></ul><ul><li>Consensus must be achieved with final decision. </li></ul>
  44. 44. Systems Development in an ERP Environment <ul><li>Large projects need to be well organised to be successful </li></ul>
  45. 45. Organisational Structure for ERP projects <ul><li>Scan image Pg 16 & insert here </li></ul>
  46. 46. Roles <ul><li>Oversight committee </li></ul><ul><ul><li>Monitor project </li></ul></ul><ul><ul><li>Make key recommendations </li></ul></ul><ul><ul><li>Representative of all users </li></ul></ul><ul><li>Project Teams & workgroups formed. </li></ul><ul><ul><li>Teams assigned to different development areas </li></ul></ul><ul><ul><li>Vendor representatives </li></ul></ul><ul><li>Administrative support provided </li></ul>
  47. 47. Phases of development <ul><li>Two key factors affect development </li></ul><ul><ul><li>The scope is very large </li></ul></ul><ul><ul><li>Packaged software is used extensively </li></ul></ul>
  48. 48. Planning <ul><ul><li>Oversight committee is formed </li></ul></ul><ul><ul><li>Project team formed </li></ul></ul><ul><ul><li>General purpose and scope determined </li></ul></ul><ul><ul><li>Alternative approaches to ERP evaluated </li></ul></ul><ul><ul><li>Initial selection made </li></ul></ul><ul><ul><li>Determine how the project is to proceed </li></ul></ul><ul><ul><li>Budgets, feasibility, project schedule </li></ul></ul>
  49. 49. Analysis <ul><li>Work Groups formed, Requirements determined </li></ul><ul><li>Evaluation of vendors </li></ul><ul><li>Business process engineering requirements identified </li></ul><ul><li>Vendors selected, but not finalised </li></ul><ul><li>Prototypes developed to demonstrate integration </li></ul><ul><li>Alternatives reconsidered & re-evaluated </li></ul><ul><li>Recommendations presented to Oversight Committee </li></ul>
  50. 50. <ul><li>Question: </li></ul><ul><li>Will the analysis phase be longer or shorter than that for the custom development approach? </li></ul>
  51. 51. Design <ul><li>Varies considerably depending on approach taken </li></ul><ul><li>Interface design varies according to the amount of customisation required </li></ul><ul><li>Hardware and networks must be designed to support packages </li></ul><ul><li>Training of end-users </li></ul><ul><li>BPR performed, new procedures and job descriptions prepared </li></ul>
  52. 52. Implementation <ul><li>Configuration of modules </li></ul><ul><li>Integration of packages </li></ul><ul><li>Prototype created and evaluated until production ready </li></ul><ul><li>System is verified, tested & tuned </li></ul><ul><li>System documentation completed </li></ul>
  53. 53. <ul><li>User training completed </li></ul><ul><li>New system installed with rollout plan developed during design </li></ul><ul><li>Organisational structures changed, personnel placed in new positions </li></ul><ul><li>New procedures implemented </li></ul>Implementation (cont)
  54. 54. Support <ul><li>Continued training & support </li></ul><ul><li>Well managed Help Desk </li></ul><ul><li>Adaptive & corrective maintenance </li></ul>
  55. 55. <ul><li>Future additions: </li></ul><ul><li>Evaluation of ERP systems </li></ul><ul><li>SAP R/3 </li></ul>