JP2018084931A - Management device, method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique which allows license management to be efficiently performed even in the event of failure in license management.SOLUTION: A management device for managing software assets installed in a plurality of information devices includes: matching means which, for each piece of software as a management object, determines whether the piece of software as the management object actually installed in a prescribed information device is associated with a held license contract or not; and estimation means which, if the matching means determines that the piece of software actually installed in the prescribed information device is not associated with the held license contract, estimates a license contract to be associated with the piece of software actually installed in the prescribed information device, on the basis of an estimation rule.SELECTED DRAWING: Figure 10

Description

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

  In companies and the like, a large amount of information devices (terminals, servers, etc.) exist in the network, and the number of software installed in these information devices is enormous. Among software, there are software that can be freely used and software that requires a license agreement. For software that requires a license agreement, it is necessary to determine whether the software is being used appropriately within the scope of the license agreement. It is necessary to manage with.

  In order to efficiently manage whether the software is properly used within the scope of the license agreement, companies and the like have introduced an IT (Information technology) asset management system to efficiently manage licenses. There are many cases. As a technique related to license management, for example, a technique described in Patent Document 1 is known.

JP 2001-005659 A

  In general, in an IT resource management system, there is a license contract content (for example, the number of licenses) for each software, a function for registering which software is used by which information device, and a network. It has a function of acquiring a list of software actually installed in the information device and periodically checking whether a license violation has occurred. In addition, when a company installs software on an information device, it is required to make an application from a user to an administrator to prevent omission of registration in the IT asset management system database.

  However, since there is a huge amount of software in the world and there are a large number of license contracts held by companies and the like, there is a problem that it is practically difficult to perform license management without omission.

  The disclosed technique has been made in view of the above, and an object of the present invention is to provide a technique that enables efficient license management even when there is a leakage in license management.

  The management device of the disclosed technology is a management device that manages software assets installed in a plurality of information devices, and the management target that is actually installed in a predetermined information device for each software to be managed A matching means for determining whether the software is associated with the license agreement that is held, and in the matching means, the software that is actually installed in the predetermined information device is associated with the license agreement that is held. If it is determined that there is not, an estimation means for estimating a license contract to be associated with software actually installed in the predetermined information device based on an estimation rule.

  According to the disclosed technology, there is provided a technology that enables license management to be performed efficiently even when there is a leakage in license management.

It is a figure which shows the structural example of the IT resource management system which concerns on embodiment. It is a figure which shows the function structural example of the management apparatus which concerns on embodiment. It is a figure which shows an example of HW inventory information. It is a figure which shows an example of SW inventory information. It is a figure which shows an example of HW asset information. It is a figure which shows an example of SW asset information. It is a figure which shows an example of license management information. It is a figure which shows an example of license allocation information. It is a figure which shows an example of automatic allocation rule information. It is a flowchart which shows an example of the process sequence which the management apparatus which concerns on embodiment performs. It is a figure which shows an example of the screen which displays a matching result.

  Embodiments of the present invention will be described below with reference to the drawings. The embodiment described below is only an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

