KR100815432B1 - System and method for managing business disaster, and medium for storing computer readable program for executing the method - Google Patents

Abstract

Disclosed are a business disaster management system, a method, and a medium having recorded thereon a computer readable program for executing the method. The project disaster management system includes a disaster occurrence information transmitter, a person in charge task information transmitter, and a disaster situation transmitter. The disaster occurrence information transmission unit transmits the disaster occurrence information to a pre-registered notification communication terminal when receiving a predetermined disaster occurrence input. The person in charge task information transmission unit transmits the person in charge task information registered in advance to the connected person terminal. The disaster situation information transmission unit transmits the disaster situation information to a predetermined manager terminal when the disaster situation information is input from the person in charge of the person in charge. In the event of a disaster, it is possible to respond quickly and effectively to disasters by communicating disaster facts and missions to the person in charge, and by reporting the disaster response status reported by the person in charge to the manager.

Business Disaster, Accident Management, Mock Training, Disaster Management, Network Camera

Description

System and method for managing business disaster, and medium for storing computer readable program for executing the method}

1 is a schematic diagram illustrating a state of use of one embodiment of a business disaster management system in accordance with the present invention;

2 is a schematic block diagram of the business disaster management system of FIG. 1;

FIG. 3 is a diagram illustrating an initial screen of a web page provided by the business disaster management system of FIG. 2.

4 to 25 are web page screens for performing the accident management function of FIG.

26 to 48 are web page screens for performing the simulation training function of FIG.

49 to 67 are web page screens for performing the disaster management function of FIG.

68 is a schematic flowchart for carrying out an embodiment of a business disaster management method according to the present invention.

FIG. 69 is a flowchart detailing the disaster management step of FIG. 68; FIG.

The present invention relates to a system and a method for continuously operating a business, and more particularly, to a system and a method for maintaining the continuity of a business by effectively managing disasters that may occur during the operation of the business.

In the operation of a business, continuity has a very important meaning not only for the business owner and employees but also for the other party of the business. However, accidents that may occur during the operation of a business can interrupt its continuity, especially disasters, which can be called large accidents.

For this reason, the operator of a project must prepare for disaster by devising measures to effectively manage such disasters and ensure the continuity of the project.

It is an object of the present invention to provide a system, a method capable of effectively managing an accident that may occur during the operation of a business, particularly a disaster, and a medium having a computer readable program for executing the method.

In order to achieve the above object, the business disaster management system according to the present invention includes a disaster occurrence information transmitter, a person in charge task information transmitter, and a disaster situation transmitter.

The disaster occurrence information transmission unit transmits the disaster occurrence information to a pre-registered notification communication terminal when receiving a predetermined disaster occurrence input. The person in charge task information transmission unit transmits the person in charge task information registered in advance to the connected person terminal. The disaster situation information transmission unit transmits the disaster situation information to a predetermined manager terminal when the disaster situation information is input from the person in charge of the person in charge.

In the event of a disaster, it is possible to respond quickly and effectively to disasters by communicating disaster facts and missions to the person in charge, and by reporting the disaster response status reported by the person in charge to the manager.

The business disaster management system may further include a disaster situation response information transmission unit for transmitting the disaster situation response information input from the manager terminal to the connected person in charge. As a result, it is possible to effectively respond to unexpected accidents as well as performing a predetermined task.

The apparatus may further include a local situation detection device configured to detect and input a situation of an area installed and installed at a predetermined location, wherein the local situation detection device may be a network camera. The local situation detection device enables the real-time situation of the disaster area to be grasped in real time even in situations where personnel can not report quickly.

The apparatus may further include an emergency contact network information transmitting unit configured to transmit emergency contact network information registered in advance to the manager terminal. Pre-registration of emergency contact information for staff is made available if needed.

The disaster situation information may include a performance state of a person in charge of performing a task, and the project disaster management system may further include a disaster response evaluation storage unit storing a disaster response evaluation input received from a predetermined evaluator terminal. By reporting the performance status of the mission, the staff can systematically understand the disaster response status, and by inputting the disaster response evaluation, it is possible to evaluate the disaster response activity.

The business disaster management system may further include a report storage unit for storing a disaster status report input from the connected person in charge. By saving a report on the disaster situation, it can be used later as data for disaster response.

In addition, certain disasters may include simulated disasters for conducting simulated training. By conducting simulation training on virtual disasters like this, it is possible to respond more effectively when an actual disaster occurs.

