AU Project Report Fulltext 111667

.
·-
MS (CIS)
~ON lJNIVEJISl1Y lBWlf
PROPERTY MANAGEMENT SYSTEM
by
MS. PANNIPA REWTHAMRONGSRIS
Final Report of the Three-credit Course

CS 6998 System Development Project
Submitted In Partial Fulfillment

of the Requirements for the Degree of
Master of Science
in Computer Information Systems
Assumption University
December, 1996
,
Project Title Property Management System
Name Ms. Pannipa Rewthamrongsris
Id No. 343-9244
Project Advisor Prof. Dr. Srisakdi Charmonman
Academic Year 1996
The Graduate School of Assumption University had approved this final
report of the three-credit course, CS 6998 ~ystem Development Project,
submitted in partial fulfillment of the requirements for the degree of Master
of Science in Computer Information Systems.
Approved Committe~:
(Prof. Dr. Srisakdi Charmonman) (Dr.Suphamit Chittayasothorn)
Advisor Member
(Dr. Sudthipom Patu.mtaewapibal) (Air Marshal Dr.Chulit Meesajjee)
Member Member
(Assoc Prof .Somchai Thayamyong)
Member
TABLE OF CONTENTS
PAGE
Abstract
List of figures ii
1. Introduction
1.1 Project Background
1.2 System Objective 2
1.3 Scope of the project 2
2. The Existing System

2.1 Organization Background 4
2.2 Organization Chart 5
2.3 Current problems 6

2.4 Analysis of existing system 7
Existing system Context Diagram 9

Existing system Data Flow Diagram 10
3. The Proposed System
3.1 User requirement 11
3.2 New system requirement 12
3.3 System design Analysis & Design 15

TABLE OF CONTENTS
PAGE
_ 3.4 Hardware and Software requirement 29
3.5 Securrty and Control 31
3.6 Cost and Benefit analysis 33
4. Project implementation
4.1 Project implementation schedule 40
4.2 Training 41
4.3 Testing 43
4.4 Conversion 44
5. Conclusion and Recommendation
5.1 Conclusion 47
5.2 Recommendatiion 47
6. Reference 49
7. Appendix
7.1 Appendix A : Data Dictionary 50

TABLE OF CONTENTS
PAGE
7 .2 Appendix B : Program Mini Specification 71
7.3 Appendix C : Report Layout 76
7.4 Appendix D : Menu Design 95

ABSTRACT
This system development project provides the analysis, design
and implementation of a Property Management System for the
operation work in a Property Management Department of a real estate
development and management company.
The Property Management system is a system which
provide a better security and control of information system. This
includes the process time, data accuracy and redundancy.
We develop the system to reduce the existing problems of
the company and also better service to the customers. The manual
system will be Mplar.ed by this new sy~te~ •::hich bc~d on
computerized system for Management of Information System and using .the
advantages of Database Management System Approach This application
will be implemented on PC Lan with FOX PRO Language.
i
LIST OF FIGURES
PAGE
Figure 1 Company Organization Chart 5
Figure 2.1 Context Diagram (Existing System) 9
Figure 2.2 Data Flow Diagram (Existing System Level 1 ) - 10

Figure 3.1 Context Diagram (Proposed System) 16
Figure 3.2.1 Data Flow Diagram (Level 1) 17
Figure 3.2.2 Data Flow Diagram (Level 2) 18
Figure 3.2.3 Property Management Level 2 (Process 3.1) 19
Figure 3.3 Cost Comparison Table 38
Figue 3.4 Graph of Cost Benefit of the System 39
Figure 4 Project Implementation Schedule 46
ii
1. INTRODUCTION
1.1 Project Background
This system development project provides the analysis, design and
implementation of a Property Management System for the operation work in
Property Management Department of a real estate development and
management company. The system description, functions and system
databases are briefed thereafter.
To solve the problems of existing system which is done by wholly
manual system, the new property management system is developed under
the company committee approvals. The committee is composed of the
management level from Board of Director, Marketing Department, Operation
Department, Legal Department, Accounting __ Departmen_t, __ _System _
Development Dept. and Control Department.
The Committee agrees that the Property Management System has to
provide the management information, reduced work load, optimal data
redundancy, better customer service, more efficiency of work and result to
compete with the competitors.
We develop the system to satisfy the committee's needs and also
reduce the existing problems of the company. The manual system will be
replaced by this new system which based on computerised system within 5
1
months. This application will be implemented on PC standalone first to keep
simplicity. This application will be implemented on PC standalone first to
keep simplicity and maintaining the information in the systematic way with
FOXPRO Lanquage and then in the future we will expand the system to
implement on PC LAN which can help sharing the information and resources
to the maximum benefit.
1.2 System objective :
The main objective of this system development is to reduce the
existing problems of the manual operation of the company and also provide
better services to the customers by :
1. To analyse the existing system of the Real estate company
together with new r~"!uirArnP-rits.
2. To design the new system based on Management of information
System and using the advantages of Database Management System
Approach.
3. To provide meaningful information or reports.
1.3 Scope of the project
Actually the company provides many kinds of selling and anting of
properties but this system will concentrate on one example of Serviced
Apartment management only.
2
This system serves all the operations of customer services after the
marketing officers closed sales with either agents, occupants or clients. And
also serves for the operations of property management in providing the
service for customer complaints, customer profile information and invoice
issuings tor rents and charges.
On the other hand, this system is not included all the cashier and
accounting processes and operations.
3
2. EXISTING SYSTEM
2.1 Organization Background
The real estate company is a company which provides selling,
renting of all kinds of condominiums, housing, land, agricultural farms,
resorts and serviced apartments.
The organization chart in figure 1 shows all the management
level from Board of Director, Managing Director, and the Management
Committee. There are 5 departments i.e. Marketing Department,
Customer Services Department, Accounting Department, System
Development Department or Computer Department and Internal Central
Department.
The Customer Services Department is a newly developed
department which splitted from the Marketing Department. It is the
department which will be the developer and user of the Property
Management System's existing system is still in manual operation in
every aspects of its operation work. All the paper work and manual recorded
reports create a lot o human errors and not timely information.
4
.-~~~~~~~~~~~~~~~--.
BOARD OF DIRECTOR
MANAGBMBNT COMMITI'BE
MANAGING DIRECTOR
SBCRBTARIAL OFFICB
VI
-,
I I I
SALES & CUSTOMER. ACCOUNTING COMPUTER INTERNAL
MARKETING SERVICES & CASHIER DEPARTMENT CON'IROL
DEPARTMENT DEPARTMENT DEPARTMENT DEPARTMENT
figure 1
COMPANY ORGANIZATION CHART
2.3 Current problems
The company has soms problems in existing system both
internal and external problems.
2.3.1 External problem
- complain or comment from customer or Agent
- competition factor within the industry and/or other
industries.
- changes in government rul~- or !av.•
2.3.2 Internal problem
- insufficient in accurate information
- has to use more employees to work a job that leads to more
expenses and then result to decline of profit
6
- many employees has to do over time job and resign due to work
load
- no data security
- many reports has dons by manual
2.4 Analysis of existing system
Since there are the current problems, the committee agree to
improve the system by developing the Property Management system. This
new system emphasis on operation department for the After Sale service or
Customer Service. . However, some reports and inquiry i!'l_t~is system will
also help the users in other departments.
The existing work flow has been reviewed and some functions will
be cancelled or moved to other department. The current problems can be
grouped as follows:-
time to perform all functions
- employees
- information
7
- work process and control
Using the new system can reduce the current problems, some
modifications may be made after the implementation.Modification will be
done more or less depends on the uncertainty from internal and external
information.
8
- time to perform all functions
- employees
information
- work process and control
Using the new system can reduce the current problems, some
modifications may be made after the implementation.Modification will be
done more or less depends on the uncertainty from internal and external
information.
8
•contract info
•client info & details
•unit info
•rent & amenities details
•status details
contract
invoice
Manual
'° reports
client details
job/com.plaints slip
cheek in details
figure 2.1
EXISTING SYSTEM CONTEXT DIAGRAM

Contracts,
Invoices, etc.
Client Details
check in
Contract
details
I-'
0
Manual Reports
figure 2.2
EXISTING SYSTEM DATA FLOW DIAGRAM (LEVEL 1)

~fS CCIS)
~ UNIVEDSlIY UBRART
3. PROPOSED SYSTEM
1233 C-<~
3.1 User requirement
The success of the new system depends heavily on the attitudes and
skills of user personnel. Thus, the ability of personnel to understand and
work with the new system and to adapt to changed must be considered.
User requirement, from system study, can be defined as follows:-
3 .1 .1 Property Management System is required to reduced the

processing time which is now done by manual.
3 .1 .2 The hardware configuration is a Local Area Network (LAN) in
order to supPQrt the users in other departments with shared data and __
data security requirement. The security and control procedure should
be done in order to specify authorized authorized access for each
user.
3.1.3 The system should be provided the screen inquiry to enable
the user to interact with the system in a user-friendly environment
and obtain information as required at any time.
3.1.4 Reports should be produced on time. Each user can
11
receive reports on time for his work such as planning and control
purpose.
3.1.6 Input function should be done in easy, quickly, and accurate
way. The data error detection is required because an information
system with faulty input can never produce effective output.
3.2 New system requirement
In order to define what the new system must be able to do, all the
data collected during the study of the existing system should be reviewed.
The user requirement should be analyzed and refined. This information and
any other relevant information should be used as a basis of developing the
new system requirement. -- ----
The input and output are determined as follows :-
Input requirement :
1. Customer information
2. Contract details
3. Rental rates
4. Charges standard
5. Meter reading
6. Equipment Rental charges
12
ASSUMPTION UN1VEHSfTY URRAlft
7. Job/complaint details
8. Job/complaint work done
9. Dates of important job
10. Billing cycles
11 . Occupant Profiles
12. Agent details
Output requirements:
1. Contracts
2. Invoices
3. Property Manager Diary
4. Reports :
Ell'.cl?ption Reports :
• List of equipments not returned
• List of equipments out of order
MIS Reports:
• Vacancy Status report
• Project invoice summary
Other reports
• List of Agents
• Servicesd Apartment contract
• Tenant_profiles
13
ASSUMPTION UNMllsnY UBRARY
• Report on type of charges
• List of miscellaneous charges
• Meter reading checklist
• Equipment available for rental
• Complaint log register
• Vacancy Status report
• Invoice register
14
ASSl.'MPTION UNIVERSITY tmRAR1
3.3
SYSTEM ANALYSIS & DESIGN
15
• contract info & status details
• client & unit's info
Various reports
• rent & amenities details
contract
>
~
~
invoice E;i
~
client profile request =:I
o1ie:c.t detai1s ::::I
;;;:
status of job/complaints
information ~
f-'
°' complaints
~
~=i
details
figure 3.1 PROPERTY MANAGEMENT

