Business continuation support system and information processing device

Abstract

To enable the execution of a business continuation plan to be supported by determining a significant business to an enterprise and the influence range of a disaster from the point of view of a significant process related to the significant business.SOLUTION: A business continuation support system includes a management data storage part 101 for storing enterprise significant business, a significant process related to the significant business, resources to be allocated to the significant process, and locations of the resources in a database as management data, and an influence range specification part 14 for determining disasters at a base being a location of the resources or the existence / nonexistence of a disaster possibility on the basis of disaster related information acquired from an external information provision system 4, and specifying a disaster determination base determined to have a disaster or a disaster possibility, resources sequentially linked to the disaster determination base, significant processes, significant businesses and other related bases as the influence range of a disaster on the basis of the management data stored in the management data storage part 101.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a business continuity support system and an information processing device, and is particularly suitable for use in a system that executes processing related to supporting the execution of a business continuity plan. [Background technology]

[0002] In recent years, the occurrence of large-scale natural disasters such as major earthquakes and heavy rains and snowfalls has been increasing. The occurrence of such large-scale disasters poses a risk to companies' business activities. The importance of a BCP (Business Continuity Plan) is recognized as a way to prepare for such risks. A BCP is a plan that defines in advance the actions that a company should take to continue or quickly restore its core business in the event of an emergency such as a natural disaster or pandemic.

[0003] Various systems have been proposed to support the formulation or implementation of BCPs (see, for example, Patent Documents 1 to 9). Patent Documents 1 to 5 disclose systems that determine the risk status of multiple bases that are connected in a business and provide information to bases at risk and management bases. Patent Documents 6 to 9 also disclose systems that present recovery measures according to the damage situation and calculate a recovery curve leading up to the scheduled completion of recovery to manage progress.

[0004] The business recovery support system described in Patent Document 1 comprises an individual company management server installed for each company, and an overall aggregation server that aggregates and manages information related to the operating status of resources (such as essential equipment and personnel that cannot perform business without their operation) and businesses (including businesses that provide goods and services externally) managed by each individual company management server. The overall aggregation server manages the correspondence between information related to the operating status of each of the aggregated resources and businesses (including whether goods can be shipped or services can be provided) and each user, and when it receives an information acquisition request from a user, it provides information related to the operating status of the resources and businesses associated with the requesting user.

[0005] Patent Document 1 also discloses the presentation of recovery measures according to the operating status of resources, the calculation of estimated recovery times, and progress management. Specifically, in the business recovery support system of Patent Document 1, a field terminal device inputs status information identifying the operating status of resources and transmits it to a management server. Based on the input status information and the status information received from the management server, the management server presents recovery measures to be implemented to restore each resource to its original operating state. Based on the status information of each resource received from the field terminal device, the management server identifies measures to be implemented for the business to which the resource belongs, calculates the estimated recovery time from the time required to implement the measures, and determines the progress of the implementation of the recovery measures relative to the estimated recovery time. Furthermore, the management server predicts the time when the business to which the resource belongs will resume operation. This information is then presented on the management terminal device as a dashboard screen.

[0006] The dashboard screen is a screen for understanding the operating status of all managed business operations, and displays the operating status (status) and the number of check-ins (the number of people involved in implementing recovery measures) as information for the entire business operation. In addition, the dashboard screen displays information for each business operation, such as the operating status (status), the operating status (status) of each resource belonging to the business operation, the predicted recovery line for the business operation and resources, the number of tasks completed among the work procedures implemented as recovery measures (number of completed tasks), the target date and time for completing all tasks as recovery measures, and the number of check-ins. The information displayed on the dashboard screen is updated as the operating status changes over time.

[0007] The business risk calculation system described in Patent Document 2 evaluates business interruption risk by taking into account earthquake risks not only within a single company but also for each related facility (supply chain). The system includes a supply chain supply network setting means for setting up a supply network from each supply chain to a company, a supply chain status input means for inputting the location, building characteristics, current status of lifelines, and inventory days of each supply chain, an allowable operation shutdown period calculation means for calculating the allowable operation shutdown period of each supply chain based on the inventory days, an operation shutdown probability calculation means for calculating the probability of operation shutdown due to damage caused by an earthquake, a business interruption probability calculation means for calculating the probability of business interruption at a company based on substitutability in the supply chain (whether it is a series system or a parallel system), and a means for calculating the impact level based on the operation shutdown probability of each supply chain, displaying the calculated impact level on a map, and displaying the priority order for taking measures taking into account the impact level, etc.

[0008] The information processing system described in Patent Document 3 acquires disaster-related prediction information, and determines whether there are any bases expected to be damaged based on the acquired prediction information, location information of multiple bases (including information indicating the relationship between a certain base and bases related to that base), and attribute information associated with the multiple bases.The system then determines suggested information related to disaster countermeasures for each of the multiple bases expected to be damaged, and notifies the user of the determined suggested information.In addition, the system notifies the user at a specific base of status list information related to the multiple bases (including action record information at the multiple bases).

[0009] Bases include business entities such as subsidiaries, sub-subsidiaries, and suppliers. Base attribute information includes information related to multiple bases, such as the industry, building structure, construction date, building area, number of floors, number of employees, BCP status, and manufactured goods. Suggested information indicates recommended actions to take in the event of a disaster, such as confirming the safety of employees, evacuating employees, securing hard-to-replace parts (evacuating goods to safe locations, increasing production, moving goods, etc.), placing sandbags, closing stores, and changing logistics routes. For example, if the substitutability of goods manufactured at a certain base is low, meaning that it is difficult to replace the production of goods at bases other than that base, securing those goods is likely to be important from a BCP perspective, and therefore measures to secure those goods are included in the suggested information.

[0010] The business risk assessment system described in Patent Document 4 assesses the business risk of individual products while taking into account the impact of bases that indirectly supply parts and other supplies to a company. The system includes a supplier location information database that stores the location information of supplier bases; a supply information database that stores dependency information indicating the configuration of supplies included in the product and the dependencies between the supplies; a distance calculation unit that calculates the distance between the disaster occurrence point and the supplier base; an affected supplier determination unit that determines suppliers that may be affected by the disaster based on the calculated distance; an affected supply determination unit that determines supplies affected by the disaster; and an impact range determination unit that determines products affected by the disaster based on the supply dependency information. The system also includes a dependency analysis unit that analyzes the dependency of supplies that make up the product on specific resources, such as region, and visualizes the results to present to the user.

[0011] The crisis management support method described in Patent Document 5 uses a computer to support crisis management in a parts supply system when a disaster occurs or a disaster is predicted in a system that produces products using parts supplied from multiple parts supply bases. Specifically, disaster-affected area information, including location information of areas affected by the disaster that are unable to fully function or have stopped functioning under normal circumstances, is input, and map information containing location information of parts supply bases is read. A calculation unit calculates and identifies locations affected by the disaster (including transportation routes connecting each parts supply base and secondary parts supply bases) based on the disaster-affected area information and the map information. Information on parts supplied by the parts supply base affected by the disaster is then obtained from a storage unit. The calculation unit calculates and identifies product groups that use parts supplied by the parts supply base affected by the disaster, and displays the production bases of the identified product groups.

[0012] The countermeasure selection device described in Patent Document 6 determines whether or not each vulnerability of a resource included in a business for which countermeasures are to be formulated has been addressed based on a vulnerability master that defines resources, vulnerabilities that the resource has, and recovery times caused by the vulnerabilities in association with each other, a countermeasure master that defines vulnerabilities defined in the vulnerability master in association with countermeasures to resolve the vulnerabilities, and countermeasure status data that registers whether or not each countermeasure defined in the countermeasure master has been implemented, and selects countermeasures from among the countermeasures defined in the countermeasure master based on the recovery times defined in association with vulnerabilities that have been determined to have not been addressed.

[0013] The disaster prevention information processing system described in Patent Document 7 measures the scale of a disaster as a physical quantity based on collected infrared image information and various image information related to the disaster site. When a disaster occurs involving multiple simultaneous incidents, the amount of damage at each disaster point is measured. Furthermore, a simulation is performed to calculate the amount of resources required to mitigate the damage measured. The system then calculates the amount of resources needed and the amount of resources already deployed at each disaster point, and determines resource allocation based on a policy of allocating surplus resources to disaster points with insufficient resources.

[0014] The recovery period calculation system described in Patent Document 8 targets high-precision production equipment, such as semiconductor factories, which would suffer enormous damage in the event of an earthquake. Based on a fragility curve (damage probability distribution) based on the vibration amplification characteristics of the production equipment derived from vibration experiments, and past earthquake damage data, the system predicts damage that will occur due to an earthquake, and takes into account not only the actual work period but also the restoration of lifelines and other elements, if these are assumed, to determine the number of recovery days. By comparing each element, the system evaluates the recovery period required to restart the factory from damage caused by a disaster such as an earthquake as a recovery curve.

[0015] In the restoration process evaluation method described in Patent Document 9, the buildings that make up a production facility, the production equipment that produces the products, and the lifelines related to production are determined as evaluation targets, and then the damage state is classified into cases for each evaluation target, and for each classified damage state, the damage probability of that damage state occurring, the production reduction rate in that damage state, and the restoration period for that damage state are determined.Then, based on the determined damage probability, production reduction rate, and restoration period, the process until production at the production facility is restored is evaluated, and the evaluation results are displayed as a production restoration curve. [Prior art documents] [Patent documents]

