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

Abstract

To support software license management.SOLUTION: A management device for managing licenses of software installed in a plurality of information devices, includes: first determination means for determining whether or not the software installed in the information device violates the license based on inventory information collected from the information devices and license information stored in a storage unit; and display means for displaying on a predetermined terminal, if it is determined that the software installed in the information device violates the license, either an alert screen for warning that the software violates the license or a candidate presentation screen for presenting license candidates that can be allocated to the software depending on the type of license violation.SELECTED DRAWING: Figure 10

Description

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

In companies and the like, a large number of information devices (for example, various terminals such as PCs (personal computers) and server devices) exist in a network, and the number of software installed in these information devices is enormous. For this reason, companies and the like often have introduced IT (Information Technology) asset management systems in order to efficiently manage their software assets and licenses.

In the IT asset management system, for example, software is used appropriately by checking the usage status of software that requires license management for a fee and software that uses non-commercial licenses whose use within the company is restricted. It provides a mechanism to make it.

Japanese Unexamined Patent Publication No. 2001-005659

By the way, in general, software has license agreement terms (also called "license agreements", etc.), and software users understand and agree to all the contents of these license agreement terms before using the software. It is supposed to be used. However, in general, license agreement terms are often esoteric, and software users do not always understand everything correctly. Therefore, the software user may unintentionally violate the license agreement terms.

Also, if unlicensed software is found among the software installed on each information device (terminal, server device, etc.) (that is, if unauthorized software is found), a license is given to this software. It is necessary to allocate and eliminate unauthorized use. However, for example, even if the software is the same, the license may differ depending on the version, purchase form, etc., or there may be multiple license management organizations in a large company, etc., which license should be assigned. It may be difficult to judge.

An embodiment of the present invention has been made in view of the above points, and an object of the present invention is to support software license management.

In order to achieve the above object, the management device according to the embodiment of the present invention is a management device that manages licenses of software installed in a plurality of information devices, and stores inventory information collected from the information devices. Based on the license information stored in the unit, the first determination means for determining whether or not the software installed in the information device has a license violation, and the software installed in the information device. If it is determined that a license violation has occurred, an alert screen for warning that the software has a license violation or a license candidate that can be assigned to the software is displayed according to the type of the license violation. It is characterized by having a display means for displaying any of the candidate presentation screens for presentation on a predetermined terminal.

Can assist in software license management.

It is a figure which shows an example of the whole structure of the asset management system which concerns on this embodiment. It is a figure which shows an example of the functional structure of the management apparatus which concerns on this embodiment. It is a figure which shows an example of the hardware inventory information. It is a figure which shows an example of software inventory information. It is a figure which shows an example of the hardware asset management ledger information. It is a figure which shows an example of software asset management ledger information. It is a figure which shows an example of the license management ledger information. It is a figure which shows an example of the license allocation information. It is a flowchart which shows an example of the license management process which concerns on this Embodiment. It is a figure which shows an example of an alert screen. It is a figure which shows an example of the allocation license candidate presentation screen. It is a figure which shows an example of the rule table used for the score calculation by a rule base. It is a figure for demonstrating an example of score calculation by collaborative filtering (user base). It is a figure for demonstrating an example of score calculation by collaborative filtering (item base).

Hereinafter, embodiments of the present invention (hereinafter, also referred to as “the present embodiment”) will be described with reference to the drawings. In this embodiment, an asset management system 1 that manages software licenses and the like as IT assets will be described. The embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.

<Overall configuration>
First, the overall configuration of the asset management system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of the overall configuration of the asset management system 1 according to the present embodiment.

As shown in FIG. 1, the asset management system 1 according to the present embodiment includes a management device 10, a collection device 20, one or more information devices 30, and an administrator terminal 40.

The information device 30 is various terminals (for example, a PC, a smartphone, a tablet terminal, etc.), a server device, and the like. For example, various software is installed in the information device 30. The software installed in the information device 30 and the licenses of these software are managed by the management device 10. Further, the information device 30 itself (or various devices, various devices, etc. included in the information device 30) is managed as a hardware asset by the management device 10.

Further, the information device 30 relates to software inventory information indicating information about software installed in the information device 30, and the information device 30 itself (or various devices, various devices, etc. included in the information device 30). Dedicated software (inventory collection software) for transmitting hardware inventory information indicating information to the collection device 20 is installed. Hereinafter, the software inventory information and the hardware inventory information are collectively referred to as "inventory information".

Here, inventory is a term indicating owned assets, and is a term widely used in fields such as IT asset management. The inventory collection software itself may also be included in the software managed by the management device 10.

However, when the collection device 20 can acquire the software inventory information and the hardware inventory information from the information device 30 (that is, when the agentless inventory collection software is installed in the collection device 20, for example, etc.) ), The inventory collection software may not be installed in the information device 30.

The collecting device 20 is a computer or a computer system that collects software inventory information and hardware inventory information transmitted from the information device 30. The collecting device 20 transmits the software inventory information and the hardware inventory information collected from the information device 30 to the management device 10.