The business disaster management system may further include an accident management data storage configured to store management data about an accident not included in a predetermined disaster. This makes it possible to later use data on minor accidents that do not lead to disaster.

In addition, an invention claiming the invention of the system in the form of a method and a medium invention recording a computer readable program for performing the method are disclosed.

Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings.

1 is a schematic diagram illustrating a use state of an embodiment of a business disaster management system according to the present invention.

In FIG. 1, the business disaster management system 100 is connected to the notification communication terminal 200, the person in charge of the terminal 300, the manager terminal 400, the evaluator terminal 500, and the network camera 600 through the communication network 700. It is.

In this embodiment, the disaster management system 100 is implemented as a server, the person in charge of the terminal 300, the manager terminal 400, the evaluator terminal 500 is implemented as a computer terminal. The computer terminal may be preset as a specific terminal, but may be specified in such a manner that a general purpose computer terminal connected to the disaster management system 100 by the communication network 700 performs a login procedure.

The communication network 700 is a wired or wireless communication network including an internet network, and the notification communication terminal 200 is implemented as a mobile communication terminal. Although the notification communication terminal 200 in FIG. 1 is implemented as a mobile communication terminal, in another embodiment, the notification communication terminal 200 may be implemented as a computer terminal as well as any other communication terminal that can be considered by those skilled in the art.

The network camera 600 is a device that detects visual information of an installed area, and may be a web camera as well as other types of remote assisted cameras capable of controlling the camera remotely through a communication network. In addition, in another embodiment, it may be replaced or installed with other types of sensing devices for sensing audio information, temperature information, pressure information and the like.

FIG. 2 is a schematic block diagram of the business disaster management system of FIG. 1.

The business disaster management system 100 of FIG. 2 includes a disaster occurrence information transmitter 110, a person performing task information transmitter 120, a disaster situation transmitter 130, a disaster response information transmitter 140, and a local situation. The sensing device 150, an emergency contact network information transmitter 160, a disaster response evaluation storage unit 170, a report storage unit 180, and an accident management data storage unit 190 are included.

Each component constituting the business disaster management system 100 except for the local situation detection apparatus 150 may be integrally configured or implemented as a separate device, and may be implemented in hardware as well as software.

The disaster occurrence information transmitter 110 transmits the disaster occurrence information to a pre-registered notification communication terminal when a predetermined disaster occurrence input is received. The person performing task information transmitting unit 120 transmits the person performing task information registered in advance to the connected person terminal. The disaster situation information transmitting unit 130 transmits the disaster situation information to a predetermined manager terminal when the disaster situation information is input from the person in charge of the terminal.

The disaster response information transmitting unit 140 transmits the disaster response information input from the manager terminal to the connected person in charge. The local situation detecting apparatus 150 detects and inputs a situation of an area installed and installed at a predetermined position. In this case, the local situation detecting apparatus 150 may be a network camera. In particular, when a network camera is installed, video conferencing is also possible.

The emergency contact network information transmission unit 160 transmits emergency contact network information registered in advance to the manager terminal. The disaster response evaluation storage unit 170 stores a disaster response evaluation input received from a predetermined evaluator terminal.

The report storage unit 180 stores the disaster status report input from the connected person in charge. The accident management data storage unit 190 stores management data about an accident not included in a predetermined disaster.

Here, the disaster status information may include the performance status of the person in charge of performing the task, and the predetermined disaster may include a simulation disaster for conducting the simulation training.

With such a configuration, it is possible to respond to disasters quickly and effectively by transmitting disaster facts and missions to the person in charge when a disaster occurs, and by delivering the disaster response situation reported from the person in charge to the manager.

FIG. 3 is a diagram illustrating an initial screen of a web page provided by the business disaster management system of FIG. 2.

In FIG. 3, the Business Disaster Manager (BDM) implemented in the web page to provide a disaster management service is composed of Incident management, Simulation, and Disaster management. .

The user may select a desired function on the screen of FIG. 3 and move to the corresponding web page.

Hereinafter, the functions of the disaster manager of FIG. 3 will be described by dividing them into accident management, simulation training, and disaster management, respectively.

Accident Management

Incident management is a configuration for managing various events, accidents, and disability situations (hereinafter referred to as accidents) that may occur in a normal way, which is not severely damaged. Since the same names are sometimes used hierarchically in the accompanying drawings, in the following description, the same names are assigned by numbering them in order from the upper layer.

