2 MAIN WORKFLOW AND
SYSTEM DESCRIPTION
From a simple point of view, the system takes a
comment (it may be a complaint or a suggestion)
which is sent to the Town Council through the Web.
It is processed, some times automatically, some
times manually, and then, the comment is taken into
account.
Due to this workflow model, the system is
completely described in a comprehensible way to all
the people involved in the development of the final
system: civil servant, analysts and developers.
Figure 1 shows the complete chart of the main
process in blocks. Obviously, the process is not as
simple and it will be described in the following
sections, block by block.
In concrete, these blocks are: (1) complaint or
suggestion arrival, (2) validation of comments, (3)
invalid comment workflow, (4) valid comment
workflow, and (5) complaints control time.
Complaint or suggestion arrival block describes
the arrival of a comment to the system, just before
starting the real process.
Then a validation process about the content of
the comment is necessary to filter only constructive
messages. This is the validation comment block. An
intelligent agent, the Semi-automatic Garbage
Content agent, classifies comments as valid or
invalid; then, a particular user of the system decides
what to do with the comments, or they even can be
automatically eliminated.
Invalid comment workflow block shows the way
in which an invalid comment is eliminated from the
system.
Valid comment workflow block shows the logical
steps followed for a valid comment. In this block
there are two more intelligent agents: the first one –
the Unit Assignment agent - recommends a re-
assignment of a comment to a Unit Responsible
(zero, one or more units, as described later on), but
the main responsible of the system would have the
last word; and the second one – the Comment
Classification agent - classifies comments
semantically according to a valid vocabulary for the
administrative unit.
The last block, complaints control time,
describes two threshold times in the system.
The workflow has been modelled by means of
basic flow charts using MS Visio and the application
is a work in progress which is being developed using
PHP technology. This basic flow chart has been
extended with a new figure to support intelligent
agent modelling.
For a better understanding of the system, we
include this subsection to briefly describe both the
necessary roles and the comment marks, which will
be mentioned later on.
A user in the system accessing to the Web
without authentication, that is to say, with the
default user, is considered to be a Citizen. This is a
public role. Neither a user nor a password is required
to access the system as a Citizen. Complaints and
suggestions could be sent through the system, but we
have considered that a valid e-mail is essential for
providing responses to the citizens. Any user with
another role needs to be authenticated in the system.
A Reception Responsible user receives all the
comments (complaints and suggestions) and he may
personally answer to the comments or assign them to
Unit Responsible users, assisted by the two
mentioned intelligent agents, the Unit Assignment
agent and the Comment Classification agent.
The
Unit Responsible user is usually a civil
servant in an administrative unit. Such a user only
receives assigned comments from the Reception
Responsible and he must answer in time.
There is a final role in the system, the General
Administrator. This user is in charge of creating,
modifying and deleting users.
And on the other hand, a series of comment
marks have been created so that users and
administrators can follow the process of any
comment: (1) Kind, an initial classification of the
comments –might be a complaint or a suggestion;
(2) Received, the comment has been received and
saved in the system and may be processed; (3)
Invalid, a rude, insulting, offensive or non
constructive comment, which will not be accepted in
the system; (4) Analyzed and Valid, if the content
analyzed is accepted; (5) Threshold, when a timely
warning threshold has been overcome; (6) Timeout,
when a final time-based threshold has been
exceeded; (7) Assigned, if the Reception Responsible
has re-addressed the comment to a Unit Responsible;
(8) Answered, for the case of a complaint that has
been answered; and finally, (9) Filed, when the
process is fully accomplished.
3 COMPLAINT OR SUGGESTION
ARRIVAL
Complaint or suggestion arrival comprises the time
range from the moment when a user enters a
comment in the system up to the logical bifurcation -
complaint or suggestion-.
ICEIS 2008 - International Conference on Enterprise Information Systems
310