1 / 7

Implementing Financial Management Information System Projects: Selected Lessons from IFMIS Community of Practice

Implementing Financial Management Information System Projects: Selected Lessons from IFMIS Community of Practice. Bill Dorotinsky. October 15, 2008. Outline. Origins and some basic findings Formalizing a FMIS maturity model A frequent question - Make vs. Buy.

fairfax
Download Presentation

Implementing Financial Management Information System Projects: Selected Lessons from IFMIS Community of Practice

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. Implementing Financial Management Information System Projects:Selected Lessons from IFMIS Community of Practice Bill Dorotinsky October 15, 2008

  2. Outline • Origins and some basic findings • Formalizing a FMIS maturity model • A frequent question - Make vs. Buy

  3. COP Origins:Bank FMIS Project Review • The review covered 34 projects in 27 countries across 6 regions, involving $1 billion over 17 years • Most Bank projects were not FMIS-only, but embedded in broader financial management or public sector reforms • Many of the projects paid attention to training and ‘soft systems’ surrounding the technology, including FM training, change management training/advice • An FMIS project, on average, • took 7 years to be complete • Ranging from 9.1 years for Africa to 5.8 years for Latin America/Caribbean • average Bank-financed cost was $12.3 million* • component changes in 75 % of projects * Excluding $600 million for Russia

  4. Risks, success & failure factors • Projects risks • 20 % cited technical complexity, too many components • 24 % lack of institutional capacity • 21 % weak government commitment • Success factors • Full-time project coordinator (36%) • Champion at political level (14 %) • Training (14 %) (IT, FM, change management) • Failure factors • Full-time project coordinator (23%) • Commitment (23%) • Project design (20%)

  5. Preconditions for success? HR Capacity, ICT Readiness, & Project Success Burkina Faso L 0.9 Argentina S Malawi L 0.8 0.7 Hungary S 0.6 Uganda L 0.5 0.4 0.3 Chile S Bolivia L 0.2 0.1 0 Columbia S Indonesia L Ecuador (2) S Brazil L Honduras S Guatemala (1) S Nicaragua S Human Development Index* E-gov Readiness* (Human Development Index: UNDP Human Development 2001 Index, E-government Readiness: UNPAN Global E-Government Index)

  6. Maintenance and Support 7 Implementation 5 • Budget funds • Technical capacity • System administration • Maintenance • System development & integration • Full scale testing and rollout • Training and change management Procurement 4 • Large scale ICT systems • Technical Assistance and Training 18 – 36 months PFMS Design 3 9 – 18 months • Definition of system functionality • Detailed technical requirements Monitoring & Evaluation 6 Preparation • Monitoring mechanisms • Project mgmt capacity 2 • Legal and institutional frameworks • Budget coverage • Treasury Single Account (TSA) 9 – 18 months Readiness 1 • PFM reform strategy • Institutional capacity • Countrywide network infrastructure Treasury/PFMS Maturity Framework Effectiveness Time Maturity Framework for Treasury/PFMS projects www.pempal.org/pfmstool interactive monitoring and management of MF indicators Resources February 2008 ECA Treasury / PFMS Projects 6

  7. Make vs. Buy Question:Selected Parameters • Development Period • Functionality • Compliance with BPR • Total Cost of Ownership (TCO) • Intellectual Property Rights (IPR) • Maintenance and Upgrades • Flexibility • Integration with other systems and modules • Performance and Quality • Documentation and Training • Software Evaluation • Legal Redress Conclusion – no one right answer.

More Related