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

Description

Applicable under Article 30, Paragraph 2 of the Patent Act. Published at IAITAM ACE JAPAN 2017 on October 4, 2017.

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

In companies and other organizations, there are a large number of information devices (for example, various terminals such as PCs and server devices) within the network, and the number of software programs installed on these information devices is also enormous. For this reason, companies and other organizations often introduce IT (Information Technology) asset management systems to efficiently manage the software assets and licenses they own.

In an IT asset management system, for example, software assets held within a company are managed using a ledger (this ledger is also called a "software asset management ledger").

JP 2001-005659 A

For example, software that is not managed in the software asset management ledger may be installed on an information device. This is because a user of the information device may, for example, purchase and install software at his or her own discretion.

In such cases, the administrator of the IT asset management system must determine whether the software installed on the information device is appropriate (for example, whether it complies with the software asset operation rules and security policies, etc.) before registering it in the software asset management ledger. This is because, for example, if software that does not comply with the software asset operation rules and security policies, etc. is installed on an information device, there is a risk of external attacks such as computer viruses and information leaks, as well as contract violations due to unauthorized use of licenses.

However, when there are a large number of information devices, it is conceivable that software that is not managed in the software asset management ledger may be installed on the information devices. For this reason, it is thought that the work of registering software in the software asset management ledger by the administrator of the IT asset management system requires a lot of effort.

The embodiment of the present invention was made in consideration of the above points, and aims to facilitate the registration process in the software asset management ledger.

In order to solve the above problem, a management device according to an embodiment of the present invention is a management device that manages software assets installed in a plurality of information devices, and has a first determination means for determining whether or not the software installed in the information device is managed in a software asset management ledger, and a registration means for registering information about the software in the software asset management ledger in association with a category into which the software is classified and which is used to determine whether or not the software is being used appropriately, when the first determination means determines that the software is not managed in the software asset management ledger. The categories include a first category indicating that the software is permitted to be used in the information device and is used appropriately, a second category indicating that the software is prohibited from being used in the information device and is subject to an alert notification as inappropriate software use, a third category indicating that a prior application is required to use the software and that if no prior application is made, the software is subject to an alert as inappropriate software use, and a fourth category indicating that the software is an update program or device driver for other software and is not subject to a determination of whether or not the software is being used appropriately.

This makes it easier to register software assets in the software asset management ledger.

1 is a diagram illustrating an example of an overall configuration of an asset management system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a functional configuration of a management device according to the present embodiment. FIG. 2 illustrates an example of hardware inventory information. FIG. 11 illustrates an example of software inventory information. FIG. 2 is a diagram illustrating an example of hardware asset management ledger information. 11 is a diagram illustrating an example of software-property management ledger information. FIG. 2 is a diagram illustrating an example of license management register information. FIG. 11 illustrates an example of license allocation information. FIG. 11 is a diagram showing an example of automatic registration condition information. 13 is a flowchart illustrating an example of an automatic registration process in a software-asset management ledger. 13 is a flowchart illustrating an example of an alert notification process. 13A and 13B are diagrams illustrating an example of an alert list screen and an alert details screen.

The following describes an embodiment of the present invention with reference to the drawings. Note that the embodiment described below is merely an example, and the embodiment to which the present invention is applicable is not limited to the following embodiment.

<Overall composition>
First, an asset management system 1 that manages IT assets such as software assets, hardware assets, and licenses will be described with reference to Fig. 1. 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 this 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, for example, a PC, a smartphone, a tablet terminal, or other terminal, a server device, or the like. For example, various software is installed on the information device 30. The information device 30 and the software installed on the information device 30 are hardware assets and software assets to be managed by the management device 10. Note that software includes software purchased under a license agreement or the like, pre-installed software, updates for certain software, security patches, and the like.

