JP7661262B2 - ALERT AI MANAGEMENT DEVICE, ALERT AI MANAGEMENT METHOD, AND ALERT AI MANAGEMENT PROGRAM - Google Patents

Description

The present invention relates to an alert AI management device, an alert AI management method, and an alert AI management program.

Patent document 1 discloses a configuration for managing the environment in which a control function realized by AI (Artificial Intelligence) operates.

JP 2021-193511 A

However, the invention described in Patent Document 1 above has an issue in that unauthorized changes to the alert AI definition, either intentionally or accidentally, can prevent unauthorized operations that should be detected from being detected, resulting in a malfunction of the control system.

The present invention has been made in consideration of the above problems, and aims to provide an alert AI management device, an alert AI management method, and an alert AI management program that can create definition groups by grouping audit scenarios based on the nature of the audit content of the alert AI, and assign roles to each group, thereby appropriately allocating authority to each role and controlling security.

In order to solve the above-mentioned problems and achieve the object, the alert AI management device according to the present invention is an alert AI management device having a storage unit and a control unit, the storage unit storing a user group member master set by linking users and user groups, an alert AI definition group compiled according to an audit scenario based on the nature of the monitoring content of the alert AI that judges abnormal values during business execution, the role type of the user group or the user, and a user alert definition group relation storage means for storing a user alert definition group relation table set by linking the user group, and The system is characterized in that it includes an alert AI definition group master in which an alert AI definition for an alert AI is set, and an abnormal value judgment definition storage means for storing an abnormal value judgment definition table in which the definition contents of each alert AI definition are set, and the control unit includes a user acquisition means for acquiring user data of a target user for which authority is specified, and an authority specification means for specifying the role type of the target user and the alert AI definition for which the user has modification authority and/or viewing authority based on the user data, the user group member master, the user alert definition group relation table, the alert AI definition group master, and the abnormal value judgment definition table.

In the alert AI management device according to the present invention, the role types include an alert AI administrator who manages the audit scenario, an alert AI operation checker who is responsible for checking whether any fraud has been committed in creating and changing the definition of the alert AI, and/or whether the operation personnel who perform the audit check to see whether any abnormalities are found in the actual use of the alert AI and/or the alert AI definition assigned by the alert AI administrator are correctly performing the audit check, and the operation personnel who perform the audit check to see whether any abnormalities are found in the actual use of the alert AI and/or the alert AI definition assigned by the alert AI administrator.

In addition, in the alert AI management device according to the present invention, the authority identification means identifies the role type of the target user based on the linkage between the user data, the user group member master, and the user alert definition group relation table, and identifies the alert AI definition for which the change authority and/or the viewing authority is available based on the linkage between the user alert definition group relation table, the alert AI definition group master, and the abnormal value judgment definition table.

In the alert AI management device according to the present invention, the storage unit further includes an alert AI management storage means that stores a control table that sets the change authority and the viewing authority for the alert AI definitions constituting each of the alert AI definition groups for each role type, the viewing authority for the change history of the alert AI definition, the viewing authority for the alert AI list inquiry based on the alert AI definition, the viewing authority for the alert AI detail inquiry based on the alert AI definition, and the viewing authority for the alert AI execution history and log based on the alert AI definition, and the control unit further includes a system control means that controls, based on the control table, the target user's changes and/or viewing of the alert AI definition identified by the authority identification means, viewing of the change history of the alert AI definition, viewing of the alert AI list inquiry, viewing of the alert AI detail inquiry, and/or viewing of the alert AI execution history and log.

In the alert AI management device according to the present invention, the storage unit further includes a user alert definition relation storage means for storing the alert AI definition and a user alert definition relation table that is set by linking the user or the user group who is the operation staff, and the authority identification means further identifies the alert AI definition for which the target user who is the operation staff has the change authority and/or the viewing authority based on the user data, the user group member master, the user alert definition relation table, and the abnormal value judgment definition table.

In the alert AI management device according to the present invention, the alert AI definition group includes a fictitious order alert definition group, a sales recording alert definition group, a fictitious transaction alert definition group, and/or an expense fraud alert definition group.

The alert AI management method according to the present invention is an alert AI management method to be executed by an alert AI management device having a storage unit and a control unit, the storage unit including a user group member master set by linking users and user groups, an alert AI definition group compiled according to an audit scenario based on the nature of the monitoring content of an alert AI that judges abnormal values during business execution, the role type of the user group or the user, and a user alert definition group relation storage means for storing a user alert definition group relation table set by linking the user group, and the alert AI definition group that constitutes the alert AI definition group. The system includes an alert AI definition group master in which an AI alert AI definition is set, and an abnormal value judgment definition storage means for storing an abnormal value judgment definition table in which the definition contents of each of the alert AI definitions are set, and includes a user acquisition step executed by the control unit to acquire user data of a target user for which authority is specified, and an authority specification step to specify the role type of the target user and the alert AI definition for which the user has modification authority and/or viewing authority based on the user data, the user group member master, the user alert definition group relation table, the alert AI definition group master, and the abnormal value judgment definition table.

The alert AI management program according to the present invention is an alert AI management program to be executed by an alert AI management device having a storage unit and a control unit, the storage unit storing a user group member master set by linking users and user groups, an alert AI definition group compiled according to an audit scenario based on the nature of the monitoring content of an alert AI that judges abnormal values during business execution, the role type of the user group or the user, and a user alert definition group relation storage means for storing a user alert definition group relation table set by linking the user group, and the alert AI definition group that constitutes the alert AI definition group. The system includes an alert AI definition group master in which an alert AI definition for an alert AI is set, and an abnormal value judgment definition storage means for storing an abnormal value judgment definition table in which the definition contents of each alert AI definition are set, and the control unit executes a user acquisition step for acquiring user data of a target user for which authority is specified, and an authority specification step for specifying the role type of the target user and the alert AI definition for which the user has modification authority and/or viewing authority based on the user data, the user group member master, the user alert definition group relation table, the alert AI definition group master, and the abnormal value judgment definition table.

