You are on page 1of 21

Identifying the Extended Role of

IT Infrastructure in
Optimizing Operational Procedures of
RESCUE 1122
Proposed Network Enhancement Plan
Advanced Enterprise Network
Second Semester
MSc Telecom Networks

Homaira Arif

2013-MS-TN-01

Nada Fahim

2013-MS-TN-31

Noreen Anwer 2013-MS-TN-34


Madiha Ikram 2013-MS-TN-56

Contents
Main Scope: ............................................................................................................................................................................ 3
Mission Statement of Rescue 1122 ......................................................................................................................................... 3
Identifying Business Goals ..................................................................................................................................................... 3
Identifying Technical Goals .................................................................................................................................................... 3
Characterizing Existing Network ............................................................................................................................................ 4
Identifying Customers Existing Network Applications: ........................................................................................................ 4
Existing Limitations and Proposed Solutions ......................................................................................................................... 5
Proposed Network Overview and Connectivity Diagram ....................................................................................................... 7
Logical Network Topology ..................................................................................................................................................... 7
Overview of Proposed Network .............................................................................................................................................. 8
Detailed Network Architecture ............................................................................................................................................. 11
User Communities ................................................................................................................................................................ 12
Data Stores and Servers ........................................................................................................................................................ 16
Proposed Applications .......................................................................................................................................................... 16
Annexures ............................................................................................................................................................................. 17
Calculation of number dial-in circuits required for 1122 calls ............................................................................................. 18
Abbreviations ........................................................................................................................................................................ 20
References: ............................................................................................................................................................................ 21

Main Scope:
Mission Statement of Rescue 1122
Development of safer communities through establishment of an effective system for emergency preparedness,
response and prevention
Our main focus in this document is to enhance existing IT infrastructure in order to optimize operational performance of
RESCUE 1122 with a focus on streamlining mission critical communications and reducing the end-to-end response time
(the Golden Hour).

Identifying Business Goals


1. Rescue 1122 network is legally bound under Punjab Emergency Services Act 2006
2. Other legal documents governing the SOPs include:
a. Punjab Emergency Service Leave, Efficiency and Discipline Rules 2007
b. Punjab Emergency Service Financial Rules 2007
c. Code of Conduct
d. Shifting Protocols and Standard Operational Procedures documented under law.
3. Most of the software applications are considered to be Mission Critical Operations:
a. Zero downtime tolerance
b. High availability networks
4. One main goal is to increase efficiency and facilitate the over-worked staff through IT infrastructure support
5. Having expanded to 36 districts in Punjab, the network should be able to further devolve to Tehsil level if required.
6. Coordination with PTCL and cellular mobile operators for A-number location information and Cell Broadcast
Systems under auspices of PTA .
7. Network Integration & simple, single reporting formats
8. Resolve existing limitations
9. Ensure after sales support, security and robustness of deployed equipment

Identifying Technical Goals


1. Developing a secure WAN environment between the Provincial and district level offices
2. WAN should be expandable to Tehsil level
3. Secure access to web for TPL, Hospital Management System Website and other GPS tracking applications (e.g.
IntelMap)
4. Dial in services (1122) with high availability and alternate routing. Toll free short code should be accessible
from all networks as an emergency number
5. Resolve existing limitations through new applications, and upgrading existing applications
6. Wireless communication network should allow caller ID and call records DB.
3

7. The CMS and EMS DBs should contain a linking parameter with Wireless set ID
8. Develop an Emergency Record Management online and automated infrastructure to handle Emergency Call and
Response Forms (ECF, ERF).
9. Integrate CMS with an ALI database for Mobiles & Landlines
10. Fleet Tracking System to be enhanced
11. Mission Critical operations should have the five 9s Availability but with a trade-off between affordability due to
limitations of Govt. funds
12. Overall network integration and database synchronization.
13. Scalability should be ensured to double the size in 3 years- may go to Tehsil level deployment
14. Disaster Recovery procedures & security risks identification

Characterizing Existing Network


Existing IT infrastructure of Rescue 1122 consists of localized LAN environments in each of the following:
1. Provincial Monitoring Center
2. District Control Rooms (36 districts)
The LANs are not connected through a full-scale WAN deployment. Instead VPN connectivity through ISPs is
available only for certain applications and access to Internet is provided in above-mentioned locations.
Correspondence between control rooms and PMC is through email. Most of the applications are localized e.g.
CMS is an autonomous software in each district managing and logging calls per district. However, all the call
logs are uploaded every evening to PMC using Internet.
IP traffic is mostly limited to LAN. Main traffic flows to consider for existing network are:
1. Calls to 1122
2. Wireless communication.

