System and method for supporting id inventory and program

Abstract

To provide an art for supporting ID inventory.SOLUTION: A system for supporting ID inventory according to one embodiment of the present disclosure, for supporting the inventory of an ID to be utilized in a business system, comprises an extracting section that extracts an object ID indicative of an ID with which the inventory is concerned from an ID management table storing at least the ID and a business system in which the ID is to be utilized in association with each other, a query setting section that sets the object ID with a query about the inventory, an inventory requesting section that requests an answer to the query set for the object ID to a manager of the business system in which the object ID is to be utilized, and a providing section that provides information representative of a situation of the answer to a user who requested the query.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present disclosure relates to an ID inventory support system, an ID inventory support method, and a program.

Background Art

[0002] Generally, in a company, various business systems (for example, a personnel system, a sales support system, a development system, an attendance management system, an accounting system, etc.) are used. Employees of the company, for example, can use these business systems by using IDs issued by a department that manages these business systems.

[0003] From the viewpoint of preventing unauthorized access to business systems, etc., appropriate management and regular inventory checks of the above-mentioned IDs are required (for example, see Non-Patent Document 1). Note that an inventory check is an operation for checking whether the ID has been correctly created, changed, or deleted, and whether there is a discrepancy from the actual state of use. Such an inventory check is also called "ID inventory check" or "account inventory check".

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, conventionally, when requesting an ID inventory from each department that manages a business system, for example, it has been done by sending an email with an ID list file created using spreadsheet software such as Microsoft Excel (registered trademark). For this reason, the person requesting the inventory has to identify the IDs managed by that department and the administrator and email address of that department for each department to which the request is sent, for example, and the inventory request work has required a lot of work costs.

[0006] The present disclosure has been made in view of the above points, and an object thereof is to provide a technique for supporting ID inventory.

Means for Solving the Problems

[0007] An ID inventory support system according to an aspect of the present disclosure is an ID inventory support system for supporting an inventory of IDs used in a business system, wherein an extraction unit extracts a target ID indicating an ID to be inventoried from an ID management table in which at least the ID and the business system in which the ID is used are stored in association with each other, a question setting unit sets a question regarding the inventory for the target ID, an inventory request unit requests an administrator of the business system in which the target ID is used for an answer to the question set for the target ID, and a providing unit provides information representing the status of the answer to the user who requested the question.

Effects of the Invention

[0008] A technique for supporting ID inventory is provided.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Embodiments for Carrying Out the Invention

[0010] Hereinafter, an embodiment of the present invention will be described. Hereinafter, an ID inventory support system 1 that supports the inventory of IDs for a business system used in a company will be described.

[0011] <Definition of Terms> · Business system: Any computer or computer system used for any business in an enterprise (including computers or computer systems that can be used as cloud services, etc.). Examples of business systems include personnel systems, sales support systems, development systems, attendance management systems, accounting systems, etc.

[0012] · ID: Information for using a business system. An ID may also be referred to as, for example, an account or user ID, etc. In addition to those assigned to users of a business system, there are also IDs that are shared and used by multiple users for the purpose of being used in certain businesses or operations, etc. (this is also called a "shared ID", etc.). While a normal ID is associated with a specific user, a shared ID is not associated with a specific user and is associated, for example, with things such as a specific department or organization, the object of aggregation and management, the purpose of use, the application to be used, etc.

[0013] · ID inventory check: The work of checking whether an ID has been correctly created, modified, deleted, or there is no deviation from the actual situation of use, etc. Such work is also simply referred to as "inventory check". An ID inventory check may also be referred to as, for example, an account inventory check, etc. An ID inventory check is generally often carried out regularly, but may also be carried out irregularly.

[0014] · Inventory requester: The person who requests the administrator to conduct an inventory check on the ID to be inventoried. The inventory requester sets questions related to the inventory check, such as whether to continue using the ID or delete it, etc., and requests the administrator for the answers.

[0015] · Managers: It includes the following two types of managers. The first type of manager is the person in charge of managing the business system in the department or organization (hereinafter, collectively referred to as "organization" for departments and organizations) that oversees the business system (hereinafter, such a manager is also referred to as the "system manager"). For example, when the business system is the personnel system, the overseeing organization is the "Personnel Department", and the system manager is the person in charge of managing the personnel system in the Personnel Department. Similarly, for example, when the business system is the sales support system, the overseeing organization is the "Sales Department", and the system manager is the person in charge of managing the sales support system in the Sales Department. The second type of manager is the person in charge of managing the IDs for each business system (such as newly adding, updating, deleting IDs, etc.) and providing operation support for the business system so that users of the business system can properly use the system (hereinafter, such a person in charge is also referred to as the "usage manager"). For example, when the business system is the personnel system, employees in the Personnel Department may be the usage managers for each organization using the personnel system, or employees of the organization using the personnel system may be the usage managers for that organization. Also, in a certain organization, the usage managers for a certain number of business systems (such as the personnel system and the sales support system) may be different, or the same employee may hold both positions.

[0016] Hereinafter, when referring to the "manager of the business system" or simply "manager", it shall be deemed to include the above two types of managers (system manager, usage manager).

[0017] · Respondents: They are the people who answer the questions set by the inventory requester. Respondents are basically the above-mentioned managers, but may also include those who are entrusted by the manager to answer on behalf (hereinafter, also referred to as proxy respondents). Typically, proxy respondents include subordinates ordered by the manager to conduct inventory operations, those who assist or act on behalf of the manager within each organization using the business system, and further, managers of smaller organizations within each organization using the business system and those who assist or act on behalf of their operations, etc.

[0018] <Overall configuration example of the ID inventory support system 1> An overall configuration example of the ID inventory support system 1 according to this embodiment is shown in FIG. 1. As shown in FIG. 1, the ID inventory support system 1 according to this embodiment includes an ID inventory support device 10 and a plurality of terminals 20. The ID inventory support device 10 and each terminal 20 are communicably connected via a communication network 30 including, for example, the Internet or the like.

[0019] The ID inventory support device 10 is a computer or a computer system such as a general-purpose server that supports ID inventory. The ID inventory support device 10 creates an event representing an inventory (hereinafter, also referred to as an "inventory event") in response to a request from an inventory requester, and requests an appropriate administrator for an answer to a question set in this inventory event. Further, the ID inventory support device 10 outputs the result of the ID inventory as a report (this is also called an audit report or the like).

[0020] The terminal 20 is various computers or computer systems used by employees of a company that uses a business system targeted for ID inventory. Examples of the terminal 20 include a PC (personal computer), a tablet terminal, a smartphone, a wearable device, and the like. Hereinafter, the terminal 20 used by the inventory requester is also referred to as the "requester terminal 20", the terminal 20 used by the administrator is also referred to as the "administrator terminal 20", and the terminal 20 used by the proxy respondent is also referred to as the "proxy respondent terminal 20". The inventory requester has an account (hereinafter, also referred to as an "ID inventory account") for logging in to the ID inventory support device 10, but the administrator and the proxy respondent do not necessarily have an ID inventory account (the administrator and the proxy respondent may or may not have an ID inventory account). Further, among the accounts registered in the ID inventory support device 10, only the "ID inventory account" having a special privilege to perform ID inventory may be able to create an inventory event.

[0021] Note that the overall configuration example of the ID inventory support system 1 shown in FIG. 1 is just an example and is not limited thereto. For example, in the example shown in FIG. 1, the ID inventory support device 10 is composed of one device, but it may be composed of a plurality of devices connected to each other via a communication network.

[0022] <Functional configuration example of the ID inventory support device 10 and the terminal 20> A functional configuration example of the ID inventory support device 10 and the terminal 20 according to the present embodiment is shown in FIG. 2.

