This is to certify that I have read this thesis write-up and recognized the scope and quality as sufficient for the award of
Master of Science Facilities Management ii
Date : 26 th
November 2005

DECLARATION
This is to certify that this thesis entitled
THE DEVELOPMENT OF A LANDSCAPE MANAGEMENT SYSTEM
FOR PEJABAT HARTA BINA,
UNIVERSITI TEKNOLOGI MALAYSIA:
A STUDY FOR THE GUIDELINES is entirely of my own work and research and has never been submitted for any other award of Masters degree except those that are noted as excerpts of other works and sources iii
Author : IZRAN SARRAZIN MOHAMMAD
Date : th
November 2005

iv

v
ACKNOWLEDGEMENT
The author would like to express his gratitude to En. Shahabudin Bin Abdullah of the
Department of Property Management, Faculty of Geoinformation Engineering &
Science Universiti Teknologi Malaysia for his constructive advice, comments and guidance throughout the undertaking of this research.
The author would also like to thank Dr. Hishamuddin Bin Mohd. Ali, Assoc. Prof. Dr
Abdul Hakim Bin Mohamed, En. Zamri Ismail, all the academic staffs of the
Department of Property Management and the Department of Geoinformatics, and all the parties that made the completion of this Masters project possible.

vi
ABSTRAK
Projek Sarjana ini melaporkan kajian bagi menghasilkan garis panduan bagi membangunkan Sistem Pengurusan Landskap bagi Pejabat Harta Bina, Universiti
Teknologi Malaysia. Landskap merupakan salah satu dari perkhidmatan sokongan di
UTM yang bertindak mewujudkan persekitaran pembelajaran yang kondusif untuk para pelajar serta kakitangan akademik. Untuk memastikan kebaikan dan keterpeliharaan pembangunan landskap UTM, Pejabat Harta Bina memerlukan Sistem Pengurusan
Landskap yang komprehensif dan sistematik untuk membantu kerja-kerja pengurusan landskap kampus UTM. Kajian dan analisis terhadap keperluan Sistem Pengurusan
Landskap bagi Pejabat Harta Bina, skop kerja, proses kerja serta data yang terlibat di dalam kerja-kerja pengurusan landskap dilakukan bagi memahami secara menyeluruh fungsi-fungsi yang perlu dipenuhi oleh sistem yang dicadangkan. Struktur modul-modul dan rekabentuk pangkalan data kemudiannya dihasilkan, dimana ini bertindak sebagai garispanduan terhadap perkara-perkara yang perlu dilibatkan dan bagaimana untuk membangunkan satu Sistem Pengurusan Landskap sebelum proses pembangunan yang seterusnya iaitu rekabentuk antaramuka dan pengarurcaraan dilakukan.

vii
ABSTRACT
This Masters project reports the task of studying for the guidelines for the development of a Landscape Management System for Pejabat Harta Bina, Universiti
Teknologi Malaysia. Landscape is one of the support services in UTM that serves to provide a conducive learning environment for students and academic staffs. To ensure the well-being of its landscape developments, Pejabat Harta Bina requires a comprehensive and systematic Landscape Management System to assist landscape management tasks for the campus. Studies and analysis on Pejabat Harta Bina’s requirements of a Landscape Management System, the scope of work, work processes and data involved in landscape management works were undertaken to thoroughly comprehend the functions that the proposed system should fulfill. Module structures and database design were then produced, functioning as guidelines on what should be incorporated and how to develop a Landscape Management System prior to subsequent development processes of interface design and programming.

viii
CONTENTS
CHAPTERS ITEMS PAGES
SUPERVISOR’S CERTIFICATION
DECLARATION
DEDICATION
ACKNOWLEDGEMENT
ABSTRAK
ABSTRACT
CONTENTS
ii iii iv v vi vii viii xiv xv xviii
CHAPTER 1 INTRODUCTION
1.4 The Importance Of The Research
1
3
6
7
7

ix
8
11
CHAPTER 2 LANDSCAPE MANAGEMENT & INFORMATION
SYSTEM
13
2.1 The Definition Of Landscape 14
14
2.2.1 14
15
2.3
2.5
Functions Of Landscapes
Factors Governing The Complexities Of
15
15
15
17
18
2.6 Living Landscape Maintenance
2.7 Hard Landscape Maintenance
20
26
27
29 2.9 Facilities Management Information System
2.10 Information System Components
2.11 System Development
30
31

2.11.2 Analysis & Requirements Capture x
34
34
36
39
39 2.12 Landscape Information Systems
2.12.1 The Putrajaya Lake & Wetland Management 41
2.12.2 The Arbor Tracker System 44
2.12.3 The Landscape Management System (LMS) 45
50
CHAPTER 3 CASE STUDY
3.1 Background Of Pejabat Harta Bina
3.2 Scopes & Responsibilities
3.3 The Field Of Work For Each Unit
3.3.1 Penyenggaraan
3.3.2 Ubahsuai
3.4
3.5
3.3.3 Unit Perkhidmatan Aset
Landscape Development In UTM
UTM’s Landscape Maintenance System
51
51
53
54
54
55
55
55
57

xi
3.6 Implementation Of Landscaping Works In UTM 57
3.7 The General Landscape Work Processes Of 61
Pejabat Bina
3.8 The Work Process Of Landscaping Works, 62
Unit Penyenggaraan & Ubahsuai Bahagian Harta
3.9 Requirement Analysis: A Qualitative Approach 65
66 3.10 Pejabat Harta Bina’s Requirements Of A
Landscape Management System
67 3.11 Analysis On The Requirements Of The
Proposed System
3.12 Ready Systems Versus Customised System
3.13 Summary Of The Analysis
73
77
79
CHAPTER 4 SYSTEM DESIGN
4.1 The Proposed Structure Of The Landscape
80
80
4.2 The Proposed Modules Of The Landscape 82
4.2.1 The Maintenance Module
4.2.2 The Inventory Module
84
85

4.2.3 The Contractors & Suppliers Module
4.2.4 Module
4.2.5 Module
4.3 The Database Design Of The System
4.4 Summary Of The Modules & Functionalities
4.5 Summary Of The Database Design Structure xii
86
87
88
89
96
98
100
CHAPTER 5 INVENTORY MODULE PROTOTYPE
101
5.1 ARCHIBUS/FM: An Overview Of The Software 102
5.2 Justification For Using ARCHIBUS/FM For The 105
Prototype
5.3 The Landscape Management System Inventory 106
Module Prototype
110

xiii
CHAPTER 6 CONCLUSION
111
111
113
114
BIBLIOGRAPHY 115

LISTOF TABLES
Table 1.1. Computer Aided Facilities Management (CAFM)
Systems & Module.
Table 2.1. Watering Process
Table 2.2. Weeding Process
Table 2.3. Insect & Disease Control Process
Table 2.4. The Most Common Components of A Landscape
Information System
Table 3.1. Cleaning
Table 3.2. Mature Trees Maintenance
Table 3.3. Immature Trees Maintenance
Table 3.4. Small Trees Maintenance
Table 3.5. Ground Cover Maintenance
Table 3.6. Types Of Data Involved in Pejabat Harta Bina’s
Landscape Scope Of Work
5
21
24
25
40
Table 3.7. CAFM System Users & Functionality
Table 3.8. Summary of Analysis
74
78
Table 4.1. Landscape Management System: Modules & Functionalities 97
Table 4.2. Summary Of The Database Design Structure 98
58
58
59
60
60
70 xiv

LIST OF FIGURES
Figure 1.1. The function of landscape as a support service entity
Figure 1.2. Research Methodology Diagram
Figure 2.1. An Information System
Figure 2.2. System Development Life Cycle
Figure 2.3. Methodology, Tools & Techniques
Figure 2.4. PLWMOS System Components
Figure 2.5. The Arbor Tracker PDA and Transponder Terminal
Figure 2.6. Information displays in the LMS
Figure 3.1. Landscape development in UTM
Figure 3.2. Tropical Park UTM
Figure 3.3. The General Landscape Work Processes Of
Pejabat Harta Bina, UTM
Figure 3.4. Landscape Maintenance Work Process
Figure 3.5. Modification Work Process
Figure 4.1. Data Flow Diagram (DFD) Of The Landscape
Management System
Figure 4.2. Diagram 0 (Modules & Processes of the Landscape
Management System)
63
64
82
83
45
49
56
57
61
3
10
31
32
33
43 xv

Figure 4.3.
Maintenance Module (Processes)
Figure 4.4.
Inventory Module (processes)
Figure 4.5.
Contractors & Suppliers Module (Processes)
Figure 4.6.
Report Module (Processes)
Figure 4.7. Drawing Module (Processes)
Figure 4.8.
Entity Relationship Diagram (ERD) For The
LandInfoPHB Database, Pejabat Harta Bina
Figure 4.9.
Entity & Attributes (Zones)
Figure 4.10. Entity & Attributes (Soft Landscape Maintenance)
Figure 4.11.
Entity & Attributes (Hard Landscape Maintenance)
Figure 4.12.
Entity & Attribute (Soft Landscape)
Figure 4.13.
Entity & Attributes (Hard Landscape)
Figure 4.14.
Entity & Attributes (Equipment)
Figure 4.15.
Entity & Attributes (Fertiliser)
Figure 4.16.
Entity & Attributes (Contractor)
Figure 4.17.
Entity & Attributes (Soft Landscape Suppliers)
Figure 4.18.
Entity & Attributes (Hard Landscape Suppliers)
Figure 4.19.
Entity & Attributes (Equipment Suppliers)
Figure 4.20.
Entity & Attributes (Fertiliser Suppliers)
Figure 4.21.
Entity & Attributes (Drawings)
Figure 4.22.
Entity & Attributes (Defects)
Figure 4.23.
Entity & Attributes (Report)
Figure 4.24.
Entity & Attributes (Order Information)
Figure 5.1.
Inventory Module: Zones
84
85
86
87
88
89
92
93
93
94
94
94
95
95
90
90
91
91
92
95
96
96
106 xvi

Figure 5.2. Inventory Module: Sites With Image
Figure 5.3. Inventory Module: Sites With Drawing
Figure 5.4. Inventory Module: Plants
Figure 5.5. Inventory Module: Equipment
107
108
109
110 xvii

LIST OF APPENDICES
Appendix 1
Appendix 2
Appendix 3
Appendix 4
Appendix 5
PLWMOS (Putrajaya Lake & Wetland Monitoring System)
Modules & Functionalities
PLWMOS (Putrajaya Lake & Wetland Monitoring System)
Interface
Tropical Park, UTM Landscape Plan
UTM Aerial Photo
Bahagian Harta’s Action Plan 2004 (Excerpt of the report) xviii

1
Chapter 1
INTRODUCTION
1.0 Introduction
Landscape is most popularly known as one of the artistic elements, used to modify and manipulate natural as well as manmade elements to make the landscape more attractive without jeopardising its function. The natural elements may include plants, water and the earth surface itself. Manmade elements on the other hand may include structures and buildings for public uses. Hence, landscape requires meticulous planning and design not only to ensure that it is able to function well but to ensure that it fulfils the public needs with regards to its surroundings. Landscape also requires thorough management, preservation, conservation and maintenance to ensure that it is always in good form and to allow the public to enjoy its aesthetical values.
With the development of information technology that offers various possibilities of data storage, data retrieval and manipulation of both spatial and attribute data, management tasks have recently shifted to a new trend through the utilisation of information technology to further improve decision makings, strategic planning, tactical approaches, policy makings, assessment tasks as well as assisting operational works.

2
However, the application of information technology in landscape management is still considered to be relatively new and uncommon, where manual filing systems are still the common practice in most government and private organisations. In fact, landscape management software are rare and mostly custom made for certain organisations to cater its own requirements. However, custom-made landscape management systems are also relatively rare. Perhaps, the fact that landscaping is often seen as a discipline that merely functions to provide aesthetics and conducive environment influences the perception of landscape managers to not see the benefit that can be gained through the investment of information technology in landscape management.
As landscape provides values that may increase the competence of organisations, core businesses that focus on recreational activities and education require good and wellmanaged landscape in order to complement and support the running of the core business.
The following diagram shows how landscape functions as a support service entity.

3
Core Business
Require
Aesthetics/ Image
Function
Conducive
For
Leisure activities
Commercial activities
/ Events
Support
(Support Service)
Landscape
Provide
Require
Soft & Hard landscape design
Shade, stroll, play, sports, etc.
Natural landscape + designed landscape
Provide
Facilitate
Landscape facilities (walkways,
Planting)
Strategy (Concept & design)
Management
Maintenance strategy
Maintenance
Require
Figure 1.1. The function of landscape as a support service entity
(Source: Author’s interpretation)
Cullen (1981) stated that two of the most influential factors that govern the failure of landscape projects are poor landscape planning and poor landscape maintenance works. Landscape planning requires thorough understanding on matters pertaining to the site, goal to be achieved, cost, and labour. Landscape maintenance on the other hand requires thorough understanding on the requirements of maintaining the landscape elements in good condition. Both factors inevitably demand organised, comprehensive and convenient accessible information to assist management and maintenance works.

4
Pejabat Harta Bina, Universiti Teknologi Malaysia is currently facing problems in landscape management and maintenance works due to unsystematic archiving of landscape information. Hence, records on landscape contractors, fertilisers, schedules, soft and hard landscapes, etc. are often hardly available when needed by the management team for evaluation, strategy-making and planning. En. Mohd. Faizal B.
Suleiman, the Landscape Technical Assistant at Unit Penyenggaraan & Ubahsuai
Bahagian Harta, Pejabat Harta Bina conveyed the problem of facing difficulties in retrieving and analysing landscape related information due to the absence of a systematic information system to assist landscape management works. En. Roslan
Shariff, a Civil Engineer at Bahagian Harta, Pejabat Harta Bina with wide experience in system development on the other hand stated that where other information systems can be found in abundance that include Real Estate Information Systems, Property
Management Information Systems and Facilities Management Information Systems,
Landscape Information Systems are rare.
The existence of various other facilities management software with various modules to assist management tools can be found in abundance in the market. However, these software do not provide modules that are suited for landscape management purposes despite the recognition of landscape as one of the elements in facilities management. Table 1.1 shows a number of the most popular facilities management software in the market and the modules that they offer.

Table 1.1. Computer Aided Facilities Management (CAFM) Systems & Modules.
Archibus
Aperture
FM Systems
OFMS
Prism
ATG
SSM
Software Modules
ƒ
Space management
ƒ
Real estate management
ƒ
Building operations
ƒ
Telecommunication
ƒ
Space management
ƒ
Space management
ƒ
Space accounting
ƒ
Space management
ƒ
Autocad ARX overlay
ƒ
Maintenance management
ƒ
Inventory control
ƒ
Space management
ƒ
Event management
ƒ
Space management
ƒ
Electricity
ƒ
Life safety
ƒ
Space management
ƒ
Electricity
ƒ
Life safety
Source: CAFM System Peer Preview –University of Massachusetts (2001)
5
From the above table, it can be seen that CAFM systems do not offer modules that can be applied to landscape management works. The Space Management modules are somewhat related and can be partly utilised in landscape management works but lack essential functions that are vital in landscape management. Hence, the scenario of the problem is:

i. Most landscape organisations (including Pejabat Harta Bina, UTM) that are responsible in landscape management still practise manual filing systems. ii. Most management software including CAFM do not have modules for landscape management works.
6
Due to these facts, this research project aims to study for the guidelines for the development of a Landscape Management System that can be recommended to Pejabat
Harta Bina, Universiti Teknologi Malaysia which can benefit landscape management works.
1.2 Goal & Objectives
The goal of this research is to study for the guidelines for the development of a
Landscape Management System that covers all landscape management aspects practised by Pejabat Harta Bina, UTM. A prototype of one of the modules of the proposed system
(inventory module) will be produced as a by-product of this research. The objectives of this research are to: i. To translate the work process of landscape management & maintenance practised by Pejabat Harta Bina, Universiti Teknologi Malaysia into an information system that will enhance the efficiency of the work process. ii. To structure the modules that are essential to be incorporated in a Landscape
Management System. iii. To structure the database design of a Landscape Management System by analysing the types of landscape management data required in the system.