<System configuration>
FIG. 1 is a diagram illustrating a configuration example of an IT resource management system according to an embodiment. The IT resource management system includes a management device 10 that manages IT resources, a collection device 20 that collects information about software installed in the information device 30, an information device 30 that is a hardware asset to be managed, a hardware And an administrator terminal 40 used by an administrator who manages software assets and software assets.

  The management apparatus 10 has information (hereinafter referred to as “license management information 205”) for managing license contract contents (number of licenses, license form, etc.) for each software, and software installed in each information apparatus 30. It has a function of managing, in a database, information (hereinafter referred to as “license allocation information 206”) indicating which license contract is associated with the license contract to be executed. The license management information 205 is input to the database via the administrator terminal 40 by the administrator at a timing such as when a new license contract is concluded. The license allocation information 206 is input to the database via the administrator terminal 40 by the administrator based on the application of the user who uses the software.

  In addition, the management device 10 has a function of determining whether software installed in each information device 30 is associated with any of the license agreements that are held. In addition, when it is determined that the software actually installed in each information device 30 is not associated with any of the license contracts held by the management device 10, It has a function of estimating a license contract to be associated with installed software. In the present embodiment, the management apparatus 10 is provided with this estimation function, so that license management can be performed efficiently even when there is a leakage in license management.

  The collection device 20 includes information regarding hardware of each information device 30 (hereinafter referred to as “HW (hardware) inventory information 201”) and information regarding software actually installed in each information device 30 (hereinafter, “ SW (Software) inventory information 202 ”is collected, and the collected HW inventory information 201 and SW inventory information 202 are transmitted to the management apparatus 10. “Inventory” is a term indicating an owned asset, and is a term widely used in IT asset management and the like. Note that the collection device 20 may be integrated with the management device 10. That is, the collection function included in the collection device 20 may be included in the management device 10.

  The information device 30 is a terminal and a server such as a personal computer, for example, and preinstalled software, software purchased under a license agreement, and the like are installed. In addition, dedicated software (inventory collection software) for transmitting the HW inventory information 201 and the SW inventory information 202 to the collection device 20 is installed in the information device 30 in advance. The administrator terminal 40 is a personal computer, for example, and accepts various operations from the administrator.

<Functional configuration>
FIG. 2 is a diagram illustrating a functional configuration example of the management apparatus according to the embodiment. The management apparatus 10 according to the embodiment includes a collection unit 101, a management unit 102, a matching unit 103, an estimation unit 104, a display unit 105, and a storage unit 106. The storage unit 106 includes a database (HW inventory information 201, SW inventory information 202, HW asset information 203, SW asset information 204, license management information 205, license allocation information 206, and automatic allocation rule information 207) provided in the information device 30. Is stored.

  The collection unit 101, the management unit 102, the matching unit 103, the estimation unit 104, the display unit 105, and the storage unit 106 may be realized using one computer, or may be realized using different computers. The computers may be distributed in fine units. That is, the information device 30 may be realized using one or a plurality of computers. In addition, the one or more computers may be virtual servers using virtualization technology, or may be virtual servers mounted on the cloud.

  The collection unit 101 has a function of storing the HW inventory information 201 and the SW inventory information 202 for each information device 30 collected by the collection device 20 in the storage unit 107. When the collection device 20 and the management device 10 are integrated, the collection unit 101 may collect the HW inventory information 201 and the SW inventory information 202 directly from each information device 30.

  The management unit 102 has a function of managing the HW asset information 203, the SW asset information 204, the license management information 205, the license allocation information 206, and the automatic allocation rule information 207. Based on the instruction, addition / update / deletion of records included in the HW asset information 203, SW asset information 204, license management information 205, license allocation information 206, and automatic allocation rule information 207 is performed.

  The matching unit 103 has a function of determining, for each piece of management target software, whether the management target software actually installed in the information device 30 is associated with the license contract that it holds.

  In addition, in the case where the license agreement that is held is a user license agreement, the matching unit 103 determines whether a user who uses the information device 30 in which the software to be managed is actually installed is associated with the license agreement that is held. It may be determined whether the management target software actually installed in the information device 30 is associated with the license agreement that is held.

  The matching unit 103 has an upgrade right or downgrade right attached to the license agreement that is held, and the software to be managed that is actually installed in the information device 30 is associated with the license agreement that is held. If it is determined that the license is used in the license agreement with the upgrade right or downgrade right, the number of licenses used is counted and the number of upgrade rights or downgrade rights used is counted. It may be.

  When the matching unit 103 determines that the software that is actually installed in the information device 30 is not associated with the license agreement that the estimation unit 104 has, the estimation unit 104 actually performs the information device 30 based on the estimation rule. It has a function of estimating a license contract to be associated with installed software.

  More specifically, the estimation rule includes a plurality of estimation rules, and each of the plurality of estimation rules relates to information (for example, a product ID) related to software actually installed in the information device 30 or the information device 30. Information (for example, management organization name, etc.) and information related to the license agreement held (for example, product ID, management organization name managing license agreement, etc.) satisfy a comparison condition (for example, match / more / less). Indicates whether or not there is. The estimation unit 104 estimates a license contract to be associated with software actually installed in the information device 30 based on the number of estimation rules determined to satisfy the comparison condition among the plurality of estimation rules. May be.

  Further, when the estimation unit 104 determines that the estimation accuracy is high, the estimation unit 104 adds a correspondence between the estimated license contract and software actually installed in the information device 30 to the license allocation information 206 (hereinafter, referred to as “license allocation information 206”). For convenience, this may be referred to as “automatic allocation processing”. In addition, the estimation unit 104 determines that the estimation accuracy is high when the number of estimation rules determined to satisfy the comparison condition among a plurality of estimation rules is equal to or greater than a predetermined number (for example, three). May be.

  Based on the determination result made by the matching unit 103, the display unit 105 displays, for each managed software, the number of licenses used in the license agreement, the number of upgrade rights or downgrade rights used, the excess or shortage of licenses (surplus licenses) For example, the number of licenses and the number of insufficient licenses).