[0016] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-232910 [Patent Document 2] Japanese Patent Application Laid-Open No. 2009-053977 [Patent Document 3] Japanese Patent Publication No. 2023-001812 [Patent Document 4] Japanese Patent Application Laid-Open No. 2014-115745 [Patent Document 5] Japanese Patent Application Laid-Open No. 2004-334492 [Patent Document 6] WO09 / 116173 publication [Patent Document 7] Japanese Patent Application Laid-Open No. 2001-325686 [Patent Document 8] Japanese Patent Application Laid-Open No. 2017-167668 [Patent Document 9] Japanese Patent Application Laid-Open No. 2009-265765 Summary of the Invention [Problem to be solved by the invention]

[0017] The systems described in Patent Documents 1 to 3 above assess the risk situation not only for the business establishment where the disaster occurred, but also for multiple bases including other business establishments connected to the business establishment in the disaster area, employees' homes, supply chains, etc., and perform processing to support business continuity and recovery. In addition, the systems described in Patent Documents 4 and 5 analyze suppliers, products, transportation routes, bases, etc. that may be affected by the disaster.

[0018] However, what is necessary for the execution of a business continuity plan is an awareness of the impact that the occurrence of an emergency will have on a company's critical business. In contrast, the systems described in Patent Documents 1 to 3 simply identify connected business locations, employee homes, supply chains, etc., and perform processing to support business recovery, etc., but do not manage these by linking them to critical businesses. Furthermore, the systems described in Patent Documents 4 and 5 only analyze suppliers, products, transportation routes, bases, etc. that may be affected by a disaster, but do not perform processing to support the execution of a business continuity plan.

[0019] In contrast, the present invention aims to determine the extent of the impact of a disaster from the perspective of important businesses and important processes related to the businesses, and to support the execution of business continuity plans. [Means for solving the problem]

[0020] In order to solve the above-mentioned problems, the present invention includes a management data storage unit that stores one or more important businesses of a company, one or more important processes related to the important businesses, one or more resources assigned to the important processes, and the locations of the resources as management data in a database, and when disaster-related information regarding the occurrence of a disaster is acquired, a determination is made based on the disaster-related information as to whether or not the bases where the resources are located have been affected by damage or are at risk of being affected by damage, and based on the management data stored in the management data storage unit, the disaster-affected areas are identified as the scope of impact of the disaster, including damage-determined bases that have been determined to be affected by damage or are at risk of being affected by damage, and the resources, important processes, important businesses, and other related bases that are linked in turn to the damage-determined bases. [Effects of the Invention]

[0021] According to the present invention configured as described above, it is possible to determine the extent of the impact of a disaster from the perspective of important businesses for a company and important processes related to those businesses, and to support the execution of a business continuity plan. [Brief explanation of the drawings]

[0022] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of a business continuity support system according to an embodiment of the present invention. [Figure 2] 1 is a block diagram showing an example of the functional configuration of a BCM support system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a block diagram showing a specific example of the functional configuration of a support process execution unit according to the present embodiment. [Figure 4] FIG. 2 is a diagram showing the relationships between various management data related to a company. [Figure 5] FIG. 1 is a diagram showing the relationship between various management data related to important projects. [Figure 6] FIG. 1 is a diagram showing the relationship between various management data related to important processes. [Figure 7] FIG. 2 is a diagram showing the relationships between various management data related to employees. [Figure 8] FIG. 2 is a diagram showing the relationship between various management data related to bases. [Figure 9] FIG. 10 is a diagram showing the relationship between various management data related to funds. [Figure 10] 10 is a schematic diagram for explaining a method for identifying an influence range by an influence range identification unit; FIG. [Figure 11] FIG. 10 is a diagram illustrating an example of an information providing screen for an impact extent identified by an impact extent identification unit. [Figure 12] FIG. 10 is a diagram showing an example of a dashboard screen (top screen). [Figure 13] FIG. 10 is a diagram illustrating an example of a business confirmation screen. [Figure 14] FIG. 10 is a diagram illustrating an example of a business establishment confirmation screen. [Figure 15] FIG. 10 is a diagram illustrating an example of an employee confirmation screen. [Figure 16] 3 is a flowchart showing an example of the operation of the BCM support system according to the present embodiment. [Figure 17] FIG. 10 is a diagram illustrating another example of the relationship between various management data related to important processes. DETAILED DESCRIPTION OF THE INVENTION

[0023] An embodiment of the present invention will be described below with reference to the drawings. Fig. 1 is a diagram showing an example of the overall configuration of a business continuity support system according to this embodiment. As shown in Fig. 1, the business continuity support system of this embodiment is configured to include a BCM (Business Continuity Management) support system 1, a management terminal 2, multiple base terminals 3, and an external information providing system 4.

[0024] The BCM support system 1, management terminal 2, multiple base terminals 3, and external information provision system 4 are connected via a communication network 5. The communication network 5 includes the Internet, a mobile phone network, a dedicated line, a LAN (Local Area Network), etc., and any one or a combination of these is set according to the operating environment of the system of this embodiment.

[0025] The BCM support system 1 is configured with a server device (corresponding to an information processing device in the claims). The BCM support system 1 may be configured with one server device, or may be configured with multiple server devices. The BCM support system 1 executes processing related to supporting the execution of business continuity plans in the event of an emergency such as a natural disaster, for the management terminal 2 and the base terminal 3. Details of this processing will be described later.

[0026] The management terminal 2 is a terminal used by a company administrator, and is configured, for example, as a personal computer, tablet, smartphone, etc. The company administrator may be, for example, the CEO, a crisis manager, or a general affairs department staff member, and is set arbitrarily for each company that uses the business continuity support system.

[0027] The base terminals 3 are terminals used by the site managers and employees of each base, and are configured, for example, as personal computers, tablets, smartphones, etc. Bases are the locations of various resources required to carry out business. Resources include company offices, employees, business partners, etc.

[0028] The external information providing system 4 is a system that issues disaster-related information regarding the occurrence of natural disasters and a system that provides hazard maps related to natural disasters. Examples of systems that issue disaster-related information include the Japan Meteorological Agency's disaster prevention information providing system and the J-Alert system. Natural disasters include earthquakes, tsunamis, typhoons, heavy rain, heavy snowfall, floods, landslides, and volcanic eruptions. Disaster-related information includes information such as the location where a disaster has occurred or is likely to occur, the date and time, and the extent of the disaster. For example, in the case of an earthquake, the disaster-related information includes information such as the location, date and time of the earthquake, and the magnitude of the earthquake.

[0029] Fig. 2 is a block diagram showing an example of the functional configuration of a BCM support system 1 according to this embodiment. As shown in Fig. 2, the BCM support system 1 of this embodiment includes, as its functional configuration, a management data registration unit 11, a hazard map acquisition unit 12, a disaster-related information acquisition unit 13, an impact range identification unit 14, and a support process execution unit 15. The BCM support system 1 of this embodiment also includes, as storage media, a management data storage unit 101, a hazard map storage unit 102, a disaster-related information storage unit 103, a status storage unit 104, an action log storage unit 105, and an operation log storage unit 106.

[0030] The functional blocks 11 to 15 execute the processes described below through cooperation between hardware and software. For example, the processes of the functional blocks 11 to 15 are executed by the operation of a program stored in a storage medium such as RAM, ROM, a hard disk, or a semiconductor memory under the control of a microcomputer including a CPU, RAM, ROM, etc. Note that a DSP (Digital Signal Processor) or the like may be included in addition to the microcomputer.

[0031] 2 shows an example of a configuration in which a single server device includes multiple function blocks 11-15 and multiple storage units 101-106 of the BCM support system 1. However, as described above, the BCM support system 1 may be configured with multiple servers, in which case the processing of the function blocks 11-15 is executed by the cooperation of the multiple server devices. Furthermore, the storage units 101-106 are distributed across the multiple server devices.

[0032] The management data registration unit 11 acquires various management data required for processing related to BCP execution support from the management terminal 2 and stores it in a database in the management data storage unit 101. That is, the company's administrator inputs various management data into the management terminal 2 and sends it to the BCM support system 1 via the communication network 5. The management data registration unit 11 of the BCM support system 1 acquires the management data sent from the management terminal 2 and stores it in the management data storage unit 101.

[0033] The management data stored in the management data storage unit 101 includes data such as one or more important businesses of the company, one or more important processes related to the important businesses, one or more important tasks related to the important processes, one or more resources assigned to the important processes and the locations of the resources, response actions to be taken for business continuity or business recovery and the execution procedures for each response action and the target completion time for each response action, and funds required to implement the BCP.

[0034] A company administrator inputs into the management terminal 2 one or more businesses that are deemed particularly important among the multiple businesses conducted by the company (businesses for which BCP implementation is being undertaken), and transmits important business information that can identify the business to the BCM support system 1. The important business information can be, for example, the name of the important business. The important business information may also include information other than identification information, such as information indicating the content of the business. The management data registration unit 11 stores the important business information acquired from the management terminal 2 in the management data storage unit 101.