7
1.3
Scope of Research
The scope of this research shall cover these following aspects: i. The landscape management & maintenance policies, strategies, and procedures of Pejabat Harta Bina, Universiti Teknologi Malaysia. ii. The criteria that should be taken into consideration in designing and developing a complete Landscape Management System. iii. The types of modules and data to be incorporated in a Landscape
Management System.
This research aims to study for the guidelines for developing a Landscape
Management System by studying the work process, required modules and data, followed by the designing of the structure of the system modules and database. This research does not however cover subsequent system development processes such as interface design and programming due to limitation of time.
1.4 The Importance Of The Research
This undertaking of this research is expected to benefit the following parties: i. The UTM Administration
This research can benefit the UTM administration in identifying problems in landscape management works, upgrading landscape policies and strategies, and further improve and refine outsourcing criteria, through the awareness of the development of an organised and systematic landscape management system.

ii. Pejabat Harta Bina, UTM
Pejabat Harta Bina, UTM can benefit from this research by gaining insights on how to develop a system that can further improve the efficiency of landscape management and maintenance works.
8
1.5 Methodology
The steps of works involved in this research are mainly divided into: i) Literature Review
Literature studies on related works, landscape management scopes, information system designs and requirements, required data sets. ii) Landscape Management Appraisal
Studying the landscape management policies, strategies, procedures, scopes and work processes of Pejabat Harta Bina, Universiti Teknologi Malaysia.
iii) Data Acquisition
Acquiring data related to user requirements, scopes, and work processes via interviews with the personnel in charge of landscape management and other related works at Pejabat Harta Bina.

iv) User Requirements Analysis
The main purpose of analysing user requirements is to understand the function that the system has to fulfil. A thorough study on current problems and discussion with the user are important to truly understand the objective of the system. The gathered information that may include user’s specification, organisation policies and standards is subsequently analysed in order to produce the specification of the system. The identification of user requirements will decide the data that has to be acquired for the design of the system.
9 iv) Landscape Management System Design
Designing the system based on the findings in the user requirements analysis phase. Existing landscape management systems shall be studied to look into the possibilities of adaptation or improvement, with regards to the suitability of the intended landscape management system. The output of this phase is the module and database design of a complete landscape management system for Pejabat Harta Bina, UTM. This research will not develop the whole complete system due to the constraints of time.
Instead, only a single inventory module will be developed as a partial prototype of the whole system. v) Development of The Inventory Module Prototype
The development of a prototype module of the system will be developed as a byproduct of this research. The prototype shall be an inventory module of the larger designed system. This research will utilise ARCHIBUS/FM V.14 for the development of the inventory module.
Figure 1.1 shows the Methodology Diagram for this research.

10
Landscape management, information system designs and requirements, required data sets.
Landscape management policies, strategies, procedures, scopes, work processes of Pejabat Harta Bina UTM
Interviews with Pejabat Harta Bina’s landscape management personnel for gaining user requirements, scopes & work processes.
Qualitative analysis on Pejabat Harta Bina’s requirements of a
Landscape Management System (work process, scope, data, existing systems)
Module structures, functions, database design
By product
Developing a prototype of the inventory module
Figure 1.2. Research Methodology Diagram
(Source: Author’s Interpretation (2005))

1.6 Chapters
The write-up of this research is divided into 6 chapters. The first two chapters cover the theoretical part of the research while the 4 remaining chapters cover the practical aspects of the research. The chapters are as follows:
11
Chapter 1: Consist the introduction part of the research. This chapter discusses the issues of the research, research goal and objectives, importance of the research, research methodology and chapters.
Chapter 2: Chapter 2 mainly discusses landscape and information systems. It comprises the definition of landscape, types of landscape, landscape elements, landscape planning, management and maintenance, landscape information systems, issues of landscape information systems, information system design criteria and approaches, models and examples of existing systems.
Chapter 3: This chapter looks into the details of landscape management of
UTM. It covers the landscape areas of UTM, UTM’s landscape policies, strategies, management standards and systems, maintenance systems, existing database/filing systems and UTM’s requirements of a landscape management system. These findings will then be analysed by using qualitative analysis methods to reach a conclusion to what the design of the proposed system should be like.
Chapter 4: This chapter is the pinnacle of the research. It discusses the design of the system based on the findings in Chapter 3. The information acquired in Chapter 3 is analysed and the results of the analysis are used to propose a design most compatible with the requirements of Pejabat Harta Bina, UTM.

Chapter 5: This chapter discusses the development of the Landscape
Inventory Module using Archibus version 14. The inventory module covers the landscape elements in the UTM’s Tropical Park where information of types and names of soft landscapes, hard landscapes, maintenance works and contractors and personnel involved can be acquired.
12
Chapter 6: This chapter is the final part of the research. It provides the summation and conclusion of the research. It also discusses possibilities for future improvements in undertaking projects of somewhat similar nature to this research.

13
Chapter 2
LANDSCAPE MANAGEMENT & INFORMATION SYSTEM
2.0 Introduction
In general, all of the objects that can be found in this world are parts of the term landscape. In other words, landscape is the outer view or earth surface formed by natural processes or constructed by man. Landscape is also a process of using spaces in an attractive manner. This can be achieved via medication of the earth surface as well as the elements that can be found on it which can contribute to elevating the site’s potential and resident’s well being (Laurie, 1975).
Landscape is one of the important aspects of development that has to be emphasised for it is closely related to the well-being of the public. Rapid urbanisation that is currently taking place all over the globe has started to affect the environment physically, socially and economically. Carelessness, failure and being oblivious toward the equilibrium of the ecosystem will lead to high cost consumption and may not be able to be undone as before (Dato’ Khalid Hussin, 2000). Thus, awareness towards conserving nature including rivers, mountains, forests and the urban landscape is currently one of the most important agendas in landscape development (Dato’ Abdul
Ghani Othman, 2000).

14
2.1 The Definition of Landscape
The term landscape can be defined as ‘the outer view that exists either naturally or culturally that can be seen on the earth surface such as plants, topography, buildings, rivers, lakes, etc (Kecom, 1998). Another definition quotes ‘landscape includes all things that can be seen on the earth surface (Rosimah, 1998). A more comprehensive definition may be found in Covejoys’s ‘Land Use and Landscape Planning’ (1993) that defines landscape as ‘ ….not merely fine arts with the most important function of creating and conserving man’s habitat and the natural beauty of a country but also involves comfort, convenience and the well-being of urban dwellers that don’t have the luxury of indulging themselves with the beauty and serenity of countryside natural beauty through the aid of landscape arts’
2.2 Types of Landscapes
Generally, there are two types of landscapes that are soft landscapes and hard landscapes. These however can be further divided into four types of landscapes that are soft landscape, hard landscape, natural landscape and manmade landscape. Hard and manmade landscapes are products of man’s creativity and the imagination of a landscape designer.
Soft landscapes are the arrangement of plants and natural elements that can create a comfortable and serene surrounding. It must be so compatibly done with the soil condition as well as suitable exposure to sunlight. Soft landscape also refers to various plants, trees, foliages, creepers, ground covers etc.

15
2.2.2 Natural Landscape
The natural landscape or sometimes known as virgin landscape consists of plants, rivers, earth surface and other natural entities that have not been disturbed by any form development. It has been increasingly difficult to identify an area of true virgin landscape due to mass human exploration and development since the past two decades.
Hard landscapes include all manmade structures such as lamp poles, signage, bridges etc (Mustapa Kamal, 1989). It also includes pavements, public seats, dump sites, and various focal elements. Hard landscapes function as structures or visual skeletons of a particular landscape. They are usually integrated with soft landscapes, complementing each other, forming an attractive scene as well as providing certain specific functions.
2.2.4 Manmade Landscape
According to Hasliza (1994), manmade landscapes are artificial products of human imagination and creativity in mimicking natural landscape elements such as ponds, lakes, caves, and even beaches.
2.3 Functions of Landscapes
The functions of landscapes can be divided into a few main parts:

16 i) Aesthetics
This is the most common perceived function of landscape, acting as the backdrop of a building, define a space, provide a sense of space, framing a man-made element, creating a desired image in order to convey the operation and services of an organisation, etc. ii) Environmental aspects
Being closely related to the environment, landscape inevitably plays an important role in creating a conducive environment including climate control, preserving the ecological equilibrium, providing clean air through the process of photosynthesis, soil erosion control, and providing a natural habitat for animals that share the environment with humans. iii) Economics
Landscape is also known to contribute to the economics sector. A well-planned landscape development has been known to promote tourism via the presentation of cultural values, ethno-landscaping, agriculture and others that can attract local and foreign tourists. Landscape also has the ability to increased property value compared to a property that is not complemented with a well-developed landscape. iv) Functional Purposes
Landscape also provide various functional purposes, facilitating a developed area with unsubtle services including security, providing shade, creating boundaries, buffering and providing privacy for users.

17
Landscape Management consists of management and monitoring works of landscape projects and elements. It is mainly divided into a series of phases that include policy making, strategic planning, project tendering, landscape project management, maintenance, equipment considerations, cost estimating, and sustainability.
All landscape development works have to be followed by well-planned and thorough management and maintenance works. Plant maintenance in particular, is vital and must be properly scheduled in order to ensure that the plants are able to grow healthily. The maintenance programme should commence immediately after planting works have be done and needs to be carried throughout the life cycle of the plants (Garis
Panduan Landskap Negara, 1995).
A landscaped area will not achieve the desired and expected success if maintenance works are not carried out properly and consistently. Cullen (1981) in his book The Concise of Townscape stated that 60% of the failure of landscape projects is due to poor landscape maintenance works. Unlike other architectural projects, a landscape project deals with living elements (plants) and as all living things do, these living landscape elements require nutrients, nourishment, sufficient light and water, trimming, treatment or they won’t be able to grow healthily hence won’t be able to fulfil their function in the whole landscape context. Be it for aesthetics, security, buffering and others, the well-being of the living landscape elements require continuous care and must be well-attended in order to ensure the success of the landscape project.

18
2.5 Factors Governing The Complexities of Landscape Management
There are a number of factors that govern the complexities of landscape management and maintenance works. i) Area size
A large landscaped area requires more manpower, carefully scheduled maintenance work, evenly covered watering and fertilising tasks, more strenuous observation of the well-being of the plants, more difficult and time consuming weeding task and involve higher maintenance cost. ii) Types of plants used
The very plants that are used in the landscape project can also pose differing level of complexities in maintenance works. The involvement of plants that are sensitive to light, vulnerable to insects and diseases, require more frequent watering and fertilising, deciduous plants and others require more attention, hence making maintenance works more difficult. For example, the use of Ficus benjamina for hedges and triphoria is very popular here in Malaysia. However, this type of plant is vulnerable to insects and require continuous trimming as the leaves and branches grow at a rapid rate. The use of flowering plants such as Bougainvilla require a well-monitored watering and fertilising programme or the plants will not bear flowers. Plants with short life span such and plants that reproduce rapidly also pose difficult maintenance works.

19 iii) Planting Design
Landscape designers often create a much more attractive landscape setting via the use of mass planting or weaving. This is one of the most common techniques used by landscape designers. However, this type of design requires meticulous care of the plants or the desired affect will not be accomplished successfully. Continuous trimming is required to avoid untidiness, or overpowering of one plant towards the other. iv) Types of Landscape Elements Used
A landscape design usually incorporates various types of elements including water, rocks, timber, artificial rocks (cement), etc. These different landscape elements require different types of maintenance and are often found mouldy, chipped away and decaying. Fish ponds for example, are one of the most difficult to maintain landscape elements as they are prone to becoming mouldy, and the water is usually murky. v) Types of Activities That Take Place in The Landscaped Area
The landscape elements in a landscaped area that are used by large crowd for various activities is often found to be in poor condition. Plants are stamped, twigs and branches are broken, flowers are picked, benches and other manmade structures are covered with graffiti, etc. This type of area requires extra attention and maintenance works may have to be carried out more frequently. vi) Fauna Involvement
Fauna including various animals and insects that inhabit a landscape are known to double the attractiveness of the area. However, the landscape management often has

to deal with the clearing of their droppings and in some cases deal with destructive faunas such as woodpeckers, and various insects.
20
2.6 Living Landscape Maintenance
The maintenance works for living landscapes include watering, ground covering, weeding, fertilising, insect and disease control, trimming, weaving, gapping and replanting.
i) Watering
Watering has to be carried out according to various factors including climate, types of plants and soil type. The tale below describes the watering process according to types of trees.

21
Table 2.1. Watering Process
Types of Trees
All types of trees
Major trees/ Palms
Small trees
Ground covers/ Grass
Watering description
ƒ
Watering should commence immediately after planting
ƒ
Sufficient water with absorption depth of 150mm.
ƒ
Water should reach the surface of leaves to remove dusts.
ƒ Water pressure should not damage the plants or scrape the soil surface.
ƒ
Watering frequency for immature plants is twice a day in the morning and evening. Avoid watering in hot sunny periods.
ƒ
Big mature trees do not require watering unless showing signs of lacking water such as wilting, dull leaves and flowers.
ƒ
Daily watering is required for the first 6 months.
ƒ
Major trees that are planted in paved areas require watering especially during rainy seasons.
ƒ
Once in 3 months, plants should be watered with large amount of water to remove dusts.
ƒ
Require daily watering
ƒ
Plants with broad leaves require watering at the base of the plants to ensure sufficient water is supplied to the plants.
ƒ
Avoid watering directly on the surface of the leaves if watering that takes place at noon to avoid blistering the surface of the leaves.
ƒ
Watering should commence immediately after planting.
ƒ Avoid watering in hot sunny periods and late evening to prevent blistering and molds.
Source: Garis Panduan Lanskap Negara (1995)

22 ii) Ground covering
This is a task of covering the surface of the soil with dried grass, dried leaves or black plastics. This is to: a) Reduce water loss in the soil b) Avoid growth of weeds c) Stabilise soil temperature d) Improve air and water flow
The ground covers should be: a) From materials that do not burn and decompose easily. b) Applied especially during rainy seasons to prevent soil erosion. c) Applied to newly planted areas. iii) Fertilising
Fertilising is done to supply nutrients with nitrogen, phosphorus, kalium, etc to the plants. The purpose of fertilising is to replenish the content of nutrients in soils. The lack of nutrients will cause plants to easily break, retards growth and leaves turning yellow. The percentage of fertilisers needed depends on the pH value and fertility of the soil.
The health of plants depends on the type of fertiliser used, method and time of application. There are mainly two types of fertilisers, organic and chemical fertilisers.
Fertilising works are most suitably done after weeding and trimming.

23 iv) Trimming
Plants are dynamic landscape elements where the shapes, sizes and colours change over time. In order to ensure that the plants do not change and the measurement is always in accordance to the scale, fixed during the design stage, trimming works have to be undertaken from time to time. This is done to: i. Control the shapes and measurements of the plants as desired. ii. Control the size of trees to avoid over growth. iii. Remove damaged, dead of infected branches. iv. Promote the bearing of flowers and fruits. This is done by removing old flowers or fruit stems. v. Shape plants into specific shapes. v) Weeding
Weeds are the main enemy for plants in a landscaped area. Weeds compete the plants for food and can even be hosts for destructive insects, fungus or bacteria that may attack the plants. Weeds also flaw the view of a landscaped area especially if they have overpowered the other plants. The removal of weeds will enable nutrients to be absorbed fully by the plants without competition. Table 2.2 shows the weeding process according to the type of trees.

Table 2.2. Weeding Process
Types of Plants
All types of plants
Major trees
Small trees
Ground covers
Weeding
ƒ
Manual weeding
ƒ
Weeds must be removed before bearing of flowers.
ƒ
Manual weeding at tree buttress
ƒ
Use of weed poison only for areas where manual weeding cannot be carried out
ƒ
Manual weeding
ƒ
The use of weed poison should be minimal as small trees may be affected by the poison
ƒ
Must use suitable weed poison to avoid damaging the ground covers.
Source: Garis Panduan Lanskap Negara (1995)
24 vi) Insect & Disease Control
Insect and disease control should be undertaken at least once a month. Control and inspection should be carried out accordingly based on appropriate scheduling. The process of insect and disease control is as follows:

Table 2.3. Insect & Disease Control Process
Types of plants
All types of plants
Insect & disease control
ƒ
Inspection should be carried out once a week.
ƒ
Need to identify the types of insects and the damaged caused prior to insecticide application.
ƒ
Fungicide is used for fungal control.
ƒ Requires appropriate scheduling and suitable quantity of poison used in application.
ƒ
Plants with severe infection should be removed.
Source: Garis Panduan Lanskap Negara (1995)
25 vii) Weaving
Weaving is undertaken from time to time as a landscape area usually consists of various types of plants. Plants that are retarded or showing signs of infections have to be inspected and replaced if required. Usually small plants that form hedges and ground coverings have to be replaced after 3 to 9 months. To ensure consistencies, new plants that are woven should be the same size as the existing ones. viii) Gapping
Gapping is seldom undertaken after the landscape has been established. To ensure healthy growth, plants require space and suitable airflow and sufficient sunlight.
Hence, plants that are too close between one and the other should be removed permanently or to another place.

