Personal digital assistants as a mobile inspection system at construction site

“I hereby declare that I have read this project report and in my opinion this project report is sufficient in terms of scope and quality for the award of the degree of Master of Science (Construction Management).”

Signature

:

Name of Supervisor :

DR. ARHAM ABDULLAH

Date

02 MAY 2006

:

PERSONAL DIGITAL ASSISTANTS AS A MOBILE INSPECTION SYSTEM AT CONSTRUCTION SITE

ONG BOON THAI

A project report submitted in partial fulfilment of the requirement for the award of the degree of Master of Science (Construction Management)

Faculty of Civil Engineering Universiti Teknologi Malaysia

MAY 2006

ii

DECLARATION

I declare that this project report entitled “Personal Digital Assistants As A Mobile Inspection System At Construction” is the result of my own research except as cited in the references. The report has not been accepted for any degree and is not concurrently submitted in candidature of any other degree.

Signature

:

Name

:

ONG BOON THAI

Date

:

02 MAY 2006

iii

DEDICATION

To my beloved Mother and Father. Thank you for your support, guidance and confidence in me.

iv

ACKNOWLEDMENTS

This project report was completed with the contribution of many people to whom I want to express my sincere gratitude. First and foremost, I would like to convey my sincere thanks and gratitude to my supervisor, Dr. Arham Abdullah for his patient, time and guidance, throughout the entire research. Special appreciation also goes to Geobina Solutions and Mr Ewe Hong Cheong from Sunset Villa Sdn. Bhd. and all other individual as well as organizations which participated and contributed towards making this research success. I am deeply grateful to my family for their unconditional love through the years. Grace Ng Sock Hooi deserves a special mention upon her continual patience, boundless encouragement and support during this study. Finally yet importantly, I want to extend my grateful appreciation to all the people who have contributed in some way to the completion of this project report.

v

ABSTRACT

Construction defects are always the key concern of the construction industry. Different constructed facilities generate different types of defects and demanded different levels and types of quality, depending on the functions, system types, and materials used. Nevertheless, construction projects was typically take place in an environment where it is difficult to gain access to conventional computers for use as real-time decision aids as gone through the project quality inspection. The objectives of this study was to identify the inspection process and standard check list used in practice at construction site; to identify the potential and requirement for mobile inspection system at construction site and to develop a prototype of a mobile inspection system for construction site. Data was gathered from the literature study and also through local construction organizations by means of interview questionnaire. A prototype was developed using rapid prototyping method in a final phase. The finding revealed that generally construction industry does not have its standard inspection process and standard check list in practice. Besides this, the study also reveals that there was a potential and requirement for mobile inspection system at construction site. Finally a mobile defect inspection which consists of a sub system checklist and reference system was developed to suit the need of industry. The developed prototype will standardize the way of managing building defects and improve quality, increased productivity of inspectors, accurate photographic records and improved building defect communication.

vi

ABSTRAK

Kecacatan pembinaan pada amnya merupakan isu yang sering dititikberatkan dalam industri pembinaan.

Kemudahan fasiliti pembinaan yang berlainan akan

menghasilkan kecacatan dan kualiti pembinaan yang berbeza, dan ini adalah bergantung kepada fungsi dan jenis bahan binaan yang digunakan. Pada amnya, projek pembinaan adalah dijalankan dalam keadaaan yang sempit dan menyukarkan seseorang itu bekerja dengan menggunakan komputer biasa di mana ia akan membantu meringankan beban seseorang itu dalam melakukan pemeriksaan kualiti bangunan.

Maka objektif kajian adalah untuk menentukan keperluan senarai

semakan kualiti yang standard dalam tapak pembinaan; menentukan tahap keperluan terhadap sistem semakan kualiti bangunan mudah alih dalam tapak pembinaan dan membangunkan suatu aplikasi sistem semakan kualiti mudah alih bagi kegunaan dalam tapak pembinaan. Data terhadap keperluan aplikasi sistem semakan kualiti bangunan mudah alih tersebut diperolehi melalui kaedah soal selidik dan juga kajian literatur terhadap industri pembinaan tempatan.

Satu model aplikasi telah

dibangunkan dengan cara rapid prototyping pada fasa akhir kajian ini.

Hasil

daripada kajian ini menunjukkan bahawa industri pembinaan tempatan pada hari ini masih tidak mempunyai suatu senarai semakan dan proses semakan yang standard. Selain daripada itu, keputusan kajian juga menunjukkan bahawa terdapatnya ruang dan potensi yang besar dalam industri pembinaan tempatan untuk penggunaan semakan kualiti bangunan secara mudah alih. Satu model sistem semakan kecacatan mudah alih yang mengandungi sub-sistem senarai semakan dan rujukan telah dibangunkan bagi memenuhi kehendak industri. Model tersebut dapat mendatangkan pelbagai kebaikan dalam pengurusan kecacatan bangunan, peningkatan kualiti dan produktiviti juru semakan, rekod gambaran yang tepat dan meningkatkan komunikasi kecacatan bangunan.

vii

CONTENTS

CHAPTER

TITLE

PAGE

DECLARATION............................................................................................... ii DEDICATION..................................................................................................iii ACKNOWLEDMENTS .................................................................................. iv ABSTRACT ....................................................................................................... v ABSTRAK ........................................................................................................ vi CONTENTS..................................................................................................... vii LIST OF TABLES ........................................................................................... xi LIST OF FIGURES ........................................................................................ xii LIST OF FORM............................................................................................. xiv ABBREVIATIONS ......................................................................................... xv LIST OF APPENDICES ............................................................................... xvi 1

INTRODUCTION................................................................................. 1 1.1 Introduction .................................................................................... 1 1.2 Background of Study ..................................................................... 3 1.3 Previous Research .......................................................................... 4 1.4 Statement of the Problems ............................................................. 5 1.5 Objectives of Study ........................................................................ 6 1.6 Scope of Study ............................................................................... 6 1.7 Methodology .................................................................................. 7 1.8 Report Organization ....................................................................... 9

2

LITERATURE REVIEW................................................................... 10 2.1 Applying Handheld Computers in the Construction Industry...... 10 2.2 Information and Computing Needs at Construction Sites............ 11 2.3 General and Project-Specific Information ................................... 12

viii 2.4 Handheld Computing Devices ..................................................... 13 2.5 Emerging Technologies ............................................................... 14 2.5.1 Introduction to Wireless Communication ........................ 15 2.6 PDA's History and Features ......................................................... 17 2.6.1 History of Pocket PC........................................................ 19 2.6.1.1

Feature of Pocket PC......................................... 20

2.7 Previous Thesis Review on Construction Check List .................. 21 2.8 Result From the Literature Study................................................. 23 2.9 Result from Thesis Research........................................................ 24 2.9.1 Problem in Construction Site ........................................... 24 2.9.2 The Level of PDA Demanding in Construction............... 25 2.9.3 The Activity Which Need Most Check List in Construction .......................................................................................... 26 2.9.4 The Level of Need in Check List ..................................... 26 2.9.5 The Suggestion of Further Improvement ......................... 27 2.10 Conclusion ................................................................................... 28 3

RESEARCH METHODOLOGY ...................................................... 29 3.1 Introduction .................................................................................. 29 3.2 Research Process.......................................................................... 29 3.3 Literature Review......................................................................... 32 3.4 Interview ...................................................................................... 32 3.4.1 Interview Questionnaire Design....................................... 33 3.5 System Design.............................................................................. 34 3.6 Introduction to Rapid Prototyping ............................................... 34 3.6.1 Method ............................................................................. 35 3.7 Prototype Testing ......................................................................... 37 3.8 Conclusion ................................................................................... 37

4

ANALYSIS AND SYSTEM DESIGN ............................................... 38 4.1 Analysis of Interview Situation.................................................... 38 4.1.1 Introduction to Qualitative Data....................................... 38 4.1.2 Coding Steps .................................................................... 39 4.1.2.1

Initial Coding .................................................... 39

ix 4.1.2.2

Focused Coding................................................. 39

4.2 The Defect Management Requirement From of the Industry ...... 40 4.2.1 Usage of Defect Inspection Check List............................ 40 4.2.1.1

Comparison of Defect Inspection Check List as Criteria to Select Test Field Company .............. 40

4.2.2 Party Involve in the Defect Management......................... 41 4.2.2.1

Defect Management Organization in Selected Company ........................................................... 42

4.2.3 Current Inspection System / Method................................ 44 4.2.4 Business Process Defect Inspection System for Current Selected Company............................................................ 46 4.3 Introduction to Mobile Inspection System Design ...................... 48 4.3.1 Database Design............................................................... 49 4.3.1.1

DFD of Inspection Process ............................... 50

4.3.1.2

Introduction to Data Modeling Overview ......... 54

4.3.1.3

Data Structure of Inspection System................. 55

4.3.1.4

ERD Model of Inspection System .................... 57

4.3.1.5

Entities .............................................................. 57

4.3.2 System Design.................................................................. 58 4.3.2.1