According to the present invention, it is possible to provide an effect that only appropriate users can use the system for each definition based on the contents of the audit scenario. In addition, according to the present invention, it is possible to prevent unauthorized changes by monitoring changes to the alert AI definition and the execution history of the judgment. In addition, according to the present invention, it is possible to flexibly set the person in charge who uses the alert AI. In addition, according to the present invention, it is possible to specify the authority that each user can operate, mainly by defining the role by the relationship setting. In addition, according to the present invention, it is possible to provide roles and mechanisms in terms of security in order to operate to detect fraud and abnormalities within the company. In addition, according to the present invention, it is possible to provide an effect that multiple judgment definitions can be managed in one database, and judgment processing according to the characteristics of each business can be set by setting. In addition, according to the present invention, it is possible to provide an effect that the judgment result of each judgment definition and a screen for analyzing the accompanying business data can be provided. In addition, in this embodiment, it is possible to group the definitions of abnormal value judgment and set roles for each group. Additionally, this embodiment has the advantage that audit scenarios based on the nature of the audit content of the alert AI can be grouped together, and the authority to change the definition or view the results can be specified for each group.

FIG. 1 is a block diagram showing an example of the configuration of an alert AI management device according to the present embodiment. FIG. 2 is a diagram showing an example of the user master 106a in this embodiment. FIG. 3 is a diagram showing an example of the user group master 106b in this embodiment. FIG. 4 is a diagram showing an example of the user group member master 106c in this embodiment. FIG. 5 is a diagram showing an example of the alert AI definition group master 106d in this embodiment. FIG. 6 is a diagram showing an example of the alert AI definition group member master 106e in this embodiment. FIG. 7 is a diagram showing an example of management data in this embodiment. FIG. 8 is a diagram showing an example of management data in this embodiment. FIG. 9 is a diagram showing an example of management data in this embodiment. FIG. 10 is a diagram showing an example of management data in this embodiment. FIG. 11 is a diagram showing an example of management data in this embodiment. FIG. 12 is a diagram showing an example of management data in this embodiment. FIG. 13 is a flowchart showing an example of processing of the alert AI management device in this embodiment. FIG. 14 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 15 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 16 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 17 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 18 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 19 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 20 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 21 is a diagram showing an example of an authority specifying method in this embodiment. FIG. 22 is a diagram showing an example of an application environment in this embodiment. FIG. 23 is a diagram showing an example of an application environment in this embodiment. FIG. 24 is an explanatory diagram showing an example of the significance of setting an alert AI operation checker in this embodiment. FIG. 25 is a diagram showing an example of role setting in this embodiment. FIG. 26 is a diagram showing an example of a screen configuration and a business flow that can prevent unauthorized changes in this embodiment. FIG. 27 is a diagram showing an example of a screen configuration and a business flow that can prevent unauthorized changes in this embodiment. FIG. 28 is a diagram showing an example of a screen configuration and a business flow that can prevent unauthorized changes in this embodiment. FIG. 29 is a diagram showing an example of a screen configuration and a business flow that can prevent unauthorized changes in this embodiment. FIG. 30 is a diagram showing an example of an alert definition creation screen in this embodiment. FIG. 31 is a diagram showing an example of an alert AI definition change history screen in this embodiment. FIG. 32 is a diagram showing an example of an alert AI inquiry screen in this embodiment. FIG. 33 is a diagram showing an example of an alert AI inquiry screen in this embodiment. FIG. 34 is a diagram showing an example of an alert AI execution history/log viewer in this embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
First, an overview of the present invention will be described.

In the past, when there was a high possibility of handling highly confidential data, such as detecting business fraud such as inflated sales or manipulation of inventory values, it was not possible to restrict the users who could change and view the settings of the alert AI definition to only the minimum necessary content for each user, so it was desirable to restrict the users who could change and view the settings of the alert AI definition, even within the same company. In other words, in the past, there was a high possibility that highly confidential data would be handled when making judgments or viewing results with alert AI, but there was no mechanism to control the minimum necessary authority for each user according to the content of the audit scenario. In addition, in the past, only system administrators who were not business personnel could set authority, so it was not possible to flexibly change the person in charge of using the alert AI. In addition, in the past, the alert AI definition could be changed by setting, so there was a risk that unauthorized changes to the alert AI definition due to intentional or negligence would not detect business fraud that should be detected and the control would not function, but there was no mechanism to control the changes. In addition, in the past, there was a possibility that users would view data that should not be viewed due to the nature of the data, and appropriate security control was lacking.

In this embodiment, therefore, it is possible to create definition groups that group audit scenarios based on the nature of the audit content of the alert AI, and to each group, three roles can be assigned: an alert AI manager, an alert AI operation checker, and an operation manager. Each role is appropriately assigned the authority to change and view definitions, view judgment results, view history, etc., providing a mechanism for controlling security.

In this embodiment, the alert AI definitions can be grouped and roles can be set for each group, and can be set in a unit for each task. Three roles are provided and authority is divided for each role, so that each person can perform the necessary processing while preventing fraud. In addition, in this embodiment, unauthorized changes are prevented by monitoring changes to the alert AI definition and the execution history of judgments, and the alert AI operation checker is given the authority to monitor the implementation of settings added and changed by the alert AI management person, and it is possible to check whether unauthorized changes have been made. In addition, in this embodiment, even if you are not a system administrator user, you can create alert AI definitions and change the authority settings of the operation person, and the authority to grant viewing authority can be delegated from the system administration user to the alert AI management person by giving them the authority to set the operation person.

Here, the system administrator has the authority to perform the appointment management of alert AI administrators and alert AI operation checkers according to the business content, to create definition groups that are managed by user groups and compile audit scenarios based on the nature of the audit content of the alert AI, to create user groups that compile users, to assign users to user groups, to assign user groups that will be alert AI administrators to definition groups, and to assign user groups that will be alert AI operation checkers to definition groups. In this embodiment, an alert AI administrator and an alert AI operation checker may be selected for each audit scenario based on the nature of the audit content of the alert AI, and the necessary authority may be delegated.

