JP7664899B2 - Fault information management device, fault information management method, and fault information management system - Google Patents

Description

The present invention relates to a fault information management device, a fault information management method, and a fault information management system.

Banks and other financial institutions use large-scale computer systems (so-called accounting systems) to process accounting accounts. In recent years, the promotion of FinTech and DX (Digital Transformation) initiatives and the diversification of products have improved convenience for general users, but the impact on society in the event of a system failure has become extremely large. For this reason, it is necessary to vigorously promote the prevention of such system failures and measures to be taken in the event of a system failure.

To achieve this goal, it is important to collect a lot of information about system failures. For example, Patent Document 1 discloses a technology for a bank to automatically obtain information about failures that occur in automated transaction devices such as ATMs (Automated Teller Machines). The automated transaction device has a banknote section that handles banknotes, a detection section that detects failures in the banknote section, and a device control section that controls the device. When a failure is detected by the detection section, the device control section creates failure information that is information about the state of the failure in the automated transaction device and the failure history, and a server stores the failure information sent from the automated transaction device and displays the stored failure information.

JP 2015-207228 A

Thus, currently, financial institutions generally accumulate their own information on failures that occur within their institutions and know-how on countermeasures. Although financial institutions can collect information on large-scale failures from general media, the information that can be obtained is limited. As a result, when financial institutions attempt to carry out operations such as updating their systems to launch new services or introducing new systems, they do not have sufficient information to refer to, making it difficult to predict the risk of system failures occurring, which can be an obstacle to carrying out said operations. Furthermore, even when taking measures against system failures that occur, the information accumulated within the organization itself may not be sufficient.

The present invention has been made in light of these circumstances, and its purpose is to provide a fault information management device, a fault information management method, and a fault information management system that can facilitate the collection of information on system faults and enable appropriate use of that information.

One aspect of the present invention for solving the above problem is a fault information management device that includes a storage device that stores information on a system fault related to a financial institution received from a first information processing device, and a control device that executes a compensation calculation process that calculates the value of the system fault information and generates compensation information corresponding to the calculated value, and a burden calculation process that receives a request for information on a system fault related to the financial institution from a second information processing device, generates information that satisfies the received request from the stored system fault information, and generates burden information corresponding to the value of the generated information.

Another aspect of the present invention for solving the above problem is a fault information management system including a first information processing device, a second information processing device, and a fault information management device, the fault information management device includes a storage device that stores information on a system fault related to a financial institution received from the first information processing device, and a control device that executes a compensation calculation process that calculates the value of the information on the system fault and generates compensation information corresponding to the calculated value, and a burden calculation process that receives a request for information on the system fault related to the financial institution from the second information processing device, generates information that satisfies the received request from the stored information on the system fault, and generates burden information corresponding to the value of the generated information, and in the compensation calculation process, sets the generated compensation information in the first information processing device or a device associated with the first information processing device, and in the burden calculation process, sets the generated burden information in the second information processing device or a device associated with the second information processing device.

According to the present invention, it is possible to promote the collection of information on system faults and to appropriately utilize the information on system faults.
Configurations and effects other than those described above will become apparent from the following description of the embodiments.

1 is a diagram illustrating an example of a configuration of a fault information management system according to an embodiment of the present invention. FIG. 13 is a diagram showing an example of a standard charging point management table. FIG. 13 illustrates an example of an influence extent rank management table. FIG. 13 is a diagram showing an example of a rebate calculation condition table. FIG. 11 is a diagram showing an example of a charge calculation condition table. 2 is a diagram illustrating an example of a hardware configuration of each information processing device in the fault information management system. FIG. FIG. 2 is a flow diagram illustrating an example of a process performed in the fault information management system. FIG. 11 is a diagram showing an example of a menu screen. FIG. 13 is a diagram showing an example of a fault information registration screen. 13 is a diagram showing an example of a correspondence relationship between the rank of the extent of influence and the pattern of the extent of influence in that case; FIG. FIG. 13 is a diagram showing an example of an inquiry screen. FIG. 13 is a diagram showing an example of an individual request input screen. FIG. 13 is a diagram showing an example of a query list display screen. FIG. 13 is a diagram showing an example of a system fault individual display screen. FIG. 13 is a diagram showing an example of a system fault individual option display screen. FIG. 13 is a diagram showing an example of a system failure individual limited disclosure display screen. FIG. 13 is a diagram illustrating an example of a feedback input screen.

The following describes in detail an embodiment of the present invention with reference to the drawings.

1 is a diagram showing an example of the configuration of a fault information management system 1 according to the present embodiment. The fault information management system 1 includes one or more fault information providing terminals 10 (first information processing device) managed by each financial institution such as a bank (hereinafter also referred to as the provider side), a fault information management device 20 that manages information on system faults that have occurred in an information processing system such as an accounting system used by the provider side, and one or more fault information viewing terminals 30 (second information processing device) managed by each financial institution such as a bank or a business operator (hereinafter also referred to as the user side) that utilizes the information on system faults managed by the fault information management device 20 for various business operations.

The trouble information providing terminal 10 and the trouble information viewing terminal 30 may be managed by the same entity. The trouble information providing terminal 10, the trouble information management device 20, and the trouble information viewing terminal 30 may be connected to each other via, for example, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), etc.
, or via a wired or wireless communication network 5 such as a dedicated line.

The fault information management device 20 receives information (hereinafter referred to as fault information) about a system fault that has occurred in an information processing system (hereinafter referred to as an accounting system) managed by the provider from the provider's fault information providing terminal 10. The fault information management device 20 then provides the provider's fault information providing terminal 10 with a compensation (remuneration) corresponding to the value of the received information. In this embodiment, the fault information management device 20 pays an information provision fee as compensation.

Meanwhile, the fault information management device 20 receives a request for information on a system fault from the fault information viewing terminal 30 on the user side, generates information that satisfies the received request from the fault information, and transmits the generated information (answer information) to the fault information viewing terminal 30. The fault information management device 20 then charges the user a fee corresponding to the value of the answer information. In this embodiment, the fault information management device 20 charges the user a usage fee as this fee and settles the payment.

In addition, when the fault information management device 20 receives information related to the answer information (feedback on the answer information) from the fault information viewing terminal 30 on the user side, it performs a discount process to reduce the above-mentioned burden according to the value of the information.

Next, the functions of the fault information management device 20 will be described in detail.
First, as shown in FIG. 1, the trouble information management device 20 has functional units, namely, a trouble information receiving unit 201 that performs processing related to the trouble information provided by the trouble information providing terminal 10, and a trouble information viewing unit 202 that performs processing in response to requests related to trouble information from the trouble information viewing terminal 30.