The collecting device 20 may be integrally configured with the management device 10. That is, the management device 10 may have a function (that is, a function of collecting software inventory information and hardware inventory information) included in the collection device 20.

The management device 10 is a computer or computer system that manages IT assets (software assets, licenses, hardware assets, etc.). The management device 10 uses the software inventory information and the hardware inventory information collected by the collection device 20 to give a notification or the like for supporting software license management, or to support license allocation. That is, the management device 10 determines whether or not a license violation has occurred in the information device 30, and if a license violation has occurred, notifies a warning or the like or provides license allocation support. This makes it possible to eliminate software license violations, reduce the risk of compliance violations in companies and the like, and reduce the burden of license allocation work by administrators and the like.

Here, in the present embodiment, it is assumed that there are two types of license violations: license violation and unauthorized use. License breach means that the software is licensed but violates the terms of the license agreement (license agreement). The case where the license violation has occurred includes, for example, the case where the number of devices that can be used with the same license is exceeded, the case where the product is used for commercial purposes with a non-commercial license, and the like. Unauthorized use, on the other hand, means that the software is not licensed.

The administrator terminal 40 is various terminals (for example, a PC, a smartphone, a tablet terminal, etc.) used by an administrator (for example, a system administrator) of the information device 30. For example, a notification or the like transmitted from the management device 10 is displayed on the administrator terminal 40. The administrator terminal 40 may be integrally configured with the management device 10.

<Functional configuration>
Next, the functional configuration of the management device 10 according to the present embodiment will be described with reference to FIG. FIG. 2 is a diagram showing an example of the functional configuration of the management device 10 according to the present embodiment.

As shown in FIG. 2, the management device 10 according to the present embodiment includes an acquisition unit 101, a hardware identification unit 102, a software identification unit 103, a determination unit 104, an alert notification unit 105, and a score calculation unit 106. And a candidate presentation unit 107. Each of these functional units is realized by a process in which one or more programs installed in the management device 10 are executed by a processor such as a CPU (Central Processing Unit).

Further, the management device 10 according to the present embodiment has a storage unit 108. The storage unit can be realized by using a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The storage unit may be realized by using a storage device or the like connected to the management device 10 via a communication network.

The storage unit 108 stores hardware asset management ledger information 220, software dictionary information 230, software asset management ledger information 240, license management ledger information 250, and license allocation information 260. Each of these pieces of information may be stored in the storage unit 108 realized by using one storage device, or may be stored in the storage unit 108 realized by using a plurality of storage devices. ..

The hardware asset management ledger information 220 is information indicating a hardware asset management ledger for managing hardware assets. Details of the hardware asset management ledger information 220 will be described later.

The software dictionary information 230 is information indicating a software dictionary used for name identification of software. Software name identification is the conversion of software names contained in software inventory information into software names that uniquely identify the software (this conversion is also referred to as "software name normalization").

In general, the software name included in the software inventory information is often not a name that can uniquely identify the software. For example, the software name included in the software inventory information may be represented by a symbol or an abbreviated name. In addition, the software name included in the software inventory information may include half-width and full-width characters. Therefore, the software dictionary information 230 is used to convert such a software name into a software name that uniquely identifies the software.

The software dictionary information 230 is associated with, for example, a software name included in the software inventory information and a normalized software name. The software dictionary information 230 may be further associated with, for example, the type of license of the software (for example, information indicating whether the license is paid or free of charge).

The software asset management ledger information 240 is information indicating a software asset management ledger for managing software assets. Details of the software asset management ledger information 240 will be described later.

The license management ledger information 250 is information indicating a license management ledger for managing licenses. Details of the license management ledger information 250 will be described later.

The license allocation information 260 is information indicating the license allocation status. Details of the license allocation information 260 will be described later.

The acquisition unit 101 acquires the inventory information 210 by receiving the inventory information 210 transmitted from the collection device 20. Here, the inventory information 210 is composed of the hardware inventory information 211 and the software inventory information 212. The details of the hardware inventory information 211 and the software inventory information 212 will be described later. It is assumed that one inventory information 210 is composed of the hardware inventory information 211 of a certain information device 30 and the software inventory information 212 of the information device 30.

The hardware identification unit 102 uses the hardware asset management ledger information 220 stored in the storage unit 108 to display the hardware (that is, the information device 30) indicated by the hardware inventory information 211 acquired by the acquisition unit 101. Identify.

The software identification unit 103 identifies the software indicated by the software inventory information 212 acquired by the acquisition unit 101 by using the software dictionary information 230 and the software asset management ledger information 240 stored in the storage unit 108.

The determination unit 104 uses the license management ledger information 250 and the license allocation information 260 stored in the storage unit 108 to cause a license violation in the hardware (that is, the information device 30) specified by the hardware identification unit 102. Determine if it has occurred. Further, when the determination unit 104 determines that a license violation has occurred, it determines whether the license violation is a license violation or an unauthorized use. Here, the determination unit 104 determines that the software specified by the software identification unit 103 is assigned a license, but if it violates the contract clause (license agreement) of the license, it is a license violation. On the other hand, if the license is not assigned to the software specified by the software specifying unit 103, it is determined that the software is illegally used.

