WO2019003099A1

WO2019003099A1 - A system for real time control of exigency response operations and deployment of resources therefor

Info

Publication number: WO2019003099A1
Application number: PCT/IB2018/054696
Authority: WO
Inventors: Venkata Narasimha Sai Mallela
Original assignee: Venkata Narasimha Sai Mallela
Priority date: 2017-06-28
Filing date: 2018-06-26
Publication date: 2019-01-03

Abstract

A system (10) for real time control of exigency response operations, comprising an autonomous command and control system (100) comprising: an interface server (110) configured to receive data from data sources external to the autonomous command and control system, indicating the event of an exigency; a communication server (120) configured to facilitate flow of data within the command and control system; an application server (140) configured to assess damage, allocate resources, issue alerts and activate resources for implementing exigency response operations; an administration server (150) configured to monitor health of all the servers and manage the operation of all the servers; a plurality of workstation terminals (170) each configured to enable monitoring, control and management of exigency response operations in real time; a database server (130) configured to store data corresponding to the event of exigency and implementation of exigency response operations; and a central storage server (150) configured to store data from database server as back-up data; the servers (110-160) selectively communicating with each other and with the plurality of workstation terminals (170) for enabling real time control of exigency response operations.

Description

A SYSTEM FOR REAL TIME CONTROL OF EXIGENCY RESPONSE OPERATIONS AND DEPLOYMENT OF RESOURCES THEREFOR

FIELD

The present disclosure relates to a support system for operations carried out during exigencies. More particularly, the present disclosure relates to a command and control system to control the implementation of exigency response operations.

BACKGROUND

Exigencies can result from any sudden calamitous disaster that causes huge damage, loss and destruction and devastation to life and property. Disasters can be natural or man-made. Natural disasters arise due to naturally occurring physical phenomena caused either by rapid or slow onset of events which can be geophysical, hydrological, climatological, meteorological or biological; for example floods, cyclone, drought, earthquake, tsunami, rainfall, landslide, etc. Man-made disasters arise due to events that are caused by humans and occur in or around human settlements, for example road and train accidents, fire, structural failure and collapse, riots, industrial disasters, environmental pollution, etc., leading to displaced populations. The exigencies resulting from the damage caused by disasters vary with the geographical location, climate, the type of earth surface, degree of vulnerability, etc. Depending on its intensity and severity, disaster not only disrupts normal day to day life, but also negatively influences the exigency response operations and deployment of resources which are necessary to reach out to the affected people to supply them with normal needs like food, shelter, health care, etc., and carry out relief work.

In the event of any exigency caused by a disaster, the organization, management and deployment of resources is critical for dealing with all humanitarian aspects of the exigency in order to lessen the impact of the disaster. Exigency response operations in the past especially in cases of catastrophic damages have had several shortcomings, particularly in terms of preparedness for the disaster, response operations and recovery. Effective management of exigency response must encompass disaster prediction, mitigation, post- disaster rescue, relief and rehabilitation. This has lead to a need for creation and maintenance of appropriate facilities and systems to continuously monitor all the parameters leading up to an impending disaster for effectively forecasting the possibility of occurrence of the disaster and mitigating its effects by undertaking exigency response operations on a round the clock basis and efficiently deploying the resources required for carrying out relief work.

OBJECTS

Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows.

An object of the present disclosure is to provide a system for real time control, monitoring and management of exigency response operations and the resources deployed for carrying out the operations in the event of a disaster.

Another object of the present disclosure is to provide a system for creating and maintaining high levels of situational awareness at times of crisis or impending or ongoing disasters to enable real time control of the exigencies resulting from the disaster.

Another object of the present invention is to provide a system that interprets a disaster and the exigency resulting thereby in terms of location, extent and severity to facilitate quick and efficient deployment of resources for exigency response operations. Another object of the present invention is to provide a system that automatically and autonomously activates resources and guides the resources deployed for exigency response operations to enable their movement to the disaster site expeditiously.

Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure. SUMMARY

In accordance with an aspect of the present disclosure, there is provided a system for real time control of exigency response operations, the system comprising:

• a plurality of nodes organized in a multi-level hierarchy with each node comprising an autonomous command and control system comprising:

^■ an interface server configured to receive data from data sources external to the autonomous command and control system, the data indicating the event of an exigency arising from occurrence of a disaster;

^■ a communication server configured to facilitate flow of data within the autonomous command and control system; ^■ an application server configured to assess damage resulting from occurrence of the disaster and giving rise to the event of the exigency, allocate resources, issue alerts and activate resources for implementing exigency response operations;

^■ an administration server configured to monitor the health of all the servers and manage the operation of all the servers of the autonomous command and control system;

^■ a plurality of workstation terminals each configured to enable monitoring, control and management of exigency response operations in real time;

^■ a database server configured to store data corresponding to the event of the exigency and the implementation of exigency response operations; and

^■ a central storage server configured to store data from the database server as back-up data;

the servers selectively communicating with each other and with the plurality of workstation terminals for enabling the real time control of exigency response operations.

Preferably, the multi-level hierarchy is a three level hierarchy with a first level having a single node, a second level having one or more nodes and a third level having a plurality of nodes. In accordance with the aforementioned aspect:

• the interface server is in communication with the communication server and the administration server;

• the interface server executes an interface module, enabling transfer of data between the data sources external to the autonomous command and control system and the servers of the autonomous command and control system, the interface module including:

^■ a data receiver configured to receive the data indicating the event of the exigency from the external data sources;

^■ a data extractor cooperating with the data receiver and configured to extract predefined data from the data indicating the event of the exigency; and

" a data sender cooperating with the data extractor and configured to transmit the extracted pre-defined data to the communication server;

• the interface server further executes a web module configured to provide access to the system, the web module being accessible as an external graphical user interface (GUI) on an external portable terminal to enable users of the system to input information pertaining to the occurrence of the disaster and the event exigency therein from a site of the disaster, the information entered in the external GUI being received by the interface module. Typically, the data indicating the event of the exigency comprises sensor data including weather sensors providing weather data, water level sensors providing data related to water level in rivers, seismological sensors providing seismological data and landslide data; the extracted pre-defined data includes the sensor data and data corresponding to information entered in the GUI on the portable terminal and received by the interface module.

In accordance with the aforementioned aspect:

• the communication server is in communication with the interface server, the application server, the administration server, the plurality of workstation terminals, and the database server;

· the communication server executes a communications module facilitating flow of data within the autonomous command and control system, the communications module including:

^■ a data receiver configured to receive the extracted pre-defined data transmitted by the data sender of the interface server;

" a data converter cooperating with the data receiver to convert the extracted predefined data to a pre-determined data format and structure;

^■ a validity checker cooperating with the data converter to verify the validity of the structure and format of converted data; and

^■ a data sender cooperating with the validity checker to pre-process the converted data and transmit the pre-processed data to the data base server, and also transmit the extracted pre-defined data to the application server.

In accordance with the aforementioned aspect:

• the application server is in communication with the communication server, the administration server, the plurality of workstation terminals, and the database server;

• the application server executes a plurality of modules for implementing exigency response operations, the modules including: a damage assessment and resource allocation module configured to assess severity of damage in the event of the exigency based on the extracted pre-defined data received from the communication server and decide on allocation of resources for exigency response operations, and further configured to transmit a record of the event of the exigency, the assessed severity of damage and the allocation of resources to the database server; the damage assessment and resource allocation module also configured to transmit the extracted pre-defined data received from the communications server to the plurality of workstations;

an alert and warning generation module configured to interpret the extracted predefined data received from the communication server and generate warning and alerts indicating the event of the exigency, the warning being transmitted to the plurality of workstation terminals, the alerts being transmitted to external resource providers connected to the system;

an emergency vehicle guidance alert module cooperating with the damage assessment and resource allocation module and configured to analyze the resources allocated for exigency response operations, and generate activation commands for deployment of the allocated resources and guidance commands for guiding each allocated resources to the site of the disaster, the activation commands and guidance commands being transmitted to each allocated resource deployed for exigency response operations; a live data monitoring module cooperating with the emergency vehicle guidance alert module and with a geographic information system (GIS), and configured to compute a shortest and a fastest path between the site of the disaster and a location of each allocated resource, the shortest and fastest path being transmitted to each allocated resource deployed for exigency response operations; the emergency vehicle guidance alert module further configured to match a resource at a location closest to the site of the disaster and generate activation and guidance commands based on a successful match;

a disaster information and incident log module cooperating with the damage assessment and resource allocation module, the alert and warning generation module, emergency vehicle guidance alert module and the live data monitoring module, to chronologically log the event of the exigency and exigency response operations carried out;

a historic data analysis module cooperating with the disaster information and incident log module and configured to analyze the event of the exigency and exigency response operations to aid each of the damage assessment and resource allocation module, the alert and warning generation module, emergency vehicle guidance alert module and the live data monitoring module in performing functions thereof. In accordance with the aforementioned aspect:

• the administration server is in communication with the interface server, the communication server, the application server, the plurality of workstation terminals, and the database server, and the central storage server;

• the administration server executes a plurality of modules for monitoring the health of all the servers and managing the operation of all the servers of the autonomous command and control system, the modules including:

^■ a network management module configured to observe the status of all the servers and the workstation terminals by receiving a 'heart-beat' signal from each server to monitor a plurality of parameters of each server, the parameters including CPU occupancy, memory status, module status and module failure;

