|
(11) | EP 4 134 926 A1 |
| (12) | EUROPEAN PATENT APPLICATION |
|
|
|
|
||||||||||||||||||||||||
| (54) | A COMPUTER IMPLEMENTED METHOD FOR GENERATING AN EVACUATION MANIFEST |
| (57) The present invention relates to a computer implemented method (100) for generating
an evacuation manifest for a rescue vessel of a mother ship. The method (100) comprising:
upon persons embarking the rescue vessel, registering (S102) identification information
of the persons embarking the rescue vessel by scanning individual identification tags
associated with the respective persons embarking the rescue vessel using an identification
tag sensor, thereby generating the evacuation manifest, and storing (S104) the generated
evacuation manifest.
|
Technical field
[0001] The present invention relates to maritime safety. More particularly, it relates to a method for generating an evacuation manifest for a rescue vessel.
Background of the invention
[0002] Over the past century a multitude of maritime casualties as a result of abandon-ship events, such as the Titanic, Scandinavian Star, Costa Concordia, have changed the perception of onboard safety. Technology in the shipping industry has advanced in various sectors, for example in navigational systems. These are a common sight in a modern bridge where there are various systems assisting the navigator towards the safety of the crew, passengers, and the vessel. Radars equipped with ARPA, which have the ability to detect accurately and plot targets several miles ahead, satellite-based radio navigation systems (RNSS) such as GPS, GLONASS, GALILEO give the opportunity to the watch keeping officer to know the exact position of the vessel with high accuracy, communication means (e.g. VHF, MF/HF) which ease the conciliation between vessels in many dangerous circumstances, Automatic Identification System (AIS) which gives the opportunity to the Officer on Watch (OOW) to access information about vessels in the surrounding vicinity and most recently the mandatory installation of ECDIS in many types of vessels give a better view of vessel's position and monitoring of the followed route.
[0003] Today, a significant number of quite advanced technology applications also support safety at sea. Unfortunately, the manifestation of passengers during an evacuation scenario has not followed a similar path of improvement, when compared to the counterpart Life Saving Appliances (LSA) Code. Embarkation and muster proceedings are still following similar approaches that were established during the early 1900s. There have been relatively few advances in these procedures; most often, they include manually checking-in the passengers on electronic systems, along with "on the spot" completion of check-off lists and passenger counts, allowing for an influx of potential error by the pressured crew. Furthermore, the transmission of the manifest to a Maritime Rescue Coordination Centre (MRCC) is often associated with a considerable amount of time, or even involving secondary passenger counts, after the disembarkation event has been concluded.
[0004] Thus, there is a need for improvements within this field. In particular, improvements related to the procedure of embarkation of lifeboats.
Summary of the invention
[0005] In view of the above, it is an object of the present invention to provide a method for generating an evacuation manifest for a rescue vessel of a mother ship and a system thereof.
[0006] It has been realized that by utilizing a data keeping and transmitting system employing the use of sensors at an entrance of the rescue vessel, the evacuation procedure can be performed more effectively, and critical time can be saved during an evacuation event.
[0007] According to a first aspect, a computer implemented method for generating an evacuation manifest for a rescue vessel of a mother ship is provided. The method comprising: upon persons embarking the rescue vessel, registering identification information of the persons embarking the rescue vessel by scanning individual identification tags associated with the respective persons embarking the rescue vessel using an identification tag sensor, thereby generating the evacuation manifest, and storing the generated evacuation manifest.
[0008] The identification information may comprise a personal identification of the person. It may further comprise other personal information associated with the person, such as place of residence, medical information, contact information to an emergency contact or the like.
[0009] A possible associated advantage is that the evacuation procedure may be performed more effectively since the persons can embark the rescue vessel immediately, without having to gather at mustering stations to be accounted for. The evacuation time is further shortened by avoiding buildup at the rescue vessel which can cause delays. Such buildup may happen as a result of gathering a group of people at a mustering station before allowing them to embark the rescue vessel. By the proposed method, this can be avoided.
[0010] The generated evacuation manifest may be stored locally at the rescue vessel. Storing the generated evacuation manifest of the persons onboard of the rescue vessel locally on the rescue vessel may allow a rescue unit to directly learn who is on the rescue vessel and if there may be persons with critical medical conditions onboard.
[0011] The method may further comprise transmitting, via an onboard network, the generated evacuation manifest to a bridge monitor of the ship. This may be advantageous in that for instance a captain or Master of the ship, can oversee the evacuation procedure without having to interfere with the procedure by having to communicate with a rescue vessel commander involved in the embarkation of the rescue vessel.
[0012] The generated evacuation manifest may be continuously transmitted to the bridge monitor in real-time, as the persons are embarking the rescue vessel. This may be advantageous in that the captain or Master of the ship, or any other person overseeing the evacuation process, can get a live view of how the evacuation procedure proceeds and detect any possible delays.
[0013] The method may further comprise transmitting, via long-range wireless communication, the generated evacuation manifest to a rescue center. A possible associated advantage may be that the rescue center gets a clear view of which persons have evacuated and which persons could be remaining on the mother ship. Thus, there is no need to search blindly for passengers remaining or having to wait for a confirmed countdown of the persons having embarked the rescue vessel. The rescue efforts can thus be performed more effectively and focused on the most critical tasks.
[0014] The act of transmitting the generated evacuation manifest to a rescue center may be performed in response to a launch of the rescue vessel. A possible associated advantage is that the required bandwidth can be reduced by transmitting the evacuation manifest only once when is has been launched. Further, the receiver of the evacuation manifest can get a clear view of which persons have embarked the rescue vessel, and which persons may be still onboard the mother ship.
[0015] The method may further comprise displaying, on a display associated with the rescue vessel, information pertaining to the generated evacuation manifest. The display may allow the commander of the rescue vessel to monitor the embarkation procedure on the site.
[0016] The method may further comprise transmitting the generated evacuation manifest to another rescue vessel of the mother ship. The evacuation manifest may be displayed on a display associated with the another rescue vessel. A possible associated advantage may be that the evacuation manifests can be synchronized between different rescue vessels. This may allow the persons onboard the mother ship to embark any rescue vessel. It may also allow the commander of the rescue vessel to check which persons has embarked the another rescue vessel.
[0017] According to a second aspect, a system for generating an evacuation manifest for a rescue vessel of a mother ship is provided. The system comprising: an identification tag sensor located at an embarkation entrance of the rescue vessel and configured to register identification information of persons embarking the rescue vessel through the embarkation entrance by scanning individual identification tags associated with the respective persons embarking the rescue vessel, a controller communicatively connected to the identification tag sensor and configured to generate the evacuation manifest from the registered identification information, and a storage device communicatively connected to the controller and configured to store the generated evacuation manifest.
[0019] The system may further comprise an external communication device, communicatively connected to the controller, and configured to transmit the evacuation manifest to one or more external receivers.
[0020] The identification tag sensor may be provided along one or more sides of the embarkation entrance of the rescue vessel. The identification tag sensor may be provided on or in a bulkhead of the rescue vessel. The identification tag sensor may be provided on or in a deck of the rescue vessel. In case the identification tag sensor is provided on or in a bulkhead and/or on or in a deck, the identification tag sensor may be provided in proximity of the embarkation entrance of the rescue vessel. By in proximity is meant within a meter from the embarkation entrance of the rescue vessel.
[0021] The identification tag sensor may be a Radio Frequency Identification (RFID) tag sensor or a Near-Field Communication (NFC) tag sensor.
[0022] The external communication device may be a long-range wireless communication device, such as a long-range radio antenna, satellite data link or cellular network antenna.
[0023] The system may further comprise a display associated with the rescue vessel, the display being communicatively connected to the controller and configured to display information pertaining to the generated evacuation manifest. The display may be provided as a display mounted on the rescue vessel, or as a mobile device.
[0024] The external communication device may be configured to transmit the generated evacuation manifest to a rescue center.
[0025] The system may further comprise an on-board communication device communicatively connected to the controller and configured to transmit the generated evacuation manifest to a bridge monitor of the mother ship.
[0027] The above-mentioned features and advantages of the first aspect, when applicable, apply to the second aspect as well. To avoid undue repetition, reference is made to the above.
[0028] Still other objectives, features, aspects, and advantages of the invention will appear from the following detailed description as well as from the drawings. The same features and advantages described with respect to one aspect are applicable to the other aspects unless explicitly stated otherwise.
Brief description of the drawings
[0029] The above and other aspects of the present inventive concept will now be described in more detail, with reference to appended drawings showing variants of the invention. The figures should not be considered limiting the invention to the specific variant; instead they are used for explaining and understanding the inventive concept.
[0030] As illustrated in the figures, the sizes of layers and regions are exaggerated for illustrative purposes and, thus, are provided to illustrate the general structures of variants of the present inventive concept. Like reference numerals refer to like elements throughout.
Fig. 1 is a flow chart illustrating the steps of a computer implemented method for generating an evacuation manifest.
Fig. 2 schematically illustrates a system for generating an evacuation manifest.
Fig. 3 shows, by way of example, a rescue vessel equipped with the system for generating an evacuation manifest.
Fig. 4a and 4b shows additional examples of the rescue vessel equipped with the system for generating an evacuation manifest.
Detailed description
[0031] The present inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which currently preferred variants of the inventive concept are shown. This inventive concept may, however, be implemented in many different forms and should not be construed as limited to the variants set forth herein; rather, these variants are provided for thoroughness and completeness, and fully convey the scope of the present inventive concept to the skilled person.
[0032] A computer implemented method and system for generating an evacuation manifest for a rescue vessel of a mother ship will now be described with reference to Fig. 1 to Fig. 4.
[0033] Fig. 1 is a flow chart illustrating the steps of the method 100. Below, the different steps is described in more detail. Even though illustrated in a specific order, the steps of the method 100 may be performed in any suitable order, as well as multiple times.
[0034] Upon persons embarking a rescue vessel, identification information of the persons embarking the rescue vessel is registered S102. The identification information is registered S102 by scanning individual identification tags associated with the respective persons embarking the rescue vessel using an identification tag sensor. By registering the identification information of the persons embarking the rescue vessel, the evacuation manifest is generated.
[0036] The generated evacuation manifest may be transmitted S106 to a bridge monitor of the mother ship. The evacuation manifest may be transmitted S106 via an onboard network. As an example, the evacuation manifest may be transmitted wirelessly, e.g. over Wi-Fi. Alternatively, the evacuation manifest may be transmitted over wired communication through the mother ship.
[0037] The transmission S106 of the evacuation manifest may be performed continuously as the persons are embarking the rescue vessel. Put differently, the evacuation manifest may be transmitted in real-time to the bridge monitor. In one example, the registered identification data may be transmitted to the bridge monitor and thereby generating the evacuation manifest on the bridge monitor.
[0038] The evacuation manifest may be transmitted to and stored on a Voyage data recorder (VDR), or Vessel data recorder, of the mother ship.
[0039] The generated evacuation manifest may be transmitted S108, via long-range wireless communication, to a rescue center, such as a maritime rescue coordination center (MRCC).
[0040] The generated evacuation manifest may be transmitted S108 in response to a launch of the rescue vessel.
[0041] Information pertaining to the generated evacuation manifest may be displayed S110, on a display associated with the rescue vessel.
[0042] Fig. 2 illustrates a system 200 for generating an evacuation manifest for a rescue vessel of a mother ship.
[0043] The system 200 comprises an identification tag sensor 202. The identification tag sensor 202 may be located at an embarkation entrance of the rescue vessel. The identification tag sensor 202 may be configured to register identification information of persons embarking the rescue vessel through the embarkation entrance by scanning individual identification tags associated with the respective persons embarking the rescue vessel. The individual identification tags may for instance be Radio Frequency Identification (RFID) tags or Near-Field Communication (NFC) tags carried by the persons on the ship. As an example, the RFID individual identification tags can be carried on a wrist of the persons. The identification tag sensor 202 may thus be a RFID or NFC tag sensor or reader. The identification tag sensor 202 may be provided along one or more sides of an embarkation entrance of the rescue vessel which is further described in connection with Fig. 3 and Fig. 4a-4b.
[0044] The system 200 further comprises a controller 204. The controller 204 may be communicatively connected to the identification tag sensor 202. The controller 204 may be configured to control functions of other devices which are a part of the system 200. The controller 204 may be configured to carry out overall control of functions and operations of the system 200. The controller 204 may include a processor, such as a central processing unit (CPU), microcontroller, or microprocessor. The processor may be configured to execute program code stored in the memory, in order to carry out functions and operations of the system 200. The memory may be one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, a random access memory (RAM), or another suitable device. In a typical arrangement, the memory may include a non-volatile memory for long term data storage and a volatile memory that functions as system memory for the control circuit. The memory may exchange data with the processor over a data bus. Accompanying control lines and an address bus between the memory and the processor also may be present. Functions and operations of the controller 204 may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) that are stored on a non-transitory computer readable recording medium (e.g., the memory) of the controller 204 and are executed by the processor. Furthermore, the functions and operations of the controller 204 may be a stand-alone software application or form a part of a software application that carries out additional tasks related to the controller. The described functions and operations may be considered a method that the corresponding device is configured to carry out. Such as the method discussed above in connection with Fig. 1. Also, while the described functions and operations may be implemented in software, such functionality may as well be carried out via dedicated hardware or firmware, or some combination of hardware, firmware and/or software. The controller 204 may be configured to generate the evacuation manifest from the registered identification information.
[0045] The system 200 further comprises a storage device 206 communicatively connected to the controller 204. The storage device 206 may be configured to store the generated evacuation manifest locally at the rescue vessel. As an example, the storage device 206 may be a hard drive or a flash memory device such as a Solid-State Drive, SSD.
[0046] The system 200 may further comprise an external communication device 208 communicatively connected to the controller 204. The external communication device 208 may be configured to communicate with external receivers. By external receivers it is hereby meant receivers that is not part of the rescue vessel or the mother ship. As an example, the external receivers may be a rescue center on the shore. The external communication device 208 may for instance transmit the evacuation manifest to the rescue center. The transmission of the evacuation manifest may be performed in response to a launch of the rescue vessel. Another example of external receiver may be other ships or rescue vehicles taking part in the rescue operation.
[0047] The external communication device 208 may be a long-range wireless communication device. As an example, it may be a long-range radio antenna, a satellite data link or cellular network antenna.
[0048] The system 200 may further comprise a display 210 associated with the rescue vessel and communicatively connected to the controller 204. The display 210 may be configured to display information pertaining to the generated evacuation manifest. The display 210 may allow a rescue vessel commander, in charge of the rescue vessel, to monitor the embarkation procedure in real-time. The rescue vessel commander may be a person in charge of the embarkation procedure of the rescue vessel.
[0049] The system 200 may further comprise an on-board communication device 212 communicatively connected to the controller 204. By on-board communication device 212 it is herein meant that the communication device is configured to communicate with other device on board of the mother ship, in contrast to the external communication device 208. However, is should be noted that the external communication device 208 and the on-board communication device 212 may be the same device.
[0050] The on-board communication device 212 may be configured to transmit the evacuation manifest to a bridge monitor of the mother ship. The transmission of the evacuation manifest to the bridge monitor may be done via an on-board network. It may be done either wirelessly of over a wired connection. The transmission of the evacuation manifest to the bridge monitor may be performed in real-time, as the persons are embarking the rescue vessel. Put differently, a live feed of the embarkation procedure may be provided to the bridge monitor allowing the Master of the ship to oversee the procedure.
[0051] The on-board communication device 212 may further communicate with other rescue vessels of the mothership, either directly or via the bridge. This may allow the evacuation manifest of multiple rescue vessels to be synchronized. The synchronized evacuation manifests may then be compared to the passenger manifest of the mother ship to determine which passengers may be left on the mother ship. A further advantage may be that the persons can embark any rescue vessel. Put differently, is it not necessary for the person to go to a pre-assigned rescue vessel. This will allow for a quicker embarkation procedure for at least two reasons. The first being that the person can go to the nearest possible rescue vessel. The second being that the launch of the rescue vessel can be done quicker since there is no need to wait for a specific person which is assigned to that rescue vessel. In other words, the rescue vessel can just be filled with the persons that are nearby.
[0052] The system 200 may comprise a backup power supply 214. The backup power supply 214 may for instance be a battery pack or a power generator. The backup power supply 214 may allow the evacuation manifest to be generated even if the mother ship suffers a power loss. Further, the backup power supply 214 may allow the external communication device 208 to transmit the evacuation manifest, or other data when the rescue vessel has been launched and no longer can receive power from the mother ship.
[0053] Fig. 3 illustrates, by way of example, a rescue vessel 300 equipped with the system 200 described in connection with Fig. 2.
[0054] In this example, the rescue vessel 300 comprises a first embarkation entrance 302a and a second embarkation entrance 302b. It should be noted that the rescue vessel may have any number of embarkation entrances.
[0055] An identification tag sensor 202 may be provided on the first and second embarkation entrance 302a, 302b respectively. The identification tag sensor 202 may be provided on any side of the embarkation entrance. For example, the identification tag sensor 202 may comprise two parts which are provided along two opposite sides of the embarkation entrance as illustrated on the first embarkation entrance 302a. Such a configuration may be advantageous in that increases the reading success of the individual identification tags, compared to having the identification tag sensor only on one side of the embarkation entrance. At the same time, the material cost is kept low. As illustrated on the second embarkation entrance 302b, the identification tag sensor may be provided along a top and bottom of the embarkation entrance. Further illustrates is that the identification tag sensor 202 may be of different sizes. Additional examples of how the identification tag sensor 202 can be provided is further discussed in connection with Fig. 4a and 4b.
[0056] It is hereby noted that the way the identification tag sensor 202 is illustrated is only for illustrative purposes. The identification tag sensor 202 may have any size and shape suitable for the cause. Further, the identification tag sensor 202 may be incorporated into the sides of the embarkation entrance such that it is not visible and is protected from the surrounding environments.
[0057] The rescue vessel 300 may further comprise the display 210 as described in connection with Fig. 2. The display 210 may be provided on the rescue vessel 300 as illustrates herein, and preferably in connection with the embarkation entrances 302a, 302b. Alternatively, the display 210 may be a mobile device, such as a tablet. The mobile device may be stored on or in connection with the rescue vessel when not in use. Upon beginning an embarkation procedure, the mobile device may be collected by a rescue vessel commander in charge of the rescue vessel.
[0058] The rescue vessel 300 may further comprise the external communication device 208 as described in connection with Fig. 2. The external communication device 208 may be provided on an outside of the rescue vessel as illustrates herein, in order to increase a communication quality. The external communication device 208 may be fixed on the rescue vessel 300. Alternatively, the external communication 208 may be detachably provided on the rescue vessel 300. For example, the external communication device 208 may be attached to the rescue vessel 300 with a magnetic mount. Having the external communication device 208 detachably provided on the rescue vessel 300 allows the external communication device 208 to be installed on the rescue vessel 300 without having to modifying the rescue vessel. As described above, the external communication device 208 may for instance communicate with a rescue center 304.
[0059] The rescue vessel 300 further comprises the controller 204 as described in connection with Fig. 2. The controller 204 may be provided inside of the rescue vessel 300 as illustrated by the dashed lines.
[0060] The rescue vessel 300 may further comprise the on-board communication device 212 as described in connection with Fig. 2. The on-board communication device 212 may communicate with the bridge monitor 306 as described above.
[0061] The rescue vessel 300 may further comprise the storage device 206 as described in connection with Fig. 2.
[0062] The rescue vessel 300 may further comprise the backup power supply 214 as described in connection with Fig. 2.
[0063] Fig. 4a and 4b illustrates the rescue vessel 300 as described in connection with Fig. 3 but with additional examples of the embarkation entrance and identification tag sensor.
[0064] In the example of Fig. 4a, the rescue vessel 300 is illustrated with one large embarkation entrance 302c. In such an example, the persons may embark the rescue vessel by climbing in at any point along the side of the rescue vessel. The identification tag sensor 202 may then primarily be provided along the bottom side of the embarkation entrance 302c in order to register all persons embarking the rescue vessel 300. The identification tag sensor 202 may be provided along other parts of the embarkation entrance 302c as well. For example, at a bottom section of the sides of the embarkation entrance 302c as herein illustrated.
[0065] In the example of Fig. 4b, the rescue vessel 300 is illustrated having a smaller embarkation entrance 302d. In such an example, the identification tag sensor 202 may be provided on all sides of the embarkation entrance 302d as illustrated herein.
[0066] The identification tag sensor 202 may be provided on or in a bulkhead of the rescue vessel 300. The identification tag sensor 202 may be provided in a proximity of the embarkation entrance of the rescue vessel. 300. The identification tag sensor 202 may be provided on or in a deck of the rescue vessel 300. The identification tag sensor 202 may be provided on or in a roof of the rescue vessel 300. The identification tag sensor 202 may be provided at an entrance of a slide leading into the rescue vessel 300. Hence, the embarkation entrance may be an entrance to a slide leading into the rescue vessel 300.
1. A computer implemented method (100) for generating an evacuation manifest for a rescue
vessel of a mother ship, the method comprising,
upon persons embarking the rescue vessel, registering (S102) identification information of the persons embarking the rescue vessel by scanning individual identification tags associated with the respective persons embarking the rescue vessel using an identification tag sensor, thereby generating the evacuation manifest,
storing (S104) the generated evacuation manifest.
2. The method (100) according to claim 1, further comprising transmitting (S106), via
an onboard network, the generated evacuation manifest to a bridge monitor of the mother
ship.
3. The method (100) according to claim 2, wherein the generated evacuation manifest is
continuously transmitted to the bridge monitor in real-time, as the persons are embarking
the rescue vessel.
4. The method (100) according to any one of claims 1 to 3, further comprising transmitting
(S108), via long-range wireless communication, the generated evacuation manifest to
a rescue center.
5. The method (100) according to claim 4, wherein the act of transmitting (S108) the
generated evacuation manifest to a rescue center is performed in response to a launch
of the rescue vessel.
6. The method (100) according to any one of claims 1 to 5, further comprising displaying
(S110) on a display associated with the rescue vessel information pertaining to the
generated evacuation manifest.
7. A system (200) for generating an evacuation manifest (308) for a rescue vessel (300)
of a mother ship, the system (200) comprising:
an identification tag sensor (202) located at an embarkation entrance (302a-d) of the rescue vessel (300) and configured to register identification information of persons embarking the rescue vessel (300) through the embarkation entrance (302a-d) by scanning individual identification tags associated with the respective persons embarking the rescue vessel (300),
a controller (204) communicatively connected to the identification tag sensor (202) and configured to generate the evacuation manifest (308) from the registered identification information, and
a storage device (206) communicatively connected to the controller (204) and configured to store the generated evacuation manifest (308).
8. The system (200) according to claim 7, wherein the system (200) further comprises
an external communication device (208), communicatively connected to the controller
(204), and configured to transmit the evacuation manifest (308) to one or more external
receivers.
9. The system (200) according to claim 7 or 8, wherein the identification tag sensor
(202) is provided along one or more sides of the embarkation entrance (302a-d) of
the rescue vessel (300).
10. The system (200) according to any one of claims 7 to 9, wherein the identification
tag sensor (202) is a Radio Frequency Identification (RFID) tag sensor or a Near-Field
Communication (NFC) tag sensor.
11. The system (200) according to any one of claims 7 to 10, wherein the external communication
device (208) is a long-range wireless communication device, such as a long-range radio
antenna, satellite data link or cellular network antenna.
12. The system (200) according to any one of claims 7 to 11, further comprising a display
(210) associated with the rescue vessel (300), the display (210) being communicatively
connected to the controller (204) and configured to display information pertaining
to the generated evacuation manifest (308).
13. The system (200) according to any one of claims 7 to 12, wherein the external communication
device (208) is configured to transmit the generated evacuation manifest to a rescue
center (304).
14. The system (200) according to any one of claims 7 to 13, further comprising an on-board
communication device (212) communicatively connected to the controller (204) and configured
to transmit the generated evacuation manifest (308) to a bridge monitor of the mother
ship.
15. The system (200) according to any one of claims 7 to 14, wherein the system (200)
further comprises a backup power supply (214).