JP7120875B2 - Management device, management method and program - Google Patents

Description

Article 30, Paragraph 2 of the Patent Act applies Published on October 3, 2018 at the press club of the Ministry of Internal Affairs and Communications and the NTT Corporate Newsroom

The present invention relates to a management device, management method and program.

Companies use various business systems such as core systems, accounting systems, and document management systems. Persons in charge of various operations (including full-time employees, contract employees, temporary employees, part-time workers, part-time employees of the company, employees of cooperating companies, etc.), etc., shall provide the departments that manage these business systems and the relevant business systems. The business system can be used using an ID issued by a vendor (for example, a vendor that provides the business system as a cloud service). In addition, hereinafter, the ID for using the business system is also referred to as "user ID".

By the way, there is a demand for appropriate management of user IDs from the viewpoint of preventing unauthorized use of user IDs. For this reason, companies generally take inventory of user IDs on a regular basis. In inventory, for example, using attribute information such as the employee number, name, gender, and email address of the person in charge (hereinafter also referred to as “user”) who uses the business system, the user and the usage issued to this user Correlation with the person ID is performed. Then, for a user ID that has not been associated with a user, for example, a user ID deletion request or the like is made. Correlating users and user IDs in this manner is also referred to as “user ID identification”.

On the other hand, there is known a technique of performing user ID identification using a table in which predetermined rules or conditions are defined (see, for example, Patent Document 1).

JP-A-63-282838

Here, as described above, users who use the business system may be not only full-time employees of the company, but also contract employees, temporary employees, part-time workers, employees of cooperating companies, and the like. If you are a regular employee or contract employee (hereinafter referred to as "regular employee, etc.") of the company, user information such as employee information is often managed by a personnel system, etc., so user ID However, in the case of temporary employees, part-time workers, employees of cooperating companies, etc. (hereinafter referred to as "collaborators"), it may be difficult to perform name identification of user IDs. be. This is because the user information of collaborators may be managed in electronic files, paper ledgers, or the like (hereinafter referred to as "collaborator management book") different from the personnel system or the like. User information includes user attribute information such as name, gender, and email address. Attribute information includes, for example, an employee number when the user information is employee information, in addition to the name and gender.

In addition, the above collaborator management book may be managed, for example, by each department of the company, and the identification information (key information) that uniquely identifies the user information of the collaborators differs for each department. Sometimes. For this reason, for example, when the same collaborator is performing work in multiple departments, the user information of the collaborator is associated with each other on the cooperator management list managed by each of these multiple departments. Sometimes it was difficult. Therefore, although the user is the same user, the user may be treated as a different user, and user ID identification may not be performed appropriately. Henceforth, among the user information of a user including a full-time employee etc. and a collaborator, matching the user information of the same user is also called "user information name collation."

The embodiment of the present invention has been made in view of the above points, and aims to perform name identification of user information.

In order to achieve the above object, according to the embodiment of the present invention, source information data including one or more pieces of user information is input, and for each source indicating the input source of the source information data, a first creation means for creating source control information data composed of source control information including said user information using each user information; a second creation means for creating master user information data composed of master user information to which a user key, which is identification information for uniformly identifying a user, and source identification information for identifying the source, is added; addition means for adding a user key included in the master user information to source management information corresponding to the master user information; and master user information indicating the same user exists in the master user information included in the master user information data. merging means for merging a plurality of pieces of master user information indicating the same user into one piece of master user information; each user key included in the plurality of pieces of master user information indicating the same user; and the plurality of pieces of master user information. updating means for updating remaining user keys other than a predetermined one user key to the one user key for each user key included in a plurality of source management information, each of which is the same user key. and

Name identification of user information can be performed.

It is a figure showing an example of the whole composition of a user information management system concerning this embodiment. FIG. 4 is a diagram (part 1) for explaining an example of a flow from input of source information data to reflection in master user information data; FIG. 10 is a diagram (part 1) for explaining an example of the flow of reflection to ID possession information data; FIG. 10 is a diagram (part 2) for explaining an example of a flow from input of source information data to reflection in master user information data; FIG. 12 is a diagram (part 2) for explaining an example of the flow of reflection to ID possession information data; FIG. 4 is a diagram for explaining an example of the flow of merging master user information in master user information data; FIG. 10 is a diagram (part 1) for explaining an example of a flow from input of updated source information data to reflection in master user information data; FIG. 11 is a diagram (part 2) for explaining an example of a flow from input of updated source information data to reflection in master user information data; FIG. 10 is a diagram for explaining an example of the flow of correction when source management information data and master user information data are inconsistent; FIG. 10 is a diagram for explaining an example of the flow when source management information is added individually;

Hereinafter, embodiments of the present invention (hereinafter referred to as "present embodiments") will be described with reference to the drawings. In this embodiment, systems and devices that manage user information, such as personnel systems and collaborators management records, electronic files, ledgers, etc., are referred to as "sources", and name identification of user information recorded in multiple different sources. A user information management system 1 capable of performing

As a specific example of the source, as described above, for example, the personnel system that manages user information (employee information, etc.) of regular employees, etc., and the user information of collaborators who perform work under the jurisdiction of a certain department A terminal such as a PC that stores a collaborator management record recorded in an electronic file or paper, or a collaborator management record that is an electronic file (or that can access the collaborator management record). When the collaborators management book is an electronic file, the collaborators management book is often implemented using, for example, Microsoft (registered trademark) Excel (registered trademark), Microsoft Access, or the like.

Hereinafter, it is assumed that the cooperator management list is stored in a terminal such as a PC (or stored in a storage device or the like accessible by the terminal) in the form of an electronic file. If the collaborators management book is a paper ledger or the like, it may be stored in a terminal such as a PC (personal computer) after the ledger is recorded in an electronic file by, for example, a department ledger manager.