2.7 Hard Landscape Maintenance
The maintenance scope for hard landscape elements involves: i) Pedestrian walkway repaving
Repairs and amendments should be done for pavement tiles that are loose or broken especially for areas of high traffic flow.
26 ii) Repainting works
Inspection for repainting works for hard landscape elements should be undertaken to determine whether repainting is or not required. Usually, repainting works are done for structures that consist of metal, timber and concrete, once a year. iii) M&E Equipment Inspection and Replacement
Inspections are usually done at monthly basis especially to identify damages or malfunctions of M&E equipment in the landscaped area. Among the maintenance works that are involved are repairing of street lamps, decorative lamps, water pumps, etc. iv) Replacement of Hard Landscape
Works include the replacement of benches, tables, sculptures, etc, that are damaged, broken. Replacement works are also done in conjunction of changes of theme and image that the management has agreed upon.

27
2.8 Information Systems
Information is a key corporate resource in nearly all organisations. They need accurate, relevant and timely information to make intelligent business decisions. This involves identifying relevant business entities and gathering information about them. It also involves designing good database systems that will capture, validate, process and generate information that is need for decision-making. To generate such information, organisations must plan, design, implement, evaluate and maintain their corporate database using sophisticated management system (DBMS).
Many organisations today are data rich but information poor. They collect lots of data but don’t have appropriate systems to turn those data into useful information for decision-making. Decision-makers must have information in the right form, at the right time, and at the right place. This is where information systems come in. It is very unlikely that organisations will be effective if they do not have in place appropriate information systems which include well-designed databases.
Early information systems were stand-alone batch systems. They offered limited capabilities. Today, such systems are inadequate. Then came online (interactive) systems and real-time systems, which offered greater flexibility. These systems enabled organisations to update data in real time. They offered great improvement over the precious batch systems because now data can be captured and updated in real time. They were real boost to organisations that had disturbed offices/ sites as data from various sites can now be collected and integrated. This made the generation of quality information for effective decision-making. These systems came to be known as intraorganisational information systems ; systems that allowed access to information from anywhere within the organisation (Sellapan 2000).
Organisations also needed to do business with other organisations. This resulted in the emergence of inter-organisational information systems ; systems that allowed trading partners to communicate with one another by accessing each other’s databases.

28
Most of these systems were based on EDI or Electronic Data Interchange (Sellapan
2000). These systems enabled organisations to greatly improve their business operations.
Organisations today use Internet or web-based information systems. The Internet offers limitless opportunities to do business. It transcends the distance and time barriers.
The web-based systems are an extension of the intra-organisational information system since they allow anyone who is connected to the Internet to access these systems.
Organisations need appropriate information systems to meet the information needs of users at each level and across all functional units. To this end, several information systems have been developed to meet the information needs of users. These include the following: i. Transaction Processing System (TPS) – A departmental information system to meet the information needs of lower-level or operational management. ii. Management Information systems (MIS) – An enterprise-wide information system to meet the information needs of middle and top management. iii. Executive Information System (EIS)/ Executive Support System (ESS) – An information system that filters and presents information in a variety of formats to help executives in their decision-making. iv. Decision Support Systems (DSS) – AN information system with modelling facilities that allow top and middle management to perform ‘what-if’ analysis. v. Expert Systems (ES) – A system that mimics the human expertise and offers suggestions and recommendations to the user in a particular domain.
(Sellapan, 2000)

29
2.9 Facilities Management Information System
Facilities Information Management System (FIMS) is a Management
Information System (MIS) that manages information concerned with FM processes and functions. It is a system that can be used to manage the following categories of information:
ƒ
Physical Resources – site, infrastructure (utility systems), buildings, resources/assets within buildings.
ƒ
Support Services – administration, property maintenance, security, health and safety, catering, car fleet management, contract control, cleaning, etc.
ƒ
Human Resources – personnel management, contracts, recruitment, training, etc.
ƒ
Business information – process documentation, contractual, policies, financial, etc.
(Joudah, 1996)
FIMS reflects the setting up of strategies and frameworks, and the tools used, for managing information at strategic and tactical levels. An example of FIMS which deals with computerised tools or systems through which these information management functions are processed is called Computer Aided Facilities Management or more commonly known as CAFM. CAFM can be defined as the use of automated tools and procedures which increase productivity and efficiency in facilities management (Joudah,
1996). CAFM softwares are among others ARCHIBUS/FM, Aperture, FM Systems,
OFMS and PRISM.
The FIMS framework can be based on two main functional categories common to many organisations that are:

30 i) Office Automation
Includes most of the organisational administration, finance and personnel office functions as well as FM processes/ project functions, handled separately or by integration. A FIMS framework for this category should comprise three main modules, namely document preparation, document presentation and document management. ii) FM process/ project functions
According to the nature of FM processes/ projects and the type/ format of information handled and managed, such functions are facility-based, subdivided by management process (categorise, list, and describe a facility / analyse, model and evaluate the performance of a facility against indicators/ appraise the facility against other options and make decisions about it). A FIMS framework for these categories should comprise 6 main modules, namely facilities (estate/ assets) descriptive, facilities performance analysis and modelling, facilities option appraisal and decision support, facilities report/ document preparation, facilities report/ document presentation, and facilities report/ document management.
2.10 Information System Components
An information system consists of several components or modules, all working together to accomplish the system’s objectives. The modules interact with one another to perform the various business functions. For example, the output from one module may become the input top another module. Each module does a specific task or set of related tasks. It may also use data stores (files) to store and retrieve information. Figure 2.1 shows the basic structure of an information system.

31
Inputs
Information System
Hardware, Software, Tools,
Procedures, Standards, Data,
Figure 2.1. An Information System
(Courtesy of Sellapan, 2000)
Outputs
Inputs take the form of text (numbers, text, date, currency, Boolean), images, audio and video. Most of the inputs to databases usually take the form of text. Outputs take the form of reports (soft or hard copy). They usually include charts such as line, bar and pie charts. The information transforms the inputs to outputs using data operations
(sort, calculating, summarising, etc). Data and programmes (software) constitute the core of an information system.
Developing and maintaining an information system is a complex but welldefined process. It is usually done in several stages- preliminary investigation, analysis and requirements capture, design, implementation and maintenance. The term ‘system development life cycle’ (SDLC) is often used to describe these stages as shown in
Figure 2.2.

32
Preliminary investigation
Maintenance
Implementation
A nalysis & requirements capture
Design
Figure 2.2. System Development Life Cycle
(Courtesy of Sellapan, 2000)
2.11.5.
Further explanation on the components of the SDLC is elaborated in 2.11.1 to
System development and maintenance involve several groups of people such as the client, user, system analyst, programmer, database administrator, network administrator, software quality assurance (SQA) group and the maintenance staff. All these people must work together to develop and maintain a system successfully.
System development involves the selection of suitable: i. Methodology
The methodology to be used (e.g. structured, object-oriented). The client may decide on which methodology to use, in which case it acts a constraint. Each methodology has its own strengths and weaknesses. So the client and developer must discuss and select a methodology that is suitable for the application and the organisation.
The methodology selected may determine which tool or technique to use.

33 ii.
Computer Aided System Engineer (CASE) tools
Computer Aided System Engineer or CASE tools (e.g. System Architect, Visible
Analyst, Rational Rose) help system developers to simplify and speed up the system development process. They also help to reduce the system development cost. Systems developed using case tools are usually of a higher quality because they follow accepted standards for coding and documentation. There are several features available in a CASE tool such as diagramming, design checking and code generation. iii. Techniques
This may include Entity Relationship Diagram (ERD), Data Flow Diagram
(DFD), Class Diagrams, Use case diagrams, and Sequence diagrams. Different methodologies use different techniques. For example the structured methodology uses techniques such as ERD and DFD while the object-oriented methodology uses techniques such as Class diagrams, Use case diagrams and Sequence diagrams (Price,
1999). Figure 2.3 illustrates this system development concept.
Methodology System Development
Techniques
Figure 2.3. Methodology, Tools & Techniques
(Courtesy of Sellapan, 2000)
CASE Tool

34
2.11.1 Preliminary Investigation
In this phase, the system developer (with the cooperation of the client/ user) briefly analyses the system to determine if there is a real need to develop a new system or the current or existing system is adequate perhaps with some minor modifications. If a current or existing system is needed, this phase also examines if its development is feasible from the financial, technical, social and legal point of view. If the system is needed and is feasible, system development moves on to the next phase.
2.11.2 Analysis & Requirements Capture
In this phase, the existing system is analysed in greater detail to determine what is needed and why the current system is not satisfactory. The system developer studies the system to gain an in-depth knowledge about the system; input, processing, storage, outputs, to determine the problem areas. The system developer typically uses a combination of fact-finding techniques such as document gathering (organisational charts, code, and procedures and standards manuals) observation, questionnaire and interviews.
To acquire detailed information about the system, the system developer will typically ask probing questions that start with ‘What, Why, When, Where, Who and
How?’ The system developer analyses responses to these questions to determine the problems and bottlenecks inherent in the system. To analyse the system, the system developer may use techniques such as DFD and ERD.
One way to analyse the system is to look at all the system modules and for each module, determine what (input) goes into the module, what processing (transformation) takes place, what data store (file) are used and where the output goes. (Sellapan, 2000)

The analysis will reveal the shortcomings in the existing system in meeting the current future requirements. Once the analysis is completed, the system developer (in consultation with the client/ user) validates and establishes the requirements of the system.
35
The system requirements fall into two categories that are functional and nonfunctional requirements.
This refers to functions (e.g. data entry and validation, computations, queries and reports) that the client needs in order to do his/her business. The client will not accept the new system unless it includes all these functions .
ii. Non-Functional Requirements
This refers to functions (e.g. security, performance, usability, portability) that are essential but which are not directly related to the business. The client will also insist on these features.
The developed system will be evaluated against these requirements. All the functional requirements as well as all or most of the non-functional requirements must be present in the new system. Otherwise, the client will not accept the system, and the system will be considered as a failure.

36
2.11.3 Design
In this phase, the system developer proposes a system design that will solve the client’s problems or seize a business opportunity. System design is concerned with how the final system will work. It includes process design, database design, interface design and network design.
i. Process Design
Process design describes how the functions (or modules) of an information system are structured (organised) and how they will interact with one another to perform the various business tasks. One approach typically used is to decompose (break up) the system (e.g. the application) into several high-level modules. Then each of these highlevel modules is further decomposed into lower-level modules, and so forth. This is done in such a way that each module is small and manageable and does a specific task (or a set of related task).
A structure Chart (SC) is typically used to show the hierarchy of the modules in a system. The higher-level modules describe higher-level functionality while the lowerlevel modules describe the detailed functionality. The higher-level modules call the lower-level modules to perform the needed tasks.
It is also necessary to show where the data for the system originates (data source), who or which system will eventually receive the output, how the data flows through the system (processes), what each process does to the data and what files (data stores) it will use.
The logic for each process must also be included. This usually takes the form of
Structured English. Each process describes the input it receives (from the data source or

another process), the processing it does, the file it uses, and the output it sends (to the destination or another process).
37
Process design thus captures the functionalities of a system. Eventually, the process design leads to the production of code. ii. Database Design
Database design is concerned with identifying the business entities relevant to the application, and how they are related to one another (e.g. the business rules). It is also concerned with identifying the attributes needed for each of the entities. The Entity
Relationship Diagram (ERD) is usually used to present this information graphically.
The entities are then converted to a set of a set of tables and their relationships
(one-to-one, one-to-many, etc) established.
Interface design is concerned with how the users will use the functionalities provided in the system. Typical user interfaces will include menu system, command buttons, dialogue, text, list, check and combo boxes, option buttons, frames, scroll bars, and image and timer. Interface design is also concerned with the use of colours, animation, pictures and audio.
The main concern in interface design is that it must be simple and easy to use. It must appeal to users, easy to navigate, minimise user errors, easy to undo, consistent, and which causes less strain to the body.

38
Network design is concerned with the architecture of the system when it is implemented in a geographically distributed environment. It describes the network architecture/ topology, and protocols and communications devices used to transmit data from one site to another.
2.11.4 Implementation
Implementation is concerned with writing code for the various modules and then testing them for errors. A suitable language (e.g. Visual Basic, Visual C++, Java) is selected and codes are written for each module. The coding is done using accepted coding standards.
Testing is done in stages. First, each module is tested using suitable test data.
This is called module or unit testing. There are several approaches one can use to test the modules such as statement testing, branch testing and path testing. After all the modules have been tested individually, they are integrated and tested again to check for errors in linking the modules. This is called integration testing. There are several approaches one can use such as bottom-up, top-down, or a combination of both. After the integration test, the system is tested to see if it meets all the functional and performance requirements.
After the database has been designed and codes for the modules have been written and tested, the system is ready for installation. The current system (if any) is replaced with the new system using a suitable approach (e.g. parallel, phased, direct).
The system is now in production (operational).

39
2.11.5 Maintenance
Although maintenance is not part of system development, it is an important phase in the system development lifecycle (SDLC). Studies have shown that about 60% to 70% of all IT budget goes to maintenance. All systems undergo changes due to several reasons such as (undiscovered) errors, new business requirements, performance improvement, and changes in the environment. That means changes must be made to the system as and when they are required. The system must be maintained throughout its life. This involves committing adequate resources top maintain the system until the system becomes obsolete and a new system is needed.
2.12 Landscape Information System
The application of information systems has recently involved landscape management and maintenance works. Plant cataloguing, ecological monitoring, project tendering, outsourcing, fertilising scheduling, are among the works involved in landscape management and maintenance that have utilised information systems in their undertakings.
While a landscape information system is developed based on the requirements of a landscape oriented organisation, a number of the most common components in a landscape information system have been outlined by Parker (1989). The components include Policies and Guidelines, Maintenance, Plant Inventory, Operations Inventory,
Equipment Inventory, Damage and Defect Reports, Maintenance Report, Project
Inventory, and Finance, as shown in Table 2.4.

Table 2.4. The Most Common Components of A Landscape Information System
Maintenance
Projects
Finance
Components
Policies & Guidelines
Plant Inventory
Equipment Inventory
Operations Inventory
Defect/ Disease & Insect Reports
Contents
ƒ
Environmental policies
ƒ
Organisational policies
ƒ
Landscape policies
ƒ
Maintenance guidelines
ƒ
Plant names
ƒ
Number of plants
ƒ
Suppliers
ƒ
Prices
ƒ
Soft landscape maintenance
ƒ
Hard landscape maintenance
ƒ
Water features
ƒ
M&E
ƒ
Equipments
ƒ
Prices
ƒ
Year of purchase
ƒ
Condition/ Performance
ƒ Personnel
ƒ
Contractors
ƒ
Suppliers
ƒ
Soft landscape
ƒ
Hard landscape
ƒ
Water features
ƒ
Projects
ƒ
Implementation
ƒ Cost
ƒ
All pertaining financial matters
40
Source: Parker (1989)

41
A number of landscape information systems have emerged throughout the years in order to further improve landscape management and maintenance works. The followings are among the landscape information systems that have been developed.
2.12.1 The Putrajaya Lake & Wetland Management Operational System
(PLWMOS)
Putrajaya Lake & Wetlands Management and Operational System (or
PLWMOS) is an environmental monitoring and environmental decision support system that serves as the main environmental database and spatial analytical tool for the current survey of hydrological, physico-chemical, and biotics parameters of Putrajaya lake and wetlands.
The PLWMOS system comprises of functionalities for data entry, environmental modeling and report generation, particularly to serve as an early warning system to alert for potential environmental problems. Development of PLWMOS system is independent of any other existing systems within CMC. However, the system has the capability to be linked to the existing systems within CMC. The Putrajaya management has stressed on the need for the system to be linked to Putrajaya Portal, which currently is in development stage.
The objectives of PLWMOS can be divided into both short term and long term objectives. In short term (within 1 year time frame), PLWMOS is aimed to achieve the following objectives:
ƒ
To provide data entry module for scientists & technical consultants.
ƒ
To setup a centralized, easily accessible, and integrated environmental database management system.

