THE REPUBLIC OF SERBIA ROAD DATABASE MANAGEMENT SYSTEM

Dragan Mihajlovi, Ph.D.

University of Banja Luka, Faculty of
Architecture and Civil Engineering,
77 Vojvode Stepe Stepanovia
Boulevard, 78000 Banja Luka,
Bosnia and Herzegovina
e-mail: dram@inecco.net

Raj Mallela, M.Plan.

HIMS Ltd., 10B Bentinck St.,
New Lynn, Auckland 0600,
New Zealand
e-mail: raj@himsltd.com

Neboja Radovi, Ph.D

PE Roads of Serbia,
19a Vlajkovieva St,
11000 Belgrade, Serbia
e-mail: radovicn@drenik.net

Igor Jokanovi, M.Sc.

Infra Ltd., 28 Ranka ipke St,
78000 Banja Luka,
Bosnia and Herzegovina
e-mail: jokanovic@blic.net

Sanja alija
Centar za puteve Vojvodine s.c.,
36 Takovska St.,
11000 Belgrade, Serbia
e-mail: sanja.calija@cpv-bgd.com

Abstract: Database management system is the core of the road maintenance planning and
management. Selection of the database management system is the strategic decision as it
influences numerous aspects related to practical realization of the system. Therefore, it has to
enable efficient road database functioning and future enhancements. The tool used for the new
Republic of Serbia road database is a powerful and flexible database management system
designed to meet the needs of consultants and road agencies. It is capable of storing data on any
type of asset and analyzing the data to prepare files for applications such as the HDM-4 and
dTIMS. The system acts as a bridge between data collected and analysis. It is used for creating
the analysis sections as well as reporting. The system is designed to work with almost any analysis
tool, although it contains specific functions and features that make it invaluable for use with the
HDM-4, as well as provide appropriate graphical presentation through build-in GIS module.
Key words: roads, road database, database management, sectioning, GIS

maintenance that will guarantee required condition

of road network. This will provide such homogeneity
of the network that the condition of the same does
not fell bellow the level estimated to be the allowed
limit.
What is apparent from the various studies is
that
road
agencies
successful
in
their
implementations have built strong foundations in all
of the fundamental components over a number of
years. First and foremost, they have developed an
asset management mindset, i.e. they explicitly and
conscientiously implement policies that are geared
towards managing their road infrastructure as an
asset whose value must be maintained and
improved. Their executives and management
promote asset management principles in order to
ensure that funding and budget are allocated to
appropriate areas. They are explicitly committed to

1. GENERAL
Road management can be seen as a process that is
attempting to optimize the overall performance of the
road network over time. In other words, the process
may be seen to comprise a number of activities (or
measures) that will have impacts on the road
network.
Over the last 20 years most road agencies
have implemented some form of computerized road
management system (RMS). The purpose of these
systems is to assist the road agency in planning and
prioritization of road investments.
Experience shows that application of RMS
on complete road network provides the possibility to
establish long-term consequences of the adopted
financing policy. On the other hand, it enables
overview of necessary financial resources for

- information about roads utilization (traffic

and vehicle data).
The road agency is to be in charge of the
entire RDB. This is necessary to ensure uniform
reporting for the purpose of keeping official statistics
and as a basis for the allocation of road
maintenance budget funds.
Entry of data into the RDB must proceed in
a modern, primarily computer-based way, ensuring
fast data access, processing, analysis and reporting
in accordance with the purpose for which the data is
being processed or analyzed.
The information collected should be retained
for long term historic analysis and for performance
assessment. There are many purposes for which
historical information may be used. Typical utilization
is as follows:
- check on overall condition of items on a
year-by-year basis (i.e. trend analysis);
- evaluation of efficiency of treatment;
- check on life treatments;
- financial evaluation of treatments.
The storage and retrieval of information
should be on the basis of the section requiring
attention and, in addition, it should be possible to
retrieve information for analysis of management
information on the basis of:
- geographical area;
- urban/rural area;
- road classification;
- traffic type;
- routes;
- treatments;
- any parameter which is considered as
inventory or condition data.
More often than not, a simple, flexible,
scalable and modularized software package is
recommended for a usable and sustainable RMS
which can be easily and economically extended over
time, as the RDB structure implemented might be
required to incorporate different data needs related
to planning process, different levels of data
complexity might be required to be included in the
database, and more reports and management
functionality might be required with time. The
database structure should be an open one, based
on personal computers, and it should serve as a
support to any type of the RMS (of-the-shelf or
custom made), with the ability to evolve and where
data can be added when required and wished.