In addition, full-time employees are given identification information such as an employee number (key information. Since this key is the key of user information managed by the source, it is hereinafter also referred to as a “source key”). , for example, a person whose user information is managed by a personnel system or the like (for example, a regular employee, a contract employee, etc.). On the other hand, collaborators are those whose user information is managed, for example, in a collaborator management book for each department, and who are other than full-time employees and who perform some kind of work at the company (for example, temporary employees, part-timers, part-time workers , employees of cooperating companies, etc.).

Here, since the collaborator management book is managed for each department (or for each section, for each group, or for each team, etc.), the source key of the user information may be different for each department. There is For example, a department A may use "mail address" as a source key for user information, and another department B may use "name" as a source key for user information. Further, for example, another department C may use a plurality of items such as "name"+"department name" as key information of user information.

<Overall Configuration of User Information Management System 1>
First, the overall configuration of a user information management system 1 according to this embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of the overall configuration of a user information management system 1 according to this embodiment.

As shown in FIG. 1, the user information management system 1 according to the present embodiment includes a user information management device 10, one or more personnel systems 20, one or more terminals 30, and one or more business systems 40. included. The user information management device 10, the personnel system 20, and the terminal 30 are communicably connected via a network. Also, the user information management device 10 and the business system 40 are communicably connected via a network.

The personnel system 20 is an example of a source and manages employee information, which is an example of user information. User information (employee information) includes, for example, an employee number as a source key for the user information. User information (employee information) includes, for example, name and gender. In addition to these, the user information (employee information) may include various types of attribute information such as department, e-mail address, telephone number (extension number or outside number), name in kana characters, and the like.

Note that the user information management system 1 may include a plurality of personnel systems 20 . For example, if a company consists of a parent company and a subsidiary company, and each company uses a different personnel system 20, the user information management system 1 includes the personnel system 20 used by the parent company and the personnel system 20 used by the subsidiary company. A personnel system 20 may also be included. In this case, the personnel system 20 used by the parent company and the personnel system 20 used by the subsidiaries are different sources.

The terminal 30 is a PC or the like that stores a collaborator management record, which is an example of a source (or can access the collaborator management record). In the cooperator management book, user information of cooperators is managed. Collaborator user information includes, for example, source keys explicitly or implicitly determined by a department or the like that manages the collaborator management record. Such a source key may be, for example, "name", "e-mail address", extension number, or a number uniquely assigned by the relevant department or the like. Note that the terminal 30 is not limited to a PC, and may be, for example, a tablet terminal, a smart phone, or the like.

Here, when the cooperator management book is managed for each department, for example, a cooperator management book managed by department A, a cooperator management book managed by department B, etc., a plurality of cooperator management books exists. In this case, for each department, there is a terminal 30 that stores a cooperator management record managed by the department (or that can access the cooperator management record).

The personnel system 20 according to this embodiment transmits CSV (Comma-Separated Values) data of each user information (employee information) managed by the personnel system 20 to the user information management device 10 as source information data. Also, the terminal 30 according to the present embodiment transmits CSV data of each user information managed in the collaborator management book to the user information management device 10 as source information data. Here, the CSV data of each user information means data items included in the user information (for example, each attribute information item such as "name", "email address", "department") for each user information. The data is in comma separated format. Each piece of source information that constitutes the source information data corresponds to user information managed by the personnel system 20 or user information managed by the cooperator management book.

However, source information data is not limited to CSV data, and may be in any data format (for example, TSV (Tab Separated Values) data of each user information, etc.).

The business system 40 is, for example, a core system, an accounting system, a document management system, etc., and is used by a user using a user ID. The business system 40 may be installed as an on-premises system of the company, or may be realized by a cloud service provided by an external company or the like. Although one business system 40 is illustrated in FIG. 1 for the sake of convenience, a plurality of business systems 40 are generally included in the user information management system 1 .

The business system 40 manages user IDs used to use the business system 40, and is composed of information including each of these user IDs (hereinafter, this information is also referred to as "ID management information"). The received ID management information data is transmitted to the user information management device 10 . The ID management information constituting the ID management information data includes a system ID for identifying the business system 40, a user ID for using the business system 40, and attribute information of the user to whom the user ID is assigned. and are included.

The user information management device 10 receives the source information data of each source and creates source management information data for managing the source information data on the user information management device 10 for each source. Then, the user information management device 10 creates master user information data used for identification of user IDs from source management information data of each source.

In addition, the user information management device 10 identifies the master user information of the same user on the master user information data, merges the master user information of the same user, and combines the source information and the master user information included in the source information data. Update the correspondence of . As a result, user information recorded in a plurality of different sources is collated. By performing user information name identification, the user information of the same user that is distributed and managed by multiple sources is associated, so that it is possible to perform name identification of user IDs across multiple sources. become.

Here, the user information management device 10 according to this embodiment has a user information management processing section 101 as a functional section. The user information management processing unit 101 is implemented by processing that one or more programs installed in the user information management apparatus 10 cause a CPU (Central Processing Unit) or the like to execute.

Further, the user information management device 10 according to the present embodiment includes, as storage units, source management information data storage unit 102, master user information data storage unit 103, ID management information data storage unit 104, and ID ownership information data storage. 105. Each of these storage units can be implemented using, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive). Note that at least one of these storage units may be implemented using a storage device or the like connected to the user information management device 10 via a network.

The source management information data storage unit 102 stores source management information data for each source. The master user information data storage unit 103 stores master user information data. The ID management information data storage unit 104 stores ID management information data. The ID ownership information data storage unit 105 stores ID ownership information data. The ID ownership information data is ID ownership information indicating the correspondence between the master user information and the ID management information (that is, the ID ownership information is information indicating which user owns which user ID). It is data composed by