^■ a time server module configured to setup each server and set parameters of each server, the time server module accessible through an internal GUI on at least one display unit of a workstation terminal or on a display unit of the administration server to enable setting up of the server;

■ an access module cooperating with the network management module and the time server module to provide permission for logging onto the system through the workstation terminals.

In accordance with the aforementioned aspect:

• each of the plurality of workstations is in communication with the communication server, the application server, the administration server, the database server and the central storage server;

• each workstation terminal executes an interactive module configured to enable an operator to control and manage exigency response operations and deployment of resources;

• at least one workstation in communication with the communication server receives the extracted pre-defined data transmitted by the damage assessment and resource allocation module of the communications server, to enable generation of a report therein of the occurrence of the disaster to enable the damage assessment and resource allocation module to assess the severity of damage;

• each workstation terminal comprises a primary display unit displaying a situation picture of the event of exigency and the exigency response operations, and a secondary display unit displaying a GUI to facilitate access to the system,

• the situation picture displayed on the primary display unit shows:

^■ GIS layers,

^■ depiction of the disaster,

^■ resource tracking through GPS,

■ activated resources per disaster,

^■ alerts and warnings with geo-tags,

^■ sensor data,

^■ the shortest and fastest path for the allocated resource, and

^■ prominent landmarks near the site of disaster;

· the GUI displayed on the secondary display unit includes:

^■ tabs for disaster declaration,

^■ activation and de-activation of resources,

^■ monitoring of the declared disaster/event of exigency,

^■ resource tracking,

■ insertion and updation of data in the database server,

^■ sensor data,

^■ alerts and warnings, and

^■ login authentication for logging into the system. In accordance with the aforementioned aspect:

• the database server is in communication with the communication server, the application server, the administration server, the plurality of workstations, and the central storage server;

• data stored by the database server includes the sensor data, geo-spatial and relational data, incremental back-ups of all data, and logs of the disaster and the event of exigency;

• the database server is configured to execute a replication module enabling hot standby replication in the form of incremental backups, the replication module configured to update data concurrently across all the servers of the autonomous command and control system.

In accordance with the aforementioned aspect:

· the central storage server is in communication with the administration server, the plurality of workstations, and the database server;

• the central storage server is configured as a backup storage server to stored data received from the database server, the administration server and the plurality of workstations;

• the central storage server is configured to execute a replication module enabling hot standby replication in the form of incremental backups, the replication module configured to update data concurrently across all the servers of the autonomous command and control system.

In accordance with another aspect of the present disclosure, there is provided a method for real time control of exigency response operations, the method comprising the following steps:

• receiving data indicating the event of an exigency arising from occurrence of a disaster;

• extracting pre-defined data from the data indicating the event of the exigency;

• converting the extracted pre-defined data to a pre-determined data format and structure;

• verifying the validity of the structure and format of converted data;

· assessing severity of damage in the event of the exigency based on the extracted predefined data and deciding on allocation of resources for exigency response operations;

• generate warning and alerts indicating the event of the exigency;

• analyzing the resources allocated for exigency response operations, generating activation commands for deployment of the allocated resources and guidance commands for guiding each allocated resources to a site of the disaster, and transmitting the activation and guidance commands to each allocated resource;

• computing a shortest and a fastest path between the site of the disaster and a location of each allocated resource and transmitting the shortest and fastest path to each allocated resource deployed for exigency response operations; and

· chronologically logging the event of the exigency and exigency response operations carried out. Generally, the step of generate warning and alerts includes acknowledging the alert in a predetermined time.

Typically, the step of computing the shortest and fastest path includes matching a resource at a location closest to the site of the disaster and generating activation and guidance commands based on a successful match.

Typically, the step of assessing severity of damage includes generating a report of the occurrence of the disaster for assessing severity of damage.

Generally, the step of chronologically logging the event of the exigency includes storing the extracted pre-defined data.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

The system of the present disclosure will now be described with the help of the accompanying drawing, in which:

Figure 1 illustrates an architecture of the system for real time control of counter exigency operations and deployment of resources therefor, in accordance with the present disclosure;

Figure 2a illustrates an interface server of the system of figure 1 and the interconnections of the interface server within the system and externally;

Figure 2b illustrates entity relationship flow diagram of the interface server of figure 2a within the system and externally;

Figure 3a illustrates a communication server of the system of figure 1 and the interconnections of the communication server within the system; Figure 3b illustrates entity relationship flow diagram of the communication server of figure 3a within the system;

Figure 4a illustrates a database server of the system of figure 1 and the interconnections of the database server within the system; Figure 4b illustrates entity relationship flow diagram of the database server of figure 4a within the system;

Figure 5a illustrates an application server of the system of figure 1 and the interconnections of the application server within the system;

Figure 5b illustrates entity relationship flow diagram of the application server of figure 5a within the system; Figure 6a illustrates an administration server of the system of figure 1 and the interconnections of the administration server within the system;

Figure 6b illustrates entity relationship flow diagram of the administration server of figure 6a within the system; Figure 7a illustrates a central storage server of the system of figure 1 and the interconnections of the central storage server within the system;

Figure 7b illustrates entity relationship flow diagram of the central storage server of figure 7a within the system;

Figure 8a illustrates at least one of a plurality work station terminals of the system of figure 1 and the interconnections of the work station terminal within the system; and

Figure 8b illustrates entity relationship flow diagram of the work station terminal of figure 8a within the system.

DETAILED DESCRIPTION

Exigencies resulting from calamitous disasters that cause catastrophic damage need to be responded swiftly to minimize the destruction and devastation to life and property. In the event of exigencies caused by disasters, the exigency response operation and deployment of resources to carry out the operations is critical to ensure relief and rehabilitation of the affected people. Exigency response operations in the past have had several shortcomings such as unpreparedness for the disaster, late response and recovery. To overcome the aforementioned shortcomings of exigency response operations, the present disclosure envisages a system for real time control of exigency response operations and deployment of resources therefor, that forecasts the possibility of occurrence of a disaster and aids in mitigating its effects by facilitating exigency response operations on a round the clock basis and efficient deployment of resources required to carry out relief work. The system in accordance with the present disclosure will now be described with reference to the embodiments shown in the accompanying drawings. The embodiments do not limit the scope and ambit of the disclosure. The description relates purely to the examples and preferred embodiments of the disclosed method and its suggested applications. The embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

The system in accordance with the present disclosure uses rule based engines for conduct of control of exigency response operations. The principle aim of the system is to enhance the situational awareness of the exigency response operatives/functionaries by receiving and processing inputs from sensors and systems, analyzing these inputs through custom built techniques and decision tables, channelizing alerts to operators and users of the system using a combination of updates and directions, enabling activation and guidance of resources such as vehicles to enable physical movement of the vehicles to the designated disaster spot, enable conduct of diverse exigency response operations as per standard procedures laid down and facilitate a cohesive response to the disaster through a networked set of operator work stations equipped with customized user interfaces. Referring to figure 1, the architecture of the system (10) for real time control of exigency response operations and deployment of resources therefor, is illustrated. The system (10) designed to support multi-level hierarchy. Typically the system (10) is configured to operate at three levels of hierarchy, and comprises a plurality of nodes organized to form a three-tier hierarchical architecture, wherein: tier-1 or level- 1 is a super-node (1) of the system,

tier-2 or level-2 is an intermediate-node (2) of the system, and

tier-3 or level-3 is a sub-node (3) of the system. In accordance with one embodiment, the intermediate node (2) of the system (10) comprises an autonomous command and control system (100) comprising a plurality of processing units including an interface server (110), a communication server (120), a database server (130), an application server (140), an administration server (150), a central storage server (160) and a plurality of workstation terminals (170). Typically, each server may comprise various components including, but not limited to, one or more input devices, one or more processors, one or more memories, one or more communication interfaces, one or more display units and the like. The input devices may be touch screen, touchpad, keyboard, keypad, track-wheel, and the like. The processors may include microprocessors, microcontrollers, and the like computing units executing various types of computer instructions in various computer languages. The memories may include magnetic media, optical media, random access memory (RAM), read only memory (ROM), flash memory and the like volatile and/or nonvolatile memories. The communication interfaces may be operable to support wired and/or wireless communications. The display units may include liquid crystal displays (LCD), light emitting diode (LED) displays, touch sensitive LCD's, touch sensitive LED displays, and the like. In each of the servers the aforementioned components may at least be interconnected and may be cooperating with each other for operation and management of the server.

Each workstation terminal may be comprised of a computing device such as a desktop computer, a laptop, an iPad, a tablet or other similar computing device. Each terminal may comprise various components including, but not limited to, an input device, a processor, a memory, a communication interface, a display unit and the like, as mentioned herein above. Each workstation terminal may be manned by an exigency response operator/functionary for monitoring an exigency situation due to a disaster, monitoring different aspects of the exigency response operations such as medical camps, availability of power and communication lines, rehabilitation of affected persons, etc., and the deployment of resources for the same. The servers and the workstation terminals may communicate with each other over wired networks such as, but not limited to, Local Area Network (LAN), Wide Area Network (WAN), and the like. Additionally, each autonomous command and control system (100) may be capable of receiving data from mobile/smart phones, PDA's, etc., of various users of the system in the field where a disaster has occurred.