Incident Management (1) consists of Incident Management (2), My Page, Report Management, Help, and System Management, Incident Management (2) consists of Incident Management (3), Human Damage, Physical Damage, Other Information, Accidents It consists of reports. Incident management (3) again consists of accident list, accident registration, accident correction, accident overview.

Figure 4a is a web page of the accident list, the accident list can check the accident overview on the accident management list screen. 4B is a web page of accident registration, in which accident registration is a screen for registering an accident. 4C is a web page of accident correction, in which accident correction is a screen for correcting registered accident contents. 4D is a web page of an accident summary, and the accident overview is a screen for confirming details of the accident and progress.

In Injury, enter the injured from the list of injured and enter the personal injury details for the accident. Human damages include injury input, injury information, medical treatment information, and requirements information.

5A shows basic information of an injured person on the injured screen. If you select past injury information, you can check the past injury information. 5B is an injury information screen, which is a screen for checking and correcting injury information input for human damage. FIG. 5C is a screen for inputting medical treatment information, and FIG. 5D is a screen for inputting requirements, opinions, and other items for human injury.

FIG. 6 is a screen for inputting contents on physical damage and stores each item after input. To modify, select an item from the physical damage list at the top and modify the item from the bottom details.

Other information inputs consist of emergency services, witnesses, security systems, and insurance processing information.

Figure 7a is a screen for inputting the information of the agencies to be connected in case of an emergency, the contents of the emergency service at the bottom and save the information. FIG. 7B is a screen for inputting eyewitness information about an accident, and inputs and stores contents in eyewitness details at the bottom. 7C is a screen for inputting a security system or available security system owned by the company, and then enters the details in the security system details at the bottom and stores it. FIG. 7D is a screen for registering and managing insurance processing contents after an accident is input and stored in details of insurance information at the bottom. FIG. 7E is an accident report screen, which is a screen for creating a report on an accident occurrence and notifying persons in charge by using an e-mail, and attaching mail contents and files to send a mail.

My Page consists of announcements, messaging, call trees, and review results.

FIG. 8 is a notice screen for registering / modifying / deleting a notice content related to an accident. To register a new notice, press an initialization button, enter a content, and save the information.

The messaging screen consists of received mail, sent mail, and sending mail.

9A is a received mail screen for confirming mail received in the accident management of the BDM, and the detailed information of the mail can be checked by clicking the corresponding list. 9B is a sent mail screen for confirming mail sent from an accident management of a BDM. When a corresponding list is clicked, detailed contents of the mail can be checked. Figure 9c selects the person to be sent to the e-mail sending screen, enter the contents and click the send button to send.

Call tree 1 consists of call tree 2 and call tree registration.

10A may confirm a call tree registered as a call tree screen or configure a new call tree. FIG. 10B illustrates a call tree registration screen for adding a team member, deleting a team member, setting up a reply, canceling a reply, moving a location, printing, saving, and initializing.

The review result inquiry consists of a list of review targets and a review request list.

FIG. 11A is a screen for confirming a report review history requested in report management, and may be replied after review. 11B is a screen for checking the details requested by the user, and when the list is selected, the contents can be checked.

Report management consists of a list of reports, report generation, and review of review results. The report list 1 is in turn composed of a report list 2, an accident statistical report, an accident contents report, and an overview report.

12A is a screen for checking a list of generated reports. If a corresponding report is selected, the contents can be checked and the position of the report can be adjusted. In addition, there is a function for requesting the relevant person to review the report by e-mail. 12B is a screen for confirming an accident statistics report that has already been made. If you want to change the title of the report, first change the title of the report and then click the Modify Report Title button. 12C is a screen of an accident contents report, and FIG. 12D is a screen for confirming an overview of the report.

The report generation consists of an accident statistics report, an incident content report, and an overview report. The Incident Statistics Report, Incident Content Report, and Summary Report are each composed of a report list and report generation.

FIG. 13A is a screen for checking a list of accident statistics reports, and selects a corresponding list and checks the contents of the report. FIG. 13B may output or store a generated report as a screen for generating an accident statistics report.

FIG. 14A is a list of accident details report screens, and FIG. 14B is a screen for generating an accident details report.

15A is an overview report list screen. 15B is a screen for generating an overview report, which provides a function of creating and previewing an overview report.

16 is a review result inquiry screen for inquiring a result (response) for a requested review list. If you select the list, you can check the contents after review in the bottom reply result.