In addition, the alert AI administrator has the authority to manage audit scenarios based on the nature of the audit content of the transferred alert AI, to create, modify, delete, and view alert AI definitions in the definition group that is managed by the user group and assigned by the system administrator, to view the change history of the alert AI definitions in the definition group assigned by the system administrator, to assign operational users to the alert AI definitions in the definition group assigned by the system administrator, and to view the results of abnormal value judgments performed from the alert AI definitions in the definition group assigned by the system administrator.

In addition, the alert AI operation checker is responsible for checking whether any irregularities have been committed when creating or changing alert AI definitions, whether the operations staff is operating the audit check correctly, etc., and has the authority to view the change history of alert AI definitions within the definition group managed by user groups and assigned by the system administrator, to view the execution history and logs of abnormal value judgments performed from alert AI definitions within the definition group assigned by the system administrator, and to view the judgment results of abnormal value judgments performed from alert AI definitions within the definition group assigned by the system administrator.

In addition, the operations staff is the person in charge of performing audit checks to see whether any abnormalities are found in the alert AI definitions assigned by the alert AI administrator who actually uses the alert AI, and is managed by user groups or users. The operations staff has the authority to view the alert AI definitions assigned by the alert AI administrator (depending on the assignment of authority), to view the results of abnormal value judgments performed from the alert AI definitions assigned by the alert AI administrator, and to output the results of abnormal value judgments performed from the alert AI definitions assigned by the alert AI administrator.

2. Configuration
An example of the configuration of an alert AI management device 100 according to this embodiment will be described with reference to Fig. 1 to Fig. 12. Fig. 1 is a block diagram showing an example of the configuration of the alert AI management device 100 according to this embodiment.

As shown in FIG. 1, the alert AI management device 100 is a commercially available desktop personal computer. Note that the alert AI management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The alert AI management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the alert AI management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the alert AI management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the alert AI management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work with the OS (Operating System) to give commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes a user master 106a, a user group master 106b, a user group member master 106c, an alert AI definition group master 106d, an alert AI definition group member master 106e, and an alert AI management database 106f.

The user master 106a is a master that sets users. Here, the user master 106a may be set in association with a user ID (identification) and a user name.

Here, an example of the user master 106a in this embodiment will be described with reference to FIG. 2. FIG. 2 is a diagram showing an example of the user master 106a in this embodiment.

As shown in FIG. 2, the user master 106a in this embodiment is set in association with a user ID and a user name, and may be configurable only by the system administrator.

Returning to FIG. 1, the user group master 106b is a master that sets user groups. Here, the user group master 106b may be set in association with a user group ID and a user group name.

Here, an example of the user group master 106b in this embodiment will be described with reference to FIG. 3. FIG. 3 is a diagram showing an example of the user group master 106b in this embodiment.

As shown in FIG. 3, the user group master 106b in this embodiment is set by linking the user group ID and the user group name, and may be configurable only by the system administrator.

Returning to FIG. 1, the user group member master 106c is a master that links and sets users and user groups. Here, the user group member master 106c may be set to link user IDs and user group IDs.

Here, an example of the user group member master 106c in this embodiment will be described with reference to FIG. 4. FIG. 4 is a diagram showing an example of the user group member master 106c in this embodiment.

As shown in FIG. 4, the user group member master 106c in this embodiment is set in association with the user group ID and the user ID, and may be configurable only by the system administrator.

Returning to FIG. 1, the alert AI definition group master 106d is a master that sets the alert AI definition of the alert AI that constitutes the alert AI definition group. Here, the alert AI definition group may include a fictitious order alert definition group, a sales recording alert definition group, a fictitious transaction alert definition group, and/or an expense fraud alert definition group. In addition, the alert AI definition group master 106d may be set in association with a definition group ID and an alert AI definition group name. Here, the fictitious order alert definition group may include a fictitious order alert definition, a fictitious business partner sales alert definition, and an accounts payable alert definition. In addition, the sales recording alert definition group may include a sales cancellation alert definition, a sales correction alert definition, and a sales discount alert definition. In addition, the fictitious transaction alert definition group may include an expense item fraudulent use alert definition and an excessive billing alert definition. In addition, the expense fraud alert definition group may include an excessive expense alert and a fictitious business partner expense alert.

Here, an example of the alert AI definition group master 106d in this embodiment will be described with reference to FIG. 5. FIG. 5 is a diagram showing an example of the alert AI definition group master 106d in this embodiment.

As shown in FIG. 5, the alert AI definition group master 106d in this embodiment is set by linking the definition group ID and the alert AI definition group name, and may be configurable only by the system administrator.

Returning to FIG. 1, the alert AI definition group member master 106e is a master that links and sets the alert AI definition group and the alert AI definition. Here, the alert AI definition group member master 106e may be set to link and set the definition group ID and the definition ID.

Here, an example of the alert AI definition group member master 106e in this embodiment will be described with reference to FIG. 6. FIG. 6 is a diagram showing an example of the alert AI definition group member master 106e in this embodiment.

As shown in FIG. 6, the alert AI definition group member master 106e in this embodiment is set in association with the definition group ID and the definition ID, and only the definitions assigned to the definition group to which the alert AI administrator is assigned may be set.