Each node of the three-tier hierarchical architecture may comprise at least one command and control system (100). Typically, the three-tier hierarchical architecture may comprise at least one command and control system (100) at tier-1 i.e. the super-node (1), a plurality of command and control systems (100) at tier-2 i.e. the intermediate-node (2), and a plurality of command and control systems (100) at tier-3 i.e. the sub-node (3). The nodes may be linked to each other through wired networks and/or wireless networks to enable communication between command and control systems (100) of different nodes, whereby the servers and the workstation terminals of a command and control system (100) in one node may communicate with the servers and the workstation terminals of another command and control system (100) in another node, over wired networks such as, but not limited to, Local Area Network (LAN), Wide Area Network (WAN), and the like; or over wireless networks such as, but not limited to, Radio Frequency (RF) network, Global System for Mobile Communications (GSM) network, General Packet Radio Service (GPRS) network, Enhanced Data for GSM Evolution (EDGE) network, Code Division Multiple Access (CDMA) network, Universal Mobile Telecommunications System (UMTS) network, High-Speed Downlink Packet Access (HSDPA) network, and the like.

Thus the three-tier architecture of the system (10) with the organization and the inter-linking of the nodes, enables data communication from a command and control system of tier-3 sub- node (3) to a command and control system of tier-1 super-node (1), thereby establishing state-of-the-art networking and communication within the system.

In accordance with an exemplary embodiment of implementation of the system in India, a tier-1 super-node (1) may be setup at an establishment under the authority of the Central/Union Government, a plurality of tier-2 intermediate-nodes (2) may be setup at establishments under the authority of different State Governments, and a plurality of tier-3 sub-nodes (3) may be setup at establishments under the authority of different District Administrations. Thus the three-tier architecture of the system (10) with the organization and the inter-linking of the nodes, enables data communication from a command and control system of tier-3 sub-node (3) setup at an establishment under the authority of a District Administration to a command and control system of tier-1 super-node (1) setup at an establishment under the authority of Central/Union Government, thereby facilitating control of exigency response operations right from District Administration through its respective State Government upto Central/Union Government, in real time. Referring to figures 2a and 2b, the interface server of the autonomous command and control system (100) of figure 1 including the interconnections of the interface server within the system (100) and externally, and the entity relationship flow diagram of the interface server with the communication server and the administration server within the system (100), is illustrated. The interface server (110) acts as a gateway between external and internal command and control systems (100). The interface server (110) hosts an interface module/application (111) that allows the flow of customized data within the command and control system (100) over LAN, and enables interaction with command and control systems (100) of various nodes over the network such as WAN. The interface module (111) of the interface server is capable of receiving sensor data pertaining to weather data such as rainfall, cyclone, etc., from weather bureaus for example the Indian Meteorological Department (IMD), water levels in different rivers at various points along the rivers from water resource departments for example the Central Water Commission (CWC) of India, and seismological information from different seismographic centers for example National Geophysical Research Institute (NGRI) of India, IMD, etc. through WAN and/or GPRS/GPS. The interface module (111) is also capable of receiving inputs from individual sensors such as landslides sensors through WAN and/or GPRS/GPS.

The interface module/application (111) comprises a data receiver (112), a data extractor (113) and a data sender (114). The interface module (111) including the data receiver (112), the data extractor (113) and the data sender (114) are executed by at least a processor of the interface server (110). The data receiver (112) is configured to receive the sensor data by means of TCP/UDP protocols through the communication interface of the interface server connected to the WAN. The data extractor (113) cooperates with the data receiver (112) to extract the sensor data pertaining to the weather data, water levels in different rivers at various points along the rivers, seismological data and landslide data received by the data receiver (112), and provides the extracted sensor data to the data sender (114) that cooperates with the data extractor (113) to transmit the sensor data to the communication server (120) over the LAN by means of TCP/UDP protocols through the communication interface of the interface server (110) connected to the LAN, and data for exigency response operatives/functionaries on workstation terminals. Thus, the interface server (110) acts as a bridge between the servers of its command and control system (100) in the node where it is situated and the external world i.e. the servers of the command and control system (100) belonging to other nodes.

The interface server (110) further hosts a web server module/application (115) that presents a custom developed user interactive web module/application having a graphical user interface (GUI) on the mobile/smart phones, PDA's, etc., of users of the system on the field or a disaster site to enable them to input information pertaining the disaster and the exigency. The web server module/application (115) also presents a web portal (WP) on desktop/personal computers of the users of the system. The users of the system may include an individual citizen, local administrative authority, reporter, etc., who may be present at the disaster site. The web server module/application (115) is also executed by at least the processor of the interface server (110). The data corresponding to this information is then typically transmitted via GPRS/GPS by the mobile/smart phone to the autonomous command and control system (100), which data is then received by the data receiver (112) of the interface module/application (111) through the communication interface of the interface server (110). Thus, the web server module/application (115) enables connectivity with external devices such as the mobile phones, PDA's, etc., while the last mile connectivity is achieved using GPRS/GPS.

Typically, the at least the processor and a memory of the interface server (110) cooperate together to implement an OpenSUSE and/or C/C++ platform for operation and management of the interface server, whereby the processor executes both the interface module/application (111) and the web server module/application (115) thereon. The interface server (111) is configured in a dual redundant manner, with a main server and a standby server using IP binding techniques. Referring to figures 3a and 3b the communication server of the autonomous command and control system (100) of figure 1 and the interconnections of the communication server within the system (100), and the entity relationship flow diagram of the communication server with the interface server, the database server, the application server, the administration server and the workstation terminals within the system (100), illustrated. The communication server (120) acts as a bridge between the interface server (110) and other servers and the workstation terminals within the command and control system (100). The communication server (120) hosts a communications module/application (121) that allows the flow of customized data within the command and control system (100) over LAN. The communications module (121) of the communication server (120) is capable of receiving, converting and validating data before sending data to other servers in the command and control system (100).

The communications module/application (121) comprises a data receiver (122), a data converter (123), a validity checker (124) and a data sender (125). The communications module (121) including the data receiver (122), the data converter (123), the validity checker (124) and the data sender (125) are executed by at least a processor of the communications server (110). The data receiver (122) is configured to receive the sensor data as well as the GPRS/GPS data pertaining to the disaster from the users of the system and data for the exigency response operatives/functionaries, from the interface server (110) by means of TCP/UDP protocols through the communication interface of the communications server (120) connected to the LAN. The data converter (123) cooperates with the data receiver (122) to convert the sensor data (SD) and the GPRS/GPS data pertaining to the disaster, to a predefined structure. The validity checker (124) cooperates with the data converter (123) to verify the validity of the protocol, structure and format of the converted data, and provides the verified data to the data sender (125) that cooperates with the validity checker (124) to perform certain pre-processing functions on the data and transmits the pre-processed data to the database server (130), the application server (140) and the workstation terminals (170) over the LAN by means of TCP/UDP protocols through the communication interface of the communication server (120) connected to the LAN. Typically, the sensor data pre-processed to form a sensor table containing sensor data from a plurality sensors pertaining to the weather data, water levels in different rivers at various points along the rivers, seismological data and landslide data in tabular form and GPS data pre-processed to from a GPS table containing GPRS/GPS data pertaining to the disaster from multiple operatives and users of the system, is transmitted to the database server; data indicating sensor triggers (ST) extracted and determined from the sensor data and GPS data are transmitted to the application server (140); and GPS data is transmitted to the workstation terminals (170). Typically, the at least the processor and a memory of the communication server (120) cooperate together to implement an OpenSUSE and/or C/C++ platform for operation and management of the communication server, whereby the processor executes communications module/application (121) thereon. The communication server (120) is configured in a dual redundant manner, with a main server and a standby server using IP binding techniques.

Referring to figures 4a and 4b the database server of the autonomous command and control system (100) of figure 1 and the interconnections of the database server within the system (100), and the entity relationship flow diagram of the database server with the communication server, the application server, the administration server, the central storage server, and the workstation terminals within the system (100), illustrated. The database server (130) comprises a plurality of non-volatile memories such as hard disks (HDD) that are used to store data received from the communication server (120), the application server (140), the administration server (150) and the workstation terminals (170), by means of TCP/UDP protocols through the communication interface of the database server (130) connected to the LAN. The database server (130) receives the sensor table and the GPS table from the communication server (120). All the data received from the servers is typically stored in the form of data tables in the hard disks of the database server (130). A back-up of all the tables is transmitted by the database server (130) to the central storage server (160). The data stored on the hard disks of the data base server (130) include geo-spatial data and relational data (131), incremental back-ups (132) of all the data, and incident logs (134) of the disasters and the exigencies along with historical data related to all the disasters natural as well as man-made. The database server (130) hosts a replication module/tool (133) that provides hot stand-by replication to one or more standbys and enables replication in the form of incremental back-ups. The hot-standby replication module is executed by at least a processor of the database server (130). The replication module/tool (133) updates data concurrently across all the servers in the command and control system (100) by means of TCP/UDP protocols through the LAN. The database server (130) is typically a COTS server class machine that operates in dual- redundant manner with the main and standby systems bound together using appropriate IP binding techniques. The technique used to maintain this type of data management system is master-master replication and object-relational data model. The data tables themselves are devised in a manner that enables storage of data in the form of static, semi-static, dynamic data. Logging and storing of database is maintained based on frequent updates and disaster type. The data can be entered from the workstation terminals (170) as well as the web interface or the user interactive web module/application i.e. the GUI on the mobile phone of a user of the system.