[0023] ≪ID inventory support device 10≫ As shown in FIG. 2, the ID inventory support device 10 according to the present embodiment includes an ID inventory support processing unit 101 and a report output unit 102. Each of these units is realized, for example, by a process in which one or more programs installed in the ID inventory support device 10 are executed by a processor such as a CPU (Central Processing Unit). Further, the ID inventory support device 10 according to the present embodiment includes an ID management table storage unit 103, a personnel information table storage unit 104, an administrator table storage unit 105, and an event information storage unit 106. Each of these storage units is realized, for example, by a storage device such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory. However, a part of these storage units may be realized by a storage device such as a database server connected to the ID inventory support device 10 via a communication network.

[0024] The ID inventory support processing unit 101 executes various processes for supporting ID inventory. The ID inventory support processing unit 101 includes an inventory event creation unit 111, a target ID extraction unit 112, a UI providing unit 113, and an inventory event management unit 114.

[0025] The inventory event creation unit 111 creates information representing an inventory event (hereinafter referred to as event information) in response to a request from the requester terminal 20. Further, the inventory event creation unit 111 requests the administrator of the business system in which the ID to be inventoried is used to conduct an inventory of the ID to be inventoried in this inventory event.

[0026] When the event information is created by the inventory event creation unit 111, the target ID extraction unit 112 extracts the ID to be inventoried in this inventory event. At this time, the target ID extraction unit 112 refers to the personnel information table stored in the personnel information table storage unit 104 and the administrator table stored in the administrator table storage unit 105 as necessary, and extracts the ID to be inventoried from the ID management table stored in the ID management table storage unit 103. The details of the ID management table stored in the ID management table storage unit 103, the personnel information table stored in the personnel information table storage unit 104, and the administrator table stored in the administrator table storage unit 105 will be described later.

[0027] When the event information is created by the inventory event creation unit 111, the UI providing unit 113 provides various screens as a UI (user interface) to the terminal 20.

[0028] The inventory event management unit 114 stores the event information created by the inventory event creation unit 111 in the event information storage unit 106. Further, the inventory event management unit 114 updates the event information stored in the event information storage unit 106 in response to requests from the requester terminal 20, the administrator terminal 20, the proxy responder terminal 20, etc. The details of the event information stored in the event information storage unit 106 will be described later.

[0029] The report output unit 102 outputs a report representing the result of the ID inventory to a predetermined output destination.

[0030] ≪Terminal 20≫ As shown in FIG. 2, the terminal 20 according to the present embodiment includes a UI processing unit 201. The UI processing unit 201 is realized, for example, by a process executed by a processor such as a CPU for one or more programs such as a web browser installed in the terminal 20.

[0031] The UI processing unit 201 displays the UI provided from the ID inventory support device 10 on a display device such as a display included in the terminal 20. Further, the UI processing unit 201 accepts various operations on the UI.

[0032] ≪ID Management Table≫ An example of the ID management table stored in the ID management table storage unit 103 is shown in FIG. 3. The ID management table 1100 shown in FIG. 3 is composed of one or more records (hereinafter, these records are also referred to as "ID management records"). Each ID management record represents an object such as an ID of a business system and a person (employee), organization, etc. associated with that ID, and includes employee information and ID information. The employee information includes, for example, employee number, name, company name, organization name, etc. The ID information includes the ID (ID of the business system) associated with the object (employee, organization, etc.) represented by the employee information.

[0033] For example, the ID management record in the first row of the ID management table 1100 shown in FIG. 3 includes the employee number "001", the name "Ichiro Tanaka", the company name "A", and the organization name "Personnel Department" as employee information, and also includes the personnel system "h001" and the attendance management system "a001" as ID information. This indicates that the ID "h001" of the personnel system and the ID "a001" of the attendance management system are associated with "Ichiro Tanaka" (employee number: 001) belonging to the Personnel Department of Company A.

[0034] Similarly, for example, in the ID management record on the second line of the ID management table 1100 shown in FIG. 3, the employee information includes employee number "002", name "Jiro Suzuki", company name "A", and organization name "Sales Department", etc. Also, as ID information, it includes sales support system "s001" and attendance management system "a002", etc. This indicates that the ID "s001" of the sales support system and the ID "a002" of the attendance management system are associated with "Jiro Suzuki" (employee number: 002) belonging to the Personnel Department of Company A.

[0035] On the other hand, for example, in the ID management record on the sixth line of the ID management table 1100 shown in FIG. 3, the employee information does not include the employee number and name, but only includes the company name "A" and the organization name "Development Department". As ID information, it includes the development support system "d900". This indicates that the ID "d900" of the development support system is not associated with a specific employee and is a shared ID shared by the employees in the Development Department.

[0036] In the example shown in FIG. 3, when the employee number and name are not included in the employee information, the ID included in the ID information corresponding to the employee information is regarded as a shared ID. However, this is just an example and is not limited to this. For example, a flag indicating whether it is a shared ID or the like may be included in the ID management record, and the flag may indicate whether the ID included in the ID information is a shared ID.

[0037] Also, the ID information of the ID management record may include, for example, for each ID, the last use date and time indicating the date and time when the ID was last used.

[0038] ≪Personnel Information Table≫ An example of the personnel information table stored in the personnel information table storage unit 104 is shown in FIG. 4. The personnel information table 1200 shown in FIG. 4 is composed of one or more records (hereinafter, these records are also referred to as "personnel information records"). Each personnel information record represents the organization to which the employee currently belongs (the latest organization), whether the employee has retired, etc. For example, it includes employee number, name, company name, organization name, retirement flag, etc. The retirement flag is a flag indicating whether the employee has retired. For example, if the employee has retired, "1" is set, and if not, a blank is set. Note that each personnel information record included in the personnel information table is synchronized with, for example, the personnel information (employee name, organization to which the employee belongs, whether retired, etc.) managed by the personnel system, and represents the latest personnel information.

[0039] For example, the personnel information record in the first row of the personnel information table 1200 shown in FIG. 4 includes employee number "001", name "Ichiro Tanaka", company name "A", organization name "Personnel Department", etc. This indicates that "Ichiro Tanaka" (employee number: 001) currently belongs to the Personnel Department of Company A.

[0040] Also, for example, the personnel information record in the fifth row of the personnel information table 1200 shown in FIG. 4 includes employee number "005", name "Aiko Saito", company name "A", organization name "Development Department", etc. This indicates that "Aiko Saito" (employee number: 005) has retired from Company A. It also indicates that the organization to which "Aiko Saito" (employee number: 005) belonged at the time of retirement from Company A was the "Development Department".

[0041] Here, each personnel information record included in the personnel information table represents the organization to which the employee currently belongs if the employee has not retired. For example, the employee information of the ID management record in the 4th row of the ID management table 1100 shown in FIG. 3 includes the employee number "004", the name "Saburo Sato", the company name "A", and the organization name "Personnel Department". On the other hand, for example, the personnel information record in the 4th row of the personnel information table 1200 shown in FIG. 4 includes the employee number "004", the name "Saburo Sato", the company name "A", and the organization name "Development Department". Therefore, it can be seen that the current affiliated organization of "Saburo Sato" (employee number: 004) is the "Development Department", but before the transfer to the "Development Department", he belonged to the "Personnel Department". Also, it can be seen that the ID "d001" of the development system and the ID "a004" of the attendance management system remain associated with "Saburo Sato" (employee number: 004) when he belonged to the "Personnel Department".

[0042] In this way, each personnel information record included in the personnel information table represents the current organization (the latest organization) to which the employee belongs or whether the employee has retired. On the other hand, the affiliated organization of the employee represented by the employee information of the ID management record included in the above ID management table is not necessarily the latest, and there may also be ID management records regarding retired employees. For example, "Aiko Saito" (employee number: 005) has retired from Company A, but there is an ID management record regarding "Aiko Saito" (employee number: 005) in the 5th row of the ID management table 1100 shown in FIG. 3.

