1 / 18

Building Municipal Collaboration

Building Municipal Collaboration. ERP Roadmap Update ECRUG 2010 Conference Mississauga, Ontario International Centre Monday, June 21st 10:15am. Agenda. ERP Roadmap Journey Activities and Accomplishments Project Update: 3 rd -party ERP Support Feasibility Study

yoshino
Download Presentation

Building Municipal Collaboration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Building Municipal Collaboration ERP Roadmap Update ECRUG 2010 Conference Mississauga, Ontario International Centre Monday, June 21st 10:15am

  2. Agenda ERP Roadmap Journey Activities and Accomplishments Project Update: 3rd-party ERP Support Feasibility Study Moving Forward – Developing Collaboration Building on the MISA Strategy Next Steps

  3. The ERP Roadmap Journey • Common Projects • Collaboration Forum • “OMCI” Municipal Collaboration VendorDiscussions VendorRelationship Management • Renewed Discussions • Options Identified • ERP Vendor Talks • Alternate Service • Province of Ontario • Initiatives ERP Options RFI • Vendor Options • ERP TVO/TCO ERP Framework • Vendor Concerns • Deloitte Framework We Are Here ERP Day 2 • Vendor Presentations • ERP TVO/TCO ERP Day 1 • Vendor Presentations • Where is the Value? 2005 2006 2007 2008 2009 2010

  4. The Need for Change – Beginning the Journey • Application support costs and maintenance fees make up for majority of the TCO Costs and are forecasted to increase over the next 5 years • Overall, no direct correlation between thresholds (budget/ employee) and the license or maintenance fees • The lowest/highest fee structures are not necessarily by smallest/largest municipality • Municipalities are paying for On-shelf Modules with no annual benefits in return • Original ERP expectations have not generally been realized • Primary concerns were to mitigate Y2K risks and de-commission legacy systems • CIO’s often challenged to justify ever-increasing TCO of ERP. * (Taken from the TCO Findings of the Developing an ERP Roadmap for Municipalities Report)

  5. Engaging the Vendors – 11 Item Action Plan Map maintenance levels to market realities: • Develop an Industry based Pricing Model for License and Maintenance contracts • Develop a Bulk Purchase Model for software products • Develop a Shared service delivery model for municipalities to evaluate • Develop a framework to allow License exchange – module for module • Develop a framework to direct a portion of maintenance to develop required features and products • Develop a framework to drop unused modules to reduce maintenance costs • Develop a framework to reinstate products that had been dropped from maintenance

  6. Engaging the Vendors - 11 Item Action Plan Develop mechanisms for building value: • Increase training options for Canadian clients • Develop implementation tools/scripts to reduce delivery time for modules and functions • Pre-built configuration examples • Scripted configuration for basic implementations of functions and workflows • Develop extended solutions along business processes • Work with clients to design solutions to common problems (e.g. PSAB) • Leverage core and partner systems to build integrated processes • Establish a collaboration environment for exchange of customizations, knowledge • Open forum to trade customizations, reports and bolt-on’s • Non-supported, but adopted functions licensed for all

  7. 3rd-Party Maintenance Feasibility Study Objective: Analyze options for employing 3rd-party services for ERP application support Identify potential risks and opportunities Demonstrate feasibility to freeze existing version Assess cost savings to finance future investment in alternate product and/or service delivery model Summary of Findings: The risks associated with pursuing the use of a 3rd party to provide PeopleSoft, or other ERP, maintenance and support are considered high. Vulnerability of 3rd party support vendors to legal action from the ERP vendors As demonstrated by the recent law suit filed by Oracle against Rimini Street The financial benefits from this approach do not seem to be of sufficient magnitude to outweigh that risk Supported by TCO Cost Model developed using York Region data

  8. Change the Value Equation by Reducing the Value Gap. Therefore there are 2 paths to improving the net value: Reduce the cost Increase the business value * Please note that no attempt was made during the course of this project to quantify the business value currently being received. The focus was on how the options under consideration might have an impact on Net Value. Info-Tech Research Group 7

  9. Reduce Costs and Increase Value Info-Tech Research Group 8

  10. Cost Management Strategies • Pursue options to enable dropping unused modules from Support and Maintenance contracts: • Contracts are vague on the option • Penalties may include repurchasing the modules and pay back maintenance or re-pricing remaining modules • Assess contracts; consider legal arbitration • Negotiate with Vendor: • Find a “win-win” approach; leverage new acquisition • Contract migration strategies; Amendment options • Find a the right connections in the Vendor Hierarchy • Oracle businesses separated by major product lines and managed in a North American pricing structure • Difficult to leverage acquisitions across product lines Info-Tech Research Group 9

  11. Cost Management Strategies • Investigate alternate product lines • Previous Tier II products may meet current needs • Vendors have been closing the functionality gaps • Leverage best-of-breed applications • Investigate opportunities to collaborate: • Joint projects on new initiatives • Shared-Service ventures • Key option that demonstrated high ROI in strategic options Info-Tech Research Group 10

  12. ERP Roadmap Taskforce Accomplishments • Deloitte Study: Developing and ERP Roadmap for Municipalities • Report and Executive Summary for ERP Investments • Decision Tools: Total Cost Assessment; Value Assessment; Strategic Option Assessment • RFI for Common Business Systems • Evaluated key product offerings for 26 Business Application areas • Survey of Municipalities – 3 year IT Programs • Inventory of IT project portfolios for 3 year outlook • Identified potential areas of collaboration • 3rd-Party ERP Maintenance Feasibility Study • Evaluated the viability and risks associated with 3rd-party offerings • Decision Tool: Total Cost Assessment for ERP Strategic Options * Documents available on the MISA Sharepoint Site – under the Municipal Members section: ERP Roadmap

  13. Moving Forward: Developing Collaboration Municipal Collaboration VendorDiscussions VendorRelationship Management Moving Forward ERP Options RFI ERP Framework ERP Day 2 ERP Day 1 2005 2006 2007 2008 2009 2010 • Refocus on Collaborative Initiatives • Develop Value through leveraging common processes and systems • Develop common projects of interest • Pursue vendor partnerships for projects and initiatives

  14. Moving Forward: Developing Collaboration ERP Roadmap Taskforce has enabled municipalities to take a fresh look at their IT investments Developed tools for comparing and evaluating costs Investigated product options in the municipal space Evaluating strategic options for enterprise applications Assessed the risks and costs of alternatives Identified common IT priorities and projects Key accomplishment has been to demonstrate the need and willingness for municipalities to collaborate on common interests

  15. Common Collaborative Initiatives Key Municipal Initiatives for potential collaboration: Enterprise Architecture Asset Management Disaster Recovery/Business Continuity Content Management/Information Management Financial Capital Management Human Capital Management Reporting/Business Intelligence Security/Privacy

  16. Building on the MISA Strategy Collaboration opportunities extend beyond the scope of the ERP Taskforce To develop effectively, the push for collaboration must be led from the MISA organization The new MISA Strategic Plan already contains the key elements for developing collaboration: Focused leadership – the creation of a full-time Executive Director Active Projects – call for projects in 2010 Forum for Members – building communities of interest

  17. “Ontario Municipal Collaboration Initiative” Similar to OMBI; Focused on Collaboration Imagine the Possibilities of OMCI for municipalities A ‘Purchasing Co-operative’ to maximize incentives and benefits. Shared or ‘templated’ configuration and implementation Standard volume discounts on software Simple Hosting Service to peer organizations Hosted and Managed services Evolution toward an OMCI: Initiate among 2-3 municipal partners Expand scope over time as a full service offering of MISA through OMCI

  18. Next Steps Engage the MISA Board to take on the collaboration initiative Develop an ERP Community of Interest Ad Hoc Activities for ERP Taskforce: Continue to exchange information on products and projects Provide support during procurement and vendor negotiations Continue to lobby vendors for changes in license and support models Continue to explore shared service opportunities

More Related