I
SYSTEM CONTEXT DIAGRAM
Contracts,
Invoices, etc.
Client Profiles,
Request for services,
Payments etc.
Contract
details
I Unit details ..J 01 I PROPERT MGT UNIT
f-"'
-..J I Contract details .J 02 I SERVICE APAR!rMENT CON'rRACT
Report I Billing details ., I 031 INVOICES
figure 3.2.1 PROPERTY MANAGEMENT SYSTEM DATA FLOW DIAGRAM (LEVEL 1)

ASSUMPTION llNlVERSflY LIBRARY
Unit Bl8tus
-
Im PROPER'lY MOT.
CODtnu:tB renewal 3.1
I
! dates etc.
Client's profile
CRI11CAL DA1ES
CHECK IN -m TENANT PROPJLES
Client's profile
-
Client's profile
~
•3.2
Serviced apartment rates
Coulract miewal dates etc.

Ins
I
ROOM RATES
•
- DlO CRITICAL DA 1ES
Coolracts
CONTRACT
PREPARATION Coolract details
I
Dl SERVICE .APARTMFNT CONTRACT

CLIENT I
Rent, Furniture
charges etc. details
- Invoices .Im MISC.CHAROES
Miscellaneous
Compllints charges details
~
I D4 ME'IER READIN<J
3.3 I
Charge details
--
PROPERTY Billing Hml'ARAilON
MANACD!MENT -- OF INVOICES
-
cycles
I I D6 EQUIPMENT RENT
-
~
.I Rental charges details

-
IDvoices
I Dl INVOICES
Service charges
-
3.4
MAINTENANCE
Compllliols lk. Job/Complaillt details
DEPARTMENT
COMPLAINT Im JOB ORDER
• · ---ANCE
wodr. done & work done
3.5
PROPER'lY i.-
MANAOER Staitus of jobs PROPER'lY Dates of other important
complaiob MANAGER -Imo
- CRITICAL DA1ES
DIARY Jobs
Contract
rcocwal dates ....
de.
figure 3.2.2
.. PROPERTY MANAGEMENT (LEVEL 2) DATA FLOW DIAGRAM
18
ontract renewal
dates, etc.
D10 CRITICAL DATES

Reply
Contract details
D1 SERVICE APARTMENT CONTRACT
Unit status
Reply
D2 PROPERTY MGT. UNIT
Amentities status
Rent rate
DS ROOM RATES
TENANT PROFILES
Rate
D6 EQUIPMENT RENTAL CHARGES
Charge
D10 CRITICAL DATES
figure 3.2.3
PROPERTY MANAGEMENT LEVEL 2 (PROCESS 3.1)
19
PROPERTY MANAGEMENT SYSTEM
SYSTEM DESCRIPTION
The main purpose of the property management system is to manage
various property units constructed by the company.The main function of the
system will be to maintain detailed information about each unit and its
occupant.This detail will include occupant profiles,billing details of rental
charges and other services availed by the occupanat and property details.This
sysstem will have following important functions:
1. Check In
2. Contract Preparation
3. Invoice
4. Job Orders/Complaints
5. PM Diary
Figures 3.1 (Context Diagram) and figures 3.2.1 and 3.2.2 give an
overview of the property management system module and its interaction
with other modules of the system. In the Appendix ; Forms 1 to 17 are the
various input forms and formats for the inputs that will be required by the
system.
The main functions of property management system are briefly
discussed below:
20
ASSUMPTIDN llNIVERSTTY UBRAR'f
Check In
This system will maintain a database of all the property units in which
its type,model,occupancy status.type of ownership and all details are stored.
The system will get this information from the marketing department. The
main aim of this system will be to update the occupancy status of a unit
whenever a client checks in or checks outin case of service apartments.The
system also maintains a detailed occupant/tenants profiles in which the
details like his name,address,nationality,passport number.check in date etc.are
stored.The main reports generated by the system will be tenant profile and
occupancy status reports.
Contract
Th!s prc~ss will take care of preparation of contracts in case of -·
serviced apartments. In case of service apartments it is possible tha.t a
client checks in before preparation of contract. In that case this process will
get information about client from tenant profile. The system will get the rent
charges from a database in which different rates will be defined.Based on all
this information a contract is prepared which keeps all the details of terms
and conditions. The main purpose of this module is preparation of service
apartment contract.
21
lnvojceing
This process will prepare rent incoices, and invoices for various
services availed by the owner/occupant of various property units. For this the
system will get information relating to property unit and client from the
property contract. These invoices willbe prepared based on various billing
cycles defined by the user and will have all details of rental charges.furniture
charges and any other services availed by the occupant.It is possible that the
occupant of the serviced apartment avails some other services or rents any
equipment like Video,lV,Refrigerator etc. The invoicing for these will also be
done by the system.The system will maintain a table of various charges along
with their descriptions and also a database of various equipments available
for rent will be maintained by the system along with their monthly charges,
quantity in hand etc.. The various billing cycles will be entered in the
beginning of the financial ye~r -~ _th~t the billing is done based on !he~e
billing periods. Besides generating invoices the other important outputs of
the system will generate various reports like invoice summary for each
project.list of ewuipment available for rental.list of equipment not returned,
miscellaneous charges report etc.
Job Orders
This system will process the job orders I complaints received from
the occupants of various property units.Based on these complaints a
22
complaint log register and a complaint attended register will be maintained
which will be used to keep a track of whether the complaint has been
attended or not.This information will be used for Property Manager's Diary
alos.The labour charges and other charges on job order will be entered and
invoices will be generated based on this.
Property Manger's Diary
The main purpose of this system will be to keep track of a number of
functions. These functions! will include tasks like maintenance schedules,
insurance renewals, contract renewals etc.And for servived appartments and
residential condominiums reminders of client's birthdays/anniversaries will
also be important for sending out greetings.The system will get its input
from property contracts where the details of contract renewals,end dates etc.
Will be stored. Stat'.ls of comp!2ints recei'Jed-~tc.stor-cd - in complaint log
register will also serve as an input for this sysstem.This information will. be
used to generate a list of such functions on a daily basis.
23
ASSUMPTION umvERStTY llBRARl
BRIEF DESCRIP"TION OF VARIOUS DATABASES IN THE SYSTEM
This section describes the entities involved in the property
management system. Various databases in the system are listed below:
1) Property Management Unit
2) Serviced Apartment Contract

3) Occupant Profiles
4) Agent
5) Invoice
6) Equipment For Rental
7) Meter
8) Billing Cycle
9) Job Order
Propertt Management Unit
The different types of property units in the system are serviced