FIG. 3 is a diagram illustrating an example of the HW inventory information. The HW inventory information 201 is collected for each information device 30 and stored in the storage unit 106. The “HW management ID” is an ID that uniquely identifies the information device 30, and is used to associate the HW inventory information 201, the SW inventory information 202, the HW asset information 203, and the license allocation information 206 with each other. The HW management ID may be referred to as a hardware asset identifier.
The “apparatus identification number” is a number generated by the inventory collection software installed in the information apparatus 30 and is an ID that uniquely identifies the information apparatus 30 like the HW management ID. The “device identification number” may be called by other names such as “device number” and “terminal identification number”.

  In the field of IT asset management, hardware assets possessing information that can be collected from information devices 30 existing in the network (for example, information unique to each information device 30 such as computer name, MAC address, serial number, etc.) Is recorded in advance in the ledger for managing the information, and it is confirmed that the information device 30 is actually operating on the network by checking whether the information actually collected from the information device 30 exists in the ledger. Work (called provisioning) is underway. “HW management ID” is an ID registered in advance in the HW asset information 203 (corresponding to “the ledger for managing the owned hardware assets” described above), and when “allocation” is successful, The management device 10 may be paid out to the information device 30, and is not limited thereto, and may be paid out by other methods. The “device identification number” is registered in the HW asset information 203 when “allocation” is successful. In general, “allocation” is performed periodically. In the present embodiment, in the first allocation process, “serial number”, “computer name” and / or “MAC” included in the HW inventory information 201 are used. The allocation is performed by matching the “address” with the “serial number”, “computer name”, and / or “MAC address” included in the HW asset information 203. In the subsequent allocation process, the “device identification number” is used. It is assumed that the allocation is performed by matching the “device identification number” included in the HW asset information 203.

  FIG. 4 is a diagram illustrating an example of SW inventory information. The SW inventory information 202 is collected for each information device 30 and stored in the storage unit 106. The “SW management ID” is an ID that uniquely identifies software, and is used to associate the SW inventory information 202, the SW asset information 204, and the license management information 205 with each other. The SW management ID may be referred to as a software asset identifier.

  In the field of IT resource management, the software name that can be collected from the information device 30 existing in the network is uniquely identified by converting the software name into a specific software name using a software dictionary as necessary. It is common to do (called name identification). This is because the software names collected from the information device 30 are often expressed by symbols or the like, and it is often not clear what the software is. In the present embodiment, “SW management ID” is confirmed by “name identification” to confirm that the software included in the SW inventory information 202 exists in the SW asset information 204 indicating the software asset to be managed. The management device 10 may be paid out to the information device 30, and is not limited thereto, and may be paid out by other methods. The “HW management ID” is the same as the HW management ID included in the HW inventory information 201 described above, and indicates from which information device 30 the SW inventory information 202 is output. “SW name” is the name of the software. In the following description, for the sake of convenience, “SW name” is a software name after name identification (that is, “SW name” of SW inventory information 202 and “SW name” included in SW asset information 204). "Is assumed to be the same character string).

  “Manufacturer name” indicates the manufacturer of the software. “Installation date” indicates the date (or date and time) when the software was installed. “Product ID” indicates a product ID assigned by the manufacturer of the software. Note that the product ID may not exist depending on the software.

  FIG. 5 is a diagram illustrating an example of HW asset information. The HW asset information 203 is information indicating a list of hardware assets to be managed in the IT asset management system according to the present embodiment, and is registered in advance by the administrator when the hardware assets are introduced. Since “HW management ID”, “device identification number”, “manufacturer name”, “model number”, “serial number”, “computer name”, and “MAC address” are the same as those columns in the HW inventory information 201 Description is omitted. “Management department” indicates a department that manages the information device 30. “Administrator” indicates an administrator who manages the information device 30. “User ID” indicates an ID that uniquely identifies a user who uses the information device 30.

  FIG. 6 is a diagram illustrating an example of SW asset information. The SW asset information 204 is information indicating a list of software assets (software that requires a license agreement) to be managed in the IT asset management system according to the present embodiment, and is used when newly installing software to be managed. Registered in advance. Note that even software with the same name is managed as separate software if the versions (intended to be major versions and the same in the following description) are different. Since “SW management ID” and “manufacturer name” are the same as these columns in the SW inventory information 202, description thereof is omitted. “SW name” is the name of the software. “Version” indicates the version of the software.

  FIG. 7 is a diagram illustrating an example of license management information. The license management information 205 is registered by the administrator at a timing such as when a new license contract is concluded. The SW asset information 204 described above is information registered for each record in software units, whereas the license management information 205 is information registered for each record in license units. That is, even if the software is the same, if a plurality of license agreements are concluded, a plurality of records are registered in the license management information 205.

  The “license management ID” is an ID that uniquely identifies a software license agreement. Since the “SW management ID” is the same as the “SW management ID” in the SW inventory information 202 and the SW asset information 204, a description thereof is omitted. “License type” indicates a unit to which a license is granted. For example, a device license is a license that permits installation on one information device 30 with one license. In the case of a device license, a plurality of licenses are required even if one person uses a plurality of terminals. A user license is a license that is permitted to be used by one specific user with one license. In the case of a user license, only one license is required when one person uses a plurality of terminals (the upper limit number may be set). In the “license type”, various license units such as a processor license can be set in addition to the device license and the user license.

  “Additional license” indicates a right (contract) attached to the license agreement. For example, the upgrade right (downgrade right) is a right that permits the use of software of a higher (lower) version than the original version. The duplicate installation right is a right for permitting the same information device 30 to install the original version software and the lower version software in duplicate. The second license is an additional license attached to the device license. If the terminal is used by the same user, the software is installed on a plurality of specific terminals (for example, both desktop PC and mobile PC). The right to grant. “Purchase date” indicates the date on which the license agreement is concluded (or the date on which the software is purchased). “Management department” indicates a department (or a department that has purchased software) that has concluded a license agreement. “Manager” indicates an administrator who manages the license agreement. “Product ID” is the same as the product ID included in the SW inventory information 202 and indicates the product ID of the software corresponding to the license contract. The “original license management ID” indicates a license management ID of a parent license agreement when an upgrade right or downgrade right is attached to the license agreement. “Number of licenses held” indicates the number of licensed software. For example, if the device license is 10 and the number of licenses is 10, it means that 10 device licenses are licensed. Similarly, if the number of licenses held is 10 in the user license, it means that 10 user licenses are licensed.

  “Total number of usage”, “Number of usage (number of upgrades)”, “Number of usage (number of downgrade)”, “Number of usage (number of second licenses)” and “Number of usage (number of duplicate installations)” This column is used in the column and stores the number of licenses confirmed to be used.

  FIG. 8 is a diagram illustrating an example of license allocation information. The license assignment information 206 is registered by the administrator based on the application of the user who uses the software. The “assignment information management ID” is an ID that uniquely identifies a record of the license assignment information 206. The “HW management ID” is the same as the HW management ID included in the HW inventory information 201 and the HW management information described above. When the license is a device license, it means the HW management ID of the information device 30 to which the license is associated. When the license is a user license, it means the HW management ID of the information device 30 used by the user associated with the license. “User ID” is the same as the user ID included in the HW management ID. When the license is a device license, it means the user ID of the user who uses the information device 30 to which the license is associated. The user ID of the user to which the user license is associated. The “license management ID” is the same as the license management ID included in the license management information 205. For example, in FIG. 8, the record whose allocation information management ID is AS01 is installed in the information device 30 (device 01 in the example of FIG. 5) that is HW01 and is used by the user A (FIGS. 6 and 7 corresponds to “Presentation Ver3”), which indicates that it is assigned (associated) with the license contract of LS01.

  FIG. 9 is a diagram illustrating an example of automatic allocation rule information. The automatic allocation rule information 207 stores an estimation rule used when the estimation unit 104 performs a process (estimation process) for estimating a license contract to be associated with software installed in the information device 30. In order to make it possible to change the estimation process for each software (or for each manufacturer), a plurality of estimation rules can be grouped and registered in the automatic allocation rule information 207 shown in FIG.

  The “estimation rule group ID” in FIG. 9A is an ID that identifies a group including a plurality of estimation rules. “Applicable object” indicates software or a manufacturer (for example, software whose manufacturer name is xx-software) to which the grouped estimation rule is applied. The “number of automatic assignment execution rules” is set with a threshold value indicating how many estimation rules satisfy the “comparison condition” described later and the estimation unit 104 performs automatic assignment processing. The estimation accuracy increases as the threshold value increases.

  The “estimation rule ID” in FIG. 9B is an ID that uniquely identifies the estimation rule. “Comparison source” indicates information regarding software actually installed in the information apparatus 30, and “Comparison destination” indicates information regarding a license contract held. The “comparison condition” indicates whether the estimation rule is determined to satisfy the condition when the “comparison source” and the “comparison destination” have a relationship that satisfies the condition. For example, in the example of FIG. 9, “HW management information. Management organization” is set in the “comparison source”. This is the information when the estimation process is performed on the software installed in the information device 30. It shows that “management organization” included in the record of the HW management information in the device 30 is used as a comparison source. Similarly, “license management information. Management organization” is set in “comparison destination”, which indicates that “management organization” included in all records of the license management information 205 is set as a comparison destination. . In addition, “match” is set in “comparison condition”. This means that when “comparison source” and “comparison destination” match, it is determined that the estimation rule satisfies the condition. Show.