Returning to FIG. 1, the alert AI management database 106f stores management data of the alert AI. Here, the alert AI management database 106f may store (as management data) a control table that sets the change authority and viewing authority for the alert AI definition constituting each alert AI definition group for each role type, the viewing authority for the change history of the alert AI definition, the viewing authority for the alert AI list inquiry based on the alert AI definition, the viewing authority for the alert AI detail inquiry based on the alert AI definition, and the viewing authority for the alert AI execution history and log based on the alert AI definition. In addition, the alert AI management database 106f may store (as management data) an alert AI definition group summarized according to an audit scenario based on the nature of the monitoring content of the alert AI that determines an abnormal value during business execution, a user group or user role type, and a user alert definition group relation table that is set by linking the user group. Here, the role types may include an alert AI administrator who manages the audit scenario, and an alert AI operation checker who is responsible for checking whether any fraud has been committed in creating and changing the definition of the alert AI, and/or whether the operation staff who performs the audit check to check whether anomalies are found in the actual use of the alert AI and/or the alert AI definition assigned by the alert AI administrator is performing the audit check correctly. The alert AI management database 106f may also store (as management data) an abnormal value determination definition table in which the definition contents of each alert AI definition are set. The alert AI management database 106f may also store (as management data) an alert AI definition and a user alert definition relation table that is set by linking the user or user group who is the operation staff.

Now, an example of management data in this embodiment will be described with reference to Figures 7 to 12. Figures 7 to 12 are diagrams showing an example of management data in this embodiment.

As shown in FIG. 7, the management data in this embodiment includes a user alert definition group relation table in which the definition group ID, role type, and user group ID are linked and set, and may be set only by the system administrator. Also, as shown in FIG. 7, the management data in this embodiment includes a user alert definition relation table in which the definition ID, setting type, user group ID, user ID, output authority flag, and definition reference flag are linked and set, and only the definition assigned to the definition group assigned as the alert AI administrator can be set, and a user or user group who will be the operator may be assigned to each definition. Also, as shown in FIG. 7, the management data in this embodiment includes a control table in which the change authority and viewing authority of the alert AI definition, the viewing authority of the alert AI definition change history, the viewing authority of the alert AI inquiry (list), the viewing authority of the alert AI inquiry (details), and the viewing authority of the alert AI execution history and log are set for each role type, and may be used to control other tables included in the management data. Here, the control table is linked to a role for each alert AI definition group, and all data outside the linked alert AI definition group may not be viewable. In this embodiment, the control table shown in FIG. 7 may be displayed as the definition screen.

In this embodiment, the scope of authority for the table related to the definition of the alert AI administrator is that new additions can only be made within the definition group assigned to the alert AI administrator, that only definitions belonging to the definition group assigned to the alert AI administrator can be modified and deleted, and that only definitions belonging to the definition group assigned to the alert AI administrator can be viewed. In this embodiment, the scope of authority for the table related to the definition of the alert AI operation checker is that only definitions belonging to the definition group assigned to the alert AI operation checker can be viewed. In this embodiment, the scope of authority for the table related to the definition of the operation person is that only definitions assigned as the operation person and with the "definition reference flag = TRUE" can be viewed. Here, as shown in FIG. 8, the abnormal value determination definition table, which is a table related to the definition in this embodiment, may be set by linking the definition ID, definition name, algorithm code, definition, result table name, and data acquisition definition ID. As shown in FIG. 8, the extraction condition table, which is a table related to the definition in this embodiment, may have a definition ID, a position number, a conjunction, a parenthesis, an extraction column name, an operator, a threshold, a data type, a comparison column name, and a rear parenthesis. As shown in FIG. 8, the change point definition table, which is a table related to the definition in this embodiment, may have a definition ID, a time series name, a key item, a target column name, a comparison target, a change degree calculation type, a number, a change point detection type, an upper limit, and a lower limit. As shown in FIG. 8, the anomaly rank definition table, which is a table related to the definition in this embodiment, may have a definition ID and an anomaly rank number associated with each other. As shown in FIG. 8, the data acquisition definition table, which is a table related to the definition in this embodiment, may have a data acquisition definition ID, a data acquisition definition name, and a stored procedure name associated with each other.

In this embodiment, the scope of authority for the history table of the table related to the definition of the alert AI administrator is that only the definitions belonging to the definition group assigned to the alert AI administrator can be viewed. In this embodiment, the scope of authority for the history table of the table related to the definition of the alert AI operation checker is that only the definitions belonging to the definition group assigned to the alert AI operation checker can be viewed. In this embodiment, the scope of authority for the history table of the table related to the definition of the operation person does not have viewing authority. In this embodiment, the history table is updated whenever there is a change in the original table, and the generation number is counted up each time there is a change for each definition ID. Here, as shown in FIG. 9, the abnormal value determination definition generation management table, which is the history table of the table related to the definition in this embodiment, may be set in association with the generation number, definition ID, update content, and update date. Also, as shown in FIG. 9, the abnormal value determination definition history table, which is a history table of tables related to definitions in this embodiment, may be set in association with the generation number, definition ID, definition name, algorithm code, definition, result table name, data acquisition definition ID, update contents, and update date.

Also, as shown in FIG. 10, the extraction condition history table, which is a history table of the table related to the definition in this embodiment, may be set with a generation number, definition ID, position NO, conjunction, parentheses, extraction column name, operator, threshold, data type, comparison column name, parentheses, update contents, and update date linked together. Also, as shown in FIG. 10, the change point definition history table, which is a history table of the table related to the definition in this embodiment, may be set with a generation number, definition ID, time series name, key item, target column name, comparison target, change degree calculation type, number, change point detection type, update contents, and update date linked together. Also, as shown in FIG. 10, the anomaly rank definition history table, which is a history table of the table related to the definition in this embodiment, may be set with a generation number, definition ID, anomaly rank number, update contents, and update date linked together. Also, as shown in FIG. 10, the data acquisition definition history table, which is a history table for tables related to definitions in this embodiment, may be set in association with the data acquisition definition ID, data acquisition definition name, stored procedure name, update content, and update date.

In this embodiment, the scope of authority of the alert AI administrator to the table related to the judgment result is that only data linked to the definition belonging to the definition group assigned to the alert AI administrator can be viewed. In this embodiment, the scope of authority of the alert AI operation checker to the table related to the judgment result is that only data linked to the definition belonging to the definition group assigned to the alert AI operation checker can be viewed. In this embodiment, the scope of authority of the operation staff to the table related to the judgment result is that only data linked to the definition assigned to the operation staff can be viewed. Here, as shown in FIG. 11, the judgment result table, which is a table related to the judgment result in this embodiment, may be set with an index, definition ID, execution Guid, judgment result, staff CD (code), customer CD, accounting year and month, and sales cancellation amount linked together. In addition, as shown in FIG. 11, the result message table, which is a table related to the judgment result in this embodiment, may be set with an index, execution Guid, index, layout element CD, and message linked together.