.
apartments,condominiums,commercial complexes and housing units. This
entity will keep information of each individual property unit.
The system gets this information from the marketing department and
the status will be updated by the system.
24
Serviced Apartment Contract
This will stroe all the information relating to a serviced apartment
contract which is prepared at the time of allocation of a serviced apartment.
This will contain all the terms and cdonditions of a contract.
The rent charges will be picked up from room rates database.
Occupant Profiles
This will contain information of all the tenants/ occupants of the
property units.This will have detailed information of a unit's owners and
occupants.
.....
The information about occup:nts -, • ,:11 be stored in Occupants
database.
This will maintain complete information of various agents associated
with the company. In case some contract is throgh some agent the property
contract will contain the reference of agent code.This is a master data entry.
I.
25
Invoice
This will contain the informaation of rent and other expenses
chaargeable from viarious property unit owners/occupants.This will have a
header portion and a detail portion. All the invoiceing will be done based on
property unit identificaation.
EQuipment For Rental
This will contain information of all the equipments available for rental
with the company.This will be a master data file and will contain a description
of each and every equipment.
The in formation about various equipments rented out and the
charges payable for the - p~rpcse of invsk~in~ are ctcmd in ;sqa:pment rental
charges.
This will keep detail of each and every meter installed in the property
units. This will be a master data file and will contain a description of each
and every meter.
This information of meter readings taken at various time intervals will
. be kept in reading.
26
Billing Cycle
This will contain the codes of various billing cycles and theit starting
and ending dates.These billing cycles will be entered in the database at the
beginning of each financial year and the entire invoicing will be done based
on these billing cycles.
Job Order
This will contain information of all the job orders/complaints received
from occupants of various property units.
This information about the labour charges, miscellaf'.lous charges and
details of action taken on a complaint will be kept in job order details.
27
CODING SCHEME
The property management system will be following the coding
scheme described below for the purpose of allotting a unique identification
to each property unit.
Company Code
Project Code
Building Number Property ID
Floor (Identification)
Unit Number
99 999 xx xx xx
The entire invoicing in the system will be done based on above
coding scheme.
28
ASSUMPTION UN1VEffSl1Y UBHAtn
3.4 Hardware and Software requirement
For the new system, after a consistant successful implementtation of
the proposed system, the committee decided to use a centralized data
processing through Local Area Network (LAN). The purpose of using LAN
are :-
- to share peripherals and a database
- to facilitate communication within a work group
LAN is a system of hardware, software, and communications channels
that connects devices on the same premises.
LAN can help us to share relatively expensive facilities or peripherals
such as printers, application prcgrarr.s,- ::>rr::nunication lines to othiitr
computers, and large capacity disk drives among multiple users rather thar:i to
provide one to each user for his or her dedicated use. It also enhances
communication by allowing electronic mail, document and spreadsheet
transfer, and other intragroup exchanges. LAN are especially effecially
effective in fulfilling these functions because every device on the network
can access every other device directly.
LAN consists of the following basic components.
- Microcomputer and 1/0 devices
29
- Netword server
- Network interface
- Controller
- Transmission media
Anyway for the initial stage, the Hardware and software requirements
are as follows:
3.4.1 Hardware requirement
1. Microcomputer B0486DX2-66 Intel
- RAM 8 MB expandable to 64 MB on
board
- Hard disk 545 MB HH/J.5" 12 MS
Seagate
- 14" SVGA Monitor - Low Emission
2. Printer L0-1170i EPSON
3. Uninterrupted Power Supply for the
server
4. Backup tape
30
3.4.2 Software requirement
1. FOX PRO V2.6
3.5 Security and control
3.5.1 Physical security
- Uninterruptible power source (UPS) Dirty power, such as sags and
surges in power output or low power, causes data transmission errors and
program execution errors. An UPS system seives as a control buffer between
the extenal source and the computer system. If the external power source
fails, the UPS system permits operation to continue for a period of time after
outage. This allows operators to either '"power down" normally or switch to
a ~c:*up power source. _ _ .
- Back-up facilities
It is provided for both data files and programs to ensure that :
- data files can be reconstructed in the event of master file loss or
corruption
- application and system software can be reinstated in the event of
loss or corruption
31
When a system fails, backup files/data bases and/or backup
transaction logs are used to recreate processing from the last "checkpoint".
The system is restarted at the last checkpoint and normal operation is
resumed.
3.5.2 Logical security
- Password
To ensure that access to the system is gained for ligitimate purposes
only, Passwords should be used to restrict access to the system or
parts of it.
- User Profiles.
It is used to create user class and special authority determine whether
the user is allowed to perform his or her functions. It makes an
authorization for access to application programs.
- System time out
This is the time limitation for each user. If user does not touch the
system about 5 miniutes, the system will be time out automatically.
This also includes time out at the input·password screen.
32
- Security control log and audit trail
Possible attempts to use the system illegally can be highilghted by a
review of the log together with an exeption report on invalid use
(such as failed access attempts).
- File control
It is to ensure suitable storage and to limit access to the files. Thus
files are normally labelled externally and internally, and stored in a
library when not in use. Unauthorized persons connot gain access to
the files held.
- System force change password
- System will force user to change his or her password once~
month. However, user can change his or her password at any time.
3.6 Cost and Benefit analysis
3.6.1 Cost analysis
A. Investment Cost
33
Unit Budget
1. MicrcrComputer
80486DX-66 1 65,805.00
2. Printer
EPSON L0-117oi 2 50,000.00
3. Tape Backup 36 18,000.00
4. FOX PRO 1 3,745.00
Tot~- inv9etm9nt cost Bcht 137,!350.0C
--------
B. Implementation Cost
1. System development cost 40,000.00
2. Training cost 25,000.00
3. Conversion cost 10,000.00
34
Total implementation cost Ba ht 75,000.00
C. Annual operation cost
1. Paper 12,000.00
2. Ribbon 3,000.00
3. Diskette 2,800.00
Total annual operation cost Baht 17,800.00
Grand total of all cost Baht 230,350.00
--------
3.6.2 Benefit analysis
A. Intangible benefit
1. Im prove business planning
2. Improve working process by providing accurate, security, and
control.
3. Increase efficiency work process
4. Increase productivity
5. Increase motivation for employees due to reduce work load
35
6. Increase quality and efficiency of service
B. Tangible benefit
1. Reduce the number of employees to (transfer to Accounting
Department) operate manual system
Salary 1 persons (13,000 x 12month) 166,000.-
Bonus 1 persons (13,000 x 2 month) 26,000.-
Overtime 1 persons (1,000 x 12month) 12,000.-
2. Increase customers from better service 600,000.-
Total of tangible benefit Ba ht 794,000.-
------
3.6.3 Payback period
Payback period is used to judge the profitability of a system. It is
defined as the number of years required to accumulate earnings sufficient to
cover its costs.
The payback period calculator is
36
ASSUMPTION UNM1ISllY UBRART
p =
(1-TI R
p = 230,350
(1-0.30) 794,000
= 0.41 or approximately 5 months
Where:-
= Investment or capital expenditure
T = Corporate tax rate (use 30%)

R = Annual--s.avin:;; realized ~y ir.vestment
37
Cost Comparison Existing Proposed
1 2 3 4 5 1 2 3 4 5
ee[SODDel ~ ee[SODS ;
Salary ( 4 x 13,000 x 12 month + 10% increase) 624,000 686,400 755,040 830,644 913,698 468,000 514,800 566,280 622,908 685, 199
Bonus ( 4 x 13,0CXl x 2 month + 10% increase) 104,000 114,400 125,840 138,424 152,266 78,000 85,800 94,380 103,818 114,200
Overtime ( 4 x 1,000 x 12 month + 10% increase) 48,000 52,800 58,080 63,880 70,277 36,000 39,600 43,560 47,916 52, 708
Increase customers from better service 0 0 0 0 0 120,000 120,000 120,000 120,000 120,000
Cost Analysis :
w
co Investment Cost 0 0 0 0 0 137,550 0 0 0 0
Implementation Cost 0 0 0 0 0 7,500 0 0 0 Qi
Annual operation Cost 0 0 0 0 0 17,800 0 0 0 0

'.
Total 776,000 853,600 938,960 1,032,856 1, 136, 14, 864,850 760,200 824,220 994,642 972, 107
figure ~.3 COST COMPARISON TABLE

Baht
1200000
1100000
1000000
900000
800000
700000
_.,._ Existing System
600000
- Proposed System
500000
400000
300000
w
200000
'°
100000
0
1
2 3 4 5
Years
figure 3.4 GRAPH OF COST BENEFIT OF THE SYSTEM

4. PROJECT IMPLEMENTATION
4.1 Project Implementation Schedule
A careful and well-devised plan for the implementation of a new
system needs to be made before finally settling on the physical design.
An important reason tor this concerns the effect of the system on the user-
the need to design the system so that the changes can be introduced in a
way that is most likely to lead to the system's acceptance.
Some other reasons why the implementation needs careful advance
planning are:
- The need to design and build-in the capacity dentufying, diagnosing,
and correcting errors that may be found during the implementation
- The high cost of system
- The time-critical nature of many of the implementation activities in
the total project timetable
- The need to have a fall-back position in case system fails to operate
successfully
40
The main activities during the installation of a new system are:
- Checking to make sure the new system is producing the right
information within the specified time frame
- Completing the Training of users, key entry operators, and
computer operators
- Training mangement in the use of the informatio n reports
produced by the system
Developing the plan for implermentation a project cannot wait until
after programming is complete, as it may then be found that the system
cannot support the desired implementation plan.
Figure 4.1 is shown the project implantation schedule. This schedu~e
is planned by the committee group.
4.2 Training
End users are usually introduced to the functionality of an
information system via a one-on-one and/or group lecture training program.
At a minimum, the agenda for such a program will include the following:
Purpose and objectives of the system
41
- Differences between the existing and the new system
- Overview of system operation and proceduree
- Organization and use of the system's user manual and help
screens
- Duties and responsibilities of end users
- Duties and responsibilities of technical support personnel
- Demonstration of the system
- An introductory hands-on walkthrough of the system
- Familiarization with the system practice using the system with
test data)
In preparation for in-house user training sessions, instructors devise
operational scenaries, complete with test data, to give users an opportunity
to familiarize themselves with the system. During the sessions.instructors
provide insight into how to make the most effective use of the system.
The conversion and implementation process progresses smothly when
users feel comfortable of the system.
42
User training programs must be ongoing because employees come
and go. Each new employee has to be trained in the use and operation of
the system.
4.3 Testing
Testing includes verification of the basic logic of each program and
verification that the entire system works properly. It is vitally important that a
system works correvtly begore users become dependent on it. Testing and
modifications are continue intil the project team and participating users are
satisfied with the results of the test. Testing in leasing system includes as
the following.
4.3.1 Unit testing
Basic program modules are tested by the individual programmers who
wrote them. The programmers usually make up their own test data. Unit
testing programmer data is necessary, but it is not sufficient.
4.3.2 Combined module testing
This is to test combined module which we will stress independent
test data generation. User should be included in this test because the data
will be less contrived and mire realistic.
43
ASSUMPTION UNJVERSJlY U8IW1'f
This is to create input data that would cause another department 's
processing logic to fail.
4.3.3 System tests
The purpose is to validate all software, input I output, procedures, and
the database. User from esch department has to be included in this test. The
testing with test data and live data is necessary. Live data are actual data that
have aleady been processed through the existing system. User manual,
help screen, system procedures, and interaction between other system are
given a good test.
4.3.4 User acceptance testing
- P.!-! th::: bugs should be eliminated oild c.11 ~-.,-stei°11 ~<ii 11ponents and
affected personnel should work together smoothly. This test is to get ~he
user's stamp of approval, user managers examine and test the operation of
the system until they are satisfied. This is the last test to meet the system
objectives.
4.4 Conversion
Once acceptance testing is complete, a converion from the existing
system to the new one begins. Due to the existing system is manual,
therefore we decides to use the method of parallel conversion.
44
In parallel conversion, the existing system and to new system operate
simultaneously, unitl the project team is confident that the new system is
wirking properly. The results from the two systems are compared as a
further check on the new system before the old approach is discontinued.
The existing system serves as backup if the new system fails to operate
as expected, but they place a heavy burden on the user to keep two system
operating. User has to key input on master file at the beginning of the new
system. The duration of parallel conversion is one month then system is
customer.
45
ACTIVITIES 1996
August Sep. Oct. Nov. Dec.
SYSTEM ANALYSIS :
Context diagram of old system

•
•
-
Identify the area under study
Develop the physical DFD of the existing system
Identify the contents of the existing data stores

••
Develop the logical DFD of the existing system
DETAIL ANALYSIS AND DESIGN:

-
Develop the logical DFD of the new system
--
--
Identify the contents or the data stores for the new system
Data Dictionary
Structure Chart
Develop the physical DFD of the new system

••
IMPLEMENTATION :
Preudocode or Minispecification
Programming
.. -
Screen Layout
•
•
--
Report Layout
Data Conversion
--
Testing
Training
Accoptance Test
Production I
Documentation
figur~ 4 PROJECT IMPLEMENTATION SCHEDULE
46
6. CONCLUSIONS AND RECOMMENDATIONS
5.1 Conclusions
From user requirement through system design, the new system is
developed. The advantages of this new system are as follows:
- It satisfies the user's real information requirements

- It is easy to use and to operate
- It is easy to maintain
- It is easily modified or enhanced.
The main functions of leasing system is to perform the operation
tasks. The reports will be generated by the system, which provide
information as requir~d by the user.
5.2 Recommendations
Information technology has become an increasingly important
component of organizations. Technology facilitates the ongoing operations of
a company and contributes to its competitive strategy.
Management team plays an important role in developing information
system.. User from each department has to involve and participate in all
47
phases of system development activities. Feedback from user will be an
information for evaluation of the new system after implementation.
The postimplementation review is a critical examination of the system
after it has been put into production. The evaluation should be conducted
three months after implementation.
The postimplementation review focuses on the following.
- A comparision of the system's actual performance versus the
anticipated
- An assessment of each facet of the system with respect to preset
criteria
- Mistakes
- unexpected benefits and problems.
48
REFERENCES
1. Brookes H.P. Cyril, Grouse J. Philip , Jeffery D.Ross , Lawrence J.
Michael Information System Design Prentice-Hall International, lnc.,1982
2. Connor Dennis Information System Specification & Design Road
Map Prentice-Hall International, Inc., 1985
3. Hodge Bartow, Clements P. James Business System design
Prentice-Hall lnternation, Inc., 1986
4. Long tarry Management lnormation System Prentice-Hill International,
Inc., 1989
5. Lucas C. Henry , Jr. The analysis. Design, and Implementation of ·
Information Systems Mcgraw-Hill International Editions, 1992
6. Martin P. Merle Analysis and Design of Business Information
Systems Maxwell Macmillan International Editions, 1991
7. Nevitt K. Peter Project Financing Euromoney Publications Limited,
1983
49
APPENDIX A
DATA DICTIONARY
so
PROPERTY_MANAGEMENT_UNIT
DATA ELEMENT lYPE SIZE STATUS
COMPANY NUMBER 2
PROJECT NUMBER 3
BUILDING_NUMBER CHAR 2 PROPERlY (KEY}
B_FLOOR CHAR 2 ID
UNIT_NUMBER CHAR 2
PROPERlY_lYPE CHAR 2 CONDO/
COMMERCIAL
COMPLEX ETC.
PRODUCT_CODE CHAR 2 PROPERlY SUB
lYPES
MODEL_CODE CHAR 2
lYPE_OF_O\VNERSHIP CHAR 1 SOLD/R ENTED/L
EASED
STATUS CHAR 1 OCCUPIEDNAC
ANT
51
SERVICE_APARTMENT_CONTRACT
DATA ELEMENT TYPE SIZE STATUS
COMPANY NUMBER 2
PROJECT NUMBER 3
BUILDING_NUMBER CHAR 2
B_FLOOR CHAR 2
UNIT_NUMBER CHAR 2
CONTRACT_NUMBER CHAR 10 (KEY)
CONTRACT_DATE DATE
AGENT_CODE CHAR 3
OWNERS_NAME_ENGLISH CHAR 50
OWNERS_NAME_THAI CHAR 50
OWNERS_ADDRESS CHAR 150
CITY CHAR 20
ZIP CHAR 6
-
OWNERS_PHONE CHAR 20
OWNERS_FAX CHAR 20
LOCAL_FOREIGNER CHAR 1
NATIONALITY CHAR 20
ID_NUMBER CHAR 10
PASSPORT_NU MB ER CHAR 10
VISA_NUMBER CHAR 10
VISA_VALID_UPTO DATE
START_RENT_DATE DATE
CONTRACT_RENEWAL_DATE DATE
52
END_CONTRACT_DATE DATE
SECURllY_DEPOSIT NUMBER 16,2
DEPOSIT_RECEIPT_NUMBER CHAR 10
MONTHLY_RENT NUMBER 16,2
FURNITURE_RENT_AMOUNT NUMBER 16,2
SERVICE_ CHARGES NUMBER 16,2
53
ROOM_RATE
COMPANY NUMBER 2 (KEY FIELD)
PROJECT NUMBER 3
ROOM_TYPE CHAR 1
DAILY_RATE NUMBER 16,2
WEEKLY_RATE NUMBER 16,2
MONTHLY_RATE NUMBER 16,2
QUARTERLY_RATE NUMBER 16,2
HALF_YEARLY_RATE NUMBER 16,2
YEARLY_RATE NUMBER 16,2
54
TENANT_PROFILE
DATA ELEMENT TYPE SIZE STATUS
COMPANY NUMBER 2
PROJECT NUMBER 3
BUILDING_NUMBER CHAR 2 (KEY}
B_FLOOR CHAR 2
UNIT_NUMBER CHAR 2
CONTRACT_NUMBER CHAR 10
CONTRACT_DATE DATE
TYPE_ OF_ CONTRACT CHAR 1 SALE/LEASE/A ENT
AGENT_CODE CHAR 3
OWNERS_NAME_ENGLISH CHAR 50
OWNERS_NAME_THAI CHAR 50
OWNERS_ADDRESS CHAR 150
CllY CHAR 20
ZIP CHAR 6
OWNERS_PHONE CHAR 20
TYPE_ OF_OWNER CHAR 1 INDIVIDUAL/
JOINT/COMPANY
LOCAL_FOR EIGNER CHAR 1
NATIONALllY CHAR 20
ID_NUMBER CHAR 10
PASSPORT_NUMBER CHAR 10
VISA_NUMBER CHAR 10
55
VISA_VALID_UPTO DATE
CH ECK_IN_DATE DATE
CHECK_OUT_DATE DATE
STATUS CHAR 1
REMARKS VAR CHAR 255
56
OCCUPANTS
COMPANY NUMBER 2 (KEY)
PROJECT NUMBER 3 (KEY)
BUILDING_NUMBER CHAR 2 (KEY)
B_FLOOR CHAR 2 (KEY)
UNIT_NUMBER CHAR 2 !KEY)
SERIAL_NUMBER NUMBER 2 !KEY)
NAME CHAR 50
The alternate billing addresses will be stored as follows:
57
BILLING_ADDRESSES
COMPANY NUMBER 2 !KEY)
PROJECT NUMBER 3 (KEY)
BUILDING_NUMBER CHAR 2 !KEY)
B_FLOOR CHAR 2 !KEY)
UNIT_NUMBER CHAR 2 !KEY)
SERIAL_NUMBER NUMBER 2 !KEY)
BI LLING_NAME CHAR 50
BI LLING_ADDR ESS VAR CHAR 150

