ID inventory support system, ID inventory support method and program

Abstract

To provide a technology of supporting taking ID inventory.SOLUTION: An ID inventory taking support system according to one aspect of the present disclosure supports taking an inventory of IDs to be used by work systems. The system includes an extraction unit that is configured to extract, from an ID management table in which at least correspondences between the IDs and the work systems to use the IDs are stored, a target ID that indicates an ID to be included in the inventory, an inquiry setting unit that is configured to set, for the target ID, an inquiry concerning the inventory taking, and an inventory taking request unit that is configured to send a request for answering the inquiry set for the target ID, to a manager of the work system to use the target ID.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 technology]

[0002] Generally, companies use various business systems (e.g., personnel systems, sales support systems, development systems, attendance management systems, accounting systems, etc.) Employees of a company can use these business systems by using IDs issued by the departments that manage these business systems.

[0003] The above IDs require proper management and regular inventory in order to prevent unauthorized access to business systems (see, for example, Non-Patent Document 1). Inventory is the process of checking whether IDs are created, changed, and deleted correctly, and whether there is any discrepancy with the actual usage. This type of inventory is also called "ID inventory" or "account inventory." [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] Information Security Management Standards (Ministry of Economy, Trade and Industry Notification No. 37 of 2016), Internet <URL:https: / / www.meti.go.jp / policy / netsecurity / downloadfiles / IS_Management_Standard_H28.pdf> Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the past, when requesting an ID inventory from each department that manages a business system, this was done by email with an attached ID list file created with spreadsheet software such as Microsoft Excel (registered trademark). Therefore, the person requesting the inventory had to, for example, identify the IDs managed by each requested department, and identify the manager and email address of the department, which resulted in a lot of work costs being incurred when requesting an inventory.

[0006] The present disclosure has been made in consideration of the above points, and aims to provide a technology for supporting ID inventory. [Means for solving the problem]

[0007] An ID inventory support system according to one embodiment of the present disclosure is an ID inventory support system that supports the inventory of IDs used in a business system, and includes an extraction unit configured to extract a target ID indicating an ID to be subject to the inventory from an ID management table in which the ID and the business system in which the ID is used are stored in at least correspondence with each other, a question setting unit configured to set a question regarding the inventory for the target ID, and an inventory request unit configured to request an administrator of the business system in which the target ID is used to provide an answer to the question set for the target ID. Effect of the Invention

[0008] A technique is provided to assist with ID inventory. [Brief description of the drawings]

[0009] [Figure 1] 1 is a diagram showing an example of the overall configuration of an ID inventory support system according to an embodiment of the present invention; [Diagram 2] 2 is a diagram illustrating an example of a functional configuration of an ID inventory support device and a terminal according to the present embodiment. FIG. [Diagram 3] FIG. 13 illustrates an example of an ID management table. [Figure 4] FIG. 13 illustrates an example of a personnel information table. [Diagram 5] FIG. 13 illustrates an example of an administrator table. [Figure 6] FIG. 11 is a diagram illustrating an example of event information. [Figure 7] 1 is a flowchart showing an example of the flow of the entire process of the ID inventory support system according to the present embodiment. [Figure 8] FIG. 13 is a diagram illustrating an example of a target selection screen. [Figure 9] FIG. 13 is a diagram showing an example of a target ID list screen. [Figure 10] FIG. 13 illustrates an example of a warning screen. [Figure 11] FIG. 13 illustrates an example of an event basic information setting screen. [Figure 12] FIG. 13 is a diagram showing an example of a question setting screen. [Figure 13] FIG. 13 illustrates an example of an inventory request screen. [Figure 14] FIG. 13 is a diagram showing an example of an answer screen. [Figure 15] FIG. 13 is a diagram showing an example of an event status confirmation screen. [Figure 16] FIG. 13 is a diagram showing an example of an answer content confirmation screen. [Figure 17] FIG. 13 is a diagram showing an example of a reply delegation screen. [Figure 18] FIG. 2 illustrates an example of a hardware configuration of a computer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] An embodiment of the present invention will be described below with reference to an ID inventory support system 1 that supports the inventory of IDs in business systems used in companies.

[0011] <Terminology> Business system: Any computer or computer system used for some business in a company (including computers or computer systems available as cloud services, etc.). Examples of business systems include human resources 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 called an account or user ID, for example. In addition to IDs that are assigned to users of business systems, there are also IDs that are shared by multiple users for the purpose of being used for some business or task (these are also called "shared IDs"). While a normal ID is linked to a specific user, a shared ID is not linked to a specific user, but is linked to, for example, a specific department or organization, the objects to be counted and managed, the purpose of use, the application to be used, etc.

[0013] ID inventory: This is the process of checking whether IDs have been created, changed, or deleted correctly, and whether there is any discrepancy with the actual usage. This type of work is also simply called "inventory." ID inventory is sometimes called account inventory, for example. ID inventory is generally conducted periodically, but can also be conducted irregularly.

[0014] Inventory requester: A person who requests the administrator to take inventory of the ID to be inventoryed. The inventory requester sets questions about the inventory, such as whether the ID should continue to be used or deleted, and asks the administrator for an answer.

[0015] Administrator: This includes the following two types of administrators. The first type of administrator is the person in charge of managing the business system in the department or organization (hereinafter, departments and organizations are collectively referred to as "organizations") (hereinafter, such administrators are also referred to as "system administrators") in the department or organization that has jurisdiction over the business system. For example, if the business system is a personnel system, the organization in charge is the "personnel department," and the system administrator is the person in charge of managing the personnel system in the personnel department. Similarly, if the business system is a sales support system, the organization in charge is the "sales department," and the system administrator is the person in charge of managing the sales support system in the sales department. The second type of administrator is the person in charge of managing IDs (newly adding, updating, deleting IDs, etc.) for each business system so that users who use the business system can use the system appropriately, and supporting the operation of the business system (hereinafter, such administrators are also referred to as "user administrators"). For example, if the business system is a personnel system, an employee in the personnel department may be the user administrator for each organization that uses the personnel system, and an employee in the organization that uses the personnel system may be the user administrator for that organization. Furthermore, in a certain organization, the users of a plurality of business systems (for example, a personnel system and a sales support system) may be different, or the same employee may serve both roles.