The fault information receiving unit 201 receives fault information from the fault information providing terminal 10 and stores the received information in the fault information DB 300.

In this embodiment, the fault information includes information essential for identifying the configuration of the accounting system related to the system fault (hereinafter referred to as basic information), information identifying the content of the system fault (hereinafter also referred to as event information or base information), and information on the background of the occurrence of the system fault (hereinafter also referred to as background information or optional information). Event information includes, for example, information on the scope of the impact of the system fault.

In addition, some of the background information includes information that is particularly useful for preventing or responding to system failures (hereinafter referred to as limited disclosure information). In this embodiment, the type of limited disclosure information is set in advance by the administrator. Details of the event information and background information will be described later.

The fault information receiving unit 201 includes at least a fee calculation unit 203 .
The compensation calculation unit 203 calculates a value of the received fault information, and sets compensation information corresponding to the calculated value in the fault information providing terminal 10 or a predetermined settlement device associated with the fault information providing terminal 10 .

For example, the consideration calculation unit 203 calculates a value (first value) of information (event information) that specifies the contents of a system failure, and calculates a value (second value) higher than the first value for information (background information) on the background of the occurrence of the system failure. Specifically, the consideration calculation unit 203 calculates each value based on a standard charging point management table 500 that specifies the relationship between each item of the event information and background information and a parameter (standard charging parameter) that is the standard of the value for each item, and a rebate calculation condition table 700 that stores information on the calculation conditions of the consideration. Details of the standard charging point management table 500 and the rebate calculation condition table 700 will be described later.

When the event information is information on the impact scope of a system failure, the compensation calculation unit 203 calculates a value according to the impact scope. Specifically, the compensation calculation unit 203 calculates the compensation based on an impact scope rank management table 600 that specifies the relationship between each impact scope and the criteria for the compensation calculation method. Details of the impact scope rank management table 600 will be described later.

The fee calculation unit 203 also stores the fault information received from the fault information providing terminal 10 in the fault information DB 300.

Next, the fault information viewing unit 202 includes at least a burden calculation unit 204 .
The burden calculation unit 204 receives a request for the provision of disability information from the disability information viewing terminal 30, generates information (result information) that satisfies the received request from the disability information DB 300, and sets burden information corresponding to the value of the generated information in the disability information viewing terminal 30 or a payment device associated with the disability information viewing terminal 30.

The burden calculation unit 204 calculates the value of the result information based on the standard charging point management table 500 and the charging calculation condition table 800 that stores information about the burden calculation conditions. Details of the charging calculation condition table 800 will be described later.

The burden calculation unit 204 receives, as a request for providing fault information, from the fault information viewing terminal 30, a first request (search request) including search conditions for fault information recorded in the fault information DB 300, or a second request (processing request) including a request to the administrator of the fault information management device 20 to process data. Note that the processing request may be accompanied by information on a response deadline (processing deadline).

Then, when the burden calculation unit 204 receives a search request, it generates result information that satisfies the search request.

When the burden calculation unit 204 receives a processing request, it accepts input of the processing contents (hereinafter referred to as processing contents) from the administrator or user side, extracts and processes information from the fault information DB 300 based on the input processing contents, and generates result information that satisfies the processing request based on the processed information.

In this embodiment, the processing includes a process of searching for fault information based on keywords selected by the administrator of the fault information management device 20 based on conditions previously specified by the user in the processing request (specified keyword search), a process of extracting and aggregating fault information performed by the administrator of the fault information management device 20 based on aggregation conditions previously specified by the user in the processing request (information aggregation listing), a process of searching for specific cases of system faults performed by the administrator of the fault information management device 20 based on search conditions previously specified by the user in the processing request (specific case search), a process of searching for cases of system faults similar to the system fault performed by the administrator of the fault information management device 20 based on system fault keywords previously specified by the user in the processing request (similar case search), and a process of statistical analysis of past system faults related to the system fault performed by the administrator of the fault information management device 20 based on statistical conditions for system faults previously specified by the user in the processing request (statistical information analysis). However, the types of processing are not limited to these.

The burden calculation unit 204 displays the response information that satisfies the request (search request or processing request) received from the fault information viewing terminal 30 on the screen of the fault information viewing terminal 30.

The burden calculation unit 204 also stores the contents of the processing performed in response to the search request or processing request in the usage history DB 400.

Furthermore, the burden calculation unit 204 performs a discount process on the burden in a predetermined case. That is, the problem information viewing unit 202 accepts input of information related to the response information (feedback information) from the problem information viewing terminal 30, calculates the value of the input information, and calculates the discounted value (burden) by subtracting the calculated value of the information from the value related to the calculated result information.

In this embodiment, there are two types of discounts in the discount process. That is, there is a discount when the content of the feedback is useful for preventing a system failure or responding to a system failure that has already occurred (for example, effective measures or responses, feedback of similar cases; hereinafter referred to as a first discount), and a discount according to the amount of information in the feedback (hereinafter referred to as a second discount). However, this is not intended to limit the types of discount processes.

(Standard charging point management table)
2 is a diagram showing an example of the standard charging point management table 500. The standard charging point management table is a database that specifies the relationship between each item of fault information and the standard charging point for calculating the price and burden related to that item.

The standard charging point management table 500 has the following data items: a charging number 501, a category 502 in which the type of target fault information (event information or background information) is set, an item 503 in which the item of that fault information is set, a standard charging point 504 in which the standard charging point for that item is set, and a DB management 505 that indicates whether input of that item by the provider is mandatory.

In the example shown in the figure, the fields for information on the scope of impact, information on the business category, input of the business that occurred, the date the cause was discovered, and the date on which countermeasures were completed are required, while the other input fields are optional. In addition, the standard charging point for background information ("2") is higher than the standard charging point for event information ("1").

As shown in the figure, for the impact scope items in the event information, the standard charging points are managed by the impact scope rank management table 600, which is a different table from the standard charging point management table 500.

(Influence range rank management table)
3 is a diagram showing an example of an impact range rank management table 600. The impact range rank management table 600 is a database that stores the size (rank) of the impact range of a system failure and a standard charging point (here, specifically referred to as an impact range coefficient) related to the calculation of the price and burden according to the size, in association with each other.

The impact range rank management table 600 has the following data items: rank number 601, which sets the number of the range (rank) affected by the system failure; rank name 602, which sets information about the rank name; category 603, which sets information specifying the size of the impact range indicated by that rank; and coefficient 604, which sets the impact range coefficient related to that rank.