Hardware and Software Requirement ............... 60

4.3.2.2

System Platform................................................ 62

4.3.2.3

System Architectural......................................... 63

4.4 User Operations Manual of MDIS ............................................... 71 4.4.1 User Manual for Pocket PC ............................................. 71 4.4.2 User Manual of Workstation............................................ 73 4.5 Testing of Prototype..................................................................... 75 4.5.1 The Hardware Equipment Needs to Prepare Before Inspection ......................................................................... 79 5

EVALUATION OF THE PROTOTYPE SYSTEM ........................ 81 5.1 Introduction .................................................................................. 81 5.2 Evaluation Questionnaire Design................................................. 82 5.3 Evaluation Result ......................................................................... 83 5.4 Advantage of the Prototype.......................................................... 87

x 5.5 Prototype Limitation .................................................................... 88 5.6 Summary ...................................................................................... 88 6

CONCLUSION.................................................................................... 89 6.1 Introduction .................................................................................. 89 6.2 Realization of Research Objective ............................................... 90 6.3 Recommendations for Improvement............................................ 92 6.4 Recommendations for Future Improvement ................................ 92

REFERENCES................................................................................................ 94 APPENDICES .……………………………………………………………. 100 APPENDIX A ....…………………………………………………….100 APPENDIX B ……………………………………………………….105

xi

LIST OF TABLES

Table 2.1: Comparison between Palm Devices and Pocket PC ................................. 14 Table 2.2 : Level of Problems Occurred During Site Checking ................................ 25 Table 2.3 : Valuation on the Uses of Pocket Personnel Computer ............................ 25 Table 2.4 : Activity Which Need Most Check List.................................................... 26 Table 2.5 : The Level of Need in Check List............................................................. 27 Table 2.6 : Proposal on Improving the Site Checking System .................................. 27 Table 4.1 : Analysis Result of an Organisation Layer ............................................... 41 Table 4.2: Hardware Requirement for Handheld Unit............................................... 61 Table 4.3: Hardware Requirement for Workstation................................................... 61 Table 4.4: ASP Source Code of Database Management and Control Module .......... 64 Table 4.5: ASP Source Code of OS Detection and GUI Control Module ................. 65 Table 4.6: ASP Source Code of Image Processing Module....................................... 66 Table 4.7: ASP Source Code of Information Access Security Control by Level and Group Module .......................................................................................... 67 Table 4.8: ASP Source Code of Data Print Module................................................... 69 Table 4.9: List of Compartment Extracted................................................................. 78 Table 4.10: List of Contractor in the Project.............................................................. 78 Table 4.11: Comparison of Price and Service from Different Cellular Network Provider in Malaysia ................................................................................ 80 Table 5.1: Result of Evaluation.................................................................................. 84 Table 5.2: Additional Comment................................................................................. 85 Table 5.3: Benefit of the Prototype ............................................................................ 87

xii

LIST OF FIGURES

Figure 1.1 : Study of Methodology Flow Chart......................................................... 8 Figure 2.1 : Mobile Communication Networks for Construction Project Team...... 15 Figure 2.2 : Comparison of Various Network Speed through Packet Download Test ...................................................................................... 16 Figure 2.3 : Checking Process at Construction Site................................................. 23 Figure 3.1 : Steps in Methodology........................................................................... 31 Figure 3.2 : A Model of Rapid Prototyping ............................................................. 34 Figure 3.3 : Comparing Design and Development within Rapid Prototyping and Formative Evaluation ............................................................................ 35 Figure 4.1 : Usage of Defect Inspection Check List ................................................ 40 Figure 4.2 : Defect Communication from Top Management till Contractor ........... 43 Figure 4.3 : Percentage of Date Reentry .................................................................. 44 Figure 4.4 : Data Short Out Method According to Project ...................................... 45 Figure 4.5 : Level of Need in Standard Document Format...................................... 46 Figure 4.6 : Basic Mobile Inspection Concept at Construction Site ........................ 48 Figure 4.7 : Spider Web ........................................................................................... 50 Figure 4.8 : Centralized Network............................................................................. 50 Figure 4.9 : Traditional Defect Management Business Process .............................. 51 Figure 4.10 : Defect Management Business Process after Reengineering................. 52 Figure 4.11 : Data Flow Diagram (DFD) for Targeted Company ............................. 52 Figure 4.12 : Data Flow for Input and Output from MDIS........................................ 54 Figure 4.13 : Database Structure of MDIS................................................................. 55 Figure 4.14 : Entity-Relationship Model ................................................................... 58 Figure 4.15 : Mobile Defect Inspection System (MDIS) Main System Topology .... 59 Figure 4.16 : Cellular Coverage in Malaysia ............................................................. 60 Figure 4.17 : Interaction in Between MDIS System Platform ................................... 63 Figure 4.18 : System Architectural of MDIS ............................................................. 64

xiii Figure 4.19: A Report Which Been Generating Automatically By Defect Report Auto Generation Module ...................................................................... 70 Figure 4.20: Location of Test Field............................................................................ 76 Figure 4.21: Ground Floor Plan ................................................................................. 77 Figure 4.22: First Floor Plan ...................................................................................... 77 Figure 5.1 : System Performance .............................................................................. 85 Figure 5.2 : Applicability to Construction Industry .................................................. 86 Figure 5.3 : Overall Rating ....................................................................................... 86

xiv

LIST OF FORM

Form 4.1 : Quality Form for Inspection System ........................................................ 47

xv

ABBREVIATIONS

ADO

ActiveX Data Object

ADODB

ActiveX Data Object Database

ASP

Active Server Page Language

CDMA

Code-Division Multiple Access

DFD

Data Flow Diagram

EDGE

Enhanced Data Rates For Global Evolution

ER

Entity-Relationship

GPRS

General Packet Radio Services

GSM

Global System For Mobile Communication

GUI

Graphics User Interface

IT

Information Technology

LAN

Local Area Network

LCD

Liquid Crystal Display

MDIS

Mobile Defect Inspection System

MSN

Microsoft Network

OS

Operating System

PDA

Personal Digital Assistant

PPC

Pocket Pc

PWD

Public Work Department

RAM

Random Access Memory

ROM

Read Only Memory

SQL

Structured Query Language

TDMA

Time Division Multiple Access

VB

Visual Basic

WLAN

Wide Local Area Network

xvi

LIST OF APPENDICES

APPENDIX

TITLE

PAGE

A

Questionnaire

100

B

Evaluation Questionnaire

105

CHAPTER 1

1INTRODUCTION

1.1

Introduction

Construction projects typically take place in an environment where it is difficult for site officer and project engineers in the construction site to gain access to conventional computers for use as real-time decision aids as the gone through the project valuation, building M & E inspection, or the pre and post concrete quality inspection (Trefor, 2003).

In the massy construction site area, it is often hard and inconvenient for the site officer and project engineers to carry bulky plans and reference papers to climbing up and down on the temporary access to go into the construction site or building area. It would seem that the construction industry would be a wide area for the application of handheld computers due to their special features in the light weight, small in pocket size for easier in traveling and mobilization and had own a processing feature and software as much as the desktop personal computers.

2

However the all most nature of construction projects and the cost of setting up various decision support systems often act as a barrier to implementing the systems. But, the time had change, handheld computers now days are becoming more powerful and less costly and even some of the handheld computers are now embedded in to the cell phone today to improve in organizing the phone and address book and also the daily schedule and this had make the potential to employ these devices widely in construction are become greater and wider.

The information needs at the construction site are varied. Personnel in the field require information to make decisions about the construction processes being conducted and update it updated periodically. They also collect data concerning project progress, quality, and costs. Handheld computing applications will therefore include textual information and graphical information about construction as well as form-based software to collect data.

Reference information is one of the basic uses for which handheld computers can be employed. The specific information included on the handheld device will vary from project-to-project and organization-to-organization. It would be assumed that contractors would place more of an emphasis on installation procedures, and owner organizations would emphasize documentation for inspection procedures and quality control. Typical documentation that can be accommodated on a handheld computer is such as real time progress monitoring of on-site works, remote expert support, onsite collection of qualitative and quantitative measurements, collaborative review of technical drawings, on-site supplier and subcontractor evaluation, on-site evaluation of equipment usage measurements, keeping track of the physical equipment position anytime and anywhere, answering audit checklists and filing audit reports during site audits (Meissner et al., 2001). Therefore, the application of information technology in this field will give more advantages.

IT can be define as the use of electronic machines and programs for the processing, data storage, transfer and presentation of information (Bjork, 1997).

3

With emerge of the 3G technology today, it had become the best methods to deliver reference content to the handheld devices. One method will be to download entire documents to the handheld computer by physical connection to a desktop computer. But the emerging 3G method is to wirelessly access Web pages on the Internet and display the information on a handheld computer. The advantage of this Web access is that documents can be updated easily and the new content can be made available to all users immediately.

1.2

Background of Study