[0016] Hereinafter, when we say "business system administrator" or simply "administrator", it may include the two types of administrators mentioned above (system administrator, usage administrator).

[0017] Respondent: A person who answers questions set by the inventory requester. The respondent is basically the manager mentioned above, but may also include a person who is delegated by the manager to answer questions on his / her behalf (hereinafter referred to as a proxy respondent). Proxy respondents typically include subordinates who are ordered to carry out inventory work by the manager, people who assist or act on behalf of the manager in each organization that uses the business system, and even managers of smaller organizations within each organization that uses the business system and people who assist or act on behalf of them in their work.

[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 the corresponding administrator for an answer to the question set in this inventory event. In addition, 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). Also, 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 merely an example and is not limited thereto. For example, in the example shown in FIG. 1, the ID inventory support device 10 is configured by a single device, but it may be configured by a plurality of devices connected to each other via a communication network.

[0022] <Functional Configuration Example of ID Inventory Support Device 10 and 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 processing executed by one or more programs installed in the ID inventory support device 10 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, a manager 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 each 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 (hereinafter referred to as event information) that represents an inventory event in response to a request from the requester terminal 20. The inventory event creation unit 111 also requests an administrator of the business system in which the ID is used to take stock of the ID that is the subject of the inventory in this inventory event.

[0026] When event information is created by the inventory event creation unit 111, the target ID extraction unit 112 extracts IDs to be inventory targets 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 IDs to be inventory targets from the ID management table stored in the ID management table storage unit 103. 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 inventory event creating unit 111 creates event information, the UI providing unit 113 provides various screens to the terminal 20 as a UI (user interface).