Identifying Customers Existing Network Applications:


1.
2.
3.
4.
5.

IDS - Call Management System with audio files storage


Wireless Communication Network with audio files storage
Fleet Tracking System C-track Maxx and Star track (TPL)
Emergency Dispatch software (for punching in ECF and ERF) being done as a backup of paper procedure only.
IP based Surveillance Cameras in control rooms and PMC using VoIP over WAN for real-time communications
only at the time of need as an alternate to wireless. They have local storage on site.
6. Email through Internet (Gmail) and Print services
7. Internet access (ISPs)
The applications 1 to 3 require five 9s availability, whereas the remaining applications are network outage tolerant for up
to 24 hours.

Existing Limitations and Proposed Solutions


Sr. No
1.

Problem
Unavailability of Information about caller
location for Dispatch of emergency vehicle

2.

Alternative to landline in case of power


outage

3.

Emergency calls received on IDS are not


mapped to the Dispatched Ambulance ID so
follow-up and back-tracking is not possible

Proposed Solution
Implementation through PTA
Directory Information Server for PTCL
and other landline numbers
ALI database for mobile / cellular
networks
Street map software suggested in 6. Below
shall also help once ambulance has been
dispatched
PTCL should allow alternate routes to any other
nearest Control Room CMS e.g. for Kasur PTCL
could route calls to Lahore Control Room if the
Kasur CR is inaccessible. The CMS servers of all
control rooms shall also be connected over IP via
PMC. This shall help in forwarding to respective
CTWOs in the correct control room even if call is
received in some other nearby CR. (fig. 3)
Each valid call logged on the CMS may be
forwarded to Emergency Management System.
EMS shall create an ECF & forward to
corresponding WO who after ascertaining the
ambulance in respective area, calls the EMT on
wireless and dispatches unfilled ECF to the
corresponding EMTs notebook. EMT shall then
fill in patients details online and send it back to
WO. EMT is then free to handle the emergency,
5

4.

Traffic congestion impedes the movement


of ambulance destined towards disaster site

5.

Identifying the locations of humans under


the debris to evacuate them
Location of emergency site is often difficult
to find without updated area maps as if may
not be clearly stated by the victim.

6.

7.

Once patient is handed over to the hospital,


the location and current state of patient
should be accessible to patient attendants.

8.

For provision of effective emergency &


better post-handover care to the patient,
awareness about the current load and
available bedding of public sector hospitals
is desired
Currently manual process for ECF & ERF is
employed and personnel have to enter on
paper as well as computers
Monitoring of CTWOs alertness

9.
10.

11.

To improve response time facilitate the


digitalization of emergency call activity

12.

Improve end to end response time by


employing other approaches to reach site
even during traffic blockades
Ambulance movement in case of traffic
congestion becomes very difficult
Uploading of emergency site pictures to
PMC or CR for guidelines and further task
assignment

13.
14.

while WO locates available hospitals in vicinity,