[0035] For each of one or more important businesses, a company administrator inputs into the management terminal 2 one or more processes that are deemed particularly important from among the multiple processes carried out in each important business, and transmits important process information that can identify the process to the BCM support system 1. The important process information can be, for example, the name of the important process. The important process information may also include information other than identification information, such as information indicating the content of the process. The management data registration unit 11 associates the important process information acquired from the management terminal 2 with important business information and stores it in the management data storage unit 101.

[0036] For each of one or more important processes, a company administrator inputs into the management terminal 2 one or more tasks that are deemed particularly important from among multiple tasks related to each important process, and transmits important task information that can identify the task to the BCM support system 1. The important task information can be, for example, the name of the important task. The important task information may also include information other than identification information, such as information indicating the content of the task. The management data registration unit 11 associates the important task information acquired from the management terminal 2 with important process information and stores it in the management data storage unit 101.

[0037] A company administrator inputs one or more resources allocated to each important process into the management terminal 2 for each important process, and transmits resource information that can identify the resource to the BCM support system 1. The resource information can be, for example, the name of the resource. The resource information may also include information other than identification information, such as information indicating the content of the resource. The management data registration unit 11 associates the resource information acquired from the management terminal 2 with important process information and stores it in the management data storage unit 101. The resource information may also be associated with important task information.

[0038] Resources include one or more business locations of a company, one or more employees, and one or more business partners. Here, employee information may include information about the organization to which the employee belongs, and may also include information about their family members. Business location and employee information may also include information about equipment, stockpiles, etc. Business partners include buyers related to accounts receivable (deposits) and suppliers related to accounts payable (withdrawals), and have either or both as attributes. Business partner information may also include information about personnel, as well as information about equipment, stockpiles, etc.

[0039] In addition, the company's administrator enters the locations of one or more resources into the management terminal 2 and transmits information that can identify the locations to the BCM support system 1. The management data registration unit 11 associates the resource location information acquired from the management terminal 2 with the resource information and stores it in the management data storage unit 101. Here, the employee's location includes the location of the business office to which the employee belongs, as well as the employee's other workplace outside the business office (home, satellite office, workation, etc.). The reason for registering an employee's other workplace is that it is considered that an employee may perform work outside the business office. Therefore, it is possible to register other workplaces only for employees who may perform work outside the business office.

[0040] A company administrator inputs response actions to be taken for business continuity or business recovery for one or more critical processes into the management terminal 2 and transmits information that allows the response actions to be recognized to the BCM support system 1. The information that allows the response actions to be recognized can be, for example, information indicating the name and content of the response action. Response actions include response actions to avoid damage for business continuity at bases where resources are located, response actions to prepare for disasters for business continuity at bases, response actions to be taken for business recovery at affected bases, response actions for initial responses that may be life-threatening, and response actions to be taken for business continuity or business recovery at related bases (described below). The management data registration unit 11 associates the response action information acquired from the management terminal 2 with critical process information and stores it in the management data storage unit 101.

[0041] A company administrator inputs information indicating a BCP, including the execution procedures for response actions, the target completion time for each response action, and the association between the response actions and important tasks, into the management terminal 2 for each of one or more important businesses, and transmits the BCP information to the BCM support system 1. The management data registration unit 11 associates the BCP information acquired from the management terminal 2 with important business information and stores it in the management data storage unit 101. BCPs differ not only depending on the content of important businesses, but also depending on the type and scale of the natural disaster in question. Therefore, for one important business, multiple pieces of BCP information may be input and registered in the BCM support system 1 according to the type and scale of the natural disaster, etc.

[0042] A company administrator inputs information about the funds required to implement BCP for one or more critical processes into the management terminal 2 and transmits the fund-related information to the BCM support system 1. The fund-related information includes information about deposits and withdrawals. The information about deposits includes information indicating accounts receivable from business partners (estimated sales amount) and information indicating the amount of equipment insurance allowance that may be paid by insurance companies in the event of a critical business interruption, as well as payment terms. The information about withdrawals includes information about accounts payable from business partners (estimated payment amount), estimated employee salaries, and estimated resource damage. The management data registration unit 11 stores the fund-related information acquired from the management terminal 2 in the management data storage unit 101, appropriately associating it with critical business information, critical process information, and resource information.

[0043] 4 to 9 are diagrams that schematically show the relationships (linking relationships) between various pieces of management data stored in the management data storage unit 101. In Fig. 4 to Fig. 9, each piece of management data is shown by a rectangular frame, and the linking relationships between the management data are shown by straight lines between the rectangular frames. Fig. 4 to Fig. 9 also show the relationships (correspondence relationships) with hazard maps, disaster-related information, and status information, which will be described later, and the correspondence relationships between these pieces of information and the management data are shown by dotted lines.

[0044] Figure 4 shows the relationships between various management data related to a company, Figure 5 shows the relationships between various management data related to important businesses, Figure 6 shows the relationships between various management data related to important processes, Figure 7 shows the relationships between various management data related to employees, Figure 8 shows the relationships between various management data related to locations, and Figure 9 shows the relationships between various management data related to funds.

[0045] The hazard map acquisition unit 12 acquires a hazard map in advance from the external information provision system 4 via the communication network 5 and stores it in the hazard map storage unit 102. The hazard maps acquired by the hazard map acquisition unit 12 include those related to earthquakes, tsunamis, floods, landslides, volcanic eruptions, etc. Hazard maps are map data that indicate areas expected to be affected by natural disasters and the extent of damage. Using this hazard map and the locations of resources, it is possible to identify bases located within areas expected to be affected.

[0046] The disaster-related information acquisition unit 13 acquires disaster-related information from the external information provision system 4 via the communication network 5 and stores it in the disaster-related information storage unit 103. When a natural disaster occurs or when a natural disaster is predicted to occur, disaster-related information is issued from the external information provision system 4. The disaster-related information acquisition unit 13 acquires the disaster-related information issued from the external information provision system 4 in real time and stores it in the disaster-related information storage unit 103. When the disaster-related information issued from the external information provision system 4 is updated, the disaster-related information acquisition unit 13 also acquires the updated disaster-related information in real time and updates the disaster-related information stored in the disaster-related information storage unit 103 with the most recent disaster-related information.

[0047] The affected area identification unit 14 determines whether or not bases where resources are located have been affected by or are likely to be affected by disaster, based on the hazard map acquired by the hazard map acquisition unit 12 and stored in advance in the hazard map storage unit 102, and the disaster-related information acquired by the disaster-related information acquisition unit 13 and stored in real time in the disaster-related information storage unit 103. The affected area identification unit 14 further identifies, based on the management data stored in the management data storage unit 101, bases determined to be affected by disaster or to be likely to be affected (hereinafter, these will be collectively referred to as damage-determined bases. Also, a base determined to have been affected will be referred to as a damaged base, and a base determined to be likely to be affected will be referred to as a likely-damaged base), as well as resources, important processes, important businesses, and other bases (hereinafter referred to as related bases) that are sequentially linked to the damage-determined bases, as the affected area of ​​the disaster.

[0048] If the resource is an employee of a company, the location may be the business establishment or another workplace as described above, or the current location while traveling. The current location while traveling indicates the employee's current location while commuting to work or while visiting a business location. The location to be applied to the employee is determined based on the status information stored in the status storage unit 104, as will be described later. The current location while traveling is stored in the status storage unit 104, not in the management data storage unit 101.

[0049] If the disaster-related information stored in the disaster-related information storage unit 103 is related to an earthquake, the affected area identification unit 14 determines that the bases corresponding to the location of the earthquake indicated in the disaster-related information are disaster-affected bases. Only bases corresponding to the location of the earthquake indicated in the disaster-related information where the magnitude of the earthquake is equal to or greater than a predetermined value may be determined to be disaster-affected bases.

[0050] Furthermore, if the disaster-related information relates to a tsunami forecast, the affected area identification unit 14 determines that bases corresponding to areas where the tsunami is expected to reach are bases that are likely to be affected. If the disaster-related information relates to a report of the arrival of a tsunami, the affected area identification unit 14 determines that bases corresponding to areas where the tsunami will reach are bases that are affected. Only bases that correspond to areas where the tsunami magnitude indicated in the disaster-related information is expected to reach or that are expected to reach the tsunami and is equal to or greater than a predetermined value may be determined to be affected bases or bases that are likely to be affected.

[0051] Furthermore, if the disaster-related information relates to a typhoon forecast, the impact range identification unit 14 determines that bases corresponding to areas along the typhoon's predicted path are likely to be affected bases. If the disaster-related information relates to a typhoon passage report, the impact range identification unit 14 determines that bases corresponding to areas through which the typhoon will pass are likely to be affected bases. Bases corresponding to areas through which the typhoon will pass may be determined as affected bases or likely to be affected bases only when the typhoon scale indicated in the disaster-related information is equal to or greater than a predetermined value. Furthermore, the impact range identification unit 14 refers to a hazard map and determines that bases corresponding to areas where there is a possibility of flooding, landslides, etc. occurring due to the passage of the typhoon are likely to be affected bases.