[0043] In the example shown in FIG. 4, it is assumed that the organization to which the employee currently belongs (the latest organization) and whether the employee has retired or not are included in the personnel information record. However, not only the latest organization but also the history of the organizations to which the employee has belonged so far (i.e., the transfer history) may be included. In addition, the personnel information record may include various information other than the above (for example, email address, extension number, various flags other than the retired flag, etc.). Examples of flags other than the retired flag include a flag indicating whether the employee is on secondment, a flag indicating whether the employee is concurrently employed in multiple organizations, a flag indicating whether the employee has transferred from the relevant organization, a flag indicating whether the employee is on leave, a flag indicating whether the employee is a temporary resident (non-resident), etc.

[0044] ≪Administrator Table≫ An example of the administrator table stored in the administrator table storage unit 105 is shown in FIG. 5. The administrator table 1310 shown in FIG. 5(a) is a table composed of one or more records representing system administrators (hereinafter, these records are also referred to as "system administrator records"). On the other hand, the administrator table 1320 shown in FIG. 5(b) is a table composed of one or more records representing usage administrators (hereinafter, these records are also referred to as "usage administrator records"). Hereinafter, the table composed of system administrator records is also referred to as the "system administrator table", the table composed of usage administrator records is also referred to as the "usage administrator table", and when referring to either or both of them, it is simply referred to as the "administrator table".

[0045] As shown in FIG. 5(a), each system administrator record includes, for example, employee number, name, company name, organization name, email address, etc.

[0046] For example, in the first row of the system administrator record in the system administrator table 1310 shown in Fig. 5(a), the employee number "101", name "Hanako Kobayashi", company name "A", organization name "Personnel Department", etc. are included. This indicates that "Hanako Kobayashi" (employee number: 101) is the system administrator of the business system (for example, the personnel system) under the jurisdiction of the Personnel Department of Company A.

[0047] Similarly, for example, in the second row of the system administrator record in the system administrator table 1310 shown in Fig. 5(a), the employee number "111", name "Taro Sato", company name "A", organization name "Sales Department", etc. are included. This indicates that "Taro Sato" (employee number: 111) is the system administrator of the business system (for example, the sales support system) under the jurisdiction of the Sales Department of Company A.

[0048] Note that, for example, when there is no system administrator in the business system under the jurisdiction of a certain organization, a system administrator record containing only the organization name of that organization may be stored in the system administrator table, or the system administrator record regarding that organization may not exist in the system administrator table. Also, it is possible that a certain organization manages multiple business systems and the system administrators of each business system are different. In such a case, the system administrator record may include a "target system" in which the system name of the business system managed by the system administrator is set.

[0049] On the other hand, as shown in Fig. 5(b), each user administrator record includes, for example, the employee number, name, company name, organization name, target system, email address, etc.

[0050] For example, in the first row of the user administrator record in the user administrator table 1320 shown in Fig. 5(b), the employee number "334", name "Toru Tanaka", company name "A", organization name "Development Department", target system "XX System", etc. are included. This indicates that "Toru Tanaka" (employee number: 334) is the user administrator of the "XX System" in the Development Department of Company A.

[0051] Similarly, in the second line's usage administrator record of the usage administrator table 1320 shown in FIG. 5(b), it includes employee number "236", name "Yamada Akira", company name "A", organization name "Development Department", target system "XX System", etc. This indicates that "Yamada Akira" (employee number: 236) is the usage administrator of the "XX System" in the Development Department of Company A.

[0052] Similarly, for example, in the third line's usage administrator record of the usage administrator table 1320 shown in FIG. 5(b), it includes employee number "022", name "Suzuki Hanako", company name "A", organization name "General Affairs Department", target system "OO System", etc. This indicates that "Suzuki Hanako" (employee number: 022) is the usage administrator of the "OO System" in the General Affairs Department of Company A.

[0053] Here, from the first and third line's usage administrator records of the usage administrator table 1320 shown in FIG. 5(b), it can be seen that the "OO System" is used by both the Development Department and the General Affairs Department of Company A, and the usage administrator of the Development Department is "Yamada Akira" (employee number: 236), and the usage administrator of the General Affairs Department is "Suzuki Hanako" (employee number: 022). Thus, the usage administrator can be different for each organization using the business system.

[0054] Note that, for example, when there is no usage administrator for a business system used by a certain organization, a usage administrator record containing only the organization name of that organization and the system name of that business system may be stored in the usage administrator table, or the usage administrator record regarding that organization and business system may not exist in the usage administrator table.

[0055] <<Event Information>> An example of the event information stored in the event information storage unit 106 is shown in FIG. 6. The event information 1400 shown in FIG. 6 represents an inventory event. For example, it includes event ID, event name, event status, creator, response deadline, target system, conditions, target ID, response status, response content, responder, etc.

[0056] The event ID is identification information that uniquely identifies an inventory event. The event name is the name of the inventory event. The event status is the status of the inventory event. Examples of the event status include "In progress" indicating that the inventory event is being created, "Answer reception in progress" indicating that the inventory event has been created and answers to questions are being accepted, "Deadline" indicating that the acceptance of answers to questions has ended, "Completed" indicating that the inventory event has been completed, and so on. The creator is the employee number, name, etc. of the creator who created the inventory event (i.e., the inventory requester). The answer deadline is the deadline for answering questions in the inventory event. The target system is the business system that is the target of the inventory in the inventory event. The conditions are the conditions (extraction conditions) used when extracting the IDs of the inventory targets in the inventory event. The target ID is the ID of the inventory target. The answer status is the answer status of the questions set for each ID of the inventory target. Examples of the answer status include "Answered" indicating that an answer has been given to the question, "Unanswered" indicating that an answer to the question has not yet been given, and so on. The answer content is the content of the answer to the questions set for each ID of the inventory target. The answerer is the employee number, name, etc. of the person who can answer the questions set for each ID of the inventory target (e.g., the administrator of the business system (system administrator, usage administrator) where the ID is used). Note that the answer status, answer content, and answerer exist for each ID of the inventory target.

[0057] <Overall processing flow of the ID inventory support system 1> Hereinafter, the overall processing flow of the ID inventory support system 1 according to the present embodiment will be described with reference to FIG. 7.

[0058] Step S101: The ID inventory support system 1 creates an inventory event. Here, the inventory event is created, for example, according to the following procedures 1-1 to 1-22.

[0059] Step 1-1) The UI processing unit 201 of the requester terminal 20 transmits a stocktake event creation start request to the ID stocktake support device 10 in response to a stocktake event creation start operation by the stocktake requester. Examples of the stocktake event creation start device include an access operation to a web page for creating a stocktake event.

[0060] Step 1-2) The ID stocktake support processing unit 101 of the ID stocktake support device 10 transmits a target selection screen to the requester terminal 20 via the UI providing unit 113. The target selection screen is one of the screens for creating a stocktake event, and is a screen on which information for extracting the IDs to be subject to stocktake is selected or specified.

[0061] Step 1-3) The UI processing unit 201 of the requester terminal 20 displays the target selection screen received from the ID stocktake support device 10 and accepts various operations on the target selection screen.

[0062] Here, an example of the target selection screen is shown in FIG. 8. The target selection screen 2100 shown in FIG. 8 includes an extraction target system selection column 2110, an extraction condition selection column 2120, a next button 2130, and a cancel button 2140.

