Posts Tagged ‘capacity’

Just when you thought it was safe to talk about Governance…

Monday, March 4th, 2013

Francis Fukuyama asks What is Governance?

Doug Hadden, VP Products

We’ve been building a governance framework that shows linkages between the use of technology, such as Government Resource Planning (GRP) systems, and Public Financial Management (PFM) processes to improving governance in government. Our President and CEO, Manuel Pietra, presented a draft of this framework to a class at the Harvard Kennedy School last week.

We recognize that there is no universal “governance” definition.

Now, Francis Fukuyama has entered the fray with What is Governance? published through the Center for Global Development. It’s an important work.

Fukuyama doesn’t pull any punches. He states up front: “points to the poor state of empirical measures of the quality of states, that is, executive branches and their bureaucracies.” He articulates the flaws from current thinking on governance.

Flaws in theory. In ideology. In the difficulty of measuring.

Fukuyama points out that “an authoritarian regime can be well governed, just as a democracy can be mal-administered.

What about those flaws?

Fukuyama focuses on examples where a governance rating can be misleading. But, he doesn’t show whether a rating such as the World Governance Indicator of Rule of Law has frequent exceptions to the rule.

It seems to me that many observers attempt to decompose governance into a limited set of measures and concepts. As Fukuyama attempts. But, perhaps, considering multiple governance measurements, can, in aggregate, provide an effective meta picture. Some flaws might be canceled out. At least, the exceptions could be easily exposed.

Capacity and Autonomy

Fukuyama does good work in presenting the impact of capacity and autonomy in government. He shows the interrelationship between these factors. The need for human capacity to achieve discretion. And, the potential reversal of governance effects through increased public service autonomy.

My sense is that the quality to autonomy and capacity relationship differs when applied to other governance stakeholders such as civil society, businesses and legislatures.

Nit-picking

Fukuyama suggests that Max Weber’s bureaucracy ideal of “officials subject to strict discipline and control” is “incompatible with civil service protection.” My sense is that “discipline and control” might relate to governance in a similar way as capacity and autonomy. Governments need to ensure that public servants operate to a budget, and therefore, to achieve fiscal discipline.

The notion of measuring ‘outputs’ as a governance measurement comes under fire by Fukuyama. He is concerned about the “tainting of output measures by exogenous factors” and the difficulty of measuring these outputs in the first. Yes, outputs and outcomes are notoriously hard to measure in government because there is not objective bottom line such as ‘profit’.

I think Fukuyama is confused about outputs and outcomes. Outputs, such as the number of vaccinations or the kilometers or roads built, can be easily measured. Outcomes are the problem. Yet, outputs can lead to better understanding outcomes and can help to determine what exogenous factors are at play.

5.3 FreeBalance Non Functional Technical Requirements

Sunday, June 28th, 2009

This is section 5.3 of a series of blog entries creating a Government IFMIS Technology Evaluation Guide. This includes information to assist in evaluating IFMIS options and the technology requirements for FreeBalance IFMIS implementations. These series will be combined with feedback to produce a comprehensive Technology Evaluation Guide to be published on our web site.

Non-Functional Requirements include reliability, availability, compatibility and performance. These are used for FreeBalance product requirements and are designed to match the range of government customer needs. Many of these requirements differ from needs in the private sector. The following is a summary of non-functional requirements used in the development and testing of the FreeBalance Accountability Platform and web-based applications.

Deployment

Deployment and installation of FreeBalance applications covers typical government needs including decentralization:

  • Centralized, decentralized and hybrid deployment.
  • Named, concurrent, occasional, site and government-wide licensing and licensing combinations.
  • Simplified license keys for rapid upgrading.
  • Use of test, training and production environments.
  • Version upgrades and downgrades.
  • Software as a Service (SaaS) and Cloud Computing deployment.
  • Government shared services deployment.
  • Support for low bandwidth setups such as dial-up and VSAT for remote government offices.
  • Optimized technical footprint to ensure that FreeBalance software can operate on a stand-alone laptop.
  • Ability to deploy to training centers, testing environments and disaster recovery sites.

Compatibility