Further, when the determination unit 104 determines that the license violation is unauthorized use, the determination unit 104 determines whether or not there is a license that can be assigned to the illegally used software (that is, the software to which the license is not assigned). To do.

When the determination unit 104 determines that the license violation is a license violation or the alert notification unit 105 determines that there is no license that can be assigned to the software that is being used illegally, the alert notification unit 105 determines the predetermined notification destination ( For example, an alert is notified to the administrator terminal 40, the information device 30 in which the license is violated, and the like.

When the judgment unit 104 determines that the software that is being abused has licenses that can be assigned (that is, licenses that have a vacant number of licenses), the score calculation unit 106 determines that the scores of these licenses are available. It is calculated by a predetermined score calculation method. Here, the score is an index value indicating how appropriate it is to allocate the license to the software.

The candidate presentation unit 107 uses the score calculated by the score calculation unit 106 to present a license candidate that can be assigned to the software that is being abused to a predetermined presentation destination (for example, the administrator terminal 40 or a license violation occurs. It is presented to the information device 30 etc. At this time, the candidate presentation unit 107 presents license candidates in ascending order of score (or descending order of score), for example. As a result, the administrator or the like who assigns the license can assign an appropriate license to the software in which the unauthorized use has occurred.

<Hardware inventory information 211>
Here, the hardware inventory information 211 will be described with reference to FIG. FIG. 3 is a diagram showing an example of hardware inventory information 211. The hardware inventory information 211 is collected by the collecting device 20 for each information device 30.

As shown in FIG. 3, the hardware inventory information 211 includes a "device identification number", a "manufacturer name", a "model number", a "serial number", a "computer name", and a "MAC (Media Access). Control address) Address ”is included.

The "device identification number" is a number generated by the inventory collection software installed in the information device 30, and is an ID that uniquely identifies the information device 30. The "device identification number" may be another name such as a "device number" or a "terminal identification number".

The "manufacturer name" is the manufacturer name of the manufacturer of the information device 30. The "model number" is the model number of the information device 30. The "serial number" is a serial number of the information device 30 (for example, a manufacturing unique number or the like). The "computer name" is a name set in the information device 30. The "MAC address" is the MAC address of the information device 30.

The manufacturer name, model number, serial number, computer name, and MAC address are examples of the information of the information device 30 collected by the inventory collection software, and the information of the information device 30 collected by the inventory collection software. Is not limited to these.

<Software inventory information 212>
Next, the software inventory information 212 will be described with reference to FIG. FIG. 4 is a diagram showing an example of software inventory information 212. The software inventory information 212 is collected by the collecting device 20 for each information device 30.

As shown in FIG. 4, the software inventory information 212 includes one or more records. In addition, each of these records includes a "software name", a "maker name", and an "installation date".

The "software name" is the name of the software. As described above, the software name of the software inventory information 200 is often not a name that can uniquely identify the software.

The "manufacturer name" is the name of the software manufacturer. The "installation date" is the date on which the software is installed in the information device 30. The "installation date" may be the date and time when the software was installed in the information device 30.

The software inventory information 212 is associated with, for example, a “device identification number”, and the hardware inventory information 211 and the software inventory information 212 are associated with the “device identification number”. The software name, manufacturer name, and installation date are examples of software information collected by the inventory collection software, and the software information collected by the inventory collection software is not limited to these. Absent.

<Hardware asset management ledger information 220>
Next, the hardware asset management ledger information 220 will be described with reference to FIG. FIG. 5 is a diagram showing an example of the hardware asset management ledger information 220.

As shown in FIG. 5, the hardware asset management ledger information 220 includes one or more records. In addition, each of these records includes a "hardware management ID", a "device identification number", a "maker name", a "model number", a "serial number", a "computer name", and a "MAC address". , "Administrative department", "administrator", "user ID", and "state".

The "device identification number", "manufacturer name", "model number", "serial number", "computer name", and "MAC address" are as described above.

The "hardware management ID" is an ID that uniquely identifies the information device 30. The "management department" is a department that manages the information device 30. The "administrator" is an ID that uniquely identifies the administrator of the information device 30. The "user ID" is an ID that uniquely identifies a user (user) who is using the information device 30.

The "state" is the state of the hardware. The hardware status includes, for example, "in use", "idle", "discarded", and the like. "In use" means that the user is using the information device 30. The “idle” state is a state in which the user is not using the information device 30 (that is, a state in which the information device 30 is not assigned to the user). The "discarded" state is a state in which the information device 30 has been discarded.

For example, when the hardware to be managed is added or deleted, the administrator uses the administrator terminal 40 to add or delete the record of the hardware asset management ledger information 220.

<Software Asset Management Ledger Information 240>
Next, the software asset management ledger information 240 will be described with reference to FIG. FIG. 6 is a diagram showing an example of software asset management ledger information 240.

As shown in FIG. 6, the software asset management ledger information 240 includes one or more records. In addition, each of these records includes a "software management ID", a "software name", a "maker name", a "version", a "paid / free classification", and a "type".

The "software name" and "manufacturer name" are as described above. The "software management ID" is an ID that uniquely identifies the same type of software. A "version" is a version of the software. The version may include a software revision. The "paid / free category" is a category indicating whether the software is paid or free.

"Type" is the type of software. Examples of software types include "business", "utility", and "other". The "business system" is software that provides functions that directly or indirectly support various businesses, and examples thereof include various application software such as word processing software and spreadsheet software. The "utility" is software that provides ancillary functions, and examples thereof include a printer driver and encryption software. “Other” refers to software other than “business” and “utility”, and examples thereof include software updates and security patches.

For example, when the software to be managed is added or deleted, the administrator uses the administrator terminal 40 to add or delete the record of the software asset management ledger information 240.

<License management ledger information 250>
Next, the license management ledger information 250 will be described with reference to FIG. 7. FIG. 7 is a diagram showing an example of the license management ledger information 250.

As shown in FIG. 7, the license management ledger information 250 includes one or more records. In addition, each of these records includes a "license management ID", a "software management ID", a "license type", an "additional license", a "purchase date", a "management department", and an "administrator". , "Original license management ID", "number of licenses held", "total number of uses", and "other conditions".

The "license management ID" is an ID that uniquely identifies the license of the software. As described above, the "software management ID" is an ID that uniquely identifies the same type of software.

The "license type" is the type of license. Examples of the license type include "user license", "device license", and "freeware". The "user license" is, for example, a license that allows one user to use the software with one license. The "device license" is, for example, a license that allows the installation of software on one information device 30 with one license. "Freeware" is, for example, a license that does not require a license agreement. In addition to these, there are various types of licenses such as "processor license".

An "additional license" is a right (contract) incidental to a license agreement. Such rights include, for example, "upgrade rights" and "downgrade rights". The upgrade right is the right to use a higher version of the software than the licensed version of the software. A downgrade right is a right to use a lower version of the software than the licensed version of the software. In addition to these, there are various additional licenses such as "duplicate installation right".

The "purchase date" is the date on which the license was purchased. The "administrative department" is the department that manages licenses. An "administrator" is a license administrator. Here, even if the licenses are for the same software (that is, the same software management ID), they are managed as different licenses when the management departments and the like are different (that is, they are managed by different license management IDs). For example, in the example shown in FIG. 6, the record of the license management ID "LC01" and the record of the license management ID "LC02" are licenses for the same software (that is, the software management ID "SW01"), but different licenses. It is managed as.

The "original license management ID" is the license management ID of the parent license (that is, the license management ID of the software before the upgrade or downgrade) when the license contract has an upgrade right or a downgrade right. ).

The "number of licenses held" is the number of licenses held. For example, when the number of licenses held is "10" and the license type is "device license", it means that the licenses for 10 devices are held. Similarly, for example, when the number of licenses held is "10" and the license type is "user license", it indicates that the licenses for 10 users are held.

The "total number of licenses" is the license actually used (that is, the license assigned to the software) out of the number of licenses held. "Other conditions" are various conditions related to the use of software (that is, conditions stipulated in the license agreement terms (license agreement), etc.). Such conditions include, for example, "conditions regarding the number of devices that can use the software at the same time with one license", "conditions regarding the period during which the software can be used", and "conditions that the software can be used only for non-commercial use". , Etc. can be mentioned.

In addition to the above, each record of the license management ledger information 250 includes a "license name" indicating the name of the license, a "usage mode" indicating whether the license is a permanent license or a non-permanent license, and the like. To be licensed. In addition to this, for example, when the usage pattern of the license is non-permanent, a "license expiration date" indicating the expiration date of the license may be included.

Further, for example, when a license contract is newly concluded or when the license contract expires, the administrator adds or deletes a record of the license management ledger information 250 using the administrator terminal 40.

<License allocation information 260>
Next, the license allocation information 260 will be described with reference to FIG. FIG. 8 is a diagram showing an example of license allocation information 260.

As shown in FIG. 8, the license allocation information 260 includes one or more records. In addition, each of these records includes a "assignment management ID", a "hardware management ID", and a "license management ID".

The “allocation management ID” is an ID that uniquely identifies each record of the license allocation information 260. As described above, the "hardware management ID" is an ID that uniquely identifies the information device 30. As described above, the "license management ID" is an ID that uniquely identifies the software license.

As a result, it is managed which information device 30 the software license is assigned to the software installed. For example, in the record of the allocation management ID "AS01", the license of the license management ID "LC01" (that is, the software license of the software management ID "SW01") is installed in the information device 30 of the hardware management ID "HW01". It indicates that the software is assigned to the software (software with the software management ID "SW01").

For example, when the license allocation is added or deleted, the record of the license allocation information 260 is added or deleted.

<License management process>
Hereinafter, a process of managing software licenses by the management device 10 according to the present embodiment (license management process) will be described with reference to FIG. FIG. 9 is a flowchart showing an example of the license management process according to the present embodiment.

First, the acquisition unit 101 acquires the inventory information 210 by receiving the inventory information 210 transmitted from the collection device 20 (step S101). As described above, the inventory information 210 is composed of the hardware inventory information 211 and the software inventory information 212.

Next, the hardware identification unit 102 uses the hardware asset management ledger information 220 stored in the storage unit 108 to indicate the hardware (that is, information) indicated by the hardware inventory information 211 acquired in step S101 above. The hardware management ID of the device 30) is specified (step S102). More specifically, the hardware identification unit 102 is a hardware asset management ledger stored in the storage unit 108 according to the manufacturer name, model number, serial number, computer name, MAC address, etc. included in the hardware inventory information 211. The record of information 220 (that is, the hardware management ID of this record) is specified. As a result, the hardware management ID of the information device 30 indicated by the hardware inventory information 211 is specified.