Traditionally, the construction industry has employed paper-based data capture and communication methods. These were time-consuming and potentially error-prone, and discouraged project managers from using them on a regular basis. Thus people tend to minimize communication with other project participants. Since the various stages and tasks of construction are highly interdependent this minimal interaction in practice causes severe problems, widely reflecting on other partners and the final construction product (Ladh, 1995). It has been recognized for some time that capturing data through handheld computing devices, enabled with suitable wireless capability, can address these problems, thereby increasing operative efficiency and ensuring better integration with the existing project management systems.

A number of construction projects are based on online project collaboration solutions and a new community of virtual construction team members has emerged. This team has two main categories of people who would benefit from the adoption of mobile computing technologies. The first category comprises of workers such as contractor’s team executing the project. Such workers require an interface to backend system to maintain contact with their office based counterparts. The other

4

category comprises professionals who spend a significant amount of time in the office but quite often have to travel to the different construction sites. Such professionals will need an interface to the information held in their offices both while in transit and while on the site.

The rapid growth of handheld computing devices in recent years has marked the beginning of a real mobile communication capability. From their roots as standalone devices that were reliant upon a cable connection to a desktop PC or a connected mobile phone, handhelds are now evolving to integrate features that enable wireless connection to mobile phone and corporate networks. However to a large extent, current use of mobile communication devices for the construction industry remains limited to use of standalone hand held device (C.J Anumba, 2003).

1.3

Previous Research

Nevertheless the used of PDA and telecommunications are long exits in Construction industry and there are few research been carries out on concept of using obsolesce technology such as concept of using Psion as mobile web browser to browse through the internet at any ware in the paper of “PDA as mobile WWW browsers” (Stefab Gessler, 1995), and also using handheld computer to browse through an electronic document such as e-book in the construction industry and also using a third party software for data collection in the paper of “Applying Handheld computers in the construction industry” (Trefor P.willians, 2003).

Later, the player in the construction industry had aware of the need of more capable mobile computing system in the construction industry due to the booming of information technology, then they had put their mind into and develop a concept of

5

interaction between mobile computing system and construction in the paper “Mobile Communication In Construction-Trends And Prospects” (C. J.Anumba, 2003). In the paper of “The application of PDA as mobile computing system on construction management” (Kenji Kimoto, 2005) had draft out a stand along construction management prototype where the information collection from construction site is not transmit instantaneous and only can be retrieve and analysis when the mobile device is send back to office, further more the interface use in this prototype is a set of static programs which more to structure engineering analysis. Therefore it can not perform dynamic interaction to collect data due to the dynamic nature of construction environment.

1.4

Statement of the Problems

Since the office automation at the late 1980s has improved the productivity of office works rapidly until today. Site officer, project engineers and construction managers in Malaysia today have recently handled various types of digital information such as drawings, specification, checklists and daily reports.

However, they still need to access the real construction site to check and manage the construction project. They usually use sheets of paper and/or field notes. As a result, they still have a lot of typical and routine jobs in construction site, such as the collection of construction data and the inspection. A gap in time and space between the outdoor construction site and the office, which leads to the low efficiency, occurs and cause into several issues and problem that have been discussed by the public and government recently. From the issues of computer labs and 16 “sick” schools and five community colleges with structural defects, to the closing of Sultan Ismail Hospital in Johor Bahru because of a fungal outbreak due to faulty air-

6

conditioning and the latest issues where the key Middle Ring Road in Kuala Lumpur had to be closed after cracks were found.

1.5

Objectives of Study

1. To review the inspection process and standard check list used in practice at construction site. 2. To identify the potential at and requirement for mobile inspection system at construction site. 3. To develop a prototype at a mobile inspection system for construction site.

1.6

Scope of Study

The scope of this study will focus on the activity of defect inspection at the final phase construction before handover. Area of this study will only carry out in area of PERAK and JOHOR.

7

1.7

Methodology

The following methodology has been adopted in achieve the objective list previously: 1. In order to achieve the first objective which is identify the problems face in construction site and the method of inspection during concreting structure frame, the method for acquisition data will be interviewing construction site personal. 2. However to achieve the second objective which is to identify the potential at and requirement for mobile inspection system at construction site, the method to acquire data is by conducting a literature research on previous thesis which had been carried out before. 3. To achieve final objective which is to develop a prototype at a mobile inspection system for construction site, rapid prototyping method has been chosen to develop the mobile system.

8

Figure 1.1: Study of Methodology Flow Chart

9

1.8

Report Organization

a. Chapter 1 consists of the introduction of the entire study. It covers the background, problem statement, objective, scope and methodology of the study. b. Chapter 2 will focus on the literature study especially in definition of mobile technology and also the type of device applicant in mobile technology. Besides this, the important and role of mobile technology in construction field will also review in this chapter. c. Chapter 3 will review the previous study on the standard check list in construction industry and how it is adopted in the concreting checking procedure. d. Chapter 4 will discuss on the information flow and technique of using ASP in the web severs. This chapter will also look into the way of developing mobile inspection system and the prototype development and demonstration. e. Chapter 5 will discuss on the evaluation method and also evaluation result analysis of the prototype. f. Chapter 6 will conclude the findings of the project and recommends or further study.

CHAPTER 2

2LITERATURE REVIEW

2.1

Applying Handheld Computers in the Construction Industry

Construction defects are always the key concern of the construction industry. Different constructed facilities generate different types of defects and demand different levels and types of quality, depending on the functions, system types, and materials used.

Most defect research concentrates on materials and systems,

examining different types of defects under given conditions and determining methods for how to detect them. As a result, these researches are generally focused on technical and technological issues. Numerous systems have been designed to eliminate defects during construction operations. Many of these systems were very effective in detecting and eliminating defects that occurred at the construction stage, but a large number of complaints about defects were also recorded a few years after the occupants moved in, which suggested that there were still loopholes in the existing inspection and management systems (Wai-Kiong Chong, 2005).

11

Therefore, for the construction projects typically take place in an environment where it is difficult for project engineers and inspectors in the field to gain access to conventional computers for use as real-time decision aids, it is often inconvenient to carry bulky plans and reference documents into the field. It would seem that the construction industry would be a fertile area for the application of handheld computers. However the one-time nature of most construction projects and the cost of setting up various decision support systems often act as a barrier to implementing the systems.

Handheld computers are becoming more powerful and less costly. The potential exists to employ these devices widely in construction. However, it is necessary to examine their capabilities and to consider how they can best be employed. At a basic level, a handheld computer can be used as a personal digital assistant that allows users to access and organize information such as addresses and phone numbers. On a more sophisticated level, handheld computers can be used to run programs for a wide variety of applications, and provide e-mail and Internet access (Helpful, 2001).

2.2

Information and Computing Needs at Construction Sites

The information needs at the construction site are varied. Personnel in the field require information to make decisions about the construction processes being conducted. They also collect data concerning project progress, quality, and costs. Handheld computing applications will therefore include textual information and graphical information about construction as well as form-based software to collect data.

12

Reference information is one of the basic uses for which handheld computers can be employed. The specific information included on the handheld device will vary from project-to-project and organization-to-organization. It would be assumed that contractors would place more of an emphasis on installation procedures, and owner organizations would emphasize documentation for inspection procedures and quality control. Typical documentation that can be accommodated on a handheld computer is standard specifications, quality standards, construction techniques, inspection checklists, and any type of training or educational material. An exciting feature of handheld computers is their ability to display full-motion videos with sound. This suggests the potential to present videos of correct construction techniques to workers at the construction site.

With the continuing technological advances in wireless connectivity, additional questions will emerge over the next several years concerning the best methods to deliver reference content to the handheld devices. One method will be to download entire documents to the handheld computer by physical connection to a desktop computer. But now the emerging method is to wirelessly access Web pages on the Internet and display the information on a handheld computer. The advantage of this Web access is that documents can be updated easily and the new content can be made available to all users immediately.

2.3

General and Project-Specific Information

Much of the information used on the construction site is of a type that can be applied on many different projects. This would include items like standard specifications, educational materials about standard construction methods, and material standards. Project-specific information includes the project plans and the project-specific specifications. Obviously, these documents are the most important to

13

include and the ability to provide them in an electronic format could have the greatest impact on a project.

However, the nature of the construction industry requires that these documents be set up in an electronic format specifically for each individual project. Additionally, these electronic plans will only be used for the duration of construction, which proves to be for a short period compared to the service life of the structure or facility. A utility company can justify the expense of developing a system to display plans on a handheld device because it will be used for a long period of time to maintain its infrastructure.

Due to the short-term nature of many construction projects, the cost precludes implementation of sophisticated, project-specific applications. Only complex longlived projects can justify having a specific decision-support system developed. The project-specific applications require the most significant investment because more sophisticated equipment and software is required to display complex plans and engineering documentation on handheld computers.

2.4

Handheld Computing Devices

The most widely used handheld computers operate either on the Palm or the Windows-based Pocket PC operating systems. Palm computers are the leader in the handheld computer market. In addition, the popular Handspring Visor also uses the Palm operating system. The Palm operating system is easy to use and there is a large quantity of general-purpose add-on software and hardware to increase the devices functionality (Pogue, 1999), but there is not a large quantity of specific construction software or applications are available in the market now.