In this embodiment, the ranks in descending order of the impact of a system failure are as follows: rank "A", which is assumed to affect all customers and have unspecified or numerous impacts; rank "B", which is assumed to affect only some customers, with the prospects for recovery unclear or recovery in a short time difficult, and with a limited impact; rank "C", which is assumed to affect only some customers, with a short time recovery certain and with a limited impact; rank "D", which is assumed to affect internal business operations to a certain extent; and rank "E", which is assumed to not affect internal business operations to a certain extent. The higher the rank, the higher the impact range coefficient value.

(Rebate calculation condition table)
4 is a diagram showing an example of a rebate calculation condition table 700. The rebate calculation condition table 700 is a database that defines calculation conditions for a compensation (value) for each type of fault information.

The rebate calculation condition table 700 includes a number 701 in which a number (method number) assigned to each calculation condition of compensation is set, a category 702 in which a category of fault information of a system fault corresponding to the number is set (for example, information that the provider should register the first time, or information that the provider should register from the second time onwards), a registration content 703 in which the type of fault information is set, a number definition 704 in which the number of fault information items that are the unit for calculating compensation is set, an upper limit of the fault information that can be the subject of compensation, and The data items are upper and lower limits 705, which set the upper and lower limit of the number of cases (number of cases per month in this embodiment), a rebate coefficient 706, which sets a weighting value (rebate coefficient) when calculating the amount of compensation per piece of fault information, a frequent case unit price 707, which sets a weighting value (frequent case coefficient) when calculating the amount of compensation when the system fault indicated by the fault information is a frequent fault, and a first case unit price 708, which sets a weighting value (first case coefficient) when calculating the amount of compensation when the system fault indicated by the fault information is a first fault.

In this embodiment, the amount of the compensation is calculated by multiplying the standard charging point determined in the standard charging point management table 500 or the impact range rank management table 600 by the rebate coefficient and the frequent case coefficient or the leading case coefficient, as appropriate, and multiplying this multiplied value (charging point) by a predetermined standard amount. The standard amount is set in advance by an administrator, etc.

Basic information is information required for entering fault information for system faults, and is, for example, infrastructure information (information about the overall configuration of the accounting system managed by the provider, and information about the configuration of the hardware and software that are the components of the accounting system). Basic information is also, for example, business information (an overview of the business, and the development language of the system). Basic information may be set in advance by the administrator, or it may be set by the provider.

The base information is, for example, an overview of the failure event and an overview of the cause of the failure.

Optional information is information that is useful for preventing or responding to the recurrence of a system failure, such as information about measures taken in response to the system failure that has occurred and measures to prevent recurrence. Optional information is, for example, detailed information about the cause of the system failure, detailed information about measures taken in response to the system failure, and detailed information about measures to prevent recurrence to prevent similar system failures from occurring in the future. Note that optional information may also include diagrams.

The restricted disclosure information is information that is particularly useful for preventing or dealing with the recurrence of a system failure, such as information about a third party who has an interest in the system failure. The restricted disclosure information is, for example, detailed information about the impact of the system failure on customers, and information about documents that should be reported to authorities such as government agencies regarding the system failure.

In this embodiment, the value of the rebate coefficient is the same for each of the cases of limited disclosure information, background information, and event information, but the frequent case coefficient and the leading case coefficient are higher when the target fault information is limited disclosure information than when it is background information (not limited disclosure information), and are higher when the target fault information is background information than when it is event information. In other words, the compensation for limited disclosure information is set to be higher than the compensation for background information, and the compensation for background information (second value) is set to be higher than the compensation for event information (first value).

Regarding the frequent occurrence coefficient, if the system failure occurs frequently, it is an example of a system failure that is likely to occur at each financial institution, such as software with a high penetration rate. Also, if the system failure is the first occurrence, it is an example of a system failure that, although it is the first occurrence, requires a response from each financial institution.

(Charge Calculation Condition Table)
5 is a diagram showing an example of a charge calculation condition table 800. The charge calculation condition table 800 is information that defines calculation conditions for the burden (value) on the user side for each type of processing (search processing, processing processing, or discount processing) performed by the fault information management device 20 and for each target and content of the processing.

The charge calculation condition table 800 has the following data items: number 801, which sets a number (method number) assigned to each charge calculation condition; service category 802, which sets the type of processing associated with that calculation method; service content 803, which sets the item of that type of processing; provided information 804, which sets the type of fault information (base information, optional information, or limited disclosure information) that the processing of that item targets; number definition 805, which sets the number of fault information items that are the unit of charge calculation; upper and lower limits 806, which set the upper and lower limits of the number of fault information items that can be the subject of the charge (number per month in this embodiment); charge coefficient 807, which sets a weighting value (charge coefficient) when calculating the amount of the charge per fault information item; and response deadline parameter 808, which sets a weighting value (response deadline parameter) when calculating the amount of the charge according to the response deadline when the type of processing is processing and the processing request has a response deadline.

In this embodiment, the amount of the charge is calculated by multiplying the standard charging point determined in the standard charging point management table 500 or the impact range rank management table 600 by the charging coefficient and the response deadline parameter as appropriate, and multiplying this multiplied value (charging point) by a predetermined standard amount. The standard amount is set in advance by an administrator, etc.

When the type of processing is processing, the service content 803 is set to one of "keyword search" for performing a specified keyword search, "information compilation and listing" for compiling and listing information, "specific case search" for performing specific case search processing, "similar case search" for performing similar case search processing, and "statistical information analysis" for performing statistical information analysis processing.

The response deadline parameter 808 is set with values for the response deadline parameter for each of the cases where the response deadline is a normal period, where the response deadline is a short period (semi-urgent), and where the response deadline is an even shorter period (urgent).

The charge coefficient is higher when the target fault information is limited disclosure information than when it is background information (not limited disclosure information), and is higher when the target fault information is background information than when it is event information. In other words, the charge coefficient is set so that the burden associated with limited disclosure information is greater than the burden associated with background information, which is greater than the burden associated with event information.

6 is a diagram showing an example of a hardware configuration of each information processing device (the fault information providing terminal 10, the fault information management device 20, and the fault information viewing terminal 30) in the fault information management system 1. Each information processing device includes a control device 11 such as a CPU (Central Processing Unit), a main storage device 12 such as a RAM (Random Access Memory) or a ROM (Read Only Memory), an auxiliary storage device 13 such as a HDD (Hard Disk Drive) or an SSD (Solid State Drive), an input device 14 such as a keyboard, a mouse, or a touch panel, an output device 15 such as a display or a touch panel, and a communication device 16 configured of a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like.

The functions of the functional units of each information processing device in the fault information management system 1 described above are realized by the control device 11 reading out a program from the main storage device 12 or the auxiliary storage device 13. Each program can be recorded on a portable or fixed recording medium and distributed, for example. Note that all or part of these programs may be realized using virtual information processing resources provided using virtualization technology, process space separation technology, or the like, such as a virtual server provided by a cloud system. Also, all or part of these programs may be realized by a service provided by a cloud system via an API (Application Programming Interface), for example.
Next, the process performed by the fault information management system 1 will be described.