the RMS, in the sense that it is built into their

processes and procedures. They ensure that
sufficient budget is available for data collection, for
upgrades and maintenance of the systems, and for
staff training and progression.
Data is vital to success of any management
system. Without data, it is not possible to conduct
proper analysis and monitoring of the road network.
Problems with data are one of the main causes cited
in failure of an RMS.
Information used by the RMS are far more
voluminous than for other management systems.
Complex RMS includes all information on the road
network (from inventory of roads, structures and
pavements, traffic volume, climate, bridge condition,
road damage level and surface pavement
characteristics to construction history and previous
financial investments). Usually, this huge amount of
data is being stored within some kind of road
database (RDB).
The Public Enterprise Roads of Serbia has
established its RDB for main and regional roads at
the beginning of 1990s, but since that time there
was no major update of data or any improvement
within the RDB structure or interface. In 2001, the
Republic of Serbia (RS) has received the loan from
the World Bank for improvement of the state road
network condition and institutional capacity. One of
the loans components was improvement of the
current RDB, and the contract has been awarded to
the consulting company Centar za puteve Vojvodine
from Novi Sad.

2. ROAD DATABASE
2.1. Conditions
An information system usually serves several goals
of the road agency, i.e. road planning, design and
investments, and the needs when organizing routine
maintenance and protection of roads. This
complexity of the multiple goals also imposes higher
requirements on the information system. A wide
selection of systems, comprising both hardware and
software, is available for specific needs.
Good information systems provide userfriendly data entry and search functionality and allow
ordering and organizing all sorts of data as it is
being collected or monitored. A RDB should include
the following data about roads and structures:
- technical data about roads and structures
(road network data);
- information on pavements and other road
elements defects and characteristics (road
condition data);
- information about expenses on roads
(works and costs data);

2.2. Road database structure

As detailed previously, RDB has to contain
numerous data. In accordance with recommendation
to structure the database on a modular basis and to
group data describing similar items into the same
module, the modules of the new RDB have been
developed to contain data presented in Table 1.

Table 1: General structure of the RDB

module
table
RS-Cvorovi
RS-Deonice
RS-Putevi
RS-Opstine
I
Reference system
RS-Odrzavanje
RS-GPS
RS-CvoroviSt
RS-DeoniceSt
D-IstPlanDokum
D-IstProjDokum
D-IstRadovi
II
Sections
D-Osovina
D-PodProfil
D-KolProfil
D-Klima
I-RazdTrake
I-Bankine
I-Kosine
I-Berme
I-Odvodnjavanje
I-Znakovi
I-HorizSig
I-Zidovi
III
Inventory
I-Propusti
I-Ograde
I-Mreze
I-Pojave

I-Ostalo

IV

Traffic

Pavement

S-PGDS
S-Prognoza
S-Zagusenje
S-STok
S-VPark
S-VParkKal
S-Nezgode
K-Povrsina
K-Konstrukcija
K-Istorija
K-PopPuk
K-MrePuk
K-PodPuk
K-Ravnost
K-Makrotekstura
K-Trenje
K-UdRupe
K-Kolotrazi
K-CupAgr
K-IzlucBit
K-LomIvice
K-Deformacije
K-Popravke
K-Unisteno
K-Defleksije
K-NeasfPut
K-TehStanje
K-KorStanje
K-Kalibracija