14

Nevertheless Pocket PC devices tend to be more expensive than Palm devices because they offer software and hardware more in-line with full-featured computers. But in particular, Pocket PC devices run a compact version of the Windows operating system (Morrison, 2001). Table 2.1 shows a comparison of the Palm and Pocket PC devices. Pocket PC devices are selected over Palm devices for high-end applications that require high screen resolution and color. In now days, two for use with Pocket PC devices are support by many very powerful software applications are available in the market that can be used to develop project-specific applications for viewing plans and maps.

Table 2.1: Comparison between Palm Devices and Pocket PC Feature Memory

Pocket PC devices 16–64MB SDRAM, 64 MB ROM Screens 3.5”(89mm) Transflective TFT color with LED backlight Expansion slot Integrated SD slot-Supports SD/MMC type standard, SDIO ready Web browsing Web clipping or add-on Full Web-browsing using software GSM/GPRS, Bluetooth or WLAN Cost $100–$450 $350–$600 Source: (http:// www.Microsoft.com/mobile/pocketpc/pdainfo.asp Aug. 6, 2004) “Helpful facts about personal digital assistants’’

2.5

Palm devices 2–8MB RAM, 2MB ROM 160 x 160 resolution, grayscales, or color None or proprietary

Emerging Technologies

Various technologies will emerge over the next several years that will change how handheld devices are used. In particular, various methods for wireless communication such as WLAN, 3G and Bluetooth are emerging.

15

With emerging of these wireless communications technology that will allow for easier communications between mobile devices, once a handheld computer is equipped with the these wireless communications hardware, it can communicate wirelessly with other wireless communications equipped devices within 10 m including other handheld computers, mobile phones, desktop PCs, and printers. It can be used to form local wireless networks or to allow devices to communicate directly. It can potentially provide a wireless means of transferring data from a handheld device to a desktop PC in a project field office. The implication for the construction site will be that information can be transferred between users at the construction site more easily as these various types of data networks emerge (Figure 2.1) (McDonough, 2001).

Figure 2.1: Mobile Communication Networks for Construction Project Team Source: C.J. Anumba, 2003

2.5.1

Introduction to Wireless Communication

The 1G period began in the late 1970s and lasted through the 1980s. These systems featured the first true mobile phone systems, known at first as "cellular mobile radio telephone." These networks used analog voice signaling, and were little more sophisticated than repeater networks used by amateur radio operators. The 2G phase began in the 1990s, and much of this technology is still in use. The 2G cell phone features digital voice encoding. Examples include CDMA, TDMA, and GSM. Since its inception, 2G technologies have steadily improved, with increased

16

bandwidth, packet routing, and the introduction of multimedia. The present state of mobile wireless communications is often called 2.5G.

3G is a short term for third-generation wireless, and refers to near-future developments in personal and business wireless technology, especially mobile communications. This phase is expected to reach maturity between the years 2003 and 2005. The third generation, as its name suggests, follows the first generation (1G) and second generation (2G) in wireless communications. Ultimately, 3G is expected to include capabilities and features such as: •

Enhanced multimedia (voice, data, video, and remote control)

•

Usability on all popular modes (cellular telephone, e-mail, paging, fax, videoconferencing, and Web browsing)

•

Broad bandwidth and high speed (upwards of 2 Mbps)(Figure 2.2)

•

Routing flexibility (repeater, satellite, LAN)

•

Operation at approximately 2 GHz transmit and receive frequencies

•

Roaming capability throughout Europe, Japan, and North America

Figure 2.2: Comparison of Various Network Speed through Packet Download Test Source: Maxis, 2005

While 3G is generally considered applicable mainly to mobile wireless, it is also relevant to fixed wireless and portable wireless. The ultimate 3G system might be operational from any location on, or over, the earth's surface, including use in

17

homes, businesses, government offices, medical establishments, the military, personal and commercial land vehicles, private and commercial watercraft and marine craft, private and commercial aircraft (except where passenger use restrictions apply), portable (pedestrians, hikers, cyclists, campers), and space stations and spacecraft.

Proponents of 3G technology promise that it will "keep people connected at all times and in all places." Researchers, engineers, and marketers are faced with the challenge of accurately predicting how much technology consumers will actually be willing to pay for. (Recent trends suggest that people sometimes prefer to be disconnected, especially when on vacation.) Another concern involves privacy and security issues.

2.6

PDA's History and Features

The first prototype of hand held organizer was developing by the Psion in the mid-1980s and later in spring of 1984, Psion had launched its first organizer in the world which is Psion 1. The Psion 1 was slightly longer and thicker than a large pack of cigarettes and was built using the 8-bit technology. Besides that, Psion 1 is using the 10 K character storage to store its data and it’s also performed basic organizer functions such as recording a phone book, address and daily schedule. The Psion is using only 16-character mono chrome LCD display.

The launch of the Psion 1 was very successful and later in year 1986, the Psion II was been develop and launch. This Psion II is more powerful than the Psion 1 and it had 64 K ROM and 32 K RAM memory for a bigger data storage and also a wide 4 x 20 character display for a wider display purpose and then later the Series 3a

18

Psion which is representing a new generation of PDAs. The Psion Series 3a was created based on 16-bit technology and with LCD which consist of 40 characters x 8 line. The Psion Series 3a at that time also consist of 58-key keyboard and this PDA was the first built to link to desktop PC for data transfers. However the Psion Series 5 had been created with followed up the success of the 3a which is base on 32-bit technology on its mobile processor. The display screen of the Psion Series 5 had been enlarge to screen (640 x 240 pixels) and also enlarged keyboard to date

In 1993 Apple Computer Inc. tried to copy Psion's success, Apple Computer Inc. had introduced the world to the first PDA, the Newton®. They were dubbed PDAs (personal digital assistants) by John Sculley, former chairman of Apple Computer Inc, and were sold as the ultimate information appliance. Sculley predicted PDAs would become ubiquitous tools that would hold telephone numbers, keep your calendar, store notes, plus send and receive data wirelessly. Although, the Newton was not able to deliver all of those features at the time it was released.

For the next three years, PDA sales dwindled, and were almost off the charts. Then, in March 1996, Palm™, Inc. delivered the industry's first truly compelling handheld computer, the PalmPilot. A robust yet small go-anywhere device that helped people manage and organize their personal and professional lives by providing instant, anytime access to schedules, important phone numbers, to-do lists and other key information. This new type of information management was met with tremendous acceptance. Mobile, busy people embraced the small and powerful Palm™ handhelds. Today, Sculley's predictions have come true in the form of the Palm™ VII, the first and only wireless data transfer PDA. New PDAs which is call Pocket PC is continue to arrive from Palm™, Psion/Symbian, IBM, Apple, Compaq, HP, Motorola, Sony, and others.

19

2.6.1

History of Pocket PC

On April 19th, 2000, that Microsoft unveiled the new handheld OS which built main core to support and driven operating in the Palm-size PC time which call Windows CE 2000 and it is the first operating system use in the Compaq Aero 2180 . But before Pocket PCs were released, there were other Windows-based machines of the same form factor made by HP, Philips, and others called Palm-size PCs. These devices ran Windows CE 2.0–2.11 and had an interface that was nearly identical to the then-current desktop version of Windows, Windows 98. The launch of Windows CE 2000 and Compaq Aero 2180 had convinced everyone that in the near future, the world can expect the next step in PDA performance in the smart phone. It will combine a wireless phone will all of the functions of a PDA.

In the previous operating system, Microsoft Windows Mobile 2003 for Pocket PC, consists of the Windows CE.NET 4.2 operating system bundled with scaled-down versions of many popular desktop applications, including Microsoft Outlook, Internet Explorer, Word, Excel, Windows Media Player, and others. Past Pocket PC operating systems include Pocket PC 2002 (launched October 2001) and Pocket PC 2000 (launched April 2000), both running Windows CE 3.0 underneath. But in now days, Microsoft's current release is Windows Mobile 2003 Second Edition, which adds native landscape support as well as other fixes and changes to those features already present in the original release of WM2003. The first device to come with 2003SE was the Dell Axim x30.

Windows Mobile 5, internally code-named Magneto, was officially released by Microsoft on May 10, 2005. Based on Windows CE 5.1, Windows Mobile 5 incorporates features such as Direct3D Mobile, integrated Bluetooth and WiFi stacks, and the ability to be mounted as a USB Mass Storage device, bypassing ActiveSync. Pocket Word and Pocket Excel have been renamed Word Mobile and Excel Mobile, respectively, and both applications have gained more complete feature sets, including support for tables, ordered lists, and embedded graphics in Word

20

Mobile, and support for charts in Excel Mobile. PowerPoint Mobile, a new addition to the Office Mobile suite, supports the ability to display and edit PowerPoint presentations on a Pocket PC. Windows Mobile 5 also improves support for onehanded usage by inserting two, context-sensitive "soft" buttons at the bottom of the screen which can be mapped to hardware buttons on any specific device.

Windows Mobile 5 marks the convergence of the Phone Edition and Professional Edition operating systems into one system that contains both phone and PDA capabilities. A 'Phone' application is now included in the OS, and all PIM applications have been updated to interface with it. Windows Mobile 2005 is compatible with Microsoft's Smartphone operating system and is capable of running Smartphone applications.

Pocket PCs running previous versions of the operating system generally stored user-installed applications and data in RAM, which meant that if the battery was depleted the device would lose all of its data. Windows Mobile 5 solves this problem by storing all user data in the ROM, leaving the RAM to be used only for running applications, as it would be on a desktop computer. As a result, Windows Mobile 5 Pocket PCs generally have a greater amount of flash ROM, and a smaller amount of RAM, compared to earlier devices.

2.6.1.1 Feature of Pocket PC

A Pocket PC is a handheld-sized computer that runs a specific version of the Windows CE operating system. It has many capabilities of modern desktop PCs. Currently there are thousands of applications for Pocket PC, many of which are Freeware. Some of these devices, running Microsoft Windows Mobile 2003 Phone Edition, also include mobile phone features. Pocket PCs can also be used with many other add-ons like GPS receivers, barcode readers, and cameras.

According to

21

Microsoft, the Pocket PC is "a handheld device that enables users to store and retrieve e-mail, contacts, and appointments, play multimedia files, games, exchange text messages with MSN Messenger, browse the Web, and more."

Pocket PC is commonly abbreviated as "PPC". From a technical standpoint, "Pocket PC" is a standard from Microsoft that sets various hardware and software requirements for mobile devices bearing the "Pocket PC" label.

For instance, any device which is to be classified as a Pocket PC must: •

Run Microsoft's Windows CE (Pocket PC version) operating system

•

Come bundled with a specific suite of applications in ROM

•

Include a touch screen

•

Include a directional pad or touchpad (case of HP iPAQ hx4700)

•

Include a set of hardware application buttons

•

Be based on a ARM version 4 compatible CPU, Intel XScale CPU, MIPS CPU or SH3 CPU.

•

Pocket PC 2002 (Codename Merlin) works only with ARM-based CPUs.

2.7

Previous Thesis Review on Construction Check List

Quality control and safety represent increasingly important concerns for project managers. Defects or failures in constructed facilities can result in very large costs. Even with minor defects, re-construction may be required and facility operations impaired. Increased costs and delays are the result. In the worst case, failures may cause personal injuries or fatalities. Accidents during the construction process can similarly result in personal injuries and large costs. Indirect costs of

22

insurance, inspection and regulation are increasing rapidly due to these increased direct costs. Good project managers try to ensure that the job is done right the first time and that no major accidents occur on the project.

Therefore, inspection process at the construction site is an important process and necessary to be conducted by the construction project supervisor such as engineer and technical assistant to ensure that the construction project is complying to the specify work standard, specification and guide line.

In order to do so, a study on standard defect checking list in thesis of “Penyediaan Senarai Semak untuk Pemeriksaan di Tapak Bina bagi Kegunaan Jabatan Kerja Raya, Penampang Sabah” was carried out for the purpose of identifying the process involve and the problems encountered while carrying out the inspection at the construction site. Later at the end of the research, a standard electronic defect check list which is common use by Public work Department (PWD) had been created.

Science this thesis was been done in year 2005, so most of the data and result had been consider up to the date and will be adopted and under taking into count for the support of this research. Besides this, the literature study on the thesis of “Penyediaan Senarai Semak untuk Pemeriksaan di Tapak Bina bagi Kegunaan Jabatan Kerja Raya, Penampang Sabah” will be used prior to developing of the interview pilot questionnaire.

23

2.8

Result From the Literature Study

From the literature study of “Penyediaan Senarai Semak untuk Pemeriksaan di Tapak Bina bagi Kegunaan Jabatan Kerja Raya, Penampang Sabah”, it is clearly show that check list is one of an important tool for a project manager to supervise the construction site. This thesis also cites one project will become more a manageable and quality and the problem will also become easily trace in the project earlier stage. Besides this, with the use of check list in construction site supervision, the changes of over look due to human error will also been reduce to minimum.

Result from the thesis literature study also clearly identify out that the common traditional construction process are as listed below.

CHECKING ON SITE PREPARATION

PREPARATION OF SITE FACILITIES CHECKING ON STRUCTURE WORKS CHECKING ON ELECTRICAL WORKS CHECKING ON PLUMBING WORKS CHECKING ON BUILT-INFITMENT WORKS CHECKING ON FINISHING WORKS CHECKING ON SITE CLEARANCE

Figure 2.3: Checking Process at Construction Site

24

2.9

Result from Thesis Research

The thesis of “Penyediaan Senarai Semak untuk Pemeriksaan di Tapak Bina bagi Kegunaan Jabatan Kerja Raya, Penampang Sabah” had carried out its research in the area of:a. Problem in construction site b. The level of PDA demanding in construction c. The Activity which need most check list in construction d. The level of need in check list e. The suggestion of further improvement f. Creating the most common use checking list in electronic format

2.9.1

Problem in Construction Site

Result from the thesis research on the problem facing while the field engineer or technician carried out their field work are as below:-

25

Table 2.2 : Level of Problems Occurred During Site Checking Problems Occurred Identified the quality for structure construction materials Identified the type of structure construction materials Identified quality for finishing materials Checking done without check list Identified type of finishing materials Lack of references for carrying out checking No knowledge about what to check No knowledge about the next steps No knowledge how to carry out the site checking Lack of confident on checking techniques Source: Nelliah Sittor 2005

2.9.2

Number/Percentages of Respondents

Indices of Importance

Level

≤2 (most problem)

0.51

1

4

44.44%

3

33.33%

2

22.22%

0.44

2

5

55.56%

3

33.33%

1

11.11%

0.44

3

5

55.56%

4

44.44%

0

0.00%

0.42

4

6

66.67%

2

22.22%

0

11.11%

0.42

5

5

55.56%

4

44.44%

0

0.00%

0.36

6

8

88.88%

1

11.11%

0

0.00%

0.33

7

7

77.78%

2

22.22%

0

0.00%

0.33

8

7

77.78%

2

22.22%

0

0.00%

0.33

9

7

77.78%

2

22.22%

0

0.00%

0.31

10

7

77.78%

2

22.22%

0

0.00%

3 (moderate)

≥ 4 (less problem)

The Level of PDA Demanding in Construction

Result from the thesis research it had clearly shows that there is a high demanding on personal digital assistant due to the massy construction environment.

Table 2.3 : Valuation on the Uses of Pocket Personnel Computer Site Valuation

Average Score

Use of Pocket Personnel 2.56 Computer Source: Nelliah Sittor, 2005

Number/Percentages of Respondents ≥ 4 (Not Agree)

4

44.44%

≤2 (Most Agree)

3

33.33%

3 (Fine)

2

22.22%

26

2.9.3

The Activity Which Need Most Check List in Construction

Result from the thesis research it had short list out the construction process which mostly need in check list management.

Table 2.4 : Activity Which Need Most Check List Types of Works which Required Check List Site clearance after completion Preparation of finishing Pipe installment Site preparation Installment of build-infitment Preparation of site facilities Structure works Electrical works

Number/Percentages of Respondents

Indices of Importance

Level

0.40

1

6

66.67%

2

22.22%

1

11.11%

0.38 0.36 0.36

2 3 4

6 7 6

66.67% 77.78% 66.67%

2 1 3

22.22% 11.11% 33.33%

1 1 0

11.11% 11.11% 0.00%

0.36

5

6

66.67%

3

33.33%

0

0.00%

0.33

6

7

77.78%

2

22.22%

0

0.00%

0.31 0.31

7 8

7 8

77.78% 88.88%

2 1

22.22% 11.11%

0 0

0.00% 0.00%

≤2 (Most Need)

3 (Moderate)

≥ 4 (Less Need)

Source: Nelliah Sittor, 2005

2.9.4

The Level of Need in Check List

The thesis study also indicates that the levels of need in check list in construction are clearly showed as below (Table 2.5).

27

Table 2.5 : The Level of Need in Check List Usages of Check List Most helpful in checking Acceleration on checking Easier for checker Provide knowledge for checker Provide clearer about the site progress work Controlling on quality of works Preparing of consistent, systematic and standard of check list Prevent careless during checking

Number/Percentages of Respondents

Indices of Importance

Level

≤2 (Most Agree)

0.31

1

7

77.78%

2

22.22%

0

0.00%

0.31

2

7

77.78%

2

22.22%

0

0.00%

0.31

3

7

77.78%

2

22.22%

0

0.00%

0.31

4

7

77.78%

2

22.22%

0

0.00%

0.31

5

8

88.88%

1

11.11%

0

0.00%

0.29

6

8

88.88%

1

11.11%

0

0.00%

0.29

7

8

88.88%

1

11.11%

0

0.00%

0.29

8

8

88.88%

1

11.11%

0

0.00%

3 (Fine)

≥ 4 (Not Agree)

Source: Nelliah Sittor, 2005

2.9.5

The Suggestion of Further Improvement

From the study, it had show that the industry need more improve to achieve better quality. The suggestions of improvements are show as follow (Table 2.6).

Table 2.6 : Proposal on Improving the Site Checking System No.

Proposal on Improving the Site Checking System

a)