Next, the software identification unit 103 uses the software dictionary information 230 and the software asset management ledger information 240 stored in the storage unit 108, and each software indicated by the software inventory information 212 acquired in step S101 above ( That is, the software management ID of each of these softwares) is specified (step S103). More specifically, the software identification unit 103 first identifies the normalized software name by performing name identification of each software name included in the software inventory information 212 using the software dictionary information 230. Then, the software identification unit 103 identifies the record of the software asset management ledger information 240 (that is, the software management ID of this record) by the normalized software name. As a result, the software management ID of each software indicated by the software inventory information 212 is specified.

Next, the determination unit 104 uses the license management ledger information 250 and the license allocation information 260 stored in the storage unit 108, and the license violation has not occurred in the information device 30 identified in step S102 above. (Step S104). That is, in the information device 30 of the hardware management ID specified in step S102, the determination unit 104 causes either a license violation or unauthorized use in the software of the software management ID specified in step S103. Determine if not.

Here, when determining whether or not a license agreement has occurred, the determination unit 104 first identifies, for example, the allocation management ID corresponding to the hardware management ID by referring to the license allocation information 260. Then, the determination unit 104 may refer to the license management ledger information 250 and determine whether or not the information device 30 satisfies the "other conditions" corresponding to the allocation management ID. In this case, if the information device 30 satisfies all of the "other conditions", it is determined that the license agreement has not occurred, and the information device 30 does not satisfy at least a part of the "other conditions". If so, it is determined that the license agreement has been violated.