In addition, the information device 30 has installed therein dedicated software (inventory collection software) that transmits to the collection device 20 software inventory information indicating information related to software installed in the information device 30 and hardware inventory information indicating information related to the information device 30. Inventory is a term that indicates owned assets, and is a term that is 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, if the collection device 20 can obtain software inventory information and hardware inventory information from the information device 30 (i.e., for example, if inventory collection software using an agentless method is installed in the collection device 20), the inventory collection software does not need to be installed in the information device 30.

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

The collection device 20 may be configured as an integral part of the management device 10. In other words, the management device 10 may have the functions of the collection device 20 (the function of collecting software inventory information and hardware inventory information).

The management device 10 is a computer or computer system that manages IT assets. The management device 10 registers software assets in the software asset management ledger using the software inventory information collected by the collection device 20. That is, when software that is not managed in the software asset management ledger is included in the software inventory information (in other words, when software that is not managed in the software asset management ledger is installed in the information device 30), the management device 10 registers the software as an asset in the software asset management ledger.

The management device 10 also uses the software inventory information and hardware inventory information sent from the collection device 20 to determine whether the IT assets are being used appropriately, and notifies the administrator terminal 40, information device 30, etc. of an alert based on the determination result.

The administrator terminal 40 is, for example, a PC, a smartphone, a tablet terminal, or other type of terminal, and is used by the administrator of the management device 10. For example, the management device 10 displays a list of alerts notified from the management device 10. The administrator terminal 40 may be configured as an integrated part of 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. 2. 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 this embodiment has a registration processing unit 110 and an alert notification processing unit 120. Each of these functional units is realized by a process executed by a CPU (Central Processing Unit) of one or more programs installed in the management device 10.

The management device 10 according to this embodiment also has a storage unit 130. The storage unit can be realized, for example, using a hard disk drive (HDD) or a solid state drive (SSD). The storage unit may also be realized using a storage device connected to the management device 10 via a network.

The storage unit 130 stores hardware inventory information 210, software inventory information 220, hardware asset management ledger information 230, software asset management ledger information 240, license management ledger information 250, license allocation information 260, automatic registration condition information 270, and software dictionary information 280. Each of these pieces of information may be stored in a storage unit 130 realized using one storage device, or may be stored in a storage unit 130 realized using multiple storage devices.

The hardware inventory information 210 is hardware inventory information collected by the collection device 20 for each information device 30. Details of the hardware inventory information 210 will be described later.

The software inventory information 220 is software inventory information collected by the collection device 20 for each information device 30. Each piece of software inventory information 220 includes a record indicating information about each piece of software installed in the information device 30 (e.g., the software name, installation date, etc.). Details of the software inventory information 220 will be described later.

Hardware asset management ledger information 230 is information that indicates a hardware asset management ledger for managing hardware assets. Details of hardware asset management ledger information 230 will be described later.

The software asset management ledger information 240 is information that indicates the software asset management ledger. Details of the software asset management ledger information 240 will be described later.

The software assets managed by the software asset management ledger in this embodiment are classified into five software categories: "standard software," "prohibited software," "unauthorized software," "unmanaged software," and "individually installed software."

"Standard software" is software that is permitted for use on the information device 30. "Prohibited software" is software that is prohibited for use on the information device 30. "Unauthorized software" is software that requires a specific permission application to be made in advance in order to be used on the information device 30. "Unmanaged software" is software that is not managed by the management device 10. Examples of software that is classified as "unmanaged software" include software update programs and various device drivers.

Note that the above five software categories into which software assets are classified are merely examples, and software assets are not limited to these five software categories.

License management ledger information 250 is information that indicates a license management ledger for managing licenses. Details of license management ledger information 250 will be described later.

License allocation information 260 is information regarding license allocation. Details of license allocation information 260 will be described later.

The automatic registration condition information 270 is information indicating the conditions for registering software that is not managed in the software asset management ledger as an asset in the software asset management ledger when that software is installed in the information device 30. Software that is not managed in the software asset management ledger is registered in the software asset management ledger in one of five software categories, "standard software," "prohibited software," "unauthorized software," "unmanaged software," and "individually installed software," according to the automatic registration condition information 270.