The user information management processing unit 101 performs processing for realizing name identification of user information and identification of user IDs. Here, the user information management processing unit 101 includes an input unit 111, a source management information data creation unit 112, a master user information data creation unit 113, a matching unit 114, an ID possession information data creation unit 115, a UI Provider 116 is included.

The input unit 111 inputs source information data transmitted from the personnel system 20 or the terminal 30 . Here, each source information constituting the source information data includes a source key of the source information (user information) and attribute information of the source information. From the personnel system 20, for example, source information data is transmitted to the user information management device 10 at predetermined time intervals, predetermined timing, or the like. On the other hand, source information data is transmitted from the terminal 30 to the user information management device 10 by operating the terminal 30, for example.

When the input unit 111 inputs the source information data, the source control information data creation unit 112 creates or updates the source control information that constitutes the source control information data for each source. Each withholding control information that makes up the withholding control information data has a key (hereinafter referred to as , “user key”). However, the user key is set to blank (or NULL value) when source management information is created. The source control information user key is updated. Here, each source management information constituting the source management information data includes a source key, attribute information, and a user key.

The master user information data creating unit 113 creates or updates master user information constituting the master user information data using source management information data stored in the source management information data storage unit 102 . When creating master user information, master user information data creation unit 113 creates a user key and then creates master user information including the user key.

Also, the master user information data creating unit 113 merges the master user information of the same user based on the result of matching by the matching unit 114 .

A user key is included in each piece of master user information that constitutes the master user information data, and this user key is associated with source management information and ID ownership information. As a result, source management information of the same user from different sources is associated via the user key, and source management information and ID possession information are associated via the user key. Here, the master user information includes a user key, a source name of source control information that is the basis of the master user information, a source key of the source control information, and attribute information of the source control information. .

The matching unit 114 matches attribute information included in a plurality of pieces of master user information under a predetermined condition. Thereby, when a predetermined condition is satisfied, the master user information of the same user is specified from among a plurality of pieces of master user information.

Also, the matching unit 114 matches the attribute information included in the master user information and the attribute information included in the ID management information under a predetermined condition. As a result, when a predetermined condition is satisfied, ID ownership information corresponding to the ID management information is created, and the master user information and the ID ownership information are associated.

The ID ownership information data creating unit 115 creates or updates ID ownership information constituting the ID ownership information data according to the matching result of the matching unit 114 .

The UI providing unit 116 provides the terminal 30 with a predetermined UI (user interface) screen. As such a UI screen, for example, the input unit 111 inputs updated source information data, and a new source key (that is, stored in the source management information data storage unit 102) is added to the updated source information data. A UI screen or the like for inquiring of the operator of the terminal 30 how to handle the source information of the new source key when a source key that is not included in each source management information included in the source key is included.

Note that the configuration of the user information management system 1 shown in FIG. 1 is an example, and other configurations may be used. For example, in the example shown in FIG. 1, the user information management device 10 is composed of one device (computer), but the user information management device 10 may be composed of a plurality of devices (computers).

<Example>
Hereinafter, as an example, there are two sources, "Source 1" and "Source 2", and source information data is input from these two sources. will be described.

<<Reflection from input of source information data of source 1 to master user information data>>
First, when source information data of source 1 is input for the first time, the flow from input to reflection in master user information data (that is, creation of master user information) will be described with reference to FIG. FIG. 2 is a diagram (part 1) for explaining an example of the flow from input of source information data to reflection in master user information data.

S11-1) The input unit 111 inputs the source information data transmitted from the source 1 (for example, the personnel system 20, the terminal 30, etc. Hereinafter, the source 1 is the terminal 30 of the department A). Here, as an example, the source information data of the source 1 is composed of five source information, the attribute information of the source key "1" is "A", the attribute information of the source key "2" is "B", Assume that the attribute information of the source key "3" is "C", the attribute information of the source key "4" is "D", and the attribute information of the source key "5" is "E".

For the sake of convenience, source keys are expressed as "1" to "5", but source keys may be arbitrary information or a combination of arbitrary information. For example, as described above, information such as "email address" or "name" may be used as the source key, or a combination thereof (for example, "email address" + "name") may be used. . Similarly, for the sake of convenience, the attribute information is expressed as "A" to "E", but the attribute information can be any one or more pieces of information (for example, "name", "e-mail address", "department", "kana name"). ", "telephone number", etc.).

S12-1) Next, the source management information data creating section 112 creates each source management information from each source information constituting the source information data of the source 1, respectively. At this time, as described above, a blank (or NULL value) or the like is set as a user key in each source management information. Note that the user key itself does not have to be set in each source management information.

The source management information data creating section 112 stores the source management information data composed of these source management information in the source management information data storage section 102 as source 1 source management information data.

While the attribute information of the source management information is composed of uniform items among the sources, the attribute information of the source information may be composed of different items for each source. For example, the attribute information of source information of source 1 consists of "name" and "email address", while the attribute information of source information of source 2 consists of "surname", "first name" and "email address". and so on. In this case, when creating source management information from source information, the source control information data creation unit 112 converts each item included in the source information attribute information of the source into may be mapped to a predetermined item included in . As a result, for example, the attribute information "name" of the source information of source 1 and the attribute information "surname" and "name" of the source information of source 2 can be mapped to the same item of the attribute information of the source management information. become able to.

S13-1) Next, the master user information data creating section 113 creates master user information from each source management information of the source 1 source management information data stored in the source management information data storage section . That is, the master user information data creation unit 113 generates a user key for each source management information, and then generates a master user key containing this user key, the source key and attribute information of the source management information, and the source name. create information. For example, the master user information data creation unit 113 uses the source management information of the source key “1” to generate the user key “user01”, and then creates the user key “user01” and the source name “source 1”. , create master user information containing source key "1" and attribute information "A". At this time, the resource management information data creation unit 112 updates the user key of the resource management information of the source key "1" with the user key "user01".