BILLING_RATIO NUMBER 5,2
This will maintain complete information of various agents associated with the
company. In case some contract is through some .agent the property
contract will contain the reference of agent code. This is master data entry.
58
AGENT
AGENT_CODE CHAR 3 KEY FIELD
AGENT_NAME_ENGLISH CHAR 50
AGENT_NAME_THAI CHAR 50
AGENT-ADDRESS CHAR 150
CITY CHAR 20
ZIP CHAR 6
AGENT_PHONE CHAR 20
This will contain the information of rent and other expenses chargeable from
various property unit owners/occupants. This will have a header portion and
a detail protion. All the invoicing will be done based on property unit
identification.
59
HEADER INFORMATION
INVOICE_NOTE
COMPANY NUMBER 2 KEY FIELD
PROJECT NUMBER 3 KEY FIELD
INVOICE_NU MB ER CHAR 8 KEY FIELD
TYPE_OF_INVOICE CHAR 1
AR_ CODE NUMBER 6 AIR CODE
60
OF CLIENT
B_FLOOR CHAR 2
UNIT_NUMBER CHAR 2
BILLING_ADDRESS CHAR 150 ADDRESS
WHERE THE
BILL WILL BE
-
SEND
CllY CHAR 20
ZIP CHAR 6
TOTAL_INVOICE_AMOUNT NUMBER (16,2)
TOTAL_VAT_AMOUNT NUMBER (16,2) TO KEEP TRACK
OF VAT
81LLl~(:i_CYCLE NUMBER 6 EBERY BILL
WILL BE BASED
ON SOME
BILLING CYCLE
-
61
DETAIL INFORMATION
INVOICING_DETAIL
INVOICE_NUMBER CHAR 8 KEY FIELD
CHARGE_ CODE CHAR 2 (USER DEFINED
IN lYPE OF
CHARGE TABLE)
CHARGED _AMOUNT NUMBER 16,2

VAT NUMBER 16,2
-
This will contain information of all the equipments available for rental
with the company. This will be a master data file and will contain a
description of each and every equipment.
62
EQUIPMENT_CODE (MASTER DATA)
EOUIPMENT_CODE NUMBER 2 KEY FIELD
EQUIPMENT_DESRIPTION CHAR 50
STANDARD_RENTAL_CHARGES NUMBER 16,2
63
EQUIPMENT_FOR_RENTAL (MASTER DATA)
EOUIPMENT_CODE NUMBER 2 KEY FIELD
EOUIPMENT_ID CHAR 8 KEY FIELD
EOUIPMENT_STATUS CHAR 1 RENTED/OUT OF
ORDER/AVAILABLE
OUT_OF_OADER_DATE DATE
This information about various equipments rented out and the charges
payable for the purpose of invoicing ar stored in equipment rental charges.
64
EQUIPMENT_RENTAL_CHARGES (TRANSACTION DATA)
ISSUE_SLIP_NUMBER CHAR 6 KEY FIELD
B_FLOOR CHAR 2
UNIT_NUMBER CHAR 2
'
EOUIPMENT_CODE NUMBER 2
EOUIPMENT_ID_NUMBER CHAR 8
MONTHLY CHARGES NUMBER 16,2
START_DAY_OF_R ENT DATE
END_DAY_OF_RENT DATE
ISSUE_DATE DATE
RETURN_DATE DATE
STATUS CHAR 1 WHETHER
RETURNED OR
NOT
This will keep detail of each and every meter installed in the property units.
This will be a master data file and will contain a description of each and
every meter.
65
METER (MASTER DATA)
COMPANY NUMBER 2
PROJECT NUMBER 3
METER_NU MB ER CHAR 10 KEY FIELD
METER_TYPE CHAR 1 WATER/ELECTRI
CITY ETC.
METER_INSTALLED_DATE DATE
B_FLOOR CHAR 2
~
UNIT_NUMBER CHAR 2
MULTIPLICATION_NUMBER NUMBER 5,2 WITH EVERY
METER A
MULTIPLICATIO
.
N FACTOR IS
ASSOCIATED
RUNNING_AVERAGE NUMBER 8
DATE_ OF_READING DATE
LAST_READING NUMBER 8
LAST_A EADING_DATE DATE
STATUS CHAR 1 WORKING/OUT
OF ORDER
This information of meter readings taken at various time intervals will be kept
in meter reading.
66
METER READING (TRANSACTION DATA)
METER_NUMBER CHAR 10 KEY FIELD

METER_R EADING_DATE DATE KEY FIELD
CURRENT_READING NUMBER 8
READING_TAKEN_BY CHAR 6
METER_AMOUNT NUMBER 16,2
BILLING_CYCLE CHAR 6
This will contain the codes of various billing cycles and their starting and
ending dates. These billing cycles will be entered in the database at the
begining of each financial year and the entire invoicing will be done based on
these billing cycles.
67
BILLING_CYCLE
CODE CHAR 6 KEY FIELD
PERIOD_FROM DATE
PERIOD_TO DATE
This will contain information of all the job orders/complaints received from
occupants of various property units.
68
JOB_ORDER
COMPLAINT_NUMBER HAR 8 KEY FIELD
DATE_ AEPORTED DATE
B_FLOOR CHAR 2
UNIT_NUMBER CHAR 2
COMPLAINT_DESCRIPTION VAR CHAR 100
REPORTED_BY CHAR 50
RECEIVED_BY CHAR 50
This information about the labour charges, miscellaneous charges and details
of action taken on a complasint will be kept in job order details.
69
JOB_ORDER_DETAILS
COMPLAINT_NUMBER CHAR 8 KEY FIELD
DATE_ATIENDED DATE
ACTION_TAKEN_BY CHAR 6
AUTHOR IS ED _BY CHAR 6
LABOUR_CHARGES NUMBER 16,2
MAINTENANCE_CHARGES NUMBER 16,2
STATUS CHAR 1 COMPLETE/
PENDING
BILLING_ CYCLE CHAR 6

-
70
APPENDIX B
PROGRAM MINI SPECIFICATION
71
System Property Management
Module No. 3.0
Module Name PROPERTY MANAGEMENT
Purpose: - Update client profile
- Classify type of customer
- Update contract information
- Update invoice information
Input: - Customer information
- Contract detatils
Output: - Client profile details
Process: 1. Verify whether the customer is a new or·
existing customer
2 In case of existing customer, update
customer as in application form
3 In case of new customer, add new customer
as in application form
4. Generated customer number
5. Update customer profile details
72
Module No. 3.1
Module Name Check in
Purpose - Update client's profile in tenant profiles
- Update unit status in Property Management
Unit (02)
- Update untract renewal in Critical dates (010)
Input: - Client•s Profiles
- Unit Status
- Amentities
Output: - Detail reply to customer
Process: 1. Verify unit status
2. Update unit status

3. Input client details from client profiles
4. Input amentities
5. Update contract renewal dates in critical
dates
73
Module No. 3.2
Module Name - Contract Preparation
Purpose - Update contract and prepare data to print
contract in module no. 3.2.3
- Customer information must be existed
- Verify contract before go to module
Input: - Client's Profiles
- Serviced Aparment rates
Output: - Contracts
- Contract details
- Contract renewal dates
Process: 1. Verify contract details from Marketing
2. Get clienfs details from 05
3. Get room rate form 08
4. Generate contract no.
5. Update contract renewal dates
74
System: Property Management
I
Module No.: 3.2.3

II.
II
Module Name: Print Contract
Purpose: - Print contract and send to manager
- Print contract to customer after approval
Input: - Contract details
- Client's profile
- Serviced apartment rates
Output: - Contracts Approval
- Contract
Process: 1. Print all of these documents
.!
75
APPENDIX C
REPORT LAYOUT
76
PROPERTY MANAGEMENT SVSIEM
PROPERTY MANAGEMENT REPORTS.
EXCEPTION REPORTS
1. LIST OF EQUIPMENTS NOT RETURNED

2. LIST OF EQUIPMENTS OUT OF ORDER
MIS REPORTS
1. VACANCY STATUS REPORT

2. PROJECT WISE INVOICE SUMMARY
OTHER REPORTS
1. LIST OF AGENTS
2. SERVICE APARTMENT CONTRACT
3. TENANT PROFILES
-....J
-....J 3. REPORT ON TYPE OF CHARGES
4. LIST OF MISCELLANEOUS CHARGES
5. METER READING CHECKLIST
6. EQUIPMENTS AVAILABLE FOR RENTAL
7. EQUIPMENTS ISSUE/RECEIPT REGISTER
8. COMPLAINT LOG REGISTER
9. COMPLAINT AITENTED REGISTER
10. VACANCY STATUS REPORT
11. PROPERTY MANAGER'S DIARY
12. INVOICE REGISTER
REPORT NAME : VERSION : XXXXXXXXXXXX
RUN BY : XXXXXXXX (USER • ID) ON 99/9U9999 99:99
XXXXXXXXXXXX COMPANY NAME CHAR(50) XXXXXXXXXXXXXXX DATE: 99/99/9999

XXXXXXXXXXXX PROJECT NAME CHAR(5?l XXXXXXXXXXXXXXX PAGE: 999
LIST OF AGENTS FROM XXX TO XXX
AGENT NAME &

CODE ADDRESS
XXX XXXXXXXXXXXXXXX!50JXXXXXXXXXXXXXX
i
XXXXXXXXXXXXXXX(50)XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX150JXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX!50JXXXXXXXXXXXXXXX
CITY XXXXXXXXXXXXXXX ZIP : XXXXXX
I
PHONE XXXXXXXXXXXXXXX
-...J sma••••••••••••••••••••••m•••••••••••m•=•=•••••Ea=mm•=•m•am#•===•z•••••••••===•z
co
.. END OF REPORT • •
Sort Order Company code, Project code, Agent code. i

Tables used Agent. ~
Report Width 80 cols
REPORT NAME : JOOOOOOOOOOOOOO VERSION : )()()()()()()()
RUN BY : )()()()()()()() (USER • IOI ON 99mi9999 99:99
~nn oer:._.._...=~=~
)()()()()()()() COMPANY NAME CHAR(SOI )()()()()()()() DATE ; 99,99,9999

)()()()()()()() PROJECT NAME CHAR(501 lOOOOOOOOOOOOOO PAGE : 99,99,9999
SERVICE APARTMENT CONTRACTS FROM )()()()()()()() TO )()()()()()()()
~™--&:Uaaaaaa. & W"",...__~~- ·....,... ..._ . _ •· =--==~~~~--·- ·--=----- - -- ~amrn - -- - -
CONTRACT DATE OF BLDG FLOOR UNIT CONTRACT PERIOD RENEWAL RENT AGENT RATE <-- RENT --> TOTAL SECURITY DEPOSIT
NUMBER CONTRACT NO. NO. FROM TO DATE START DATE CODE CODE MONTHLY FERNITURE SERVICE RENT DEPOSIT RECEIPT NO.
m z z r n m.& MWwwwm.a m ·a aars:=-mm-.......rw &:&.aa ===~ a .w a m r ,. • • •._..,._ ...,....wr-ai"S"C==-==---=-·- -·- --- _
)()()()()()()() 99,g9,g9 xx xx xx 99,g9,g9 99,;99,g9 99,g9,g9 99,g9,g9 )()()( xx 999,999.99 999,999 99 999,999 99 999,999.99 999,999.99 xxxxxxxxxx
OWNER'S NAME : )()()()()()()()OJXlOOOOOOOOOOOOOJOOOOO(

ADDRESS : )()()()()()()()OJX)OOOOOOOOOOO '.XXXXXX
: )()()()()()()()O)JOOOOOOOOOOOOO'.XXXXXX
: )()()()()()()()501l00000000000000
CITY XXXXXlOOOOOOOOO ZIP : )()()()()()(
-...J PHONE : XXXXXlOOOOOOOOO FAX : XXXXXlOOOOOOOOO
"' REMARKS : )()()()()()()()50JXXXXXXXXXXXXXXJ
: )()()()()()()()60)XX)OOOOOOOOOOO
: XXXXlOOOOOOOOOOOllOOOOOOOOOOOOOO
••END OF REPORT..
Sort Order Company code, Project code, contract number.