Site Supervisor should has knowledge on checking

b)

Preparing a quality plan and report on checking

c)

A on the spot tools needed to record the detail of checking to avoid losing any data and easier in downloading in personnel computer. That particular tool should be user friendly and easier for understanding. Training about the uses of that tools should be provided.

d)

Keep in touch with the architect and engineer if there is a problems occurred.

e)

There are at least 2 persons in charge on the site checking.

Source: Nelliah Sittor, 2005

28

2.10 Conclusion

As a conclusion, the thesis of “Penyediaan Senarai Semak untuk Pemeriksaan di Tapak Bina bagi Kegunaan Jabatan Kerja Raya, Penampang Sabah” had justified the facts that there is a need of check list in local construction field to counter the existing problem. Never than less the thesis also cited there the construction industry is need of mobile inspection which will transmit has information instantaneously backed to the office.

Besides this, the study on the introduction to wireless communication help on improving the knowledge of how the telecommunication system now day provide their services on information transmitting and retrieving.

Nevertheless the

background study on Personal Digital Assistant (PDA) feature and history will getting to know the personal digital assistant’s feature and function more detail and also increasing the capability of personal digital assistant’s usage range in construction field.

“Good IT is an essential part of improving the efficiency of construction”. (Sir John Egan,1998) .

CHAPTER 3