Similarly, for the source management information of source keys “2” to “5”, the master user information data creation unit 113 generates user keys “user02” to “user05”, respectively, and then creates these user keys and these user keys. master user information containing source keys "2" to "5" of source management information, attribute information, and source names. At this time, similarly, the source control information data creation unit 112 updates the user keys of the source control information of the source keys “2” to “5” with the user keys “user02” to “user05”, respectively. do.

Then, master user information data creation section 113 reflects the created master user information in the master user information data stored in master user information data storage section 103 . As a result, the master user information corresponding to each source management information constituting the source management information data of the source 1 is reflected in the master user information data.

<<Reflection to ID possession information data after creation of source 1 master user information>>
Next, by reflecting the ID ownership information corresponding to the master user information created in FIG. 2 above in the ID ownership information data (that is, creating the ID ownership information), the user ID name identification is performed. will be described with reference to FIG. FIG. 3 is a diagram (part 1) for explaining an example of the flow of reflection to ID ownership information data. It is assumed that ID management information data collected from each business system 40 is stored in the ID management information data storage unit 104 .

S21-1) First, the matching unit 114 extracts the attribute information of each piece of master user information constituting the master user information data (that is, each piece of master user information of the source name “source 1”), and the attribute information of each piece of ID management information data. It matches the attribute information of the ID management information under a predetermined condition.

Here, the predetermined condition can be arbitrarily set by, for example, the manager or operator of the user information management device 10 or the operator of the terminal 30 . The predetermined condition is, for example, that the "name" included in the attribute information of the master user information matches the "name" included in the attribute information of the ID management information. In addition to this, as a predetermined condition, for example, a combination of "e-mail address" included in the attribute information of the master user information and "name" and "e-mail address" included in the attribute information of the ID management information matches. Alternatively, the combination of "name" and "e-mail address" included in the attribute information of the master user information matches the "e-mail address" included in the attribute information of the ID management information. It can be.

As described above, the predetermined condition is a condition for comparing one or more arbitrary information included in the attribute information of the master user information and one or more arbitrary information included in the attribute information of the ID management information. Conditions can be set. Also, the comparison condition may be not only "match" but also "partial match", "mismatch", and the like. The predetermined conditions are stored in advance in the user information management device 10 in, for example, a table format, and the operator of the terminal 30 or the like selects a desired condition (or a combination of desired conditions) from this table. It may be set by

S22-1) Next, the ID possession information data creation unit 115 generates the master user information of source 1 (that is, the master user information including the source name “source 1”) and ID Create ID ownership information corresponding to the management information. That is, when the match result between the master user information of the source 1 and the ID management information satisfies a predetermined condition, the ID ownership information data creation unit 115 creates the ID ownership corresponding to the master user information and the ID management information. create information. For example, when the matching result between the master user information of the user key "user01" and the ID management information of the system ID "sys01" and the user ID "ID04" satisfies a predetermined condition, the ID possession information data creation unit 115 creates ID ownership information as user key "user01", system ID "sys01" and user ID "ID04". More specifically, the master user information of the user key "user01" and each ID management information are collated in order, and attribute information "A" included in the master user information, system ID "sys01" and user ID The result of comparing the attribute information "d" included in the ID management information of "ID04" is a predetermined condition (for example, "name" matches, "mail address" matches, a combination of these). If a preset condition such as matching) is satisfied, the ID ownership information data creation unit 115 creates the ID ownership information as a user key “user01”, a system ID “sys01”, and a user ID “ID04”. create. The same applies to the master user information of the user keys "user02" to "user05".

Then, ID ownership information data creation unit 115 reflects the created ID ownership information in the ID ownership information data stored in ID ownership information data storage unit 105 . As a result, each master user information of source 1 is associated with the ID management information via the ID ownership information, and the user information of source 1 is identified.

In S22-1 above, when the matching result by the matching unit 114 satisfies a predetermined condition, the ID possession information corresponding to the master user information and the ID management information is created. The candidate may be notified to the operator of the terminal 30 or the like. For example, if the matching result satisfies the first condition, the ID possessing information is created. (or source management information corresponding to this master user information) and corresponding ID management information are notified to the operator of the terminal 30 or the like. Then, in response to this notification, when the operator or the like operates the terminal 30 to indicate "confirmation of name identification", the ID ownership information corresponding to the master user information and the ID management information may be created. .

<<Reflection from input of source information data of source 2 to master user information data>>
Next, when source information data of source 2 is input for the first time, the flow from input to reflection in master user information data (that is, creation of master user information) will be described with reference to FIG. FIG. 4 is a diagram (part 2) for explaining an example of the flow from input of source information data to reflection in master user information data.

S11-2) The input unit 111 inputs the source information data transmitted from the source 2 (for example, the personnel system 20, the terminal 30, etc. Hereinafter, the source 2 is the terminal 30 of the department B). Here, as an example, the source information data of the source 2 is composed of five source information, the attribute information of the source key "1" is "F", the attribute information of the source key "2" is "G", Assume that the attribute information of the source key "3" is "H", the attribute information of the source key "4" is "I", and the attribute information of the source key "5" is "J".

For the sake of convenience, the source keys are expressed as "1" to "5", but as described above, the source key may be arbitrary information or a combination of arbitrary information. Similarly, the attribute information is represented by "F" to "J" for convenience, but as described above, the attribute information includes any one or more pieces of information.

S12-2) Next, the source management information data creation section 112 creates each source management information from each source information constituting the source information data of the source 2, respectively. At this time, as described above, a blank (or NULL value) or the like is set as a user key in each source management information. Note that the user key itself does not have to be set in each source management information.

The source management information data creating section 112 stores the source management information data composed of these source management information in the source management information data storage section 102 as source 2 source management information data.