Data base tables can be updated using triggers from live data inserts and operator/user actions through the GUI. The command and control system (100) provides permissions for logging and storing of data which is controlled from an administrative setting. All topographic, demographic and incident information layers are stored in custom designed data tables. Data of exigency response resources and road network data are static or semi static in nature while sensor and disaster/incident related data are dynamic.

Typically, database server (130) is "PostgreSQL" that supports both relational queries and spatial queries. Maintenance of the database server (130) is categorized into two models relational-database and geo-database. Relational database management system (RDBMS) model maintains static, semi-static and dynamic data tables such as hospitals, volunteers, emergency vehicles, heli-bases, government shelters, relief materials, sensor data, etc. Geo database model maintains data tables of points of interest (POIs) such as roads, railway lines, buildings and other POIs. Generally spatial queries will facilitate querying data based on geometry (polygon/multipolygon/point). Logs and time bound backups are maintained in the database server (130) based on start and end-time.

Typically, the at least the processor and a memory of the database server (130) cooperate together to implement an Open Source platform such as Linux, for operation and management of the database server (130), whereby the processor executes replication module/tool (133) thereon to backup data incrementally.

Referring to figures 5 a and 5b the application server of the autonomous command and control system (100) of figure 1 and the interconnections of the application server within the system (100), and the entity relationship flow diagram of the application server with the communication server, the database server, the administration server and the workstation terminals within the system (100), illustrated. The application server (140) is a decision support system which after making damage assessment, issues alerts and activates the necessary resources to support rescue and relief operations. The application server (140) is designed to be the heart of each autonomous command and control system (100) and forms the basis for decision support in the system (100). The application server (140) interacts with the communications server (120) as well as the workstation terminals (170) over the LAN for collection of triggers, i.e. occurrence of a disaster. Thereafter the application server (140) interacts with the database server (130) over the LAN for collecting additional state and status information for consideration. The application server (140) delivers actionable information for the operators manning the workstation terminals (170) to execute their task. The application server (140) hosts a plurality of custom developed modules/applications for implementing the exigency response operations. The modules/applications invoke operating procedures embedded on the modules so as to generate necessary decision cues for execution of the operational tasks at hand. The modules/applications implement a rule-engine that interprets the standard operating processes to be followed in dealing with the exigency resulting from the disaster. The application server (140) typically hosts a damage assessment and resource allocation module (141), an alert and warning generation module (142), an emergency vehicles guidance alert module (143), a live data monitoring module (144) for allocation of a shortest path to an emergency vehicle, a historic data analysis module (145) and a disaster information and incident log module (146). All the modules (141-146) are executed by at least a processor of the application server (140).

The damage assessment and resource allocation module (141) assesses severity of the damage caused by the disaster. Whenever an incident or disaster occurs, the damage assessment module (141) provides assessment of the situation. The damage assessment and resource allocation module (141), based on data indicating sensor triggers and GPS data transmitted by the communication server (120), provides incident/disaster declaration to the workstation terminals manned by the operators for operator actions such as generation of incident/disaster report. After reading an incident/disaster report generated from workstation terminals (170) by the operators manning the workstation terminal, the damage assessment and resource allocation module (141) assesses the damage posed by the incident/disaster trigger and computes requirements for the resulting exigency response operations, and allocates different types of resources (tents, boats, food, water, etc.) to be deployed for carrying out exigency response operations. The decision to allocate the resources for carrying out exigency response operations is arrived at by conducting data analysis between topographic and demographic layers, by invoking a suitable rule engine. The damage assessment and resource allocation module (141) saves the disaster/incident information from the disaster/incident report in a disaster/incident table, and also the allocation of resources in a resource table. While allocating resources, the damage assessment and resource allocation module (141) extracts any previous resource table stored in the database server (130) to check for the available resources before allocating the resources and also data for the exigency response functionaries on the workstation terminals (170). The damage assessment and resource allocation module (141) transmits the disaster/incident table, the resource table, live incident information, a record of the incident/disaster to the database server (130), and receives the previous resource table and data for the exigency response functionaries list from the database server (130), as also illustrated in figure 4b; and further transmits a list of the exigency response functionaries to the communication server (120), over the LAN by means of TCP/UDP protocols. The alert and warning generation module (142) module generates alerts and warnings for the operators manning the workstation terminals (170) based on pre-decided thresholds and limits. The alert and warning generation module (142) brings to context, data being continuously received from various sensors such as seismic, rainfall and water gauges etc., interprets the data and generates necessary warning and the disaster/incident information for operator actions on workstation terminals (170). The alert and warning generation module (142) also issues alerts for resources as a forewarning of impending activation to the resource providers connected to the system (100) as well as to the operators manning the workstation terminals (170). Warnings are issued whenever, the module (142) deems that some impending breach-point has been crossed. The alert and warning generation module (142) transmits the alerts and warnings, the disaster/incident information and alerts for resources to the workstation terminals (170) over the LAN by means of TCP/UDP protocols.

The emergency vehicles guidance alert module (143) analyses the exigency and the resources allocated for carrying out the exigency response operations by the resource allocation module (141) and generates activation orders/commands for deployment of the resources. At least some of the resources namely emergency vehicles such as ambulances, fire brigade trucks, etc., are connected to the command and control system (100) through the user interactive web module/application i.e. the GUI on the mobile phone associated with the emergency vehicle or the driver of the vehicle. The emergency vehicles guidance alert module (143) of the application server (140) transmits the activation order for the resources/emergency vehicles along with guidance commands for guiding the vehicles to the disaster site, through the communication server (120) over the LAN by means of TCP/UDP protocols. All emergency vehicles that are connected to the command and control system (100) are initially registered with the system (100). The driver or any person associated with the emergency vehicle needs to enter the vehicles details such as vehicle number, vehicle type, etc., in the GUI on the mobile phone associated with the emergency vehicle or the driver of the vehicle to register the vehicle, whereupon the vehicle registration data is transmitted via GPRS/GPS by the mobile phone to the autonomous command and control system (100). The vehicle registration data from the mobile phone associated with the vehicle is received by the interface server (110) and transmitted to the communication server (120) which further transmits the vehicle registration data to the database server (130) wherein the vehicle registration is typically stored in the form of vehicle table in the resource table, as illustrated in figures 3b and 4b. On receiving the activation orders/commands for deployment of the resources from the application server (140), the communication server (120) extracts the vehicle table from the database server (130) and provides the vehicle registration data to the interface server (110) for transmitting the activating order/command to the mobile phone associated with the emergency vehicle or the driver of the vehicle to deploy the vehicle. The data receiver (112), data extractor (113) and data sender (114) of the interface module (111) in the interface server (110) perform similar operations as stated above on the vehicle registration data. Similarly, the data receiver (122), data converter (123), validity checker (124) and data sender (125) of the communications module (121) perform operations as stated above on the vehicle registration data.

The live data monitoring module (144) computes the shortest and the fastest path between the disaster site and the emergency vehicle deployed for rescue and relief, in collaboration with a geographic information system (GIS) application included in the live data monitoring module (144). The live data monitoring module (144) besides computing the shortest path, also considers a resource-exigency match to determine an appropriate response operation based on the condition of the exigency, before computing the shortest path. Re-routing requests from already deployed resources are also processed by the live data monitoring module (144). After the shortest path is determined by the live data monitoring module (144), the emergency vehicles guidance alert module (143) matches the resource and its location and the destination i.e. the disaster site, to ensure that a correct path that successfully matches with the vehicle/resource allocated is identified before issuing activation orders/commands for deployment of the resource and committing the vehicle on the path.

The disaster information and incident log module (145) chronologically arranges the information pertaining to the exigency response operations for the disaster occurred. This information is arranged in the form of a comprehensive table that keeps track of all elements connected with a particular disaster/incident. The table is interactive and can be viewed from any workstation terminals (170), and is transmitted to the database server (130) after completion of the incident.

The historic data analysis module (146) analysis all the historic data related to the occurrence of the disaster, the resulting exigency and the exigency response operations carried out at the same disaster site to aid the damage assessment and resource allocation module (141), alert and warning generation module (142), emergency vehicles guidance alert module (143), and live data monitoring module (144) to process data and perform the requisite functions.

The application server (140) is configured in a dual redundant manner, with a main server and a standby server using IP binding techniques.

Referring to figures 6a and 6b the administration server of the autonomous command and control system (100) of figure 1 and the interconnections of the administration server within the system (100), and the entity relationship flow diagram of the administration server with the interface server, the communication server, the database server, the application server, the central storage server and the workstation terminals within the system (100), is illustrated. The administration server (150) facilitates the management of the autonomous command and control system (100) as a whole. Administrator activities such as health monitoring of all the servers of the system (100), network overloads, etc., are maintained by the administration server (150). The administration server hosts a network management module (151), a timer server module (152) and an access module (153). All the modules (151-153) are executed by at least a processor of the administration server (150). The network management module (151) is used for network configuration and performance monitoring. The network management module (151) is configured to observe the status of all the servers (110-160) and the workstation terminals (170) of the command and control system (100). Besides 'ON'/'OFF' status, each server sends a 'heart beat' to the network management module (151) whereby the module (151) monitors several vital performance parameters such as CPU occupancy, memory status, module/application status and/or failure, etc. of each server. System (100) configuration and re-loading of modules/applications in each server of the system (100) can be undertaken from the network management module (151). Further, the network management modules (151) of administration servers (150) in different command and control system (100) can also be configured for remote administration of the entire system (10). The network management module (151) receives the 'heart beat' signal over the LAN by means of TCP/UDP protocols through the communication interface of the administration server (150) connected to the LAN. The monitoring of the vital parameters is facilitated on at least a display unit of the administration server (150). The time server module (152) can also be utilized for system (100) setup, managing system (100) configuration as well as setting defaults. An administrator interactive module having an administrator GUI is facilitated to a system administrator for effecting changes to the configurable parameters of the system (100) which would ensure that different benchmarks could be set for different local conditions. The administrator GUI enables system administrators to ingest system data from any location over the LANAVAN, create and modify data in the database server and also provides flexibility in workstation terminal utilization. The administrator GUI can be accessed by the system administrators on the display unit of the administration server (150) or on a display unit of a workstation terminal (170).