3RESEARCH METHODOLOGY

3.1

Introduction

There are various steps that can be adopted to fulfill the objectives of this study. The research methodology for this research includes discussion on method of data collection, the approach used, research consideration such as design of questionnaire and data analysis.

3.2

Research Process

The research process for this thesis mainly was divided in to 2 phases. In the first phases, this research involve literature reviews, an industry interview will be conducted on construction firm to identify the most commonly used standard checklist. A pilot questionnaire, drafted from the findings of literature will be used

30

prior to developing of the interview questionnaire.

Analysis of data from the

interview questionnaire will be conducted for selecting and ranking of the most common use defect check list. Data collection for interview in this study will carried out within the Perak and Johor. Data collection is made through by interview the potential contractor or developer face to face. After that data will be analyze using Statistical Package for Science Social 11.0 (SPSS).

Later on, in second phases of this research will involve the rapid prototyping method in process of creating prototype development of a prototype as a primary platform for defect check list which will use in PDA.

31

Figure 3.1 Steps in Methodology

32

3.3

Literature Review

The main aim in carrying out the literature reviews is to ensure basic understanding of the topic itself. It is also a method to analyze former study within the scope of the topic. It has been done by referring to articles, journals, paperwork, thesis and also relevant books. For this study, the related books that related to Personal Digital Assistants (PDA) As A Mobile Inspection System At Construction is limited number, so journal papers and proceeding help the researcher to get the information.

This research also review on the previous researcher’s research on “Penyediaan Senarai Semak Untuk Pemariksaan Di Tapak Bina Bagi Jabatan Kerja Raya Penampang Sabah”(Nelliah Sittor, 2005) to retrieve the standard defect check list which will use in the construction. Later, a pilot questionnaire, drafted from the findings of literature will be used prior to developing of the interview questionnaire.

3.4

Interview

Interview will be carried out with the management level officer from the developer or the contractor at construction industry with the questionnaire which had been develop from literature review to determine the most common and practical used defect check list.

33

3.4.1 Interview Questionnaire Design

Basically the interview question will design into 3 parts for try to gathering the information about defect management in the company from the interviewer and the sample are provided in Appendix A.

a. General Information In this part the question will design to get the background and basic information of the interviewer.

Besides this, this part will also try to determine how

experience is the targeted interviewer which will be used to later in judging the performance of the prototype.

b. Current Defect Working and Communication System In this part, the question of interview will be design to approach the interviewer to find out how is the current defect business process exists in their existence company and what is specification they need if there is such defect inspection prototype.

c. Aspect of IT In this part, the interview question will design to find out how well is the company make good use in Information Technology (IT) to manage their daily defect communication with outsider and insider.

34

3.5

System Design

In order for develop a system which will cater PDA’s functionality web application in web portal, earlier stage of system concept will be design using the Data Flow Diagram (DFD) technique for activity modeling to show the input and output and also a breakdown of each of the main process (De Marco, 1978). Later in order to develop a prototype, a rapid prototyping method will be adopted.

3.6

Introduction to Rapid Prototyping

In rapid prototyping interactive prototypes are developed which can be quickly replaced or changed in line with design feedback. This feedback may be derived from colleagues or users as they work with the prototype to accomplish set tasks (Figure 3.1).

Figure 3.2: A Model of Rapid Prototyping

This method is concerned with developing different proposed concepts through software or hardware prototypes, and evaluating them. In general the process is termed ‘rapid’ prototyping. The development of a simulation or prototype of the

35

future system can be very helpful, allowing users to visualize the system and provide feedback on it. Thus it can be used to clarify user requirements options. Later on in the lifecycle, it can also be used to specify details of the user interface to be included in the future system.

Figure 3.3: Comparing Design and Development within Rapid Prototyping and Formative Evaluation

3.6.1 Method

A general procedure for adopting the rapid prototyping method is outlined below:a. Allow enough time to create the prototype. If the prototype is to be evaluated with users then allow time to design relevant tasks, recruit the users, evaluate the prototype and report the results. b. Assemble the necessary equipment, including the hardware and software tools necessary to create the interactive prototype. c. Develop the prototype itself. d. Select appropriate users to test the prototype, trying to cover the range of users within the target population. A facilitator will also be required to instruct the users and run the evaluation.

36

e. Prepare realistic tasks to occupy the users as they work with the prototype. f. Pilot the evaluation procedure and ensure the prototype can be used to accomplish the tasks. g. Ensure recording facilities are available and functioning. h. Conduct each session. The facilitator instructs the user to work through the allocated tasks, interacting with, and responding to, the system as appropriate. i. If necessary additional information can be obtained by interviewing users following their use of the prototype. Debrief and thank the user. j. Analyze the obtained information and then summaries the observations and user evaluations. Determine the themes and severity of the problems identified. k. Summaries design implications and recommendations for improvements and feed back to design team. Video recordings can support this. l. Where necessary refine the prototype and repeat the above process.

When using this method, it is important avoid spending too long on the development of initial prototypes as user evaluation may result in substantial changes. Also, avoid making the prototype too polished as this may force users to accept it as finished. Do not put in features that will raise the users expectations but which are unlikely to be achieved with the real system (e.g. too fast response times, too sophisticated graphics) and do not put too much effort into particular features (e.g. animations) which may not be required.

37

3.7

Prototype Testing

When user are satisfy with the prototype been develop using rapid prototyping method, the prototype will be try run in a real construction area with the input of realistic data. Later, the comparison in using traditional method of inspection system with new mobile inspection system will carried out and the result of this comparison will be used as the indicator to show the result of this research.

3.8

Conclusion

As a conclusion of the research method, all the literature review of PDA in construction, the review of the standard electronic checklist and the interview will be done in the first phase of this research. However, the system concept design using the DFD modeling technique and the prototype development using rapid prototyping method will be carried out in the second phase. The successful of this research will be shown at the result from the comparison of using traditional method of inspection system with new mobile inspection system.

CHAPTER 4

4ANALYSIS AND SYSTEM DESIGN

4.1

Analysis of Interview Situation

4.1.1 Introduction to Qualitative Data

Since the data collection are from interviewing the managing or directing personnel at Developer Company. As a result, the data which collected will qualitative data. Content analysis will carried out after reviewing the short note written down during the interview and latter the data will be assign a coding to pieces of text that represent either important concepts, common patterns between respondents, or distinct responses by different subgroups. Isolate text associated with each code and then group it together by category. Categories can be predetermined (chosen at the time the instrument is developed) or emergent (chosen after examining the data).

39

4.1.2 Coding Steps

4.1.2.1 Initial Coding

It’s usually best to start by generating numerous codes as you read through responses, identifying data that are related without worrying about the variety of categories. Because codes are not always mutually exclusive, a piece of information might be assigned several codes.

4.1.2.2 Focused Coding

After initial coding, it is helpful to review codes and eliminate less useful ones, combine smaller categories into larger ones, or if a very large number of responses have been assigned the same code, subdivide that category. At this stage you should see repeating ideas and can begin organizing codes into larger themes that connect different codes. It may help to spread responses across a floor or large table when trying to identify themes.

40

4.2

The Defect Management Requirement From of the Industry

4.2.1 Usage of Defect Inspection Check List

To analysis this section, the initial coding used is word of “defect”. Then by care fully study through the interview note, it can be conclude that from the data analysis, the data shows that 3 out of 5 of the developer do use a proper defect check list to carried out their daily defect inspection job. This is about 60 % of the respondent do agree that they use a defect inspection list.