As described above, when creating source management information from source information, the source management information data creation unit 112 converts each item included in the attribute information of the source information of the source according to the source to source management information. It may be mapped to a predetermined item included in the attribute information of the information.

S13-2) Next, the master user information data creating section 113 creates master user information from each source management information of the source 2 source management information data stored in the source management information data storage section . That is, the master user information data creation unit 113 generates a user key for each source management information, and then generates a master user key containing this user key, the source key and attribute information of the source management information, and the source name. create information. For example, the master user information data creation unit 113 uses the source management information of the source key “1” to generate the user key “user06”, and then creates the user key “user06” and the source name “source 2”. , create master user information containing source key "1" and attribute information "F". At this time, the resource management information data creation unit 112 updates the user key of the resource management information of the source key "1" with the user key "user06".

Similarly, for the source management information of source keys “2” to “5”, the master user information data creation unit 113 generates user keys “user07” to “user10”, respectively, and then creates these user keys and these user keys. master user information containing source keys "2" to "5" of source management information, attribute information, and source names. At this time, similarly, the source control information data creation unit 112 updates the source control information user keys of source keys “2” to “5” with the user keys “user07” to “user10” respectively. do.

Then, master user information data creation section 113 reflects the created master user information in the master user information data stored in master user information data storage section 103 . As a result, the master user information corresponding to each source management information constituting the source management information data of the source 2 is reflected in the master user information data.

In this way, user information obtained from a plurality of sources (in this embodiment, user information (source management information) obtained from source 1 and user information (source management information) obtained from source 2) are mastered. As user information, master user information data is composed of these pieces of master user information.

<<Reflection to ID possession information data after creation of source 2 master user information>>
Next, by reflecting the ID ownership information corresponding to the master user information created in FIG. 4 to the ID ownership information data (that is, creating the ID ownership information), the user ID name identification is performed. will be described with reference to FIG. FIG. 5 is a diagram (part 2) for explaining an example of the flow of reflection to the ID ownership information data. It is assumed that ID management information data collected from each business system 40 is stored in the ID management information data storage unit 104 as described above.

S21-2) First, the collating unit 114 extracts the attribute information of the master user information with the source name “Source 2” from among the pieces of master user information that make up the master user information data, and the ID management information that makes up the ID management information data. The attribute information of the information is matched under a predetermined condition. Here, as the predetermined condition, the same condition as used in S21-2 above may be used.

S22-2) Next, the ID possession information data creation unit 115 generates the master user information of source 2 (that is, the master user information including the source name “source 2”) and the ID Create ID ownership information corresponding to the management information. That is, when the match result between the master user information of the source 2 and the ID management information satisfies a predetermined condition, the ID ownership information data creation unit 115 creates the ID ownership corresponding to the master user information and the ID management information. create information. For example, when the matching result between the master user information of the user key "user06" and the ID management information of the system ID "sys01" and the user ID "ID06" satisfies a predetermined condition, the ID possession information data creation unit 115 creates ID ownership information as user key "user06", system ID "sys01" and user ID "ID06". More specifically, the master user information of the user key "user06" and each ID management information are collated in order, and the attribute information "F" included in the master user information, the system ID "sys01" and the user ID The result of comparing the attribute information "f" included in the ID management information of "ID06" is a predetermined condition (for example, "name" matches, "mail address" matches, a combination of these If a preset condition such as matching) is satisfied, the ID ownership information data creation unit 115 generates the ID ownership information as a user key “user06”, a system ID “sys01”, and a user ID “ID06”. create. The same applies to the master user information of the user keys "user07" to "user10".

Then, ID ownership information data creation unit 115 reflects the created ID ownership information in the ID ownership information data stored in ID ownership information data storage unit 105 . As a result, each piece of master user information of the source 2 is associated with the ID management information via the ID ownership information, and the name identification of the user information of the source 2 is performed.

In S22-2 above, when the matching result by the matching unit 114 satisfies a predetermined condition, the ID possession information corresponding to the master user information and the ID management information is created. If a certain condition is satisfied, the operator of the terminal 30 or the like may be notified as a name identification candidate.

≪Merging master user information≫
Next, assuming that the master user information of the same user exists in each piece of master user information constituting the master user information data, the flow of merging the master user information of the same user will be described with reference to FIG. explain. FIG. 6 is a diagram for explaining an example of the flow of merging master user information in master user information data. Subsequent S31 may be started, for example, at predetermined time intervals or preset timing.

S31) First, the matching unit 114 matches the attribute information among the pieces of master user information constituting the master user information data under a predetermined condition. Then, the master user information data creating unit 113 identifies the master user information of the same user according to the result of matching by the matching unit 114 .

Here, the predetermined condition can be arbitrarily set by, for example, the manager or operator of the user information management device 10 or the operator of the terminal 30 . The predetermined condition is, for example, that the "names" included in the attribute information of each piece of master user information match each other. In addition to this, the predetermined condition may be, for example, that the "e-mail addresses" included in the attribute information of each master user information match each other, or that "e-mail addresses" included in the attribute information of each master user information The combination of "name" and "e-mail address" may match each other.

In this way, as the predetermined condition, a condition for comparing one or more pieces of arbitrary information included in the attribute information of the master user information can be set. Also, the comparison condition may be not only "match" but also "partial match", "mismatch", and the like.

In the following description, it is assumed that the master user information of the user key "user03" and the master user information of the user key "user08" are identified as the master user information of the same user. It should be noted that there is a possibility that the master user information of the same user cannot be specified depending on the result of matching.

Further, hereinafter, of the master user information of the user key "user03" and the master user information of the user key "user08", the master user information of the user key "user03" is the main information. As will be described later, of the master user information of the same user, only the master user information of the main information remains, and the master user information that is not the main information is deleted. It is possible to arbitrarily decide which master user information to use as main information among a plurality of pieces of master user information of the same user. For example, the master user information with the smaller user key may be used as the main information.