ƒ
To develop monitoring & environmental assessment modules based on techniques and models within the scope as advised by the sectoral consultants.
ƒ
To develop and provide means for internet based report submission and assessment module (data reports and results visualization).
ƒ
To develop an early warning system to alarm for potential environmental problems.
42
The above objectives are the main aims of the system. In the long run, the system is intended to achieve the following objectives: i. Total lake management system, which include maintenance scheduling, asset management, contractual and payment system, and environmental forecasting and decision support system. ii. The system as a tool to encourage further R&D work on the lake eco-system. iii. The system as a tool to promote awareness and environmental education as well as promotional and marketing tools.
The system consists of the nine (9) main components as illustrated by Figure 2.1.
These main components can further be sub-divided into modules of applications. As an example, Online Report Submission and Approval has the following main modules:
ƒ
Online report submission module for each sector (total of 13 monitoring sectors)
ƒ
Online report endorsement module (for main contractor)
ƒ
Online report assessment and approval module (for management)
ƒ
Online report viewing module
ƒ
Online report commenting and discussion board module
ƒ
Due date alert and reminders module for each activity

43
ƒ
Online report archiving module
ƒ
Work status and workflow reporting module
Web-Based
DBMS
System
Administration
1 page Decision
Support Info
Online Report
Submission &
Approval
PLWMOS
Web- Based
GIS
Alert
Response /
Action Guide
Alert System
Telemetric
Monitoring
Management
Tool
Figure 2.4. PLWMOS System Components
(Courtesy of Putrajaya Corporation)
The various application components, their main modules, and their general functionalities are as listed in Appendix 1.
PLWMOS is as an e-environmental reporting system which offers the following benefits:
ƒ
A centralized monitoring database system accessible to permissible users from almost anywhere
ƒ
An online report submission facility

44
ƒ
An online lake and wetlands discussion board
ƒ
An online and integrated data and report archiving system
ƒ
An online spatial mapping system of Putrajaya lake and wetlands environment
ƒ
Alert and messaging system to aid management and monitoring of
Putrajaya lake and wetlands environment
ƒ
Dissemination of Putrajaya lake and wetlands information to the general public through web page.
ƒ
A management tool to support daily operations, work coordination, as well as triggering response action whenever necessary.
PLWMOS has been designed as an open system – with capability to be expanded in the future. The management may consider future expansion of PLWMOS into a decision support system and incorporating other management modules to support the management, maintenance, and the sustenance of Putrajaya lake and wetlands environment.
2.12.2 The Arbor Tracker System
The Arbor Tracker System has been recently developed by the Forestry Research
Institute of Malaysia (FRIM) to catalogue trees systematically. The system utilizes
Personal Digital Assistance (PDA) that enables it to communicate with smart tags with
Radio Frequency Identification (RFID) capability that are implanted an inch deep in the trunk of the trees. The PDA equipped with Bluetooth technology will detect the tags and display the information on screen.

45
Among the information included in the system are botanical names, plant origins, plant diameters and heights, and date of the most recent maintenance works undertaken for each tree that include trimming, fertilizing and insect control. Figure 2.5 shows the tree information displayed in the Arbor Tracker PDA and Transponder Terminal.
The Arbo Tracker PDA The Arbo Tracker Transponder Terminal
Figure 2.5. The Arbo Tracker PDA and Transponder Terminal
(Courtesy of Utusan Malaysia, 2005)
2.12.3 The Landscape Management System (LMS)
The Landscape Management System (LMS) is an evolving set of software tools designed to aid in landscape level management of forest resources. LMS is being developed as part of the Landscape Management Project at the Silviculture Laboratory,
College of Forest Resources, University of Washington.

LMS is a computerized system that integrates landscape level spatial information, stand-level inventory data, and individual tree growth models to project changes through time across forested landscapes. LMS facilitates forest management planning, policy-making, as well as education.
46
LMS coordinates the execution and information flow between many different computer programs (40+). These programs: format, classify, summarize, and export information; project tree growth and snag decay; manipulate stand inventories; and present stand and landscape level visualization and graphics.
The Landscape Management Project is a cooperative project between the
Silviculture Laboratory, College of Forest Resources, University of Washington and the
USDA Forest Service, Pacific Northwest Research Station.
The Landscape Management Project was created to investigate methods and facilitate techniques for the management of forested landscapes. One focus of the project is to emphasize management over broader temporal and spatial scales. Funding for the project was initiated through the efforts of Congressman Norm Dicks. A major effort of the Landscape Management Project is to integrate and/or develop necessary technologies to facilitate landscape level management.
The Landscape Management System (LMS) integrates forest inventory information, geographic information, computerized growth models, decisions support systems, and other applications to facilitate landscape, ecosystem, and watershed management. LMS projects changes in individual stands and landscapes up to 50,000 acres; it can be used on any forested region for which there is a growth model and appropriate inventory information. LMS can be used for management, planning, policymaking, and education. It has been designed with the following features:

47 i. Modular
It can incorporate all forms of inventory data, geographic information, growth models, and decision support systems; various parts of the system can be replaced as new information and techniques become available or they can be used as components in other computerized systems. ii. Flexible
LMS works with a representative tree list. By maintaining the large amount of information about stands contained in a tree list, LMS can incorporate new management objectives and measures that can be linked to the tree list information. iii.
Easy to Use
LMS is a Microsoft Windows application and operates in a point and click manner. iv. Project Growth
LMS projects growth at the stand and landscape levels using existing growth models (of your choice). Changes in stands and landscapes can be projected over time under different management regimes.

48
LMS, in concert with the Stand Visualization System (SVS) and UVIEW, provides visualizations of the projected stands and landscapes and can be used to provide information on changes in habitats, susceptibilities to fire, etc., along with wood quantity and quality in graphic and tabular forms.
LMS coordinates the activities of various pieces of software that, in combination, can be used for the management, projection, summarization, and visualization of information about stands on the landscape. It is an integrative effort that combines technologies and available software into a comprehensive system that facilitates landscape level planning, management, and analysis.
In LMS, landscapes are composed of stands. These stands are projected through time using available forest projection models (growth and yield or successional).
Existing models are incorporated into the system using data filters that translate and reformat data as needed to accommodate the projection and analysis systems. Other attributes of a stand can be projected by providing projection models for those attributes.
The stands in LMS are represented by a tree list for each stand. The tree list includes species, diameter, height, trees per acre, and other attributes for trees in the stand. Stand average information can also be used. These tree lists are the basic unit of projection and allow LMS to be flexible because information about individual trees on the landscape is maintained as the stands are projected.
Figure 2.6 shows some of the screen shots of the LMS.

Table Dialogue Box Landscape Inventory Table
Landscape Visualisation
Figure 2.6. Information displays in the LMS
(Courtesy of College of Forest Resources, University of Washington)
49

50
2.13 Conclusion
Understanding the components of landscape management and the various techniques and approaches in the development of an information system is important in order to develop a landscape management system that is able to fulfill the expectations and requirements of the client/ user. Relatively new, the application of information system in landscape management demands the top managers, users and the system developer to truly understand the nature and needs of the operation if an effective and useful landscape management system is to be achieved.

51
Chapter 3
CASE STUDY
3.0 Introduction
This chapter mainly talks about the background of Pejabat Harta Bina. Focus shall be given on the different units that make up Pejabat Harta Bina and the scope of work as well as the work process that they practice. A qualitative analysis on the requirements of Pejabat Harta Bina, based on interviews are also discussed in this chapter. Understanding these aspects is important to enable the researcher to design a system that will conform to the requirements of Pejabat Harta Bina.
3.1 The Background Of Pejabat Harta Bina
Formed in the year 1973, Pejabat Harta Bina which was previously known as
Pejabat Pengarah Kerja functions to implement the physical development of the campus, maintain existing assets, provide facilities management services throughout the campus and other support services such as transportation services and event management and preparation.

The first structure of Pejabat Harta Bina in 1996 (known as Pejabat Pengarah
Kerja as that time) was divided into the following units:
52 i) Unit Penyenggaraan dan Ubahsuai
This structure was so formed to ease the office’s operation based on the field of works that have been assigned.
In the year 2000, a restructuring of the office was performed where Pejabat
Pengarah Kerja was divided into 2 main technical parts which are:
The restructuring of Pejabat Pengarah Kerja had lead to the change of the name of the office, hence known as Pejabat Harta Bina.
Under the field of works of Bahagian Harta, a number of units were formed to support and further increase its efficiency that are: iii) Unit Perkhidmatan Aset
Some 163 staffs are appointed under the management of Bahagian Harta with the following division:

53 i) Officer A ii) Officer B iii) Officer C - iv) Officer D -
-
-
7 personnel
12 personnel
60 personnel
84 personnel
3.2 Scopes & Responsibilities
Bahagian Harta, Pejabat Harta Bina is responsible in managing and implement maintenance works, modification, transportation and event preparations.
Maintenance works consist all buildings, areas and infrastructures as follows: i) 1,114 hectares (2,752 acres) campus area. ii) 405 hectares (1000 acres) developed campus area. iii) 430 building blocks with a floor area of approximately 476,300m
2
.
iv) 26 electric distributor stations of 22kV each. v) 2 water tanks with the capacity of 1.5 million gallons each. vi) 8 packages of centralised air conditioners that uses the Chiller System with the capacity of 250 tonnes to 400 tonnes of refrigerant. vii) 8 packages of centralised air conditioners that use the Water Cooled Package with the capacity of 10hp to 30hp. viii) 254 university vehicles.
Modification works involve all building spaces including planning and standardisation of space use and the provision of equipment for learning purposes.
Asset services include the provision of transportation facilities for academic and staff activities. Asset services also include preparations of various that events such as convocations, seminars, conferences, sports, recreational events, etc.

54
RM 20 million to RM 30 million is received each year for the management of utilities, maintenance, modifications, transportation, events and all other works involved under the management of Bahagian Harta.
3.3 The Field of Work For Each Unit
Generally, there are 3 main divisions of work for each unit: iii) Unit Perkhidmatan Aset
The maintenance works that are undertaken include civil works, mechanical, electrical and landscapes. This unit is responsible in ensuring the smooth running of the university’s operations and activities as well as safe and conducive space and environment.
This unit is divided into a number of services that are: i) Operation ii) Engineering iii) Services

55
The maintenance scope of work comprise of all buildings, facilities and building equipment, cleaning and university assets in the campus (does not include assets that are bought and managed by faculties or departments) and university vehicles.
3.3.2 Unit Ubahsuai
The services provided by this unit include modification works and space upgrading, based on standards that have been commissioned by the university. This unit is responsible in ensuring that all modification works can be implemented effectively and meet the expected quality.
3.3.3 Unit Perkhidmatan Aset
Transportation and preparation for events in the campus is under the responsibility of this unit. All transportation facilities and preparations for events that include decorations, equipment, etc. are managed and provided by this unit.
3.4 Landscape Development in UTM
Green areas in the UTM campus consist of 1008.48 acres. A few landscape development projects have been undertaken in order to utilise the green areas. Pejabat
Harta Bina has been given the responsibility to implement all landscape planning, development and management works for the whole campus. Among the best landscaped areas in the campus are the Tropical Park and the internal courtyard within the UTM
Administration Building.

56
The Tropical Park is divided into 4 zones that are Laman Bistari, Laman Seni,
Laman Menanti and Laman Riadah. Until now, only Laman Riadah has been developed as the first phase of the project. The internal courtyard within the UTM Adiministration
Building was constructed in 1987. The design concept assimilated tropical characteristics in order to complement the architecture of the building.
In the year 2001, UTM had received a total of RM270, 340.00 from Jabatan
Lanskap Negara under the landscape upgrading programme for the development of
Alpinia and Heliconia gardens in the Tropical Park. Figures 3.1 and 3.2 shows the development of landscape areas in UTM.
Tropical Park
Orchard
Golf driving range
Ethnological Park
Orchard
Figure 3.1. Landscape development in UTM

57
Tropical Park
Figure 3.2. Tropical Park UTM
3.5
UTM’s Landscape Maintenance System
The landscape maintenance system in UTM is based on contract system. The contract is usually offered to contractors who will carry out the landscaping works as stated in the tender document. The time frame of carrying the tasks is based on the terms in the tender document as agreed between Pejabat Harta Bina and the contractors. All landscape maintenance works are obligated by the contractors while Pejabat Harta Bina is responsible in planning the scope and schedule of the maintenance works as well as monitor and control the works undertaken by the contractors.
3.6
Implementation Of Landscaping Works in UTM
The implementation of landscaping works in UTM is divided into 6 main parts that are general cleaning landscaped areas, mature trees maintenance, immature trees

maintenance, small trees maintenance, ground cover maintenance, & special turf maintenance. The details of each of the work are shown in the following tables:
58
Table 3.1. Cleaning
Types of Maintenance
Existing, fallen and dead trees/ plants
Debris, trash
Source: PHB, UTM
4 X / week
4 X / week
Frequency
Table 3.2. Mature Trees Maintenance
Types of Maintenance
Weeding (Landscaped areas must be free of weeds by using suitable methods and materials)
Fertilising ( To be carried out after weeding. Must use suitable fertilizers)
Watering (Plants must be watered sufficiently & water absorption rate not less than 8” into the ground)
Trimming (Must use suitable equipment.
Dead, unhealthy branches & twigs must be removed)
Insect & disease control (Plants must be inspected for insects & diseases.
Immediate treatment & control if encountered)
Source: PHB, UTM
Frequency
2 X / Year
2 X/ Year
5 X/ Year (When instructed)
3 X/ Year
3 X / Year

Table 3.3. Immature Trees Maintenance
Types of Maintenance
Weeding (Landscaped areas must be free of weeds by using suitable methods and materials)
Fertilising ( To be carried out after weeding. Must use suitable fertilizers)
Watering (Plants must be watered sufficiently & water absorption rate not less than 8” into the ground)
Trimming (Must use suitable equipment.
Dead, unhealthy branches & twigs must be removed)
Insect & disease control (Plants must be inspected for insects & diseases.
Immediate treatment & control if encountered)
Source: PHB, UTM
Frequency
2 X / Year
2 X/ Year
5 X/ Year (When instructed)
3 X/ Year
3 X / Year
59

60
Table 3.4. Small Trees Maintenance
Types of Maintenance
Weeding (Weeds to be removed together with their roots or rhizomes)
Fertilising ( suitable fertilizers at fixed time & quantity)
Watering (Plants must be watered sufficiently & water absorption rate not less than 8” into the ground)
Trimming (Must use suitable equipment. Dead, unhealthy branches & twigs must be removed)
Insect & disease control (Plants must be inspected for insects & diseases. Immediate treatment & control if encountered)
Plant replacement (Dead or unhealthy plants are to be replaced with suitable plants)
Source: PHB, UTM
Frequency
1 X / month
6 X/ Year
4 X/ month (When instructed)
6 X/ Year
4 X / Year
To be informed to PHB.
Table 3.5. Ground Cover Maintenance
Types of Maintenance
Weeding (Weeds are to be removed with their roots are by applying suitable weed poison)
Fertilising ( Suitable fertilizers at fixed time & quantity.
Must be evenly spread & not in heaps)
Watering (Plants must be watered sufficiently especially during dry season)
Trimming (Must use suitable equipment & method)
Insect & disease control (Plants must be inspected for insects & diseases. Immediate treatment & control if encountered)
Source: PHB, UTM
Frequency
1 X / Month
6 X/ Year
14 X/ Month
2 X/ Month
4 X / Month

61
3.7
The General Landscape Work Processes Of Pejabat Harta Bina
The landscape development and maintenance work processes involve Bahagian
Pembangunan, Bahagian Pengurusan Kontrak & Harta, and Unit Penyenggaraan &
Ubahsuai, Bahagian Harta. The following figure demonstrates the general landscape work processes of Pejabat Harta Bina.
Unit Landskap,
Bahagian Pemb angunan
Propose & design
Landscape development proposal
Landscape development BQ preparation Bahagian Pengurusan
Kontrak & Harta
Tendering to contractors
D E V E L O P M E N T P H A S E
Unit Penyenggaraan &
Ubahsuai
M A I N T E N A N C E P H A S E
Maintenance schemes & detailings
Maintenance budget
Bahagian Pengurusan
Kontrak & Harta
Landscape maintenance
Landscape modification
Plant ordering
ƒ
Define/ redefine scope & schedules
ƒ
Monitor progress
ƒ
Evaluation
ƒ
Site Modification
ƒ
Hardscape modification
ƒ
Order plants from suppliers
ƒ
Order plants from UTM Nursery
Tendering to contractors
& suppliers
Contractors/
Suppliers appointed
Fertiliser ordering
Equipment provision
ƒ
Order fertilisers from suppliers
ƒ
Order equipment
ƒ
Monitor equipment condition & availability
Figure 3.3. The General Landscape Work Processes Of Pejabat Harta Bina, UTM
(Courtesy of Pejabat Harta Bina, UTM)