The access module (153) in cooperation with the network management module (151) and the time server module (152) provides permissions for logging into the system by implementing a lightweight directory access protocol (LDAP). All logins including those by system administrators, operators manning workstation terminals (170), drivers of emergency vehicles through the GUI on the mobile phone, and users of the system in the field through the GUI on the mobile phone would be facilitated through the LDAP for authentication and rights management.

The administration server (150) is configured in a dual redundant manner, with a main server and a standby server using IP binding techniques.

Referring to figures 7a and 7b the central storage server of the autonomous command and control system (100) of figure 1 and the interconnections of the central storage server within the system (100), and the entity relationship flow diagram of the central storage server with the database server, the administration server and the workstation terminals within the system (100), is illustrated. The central storage server (160) is configured as a backup storage server. The central storage server (160) comprises a plurality of non- volatile memories such as hard disks that are used to store data received from the database server (130), the administration server (150) and the workstation terminals (170), by means of TCP/UDP protocols through the communication interface of the central storage server (136) connected to the LAN. The data stored in the hard disks of the central storage server (160) include backup of historic data (161), record and replay data (162), static geo spatial data/tables (163), static relational data/tables (164), incident/disaster logs, satellite images, etc. The central storage server (160) hosts a replication module/tool that enables replication in the form of incremental back-ups. The replication module is executed by at least a processor of the central storage server (160). The replication module/tool updates data concurrently across all the servers in the command and control system (100) over the LAN by means of TCP/UDP protocols. The central storage server (130) is typically a COTS server class machine that operates in dual-redundant manner with the main and standby systems bound together using appropriate IP binding techniques. The technique used to maintain this type of data management system is master-slave configuration. The record and reply data (164) is uploaded to the central storage server (160) using a secure tunnel. Typically, the at least the processor and a memory of the central storage server (160) cooperate together to implement an Open Source platform such as Linux, for operation and management of the central storage server (160), whereby the processor executes replication module/tool thereon to backup data incrementally. Referring to figures 8a and 8b at least one of a plurality work station terminals of the autonomous command and control system (100) of figure 1 and the interconnections of the work station terminal and the entity relationship flow diagram of the work station terminal with the communication server, the database server, the application server, the administration server and the central storage server within the system (100), is illustrated. The autonomous command and control system (100) comprises multiple workstation terminals each being manned by an operator for real time control of the exigency response operations. In accordance with one embodiment, the system (100) comprises 24 workstation terminals, each adapted to function in ten different modes of operation. Further, each workstation terminal can function in two modes of operation simultaneously with necessary permissions. Each operator workstation terminal can function in main and stand-by configuration to enable two different operators to share the work load. Furthermore, a designated workstation terminal could take over the functionality of another workstation terminal on a need basis. Each workstation terminal (170) is configured for record and replay by means of a customized operator interactive module (170c) having an operator graphical user interface (GUI) to enable the operator manning the work station terminal (170) control and manage the exigency response operations and deployment of resources in real time. Typically each workstation terminal (170) includes two display units, wherein a primary display unit (170a) displays a situation picture (SP) and a secondary display unit (170b) displays the GUI for the operator.

The situation picture displayed on the primary display unit (170a) shows a GIS setting and depicts objects and maps against the GIS setting. Situational awareness consisting of all points of interest (such as location of important points, weather inputs, cyclone warnings, earthquake data, resource availability, POIs in terms of hospitals, police station, fire stations, railway network, road network etc.,), location of the disaster reported, are displayed on the primary display unit (170a) against GIS with different symbols representing different objects. On the primary display unit (170a), the GIS map of the disaster site is displayed with the following as overlay:

• the affected site of the disaster in appropriate color; • flood, earthquake and rainfall status at various monitoring stations for water with level/rainfall with different color codes for different states of warning;

• weather data for high winds, cyclones and relevant warnings;

• points of interest such as hospitals, police stations, schools, shelter, logistic hubs etc., with different symbols;

• geographical features such as road network, rivers and canal network, railway

network, water bodies etc. ;

• airports, helipads, bridges with different symbols;

• current positions of moving objects such as transport requisitioned for exigency relief, ambulances, police vehicles, specialist vehicles etc.;

• historic data in the form of GIS interpretable maps in case of natural disasters and man- made disasters.

Further, the primary display unit (170a) displaying the situation picture typically shows GIS layers (170aj), depiction of the disaster/incident (170a₂), resource tracking through GPS (170a₃), activated resources per disaster (170a₄), alerts/warnings with geo-tags (170as), sensor/resource data (170a₆), the shortest path for the emergency vehicle (170a₇), and prominent points, buildings and places near the disaster site (170as) against the GIS setting. The GUI displayed on the secondary display unit (170b) provides tabular data and interface menus for all operator actions with the system (100). Typically, the following textual messages are displayed in the GUI:

• user interfaces for system interactions;

• status of all the resources needed for exigency relief operations;

· alert warning table consisting of all the resources altered for each disaster;

• status and location of resources activated for each disaster

• status of all emergency vehicles, ambulances, police vehicles, specialist vehicles, hired transport etc., whose position will be updated at a frequency different from normal conditions in a disaster situation;

other relevant information pertaining to the mode of operation;

input management menus from the secondary display unit. Further, the second display unit (170b) displaying the GUI typically provides tabs for disaster/incident declaration (170bj), activation and de-activation of resources (170b₂), monitoring the declared disaster (170b₃), resource tracking (170b₄), insertion and updation of data (170bs) in the database server, displaying sensor/resource data (170be), displaying alerts and warnings (170b₇), and login authentication (170bs) for the operator.

The two displays of each workstation terminal can be recorded in a video format and can be replayed as desired, even from another server of the system (100). Typically each operator manning each workstation terminal will have to register himself with the system through the GUI of the operator interactive module by providing his personal and professional details and creating a user ID and a password. Thereafter, each operator can login to the system through the login authentication (170bg) tab on the GUI displayed on the second display unit (170b) on his/her respective workstation terminal with his/her user ID and password.

Major functionalities of the workstation terminals (170) include:

• overlay of situational display over different map layers, physical and topographical;

• layering additional data for Points of Interest like roads, rail networks etc.;

· creation and display of objects with customized exigency response symbology;

• provision for GUI menus for operator system interactions;

• display of system information in tabular and graphical format;

• creation and maintenance of disaster information report

• generation of alerts and warnings and contexting these to the operator;

· pop-up menus, symbol color changes and symbol highlighting;

• disaster information depiction on the primary screen using suitable overlays on the GIS.

In accordance with an exemplary embodiment, nine workstation terminals out of the 24 workstation terminals are configured for nine functionalities, wherein each workstation terminal configured for one functionality. A first workstation terminal (171) is configured for weather monitoring, a second workstation terminal (172) is configured for transport management, a third workstation terminal (173) is configured for medical services rendering, a fourth workstation terminal (174) is configured for power management, a fifth workstation terminal (175) is configured for communication management, a sixth workstation terminal (176) is configured for induction of rescue workers, a seventh workstation terminal (177) is configured for relief and rehabilitation, an eighth workstation terminal (178) is configured for logistics management, and a ninth workstation terminal (179) is configured for imagery display. Each of workstation terminals (171-179) includes the primary display unit displaying the situation picture (SP) and the secondary display unit displaying the GUI for the operator.

The first workstation terminal (171) is configured for weather monitoring by configuring at least a processor of the terminal (171) to process all types of weather related data. The operator manning the first workstation terminal (171) will be responsible for all the activities pertaining to the declared disaster/incident. Upto four workstation terminals can be used for weather monitoring. The weather information displayed on the display unit of the first workstation terminal (171) includes:

• overlay of weather data including cyclone, rainfall, floods, landslide, earthquake;

· POI overlay, maps and vector layers;

• data tables;

• resources information displayed in tables;

• mobile alerts;

• disaster/incident information reports;

· disaster/incident declaration;

• display of weather images;

• replay within specified time limits;

• satellite image displayed in specific time limit;

• received and processed weather related data of all types;

· requests from other workstation terminals.

The second workstation terminal (172) is configured for transport management by configuring at least a processor of the terminal (172) to process transport related data to facilitate the operator manning the terminal (172) to handle vehicle deployment, routing, guiding and tracking. The transport related information displayed on the display unit of the second workstation terminal (172) includes:

• overlay of resources data including civil transport providers;

• POI overlay, maps and vector layers; • data tables;

• resources information displayed in tables;

• mobile alerts;

• vehicle tracking windows;

· disaster/incident information reports;

• replay within specified time limits;

