The document proposes an Emergency Control System to better allocate ambulance resources in response to accidents. It includes three subsystems: 1) accident data provided to appropriate users, 2) a map graphically showing accident, hospital and ambulance locations using GIS, and 3) data exchange ability. The system uses a web interface for mobility and automation to reduce complexity and improve usability. It will store accident data, control ambulance districts via maps indicating locations, and link districts and ambulances to efficiently respond to incidents. The proposal outlines user requirements, system models, and a timeline for implementing the GIS-based emergency response coordination system within 12 weeks at an estimated cost of $850.

1. 1
E.C.S
Emergency Control
System
Prepared by:
Ahmad Mohsen Nassar

2. 2
Index
Introduction
User Requirement
Entity Relationship Diagram (ERD)
Context Model
Sequence Diagram
Use Case
System Requirements
System Model (Object Model)
Security
Plan and Required Timeline
Summary

3. 3
Introduction
most accidents go unreported and poorly handled mainly because the current system
that doesn't provide the ability to provide quick and rapid response
The new system is created for the purpose of aiding health care organizations by best
allocating recourses being that of human and mechanical.
Three interconnected subsystems that provide accident data to its suitable users, a
map that graphically illustrates accident, hospital and ambulance locations (GIS)
and data exchange ability.
The system uses web interface to provide mobility and accessibility to its users.
There are automated processes that that reduce the complexity of the system and be a
user friendly implement.
The system uses many tools (PHP, AJAX, etc) to achieve a minimum response time
and maximum efficiency.

4. 4
User Requirements
A- Functional requirements:
Control of all ambulances by its respective district and the knowledge of its location via GIS system
Dividing the map into districts of which will have its dedicated ambulances.
The control center should determine hotspots where accidents often occur.
A link to transfer accident data between the Control Center and district and between the district and
Ambulance for accident / patient /ambulance data.
Using GIS reference for the accident location, Ambulance and Hospital on the map.
Storing the accidents in a database and an alert for recently added ones.

5. 5
User Requirements(Cont.)
B- Non Functional requirements:
The control center operator delivers accident data to district within 20 seconds.
The control center operator has a birds eye view of all ambulances with their ID numbers, if it busy or
vacant, their fuel quantity and supply rate.
The district operator see the locations of all hospitals.
The district operator assigns the nearest ambulance assigned to each district to the accident within 20
seconds.
The ambulance should report the control operator that the accident delivery is completed.
The control operator sees the recent accident in a highlighted different color.
When the accident reporting and delivery is completed, the marker will disappear automatically.
Severity of the accident is shown via marker KPI (red, yellow, green)
The system should be robust in inserting and updating cases.
The control center dashboard should display each district with a KPI (red more than 100 incidents / day,
yellow from 99 -15 i/day , green less than 15 i/day) indicating the frequency of incidents / day

6. 6

7. 7
• Context Model

8. 8
• Sequence Diagram

9. 9
• Use Case

10. 10
System Requirements
A- Functional requirements:
1-Control Center:
New Accident
Create accident marker on the map and gather all required data needed by district to assign an ambulance.
Query Browser
A dedicated database browser for the control center admin to browse certain fields for data retrievals.
Completed report
Returns the completed accidents and displays them for the control center operator.
2-district:
Receive accident report
Receive accident data and marker from control center.
Assign ambulance
Automatically or manually assign an ambulance to selected accident in (relation to location, fuel and medical supply) to nearest relative hospital.
Add ambulance
When a new ambulance is received it is added to the database.
Add patient
Enter patient data provided by ambulance via arrival.
Complete accident
Alter status of specified accident to that of completed announcing successful delivery to the hospital.
Edit assigned ambulance
Change the assigned ambulance in case of request denial
Ambulance:
Receive accident request
Receive and display assigned accident marker on the map and it’s area.
Request reply
Reply to district with a confirmation or deny to the assigned accident.

11. 11
System Requirements(Cont.)
B- Non Functional requirements:
System has to have 4 interfaces one for each of the Control Center, district, Ambulance and Hospital
A Google map with controls should be provided for the interfaces of the Control Center, district and Ambulance.
All interfaces should be provided with their own JavaScript engine.
All JavaScript engines should be hooked with the database via PHP.
Data retrieved from the database should be refreshed asynchronously to server.
Data sent should be uploaded to the database asynchronously to the database.
All users of the system should have approval thus a login gate should be enforced at the beginning of the page

12. 12
• System Model (Object
Model)