System management consists of project recovery, menu management, code management, user management, organization management, rights management, rights group management, help management, distribution list management, mail server settings, license information, customer information, and personnel / organization changes.

17 is a screen for recovering a deleted accident (project), mark the corresponding item, and recover by pressing the recovery button.

Menu management consists of menu list, menu registration, and menu modification. FIG. 18A is a menu list screen for managing a menu list used in BDM, and contents thereof may be modified by selecting a corresponding menu list. 18B is a screen for newly registering a menu, and basic information about a menu, a right to manage a system, and a menu help may be registered. 18C is a screen for modifying a menu, and basic information about the menu and help / permission may be modified.

Code management consists of code sets and code management details. 19A is a screen for managing a code set, and after selecting a corresponding code, detailed code contents can be checked. 19B is a detailed code management screen for checking, adding, and deleting detailed codes.

User management consists of user lists, user registrations, and user modifications. FIG. 20A has a function of importing or exporting a user file externally to a user list screen. In order to use a registered user as a resource in a BCP (Business Continuity Planning) solution, the user must be registered as a component. Here, the BCP solution refers to a preconfigured planning solution applied to maintain business continuity. FIG. 20B is a screen for registering a user and is registered based on personnel data, and at the bottom of the screen, a right of the user is granted. 20C is a screen for modifying user information, and is corrected based on personnel data.

Organization management consists of organization lists, organization registrations, organization modifications, and organization assignments. 21A shows a list of organizations registered in PRISM. PRISM (Project Management, Recovery Planning, Impact Analysis, Structured Simulation, Managing Disaster) is a preconfigured planning solution for maintaining business continuity. In the list of organizations, you can select the organization and modify the information. You can also print / delete and import / export files. 21B is a screen for registering organization information. The organization code, organization name, level, upper department and the like must be entered. FIG. 21C is a screen for modifying organization information, and the information modification function and the organization may be stored under another name. 21D can be collectively processed at the organization level or higher organization setting, and is used when setting an organization to which an organization level is not assigned. It is also used to assign company-specific organizations to organizations in the BCP plan.

Rights management consists of a right list, right registration, right modification, and user rights. FIG. 22A is a screen for searching a list of registered rights, and can be inquired by an authority ID or an authority name. FIG. 22B is a screen for registering a right, and inputs and stores a right ID and a name. Fig. 22C is a screen for modifying authority information, and after modifying the contents as appropriate, stores it. 22D is a screen for granting individual user rights, and individual rights can be set.

Authorization group management consists of authorization group list, authorization group registration, and authorization group modification. FIG. 23A is a screen for searching a list of registered authority groups and may be inquired by an authority group ID or an authority group name. 23B is a screen for registering an authority group, and one or more privileges may be registered and used as a group authority. 23C is a screen of modifying a permission group.

Distribution group management consists of distribution list, distribution list registration, and distribution list modification. FIG. 24A is a screen for inquiring a list of distribution lists for collectively sending mail to a plurality of users. 24B is a screen for registering a distribution list, and specific employees may be set as distribution lists. 24C is a screen for modifying a distribution group.

25 is a personnel / organization change screen. Since the organization and personnel information of PRISM is not linked to the personnel / organization information in the company in real time, the changed personnel / organization information should be updated from time to time. Therefore, you can perform this update on this screen.

Mock training

Mock training consists of a mock training plan, command center, My Page, help, and system administration. The simulation training plan consists of project creation, BC PLAN plan, resource plan, evaluation plan, scenario plan, time plan, and geographic information registration.

Project creation consists of project list, project registration, project modification, and project overview. FIG. 26A is a project list screen for querying, outputting, and deleting a project list screen in which mock training is in progress or ended.

FIG. 26B is a screen for registering a mock training project as a project registration screen, and inputs and stores the data correctly according to actual training. The training style determines the actual training style of the mock training. In FIG. 26B, Full Exercise performs all procedures of the BCP as the actual situation, Drill performs a part of independent training, and Walkthrough performs informal virtual training based on documents or data. In addition, Workshop conducts Workshop related to progressing BCP training, and Call Tree conducts emergency contact training only. If your training is not publicly available, you can set it up as a private project. You can also attach imagery to register relevant maps and locations.

FIG. 26C is a project modification screen for modifying a registered project, and FIG. 26D is a project overview screen for checking registered project information.

The BC PLAN plan is a screen that links PRISM's BC PLAN plan with the BDM simulation. A BC PLAN plan is based on the BC PLAN plan. Therefore, the BC PLAN plan must be established in the BCP solution prior to the simulation training of the BDM.