[0063] The extraction target system selection column 2110 is a UI component for selecting the business system that extracts the IDs to be inventoried. The extraction target system selection column 2110 includes check boxes 2111. The inventory requester can select one or more check boxes 2111 to select the business system corresponding to the selected check box 2111 as the extraction target system for the IDs. In the example shown in Figure 8, the case where the check box 2111 corresponding to the development support system is selected is shown. Also, the inventory requester can select all business systems by selecting the uppermost check box 2111 among the check boxes 2111. Note that the extraction target system selection column 2110 shown in Figure 8 also includes the "number of registered IDs" representing the number of IDs registered in the business system, the "inventory status" representing the inventory status when the ID of the business system has already been targeted for inventory, and the "inventory completion date" representing the completion date when the inventory has already been completed.

[0064] The extraction condition selection column 2120 is a UI component for selecting the conditions (extraction conditions) for extracting the IDs to be inventoried. The extraction condition selection column 2120 includes check boxes 2121. The inventory requester can select one or more check boxes 2121 to select the extraction conditions corresponding to the selected check box 2121. In the example shown in Figure 8, the case where the check box 2121 corresponding to the extraction condition "unused for a long time" is selected is shown. Also, the inventory requester can select all extraction conditions by selecting the uppermost check box 2121 among the check boxes 2121.

[0065] Here, in the example shown in FIG. 8, there are extraction conditions of "unused for a long time", "not set by the administrator", "shared ID", and "ID of a retiree / transferred person". "Unused for a long time" is a condition for extracting IDs that have not been used for a predetermined period or longer. "Not set by the administrator" is a condition for extracting IDs in a business system where there is no administrator, or IDs that are not shared IDs and are not associated with a specific employee (i.e., IDs that are not shared and have no owner), or both types of IDs. "Shared ID" is a condition for extracting shared IDs. "ID of a retiree / transferred person" is a condition for extracting IDs that were used by a retiree or IDs of those who transferred from one organization to another and are IDs in the business system under the jurisdiction of the organization before the transfer. However, these extraction conditions are just examples, and the extraction conditions are not limited to these.

[0066] The Next button 2130 is a UI component for transitioning to the next screen. On the other hand, the Cancel button 2140 is a UI component for canceling the creation of the inventory event. In the following, it is assumed that at least one of the business system (extraction target system) for extracting the IDs to be inventoried by the inventory requester and the extraction conditions is selected, and then the Next button 2130 is pressed.

[0067] Note that when one business system is selected in the extraction target system selection field 2110, the extraction conditions do not have to be selected in the extraction condition selection field 2120. Also, when one or more extraction conditions are selected in the extraction condition selection field 2120, the business system does not have to be selected in the extraction target system selection field 2110. That is, it is sufficient that one or more are selected from both the extraction target system selection field 2110 and the extraction condition selection field 2120.

[0068] Step 1-4) The UI processing unit 201 of the requester terminal 20 transmits information regarding the extraction target system / extraction conditions selected in the above steps 1-3 (hereinafter referred to as extraction target information) to the ID inventory support device 10.

[0069] Step 1-5) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives the extraction target information from the requester terminal 20, the target ID extraction unit 112 extracts the ID to be inventoried (and the corresponding employee information). The target ID extraction unit 112 extracts the ID to be inventoried (and the corresponding employee information) according to the following (A), (B), or (C).

[0070] (A) When only the extraction target system is included in the extraction target information In this case, the target ID extraction unit 112 extracts the ID of the extraction target system from the IDs stored in the ID management table, and extracts the employee information associated with that ID.

[0071] For example, taking the ID management table 1100 shown in FIG. 3 as an example, when the extraction target system is the "Sales Support System", the ID "s001" and the corresponding employee information (employee number "002", name "Jiro Suzuki", company name "A", organization name "Sales Department", etc.), and the ID "s002" and the corresponding employee information (employee number "003", name "Hanako Yamada", company name "A", organization name "Sales Department", etc.) are extracted.

[0072] (B) When only the extraction conditions are included in the extraction target information In this case, the target ID extraction unit 112 refers to the personnel information table, the administrator table, etc. as necessary, extracts the IDs that meet the extraction conditions from the IDs stored in the ID management table, and extracts the employee information associated with that ID. Hereinafter, the extraction method when the extraction conditions are "unused for a long time", "not set by the administrator", "shared ID", or "retired ID / transferred ID" will be described. When multiple extraction conditions are included in the extraction target information, the extraction methods described below may be combined.

[0073] · When the extraction condition is "unused for a long time" The ID information of the ID management records that make up the ID management table shall include the last usage date and time of each ID. At this time, the target ID extraction unit 112 extracts from the ID management table the IDs whose last usage date and time is before a predetermined period, and extracts the employee information associated with the IDs.

[0074] ·When the extraction condition is "not set by administrator" When extracting the IDs of business systems without an administrator, first, the target ID extraction unit 112 refers to the administrator table to identify the organizations without an administrator. That is, it identifies the organization in charge of the business system without a system administrator, or the organization using the business system without a usage administrator, or both. Then, the target ID extraction unit 112 extracts from the ID management table the ID of the business system among the employee information including the organization name of the identified organization and the ID associated therewith. Note that this is just an example, and in addition, for example, when some administrator is associated with an ID, the ID may be extracted individually.

[0075] When extracting an ID that is not a shared ID and is not associated with a specific employee (that is, an ID that is not a shared ID and has no owner), the target ID extraction unit 112 extracts from the ID management table, for example, the IDs that exist only in the ID management table and have no employee information (or the employee information is null). Or, for example, when a flag indicating whether it is a shared ID is included in the ID management record, the target ID extraction unit 112 extracts from the ID management table the ID associated with a flag having a value indicating that it is not a shared ID and is associated with employee information that does not include at least the employee number and name.

[0076] ·When the extraction condition is "shared ID" The target ID extraction unit 112 extracts the shared IDs from the ID management table.

[0077] ·When the extraction condition is "former employee ID · transferred employee ID" When extracting the IDs used by retired employees, first, the target ID extraction unit 112 refers to the personnel information table to identify the employee numbers of the retired employees. This can be done, for example, by identifying the employee numbers included in the personnel information records where the retirement flag is "1". Then, the target ID extraction unit 112 extracts the IDs associated with the employee numbers of the retired employees from the ID management table.

[0078] When extracting the IDs of those who have transferred from one organization to another and the IDs of the business systems under the jurisdiction of the organization before the transfer, first, for each personnel information record in the personnel information table where the retirement flag is not "1", the target ID extraction unit 112 identifies the ID management records that contain the same employee number as that personnel information record and a different organization name from that personnel information record. Then, the target ID extraction unit 112 extracts the employee information and the associated IDs included in the identified ID management records from the ID management table.

[0079] (C) When both the extraction target system and the extraction conditions are included in the extraction target information In this case, the target ID extraction unit 112 may extract the IDs to be inventoried by combining (A) and (B) above.

[0080] Procedure 1-6) The ID inventory support processing unit 101 of the ID inventory support device 10 transmits the target ID list screen to the requester terminal 20 through the UI providing unit 113. The target ID list screen is a screen on which a list of the IDs extracted in the above Procedure 1-5 is displayed. However, it is not essential to transmit the target ID list screen to the requester terminal 20, and this procedure may not be executed. Note that if this procedure is not executed, the next Procedure 1-7 is also not executed.

[0081] Procedure 1-7) The UI processing unit 201 of the requester terminal 20 displays the target ID list screen received from the ID inventory support device 10 and accepts various operations on the target ID list screen.

[0082] Here, an example of the target ID list screen is shown in FIG. 9. The target ID list screen 2200 shown in FIG. 9 includes an ID list display column 2210, a next button 2220, and a back button 2230.

[0083] The ID list display column 2210 is a UI component in which the IDs extracted in the above steps 1-5 (i.e., the IDs of the inventory target) and the corresponding employee information are displayed. By referring to the ID list display column 2210, the inventory requester can confirm the IDs extracted as the inventory targets and the employee information corresponding to those IDs.