The software dictionary information 280 is information that indicates a software dictionary used for software name matching. Software name matching refers to converting the software names included in the software inventory information 220 into software names that uniquely identify the software (this conversion is also called "software name normalization").

In general, the software names included in the software inventory information 220 are often not names that can uniquely identify the software. For example, the software names included in the software inventory information 220 may be expressed using symbols or abbreviated names. Furthermore, the software names included in the software inventory information 220 may contain a mixture of half-width and full-width characters. Therefore, the software dictionary information 280 is used to convert such software names into software names that can uniquely identify the software.

In the software dictionary information 280, for example, software names included in the software inventory information 220 are associated with normalized software names. Note that the software dictionary information 280 may also be associated with software types (e.g., "utility," "device driver," or "update program") and license types (e.g., "freeware" or "shareware").

When software that is not managed in the software asset management ledger is installed in the information device 30, the registration processing unit 110 performs a process of registering the software in the software asset management ledger as an asset. The registration processing unit 110 includes an acquisition unit 111, a normalization unit 112, and a registration unit 113.

The acquisition unit 111 acquires one record from the software inventory information 220 stored in the memory unit 130.

The normalization unit 112 normalizes the software name contained in the record acquired by the acquisition unit 111 by referring to the software dictionary information 280 stored in the memory unit 130.

The registration unit 113 refers to the software asset management ledger information 240 and determines whether or not the software asset with the software name normalized by the normalization unit 112 is registered in the software asset management ledger. If the registration unit 113 determines that the software asset with the software name is not registered in the software asset management ledger, the registration unit 113 refers to the automatic registration condition information 270 and registers the software with the software name as an asset in the software asset management ledger in a software classification according to the automatic registration condition information 270.

The alert notification processing unit 120 performs processing to notify an alert when an IT resource is not being used appropriately. The alert notification processing unit 120 includes a determination unit 121 and an alert notification unit 122.

The determination unit 121 determines whether or not IT assets are being used appropriately based on various information stored in the memory unit 130 (hardware inventory information 210, software inventory information 220, hardware asset management ledger information 230, software asset management ledger information 240, license management ledger information 250, and license allocation information 260).

When the determination unit 121 determines that the IT assets are not being used appropriately, the alert notification unit 122 notifies the administrator terminal 40, the information device 30, etc. of an alert according to the determination result.

<Hardware Inventory Information 210>
Here, the hardware inventory information 210 will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the hardware inventory information 210. The hardware inventory information 210 is collected by the collection device 20 for each information device 30, and stored in the storage unit 130.

As shown in FIG. 3, the hardware inventory information 210 includes a "hardware management ID," a "device identification number," a "manufacturer name," a "model number," a "serial number," a "computer name," and a "MAC (Media Access Control) address."

The "hardware management ID" is an ID that uniquely identifies the information device 30. The hardware management ID associates the hardware inventory information 210 with the software inventory information 220.

The "device identification number" is a number generated by inventory collection software installed on the information device 30, and, like the hardware management ID, is an ID that uniquely identifies the information device 30. Note that the "device identification number" may be other names such as a "device number" or a "terminal identification number."

"Manufacturer name" is the name of the manufacturer of the information device 30. "Model number" is the model number of the information device 30. "Serial number" is the serial number of the information device 30 (e.g., a manufacturing specific number, etc.). "Computer name" is the name set for the information device 30. "MAC address" is the MAC address of the information device 30.

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

<Software Inventory Information 220>
Next, the software inventory information 220 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the software inventory information 220. The software inventory information 220 is collected by the collection device 20 for each information device 30, and stored in the storage unit 130.

As shown in FIG. 4, the software inventory information 220 includes one or more records. Each record includes a "software management ID," a "hardware management ID," a "software name," a "manufacturer name," and an "installation date."

The "software management ID" is an ID that uniquely identifies the software. Note that the software management ID may also be called something else, such as a "software identifier" or a "software asset identifier."