[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. Furthermore, 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 manager terminal 20, the proxy respondent terminal 20, etc. 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 indicating the results of the ID inventory to a predetermined output destination.

[0030] <Terminal 20> 2, the terminal 20 according to this embodiment has a UI processing unit 201. The UI processing unit 201 is realized by, for example, processing that one or more programs, such as a Web browser, installed in the terminal 20 executes on a processor, such as a CPU.

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

[0032] <ID management table> An example of an 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 ID of a business system and an object such as a person (employee) or organization linked to that ID, and includes employee information and ID information. The employee information includes, for example, an employee number, name, company name, organization name, etc. The ID information also includes an ID (ID of the business system) linked to 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 employee number "001", name "Tanaka Ichiro", company name "A", and organization name "Personnel Department" as employee information, and also includes personnel system "h001" and attendance management system "a001" as ID information. This indicates that the personnel system ID "h001" and attendance management system ID "a001" are linked to "Tanaka Ichiro" (employee number: 001) who belongs to the personnel department of Company A.

[0034] 3, for example, includes employee number "002", name "Suzuki Jiro", company name "A", and organization name "Sales Department" as employee information, and also includes sales support system "s001" and attendance management system "a002" as ID information. This indicates that the sales support system ID "s001" and attendance management system ID "a002" are linked to "Suzuki Jiro" (employee number: 002) who belongs to the human resources department of Company A.

[0035] On the other hand, for example, the ID management record in the sixth row of the ID management table 1100 shown in Fig. 3 does not include an employee number or name as employee information, but only includes the company name "A" and the organization name "Development Department", and includes the development support system "d900" as ID information. This indicates that the development support system ID "d900" is not linked to a specific employee, but is a shared ID used by employees in the development department.

[0036] In the example shown in Fig. 3, when the employee information does not include an employee number and a name, the ID included in the ID information corresponding to that employee information is treated as a shared ID, but this is just an example and is not limiting. For example, a flag indicating whether or not it is a shared ID may be included in the ID management record, and the flag may indicate whether or not the ID included in the ID information is a shared ID.

[0037] Furthermore, the ID information in the ID management record may include, for each ID, a last use date and time indicating the date and time when the ID was last used.

[0038] <Personnel Information Table> An example of a 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 indicates the organization to which an employee currently belongs (the latest organization) and whether or not the employee has left the company, and includes, for example, an employee number, a name, a company name, an organization name, a retirement flag, and the like. The retirement flag is a flag that indicates whether or not an employee has left the company, and is set to "1" if the employee has left the company, and is otherwise blank. Note that each personnel information record included in the personnel information table is, for example, synchronized with personnel information (the employee's name, the organization to which the employee belongs, whether or not the employee has left the company, 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 "Tanaka Ichiro", company name "A", organization name "Personnel Department", etc. This indicates that "Tanaka Ichiro" (employee number: 001) currently belongs to the Personnel Department of Company A.

[0040] 4 includes employee number "005", name "Saito Aiko", company name "A", organization name "Development Department", etc. This indicates that "Saito Aiko" (employee number: 005) has already left Company A. It also indicates that the organization to which "Saito Aiko" (employee number: 005) belonged at Company A at the time of her retirement 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 yet left the company. For example, the employee information of the ID management record in the fourth row of the ID management table 1100 shown in FIG. 3 includes employee number "004", name "Sato Saburo", company name "A", and organization name "Personnel Department". On the other hand, for example, the personnel information record in the fourth row of the personnel information table 1200 shown in FIG. 4 includes employee number "004", name "Sato Saburo", company name "A", and organization name "Development Department". Therefore, it can be seen that the current organization of "Sato Saburo" (employee number: 004) is "Development Department", but that he belonged to the "Personnel Department" before being transferred to the "Development Department". It can also be seen that the ID "d001" of the development system and the ID "a004" of the attendance management system are still linked to "Sato Saburo" (employee number: 004) when he belonged to the "Personnel Department".

[0042] In this way, while each personnel information record included in the personnel information table indicates the current organization (latest organization) to which an employee belongs or whether the employee has left the company, the organization 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 related to employees who have left the company. For example, "Saito Aiko" (employee number: 005) has left Company A, but the fifth row of the ID management table 1100 shown in Figure 3 contains an ID management record related to "Saito Aiko" (employee number: 005).

[0043] In the example shown in Fig. 4, the personnel information record includes the organization to which the employee currently belongs (the latest organization) and whether the employee has left the organization, but it may also include not only the latest organization but also the history of organizations to which the employee has previously belonged (i.e., transfer history). The personnel information record may also include various information other than the above (e.g., email address, extension number, various flags other than the left flag, etc.). Examples of flags other than the left flag include a flag indicating whether the employee is a seconded employee, a flag indicating whether the employee is an employee who holds concurrent positions in multiple organizations, a flag indicating whether the employee has been transferred from a relevant organization, a flag indicating whether the employee is on leave, and a flag indicating whether the employee is a temporary (non-resident) employee.

[0044] <Administrator Table> An example of an administrator table stored in administrator table storage unit 105 is shown in Fig. 5. Administrator table 1310 shown in Fig. 5(a) is a table made up of one or more records representing system administrators (hereinafter, these records are also referred to as "system administrator records"). On the other hand, administrator table 1320 shown in Fig. 5(b) is a table made up of one or more records representing usage administrators (hereinafter, these records are also referred to as "usage administrator records"). Hereinafter, a table made up of system administrator records will be referred to as the "system administrator table", and a table made up of usage administrator records will be referred to as the "usage administrator table", and when referring to either or both, it will be simply referred to as the "administrator table".

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

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

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

[0048] For example, if a business system under the jurisdiction of an organization does not have a system administrator, a system administrator record containing only the organization name of that organization may be stored in the system administrator table, or a system administrator record related to that organization may not exist in the system administrator table. Also, an organization may be in charge of multiple business systems, and each business system may have a different system administrator. In such cases, the system administrator record may include a "target system" in which the system name, etc. of the business system managed by the system administrator is set.

[0049] On the other hand, as shown in FIG. 5(b), each usage manager record includes, for example, an employee number, a name, a company name, an organization name, a target system, an email address, and the like.

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

[0051] 5(b), the usage manager record in the second row of the usage manager table 1320 includes employee number "236", name "Yamada Satoshi", company name "A", organization name "Development Department", target system "XX System", etc. This indicates that "Yamada Satoshi" (employee number: 236) is the usage manager of the "XX System" in the Development Department of Company A.

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

[0053] Here, it can be seen from the usage manager records in the first and third rows of the usage manager table 1320 shown in Figure 5(b) that the "XX system" is used by both the development department and the general affairs department of Company A, and that the usage manager for the development department is "Yamada Satoshi" (employee number: 236), and the usage manager for the general affairs department is "Suzuki Hanako" (employee number: 022). In this way, usage managers can be different for each organization that uses a business system.

[0054] For example, if there is no usage manager for a business system used by an organization, a usage manager record containing only the organization name of the organization and the system name of the business system may be stored in the usage manager table, or a usage manager record related to the organization and business system may not exist in the usage manager table.

[0055] Event Information An example of event information stored in the event information storage unit 106 is shown in Fig. 6. Event information 1400 shown in Fig. 6 represents an inventory event, and includes, for example, an event ID, an event name, an event status, a creator, a reply deadline, a target system, conditions, a target ID, a reply status, a reply content, a replyer, and the like.

[0056] The event ID is identification information that uniquely identifies the 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 receiving" 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 (i.e., the inventory requester) who created the inventory event. 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 condition is the condition (extraction condition) used when extracting the ID of the inventory target 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 (system administrator, user administrator) of the business system in which 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) In response to an operation to start creating an inventory event by the inventory requester, the UI processing unit 201 of the requester terminal 20 transmits a request to start creating an inventory event to the ID inventory support device 10. An example of an inventory event creation start device is an operation to access a web page for creating an inventory event.

[0060] Step 1-2) The ID inventory support processing unit 101 of the ID inventory 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 an inventory event, and is a screen on which information for extracting IDs to be inventoryed 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 inventory support apparatus 10, and accepts various operations on the target selection screen.

[0062] An example of the target selection screen is shown in Fig. 8. A target selection screen 2100 shown in Fig. 8 includes an extraction target system selection field 2110, an extraction condition selection field 2120, a next button 2130, and a cancel button 2140.

[0063] The extraction target system selection field 2110 is a UI part for selecting a business system from which an ID to be stocked is to be extracted. The extraction target system selection field 2110 includes check boxes 2111. By selecting one or more check boxes 2111, the stocktaking requester can select the business system corresponding to the check box 2111 selected by the requester as a system to be extracted for IDs. In the example shown in FIG. 8, the check box 2111 corresponding to the development support system is selected. The stocktaking requester can also select all business systems by selecting the top check box 2111 among the check boxes 2111. The extraction target system selection field 2110 shown in FIG. 8 also includes a "number of registered IDs" indicating the number of IDs registered in the business system, an "inventory status" indicating the inventory status when the ID of the business system has already been stocked, and an "inventory completion date" indicating the completion date when the inventory has already been completed.

[0064] The extraction condition selection field 2120 is a UI component for selecting conditions (extraction conditions) for extracting the IDs of inventory targets. The extraction condition selection field 2120 includes check boxes 2121. By selecting one or more check boxes 2121, the inventory requester can select the extraction conditions corresponding to the check boxes 2121 selected by the person himself / herself. The example shown in FIG. 8 shows a case where the check box 2121 corresponding to the extraction condition "unused for a long time" is selected. In addition, the inventory requester can also select all extraction conditions by selecting the topmost check box 2121 among the check boxes 2121.

[0065] In the example shown in FIG. 8, the extraction conditions are "unused for a long time", "no administrator specified", "shared ID", and "ID of former employee / ID of transferred employee". "Unused for a long time" is a condition for extracting IDs that have not been used for a predetermined period of time. "No administrator specified" is a condition for extracting IDs of business systems without an administrator, or IDs that are not shared IDs and are not linked to a specific employee (i.e., IDs that are not shared IDs and have no owner), or both of these IDs. "Shared ID" is a condition for extracting shared IDs. "ID of former employee / ID of transferred employee" is a condition for extracting IDs used by former employees, or IDs of employees who have transferred from one organization to another organization and IDs of business systems under the jurisdiction of the previous organization. However, these extraction conditions are merely 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 an inventory event. In the following, it is assumed that the inventory requester selects at least one of the business system (extraction target system) from which the inventory target ID is extracted and the extraction conditions, and then presses the next button 2130.

[0067] Note that, when one business system is selected in the extraction target system selection field 2110, no extraction condition may 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, no business system may be selected in the extraction target system selection field 2110. In other words, it is sufficient that one or more is 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 to the ID inventory support apparatus 10 information related to the extraction target systems and extraction conditions selected in step 1-3 above (hereinafter referred to as extraction target information).

[0069] Step 1-5) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives extraction target information from the requester terminal 20, the target ID extraction unit 112 extracts the ID (and the corresponding employee information) of the inventory target. The target ID extraction unit 112 extracts the ID (and the corresponding employee information) of the inventory target by 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 also extracts the employee information associated with that ID.