<Processing procedure>
FIG. 10 is a flowchart illustrating an example of a processing procedure performed by the management device according to the embodiment. The process in which the management apparatus 10 matches whether each software installed in the information apparatus 30 is associated with (or assigned to) the license contract that the management apparatus 10 uses will be specifically described with reference to FIG. The HW inventory information 201, the SW inventory information 202, the HW asset information 203, the SW asset information 204, the license management information 205, the license allocation information 206, and the automatic allocation rule information 207 used when showing specific examples are respectively Assume that the information shown in FIGS. 3 to 9 is stored.

  In step S <b> 101, the matching unit 103 selects one SW inventory information 202 of each information device 30 stored in the storage unit 106, thereby selecting the information device 30 that performs the matching process.

  In step S102, the matching unit 103 selects the software to be matched by acquiring one record in the SW management ID order from the selected SW inventory information 202.

  In step S103, the matching unit 103 checks whether a license is assigned to the software to be matched. Specifically, first, the matching unit 103 collects one or more license management IDs by searching the license management information 205 using the SW management ID of the record acquired in step S102 as a key.

  When the matching target software is a device license, the matching unit 103 selects one of the collected license management IDs and the HW included in the SW inventory information 202 record acquired in step S102. It is confirmed whether a record including both the management ID exists in the license allocation management information. If it exists, the matching unit 103 determines that the software to be matched is assigned a license, and proceeds to step S104. If it does not exist, the matching unit 103 determines that the license target software is not assigned a license, and proceeds to step S105.

  When the matching target software is a user license, the matching unit 103 searches the HW asset information 203 using the HW management ID included in the SW inventory information 202 record acquired in step S102 as a key, and uses the information device 30. Get the user ID of the user who is. Subsequently, the matching unit 103 confirms whether or not a record including both one of the collected license management IDs and the acquired user ID exists in the license allocation management information. . If it exists, the matching unit 103 determines that a license is assigned to the software to be matched, and the process proceeds to step S104. If it does not exist, the matching unit 103 determines that no license is assigned to the software to be matched, and the process proceeds to step S105.

  In step S104, the matching unit 103 adds 1 to the “total number of uses” of the record corresponding to the license determined to be assigned in the license management information 205. Note that the flowchart shown in FIG. 10 is repeatedly executed for the number of information devices 30 and for the number of installed software. Therefore, when the software to be collated is a user license, the collation unit 103 stores the user who has once counted the number of use, and does not add 1 to the “total number of used” for the user who has once counted the number of use. To. Thereby, even when the software to be collated is installed in each of the plurality of information devices 30 used by the same user, it is possible to prevent the “total number of uses” from being counted repeatedly.

  Here, when the matching unit 103 determines that the software to be matched uses the additional license of the assigned license, the number of usages according to the type of the corresponding additional license (“number of used (number of upgrades) ) ”,“ Used Number (Downgrade Number) ”,“ Used Number (Second License Number) ”, and“ Used Number (Duplicate Installed Number) ”are also incremented by one.

  In step S105, the estimation unit 104 determines whether the “comparison source” and the “comparison destination” satisfy the “comparison condition” for each of the plurality of estimation rules included in the estimation rule group applied to the matching target software. Thus, the license contract to be assigned to the matching target software is estimated. When there are a plurality of estimated license contract candidates, the estimation unit 104 determines a license contract with a large number of estimated rules that satisfy the “comparison condition” and the “comparison destination” as “matching target software”. License agreement to be assigned to

  In step S106, if the estimation rule satisfying the “comparison condition” is equal to or greater than the “number of automatic allocation execution rules” as a result of the processing procedure of step S105, the estimation unit 104 proceeds to step S107, and the “number of automatic allocation execution rules” If it is less than “,” the process proceeds to step S109.

  Here, a specific example of step S105 and step S106 will be described. The matching target software is software (Drawing Ver5) which is SW03 in the SW inventory information 202, and it is assumed that the estimation rule group of RG001 is applied. Since the HW management ID in the matching target software is HW01, it can be seen from the HW asset information 203 that the management department of the matching target software is the general affairs department and the administrator is the manager A. That is, the comparison source of the estimation rule (R01) and the estimation rule (R02) is “General Affairs Department” and “Administrator A”, respectively. Similarly, since the installation date in the matching target software is 2016/6/1, the comparison source of the estimation rule (R03) is “2016/6/1”.

  Next, a record corresponding to the SW management ID of the software to be collated is extracted from all the records of the license management information 205, and “comparison destination” of each estimation rule (R01 to R03) is extracted in the extracted record. Search for a record that satisfies the “comparison condition”. In the license management information 205 shown in FIG. 7, the records whose SW management ID is SW03 are the records of LS04 and LS05. Here, in the record that is LS04, the management organization and the administrator are “General Affairs Department” and “Administrator A”, respectively, and the “installation date” is larger than the “purchase date”. That is, the record of LS04 satisfies all three estimation rules (R01 to R03). On the other hand, in the record that is LS05, the management organization and the administrator are “HR department” and “manager B”, respectively, and the “installation date” is larger than the “purchase date”. That is, the record that is LS05 satisfies only the estimation rule (R03). Accordingly, in step S105, the estimation unit 104 estimates that the license contract of the record that is LS04 that has many estimation rules that are satisfied is a license contract that should be assigned to the matching target software. In addition, since the “number of rules for automatic assignment execution” in the estimation rule group of RG001 is “3”, the estimation unit 104 proceeds to the processing procedure of step S107.

  In step S <b> 107, the estimation unit 104 adds the correspondence relationship between the matching target software and the license contract to be allocated to the matching target software to the license allocation information 206. In the case of the specific example described above, the estimation unit 104 adds a record with the HW management ID “HW01”, the user ID “user A”, and the license management ID “LS04” to the license allocation management information. It will be.

  Since the processing procedure of step S108 is the same as that of step S104, description thereof is omitted. In the case of the specific example described above, the estimation unit 104 adds 1 to the “total number of uses” of the record whose license management ID is “LS04”.

  In step S109, the display unit 105 uses the ratio of the number of estimation rules determined to satisfy the “comparison condition” and the number of “automatic allocation execution rules” as a result of the processing procedure in step S105 as an estimation rate. It is displayed on the screen of the terminal 40. For example, when the number of estimation rules satisfying the “comparison condition” is 2 and the “number of automatic allocation execution rules” is 3, the display unit 105 displays “67%” as the estimation rate. The administrator can perform the work with reference to the estimation rate when visually allocating the license to the matching target software.

  Note that the processing procedure of steps S106 to S108 may be omitted, and the processing procedure of step S105 may be followed by the processing procedure of step S109. That is, the management apparatus 10 may only display the estimated rate to the administrator without performing the automatic allocation process.

  In step S110, when the matching process is completed for all the records in the SW inventory information 202 of the information device 30 that performs the matching process, the estimation unit 104 proceeds to step S111. When the matching process has not been completed for all the records, the estimation unit 104 returns to step S102 and performs the matching process for the next record.

  In step S111, when the matching process is completed for all the information devices 30, the estimation unit 104 proceeds to step S112. When the matching process has not been completed for all the information devices 30, the estimation unit 104 returns to step S <b> 101 and performs the matching process for the next information device 30.

  In step S112, the display unit 112 displays the number of licenses used in the license agreement, the number of upgrade rights or downgrade rights used, the number of surplus licenses (the number of surplus licenses) based on the result of the matching performed in steps S101 to S111. , The number of insufficient licenses) is displayed on the screen of the administrator terminal 40 or the like. An example of the display screen is shown in FIG. 11A shows a display example in software units, and FIG. 11B further shows a display example in software units and license contract units.

  From the license management information 205, the display unit 112 displays “SW management number”, “license management number”, “management department”, “number of licenses held”, “total number of used”, “number of used (upgrade used)”, “ The number of uses (the number of downgrades used), the number of uses (number of second licenses used), and the number of uses (number of duplicate installation uses) are acquired and displayed in a list as shown in FIG. “Allocation number” indicates the number of license allocation destinations registered (allocated) in the license allocation information 206. In the case of a device license, the number of records having the same license management number and different HW management IDs among all records of the license allocation information 206 corresponds to “number of allocations”. In the case of a user license, the number of records having the same license management number and different user IDs in the license assignment information 206 corresponds to “number of assignments”. “License excess / deficiency number” is a number obtained by subtracting “total number of uses” from “license possession number”.

  The processing procedure performed by the management apparatus according to the embodiment has been described above. Since the management apparatus according to the embodiment performs automatic license allocation processing based on the estimation rule when there is a leakage in license management, the license is to be used in an environment where there are a large number of information apparatuses 30 and license contracts. Management can be performed efficiently.