If the software management ID included in a record of the software inventory information 220 also exists in the software asset management ledger information 240, the record of the software inventory information 220 and the record of the software asset management ledger information 240 are mutually associated by the software management ID.

On the other hand, there may be cases where the software management ID included in a record in the software inventory information 220 does not exist in the software asset management ledger information 240. This may be the case, for example, when a user of the information device 30 installs software on the information device 30 that is not managed in the software asset management ledger.

As described above, the "hardware management ID" is an ID that uniquely identifies the information device 30. The "software name" is the name of the software. Note that, as described above, the software name in the software inventory information 200 is often not a name that can uniquely identify the software.

"Manufacturer name" is the name of the manufacturer of the software. "Installation date" is the date on which the software was installed on the information device 30. Note that "Installation date" may also be the date and time when the software was installed on the information device 30.

<Hardware Asset Management Register Information 230>
Next, the hardware asset management ledger information 230 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the hardware asset management ledger information 230.

As shown in FIG. 5, the hardware asset management ledger information 230 includes one or more records. Each record includes a "hardware management ID," a "device identification number," a "manufacturer name," a "model number," a "serial number," a "computer name," a "MAC address," a "management department," a "administrator," a "user ID," and a "status."

The "Hardware Management ID", "Device Identification Number", "Manufacturer Name", "Model Number", "Serial Number", "Computer Name", and "MAC Address" are as described above.

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

"Status" refers to the state of the hardware. Examples of hardware states include "in use," "idle," and "discarded." "In use" refers to a state in which the information device 30 is being used by a user. "Idle" refers to a state in which the information device 30 is not being used by a user (a state in which the information device 30 has not been assigned to a user). "Discarded" refers to a state in which the information device 30 has been discarded.

For example, when managed hardware is added or deleted, the administrator uses the administrator terminal 40 to add or delete records in the hardware asset management ledger information 230.

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

As shown in FIG. 6, the software asset management ledger information 240 includes one or more records. Each record includes a "software management ID," a "software name," a "manufacturer name," a "version," a "paid/free classification," a "type," and a "software classification."

The "Software Management ID", "Software Name", and "Manufacturer Name" are as described above.

"Version" is the version of the software. Note that the version may also include the revision of the software. "Paid/free classification" is a classification that indicates whether the software is paid or free.

"Type" is the type of software. Examples of software types include "business", "utility", and "other". "Business" software is software that provides functions that directly or indirectly support various business operations, such as various application software such as word processing software and spreadsheet software. "Utility" is software that provides auxiliary functions, such as printer drivers and encryption software. "Other" is software other than "business" and "utility", such as software update programs and security patches.

"Software classification" is a classification for classifying software assets. As mentioned above, there are five software classifications: "standard software," "prohibited software," "unauthorized software," "unmanaged software," and "individually installed software."

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

<License Management Register Information 250>
Next, the license management register information 250 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the license management register information 250.

As shown in FIG. 7, the license management ledger information 250 includes one or more records. Each record includes a "license management ID," a "software management ID," a "license type," an "additional license," a "purchase date," a "management department," an "administrator," a "original license management ID," a "number of licenses held," and a "total number of uses."

The "license management ID" is an ID that uniquely identifies the software license. The "software management ID" is an ID that uniquely identifies the software, as described above.

"License type" is the type of license. Examples of license types include "user license", "device license", and "freeware". A "user license" is, for example, a license that allows one user to use the software. A "device license" is, for example, a license that allows the installation of the software on one information device 30. "Freeware" is, for example, a license that does not require a license agreement.

In addition to the above, each record in the license management ledger information 250 may also include, for example, the expiration date of the license.

In addition to the above, there are various types of licenses, such as processor licenses.

An "additional license" is a right (contract) that accompanies a license agreement. Examples of such rights include "upgrade rights" and "downgrade rights." Upgrade rights are the right to use software that is a higher version than the version of the software that has been licensed. Downgrade rights are the right to use software that is a lower version than the version of the software that has been licensed.