[0071] For example, when the ID management table 1100 shown in FIG. 3 is used as the target system, the ID "s001" and its corresponding employee information (employee number "002", name "Suzuki Jiro", company name "A", organization name "Sales Department", etc.) and the ID "s002" and its corresponding employee information (employee number "003", name "Yamada Hanako", 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 references the personnel information table, administrator table, etc. as necessary to extract IDs that satisfy the extraction conditions from the IDs stored in the ID management table, and extracts employee information associated with those IDs. Below, an explanation is given of the extraction method when the extraction conditions are "unused for a long time", "administrator not set", "shared ID", or "retired employee ID / transferred employee ID". Note that if multiple extraction conditions are included in the extraction target information, the extraction methods explained below can be combined.

[0073] When the extraction criteria is "unused for a long time" The ID information in the ID management records that make up the ID management table includes the last usage date and time for each ID. At this time, the target ID extraction unit 112 extracts from the ID management table IDs whose last usage date and time are more than a predetermined period ago, and also extracts employee information associated with those IDs.

[0074] When the extraction conditions are "Administrator not set" When extracting an ID of a business system that does not have an administrator, the target ID extraction unit 112 first refers to the administrator table to identify an organization that does not have an administrator. That is, it identifies an organization that manages a business system that does not have a system administrator, or an organization that uses a business system that does not have a user administrator, or both. Then, the target ID extraction unit 112 extracts employee information including the organization name of the identified organization and the ID of the business system from the ID management table that is associated with the employee information. Note that this is just one example, and in addition to this, for example, if some administrator is linked to an ID, the ID may be extracted individually.

[0075] When extracting an ID that is not a shared ID and is not linked to a specific employee (i.e., 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, an ID for which only the ID exists in the ID management table and no employee information exists (or the employee information is null). Alternatively, for example, if the ID management record contains a flag indicating whether or not it is a shared ID, the target ID extraction unit 112 extracts from the ID management table an ID that is 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 an employee number and a name.

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

[0077] When the extraction condition is "Retired employee ID / Transferred employee ID" When extracting IDs used by former employees, the target ID extraction unit 112 first refers to the personnel information table to identify the employee numbers of employees who have left the company. For example, this can be done by identifying the employee numbers included in personnel information records whose retirement flags are set to "1". The target ID extraction unit 112 then extracts IDs associated with the employee numbers of employees who have left the company from the ID management table.

[0078] When extracting the ID of an individual who has been transferred from one organization to another and the ID of a business system under the jurisdiction of the previous organization, the target ID extraction unit 112 first identifies, for each personnel information record constituting the personnel information table whose retirement flag is not "1," an ID management record that contains the same employee number as that personnel information record and contains a different organization name from that personnel information record.The target ID extraction unit 112 then extracts the employee information contained in the identified ID management record and the ID associated with it from the ID management table.

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

[0080] Step 1-6) The ID inventory support processing unit 101 of the ID inventory support device 10 sends a target ID list screen to the requester terminal 20 via the UI providing unit 113. The target ID list screen is a screen that displays a list of the IDs extracted in step 1-5 above. However, sending the target ID list screen to the requester terminal 20 is not essential, and this step does not have to be executed. Note that if this step is not executed, the following step 1-7 is not executed either.

[0081] Step 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] An example of the target ID list screen is shown in Fig. 9. A target ID list screen 2200 shown in Fig. 9 includes an ID list display field 2210, a next button 2220, and a back button 2230.

[0083] The ID list display field 2210 is a UI widget that displays the IDs extracted in steps 1-5 above (i.e., the IDs of the inventory targets) and the employee information corresponding to them. By referring to the ID list display field 2210, the inventory requester can confirm the IDs extracted as inventory targets and the employee information corresponding to those IDs.

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

[0085] Here, for example, when IDs are extracted using the extraction condition "administrator not set," IDs linked to employees of organizations that do not have administrators or IDs associated with employee information that does not include an organization name may be extracted. When such IDs are extracted, since no administrator to whom the inventory is to be requested is associated with these IDs, the inventory requester can set the administrator (or the organization in which the administrator exists) to whom the inventory is to be requested for these IDs on the target ID list screen 2200.

[0086] In addition, the inventory requester may be able to, for example, select IDs to be excluded from the inventory from among the IDs displayed in the ID list display field 2210 of the target ID list screen 2200, or add IDs to be included in the inventory to the ID list display field 2210.