On the other hand, when determining whether or not unauthorized use has occurred, the determination unit 104 first identifies, for example, the allocation management ID corresponding to the hardware management ID by referring to the license allocation information 260. Then, the determination unit 104 refers to the license management ledger information 250 and determines whether or not the software management ID specified in step S103 above exists among the software management IDs corresponding to the allocation management ID. do it. In this case, if the software management ID specified in step S103 above exists, it is determined that unauthorized use has not occurred, and if the software management ID specified in step S103 above does not exist, unauthorized use has not occurred. Is determined to have occurred.

When it is determined in step S104 above that a license violation has occurred, the determination unit 104 determines whether the license violation is a license violation or unauthorized use (step S105). If it is determined in step S104 that a plurality of license violations have occurred, the processes after step S105 may be executed for each of the plurality of license violations.

When it is determined in step S105 that unauthorized use has occurred as a license violation, the determination unit 104 has a license that can be assigned to the software in which the unauthorized use has occurred (that is, the software to which the license has not been assigned). It is determined whether or not there is (step S106). More specifically, the determination unit 104 refers to the license management ledger information 250, includes the software management ID of the software in which unauthorized use has occurred, and has a vacant license (that is, "the number of licenses held". > Determine if there is a record (> total number of uses). If such a record exists, it is determined that there is an assignable license, and if it does not exist, it is determined that there is no assignable license. Hereinafter, the software in which unauthorized use has occurred is also referred to as “allocation target software”, and the license that can be assigned to this allocation target software is also referred to as “allocation license candidate”.

If it is determined in step S105 above that a license violation has occurred as a license violation, or if it is determined in step S106 above that there is no license that can be assigned (allocated license candidate), the alert notification unit 105 will set the alert notification unit 105. The alert notification screen is displayed by notifying a predetermined notification destination (for example, the administrator terminal 40, the information device 30 in which the license violation has occurred, etc.) of the alert (step S107).

Here, FIG. 10 shows an example of an alert notification screen displayed on the administrator terminal 40 and the information device 30. On the alert notification screen 1000 shown in FIG. 10, for example, the "date of occurrence" of the alert, the "status" indicating whether or not the alert has been resolved, the "message" indicating the content of the alert, and the information device in which the alert has occurred are displayed. "Computer name" indicating the computer name of the 30 computer, "administrative department name" indicating the management department name of the information device 30, "administrator name" indicating the administrator of the information device 30, user name of the information device 30 "User name" and the like indicating. It also includes a "Details" button to display more detailed content of the alert.

By referring to such an alert notification screen 1000, the user or the like of the administrator terminal 40 or the information device 30 can receive an alert generated by the information device 30 (that is, an alert indicating that a license violation has occurred). You can know the alert that indicates that unauthorized use has occurred). Therefore, in order to clear this alert, the license violation state can be cleared or a license can be assigned. The alert notification screen 1000 can be displayed by, for example, a browser mounted on the administrator terminal 40 or the information device 30, a predetermined application program, or the like.