[0084] The next button 2220 is a UI component for transitioning to the next screen. On the other hand, the back button 2230 is a UI component for transitioning to the previous screen. Hereinafter, it is assumed that the next button 2220 is pressed.

[0085] Here, for example, when IDs are extracted according to the extraction condition "not set by administrator", IDs associated with employees in an organization without an administrator or IDs associated with employee information not including the organization name may be extracted. When these IDs are extracted, since no administrator who is the inventory request destination is associated with these IDs, the inventory requester can set the administrator (or the organization where the administrator exists) who is the inventory request destination for these IDs on the target ID list screen 2200.

[0086] Note that the inventory requester may, for example, select an ID to be excluded from the inventory target from among the IDs displayed on the ID list display column 2210 of the target ID list screen 2200, or add an ID to be the inventory target to the ID list display column 2210.

[0087] Also, the inventory requester may be able to customize the information that can be confirmed when the respondent answers the question, for example, on the ID list display column 2210 of the target ID list screen 2200. For example, in the example shown in FIG. 9, the employee information includes the employee number, name, company name, and organization name. However, if the inventory requester and the respondent are within the same company, the company name may be considered unnecessary. Therefore, the inventory requester may delete the company name and use the employee number, name, and organization name as the employee information that can be confirmed when the respondent answers the question. Furthermore, the inventory requester may be able to preview the screen that is displayed when the respondent answers the question.

[0088] Step 1-8) The UI processing unit 201 of the requester terminal 20 transmits a transition request to the next screen to the ID inventory support device 10.

[0089] Step 1-9) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the next screen from the requester terminal 20, the UI providing unit 113 determines whether there is an ID to be warned among the IDs displayed on the target ID list screen. The UI providing unit 113 may determine, for example, whether there is an ID that meets a preset warning condition among the IDs displayed on the target ID list screen. Examples of the warning condition include the existence of an ID that is not a shared ID and is not associated with a specific employee (that is, the existence of an ID that is not a shared ID and has no owner), the existence of an ID of a business system without an administrator, and the like. Hereinafter, it is assumed that it is determined in this procedure that there is an ID to be warned. Note that if it is not determined in this procedure that there is an ID to be warned, the following steps 1-10 to 1-11 are not executed.

[0090] Step 1-10) When it is determined in step 1-9 above that there is an ID to be warned, the ID inventory support processing unit 101 of the ID inventory support device 10 transmits a warning screen to the requester terminal 20 by the UI providing unit 113. The warning screen is, for example, a screen on which a list of IDs that meet the warning condition is displayed.

[0091] Step 1-11) The UI processing unit 201 of the requester terminal 20 displays the warning screen received from the ID inventory support device 10 and accepts various operations on the warning screen. Note that the warning screen is, for example, pop-up displayed on the target ID list screen.

[0092] Here, an example of the warning screen is shown in FIG. 10. The warning screen 2300 shown in FIG. 10 includes a first warning ID display column 2310, a second warning ID display column 2320, a next button 2330, and a cancel button 2340.

[0093] The first warning ID display column 2310 is a UI component on which a list of IDs that are not shared IDs and not associated with a specific employee is displayed. The second warning ID display column 2320 is a UI component on which a list of IDs of business systems without an administrator is displayed. The next button 2330 is a UI component for closing the warning screen and transitioning to the next screen. On the other hand, the cancel button 2340 is a UI component for closing the warning screen. Hereinafter, it is assumed that the next button 2330 is pressed by the inventory requester.

[0094] Step 1-12) The UI processing unit 201 of the requester terminal 20 sends a transition request to the next screen to the ID inventory support device 10.

[0095] Step 1-13) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the next screen from the requester terminal 20, the UI providing unit 113 sends an event basic information setting screen to the requester terminal 20. The event basic information setting screen is a screen for setting basic information of an event such as an event name.

[0096] Step 1-14) The UI processing unit 201 of the requester terminal 20 displays the event basic information setting screen received from the ID inventory support device 10 and accepts various operations on the event basic information setting screen.

[0097] Here, an example of the event basic information setting screen is shown in FIG. 11. On the event basic information setting screen 2400 shown in FIG. 11, there are an event name setting field 2411, an event ID display field 2412, a target system display field 2413, a condition display field 2414, a request content setting field 2415, a destination display field 2416, a sender display field 2417, a reply destination setting field 2418, a response deadline setting field 2419, a requester setting field 2420, a next button 2430, and a back button 2440.

[0098] The event name setting field 2411 is a UI component where the inventory requester can input an arbitrary event name. The event ID display field 2412 is a UI component where the event ID that uniquely identifies the inventory event is displayed. Note that the event ID is determined by the inventory event creation unit 111. The target system display field 2413 is a UI component where the business system in which the ID of the inventory target is used (in other words, the business system of the inventory target) is displayed. The condition display field 2414 is a UI component where the extraction conditions used when extracting the ID of the inventory target are displayed. The request content setting field 2415 is a UI component where the inventory requester can input arbitrary request content. The destination display field 2416 is a UI component where the destination of the inventory request is set. In the example shown in FIG. 11, in the destination display field 2416, "Administrators of each organization", which indicates that the administrator of the business system in which the ID of the inventory target is used is the destination, is displayed. The sender display field 2417 is a UI component where the sender (in the example shown in FIG. 11, the sender's email address) when making the inventory request is displayed. The reply destination setting field 2418 is a UI component where the inventory requester can arbitrarily input the reply destination (for example, the email address of the reply destination, etc.) for the inventory request. The response deadline setting field 2419 is a UI component where the inventory requester can input or select an arbitrary date as the response deadline date. The requester setting field 2420 is a UI component where the inventory requester can arbitrarily input information regarding the requester (for example, name, extension number, etc.). Note that in the response deadline setting field 2419, for example, a date a predetermined period from the present may be automatically set.

[0099] The Next button 2430 is a UI component for transitioning to the next screen. On the other hand, the Back button 2440 is a UI component for transitioning to the previous screen. In the following, it is assumed that after the necessary information has been input on the Event Basic Information Setting Screen 2400 by the inventory requester, the Next button 2430 is pressed.

[0100] Note that in the example shown in FIG. 11, the case where an inventory request for each organization's administrator is notified by email is shown, but this is just an example, and the inventory request may be notified by a method other than email and is not limited to a specific notification method. Examples of notification methods other than email include notification of an inventory request on a web page, notification of an inventory request by a messaging application such as a business chat, etc.

[0101] Step 1-15) The UI processing unit 201 of the requester terminal 20 sends a transition request to the next screen to the ID inventory support device 10.

[0102] Step 1-16) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the next screen from the requester terminal 20, it sends a question setting screen to the requester terminal 20 through the UI providing unit 113. The question setting screen is a screen for setting questions regarding the inventory for the ID of the inventory target.

[0103] Step 1-17) The UI processing unit 201 of the requester terminal 20 displays the question setting screen received from the ID inventory support device 10 and accepts various operations on the question setting screen.

[0104] Here, an example of the question setting screen is shown in FIG. 12. The question setting screen 2500 shown in FIG. 12 includes a New Addition button 2510, a question setting column 2520, a Next button 2530, and a Back button 2540.

[0105] The new addition button 2510 is a UI component for adding rows to the question setting column 2520. When the new addition button 2510 is pressed by the inventory requester, a row is added to the question setting column 2520. Note that rows can be added up to a predetermined maximum number (for example, up to 4 rows) in the question setting column 2520.

[0106] The question setting column 2520 is a UI component for setting questions for the ID of the inventory target. When a row is added to the question setting column 2520 by pressing the new addition button 2510, for this row, set a question name representing the name of the question, a mandatory flag indicating whether an answer is required for the question, and an answer format indicating whether a selection-type or descriptive-type answer is required, and when the answer format is "selection-type", set the options, so that questions are set for the ID of the inventory target. The options can be set, for example, in comma-separated form. Note that a UI component for deleting that row is associated with each row, and the inventory requester can delete the row corresponding to the UI component from the question setting column 2520 by pressing the UI component.