Figure 7 is a flow diagram illustrating an example of processing performed by the fault information management system 1. This processing is started, for example, when the fault information management device 20 is started.

First, the problem information management device 20 displays a menu screen 850 (described later) on the problem information providing terminal 10 and the problem information viewing terminal 30, respectively, and accepts a request to register problem information from the problem information providing terminal 10 and a request to provide problem information from the problem information viewing terminal 30 (s101).

When the fault information management device 20 receives a request to register fault information from the fault information providing terminal 10 (s102: registration), it executes the process of s110, and when it receives a request to provide fault information from the fault information viewing terminal 30 (s102: inquiry), it executes the process of s120.

(Menu screen)
8 is a diagram showing an example of a menu screen 850. The menu screen 850 includes a registration section 860 for accepting registration of trouble information from the providing side (the trouble information providing terminal 10) and displaying a trouble information registration screen described below, and a query section 870 for attaching a request for provision of information related to trouble information from the using side (the trouble information viewing terminal 30) and displaying a query screen 1100 described below.

As shown in FIG. 7, in s110, the fault information management device 20 displays a fault information registration screen 900, which accepts the registration of fault information from the fault information providing terminal 10, on the screen of the fault information providing terminal 10. When the fault information management device 20 completes the registration of the fault information, it stores the registered fault information in the fault information DB 300. After that, the process of s111 is performed.

(Fault information registration screen)
9 is a diagram showing an example of a trouble information registration screen 900 (the screen is shown separated due to space limitations). The trouble information registration screen 900 includes a trouble event input field 910 for receiving input of each item of the event information among the trouble information, a background information input field 930 for receiving input of each item of the background information among the trouble information, and a content confirmation field 950 for receiving input for confirming the content input on the trouble information registration screen 900.