Returning to the description of FIG. When it is determined in step S106 that there is a license that can be allocated (allocated license candidate), the score calculation unit 106 calculates the score of each allocated license candidate by a predetermined score calculation method (step S108). The details of the score calculation method will be described later.

Next, the candidate presentation unit 107 presents the score calculated in step S108 and the allocation license candidate that can be assigned to the software that is being abused (allocation target software) to a predetermined presentation destination (for example, an administrator). By transmitting to the terminal 40, the information device 30 in which the license is violated, etc.), the allocation license presentation screen is displayed. At this time, on the allocation license presentation screen, for example, allocation license candidates are displayed in ascending order of score (or descending order of score). The number of allotted license candidates and their scores displayed on the license presentation screen may be all allotted license candidates and their scores, or some allotted license candidates and their scores (for example, the score is the top N). It may be an allotted license candidate and its score, etc.).

Here, FIG. 11 shows an example of the allocation license presentation screen displayed on the administrator terminal 40 and the information device 30. On the allocation license candidate presentation screen 2000 shown in FIG. 11, for example, a “license name” indicating the name of the allocation license candidate, a “management department name” indicating the management department name of the allocation license candidate, and a usage pattern of the allocation license candidate are displayed. "Usage pattern" indicating the total number of usages and the number of licenses held by the allotted license candidate, "total number of uses / number of licenses held", "license type" indicating the license type of the allotted license candidate, and the allotted license candidate A "score" or the like indicating a score is included. It also includes an "Assign" button 2001 for assigning the corresponding allocation license candidate to the allocation target software.

At this time, each assigned license candidate is displayed, for example, in ascending order of score (or descending order of score). For example, if it is more appropriate to allocate the allocation license candidate to the allocation target software as the score is higher, the allocation license candidate is displayed in descending order of the score. On the other hand, if it is more appropriate to allocate the allocation license candidate to the allocation target software as the score is lower, the allocation license candidates are displayed in ascending order of the score. As a result, the user of the administrator terminal 40 or the information device 30 can easily know which allocation license candidate is appropriate to be assigned to the allocation target software. Then, when the "assignment" button 2001 is pressed by the user, the allocation license candidate corresponding to the "assignment" button 2001 is assigned to the allocation target software.

In the present embodiment, the score and the allocation license candidates sorted in ascending or descending order of the score are presented to the user (user of the administrator terminal 40, user of the information device 30, etc.), and then the user operates. The license is assigned to the software to be assigned, but the present invention is not limited to this, and the management device 10 may automatically assign the license to the software to be assigned according to the score. For example, the management device 10 may automatically allocate the allocation license candidate having the highest score (or the allocation license candidate having the lowest score) among the allocation license candidates to the allocation target software. Further, at this time, for example, the management device 10 automatically assigns the score only when the maximum value of the score is equal to or higher than a predetermined threshold value (or the minimum value of the score is equal to or lower than the predetermined threshold value), and in other cases. May display the allocation license candidate presentation screen.

<Score calculation method>
Hereinafter, a score calculation method for calculating the score of each assigned license candidate in step S109 of FIG. 9 will be described.

-Score calculation method 1: Rule-based As the score calculation method # 1, a case where the score of each assigned license candidate is calculated by the rule base will be described. In this case, the score calculation unit 106 calculates the score of each allocation license candidate using a table (rule table) in which rules are defined in advance. For example, the rule table includes items and conditions (rules), and the score calculation unit 106 calculates the score for each item by determining whether or not the allotted license candidate satisfies the condition. Here, an example of the rule table used for the rule base is shown in FIG. The rule table shown in FIG. 12 includes, as an example, the item "user / management department" and its conditions, the item "total number of uses / number of licenses held" and its conditions, the item "license type" and its conditions, and the like. There is. The score calculation unit 106 calculates the score by determining for each item whether or not the allocation license candidate satisfies the condition corresponding to the item, and then assigning a score according to this condition.

For example, in the rule table shown in FIG. 12, the condition corresponding to the item "user / management department" is "score a _{1 if the organization / hardware management department to which the user belongs matches the license management department".} Grant ". In this case, the score calculation unit 106 determines the allocation license when the organization to which the user of the information device 30 in which the allocation target software is installed or the management department of the information device 30 matches the management department of the allocation license candidate. _{Give a 1} to the candidate's score. The total of the scores given in this way becomes the score of the allotted license candidate.