In this embodiment, the scope of authority for the table used by the alert AI administrator to refer to the execution history and log is that only data linked to the definitions belonging to the definition group assigned to the alert AI administrator can be viewed. In this embodiment, the scope of authority for the table used by the alert AI operation checker to refer to the execution history and log is that only data linked to the definitions belonging to the definition group assigned to the alert AI operation checker can be viewed. In this embodiment, the scope of authority for the table used by the operation staff to refer to the execution history and log is that they do not have viewing authority. Here, as shown in FIG. 12, the judgment log table, which is a table used to refer to the execution history and log in this embodiment, may be set in association with a serial number, definition ID, execution Guid, message, and update time. In addition, as shown in FIG. 12, the judgment history table, which is a table used to refer to the execution history and log in this embodiment, may be set in association with a serial number, definition ID, execution Guid, state, and update time.

Returning to FIG. 1, the control unit 102 is a CPU or the like that provides overall control of the alert AI management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. In terms of functional concept, the control unit 102 includes a user acquisition unit 102a, an authority identification unit 102b, and a system control unit 102c.

The user acquisition unit 102a acquires user data of the target user for which authority is to be identified.

The authority identification unit 102b identifies the role type of the target user and the alert AI definition for which the target user has change authority and/or viewing authority. Here, the authority identification unit 102b may identify the role type of the target user and the alert AI definition for which the target user has change authority and/or viewing authority based on the user data, the user group member master 106c, the user alert definition group relation table, the alert AI definition group master 106d, and the abnormal value judgment definition table. The authority identification unit 102b may also identify the role type of the target user based on the linkage between the user data, the user group member master 106c, and the user alert definition group relation table, and may identify the alert AI definition for which the target user has change authority and/or viewing authority based on the linkage between the user alert definition group relation table, the alert AI definition group master 106d, and the abnormal value judgment definition table. The authority identification unit 102b may also identify the change history of the alert AI definition of the alert AI for which the target user has viewing authority, the alert AI list inquiry, the alert AI detail inquiry, and/or the alert AI execution history/log. The authority identification unit 102b may also identify an alert AI definition for which the target user, who is an operation staff member, has modification authority and/or viewing authority based on the user data, the user group member master 106c, the user alert definition relation table, and the abnormal value judgment definition table. The authority identification unit 102b may also identify the role type of the target user and the alert AI definition for which the target user has modification authority and/or viewing authority based on the linkage of the user data, the user master 106a, the user group master 106b, the user group member master 106c, the user alert definition group relation table, the alert AI definition group master 106d, the alert AI definition group member master 106e, and/or the abnormal value judgment definition table.

Based on the control table, the system control unit 102c controls the target user's ability to change and/or view the alert AI definition identified by the authority identification unit 102b, view the change history of the alert AI definition, view the alert AI list inquiry, view the alert AI detail inquiry, and/or view the alert AI execution history and log.

3. Specific Examples
A specific example of this embodiment will be described with reference to FIGS.

[Alert AI Management Processing]
An example of an alert AI management process in this embodiment will now be described with reference to Fig. 13. Fig. 13 is a flowchart showing an example of a process of the alert AI management device 100 in this embodiment.

As shown in FIG. 13, when a login is performed by a target user with specific authority, the user acquisition unit 102a acquires user data in which the target user's user name and/or user ID is set (step SA-1).

Then, the authority identification unit 102b identifies the role type of the target user based on the linkages between the user data, the user master 106a, the user group master 106b, and the user alert definition group relation table, and determines whether the target user is an alert AI administrator or an alert AI operation checker (step SA-2).

If the authority identification unit 102b determines that the target user is not an alert AI administrator or an alert AI operation checker (step SA-2: No), it transitions the process to step SA-3.

Then, the authority identification unit 102b determines whether the target user is an operations officer based on the linkages between the user data, the user master 106a, the user group master 106b, and the user alert definition relationship table (step SA-3).

If the authority identification unit 102b determines that the target user is not an operations manager (step SA-3: No), it transitions the process to step SA-6.

On the other hand, if the authority identification unit 102b determines that the target user is an operations manager (step SA-3: Yes), it transitions the process to step SA-4.

Then, the authority identification unit 102b identifies the alert AI definition that the target user, who is the operations officer, has viewing authority for, based on the linkages between the user data, the user master 106a, the user group member master 106c, the user alert definition relation table, and the abnormal value determination definition table (step SA-4), and moves the process to step SA-6.

On the other hand, if the authority identification unit 102b determines that the target user is an alert AI administrator or an alert AI operation checker (step SA-2: Yes), it transitions the process to step SA-5.

Then, the authority identification unit 102b identifies the alert AI definition for which the target user has modification authority and/or viewing authority based on the linkages between the user data, user master 106a, user group master 106b, user group member master 106c, user alert definition group relation table, alert AI definition group master 106d, alert AI definition group member master 106e, and the abnormal value determination definition table (step SA-5), and proceeds to step SA-6.

Then, based on the control table stored in the alert AI management database 106f, the system control unit 102c controls the target user's ability to change and/or view the alert AI definition identified by the authority identification unit 102b, view the change history of the alert AI definition, view the alert AI list inquiry based on the alert AI definition, view the alert AI detail inquiry based on the alert AI definition, and/or view the alert AI execution history and log based on the alert AI definition (step SA-6), and then ends the process.

Here, an example of an authority identification method in this embodiment will be described with reference to Figs. 14 to 21. Figs. 14 to 21 are diagrams showing an example of an authority identification method in this embodiment.