62
3.8 The Work Process of Landscaping Works, Unit Penyenggaraan & Ubahsuai
Bahagian Harta
Unit Penyenggaraan & Ubahsuai Bahagian Harta, Pejabat Harta Bina has recently been awarded the Quality Management System ISO 9001:2000, where all works under this unit are based upon.
The implementation scope of the SPK ISO 9001:2000 BH-PHB UTM, Skudai comprise of Facilities Services Management that covers four main services, that are:
ƒ
Maintenance
ƒ
Space modification and building facilities
ƒ
Transportation
ƒ
Event preparation
Landscaping works that include landscape maintenance and modification are part of the scope of work of this unit. The work process of landscape maintenance and modification are as shown in the following figures 3.4 and 3.5.

Commence
Identify Maintenance
Works
Distribution
63
Input
User requirements towards facilities that have been identified through complaints, user’s requests and university’s requirements, system operation manual and equipment maint enance
To plan maintenance works based of fixed schedules. To receive and attend user complaints through SiLK, letters, email, telephones, fax, and direct instruction from the university’s m anagement.
To distribute works according to discipline, level, type and location of work.
Inspection
Improvement by BH staffs
Implementation of works
Work through contractor
Acquisition
To identify the cause of problems and solution proposals.
To manage maintenance works through fixed and permitted acquisitions.
To implement and complete site works or observe and control contractors that implement maintenance works based on user requirements, specifications and regulations.
Output
All systems and equipment function perfectly and safe to be used
Client’s certification
& valuation
To ensure clients are satisfied with the service provided through certification of work completion and valuation of the implemented works.
Payment & record
To pay contractors, inspection reports on the performance of contractors and record all work details.
End
Figure 3.4. Landscape Maintenance Work Process
(Courtesy of Bahagian Harta, Pejabat Harta Bina, UTM)

Commence
Planning & Determining
Modification & Upgrading
Works
Site & client’s requirements studies
64
INPUT
Application of client’s requirements towards modification works and facilities
Planning and determining modification works based on client’s requirements, instructions from the university’s authorities and current requirements.
To carry out feasibility studies on the alternatives to ensure the modification works fulfil client’s requirements, cost effective and in accordance to the university plans.
Not
Approved
Approval
Draw
Design Preparation
Manage Acquisitions
Work Implementation & Site
Observation
Site submission to client
To gain approval to carry out modification works from the
Director of Bahagian Harta, Pejabat Harta Bina.
To provide and improve designs to elevate and enhance the image of the university.
To determine the type of acquisitions based on scopes and work priority. The appointment of contractors is made in the acquisition process.
Implementation of work on site by contractors and work s are supervised to ensure that works are carried out at the specified quality and time perio d.
Completed works will be tested to ensure functionality and safe to use by the clients.
OUTPUT
Modification works that completely follow specifications, quality, function and safe to be used by clients.
Payment to contractors
To manage payments and produce Contractor’s Performance
Valuation Report and to record inventories.
End
Figure 3.5. Modification Work Process
(Courtesy of Bahagian Harta, Pejabat Harta Bina, UTM)

These processes are to be translated into the proposed system of this research where the system has to be able to carry out the same work processes in digital form.
65
3.9 Requirement Analysis: A Qualitative Approach
Qualitative analysis method is used in analysing the requirements of the
Landscape Management System for Pejabat Harta Bina. The selection of a qualitative approach for the analysis is based on the very nature of the data acquired in this research. The data gathered in this research mainly involve processes, observations, interpretations, translations, assumptions, expectations and logic. Van Manen (1977) stated that qualitative analysis methods are fundamentally well-suited for locating the meanings people place on events, processes and structures of their lives: their perceptions, prejudgments, assumptions and presuppositions.
The data in this research are acquired through interviews with a number of
Pejabat Harta Bina’s staffs on the requirements of a Landscape Management System to suit their needs. Hence, the data themselves are qualitative in nature that demands a qualitative approach of analysis. Qualitative data is a source of well-grounded, rich descriptions and explanations of processes in identifiable local context. With qualitative data, one can preserve chronological flow, see precisely which events led to which consequences, and derive meaningful and fruitful explanations (Amaratunga, Baldry,
Sarcshar and Newton, 2002). Jones (1997) stated:
ƒ
Qualitative methods, especially observation, or unstructured interviews, allow researchers to develop an overall picture of the investigation
ƒ
Qualitative methods are concerned with researches that involve affective characteristics, as well as overall behavioural aspects. Thus, a qualitative ‘core’ is appropriate to investigate such aspects by examining the informant’s point of view.

ƒ
Most researches are still largely exploratory. The use of qualitative methods allows for unexpected developments that may arise as part of such researches.
66
As mentioned earlier, the data in this research are acquired through interviews with a number of Pejabat Harta Bina’s staffs on the requirements of a Landscape Management
System to suit their needs. Research interviews are the most widely used qualitative method. It is a highly flexible method and can be used almost anywhere, and is capable of producing data of great depth. (King, 1994). Kvale (1996) defines the qualitative research interview as an interview, whose purpose is to gather descriptions of the lifeworld of the interviewee with respect to interpretation of the meaning of the described phenomena. The goals of any qualitative research interview are therefore to see the research topic from the perspective of the interviewee, and to understand how and why they come to have this particular perspective (Amaratunga, Baldry, Sarcshar and
Newton, 2002).
3.10 Pejabat Harta Bina’s Requirements Of A Landscape Management System
The Bahagian Harta, Pejabat Harta Bina is currently facing a problem of not having a proper system of archiving its landscape related information that include landscape features, landscape plans, contractors, maintenance schedules, costs, etc. The researcher’s experience of attempting to acquire these data has shown that there is no proper archiving system and information ore often misplaced or needs to be referred to various other departments that may possess the information. Even a simple planting plan for the landscape areas in UTM demands strenuous efforts of searching within and beyond Unit Penyenggaraan Bahagian Harta, Pejabat Harta Bina.

67
Hence, an interview conducted by the researcher with the personnel in charge of
UTM’s landscape development and maintenance En. Mohd Faizal Bin Suleiman has resulted with the following requirements that are in great need. i. An archiving system of landscape features including soft landscapes and hard landscapes.
ii. A system that records all maintenance works including types of works and dates of the works that have been carried out. iii. An archiving system of contractors that have been appointed for landscaping works in UTM. iv. A system that has the ability to report to the management matters pertaining to defects, disease control, etc. v. A system that monitors the growth and well-being of plants. vi. A system that has the ability to quantify the cost of landscaping works that include maintenance and modification. vii. A system that can be assessed (partially) by the public in order to create awareness of the environment, provide landscape information, as well as to promote the image of UTM through its landscape developments. viii. A system that can replace the manual process of landscape maintenance and modification works (as in 3.7) ix. A system that stores and permits retrieval of digital landscape plans with the ability of editing, especially for areas that often undergo replacement of plants.
3.11 Analysis On The Requirements Of The Proposed System
The analysis on the requirements of the system to be developed for Bahagian
Harta, Pejabat Harta Bina comprise of the followings:

68 i. Valuating The Problems
It is clear that Pejabat Harta Bina does not have any existing system to archive its landscape related information. The major issue here is being able to retrieve the information needed with ease, and without having to refer to various parties that include different departments. Pejabat Harta Bina should have all information pertaining to
UTM’s landscape projects. ii. Requirement Classifications
Based on interviews and observations, the requirements of the Unit
Penyenggaraan & Ubahsuai in Bahagian Harta, Pejabat Harta Bina can be divided into 3 categories: a. Mandatory
These include modules on landscape elements, maintenance scopes and schedules, cleaning, list of contractors and suppliers, digital plans and equipment inventory.
b. Important
These include modules on fertilisers, upgrading, and defects. c. Needed In Time
These include modules that may be required in the future and the system should be able to allocate these modules when required. The modules are tendering, landscape

information for the public, landscape literatures, plant growth monitoring and water quality monitoring.
69 iii. Feasibility
All units in Bahagian Harta, Pejabat Harta Bina use Windows XP as operating system. Hence the proposed system should be compatible with the Windows XP environment.
The staffs of the Unit Penyenggaraan Bahagian Harta are all computer literate and familiar with graphic software. However, their exposure to a management system that mostly involve database modules is limited, hence demand the interface of the system to be user-friendly with minimal complex instructions and procedures.
As landscape plans are all prepared using AutoCad, the system must be able to support AutoCad drawings, preferably with the ability of editing the drawings. Digital photos are also used by the Unit Penyenggaraan in Bahagian Harta, Pejabat Harta Bina to catalogue landscape elements, hence the system has to be able to store image files such as JPEG and BITMAP files.
Identification of data required by the system is essential for the operation of the system. For this task, it is important to identify the data involved in the landscape scope of work as practised by Pejabat Harta Bina in general, and its departments that are responsible in UTM’s landscape development and maintenance. Table 3.6 shows the type of data involved in Pejabat Harta Bina’s landscape scope of work.

70
Table 3.6. Types Of Data Involved in Pejabat Harta Bina’s Landscape Scope Of Work
Department/ Unit
Bahagian
Pembangunan
Unit Penyenggaraan
& Ubahsuai,
Bahagian Harta
Scope Of Work
ƒ
Design
ƒ
Development
ƒ
ƒ sheme
Soft landscape maintenance
Hard landscape maintenance
Data Required
ƒ
Site plan
ƒ
Plant types list
ƒ
Frequency
ƒ
Date of planting
ƒ
Plant price
ƒ
ƒ
Suppliers
Disease/ Insect control
ƒ
Function
ƒ
Landscape masterplan
ƒ Planting schemes
ƒ
Date of maintenance
ƒ
Contractors
ƒ
Hard landscape types
ƒ
Frequency
ƒ
Date of construction
ƒ
Date of maintenance
ƒ
Materials
Data Produced
ƒ
ƒ
Planting schemes
ƒ Working drawings
ƒ
Detail drawings
ƒ
Maintenance scopes
ƒ
Schedules
ƒ
Plant type list
ƒ
Track records
ƒ
Evaluation
ƒ
Landscape masterplan
Maintenance scopes
ƒ
Schedules
ƒ
Track records
ƒ
Evaluation

ƒ Modification
ƒ Contractors
ƒ
Defects
ƒ
Landscape masterplan
ƒ
Working drawings
ƒ Detail drawings
ƒ Landscape masterplan
ƒ
Working drawings
ƒ
Detail drawings
ƒ
Plant types
ƒ ƒ
Suppliers
ƒ Ledger reg. number ordering provision drawings
(modified)
(modified) specification
Number
ƒ
Fertiliser types
ƒ
Name
ƒ Form
ƒ
Chemical composition
ƒ
Expiry date
ƒ
Suppliers
ƒ Manufacturer
ƒ
Storage location
ƒ
Stock availability
ƒ
Equipment type
ƒ
Name purchase
71

UTM Nursery
Bahagian
Pengurusan Kontrak
& Harta (Senior
Technical Assistant)
Bahagian
Pengurusan Kontrak
& Harta (Senior
Store Officer)
ƒ
Plant provision
ƒ
Plant ordering
(supplemental)
ƒ
Equipment purchasing/ leasing
ƒ Equipment storage
ƒ Serial number
ƒ
Frequency
ƒ
Price
ƒ
Suppliers
ƒ
Manufacturer
ƒ
Equipment
Status
ƒ
Storage location
ƒ
Date of maintenance
ƒ
Plant types
ƒ
Frequency
ƒ
Plant specification
ƒ
Ledger reg.
Number
ƒ
Suppliers
ƒ
Equipment suppliers
ƒ
Equipment type
ƒ
Equipment price
ƒ Equipment type
ƒ
Serial number
ƒ
Frequency
Source: Pejabat Harta Bina verification
ƒ
Date of purchase
ƒ Storage location
ƒ
Equipment
Status
72

73
The scopes of work shown in Table 3.6 should be translated as modules in the proposed system where each scope of work is undertaken by individual module. The required and produced data on the other hand shall be stored in a database that stores these data and retrieved by the modules top carry out the different tasks as stated in the
Scope O Work column.
3.12 Ready Systems Versus Customised System
Looking into this matter, it is important to look into the large and small picture of the situation. It has always been debated whether it is more viable and more cost effective to purchase a ready-made system or to customise own system for the undertakings of the business processes of an organisation.
The management needs to truly understand what is needed and what is not prior to the purchasing of a system. A system may seem advance and tempting due to the various modules and functions it offers, yet in most cases, those modules and functions are under-utilised if not completely left aside in the organisation’s business operation.
One may look into the comprehensiveness of the system but comprehensiveness may not be what is needed by the organisation. A look into the survey conducted by the
University of Massachusetts in 2001 on a few CAFM systems has resulted with the following response from the users as shown in Table 3.7.

74
Table 3.7. CAFM System Users & Functionality
Systems Users What functions of the system are implemented but least used (and why?)
Aperture University of
Arkansas
Archibus University of Illinois-
Chicago
FM Systems Baylor Medical
There are some functions, such as zooming to a room on a floor plan from data query that are more sizzle than steak.
There are a lot of detailed columns of information that we don’t have use for.
Strategic Planning & Asset Management.
Consultants are used for planning. Asset
OFMS
Prism
MIT
Rochester management is done in the college’s SAP system.
The asset management module because it has been maintained by a separate department (for political reasons)
There is a reporting function in the system, but it is worthless, as the canned reports do not provide useful information. We just used Crystal
Reports to write our reports and circumvented the report function entirely.
Source: CAFM System Peer Review, University of Massachusetts (2001)
From the above survey, it can be seen that most ready-made systems equipped with various modules and functions are not entirely utilised by the users due to specific needs of the users that are not catered by the systems. This is in no way a surprise as every organisation has its own needs with regards to the scope and processes of its business operations. Hence, the cost effectiveness of purchasing the system is questionable.

75
In the case of Pejabat Harta Bina, UTM, a ready-made system is in the same way not viable as it has its own approach in the undertakings of its business operations. The rareness of a landscape management system let alone a ready-made landscape management system adds to the argument. Pejabat Harta Bina needs a landscape management system that can truly cater its landscape management works and as landscape management is a mere portion of its whole operation, investing on a readymade system that will eventually be under-utilised should be avoided. This is also supported by En. Roslan Shariff, Civil Engineer at Bahagian Harta, Pejabat Harta Bina who had previously developed a number of customised systems for various organisations, that purchasing ready-made systems is only viable if the management is really confident that the organisation can fully utilise all the varying modules and functions offered. Some systems can be purchased by modules, which offer greater flexibility, yet the functions contained in the modules may not truly facilitate the operation of the organisation. En. Roslan further added that for Pejabat Harta Bina,
UTM, a customised landscape management system is the better choice.
Looking further into this issue, a number of other parties related to IT and landscape departments have been consulted to gain their opinions on customised and ready-made systems. The views and response of these parties are as shown below. i. Personnel :
Organisation/ Department :
En. Mohd. Faizal Afandi
KLCC Urusharta
KLCC Urusharta’s experience with PLWMOS (Putrajaya Lake & Wetland
Monitoring System) has shown that customised systems are more viable as clients can truly acquire a system that suites their needs as they know what functions that the system must be able to cater.

ii. Personnel :
Organisation/ Department :
En. Shahrulizam Abd. Rashid
Jabatan Landskap, Majlis Perbandaran
Johor (MPJBT)
(Development & Maintenance)
76
Landscape management differs from one organisation to the other. This ranges from landscape management at environmental scales to decorative landscape.
Hence, it is difficult to find a landscape management software in th e market that can meet the varying demands of various organisations. iii. Personnel :
Organisation/ Department :
Assoc. Prof. Dr. Ismail Said
Jabatan Senibina & Landskap,
Fakulti Alam Bina, UTM
Position : Lecturer
Computerised landscape management tools are still new and for the time being, it is more advisable for an organisation to customise its own system to isolate its own requirements that may not be fulfilled by ready-made systems.