13. 13
Security
Security is critical in almost any technology-driven industry which operates on computer systems. The issues of computer based systems
and addressing their countless vulnerabilities are an integral part of maintaining an operational industry.
That is why the ECS system has to maintain a level of security given that it is a critical system. The areas in which security measures were
implemented include:
• The login page:
by entering a password the system logs to the server database(the access table) and compares it to the one entered by the user and if the
password matches any of that are in the database user number and department are retrieved then saved in a client side xml or the
domain xml. If the retrieved department matches that of the loaded page the user is granted access and his number is displayed in
the user number field, Else if any violation occurs the user is left with an unloaded webpage.
• PHP files:
Although they have the database name and password are saved in it they are safe as when they are called on by a function the only
outcome the server provides is the echo which doesn’t contain any critical information.
• JavaScript file:
as many browsers have ability to view source so as a response to such a threat some vital functions were compressed and Base62 encoded
(it refers to a specific Multipurpose Internet Mail Extensions content transfer encoding. It is also used as a generic term for any
similar encoding scheme that encodes binary data by treating it numerically and translating it into a base 64 representation. The
particular choice of base is due to the history of character set encoding: one can choose 64 characters that are both part of the
subset common to most encodings, and also printable. This combination leaves the data unlikely to be modified in transit through
systems, such as email, which were traditionally not 8-bit clean)
• Administrative areas:
Web Pages as the query browser require the user to be a database administrator in order to access it, all other users don’t have that
privilege.

14. 14
implementation
Using Google map API to show the GIS application and php for the Database application
• Query Browser:

15. 15
•Control Center Window:

16. 16
•district Window:

17. 17
•Ambulance Window:

18. 18
•Hospital Window:

19. 19
• 1- USB GPS Dongle
• Specs:
• GT-730F from Canmore of Taiwan is a simple USB GPS dongle.
• It is capable of tracking 54 satellites simultaneously and with signal
detection at only -159dBm it is quite sensitive. The GT-730F is optimized
for good performance and low cost. Its 54 parallel channels and Venus 5
search bins provide short start-up time and fast signal acquisition. Having
fast time-to-first-fix and high sensitivity, the GT-730 offers good navigation
performance even in urban canyons.
• Hardware

20. 20
• Minimum specs: Recommended specs:
P3 processor Centrino Dual Core 2 processor
512 SD ram 1G DDR 2 ram
Windows XP operating system Windows XP/Vista operating system
IE6 IE7
2- A laptop.
3-USB HSDPA Modem (High-Speed Downlink Packet Access)
Technically it is a modem, USB and (due to the CDFS format) virtual CD-ROM device.
Launched on 21 June 2006, the device is used for wireless Internet access using
3.5G,3G, or 2G mobile telephony networks. It supports UMTS (including HSDPA),
EDGE, GPRS and GSM.
Most 3G network operators bundle the device with a contract, with some operators
simlocking the device . Unlocked and unbranded modems can also be bought from
independent suppliers.

21. 21
Alternative Components:
Panasonic Toughbook 30 Laptop
Specs:
Out in the field or down in the dirt, the durable Panasonic Toughbook 30 notebook is built to
take a beating. MIL-STD-810F-tested for ruggedness, this brawny workhorse is encased in
magnesium alloy, with durability designed into every seal, hinge and connector. Plus, as
the industry's fastest fully-rugged mobile PC, it's built for lightening-quick processing and
wireless connectivity. Communicate in real time from remote areas, access databases
online and run sophisticated software applications even in the harshest environments.
Processor: Intel Core Duo L2400 1.66GHz
Bus Speed: 667MHz
Cache: 2MB L2 Cache
Chipset: Intel 945GM
Standard Memory: 1GB
Maximum Memory: 4GB
Memory Technology: DDR2
Network: GPS
Modem: Yes

22. 22
Estimated Cost:-
Type Price
GPS
dongle
$100
Laptop $500
USB
Modem
$250
Total $850
Type Price
Panasonic
Toughbook
$4167.99
Total $4167.99
• 1st set • 2nd set

23. 23
Plan & Timeline
Implementation Plan:
Preparing the dataset and spacial views
Implementation the GIS server for the application
Launch of the GIS server
Creation of the dashboard
Configuration and preperation
Testing and validation
Preparing the dataset and
spacial views
Implementation
the GIS server
for the
application
Launch of the
GIS server
Creation of the
dashboard
Configuration
and
preperation
Testing and
validation
Delivery
1-2 weeks 2 weeks 1 week 4 weeks 1 week 1 week Done

24. 24
Future Plans:
Log book to track entries and activities of all operators
Calculate route and display it on map.
Real time traffic data.
Implementation with fire and police department for full emergency system integration.

25. 25
Summary
Finally this system although is not perfected we hope it will be a step in
the milestone of success, as it will introduce the vast and ever
changing field of the computer systems. ECS will ensure a that the
basic standard will be met and from there the upgrading and
improvements will go on. Hopefully we wish that this system will be
met with acceptance and embraced by people in the field .Last but not
least what we really expect is that system will save valuable life for
everything could be replaced except for the loss of a soul.
Thank you