In addition to the above, there are various other additional licenses, such as the right to duplicate installations.

"Purchase date" is the date the license was purchased. "Management department" is the department that manages the license. "Administrator" is the person who manages the license. "Original license management ID" is the license management ID of the parent license (i.e. the license management ID of the software before the upgrade or downgrade) when the license contract includes upgrade or downgrade rights.

"Number of licenses held" is the number of licenses held. For example, if the number of licenses held is "10" and the license type is a "device license", this indicates that licenses for 10 devices are held. Similarly, if the number of licenses held is "10" and the license type is a "user license", this indicates that licenses for 10 users are held.

"Total number of uses" refers to the number of licenses actually being used out of the number of licenses held (i.e., licenses assigned to information devices 30 or users).

For example, when a new license agreement is concluded or when a license agreement expires, the administrator uses the administrator terminal 40 to add or delete records in the license management ledger information 250.

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

As shown in FIG. 8, the license allocation information 260 includes one or more records. Each record includes an "allocation management ID," a "hardware management ID," a "user ID," and a "license management ID."

The "allocation management ID" is an ID that uniquely identifies each record in the license allocation information 260. The "hardware management ID" is an ID that uniquely identifies the information device 30, as described above. The "user ID" is an ID that uniquely identifies the user who is using the information device 30, as described above. The "license management ID" is an ID that uniquely identifies a software license, as described above.

This allows management of which information device 30 a software license is assigned to which user. For example, a record with assignment management ID "AS01" indicates that a license with license management ID "LC01" has been assigned to a user (user ID "User A") who uses an information device 30 with hardware management ID "HW01."

For example, when a license allocation is added or deleted, the administrator uses the administrator terminal 40 to add or delete a record in the license allocation information 260.

<Automatic Registration Condition Information 270>
Next, the automatic registration condition information 270 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the automatic registration condition information 270.

As shown in FIG. 9, the automatic registration condition information 270 includes one or more records. Each record includes a "software name," a "manufacturer name," a "type," an "automatic registration category," and a "software category."

As described above, "software name" is the name of the software. The software names included in the records of the automatic registration condition information 270 are software names normalized using the software dictionary information 280. However, the software names may be unnormalized. Furthermore, the automatic registration condition information 270 may contain a mixture of records containing normalized software names and records containing unnormalized software names.

As mentioned above, "Manufacturer name" is the name of the software manufacturer. "Type" is the type of software.

The "automatic registration category" is a category that indicates whether or not software that is not managed in the software asset management ledger is to be registered as an asset in the software asset management ledger when the software is installed on the information device 30. If the automatic registration category is "automatic registration", the software is registered in the software asset management ledger. On the other hand, if the automatic registration category is "alert", an alert is notified to, for example, the administrator terminal 40 or the relevant information device 30. As described above, the "software category" is a category that classifies software assets.

For example, if software named "PresentationA" is installed on information device 30 but is not registered in the software asset management ledger, the software is registered in the software asset management ledger with the software classification as "standard software."

Note that the "*" in the software name represents any character string. For example, if the software name is "Update*", software with names such as "Update20171201" or "Update20171210" (for example, updates for a certain piece of software) can be registered in the software asset management ledger with the software classification as "unmanaged software".

<Automatic registration process to software asset management ledger>
Hereinafter, a process of registering software that is not managed in the software-asset management ledger in the software-asset management ledger when the software is installed in an information device 30 will be described with reference to Fig. 10. Fig. 10 is a flow chart showing an example of an automatic registration process in the software-asset management ledger. Note that the automatic registration process shown in Fig. 10 is executed, for example, for each piece of software inventory information 220 collected on an information device 30 basis (i.e., for each information device 30).

First, the acquisition unit 111 of the registration processing unit 110 acquires one record from the software inventory information 220 stored in the memory unit 130 (step S101).

