Professional Documents
Culture Documents
Database Systems
Report on Hajj
Management
Information System
Hajj Management System
Abdul M. Rahman,
Thomas Mays,
Nam Pham,
Kai Fai Lau
07
EXECUTIVE SUMMARY
The yearly pilgrimage to Saudi Arabia, known as the Hajj, is performed by millions of
people from around the world. Due to the extremely large number of people all
performing the same activities in the same locations, tracking an individual pilgrim is
very difficult.
The proposed system will introduce RFID Tags, which will be worn by every pilgrim.
When a sensor sweep is performed, the system will automatically store the current
location of all pilgrims participating in the Hajj in a database. If a pilgrim were to go
missing, that pilgrim’s last known location can be seen in the database; narrowing the
search location significantly. This will greatly increase the success of finding any lost
pilgrims.
The information stored on each pilgrim’s RFID Tag will include their pilgrim ID, name,
group manager, finger print, retina print and more. If a pilgrim is found and cannot be
identified by physical means, the Tag can be used to identify the pilgrim.
2
REPORT ON HAJJ MANAGEMENT
INFORMATION SYSTEM
AUTHORS
Abdul M. Rahman
Thomas Mays
Pnam Pham
Kai Fai Lau
SUBJECT NUMBER
7157
SUBJECT NAME
Database Systems
TUTORIAL DAY/TIME
Thursdays
TUTOR
Mohammad Yamin
3
TABLE OF CONTENTS
AUTHORS ............................................................................................................................... 3
SUBJECT NAME.................................................................................................................... 3
TUTOR..................................................................................................................................... 3
INTRODUCTION ................................................................................................................... 7
INTRODUCTION......................................................................................................................... 8
RICH PICTURE .......................................................................................................................... 9
DOMAINS................................................................................................................................. 10
MAPPING OBJECTS TO RELATIONS ...................................................................................... 10
OBJECT RELATIONSHIPS ....................................................................................................... 11
OPERATIONS ........................................................................................................................... 11
SCHEMA .................................................................................................................................. 14
OBJECT MODEL ..................................................................................................................... 15
USE CASE DIAGRAM ............................................................................................................. 16
SYSTEM SEQUENCE DIAGRAMS ..................................................................................... 17
AMEER ..................................................................................................................................... 17
FAMILY .................................................................................................................................... 17
HOSPITAL ................................................................................................................................. 18
MINISTRY OF HAJJ ................................................................................................................... 18
POLICE ..................................................................................................................................... 19
SAUDI EMBASSY ...................................................................................................................... 20
CONCLUSION .......................................................................................................................... 21
INTRODUCTION....................................................................................................................... 22
SOFTWARE INTERFACE DESIGN ............................................................................................ 22
PROTOTYPE FUNCTIONALITIES ............................................................................................ 22
4
PILGRIM HISTORY SYSTEM...................................................................................................... 22
MISSING PILGRIM INFORMATION SYSTEM .............................................................................. 22
PILGRIM IMMIGRATION INFORMATION SYSTEM ..................................................................... 22
PILGRIM IDENTITY INFORMATION SYSTEM ............................................................................. 22
DBMS INTERFACE ................................................................................................................. 22
CONCLUSION .......................................................................................................................... 22
INTRODUCTION....................................................................................................................... 23
RFID SENSOR ......................................................................................................................... 23
SENSOR ZONES ........................................................................................................................ 23
SENSOR DATA COLLECTION STRATEGY .............................................................................. 23
S ENSOR S ERVER ( S ) ............................................................................................................... 23
C ITY R OUTERS AND C ENTRAL D ATA S TORAGE F ACILITY ............................................. 23
CONCLUSION ...................................................................................................................... 24
INTRODUCTION....................................................................................................................... 25
CENTRAL DATA STORAGE FACILITY.................................................................................... 25
JEDDAH .................................................................................................................................... 25
CITY NETWORKING ROUTER(S)/SERVER ............................................................................. 25
MECCA ..................................................................................................................................... 25
MEDINA ................................................................................................................................... 25
SENSOR & SERVER LOCATIONS ............................................................................................ 26
TRANSPORT SENSORS .............................................................................................................. 26
Public Buses ............................................................................................................................ 26
Airport Sensors........................................................................................................................ 26
Airport Arrival Gates............................................................................................................... 26
PHYSICAL LOCATION SENSORS ............................................................................................... 26
Jeddah Airport ......................................................................................................................... 26
Jeddah to Mecca ...................................................................................................................... 26
Mecca ...................................................................................................................................... 26
Kabaa....................................................................................................................................... 26
Tent City of Mina .................................................................................................................... 27
Mount Arafat ........................................................................................................................... 27
Mecca to Medina ..................................................................................................................... 27
Medina..................................................................................................................................... 27
Medina to Jeddah..................................................................................................................... 27
CONCLUSION .......................................................................................................................... 27
INTRODUCTION....................................................................................................................... 28
HAJJ MANAGEMENT INFORMATION SYSTEM ...................................................................... 28
5
MISSING PILGRIM INFORMATION SYSTEM .............................................................................. 28
Design...................................................................................................................................... 28
Implementation........................................................................................................................ 28
PILGRIM HEALTH INFORMATION SYSTEM ............................................................................... 29
Design & Implementation ....................................................................................................... 29
PILGRIM IMMIGRATION INFORMATION SYSTEM ..................................................................... 29
Design and Implementation..................................................................................................... 29
PILGRIM IDENTITY INFORMATION SYSTEM ............................................................................. 29
Design and implementation..................................................................................................... 29
PILGRIM HISTORY SYSTEM...................................................................................................... 29
Design and Implementation..................................................................................................... 29
SENSOR MANAGEMENT SYSTEM ............................................................................................. 30
Design and Implementation..................................................................................................... 30
ACTORS AND FUNCTIONALITIES ........................................................................................... 30
CONCLUSION .......................................................................................................................... 30
INTRODUCTION....................................................................................................................... 31
DATA MINING BENEFITS ....................................................................................................... 31
ACCOMMODATION & UTILITIES .............................................................................................. 31
TRANSPORTATION ................................................................................................................... 31
ROUTE PLANNING .................................................................................................................... 31
PATTERN RECOGNITION .......................................................................................................... 31
Crowding Pilgrims .................................................................................................................. 31
Lost Pilgrims ........................................................................................................................... 31
GENERAL STATISTICS .............................................................................................................. 32
DATA QUALITY ISSUES .......................................................................................................... 32
CONCLUSION .......................................................................................................................... 32
CONCLUSION OF REPORT.............................................................................................. 33
6
INTRODUCTION
Every year, millions of pilgrims travel to the sacred country of Saudi Arabia to perform
in the spiritual event known as the Hajj. While there, each pilgrim must complete a
number of scheduled activities over their four day pilgrimage.
Due to the extremely large number of participants (up to 6 million people), all of which
must perform the same activities at the same time, tracking any one pilgrim physically is
almost impossible. Currently, Hajj officials must rely on physical characteristics to track
individuals down. If a pilgrim were to go missing or get lost in such a large crowd,
locating that pilgrim is very difficult.
It is proposed in this project that an information based system should be implemented
to track the location, and to store the personal details, of all participants at the Hajj.
In order for the new system to work, every pilgrim will be allocated with an RFID Tag
which will store that pilgrim’s personal details (pilgrim ID, name, group manager, finger
print, retina print, etc). To track the location of the pilgrim, organisers simply search the
database for that pilgrims ID and the last known location of that pilgrim will be
displayed. To locate a Tag, sensors will be strategically positioned around cities and
events.
Not only will the RFID Tags be used to locate any pilgrim at the Hajj, the details stored
on the Tag can also be used to identify pilgrims who have been killed and their bodies
are unidentifiable by physical methods.
7
DOCUMENT ANALYSIS & DESIGN OF HMIS
INTRODUCTION
The analysis and design of the system is dependent on the main requirements of the
HMIS (Hajj Management Information System) Case Study. This design is highly
dependent upon the nature of that case study in terms of scope and boundary.
HMIS is a very complex system, and will have to go undergo several revisions to be of
any practical use. The report, however, presents the audience with the backbone
structure of such a system. Further research should be commissioned on the
implementation of such a system.
The system has been designed following the Object Modeling Methodology, so it will
show the reader the process by which the modeling has evolved from rich pictures to
final object models for this project.
8
RICH PICTURE
Police
Area #
Sensor
Pilgrim
Sensor Location Database
Pilgrim Information Database History Database
Embassy PDA
Network Interface
Family
Authorities/ Ameer/
Hospital Maulim
9
DOMAINS
To construct the domain of this system, the rich picture was used to break all the main
actors down. This list of main entities/objects would be responsible for all operations in
the system and they have listed below:
Pilgrim
Responsible for all pilgrim related information including all pilgrim details, and
pilgrim related operations.
Group
Responsible for accessing/reviewing information related to the various groups
in the pilgrimage.
History
History will keep the locations of every pilgrim’s RFID scan data. This is the main
object that will be responsible to keep that data.
SensorZones
This object will keep the entire list of sensor ID’s and their relevant details, such
as their location.
MAPPING OBJECTS TO RELATIONS
The objects are then turned into their own relations following a process of
generalization. This would involve the objects be assigned variables that would match
the data in the relational tables.
As the relations show below, the fields have been set in, and the unique/primary keys
have been assigned to the tables.
Pilgrim (pilgrimID, pilgrimName, pilgrimDOB, pilgrimCountry, pilgrimPassport,
pilgrimFingerprint, pilgrimRetina, pilgrimMedicalIssues, groupID, sensorID,
pilgrimDistance, pilgrimTimeDate, pilgrimAlert)
Group (groupID, ameerID, maulimID)
History (pilgrimID, sensorID, pilgrimDistance, pilgrimTimeDate)
SensorZones (sensorID, sensorZoneDescription)
10
OBJECT RELATIONSHIPS
The relationships of the entities have been described below with the diagram:
Relationship 1 – Pilgrim and Group
Relationship 2 – Pilgrim and History
Relationship 3 – Pilgrim and SensorZones
OPERATIONS
The operations of the various objects are listed and described below:
Pilgrims
addPilgrimInformation (string pilgrimID, string pilgrimName, date pilgrimDOB, string
pilgrimCountry, string pilgrimPassportNo, string pilgrimMedical, string groupID)
– This will add basic information to the database about a particular pilgrim. The actor who
will be responsible for this would be the Saudi Embassy or the Ministry of Hajj.
editPilgrimInformation (string pilgrimID, string pilgrimName, date pilgrimDOB, string
pilgrimCountry, string pilgrimPassportNo, string pilgrimMedical, string groupID)
‐ This method will be responsible for any correction to be made to the pilgrim’s information.
deletePilgrimInformation (string pilgrimID)
‐ Responsible for deleting a particular pilgrim.
addPilgrimCurrentLocation (string sensorID, int pilgrimDistance, date pilgrimTimeDate)
‐ This method will be responsible for adding the current location of a pilgrim in.
11
verifyDistress (string pilgrimID)
‐ Will return a Boolean value indicating if the pilgrim is under distress.
activatePilgrimDistress (string pilgrimID)
‐ Will activate the pilgrim’s distress value in the database.
viewPilgrimImmigration (string pilgrimID, string pilgrimName, string pilgrimDOB, string
pilgrimPassportNo)
‐ View the pilgrim’s immigration information, using any of those values.
viewPilgrimHealth (string pilgrimID, string pilgrimName, string pilgrimDOB, string
pilgrimPassportNo)
‐ View the pilgrim’s health information, using any of those values.
viewPilgrimCurrentLocation (string pilgrimID)
‐ View the pilgrims current sensor location data.
Group
addGroup (string groupID, string ameerID, string maulimID)
‐ Adds the particular group
editGroup(string groupID, string ameerID, string maulimID)
‐ Edits the group details
deleteGroup(string groupID, string ameerID, string maulimID)
‐ Delete the group
History
addPilgrimHistory(string pilgrimID, string sensorID, int pilgrimDistance, date
pilgrimTimeDate)
‐ Add a history of a particular’s pilgrim data.
12
viewPilgrimHistory(string pilgrimID, string sensorID, int pilgrimDistance, date
pilgrimTimeDate, ArrayList result)
‐ Return the specific Pilgrim’s history
SensorZones
addZone (string sensorID, string sensorZoneDescription)
deleteZone (string sensorID)
editZone (string sensorID, string sensorZoneDescription)
viewZoneInformation (string sensorID, string sensorZoneDescription)
13
SCHEMA
14
OBJECT MODEL
15
USE CASE DIAGRAM
16
SYSTEM SEQUENCE DIAGRAMS
AMEER
FAMILY
17
HOSPITAL
MINISTRY OF HAJJ
18
POLICE
Police HMIS
activatePilgrimDistress
{string PilgrimID}
Distress activated
viewPilgrimImmigration
{string PilgrimID, sting PilgrimName, data PilgrimDOB, string PilgrimPassportNo}
viewPilgrimHealth
{string PilgrimID, sting PilgrimName, data PilgrimDOB, string PilgrimPassportNo}
viewPilgrimCurrentLocation
{string PilgrimID}
19
SAUDI EMBASSY
Saudi
HMIS
Embassy
addPilgriminfo
{String PilgrimID, String PilgrimName, Date PilgrimDOB, String PilgrimCountry,
String PassportNo, String Fingerprint, StringMedical, String groupID}
deletePilgrimInformation
{string PilgrimID}
Deletation confirm
activatePilgrimDistress
{string PilgrimID}
Distress activated
viewPilgrimImmigration
{string PilgrimID, sting PilgrimName, data PilgrimDOB, string PilgrimPassportNo}
viewPilgrimHealth
{string PilgrimID, sting PilgrimName, data PilgrimDOB, string PilgrimPassportNo}
viewPilgrimCurrentLocation
{string PilgrimID}
Deletation confirm
20
CONCLUSION
The design of this system has been made to accommodate the needs as stated by the
various actors and users of system. The system successfully meets those requirements
by this design, and thus if the requirement would change it would require the design to
change even, drastically to accommodate those needs.
The design of this system has been kept as simple as possible to accommodate the huge
amount of data the system has to deal with, but the end result will depend on the
hardware itself.
21
PROTOTYPE OF HMIS SYSTEM
INTRODUCTION
The prototype of the Hajj Management Information System has been developed
to show the main functionalities of the system. The prototype’s main function is
to show potential clients on how a system might look like for the end user.
SOFTWARE INTERFACE DESIGN
The interface design
has been kept very
simple to use with
the data being
displayed, and the
associated functions
of the system on the
right side of the
displayed data.
The interface has
been divided into tabs to demonstrate the various functionalities of the system
(Please see the image pasted on the side). The functionalities and their purpose
have been explained in the next section.
PROTOTYPE FUNCTIONALITIES
PILGRIM HISTORY SYSTEM
This form will display all the last locations of the pilgrim.
MISSING PILGRIM INFORMATION SYSTEM
This form will show the pilgrim’s last known location.
PILGRIM IMMIGRATION INFORMATION SYSTEM
The Pilgrim’s Immigration system shows the passport number and the visa
number of the pilgrim.
PILGRIM IDENTITY INFORMATION SYSTEM
This shows the pilgrim’s identity details such as birth date and country of origin.
DBMS INTERFACE
The DatabaseRead class contains instructions for the software to connect to the
relational database. This class contains methods that connect according to their object
parent. Source code has been provided in the HTML file in the CD.
CONCLUSION
The prototype is in it’s infancy as a system as it displays the data, and does basic data
manipulation. The prototype shows all the functionalities of the system. The
functionalities can then be implemented into other platforms so that other systems can
access these functionalities using the prototype as a guide.
22
INTERFACE TO SENSOR NETWORKS
INTRODUCTION
Sensors are an essential part of the system, as they will be intimately involved in
solving the report’s main focus of tracking pilgrims. Pilgrims are to wear these
RFID (Radio Frequency Identification Tag) at all times during the voyage.
These RFID tags will distribute their signal constantly (5 minutes), and sensors
will be installed all over popular spots to track the pilgrims.
RFID SENSOR
SENSOR ZONES
Zones will be set up as individual sensor(s). Thus, for every zone there is a
sensor. Sensors will be mounted on top of roof tops and lamp posts, and other
government related structures to monitor the pilgrims.
Zones will also be broken down on how many people are expected to be in the
particular zone. Mina is heavily congested and this compartmentalization of
sensors might be necessary to let the technology work sufficiently enough.
(Please view Map 2)
Global Positioning data will not be natively supported but local co‐ordinates and
zone number will be sufficient enough to create a GPS co‐ordinate.
This process will involve recording the co‐ordinate from the local sensor first.
After that, the co‐ordinate will be recalled from the database, and with the co‐
ordinate and the zone number will be enough to create a GPS co‐ordinate on the
fly by the HTTP server.
SENSOR DATA COLLECTION STRATEGY
S ENSOR S ERVER ( S )
Sensor Servers will maintain the intensive initial sensor data collection. They
will have to provide the service through the following process:
1. Collect all sensor information
2. Scan the information for pilgrim zone repeats
3. Send the information back to Central Data Storage Facility.
4. Do this every time the sensor is repeating a scan.
C ITY R OUTERS AND C ENTRAL D ATA S TORAGE F ACILITY
City Routers will receive the information from the sensor servers, and forward it
to the Central Date Storage Facility for update/archival purposes. Please look at
the image attached below, which shows the hierarchical nature of the (partial)
system from top to bottom.
23
Note: There will be many more sensor networks. The selection of a server will depend on the traffic of pilgrims in
a particular sensor network
CONCLUSION
The sensors have to be built in areas where pilgrims are to be most seen, or
visiting. This will involve analyzing some Hajj’s so that general areas of interest
can be drawn up. The distributed nature of the system makes it possible for this
system to work effectively.
24
PHYSICAL LOCATION OF HMIS AND/OR OPERATIONS
INTRODUCTION
Hajj Management Information System is primarily constructed as a database system that
will store a given pilgrims immigration, health, identity and location details. As there are
many of these pilgrims so the storage of the database system will require a large
physical storage space.
The physical location of the database system is important as the other servers will be
continuously streaming information to the Central Data Storage Facility, so this main
server must be centrally located so that the other servers can communicate with it
efficiently.
CENTRAL DATA STORAGE FACILITY
JEDDAH
Jeddah is the natural choice for the Central Data Storage Facility as it is the
central point where all pilgrims are sent to in the Kingdom of Saudi Arabia (from
now on referred to as the KSA). Jeddah also has the headquarters of police,
immigration offices, and a fast network connection can easily be established.
Jeddah is geographically centrally located to these two cities and the network
would incur less cost to build. The city also provides access to satellite internet
networks, which will serve overseas connection(s).
It should also be added that any historical data be stored here, for data‐mining
or data‐warehouse purposes, to keep costs down from making another data
storage facility anywhere else.
The Central Data Storage Facility will be called CDSF from now on.
CITY NETWORKING ROUTER(S)/SERVER
City Networking Routers have one main operation. They are simple data re‐
route stations, as they provide the access to the high‐speed optical fiber network
connection to the CDSF.
MECCA
Mecca Router will be responsible for:
• Sensor Data
o Mina
o Mount Arafat
o Kabba
o Other Locations
MEDINA
25
Medina Router will be responsible for:
• Sensor Data
o Central Medina and other spots
SENSOR & SERVER LOCATIONS
All the sensor & servers will be listed below with reasons as to their location
placement. It should be noted that this is preliminary analysis of the sensor
network and much more detailed analysis will be needed for the placement of
sensors, to achieve maximum effectiveness.
The sensors below are all described on maps, which have been referenced at the
end of each sensor location.
TRANSPORT SENSORS
Public Buses
Public Buses are important points to place sensors in. This will be vital in
keeping track of the pilgrims, during the Hajj as pilgrims use this service
a lot.
Airport Sensors
Airport Arrival Gates
This will be very important as the pilgrims must be tracked to
confirm that they have actually stepped on Saudi Arabian land.
This should be put on as the initial sensor for all pilgrims to pass
through.
PHYSICAL LOCATION SENSORS
Jeddah Airport
This is the starting point of all pilgrims and sensors over this location is
crucial in keeping data regarding the pilgrim’s arrival to Saudi Arabia,
and thus their successful start to the pilgrimage. (Please view Map 1)
Jeddah to Mecca
The transport route from Jeddah to Mecca is subject to a lot of pilgrimage
traffic, and a sensor network compromising of three checkpoints which
would scan all the pilgrims as they pass by would be beneficial for the
overall goal of keeping track of pilgrims.
Also, it should be noted that the sensors could also be installed on the
transport vehicles themselves.
Mecca
A router should be installed near central Mecca, so that the sensor
network from Mecca can transfer the data to Jeddah directly. In Mecca a
sensor network that consists of covering the Kabaa, shopping malls,
hotels and highways can benefit the system. (Please view Map 2)
Kabaa
26
A sensor network should be placed inside the main mosque to track the
potentially huge number of pilgrims circling the Kabaa at the same time.
Also as Kabaa is virtually the centre of Mecca, the central router could be
placed there. (Please view Map 2)
Tent City of Mina
The tent city of Mina will have to accommodate many sensors to serve
the entire population of pilgrims properly. Also a router for this region is
recommended as it is quite large, so that it can handle the data
effectively. (Please view Map 2)
Mount Arafat
Mount Arafat would also require a sensor network that would pick up
the RFID signals of the pilgrims. The approximate area needed is given in
the satellite picture. (Please view Map 3)
Mecca to Medina
The route from Mecca to Medina would require sensor checkpoints
again, which would upload pilgrim information through to the
checkpoints as they pass along. (Please view Map 4)
Medina
Medina will need sensors in its most important historic sites, as well as,
shopping malls, incoming and outgoing highways. (Please view Map 5)
Medina to Jeddah
This route should also have sensors that would record the last part of the
pilgrimage. This would be important for immigration purposes, to see
that pilgrims have checked out.
CONCLUSION
The Hajj Management System designed will serve the purpose of streaming the data to
the data warehouse efficiently. The sensor network designed tries to effectively gather
all relevant information and send it through, however much more research will be
needed by Saudi authorities on how to make the sensor network more feasible.
27
FUNCTIONALITIES OF HMIS
INTRODUCTION
Hajj, the annual pilgrimage to holy sites in Saudi Arabia, is performed by millions
of people every year. The objective of HMIS is to manage this task for the
authorities.
The overall system has been divided into its major functionalities to better
handle the scope of the individual actor’s requirements. This creates clear
functionalities for the system and can be distributed to any user of the system
with ease if an authentication system is implemented.
The system has been designed to have a web interface for all it’s actors for ease
of use. Having a web interface helps in cross‐platform distribution of the data
from this system, in an efficient and interactive manner. However, a form based
interface is also included, to demonstrate potential functionalities.
HAJJ MANAGEMENT INFORMATION SYSTEM
MISSING PILGRIM INFORMATION SYSTEM
As the name suggests the functionality of this particular sub‐system is to locate a
missing pilgrim. This has two specific actions:
• Trigger an internal alarm if a pilgrim is undetected for 12 hours in any sensor.
• If asked, display a map and show the pilgrim’s last known location as a dot on
the map.
• Also, a history of the pilgrim can be called for and the pilgrim’s history can be
displayed as dots on a web page.
Design
The database has the capability of providing all these functionalities; however our
software does not have the ability to do all these actions yet. This is because
implementing these functions will be quite time‐consuming to code in and is beyond the
scope of this project.
Implementation
The internal trigger of the alarm can be activated if the particular pilgrim’s current
known location hasn’t been updated for 12 hours. This will check a boolean value in the
database which will alert the authorities that a pilgrim is missing.
The map can be implemented by combining the data from the sensors, of the pilgrim’s
last known location. This can be manipulated into a GPS co‐ordinate by a mathematical
formula along with the pilgrim’s signal distance. A map can be generated on the fly, and
given to the user.
The last functionality would mean the ability of the police/relevant authorities to track
the pilgrim’s last movements very accurately on a map.
28
PILGRIM HEALTH INFORMATION SYSTEM
The PHIS is a module of the software that only displays pilgrim’s health information.
This information is directly accessible from the web interface, and has been primarily
designed for hospitals and emergency staff members.
Design & Implementation
The design of this module is quite simply to construct a view in the database for this
particular information. This is included in the application, as the application connects to
the database with SQL code.
The data is then displayed in the webpage in the appropriate fields. This data can be
used by actors to perform their associated activities.
PILGRIM IMMIGRATION INFORMATION SYSTEM
This particular sub‐system creates a view that lets actors see all the immigration details
of a pilgrim. This system also means that users can add immigration details of the
pilgrims.
Design and Implementation
The design of this system would involve a specific SQL Table view that would import the
necessary information, and another SQL statement that would add the pilgrim’s
immigration information.
This then can be updated on a web page in appropriate fields.
PILGRIM IDENTITY INFORMATION SYSTEM
The Pilgrim Identity Information System is a very simple system that displays the
pilgrim’s identification details, and nothing else.
Design and implementation
This is done by creating a view of the database and displaying the data directly to the
web page.
PILGRIM HISTORY SYSTEM
The Pilgrim History System has two specific functionalities:
• To add location history for every pilgrim
• Return a full set of history for anyone wanting access to that particular data.
Design and Implementation
The database can be accessed through the History object and the operations in the
history interact with the database to create a new history record or create a history list
for a particular pilgrim.
29
Creating a history record is a simple INSERT command in SQL language while getting a
historical record of a pilgrim’s locations can be initiated through a SELECT SQL
command.
SENSOR MANAGEMENT SYSTEM
The Sensor Management System is a simple system that adds or edits details of the
sensors in the database.
Design and Implementation
The Sensor System involves adding and/or editing SQL commands sent to the database
for processing. The System is not major, as once it lists all the sensors and their details, it
will be idle.
ACTORS AND FUNCTIONALITIES
Hospital Pilgrim Health Information System
Police Pilgrim History System
Pilgrim Identity Management System
Missing Pilgrim Information System
Saudi Embassy Pilgrim Immigration Information System
Travel Agency Pilgrim Immigration Information System
Maulim/Ameer Pilgrim History System
Pilgrim Identity Management System
Missing Pilgrim Information System
Ministry of Hajj Sensor Management
Pilgrim History System
Pilgrim Identity Management System
Pilgrim Immigration Information System
Missing Pilgrim Information System
CONCLUSION
The functionalities of this system have been made by determining the most immediate
needs of the actors, and there is room for improvement. The system is more than
capable of handling more complex functions and more research can determine what
kind of functionalities the system should keep and add in the future.
30
DATA WAREHOUSING & MINING OF HMIS
INTRODUCTION
Hajj Management Information System is primarily constructed as a database system that
will store a given pilgrims immigration, health, identity and location details. The
warehousing and the potential mining value of all this information are too valuable to
simply delete it all.
The Ministry of Hajj will be the main body responsible for accessing and processing this
information as it would be under their jurisdiction to do so.
DATA MINING BENEFITS
ACCOMMODATION & UTILITIES
The planning for the accommodation of all these pilgrims can be researched through the
mining of the data. This research would involve identifying pilgrim’s common needs and
habits, and identifying trends.
Data mining will help the Ministry of Hajj to provide better management over
accommodations and utility development. The Ministry can then make provisions, plans
and eventually build accommodations in accordance with the current and expected
trends; therefore saving un‐necessary costs if there are any.
TRANSPORTATION
The transportation of pilgrims can be analyzed to determine if more transportation
vehicles are needed, or a new transportation medium is required (for example, a high
speed railway). This could help with the many delays the pilgrims are subjected to
when traveling from Jeddah to Mecca.
ROUTE PLANNING
The analysis of foot‐traffic caused by pilgrims walking along the various roads and
streets would give vital information to organizers on how to avoid unnecessary traffic
congestion in the future.
The Ministry could also forward the information to the city government when they are
planning to build roads/highways.
PATTERN RECOGNITION
Crowding Pilgrims
Patterns can be formed as pilgrims start crowding around venues. These
patterns can then be used to manage the over‐crowding; providing a safer
experience for all participants.
Also, over‐crowding in general can be analyzed and tracked, providing
organizers will vital information about which events need the most attention
and supervision. This way, pilgrims can be allowed into specific venues in a slow,
steady pace, reducing the risk of pilgrim injury.
Lost Pilgrims
31
Patterns can be formed as to where the majority of pilgrims get lost. A graphical
display showing the lost pilgrim’s last movements would help organizers with
checkpoint positioning, signs, and even build landmarks around these locations
to help lost pilgrims find their way back.
GENERAL STATISTICS
Statistics will help the Ministry plan the overall flow of the Hajj. Issues such as how
many pilgrims from each country have arrived, can help the Ministry decide on future
rations to other countries.
General statistics can help the Ministry decide on how to serve the ever‐expanding
number of pilgrims as well, if projections are carried out.
DATA QUALITY ISSUES
The major data quality concern relates to the frequency of scans made by the sensors;
sensor will be turned on and off systematically every five minutes. This creates gaps in
the coverage of the pilgrims’ movements. This is the major quality issue that the Hajj
Ministry has to deal with. One possible work‐around to this problem could be to use the
data gathered from multiple Hajj’s and use the combined data to make analysis and to
draw conclusions.
CONCLUSION
The Data Warehousing and Mining of HMIS could provide Hajj organizers with valuable
information about traffic flows, over‐crowding, and more. Information can also be
gathered about where and how pilgrims get lost during their pilgrimage.
The capability and functions of HMIS can be multiplied if all that data is warehoused and
stored for analysis for several years. This would provide invaluable advice to the
Ministry of Hajj as to how to effectively manage the Hajj in its entirety.
32
CONCLUSION OF REPORT
The proposed system will operate by tracking an RFID Tag located on the body of all
pilgrims participating in the Hajj. These tags will be scanned by sensors strategically
positioned around all cities and events. If a pilgrim were to go missing, police,
organizers, or even family members, will be able to track the pilgrim’s location over the
internet.
The RFID Tags will also have built in data storage capabilities, which will be used to
store the personal details of that pilgrim. This information will include their pilgrim ID,
name, group manager, finger print, retina print, and more. If a pilgrim was to be killed
during their pilgrimage, and their body is unidentifiable, their details can be attained by
simply scanning their tag.
This report has presented an outline of the proposed system and how it should operate.
If an automated tracking system were to be implemented for the Hajj, this report can act
as the back bone for such a system.
BIBLIOGRAPHY OF REPORT
http://en.wikipedia.org/wiki/Hajj , Wikipedia Link to Hajj article
Articles in Database Systems Site:
• Main Activities of Hajj
• A framework for improved hajj management and future research,
Mohammad Yamin, 2006
• Hajj Case Study, Pages:44
• Hajj Management System, Fariza Israfil, Uzma Yamin, John Ashcroft, An Do,
Osama AlKadi
• Database_RFID_Interface, University of Canberra/ Information Sciences
Extension Studies
33