27 is a screen of a BC PLAN plan. In FIG. 27, a project can be selected only one project, and all teams and team members' missions to participate in the actual simulation training must be registered. Assign team members the task of assessing damage, moving, and resuming key tasks so that each team member can see the role on My Page.

FIG. 28 is a screen for designing a detailed plan for necessary resources where / how / who prepares various resources (equipment / tool / manpower, etc.) necessary for simulation training as a resource plan.

The evaluation plan consists of registration of evaluation items and selection of evaluators.

29A is an evaluation item registration screen, in which an evaluation item is registered in establishing an evaluation plan for mock training. In addition, evaluation criteria and grades for evaluation can be registered together. 29B is a screen for selecting a person to perform an evaluation, and may perform evaluator registration, evaluation grade view, and evaluator view. In order to register an evaluator, evaluation items must be registered in advance, and an evaluation item is assigned to the evaluator.

The scenario plan of FIG. 30 is a screen for registering and managing detailed scenarios used for mock training and selecting a role actor (subject) to perform a task on the detailed scenarios.

In the time plan of FIG. 31, a time plan for each plan should be established after a BC plan plan / resource plan / evaluation plan / scenario plan is input. This screen is to input time plan for each plan, and set and start plan start date and plan end date. Dependency between each plan can be set, and the established time plan can be output in chart form.

32 is a screen for registering a variety of geographic information can register the local road and water / sewage map, etc. The registered images can be confirmed in the command center menu. In addition, by registering a network camera can monitor the area where the camera is installed in real time.

The command center (1) consists of the command center (2), announcements, and call tree. The command center 2 can monitor various progress information. Real-time monitoring is possible with cameras installed in each area, and each mission can be checked at a glance with the status of each mission completed and the number of participants. In addition, emergency communication can be performed using various media, and notices can be confirmed in real time.

Contacting on the command center screen consists of sending a Short Message Service (SMS), sending an e-mail, and finding a contact. 33A is an SMS sending screen, FIG. 33B is an email sending screen, and FIG. 33C is a contact searching screen.

34 is a screen for registering and managing the announcement contents to be posted on the announcement of the command center menu.

Call Tree screen is composed of call tree management screen and call tree registration screen. FIG. 35A is a screen for managing a call tree, which supports a function of calling or exporting a call tree content from the outside. Detailed settings of the call tree are managed using a call tree configuration. 35B is a call tree registration screen for configuring call tree details.

My Page consists of mission list inquiry, mission completion input, damage input, evaluation result input, budget item registration, budget execution input, messaging, SMS, and call tree.

36 is a mission list inquiry screen, in which tasks to be performed by the logged in party in simulation training are output. Clicking on the mission takes you to the mission complete input menu where you can enter the processing results for the mission.

FIG. 37 is a screen for inputting a completed or completed task, and selects and stores an appropriate task processing state.

Damage input consists of accident management, human damage, physical damage, and other information. Incident management consists of an incident list, incident registration, incident correction, and incident summary.

38A is a screen of an accident list. The accident list is a screen for searching the accident list among the damage input items, and the accident contents can be modified by selecting the corresponding item.

Accident registration is a screen to register the accident contents among the damage input items. The accident correction is a screen for correcting the registered accident contents and saves after changing necessary contents. The accident summary is a screen for confirming the contents of the accident, and can confirm the entered accident contents.

Human injury consists of injured person, injury information, medical treatment information and requirements information.

38B is an injured and casualty list screen for searching the injured and casualty details of human injury items, and the details can be entered and checked by moving to the injured information / medical processing information / requirement information tab.

Injury information is a screen for entering the injury information of the injured. The medical treatment information is a screen for inputting medical treatment information on the injured person. Requirements information is a screen for entering requirements information related to the injured and casualties.

38C is a screen for inquiring and inputting physical damage matters, and correctly storing each item.

Other information consists of emergency services, witnesses, security systems, and insurance processing information.

39A is an emergency service screen, in which information for contacting a similar authority in an emergency is inputted. For example, enter and store the agency information such as the police station, fire department, and the person in charge of the jurisdiction. FIG. 39B is a witness screen, and a screen for registering a person who witnessed a scene when a disaster occurs, and inputs contact information and listening contents of the witness. FIG. 39C is a screen of a security system, a screen for inputting security equipment and a system. FIG. 39D is a screen for inputting corresponding information when there is related insurance, and inputs and stores correct information. FIG.