: En. Muhammad
Organisation/ Department : Unit GIS Perancangan (UGISP)
77
Existing management systems and GIS software have been known to be applied in landscape management. However, numerous functions and modules are mostly under-utilised. Existing landscape management systems are rare and other management systems do not possess the specific functions required in landscape management. GIS on the other hand is more viable for tasks that involve data analysis and modelling, hence will most probably be under-utilised when applied for landscape management that consists of mainly inventories.
From the facts stated above and the limited time to comprehensively explore all available ready-made systems in the market, it is concluded in this research that a customised landscape management system is more viable for landscape management works at Pejabat Harta Bina, UTM.
3.13 Summary Of The Analysis
Based on the findings in this chapter, a summary of the analysis on Pejabat Harta
Bina’s requirements of a landscape management system as shown in Table 3.8 is produced:

78
Table 3.8. Pejabat Harta Bina’s Requirements Of A Landscape Management System:
Summary of The Analysis
Item Remarks
Existing systems
Type of system required
Required operating system compatibility
Required graphic support & compatibility
Interface
Information/functions to include
Future needs
Database entities
ƒ
ƒ
ƒ
ƒ
None
Customised
Windows XP
AutoCad, Image files
ƒ
User-friendly
ƒ
Landscape elements
ƒ
Maintenance
ƒ
Cleaning
ƒ
Contractors
ƒ
Suppliers
ƒ
Equipments
ƒ
Public landscape information
ƒ
Landscape literatures
ƒ
Plant growth monitoring
ƒ
Soft landscape
ƒ
Hard landscape
ƒ
Soft landscape suppliers
ƒ
Hard landscape suppliers
ƒ
Fertilisers
ƒ
Soft landscape maintenance
ƒ
Hard landscape maintenance
ƒ
Contractors
ƒ
Equipment
Source: Author’s Research (2005)
ƒ
Drawings/Plans
ƒ
Fertilisers
ƒ
Defects
ƒ
Modification
ƒ
Plant ordering
ƒ
Report
ƒ
Water quality
ƒ monitoring
Equipment suppliers
ƒ
Zones
ƒ
Drawings
ƒ
Fertiliser suppliers
ƒ
Defects
ƒ
Report
ƒ
Order information

79
3.14 Conclusion
Bahagian Harta, Pejabat Harta Bina is in need of a landscape management system that has the ability to properly organise landscape information to assist maintenance and decision makings. A number of emerging requirements have been identified through interviews parties responsible in landscape management of Bahagian
Harta, Pejabat Harta Bina and these requirements shall be the basis of the design of the proposed system that will be further discussed in Chapter 4.

80
Chapter 4
SYSTEM DESIGN
4.0 Introduction
This chapter elaborates on the proposed system that will solve the client’s problems and fulfil the requirements of a Landscape Management System as discussed in Chapter 3. This chapter discusses the modules to be incorporated in the proposed system, how the system works and the system’s database design. However, subsequent design processes that include interface design and programming are not parts of the scope of this research, hence not be included in this write up.
4.1 The Proposed Structure of The Landscape Management System
Based on the findings in Chapter 3, a number of modules that make up the system are proposed based on the requirements of landscape management works practiced by Pejabat Harta Bina.
The system allows users to operate the system with access to the various levels, controlled by username and passwords. Figure 4.1 shows the context diagram of the proposed system.

81
Bahagian Pembangunan
(Landscape Architect)
Planting schemes
Landscape
Development
Plans/ Reports
Maintenance scopes & schedules
Maintenance report
Plant order information
Order specifications
Unit Penyenggaraan,
Bahagian Harta
(Landscape Technical
Assistant)
Defects
Contractor
Development scheme
Site modification
Unit Ubahsuai,
Bahagian Harta (Chief)
Order verification
Plant order information
Order specifications
UTM Nursery
Order Order verification form
Suppliers
Legend :
Process
Entity
Figure 4.1. Data Flow Diagram (DFD) Of The Landscape Management System
Mainly, the users of the system that are Unit Penyenggaraan & Ubahsuai
Bahagian Harta, Bahagian Pembangunan and the UTM Nursery. Unit Penyenggaraan
Bahagian Harta uses the system mainly to catalogue information on maintenance scopes and schedules, producing reports on maintenance progress, evaluation, defects and

82 disease/insect threats . This unit also uses the system to submit orders to the UTM
Nursery for supplies of plants, either in-house supply or supplies from suppliers.
Unit Ubahsuai Bahagian Harta on the other hand, uses the system to retrieve development schemes set by Unit Landskap, Bahagian Pembangunan in order to analyse and evaluate modification possibilities when needed. This unit will also update the landscape schemes in drawings and specifications subsequent to the modification process to ensure availability of updated landscape development information.
Unit Landskap Bahagian Pembangunan, Pejabat Harta Bina utilises the system by providing landscape development plans and reports as well as planting schemes of landscaped areas. This ensures organised archiving system of landscape development plans.
The UTM Nursery receives orders for soft landscape elements via the system submitted by Unit Penyenggaraan Bahagian Harta. Order information and specifications are received and verification of the order is submitted via the system. This is followed up with the submission of the order verification form to Unit Penyenggaraan Bahagian
Harta.
4.2 The Proposed Modules Of The Landscape Management System
Development of the system is primarily based on modular approach allowing new add-on modules to be incorporated to the system for future expansion and development purposes. The system is divided into 5 main modules namely Maintenance,
Inventory, Reports, Contractors and Suppliers, and Drawings. Figure 4.2 demonstrates the process undertaken by each module.

83
1
Info Storage
Info Retrieval D1 LandInfoPHB
Info Storage
Info Retrieval
Contractor/ Supplier Info
Maintenance progress/ evaluation report
Defects/ Disease/ Insect threats report
Defects, disease, insects
Landscape Technical
Assistant
Scopes & schedules
Contractors
3
Contractors
& Suppliers
D1 LandInfoPHB
Maintenance
D1 LandInfoPHB
Info Storage
Info Retrieval
Plant order info & specs
Order verification
Chief UTM Nursery
Retrieve drawings
Modification
Unit Penyenggaraan
& Ubahsuai.
Plant list updating
Plant order info
& specs
2
Inventory
5
Drawings
Info Storage
Info Retrieval
All reports
4
Reports
Chief Penyenggaraan
& Ubahsuai
Plan & design
Report
Storage
Report retrieval
Landscape Architect
D1 LandInfoPHB
Supplier Info
Legend: Process Data storage Entity
Figure 4.2. Diagram 0 (Modules & Processes of the Landscape Management System)

84
4.2.1
The Maintenance Module
The Maintenance module executes landscape maintenance tasks via three main sub-modules that are Maintenance Packages, Cleaning Packages and Track Records.
Generally, the users of this module include the Landscape Technical Assistant, Cleaning
Maintenance Officer and the Chief of Unit Penyenggaraan & Ubhasuai, Bahagian Harta
. Figure 4.3 illustrates the processes that run in this module.
Cleaning
Maintenance Officer
Scope & schedules
Verification of performance & quality
Scope & schedules
Landscape Technical
Assistant
1.1
Maintenance
Packages
Checklist Work form Info storage
Info retrieval
Info storage
Contractor
Chief Unit Penyenggaraan
& Ubahsuai
Verification of work execution
Info retrieval
D1
Info storage
LandInfoPHB
Info retrieval
1.3
Track
Records
1.2
Cleaning
Packages
Info retrieval
Entity Legend: Process Data storage
Figure 4.3. Maintenance Module (Processes)

85
4.2.2
The Inventory Module
This module provides systematic archiving functions ranging for landscape and equipment inventories, plant ordering and equipment borrowing. The users of this module are the Landscape Technical Assistant, Unit Penyenggaraan & Ubahsuai
Bahagian Harta, the UTM Chief Nursery, and the Senior Store Officer, Bahagian
Pengurusan Kontrak & Harta. Figure 4.4 shows the processes that run in this module.
Landscape Technical
Assistant
Verify order
2.2
Order info
Order
Form
Indexation
2.1
Ledger
Reg. Num
Archiving & Updating
Order listing
2.3
Order List
2.4
Soft
Landscape
Ledger
Num
D1
Info storage
Info storage
LandInfoPHB
Info retrieval
Verify order Form retrieval
Chief UTM Nursery
Info retrieval
Senior Store Officer
Archiving
& Updating
Equipment borrowing info
Equipment borrowing verification
Equipment borrowing form
Contractor
2.6
Equipment
Info storage
Info retrieval
Info storage
D1 LandInfoPHB
Info retrieval
Info storage
Info retrieval
D1
Info storage
LandInfoPHB
Info retrieval
2.5
Hard
Landscape
2.7
Fertilisers
Legend: Entity Process Data storage
Figure 4.4. Inventory Module (processes)

86
4.2.3
The Contractors & Suppliers Module
This module provides information on 4 main parties namely maintenance contractors, soft landscape suppliers, hard landscape suppliers, equipment suppliers, and fertiliser suppliers, enabling users to systematically archive and retrieve information with ease. Generally, the users of this module include the Landscape Technical
Assistant, Unit Penyenggaraan & Ubahsuai Bahagian Harta, the UTM nursery Chief and the Senior Technical Assistant, Bahagian Pengurusan Kontrak & Harta. Figure 4.5 illustrates the process run in this module.
Landscape Technical
Assistant
Contractor info
3.1
Maintenance
Contractors
3.2
Soft
Landscape
Suppliers
Supplier info
3.3
Hard
Landscape
Suppliers
3.4
Equipment
Suppliers
Info retrieval
Info storage
Info retrieval
Info storage
Info retrieval
Info storage
Info retrieval
Info storage
Info storage
Supplier
info
D1 LandInfoPHB
3.5
Info retrieval
Info retrieval
Info retrieval
Info retrieval
Chief UTM Nursery
D1
Fertiliser
Suppliers
Senior Technical
Assistant
LandInfoPHB
Info retrieval
Entity Legend: Process Data storage
Figure 4.5. Contractors & Suppliers Module (Processes)

87
4.2.4
The Report Module
This module permits reporting on 5 main areas namely maintenance, defects, disease and insect control, cleaning, and modification and upgrading. The users of this module include the Landscape Technical Assistant, Cleaning Maintenance Officer and the Chief of Unit Penyenggaraan & Ubahsuai, Bahagian Harta. Figure 4.6 demonstrates the processes in this module.
Landscape Technical
Assistant
Defects report
Report retrieval
4.2
Progress report
Evaluation report
Disease/ Insect control report
Defects
4.1
Maintenance
Report
4.3
Disease & Insect
Control
Report storage
Report retrieval
Report retrieval
D1 LandInfoPHB
Report storage
D1 LandInfoPHB
Modification
/ Upgrading report
Briefings
4.5
4.4
Progress report
Evaluation report
Report retrieval
Briefings
Modification &
Upgrading
Chief Unit Penyenggaraan
& Ubahsuai
Verification
Cleaning
Report storage Report retrieval
Report retrieval
Report retrieval
Cleaning
Maintenance Officer
D1 LandInfoPHB
Legend: Entity Process Data storage
Figure 4.6. Report Module (Processes)

88
4.2.5
The Drawing Module
This module enables users to create and update landscape drawings including site and masterplans, planting and working drawings, and detail drawings. The Landscape
Architect of Bahagian Pembangunan produces the drawings and stores them into this module. Subsequently, the drawings are retrieved and amended or updated by the
Landscape Technical Assistant of Unit Penyenggaraan & Ubahsuai Bahagian Harta when there is a requirement. Figure 4.7 demonstrates the processes undertaken in this module.
Site planning & design
Drawing storage
Landscape Architect
D1
Drawing storage
LandInfoPHB
Drawing retrieval
Drawing retrieval
5.1
5.2
Planting & structural design
5.3
Site &
Masterplans
Planting &
Working
Drawings
Modify/update drawings
Retrieve drawings
Landscape Technical
Assistant
Modify/update drawings
Retrieve drawings
Retrieve drawings
Submit
Verification
& approval
Chief Unit Penyenggaraan
& Ubahsuai
Modify/update drawings
Legend:
Detail
Drawings
D1
Drawing retrieval
Drawing storage
LandInfoPHB
Process
Data storage
Figure 4.7. Drawing Module (Processes)
Entity

89
4.3
The Database Design Of The System
The database design of the proposed system named LandInfoPHB is concerned with the landscape management entities relevant to the application, how they are related to one another and identifying the attributes needed for each of the entities. Figure 4.8 shows an Entity Relationship Diagram (ERD) of the proposed database.
Have
Defects
Have Have
Soft
Landscape
Report s
Have Have
Hard Landscape
Maintenance
Soft Landscape
Maintenance
Have
Have
Supply
Use
Have
Order Information
Have
Soft Landscape
Suppliers
Fertiliser
Supply
Fertiliser
Supplier
Hard
Landscape
Drawings
Assigned to Have Assigned to
Contractors
Use
Maintain Zones
Have
Have
Supply
Have Equipment Supply
Equipment
Suppliers
Hard Landscape
Suppliers
Legend:
Entity
Relationship
One
Many
One or
Many
Figure 4.8. Entity Relationship Diagram (ERD) For The LandInfoPHB Database,
Pejabat Harta Bina

90
The database design, entities and attributes are derived from the findings in Table
3.6 and Table 3.8 in Chapter 3. The type of data involved in Pejabat Harta Bina’s landscape management works and how the data is linked are translated in the proposed
ERD shown in Figure 4.8 – Figure 4.24. figures:
The attributes of each of the entities of the ERD shown above are as following
Package Name Package ID
Zones
Zone ID
Figure 4.9. Entity & Attributes (Zones)
Weeding
Contractor
Report ID
Zone ID Package
Contractor
ID
Schedule Package ID
Soft Landscape
Maintenance
Date
Trimming
Disease/
Insect Control
Watering
Cleaning
Fertilising
Figure 4.10. Entity & Attributes (Soft Landscape Maintenance)

Zone ID Package
Contractor
ID
Schedule Package ID
Contractor
Repainting
Structure checking
Hard
Landscape
Maintenance
Cleaning
Type
Date
Report ID
Figure 4.11. Entity & Attributes (Hard Landscape Maintenance)
Name
Date of planting
Price
Type
ID
Function
Soft Landscape
Package ID
Supplier
ID
Figure 4.12. Entity & Attribute (Soft Landscape)
Nos
Zone ID
91

Type
Supplier
ID
Contractor
ID
ID
Material
Date of
Construction
Package ID
Hard Landscape
Figure 4.13. Entity & Attributes (Hard Landscape)
Units
Zone ID
92
Price
Supplier
Name
Serial Num Supplier ID
Storage
Location
Equipment
Units
Package ID
Type Status
Date of
Purchase
Date of
Maintenance
Manufacturer
Figure 4.14. Entity & Attributes (Equipment)

93
Price
Supplier
Name
Type Supplier ID
Storage
Location
Fertiliser
Package ID
Date of purchase
Form Expiry date
Chemical composition
Manufacturer
Figure 4.15. Entity & Attributes (Fertiliser)
Name
Class
Address
Contractors
Tel Num
Contractor
ID
Package
Figure 4.16. Entity & Attributes (Contractor)

Name
Co.Status
Address Tel Num
Soft Landscape
Suppliers
Supplier
ID
Package
Figure 4.17. Entity & Attributes (Soft Landscape Suppliers)
Name
Co.Status
Address Tel Num
Hard Landscape
Suppliers
Supplier
ID
Package
Figure 4.18. Entity & Attributes (Hard Landscape Suppliers)
Name
Co.Status
Address
Equipment
Suppliers
Tel Num
Supplier
ID
Package
Figure 4.19. Entity & Attributes (Equipment Suppliers)
94

Name
Co.Status
Address
Fertiliser
Suppliers
Tel Num
Supplier
ID
Package
Figure 4.20. Entity & Attributes (Fertiliser Suppliers)
Drawing Num.
Title Scale Package ID
Zone ID
Drawings
Preparation Date Last Updated
Figure 4.21. Entity & Attributes (Drawings)
Prepared by
Hardscape
Defects
Zone ID
Report ID
Softscape
Disease
Defects
Insects threats
Reported By
Package ID
Date of
Detection
Remarks
Figure 4.22. Entity & Attributes (Defects)
95

Author Date
Reports
Title
Figure 4.23. Entity & Attributes (Report)
Report ID
Ledger Reg.
Num
Package ID
Item
Order
Information
Date of order
Frequency
Plant height
Figure 4.24. Entity & Attributes (Order Information)
96
4.4
Summary Of The Modules & Functionalities
The summary of each module and its functions is as shown in Table 4.1.