The items and conditions in the rule table shown in FIG. 12 are examples, and various items and conditions other than these items and conditions can be considered. For example, "If the license usage pattern is" permanent ", a score of a ₅ is given, and if it is" non-permanent ", a score of a ₆ is given (a ₅ > a ₆ )", "Software to be allocated on the virtual machine There when operating, the same imparts score a ₇ to licenses already assigned to software running on host hardware ", and the like" second license is granted score a ₈ " .. The score may be normalized so as to be 0 or more and 1 or less.

-Score calculation method # 2: User-based collaborative filtering As the score calculation method # 2, a case where the score of each assigned license candidate is calculated by user-based collaborative filtering will be described. In this case, the score calculation unit 106 increases the score of the license used by another user who is using a license similar to that of the user of the information device 30 in which the allocation target software is installed. Calculate the candidate score.

Specifically, for example, as shown in FIG. 13, the user of the information device 30 in which the allocation target software (this software is referred to as "software X") is installed is "U10", and the other users are "U1". "~" U9 ". At this time, it is assumed that there are "Software X license 1" and "Software X license 2" as licenses for score calculation (that is, assigned license candidates).

Further, in FIG. 13, it is assumed that "1" is set for the license used by the user. For example, in the example shown in FIG. 13, the licenses used by "U1" are "Software A license 1", "Software B license 1", and "Software X license 1". Similarly, for example, the licenses used by "U9" are "Software A license 3", "Software C license 2" and "Software X license 2".

In this case, the score calculation unit 106 calculates the number of users "U10" and the other users "U1" to "U9" using the same license as the degree of similarity, and then calculates the "software X license". The maximum value of the similarity of the user using "1" is used as the score of the "Software X license 1", and the maximum value of the similarity of the user using "Software X license 2" is used as the score of the "software X license". The score is "X license 2".

For example, the user "U10" and the user "U1" use the same license "Software B license 1". Therefore, the similarity of the user "U1" is "1". Further, for example, the user "U10" and the user "U4" use the same licenses "Software A license 2", "Software B license 1", and "Software C license 1". Therefore, the similarity of the user "U4" is "3". The similarity of other users is calculated in the same way.

Therefore, in the example shown in FIG. 13, the score of "Software X license 1" is "3", and the score of "Software X license 2" is "2". In addition, these scores may be normalized so as to be 0 or more and 1 or less. However, instead of the maximum value of the similarity, for example, the average value of the similarity of the users who are using the allocation license candidate may be used as the score of the allocation license candidate.

When calculating the score by user-based collaborative filtering, unlike the rule base, there is no need to define rules in advance, and the more training data (that is, the record of license allocation information) is accumulated, the higher the score is. It becomes possible to calculate.

In the above, the score of the allocation license candidate is calculated so that the score of the license used by another user who is using the license similar to the user of the information device 30 in which the allocation target software is installed is high. However, the present invention is not limited to this, and for example, when the license type is "device license", it is applied to another information device 30 to which a license similar to the information device 30 in which the allocation target software is installed is applied. You may calculate the score of the license you have.

-Score calculation method # 3: Item-based collaborative filtering As the score calculation method # 3, a case where the score of each assigned license candidate is calculated by item-based collaborative filtering will be described. In this case, the score calculation unit 106 calculates the score of the assigned license candidate so that the score of the license that is easily assigned together for each license is high.

Specifically, for example, as shown in FIG. 14, the user is represented by "U1" to "U9", the license is represented by "L1" to "L9", and the license used by the user is represented by "○". .. Further, the user of the information device 30 in which the allocation target software is installed is defined as "U9".

For example, in the example shown in FIG. 14, the user "U1" is using the licenses "L1", "L4", and "L7". Similarly, the user "U2" is using the licenses "L2", "L6", and "L8". The same applies to other users.

At this time, the score calculation unit 106 calculates the degree of co-occurrence between licenses and calculates the co-occurrence matrix. For example, the users who are using both the licenses "L1" and "L4" are "U1", "U3", "U4", "U7", and "U9", and therefore the licenses "L1" and "L4". The co-occurrence degree of is "5". Further, for example, since the user who uses both the licenses "L1" and "L6" is "U8", the co-occurrence degree of the licenses "L1" and "L6" is "1". By calculating the co-occurrence degree between the licenses in this way, as shown in FIG. 14, a co-occurrence matrix having the co-occurrence degree between the licenses as its element is calculated. In the co-occurrence matrix shown in FIG. 14, elements having a value of 0 are represented by blanks.

When calculating the score for a single license, the score calculation unit 106 uses the total degree of co-occurrence with other licenses as the score. For example, in the example shown in FIG. 14, the score of the license "L2" is "4".