40 may deliver the prepared scenario to the subject through the scenario delivery screen.

41 is an evaluation result input screen, where evaluators may select an evaluation list and input the evaluation result.

42 is a budget item registration screen, when there is a budget related input right, a budget item may be registered in this screen.

43 selects a budget item registered as a budget execution input screen, inputs contents, and stores the content.

Messaging consists of received mail, sent mail, and sending mail. Received mail can receive mail sent from PRISM and can check received mail contents. You can check the sent mail in this screen by sending the mail in Send mail to the place where the sent mail is saved. Send mail can send mail with attachments, and can send mail to multiple people at the same time.

44 is a mail sending screen.

45 is a screen for sending a mobile phone text message (SMS) to notify the user of various emergency conditions remotely.

The call tree consists of a call tree list screen and a call tree configuration screen. 46 is a screen for managing a call tree to be used for simulation training, and has a call tree output and configuration function.

Report management consists of report list, report generation and review result review. The report list 1 is composed of a report list 2, a result report, and an overview report.

47A is a report list (2) screen, in which a review request mail can be sent to a specific user, and reviewed mail can be confirmed in a review result inquiry menu.

Report generation consists of a plan report, a result report, an evaluation result report, and an overview report and a review result report. The plan report, the result report, the evaluation result report, and the summary report, and the review result report each consist of a report list and a report generation.

The report list of the planning report can be checked by clicking the report. The report generation is the screen for creating the planning report. Select the project, output destination, and output range.

47B is a result report list screen, when the corresponding report is selected, the contents of the report can be confirmed. Report generation is a screen for generating a result report.

The report list screen of the evaluation result report can be confirmed by clicking the report. 47C is a result report generation screen for selecting each combo box item to output and save a report.

You can check the report contents by selecting the report from the report list of the overview report. FIG. 47D is an overview report generation screen. After inputting appropriate contents for report contents 1 to 5, the user can press the Save or Inquire button after setting the size, alignment, thickness, and font of the text.

48 shows a list of requests for report review on a review result inquiry screen. When a corresponding item is selected, the content of the review request can be confirmed.

Disaster Management

Disaster Management (1) consists of Disaster Declaration (1), Command Center, My Page, Report Management, Help, and System Management. The disaster declaration 1 consists of disaster management 2, BC PLAN registration, disaster declaration 2, and geographic information registration. Disaster management (2) again consists of disaster listing, disaster registration, disaster correction, and disaster summary.

49A illustrates a screen of a list of registered disasters, which may be used to check or delete the contents of a disaster and to output a report. 49B is a screen for registering an actual disaster, and inputs and stores all possible items. 49C is a screen for correcting a disaster and appropriately changes items to be corrected. FIG. 49D is a screen for confirming the contents of the registered disaster, and may confirm the registered disaster contents.

50 is a screen for registering a BC Plan is a screen for assigning their tasks to each team member by interlocking the tasks registered in the BCP system. You can also set permissions or check missions for each team member.

51 is a screen for declaring an actual disaster when a disaster occurs, and each team may declare a disaster by mail or SMS. You can also declare disasters by email or SMS in addition to separate users.

FIG. 52 is a screen for registering various types of geographic information, and may register local roads and water / sewer maps, and registered images may be checked in a command center menu. In addition, network cameras can be registered and the area installed by the camera can be monitored in real time.

The command center consists of a disaster context menu, announcements, and a call tree.

53 may monitor various progress information on a command center screen of a disaster situation. Real-time monitoring of each region's information and disaster situation is possible with installed cameras, and each mission's performance status and personnel status can be checked at a glance. In addition, emergency communication can be performed using various media, and notices can be checked. You can also remotely control your network camera from the command center screen, send SMS, send E-mail, and find contacts.

The notice of FIG. 54 is a screen for registering and managing a notice content to be posted on a notice of a command center menu.

FIG. 55 is a screen for managing a call tree, which supports a function such as calling or exporting call tree contents from the outside, and manages details using a call tree configuration.

My Page consists of mission list inquiry, preliminary damage assessment, mission completion input, damage input, budget item registration, budget execution input, messaging, SMS, and call tree.

56 shows a list of tasks to be performed as a menu with tasks to be performed by the logged in party. Selecting the mission takes you to the mission complete input menu where you can enter the processing results for the missions.