Next, the normalization unit 112 of the registration processing unit 110 normalizes the software name contained in the record acquired by the acquisition unit 111 by referring to the software dictionary information 280 (step S102).

Next, the registration unit 113 of the registration processing unit 110 refers to the software asset management ledger information 240 and determines whether or not a software asset with the software name normalized by the normalization unit 112 is registered in the software asset management ledger (step S103). That is, the registration unit 113 determines whether or not a record including the software name normalized in step S102 above exists in the software asset management ledger information 240.

If it is determined in step S103 that a software asset with that software name is registered in the software asset management ledger, the registration processing unit 110 proceeds to step S105.

On the other hand, if it is determined in step S103 that a software asset with that software name is not registered in the software asset management ledger, the registration unit 113 of the registration processing unit 110 refers to the automatic registration condition information 270 and registers the software with that software name as an asset in the software asset management ledger in a software classification according to the automatic registration condition information 270 (step S104).

In other words, the registration unit 113 refers to the automatic registration condition information 270, identifies the software category that corresponds to the software name, and then adds a record that includes the identified software category and the software name to the software asset management ledger information 240.

For example, if the software name is "Editsoft C", the software category "standard software" is identified by referring to the automatic registration condition information 270. Therefore, the registration unit 113 creates a record including the software name "Editsoft C" and the software category "standard software" and adds it to the software asset management ledger information 240. At this time, the manufacturer name, version, etc. of the record may be obtained from the automatic registration condition information 270 or from the software inventory information 220. Alternatively, the manufacturer name, version, etc. of the record may be left blank.

For example, if the software name is "Update20171211", the software category "unmanaged software" is identified by referring to the automatic registration condition information 270. Therefore, the registration unit 113 creates a record including the software name "Update20171211" and the software category "unmanaged software" and adds it to the software asset management ledger information 240.

As described above, software with that software name is registered in the software asset management ledger when the automatic registration category "automatic registration" is associated with that software name in the automatic registration condition information 270. If the automatic registration category "alert" is associated with that software name, the registration unit 113 does not register the software in the software management ledger, but instead sets a specific flag for notifying an alert to "1", for example. In the alert processing described below, by referencing this flag, the alert notification unit 122 notifies the administrator terminal 40 and the relevant information device 30 of an alert.

Next, the acquisition unit 111 of the registration processing unit 110 determines whether all records have been acquired from the software inventory information 220 (step S105).

In step S105, if there are records in the software inventory information 220 that have not yet been acquired, the registration processing unit 110 returns to step S101. As a result, the above steps S102 to S104 are executed for all records included in the software inventory information 220.

On the other hand, if it is determined in step S105 that all records have been obtained from the software inventory information 220, the registration processing unit 110 terminates the automatic registration process to the software asset management ledger.

As described above, when software that is not managed in the software asset management ledger is installed in the information device 30 (i.e., when the software name of the software that is not managed in the software asset management ledger is included in the software inventory information 220), the management device 10 according to this embodiment can register the software in the software asset management ledger. As a result, the management device 10 according to this embodiment can facilitate the administrator's registration work in the software asset management ledger.

In particular, when updates, device drivers, etc. are installed on the information device 30, the management device 10 according to this embodiment registers the software classification of the software as "unmanaged software" in the software asset management ledger. Therefore, for example, when software for which updates are frequently provided is installed on the information device 30, the burden of software management on the administrator can be reduced.

<Alert notification processing>
Hereinafter, a process for issuing an alert when an IT resource is not being used appropriately will be described with reference to Fig. 11. Fig. 11 is a flowchart showing an example of an alert notification process.

First, the determination unit 121 of the alert notification processing unit 120 refers to various information stored in the memory unit 130 (hardware inventory information 210, software inventory information 220, hardware asset management ledger information 230, software asset management ledger information 240, license management ledger information 250, and license allocation information 260) to determine whether the alert notification conditions are met (step S201).

The determination unit 121 may determine that the alert notification conditions are met in the cases shown in (1) to (12) below, for example.