Tables used Property_contract. Comrac:t.amenities. Ameni1ies_details.
THIS REPORT CAN BE PRINTED BY PROPERTY TYPE. BY BUILPING AND BY FLOOR

REPORT NAME : XX)(:JOOOOOOOCIOOCXXXXXX:JOOOOOOOCX VERSION XX)(:JOOOOOOOQ(
RUN BY : XXXXXXXX (USER - ID) ON 99/99/9999 99:99
XX)(:JOOOOOOOQ( COMPANY NAME CHAR(50) XXXXXXXXXXXXXXX DATE 99/99/9999

XX)(:JOOOOOOOQ( PROJECT NAME CHAR(50) XXXXXXXXXXXXXXX PAGE 999
LIST OF CHARGES FROM XX TO XX

•=2=•~a-m.._.-~._.me;aa~.-=cc:::=a.:a;i::r::maw-ss:zs:m••rl ca•~-a•:a-m-:zc=:~!!l•m:n=n=tD~~=a•:::ae----..::r::a:ca.-ea~•=c...a.ca
CHARGE DESCRIPTION VATABLE
CODE
ao.:t::1:1JC:llll::cse:u-m:::.:•c.::ac•--&e...111cm:1a•nc~ass:~••-a·111;:.:~===:ll!:=:cr==r•~=i=s~-m.:==s~9:1:11•=-::=-=..=a:a-mm,••-.=~
xx XXXXXXXXXXXXXXX(50JXXXXXXXX)900000 x
===------•••~ = m:....-::m::.-=-.==••~=--cc•m~•~--•r:=••-.m:a=r:-=~e.!l:IZ::CQ:==--m::~=.::•a•::::==~-=..1:.=.:=~
.. END OF REPORT..
CX>
0
Sort Order Company code, Project code, Charge code.
Tables used Type_of_charge.
REPORT NAME : lOOOOOOOOOOOOOO VERStON : )0()()00()()()(
RUN BY : XXXXXXXX (USER • 10) ON 99/99/H99 99:99
JOOOOOOOOOOO( COMPANY NAME CHAR~OI XXXXXXXlOOOOO() DATE: 9919919999

JOOOOOOOOOOO(PROJECT NAME CHAR~OI lOOOOOOOOOOOOOC PAGE: 999
TENANT PROFILES FROM UNIT FROM XXXXXX TO XXXXXX
....,.. - -·- · - -·_....., --mam a,..:;~~ ms:s"T'?-._... ----= -e--..____......,..,..----r-=r--m :i=:ca. .....a m m=.--:=-a::t; :::a .:..cs:s~
BLDG FLOOR UNIT OWNER'S NAME lYPE ()f LOCAi../ NATIONALITY ID NUMBER PASSPORT VISA lYPE VAi.JO CHECK
DATE OF
NO. NO. ANO ADDRESS OWNER FOREIGNER NUMBER & NUMBER UPTO IN
rn-----------·--.....,..,.....asac•sm · ~~.c.s.=·•--2 - e:w · •-m••mJE•rr:-.,.....,.... :a:c=a•:&mmsc:a::s::aww -----., ~---- _ __...........,.,.. _ _ _ _
)()( )()( XX XXXXXXXXXXXXXX English ~I )()()()()()()() X x )()()()()()(lOO xxxxxxxxxxxxxxx xxxxxxxxxx xxxxxxxxxxxxxxx 99199199
xxxxxxxxxx 99"8199
xxxxxxxxxxxxxx Timi
~) lOOOOOOOOOOOOOO
l0000000000000060) lOOOOOOOOOOOOOO
CITY xxxxxxxxxxxxxxx 21P lOOOOCX
PHONE : XXXXXXXXXXXXXXX FAX : lOOOOCXXXXXXXXX
00 OCCUPANT'S DETAILS
f-'
S.NO OCCUPANT NAME
99
99
99 lOOOOOOOOOOOOOOO)l()OOO()()()OO
BIWNG DETAILS
S.NO. NAME BIWNG ADDRESS BIWNG RATIO
'99 XXXXXXXXXXXXXXXO!XXXlOOOOOOOOOOO XXXXl00000000006QIXXXXXXXXXlOOO '99 99

lOOOOOOOC0000006QIXXXXXXXXXlOOO
XXXXXXXXXXXXXXXOI)()()()()()()()
'99 lOOOOOOOOOOOOOODOOOOOOOOOOOOOOO:xxxx XXXXXl00000000060)XXXXXXX:XXXXXXX '99 99
REMARKS
XXXlOOOOOOOOOOOOIXXXlOOOOOOOOOOO
)()()()()()()()OllOOOOOOOOOOOOOO
=~=~•:rm:m::s=~ac:.:::~ar=mm.1:1::a:••1U1-- 1.-·-=-T"" ... 11- r••rmm::icm • m-a.a:::::::==-====-"·- =--•=--:a:~-=::::c-=