FIG. 57 is a preliminary evaluation of damages when a disaster occurs. When a damage evaluation task is registered, a My Page of the person in charge should input a preliminary damage evaluation and request a disaster declaration. Depending on your current progress, you can select "In Assessment / Disaster Declaration / End".

58 is a screen for inputting a completed or completed task, and selecting and storing an appropriate task processing state.

Damage input consists of incident management, human damage, physical damage, other information, and accident reporting. Incident management consists of an incident list, an incident registration, an incident correction, and an incident overview.

59A is a screen for searching an accident list among damage input items, and selecting an item may modify the contents of the accident. The accident registration screen is a screen for registering accidents that occurred during a disaster situation. The accident correction screen is a screen for correcting a registered accident and changes the contents and saves it. The accident summary screen is an accident summary screen selected from the accident list to check the details of the accident.

Human injury consists of injured person, injury information, medical treatment information, and requirements information.

59B is a screen for confirming the injured list and the injured information, and may register the injured or check past injured information. The injury information screen is a screen for confirming and registering injury information. After selecting a registered injured person, the injury information can be input. The medical treatment information screen is a screen for checking and registering medical treatment information, and after selecting a registered injured person, may input medical treatment information. Requirements information is a screen for checking and registering requirement information. After selecting the registered injured person, the requirement information can be input.

59C is a screen for identifying and registering physical damages during a disaster, and may register / modify damage details.

Other information consists of emergency services, witnesses, security systems and insurance processing information.

FIG. 59D is a screen for inputting information of agencies to be linked in an emergency, and inputs contents from the emergency service details below and stores the information. The eyewitness screen is a screen for inputting eyewitness information. The eyewitness details are stored in the eyewitness details. The security system screen is a screen for entering a security system or a security system owned by the company. The information is stored in the security system details at the bottom. The insurance treatment information screen is a screen for registering and managing insurance treatment details after an accident. After inputting the contents in the insurance information details at the bottom, the insurance treatment information screen is stored. The accident report screen creates a report on the occurrence of an accident and sends a mail with the contents of the mail and the file attached to the screen to notify related persons by using E-Mail.

60 is a budget item registration screen, when there is a budget related input right, a budget item in this screen may be registered.

61 selects a budget item registered as a budget execution input screen, inputs contents, and presses a save button.

Messaging consists of received mail, sent mail, and sending mail. FIG. 62A shows where mail is sent from PRISM.

62B shows mails sent from this screen when the mails are sent to the place where the sent mails are stored. FIG. 62C shows a mail sending screen, and a mail may be sent by attaching a file, or mail may be simultaneously sent to several people.

FIG. 63 is a screen for sending a text message (SMS) for mobile phones to notify users of various emergency situations remotely located.

64 is a screen for managing a call tree to be used in case of a disaster, and has a call tree output and configuration function.

Report management consists of report list, report generation and review result review. FIG. 65A illustrates a screen for inquiring a report list, such as changing the order of reports and sending a review request mail. Fig. 65B, to select a report from the report list, the screen is returned to the result report screen. 65C is an overview report screen. When the corresponding report is selected from the report list, the overview report screen is displayed.

Report generation consists of a result report and an overview report.

The result report and summary report consist of a report list and a report generation, respectively. Fig. 66A shows the contents of the report when the corresponding report is selected on the result report list screen. The Result Report Generation screen allows you to print and save the report.

Overview In the report list screen, you can check the contents of the report by clicking the report. Fig. 66B is an overview report generation screen, in which contents are properly inputted from report contents 1 to report contents 5, and then the size, alignment, thickness, font, and the like of the font are set and stored or retrieved.

67 shows a list of requests for report review on the review result inquiry screen. When the corresponding item is selected, the content of the review request can be confirmed.

68 is a schematic flowchart for performing an embodiment of a business disaster management method according to the present invention.

In FIG. 68, the business disaster management system first performs accident management (S100). Incident management is the management of everyday incidents, and manages routine small disasters where the disaster management phase is not performed.

When the simulation training input is input during the execution of the accident management step (S200), the simulation training step is performed (S300). Simulation training is a step of performing a predetermined disaster management process in response to the simulated disaster.

In addition, if there is a disaster occurrence input during the execution of the accident management step (S400), the disaster management step is performed (S500). The entire project disaster management process will continue unless there is a separate disaster management exit input, and if the simulation or disaster management phase has ended, the accident management process will be performed again.

If there is a separate disaster management end input (S600), the business disaster management process ends.