[0107] In the example shown in FIG. 12, in the first row of the question setting column 2520, the question name "Whether ID continuation is required", mandatory flag "mandatory", answer format "selection-type", and options "continuation, not required" are set. This represents a question for asking the respondent whether to continue using the ID of the inventory target or not.

[0108] Also, in the example shown in FIG. 12, in the second row of the question setting column 2520, the question name "Scheduled deletion date", mandatory flag "not mandatory", and answer format "descriptive" are set. This represents a question for asking the respondent about the scheduled deletion date of the ID of the inventory target.

[0109] Needless to say, various questions other than those described in the example shown in FIG. 12 can be set. For example, when pausing the ID instead of deleting it, a question indicating whether to pause the ID can also be set.

[0110] The Next button 2530 is a UI component for transitioning to the next screen. On the other hand, the Back button 2540 is a UI component for transitioning to the previous screen. In the following, it is assumed that after questions regarding the ID of the inventory target are set on the question setting screen 2500 by the inventory requester, the Next button 2530 is pressed.

[0111] Step 1-18) The UI processing unit 201 of the requester terminal 20 transmits a transition request to the next screen to the ID inventory support device 10.

[0112] Step 1-19) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the next screen from the requester terminal 20, the UI providing unit 113 transmits an inventory request screen to the requester terminal 20. The inventory request screen is a screen for requesting the inventory of that ID from the administrator of the business system that uses the ID of the inventory target.

[0113] Step 1-20) The UI processing unit 201 of the requester terminal 20 displays the inventory request screen received from the ID inventory support device 10 and accepts various operations on the inventory request screen.

[0114] Here, an example of the inventory request screen is shown in FIG. 13. The inventory request screen 2600 shown in FIG. 13 includes a destination list display column 2610, a request content display column 2620, a request execution button 2630, and a back button 2640.

[0115] The destination list display column 2610 is a UI component in which a list of destinations to which the inventory request is to be notified is displayed. The request content display column 2620 is a UI component in which the request content etc. set on the event basic information setting screen are displayed. In the example shown in FIG. 13, the destination, sender, reply-to, and body of the email are displayed in the request content display column 2620.

[0116] The request execution button 2630 is a UI component for executing an inventory request. On the other hand, the back button 2640 is a UI component for transitioning to the previous screen. When the request execution button 2630 is pressed by the inventory requester, event information representing the inventory event is created by the inventory event creation unit 111. Hereinafter, it is assumed that the request execution button 2630 is pressed on the inventory request screen 2600 by the inventory requester.

[0117] Step 1-21) The inventory support processing unit 101 of the ID inventory support device 10 creates event information representing the inventory event by the inventory event creation unit 111. Here, the event information includes at least an event ID determined by the inventory event creation unit 111, an event name and a response deadline set on the event basic information setting screen, a creator representing the employee number and name of the inventory creator, an ID of the inventory target, and a business system in which the ID is used. In addition, when extraction conditions are used when extracting the ID of the inventory target, the extraction conditions are also included in the event information. Note that the event status included in the event information may be "response received", the response status for each ID of the inventory target may be "not answered", and the responder for each ID of the inventory target may be the employee number and name of the administrator of the business system in which the ID is used.

[0118] Step 1-22) Finally, the inventory support processing unit 101 of the ID inventory support device 10 causes the inventory event management unit 114 to store the event information created in the above step 1-21 in the event information storage unit 106.

[0119] Regarding the screen transition of the screen displayed on the requester terminal 20 described in the above steps 1-1 to 1-22, the order of the target selection screen to the warning screen and the event basic information setting screen is arbitrary. That is, after the event basic information setting screen is displayed, the target selection screen to the warning screen may be displayed.

[0120] In addition, the inventory taker may be able to save the inventory event, for example, during the creation of the inventory event. In this case, event information representing the inventory event being created is created by the inventory event creation unit 111, and the event information is stored in the event information storage unit 106 by the inventory event management unit 114. At this time, "being created" is set in the event status of the event information representing the inventory event being created.

[0121] Step S102: The ID inventory support system 1 requests an inventory count. That is, the ID inventory support processing unit 101 of the ID inventory support device 10 notifies each destination (that is, the administrator of the business system where the ID of the inventory target is used) of the inventory request by the inventory event creation unit 111.

[0122] Step S103: The ID inventory support system 1 answers the questions set for the ID of the inventory target. Here, the answer to the question is performed according to the following procedures 2-1 to 2-5.

[0123] Procedure 2-1) The administrator terminal 20 used by the administrator who has received the inventory request sends a transition request to the answer screen related to this inventory request to the ID inventory support device 10. Note that this transition request includes, for example, the employee number and name of the administrator.

[0124] Procedure 2-2) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the answer screen from the administrator terminal 20, the UI providing unit 113 sends the answer screen to the administrator terminal 20. The answer screen is a screen for the respondent to answer the questions set for the ID of the inventory target.

[0125] Procedure 2-3) The UI processing unit 201 of the administrator terminal 20 displays the answer screen received from the ID inventory support device 10 and accepts various operations on the answer screen.

[0126] Here, an example of the response screen is shown in FIG. 14. The response screen 3100 shown in FIG. 14 includes a response target ID display column 3110, a response button 3120, and a cancel button 3130. Note that the example shown in FIG. 14 shows, as an example, a response screen 3100 for responding to a question regarding whether an ID needs to be continued.

[0127] The response target ID display column 3110 is a UI component in which, among the IDs of the inventory target, the employee number, name, etc. included in the transition request to the response screen are set as the responder's ID and the information related thereto (name, company name, organization name, system name of the business system) are displayed, and the response to that ID can be set. In the example shown in FIG. 14, a response column is associated with the ID of the inventory target, and the responder can select the desired response content from the pull-down list 3111 included in this response column. Note that the example shown in FIG. 14 shows the case where the response format for the question set for the ID of the inventory target is "selection type". For example, when the response format is "description type", for example, an input form in which the responder can input the response content is included in the response column.

[0128] The response button 3120 is a UI component for transmitting the content answered in the response column included in the response target ID display column 3110. On the other hand, the cancel button 3130 is a UI component for canceling the response. Hereinafter, it is assumed that the response button 3120 is pressed after the responder has set a response to the question set for the ID of the inventory target on the response screen 3100.

[0129] Step 2-4) The UI processing unit 201 of the administrator terminal 20 transmits response result information including the ID set with the response and the response content on the response screen displayed in the above step 2-3 to the ID inventory support device 10. Note that, for example, the event ID of the inventory event, the name and employee number of the responder, etc. are also transmitted to the ID inventory support device 10 in the response result information.

[0130] Step 2-5) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives the response result information, the inventory event management unit 114 updates the corresponding event information with the response result information. That is, the inventory event management unit 114 identifies the event information of the event ID included in the response result information among the event information stored in the event information storage unit 106, and then uses the ID, response content, and name or employee number of the respondent included in the response result information to update the response content and respondent corresponding to the ID among the response content and respondent included in the identified event information. At this time, the inventory event management unit 114 updates the response status corresponding to the ID among the response statuses included in the identified event information to "responded".

[0131] Step S104: Finally, when the ID inventory support system 1 completes the inventory event (for example, when responses to questions have been obtained for all IDs to be inventoried), the ID inventory support system 1 outputs a report representing the result of the inventory. That is, the report output unit 102 of the ID inventory support device 10 outputs a report of the event information whose event status is "completed" among the event information stored in the event information storage unit 106 to a predetermined output destination. Here, examples of the predetermined output destination include an auxiliary storage device provided in the ID inventory support device 10, a display, other devices, equipment, terminals, etc. connected via a communication network.

