Information and Knowledge Management using ArcGIS ModelBuilder

Michal Pivnička
strategy and the BSC because the Strategy Map presents causal relationships between objectives,
from which measures can be derived.
Figure 1: The balanced scorecard and its role in strategic management (Kaplan 2004)
3. Oracle balanced scorecard
It is clear that the implementation of the BSC in a business is no simple matter. Especially in relation
to large companies, proper use of the BSC as a strategic tool cannot proceed without the support of a
good quality information system. Without this, it is almost impossible that all information would be
received on time, placed in the right hands, and in the correct form. The practical application of the
Balanced Scorecard in Oracle is examined in the rest of this article.
Oracle Balanced Scorecard enables support for the methodology of the Balanced Scorecard. It may
also be used to support, for example, the EFQM or EVA. However, particular attention shall only be
paid to supporting the BSC.
Three types of users possessing different roles can utilize this application:
Viewers: people using the system for monitoring performance objectives, for the achievement of
which they are responsible.
Designers: users in charge of designing scorecards, views, KPIs and targets for the system. They
define default settings and reports.
Administrators: people caring for installation, implementation and maintenance of the application.
They set up the application and maintain the data structure. Moreover, they are also responsible
for security of the application.
3.1 Viewers
Viewers of this system are people responsible for fulfilling the objectives derived from the strategy, i.e.
objectives that they are responsible for or for which they possess decision-making power. A specific
ID is assigned to each user. Based on this, the application displays for users merely the information,
and only in such a way, that they need. Usually, therefore, the objectives owned by Users are
displayed.
3.1.1 Navigating scorecards
After logging into the system, a Viewer will see a list pertaining to the Scorecard (fig. 2) available to
the User that is logged-on. This list is for quick orientation and access to an individual Scorecard. It
displays the Scorecard’s name, its owner and any additional information relating to these. Viewers
can also look at details of each Scorecard. The hierarchical structure of a Scorecard shows the logical
relationship between the Scorecards, not the data in the same. The application also allows a search
in terms of a Scorecard name or owner. From this list, it is possible to double-click on a Scorecard’s
name to access one of them.
542