FIG. 69 is a detailed flowchart of the disaster management step of FIG. 68;

When receiving a predetermined disaster occurrence input, the disaster management system transmits the disaster occurrence information to the pre-registered notification communication terminal (502), and then transmits the pre-registered person performing task information to the connected person terminal (S504).

When disaster situation information is input from the person in charge of the terminal (S506), the disaster situation information is transmitted to the predetermined manager terminal (S508). At this time, the disaster status information may include the performance status of the person performing the task.

In addition, the controller checks the input from the local situation detecting apparatus for detecting the situation of the region installed and installed at a predetermined position (S508), and if there is an input, transmits the input local situation detecting information to the manager terminal (S508). The local situation detection apparatus may be a network camera, and video conferencing may also be performed using the network camera.

In addition, when there is an emergency contact network information request input from the administrator terminal (S510), the emergency contact network information registered in advance is transmitted.

 When there is a disaster situation response information input from the manager terminal (S514), the input disaster situation response information is transmitted to the connected person in charge terminal (S516). Disaster situation response information may be output in the form of announcements.

When an evaluation input for disaster response is received from a predetermined evaluator terminal (S524), the input evaluation result is stored (S526).

These steps continue until a separate disaster termination input is entered. If the disaster is terminated and there is a corresponding disaster termination input (S518), the disaster management process ends.

There may be an entry in the disaster status report before the disaster management process ends. In this case (S520) ends after saving the input report.

When a disaster occurs according to the present invention, it is possible to quickly and effectively respond to a disaster by transmitting a disaster fact and a task to the person in charge, and a disaster response situation reported from the person in charge.

Although the present invention has been described in terms of some preferred embodiments, the scope of the present invention should not be limited thereby, but should be construed as a modification or improvement of the above embodiments supported by the appended claims.

Claims (21)

A disaster occurrence information transmission unit for transmitting the disaster occurrence information to a pre-registered notification communication terminal when receiving a predetermined disaster occurrence input; A person performing task information transmitting unit which transmits the person performing task information registered in advance to the connected person terminal; And A disaster management system comprising a disaster situation information transmission unit for transmitting the disaster situation information to a predetermined manager terminal when the disaster situation information is input from the person in charge of the terminal, Further comprising a disaster response evaluation storage for storing a disaster response evaluation input received from a predetermined evaluator terminal, The predetermined disaster comprises a simulated disaster for conducting a simulation training. The method of claim 1, And a disaster situation response information transmission unit which transmits the disaster situation response information input from the manager terminal to a connected person in charge terminal. The method of claim 1, Project disaster management system further comprises a local situation detection device for detecting and inputting the situation of the area installed and installed in a predetermined position. The method of claim 3, wherein The local situation detection device is a business disaster management system, characterized in that the network camera. The method of claim 1, Business emergency management system further comprises an emergency contact network information transmission unit for transmitting the emergency contact network information registered in advance to the manager terminal. The method of claim 1, The disaster situation information business disaster management system, characterized in that it comprises the performance of the person performing the task. delete The method of claim 1, Business disaster management system further comprises a report storage unit for storing the disaster status report input from the connected person in charge. delete The method of claim 1, Business disaster management system further comprises a disaster management data storage for storing the management data for the disaster. Transmitting a disaster occurrence information to a pre-registered notification communication terminal when a disaster occurrence input is received; Transmitting the pre-registered task performance information to the connected staff terminal; And When the disaster situation information is input from the person in charge of the terminal, the project disaster management method comprising the step of transmitting the disaster situation information to a predetermined manager terminal, And receiving an evaluation input for disaster response from a predetermined evaluator terminal, And said predetermined disaster comprises a simulated disaster for conducting a simulated training. The method of claim 11, And transmitting the disaster response information inputted from the manager terminal to a connected person in charge. The method of claim 11, And transmitting, to the administrator terminal, local situation detection information input from a local situation detecting device detecting a situation of an installed area installed at a predetermined location. The method of claim 13, The local situation detection apparatus is a business disaster management method, characterized in that the network camera. The method of claim 11, And transmitting the emergency contact network information registered in advance to the manager terminal. The method of claim 11, The disaster situation information is a business disaster management method, characterized in that it comprises the performance of the person performing the task. delete The method of claim 11, And storing a disaster status report inputted from a connected person in charge terminal. delete The method of claim 11, And storing the management data on the disaster. A medium having a computer readable program recorded thereon for executing the method of any one of claims 11 to 16, 18 and 20.

Images