In this embodiment, it is possible to specify what authority each user has for which definition. As shown in FIG. 14, when the logged-in user is "User ID: U01, User name: Yamashita Shigeru", the role type of the user is specified as alert AI administrator, and it is possible to specify that the user has alert AI administrator authority for two definitions (linked to the alert AI administrator user), and each screen is controlled according to system control.

Also, as shown in FIG. 15, in this embodiment, if the logged-in user is "User ID: U06, User name: Shibatsuji Kotomi", the role type of the user is identified as an alert AI operation checker, and it can be identified that the user has alert AI operation checker authority for five definitions (linked to the alert AI operation checker), and each screen is controlled according to system control.

Also, as shown in FIG. 16, in this embodiment, if the logged-in user is an operations person with "User ID: U02, User name: Kinoshita Yuji", it can be determined that the user has operations person authority for one definition (linked to the operations person), and each screen is controlled according to system control.

Also, as shown in FIG. 17, in this embodiment, if the logged-in user is an operations person with "User ID: U07, User name: Yamazato Hiromichi", it can be determined that the user has operations person authority for one definition (linked to the operations person), and each screen is controlled according to system control.

Also, as shown in FIG. 18, in this embodiment, in the case of "Definition ID: T001, Definition Name: Sales Correction Alert Definition", the alert AI definition and the results are linked based on "Definition ID: T01" and "Execution Guid: 00000000-0000-0000-0000-000000000000".

Also, as shown in FIG. 19, in this embodiment, in the case of "Definition ID: T001, Definition Name: Sales Correction Alert Definition", the alert AI definition is linked to each setting or history based on the "Data Acquisition Definition ID".

Also, as shown in Figures 20 and 21, in this embodiment, a "definition ID" is set in all setting tables and history tables, making it possible to identify authority.

Furthermore, an example of an application environment in this embodiment will be described with reference to Figs. 22 and 23. Figs. 22 and 23 are diagrams showing an example of an application environment in this embodiment.

As shown in FIG. 22, the alert AI management in this embodiment is applicable to a structure in which a system administrator appoints and manages an alert AI manager and an alert AI operation checker for each of multiple alert AI definition groups within company 100. In addition, since the alert AI operation checker should be a person who can exercise control, as shown in FIG. 23, the alert AI management in this embodiment is applicable to a structure in which a system administrator appoints an alert AI operation checker within parent company 100 and appoints and manages alert AI managers for each of multiple alert AI definition groups within subsidiary companies 200 and 300.

Furthermore, the significance of setting the person in charge of checking the alert AI operation in this embodiment will be explained with reference to FIG. 24. FIG. 24 is an explanatory diagram showing an example of the significance of setting the person in charge of checking the alert AI operation in this embodiment.

As shown in FIG. 24, in this embodiment, by providing an alert AI operation checker, it is possible to prevent unauthorized changes to the alert AI by the alert AI administrator and the deletion of schedule definitions, which can result in content that should be detected going undetected. In other words, in this embodiment, by providing an alert AI operation checker, unauthorized changes can be prevented, and in the unlikely event that an unauthorized change is made, it can be detected.

Also, with reference to FIG. 25, an example of a permission setting structure in this embodiment that allows even non-system administrators to change detailed viewing permissions will be described. FIG. 25 is a diagram showing an example of role settings in this embodiment.

In this embodiment, the system administrator delegates the authority to set the operator to the alert AI administrator based on the role setting shown in FIG. 25. In addition, in this embodiment, the operator can be set for each alert AI definition. That is, in this embodiment, the person in charge of managing the entire alert AI definition group is limited, while the person who actually uses the alert AI screen often differs for each scenario and definition. Therefore, even within the alert AI definition group, the alert AI definition and the user are linked, making it possible to set the user's authority in detail and appropriately. In addition, in this embodiment, not only linking with a user group but also linking with a user is possible. Here, when setting an operator for each alert AI definition, if only a user group can be set and a new operator is to be added, it is necessary to request the system administrator to add it, but the rights cannot be divided. Therefore, in this embodiment, the alert AI administrator has the full range of authority for the operator, making it possible to set it for a single user.

In addition, in this embodiment, the authority can be divided into fine divisions for each operator. That is, in this embodiment, the definition viewing authority for whether or not the definition of what definition the abnormal value judgment is performed under can be viewed can be divided for each operator. In this embodiment, if the operator can understand the judgment conditions for abnormality detection, it is possible to control the input of business data to avoid fraud detection, so this authority is given only to the minimum number of users. In addition, in this embodiment, the result viewing authority for whether or not the analysis screen of the abnormal value judgment result can be viewed can be divided for each operator. In this embodiment, all users assigned to the operator have this authority, and when there is data judged to be abnormal, detailed data on the analysis screen can be viewed. In addition, in this embodiment, the output authority for whether or not the result can be output from the analysis screen of the abnormal value judgment result can be divided for each operator. In this embodiment, the data after output can be processed and shared, so this authority is given only to the minimum number of users.

Furthermore, with reference to Figs. 26 to 29, an example of a screen configuration and a business flow that can prevent unauthorized changes in this embodiment will be described. Figs. 26 to 29 are diagrams showing an example of a screen configuration and a business flow that can prevent unauthorized changes in this embodiment.

In this embodiment, unauthorized changes are prevented by monitoring changes to alert AI definitions and users. That is, as shown in FIG. 26 to FIG. 29, in this embodiment, since the alert AI administrator has the authority to change definitions, for example, it is assumed that an alert AI definition is deleted to conceal unauthorized changes so that abnormal value judgment is not performed, or that judgment rules are tampered with to conceal unauthorized changes, and by making it possible for the person in charge of checking the alert AI operation to know that each alert AI definition has been changed, its contents, or that it has been executed, unauthorized detection is monitored.

Furthermore, an example of a system control screen in this embodiment will be described with reference to Figs. 30 to 34. Fig. 30 is a diagram showing an example of an alert definition creation screen in this embodiment. Fig. 31 is a diagram showing an example of an alert AI definition change history screen in this embodiment. Fig. 32 is a diagram showing an example of an alert AI inquiry screen in this embodiment. Fig. 33 is a diagram showing an example of an alert AI inquiry screen in this embodiment. Fig. 34 is a diagram showing an example of an alert AI execution history/log viewer in this embodiment.