Table 4.1. Landscape Management System: Modules & Functionalities
Num.
1.
Modules
Maintenance
Functionalities
ƒ
Provide maintenance scopes
ƒ
Provide maintenance schedules
ƒ
Provide cleaning work scopes
ƒ
Provide cleaning work schedules
ƒ Tracking maintenance & cleaning work progress and
2.
3.
Contractors &
4.
Inventory
Suppliers
Reports quality
ƒ
Ordering of plants
ƒ
Archiving orders
ƒ
Archiving list of plants
ƒ
Archiving list of hard landscape elements
ƒ
Archiving of list fertilisers
ƒ
Archiving list of equipment
ƒ
Archiving contractor’s background information
ƒ
Archiving supplier’s background information
To report on all landscape management tasks including:
ƒ
Maintenance progress report
ƒ
Maintenance evaluation report
ƒ
Hard Landscape defects report
ƒ
Soft landscape disease/ insect control report
ƒ
Cleaning progress report
ƒ
Cleaning evaluation report
ƒ
Site modification/ upgrading report
5.
Drawings
ƒ
Archiving site & masterplans
ƒ
Archiving landscape working drawings
ƒ
Archicing landscape detail drawings
ƒ
Modifying/Updating
Source: Author’s Research (2005)
97

4.5 Summary The Database Design Structure
The summary of the database design structure is as shown in Table 4.2.
Table 4.2. Summary Of The Database Design Structure
Num.
Entities
1.
2.
3.
4.
5.
Zones
Soft
Landscape
Maintenance
Hard
Landscape
Maintenance
Soft
Landscape
Hard
Landscape
ƒ
Zone ID
ƒ ID
ƒ
Type
ƒ
Name
ƒ
Nos
ƒ
Function
ƒ
ID
ƒ
Zone ID
Attributes
ƒ
Zone ID
ƒ
Name
ƒ
Package ID
ƒ
Package
ƒ
Zone ID
ƒ
Weeding
ƒ
Trimming
ƒ
Watering
ƒ
Disease/ Insect control
ƒ
Package ID
ƒ
Package
ƒ
Zone ID
ƒ
Type
ƒ
Repainting
ƒ
Structure checking
ƒ
Package
ƒ
Package ID
ƒ
Fertilising
ƒ
Cleaning
ƒ
Schedule
ƒ
Contractor ID
ƒ
Contractor
ƒ
Date
ƒ
Report ID
ƒ
Cleaning
ƒ
Schedule
ƒ
Contractor ID
ƒ
Contractor
ƒ
Date
ƒ
Report ID
ƒ
Location
ƒ Date of planting
ƒ
Price
ƒ
Package ID
ƒ
Supplier ID
ƒ
Supplier ID
ƒ
Contractor ID
98

6.
7.
Equipment
Fertiliser
8.
Contractors
9.
Soft
12.
Landscape
Suppliers
10.
Hard
Landscape
Suppliers
11.
Equipment
Suppliers
Fertiliser
Supplier
ƒ Type
ƒ
Units
ƒ
Material
ƒ
Serial Num.
ƒ
Package ID
ƒ
Name
ƒ
Type
ƒ Units
ƒ
Price
ƒ
Date of purchase
ƒ
Package ID
ƒ
Type
ƒ
Name
ƒ
Form
ƒ Chemical composition
ƒ
Price
ƒ
Contractor ID
ƒ
Name
ƒ
Address
ƒ
Supplier ID
ƒ
Name
ƒ
Address
ƒ
Supplier ID
ƒ
Name
ƒ
Address
ƒ Supplier ID
ƒ
Name
ƒ
Address
ƒ
Supplier ID
ƒ
Name
ƒ
Address
ƒ Date of construction
ƒ
Package ID
ƒ
Drawing Num.
ƒ
Supplier ID
ƒ
Supplier
ƒ
Manufacturer
ƒ
Status
ƒ Storage location
ƒ
Date of maintenance
99
ƒ
Date of purchase
ƒ
Expiry date
ƒ
Supplier ID
ƒ
Supplier
ƒ Manufacturer
ƒ
Storage location
ƒ
Tel. Num
ƒ
Class
ƒ
Package
ƒ
Tel. Num
ƒ
Co. Status
ƒ
Package
ƒ
Tel. Num
ƒ
Co. Status
ƒ
Package
ƒ Tel. Num
ƒ
Co. Status
ƒ
Package
ƒ
Tel. Num
ƒ
Co. Status
ƒ
Package

13.
14.
15.
16.
Drawings
Defects
Reports
Order
Information
ƒ Drawing Num.
ƒ
Zone ID
ƒ
Package ID
ƒ
Title
ƒ
Zone ID
ƒ
Package ID
ƒ
Hardscape defects
ƒ Softscape disease
ƒ
Insect threats
ƒ
Report ID
ƒ
Title
ƒ
Ledger Reg. Num
ƒ
Package ID
ƒ
Item
Source: Author’s Research (2005)
ƒ Scale
ƒ
Prepared by
ƒ
Preparation date
ƒ
Last updated
ƒ
Date of detection
ƒ
Remarks
ƒ
Reported by
ƒ Report ID
ƒ
Author
ƒ
Date
ƒ
Plant Height
ƒ
Frequency
ƒ
Date of order
100
4.6 Conclusion
The design of the proposed Landscape Management System translates the landscape management work processes practised by Pejabat Harta Bina into a systematic flow of data from one module to another. This chapter aims to provide a guideline on what a Landscape Management system should be like with regards to the requirements of Pejabat Harta Bina. The modules and database design shown in this chapter are the essentials of a Landscape Management System that could assist and further enhance the efficiency of landscape management works in Pejabat Harta Bina.

101
Chapter 5
INVENTORY MODULE PROTOTYPE
5.0 Introduction
This chapter discusses the development of an inventory module prototype of the proposed landscape management system as described in Chapter 4. The Inventory
Module described in this chapter is developed by using ARCHIBUS/FM Version 14, a
CAFM system that possesses modules and functions somewhat similar to the proposed landscape management system though it does not fully cater the functions required in the proposed system. Through this Inventory Module, an example of how the landscape management system inventory module may look like in the proposed system can be demonstrated. It is reasonable to assume however that there are other CAFM software that may be able to undertake this tasks just as well if not better. However, due to time constraints and limited software available to the researcher, and the aim of this task that is to merely demonstrate how the Inventory Module may look like, the utilisation of
ARCHIBUS/FM version 14 for the development of the Inventory Module shall suffice.

102
5.1
ARCHIBUS/FM: An Overview Of The Software
ARCHIBUS/FM is one of the most widely recognized CAFM software programmes on the market. ARCHIBUS/FM has been developed for casual infrastructure users, infrastructure contributors, and infrastructure managers. It consist a variety of modules to suit different operations needs of organisations. The application modules of ARCHIBUS/FM are as follows: i) ARCHIBUS/FM Real Property & Lease Management
This module functions to produce meaningful reports about and accurate analyses of lease and property data. Users can model complex real estate and lease holdings on a national, or even global scale, and summarize their revenue potential.
(Terminal Velocity FM, 2005) ii) ARCHIBUS/FM Strategic Master Planning
This module provides functions to examine current space usage, analyse and forecast space needs, compare proposed layouts against existing conditions, allocate space based on the organisation's business goals, and examine the historical use of space by budget category with this planning tool. It also includes stacking and blocking features. (Terminal Velocity FM, 2005)

103 iii) ARCHIBUS/FM Space Management
This is a decision support tool that helps users to optimise the use of space within a facility. Users can determine how efficiently space is being used, identify rentable and leasable areas, calculate space costs and chargebacks, and draw up tenant and employee occupancy plans. (Terminal Velocity FM, 2005) iv) ARCHIBUS/FM Overlay for AutoCad with Design Management
This module expedite the creation of facility drawings, develop asset symbols and register them in a database, and perform asset symbol edits and database updates, all from within AutoCAD, using the drafting tools. This product is the only AutoCAD enhancement product designed specifically for facility drawing. (Terminal Velocity FM,
2005) v) ARCHIBUS/FM Furniture & Equipment Management
This module possesses inventory-tracking capabilities that enable users to monitor the costs of assets, calculate depreciation and churn rates, and plan moves of furniture and equipment. The module also helps users to control costs on F&E layout, specification, and installation. (Terminal Velocity FM, 2005)

104 vi) ARCHIBUS/FM Telecommunications & Cable Management
This module is used to create a living, electronic inventory of the physical cabling and the connectivity of telecommunications networks in a facility. Users can maintain the most up-to-date connectivity information for troubleshooting, and capacity information for planning. (Terminal Velocity FM, 2005) vii) ARCHIBUS/FM Building Operations Management
This module automates the full range of tasks involved in maintaining a facility with this Computerized Maintenance Management System (CMMS). Document and monitor preventive maintenance or repair work, manage moves, work orders, and work requests. (Terminal Velocity FM, 2005) vii) ARCHIBUS/FM Fleet Management
This module functions to maintain an organisation's fleets, whether they consist of cars, trucks, ships, or planes, is crucial to the safety and efficiency of the operations.
The Fleet Management solution for ARCHIBUS/FM helps users to track each vehicle's usage, availability, maintenance schedules and more, details that are vital to optimising the performance of fleets. Combining this information with other facilities and infrastructure management data also improves user’s ability to control costs and assign resources. Fleet Management can be added to an existing ARCHIBUS/FM system or implemented separately as a standalone solution. It is configured, customized and delivered on a customer-by-customer basis. (Terminal Velocity FM, 2005)

105 viii) ARCHIBUS/FM Room Reservations
This module allows users to learn all the relevant details about a room before reserving it. It schedules the use of shared rooms, track rooms by amenities by location, determine maximum occupancy of shared rooms, locate and highlight graphic images of rooms. (Terminal Velocity FM, 2005) ix) ARCHIBUS/FM Hotelling
This module enables organisations with high rates of churn to use space more efficiently. Track time-based ownership, charge back for time-based ownership, link assets to move planning, view a graphical depiction of a room such as a photograph and/or floor plan. (Terminal Velocity FM, 2005)
5.2 Justification For Using ARCHIBUS/FM For The Landscape Management
System (Inventory Module) Prototype
ARCHIBUS/FM does not cater for landscape management works, hence the modules and functions do not suit the requirements of Pejabat Harta Bina’s landscape management operations. However, some of the modules namely the Space Management and the Furniture & Equipment Management modules do contain a number of functions that are applicable to the proposed Landscape Management System’s inventory module with a number of adjustments and assumptions that will be further stated.

106
5.3
The Landscape Management System Inventory Module Prototype
The inventory module prototype developed for this research comprises of three categories namely Zones, Soft Landscape, and Equipment. The following figures show the inventories of the aforementioned categories developed in ARCHIBUS/FM version
14.
Assumptions: Site Code = Zone ID
Figure 5.1. Inventory Module: Zones

Assumptions: Building Code = Site ID
Building Name = Site Name
Site Code = Zone ID
Building Graphic = Site Image
Address 2 = Package ID
Address 1 = Package
Buildings = Sites
Figure 5.2. Inventory Module: Sites With Image
107

Assumptions: Building Code = Site ID
Building Name = Site Name
Site Code = Zone ID
Building Graphic = Site Image
Address 2 = Package ID
Address 1 = Package
Buildings = Sites
Figure 5.3. Inventory Module: Sites With Drawing
108

Assumptions: Floors = Plants
Building Code = Site ID
Option 1 = Type
Floor Graphic = Plant Image
Floor Code = Plant ID
Floor Name = Plant Name
Option 2 = Nos
Figure 5.4. Inventory Module: Plants
109

110
Assumptions: Option 1 = Equipment Name Option 2 = Package
Figure 5.5. Inventory Module: Equipment
5.4 Conclusion
All the figures shown in 5.3 demonstrate how the Landscape Management
System Inventory Module may look like. ARCHIBUS/FM version 14 has provided a number of useful functions for the development of this module. However, the fact that
ARCHIBUS/FM does not provide landscape management modules demands the inventory to be developed with a few adjustments and assumptions as stated in the figures.

111
Chapter 6
CONCLUSION
6.0 Introduction
The previous chapters have discussed on the criteria and considerations of developing a Landscape Management System, the design of the system modules and database design and the implementation of one of the modules by utilising
ARCHIBUS/FM version 14. The discussions in the previous chapters is mainly based on the requirements of Pejabat Harta Bina as the organisation that will use the system to further elevate the efficiency of its landscape management works. This chapter shall discuss on the findings of this research and subsequently propose a number of works that need to be undertaken to proceed with the development of the system up to the implementation stage.
6.1 Findings
From the goal and objectives stated in the first chapter, it can be concluded that through this research, a guideline of how to develop a Landscape Management System for Pejabat Harta Bina locally and the landscape management business as a whole has been achieved. Translating Pejabat Harta Bina’s landscape management work processes,

112 structuring the modules that are essential for the system and the database design based on the data required for the system have been successfully acquired.
Looking into the scope of landscape management works has given a substantial understanding of what the proposed system is supposed to do. Pejabat Harta Bina practises landscape management in a way that suits its responsibility as the organisation that caters for the well-being of the development of UTM. Been awarded the Quality
Management System ISO 9001:2000, Pejabat Harta Bina had outlined an effective process of managing its assets and this is the basis of the work process adopted by the proposed Landscape Management System. However, the absence of an information system to archive its landscape information has been a drawback for the organisation.
Structuring the modules of the proposed Landscape Management System is based on the requirements of Pejabat Harta Bina as well as various other management systems such as CAFM. Studying the modules and functions of other systems has given an insight of how the proposed system is to be structured and what modules that need to be incorporated. The findings in Chapter 3 have shown that many system users underutilised certain modules and functions due to incompatibilities of the systems they purchased with the requirements of the organisations. Hence, this research tried to structure the modules and produce a database design that remain faithful to the landscape management requirements of Pejabat Harta Bina as far as possible.
The general scenario of this research is that of a Facilities Manager who is responsible in elevating the efficiency of an organisation that is responsible in landscape management. The emergence of problems due to unsystematic information handling has surfaced the need to develop an information system to manage its landscape related information. Hence, a guideline on what modules and functions the system should provide and what data should the system process is brought into light prior to the implementation of the system. In doing so, a thorough understanding on the scope of work, work processes and the function of landscape as a support service to a higher

learning institution such as UTM should be acquired, hence outlining a Landscape
Management System that effectively fulfils the organisation’s requirements.
113 i) Further Stages Of The System Development
The guidelines provided in this research do not include the system’s interface design and programming. Hence, these subsequent development processes need to be looked into with regards to user requirements and compatibility of the hardware and operating systems that Pejabat Harta Bina possesses. ii) Further Studies On Existing CAFM Systems In The Market
The proposed Landscape Management System is portion of CAFM system.
Existing CAFM systems in the market are still rather new in Malaysia and the utilisation of these systems by local organisations especially for landscape management is relatively low. Hence, further studies on these CAFM systems are needed to appraise the modules and functions offered and their compatibility in landscape management. A study may even be carried out on how to include a landscape management module into these existing CAFM systems. iii) Standardising The Landscape Management System
The Landscape Management System proposed in this research can be categorised as a customised system, suiting the local requirements of Pejabat Harta Bina,
UTM. However, it may not be applicable for other organisations that deal with

114 landscape management. Hence, further studies on how to produce a standard Landscape
Management System that can be applied in various landscape management organisations could be undertaken. This will inevitably require in depth studies on the standard work processes, scopes and data involved in landscape management as one single discipline.
6.3 Conclusion
This research presents the task of developing a Landscape Management System for Pejabat Harta Bina, UTM. Guidelines on the considerations that have to be taken into account, the modules to be included and the database design are produced as translations of the landscape management scope of work and processes as practised by Pejabat Harta
Bina. This could provide an insight for Pejabat Harta Bina on what the system should provide, hence supplying precious reference for future development of a landscape management system prior to the appointment of system analysts and programmers for the development of the system.

115
BIBLIOGRAPHY
Amaratunga, D., Baldry, D., Srashar, M., and Newton, R. (2002), Quantitative &
Qualitative Research
Berita Harian (2000), “Pembangunan Seimbang Ke Arah Negeri Dalam Taman 2005
Diterus”
Berita Harian (2000), “Johor Jadi Negeri Dalam Taman 2005”
Covejoy. D. (1973), Land Use & Landscape Planning, (International Textbook
Company Limited)
Cullen. G. (1981), The Concise Of Townscape, London (Architectural Press)
Hasliza Abdul Majid (1995), Perancangan Penggunaan Landskap Yang Sesuai Bagi
Kawasan Perumahan, Universiti Teknologi Malaysia
In The Built Environment: Application Of Mixed Research Approach (Emerald)
Jabatan Perancangan Bandar & Desa, (1995), Garis Panduan Lanskap Negara, Kuala
Lumpur, (Kementerian Perumahan & Kerajaan Tempatan)
Jones, I. (1997), Mixing Qualitative & Quantitative Methods On Sports Fan Research,
The Qualitative Report. Online serial, Vol. 3 No. 4, http://www.nova.edu/sss/QR/QR3-
4/nau.html
Joudah, A. (1996), Developing Facilities Information Management Systems, In
Alexander, K., Facilities Management: Theory & Practice, (E & FN SPON)