Compatibility describes compatibility with industry and international government accounting standards. This ensures compatibility with a wide range of equipment and systems to protect the government investment. Compatibility requirements cover:

  • Portability to other operating systems, application servers, computer systems and databases.
  • Compatibility with JBoss, Tomcat, WebSphere and WebLogic application servers.
  • Compatibility with Microsoft, Oracle and MySQL databases.
  • Support for multiple web browsers including Mozilla and Microsoft and web standards like W3C and CSS.
  • Support for Microsoft and Linux operating systems.
  • Support for Web Services (SOAP, UDDI, WSDL).
  • Support for Unicode.
  • Support for security standards including LDAP, PKI, SSL, and Kerberos.
  • Support for IPSAS, GASB, IFRS, GaaP and GFS standards for public sector accounting.

Maintainability

Maintainability refers to the ability of governments to maintain software and the FreeBalance ability to support customers easily. The maintainability requirements cover:

  • Rapid deployment of code fixes and service packs.
  • Support for configurable system logging and auditing.
  • Parameterization for configuration and configuration changes.
  • Migration, upgrading and backward compatibility.
  • Systems management functionality and support for systems management standards like SNMP for 3rd party tools.
  • Archive and backup functionality.
  • Remote management capabilities.

Usability

Application usability and the user interface are key elements to ensure the successful implementation of a government financial management system. FreeBalance applications are sometimes used in countries with lower human capacity. Usability requirements cover:

  • User-centric design criteria to ensure simple functions oriented to the user’s objective, ease of use and ease of remembering.
  • Options for user interface changes and customization, including forms adjustment, translation, and templates.
  • Structure, skeleton, navigation and page layout standards for the user interface.
  • Use of expected web conventions.
  • Behavior for data input.
  • Localization and internationalization including multiple language and multiple calendar support.
  • Multi-lingual documentation and the ability to adapt documentation to meet government and capacity needs.
  • Support for linking help, documentation, courseware and e-learning together.

Reliability, Performance, Capacity and Quality

These requirements are designed to support government needs:

  • Availability of FreeBalance software, independent of network and server availability at better than 99.9% other than for scheduled maintenance and upgrading.
  • Scales well under load with high concurrency to over 10,000 users.
  • Fault tolerance for loss of connectivity, loss of computing resources and invalid data entry.
  • Recoverability to hardware, network or software faults including exception handling.
  • Software encryption and access control support.
  • Over 99.9% Data and transactional integrity. Tools that support transaction recreation from audit trail.

Introduction to the ICT for PFM Sustainability Blog

Monday, December 22nd, 2008

This blog explores sustainable Information and Communication Technology (ICT) for Public Financial Management (PFM). We explore proven techniques and technology from countries around the world, with a special focus on governments in Emerging Economies.

Governments have experienced mixed results when implementing ICT for PFM. FreeBalance customers have been very successful compared to industry averages.

We hope that we can share our practical experiences and market research to assist civil servants to optimize PFM systems, regardless of systems used.

What is Sustainability?

We are focusing on sustainability because we believe this to ne the most critical success factor. We define sustainability as:

  • Implemented successfully – on-time and on-budget and meets government objectives
  • Government control – civil servants manage entire system, not foreign consultants
  • Adapts to reform – meets needs for modernization including civil service reform
  • Lower cost of ownership – inexpensive to upgrade to new versions and support installed base
  • Rolls out across government – can be installed in line ministries and sub-national government organizations
  • Improves government outcomes – enables audit and performance management
  • Environmentally sustainable – minimizes the use of electricity and non-renewable resources
  • Sustainable fiscal program – provides effective tools for fiscal discipline including sustainable budgets

Explorations in Sustainability

We plan to explore important themes in sustainability:

  • Capacity building – what techniques effectively build civil service ICT and PFM capacity?
  • PFM sequencing – what PFM functionality has the most benefit at different stages of modernization? How do government needs and objectives change priorities?
  • Implementation good practices – how can PFM project be managed for optimal results?
  • Software maintenance – what software support, maintenance and upgrade methods are most effective? How should maintenance be priced? How can support be optimized
  • Build or buy – what PFM software should be developed in-house and what should be acquired off-the-shelf? Which option adapts best to change?
  • Open source – when should open source or commercial software be considered for government financial management? Which option has the lowest cost of ownership?
  • Cloud computing – how can governments leverage cloud computing and shared services to reduce costs and improve efficiency?
  • User interaction – how can software be designed to be easier to use and maintain?
  • Total Cost of Sustainability – how long term costs can be reduced.