.,.,
:'!:' .,.,
. .
~
a.
~
-0
-0
0
d
<>..
~-
~
iii
0
E.
.
0
.,
tJ
g.
·e
<>.. 0
0
0
i ...
. ~i..
0
.,
.
~
E
0
u
~
a.
,!
a.
0
0
0
00
0
<>..
w
oc
u..
~
.,., :g
"O
0 "O ::i ~
Cl 0 .,., t::
.•
z
w t::
0
(/)
. .
:a
I-
0
a.
oc
·.
82
RUN BY : XXXXXXXX !USER - ID) ON 99199/9999 99:99
~-=-------=-~·•c••&-a-•--··------m=••.aa-a •:n=•••--=-= ~-a:z1n:s·--~a-..--c!!ls=•-=e••~-------• a m a--.a..a:mmzs...=m~m:ma:= •=•• D = =~-=:s:.::::..lt:m:m
XXXXXXXXXXXX COMPANY NAME CHARl50) XXXXlOOXXXXXXXX DATE: 99/9919999

XXXXXXXXXXXX PROJECT NAME CHAR(50} xxxxxiOOOOOOOO< PAGE: 999
MISCELLANEOUS CHARGES FOR UNITS XXXXXX TO XXXXXX FOR BILLING CYCLE XXXXXX
BLDG. FLOOR UNIT CHARGE DESCRIPTION MISCELANIOUS

NO. CODE CHARGE AMOUNT
~
~----s~c- ~~ ~----~----~~-=-a --=~ =-= ·=~~,..._ - •mM=~~~=~=== ·~Da~a u~~•a===s ezea - mmu m w w a mcni:: s =~-=-= =~ ~~ ~ ~:== ~-ac ~= ce c,,,
xx xx xx xx XXXXXXXXXXXXXXXXXXXXX(50JXXXXXXXXXXXXXXX
XXXXXXXXXXXxxxx!50lXXXXXXXXXXXXXXXXXXX
999,999.99
~::::1
xxxxxxxxxxx1xxx!50)XXXXXXXXXXXXXXXXXXX ~
co
w **END OF REPORT..
Sort Order Company code, Project code, Building_number, Unit_number.

Ii
Tables used Misc_charges.
;
THIS REPORT CAN BE PRINTED BY BUILDING, BY FLOOR, BY UNIT AND BY CHARGE CODE.
REPORT NAME : lOOOOOOOOOOOOOO VERSION : )()()()()()()()
RUN BY : )()()()()()()() (USER • DI ON 99199~ 99:99
)()()()()()()() COMPANY NAME CHAR(50) )()()()()()()() DATE: 99,'d9fil999