As shown in FIG. 30, the alert definition creation screen in this embodiment is a system screen that allows the definition of an alert to be created, modified, deleted, and viewed, and the alert AI definition group member master 106e, the abnormal value judgment definition table, the extraction condition table, the change point definition table, the abnormality rank definition table, and the data acquisition definition table are set and viewed. Here, as shown in FIG. 30, in the alert definition creation screen in this embodiment, the definition group assigned as the alert AI administrator is displayed in a list, the definition group assigned as the alert AI operation checker is displayed in a list, the definition assigned as the operation person and with the "definition reference flag = TRUE" is displayed in a list, and the new creation button is displayed only when the user assigned as the alert AI administrator is started, and when a new record is created, the tables related to the definition such as the abnormal value judgment definition table are updated, and a new record in which the corresponding definition group and definition ID are set is added to the alert AI definition group member master 106e. As shown in FIG. 30, in the alert definition creation screen in this embodiment, the Modify/Delete button is displayed only when a definition belonging to a definition group assigned as the alert AI administrator is selected, and when modified or deleted, tables related to the definition, such as the abnormal value determination definition table, are updated or deleted, and when deleted, the record of the corresponding definition ID is deleted from the alert AI definition group member master 106e, and only the definitions displayed in the definition list can be viewed, and only the definition group assigned as the alert AI administrator can be added on the new creation screen. In this embodiment, the definition group to be linked from the alert AI administrator user, the definition group to be linked from the alert AI operation check person user, and the definition to be linked from the operation person user may be linked to the alert AI definition, each setting, and history.

As shown in FIG. 31, the alert AI definition change history screen in this embodiment is a system screen that allows the contents of new creation, modification, and deletion on the alert definition creation screen to be viewed, and the abnormal value determination definition generation management table, abnormal value determination definition history table, extraction condition history table, change point definition history table, abnormality rank definition history table, and data acquisition definition history table are viewed. Here, as shown in FIG. 31, on the alert AI definition change history screen in this embodiment, the definition groups assigned as the alert AI administrator are displayed in a list, and the definition groups assigned as the alert AI operation checker are displayed in a list, and only the definitions displayed in the definition list can be viewed. In this embodiment, the definition group associated with the alert AI administrator user may be identified, and the definition group associated with the alert AI operation checker user may be identified, and the alert AI definition, each setting, and history may be linked.

Also, as shown in FIG. 32, the alert AI inquiry (list) screen in this embodiment is a system screen that allows a list of judgments made based on the alert definition, and the result message table is used as the viewing destination. Here, as shown in FIG. 32, on the alert AI inquiry (list) screen in this embodiment, messages of the results judged based on the definition belonging to the definition group assigned to the alert AI administrator are displayed in a list, messages of the results judged based on the definition belonging to the definition group assigned to the alert AI operation checker are displayed in a list, and messages of the results judged based on the definition assigned to the operation person are displayed in a list. Note that, in this embodiment, the definition group linked from the alert AI administrator user may be identified, and the definition and the result may be linked from the alert AI operation checker user.

As shown in FIG. 33, the alert AI inquiry screen (screen for each scenario) in this embodiment is an analysis system screen that allows the judgments made based on the alert AI definition to be individually viewed using graphs, etc., and the judgment result table and the result message table are the viewing destinations. Here, as shown in FIG. 33, in the alert AI inquiry screen in this embodiment, the system for viewing the judgment results of the definition belonging to the definition group assigned as the alert AI administrator is displayed on the menu, the system for viewing the judgment results of the definition belonging to the definition group assigned as the alert AI operation checker is displayed on the menu, the system for viewing the judgment results of the definition assigned as the operation person is displayed on the menu, and the output button is displayed only when the operation person has output authority. Note that in this embodiment, the definition group to be linked from the alert AI administrator user, the definition group to be linked from the alert AI operation checker user, and the definition to be linked from the operation person user may be linked to the definition and the result.

Also, as shown in FIG. 34, the alert AI execution history/log viewer in this embodiment is a system screen that allows viewing of the log and execution history data that are updated in the database when a judgment is made, and the judgment log table and judgment history table are the viewing destinations. Here, as shown in FIG. 34, in the alert AI execution history/log viewer in this embodiment, the definition group assigned as the alert AI administrator can be selected, and the definition group assigned as the alert AI operation checker can be selected, and only the definitions displayed in the list can be viewed. Note that in this embodiment, the definition group linked from the alert AI administrator user and the definition group linked from the alert AI operation checker user can be identified, and the definition and the result can be linked.

