Rescue 1122 Report by Homaira Arif

8/9/2019 Rescue 1122 Report by Homaira Arif

1/21

1

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


2/21

2

Contents

Main Scope: ............................................................................................................................................................................ 3

Mission Statement of Rescue 1122 ......................................................................................................................................... 3

Identifying Business Goals ..................................................................................................................................................... 3

Identifying Technical Goals .................................................................................................................................................... 3

Characterizing Existing Network ............................................................................................................................................ 4

Identifying Customer’s 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


3/21


4/21

4

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 Customer’s Existing Network Applications:

1.

IDS - Call Management System with audio files storage

2. Wireless Communication Network with audio files storage

3.

Fleet Tracking System – C-track Maxx and Star track (TPL)

4.

Emergency Dispatch software (for punching in ECF and ERF) being done as a backup of paper procedure only.

5.

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.


5/21

5

Existing Limitations and Proposed Solutions

Sr. No Problem Proposed Solution

1. Unavailability of Information about callerlocation for Dispatch of emergency vehicle

Implementation through PTA

Directory Information Server for PTCL

and other landline numbers

ALI database for mobile / cellularnetworks

Street map software suggested in 6. Belowshall also help once ambulance has beendispatched

2. Alternative to landline in case of power

outage

PTCL should allow alternate routes to any other

nearest Control Room CMS e.g. for Kasur PTCLcould route calls to Lahore Control Room if theKasur CR is inaccessible. The CMS servers of all

control rooms shall also be connected over IP viaPMC. 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)3. Emergency calls received on IDS are notmapped to the Dispatched Ambulance ID so

follow-up and back-tracking is not possible

Each valid call logged on the CMS may beforwarded to Emergency Management System.

EMS shall create an ECF & forward tocorresponding WO who after ascertaining theambulance in respective area, calls the EMT on

wireless and dispatches unfilled ECF to thecorresponding EMT’s notebook. EMT shall then

fill in patients details online and send it back toWO. EMT is then free to handle the emergency,


6/21

6

while WO locates available hospitals in vicinity,

checks their status through web information(problem 7) and contacts focal person onwireless. Based on availability of resources in the

hospital, the WO forwards ECF online to thefocal person to prepare for patient

4. Traffic congestion impedes the movementof ambulance destined towards disaster site

Rescue 1122 authorized personnel in PMCshould have access Cell Broadcast Service andtraffic police information

5. Identifying the locations of humans underthe debris to evacuate them

Cell Broadcast System & vibration sensors fordetection under debris

6. Location of emergency site is often difficult

to find without updated area maps as if maynot be clearly stated by the victim.

GPS tracking and street maps softwares (we

could use the notebooks/ tabs provided for EMSas well as GPS tracking application (e.g.Tomotom)

7. Once patient is handed over to the hospital,the location and current state of patient

should be accessible to patient attendants.

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 withinformation of Hospital ID. This information

may be accessible on a web page and may bemaintained for upto 48 hours.

8. For provision of effective emergency & better post-handover care to the patient,awareness about the current load andavailable bedding of public sector hospitalsis desired

Hospitals should be encouraged to maintain anupdated information databases with basicinformation available on website by usingHospital management software. Focal persons athospital should have access to this information.

9.Currently manual process for ECF & ERF isemployed and personnel have to enter on

paper as well as computers

Emergency Management Software with onlineECF entry and dispatch is proposed

10. Monitoring of CTWOs alertness CMS call answer and response statistics should be monitored. Automatic alerts may be generatedto the Shift and CRI using Buzzers on theterminal to identify the CTWO based on delay in

call answering or dispatch

11. To improve response time facilitate the

digitalization of emergency call activity

Since ECF entry has been enabled in field

through simple drop-down menu selection onnotebook computers, with automatic forwarding.

This shall facilitate duplicated effort at all levels.Student scribes may also be enlisted over web.

12. Improve end to end response time byemploying other approaches to reach siteeven during traffic blockades

Rescue on bikes with MMS enabled phones

13. Ambulance movement in case of trafficcongestion becomes very difficult

Intelligent Traffic System using Blue lightsdisplays the direction of ingress ambulance

14. Uploading of emergency site pictures toPMC or CR for guidelines and further task

assignment

These pictures may be sent as attachments toECF on the Emergency Management System

application on the Edge/GPRS modem notebooks


7/21


8/21

8

Management

Fleet Tracking

WAN

Inernet

Dial In/ Wireless

Services

PMC

WAN Edge

Core

Data Center

Internet Edge

District Control

Room

Partner Site

(PTA/PTCL)

Emergency field

Worker

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.


9/21

9

CMS Kasur

CMS

CTWOs Kasur

CTWOs Lahore

Rescue

1122 calls

GSM

Number

PTCL/NTC

number

GSM

Number

PTCL/NTC

number

PTCL allows alternate path to

Lahore numbers when Kasur

lines are down

IP WAN

connectivityWAN cloud

Calls are routed to CTWOs Kasur from

CMS server Lahore to CMS server

Kasur over IP

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 portinstead 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 Ambulancenumber” which should be entered by the WO when he receives this valid E MS record and forwards to

corresponding EMT or Focal hospital person.


10/21

10

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 aswell


11/21

11

Detailed Network Architecture

Proposed Detailed Architecture of

Rescue 1122

Switch

WAN

GPRS/3G

network

Ambulance

Tablets

Primary District

CR

Surveillance

system

LCD Monitoring

GSM

Number

PTCL/NTC

number

Rescue

1122

PMC

IP

camera

ALI DB

ALI Server

VPN

Connectivity

Internet

PTA’s ALI

DataBase

Audio Visual

SurveillanceServer

AVC Stations

with Headphone

Control Room

BSC

Backup Data store

CMS

Wireless Control

System

Control Room

Lahore District CR

Other Districts CR

Emergency

Management System/

Scrum Task

Scheduler

BSC

Wireless control

system


12/21


13/21

13

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 Emergencyvehicle staff

227 various locationswithin district

Wireless Comm. network, Fleet Tracking software, EmergencyRecord 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


CTWOs, WOs 45 Gujranwala CMS , Email, Wireless Comm. Network, Fleet Tracking software,Emergency Management System





to 1122)