• roads blocked due to damage and unblocked roads;

• requests from other workstation terminals

• allocation of transport for mobilization of people or resources.

The third workstation terminal (173) is configured for medical services by configuring at least a processor of the terminal (173) to process medical related data to facilitate the operator manning the terminal (173) to handle deployment of medical teams and medical kits. The medical related information displayed on the display unit of the third workstation terminal (173) includes:

• overlay of medical data including hospital data and medical camps;

• POI overlay, maps and vector layers;

• data tables;

• resources information displayed in tables;

· mobile alerts;

• vehicle tracking windows for ambulances;

• creation and maintenance of medical camps based on request or requirement;

• replay within specified time limits;

• requests handling with other workstation terminals including transport for mobilization.

The fourth workstation terminal (174) is configured for power management by configuring at least a processor of the terminal (174) to process power status related data to make the operator manning the terminal (174) aware of the power situation at the disaster site and analyze and take decisions accordingly. The power related information displayed on the display unit of the fourth workstation terminal (174) includes:

• status of power generating stations, sub-stations, power resources and feeders;

• availability of trained manpower;

• POI overlay, maps and vector layers; • data tables;

• resources information displayed in tables and its network;

• mobile alerts;

• vehicle tracking windows;

· provision for substation block/unblock to represent powered and unpowered

areas against GIS map;

• disaster/incident information reports;

• replays within specified time limits;

The fifth workstation terminal (175) is configured for communication management by configuring at least a processor of the terminal (175) to process all types of communication stations' related data to make the operator manning the terminal (175) aware of the communication situation at the disaster site and analyze and take decisions accordingly. The communication related information displayed on the display unit of the fifth workstation terminal (175) includes:

• overlay of communication data;

• communication stations and their antenna and network;

• availability of communication resources and personnel;

· POI overlay, maps and vector layers;

• data tables;

• resources information displayed in tables;

• mobile alerts;

• deployment planning of satellite equipment/antennae and vehicles;

· disaster/incident information reports;

• replays within specified time limits;

• requests handling with other workstation terminals.

The sixth workstation terminal (176) is configured for induction by configuring at least a processor of the terminal (176) to process data related to rescue workers including volunteers and troops, to enable the operator manning the terminal (176) issue requisitions for deployment of rescue workers, volunteers and troops at the disaster site, and also de-induct them from the disaster site. The information displayed on the display unit of the sixth workstation terminal (176) includes:

• overlay of rescue workers, volunteers, troops' data;

• POI overlay, maps and vector layers;

· data tables;

• deployment and management of rescue workers, volunteers and troop at the disaster site;

• resources information displayed in tables;

• mobile alerts;

• replays within specified time limits;

· requests handling with other workstation terminals.

The seventh workstation terminal (177) is configured for relief and rehabilitation by configuring at least a processor of the terminal (177) to process relief and rehabilitation related data of all types of disasters, to enable the operator manning the terminal (177) take steps for relief and rehabilitation. The relief and rehabilitation related information displayed on the display unit of the seventh workstation terminal (177) includes:

• overlay of data including relief materials and their availability in stores;

• POI overlay, maps and vector layers;

• data tables;

· resources information displayed in tables;

• mobile alerts;

• replays within specified time limits;

• requests handling with other workstation terminals including transport for mobilization;

• resource allocation and management of reserves.

· issue necessary instructions for sending effected people to the relief camps depending upon the availability of necessary accommodation.

The eighth workstation terminal (178) is configured for logistics management by configuring at least a processor of the terminal (178) to process all types of logistics related data, to enable the operator manning the terminal (178) plan the deployment of resources. The logistics data processed also enables the operators to handle national and international volunteer troops for induction assessment operations. The logistics related information displayed on the display unit of the eighth workstation terminal (178) includes: • overlay of logistics data;

• POI overlay, maps and vector layers;

• data tables;

• resources information displayed in tables;

· logging resources imports and exports;

• replays within specified time limits;

• mobile alerts;

• requests handling with other workstation terminals including transport for mobilization. The ninth workstation terminal (179) is configured for imagery display by configuring at least a processor of the terminal (179) to process all types of image related data. The image related information displayed on the display unit of the ninth workstation terminal (179) includes:

• live videos and pictures of the disaster site;

· satellite images of the disaster site;

• drone stream videos of the disaster site;

• POI overlay;

• historical data;

• analysis of the images.

A typical operation of the entire system for exigency response operations and deployment of resources in accordance with the present invention is described hereinafter. It may be appreciated that the operation of the system is intended to facilitate understanding of the invention.

The command and control system (100) at a node, on receiving a disaster/incident report generates activation instructions of appropriate resources for immediate action to minimize the loss of life and property. The disaster report can be triggered either by a user of the system on the field through the GUI of the user interactive web module/application on his/her mobile phone or by an operator manning a workstation (170) of the system (100) through operator actions. Alternately, the system (100) can receive sensor data pertaining to weather data such as rainfall, cyclone, etc., from weather bureaus for example the Indian Meteorological Department (IMD), water levels in different rivers at various points along the rivers from water resource departments for example the Central Water Commission (CWC) of India, and seismological information from different seismographic centers for example National Geophysical Research Institute (NGRI) of India, IMD, etc. This data is received in the interface server through WAN and/or GPRS/GPS by the interface module/application (111) of the interface server (110). Thereafter the sensor data is transmitted to the communication server (120) over the LAN. The data receiver (112), data extractor (113) and data sender (114) of the interface module (111) in the interface server (110) perform similar operations as stated above on the sensor data before its transmission to the communication server (120). The data is received in the communication server (120) through the LAN by the communication module/application (121) of the communication server (120), and after processing in the communication server (120) is then transmitted to the database server (130), the applications server (140) and the workstation terminals (170) over the LAN. The data receiver (122), data converter (123), validity checker (124) and data sender (125) of the communications module (121) perform operations as stated above on the data.

If the processed data warrants, the disaster/incident report is generated in the workstation terminal (170) receiving the processed data and suitable action is initiated by the operator manning the workstation terminal (170). The disaster report includes type of disaster, location/site and time.

Whenever an input, such as disaster report, sensor data, etc. is received in the system, the same is geo-referenced and compared with historical data to determine the extent and potentially the trigger.

The disaster/incident report is received in the applications server (140) from the workstation terminal (170). Thereafter, the damage assessment and resource allocation module (141) acquires a list of all required resources within a specified proximity of the disaster site, stored in the database server (130) and allocates the resources and also acquires the list of exigency response functionaries from the database server (130). Next, the alert and warning generation module (142) issues alert message to all of the resources and the exigency response functionaries. The alert message is transmitted by the alert and warning generation module (142) in the application server (140) via LAN to the communication server (120) which further transmits the alert message via LAN to the interface server (110) from where the alert message is transmitted via GPRS/GPS to the to the resources, such as emergency vehicles. In the interface server (110), the interface module (111) including the data receiver (112), data extractor (113) and data sender (114) perform similar operations as stated above on the alert message. Similarly in the communication server (120), the communications module (121) including the data receiver (122), data converter (123), validity checker (124) and data sender (125) perform operations as stated above on the alert message. The resources connected to the system (100) are expected to acknowledge the alert message within 60 seconds of issuing the alert message. The resources need to send an alert acknowledgment through the GUI of the user interactive web module/application on the mobile phone associated with the resource. The alert acknowledgement is transmitted via GPRS/GPS by the mobile phone to the command and control system (100). The acknowledgement from the mobile phone associated with the resource is received by the interface server (110) and transmitted to the communication server (120) which further transmits the acknowledgement to the database server (130) and the application server (140) from where the acknowledgement is transmitted to the workstation terminals (170), all via the LAN of the system (100).

An 'incident manager' overseeing the operations through the workstation terminal to which the alert acknowledgement is transmitted will coordinate all the activities and activate the necessary resources from among those that have responded to the alert message. The activation message from the workstation terminal is then transmitted to the application server (140) wherein the emergency vehicles guidance alert module (143) analyses the exigency and the resources allocated for carrying out the exigency response operations by the resource allocation module (141) and generates activation orders/commands for deployment of the resources. The emergency vehicles guidance alert module (143) of the application server (140) transmits the activation order for the resources/emergency vehicles along with guidance commands via LAN to the communication server (120) which further transmits the activation order via LAN to the interface server (110) from where the activation order is transmitted via GPRS/GPS to the to the resources namely emergency vehicles such as ambulances, fire brigade trucks, etc. The system (100) starts tracking those activated resources/vehicles, which are now on the move and deployed for the exigency response operations, such as fire engines, ambulances, specialist vehicles, with the help of GPS location data sent from the vehicles. The GPS data from vehicles is received by the interface server (110) and transmitted to the communication server (120) which further transmits the GPS location data of the vehicles to the database server (130) and the application server (140) from where the GPS location data of the vehicles is transmitted to the workstation terminals (170) including the workstation terminal of the 'incident manager', all via the LAN of the system (100). An incident table, consisting of incident details, alert details, activation details and corresponding screenshots of situational display (screenshot per every 2 seconds) are recorded for posterity and replayed on demand by the record and replay on the workstation terminals. An exemplary embodiment of the operation of the entire system for exigency response operations and deployment of resources in the event of a natural disaster of excessive rainfall is described hereinafter. It may be appreciated that the operation of the system is intended merely to facilitate understanding of the invention.