S32) Next, the source control information data creation unit 112 assigns the user key “user03” to the source control information having the user key “user08” among the source control information constituting the source control information data of each source. update to In the case of this embodiment, the source control information data creating unit 112 creates the source control information with the user key "user03" among the source control information that constitutes the source control information data of the source 2. Update the key from "user08" to "user03". As a result, the source management information is associated with the master user information of the user key "user03".

S33) Next, the ID ownership information data creation unit 115 updates the user key of the ID ownership information with the user key "user08" to "user03" among the ID ownership information constituting the ID ownership information data. . As a result, the master user information of the user key "user03" and the ID ownership information of the user key "user03" are associated (therefore, the origin management information of the user key "user03" and the user key "user03") are associated with each other. is also associated with the ID possession information of .

S34) Next, the master user information data creation unit 113 deletes the master user information that is not the main information from the master user information data of the same user identified in S31 above. In the case of this embodiment, the master user information data creating unit 113 deletes the master user information of the user key "user008".

As described above, the master user information of the same user is merged with the master user information of the main information (master user information of the user key "user03"). As a result, even if the same user's user information (source information) exists among different sources, it is possible to associate these with each other among the plurality of different sources, and the ID possession information also belongs to the same user. can be associated with each other as Note that the above S32 to SS4 are in no particular order.

<<Reflection from input of updated source information data to master user information data (Part 1)>>
Next, after the master user information data is created, the source information data is updated, and when this updated source information data is entered, it is reflected in the master user information data from this input (that is, the update of the master user information ) will be described with reference to FIG. FIG. 7 is a diagram (part 1) for explaining an example of the flow from input of source information data after updating to reflection in master user information data. In FIG. 7, as an example, a case where the source information data after the source 1 is updated will be described.

S41) The input unit 111 inputs the updated source information data transmitted from the source 1 . Here, as an example, the updated source information data of the source 1 is composed of five source information, the attribute information of the source key "3" is "C'", and the attribute information of the source key "4" is Assume that the attribute information is "D", the attribute information of the source key "5" is "E", the attribute information of the source key "6" is "L", and the attribute information of the source key "7" is "M". That is, the source information of source keys "4" and "5" are common before and after updating the source information data, and the attribute information of source key "3" is changed from "C" to "C" before and after updating the source information data. It has been changed to "C'", the source information of source keys "1" and "2" is deleted from the source information data before updating, and the source information of source keys "3", "6" and "7" is added from the source information data before updating.

S42) The UI providing unit 116 sends the source key added from the pre-update source information data (that is, the source management information data storage unit 102 A UI screen is displayed for inquiring the operator of the terminal 30 about how to handle the source key not included in each source management information of the stored source management information data of the source 1.例文帳に追加In the case of this embodiment, the UI providing unit 116 displays a UI screen for asking the operator of the terminal 30 how to handle the source information of the source key "6" and the source information of the source key "7".

S43) The operator of the terminal 30 inputs some answer on the UI screen of S42. Then, the terminal 30 receives this input and transmits information indicating the content of the reply to the user information management device 10 . Here, hereinafter, it is assumed that the operator of the terminal 30 has entered the following response content on the UI screen.

(1) Source information of source key "6" is newly added user information (that is, user information indicating a user newly assigned to a department, etc.)
(2) The source information of source key "7" is updated source information of source key "1" when the key is changed, etc.)
It is also assumed that the operator of the terminal 30 has input the following response content in addition to the above response content.

(3) Source control information of the same user key is deleted from source 1 source control information data, and master user information associated only with source 1 is deleted S44) Next, source control information data creation unit 112 , based on the updated source information data and the content of the reply sent from the terminal 30 in S43, each of the source 1 source control information data stored in the source control information data storage unit 102. Update withholding information.

In the case of this embodiment, the source control information data creation unit 112 creates source control information from the source information of the source key "6" according to the above reply content (1), and then converts this source control information into source control information Reflect (add) to the data. In addition, according to the above reply content (2), the withholding management information data creation unit 112 determines the withholding management information of the withholding key "1" among the withholding management information constituting the withholding management information data. The source key is updated from "1" to "7" and the attribute information is updated from "A" to "M".

Furthermore, the source management information data creation unit 112 updates the attribute information of the source information for source information in which only the attribute information has been changed before and after updating the source information data, and updates each source that constitutes the source management information data. Of the management information, delete the source management information of the source key that is not included in the source key of each source information that constitutes the updated source information data. In the case of this embodiment, the source management information data creation unit 112 updates the attribute information of the source information of the source key "3" from "C" to "C'" and changes the source management information of the source key "2". delete.

In this way, in FIG. 7, when updated source information data is input, based on the updated source information data and the content of the reply from the operator of the terminal 30, the source management information data storage unit 102 The source control information data stored is updated.

S45) Next, the master user information data creation unit 113 reflects each source control information of the source control information data updated in S44 above in the master user information data stored in the master user information data storage unit 103. do. That is, the master user information data creation unit 113 updates the master user information of the same user key among the master user information included in the master user information data with each source management information constituting the updated source management information data. (Or, if the user key of source control information is blank, etc., after generating a user key, master user information corresponding to the source control information is created.). In addition, the master user information data creation unit 113 associates only source 1 with the master user information having the same user key as the source management information deleted from the source management information data, according to the reply content (3). If so, delete this master user information from the master user information data.

In the case of this embodiment, the master user information data creation unit 113 converts the master user information of the user key "user02" into the master user information data because the master user information of the user key "user02" is associated only with source 1. delete from Also, the master user information data creation unit 113 updates the master user information of the user keys “user01” and “user03”. Further, the master user information data creating unit 113 creates the user key “user11” and then creates master user information including this user key. Then, source management information data creation unit 112 updates the user key of the source management information of source key “6” to “user11”.