[0132] Although various information can be included in the report, for example, information such as the inventory completion date, the business system and ID to be inventoried, the questions set for each ID and their answers, the inventory requester, the respondent, etc. may be included. However, what information is included in the report may vary depending on, for example, the criteria required in the audit regarding the inventory.

[0133] <Confirmation of Event Status and Response Status> Here, the inventory taker can check the status of the inventory event created by himself / herself and the response status in that inventory event. For example, the status of the inventory event and the response status in the inventory event can be checked according to the following procedures 3-1 to 3-6.

[0134] Procedure 3-1) The UI processing unit 201 of the requester terminal 20 sends a transition request to the ID inventory support device 10 to an event status confirmation screen for checking the status of the inventory event created by itself (the inventory taker). Note that this transition request includes, for example, the employee number, name, etc. of the inventory taker.

[0135] Procedure 3-2) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the event status confirmation screen from the requester terminal 20, it sends the event status confirmation screen to the administrator terminal 20 through the UI providing unit 113. The event status confirmation screen is a screen for checking the status of the inventory event created by the inventory taker.

[0136] Procedure 3-3) The UI processing unit 201 of the requester terminal 20 displays the event status confirmation screen received from the ID inventory support device 10 and accepts various operations on the event status confirmation screen.

[0137] Here, an example of the event status confirmation screen is shown in FIG. 15. The event status confirmation screen 4100 shown in FIG. 15 includes an inventory event list display column 4110.

[0138] The inventory event list display column 4110 is a UI component that displays the event ID, event name, event status, response deadline, progress, creator, etc. of the inventory event represented by the inventory event information in which the employee number, name, etc. included in the transition request to the event status confirmation screen are set as the creator among the inventory events. Note that the progress is information indicating how many questions among the questions set for the ID to be inventoried have been answered.

[0139] Note that the inventory requester may, for example, extend the response deadline or change the event status on the event status confirmation screen 4100. Examples of changing the event status include, for example, changing the event status back to "response accepted" for an event whose status has become "closed".

[0140] Here, for example, the event name of the inventory event displayed in the inventory event list display column 4110 is in link form, and the inventory requester can display the response content confirmation screen for the inventory event with that event name by pressing the event name. In the following, it is assumed that the event name "XX system inventory" has been pressed by the inventory requester.

[0141] Step 3-4) The UI processing unit 201 of the requester terminal 20 sends a transition request to the response content confirmation screen for the inventory event with the event name selected on the event status confirmation screen to the ID inventory support device 10.

[0142] Step 3-5) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the response content confirmation screen from the requester terminal 20, the UI providing unit 113 sends the response content confirmation screen to the administrator terminal 20. The response content confirmation screen is a screen for confirming the detailed response status of the inventory event (response status for each ID to be inventoried).

[0143] Step 3-6) The UI processing unit 201 of the requester terminal 20 displays the response content confirmation screen received from the ID inventory support device 10 and accepts various operations on the response content confirmation screen.

[0144] Here, an example of the response content confirmation screen is shown in FIG. 16. The response content confirmation screen 4200 shown in FIG. 16 includes a response content list display column 4210.

[0145] The response list display column 4210 is a UI component that displays the ID of the inventory count target and the response status for the response set for that ID (whether the response has been made and, if so, the response content). In the example shown in Fig. 16, the ID of the inventory count target and its response status for the inventory count event with the event name "XX System Inventory Count" are displayed. This allows the inventory count requester to check the response status of the inventory count event created by themselves.

[0146] Note that the inventory count requester may be able to edit the response status displayed in the response list display column 4210.

[0147] <Response delegation> Here, the administrator who has received the notice of the inventory count request can delegate the response to the questions that the administrator should answer in that inventory count request to a proxy responder (for example, their subordinate, etc.). For example, the response to the questions can be delegated to the proxy responder according to the following procedures 4-1 to 4-3.

[0148] Procedure 4-1) The UI processing unit 201 of the administrator terminal 20 sends a transition request to the ID inventory count support device 10 to a response delegation screen for delegating the response to the proxy responder. Note that this transition request includes, for example, the event ID of the inventory count event for which the response is to be delegated to the proxy responder, the administrator's employee number, name, etc.

[0149] Step 4-2) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to the answer commission screen from the administrator terminal 20, the UI providing unit 113 transmits the answer commission screen to the administrator terminal 20. At this time, the UI providing unit 113 generates an event URL for transitioning to a Web page where the proxy respondent can answer the question, and then transmits the answer commission screen including this event URL to the administrator terminal 20. By presenting this event URL to the proxy respondent, the proxy respondent can use the proxy respondent terminal 20 to answer the questions set for the IDs to be inventoried even without having an ID inventory account. When an answer to a question is made by the proxy respondent, the same processing as in step S103 above is executed after reading the administrator as the proxy respondent and the administrator terminal 20 as the proxy respondent terminal 20, respectively.

[0150] Here, the UI providing unit 113 may generate an event URL including the output value when the one or more pieces of information are input to a predetermined function (e.g., a hash function, etc.) having a collision difficulty with one or more of the following pieces of information.

[0151] · Event ID · Administrator's ID inventory account · Proxy respondent's email address · Proxy respondent's employee number · Proxy respondent's name · Answer deadline · ID to be inventoried However, the above information is just an example, and various other information can also be used.

[0152] Note that by using the ID of the inventory target when generating the event URL, it becomes possible to control, for example, the ID for entrusting an answer to a proxy respondent. For a specific example, when there are "z001", "z002", and "z003" as the IDs of the inventory target, for proxy respondent A, select the IDs of "z001" and "z002" and entrust the answers to the questions set with the IDs of "z001" and "z002", and for proxy respondent B, select the ID of "z003" and want to entrust the answer to the question set with "z003", when generating the event URL to be presented to proxy respondent A, use "z001" and "z002", while when generating the event URL to be presented to proxy respondent B, use "z003". Thereby, a URL for accessing a web page where answers can be given only to the questions set with "z001" and "z002" is generated as the event URL to be presented to proxy respondent A, and similarly, a URL for accessing a web page where answers can be given only to the question set with "z003" is generated as the event URL to be presented to proxy respondent B.

[0153] Step 4-3) The UI processing unit 201 of the administrator terminal 20 displays the answer entrustment screen received from the ID inventory support device 10 and accepts various operations on the answer entrustment screen.

[0154] Here, an example of the answer entrustment screen is shown in FIG. 17. The answer entrustment screen 5100 shown in FIG. 17 includes an inventory information display column 5110 and a close button 5120.

[0155] The inventory information display column 5110 is a UI component where information related to the inventory event (event name, event ID, target system, conditions, request details, response deadline, requester, etc.) and the event URL are displayed. Also, the inventory information display column 5110 includes a copy button 5111 for copying the event URL to the clipboard. The administrator can, for example, press the copy button 5111 to copy the event URL to the clipboard and then paste this event URL into an email or the like to notify the proxy responder. The close button 5120 is a UI component for closing the response delegation screen 5100.

[0156] <Hardware Configuration Example of the Inventory Support Device 10 and the Terminal 20> The ID inventory support device 10 and the terminal 20 according to this embodiment can be realized, for example, by the hardware configuration of a computer 500 shown in FIG. 18. The computer 500 shown in FIG. 18 includes an input device 501, a display device 502, an external I / F 503, a communication I / F 504, a RAM (Random Access Memory) 505, a ROM (Read Only Memory) 506, an auxiliary storage device 507, and a processor 508. Also, these hardware components are communicably connected to each other via a bus 509.