description
primary and secondary nodes
sections according to defined primary and additional nodes
road routes according to existing classification
division of sections by municipalities
division of sections by road maintenance areas
GPS coordinates of sections paths
nodes of the old reference system
sections of the old reference system
historical data on preparation of planning documentation
historical data on preparation of design documentation
historical data on execution of works
horizontal geometry
vertical geometry
content and dimensions of carriageway elements
data on climate zones
median lanes
shoulders
slopes
berms
drainage elements
vertical signalization
horizontal signalization
retaining and other walls
culverts for drainage and traffic
protection fences and guardrails
protection nets on slopes
bridges, viaducts, tunnels, galleries, landslides, rock falls,
settlements, footways, connections, service areas, gas
stations, restaurants, parking areas, rest areas, railway
crossings, bus stops, toll plazas, etc.
other equipment (kilometer posts, direction posts, mirrors,
traffic lights, ITS, glare protection, counters, SOS, etc)
size and structure of traffic volume and change by years
traffic volume forecast
congestion flow and speed parameters
traffic flow parameters
data on vehicle fleet
vehicle fleet calibration parameters
data on traffic accidents and change by years
type of pavement surface
pavement structure
history of interventions on pavement structure
transverse cracking
map cracking
longitudinal cracking
longitudinal roughness (IRI)
texture of pavement surface
skid resistance
potholes
rutting
raveling
bleeding
edge break
surface deformation
pavement repairs (potholes and deformations)
completely destroyed pavement surface
deflection measurements (FWD)
condition of unpaved roads
technical evaluation of pavement condition
evaluation of pavement condition from users' aspect
calibration coefficients for pavement deterioration model

module

table
T-Standard
T-CeneIzgr
T-CeneOdrz

VI

Costs
T-CeneRehab
T-CeneRekons

VII

Visual documentation

VIII Organization

T-Vozila
VD-Video
VD-Slike
O-Administracija
O-Upravljanje
O-Odrzavanje
O-Izgradnja
O-Materijali
O-Postrojenja
O-Konsultanti

description
identification of maintenance, reconstruction and
improvement standards
unit costs of construction and improvement works by
positions identified through standards and validity period
unit costs of routine maintenance works by positions
identified through standards and validity period
unit costs of rehabilitation and overlay works by positions
identified through standards and validity period
unit costs of reconstruction works by positions identified
through standards and validity period
unit costs of vehicle fleet expenses by categories
video records about sections
photo documentation by sections
administrative organization of state
management organizations
road maintenance companies
road construction companies
material source areas
plants for material processing and production
consulting companies

The structure presented is based on the

requirements of the contract, review of the existing
RDB and cooperation with the Clients staff, as well
as recommendations on the types of data to be
stored in the database. Final objective is to provide
the
HDM-4
(Highway
Development
and
Management Model) with necessary data. This
structure can be changed or extended at all times
i.e. during operation.

3.1. HIMS general features

HIMS is a powerful and flexible database
management and analytical system designed to
meet the needs of asset owners, asset managers
and their consultants. HIMS is capable of storing
and analyzing data on any type of asset with a
particular emphasis on linearly referenced assets
such as roads, railways, etc. The Figure 1. shows
the role of the HIMS in road management. It acts as
the bridge between the data collected and the
analysis. It is used for creating the sections for
analysis as well as reporting. The system is
designed to work with almost any analysis tool,
although it contains specific functions and features
that make it invaluable for use with HDM-4.

3. ROAD DATABASE MANAGEMENT SYSTEM

Database management system (DBMS) is the basis
for the RDB implementation. Selection of the DBMS
is the strategic decision because it influences
numerous aspects related to practical realization of
the system. Therefore, it has to enable efficient RDB
functioning and enhancement in future. Three
systems (Oracle, Informix and Microsoft SQL
Server) were analyzed as options for the DBMS with
the final decision to implement the RDB on the
MS SQL Server DBMS.
One of the requirements and the very first
idea was the system with high advantage of being
extremely simple in use. Also, the re-definition of the
data structure (changing of database structure and
type and amount of data in the database) should be
enabled to authorized users of high level, without a
need for specific software skills. Having this in mind,
and the DBMS selected for implementation, it was
decided to make a further step and select
commercially of-the-shelf (COTS) product that
contains all necessary functions in one package.
This was achieved by implementing the HIMS Asset
Management System (HIMS) for design and
management of the database, management of road
network, road data analysis and homogenization
and GIS (Geographic Information System) view.