The other 40% of respondent are use of quality inspection form to carry out their defect inspection job.

40% USE DEFECT INSPECTION LIST 60%

USE QUALITY CHECK LIST

Figure 4.1 : Usage of Defect Inspection Check List

4.2.1.1 Comparison of Defect Inspection Check List as Criteria to Select Test Field Company

Due to this project prototype is develop base on the standard defect inspection form, there fore the defect inspection check list similarity is the priority to

41

determine which company will be chosen as a sample of prototype testing field. From the interview data collection at all the company, the company who use the defect inspection list in their defect checking work been selected, and their defect checking list was been collected to analysis the similarity of defect checking item compare with the standard inspection list which is been produce in previous thesis. As a result from that the Company A was been chosen.

4.2.2 Party Involve in the Defect Management

Poor communication has long been a problem in the Project Management. Part of the trouble is the way the industry is organized. The project team is made up of people from many different firms. Their contributions vary and a lot of information has to pass among them. This requires a well-organized network of communication. Even when this network exists, communication still breaks down at a personal level, because people fail to keep their messages simple; they pass on too much information or too little; the information they give is inaccurate or misleading (Fryer, 2002).

As a result from the interview, it show that number of a layer of organization need to pass through in order to reach down site personnel or contractor

Table 4.1 : Analysis Result of an Organisation Layer Company Name

Number Of Layer

COMPANY A

5

COMPANY B

6

COMPANY C

5

COMPANY D

5

COMPANY E

4

42

Conclusion from this analysis is there is a need of a work station which will solve the problems of lost information or information barrier in a multi layer organization as said by Fryer (2002).

4.2.2.1 Defect Management Organization in Selected Company

The party of defect management involve in the targeted company are shown in the Figure 4.2. From that figure, we can see the transmitting of defect information from the below to top need to pass through 5 level. Therefore according to Fryer (2002) once again, the information lost will occur when past through each layer of organization, therefore the defect inspection system which design for this targeted must consist a feature where every one will have a charges of information sharing.

43

Decision Making

PROJECT DIRECTOR

Mana ging PROJECT MANAGER

SITE MANAGER

CONSULTANT

ARCHITECT

Technical

Field Personnel

QUANTITY SURVEYOR

SITE ENGINEER1

SITE ENGINEER2

SITE ENGINEER3

CLERK OF WORK 3

CLERK OF WORK 4

Direct Labour

CLERK OF WORK 1

CLERK OF WORK 2

CONTRACTOR BY TRADE

Legend: Information Flow of Communication

Figure 4.2 : Defect Communication from Top Management till Contractor

44

4.2.3 Current Inspection System / Method

From the analysis of interview short note, it shows that the business process of defect inspection system is in serial mode and time consuming. Most of the time, the same process is repeating in other group.

From the data of interview question of 3.1 How is the final inspection’s data been stored in your company? The result shows that there is sign of data reentry exist in each company and it is 80% from the overall sample.

DATA STORE IN HARDCOPY 20%

DATA TO BE REENTER INTO SOFTCOPY 80%

Figure 4.3 : Percentage of Date Reentry

This is because most the company are renter the defect data from hardcopy into softcopy for proper defect short out according to PTD number and also to serve for electronic documentation purpose.

The analysis from the interview question of 3.3 normally, how is your company sort out final inspection’s data? Show’s that most of the company still done the repeating same paper work manually to short out PTD number according to project site and it is about 80% from overall project.

45

INFORMATION BEEN REPEATING SHORT OUT MANUALLY ACCODING TO PROJECT 80%

INFORMATION BEEN PROCESS AND CARTAGORIZED ACCORDING TO PROJECT USING SOFTCOPY 20%

Figure 4.4 : Data Short Out Method According to Project

For question of 3.4 Do you have a special formatting for contractor to make a reply on your request? It shows that the level of need in proper standard format in documentary management system so that all the document will be standardize for easy management and it is about 20% of overall company already implement to use standard format in documentary management system.

46

NO

20% 40%

YES

40%

IS GOD TO HAVE ONE

Figure 4.5 : Level of Need in Standard Document Format

4.2.4 Business Process Defect Inspection System for Current Selected Company

From the result of the analysis before show that there is a need of automation defect management system which is design to eliminate the data reentry problems and also automation in documentary management. Therefore a system in auto generation of standard defect inspection report will be design and the information entry is list out as sample form (Form 4.1) below.

47

QUALITY FORM

Reference

: QF-ABW

Page

: 1 of 3

ARCHITECTURAL & BUILDING Release Revision No. WORKS Date

: 1 : 0 : 1 March 2006

ARCHITECTURAL WORK INSPECTION FORM FOR CFO PROJECT

:

Please make arrangement to inspect the following unit :BLOCK

UNIT

LEVEL

ITEM

PICTURE

CONDITION

COMMENT

Form 4.1 : Quality Form for Inspection System

48

4.3

Introduction to Mobile Inspection System Design

From the literature study at section 2.8, it had clearly showed out the construction industry now days are needed a mobile defect inspection system. Therefore a new Mobile Defect Inspection System (MDIS) prototype which is design to manage and inspect the defect to more effectively and up to a state where there is a time and cost saving and also reduce the work load. And is so simple and easy to use since there is no installation required or high computer skill is needed.

With combining the Mobile Device technology, Cellular Network support and Portal support, real time data entry can be done easily in to this defect management system Portal Server and then the current defect scenario at the construction site will been reported. Defect inspection process can be done easily by using the mobile device for defect data and picture recording at any where any time without carrying a heavy plan or a bunch defect recording sheet (Figure 4.6).

Figure 4.6 : Basic Mobile Inspection Concept at Construction Site

49

With the Automation feature of portal, a defect repot will created to a correspondent party to respond instantly. And by the mean time the administrator also can make their decision or judgment base on the real time defect report update from the system.

Finally, since this system is automation, easy data entry and respond instantly. Problems of Data missing, data reentry or fragmentation in defect communication will be solved. Besides this each party involve in this system will bring to more closely on each other.

4.3.1 Database Design

The construction industry involves several disciplines with a complex network of communications between these disciplines (Egan, 1998). Currently, all the stakeholders in a construction project communicate with one another individually with faxes, telephone networks and in some cases via electronic mail (Hibberd, 2000). This kind of one-to-one correspondence can make the communication network very complex resulting in a “spider web” network

So, in here the traditional business process will be reengineering. From the result of the Figure 2 in interview analysis, it show out the targeted company is now facing a traditional chaos in the defect communication (Figure 4.7), therefore a database which function as a centralized server (Figure 4.8) will be created to server a multi party communication and also information sharing.

50

DIRECTOR CONTRACTOR BY TRADE

SITE MANAGER

QUANTITY SURVEYOR

CLERK OF WORK 2

ENGINEER 2 CONSULTANT

ARCHITECT

PROJECT MNAGER

Figure 4.7 : Spider Web

DIRECTOR CONTRACTOR BY TRADE

SITE MANAGER

QUANTITY SURVEYOR

CLERK OF WORK 2

Database Server

ENGINEER 2 CONSULTANT

ARCHITECT

PROJECT MNAGER

Figure 4.8 : Centralized Network

4.3.1.1 DFD of Inspection Process

The data flow diagram (DFD) is an excellent communication tool for analysis to model process and functional requirements. It is the graphical presentation of system showing their active components and data interface between them. DFD was one of the primary tools of the structure analysis efforts in the year of 1970’s. It was develop and enhanced by Yourdon, McMenamin, Palmer, Gane and Sarson and until today, the DFD still consider as a best mdelling techniques for eliciting and representing the processing requirement of a system (Zamri M et al, 2004).

51

From the result of the interview, it shows that the inspection the traditional business process of defect inspection system in the targeted company was as shown in Figure 4.9.

Figure 4.9 : Traditional Defect Management Business Process

After reengineering, the defect management process with the aid of MDIS will look like Figure 4.10.

52

Figure 4.10 : Defect Management Business Process after Reengineering

DFD diagram been created after the reengineering Defect Inspection Process, for the purpose to identifying the data entry require. Beside this, the DFD also help in showing the type of information and entity related in the process flow. Therefore DFD for targeted company had been created as Figure 4.11.

Figure 4.11 : Data Flow Diagram (DFD) for Targeted Company

53

From the DFD above, it clearly shows that the data entry needed to be download by the portal to inspector’s PPC are: 1. A Selected standard defect Inspection list form 2. Listed PTD need to be Inspect 3. List of Inspection type 4. Type of Building

And the feed back from the inspector PPC to portal system was a filled selected standard defect inspection form which contained :1. PTD number of the houses contain defect 2. Condition of defect at particular selected defect type 3. Location of the defect 4. Contractor responsible 5. Comment 6. Picture (if any)

After all the information was completely send to the database portal, then the output from the portal of MDIS system will automatically generate a list defect report to a responsible contractor and also a report to system administrator about the currently number of logged defect and the number of defect completely been fixed (Figure 4.12).