A

Bahawalpur CMS

Emergency Officers,

CRIs and Sis

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


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


to 1122)



A

Sargodha CMS

Emergency Officers,

CRIs and Sis

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


CTWOs, WOs 31 Sargodha CMS , Email, Wireless Comm. Network, Fleet Tracking software,Emergency Management System





14/21

14


to 1122)



A

D.G.Khan CMS

Emergency Officers,

CRIs and Sis

15 D.G.Khan CMS , Email, Printer, Wireless Comm. Network, IP surveillance


CTWOs, WOs 35 D.G.Khan CMS , Email, Wireless Comm. Network, Fleet Tracking software,Emergency Management System





to 1122)


the area). Traffic calculated in AnnexureA

Sahiwal CMS

Emergency Officers,

CRIs and Sis

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


CTWOs, WOs 20 Sahiwal CMS , Email, Wireless Comm. Network, Fleet Tracking software,






to 1122)


the area). Traffic calculated in AnnexureA

Sialkot CMS

Emergency Officers,

CRIs and Sis

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


CTWOs, WOs 34 Sialkot CMS , Email, Wireless Comm. Network, Fleet Tracking software,






15/21

15


to 1122)



A

Rahim Yar Khan CMS

Emergency Officers,

CRIs and Sis

8 Rahim Yar Khan CMS , Email, Printer, Wireless Comm. Network, IP surveillance


CTWOs, WOs 18 Rahim Yar Khan CMS , Email, Wireless Comm. Network, Fleet Tracking software,Emergency Management System

EMTs and Emergency

vehicle staff


within district



Emergency callers (callsto 1122)

Unlimited (can be anyone from public inthe area). Traffic calculated in Annexure

A

Murree CMS

Emergency Officers,CRIs and Sis

10 Murree CMS , Email, Printer, Wireless Comm. Network, IP surveillanceCameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs 24 Murree CMS , Email, Wireless Comm. Network, Fleet Tracking software,


EMTs and Emergency

vehicle staff


within district



Emergency callers (callsto 1122)

Unlimited (can be anyone from public inthe area). Traffic calculated in Annexure

A

other Districts CMS

Emergency Officers,CRIs and Sis

5 other Districts CMS , Email, Printer, Wireless Comm. Network, IP surveillanceCameras, IntelMap fleet monitoring, Emergency Management System

CTWOs, WOs 12 other Districts CMS , Email, Wireless Comm. Network, Fleet Tracking software,


EMTs and Emergency

vehicle staff


within district




16/21

16

Data Stores and Servers

Proposed Applications

Data Store Location Application Used by Remarks

Call Management System server

with Audio logs and reports PMC , CR

Call Management System, CMS

reports and logs

CRI, SI, CTWO and WO and

Higher management in PMC if

required

Higher Management

may refer to reporting

dashboards

IP surveillance video logs PMC , CR IP surveillance control CRI, SI and security staff

Network Management Server

and DB PMC , CR

Network and Equipment

Monitoring CTWO