Figure 1: Role of HIMS

- Data view: Integrates video and other

attribute data, thereby allowing users to
drive down the road and visualize the
condition. With flexible navigator based on
data group as well as spatial interface, the
data view is very simple and easy;
- Reports: HIMS has another royalty free
distribution embedded engine to design
report, charts and other graphs. With this
engine, existing reports can be modified or
new reports can be developed by the end
user (having enough privileges) at any
time without requiring any additional
software;
- Multi-language support: HIMS is built
considering the need for multi-language
support facilities. So far, it was
successfully used and implemented in
English, Chinese and Serbian language;
- Application: HIMS was programmed using
Visual Basic as the front end. HIMS
system can work in LAN/WAN networks
and as a disconnected (or stand alone)
database when LAN/WAN is not available.
A typical application of the HIMS contains
following steps:
- Create database: creation of a new
database using one of the templates or as
an empty database;
- System design: designing the data
referencing and data tables;
- Network
design:
definition
of
nodes,location
reference
points,
links/sections and segments;
- Enter data: database population with data;
- Segmentation: creation of homogeneous
analysis sections from the data;
- Data conversions and transformations:
population of target database with the
analysis section limits and data for eachh
section;
- Analysis: running of application such as
HDM-4 or dTIMS on the analysis sections.
The first three steps (creating the database,
system design and network design) are once off
exercises. Once done, they are not repeated,
although the network will be updated as it expands.
Data are then entered into the system and these
data used to define homogeneous analysis sections.
The analysis sections then have their data defined
and these are analyzed by a specific program.
The system can be as simple or as
complicated as the user requires since the level of
customization caters for almost any situation.
Within the RS RDB, Road Information
System (RIS) and Pavement Management System
(PMS) were developed using the enterprise version
of HIMS. RIS and PMS were developed as
sub-systems of the RS RMS. The system can be
extended to accommodate other sub-systems such

The HIMS is designed with a range of

features to cater for the needs of most users. Main
features of the system are:
- Flexible referencing system: HIMS was
built on the advanced and best practice
location referencing principles for linearly
referenced assests, such as roads. It is
possible to store data in multiple
referencing systems and convert it from
one referencing system to another. Linear
referencing system is linked to spatial GIS
referencing system;
- Network editing and auditing: HIMS has an
built-in network management module
which allows users to track historical
changes in the road network. It also
facilitates management (break up or
merging) of attribute data following the
changes in location referencing or road
netowork;
- User definable objects: The user can
import or define various objects such as
tables, queries and forms to store and edit
data. The system has default templates
that facilitate rapid creation of new
databases and data-entry facilities;
- Analysis engine: HIMS has built-in
analysis engine offering a platform for
various analyses including predictive
modeling, life cycle costing, optimization,
multi-criteria analysis, programming and
scheduling. This engine is very flexible,
completely configurable and can be
applied to any infrastructure asset;
- HDM-4 interface: HIMS has built-in HDM-4
interface which can prepare network and
traffic data for the HDM-4 analysis.
Results of the HDM-4 analysis can be
imported in HIMS database to prepare
customized reports and display data in
thematic maps;
- Sectioning: Based on the user defined
criteria, HIMS can automatically create
homogeneous sections of road data that
can be used for analysis. The system also
allows manual refinement of automatically
generated sections;
- Embedded GIS: HIMS was built on
embedded GIS principles. A royalty free
distribution GIS component in the HIMS
system means the end user is not required
to purchase or subscribe to any other
external GIS application. Once the line
work has been completed than HIMS can
read or import any industry standard or
data exchange files for displaying maps
within the HIMS software. GIS data can be
imported and exported to other external
GIS applications very easily;