checks their status through web information
(problem 7) and contacts focal person on
wireless. Based on availability of resources in the
hospital, the WO forwards ECF online to the
focal person to prepare for patient
Rescue 1122 authorized personnel in PMC
should have access Cell Broadcast Service and
traffic police information
Cell Broadcast System & vibration sensors for
detection under debris
GPS tracking and street maps softwares (we
could use the notebooks/ tabs provided for EMS
as well as GPS tracking application (e.g.
Tomotom)
This may be done through EMS. As soon as
patient is handed over by focal person in hospital
and the ECF and ERF are closed with
information of Hospital ID. This information
may be accessible on a web page and may be
maintained for upto 48 hours.
Hospitals should be encouraged to maintain an
updated information databases with basic
information available on website by using
Hospital management software. Focal persons at
hospital should have access to this information.
Emergency Management Software with online
ECF entry and dispatch is proposed
CMS call answer and response statistics should
be monitored. Automatic alerts may be generated
to the Shift and CRI using Buzzers on the
terminal to identify the CTWO based on delay in
call answering or dispatch
Since ECF entry has been enabled in field
through simple drop-down menu selection on
notebook computers, with automatic forwarding.
This shall facilitate duplicated effort at all levels.
Student scribes may also be enlisted over web.
Rescue on bikes with MMS enabled phones

Intelligent Traffic System using Blue lights


displays the direction of ingress ambulance
These pictures may be sent as attachments to
ECF on the Emergency Management System
application on the Edge/GPRS modem notebooks

Proposed Network Overview and Connectivity Diagram


The enhanced Rescue 1122 logical architecture is based on a partial mesh Hierarchical design with three hierarchical
layers based on their functional authority:
1.
2.
3.
4.

Provincial HQ
Main Districts
Smaller districts
Stations

Since the connectivity requirements do not require heavy bandwidths, secure VPN connections over MPLS may be leased
from ISPs for the interconnectivity as shown in the logical topology (fig. 1) below:

Logical Network Topology

WAN

District Control
Room

Inernet

Partner Site
(PTA/PTCL)

Management
WAN Edge

Dial In/ Wireless


Services

PMC
Core

Internet Edge

Emergency field
Worker

Data Center

Fleet Tracking

High Level view of Rescue 1122 Functional Diagram

Overview of Proposed Network


Existing network shall be integrated and applications enhanced as follows:
1. WAN topology shall be based on secure VPN redundant links of capacities:
a. PMC to districts Two 2Mbps links
b. PMC Internet Access 10Mbps
c. Between District CRs as alternate path over IP one 2Mbps link
d. District CR to Internet Access 4Mbps
2. New / Enhanced Applications
a. Enhanced Call Management Platform This application is enhanced to include automatic forwarding
and Dispatch functions. Its DB shall be linked to EMS through same primary key. The CMS is also
queries Automated Locations Information database (PTA provided access) which provides updated
location information of calling numbers. The Call Management Servers in control rooms are linked
together over IP to allow forwarding of calls to various CTWOs in case of failure of PTCL landline in one
city. Please refer to figure 1 on next page.
It can be seen that PTCL allows alternate routes to any other nearby CR (which Rescue 1122 management
may specify) in case main route is down. The CMS checks that the calls are from A-party numbers of
Kasur, so it forwards the call over IP to CMS server Kasur.

Rescue
1122 calls

PTCL allows alternate path to


Lahore numbers when Kasur
lines are down
CMS Kasur
PTCL/NTC
number

GSM
Number
CTWOs Kasur
PTCL/NTC
number

CMS

WAN cloud

IP WAN
connectivity

Calls are routed to CTWOs Kasur from


CMS server Lahore to CMS server
Kasur over IP

GSM
Number

CTWOs Lahore

Fig.1 Alternate routing and call handling options for 1122 Calls
b. Emergency Management System (EMS) This is a new application built upon existing ECF and ERF
logging software with secure web access through dedicated port (https and uses any other custom port
instead of port no. 443 used for https) and SSL logins. The users of this system include:
i. CTWO
ii. WO
iii. Emergency vehicle staff ( using Edge/GPRS modem enabled notebooks)
iv. Focal Person in Hospitals (using notebooks with 3G dongle or Edge / GPRS modem for Internet
access.)
The Personnel may open and fill in online forms. Printing and forwarding options should be available.
The user may send emergency site pictures as attachment of ECF form. The EMS shall be linked to CMS
such that any valid call will generate a record (ECF record) in EMS when CTWO presses the forward to
EMS option in CMS. This may also contain a compulsory entry field Wireless ID or Ambulance
number which should be entered by the WO when he receives this valid EMS record and forwards to
corresponding EMT or Focal hospital person.

A sample EMS system is shown below

Fig: Emergency Call Management System Dashboard sample


c. IP surveillance Network This is an existing application connected with IP cameras in all the Control
rooms. It may be enhanced to link the ambulances through the notebook computers installed there
d. Scrum task scheduler application can also be deployed on the EMS servers

e.

Fleet tracking software existing application set up shall be continued in enhanced proposed set up as
well

10

Detailed Network Architecture


PTAs ALI
DataBase
ALI Server

WAN
ALI DB

Internet
VPN
Connectivity

Tablets

GPRS/3G
network

IP
camera

Audio Visual
Surveillance
Server

Switch

Wireless Control
System

Emergency
Management System/
Scrum Task
Scheduler

Ambulance

BSC

Other Districts CR
Lahore District CR

Rescue
1122

CMS
PTCL/NTC
number

Primary District
CR

AVC Stations
with Headphone

Surveillance
system
LCD Monitoring

GSM
Number
Control Room
Backup Data store

PMC

Wireless control
system

BSC

Proposed Detailed Architecture of


Rescue 1122

Control Room

11

User Communities
Community
Name

Size of Community

Location

Applications Used

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Lahore

CMS

Emergency Officers,
CRIs and SI's

46

Lahore

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, Scrum based Task schedulers, IntelMap fleet monitoring,
Emergency Management System

CTWOs, WOs

107

Lahore

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

Higher Management

10

Lahore

CMS , Email, Wireless Comm. Network, IP surveillance Cameras,


IntelMap fleet monitoring, Emergency Management System

EMTs and Emergency


vehicle officers

445

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Rawalpindi

CMS

Emergency Officers,
CRIs and SIs

24

Rawalpindi

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

56

Rawalpindi

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

233

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Faisalabad

CMS

Emergency Officers,
CRIs and SIs

23

Faisalabad

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

54

Faisalabad

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

226

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Multan

CMS

12

Emergency Officers,
CRIs and Sis

24

Multan

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

55

Multan

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

227

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Gujranwala

CMS

Emergency Officers,
CRIs and Sis

19

Gujranwala

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

45

Gujranwala

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

185

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Bahawalpur

CMS

Emergency Officers,
CRIs and Sis

15

Bahawalpur

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

34

Bahawalpur

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

140

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Sargodha

CMS

Emergency Officers,
CRIs and Sis

13

Sargodha

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

31

Sargodha

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

128

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

13

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

D.G.Khan

CMS

Emergency Officers,
CRIs and Sis

15

D.G.Khan

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

35

D.G.Khan

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

146

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Sahiwal

CMS

Emergency Officers,
CRIs and Sis

Sahiwal

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

20

Sahiwal

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

82

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Sialkot

CMS

Emergency Officers,
CRIs and Sis

15

Sialkot

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

34

Sialkot

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

140

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

14

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Rahim Yar Khan

CMS

Emergency Officers,
CRIs and Sis

Rahim Yar Khan

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

18

Rahim Yar Khan

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

75

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

Murree

CMS

Emergency Officers,
CRIs and Sis

10

Murree

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

24

Murree

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

99

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

Emergency callers (calls


to 1122)

Unlimited (can be anyone from public in


the area). Traffic calculated in Annexure
A

other Districts

CMS

Emergency Officers,
CRIs and Sis

other Districts

CMS , Email, Printer, Wireless Comm. Network, IP surveillance


Cameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs

12

other Districts

CMS , Email, Wireless Comm. Network, Fleet Tracking software,


Emergency Management System

EMTs and Emergency


vehicle staff

51

various locations
within district

Wireless Comm. network, Fleet Tracking software, Emergency


Record Management System

15

Data Stores and Servers


Data Store

Location

Call Management System server


with Audio logs and reports
PMC , CR
IP surveillance video logs
PMC , CR
Network Management Server
and DB
PMC , CR
Wireless Control Server with
Audio DBs

PMC , CR

Emergency Management Server


with ECF and ERF records
PMC , CR

Print and Web servers

PMC , CR

Fleet tracking and IntelMap


servers with LCDs
Backup stores for all Data

PMC , CR
PMC

Application

Used by

Call Management System, CMS


reports and logs
IP surveillance control
Network and Equipment
Monitoring

Remarks

CRI, SI, CTWO and WO and


Higher Management
Higher management in PMC if may refer to reporting
required
dashboards
CRI, SI and security staff

CTWO
CRI, SI, CTWO and WO and
Higher management in PMC if
Wireless Communication Network required
CRI, SI, CTWO and WO and
Higher management in PMC if
EMS
required
CRI, SI, CTWO and WO and
Higher management in PMC if
Internet, Printer sharing
required
CRI, SI, CTWO and WO and
Corresponding web page display Higher management in PMC if
on large screen
required
Backup logs
CTWO

Higher Management
may refer to reporting
dashboards
Higher Management
may refer to reporting
dashboards

Proposed Applications
Name of Applications
Dial-in Access to Call
Management System
CMS & Dispatch
Emergency Record
Manage Software

Type of Traffic Flow

Protocols

User Community

Circuit Switched
Client/Server

ISDN/ISUP
Https over TCP/IP

Client/Server

Https over TCP/IP

IP Surveillance Cameras

Peer-to-Peer

VoIP over WAN

NMS

SNMP

ALI

Client/Server
Dedicated Circuit
switched signaling

Emergency callers (1122) CMS


CTWO, WO
CMS
EMT, Focal person,
CTWO and WO
EMS
IP surveillance
CRI and SI
video logs
monitoring and
CTWO, WO
alarm logs
ALI DB on PTA
Connected to CMS
cloud

Wireless Control

Wireless PTT, half-duplex


(one-way)
WiFi or WiMax

SCCP over MTP layer 3

Field personnel

Data Stores

Wireless Audio
and CDRs

Application
BandWidth

QOS

E1 / ISDN PRI
100kbps

Constant Bit rate


nrt-VBR

500kbps
500kbps

nrt-VBR, images
real-time VBR without
delays or jitter

100kbps

nrt-VBR

128kbps
half-duplex voice
(12.2 kbps AMR
Codec)

Constant Bit rate

constant bit rate

16

Annexures

Assumptions : Since exact figures of human and IT resources were not available, extrapolation has been done based on
statistics contained in The Rescue 1122 five year performance report (ref: www.rescue.gov.pk )

17

District
Lahore
Rawalpindi
Faisalabad
Multan
Gujranawala
Bahawalpur
Sargodha
D.G.khan
Sahiwal
Sialkot
Rahim Yar Khan
Murree
Jhang
Khanewal
Rajanpur
Muzafarghar
Gujrat
Bahawalnagar
Attock
Jehlum
Toba Tek Singh
Pakpattan
Mianwali
Kasur
Vehari
Chakwal
Okara
Hafizabad
Sheikhupura
Lodhran
Nankana Sahib
Khushab
MBDin
Narowal
Layyah
Bhakkar
Chiniot
Total

Rescue Drivers

DERT
383
202
195
196
160
121
111
127
72
121
64
86
44
31
31
44
31
31
31
31
31
31
44
21
31
31
31
21
31
31
21
31
21
21
31
21
21

EMT
77
40
39
39
32
24
22
25
14
24
13
17
9
6
6
9
6
6
6
6
6
6
9
4
6
6
6
4
6
6
4
6
4
4
6
4
4

291
153
148
149
121
92
84
96
54
92
49
65
33
24
24
33
24
24
24
24
24
24
33
16
24
24
24
16
24
24
16
24
16
16
24
16
16

Lead Fire
Fire Rescuers Rescuers
367
193
187
188
153
116
106
121
69
116
61
82
42
30
30
42
30
30
30
30
30
30
42
20
30
30
30
20
30
30
20
30
20
20
30
20
20

77
40
39
39
32
24
22
25
14
24
13
17
9
6
6
9
6
6
6
6
6
6
9
4
6
6
6
4
6
6
4
6
4
4
6
4
4

CTWO/WO Emergency Officers Support staff Total


107
46
184
56
24
97
54
23
93
55
24
94
45
19
77
34
15
58
31
13
53
35
15
61
20
9
34
34
15
58
18
8
31
24
10
41
12
5
21
9
4
15
9
4
15
12
5
21
9
4
15
9
4
15
9
4
15
9
4
15
9
4
15
9
4
15
12
5
21
6
3
10
9
4
15
9
4
15
9
4
15
6
3
10
9
4
15
9
4
15
6
3
10
9
4
15
6
3
10
6
3
10
9
4
15
6
3
10
6
3
10

1532
805
778
784
639
484
442
505
286
484
257
342
175
125
125
175
125
125
125
125
125
125
175
84
125
125
125
84
125
125
84
125
84
84
125
84
84

Calculation of number dial-in circuits required for 1122 calls

Consolidated Report of Emergency Calls and Rescue Operations In Punjab


From 10/10/2004 To 14/12/2013
District

Total Call

Average
erlangs

No. of
circuits

Calls per day

13,041,718

12.4065

16

3,573.07

Rawalpindi

3,073,524

2.923824

842.06

Faisalabad

5,231,691

4.976875

1,433.34

Multan

3,599,258

3.423952

986.10

Gujranawala

4,321,101

4.110636

1,183.86

Bahawalpur

2,671,775

2.541643

731.99

Sargodha

2,402,286

2.28528

658.16

D.G.khan

2,736,344

2.603067

749.68

Sahiwal

1,991,945

1.894925

545.74

Lahore

18

Sialkot

3,246,586

3.088457

889.48

Rahim Yar Khan

4,508,018

4.288449

1,235.07

953,072

0.906651

261.12

1,164,994

1.108252

319.18

Khanewal

703,119

0.668873

192.64

Rajanpur

1,052,386

1.001128

288.32

Muzafarghar

800,420

0.761435

219.29

Gujrat

768,547

0.731114

210.56

Bahawalnagar

521,332

0.49594

142.83

Attock

299,078

0.284511

81.94

Jehlum

631,250

0.600504

172.95

Toba Tek Singh

620,454

0.590234

169.99

Pakpattan

369,584

0.351583

101.26

Mianwali

432,998

0.411908

118.63

Kasur

577,935

0.549786

158.34

Vehari

206,993

0.196911

56.71

Chakwal

605,456

0.575967

165.88

Okara

393,393

0.374232

107.78

Hafizabad

374,289

0.356059

102.54

Sheikhupura

988,206

0.940074

270.74

Lodhran

605,667

0.576167

165.94

Nankana Sahib

330,587

0.314485

90.57

Khushab

137,333

0.130644

37.63

MBDin

337,172

0.32075

92.38

Narowal

381,193

0.362627

104.44

Layyah

343,055

0.326346

93.99

Bhakkar

246,895

0.23487

67.64

Chiniot

114,724

0.109136

31.43

Murree
Jhang

19

Emergency Vehicles
District

Stations

Lahore
Rawalpindi
Faisalabad
Multan
Gujranawala
Bahawalpur
Sargodha
D.G.khan
Sahiwal
Sialkot
Rahim Yar Khan
Murree
Jhang
Khanewal
Rajanpur
Muzafarghar
Gujrat
Bahawalnagar
Attock
Jehlum
Toba Tek Singh
Pakpattan
Mianwali
Kasur
Vehari
Chakwal
Okara
Hafizabad
Sheikhupura
Lodhran
Nankana Sahib
Khushab
MBDin
Narowal
Layyah
Bhakkar
Chiniot

Emergency
Ambulances

8
5
4
4
4
2
2
2
1
1
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

Fire
Trucks

27
14
12
12
12
8
8
8
4
4
7
7
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4

Rescue
Vehicles

20
12
10
10
10
6
6
6
2
2
6
3
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2

Water
Bowsers

4
3
2
2
2
2
1
1
1
1
1
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

2
2
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

Water
Rescue
Vehicles

1
1
1
1
1
0
1
0
0
0
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Recovery
Vehicles

3
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

Turntable
Ladders

2
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Aerial
Platforms

2
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Abbreviations

SOP

Standard Operating Procedures

PTA

Pakistan telecommunication Authority

PTCL

Pakistan telecommunication Company Limited

WAN

Wide Area Network

GPS

Global Positioning System


20

CMS

Call Management System

EMS

Emergency Management System

ID

Identification

DB

Database

LAN

Local Area Network

ECF

Emergency Call Form

ERF

Emergency Response Form

ALI

Automatic Location Information

VPN

Virtual Private Network

ISP

Internet Service Provider

PMC

Provincial Monitoring Center

CR

Control Room

CRI

Control Room Incharge

SI

Shift Incharge

VoIP

Voice over IP

CTWO Computer Wireless Operator


WO

Wireless Operator

EMT
GPRS

Emergency Medical Technician


General Packet Radio Service (data over cellular
mobile)

MMS

Multimedia Service

GSM

Global System for Mobile

NTC

National Telecommunication Corporation

BSC

Base Station Controller

References:
1. Rescue 1122 website www.rescue.gov.pk
2. Identifying the extended role of IT infrastructure in optimizing operational procedures of Rescue 1122,
By Dr. Ali Hammad Akbar
3. 911 services FCC, USA - http://transition.fcc.gov/pshs/services/911-services/Welcome.html
4. Fire and Emergency Services Solutions, Motorola, http://www.motorolasolutions.com/USEN/Business+Solutions/Industry+Solutions/Government/Fire+and+Emergency+Services
21