As described above, when the source information data at each source is updated, the source management information data is updated based on the updated source information data and the content of the reply from the operator of the terminal 30, and the source management information after the update. The source management information that constitutes the information data is reflected in the master user information data. As a result, the operator of the terminal 30 can send the updated source information data to the user information management device 10 when there is a change in the user information managed in the collaborator management book due to the transfer or employment of the user. The update of the source information data can be easily reflected in the master user information data only by transmission. Note that after the update of the source information data is reflected in the master user information data, user ID identification may be performed using the reflected master user information data.

In this embodiment, the UI screen is displayed on the terminal 30 from which the source information data after updating is input in S42 above, and the source management information data is updated based on the content of the answers on this UI screen. However, not limited to this, for example, without displaying the UI screen, each attribute information of the updated source information data and each attribute information of the source management information data stored in the source management information data storage unit 102 The source management information data may be updated based on the above.

For example, each attribute information of the source information data after updating and each attribute information of the source management information data are collated under a predetermined condition, and after specifying the same user from this collation result, using this identification result, source Management information data may be updated. As a result, as described above, the source information of source key "7" can be used to update the source management information of source key "1".

Similarly, by specifying that the user is not the same user from the matching result, the source information of the source key "6" can be added to the source control information data as new source control information, as described above.

As a result of matching, for example, the degree of similarity of being the same user may be calculated. In this case, if the degree of similarity is equal to or greater than a predetermined threshold, it is identified as the same user, and if the degree of similarity is less than the threshold, it is identified as not being the same user. At this time, for example, when the similarity is within a certain range (that is, when it is difficult to identify whether the user is the same user or not the same user), the above A UI screen may be displayed on the terminal 30 .

<<Reflection from input of updated source information data to master user information data (Part 2)>>
Next, after the master user information data is created, the source information data is updated, and when this updated source information data is entered, it is reflected in the master user information data from this input (that is, the update of the master user information ) will be described with reference to FIG. FIG. 8 is a diagram (part 2) for explaining an example of the flow from the input of updated source information data to the reflection in the master user information data. In FIG. 8, as an example, a case where updated source information data for source 2 is input will be described.

S51) The input unit 111 inputs the updated source information data transmitted from the source 2 . Here, as an example, the updated source information data of the source 2 is composed of five source information, the attribute information of the source key "3" is "H", and the attribute information of the source key "4" is " I'", the attribute information of the source key "5" is "J'", the attribute information of the source key "6" is "N", and the attribute information of the source key "7" is "O". That is, the source information of source key "3" is common before and after updating the source information data, and the attribute information of source keys "4" and "5" is "H" before and after updating the source information data. ' to 'H', 'I' to 'I', and 'J' to 'J'. shall be added from

S52) Next, the source management information data creation section 112 generates the source management information data of the source 2 stored in the source management information data storage section 102 based on the updated source information data input in S51. Update each withholding information that makes up the That is, the withholding management information data creation unit 112 deletes from the withholding management information data the withholding management information of the withholding key that is not included in each of the source information that constitutes the source information data after updating. For source information where only the information is changed, update the attribute information of the source information, and include the source information of the source key that is not included in each source management information that constitutes the source management information data in the updated source information data. Add the source control information to the source control information data, if applicable.

In the case of this embodiment, source keys "1" and "2" are not included in each source information that constitutes source information data after updating. Delete source control information and source control information with source key "2" from source control information data. In addition, since the source information attribute information of the source keys "4" and "5" has been changed before and after the update, the source control information data creating unit 112, among the source control information constituting the source control information data, The attribute information of source control information of source key "4" is updated from "I" to "I'", and the attribute information of source control information of source key "5" is updated from "J" to "J'". .

Furthermore, since the source information of the source keys "6" and "7" which are not included in each source control information constituting the source control information data are included in the source information data after updating, the source control information data creation unit 112 The source control information of source key "6" and the source control information of source key "7" are added to the source control information data.

As described above, in FIG. 8, when the updated source information data is input, the source control information data stored in the source control information data storage unit 102 is updated based only on the updated source information data. be done.

S53) Next, the master user information data creation unit 113 reflects each source control information of the source control information data updated in S52 above in the master user information data stored in the master user information data storage unit 103. do. That is, the master user information data creation unit 113 updates the master user information of the same user key among the master user information included in the master user information data with each source management information constituting the updated source management information data. (Or, if the user key of source control information is blank, etc., after generating a user key, master user information corresponding to the source control information is created.).

In the case of this embodiment, the master user information data creating unit 113 updates the master user information of the user keys "user09" and "user010". Also, the master user information data creation unit 113 creates user keys “user12” and “user13” and then creates master user information containing these user keys. Then, the source control information data creation unit 112 updates the user key of the source control information of the source key "6" to "user12" and the user key of the source control information of the source key "7" to "user13". At this time, unlike FIG. 7, the master user information of the same user key as the source management information (source management information of source key "1" and source management information of source key "2") deleted from the source management information data is associated only with source 2, the master user information is not deleted.

As described above, when the withholding information data at each source is updated, the withholding management information data is updated based only on this updated withholding information data, and the withholding management information that constitutes the updated withholding management information data is Reflected in the master user information data. As a result, the operator or the like of the terminal 30 can easily reflect the update of the source information data in the master user information data without giving a reply as shown in FIG. Note that after the update of the source information data is reflected in the master user information data, user ID identification may be performed using the reflected master user information data.

≪Correction of inconsistency between source management information data and master user information data≫
In the method described in FIG. 8 above, even if master user information with the same user key as the source management information deleted in the source management information data of a certain source is associated only with the source, the master user information is not deleted (that is, in the example of FIG. 8, the master user information of the user key "user06" and the master user information of the user key "user07" are not deleted). In such a case, it can be said that there is a mismatch between the source information data and the master user information data. Therefore, the case where the operator of the terminal 30 issues such a mismatch correction instruction will be described with reference to FIG. FIG. 9 is a diagram for explaining an example of the flow of correction when source management information data and master user information data are inconsistent.