as Traffic Information System (TIS), Accident

Information System (AIS), Bridge Management
System
(BMS)
and
Routine
Maintenance
Management System (RMMS), etc, if needed.

- Entry-This is the level at which the data is

imported into the system either using bulk
import and manual data entry forms;
- User-This level provides a view privilege
which most end users and managers will
use for accessing RMS outputs.
Each HIMS system object is assigned an
access level and available to different users based
on their user access level. This has been based on a
hierarchical approach as shown in Table 2.

3.1.1. Multi-level user hierarchy

RDB is designed on the basis of multi-level
hierarchy of users. However, given the sensitivity of
the data stored in the system it is necessary to
assign different management levels of access.
Access to functions and modules contained within
the system is provided and controlled by the use of a
login name and password.

3.2. Road information system

The primary functions of the RIS are to:
- manage the road network location
referencing data;
- enter and store road inventory data;
- enter and store pavement condition data;
- enter and store traffic related data;
- database management such as data
security and flagging latest data;
- view and query the stored data;
- provide GIS platform for viewing road
network and other attribute data;
- provide summarized (and current) attribute
data to other modules such as PMS.
Important feature of the system is data
storing related to sampling interval and not to
analysis segment or some common interval. When
collecting data, each data item has its own
appropriate sampling interval. For example,
roughness may be collected at 100 m intervals but
rut depths at 10 m intervals. Visual condition data
may be collected over 250 m intervals. Traditionally,
data were stored using the smallest common
denominator. Since the rut depths have been
recorded at 10 m intervals, the roughness and the
visual condition are also stored at 10 m intervals,
even though this leads to the same values being
repeated throughout the database. Instead of this
approach, in the HIMS each of these data items
would be stored in their own table, each with their
own data referencing based upon their sampling
interval. This eliminates data redundancy. The
different sampling intervals are resolved internally
when creating analysis sections.
Several examples of the RIS module are
presented on Figures 2-6.

Table 2: HIMS user roles

activities/tasks
details
data view and print
reports
spatial (GIS) map
view
data entry and
validation
data modification
and auditing
setting up
definitions/master
data
data analysis

user levels
user/
engientry
view
neer
general tasks

admin

special tasks
RIS/PMS
data manipulation

(in view screen) and

export
creating/printing

GIS thematic maps

data commit,
flagging recent
data, run analysis
transfer data to
HDM-4
location reference management
define and modify
location referencing

Four levels of login are provided within the

system:
- Admin-Administrator who will manage and
administer the system. Most of the system
functions are available with this login;
- Engineer-A level at which most of the data
analysis
is
undertaken
such
as
determining
network
condition,
determining
homogeneous
sections,
preparation of HDM input files and
generating maintenance program from
HDM output files;

3.3. HDM-4 interface

Specific data format is required for the HDM-4
analysis. To prepare data for the HDM-4 analysis
and to further process the results for customized
reports and decision-support information, the HIMS
has, but is not limited to, following functions:

(continuous length of road with similar

characteristics using certain criteria
defined);
- capability to prepare the HDM-4 analysis
input files, including assignment of
treatment to each section under analysis
based on a user definable treatment
selection decision tree relating to work
standards definition, using traffic growth
rate and classification available in
database and so on;
- capability to import HDM-4 analysis run
data (analysis results) selectively to the
RDB for customized report generation and
archiving purposes.

Figure 2: Selecting sections in list panel

Figure 3: Inventory data import

Figure 6: Typical data view screen

Beside the regular functions of the DBMS,