Further, when calculating the score obtained by multiplying the license used by the user "U9" of the information device 30 in which the allocation target software is installed, the score calculation unit 106 uses the license used by the user. The total degree of co-occurrence with is used as the score of the other license. For example, in the example shown in FIG. 14, the user "U9" is using the licenses "L1" and "L4". Therefore, the sum of the degree of co-occurrence with the license "L1" and the degree of co-occurrence with the license "L4" is used as the score of the corresponding license. Specifically, the score of the license "L6" is "1", the score of the license "L7" is "6", the score of the license "L8" is "2", and the score of the license "L9" is "1". .. Since the licenses "L1" and "L4" are licenses already used by the user "U9", the score does not have to be calculated.

When calculating the score by item-based collaborative filtering, unlike the rule base, there is no need to define rules in advance, and the more training data (that is, the record of license allocation information) is accumulated, the higher the score is. Can be calculated.

In the above, the degree of co-occurrence between the licenses used by these users among the users of the information device 30 in which the allocation target software is installed is calculated, but the present invention is not limited to this, and for example, the license type is "device". In the case of "license", the degree of co-occurrence between the licenses applied to these information devices 30 may be calculated between the information devices 30.

-Score calculation method # 4: Extraction of similar licenses by Word2Vec As score calculation method # 4, a case where the score of each assigned license candidate is calculated by Word2Vec will be described. In this case, the score calculation unit 106 calculates the score of the assigned license candidate so that the score of the license that is easily assigned together for each license is high.

Specifically, for example, after preparing time-series data indicating a list of licenses applied to the information device 30 for each information device 30, the score calculation unit 106 uses Word2Vec to obtain these time-series data. , Converts to vector data on a vector space with the number of licenses as the number of dimensions. Then, the score calculation unit 106 has, for example, a degree of similarity between the vector data corresponding to the information device 30 in which the allocation target software is installed and the vector data corresponding to the information device 30 to which the allocation license candidate is applied (for example). , Distance in vector space), and the average value of these similarities is used as the score.

The above-mentioned score calculation method 1 to score calculation method 4 may be used in combination as appropriate depending on the situation and the like. For example, when the learning data (that is, the record of the license allocation information) is small, the score calculation method 1 is used, and after the learning data is accumulated to some extent, the score calculation method 2 and the score calculation method 4 are used. Use it, etc. When combining a plurality of score calculation methods, for example, the average of the scores calculated in each score calculation may be calculated. Further, when this average is calculated, for example, the scores calculated by each score calculation method may also be presented to the user or the like.

The present invention is not limited to the above-described embodiment disclosed specifically, and various modifications and modifications can be made without departing from the scope of claims.

1 Asset management system 10 Management device 20 Collection device 30 Information device 101 Acquisition unit 102 Hardware identification unit 103 Software identification unit 104 Judgment unit 105 Alert notification unit 106 Score calculation unit 107 Candidate presentation unit 108 Storage unit

Claims (6)

A management device that manages licenses for software installed on multiple information devices.
A first determination means for determining whether or not a license violation has occurred in the software installed in the information device based on the inventory information collected from the information device and the license information stored in the storage unit. When,
If it is determined that the software installed in the information device has a license violation, an alert screen for warning that the software has a license violation or the above-mentioned alert screen, depending on the type of the license violation, A display means for displaying one of the candidate presentation screens for presenting license candidates that can be assigned to software on a predetermined terminal, and
A management device characterized by having. When it is determined that the software installed in the information device violates the license, the license violation indicating that the type of the license violation violates the license agreement of the license agreement and the software. A second determination means for determining whether the software is an unauthorized use indicating that the license is not assigned to the software, and
When it is determined that the type of the license violation is the unauthorized use, it has a third determination means for determining whether or not there is a license that can be assigned to the software based on the license information.
The display means
When it is determined that the type of license violation is the license violation, or when it is determined that the type of license violation is the unauthorized use and there is no license that can be assigned to the software. Display the alert screen on the terminal and display it.
The claim is characterized in that when it is determined that the type of the license violation is the unauthorized use and it is determined that there is a license that can be assigned to the software, the candidate presentation screen is displayed on the terminal. The management device according to 1. When it is determined that there is a license that can be assigned to the software, it has a score calculation means that calculates each score of the license that can be assigned to the software by a predetermined calculation method.
The management device according to claim 2, wherein the licenses that can be assigned to the software are displayed on the candidate presentation screen in ascending or descending order of the score. The score calculation means is
The management device according to claim 3, wherein the score is calculated using one or more of a rule-based method, collaborative filtering, and Word2Vec. A computer that manages licenses for software installed on multiple information devices
Based on the inventory information collected from the information device and the license information stored in the storage unit, a determination procedure for determining whether or not a license violation has occurred in the software installed in the information device, and a determination procedure.
If it is determined that the software installed in the information device has a license violation, an alert screen for warning that the software has a license violation or the above-mentioned alert screen, depending on the type of the license violation, A display procedure for displaying one of the candidate presentation screens for presenting license candidates that can be assigned to software on a predetermined terminal, and
A management method characterized by executing. A program for causing a computer to function as each means in the management device according to any one of claims 1 to 4.