(1) When the hardware inventory information 210 cannot be associated with a record in the hardware asset management ledger information 230 by the hardware management ID.

(2) When, among the records in the hardware asset management ledger information 230, a record that can be associated with the hardware inventory information 210 has a status of "idle" or "discarded."

(3) When, among the records in the hardware asset management ledger information 230, a record that can be associated with the hardware inventory information 210 has a status of "in use" and the hardware inventory information 210 has not been collected for a specified period (e.g., 30 days) or longer.

(4) If the software name cannot be normalized in step S102 of FIG. 10 (i.e., if software name matching cannot be performed).

(5) When the software name can be normalized in step S102 of FIG. 10, and it is determined in step S103 above that a software asset with that software name is not registered in the software asset management ledger. At this time, the above-mentioned flag may also be referenced and the flag may be set to "1."

(6) When the software inventory information 220 contains a record indicating software whose software classification is "unauthorized software" in the software asset management ledger information 240.

(7) When the software inventory information 220 contains a record indicating software whose software classification is "prohibited software" in the software asset management ledger information 240.

(8) When a license management ID is not associated in the license allocation information 260 with an information device 30 on which software indicated by a record included in the software inventory information 220 is installed (i.e., when a license is not assigned to the software installed on the information device 30).

(9) When a user of the information device 30 has requested the use of the software, but the software inventory information 220 does not contain a record indicating the software for which the request for use has been made.

(10) When software with an expired license exists (i.e., when the software inventory information 220 contains a record indicating software with an expired license).

(11) When there is software whose license is about to expire (i.e., when the software inventory information 220 contains a record indicating software whose license is about to expire). Note that when a license is about to expire, it means, for example, that there are only a few days left until the license expires.

(12) When the total number of licenses assigned to the software exceeds the number owned (i.e., when a record exists in the license management ledger information 250 where the total number of uses > the number of owned licenses).

Next, the alert notification unit 122 determines whether or not there is an alert notification condition that satisfies the condition (step S202). That is, the alert notification unit 122 determines whether or not there is an alert notification condition that satisfies the condition among the above alert notification conditions (1) to (12).

If it is determined in step S202 that no satisfying alert notification conditions exist, the alert notification processing unit 120 terminates the alert notification process.

On the other hand, if it is determined in step S202 that a satisfying alert notification condition exists, the alert notification unit 122 of the alert notification processing unit 120 notifies at least one of the administrator terminal 40 and the corresponding information device 30 of an alert corresponding to the satisfying alert notification condition (step S203). Note that for each alert, it is preset whether the alert is notified to both the administrator terminal 40 and the information device 30, the alert is notified only to the administrator terminal 40, or the alert is notified only to the information device 30.

As an example, FIG. 12 shows an alert list screen G100 that shows a list of alerts notified to the administrator terminal 40 or the information device 30, and an alert details screen G200 that shows details of an alert selected from the alert list screen G100. FIG. 12 shows an example of the alert list screen G100 and the alert details screen G200.

As shown in FIG. 12(a), the alert list screen G100 displays a list of alerts notified from the management device 10. Also, as shown in FIG. 12(b), the alert details screen G200 displays detailed information about the alerts.

By referring to the alert list screen G100 and the alert details screen G200, the administrator can learn that an IT asset is not being used appropriately and find out the details of that asset. Therefore, the administrator can take measures such as requesting the user of the information device 30 to make corrections so that the IT asset is used appropriately.

In addition, users of the information device 30 can also refer to the alert list screen G100 and the alert details screen G200 to know that they are not using IT assets appropriately and can take steps to correct this.

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

REFERENCE SIGNS LIST 1 Asset management system 10 Management device 20 Collection device 30 Information device 40 Administrator terminal 110 Registration processing unit 111 Acquisition unit 112 Normalization unit 113 Registration unit 120 Alert notification processing unit 121 Determination unit 122 Alert notification unit 130 Storage unit 210 Hardware inventory information 220 Software inventory information 230 Hardware asset management ledger information 240 Software asset management ledger information 250 License management ledger information 260 License allocation information 270 Automatic registration condition information 280 Software dictionary information