The failure event input field 910 includes a number field 911 that displays a management number that is automatically set and displayed for each failure information (system failure) to be registered, a subject input field 912 that accepts input of the subject of the system failure, a failure occurrence date input field 913 that accepts input of the date on which the system failure occurred (year, month, day, and hour), a recovery date and time input field 914 that accepts input of the date on which the system was restored from the failure (year, month, day, and hour), a failure duration display field 915 that displays the length of time that the system failure occurred, and an impact scope input field 916 that accepts selection and input of the impact scope of the system failure (for example, whether the impact was limited to the bank's system or extended to systems outside the bank). a business category input field 917 for inputting the system or software affected by the system failure (business category; for example, whether the entire accounting system business was affected (full down), whether a part of the accounting system was affected, or the subsystem or other information processing system of the accounting system that was affected); an occurring business input field 918 for inputting the type of business (occurring business) affected by the system failure; a failure phenomenon input field 919 for inputting the failure phenomenon that occurred due to the system failure (for example, the content of the service that customers were unable to use at an automatic teller machine (ATM)); a cause discovery date input field 920 for inputting the date on which the cause of the system failure was discovered; a cause input field 921 for inputting information indicating the content of the cause (for example, a text explaining the cause); a countermeasure input field 922 for inputting countermeasures to be taken to prevent a similar failure to the system failure from occurring; and a countermeasure completion date input field 923 for inputting the date on which the countermeasures were completed.

The failure duration display field 915 displays the length of time during which the system failure occurred, which is automatically calculated from the value in the failure occurrence date input field 913 and the value in the recovery date and time input field 914.

The business category input field 917 also accepts input of information on the system or software that was directly affected, information on the subsystems or sub-software of that system or software, and information on the subsystems or sub-software of other software that was affected. The business category input field 917 also accepts selection of whether the affected scope is the entire system or software, or just a part of it. The business category input field 917 also accepts input of the details of the impact on the system or software (for example, ATMs have become unusable).

The background information input field 930 includes a design factor input field 931 for accepting input of the event (e.g., the name of the case or system modification that caused the direct cause (fault location) of the system failure; a defect type 932 for accepting input of the type of design cause (e.g., design defect, manufacturing defect); a design process input field 933 for accepting input of the process in which the design cause of the system failure occurred (e.g., basic design, detailed design, manufacturing); an extraction process input field 934 for accepting input of the process in which the design cause should have been discovered (e.g., unit test, integration test; leakage cause); a technical factor input field 935 for accepting input of the technical cause in the system or program that caused the design cause (e.g., variable error, omitted processing); and a motivational cause input field 936 for accepting input of the human (motivational) cause that caused the design cause (e.g., simple mistake, lack of understanding of business use, or lack of confirmation of the design document).

When the content confirmation field 950 is selected, a screen or the like is displayed (not shown) for confirming whether or not to complete the registration based on the content entered on the fault information registration screen 900, and when the completion of the registration is confirmed, the content currently displayed on the fault information registration screen 900, i.e., the registration information for one piece of fault information entered by the provider (information for one management number), is stored in the fault information DB 300 of the fault information management device 20.

Next, as shown in s111 of FIG. 7, the fault information management device 20 stores the fault information (event information, background information, and limited disclosure information) entered on the fault information registration screen 900 in the fault information DB 300. Note that the fault information management device 20 may accept the registration of multiple pieces of fault information at one time.

Then, the fault information management device 20 calculates a fee for the provider of the fault information based on each fault information registered in the fault information DB 300 (s112). This process may be performed at a predetermined interval (e.g., once a month), or may be performed every time fault information is registered in the fault information DB 300, or may be performed at any other timing.

Specifically, first, the fault information management device 20 refers to the fault information DB 300 and identifies each fault information for which a fee is to be calculated and the items in that fault information (for example, it identifies the type of fault information as event information, background information, or limited disclosure information, and each item in the event information and background information for which data has been entered).

At this time, the fault information management device 20 refers to the upper and lower limits 705 of the rebate calculation condition table 700 to check whether the number of registered fault information items for which compensation is to be calculated exceeds the upper limit indicated by the upper and lower limits 705, and if it exceeds the upper limit indicated by the upper and lower limits 705, selects only the number of fault information items equal to the upper limit.

Then, the fault information management device 20 refers to the standard charging point management table 500 and calculates the total value of the standard charging points for each type of fault information for each registered item.

When the fault information is the impact range of the event information (data entered in the impact range input field 916), the fault information management device 20 identifies the standard charging point (impact range coefficient) by referring to the impact range rank management table 600, rather than the standard charging point management table 500, and the information entered in the fault time display field 915, impact range input field 916, and business category input field 917, etc., of the fault information registration screen 900 from the information in the fault information DB 300.

For example, if the impact scope entered in the business category input field 917 is a complete outage, the fault information management device 20 determines that the impact scope is "A" and identifies the standard charging point for "A."

In other cases, if the impact scope entered in the impact scope input field 916 is one or more people outside the bank and the impact time set in the impact time display field 915 is 30 minutes or more, the fault information management device 20 determines the impact scope to be "B" and identifies the standard charging point for "B".

In other cases, if the impact scope entered in the impact scope input field 916 is one or more people outside the bank, and the impact time set in the impact time display field 915 is less than 30 minutes, the fault information management device 20 determines the impact scope to be "C" and identifies the standard charging point for "C."

In other cases, if the impact scope entered in the impact scope input field 916 is one or more people within the bank, the fault information management device 20 determines the impact scope to be "D" and adds the standard charging points for "D".

In other cases, if the impact scope entered in the impact scope input field 916 is 0 people inside and outside the bank, the fault information management device 20 determines the impact scope to be "E" and adds the standard charging points for "E".

In this way, the fault information management device 20 automatically calculates the compensation (here, the standard charging points) according to the scope of the impact of the system fault indicated by the provided fault information, using a predetermined calculation standard.

Figure 10 shows an example of the correspondence between the rank of the impact range determined by the above calculation criteria and the impact range pattern in that case.

Next, the fault information management device 20 refers to the rebate calculation condition table 700, and calculates the charging points by further multiplying the sum of the standard charging points for each type of fault information (event information, background information, and limited disclosure information) of each registered case calculated as described above by the rebate coefficient and the frequent case coefficient or the leading case coefficient.

Specifically, first, the fault information management device 20 obtains the rebate coefficient for each type of fault information based on the rebate coefficient 706 in the rebate calculation condition table 700.

The fault information management device 20 further calculates the similarity between the fault information of each registered case for which the compensation is to be calculated and fault information previously registered, thereby determining whether the fault information of the registered case is a frequent case and whether it is an early case. The fault information management device 20 then obtains a frequent case coefficient from the frequent case 707 in the rebate calculation condition table 700 for the fault information of the registered case that is determined to be a frequent case. The fault information management device 20 also obtains an early case coefficient from the early case 708 in the rebate calculation condition table 700 for the fault information of the registered case that is determined to be an early case.

For each type of registered fault information, the fault information management device 20 calculates the charging points for each type of fault information by multiplying the standard charging points for that type by the acquired rebate coefficient and the acquired frequent case coefficient or leading case coefficient (or neither).The fault information management device 20 then calculates the amount of compensation by adding up the charging points for each type of fault information and multiplying the total value of these charging points by a predetermined standard amount.

Then, the fault information management device 20 pays the calculated compensation to the provider (s112). For example, the fault information management device 20 transmits payment information including the calculated compensation to the fault information providing terminal 10 or a specified payment device (not shown) linked to the fault information providing terminal 10. This allows the provider to obtain the compensation.

On the other hand, when the trouble information management device 20 receives a request for providing trouble information from the trouble information viewing terminal 30 (s102: inquiry), it displays an inquiry screen 1100 on the screen of the trouble information viewing terminal 30 (s120) that accepts a search request (search process) and its search conditions, or a processing request (processing process) and its processing contents from the trouble information viewing terminal 30. At this time, the trouble information management device 20 calculates the burden to be imposed on the user side for the search request or processing request.

(Inquiry screen)
11 is a diagram showing an example of an inquiry screen 1100. The inquiry screen 1100 includes a list search selection field 1110 for accepting the selection of a search process, a keyword search field 1120 for accepting the selection of a search process together with the input of search conditions, an individual request selection field 1130 for displaying an individual request input screen 1200 for accepting the input of processing contents, and an execution confirmation field 1140 for accepting the confirmation of the input and returning to the inquiry screen 1100.

The list search selection field 1110 includes a search period input field 1111 that accepts input of a period as a search criterion, and a number input field 1112 that accepts input of the number of pieces of fault information to search for as a search criterion.

(Individual request input screen)
12 is a diagram showing an example of an individual request input screen 1200 that is displayed when the individual request selection field 1130 is selected. The individual request input screen 1200 includes an individual request lineup input field 1210 for receiving input of the type of processing and the processing content, an inquiry information selection field 1220 for receiving selection of the type of fault information to be processed (base information, optional information, or limited disclosure information), a response deadline option input field 1230 for receiving designation of the transmission deadline (response deadline) of result information for the processing, and an execution confirmation field 1240 for receiving designation of confirmation of input.

The individual request lineup input field 1210 includes a lineup selection field 1211 that accepts the selection of the type of processing, a request content input field 1212 that accepts the input of the processing content of the selected processing, and a number of inquiries input field 1213 that accepts the input of the number of pieces of fault information to be extracted by the processing.

In the request content input field 1212, for example, the user inputs keywords related to the system failure (in the case of a specified keyword search, for example, the name of the software or hardware, or the name of an external data center), the content to be aggregated (in the case of information aggregation and listing, for example, "a list of measures to prevent recurrence of past cases of SI errors"), information on system failure cases (in the case of a specific case search, for example, "cases where performance was not achieved during system development"), system configuration information (in the case of a similar case search, for example, the name of the OS (Operating System) or language), or the content and target period to be subjected to statistical processing (in the case of statistical information analysis, for example, "tendencies in causes of open API failures").

When the execution confirmation field 1240 is filled in, the content currently displayed on the individual request input screen 1200, i.e., the processing and processing content specified by the user, are stored in the usage history DB 400 of the fault information management device 20.

Next, as shown in s121 of FIG. 7, when the fault information management device 20 receives input of a search process and search conditions (s121: search), it executes processing of s122, and when it receives input of a processing process and processing contents, it executes processing of s123.

In s122, the fault information management device 20 searches for fault information that matches the search criteria entered in s120 by referring to the fault information DB 300, and generates the searched content as result information. In addition, the fault information management device 20 calculates the charging points related to the user's burden based on the generated result information. After that, the process of s124 is performed.

In s123, the fault information management device 20 generates result information from the fault information DB 300 based on the processing content input in s120. In addition, the fault information management device 20 calculates the charging points related to the user's burden based on the generated result information. After that, the process of s124 is performed. Note that, if a response deadline has been set on the individual request input screen 1200, the process of s123 is performed by the time indicated by the response deadline.

Here, a specific example of the generation of the result information in s123 will be described.
For example, when the type of processing is a specified keyword search, the fault information management device 20 accepts input from the administrator of one or more related keywords based on the search keyword input in s120. The fault information management device 20 searches the fault information DB 300 for fault information that matches the input related keywords, and displays it on the screen. The fault information management device 20 accepts input of fault information to be used as result information from among the displayed fault information, and treats the input fault information as result information.

For example, when the type of processing is information aggregation and listing, the fault information management device 20 accepts input of aggregation conditions that satisfy the processing content input in s120 from the administrator. The fault information management device 20 extracts fault information that meets the input aggregation conditions from the fault information DB 300, aggregates the information, and treats the aggregation results as result information.

For example, when the type of processing is a specific case search, the fault information management device 20 accepts input from the administrator of one or more keywords (keywords related to the case) related to the processing content based on the processing content (case information) input in s120. The fault information management device 20 searches the fault information DB 300 for fault information that matches the input keywords and displays it on the screen. The fault information management device 20 accepts input of fault information to be used as result information from among the displayed fault information, and treats the input fault information as result information.

For example, when the type of processing is a similar case search, the fault information management device 20 accepts input from the administrator of one or more keywords (keywords of similar cases) related to the processing content based on the processing content (case information) input in s120. The fault information management device 20 searches the fault information DB 300 for fault information that matches the input keywords and displays it on the screen. The fault information management device 20 accepts input of fault information to be used as result information from among the displayed fault information, and treats the input fault information as result information.

For example, when the type of processing is statistical information analysis, the fault information management device 20 accepts input from the administrator of one or more keywords (keywords necessary for statistical analysis) related to the processing content based on the processing content (method of statistical information analysis and target period) entered in s120. The fault information management device 20 searches the fault information DB 300 for fault information that matches the input keywords and displays it on the screen. The fault information management device 20 accepts input of the analysis content by the administrator based on the displayed screen, and treats the input analysis content information as result information.

Next, a specific example of the method of calculating the charging points in s122 and s123 will be described.
In the case of s122, the fault information management device 20 calculates the number of retrieved fault information for each type of fault information. At this time, the fault information management device 20 refers to the upper and lower limits 806 of the charge calculation condition table 800, and checks whether each number exceeds the upper limit indicated by the upper and lower limits 806. If the number exceeds the upper limit indicated by the upper and lower limits 806, the upper limit is set as the number of cases.

Then, the fault information management device 20 multiplies the number of fault information items of each type by the standard charging point of each type indicated by the standard charging point 504 in the standard charging point management table 500, and calculates the multiplied value for each type of fault information.

Then, the fault information management device 20 refers to the charge calculation condition table 800 and multiplies each multiplication value of each type of fault information by the corresponding charge coefficient.

Specifically, the fault information management device 20 acquires a charging coefficient for each type of fault information based on the charging coefficient 807 in the charge calculation condition table 800 and the input content in s120. Then, the fault information management device 20 multiplies the multiplication value for each type by the acquired charging coefficient for each type. Then, the fault information management device 20 calculates charging points for each type of fault information by summing up the multiplication values for each type of fault information, and calculates the burden amount by multiplying the sum of these charging points by a predetermined reference amount.

On the other hand, in the case of s123, the fault information management device 20 calculates a reference value, which is a parameter corresponding to the number of pieces of fault information extracted as a result of the processing, for each type of processing and type of fault information (for example, the number of searches when the type of processing is specified keyword search, the number of pieces of fault information that were the subject of the aggregation when the type of processing is information aggregation and listing, the number of pieces of fault information that were the subject of the result information when the type of processing is specific case search, the number of pieces of fault information that were the subject of the result information when the type of processing is similar case search, and the target period that was the subject of the analysis when the type of processing is statistical information analysis). At this time, the fault information management device 20 refers to the upper and lower limits 806 of the charge calculation condition table 800, and checks whether each reference value exceeds the upper limit indicated by the upper and lower limits 806, and if it exceeds the upper limit indicated by the upper and lower limits 806, the upper limit is set as the reference value.

Then, the fault information management device 20 obtains each multiplication value by multiplying the reference value of each type of processing and fault information by the reference charging point 504 of the reference charging point management table 500 (or the coefficient 604 of the impact range rank management table 600) of each type (similar to s112).

Then, the fault information management device 20 refers to the charge calculation condition table 800 and further multiplies the calculated multiplication values for each type of processing and fault information by the charge coefficient and the response deadline parameter, respectively.

Specifically, the fault information management device 20 acquires the charging coefficient for each type of processing and fault information based on the charging coefficient 807 in the charge calculation condition table 800 and the input contents in s120. In addition, the fault information management device 20 acquires the response deadline parameter for each type of processing and fault information based on the response deadline parameter 808 in the charge calculation condition table 800 and the response deadline specified in s120.

Then, the fault information management device 20 multiplies the multiplication values related to each type of processing and fault information calculated above by the corresponding billing coefficient and response deadline parameter acquired above. Then, the fault information management device 20 calculates the charge amount by summing up all the multiplication values of each type of processing and fault information and multiplying the sum by a predetermined base amount.

When the result information is generated and the charge is calculated in the above manner, in s124, the problem information management device 20 displays the result information generated in s122 or s123, i.e., the inquiry list display screen 1300 that displays a list of the problem information for each registered item, on the problem information viewing terminal 30. In addition, the problem information management device 20 stores the list of the problem information for each registered item in the usage history DB 400.

The trouble information management device 20 also displays a feedback input screen 1700 on the screen of the trouble information viewing terminal 30, which accepts feedback input on the result information from the user side (s125). Then, the trouble information management device 20 calculates a discount amount for the burden calculated in s122 or s123 based on the input feedback (s126).

(Inquiry list display screen)
13 is a diagram showing an example of an inquiry list display screen 1300. The inquiry list display screen 1300 displays a list of system fault (fault information) names 1314, system fault (fault information) management numbers 1313, and fault occurrence dates 1312 of the system faults, and also includes a search result display field 1310 having a selection field 1311 for accepting selection of a system fault for which detailed information is to be displayed, and an inquiry confirmation field 1320 for displaying an individual system fault display screen 1400 for displaying detailed information of the system fault selected in the selection field 1311.

When the inquiry confirmation field 1320 is specified, the fault information management device 20 may add a predetermined amount (e.g., the equivalent of one standard charging point) to the charge to the user.

(System fault individual display screen)
14 is a diagram showing an example of a system failure individual display screen 1400 (the screen is divided into upper and lower parts due to space limitations). The system failure individual display screen 1400 is a screen that displays base information from among the result information.

The individual system failure display screen 1400 includes a base information display field 1410 that displays the base information of the system failure selected in the selection field 1311 of the inquiry list display screen 1300, an option information inquiry specification field 1430 that accepts the display of the individual system failure option display screen 1500 that displays option information of the system failure, a feedback specification field 1440 that displays the feedback input screen 1700 described below that accepts the input of feedback information for this system failure, and a back field 1420 for displaying the inquiry list display screen 1300 again.

When the option information inquiry specification field 1430 is specified, the fault information management device 20 may add a predetermined amount (e.g., the equivalent of one standard charging point) to the charge to the user.

(System fault individual option display screen)
15 is a diagram showing an example of a system failure individual option display screen 1500. The system failure individual option display screen 1500 is a screen for displaying option information. The system failure individual option display screen 1500 includes a base information display field 1510 for displaying option information of the system failure selected in the selection field 1311 of the inquiry list display screen 1300, a back field 1520 for displaying the inquiry list display screen 1300 again, a disclosure limited information inquiry designation field 1530 for accepting the display of a system failure individual limited disclosure display screen 1600 for displaying limited disclosure information of this system failure, and a feedback designation field 1540 for displaying a feedback input screen 1700 described later for accepting input of feedback information for this system failure. The system failure individual option display screen 1500 may be additionally displayed on the system failure individual display screen 1400.

When the disclosure restriction information inquiry specification field 1530 is specified, the fault information management device 20 may add a predetermined amount (e.g., the equivalent of one standard charging point) to the charge to the user.

(System failure individual limited disclosure display screen)
16 is a diagram showing an example of a system failure individual limited disclosure display screen 1600. The system failure individual limited disclosure display screen 1600 is a screen that displays limited disclosure information out of the result information.

The system failure individual limited disclosure display screen 1600 includes a limited disclosure information display field 1610 that displays limited disclosure information of a system failure selected in the selection field 1311 of the inquiry list display screen 1300, a back field 1620 for redisplaying the inquiry list display screen 1300, and a feedback designation field 1640 that displays a feedback input screen 1700 (described later) that accepts input of feedback information for this system failure. The system failure individual limited disclosure display screen 1600 may be additionally displayed on the system failure individual display screen 1400.

(Feedback input screen)
17 is a diagram showing an example of a feedback input screen 1700 (the screen is divided into upper and lower parts due to space limitations). The feedback input screen 1700 includes a base information feedback input field 1710 for receiving input of related base information regarding a system fault (trouble information) selected in the selection field 1311 of the inquiry list display screen 1300, an option information feedback input field 1730 for receiving input of related option information, a limited disclosure information feedback input field 1750 for receiving input of related limited disclosure information, a back field 1760 for returning to the previous screen, and a feedback information registration specification field 1770 for confirming the information input in the feedback input screen 1700 and calculating discount points.

When the feedback information registration specification field 1770 is specified, the fault information management device 20 calculates the discount amount based on the charge calculation condition table 800 .
Here, a specific example of a method for calculating the discount amount will be described.

First, the fault information management device 20 determines whether to apply the first discount points or the second discount points. For example, the fault information management device 20 may accept a selection from the administrator, or may determine based on the items of feedback information entered (for example, if a specific type or item of fault information is entered on the feedback input screen 1700, the first discount points are applied).

Then, the fault information management device 20 calculates the number of each piece of input feedback for each type of fault information. At this time, the fault information management device 20 refers to the upper and lower limits 806 in the charge calculation condition table 800, and checks whether each number exceeds the upper limit indicated by the upper and lower limits 806. If the number exceeds the upper limit indicated by the upper and lower limits 806, the upper limit is set as the number of pieces.

Then, the fault information management device 20 calculates a multiplication value for each type of feedback by multiplying the number of feedback items for each type of fault information by the standard charging point for each type indicated by the standard charging point 504 in the standard charging point management table 500.

Then, the fault information management device 20 refers to the charge calculation condition table 800 and multiplies each of the multiplication values of the feedback of each type of fault information by the corresponding charge coefficient.

Specifically, the fault information management device 20 acquires a charging coefficient for each type of fault information feedback based on the charging coefficient 807 in the charge calculation condition table 800 and the type of discount determined above (first discount, second discount). The fault information management device 20 then multiplies the multiplication value of the feedback of each type of fault information by the charging coefficient of the acquired feedback of each type of fault information. The fault information management device 20 then calculates charging points for each type of fault information feedback by summing up the multiplication values of the feedback of each type of fault information, and calculates the discount amount by multiplying the sum of these charging points by a predetermined reference amount.

Then, the fault information management device 20 calculates the charge to be requested from the user side by subtracting the discount amount calculated in s126 from the charge calculated in s122 or s123 (s127). Note that this process may be performed at a predetermined interval (e.g., once a month), or may be performed each time a search request or processing request is received, or may be performed at any other timing.

Then, the fault information management device 20 makes a payment for the calculated charge (s128). For example, the fault information management device 20 sets payment information including the calculated charge in the fault information viewing terminal 30 or a specified payment device (not shown) linked to the fault information viewing terminal 30. This allows the administrator to collect the cost.

As described above, the trouble information management device 20 of this embodiment calculates the value of the trouble information received from the trouble information providing terminal 10, generates compensation information corresponding to the calculated value, and on the other hand receives a request (search request or processing request) for information on system troubles related to financial institutions from the trouble information viewing terminal 30, generates information (result information) that satisfies the received request from the trouble information DB 300, and generates burden information corresponding to the value of the generated information (result information).

In this way, the fault information management device 20 of this embodiment generates compensation information for the provider (trouble information providing terminal 10) that provided the system fault information, while generating information on the burden of providing the information for the user (trouble information viewing terminal 30) that requested the provision of the system fault information. This promotes the collection of system fault information and allows for the appropriate use of that system fault information.

In addition, the fault information management device 20 of this embodiment calculates a first value for the event information and calculates a second value, which is greater than the first value, for the background information.

In this way, by placing a higher value on background information that may be useful for preventing system failures or for dealing with existing system failures than on event information, it is possible to collect a wider range of useful failure information.

In addition, the fault information management device 20 of this embodiment calculates a first value according to the impact range indicated by the information on the impact range of the system fault in the background information.

This allows for a higher value to be calculated for information about system failures that have a large impact, for example, making it possible to collect a wider range of useful failure information.

The fault information management device 20 of this embodiment also calculates the extent of impact indicated by the information on the extent of impact of the system failure based on event information, such as information on the system in which the system failure occurred, information on the time when the system failure occurred, and information on the number of personnel affected by the system failure, and calculates a value according to the calculated extent of impact.

In this way, by calculating the extent of the impact of a system failure based on event information, it is possible to accurately and objectively calculate the value according to the extent of the impact.

In addition, the fault information management device 20 of this embodiment calculates the value of information on events that occur due to system faults and information indicating the cause of the occurrence of the system fault, as event information.

This allows the value of fault information to be calculated with high accuracy.

The fault information management device 20 of this embodiment also calculates the value of at least one of the following background information: information identifying the process that caused the system fault, information about the program that caused the system fault, or information about the human factors that caused the system fault.

This allows the value of fault information to be calculated with high accuracy.

The trouble information management device 20 of this embodiment also receives from the trouble information viewing terminal 30 a search request including search conditions for the trouble information DB 300, or a processing request including a processing request for the trouble information DB 300, and when a search request is received, generates result information based on the search conditions, and when a processing request is received, accepts input of the processing content, processes the information in the trouble information DB 300 based on the input processing content, and generates result information based on the processed information.

In this way, by being able to both directly search for information in the fault information DB300 and to process information based on the information in the fault information DB300, convenience for users is increased and system fault information can be used more effectively.

The problem information management device 20 of this embodiment also accepts input of feedback information related to result information from the problem information viewing terminal 30, calculates the value of the input information, and generates burden information corresponding to a value obtained by subtracting the value of the feedback from the value of the result information.

In this way, by accepting feedback related to the fault information registered in the fault information DB 300 and reducing the burden on the user side accordingly, it is possible to promote the collection of more useful information on system faults.

In addition, the fault information management device 20 of this embodiment sets the payment information in the fault information providing terminal 10 or a payment device associated with the fault information providing terminal 10.

In this way, by providing compensation to the provider for the fault information they provide, it is possible to promote the collection of information on system faults.

In addition, the problem information management device 20 of this embodiment sets the burden information in the problem information viewing terminal 30 or a payment device associated with the problem information viewing terminal 30.

In this way, by charging or settling a fee from the user for providing fault information in response to their request, it is possible to ensure that system fault information is used appropriately.

The present invention is not limited to the above-described embodiment, and can be implemented using any components without departing from the spirit of the invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these contents as long as the characteristics of the invention are not impaired. In addition, although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical concept of the present invention are also included in the scope of the present invention.

For example, some of the hardware provided in each device of this embodiment may be provided in another device.

Furthermore, each program of each device may be provided in another device, a program may consist of multiple programs, or multiple programs may be integrated into a single program.

In addition, in this embodiment, the burden amount and discount amount are calculated when the result information is generated and when the feedback information is input, respectively, but these calculation timings are merely examples. The burden amount and discount amount may be calculated at different times depending on the timing of payment.

In addition, in this embodiment, the processing is performed by the fault information management device 20 receiving input of the processing content from the administrator, but the fault information management device 20 may automatically generate the processing content according to a predetermined algorithm and perform the processing based on the generated processing content.

In addition, in this embodiment, charges and discounts are granted or claimed in cash, but they may also be other types of value exchange media (for example, points to be used for specific purposes).

1 Trouble information management system, 10 Trouble information providing terminal, 20 Trouble information management device, 30 Trouble information viewing terminal

Claims (12)

a storage device that stores information on a system failure related to a financial institution received from the first information processing device; and
A compensation calculation process for calculating a value of the information on the system failure and generating compensation information corresponding to the calculated value;
a control device that executes a burden calculation process that receives a request for providing information on a system fault related to a financial institution from a second information processing device, generates information that satisfies the received request from the stored system fault information, and generates burden information corresponding to the value of the generated information. the storage device stores, as the information on the system fault, information for identifying the content of the system fault and information on the background of the occurrence of the system fault;
The control device, in the compensation calculation process, calculates a first value for information identifying the content of the system failure, and calculates a second value greater than the first value for information on the background of the occurrence of the system failure.
The fault information management device according to claim 1 . the storage device stores information on an extent of an impact of the system failure as information specifying the content of the system failure;
The control device calculates the first value according to the extent of influence indicated by the information on the extent of influence of the system failure in the compensation calculation process.
The fault information management device according to claim 2 . the storage device stores, as information for identifying the content of the system failure, information on the system in which the system failure occurred, information on the time when the system failure occurred, and information on the number of personnel affected by the system failure;
In the compensation calculation process, the control device calculates an impact range indicated by the information on the impact range of the system failure based on the stored system information, time information, and number of personnel information, and calculates the first value according to the calculated impact range.
The fault information management device according to claim 3. the storage device stores, as information specifying the content of the system failure, information on an event that has occurred due to the system failure and information indicating a cause of the occurrence of the system failure;
The control device calculates a first value for the stored information in the value calculation process.
The fault information management device according to claim 2 . the storage device stores, as background information of the occurrence of the system failure, at least any one of information identifying a process that caused the occurrence of the system failure, information on a program that caused the occurrence of the system failure, and information on a human factor that caused the occurrence of the system failure;
The control device calculates the second value for the stored information in the value calculation process.
The fault information management device according to claim 2 . The control device, in the burden calculation process,
receiving, as the request for providing, from the second information processing device, a first request including a search condition for the stored system fault information, or a second request including a request for processing the stored system fault information;
When the first request is received, generating information that satisfies the received request based on the search conditions;
when the second request is received, accepting an input of the content of the processing, processing the stored system fault information based on the input content of the processing, and generating information that satisfies the received request based on the processed information;
The fault information management device according to claim 1 . The control device, in the burden calculation process, receives an input of information related to the generated information from the second information processing device, calculates a value of the input information, and generates burden information corresponding to a value obtained by subtracting the calculated value from the value of the generated information.
The fault information management device according to claim 1 . The fault information management device according to claim 1, wherein the control device sets the generated compensation information in the compensation calculation process to the first information processing device or a device associated with the first information processing device. The fault information management device according to claim 1, wherein the control device sets the generated burden information in the burden calculation process to the second information processing device or a device associated with the second information processing device. An information processing device,
a storage device that stores information on a system failure related to a financial institution received from another first information processing device; and
A compensation calculation process for calculating a value of the information on the system failure and generating compensation information corresponding to the calculated value;
A fault information management method comprising: a control device that executes a burden calculation process that receives a request for providing information on a system fault related to a financial institution from another second information processing device, generates information that satisfies the received request from the stored system fault information, and generates burden information corresponding to the value of the generated information. A fault information management system including a first information processing device, a second information processing device, and a fault information management device,
The fault information management device includes:
a storage device that stores information on a system failure related to a financial institution received from the first information processing device; and
A compensation calculation process for calculating a value of the information on the system failure and generating compensation information corresponding to the calculated value;
a control device that executes a burden calculation process of receiving a request for providing information on a system fault related to a financial institution from the second information processing device, generating information satisfying the received request from the stored information on the system fault, and generating information on a burden corresponding to a value of the generated information;
In the compensation calculation process, information of the generated compensation is set in the first information processing device or a device associated with the first information processing device;
In the burden calculation process, information on the generated burden is set in the second information processing device or a device associated with the second information processing device.
Fault information management system.

Images