[0052] Even when the disaster-related information relates to another natural disaster, the impact extent identification unit 14 determines the damage determination base (a damaged base or a potentially damaged base) in the same manner as above. The impact extent identification unit 14 then stores resource information indicating the damage determination base in the status storage unit 104 and creates a state in the status storage unit 104 for storing status information (described later) as needed in association with the damage determination base. At this time, the impact extent identification unit 14 may store the information in the status storage unit 104 in a manner that enables identification of whether the base is a damaged base or a potentially damaged base. Since the process to be taken until business recovery differs depending on whether the base is a damaged base or a potentially damaged base, information indicating the process classification may be stored as an example of information for identifying a damaged base or a potentially damaged base. For example, the process classification is set to "disaster occurrence" for a damaged base, and "preparation" for a potentially damaged base.

[0053] Furthermore, based on the relationships between the management data stored in the management data storage unit 101, the impact extent identification unit 14 identifies resources, important processes, important businesses, and related bases that are sequentially linked to the damage determination base determined as described above, and identifies these, along with the damage determination base, as the impact extent of the disaster. The impact extent identification unit 14 then stores resource information indicating the related base in the status storage unit 104 and creates a state in the status storage unit 104 for storing status information (described later) associated with the related base as needed. At this time, the impact extent identification unit 14 may store information in the status storage unit 104 in a manner that allows the related base to be identified. As an example of information for making the related base identifiable, information indicating a process category may be stored. For example, if the base is a related base, the process category is set to "daily."

[0054] Fig. 10 is a schematic diagram for explaining a method for identifying an impact extent by the impact extent identification unit 14. In Fig. 10, the linking relationships between bases, resources, important processes, and important businesses are indicated by lines. For example, important business B1 is linked to two important processes P1 and P2. Important process P1 is linked to three resources R1 to R3, and important process P2 is linked to three resources R3 to R5. Resource R1 linked to important process P1 is linked to one base S1, and two resources R2 and R3 are linked to one base S2.

[0055] Suppose the impact extent identification unit 14 determines that base S1 is a disaster-stricken base. In this case, the impact extent identification unit 14 identifies resource R1, important process P1, and important business B1, which are linked to base S1 in turn, as the impact extent of the disaster. Furthermore, the impact extent identification unit 14 also identifies resources R2 and R3, which are linked to important process P1 in turn, and base S2, as the impact extent of the disaster. Similarly, the impact extent identification unit 14 also identifies important process P2, resources R3 to R5, and R7, and bases S3 and S5, which are linked to important business B1 in turn, as the impact extent of the disaster. In this case, bases S2, S3, and S5 are identified as related bases.

[0056] The impact extent identification unit 14 presents information on the identified impact extent in response to a request from the management terminal 2 or the base terminal 3. For example, as shown in FIG. 11, the impact extent identification unit 14 displays a mark indicating the presence of a base at each location on a map. At this time, the impact extent identification unit 14 displays the marks in a manner that allows affected bases, potentially affected bases, related bases, and other bases (bases outside the impact extent) to be distinguished from one another. In the example of FIG. 11, it is possible to select any important business, any important process, or any business establishment, and it is possible to display only the bases related to the selection.

[0057] The support processing execution unit 15 performs support processing for business continuity or business recovery at the support target bases (damage determination bases and related bases) identified by the impact range identification unit 14 as being within the disaster impact range. The support processing for business continuity mainly includes support processing for continuing important business without interruption. The support processing for business recovery includes support processing for restoring important business that has been interrupted.

[0058] Basically, the support processing execution unit 15 notifies the support target bases identified by the impact range identification unit 14 of the response actions that should be taken for business continuity or business recovery, acquires information such as the execution status of response actions and the execution status of important tasks from the support target bases, and provides various information to the management terminal 2 and the base terminal 3 based on the acquired information, thereby supporting the execution of BCP by managers and employees.

[0059] Furthermore, the log information of the response actions taken by employees is sequentially stored in the action log storage unit 105, and the log information of the operation rate calculated according to the execution status of important tasks is sequentially stored in the operation log storage unit 106. The support processing execution unit 15 presents the log information of the response actions and the log information of the operation rate in response to a request from the management terminal 2 or the base terminal 3. This makes it possible to refer to the response action log and the operation log as past performance, for example, when the operation rate has recovered and important business is being carried out on a daily basis, and to review the BCP as necessary.

[0060] Fig. 3 is a block diagram showing a specific example of the functional configuration of the support process execution unit 15 according to this embodiment. As shown in Fig. 3, the support process execution unit 15 according to this embodiment includes, as functional components, a response action notification unit 151, a status information acquisition unit 152, an operation rate calculation unit 153, a progress management unit 154, a business interruption determination unit 155, an insurance procedure notification unit 156, an action log recording unit 157, an operation log recording unit 158, and an information provision unit 159.

[0061] As described above, the assistance process execution unit 15 executes the following processes through the cooperation of hardware and software. That is, the processes of the specific function blocks 151 to 159 included in the assistance process execution unit 15 are executed by the operation of a program stored in a storage medium such as RAM, ROM, a hard disk, or a semiconductor memory under the control of a microcomputer (and a DSP, etc.) configured with a CPU, RAM, ROM, etc.

[0062] The response action notification unit 151 notifies the base terminals 3 of the support target bases identified as being within the disaster's impact range by the impact range identification unit 14 of response actions that should be taken for business continuity or business recovery. As described above, information indicating the support target bases identified as being within the disaster's impact range is stored in the status storage unit 104. In addition, information indicating response actions that should be taken for business continuity or business recovery is stored as management data in the management data storage unit 101. In addition, BCP information including the execution procedures for the response actions and the target completion times for each response action is also stored as management data in the management data storage unit 101.

[0063] The response action notification unit 151 notifies the base terminals 3 of one or more support target bases of response actions appropriate to the base, based on the information stored in the management data storage unit 101 and the status storage unit 104. At this time, the response action notification unit 151 sequentially notifies the base terminals 3 of response actions appropriate to the situation at a timing appropriate to the situation, in accordance with the execution procedure for each response action indicated in the BCP information, taking into account the execution status of the response action and the execution status of the important task acquired from the base terminal 3 by the status information acquisition unit 152. The response action information notified here may include the content of the response action as well as the designated start time of the response action.

[0064] Basically, the response action notification unit 151 notifies the next response action indicated in the BCP execution procedure when it is confirmed by a notification from the base terminal 3 that the notified response action has been completed or is no longer necessary, or when it is confirmed by a notification from the base terminal 3 that an important task related to the notified response action has been completed or is currently being executed. The response action execution procedure may be defined in relation to multiple response actions at one base, or may be defined in relation to multiple response actions at multiple bases. The response action to be notified is not limited to one at a time, and multiple response actions may be notified at a time.

[0065] For example, the response action notification unit 151 notifies the base terminal 3 of the affected base among the support target bases identified by the impact range identification unit 14 as being within the impact range of the disaster of a life-threatening initial response action, and then notifies the base terminal 3 of the affected base among the support target bases identified by the impact range identification unit 14 as being within the impact range of the disaster of at least one of a response action to avoid damage and a response action to prepare for a disaster, to the base terminal 3 of the related base. Furthermore, the response action notification unit 151 notifies the base terminal 3 of the related base of a response action to be performed at a related base in accordance with the execution status of the important task at the damage determination base, based on information indicating the execution status of an important task related to an important process in which the damage determination base is involved, as described with reference to FIG.

[0066] The status information acquisition unit 152 acquires, as needed, from the base terminal 3 of the support target base, status information indicating the execution status of the response action notified to the support target base by the response action notification unit 151 (hereinafter, this status information is particularly referred to as action execution status information), and stores the acquired status information in the status storage unit 104. The action execution status information is, for example, information indicating whether the notified response action is necessary and whether it has been executed. For example, if the situation does not require the execution of the notified response action, an employee or person in charge of the support target base inputs information indicating this into the base terminal 3 and transmits it to the BCM support system 1. Furthermore, if the situation requires the execution of the notified response action, and the execution of the response action is completed, the employee or person in charge inputs information indicating this into the base terminal 3 and transmits it to the BCM support system 1. Note that information indicating that the response action has not been executed, information indicating that the response action is being executed, information indicating that the response action cannot be executed, or the like may also be input into the base terminal 3 and transmitted to the BCM support system 1.

[0067] Furthermore, the status information acquisition unit 152 acquires status information indicating the execution status of important tasks related to important processes (hereinafter, this status information is particularly referred to as task execution status information) from the base terminal 3 of the support target base as needed, and stores the acquired status information in the status storage unit 104. The task execution status information is, for example, information indicating that execution of an important task has started or been completed by taking a notified response action. That is, when an employee or person in charge at the support target base starts or completes execution of an important task, the employee or person in charge inputs information indicating this into the base terminal 3 and transmits it to the BCM support system 1. Note that in addition to information indicating the start or completion of execution of an important task, information indicating that the important task has not been executed, information indicating that the important task is running as usual, or information indicating that the important task cannot be executed may also be input into the base terminal 3 and transmitted to the BCM support system 1.

[0068] The status information acquisition unit 152 also acquires status information indicating the operating status of resources (hereinafter, this status information is particularly referred to as resource operating status information) from the base terminal 3 of the support target base as needed, and stores the acquired status information in the status storage unit 104. The resource operating status information includes, for example, information indicating whether equipment and stockpiles are usable, information indicating the damage status of the equipment and stockpiles, information on the safety of employees, their families, and business partner personnel, information indicating whether employees are available to work, and work status (whether working at the business site, working at another workplace, or their current location while traveling). Employees or personnel at the support target base enter this information into the base terminal 3 and transmit it to the BCM support system 1. The current location of an employee while traveling is detected by a location detection device, such as a mobile terminal carried by the employee, and information indicating the detected current location is transmitted from the mobile terminal to the BCM support system 1 and stored in the status storage unit 104 in real time.