[0157] The input device 501 is, for example, a keyboard, a mouse, a touch panel, a physical button, etc. The display device 502 is, for example, a display, a display panel, etc. Note that the computer 500 may not have at least one of the input device 501 and the display device 502, for example.

[0158] The external I / F 503 is an interface with an external device such as a recording medium 503a. The computer 500 can read from and write to the recording medium 503a via the external I / F 503. Examples of the recording medium 503a include a flexible disk, a CD (Compact Disc), a DVD (Digital Versatile Disk), an SD memory card (Secure Digital memory card), a USB (Universal Serial Bus) memory card, and the like.

[0159] The communication I / F 504 is an interface for the computer 500 to connect to a communication network or the like. The RAM 505 is a volatile semiconductor memory (storage device) that temporarily holds programs and data. The ROM 506 is a non-volatile semiconductor memory (storage device) that can hold programs and data even when the power is turned off. The auxiliary storage device 507 is a storage device (storage device) such as an HDD, an SSD, or a flash memory, for example. The processor 508 is an arithmetic device such as a CPU or a GPU (Graphics Processing Unit).

[0160] The ID inventory support device 10 and the terminal 20 according to the present embodiment can realize the above-described various processes by having, for example, the hardware configuration of the computer 500 shown in FIG. 18. Note that the hardware configuration of the computer 500 shown in FIG. 18 is an example and is not limited thereto. For example, the computer 500 may have a plurality of auxiliary storage devices 507 and a plurality of processors 508, may not have a part of the illustrated hardware, or may have various hardware other than the illustrated hardware.

[0161] <Modification Example> ·Modification Example 1 In the above embodiment, procedures 1-1 to 1-22 were described as an example of the inventory event creation procedure. However, it is not necessarily required to perform them in this order. Within the range where consistency is maintained, the screen transition may be changed, or the order may be changed according to the user's input or selection.

[0162] ·Modification Example 2 In the above embodiment, the answers to the questions in the inventory event were requested from administrators including the system administrator and the usage administrator. However, the answers may be requested only from the system administrator, or only from the usage administrator. Also, when the proxy respondent appointed by the administrator answers the questions, the proxy respondent may further appoint another person to answer the questions and set up another proxy respondent. Furthermore, the proxy respondent may recursively set up other proxy respondents.

[0163] ·Modification Example 3 When the request details, etc. are notified to the respondent (including proxy respondents), some processing, etc. may be performed based on the content input by the inventory requester, the requester who requested the proxy response, etc. and the preset rules, and then the notification may be made. For example, when the request details, etc. are notified, the notification may be made after modifying the event name by adding the response deadline to the beginning of the event name.

[0164] ·Modification Example 4 In the inventory request screen (Figure 13) and response screen (Figure 14) displayed through preview or the like when creating an inventory event, and in the inventory request screen (Figure 13) and response screen (Figure 14) displayed to the responder, for example, information related to the event such as manuals, help, FAQs, etc. related to the relevant inventory event and content such as videos may be displayed. Further, for example, separate from the answers to the questions in the inventory event, various communication logs such as messages related to the inventory event itself, questions and their answers between the inventory requester and the responder (including proxy responders), and posts for information sharing may be displayed. Also, regarding the display / non-display of these information, content, messages, communication logs, etc. and which ones to display, for example, after the inventory event is created, it may be set and changed by the inventory requester or responder.

[0165] · Modification Example 5 In the response delegation screen (Figure 17), the number of responses and non-responses to the ID numbers subject to inventory, and further the number of responders including the number of responders and proxy responders, and the number of non-responders may be appropriately displayed. Also, the non-responded IDs, responders with non-responses, and responders for whom responses to the ultimately non-responded IDs are requested may be filtered and displayed as appropriate with necessary information.

[0166] Also, for the non-responding responders requested by the inventory requester, responder, or proxy responder, a reminder message for re-requesting a response or urging a response may be sent using the above filtering, search, etc. with specified search conditions.

[0167] · Modification Example 6 In the response screen (Figure 14), when the responder responds, it may be possible to record who responded. For example, when a responder with an account of the ID inventory support device 10 responds, the account name, etc. may be recorded along with the response. On the other hand, for example, when a responder without an account of the ID inventory support device 10 responds, a mail address, name, other identifier, etc. for identifying the responder may be recorded along with the response.

[0168] <Application Example> In the above embodiment, when the inventory event is completed, a report thereof is output. However, for example, when deletion or suspension of the ID is set as an answer to a question set for the ID to be inventoried, the ID may be deleted or suspended. This can be realized, for example, by requesting deletion or suspension of the ID to the business system in which the ID is used.

[0169] <Summary> As described above, in the ID inventory support system 1 according to the present embodiment, when the inventory requester creates an inventory event, the IDs to be inventoried can be easily extracted only by selecting a business system and extraction conditions. In addition, the administrator of the organization in charge of the business system in which the ID is used can be automatically identified, and an inventory request can be notified to this administrator. Therefore, the work cost required for the inventory request work can be significantly reduced.

[0170] The present invention is not limited to the specifically disclosed above embodiments, and various modifications, changes, combinations with known technologies, etc. are possible without departing from the description of the claims.

Explanation of Signs

[0171] 1 ID inventory support system 10 ID inventory support device 20 Terminal 30 Communication network 101 ID inventory support processing unit 102 Report output unit 103 ID management table storage unit 104 Personnel information table storage unit 105 Administrator table storage unit 106 Event information storage unit 111 Inventory event creation unit 112 Target ID extraction unit 113 UI providing unit 114 Inventory event management unit 201 UI processing unit 500 Computer 501 Input device 502 Display device 503 External I / F 503a Recording medium 504 Communication I / F 505 RAM 506 ROM 507 Auxiliary storage device 508 Processor 509 Bus

Claims

1. An ID inventory support system that supports inventory of IDs used in a business system, an extracting unit that extracts a target ID indicating an ID to be a target of the inventory from an ID management table in which the ID and the business system in which the ID is used are stored in association with each other; a question setting unit for setting a question regarding the inventory for the target ID; an inventory request unit that requests an administrator of a business system in which the target ID is used to provide an answer to a question set for the target ID; a providing unit that provides information indicating the answer status to the user who has requested the question; An ID inventory support system having the above configuration.

2. An ID inventory support system that supports inventory of IDs used in a business system, an extracting unit that extracts a target ID indicating an ID to be a target of the inventory from an ID management table in which the ID and the business system in which the ID is used are stored in association with each other; a question setting unit for setting a question regarding the inventory for the target ID; an inventory request unit that requests an administrator of a business system in which the target ID is used to provide an answer to a question set for the target ID; an output unit that outputs information including the target ID, a question set for the target ID, and an answer to the question to a predetermined output destination; An ID inventory support system having the above configuration.

3. The ID inventory support system supports the inventory of IDs used in business systems. an extraction step of extracting a target ID indicating an ID to be the target of the inventory from an ID management table in which the ID and the business system in which the ID is used are stored in association with each other; a question setting step of setting a question regarding the inventory for the target ID; an inventory request procedure for requesting an administrator of a business system in which the target ID is used to provide an answer to a question set for the target ID; a providing step of providing information indicating the status of the answer to the user who requested the question; An ID inventory support method that executes the above.

4. The ID inventory support system supports the inventory of IDs used in business systems. an extraction step of extracting a target ID indicating an ID to be the target of the inventory from an ID management table in which the ID and the business system in which the ID is used are stored in association with each other; a question setting step of setting a question regarding the inventory for the target ID; an inventory request procedure for requesting an administrator of a business system in which the target ID is used to provide an answer to a question set for the target ID; an output step of outputting information including the target ID, a question set for the target ID, and an answer to the question to a predetermined output destination; An ID inventory support method that executes the above.

5. A program for causing a computer to function as the ID inventory support system according to claim 1 or 2.

Images