S61) The master user information data creating unit 113 identifies master user information that is inconsistent with source management information data among the pieces of master user information that constitute the master user information data. Hereinafter, it is assumed that the master user information of the user key "user06" and the master user information of the user key "user07" are specified as inconsistent master user information.

S62) The UI providing unit 116 causes a predetermined terminal 30 (for example, the corresponding source terminal 30) to display a UI screen containing the inconsistent master user information. In the case of this embodiment, the terminal 30 displays a UI screen containing information indicating that there is a mismatch between the master user information of the user key "user06" and the master user information of the user key "user07". .

S63) The operator of the terminal 30 inputs some correction instructions on the UI screen of S62. Then, the terminal 30 receives this input and transmits information indicating a correction instruction to the user information management device 10 . Here, hereinafter, it is assumed that the operator of the terminal 30 has input the following correction instruction on the UI screen.

- Master user information with source key "1" (that is, master user information with user key "user06") is changed to source key "6" - Master user information with source key "2" (that is, master user information with user key "user05") S64) Next, the master user information data creation unit 113 updates the master user information data according to the correction instruction of S63. That is, in the case of this embodiment, the master user information data creation unit 113 updates the source key of the master user information of the user key "user06" from "1" to "6", and also updates the master user information of the user key "user07". Remove information from the master user information data.

As described above, when inconsistency occurs between the source management information data and the master user information data, the master user information can be updated by the correction instruction of the operator of the relevant terminal 30 .

≪Individual addition of source management information≫
Here, for example, when the operator of the terminal 30 individually adds source control information to the source control data to add the master user information corresponding to the source control information to the master user information data, FIG. Description will be made with reference to this. FIG. 10 is a diagram for explaining an example of the flow when source management information is added individually.

S71) The operator of the terminal 30 adds desired source control information to the source control information data of a source exclusively for individual addition of source control information (this will be referred to as "source 3"), for example. . Note that the operator of the terminal 30 can, for example, create desired resource management information on the terminal 30 and then transmit this source management information to the user information management device 10, so that the source management information can be 3 can be added to source management information data. However, a blank (or a NULL value) or the like is added to the user key by the source management information data creation unit 112 .

S72) Next, the master user information data creation unit 113 creates a user key, creates master user information from the source management information added in S71 above, and stores it in the master user information data storage unit 103. reflected in the master user information data. That is, the master user information data creation unit 113 generates a user key "user14", and then generates this user key, the source key and attribute information of the source management information of the source key "1", and the source name "source 3". is created, and this master user information is reflected in the master user information data. Thereby, the operator of the terminal 30 can add the master user information corresponding to the desired source management information to the master user information data. Therefore, for example, when a user is added to a certain department, this user's master user information can be added individually. After the master user information corresponding to the individually added source control information is reflected (added) to the master user information data, the user IDs are collated using the reflected master user information data. Also good.

The invention is not limited to the specifically disclosed embodiments above, but various modifications and changes are possible without departing from the scope of the claims.

1 user information management system 10 user information management device 20 personnel system 30 terminal 40 business system 101 user information management processing unit 102 source management information data storage unit 103 master user information data storage unit 104 ID management information data storage unit 105 ID ownership information data Storage unit 111 Input unit 112 Source management information data creation unit 113 Master user information data creation unit 114 Matching unit 115 ID possession information data creation unit 116 UI provision unit

Claims (5)

Source information data containing one or more pieces of user information is input, and a blank or NULL value is assigned to each piece of user information included in the source information data for each source indicating the input source of the source information data. a first creation means for creating source control information data composed of source control information in which the user information and the blank or NULL value are associated ;
It consists of master user information in which source control information included in source control information data of each source , user key, which is identification information that uniformly identifies a user, and source identification information that identifies the source are associated with each other. a second creation means for creating master user information data that
A blank or setting means for setting to a NULL value ;
merging means for merging a plurality of pieces of master user information indicating the same user into one piece of master user information when master user information indicating the same user exists in the master user information included in the master user information data;
For each user key included in a plurality of master user information indicating the same user and for each user key included in a plurality of source control information that is the same user key as the plurality of master user information, a predetermined one user updating means for updating the remaining user keys other than the key to the one user key;
A management device characterized by having: The first creation means is
when the source information data after updating the source information data is input, updating the source management information data with the source information data after updating,
The second creation means is
2. The management device according to claim 1, wherein said master user information data is updated with said updated source management information data. UI providing means for displaying a UI screen containing information based on the updated source information data and the source management information data on a predetermined terminal;
The first creation means is
3. The management device according to claim 2, wherein the source management information data is updated based on the information input on the UI screen and the updated source information data. Source information data containing one or more pieces of user information is input, and a blank or NULL value is assigned to each piece of user information included in the source information data for each source indicating the input source of the source information data. a first creation procedure for creating source control information data composed of source control information in which the user information and the blank or NULL value are associated ;
It consists of master user information in which source control information included in source control information data of each source , user key, which is identification information that uniformly identifies a user, and source identification information that identifies the source are associated with each other. a second creation procedure for creating master user information data that
A blank or a setting procedure for setting to a NULL value ;
a merging procedure for merging a plurality of pieces of master user information indicating the same user into one piece of master user information when master user information indicating the same user exists in the master user information included in the master user information data;
For each user key included in a plurality of master user information indicating the same user and for each user key included in a plurality of source control information that is the same user key as the plurality of master user information, a predetermined one user an update procedure for updating the remaining user keys other than the key to the one user key;
A management method characterized in that a computer executes A program for causing a computer to function as each means in the management apparatus according to any one of claims 1 to 3.

Images