[0069] The operation rate calculation unit 153 calculates the operation rate as needed based on the task execution status information acquired by the status information acquisition unit 152 and stored in the status storage unit 104. Here, the operation rate calculation unit 153 calculates at least one of the operation rate of the entire company, the operation rate of an important business, the operation rate of an important process, and the operation rate of a resource as needed. The operation rate is information indicating the percentage of important tasks that have been executed among the number of important tasks that should be executed. For example, the operation rate of an important business is an operation rate calculated by using the total number of important tasks that should be executed for that important business as the denominator and the number of important tasks that have been executed for that important business as the numerator.

[0070] The progress management unit 154 identifies the progress status of the execution of important tasks for the business continuity plan based on the operation rate calculated from time to time by the operation rate calculation unit 153 and the business continuity plan formulated in advance (BCP information stored as management data in the management data storage unit 101). The BCP information used here is selected according to the important business in question and the type and scale of the natural disaster.

[0071] For example, when the affected area identification unit 14 identifies a support target base, the progress management unit 154 starts measuring the elapsed time from that point. Furthermore, the progress management unit 154 generates a recovery curve that represents the transition of the planned operation rate that is expected when multiple important tasks are operated in order according to the BCP procedures by executing response actions, based on the BCP information stored in the management data storage unit 101. The recovery curve is expressed as a curve on a two-dimensional coordinate system with the horizontal axis representing time and the vertical axis representing the operation rate, which falls to less than 100% at the time of the disaster, and then rises over time until it is restored to 100%.

[0072] For example, the progress management unit 154 calculates the transition of the planned operation rate based on information on the target completion time of the response action, assuming that one important task is operated by completing one or more response actions. Here, when information indicating that the response action notified by the response action notifying unit 151 is not necessary is notified from the base terminal 3 and stored in the status storage unit 104, or when information indicating that the important task is operating normally is notified from the base terminal 3 and stored in the status storage unit 104, the progress management unit 154 may regenerate a recovery curve excluding the corresponding important task.

[0073] The progress management unit 154 compares the operation rate calculated by the operation rate calculation unit 153 at a certain elapsed time with the planned operation rate at the same elapsed time indicated by the recovery curve, and identifies the progress status regarding the execution of important tasks with respect to the recovery curve generated based on the BCP information (and status information). The identified progress status may be, for example, information indicating the difference between the operation rate at the time when the operation rate was calculated by the operation rate calculation unit 153 and the planned operation rate. Alternatively, it may be information indicating the difference between the time when the operation rate was calculated by the operation rate calculation unit 153 and the time when the planned operation rate, which has the same value as the calculated operation rate, is expected to be achieved on the recovery curve.

[0074] When the impact extent identification unit 14 determines that a business partner's base is a disaster-stricken base, the business interruption determination unit 155 determines whether to continue or suspend the execution of the important business that is linked to the business partner's base in turn. In the example shown in FIG. 10, when the business partner's base S5 is determined to be a disaster-stricken base, the important business that is linked to the business partner's base in turn is important business B1. The business interruption determination unit 155 determines whether to continue or suspend the execution of this important business B1. When it is determined that the important business is to be suspended, the business interruption determination unit 155 notifies the base terminal 3 and the management terminal 2 of the base that is linked to the important business to be suspended that the important business is to be suspended.

[0075] For example, the business interruption determination unit 155 determines whether or not it is possible to expect to receive sales revenue from a business partner (purchasing destination) that has been determined to be a disaster-stricken location, based on the status information transmitted from the base terminal 3 of the business partner (purchasing destination). If it is determined that no revenue is possible, it determines to interrupt the execution of important businesses that are sequentially linked to the base of the business partner.

[0076] Here, the criteria for determining whether or not a deposit is expected can be set arbitrarily. For example, if at least one of the following situations (1) to (3) applies, it may be determined that a deposit is not expected. (1) When it is confirmed that there are facilities or stockpiles that cannot be used based on the resource operation status information transmitted from the business partner's base terminal 3. (2) When it is confirmed that there is an unexecutable response action based on the action implementation status information transmitted from the business partner's base terminal 3. (3) When it is confirmed that there is an important task that cannot be executed based on the task execution status information transmitted from the client's base terminal 3.

[0077] In addition to determining whether or not a payment of sales to a business partner can be expected, the business suspension determination unit 155 may also determine whether or not a withdrawal will be involved in the execution of an important process linked to the business partner, and may decide to suspend the important business when a payment of sales from the business partner cannot be expected and it is determined that a withdrawal will be involved in the execution of the important process. In this case, the response action notification unit 151 may notify the base terminal 3 or the management terminal 2 that the withdrawal will be postponed as a response action.

[0078] In addition, when the business interruption determination unit 155 decides to interrupt an important business, the response action notification unit 151 may identify resources that are linked to the important business to be interrupted in turn and are also shared with the continuing important business, and notify the base terminal 3 of the identified resource that the response action is to focus on executing the continuing important business.

[0079] 10, if a client's base S5 becomes a disaster-stricken base and decides to suspend important business B1, the resources sequentially linked to important business B1 are resources R1 to R5, and among these, the resource that is also shared with important business B2, which continues, is resource R5. In this case, the response action notification unit 151 notifies the base terminal 3 of resource R5 that important business B1 will be suspended and that efforts should be focused on the execution of important business B2 as a response action.

[0080] Note that, although an example has been described here in which, when the impact extent identification unit 14 determines that a business partner's base is a disaster-stricken base, it is determined to continue or suspend the execution of important businesses that are sequentially linked to the business partner's base, the present invention is not limited to this. For example, when the impact extent identification unit 14 determines that a business office's base is a disaster-stricken base, it may be determined to continue or suspend the execution of important businesses that are sequentially linked to the business office's base. In this case, the business suspension determination unit 155 may determine whether or not the execution of an important process linked to the business office involves a withdrawal, and may determine to suspend the important business if it is determined that the execution of the important process involves a withdrawal.

[0081] When the business interruption determination unit 155 has decided to interrupt an important business linked to a resource that has become a disaster-stricken base, the insurance procedure notification unit 156 checks whether or not the insurance allowance amount for the resource is expected to be paid, based on the damage status of the equipment and stockpiles indicated by the resource operation status information acquired from the base terminal 3 of the disaster-stricken base and information regarding payment stored as management data in the management data storage unit 101, and if there is an expectation of payment, issues a notification to the management terminal 2 to urge the execution of the procedure. This notification may also be sent to the base terminal 3 in question.

[0082] The action log recording unit 157 records, as action log data in the action log storage unit 105, the response action information notified to the support target base by the response action notification unit 151 as needed and the action execution status information acquired from the support target base by the status information acquisition unit 152 as a response to the notification, in association with the disaster indicated by the disaster-related information stored in the disaster-related information storage unit 103. Here, the action log recording unit 157 records the action log data for each support target base.

[0083] The operation log recording unit 158 ​​associates the operation rate calculated by the operation rate calculation unit 153 as needed with the disaster indicated by the disaster-related information stored in the disaster-related information storage unit 103 and records the operation log data in the operation log storage unit 106. Here, the operation log recording unit 158 ​​records the operation log data for each support target base. Note that the operation log recording unit 158 ​​may record task execution status information and resource operating status information acquired from the support target base by the status information acquisition unit 152 as needed, together with the operation rate at each point in time, as operation log data in the operation log storage unit 106.

[0084] The information providing unit 159 provides, in response to a request from the management terminal 2 or the base terminal 3, on a specified display screen, the response action information notified by the response action notification unit 151, the status information acquired by the status information acquisition unit 152, the operation rate calculated by the operation rate calculation unit 153, the progress of important tasks identified by the progress management unit 154, information regarding the continuation or suspension of important businesses determined by the business suspension determination unit 155, and information regarding insurance procedures notified by the insurance procedure notification unit 156.

[0085] 12 is a diagram showing an example of a dashboard screen (top screen) provided by the information provider 159 when logging in to the BCM support system 1 from the management terminal 2 and the base terminal 3. As shown in FIG. 12, the dashboard screen displays an overall company operation rate 1201, an operation rate 1202 of important businesses, an operation rate 1203 of business locations, a timeline 1204, and overall company progress status information 1205.

[0086] The overall company operation rate 1201, the important business operation rate 1202, and the business establishment operation rate 1203 show the results calculated by the operation rate calculation unit 153. The timeline 1204 shows the period covered by the warning or warning in the form of a bar graph when the disaster-related information stored in the disaster-related information storage unit 103 includes information on warnings or warnings. The progress status information 1205 shows the execution status of important tasks identified by the progress management unit 154, with the horizontal axis representing time and the vertical axis representing the overall company operation rate.