• Rainfall disaster information report is taken from the IMD website is received by the interface server (110) and transmitted to the communications server (120) and thereafter sent to the application server (140). In the application server (140), the information is analyzed against historic data of the disaster site available from the database server (130) and severity and the extent of the disaster are determined.

• If the rainfall exceeds a particular value, the alert and warning generation module (142) in the application server (140) will send an alert to a workstation terminal for declaring a disaster.

• On receiving the alert, the operator manning the workstation terminal clicks on the alert whereby relevant information is filled out automatically in a 'disaster declaration widget' form. Additionally as a pre -requisite, the operator fills an exigency response resource template based on the type of disaster to alert particular type of resources.

• The disaster/incident and the exigency is declared through the 'disaster declaration widget' on the secondary display unit (170b) on the workstation terminal. After declaration of the disaster/incident on the workstation terminal, the application server (140) receives the disaster information report, whereupon the damage assessment module (141) allocates a disaster ID for the disaster/incident and fills the information in a live incident table consisting of disaster ID, disaster type, the workstation terminal declaring the disaster and time of disaster. On closure of the disaster/ incident the row in the table having this information will be deleted.

The disaster/incident is then broadcasted from application server (140) with the disaster ID, and is sent to a particular exigency response functionary through SMS.

The database server (130) maintains a resource table which keeps a record of the resources to be alerted activated for each type of disaster. This is adjusted based on the severity of the disaster and the exigency response required.

Based on the severity of the disaster, a configurable table is maintained in the database server (130) that indicates the preset numbers for resource allocation.

Based on the resource table and the configurable table information fetched from the database server (130) the damage assessment module and resource allocation module (141) of the application server (140) determines the severity of the disaster/incident and the appropriate number of resources to be alerted.

The alert and warning generation module (142) issues alert message to the allocated resources through the interface server (110).

The resources connected to the system (100) are expected to acknowledge the alert message within 60 seconds issuing the alert message.

If a resource indicates that it is not ready, it is shown in orange color on the secondary display unit (170b) of the workstation terminal.

If a resource indicates that it is ready, it is shown in green color on the secondary display unit (170b) that indicates that it is for activation.

If there is no alert acknowledgement from any resource, the alert and warning generation module (142) send alert message again every 30 seconds for 3 times through the interface server (110).

The resources that are alerted are filled in the resource table present in database server (130) by the resource allocation module (141) of the application server (140).

The resource table present in the database server (130) is updated and this data is monitored by the modules of the application server (140). The shortest and best path from the resource to be deployed to the destination i.e. the disaster site will be computed by the live data monitoring module (144) in the application server (140) and sent to the workstation terminal.

If the computed shortest route is blocked, an alternate path will be computed and communicated to the resources.

The workstation terminal will sort the resources according to the shortest distance and this be displayed on the primary display unit (170a) to the operator of the workstation terminal for selection.

The operator will activate acknowledged resources from the secondary display unit (170b).

The above information along with the shortest route is sent to the activated resources and respective active position of the deployed resources will be shown on the primary display unit (170a) of the workstation terminal with different graphics.

If the deployed resources are not sufficient, additional resources can be activated from the pool of resources ready to undertake the mission.

For resources like relief materials, a different procedure is to be executed. For instance, if the incident manager requests relief material, then this request will be sent to workstation terminal configured for relief and rehabilitation. The operator manning the relief and rehabilitation workstation terminal allots the material and in turn tags the workstation terminal configured for transport management for transporting relief materials to disaster location.

Similarly, if the incident manager requests to set a medical camp at disaster location, he will send request to the operator manning the workstation terminal configured for medical services to set camp for a certain number of people.

The operator manning the workstation terminal configured for medical services will create a medical camp which consists of different specialties of doctors, nurses, medical kits, ambulance etc., and set a camp- id.

The operator at the medical workstation will request operator at transport workstation for transporting resources to the newly setup medical camp.

Tracking provision is made in the SP shown on the primary display unit (170a) of the workstation terminals to view the deployed resources, such as emergency vehicles, exigency relief equipment, etc. at any point of time related to one particular disaster. • Once the deployed resources complete their mission, the route from disaster site to their specified/home destination is computed and transmitted to them.

• All activated and deployed resource information and disaster related information are stored in the resource table in the database server (130).

An exemplary embodiment of the operation of the entire system for exigency response operations and deployment of resources in the event of a man-made disaster such as fire is described hereinafter. It may be appreciated that the operation of the system is intended merely to facilitate understanding of the invention.

· Disaster information report either comes from a mobile alert send from the mobile phone of a user at the disaster site or through a call-in.

• If the disaster is declared through a phone call, it can be marked out on the workstation terminal (170).

• Based on the mobile phone call, the latitude and longitude along with severity (if mentioned in the voice call) is automatically filled in the disaster declaration widget on the primary display unit (170a) in the workstation terminal.

• If disaster information report is received through the GUI of the user interactive web module/application on the mobile phone of the user, an alert is sent by the alert and warning generation module (142) is sent to the workstation terminal that Fire has happened at a particular location.

· The disaster/incident and the exigency is declared through the 'disaster declaration widget' on the secondary display unit (170b) on the workstation terminal.

• After declaration of the disaster/incident on the workstation terminal, the application server (140) receives the disaster information report, whereupon the damage assessment module (141) allocates a disaster ID for the disaster/incident and fills the information in a live incident table consisting of disaster ID, disaster type, the workstation terminal declaring the disaster and time of disaster. On closure of the disaster/ incident the row in the table having this information will be deleted. • The disaster/incident is then broadcasted from application server (140) with the disaster ID, and is sent to a particular exigency response functionary through SMS.

• The damage assessment module and resource allocation module (141) of the application server (140) determines the severity of the disaster/incident and the appropriate number of resources that could be activated.

• At the outset the alert and warning generation module (142) issues alert message to a predefined number of resources through the interface server (110).

• If a resource replies that it is not ready, it is shown in orange color on the secondary display unit (170b) of the workstation terminal.

· If a resource replies that it is ready, it is shown in green color on the secondary display unit (170b) that indicates that it is for activation.

• If there is no alert acknowledgement from any resource, the alert and warning generation module (142) send alert message again every 30 seconds for 3 times through the interface server (110).

· The resources that are alerted are filled in the resource table present in database server (130) by the resource allocation module (141) of the application server (140).

• The resource table present in the database server (130) is updated and this data is monitored by the modules of the application server (140).

• The shortest and best path from the resource to be deployed to the destination i.e. the disaster site will be computed by the live data monitoring module (144) in the application server (140) and sent to the workstation terminal.

• If the computed shortest route is blocked, an alternate path will be computed and communicated to the resources.

• The workstation terminal will sort the resources according to the shortest distance and this be displayed on the primary display unit (170a) to the operator of the workstation terminal for selection.

• The operator will activate acknowledged resources from the secondary display unit (170b).

• The above information along with the shortest route is sent to the activated resources and respective active position of the deployed resources will be shown on the primary display unit (170a) of the workstation terminal with different graphics.

• If the deployed resources are not sufficient, additional resources can be activated from the pool of resources ready to undertake the mission. • Tracking provision is made in SP shown on the primary display unit (170a) of the workstation terminals to view the deployed resources, such as emergency vehicles, exigency relief equipment, etc. at any point of time related to one particular disaster.

• Once the deployed resources complete their mission, the route from disaster site to their specified/home destination is computed and transmitted to them.

Thus, the system for exigency response operations and deployment of resources in accordance with the present invention serves as a platform for comprehensive response to disasters large and small, natural as well as man-made. The system is capable of connecting with a large number of sensors and systems to collect evidence of a disaster or an event that could lead to a disaster. The data is received in disparate input formats ranging from video to textual and is thereafter stored in dedicated data-base tables and data structures, as necessary, for retrieval, comparison and establishing precedence. This data is also compared with historical data stored in another segment of the data base, so as to be able to generate necessary inferences.

The system enables operators, who essentially are functionaries to execute different tasks in the disaster relief and exigency response operations. Communication is automatically established between groups of operators managing various disciplines, on a requirement basis. The historical data keeping mechanism in the form of a record and replay sub-system that records operator actions, enables those action to be played out at a later point for debrief and analysis.

The system is capable of autonomously activating all the resources needed for the exigency response operations such as rescue and rehabilitation in real time, ensuring minimal loss of life and property. The system is multi server, multi-workstation system, capable of reportage, contexting, layering, comparing, analysing, and interfacing all elements of exigency response operations and deployment of resources therefor.

Throughout this specification the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.

The use of the expression "at least" or "at least one" suggests the use of one or more elements or ingredients or quantities, as the use may be in the embodiment of the invention to achieve one or more of the desired objects or results.

The numerical values mentioned for the various physical parameters, dimensions or quantities are only approximations and it is envisaged that the values higher/lower than the numerical values assigned to the parameters, dimensions or quantities fall within the scope of the invention, unless there is a statement in the specification specific to the contrary.

The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

CLAIMS:

1) A system for real time control of exigency response operations, said system (10) comprising:

• a plurality of nodes organized in a multi-level hierarchy with each node comprising an autonomous command and control system (100) comprising:

^■ an interface server (110) configured to receive data from data sources external to said autonomous command and control system, said data indicating the event of an exigency arising from occurrence of a disaster;

^■ a communication server (120) configured to facilitate flow of data within said autonomous command and control system;