[0087] Furthermore, the inventory requester may be able to customize the information that the respondent can confirm when answering a question, for example, on the ID list display field 2210 of the target ID list screen 2200. For example, in the example shown in FIG. 9, the employee information includes employee number, name, company name, and organization name, but if the inventory requester and the respondent are in the same company, the company name is considered unnecessary. For this reason, the inventory requester may delete the company name and set the employee information that the respondent can confirm when answering a question to employee number, name, and organization name. Furthermore, the inventory requester may be able to preview the screen that will be displayed when the respondent answers a question.

[0088] Step 1-8) The UI processor 201 of the requester terminal 20 transmits a request for transition to the next screen to the ID inventory support apparatus 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 or not there is an ID that is a warning target among the IDs displayed on the target ID list screen. For example, the UI providing unit 113 may determine whether or not there is an ID that meets a preset warning condition among the IDs displayed on the target ID list screen. Examples of warning conditions include the presence of an ID that is not a shared ID and is not linked to a specific employee (i.e., the presence of an ID that is not a shared ID and has no owner), the presence of an ID of a business system without an administrator, and the like. In the following, it is assumed that it is determined in this step that there is an ID that is a warning target. Note that if it is not determined in this step that there is an ID that is a warning target, the following steps 1-10 to 1-11 are not executed.

[0090] Step 1-10) If it is determined in step 1-9 above that an ID that is to be warned exists, the ID inventory support processing unit 101 of the ID inventory support device 10 transmits a warning screen to the requester terminal 20 via the UI providing unit 113. The warning screen is, for example, a screen that displays a list of IDs that satisfy the warning conditions.

[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. The warning screen is displayed, for example, as a pop-up on the target ID list screen.

[0092] An example of the warning screen is shown in Fig. 10. A warning screen 2300 shown in Fig. 10 includes a first warning ID display field 2310, a second warning ID display field 2320, a next button 2330, and a cancel button 2340.

[0093] The first warning ID display field 2310 is a UI widget that displays a list of IDs that are not shared IDs and are not linked to a specific employee. The second warning ID display field 2320 is a UI widget that displays a list of IDs of business systems for which no administrator exists. The next button 2330 is a UI widget for closing the warning screen and moving to the next screen. On the other hand, the cancel button 2340 is a UI widget for closing the warning screen. In the following, 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 transmits a request for transition to the next screen to the ID inventory support apparatus 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 transmits an event basic information setting screen to the requester terminal 20. The event basic information setting screen is a screen for setting basic information about an event, such as the 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] An example of the event basic information setting screen is shown in Fig. 11. The event basic information setting screen 2400 shown in Fig. 11 includes 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 reply 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 widget that allows the inventory requester to input an arbitrary event name. The event ID display field 2412 is a UI widget that displays an event ID that uniquely identifies an inventory event. The event ID is determined by the inventory event creation unit 111. The target system display field 2413 is a UI widget that displays a business system in which the ID of the inventory target is used (in other words, the business system of the inventory target). The condition display field 2414 is a UI widget that displays the extraction conditions used when extracting the ID of the inventory target. The request content setting field 2415 is a UI widget that allows the inventory requester to input arbitrary request content. The destination display field 2416 is a UI widget that sets the destination of the inventory request. In the example shown in FIG. 11, the destination display field 2416 displays "Administrator 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. The sender display field 2417 is a UI widget that displays the sender when making an inventory request (the sender's email address in the example shown in FIG. 11). The reply destination setting field 2418 is a UI widget that enables the inventory requester to input an arbitrary reply destination for the inventory request (e.g., a reply destination email address, etc.). The reply deadline setting field 2419 is a UI widget that enables the inventory requester to input or select an arbitrary date as the reply deadline. The requester setting field 2420 is a UI widget that enables the inventory requester to input arbitrary information about the requester (e.g., name, extension number, etc.). Note that the reply deadline setting field 2419 may be automatically set to, for example, a date a predetermined period from the present.

[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 the inventory requester inputs necessary information on the event basic information setting screen 2400 and then presses the next button 2430.

[0100] 11 shows a case where the inventory request is notified to the administrator of each organization by email, but this is just one 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 notifying the inventory request on a web page, notifying the inventory request by a messaging application such as business chat, etc.

[0101] Step 1-15) The UI processing unit 201 of the requester terminal 20 transmits a request for transition to the next screen to the ID stocktaking support apparatus 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, the UI providing unit 113 transmits a question setting screen to the requester terminal 20. The question setting screen is a screen for setting questions about inventory for the IDs to be inventoryed.

[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] An example of the question setting screen is shown in Fig. 12. A question setting screen 2500 shown in Fig. 12 includes an add new button 2510, a question setting field 2520, a next button 2530, and a back button 2540.

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

[0106] The question setting field 2520 is a UI widget for setting a question for the ID of the inventory target. When a row is added to the question setting field 2520 by pressing the new add button 2510, a question name indicating the name of the question, a mandatory category indicating whether an answer to the question is mandatory, and an answer format indicating whether a multiple-choice or written answer is required are set for this row, and if the answer format is "multiple-choice", the options are set, thereby setting a question for the ID of the inventory target. The options can be set, for example, by separating them with commas. Note that each row is associated with a UI widget for deleting the row, and the inventory requester can delete the row corresponding to the UI widget from the question setting field 2520 by pressing the UI widget.

[0107] 12, the question name "ID continuation required?", mandatory category "required", answer format "multiple choice", and options "continue, no need" are set in the first line of the question setting field 2520. This represents a question for prompting the respondent to answer whether the ID to be stocked will be continued or not.

[0108] 12, the question name "Planned Deletion Date", the mandatory category "Not Mandatory", and the answer format "Descriptive" are set in the second line of the question setting field 2520. This represents a question for prompting the respondent to provide the planned deletion date of the ID to be stocktaken.

[0109] Needless to say, various questions can be set other than the questions explained in the example shown in Fig. 12. For example, when an ID is to be suspended rather than deleted, a question expressing whether or not to suspend an ID can 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 the inventory requester sets a question for the ID of the inventory target on the question setting screen 2500 and then presses the next button 2530.