[0087] 12, the progress status information 1205 includes a recovery curve 1211 generated based on the BCP information (and status information), a target time bar 1212 indicating the target recovery time from the time of disaster occurrence, an elapsed time bar 1213 indicating the elapsed time from the time of disaster occurrence to the current time, and a current operation rate bar 1214 indicating the position on the recovery curve 1211 corresponding to the operation rate calculated by the operation rate calculation unit 153. The recovery curve 1211 shown here indicates the transition of the planned operation rate when, after a large-scale natural disaster such as a major earthquake occurs and the operation rate drops from 100% to 0%, a BCP formulated in advance for the large-scale natural disaster is executed to gradually restore important businesses.

[0088] In the progress status information 1205, the difference between the elapsed time bar 1213 and the current operation level bar 1214 on the horizontal time axis indicates the delay (or in some cases the advance) of the actual operation level relative to the planned operation level (the degree of recovery of important projects based on the execution status of important tasks) at the current time assumed by the recovery curve 1211. The delay here means the time lag until the actual operation level reaches the planned operation level at the current time. Note that it is also possible to recognize the difference between the actual operation level and the planned operation level at the current time by reading the operation levels at the points where the elapsed time bar 1213 and the current operation level bar 1214 intersect with the recovery curve 1211.

[0089] Fig. 13 is a diagram showing an example of a business confirmation screen provided by the information providing unit 159 when an arbitrary important business is selected on the dashboard screen of Fig. 12. As shown in Fig. 13, the business confirmation screen displays an operation rate 1301 of the selected important business, a timeline 1302, progress status information 1303 of the selected important business, and status information 1304 indicating the status of important processes and resources linked to the selected important business. In the progress status information 1303 shown in Fig. 13, the vertical axis represents the operation rate of the selected important business.

[0090] The status information 1304 indicates the current execution status of the important processes associated with the selected important business, and includes task execution status information and resource operation status information. It may also include action execution status information. In the example of FIG. 13, some important processes include important tasks that cannot be executed, and therefore the inability to execute the important processes is indicated by an "unexecutable" icon. Furthermore, an exclamation mark icon indicates that some kind of problem has occurred with the resources of the organization, equipment, or business partners.

[0091] When an arbitrary important process is selected in the display area of ​​the status information 1304, the screen transitions to a process confirmation screen that shows the status of the selected important process. The process confirmation screen has the same configuration as the business confirmation screen, but the status information area of ​​the process confirmation screen displays a list of the status of resources linked to the selected important process and the implementation status of important tasks related to the important process. Furthermore, when an arbitrary status is selected in the display area of ​​the status information 1304, the reason for the status is displayed, for example, in a pop-up screen. Furthermore, when an arbitrary resource is selected, the screen transitions to a separate screen that shows the status of the selected resource.

[0092] Fig. 14 is a diagram showing an example of an establishment confirmation screen provided by the information providing unit 159 when an arbitrary establishment is selected on the dashboard screen of Fig. 12. As shown in Fig. 14, the establishment confirmation screen displays the location 1401 of the selected establishment, a process category 1402, the establishment's operating rate 1403, a timeline 1404, progress status information 1405 of the selected establishment, and status information 1406 indicating the implementation status of the response action notified to the selected establishment.

[0093] The process category 1402 is displayed as "disaster occurrence" if the business establishment is a disaster-stricken base, "preparation" if it is a base at risk of disaster, and "daily life" if it is a related base. In this way, the BCM support system 1 of this embodiment not only implements BCP at bases that have actually been affected by disaster, but also supports the implementation of BCP at bases at risk of disaster. This has the advantage of allowing employees to practice response actions to avoid disaster or to prepare for disasters in the event of natural disasters that can occur on a daily basis, such as typhoons or snowfall.

[0094] The progress status information 1405 shown in Figure 14 shows the change in the planned operation rate when a medium- or small-scale natural disaster such as a typhoon or snowfall occurs and the operation rate drops from 100% to a specified percentage (≠0%), and then important businesses are gradually restored by implementing a BCP that was formulated in advance for the natural disaster.The horizontal axis represents time, and the vertical axis represents the operation rate of the selected business location.

[0095] In the display area of ​​status information 1406, an exclamation mark icon indicates that some kind of problem has occurred in the execution of the notified response action. Furthermore, when any response action is selected, a time period area 1407 is displayed indicating the time period on the recovery curve in which that response action should be executed.

[0096] Fig. 15 is a diagram showing an example of an employee confirmation screen provided by the information providing unit 159 when an arbitrary organization is selected in the display area of ​​the status information 1304 shown in Fig. 13 and an arbitrary employee is selected from the employee list displayed on a separate screen. As shown in Fig. 15, the employee confirmation screen displays bibliographic information 1501 such as the selected employee's name, the place of business where the employee works, the organization to which the employee belongs, and related important businesses, status information 1502 indicating the status of the selected employee and his / her family, status information 1503 indicating the implementation status of the response action notified to the employee, and a map 1504 indicating the employee's location.

[0097] Status information 1503 displays the history of the reported response actions and their implementation status. Map 1504 displays a map of the area around the office location if the employee is working at the office, a map of the area around the other workplace location if the employee is working at another workplace, or a map of the area around the employee's current location if the employee is traveling. Selecting a location mark on the map displays a pop-up with the most recent status.

[0098] The information providing unit 159 also provides, in response to a request from the management terminal 2 or the base terminal 3, a response action log and an operation log as past performance information on a specified display screen based on the log data stored in the action log memory unit 105 and the operation log memory unit 106, for example, when the operating rate has recovered and important business is being carried out on a daily basis.

[0099] Here, the information providing unit 159 may provide the log information in a form of reproducing the various screens exemplified in Figures 12 to 15 by further using the management data stored in the management data storage unit 101. In this case, for example, a time axis slide bar or the like may be further displayed on the various screens exemplified in Figures 12 to 15, and information of any time may be displayed on the screen by operating the slide bar.

[0100] Fig. 16 is a flowchart showing an example of the operation of the BCM support system 1 configured as described above. The flowchart shown in Fig. 16 outlines an example of processing executed when the disaster-related information acquisition unit 13 acquires disaster-related information from the external information provision system 4. Although not shown in the flowchart, each time the response action notification unit 151 notifies the base terminal 3 of a response action, and each time the status information acquisition unit 152 acquires action execution status information from the base terminal 3, the information is stored in the status storage unit 104 and the action log storage unit 105. Furthermore, each time the status information acquisition unit 152 acquires task execution status information or resource operation status information from the base terminal 3, and each time the operation level calculation unit 153 calculates an operation level, the information is stored in the status storage unit 104 and the operation log storage unit 106.

[0101] When the disaster-related information acquisition unit 13 acquires disaster-related information from the external information provision system 4 (step S1), the impact range identification unit 14 identifies the impact range of the disaster based on the management data stored in advance in the management data storage unit 101, the hazard map stored in advance in the hazard map storage unit 102, and the disaster-related information stored in real time in the disaster-related information storage unit 103 (step S2). As described above, the impact range of the disaster includes affected bases, bases that are likely to be affected, related bases, and important businesses, important processes, and resources linked to these.

[0102] Once the extent of the disaster's impact has been identified, the support processing execution unit 15 starts measuring the elapsed time (step S3). Next, the business interruption determination unit 155 determines whether to interrupt the execution of the important business linked to the affected base identified by the impact extent identification unit 14 (step S4). Here, if the business interruption determination unit 155 determines to continue the important business, the processing proceeds to step S6. On the other hand, if it determines to interrupt the important business, the business interruption determination unit 155 notifies the base terminal 3 and the management terminal 2 of the base linked to the important business to be interrupted that the important business will be interrupted (step S5). Thereafter, the processing proceeds to step S6.

[0103] In step S6, the response action notification unit 151 notifies the base terminal 3 of the support target base identified as being within the disaster's affected area by the affected area identification unit 14 of the response action that should be taken for business continuity or business recovery. Here, based on the BCP information (including information on the response action to be taken and the execution procedure) stored as management data in the management data storage unit 101 and the status information stored in the status storage unit 104, the response action to be notified is selected according to the base and the situation at that time, and the notification is sent to the base terminal 3.

[0104] After the corresponding action notification unit 151 notifies the corresponding action, the status information acquisition unit 152 determines whether or not status information (action execution status information, task execution status information, resource operation status information) has been acquired from the base terminal 3 (step S7). Here, if the status information acquisition unit 152 has not acquired any status information, the process proceeds to step S12.

[0105] On the other hand, when the status information acquisition unit 152 acquires the status information, if the business interruption determination unit 155 decides that an important business linked to a resource that has become a disaster-stricken base will be interrupted, the insurance procedure notification unit 156 determines whether or not there is a prospect of receiving payment of the insurance allowance for the resource based on the damage status of the equipment and stockpiles indicated by the resource operation status information acquired from the base terminal 3 of the disaster-stricken base and information regarding payment stored in the management data storage unit 101 (step S8).

[0106] If it is determined that there is no possibility of payment, the process proceeds to step S10. On the other hand, if it is determined that there is possibility of payment, the insurance procedure notification unit 156 notifies the management terminal 2 to prompt the execution of the payment procedure for the insurance allowance amount (step S9). Thereafter, the process proceeds to step S10.