one of the most important functions of the system is
sectioning and data transformation. This is an
information process performed to divide and/or group
road network sections and transform data on the
basis of criteria given by users. After selection of
criteria, sectioning and transformation are performed
for relevant data stored in the RDB in compliance
with one of five general sectioning methods:
- fixed length: sections have fixed lengths,
for example 100 m or 500 m;
- value range: ranges of values are defined;
all adjacent data within a range shall be
included in the section;
- value deviation: when the value changes
by a certain amount from the start value a
section is created;
- value change: when there is a change in
value a new section is created;
this is typically used for creating sections
when there is a change of surface type or
width;
- cusum method: cumulative deviation
method, also called cusum (for
Cumulative SUM), was developed in the
1950s as an alternative to conventional
control charts for controlling quality in
manufacturing;
extremely
powerful

Figure 4: Data editing using data entry forms

Figure 5: Selecting data to view

- flexible HDM-4 interface to prepare data

for the HDM-4 analysis and to process
analysis results;
- capability to prepare representative
sections (road sections grouped on a
basis of criteria used to define state road
network matrix) for strategic analysis;
- capability
to
generate
relatively
homogeneous
analysis
sections

sectioning method which, in general, is

usually preferable to the other methods.
In this way, virtual division of road sections
is obtained within the whole or a part of reference
system selected by the HDM experts. This tool
searches the RDB according to the selected criteria,
collects relevant data, creates new homogeneous
sections, transforms source data and formats them
for direct input into the HDM-4. After the
transformation, the information obtained is
presented for the HDM user who has initiated the
process.
The importance of creating proper analysis
sections cannot be overemphasized. Without
appropriate sections it is impossible to establish the
correct maintenance treatments or improvements. If
complete section is being analyzed as the single
one, a part of the pavement, which is in relatively
better condition, could be given a treatment when it
was not warranted (average distress value higher
than the maintenance trigger level), and another
part, with worse condition, what could be an
inadequate treatment (lowered average value
resulting in wrong selections of works).
The system includes the possibility of
manual refinement (insert, join, delete and update) of
the automatically defined sections. After the
completion of the analysis, the HDM expert provides
confirmation that obtained information is correct and
information
process
of
sectioning
and
transformations generates data on newly-created
homogenous sections in compliance with the HDM-4
data format. Obtained data are used for further
analysis of road network through the HDM-4.

- region-region boundary and name;

- municipality-municipality boundary and
name;
- nodes-identification number and name;
- sections-identification
number,
road
number and orientation;
Several examples of the GIS module are
presented on Figures 7-9.

Figure 7: GIS map view screen

3.4. GIS
As many users shall access the system for different
purposes, there is a set of built-in GIS functions for
data view and reporting, such as:
- display of information in thematic GIS map
based on data available in the RDB;
cartographic basis for such maps has to
be prepared with other standard software
i.e. MapInfo, ArcView or similar;
- printing thematic maps or exporting to feed
other standard GIS software (GIS data
preparation).
The objective of GIS module included in
HIMS is to provide a facility or platform to end users
for making thematic maps or view data over GIS
map. Some of the major GIS mapping activities such
as line editing, finalization of geometry of road
centerlines and preparation of shape files, etc. are
not included in the GIS module of HIMS.
Five layers of map information are available
to prepare user defined thematic maps:
- state and province-state and province
boundary and name;

Figure 8: Retrieving basic information in GIS map view

Figure 9: Thematic map on RIS map view screen

The HIMS can also display georeferenced

.TIF and .JPG files as background raster images on
the map display.

4. CONCLUSION
The system implemented for the management of the
RS road network can fulfill the needs of a modern
road agency for proper road data and network
management.
The software will be used for complete
management of road network (updating road
lengths, removing or inserting roads sections when
they are created due to new construction or similar,
updating of data when sections are changed, etc)
and creation of homogenous sections in accordance
with the established/user-defined criteria.
Furthermore,
the
system
enables
preparation of data for various purposes, especially
for sophisticated programs, such as HDM-4, dTIMS
and similar, that are widely used for planning and
programming of activities on the road network.

REFERENCES
[1]

Republic of Serbia, Transport

Rehabilitation Project, Road Database,
project documentation, 2007-2009.