[0111] Step 1-18) The UI processing unit 201 of the requester terminal 20 transmits a request for transition to the next screen to the ID inventory support apparatus 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 an inventory of the ID to the administrator of the business system in which the ID to be inventoryed is used.

[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] An example of the inventory request screen is shown in Fig. 13. An inventory request screen 2600 shown in Fig. 13 includes a destination list display field 2610, a request content display field 2620, a request implementation button 2630, and a back button 2640.

[0115] The destination list display field 2610 is a UI widget that displays a list of destinations to which the inventory request is to be notified. The request content display field 2620 is a UI widget that displays the request content set on the event basic information setting screen. In the example shown in Fig. 13, the destination, sender, reply destination, and body of the email are displayed in the request content display field 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 inventory requester presses the request execution button 2630, the inventory event creation unit 111 creates event information representing an inventory event. In the following, it is assumed that the inventory requester presses the request execution button 2630 on the inventory request screen 2600.

[0117] Step 1-21) The ID inventory support processing unit 101 of the ID inventory support device 10 creates event information representing an inventory event by the inventory event creation unit 111. Here, the event information includes at least the event ID determined by the inventory event creation unit 111, the event name and reply deadline set on the event basic information setting screen, the creator indicating the employee number or name etc. of the inventory creator, the ID of the inventory target, and the business system in which the ID is used. Furthermore, if 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 "answering" and the reply status for each ID of the inventory target may be "no reply", and the reply for each ID of the inventory target may be the employee number or name etc. of the administrator of the business system in which the ID is used.

[0118] Step 1-22) Finally, the ID stocktaking support processing unit 101 of the ID stocktaking support apparatus 10 causes the stocktaking 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 screens displayed on the client terminal 20 described in the above steps 1-1 to 1-22, the target selection screen to the warning screen and the event basic information setting screen may be displayed in any order. That is, after the event basic information setting screen is displayed, the target selection screen to the warning screen may be displayed.

[0120] Also, the inventory requester may be able to save an inventory event, for example, in the middle of creating the inventory event. In this case, event information representing the inventory event in the middle of being created is created by the inventory event creating unit 111, and the event information is stored in the event information storage unit 106 by the inventory event managing unit 114. At this time, the event status of the event information representing the inventory event in the middle of being created is set to "under creation".

[0121] Step S102: The ID stocktaking support system 1 requests stocktaking. That is, the ID stocktaking support processing unit 101 of the ID stocktaking support device 10 notifies each destination (i.e., the administrator of the business system in which the ID to be stocktaked is used) of the stocktaking request via the stocktaking event creating unit 111.

[0122] Step S103: The ID inventory support system 1 answers the question set for the ID to be inventoryed. Here, the answer to the question is given according to the following steps 2-1 to 2-5.

[0123] Step 2-1) The manager terminal 20 used by the manager who has been notified of the stocktaking request transmits a transition request to a response screen regarding the stocktaking request to the ID stocktaking support device 10. This transition request includes, for example, the employee number and name of the manager.

[0124] Step 2-2) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to an answer screen from the manager terminal 20, the UI providing unit 113 transmits the answer screen to the manager terminal 20. The answer screen is a screen for an answerer to answer the question set for the ID to be inventoryed.

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

[0126] An example of the answer screen is shown in Fig. 14. The answer screen 3100 shown in Fig. 14 includes an answer target ID display field 3110, an answer button 3120, and a cancel button 3130. Note that the example shown in Fig. 14 shows, as an example, the answer screen 3100 for answering a question about whether or not to continue the ID.

[0127] The answer target ID display field 3110 is a UI widget that displays IDs of inventory targets for which the employee number or name included in the transition request to the answer screen is set as an answerer and related information (name, company name, organization name, system name of the business system) and allows an answer to be set for the ID. In the example shown in FIG. 14, an answer field is associated with the ID of the inventory target, and the answerer can select a desired answer from a pull-down list 3111 included in this answer field. Note that the example shown in FIG. 14 shows a case where the answer format for the answer to the question set for the ID of the inventory target is "multiple choice", and if the answer format is "description", for example, an input form in which the answerer can input the answer is included in the answer field.

[0128] The answer button 3120 is a UI component for sending the answer entered in the answer field included in the answer target ID display field 3110. On the other hand, the cancel button 3130 is a UI component for canceling the answer. In the following, it is assumed that the answerer sets an answer to the question set for the inventory target ID on the answer screen 3100, and then presses the answer button 3120.

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

[0130] Step 2-5) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives the answer result information, the inventory event management unit 114 updates the corresponding event information with the answer result information. That is, the inventory event management unit 114 identifies the event information of the event ID included in the answer result information from among the event information stored in the event information storage unit 106, and then updates the answer content and answerer corresponding to the ID among the answer content and answerer included in the identified event information using the ID, answer content, and the answerer's name, employee number, etc. included in the answer result information. Also, at this time, the inventory event management unit 114 updates the answer status corresponding to the ID among the answer statuses included in the identified event information to "answered".

[0131] Step S104: Finally, when the inventory event is completed (for example, when answers to questions have been obtained for all IDs to be inventoryed), the ID inventory support system 1 outputs a report showing the results of the inventory. That is, the report output unit 102 of the ID inventory support device 10 outputs a report of 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 and a display provided in the ID inventory support device 10, and other devices, equipment, and terminals connected via a communication network.

[0132] The report can include various information, such as the inventory completion date, the business system and ID of the inventory target, the questions and answers set for each ID, the inventory requester, the respondent, etc. However, the type of information included in the report can vary depending on, for example, the standards required for an inventory audit.

[0133] <Checking event status and response status> Here, the inventory requester can check the status of the inventory event he / she created and the response status for the inventory event. For example, the inventory requester can check the status of the inventory event and the response status for the inventory event by following the steps 3-1 to 3-6 below.