Claims (5)

A management device for managing software assets installed in a plurality of information devices,
a first determination means for determining whether or not the software installed in the information device is managed in a software asset management ledger;
a registration means for, when the first determination means determines that the software is not managed in the software-asset management ledger, registering information about the software in the software-asset management ledger in association with a category into which the software is classified and which is used to determine whether the software is being used appropriately; and
having
The above classification includes:
a first classification indicating that the software is authorized for use on the information device and is being used appropriately;
a second classification indicating that the software is prohibited from use on the information device and is subject to an alert notification as an inappropriate software use;
A third category indicates that the use of the software requires prior application, and that if prior application is not made, the software is subject to an alert as it is an inappropriate use of the software;
and a fourth category indicating that the software is an update program for other software or a device driver, and that the software is not subject to a determination of whether or not it is being used appropriately. A management device for managing software assets installed in a plurality of information devices,
a first determination means for determining whether or not the software installed in the information device is managed in a software asset management ledger;
a registration means for, when the first determination means determines that the software is not managed in the software-asset management ledger, registering information about the software in the software-asset management ledger in association with a category into which the software is classified and which is used to determine whether the software is being used appropriately; and
a first alert notification means for notifying a predetermined notification destination of a first alert regarding the software;
a second alert notification means for notifying the notification destination of a second alert regarding the hardware when a usage state of the information device is "discarded" or "idle" at the time when information regarding the hardware of the information device is collected;
a third alert notification means for notifying the notification destination of a third alert regarding the hardware when a usage state of the information device is in use and information regarding the hardware of the information device has not been collected for a certain period of time or more;
having
The first alert notification means includes:
A management device that notifies the first alert when the first determination means determines that the software is not managed in the software asset management ledger and the automatic registration condition included in the information regarding the software indicates that an alert notification should be issued. A management device that manages software assets installed in a plurality of information devices,
a first determination step of determining whether or not the software installed in the information device is managed in a software asset management ledger;
a registration step of, when it is determined in the first determination step that the software is not managed in the software-asset management ledger, correlating information about the software with a category into which the software is classified and which is used to determine whether the software is being used appropriately, and registering the information in the software-asset management ledger;
Run
The above classification includes:
a first classification indicating that the software is authorized for use on the information device and is being used appropriately;
a second classification indicating that the software is prohibited from use on the information device and is subject to an alert notification as an inappropriate software use;
A third category indicates that the use of the software requires prior application, and that if prior application is not made, the software is subject to an alert as it is an inappropriate use of the software;
and a fourth category indicating that the software is an update program or a device driver for other software and is not subject to a determination of whether the software is being used appropriately. A management device that manages software assets installed in a plurality of information devices,
a first determination step of determining whether or not the software installed in the information device is managed in a software asset management ledger;
a registration step of, when it is determined in the first determination step that the software is not managed in the software-asset management ledger, correlating information about the software with a category into which the software is classified and which is used to determine whether the software is being used appropriately, and registering the information in the software-asset management ledger;
a first alert notification procedure for notifying a predetermined notification destination of a first alert regarding the software;
a second alert notification step of notifying the notification destination of a second alert regarding the hardware when a usage state of the information device is "discarded" or "idle" when information regarding the hardware of the information device is collected;
a third alert notification step of notifying the notification destination of a third alert regarding the hardware when a usage state of the information device is in use and information regarding the hardware of the information device has not been collected for a certain period of time or more;
Run
The first alert notification procedure includes:
A management method comprising: notifying the first alert when the first judgment procedure determines that the software is not managed in the software asset management ledger and when an automatic registration condition included in the information relating to the software indicates that an alert notification should be issued. A program that causes a computer to function as the management device according to claim 1 or 2.

Images