116
Kecom Ak Shebli Selat (1998), Pentenggaraan Landskap Hidup & Landskap Kejur Bagi
Taman-Taman Awam, University Teknologi Malaysia
King, N. (1994), The Qualitative Research Interview, In Cassell & Symon, G.,
Qualitative Methods In Organisational Research, (Sage Publications, London)
Kvale, S. (1996), An Introduction To Qualitative Research Interviewing, (Sage,
Thousand Oaks, CA)
Massachusetts, Amherst, Graphic Systems, (2001), CAFM System Peer Review-
Questionnaire Summary, University of Massachusetts, Amherst & Graphic Systems
Inc., Boston MA
Mustapa Kamal Mohd Shariff (1989), Hortikultur Hiasan & Landskap, Kuala Lumpur
(Dewan Bahasa & Pustaka)
Parker, J. (1989), Landscape Management & Maintenance, Great Britain, (Billing &
Sons Ltd)
Price, S. (1999), Database Design & Management, (McGraw-Hill)
Putrajaya Corporation, (2004), Putrajaya Lake & Wetland Management Operational
System (PLWMOS)
Rosimah Abdul Rahman (1998), Peranan Lanskap Lembut Dalam Mempertingkatkan
Kualiti Persekitaran Bandar, Universiti Teknologi Malaysia
Sellapan, P. (2000), Database Management: Theory & Practice, (Sejana Publishing)

Terminal Velocity FM, (2005), ARCHIBUS/FM - Modules and Core Application information, http://www.terminalvelocityfm.com/products/afm/modules/index.html
University Of Washington, (2002), The Landscape Management System (LMS),
(College Of Forests Resources)
Utusan Malaysia, (2005), “ ‘Arbor Tracker’: Melabel Pokok Menggunakan Kaedah
Digital”
117
Van Manen, M. (1997), Linking Ways Of Knowing With Ways Of Being Practical, Vol.
6 Curriculum Inquiry Van Manen, M., 1997, Linking Ways Of Knowing With Ways Of
Being Practical, Vol. 6

Appendix 1: PLWMOS (Putrajaya Lake & Wetland Monitoring System) Modules
& Functionalities
No.
Biotics
Sector and Sub-Sector
1.
Phytoplankton
Total Data Tables: 4
Total ASP Files: 6
2.
Benthos and Zooplank ton
Total Data Tables: 4
Total ASP Files: 12
3.
Mosquito
Total Data Tables: 6
Total ASP Files: 12
4.
5.
Waterborne Pathogen
Total Data Tables: 2
Total ASP Files: 4
Fish
Total Data Tables: 7
Total ASP Files: 14
6.
Terrestrial Fauna
Total Data Tables: 10
Total ASP Files: 20
Functionalities i.
To Add New Station ii.
To Add New Species iii.
To Key-In Sampling Data i.
To Add New Benthos Station ii.
To Add New Benthos Species iii.
To Key-In Benthos Sampling Data iv.
To Add New Zooplankton Station v.
To Add New Zooplankton Species vi.
To Key-In Zooplankton Data i.
To Add New Station ii.
To Add New Species iii.
To Key-In Larvae Sampling Data iv.
To Key-In Adult – CDC Trap Sampling Data v.
To Key-In Adult – Human Bait Sampling Data vi.
To Key-In Ovipositor Trap Sampling Data i.
To Add New Station ii.
To Key-In Sampling Data i.
To Add New Station
NEW DATA FORMAT ii.
To Add New Species iii.
To Key-In Water Quality Sampling Data iv.
To Key-In Fish Monitoring Sampling Data
OLD DATA FORMAT i.
To Add New Species ii.
To Key-In Sampling Data iii.
To Key-In Small Fish Sampling Data i.
To Key-In Weather Sampling ii.
To Add New Station iii.
To Add New Mammal Species iv.
To Key-In Mammal Sampling Data v.
To Add New Insect Species vi.
To Key-In Insect Sampling Data vii. To Add New Avifauna Species viii. To Key-In Avifauna Sampling Data ix.
To Add New Herpetofauna Species

Biotics Cont’d
No.
Sector and Sub-Sector
7.
Plant Health and Growth
Total Data Tables: 6
Total ASP Files: 16
8.
9.
Pest and Disease
Total Data Tables: 3
Total ASP Files: 8
Exotic Bird
Total Data Tables: 9
Total ASP Files: 13
Physico-Chemical
1.
Bioaccumulation
2.
Total Data Tables: 3
Total ASP Files: 6
Physico-Chemical
Total Data Tables: 8
Total ASP Files: 16
Hydrology
1.
2.
Hydrology
Total Data Tables: 2
Total ASP Files: 4
Sediment
Total Data Tables: 3
Total ASP Files: 6
Site Maintenance
1.
Lake and Wetland Daily
Maintenance
Total Data Tables: 7
Total ASP Files: 10 x. To Key-In Herpetofauna Sampling Data xi.
Functionalities i. To Add New Station ii. To Add New Species iii. To Key-In Wetland Health Sampling Data iv. To Key-In Wetland Growth Sampling Data v. To Key-In ZII Health Sampling Data vi. To Key-In ZII Growth Sampling Data i. To Add New Station ii. To Key-In Wetland Plants Sampling Data iii. To Key-In ZII plants Sampling Data i. To Add New Species ii. To Key-In Location Data iii. To Key-In Activities of the Month iv. To Key-In Activities v. To Key-In Health Monitoring i. To Add New Station ii. Add New Sampling List iii. To Key-In Sampling Data i. To Add New Station ii. To Key-In Daily Sampling Data iii. To Key-In Weekly Sampling Data iv. To Key-In Biweekly Sampling Data v. To Key-In Monthly Sampling Data vi. To Key-In Quarterly Sampling Data vii. To Key-In Yearly Sampling Data viii. To Key-In Biyearly Sampling Data i. To Add New Station ii. To Key-In Sampling Data i. To Add New Station ii. To Key-In Monitoring Status iii. To Key-In Sampling Data i. To Key-In Laporan Tinjauan Harian Tasik ii. To Key-In Laporan Tinjauan Harian Wetland iii. To Upload Tasik & Wetland Picture iv. To Upload Pencemaran Isu-isu Semasa Picture v. To Key-In Pencemaran Isu-isu Semasa
Description

No.
Sector and Sub-Sector
Biotics
1.
2.
3.
4.
5.
Phytoplankton
Total ASP Files: 8
Benthos & Zooplankton
Total ASP Files: 16
Mosquito
Total ASP Files: 10
Waterborne Pathogen
Total ASP Files: 4
Fish
Total ASP Files: 18
Functionalities i.
To Query Station List ii.
To Query Species List iii.
To Query Sampling Data iv.
To Calculate Indices
ƒ Shannon Diversity Index
ƒ Shannon Max
ƒ Equitability i.
To Query Benthos Station List ii.
To Query Benthos Species List iii.
To Query Benthos Sampling Data iv.
To Calculate Indices
ƒ Shannon Diversity Index
ƒ Shannon Max
ƒ Equitability
ƒ Average Score Per Taxa (ASPT) Index v.
To Query Zooplankton Station List vi.
To Query Zooplankton Species List vii. To Query Zooplankton Sampling Data viii. To Calculate Indices
ƒ Shannon Diversity Index
ƒ Shannon Max
ƒ Equitability i.
To Query Station List ii.
To Query Larvae Sampling Data iii.
To Query Adult – CDC Trap Sampling Data iv.
To Query Adult – Human Bait Sampling Data v.
To Query Ovipositor Trap Sampling Data i.
To Query Station List ii.
To Query Sampling Data i.
To Query Station List
NEW DATA FORMAT i.
To Query Species ii.
To Query Fish Species Sampling Data
OLD DATA FORMAT i.
To Query Species List ii.
To Query Sampling Data iii.
To Query Fish Caught List iv.
To Query Water Quality v.
To Query Small Fish List

No.
Sector and Sub-Sector
Biotics (cont’d)
6.
Terrestrial Fauna
Total ASP Files: 20
7.
Plant Growth and
Health
Total ASP Files: 16
8.
9.
Pest and Disease
Total ASP Files: 8
Exotic Bird
Total ASP Files: 10
Physico-Chemical
1.
Bioaccumulation
Total ASP Files: 6
2.
Physico-Chemical
Total ASP Files: 16
Hydrology
1.
2.
Hydrology
Total ASP Files: 8
Sediment
Total ASP Files: 8
Functionalities i. To Query Weather ii. To Query Station List iii. To Query Mammal Species List iv. To Query Mammal Sampling Data v. To Query Insect Species List vi. To Query Insect Sampling Data vii. To Query Avifauna Species List viii. To Query Avifauna Sampling Data ix. To Query Herpetofauna Species List x. To Query Herpetofauna Sampling Data i. To Query Station List ii. To Query Species List iii. To Query Wetland Health Sampling Data iv. To Query Wetland Growth Sampling Data v. To Query ZII Health Sampling Data vi. To Query ZII Growth Sampling Data i. To Query Station List ii. To Query Pest and Disease Monitoring Data
(Wetland Plants) iii. To Query Pest and Disease Monitoring Data (ZII
Plants) i. To Query Identity ii. To Query Performance iii. To Query Health Monitoring Data i. To Query Station List ii. To Query Sampling List iii. To Query Sampling Data i. To Query Station List ii. To Query Daily Sampling Data iii. To Query Weekly Sampling Data iv. To Query Biweekly Sampling Data v. To Query Monthly Sampling Data vi. To Query Quarterly Sampling Data vii. To Query Yearly Sampling Data viii. To Query Biyearly Sampling Data i. To Query Station List ii. To Query Sampling Data i. To Query Station List ii. To Query Monitoring Status iii. To Query Sampling Data

No.
Sector and Sub-Sector
Site Maintenance
1.
Lake and Wetland Daily
Maintenance
Total ASP Files: 14
Functionalities i.
To Query Station List ii.
To Query Laporan Harian Tinjauan Tasik iii.
To Query Laporan Harian Tinjauan Wetland iv.
To Query Tasik and Wetlands Pictures v.
To Query Pencemaran & Isu-isu Semasa Pictures
No.
Biotics
Sector and Sub-Sector
1.
Phytoplankton
Total ASP Files: 12
2.
Benthos and Zooplankton
Total ASP Files: 24
3.
4.
5.
Mosquito
Total ASP Files: 24
Waterborne Pathogen
Total ASP Files: 8
Fish
Total ASP Files: 36
Functionalities i.
To Edit Station Data ii.
To Edit Species Data iii.
To Edit Sampling Data i.
To Edit Benthos Station Data ii.
To Edit Benthos Species Data iii.
To Edit Benthos Sampling Data iv.
To Edit Zooplankton Station Data v.
To Edit Zooplankton Species Data vi.
To Edit Zooplankton Sampling Data i.
To Edit Station Data ii.
To Edit Species Data iii.
To Edit Larvae Sampling Data iv.
To Edit Adult – CDC Trap Sampling Data v.
To Edit Adult – Human Bait Sampling Data vi.
To Edit Ovipositor Trap Sampling Data i.
To Edit Station Data ii.
To Edit Sampling Data i.
To Edit Station Data
NEW DATA FORMAT ii.
To Edit Species Data iii.
To Edit Water Quality Data iv.
To Edit Monitoring Data
OLD DATA FORMAT v.
To Edit Species Data vi.
To Edit Sampling Data vii. To Edit Fish Caught Data viii. To Edit Water Quality Data ix.
To Edit Small Fish Data

Biotics Cont’d
No.
6.
7.
Plant Growth and Health
Total ASP Files: 24
8.
9.
Sector and Sub-Sector
Terrestrial Fauna
Total ASP Files: 40
Pest and Disease
Total ASP Files: 8
Exotic Bird
Total ASP Files: 20
Physico-Chemical
1.
Bioaccumulation
Total ASP Files: 12
2.
Physico-Chemical
Total ASP Files: 32
Hydrology
1.
Hydrology
2.
Total ASP Files: 8
Sediment
Total ASP Files: 12
Functionalities i. To Edit Weather Data ii. To Edit Station Data iii. To Edit Mammal Species Data iv. To Edit Mammal Sampling Data v. To Edit Insect Species Data vi. To Edit Insect Sampling Data vii. To Edit Avifauna Species Data viii. To Edit Avifauna Sampling Data ix. To Edit Herpetofauna Species Data x. To Edit Herpetofauna Sampling Data i. To Edit Station Data ii. To Edit Species Data iii. To Edit Wetland Health Sampling Data iv. To Edit Wetland Growth Sampling Data v. To Edit ZII Health Sampling Data vi. To Edit ZII Growth Sampling Data i. To Edit Station Data ii. To Edit Pest and Disease Monitoring Data i. To Edit Species Data ii. To Edit Location Data iii. To Edit Activities of the Month Data iv. To Edit Activities Data v. To Edit Health Monitoring Data i. To Edit Station Data ii. To Edit Sampling List Data iii. To Edit Sampling Data i. To Edit Station Data ii. To Edit Daily Sampling Data iii. To Edit Weekly Sampling Data iv. To Edit Biweekly Sampling Data v. To Edit Monthly Sampling Data vi. To Edit Quarterly Sampling Data vii. To Edit Yearly Sampling Data viii. To Edit Biyearly Sampling Data i. To Edit Station Data ii. To Edit Sampling Data i. To Edit Station Data ii. To Edit Monitoring Status Data iii. To Edit Sampling Data

Site Maintenance
No.
Sector and Sub-Sector
1.
Lake and Wetland Daily
Maintenance
Total ASP Files: 24
Functionalities i. To Edit Laporan Harian Tinjauan Tasik ii. To Edit Laporan Harian Tinjauan Wetland iii. To Edit Tasik and Wetlands Picture iv. To Edit Pencemaran & Isu-isu Semasa Picture v. To Edit Pencemaran & Isu-isu Semasa
Description

Appendix 2: PLWMOS (Putrajaya Lake & Wetland Monitoring System) Interface
PLWMOS Homepage
PLWMOS Database Query

PLWMOS Web Based GIS Example: Map Viewer
PLWMOS System Administration Interface

PLWMOS Online Summary Biotic Sector Report
PLWMOS Management Application: Report Endorsement Reminder

Appendix 3: Tropical Park, UTM Landscape Plan

Appendix 4: UTM Aerial Photo
Aerial Photo Serial Number: FC1263_L2WN_67

Appendix 5: Bahagian Harta’s Action Plan 2004 (Excerpt of the report)
5.7.1 Perancangan Teknologi Informasi Dan Komunikasi (ICT)
Untuk meningkatkan pengurusan kerja BH-PHB, perancangan ICT perlu memberi fokus kepada : -
5.7.2 Memantapkan pengurusan dan pentadbiran pejabat dengan membangun dan menambahbaikan sistem pangkalan data seperti :- i) ii)
Sistem maklumat dan prestasi kontraktor
Sistem pemantauan kerja kontraktor BH-PHB iii) Sistem rekod keluar masuk surat. iv) Sistem pemantauan Permohonan Kerja-kerja Ubahsuai v) Sistem Kewangan (penyediaan laporan kewangan bulanan,suku tahun, setengah tahun dan tahunan) vi) Penambahbaikan sistem laporan kerosakan (SILK) dan C-Works vii) Sistem pengurusan ruang berkomputer. (Archibus FM)
5.7.2 Pengunaan ICT yang efektif dan efisyen :- i) Mewujudkan polisi penggunaan IT pejabat ii) Manual penggunaan alatan ICT yang lengkap dan tepat iii) Manual cara-cara penyenggaraan komputer yang mudah
5.7.3 Memantapkan halaman web PHB i) Memastikan maklumat dan isi kandungan yang terkini. ii) Penambaihkan pengisian dan rekabentuk laman web PHB.
5.7.4 Mewujudkan pusat data dan memastikan data dan maklumat yang digunakan dalam kerja seharian diarkibkan.
5.7.5 Menjadi pusat rujukan dengan menyimpan maklumat terkini dan releven.