(Modification)
In the embodiment described above (hereinafter referred to as a basic example), the “HW management ID” included in the HW inventory information 201 and the SW inventory information 202 is the same as the “HW management ID” included in the HW asset information 203. It was explained on the assumption. Also, it is assumed that the “SW management ID” included in the SW inventory information 202, the “SW management ID” included in the SW asset information 204, and the “SW management ID” included in the license management information 205 are the same. did.

  In this modification, the “HW management ID” included in the HW inventory information 201 and the SW inventory information 202 is replaced with an ID that uniquely identifies the record of the HW inventory information 201 (hereinafter referred to as “HW inventory ID”). Similarly, the “SW management ID” included in the SW inventory information 202 is replaced with an ID that uniquely identifies the record of the SW inventory information 202 (hereinafter referred to as “SW inventory ID”). That is, in this modification, the HW inventory information 201 and the SW inventory information 202 are associated with each other using “HW inventory ID”. Also, the HW inventory information 201 and the HW asset information 203 are associated with each other using “device identification number”. Also, the SW inventory information 202 and the SW asset information 204 are associated with each other using “SW name”. The SW asset information 204 and the license management information 205 are associated with each other using the “SW management ID” as in the basic example.

  In the present modification, the processing procedures in steps S102 and S103 in FIG. 10 are executed according to the following procedure. Note that the processing procedures in steps S104 to S112 may be the same as in the basic example. Also, points not particularly mentioned may be the same as in the basic example.

  In step S <b> 102, the matching unit 103 selects one piece of software to be matched by acquiring one record from the selected SW inventory information 202 in the order of “SW inventory ID”.

  In step S103, the matching unit 103 checks whether a license is assigned to the software to be matched. Specifically, first, the matching unit 103 searches the SW asset information using the “SW name” included in the record of the SW inventory information 202 acquired in step S102 as a key, and the software corresponding to the “SW name” is searched. Obtain “SW management ID”. Subsequently, the matching unit 103 collects one or more “license management IDs” by searching the license management information 205 using the acquired “SW management ID” as a key. In addition, the matching unit 103 acquires the “device identification number” by searching the HW inventory information 201 using the “HW inventory ID” included in the record of the SW inventory information 202 acquired in step S102 as a key. Subsequently, the matching unit 103 acquires the “HW management ID” by searching the HW asset information 203 using the acquired “device identification number” as a key.

  When the matching target software is a device license, the matching unit 103 records a license including both one of the collected license management IDs and the acquired “HW management ID”. Check if it exists in the allocation management information. If it exists, the matching unit 103 determines that the software to be matched is assigned a license, and proceeds to step S104. If it does not exist, the matching unit 103 determines that the license target software is not assigned a license, and proceeds to step S105.

  When the matching target software is a user license, the matching unit 103 searches the HW asset information 203 using the acquired HW management ID as a key, and acquires the user ID of the user who is using the information device 30. Subsequently, the matching unit 103 confirms whether or not a record including both one of the collected license management IDs and the acquired user ID exists in the license allocation management information. . If it exists, the matching unit 103 determines that a license is assigned to the software to be matched, and the process proceeds to step S104. If it does not exist, the matching unit 103 determines that no license is assigned to the software to be matched, and the process proceeds to step S105.