Wireless Control Server with

Audio DBs PMC , CR Wireless Communication Network



required

Higher Management


dashboards

Emergency Management Server

with ECF and ERF records PMC , CR EMS



required

Higher Management


dashboards

Print and Web servers PMC , CR Internet, Printer sharing



required

Fleet tracking and IntelMap

servers with LCDs PMC , CR

Corresponding web page display

on large screen



required

Backup stores for all Data PMC Backup logs CTWO

Name of Applications Type of Traffic Flow Protocols User Community Data Stores

Application

BandWidth QOS

Dial-in Access to Call

Management System Circuit Switched ISDN/ISUP Emergency callers (1122) CMS E1 / ISDN PRI Constant Bit rate

CMS & Dispatch Client/Server Https over TCP/IP CTWO, WO CMS 100kbps nrt-VBREmergency Record

Manage Software Client/Server Https over TCP/IP

EMT, Focal person,

CTWO and WO EMS 500kbps nrt-VBR, images

IP Surveillance Cameras Peer-to-Peer VoIP over WAN CRI and SI

IP surveillance

video logs 500kbps

real-time VBR without

delays or jitter

NMS Client/Server SNMP CTWO, WOmonitoring andalarm logs 100kbps nrt-VBR

ALI

Dedicated Circuit

switched signaling SCCP over MTP layer 3 Connected to CMS

ALI DB on PTA

cloud 128kbps Constant Bit rate

Wireless Control

Wireless PTT, half-duplex

(one-way) WiFi or WiMax Field personnel

Wireless Audio

and CDRs

half-duplex voice

(12.2 kbps AMR

Codec) constant bit rate


17/21

17

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 )

http://www.rescue.gov.pk/http://www.rescue.gov.pk/http://www.rescue.gov.pk/http://www.rescue.gov.pk/


18/21

18

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 CallAverage

erlangs

No. of

circuitsCalls per day

Lahore 13,041,718 12.4065 16 3,573.07

Rawalpindi 3,073,524 2.923824 4 842.06

Faisalabad 5,231,691 4.976875 7 1,433.34

Multan 3,599,258 3.423952 5 986.10

Gujranawala 4,321,101 4.110636 6 1,183.86

Bahawalpur 2,671,775 2.541643 4 731.99

Sargodha 2,402,286 2.28528 3 658.16

D.G.khan 2,736,344 2.603067 4 749.68

Sahiwal 1,991,945 1.894925 3 545.74

DistrictRescue Drivers DERT EMT Fire Rescuers

Lead Fire

Rescuers CTWO/WO Emergency Officers Support staff Total

Lahore 383 77 291 367 77 107 46 184 1532

Rawalpindi 202 40 153 193 40 56 24 97 805

Faisalabad 195 39 148 187 39 54 23 93 778

Multan 196 39 149 188 39 55 24 94 784

Gujranawala 160 32 121 153 32 45 19 77 639

Bahawalpur 121 24 92 116 24 34 15 58 484

Sargodha 111 22 84 106 22 31 13 53 442

D.G.khan 127 25 96 121 25 35 15 61 505

Sahiwal 72 14 54 69 14 20 9 34 286

Sialkot 121 24 92 116 24 34 15 58 484Rahim Yar Khan 64 13 49 61 13 18 8 31 257

Murree 86 17 65 82 17 24 10 41 342

Jhang 44 9 33 42 9 12 5 21 175

Khanewal 31 6 24 30 6 9 4 15 125

Rajanpur 31 6 24 30 6 9 4 15 125

Muzafarghar 44 9 33 42 9 12 5 21 175

Gujrat 31 6 24 30 6 9 4 15 125

Bahawalnagar 31 6 24 30 6 9 4 15 125

Attock 31 6 24 30 6 9 4 15 125

Jehlum 31 6 24 30 6 9 4 15 125

Toba Tek Singh 31 6 24 30 6 9 4 15 125

Pakpattan 31 6 24 30 6 9 4 15 125

Mianwali 44 9 33 42 9 12 5 21 175

Kasur 21 4 16 20 4 6 3 10 84

Vehari 31 6 24 30 6 9 4 15 125

Chakwal 31 6 24 30 6 9 4 15 125Okara 31 6 24 30 6 9 4 15 125

Hafizabad 21 4 16 20 4 6 3 10 84

Sheikhupura 31 6 24 30 6 9 4 15 125

Lodhran 31 6 24 30 6 9 4 15 125

Nankana Sahib 21 4 16 20 4 6 3 10 8 4

Khushab 31 6 24 30 6 9 4 15 125

MBDin 21 4 16 20 4 6 3 10 84