[0134] Step 3-1) The UI processing unit 201 of the requester terminal 20 transmits a transition request to the ID inventory support device 10 to switch to an event status confirmation screen for checking the status of the inventory event created by the requester (inventory requester). This transition request includes, for example, the employee number and name of the inventory requester.

[0135] Step 3-2) When the ID stocktaking support processing unit 101 of the ID stocktaking support device 10 receives a transition request to an event status confirmation screen from the requester terminal 20, the UI providing unit 113 transmits the event status confirmation screen to the manager terminal 20. The event status confirmation screen is a screen for confirming the status of the stocktaking event created by the stocktaking requester.

[0136] Step 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] An example of the event status confirmation screen is shown in Fig. 15. An event status confirmation screen 4100 shown in Fig. 15 includes an inventory event list display field 4110.

[0138] The inventory event list display field 4110 is a UI widget that displays the event ID, event name, event status, response deadline, progress, creator, etc. of the inventory event represented by the event information for which the employee number or name, etc. included in the transition request to the event status confirmation screen is set as the creator. Note that progress is information that indicates how many questions have been answered out of the questions set for the inventory target ID.

[0139] The inventory requester may, for example, extend the reply deadline or change the event status on the event status confirmation screen 4100. An example of a case where the event status is changed is when the event status of an event that has become "closed" is changed back to "accepting reply."

[0140] Here, for example, the event names of the inventory events displayed in the inventory event list display field 4110 are in the form of links, and the inventory requester can display a response content confirmation screen for the inventory event of that event name by pressing the event name. In the following, it is assumed that the inventory requester has pressed the event name "XX system inventory."

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

[0142] Step 3-5) When the ID inventory support processing unit 101 of the ID inventory support device 10 receives a transition request to a response content confirmation screen from the requester terminal 20, the UI providing unit 113 transmits the response content confirmation screen to the manager 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 inventoryed).

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

[0144] An example of the answer confirmation screen is shown in Fig. 16. An answer confirmation screen 4200 shown in Fig. 16 includes an answer list display field 4210.

[0145] The response content list display field 4210 is a UI widget that displays the ID of the inventory target and the response status for the response set for that ID (whether or not an answer has been given, and if so, the content of the answer). In the example shown in Fig. 16, the ID of the inventory target related to the inventory event with the event name "XX System Inventory" and the response status are displayed. This allows the inventory requester to check the response status of the inventory event that he or she created.

[0146] The inventory requester may be able to edit the response status displayed in the response content list display field 4210 .

[0147] <Reply delegation> Here, the manager who has received the inventory request can delegate the answering of the questions that he / she should answer in the inventory request to a proxy answerer (for example, his / her subordinate, etc.). For example, the answering of the questions can be delegated to a proxy answerer by following the steps 4-1 to 4-3 below.

[0148] Step 4-1) The UI processing unit 201 of the administrator terminal 20 transmits a transition request to the answer delegation screen for delegating an answer to a proxy answerer to the ID inventory support device 10. Note that this transition request includes, for example, the event ID of the inventory event for which the answer is to be delegated to the proxy answerer, the employee's own 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 an answer delegation screen from the manager terminal 20, the UI providing unit 113 transmits the answer delegation screen to the manager terminal 20. At this time, the UI providing unit 113 generates an event URL for transition to a web page where the proxy answerer can answer the question, and transmits the answer delegation screen including this event URL to the manager terminal 20. By presenting this event URL to the proxy answerer, the proxy answerer can use the proxy answerer terminal 20 to answer questions set for the ID to be inventoryed, even if he or she does not have an ID inventory account. Note that when a question is answered by a proxy answerer, the same process as in step S103 above is executed with the manager replaced with the proxy answerer and the manager terminal 20 replaced with the proxy answerer terminal 20.

[0150] Here, the UI providing unit 113 may use, for example, one or more of the following information and a predetermined collision-resistant function (e.g., a hash function, etc.) to generate an event URL that includes an output value when the one or more pieces of information are input to the function:

[0151] Event ID Administrator ID inventory account Email address of proxy respondent Employee number of the proxy respondent Name of proxy respondent Deadline for responses -ID of the inventory target However, the above information is merely an example, and various other information can be used.

[0152] In addition, by using the ID of the inventory target when generating the event URL, it becomes possible to control the ID to be delegated to the proxy answerer, for example. For example, if there are IDs "z001", "z002", and "z003" as inventory targets, and you want to select IDs "z001" and "z002" for proxy answerer A to delegate the answer to the question set in IDs "z001" and "z002" and select ID "z003" for proxy answerer B to delegate the answer to the question set in "z003", you can use "z001" and "z002" to generate the event URL to be presented to proxy answerer A, and use "z003" to generate the event URL to be presented to proxy answerer B. This generates a URL to access a web page where only the questions set in "z001" and "z002" can be answered as the event URL to be presented to proxy respondent A, and similarly, a URL to access a web page where only the question set in "z003" can be answered as the event URL to be presented to proxy respondent B is generated.

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

[0154] An example of the reply delegation screen is shown in Fig. 17. The reply delegation screen 5100 shown in Fig. 17 includes an inventory information display field 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, or the like. The display device 502 is, for example, a display, a display panel, or the like. 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 and write data from and 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), a SD memory card (Secure Digital memory card), and a USB (Universal Serial Bus) memory card.

[0159] The communication I / F 504 is an interface for connecting the computer 500 to a communication network or the like. The RAM 505 is a volatile semiconductor memory (storage device) that temporarily stores programs and data. The ROM 506 is a non-volatile semiconductor memory (storage device) that can store 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, SSD, or flash memory. 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 this embodiment can realize the various processes described above by having, for example, the hardware configuration of a computer 500 shown in Fig. 18. Note that the hardware configuration of the computer 500 shown in Fig. 18 is merely an example and is not limited thereto. For example, the computer 500 may have multiple auxiliary storage devices 507 and multiple processors 508, may not have some of the hardware shown in the figure, or may have various hardware other than the hardware shown in the figure.