<Supplement of embodiment>
The present invention is not limited to the above-described embodiments, and various modifications and applications are possible within the scope of the claims. The order of the flowcharts described in the embodiments may be changed as long as there is no contradiction. The name of each column in various information stored in the storage unit 106 is a name given for convenience in describing the embodiment, and may be replaced with another name.

  As described above, each functional unit included in the information device 30 according to the embodiment executes a program corresponding to the process executed in the information device 30 using hardware resources such as a CPU and a memory included in the information device 30. Can be realized. Further, the program can be stored in a storage medium.

DESCRIPTION OF SYMBOLS 10 Management apparatus 20 Collection apparatus 30 Information apparatus 40 Administrator terminal 101 Collection part 102 Management part 103 Collision part 104 Estimation part 105 Display part 106 Storage part

Claims (7)

A management device that manages software assets installed in multiple information devices,
For each managed software, a matching means for determining whether the managed software actually installed in a predetermined information device is associated with a license agreement possessed;
If it is determined in the matching means that the software actually installed in the predetermined information device is not associated with the license agreement that is held, the software is actually applied to the predetermined information device based on an estimation rule. An estimation means for estimating a license agreement to be associated with installed software;
A management device. The estimation rule includes a plurality of estimation rules, and each of the plurality of estimation rules includes information regarding software actually installed in the predetermined information device or information regarding the predetermined information device, and the license agreement held. Information about whether or not there is a relationship that satisfies a predetermined comparison condition,
The estimation means includes a license to be associated with software actually installed in the predetermined information device based on the number of estimation rules determined to satisfy the predetermined comparison condition among the plurality of estimation rules. Estimate contract,
The management apparatus according to claim 1. Storage means for storing license allocation information indicating a correspondence relationship between the software installed in the predetermined information device and the license agreement that is held;
When the number of estimation rules determined to satisfy the predetermined comparison condition among the plurality of estimation rules is equal to or greater than a predetermined number, the estimation means actually determines the estimated license contract and the predetermined information device. Adding a correspondence with the software installed in the license allocation information,
The management device according to claim 2.   In the collating means, when the license agreement that is held is a user license agreement, a user who uses the predetermined information device in which the software to be managed is actually installed is associated with the license agreement that is held. 4. Any one of claims 1 to 3, wherein it is determined whether or not the software to be managed actually installed in the predetermined information device is associated with the license agreement that is held. The management device according to one item. The matching means includes an upgrade right or a downgrade right attached to the license agreement held, and the managed software actually installed in the predetermined information device is included in the license agreement held. If it is determined that the licenses are associated with each other, the number of licenses used is counted as if the licenses in the above-mentioned license agreement with the upgrade rights or downgrade rights attached are used, and the upgrade rights or downgrade rights are counted. Count usage,
Display means for displaying the number of licenses used counted by the matching means and the number of uses of the upgrade right or downgrade right;
The management apparatus according to any one of claims 1 to 4, further comprising: A method executed by a management device that manages software assets installed in a plurality of information devices,
Determining, for each managed software, whether the managed software that is actually installed in a predetermined information device is associated with a license agreement possessed;
Software that is actually installed in the predetermined information device based on an estimation rule when it is determined that the software that is actually installed in the predetermined information device is not associated with the license agreement that is held Estimating a license agreement to be associated with,
Having a method.   The program for functioning a computer as each means of the management apparatus as described in any one of Claims 1 thru | or 5.

Images