54

Figure 4.12: Data Flow for Input and Output from MDIS

4.3.1.2 Introduction to Data Modeling Overview

A data model is a conceptual representation of the data structures that are required by a database. The data structures include the data objects, the associations between data objects, and the rules which govern operations on the objects. As the name implies, the data model focuses on what data is required and how it should be organized rather than what operations will be performed on the data. To use a common analogy, the data model is equivalent to an architect's building plans.

From the DFD diagram Figure 4.13 above, it already show that the data and the input that need to feed in the database system in order to process and keep the record of defect logged by the field inspector, a brief draft map of the database of MDIS had been created as Figure 18 below.

55

Figure 4.13 : Database Structure of MDIS

4.3.1.3 Data Structure of Inspection System

From the Figure 12 above, the basic concept for the MDIS database structure concept is the whole MDIS system is been built up form 7 key element which is:-

A. List Of Standard Defect Check List A standard defect check list propose by the previous researcher (Nelliah Sittor, 2005) which consist of 10 type most commonly use defect check list

B. Inspection Information A part which will contain necessary information to access current inspection such as inspection type, type of buildings project name and block name.

56

C. Employee Information A part which consist of basic information of all the employee involve in the project team and it is including the inspector’s background information which will be use to assign to a selected project defect inspection.

D. Level A part consist of level information which is use for accessing a multi storied building

E. Location A part which hold information of section in a building, example: Car park, Master Bedroom and Kitchen.

F. Contractor Information A part where all the necessary basic background information of contractor will be store at. Example: Contractor’s trade

G. PTD Number PTD number was a very unique lot number which is register and assign by the land office of Malaysia to a particular lot of land or property, therefore this section will hole the information of the PTD number which will be use as a unique primary key to store defect information.

In the creation of database, Microsoft Access was been choose as a primary software use to manage and creation of this MDIS database in earlier stage, because due to the good database creation and management feature which is design in the Microsoft Access. Later when in the implementation of MDIS in the web portal,

57

Active Server Language will be use to access server for retrieve and update of MDIS portal database.

4.3.1.4 ERD Model of Inspection System

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way to unify the network and relational database views. Simply stated the ER model is a conceptual data model that views the real world as entities and relationships. A basic component of the model is the Entity-Relationship diagram which is used to visually represent data objects. Since Chen wrote his paper the model has been extended and today it is commonly used for database design for the database designer, the utility of the ER model is: •

It maps well to the relational model. The constructs used in the ER model can easily be transformed into relational tables.

•

It is simple and easy to understand with a minimum of training. Therefore, the model can be used by the database designer to communicate the design to the end user.

•

In addition, the model can be used as a design plan by the database developer to implement a data model in specific database management software.

4.3.1.5 Entities

Entities are the principal data object about which information is to be collected. Entities are usually recognizable concepts, either concrete or abstract, such as person, places, things, or events which have relevance to the database. Some specific examples of entities are employees, projects, location. An entity is analogous to a table in the relational model.

58

An entity design in especially for MDIS using Microsoft Access is as Figure 4.14.

Figure 4.14 : Entity-Relationship Model

4.3.2 System Design

To serve the purpose of mobile inspection system, basically the MDIS system is design to support two separate system parts, where one part is an in moveable part such as Pocket PC which run at window CE system, and other part is to serve a workstation which is in moveable in the office for administration purpose such as Microsoft Windows 98 OS and above. (Figure 4.15)

59

Figure 4.15: Mobile Defect Inspection System (MDIS) Main System Topology

The mobile support part in MDIS system is design to let user to enter the data and information at any place and any time. This mean the user need not back to office for renter the data back into the work station and process the data, because all the data and information of this MDIS is store in the internet portal server. Therefore, the user of the MDIS system can retrieve and store information where ever they go and where ever the site is located, provided as long as there is a cellular network signal and can connect to internet.

This MDIS system are design to connect to internet using cellular network because the cellular network was the most far area coverage then using a signal booster. Nevertheless the cellular network in Malaysia now days are almost cover the develop area with the speed up to 2Mbps (Figure 4.16).

60

Figure 4.16: Cellular Coverage in Malaysia

However on the other hand, the MDIS system also designs to including the non moveable unit such as work station in the office. This is to serve the purpose of defect report reference system to contractor who involve in the project and also to serve the purpose of system admin in database maintenance and also MDIS core system maintenance.

4.3.2.1 Hardware and Software Requirement

To use this MDIS system in the mobile unit, it is suggests that the POCKET PC is require to serve the best performance due to multiple functional feature (Detail of the feature has been discussed in Chapter 2).

However the basic hardware

specification for mobile unit to use the MDIS system shows at Table 4.2.

61

Table 4.2: Hardware Requirement for Handheld Unit Unit Type Processor Ram Rom O/S Display Connectivity

Input Method

POCKET PC ARM 255 MHz and above 32 MB 32 MB Microsoft® Pocket PC 2002 and above 3.5" 240 x 320 16 -bit color transflective TFT USB synchronization cable, Bluetooth or WIFI for connecting to internet via GPRS,EDGE or 3G, Wireless GSM jacket Stylus (Soft keyboard)

The software requirement for the MDIS in the mobile unit are only require Microsoft Win CE 2002 and above and the web browser which are able to run the java script. How ever, in this master project third party web browser “NetFront V3.1” from ACCESS CO. LTD was use due to its stability and browser access speed.

On the other hand, the hardware requirements to serve the best performance of in moveable unit such a workstation are show as the Table 4.3 below.

Table 4.3: Hardware Requirement for Workstation Unit Type Processor Ram O/S Connectivity

IBM compatible personal computer Pentium ( or equivalent) processor ( 800 MHz or above recommended ) 64 Mb ( 128 recommended ) Microsoft Windows 98 and above Via Cable modem in 50k or Via ASDL modem in STREAMYX

Software requirement for MDIS at the workstation is not limited due to the OS provided is powerful enough to process the IO from the workstation hardware.

62

4.3.2.2 System Platform

As mentioned in earlier, the MDIS system is design to support across two different OS platform which is Win CE and Standard Microsoft Windows 98 and above, therefore it is important to select a language which can communicate between these two different OS platform. Besides this, never to forget also that the MDIS is an application which need to design and operate in a Internet Information Service (IIS) server to retrieve and save information inside the server database (Figure 4.17).

Therefore, in this MDIS project, Active Server Page Language (ASP), Visual Basic (VB) Language and JAVA was use a medium which communicate through the three different platforms. ASP language was use as the primary medium to interact most of the process server instruction between these three different platforms. Following by was the VB language which use in some form design and security checksum, and JAVA language was been used in the table form controlling for Graphics User Interface (GUI).

Although the JAVA language is involve in the controlling of table form GUI, but the orientation and presentation of information to the user at different platform was control by the Hyper Text Markup Language (HTML).

For the information database retrieval at portal server, it is control by using the ActiveX Data Object (ADO) method in order to connect the user to the database. After the been connected to the database, it is good to using Structured Query Language (SQL) to retrieve the data or the information in the manner or the way as end user require.

63

Figure 4.17: Interaction in Between MDIS System Platform

4.3.2.3 System Architectural

System architectural of MDIS basically is support by 9 functional modules. Each module function is unique and interacting in each other so that it serve the function of database management and control , OS detection and GUI control, image processing, information access security control by level and group, data export, data print, report auto generation, database acquisition and data post.

64

Figure 4.18: System Architectural of MDIS

a. Database Management and Control The function of this module is to collect and save the data which user post in into database storage in the server. This module also serves as a functional module in retrieve database or information from the server database storage upon query from user.

This module retrieves the data from the database using ADODB method as

show in the ASP source code in Table 4.4.

Table 4.4: ASP Source Code of Database Management and Control Module

65

Where “ADODB.Connection” is to set a pointer to the database which is need to open for information accessing, whereas the method of “ADODB.Recordset” is to set a pointer to the record set inside the database.

b. OS Detection and GUI Control The function of this module is to detect the current operating system on supporting the unit which is in browsing the MDIS system.

Later arrange the

appropriate GUI to respond back to the browser and the source code was listed in Table 4.5 below.

Table 4.5: ASP Source Code of OS Detection and GUI Control Module

Where the “request.servervariables” is responsible to get the initial working OS string "HTTP_USER_AGENT" from the browser and from there identify the type of browser it use. From the source code listed in Table 4.5 before, the code test the Boolean function of the return string from the code “request.servervariables” weather it return the string of "Windows CE" which is an identifier for OS of Windows CE in POCKET PC. If the Boolean test is true then divert the GUI into POCKET PC mode where the screen display is readjusted to suit POCKET PC and if it is fault then the GUI is set to respond in normal workstation view.

C. Image Processing The function of this module is to reset the type and size of picture where later will respond by the database management and control module in saving the all the picture submitted or retrieve the picture which is store inside the database and the ASP code are as Table 4.6.

66

Table 4.6: ASP Source Code of Image Processing Module