[0107] In step S10, the operation rate calculation unit 153 calculates the operation rate of the entire company, the operation rate of the important business, the operation rate of the important process, and the operation rate of the resource based on the task execution status information stored at that time in the status storage unit 104. Next, the progress management unit 154 generates a recovery curve based on the operation rate calculated by the operation rate calculation unit 153 at that time and the BCP information stored in advance in the management data storage unit 101, and identifies the progress status of the execution of important tasks against the BCP (step S11).

[0108] Next, the support process execution unit 15 determines whether the execution of the BCP has been completed (step S12). For example, the support process execution unit 15 determines whether the operation rate of the entire company calculated by the operation rate calculation unit 153 has reached 100%, and if it has reached 100%, determines that the execution of the BCP has been completed. If the execution of the BCP has not yet been completed, the process returns to step S4. On the other hand, if it is determined that the execution of the BCP has been completed, the process of the flowchart shown in FIG. 16 ends.

[0109] As explained in detail above, this embodiment is provided with a management data storage unit 101 that stores various management data including the company's important businesses, important processes related to the important businesses, resources allocated to the important processes, and the locations of the resources, and a hazard map storage unit 102 that stores a hazard map. Based on the management data, the hazard map, and disaster-related information obtained from outside, disaster-affected bases and bases that are likely to be affected by disaster are identified, and the resources, important processes, important businesses, and other related bases that are linked to these bases in turn are also identified as the scope of the disaster's impact.

[0110] According to this embodiment configured as described above, it is possible to determine the extent of the impact of a disaster from the perspective of important businesses for a company and important processes related to those businesses, and to support the execution of a business continuity plan.

[0111] In particular, in this embodiment, the scope of impact of the disaster is identified not only for actual disaster-affected bases but also for bases potentially affected in the future, including potential future disasters. Furthermore, the scope of impact of the disaster is identified by tracing the resources, critical processes, and critical businesses associated with those bases, including related bases. In other words, the scope of impact is not only determined whether or not a base has been affected by disaster, but also broadly identified as the scope of impact on the continuity of critical businesses. Furthermore, resources include a company's business locations, employees, and business partners, and employee locations include the locations of the employee's business location, the locations of other workplaces, and the employee's current location while traveling. This allows all bases related to critical businesses to be identified as support-required bases, enabling support for BCP implementation.

[0112] In this embodiment, bases identified as being within the disaster's affected range are designated as support target bases, and the support target bases are notified of response actions to be taken for business continuity or business recovery. At this time, response actions appropriate to the base are notified depending on whether the support target base is a disaster-stricken base, a potentially disaster-stricken base, or a related base. For example, after notifying the disaster-stricken base of life-threatening initial response actions, the support target base is notified of response actions to be taken for business continuity or business recovery. Furthermore, the support target base is notified of at least one of response actions to avoid disaster and response actions to prepare for a disaster. Furthermore, the support target bases are notified of response actions to be taken at the related bases in accordance with the execution status of important tasks at the disaster-determined base. This allows appropriate response actions to be notified for each base, thereby enabling appropriate guidance in the implementation of BCP.

[0113] In addition, in this embodiment, information indicating the execution status of important tasks is acquired from the support target base at any time, the operation rate is calculated based on the acquired information at any time, and the information is provided in response to a request from the management terminal 2 or the base terminal 3. This makes it possible to take appropriate response actions while checking the operation rate during BCP execution. In particular, in this embodiment, the operation rate of the entire company, the operation rate of important businesses, the operation rate of important processes, and the operation rate of resources are calculated at any time. This makes it possible to easily and accurately identify important businesses, important processes, or resources with low operation rates and take appropriate response actions.

[0114] Furthermore, in this embodiment, the progress of the execution of important tasks relative to the recovery curve generated based on the BCP information is identified based on the operation rate calculated as needed and the BCP information formulated in advance, and the information is provided in response to a request from the management terminal 2 or the base terminal 3. This makes it possible to take appropriate action while checking the progress of the recovery status of important businesses during the execution of the BCP.

[0115] In addition, in this embodiment, if it is determined that the receipt of sales from a supplier determined to be a disaster-stricken base cannot be expected based on the status information of the supplier, a decision is made to suspend the execution of the important business linked to the base of the supplier. This makes it possible to take flexible measures such as focusing on other important businesses until the situation becomes such that receipt of sales from the supplier can be expected.

[0116] Furthermore, in this embodiment, when it is decided to suspend an important business, if it is determined that there is a possibility of receiving insurance payments for resources based on the damage status of equipment and stockpiles indicated by the resource operation status information of the affected base, the system prompts the user to carry out the procedures. This allows the user to confirm when and how funds (insurance payments through claims procedures with non-life insurance companies) for replacing equipment required for the important business will be obtained.

[0117] Furthermore, in this embodiment, the response action information notified to the support target base and the action execution status information acquired from the support target base are recorded as action log data, and the task execution status information and resource operation status information acquired from the support target base and the operation rate calculated as needed are recorded as operation log data, and the information is provided in response to a request from the management terminal 2 or the base terminal 3. As a result, when the operation rate has recovered and the process of carrying out important business on a daily basis begins, the action log data and operation log data can be referred to as past performance, and the BCP can be revised as necessary.

[0118] In the above embodiment, an example has been described in which a response action is notified to the base terminal 3 of a support target base identified as being within the disaster's affected area. However, a notification may also be sent to the management terminal 2. In this case, the manager can confirm the response action according to the status of the important business. Here, it may be possible for the manager to input approval / cancellation / modification of the response action notified by the response action notification unit 151 from the management terminal 2 and register it in the BCM support system 1. When the cancellation or modification of the response action is registered in the BCM support system 1, the response action notification unit 151 notifies the base terminal 3 to that effect. In addition, a notification may also be sent to the management terminal 2 for bases not identified as being within the disaster's affected area (bases not targeted for support).

[0119] Furthermore, in the above embodiment, an example has been described in which response actions are notified as needed in accordance with the BCP information pre-stored in the management data storage unit 101, but response action information tailored to the current situation may be generated and notified to the base terminal 3 (and the management terminal 2) based on at least one of information on the extent of the impact of the disaster identified by the impact extent identification unit 14, the status information stored as needed in the status storage unit 104, the operation rate calculated as needed by the operation rate calculation unit 153, and the progress status of important tasks identified as needed by the progress management unit 154. For example, a response action instructing resource substitution may be notified.

[0120] 10, if the impact extent identification unit 14 determines that the base S1 is a disaster-stricken base, there is a possibility that the resource R1 at the disaster-stricken base S1 cannot be used, and therefore a response action may be notified to instruct that the important task of resource R1 be executed by another resource R2 linked to the important process P1 linked to resource R1 instead. Here, if it is determined based on the status information or operation rate of resource R2 that certain conditions cannot be met for substituting resource R2 at base S2 for the important task performed by resource R1 at base S1, a response action may be notified to instruct that the important task of another resource R3 linked to base S2 be executed by another resource R4 at another base S3 linked to the same important process P2 as resource R3.

[0121] Furthermore, in the above embodiment, an example has been described in which a response action is notified as needed in accordance with the BCP information pre-stored in the management data storage unit 101. However, the BCP information may be modified to match the actual situation at the time based on at least one of the status information stored as needed in the status storage unit 104, the operation rate calculated as needed by the operation rate calculation unit 153, and the progress status of important tasks identified as needed by the progress management unit 154. For example, the designated start time of the response action may be reset.

[0122] Furthermore, the extent of the disaster's impact may be re-identified each time the disaster-related information stored in the disaster-related information storage unit 103 is updated or when status information is stored as needed in the status storage unit 104. For example, in the flowchart of Fig. 16, instead of returning from step S12 to step S4, the process may return from step S12 to step S1.

[0123] Furthermore, in the above embodiment, an example has been described in which the action log data stored in the action log storage unit 105 and the operation log data stored in the operation log storage unit 106 are provided as information in response to a request from the management terminal 2 or the base terminal 3. In addition to this, these log data may be used for analysis, and the analysis results may be provided as information to the management terminal 2 or the base terminal 3. Alternatively, the log data may be analyzed while the BCP is being executed, and the BCP information or recovery curve may be modified or response action information to be reported may be generated according to the analysis results.

[0124] For example, the action log data and operation log data recorded at a certain base while the BCP is being executed may be analyzed, and when the disaster-related information stored in the disaster-related information storage unit 103 is updated, the impact on the operation rate at another base may be estimated and the BCP information or recovery curve may be regenerated. When the recovery curve is regenerated, the management terminal 2 and the base terminal 3 may be notified of this. Furthermore, the action log data and operation log data recorded in the past may be analyzed, and when disaster-related information is first stored in the disaster-related information storage unit 103, the impact on the operation rate of future important tasks may be estimated and the BCP information or recovery curve may be generated.

[0125] 13 in response to a request from the management terminal 2 or the base terminal 3, an example has been described in which the status information 1304 includes task execution status information and resource operation status information. Here, an example has been described in which the resource operation status information includes information indicating whether equipment and stockpiles are usable, information indicating damage to the equipment and stockpiles, information on the safety of employees, their families, and business partner personnel, information indicating whether employees are available to work, and work status (working at the business office, working at another workplace, or currently at the location while traveling), but is not limited to this.