NAME CHAR(50) )()()()()()()()
)()()()()()()() PROJECT PAGE: 999
METER CHECKLIST FOR METER TYPE X FOR BIWNG CYCLE XlOCOOC FOR METERS XXXXXXXXXX TO )()()()()()()()
~~~~~~-=-SO:ai•w:::w:a:waaa~crsm•u a a kw~:saa:a----= -------··:=r==wa a - =--=--- =s= ~==-=-~~~=-~=-~
METER BLDG. FLOOR UNIT METER INST. MULTIPLICATION RUNNING DATE OF CURRENT LAST READING LAST UNITS AMOUNT READING STATUS
NUMBER NO. DATE NUMBER AVERAGE READING READING DATE READING CONSUMED TAKEN BY
mm:a:a.• -• ua:c•mrnawmnn.-wac -----• ::a:::z:::a:a::x-c~----~=--=::.c-~~~ma:=- --= ::a.:._m,= = = = =
)()()()()()()() )()( xx xx 99,'d9fil9 99.99 99999999 99fil9fil9 99999999 99fil9fil9 99999999 99999999 999 ,999 .99 )()()( x
)()()()()()()() )()( xx )()( 99fd9fd9 99.99 99999999 99fd9fd9 99999999 99fil9,'d9 99999999 99999999 999.999.99 )()()( x
)()()()()()()() )()( xx xx 99,'d9fil9 99.99 99999999 99,'d9fil9 99999999 99fil9fil9 99999999 99999999 999,999 99 )()()( x
TOTAL 999,999.99
CXl
~
.. END OF REPORT..
Sort Order : Company code, Project code, Meter type, Meter number
Tables used : Meter, Meter Reeding.
Report Widtt : 180 cols
THIS REPORT CAN BE PRINTED BY METER NUMBER. BY METER TYPE. BY BUILDING. BY FLOOR AND BY UNIT
REPORT NAME : XXXXXXXXXXXXXXX VERSION : XXXXXXXXXXXX
RUN BY : XXXXXXXX (USER - IOI ON 99/9919999 99:99
================================================================================================================================
XXXXXXXXXXXX COMPANY NAME CHAR(501 XXXXXXXXXXXX DATE: 99/99/999
XXXXXXXXXXXX PROJECT NAME CHAR(50l XXXXXXXXXX <X PAGE: 999
EUIPMENTS AVAILABLE FOR RENTAL AS ON 99/99/999J
===========================================·=====================================================================================
EQUP. DESCRIPTION STANDARD TOTAL RENTED OUT OF QTY IN
CODE CHARGES QTY QTY. ORDER HAND
================================================================================================================================
99 501XXXXXXXXXXXXXXX 999,999.99 999999 999999 999999 999999
XXXXXXXXXXXXXXX XXXXXXXXXXXXXXX
99 XXXXXXXXXXXXXXX50l 999,999.99 999999 999999 999999 999999
99 XXXXXXXXXXXXXXX 501XXXXXXXXXXXXXXX 999,999.99 999999 999999 999999 999999
================================================================================================================================
••END OF REPORT••
00
Vl
Sort Order Company code, Project code, Equipment code.
Tables used EquipmenUor_rental
Report Widt~ 132 cols

RUN BY : XXXXXXXX (USER • IOI ON 99/99/9999 99:99
===================================================================================================================================
XXXXXXXXXXXX COMPANY NAME CHAR(50l XXXXXXXXXXXX DATE: 99(99/9999
XXXXXXXXXXXX PROJECT NAME CHARt501 XXXXXXXXXXXX PAGE: 999
EQUIPMENT ISSUE/RECEIPT REGISTER FROM 99/99/9999 TO 99/99/9999
===================================================================================================================================
DATE SLIP EQUIPMENT DESCRIPTION PROPERTY RENT PERIOD AMOUNT RETURN
NO. CODE ID ID FROM TO DATE
\
===================================================================================================================================
99/99/99 xxxxxx 99 XXXXXXXX XXXXXXXXXXXX:00000000<(50JXXXXXXXXXXXXXXX xx xx xx 99/99199 99/99/99 999,999.99 99/99/99
99199/99 xxxxxx 99 XXXXXXXX XXXXXXXXXXXX'O<(SOJXXXXXXXXXXXXXXX xx xx xx 99/99(99 99/99/99 999,999.99 99199/99
99/99/99 xxxxxx 99 XXXXXXXX XXXXXXX>OOOOC00000000<!501XXXXXXXXXXXXXXX xx xx xx 99/99/99 99/99/99 999,999.99 99/99/99
===================================================================================================================================
.. END OF REPORT..
00
(1\
Sort Order Company code, Project code, Date.

Tables used Equipment.Jor_rentel, EquipmenLrental_cherges.
Repot Width : 132 cols
THIS REPORT CAN BE PRINTED BY DATE, BY EQUIPMENT CODE. BY BUILDING, BY FLOOR AND BY UNIT.
REPORT NAME : XXlOOOOOOOOOOOO VERSION : XXXXXXXXXXXX
RUN BY : :XXXXXXXX !USER· ID) ON 99/99/9999 99:99
==============================================================================================================================
XXXXXXXXXXXX COMPANY NAME CHARl50) XXXXXXXXXXXX DATE: 99/99/9999
XXXXXXXXXXXX PROJECT NAME CHARl50) XXXXXXXXXXXX , PAGE: 999
I
LIST OF EUIPMENTS NOT RETURNED FROM 99/99/9999 to 39/99/9999

========·===-=--.:=-= =============-=-= =============== =================================================.:::..=====::..=-==:
DATE
SLIP EQUIPMENT DESCRIPTION PROPERIY RENT PERIOD AMOUNT
NO. CODE ID ID FROM TO
;;:;:;;;;:;.::====-==========·=-=:=-=======-====.:.====--=-========.=:--===========-=-=-====-==-::.========-=·==.:::,:;;::::.:::=-==·==========-==-=:=-====
99 :xxxxxxxx 99 :XXXXXXXX XXXXXXXXXXXXXXX1501XXXXXXXXlOOOOOO xx xx xx 99/99/99 99/99/99 999,999.99
99 :xxxxxxxx 99 :XXXXXXXX XXXXXXXXXXXXlC:XXXXXXX(SO~XXXXXXXXlOOOOOO xx xx xx 99/99/99 99/99/99 999,999.99
99 :xxxxxxxx 99 :XXXXXXXX XXXXXXXXXXXXXXX(SO)XXXX'.XXXXXXXXX xx xx xx 99/99/99 99/99/99 999,999.99
00
-...J
0
END OF REPORT..
Sort Order Company code, Project code, Date
Tables used EquipmenUor_rental, EquipmenLren1ial_charges.
THIS REPORT CAN BE PRINTED DATE WISH, EQUIPMENT CODE WISE. bUILDING WISE. FLOOR WISE AND UNIT WISE
REPORT NAME : XXXXXXXXXXXXXXX /ERSION XXXXXXXXXXXX
RUN BY : XXXXXXXX (USER - ID) ON 99/9919999 99:99
================================================~=============================================================================
XXXXXXXXXXXX COMPANY NAME CHAR(50) XXXXXXXXXXXX DATE: 99/99/9999

XXXXXXXXXXXX PROJECT NAME CHARl50) XXXXXXXXXXXX PAGE : 999
LIST OF EUIPMENTS OUT OF ORDER AS ON 99/99/9999
==============================================================================================================================
EOUP. EQUP. DESCRIPTION DATE
CODE ID (FROM WHICH OUT OF ORDER)
==============================================================================================================================
99 XXXXXXXX XXXXXXXXXXXXXXX50!XXXXXXXXXXXXXXX 99/99/99
99 XXXXXXXX XXXXXXXXXXXXXXXSO!XXXXXXXXXXXXXXX 99/99/99
99 XXXXXXXX XXXXXXXXXXXXXXX50)XXXXXXXXXXXXXXX 99/99/99
00
00 =====================================================================================================r========================
.. END OF REPORT..
Sort Order Company code, Project code, Equipment code.
Tables used Equipment..for_rent81

RUN BY : XXXXXXXX: (USER - ID) ON 99/99/9999 99:99
==============================================================================================================================
XXXXXXXXXXXX COMPANY NAME CHAR!501 XXXXXXXXXXXX DATE: 99/99/9999
XXXXXXXXXXXX PROJECT NAME CHAR(50) XXXXXXXXXXXX PAGE: 999
COMPLAINT LOG REGISTER FROM 99/99/9999 TO 99/99/9999
==============================================================================================================================
DATE COMPLAINT TIME BLDG . FLOOR UNIT REPORTED BY RECEIVED BY
NUMBER NO. DESCRIPTION
==============================================================================================================================
99/99/99 xxxxxxxx 99:99 xx xx xx XXXXXXXXXXXXXXX!50):XXXXXXXXXXXXXX xxx
XXXXXXXXXXXXXXX(50):XXXXXXXXXXXXXX
XXXXXXXXXXXXXXX(50!XXXXXXXXXXXXXXX
99/99/99 xxxxxxxx 99:99 xx xx XX I XXXXXXXXXXXXXXX(501XXXXXXXXXXXXXXX xxx
XXXXXXXXXXXXXXX(50):XXXXXXXXXXXXXX
OJ
~ XXXXXXXXXXXXXXX(501XXXXXXXXXXXXXXX
==============================================================================================================================
.. END OF REPORT..
Sort Order Company code, Project code, Date.

Tables used Job_order
THIS REPORT CAN BE PRINTED BY DATE. BY COMPLAINT NUMBER, BY BUILDING, BY FLOOR AND BY UNIT.
REPORT NAME : :XXXXXXXXXXXXXX VERSION : XXXXXXXXXXXX
===-=·=====·==·==·=====-====-= ========:::::======-======-===·=·=-====:=:==-::.:::=:::-=--==-==---==-==-=-=-=============================
XXXXXXXXXXXX COMPANY NAME CHARl50) XXXXXXXXXXXX DATE: 99/99/9999

XXXXXXXXXXXX PROJECT NAME CHAR(50) XXXXXXXXXXXX PAGE: 999
COMPLAINT ATTENDED REGISTER FROM 99/99/9999 TO 99/99/9999
===-======-=======·=-=========-=-=-======~=========== ===============================================================
!
DATE COMPLAINT TIME BLDG. FLOOR UNI~- ACTION AUTH. LABOUR MAINTENANCE STATUS WORK DONE
NUMBER NO. TAKEN BY BY CHARGES CHARGES
==============================================================================================================================
99/99/99xxxxxxxx 99:99 xx xx xx xxx xxx 999,999.99 999.999.99 x xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx
l.O 99/99/99 xxxxxxxx 99:99 xx xx xx j
xxx xxx 999,999.99 999,999.99 x xxxxxxxxxxxxxxx
0
xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx
==============================================================================================================================
.. END OF REPORT..
Sort Order Company code, Project code, Pate.

Tables used Job_order
THIS REPORT CAN BE PRINTED BY DATE. BY COMPLAINT NUMBER. BY BUILDING, BY FLOOR AND BY UNIT.
RUN BY : XXXXXXXX [USER - ID) ON 99199/9999 99:99
-==---.::rc ===~a~m=:ca-a..a:-C11:.::.mm.=:-::a.•.-=-:e•m:a=::== s .c:-e~=i:-==-a-m=i===--=---=~ ~=~ s:e:2-.:11•-===-=== =====2
XXXXXXXXXXXX COMPANY NAME CHAR[50) XXXXXXXXXXXX DATE: 99/99/9999

XXXXXXXXXXXX PROJECT NAME CHAR(50) >OOXXXXXXXXX PAGE: 999
VACANCY STATUS REPORT FROM PROPERTY TYPE XX TO XX
FROM PROPERTY CODE XX TO XX
::mz====a ~~~E-c-:cni=s~==•~•~~E~n~===~=~~c=-=c=-= =~ s::a====~~n~= =~~=sze.e====:==z==E
BUILDING FLOOR UNIT STATUS VACANT

SINCE
PROPERTY TYPE : XX XXXXXXXXXXXXXXXXXXXX CHAR(50) XXXXXXXXXXXXXXX

PROPERTY CODE : XX XXXXXXXXXXXXXXX CHAR(50) XXXXXXXXXXXXXXXXX
\D
I--' xxxxx xx xxxxxx x 99199199
xxxxx xx xxxxxx x 99/99/99
TOTAL VACANT UNITS • 999 OCCUPIED s 999 SELF OCCUPIED ~ 999
"'END OF REPORT..
Sort Order Company code, Project code, Property_type, Property_code.

Tables used Property_menegement_unit.
Report Width BO cols
THIS REPORT CAN BE PRINTED BY PR"OJECT. BY PROPERTY. BY PROPERTY CODE .

REPORT NAME : >OOOOOOOCOOCXXXXXX)()()OOOOOCIOOOC VERSION XXXXXXXXXXXX
RUN BY : XXXXXXXX (USER· ID) ON 99/9919999 99:99
••ema:e••~•=•••mmzma••=~~=•••m•••••m•a•••===zs•~=~==••zmm~D••~=•s•====~anz=:w:.::=z~~=~~==aca
XXXXXXXXXXXX COMPANY NAME CHAR(50) XXXXXXXXXXXX DATE: 99/9919999

XXXXXXXXXXXX PROJECT NAME CHAR!50) XXXXXXXXXXXX PAGE: 999
PROPERTY MANAGER'S DIARY FROM 99199/9999 TO 99/99/9999
DATE : 99/99/9999
ACTIVITY BLDG FLOOR UNIT DECRIPTION
CODE NO.
xx xx xx xx XXXXXXXXXXXXXXX CHAR(50) XXXXXXXXXXXXXXX

ld:XXXXXXXXXXXXXX CHAR(50) XXXXXXXXXXXXXXX
\,!)
xx xx xx xx x;1:xxxxxxxxxxxxxx CHAR!50) XXXXXXXXXXXXXXX
N >O;'.XXXXXXXXXXXXX CHAR!50) XXXXXXXXXXXXXXX
*'END OF REPORT*'
Sort Order Company code, Project code, Date, Building_number, Floor,

Unit_number.
Tables used Property_contract. Job_order.
THIS REPORT CAN BE PRINTED BY DATE, BY BUILDING, BY FLOOR AND BY UNIT

REPORT NAME : )00:>0000000000000COOCIOOCIOOCXXX VERSION XXXXXXXXXXXX
PROPERTY ID : XX XX XX INVOICE NO : XXXXXXXX

OWNER'S NAME XXXXXXXXXXXXXXX(50JXXXXXXXXXXXXXX DATE : 99/99/99
ADDRESS : XXXXXXXXXXXXXXX(50)XXXXXXXXXXXXXXXXX BILLING CYCLE · XXXXXX
: XXXXXXXXXXXXXXX(50JXXXXXXXXXXXXXX
: XXXXXXXXXXXXXXX(50)XXXXXXXXXXXXXXX
·-------------------
S.NO DESCRIPTION WITH VA" WITHOUT VAT
AMOUNT VAT AMOUNT
99 : XXXXXXXXXXXXXXX(50)XXXXXXXXXXXXXXX 99,999,999,999,999.99 99,999,999,999,999.99 99,999,999,999,999.99

99 : XXXXXXXXXXXXXXX(50)XXXX>:XXXXXXXXXXXXXX 99,999,999,999,999.99 99,999,999,999,999.99 99,999,999,999,999 .99
I
'°w 99 : XXXXXXXXXXXXXXX(50JXXXX>·:XXXXXXXXXXXXXXXXX 99,999,999,999,999.99 99,999,999,999,999.99 99,999,999,999,999.99
TOTAL 99,999,999,999,999.99 99,999,999,999,999 99 99,999,999,999,999.99
**END OF REPORT 0
Sort Order Project, Month, Building Number, ~loor, Unit number
Tables used Project, invoicing detail,

REPORT NAME: XXX>OOOOOOOOOOO.XXX VERSION : ~
RUN BY : XXXXXXXX !USER - ID) ON 99139/'399!l 99:99

==-==========-==-=-==::::::-===-------------=:=-===~=====-=====================================================
XXXXXXXXXXXXXXX(COMPANY NAME CHAR(50) l >JOOOOOOOOOO< DATE: 99/'39/9999

PAGE: 999
INVOICE SUMMARY FOR PROJECT XX FROM 09139/'3999 TO 99139/9999
======================================~============================================================
Project code : XXX XXXXXXXXXXXXX!50
Billing Charged Amount Vet Charged

Cycle
xxxxxx 99,999,999,999,999.99 99,999,999,999,999.99
xxxxxx 99,999,999,999,999.99 99,999,999,999,999.99
'°+'
TOTAL: 99,999,999,999,999 .99 99,999,999,999,999.99
TOTAL AMOUNT CHARGED : 99,999,999,999,999.99 FROM 99/'39/9999 TO 99/991'3999

TOTAL VAT CHARGED 99,999,999,999,999.99 FROM 99/99/9999 TO 99139/9999
===================================================================================================
HEND OF REPQRTH
Sort Order Project, Month, Building Number, floor, Unit number
Tables used Project, invoicing detail,

APPENDIX D
MENU DESIGN
95
ADD MODIFY DELETE QUERY OCCUPANT DETAILS BILLING ADDRESSES EXIT
TENANT I OWNER PROFILE
COMPANY PROJECT __ PROPERTY 'TYPE

-
PROPERTY ID
-'-'- PRODUCT
-- MODEL
OWNER'S NAME (English)
'
(Thai)
ADDRESS
CITY ZIP TELEPHONE
""
O"I
TYPE OF OWNER:_
PASSPORT NUMBER
ID NUMBER
VISA NUMBER
NATIONALITY
VALID UPTO 'i
- ----- 7---- -- ---- -- - ----- - -

HELP AVAILABLE :
1) Help will be available on contract code in all modes except add mode
2) Help will be available on building. floor and unit number in all
modes other than add mode.
AUTO GENERATED FIELDS :

1) Contract number will be auto-generated in all modes except add mode
DISPLAY ONLY FIELDS :

1) Property type, product type and model number
\D SEPAAATE POPUP SCREENS FOR ENTERING OCCUPANT DETAILS AND BILLING ADDRESSES
........
WILL BE AVAILABLE AND ARE SHOWN ON NEXT PAGE
1) OCCUPANT DETAIL POPUP ;
.................................... ,............................ .
" OCCUPANT DETAILS •
• S.NO. NAME "
• -- •
" •
• -- -· ... '
•
• •
• -· •
.. "
•
• - - •
• •
....................................................................
\.0
00
2) BILLING ADDRESSES
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
" RENT INVOICIMG ADDRESSES "
" S.NO. "
" NAME
" ADDRESS "
• •
• •
• •
" RATIO - - - (PERCENll •
" •
" •
• •
·····································~····························
ADD MODIFY DELETE QUERY EXIT
SERVICED APARTMENT CONTRACT
COMPANY PRO.JECT PROPERTY ID _ / _J _