Narowal 21 4 16 20 4 6 3 10 84

Layyah 31 6 24 30 6 9 4 15 125

Bhakkar 21 4 16 20 4 6 3 10 84

Chiniot 21 4 16 20 4 6 3 10 84Total


19/21

19

Sialkot 3,246,586 3.088457 4 889.48

Rahim Yar Khan 4,508,018 4.288449 6 1,235.07

Murree 953,072 0.906651 2 261.12

Jhang 1,164,994 1.108252 2 319.18

Khanewal 703,119 0.668873 1 192.64

Rajanpur 1,052,386 1.001128 2 288.32

Muzafarghar 800,420 0.761435 1 219.29Gujrat 768,547 0.731114 1 210.56

Bahawalnagar 521,332 0.49594 1 142.83

Attock 299,078 0.284511 1 81.94

Jehlum 631,250 0.600504 1 172.95

Toba Tek Singh 620,454 0.590234 1 169.99

Pakpattan 369,584 0.351583 1 101.26

Mianwali 432,998 0.411908 1 118.63

Kasur 577,935 0.549786 1 158.34

Vehari 206,993 0.196911 1 56.71

Chakwal 605,456 0.575967 1 165.88

Okara 393,393 0.374232 1 107.78

Hafizabad 374,289 0.356059 1 102.54

Sheikhupura 988,206 0.940074 2 270.74

Lodhran 605,667 0.576167 1 165.94

Nankana Sahib 330,587 0.314485 1 90.57

Khushab 137,333 0.130644 1 37.63

MBDin 337,172 0.32075 1 92.38

Narowal 381,193 0.362627 1 104.44

Layyah 343,055 0.326346 1 93.99

Bhakkar 246,895 0.23487 1 67.64

Chiniot 114,724 0.109136 1 31.43


20/21

20

Abbreviations

SOP Standard Operating Procedures

PTA Pakistan telecommunication Authority

PTCL Pakistan telecommunication Company Limited

WAN Wide Area Network

GPS Global Positioning System

Emergency

Ambulances

Fire

Trucks

Rescue

Vehicles

Water

Bowsers

Water

Rescue

Vehicles

Recovery

Vehicles

Turntable

Ladders

Aerial

Platforms

Lahore 8 27 20 4 2 1 3 2 2

Rawalpindi 5 14 12 3 2 1 2 1 1

Faisalabad 4 12 10 2 2 1 1 0 1

Multan 4 12 10 2 2 1 1 0 1

Gujranawala 4 12 10 2 2 1 1 0 1

Bahawalpur 2 8 6 2 1 0 1 0 0

Sargodha 2 8 6 1 1 1 1 0 0

D.G.khan 2 8 6 1 1 0 1 0 0

Sahiwal 1 4 2 1 1 0 1 0 0

Sialkot 1 4 2 1 1 0 1 0 0

Rahim Yar Khan 2 7 6 1 1 1 1 0 0

Murree 2 7 3 2 1 1 1 0 0

Jhang 1 4 2 1 1 0 1 0 0

Khanewal 1 4 2 1 1 0 1 0 0

Rajanpur 1 4 2 1 1 0 1 0 0

Muzafarghar 1 4 2 1 1 0 1 0 0

Gujrat 1 4 2 1 1 0 1 0 0

Bahawalnagar 1 4 2 1 1 0 1 0 0

Attock 1 4 2 1 1 0 1 0 0

Jehlum 1 4 2 1 1 0 1 0 0Toba Tek Singh 1 4 2 1 1 0 1 0 0

Pakpattan 1 4 2 1 1 0 1 0 0

Mianwali 1 4 2 1 1 0 1 0 0

Kasur 1 4 2 1 1 0 1 0 0

Vehari 1 4 2 1 1 0 1 0 0

Chakwal 1 4 2 1 1 0 1 0 0

Okara 1 4 2 1 1 0 1 0 0

Hafizabad 1 4 2 1 1 0 1 0 0

Sheikhupura 1 4 2 1 1 0 1 0 0

Lodhran 1 4 2 1 1 0 1 0 0

Nankana Sahib 1 4 2 1 1 0 1 0 0

Khushab 1 4 2 1 1 0 1 0 0

MBDin1 4 2 1 1 0 1 0 0Narowal 1 4 2 1 1 0 1 0 0

Layyah 1 4 2 1 1 0 1 0 0

Bhakkar 1 4 2 1 1 0 1 0 0

Chiniot 1 4 2 1 1 0 1 0 0

Emergency Vehicles

StationsDistrict


21/21

Documents

Rescue 1122 Report by Homaira Arif