[0161] <Modification> Variation 1 In the above embodiment, steps 1-1 to 1-22 have been described as an example of a procedure for creating an inventory event, but the steps do not necessarily have to be performed in this order. As long as consistency is maintained, the screen transitions may be changed or the order may be changed according to user input or selection.

[0162] Variation 2 In the above embodiment, the administrators, including the system administrator and the usage administrator, are requested to answer questions in the inventory event, but the system administrator alone may be requested to answer, or the usage administrator alone may be requested to answer. Also, a proxy answerer who has been delegated by the administrator to answer a question may be able to further delegate the answer to another person and set a proxy answerer, and the proxy answerer may further recursively set other proxy answers.

[0163] Variation 3 When the request contents, etc. are notified to the respondent (including the proxy respondent), some processing may be performed based on the contents entered by the inventory requester or the requester who requested the proxy reply and on preset rules before the notification is made. For example, when the request contents, etc. are notified, the reply deadline may be added to the beginning of the event name, before the notification is made.

[0164] Variation 4 In the inventory request screen (FIG. 13) and the answer screen (FIG. 14) displayed by preview when creating an inventory event, and in the inventory request screen (FIG. 13) and the answer screen (FIG. 14) displayed to the respondent, for example, content such as information about the event, such as manuals, help, FAQs, etc., related to the related inventory event, and videos, etc. may be displayed. Furthermore, for example, in addition to answers to questions in the inventory event, various communication logs such as messages about the inventory event itself, questions and answers between the inventory requester and the respondent (including proxy responders), posts for sharing information, etc. may be displayed. In addition, the display / non-display of this information, content, messages, communication logs, etc., and which ones to display, etc. may be set or changed by the inventory requester or the respondent, for example, after the inventory event is created.

[0165] Variation 5 The answer delegation screen (Fig. 17) may be configured to appropriately display the number of answers and the number of unanswered answers for the number of IDs to be stocked, as well as the number of respondents, the number of respondents including proxy respondents, the number of unanswered answers, etc. Also, it may be configured to appropriately filter and display unanswered IDs, respondents with unanswered answers, and respondents who are ultimately required to answer unanswered IDs, etc., using necessary information.

[0166] In addition, it may be possible to send reminder messages to respondents who have not yet responded to requests by the inventory requester, respondent, or proxy respondent, requesting them to respond again or urging them to respond, using the above-mentioned filtering or searches specifying search conditions.

[0167] Variation 6 On the answer screen (FIG. 14), when an answerer answers, it may be possible to record who has answered. For example, when an answerer who has an account on the ID inventory support device 10 answers, it may be possible to record the account name, etc. together with the answer. On the other hand, for example, when an answerer who does not have an account on the ID inventory support device 10 answers, it may be possible to record an email address, name, other identifier, etc. for identifying the answerer together with the answer.

[0168] <Application Examples> In the above embodiment, when an inventory event is completed, a report on the completion of the inventory event is output, but for example, when the deletion or suspension of an ID is set as a response to a question set for the ID of an inventory target, the ID may be deleted or suspended. This can be realized, for example, by requesting the 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 this embodiment, when an inventory requester creates an inventory event, the IDs to be inventoryed can be easily extracted simply by selecting the business system and extraction conditions. In addition, the administrator of the organization in charge of the business system in which the ID is used is automatically identified, and the inventory request can be notified to this administrator. This makes it possible to significantly reduce the work costs required for inventory request work.

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

[0171] 1 ID inventory support system 10 ID inventory support device 20 Terminals 30 Communication Network 101 ID inventory support processing unit 102 Report output section 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 Department 112 Target ID Extraction Unit 113 UI provision department 114 Inventory Event Management Department 201 UI processing section 500 Computers 501 Input Device 502 Display device 503 External I / F 503a Recording media 504 Communication I / F 505 RAM 506 ROM 507 Auxiliary storage 508 Processor 509 Bus

Claims

1. An ID inventory support system that supports inventory of IDs used in a business system, an extracting unit configured to extract 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 configured to set a question regarding the inventory for the target ID; an inventory request unit configured to request 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 ID inventory support system having the above structure.

2. The extraction unit is 2. The ID inventory support system according to claim 1, further comprising: extracting, from among the IDs stored in the ID management table, an ID that satisfies a condition selected by a user as the target ID.

3. The condition is It is an ID used in a specific business system. The ID must not have been used for a specified period of time. The ID is used for a business system that does not have an administrator. It is not a shared ID used by multiple people and is an ID without an owner. It is a shared ID that is used by multiple people. It is the ID used by the former employee. The ID must be an ID of a person who has been transferred from one organization to another, and must be used in the business system under the jurisdiction of the organization prior to the transfer. The ID inventory support system according to claim 2, wherein the ID inventory support system is at least one of the above.

4. The ID inventory support system according to claim 1 , further comprising a generating unit configured to generate address information for delegating the reply from the administrator to another person.

5. The generation unit is The ID inventory support system of claim 4, configured to generate the address information using at least one of the identification information identifying the inventory, the administrator's account information, the other person's email address, the identification information identifying the other person, the other person's name, the deadline for answering the question, and the target ID, and a predetermined function that is resistant to collisions.

6. An ID inventory support system that supports inventory of IDs used in a business system, a first screen providing unit configured to provide a first screen on which conditions for extracting the IDs to be the targets of the inventory can be specified; a second screen providing unit configured to provide a second screen on which a question regarding the inventory can be set for the ID to be the target of the inventory; a third screen providing unit configured to provide a third screen for requesting an administrator of a business system in which the ID is used to provide an answer to a question set for the ID to be the subject of the inventory; An ID inventory support system having the above structure.

7. The ID inventory support system of claim 6, further comprising a fourth screen providing unit configured to provide a fourth screen indicating that an ID that satisfies a specified warning condition exists among the IDs being inventoryed.

8. 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 ID inventory support method that executes the above.

9. For ID inventory support systems that support 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 program that executes the following.

Images