CONTRACT NUMBER DATE
OWNER'S NAME (English)
(Tha~
ADDRESS
CITY
- ZIP - - -
TELEPHONE FAX
ID NUMBER NA"TIONALITY
PASSPORT NUMBER VISA NUMBER VALID UPTO
'°'°
MONTHLY RENT FURNITURE CHARGES
SERVICE CHARGES TOTAL
RENT START DATE CONTRACT END DATE

RENEWAL DATE AGENT CODE
REMARKS
HELP AVAILABLE :
1) Help will be available on contract code in ell modes except edd mode
2) Help will be available on building. floor and unit number in all modes other
then edd mode.
AUTO GENERATED FIELDS :

1) Contract number will be auto-generated in all modes except add mode
I-'
0
0
ROOM RATE MAINTENANCE
COMPANY PROJECT
--
ROOM TYPE
-
DAILY RATE WEEKLY RATE
MONTHLY RATE QUARTERLY RATE
HALF_YEARLY RATE YEARLY RATE

I-'
0
I-'
HELP AVAILABLE :
Help will be available on Room type in which different room types
will be displayed along with their descriptions.
AGENT MASTER MAINTENANCE
COMPANY PROJECT
--
AGENT CODE
NAME (English)
NAME (Thai)
ADDRESS
t-'
0
N
CITY ZIP PHONE
HELP AVAILABLE :
1) Help will be available on· field. agent code in which agent's name
and code will be displayed in sorted order and can be selected
by operator by pressing enter key.
CHARGE TYPE MASTER
CHARGE DESCRIPTION VATABLE (YIN )

CODE
1
I-'
0
I
i
w
HELP AVAILABLE
Help will be available on :
1) Charge code in which charge code end description will be
displayed. The operator i:en select any code by pressing enter.

MISCELLANEOUS CHARGES
COMPANY PROJECT BILLING CYCLE
PROPERTY ID _J_J_
CHARGE CODE
SERVICE DESCRIPllON
f--'
0
~
CHARGED AMOUNT BILLING CYCLE
HELP AVAILABLE :
Help will be aveilable on following fields :
1) Building number in which building code and description will be
displayed
2) Charge code in which charge codes and their descriptions will
be displayed and on !anterir¢electing a charge code its
description will be d~layed
I
In all these cases the ciperator can select the desired code by
pressing enter key. ·
DISPLAY ONLY FIELDS:
1) Billing cycle
f-'
0 NOTE Property Id is building number, floor, unit number
V1
METER MAINTENANCE
COMPANY PROJECT
METER NUMBER METER TYPE __ INSTALLATION DATE
PROPERTY ID _/_/_
MULTIPLICATION FACTOR
I-' LAST READING DATE LAST READING

0
°'
RUNNING AVERAGE STATUS
HELP AVAILABLE :
Help will be available on following fields :
1l Meter number in which all the meter numbers in the project
entered will be displayed e'ong with its type building. floor
and unit number.
2) Building number in which Guilding code and desc~ion will be
displayed
In all these cases the operator can select the desired code by
pressing enter key.
CALCULATED FIELD ·
1) Running average
I-'
0
'-l
NOTE Property Id is building number, floor, unit number
ADD MODIFY DELITT QUERY EXIT
MITTR READING DETAILS
COMPANY PROJECT
METER NUMBER LAST READING
PROPERTY ID
CURRENT READING
_J __L _ BILLING CYCLE
READING DATE 1
I-'
0
READING TAKEN BY
I
00
i
HELP AVAllABLE
1l Meter number in which all the meter numbers in the project
entered will be disp:ayed along with its type building. floor
and unit number.
DISPIAY ONLY FIELDS :

1) Last reading
2) Property Id
3) Billing cycle
f-J
0
'°
EQUIPMENTS AVAILABLE FOR RENTAL
COMPANY PROJECT
EQUIPMENT CODE
DESCRIPTION
STANDARD MONTHLY RENTAL CHARGES
f-' EQUIPMENT ID STATUS

f-'
0
·:
HELP AVAILABLE
1) Equipment code in which all the equipment codes will be
displayed along with their desc~ion (TELEVISION, VIDEO
etc.)
2) Equipment Id in which all equipments of a particular code will
be displao(ed along with their descriptions
pressing enter key.
I-'
I-'
I-'
EQUIPMENT RENTAL
COMPANY -- I PROJECT
ISSUE SLIP NUMBER -- ISSUE DATE
EQUIPMENT CODE EQUIPMENT ID
I
DESCRIPTION
PROPER'TY ID _/_J_
f-'
f-'
MONTHLY CHARGES
RENT PERIOD : FROM TO I

I
N
RETURN DATE STATUS

HELP AVAILABLE
1) Issue slip in which issue! slip number and date will be
displayed
2) Building number, floor and unit number.
pressing enter key.
AUTO GENERA1ED FIELDS :

1) Issue slip number will be system generated in Add mode and in
other modes will be entered by user
DISPLAY ONLY FIELDS

1) Desc~ion will be display only field and will be displayed
when equipment id is entered.
I-'
I-'
\.JJ
NOTE : Property Id is building number, floor, unit number
SERVICE COMPLAINTS
COMPANY PROJECT
COMPLAINT NUMBER STATUS _
DATE REPORTED TIME
PROPERTY ID
-'-'-
COMPLAINT_DESCRIPllON
I-'
I-' REPORTED BY
+""
RECEIVED BY
HELP AVAILABLE ·
1l Complaint number in which complaint number, date, building,
floor and un~ will be disphr,:ed
2) Building number in which building code and description will be
displayed
In ell these cases the operator can select the desired code by
pressing enter key.
I
3) Status in which ell valid val~ will be displayed on
1
status line ( R • Returned erd N • Not returned)
AUTO GENERATED FIELDS:

1) Complaint number will be system generated in Add mode and
in other modes will be entered by user
1
i
f-'
f-'
V'I DISPLAY ONLY FIELDS
1) Date reported
2) lime reported
NOTE : Property Id is building number, floor, un~ number

COMPLAINT SERVICE DETAILS
COMPANY PROJECT
COMPLAINT NUMBER STATUS
DATE REPORTED TIME PROPERTY ID _J _J _
COMPLAINT_DESCRIPTION
I-'
I-'
(]'\ S. DATE TIME DESCRIPTION LABOUR MISCELLANEOUS AUTH
NO . CHAHC.:H::~ CHAHut::~ ~y
HELP AVAILABLE
Help will be evaileble on :
1l Complaint number in which complaint number, date, building,
floor and unit will be displayed
In this case the operator can select the desired code by
pressing enter key.
DISPLAY ONLY FIELDS

1) Registration date.
2) Status
3) Date and Time
4) Poperty Id
6) Complaint desc~tion
f-' Description will be a scrollable field (length 60)

f-'
-...J

BIWNG CYCLE MAINTENANCE
BIWNG CYCLE FROM TO

CODE
r'
r'
00
HELP AVAILABLE
Help will be available on
1) Billing cycle code in w~· ich billing cycle code along
with from and to dates will be displayed. The operator can
select any code by pmsing enter.

ACTMlY CODE MAINTENANCE
ACTIVllY DESCRIPTION
CODE
f--'
f--'
'°
HELP AVAILABLE
1) Activity code in which activity codes along with their
desc~ion will be displayed. The operator can
select any code by pressing enter.
ADD MODIFY ' DELETE QUERY EXIT
PM DIARY MAINTENANCE
COMPANY PROJECT
DATE CODE DESCRIPTION REMARK PROPER1Y CONTRACT STATUS

ID NO .
_L_/ _
_ l_I_
f--'
N
0
-'-'-
_l_!_
HELP AVAILABLE
1) Activity code in which activity code along w~h their
description will be displayed. The operator can select
any code by pressing enter.
DISPLAY ONLY FIELDS :

1) Description
NOTE : Description and Remarks will be scrollable iields (length 50)
I
~ I-'
~
N
I-'

AU Project Report Fulltext 111667

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AU Project Report Fulltext 111667

Uploaded by

Copyright:

Available Formats

.

PROPERTY MANAGEMENT SYSTEM

Final Report of the Three-credit Course

Submitted In Partial Fulfillment

Name Ms. Pannipa Rewthamrongsris

Project Advisor Prof. Dr. Srisakdi Charmonman

Academic Year 1996

The Graduate School of Assumption University had approved this final

report of the three-credit course, CS 6998 ~ystem Development Project,

submitted in partial fulfillment of the requirements for the degree of Master

of Science in Computer Information Systems.

(Prof. Dr. Srisakdi Charmonman) (Dr.Suphamit Chittayasothorn)

(Dr. Sudthipom Patu.mtaewapibal) (Air Marshal Dr.Chulit Meesajjee)

(Assoc Prof .Somchai Thayamyong)

1.1 Project Background

1.2 System Objective 2

1.3 Scope of the project 2

2. The Existing System

2.2 Organization Chart 5

2.3 Current problems 6

Existing system Context Diagram 9

3. The Proposed System

3.1 User requirement 11

3.2 New system requirement 12

3.3 System design Analysis & Design 15

_ 3.4 Hardware and Software requirement 29

3.5 Securrty and Control 31

3.6 Cost and Benefit analysis 33

4.1 Project implementation schedule 40

5. Conclusion and Recommendation

7.1 Appendix A : Data Dictionary 50

7 .2 Appendix B : Program Mini Specification 71

7.3 Appendix C : Report Layout 76

7.4 Appendix D : Menu Design 95

This system development project provides the analysis, design

and implementation of a Property Management System for the

operation work in a Property Management Department of a real estate

development and management company.

The Property Management system is a system which

provide a better security and control of information system. This

includes the process time, data accuracy and redundancy.

We develop the system to reduce the existing problems of

system will be Mplar.ed by this new sy~te~ •::hich bc~d on

computerized system for Management of Information System and using .the

advantages of Database Management System Approach This application

will be implemented on PC Lan with FOX PRO Language.

Figure 1 Company Organization Chart 5

Figure 2.1 Context Diagram (Existing System) 9

Figure 2.2 Data Flow Diagram (Existing System Level 1 ) - 10

Figure 3.2.1 Data Flow Diagram (Level 1) 17

Figure 3.2.2 Data Flow Diagram (Level 2) 18

Figure 3.2.3 Property Management Level 2 (Process 3.1) 19

Figure 3.3 Cost Comparison Table 38

Figue 3.4 Graph of Cost Benefit of the System 39

Figure 4 Project Implementation Schedule 46

1.1 Project Background

This system development project provides the analysis, design and

implementation of a Property Management System for the operation work in

Property Management Department of a real estate development and

management company. The system description, functions and system

databases are briefed thereafter.

To solve the problems of existing system which is done by wholly

manual system, the new property management system is developed under

the company committee approvals. The committee is composed of the