[0126] For example, the information indicating the operating status of resources may further include information indicating the respective locations of the equipment and the person in charge at the business partner. FIG. 17 is a diagram showing the relationship between various management data related to critical processes in this case. In the example shown in FIG. 17, the status information acquired about the business partner's equipment includes information indicating the availability of the above-mentioned equipment and stockpiles, the damage status of the equipment and stockpiles, as well as the location (location) of the equipment and the organization (user). Furthermore, the status information acquired about the person in charge at the business partner includes information indicating the safety of the person in charge and the location of the person in charge. Furthermore, the status information acquired about the business partner's equipment includes information indicating the availability of the above-mentioned equipment and stockpiles, the damage status of the equipment and stockpiles, as well as the location (location) of the equipment.

[0127] 17, the status information acquisition unit 152 acquires, as information indicating the operating status of resources, information indicating the locations of the employees, as well as the locations of the facilities of the company and business partners and the locations of the business partner's personnel, from the base terminal 3 of the support target base at any time, and stores the acquired status information in the status storage unit 104 and provides it to the information provision unit 159. The locations of the employees and business partner's personnel may include information indicating specific locations within the base in addition to information indicating the base where they are located.

[0128] When configured in this way, the status information 1304 displayed on the screen as shown in Fig. 13 also displays information showing the status of each employee, equipment, and person in charge of business partners. This enables the on-site manager of the support site, employees, or company administrator to know whether the employees, equipment, and person in charge of business partners assigned as resources are (are) definitely in the locations required for important processes.

[0129] Furthermore, the above-described embodiments are merely examples of specific embodiments for carrying out the present invention, and the technical scope of the present invention should not be construed as being limited thereby. In other words, the present invention can be carried out in various forms without departing from the gist or main characteristics thereof. [Explanation of symbols]

[0130] 1 BCM support system 2 Management terminal 3 Base terminal 4. External information provision system 5. Communication Network 11 Management Data Registration Section 12 Hazard Map Acquisition Section 13. Disaster-related Information Acquisition Department 14 Impact Scope Identification Department 15 Support processing execution unit 101 Management data storage unit 102 Hazard Map Memory Unit 103 Disaster-related information storage unit 104 Status memory unit 105 Action log memory unit 106 Operation log memory unit 151 Response Action Notification Department 152 Status information acquisition unit 153 Operation Rate Calculation Department 154 Progress Management Department 155 Business Interruption Determination Department 156 Insurance Procedure Notification Department 157 Action Log Recording Section 158 Operation Log Recording Department 159 Information Provision Department

Claims

1. a management data storage unit that stores, in a database, one or more important businesses of a company, one or more important processes related to the important businesses, one or more resources allocated to the important processes, and the locations of the resources as management data; a disaster-related information acquisition unit that acquires disaster-related information relating to the occurrence of a disaster from an external source via a communication network; and an impact range identification unit that determines whether or not a base where the resource is located is damaged or likely to be damaged based on the disaster-related information acquired by the disaster-related information acquisition unit, and that identifies, as an impact range of the disaster, a damage determination base that has been determined to be damaged or likely to be damaged, the resources, the important processes, the important businesses, and other related bases that are linked to the damage determination base in turn, based on the management data stored in the management data storage unit. A business continuity support system characterized by:

2. The resources include the business locations of the company, the employees of the company, and the business partners of the company; The location of the employee includes the location of the business establishment to which the employee belongs, the location of the employee's other workplaces other than the said business establishment, and the employee's current location while traveling.

2. The business continuity support system according to claim 1.

3. 3. The business continuity support system according to claim 2, wherein the business establishment of the company includes equipment as the resources, and the business partner of the company includes personnel and equipment as the resources.

4. A business continuity support system as described in any one of claims 1 to 3, further comprising a support processing execution unit that executes support processing for business continuity or business recovery at a base identified as being within the scope of the disaster by the impact scope identification unit as a support target base.

5. The business continuity support system described in claim 4, characterized in that the support processing execution unit notifies the base terminal of the support target base identified by the impact area identification unit as being within the impact area of ​​the disaster of response actions that should be taken for business continuity or business recovery.

6. The business continuity support system described in claim 5, characterized in that the support processing execution unit notifies the bases determined by the impact range identification unit to be at risk of being affected by at least one of response actions to avoid damage and response actions to prepare for a disaster.

7. 6. The business continuity support system according to claim 5, wherein the support process execution unit notifies the response action to a management terminal used by a manager of the company in addition to the base terminal.

8. The business continuity support system according to claim 4, characterized in that the support processing execution unit periodically acquires information indicating the execution status of important tasks related to the important process from the support target base, and periodically calculates the operating rate based on the acquired information.

9. The business continuity support system according to claim 8, characterized in that the support processing execution unit calculates at least one of the overall operating level of the company, the operating level of the important business, the operating level of the important process, and the operating level of the resource at any time.

10. The business continuity support system according to claim 9, characterized in that the support processing execution unit records the operation rate calculated at any time as operation log data in association with the disaster indicated in the disaster-related information acquired by the disaster-related information acquisition unit.

11. 11. The business continuity support system according to claim 10, wherein the support process execution unit records the operation log data for each of the support target bases.

12. The business continuity support system described in claim 5 or 10, characterized in that the support processing execution unit acquires information indicating the implementation status of the response actions notified to the support target base from the support target base at any time, and records the information indicating the response actions notified to the support target base and the implementation status acquired from the support target base as action log data, associated with the disaster indicated in the disaster-related information acquired by the disaster-related information acquisition unit.

13. 13. The business continuity support system according to claim 12, wherein the support process execution unit records the action log data for each of the support target locations.

14. The business continuity support system described in claim 5, characterized in that the support processing execution unit notifies bases among the support target bases identified by the impact area identification unit as being within the impact area of ​​the disaster that are determined to be affected by the disaster of initial response actions that are life-threatening, and then notifies them of response actions that should be taken for business continuity or business recovery.

15. The business continuity support system described in claim 4, characterized in that the support processing execution unit acquires information indicating the execution status of important tasks related to the important processes in which the disaster assessment base is involved from the support target base at any time, and provides the acquired information to the base terminal of the support target base or to a management terminal used by the administrator of the company.

16. The business continuity support system described in claim 4, characterized in that the support processing execution unit acquires information indicating the operating status of the resources from the support target base at any time and provides the acquired information to the base terminal of the support target base or to a management terminal used by the administrator of the company.

17. The resources include the business locations of the company, the employees of the company, and the business partners of the company; The business establishment of the company includes equipment as the resource, and the business partner of the company includes personnel and equipment as the resource, The support process execution unit acquires information indicating the locations of the employees, the equipment, and the personnel from the support target base as information indicating the operating status of the resources, and provides the acquired information to the base terminal or the management terminal.

17. The business continuity support system according to claim 16.

18. The business continuity support system described in claim 5, characterized in that the support processing execution unit acquires information indicating the execution status of important tasks related to the important processes in which the disaster determination base is involved from the disaster determination base at any time, and based on the acquired information, notifies the related base of the response actions that should be taken at the related base in accordance with the execution status of the important tasks at the disaster determination base.

19. The business continuity support system according to claim 8, characterized in that the support processing execution unit identifies the progress status regarding the execution of the important tasks against the business continuity plan based on the operating rate calculated from time to time based on information acquired from the support target base and a business continuity plan formulated in advance.

20. The business continuity support system of claim 19, wherein the support processing execution unit generates a recovery curve that represents the expected change in planned operation rate when multiple important tasks are operated sequentially based on the business continuity plan, and identifies the progress status based on a comparison between the operation rate calculated as needed and the planned operation rate indicated by the recovery curve.

21. The business continuity support system of claim 20, wherein the support processing execution unit generates the recovery curve based on, in addition to the business continuity plan, the execution status of the important tasks obtained from the support target base at any time and the execution status of the response actions obtained from the support target base at any time regarding the response actions notified to the support target base.

22. The resources include the business locations of the company, the employees of the company, and the business partners of the company; The affected area identification unit determines whether or not the resources have been affected by disaster based on the disaster-related information acquired by the disaster-related information acquisition unit, and identifies the important businesses that are linked to the resources determined to have been affected by disaster based on the management data stored in the management data storage unit, The support processing execution unit determines whether to continue or suspend the execution of the important business identified by the impact range identification unit based on the status of at least one of deposits and withdrawals related to the identified important business.

5. The business continuity support system according to claim 4.

23. The business continuity support system described in claim 4, characterized in that the support processing execution unit acquires information indicating the damage status of the resources of the support target base from the support target base identified by the impact range identification unit as being within the impact range of the disaster, and based on the acquired information, checks whether or not there is an expectation of payment of insurance allowance amounts for the resources, and if there is an expectation of payment, prompts the execution of the procedure.

24. a management data storage unit that stores, in a database, one or more important businesses of a company, one or more important processes related to the important businesses, one or more resources allocated to the important processes, and the locations of the resources as management data; a disaster-related information acquisition unit that acquires disaster-related information relating to the occurrence of a disaster from an external source via a communication network; and an impact range identification unit that determines whether or not a base where the resource is located is damaged or likely to be damaged based on the disaster-related information acquired by the disaster-related information acquisition unit, and that identifies, as an impact range of the disaster, a damage determination base that has been determined to be damaged or likely to be damaged, the resources, the important processes, the important businesses, and other related bases that are linked to the damage determination base in turn, based on the management data stored in the management data storage unit.

1. An information processing device comprising:

Images