^■ an application server (140) configured to assess damage resulting from occurrence of the disaster and giving rise to the event of the exigency, allocate resources, issue alerts and activate resources for implementing exigency response operations;

^■ an administration server (150) configured to monitor the health of all the servers and manage the operation of all the servers of said autonomous command and control system;

^■ a plurality of workstation terminals (170) each configured to enable monitoring, control and management of exigency response operations in real time;

^■ a database server (130) configured to store data corresponding to the event of the exigency and the implementation of exigency response operations; and

^■ a central storage server (160) configured to store data from said database server as back-up data;

said servers (110-160) selectively communicating with each other and with said plurality of workstation terminals (170) for enabling the real time control of exigency response operations.

2) The system as claimed in claim 1, wherein said multi-level hierarchy is a three level hierarchy with a first level having a single node, a second level having one or more nodes and a third level having a plurality of nodes.

3) The system as claimed in claim 1, wherein:

• said interface server (110) is in communication with said communication server (120) and said administration server (150); said interface server executes an interface module (111), enabling transfer of data between the data sources external to said autonomous command and control system and said servers of said autonomous command and control system, said interface module (111) including:

^■ a data receiver (112) configured to receive said data indicating the event of the exigency from said external data sources;

^■ a data extractor (113) cooperating with said data receiver and configured to extract pre-defined data from said data indicating the event of the exigency; and

^■ a data sender (114) cooperating with said data extractor and configured to transmit the extracted pre-defined data to said communication server (120);

said interface server further executes a web module (115) configured to provide access to said system, said web module being accessible as an external graphical user interface (GUI) on an external portable terminal to enable users of said system to input information pertaining to the occurrence of the disaster and the event exigency therein from a site of the disaster, said information entered in said external GUI being received by said interface module (111).

4) The system as claimed in claim 3, wherein said data indicating the event of the exigency comprises data from sensors including weather sensors providing weather data, water level sensors providing data related to water level in rivers, seismological sensors providing seismological data and landslide data; said extracted pre-defined data includes the data from sensors and data corresponding to information entered in the GUI on the portable terminal and received by said interface module. 5) The system as claimed in claims 1 and 3 wherein:

• said communication server (120) is in communication with said interface server (110), said application server (140), said administration server (150), said plurality of workstation terminals (170), and said database server (130);

• said communication server (120) executes a communications module (121) facilitating flow of data within said autonomous command and control system, said communications module (121) including:

^■ a data receiver (122) configured to receive the extracted pre-defined data transmitted by said data sender (114) of said interface server (110); ^■ a data converter (123) cooperating with said data receiver to convert said extracted pre-defined data to a pre-determined data format and structure;

^■ a validity checker (124) cooperating with said data converter to verify the validity of the structure and format of converted data; and

^■ a data sender (125) cooperating with said validity checker to pre-process the converted data and transmit the pre-processed data to said data base server (130), and also transmit the extracted pre-defined data to said application server (140).

6) The system as claimed in any of claims 1 and 5, wherein:

• said application server (140) is in communication with said communication server (120), said administration server (140), said plurality of workstation terminals (170), and said database server (130);

• said application server (140) executes a plurality of modules for implementing exigency response operations, said modules including:

^■ a damage assessment and resource allocation module (141) configured to assess severity of damage in the event of the exigency based on the extracted pre-defined data received from said communication server (120) and decide on allocation of resources for exigency response operations, and further configured to transmit a record of the event of the exigency, the assessed severity of damage and the allocation of resources to the database server (130); said damage assessment and resource allocation module (141) also configured to transmit the extracted predefined data received from said communications server (120) to said plurality of workstations;

^■ an alert and warning generation module (142) configured to interpret the extracted pre-defined data received from said communication server (120) and generate warning and alerts indicating the event of the exigency, said warning being transmitted to said plurality of workstation terminals (170), said alerts being transmitted to external resource providers connected to said system;

^■ an emergency vehicle guidance alert module (143) cooperating with said damage assessment and resource allocation module (141) and configured to analyze the resources allocated for exigency response operations, and generate activation commands for deployment of the allocated resources and guidance commands for guiding each allocated resources to the site of the disaster, said activation commands and guidance commands being transmitted to each allocated resource deployed for exigency response operations;

a live data monitoring module (144) cooperating with said emergency vehicle guidance alert module and with a geographic information system (GIS), and configured to compute a shortest and a fastest path between the site of the disaster and a location of each allocated resource, said shortest and fastest path being transmitted to each allocated resource deployed for exigency response operations; said emergency vehicle guidance alert module (143) further configured to match a resource at a location closest to the site of the disaster and generate activation and guidance commands based on a successful match;

a disaster information and incident log module (145) cooperating with said damage assessment and resource allocation module, said alert and warning generation module, emergency vehicle guidance alert module and said live data monitoring module, to chronologically log the event of the exigency and exigency response operations carried out;

a historic data analysis module (146) cooperating with said disaster information and incident log module and configured to analyze the event of the exigency and exigency response operations to aid each of said damage assessment and resource allocation module, said alert and warning generation module, emergency vehicle guidance alert module and said live data monitoring module in performing functions thereof.

7) The system as claimed in claim 1, wherein:

• said administration server (150) is in communication with said interface server (110), said communication server (120), said application server (140), said plurality of workstation terminals (170), and said database server (130), and said central storage server (160);

• said administration server (150) executes a plurality of modules for monitoring the health of all said servers (110-160) and managing the operation of all said servers of said autonomous command and control system, said modules including:

^■ a network management module (151) configured to observe the status of all said servers (110-160) and the workstation terminals (170) by receiving a 'heart-beat' signal from each server to monitor a plurality of parameters of each server, said parameters including CPU occupancy, memory status, module status and module failure;

^■ a time server module (152) configured to setup each server and set parameters of each server, said time server module accessible through an internal GUI on at least one display unit of a workstation terminal or on a display unit of said administration server to enable setting up of the server;

^■ an access module (153) cooperating with said network management module and said time server module to provide permission for logging onto said system through said workstation terminals.

8) The system as claimed in claim 1, wherein:

• each of said plurality of workstations (170) is in communication with said communication server (120), said application server (140), said administration server (150), said database server (130) and said central storage server (160);

• each workstation terminal (170) executes an interactive module (170c) configured to enable an operator to control and manage exigency response operations and deployment of resources;

• at least one workstation in communication with said communication server (120) receives the extracted pre-defined data transmitted by said damage assessment and resource allocation module (141) of said communications server (120), to enable generation of a report therein of the occurrence of the disaster to enable said damage assessment and resource allocation module (141) to assess the severity of damage;

• each workstation terminal comprises a primary display unit (170a) displaying a situation picture of the event of exigency and the exigency response operations, and a secondary display unit (170b) displaying a GUI to facilitate access to the system,

• said situation picture displayed on said primary display unit shows:

^■ GIS layers (170aj),

^■ depiction of the disaster (170a₂),

^■ resource tracking through GPS (170a₃),

^■ activated resources per disaster (170a₄),

^■ alerts and warnings with geo-tags (170as),

^■ data from sensors (170a₆),

^■ the shortest and fastest path for the allocated resource (170a₇), and ^■ prominent landmarks near the site of disaster (170as);

• said GUI displayed on said secondary display unit includes:

^■ tabs for disaster declaration (170M),

^■ activation and de-activation of resources (170_b2),

^■ monitoring of the declared disaster/event of exigency (170_b3),

^■ resource tracking (170Μ),

^■ insertion and updation of data (170_bs) in said database server,

^■ data from sensors (170b6),

^■ alerts and warnings (170b7), and

^■ login authentication (170_bs) for logging into said system.

9) The system as claimed in claim 1, wherein:

• said database server (130) is in communication with said communication server (120), said application server (140), said administration server (150), said plurality of workstations (170), and said central storage server (160);

• data stored by said database server (130) includes the data from sensors, geo-spatial and relational data (131), incremental back-ups (132) of all data, and logs of the disaster and the event of exigency (134);

• said database server (130) is configured to execute a replication module (133) enabling hot standby replication in the form of incremental backups, said replication module configured to update data concurrently across all said servers (110-160) of said autonomous command and control system.

10) The system as claimed in claim 1, wherein:

• said central storage server (160) is in communication with said administration server (150), said plurality of workstations (170), and said database server (130);

• said central storage server (160) is configured as a backup storage server to stored data received from said database server, said administration server and said plurality of workstations;

• said central storage server (160) is configured to execute a replication module enabling hot standby replication in the form of incremental backups, said replication module configured to update data concurrently across all said servers (110-160) of said autonomous command and control system. 11) A method for real time control of exigency response operations, the method comprising the following steps:

• verifying the validity of the structure and format of converted data;

• generate warning and alerts indicating the event of the exigency;

· chronologically logging the event of the exigency and exigency response operations carried out.

12) The method as claimed in claim 11, wherein the step of generate warning and alerts includes acknowledging the alert in a pre-determined time.

13) The method as claimed in claim 12, wherein the pre-determined time is sixty seconds.

14) The method as claimed in claim 11, wherein the step of computing the shortest and fastest path includes matching a resource at a location closest to the site of the disaster and generating activation and guidance commands based on a successful match. 15) The method as claimed in claim 11, wherein the step of assessing severity of damage includes generating a report of the occurrence of the disaster for assessing severity of damage. 16) The method as claimed in claim 11, wherein the step of chronologically logging the event of the exigency includes storing the extracted pre-defined data.