27.06.2013 Views

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Multi-Scope Evaluation of Public Administration Initiatives<br />

in Process Automation<br />

Luigi Lavazza<br />

Università degli Studi dell’Insubria, Varese, Italy<br />

luigi.lavazza@uninsubria.it<br />

Abstract: Public administrations are among the most active organizations in promoting process automation<br />

based on software systems. For evident reasons, public administrations are interested in evaluating the<br />

effectiveness of their process automation initiatives. However, when performing these evaluations, public<br />

administrations have to deal with a specific characteristic of their environment: the scope of the assessment can<br />

be more or less wide, i.e., it can extend beyond the boundaries of the public administration, to include the<br />

companies, organizations, citizens, suppliers, etc. that directly or indirectly interact with the processes. In fact, the<br />

effectiveness of a process initiative does not concern only the public administration that is promoting it, but<br />

involves all the stakeholders that, to various extents, participate in the process. Although traditional methods for<br />

measurement planning <strong>and</strong> execution – like the GQM (Goal/Question/Metrics) – can be used, evaluators have to<br />

define specific means to deal with the multiplicity of scope definitions that can be chosen in order to define the<br />

boundaries of the assessment. In this paper we illustrate the usage of the GQM to define measurement plans <strong>and</strong><br />

how to update them in order to deal with extended scopes. The proposed technique is illustrated through two<br />

case studies, taken from actual evaluations in which the author was involved. The presented evaluation approach<br />

is more effective than traditional econometric methodologies. On the one h<strong>and</strong>, it lets the evaluator choose the<br />

set of indicators that are more suitable for the purpose; on the other h<strong>and</strong> it goes beyond the traditional economic<br />

<strong>and</strong> financial indicators, extending the analysis to factors that allow a more comprehensive underst<strong>and</strong>ing of the<br />

effects of process automation.<br />

Keywords: software process measurement, process evaluation, evaluation scope, Goal/Question/Metrics (GQM)<br />

1. Introduction<br />

Public administrations (PAs) are interested in process automation because of several reasons: to<br />

increase internal efficiency; to favor citizens in accessing the services provided by the PA; to enhance<br />

or make more efficient business activities, not necessarily involving the PA (in this case the process<br />

automation services are seen as infrastructures). Whatever the type of process automation initiatives<br />

carried out by a PA, several actors <strong>and</strong> stakeholders are generally involved, because of the very<br />

nature of PAs. In fact, a PA is generally involved in providing services to the citizens, to suppliers, to<br />

companies, to other PA entities, to no-profit organizations, etc. While automating its services, the PA<br />

affects not only its internal processes, but also the ones of the citizens, suppliers <strong>and</strong> external entities<br />

that use (sometimes indirectly) these services.<br />

In general, a PA needs to evaluate the efficiency of its services. This is of course due to the fact that<br />

the provided services are paid with the citizens’ money (via taxes): the PA has to show citizens (<strong>and</strong><br />

electors) that their money is well spent. The need for evaluation is even more pressing when new<br />

initiatives are undertaken: in fact the success of the initiative has to be proved, <strong>and</strong> weak points <strong>and</strong><br />

problems have to be identified in order to be tackled <strong>and</strong> corrected. When evaluations of process<br />

automation initiatives are decided, the multiplicity of scopes emerges as a variable to be duly taken<br />

into account. In fact, by definition, an evaluation makes reference to a scope. In our case, the effects<br />

of the process automation initiatives are perceived at various levels: the PA itself, the companies <strong>and</strong><br />

citizens that directly interact with the PA, the citizens that are the targets of the final effects of the<br />

process.<br />

For instance, in a process for procuring educational material, the PA is the procurer, a company is the<br />

supplier, a set of schools are the immediate beneficiary, <strong>and</strong> the pupils are the final beneficiaries. As<br />

a consequence, the evaluation can be performed at various levels: one can take into account the<br />

effects for the PA, the effects for the company, the effects for the school, the final consequences for<br />

citizens (pupils <strong>and</strong> their families).<br />

It is quite clear that the sets of issues that are of interest for the various actors <strong>and</strong> stakeholders are<br />

disjoint. For instance, the citizen will be interested in the cost <strong>and</strong> quality of the supply, while the<br />

supplier will be interested also in the duration <strong>and</strong> the profitability of the supply process.<br />

294

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!