[4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

5. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the alert AI management device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the alert AI management device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the alert AI management device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the alert AI management device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit 106 are storage devices such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

The alert AI management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The alert AI management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful in a variety of industries that require internal controls to prevent fraud.

REFERENCE SIGNS LIST 100 Alert AI management device 102 Control unit 102a User acquisition unit 102b Authority identification unit 102c System control unit 104 Communication interface unit 106 Storage unit 106a User master 106b User group master 106c User group member master 106d Alert AI definition group master 106e Alert AI definition group member master 106f Alert AI management database 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

An alert AI management device comprising a storage unit and a control unit,
The storage unit is
User group member master that links users and user groups,
a user alert definition group relation storage means for storing an alert AI definition group compiled according to an audit scenario based on the nature of monitoring content of an alert AI that determines abnormal values during business execution, the user group or the role type of the user, and a user alert definition group relation table that is set by linking the user group;
An alert AI definition group master that sets an alert AI definition of the alert AI that constitutes the alert AI definition group;
The alert AI definition group and an alert AI definition group member master that is linked and set to the alert AI definition;
an abnormal value determination definition storage means for storing an abnormal value determination definition table in which the definition contents of each of the alert AI definitions are set;
an alert AI management storage means for storing a control table that sets, for each role type, modification authority and viewing authority for the alert AI definition constituting each of the alert AI definition groups, viewing authority for the change history of the alert AI definition, viewing authority for an alert AI list inquiry based on the alert AI definition, viewing authority for an alert AI detail inquiry based on the alert AI definition, and viewing authority for the alert AI execution history and log based on the alert AI definition;
Equipped with
The control unit is
A user acquisition means for acquiring user data of a user who is a target user for authority identification;
an authority specifying means for specifying the role type of the target user and the alert AI definition to which the change authority and/ or the viewing authority has been assigned based on the user data, the user group member master, the user alert definition group relation table, the alert AI definition group master , the alert AI definition group member master, and the abnormal value determination definition table;
A system control means for controlling, based on the control table, the target user's modification and/or viewing of the alert AI definition identified by the authority identification means, viewing of the change history of the alert AI definition, viewing of the alert AI list inquiry, viewing of the alert AI detail inquiry, and/or viewing of the alert AI execution history and log;
An alert AI management device comprising: The role type is:
The alert AI management device of claim 1, further comprising: an alert AI administrator who manages the audit scenario; and an alert AI operation checker who is responsible for checking whether any fraud has occurred in the creation and modification of the alert AI definition, and/or whether the audit check is being performed correctly by an operations personnel who performs an audit check to check whether any abnormalities are found in the actual use of the alert AI and/or the alert AI definition assigned by the alert AI administrator. The authority specifying means is
The alert AI management device described in claim 1 or 2, characterized in that the role type of the target user is identified based on the linkage between the user data, the user group member master, and the user alert definition group relation table , and the alert AI definition for which the change authority and/or the viewing authority is assigned is identified based on the linkage between the user alert definition group relation table, the alert AI definition group master , the alert AI definition group member master, and the abnormal value judgment definition table. The storage unit is
A user alert definition relation storage means for storing the alert AI definition and a user alert definition relation table set by linking the alert AI definition and the user or the user group who is the operation person;
Further comprising:
The authority specifying means is
The alert AI management device of claim 2 further identifies the alert AI definition for which the target user, who is the operations officer, has viewing authority based on the user data, the user group member master , the user alert definition relation table, the alert AI definition group member master, and the abnormal value judgment definition table. The alert AI definition group includes:
The alert AI management device according to any one of claims 1 to 4 , characterized in that it includes a fictitious order alert definition group, a sales recording alert definition group, a fictitious transaction alert definition group, and/or an expense fraud alert definition group. An alert AI management method to be executed by an alert AI management device having a storage unit and a control unit,
The storage unit is
User group member master that links users and user groups,
a user alert definition group relation storage means for storing an alert AI definition group compiled according to an audit scenario based on the nature of monitoring content of an alert AI that determines abnormal values during business execution, the user group or the role type of the user, and a user alert definition group relation table that is set by linking the user group;
An alert AI definition group master that sets an alert AI definition of the alert AI that constitutes the alert AI definition group;
The alert AI definition group and an alert AI definition group member master that is linked and set to the alert AI definition;
an abnormal value determination definition storage means for storing an abnormal value determination definition table in which the definition contents of each of the alert AI definitions are set;
an alert AI management storage means for storing a control table that sets, for each role type, modification authority and viewing authority for the alert AI definition constituting each of the alert AI definition groups, viewing authority for the change history of the alert AI definition, viewing authority for an alert AI list inquiry based on the alert AI definition, viewing authority for an alert AI detail inquiry based on the alert AI definition, and viewing authority for the alert AI execution history and log based on the alert AI definition;
Equipped with
The control unit executes
A user acquisition step of acquiring user data of a target user for which authority is identified;
an authority specifying step of specifying the role type of the target user and the alert AI definition to which the change authority and/ or the viewing authority has been assigned based on the user data, the user group member master, the user alert definition group relation table, the alert AI definition group master , the alert AI definition group member master, and the abnormal value determination definition table;
A system control step of controlling, based on the control table, the target user's modification and/or viewing of the alert AI definition identified in the authority identification step, viewing of the change history of the alert AI definition, viewing of the alert AI list inquiry, viewing of the alert AI detail inquiry, and/or viewing of the alert AI execution history and log;
An alert AI management method comprising: An alert AI management program to be executed by an alert AI management device having a storage unit and a control unit,
The storage unit is
User group member master that links users and user groups,
a user alert definition group relation storage means for storing an alert AI definition group compiled according to an audit scenario based on the nature of monitoring content of an alert AI that determines abnormal values during business execution, the user group or the role type of the user, and a user alert definition group relation table that is set by linking the user group;
An alert AI definition group master that sets an alert AI definition of the alert AI that constitutes the alert AI definition group;
The alert AI definition group and an alert AI definition group member master that is linked and set to the alert AI definition;
an abnormal value determination definition storage means for storing an abnormal value determination definition table in which the definition contents of each of the alert AI definitions are set;
an alert AI management storage means for storing a control table that sets, for each role type, modification authority and viewing authority for the alert AI definition constituting each of the alert AI definition groups, viewing authority for the change history of the alert AI definition, viewing authority for an alert AI list inquiry based on the alert AI definition, viewing authority for an alert AI detail inquiry based on the alert AI definition, and viewing authority for the alert AI execution history and log based on the alert AI definition;
Equipped with
In the control unit,
A user acquisition step of acquiring user data of a target user for which authority is identified;
an authority specifying step of specifying the role type of the target user and the alert AI definition to which the change authority and/ or the viewing authority has been assigned based on the user data, the user group member master, the user alert definition group relation table, the alert AI definition group master , the alert AI definition group member master, and the abnormal value determination definition table;
A system control step of controlling, based on the control table, the target user's modification and/or viewing of the alert AI definition identified in the authority identification step, viewing of the change history of the alert AI definition, viewing of the alert AI list inquiry, viewing of the alert AI detail inquiry, and/or viewing of the alert AI execution history and log;
An alert AI management program for executing the above.

Images