JP6507880B2 - Asset management device, asset management system and program - Google Patents

Description

  The present invention relates to an asset management device, an asset management system, and a program.

  According to Patent Document 1, an information processing apparatus storing a definition file defined for each electric appliance receives a packet for determining the type of the electric appliance, and compares the received packet with the definition file for each electric appliance. Score files, extract definition files with high scores, set the product information in the definition file as the product information of the product, and associate the product information with the ID of each information processing apparatus or each user who manages the information processing apparatus And the server generates the belongings list in which the electric appliance information is listed according to each ID, and transmits the belongings list to the terminal requesting the browsing. A system is disclosed.

Patent No. 05031864 gazette

When managing assets such as devices used in an office or the like, there may be devices of all types, or a plurality of devices from old devices to new devices may be mixed. Under such circumstances, it has been difficult in some cases to determine the type of asset based only on the information of the device acquired from the packet or the like when the device communicates.
An object of the present invention is to facilitate accurate determination of the type of asset as compared to the case where the type of asset is determined only by the information of the device.

The invention according to claim 1 is an acquisition means for acquiring computerized information of an accessory attached to an asset to be managed, and accessory information of an accessory attached to an asset classified into a predetermined asset type. It is an asset management apparatus provided with the determination means which determines the asset classification of the asset of the said management object using the said computerization information which the said acquisition means acquires.
In the invention according to claim 2, an accessory attached to an asset classified into the predetermined asset type by comparison between the accessory information and information specified from the computerized information. The asset management device according to claim 1, wherein an accessory that matches or is similar to an accessory attached to the asset to be managed is identified.
The invention according to claim 3 is characterized in that the determination means is an attachment that matches or is similar to the attachment attached to the asset to be managed among the accessories attached to the asset classified into the predetermined asset type. 3. The asset management apparatus according to claim 1, wherein it is determined whether or not the asset type of the asset to be managed is determined to be the predetermined asset type in accordance with the ratio of the product. .
The invention according to claim 4 is a storage means for storing a correspondence relationship in which the predetermined asset type and accessories attached to the asset classified into the predetermined asset type are associated for each asset type. The asset management apparatus according to any one of claims 1 to 3, further comprising:
The invention according to claim 5 is that, when the accessory indicated in the correspondence relationship includes an accessory that matches or is similar to an accessory attached to the asset to be managed, the determination means If the assets of the category are classified into the same or similar asset type of the corresponding accessories, and if the accessories indicated in the correspondence do not have an accessory that matches or is similar to the accessories attached to the managed asset, The asset management device according to claim 4, wherein the asset to be managed is classified into a new asset type.
The invention according to claim 6 is an accessory attached to the asset to be managed, when there is no accessory corresponding to the accessory attached to the asset to be managed among the accessories indicated in the correspondence relationship. If the computerized information of a new item is registered and there is an accessory that matches the accessory attached to the asset to be managed among the accessories indicated in the correspondence relationship, the attachment to be attached to the asset to be managed 6. The asset management apparatus according to claim 4, further comprising a registration unit that does not newly register the computerization information of the product.
The invention according to claim 7 is characterized by further comprising presentation means for presenting the asset type of the asset to be managed determined by the determination means as a selectable asset type candidate to the user. An asset management apparatus according to any one of Items 1 to 6.
The invention according to claim 8 is an acquisition means for acquiring computerized information of an accessory attached to an asset to be managed, and accessory information of an accessory attached to an asset classified into a predetermined asset type. An asset management apparatus having determination means for determining an asset type of the asset to be managed using the computerization information acquired by the acquisition means, and a plurality of asset management apparatuses connected via the network; An asset comprising: a server device that collects accessory information of accessories attached to each of assets classified by asset type from a plurality of asset management devices and provides the collected accessory information to each asset management device It is a management system.
The invention according to claim 9 is characterized in that the determination means of the asset management apparatus uses the server apparatus for the accessory information of an accessory attached to each asset classified for each asset type by another asset management apparatus. The asset management system according to claim 8, wherein the asset type of the asset to be managed is determined by further using the acquired accessory information acquired.
The invention according to claim 10 is characterized in that the computer has a function of acquiring computerized information of an accessory attached to an asset to be managed, and an accessory of an accessory attached to an asset classified into a predetermined asset type. It is a program for realizing a function of determining an asset type of the asset to be managed using information and the acquired electronic information.

According to the first aspect of the present invention, it is easy to accurately determine the type of asset as compared to the case where the type of asset is determined only by the information of the device.
According to the second aspect of the present invention, it is possible to increase the possibility that the determination of the type of the asset can be accurately performed, as compared to the case where the type of the asset is determined only by the information of the device.
According to the invention of claim 3, compared with the case where the type of asset is determined only by the information of the device, the possibility of the determination of the type of asset being performed can be increased.
According to the fourth aspect of the present invention, it is possible to more reliably determine the type of asset as compared with the case where the type of asset is determined only by the information of the device.
According to the fifth aspect of the present invention, it is possible to increase the possibility that the determination of the type of asset can be accurately performed as compared with the case where the type of asset is determined only by the information of the device.
According to the sixth aspect of the present invention, the storage capacity can be effectively used as compared with the case where the electronic information of the accessory is registered in duplicate.
According to the seventh aspect of the present invention, it is possible to accurately determine the type of asset even if, for example, the information on the acquired accessory is insufficient.
According to the eighth aspect of the present invention, it is easy to accurately determine the type of asset as compared to the case where the type of asset is determined only by the information of the device.
According to the invention of claim 9, compared with the case where the type of the asset is determined only by the information of the device, the possibility that the determination of the type of the asset is accurately performed can be enhanced.
According to the tenth aspect of the present invention, it is possible to realize the function of facilitating accurate determination of the type of asset as compared with the case where the type of asset is determined only by the information of the device, by a computer.

BRIEF DESCRIPTION OF THE DRAWINGS It is the figure which showed the example of whole structure of the asset management system which concerns on this Embodiment. It is a figure showing an example of hardware constitutions of an asset management server concerning this embodiment. It is a block diagram showing an example of functional composition of an asset management server concerning this embodiment. It is a figure which shows an example of asset information DB. It is a figure which shows an example of asset type DB. It is a figure which shows an example of accessory information DB. It is the flowchart which showed an example of the procedure of the process which an asset management server performs. It is the flowchart which showed an example of the procedure of the error detection process by an error detection part. It is the flowchart which showed an example of the procedure of the registration process to accessory information DB by an accessory information recording part. It is a figure which shows the structural example which has arrange | positioned the cloud server. It is a block diagram showing an example of functional composition of a cloud server. (A), (b) is a figure for demonstrating the specific example of the process by a cloud server.

Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.
<System configuration>
First, the overall configuration of the asset management system 1 according to the present embodiment will be described. FIG. 1 is a diagram showing an example of the overall configuration of an asset management system 1 according to the present embodiment. The asset management system 1 is a system that manages information of assets such as equipment used in, for example, an office or the like. As illustrated, in the asset management system 1, an asset management server 100 and terminal devices 200a, 200b, and 200c are connected to a network 300.

  The asset management server 100 is a server device that manages asset information. The assets managed here are, for example, devices (hardware) such as a PC (Personal Computer), a projector, and a printer. In addition, equipment such as a USB (Universal Serial Bus) memory connected to a PC or the like, an external HDD, etc. is included in the assets. Furthermore, software such as an application used in various devices may be managed as an asset. In the present embodiment, the asset management server 100 is used as an example of the asset management apparatus.

  The terminal devices 200 a, 200 b, and 200 c are, for example, PCs, and are devices to be managed by the asset management server 100. Although FIG. 1 shows an example where the terminal devices 200a to 200c are PCs, as described above, the terminal devices 200a, 200b, and 200c are managed as assets by the asset management server 100, such as a printer and a USB memory. Any kind of object may be used.

  The network 300 is a communication means used for information communication between the asset management server 100 and the terminal devices 200a, 200b, and 200c, and is, for example, a LAN (Local Area Network).

  Then, in the present embodiment, the asset management server 100 classifies and manages each of the terminal devices 200 as the type of asset. At this time, the asset management server 100 classifies the terminal device 200 using information (electronic information) of an accessory attached to the terminal device 200 instead of using only the device information on the terminal device 200. Here, the accessories include, for example, a manual regarding the terminal device 200, a recording medium (installation medium) such as a CD-ROM in which a program for installing software in the terminal device 200 is recorded, a driver of the terminal device 200, etc. It is.

  Although FIG. 1 shows the terminal devices 200a, 200b, and 200c, they may be referred to as a terminal device 200 when it is not necessary to distinguish them. Although only three terminal devices are shown in FIG. 1, the number of terminal devices 200 is not limited to three as shown.

<Hardware configuration of asset management server>
Next, the hardware configuration of the asset management server 100 will be described. FIG. 2 is a diagram showing an example of the hardware configuration of the asset management server 100 according to the present embodiment. As illustrated, the asset management server 100 includes a central processing unit (CPU) 101 as an arithmetic unit, a main memory 102 as a storage unit, and a hard disk drive (HDD: hard disk drive) 103.

  Here, the CPU 101 executes various programs such as an operating system (OS) and applications to realize each function of the asset management server 100. The main memory 102 is a storage area for storing various programs, data used for the execution thereof, and the like. The magnetic disk drive 103 is a storage area for storing input data for various programs, output data from various programs, and the like. The asset management server 100 further includes a communication I / F 104 for communicating with the outside, a display mechanism 105 including a video memory and a display, and an input device 106 such as a keyboard and a mouse.

<Functional configuration of asset management server>
Next, the functional configuration of the asset management server 100 will be described. FIG. 3 is a block diagram showing an example of a functional configuration of the asset management server 100 according to the present embodiment. The asset management server 100 includes a device detection unit 111, an asset information input unit 112, an asset information recording unit 113, an accessory information recording unit 114, a feature information extraction unit 115, a type determination unit 116, and an error detection unit. An asset type correction unit 118 and a database storage unit 119 are provided.

  The device detection unit 111 detects a terminal device 200 connected to the asset management server 100 via the network 300. Here, for example, when the terminal device 200 is connected to the network 300, the device detection unit 111 transmits and receives data to and from the connected terminal device 200, and acquires device information of the terminal device 200. Here, for example, information that can be acquired automatically without input by the user, such as information on the OS of the terminal device 200 and the IP address, is acquired.

The asset information input unit 112 acquires device information on the terminal device 200 input by the user. Here, the asset information input unit 112 acquires the device information of the terminal device 200, for example, when the user manually inputs the device information of the terminal device 200 that has not been acquired by the device detection unit 111.
Further, the asset information input unit 112 also acquires information of accessories attached to the terminal device 200 such as a manual regarding the terminal device 200 based on the user's input.

  For example, the asset information input unit 112 manually inputs electronic data such as a manual regarding the terminal device 200 by the user, or downloads electronic data such as a manual from the Internet based on a URL (Uniform Resource Locator) input by the user. By doing so, the information on the accessories of the terminal device 200 is acquired. Further, the asset information input unit 112 may read a recording medium such as a CD-ROM to obtain electronic data such as a manual.

  The asset information recording unit 113 includes the device information of the terminal device 200 acquired by the device detection unit 111 and the asset information input unit 112, an asset information database (hereinafter referred to as an asset information DB), and an asset type database (hereinafter referred to as an asset). Record in type DB). In the asset information DB, device information related to the terminal device 200 is recorded for each terminal device 200. Further, in the asset type DB, information on the type of asset into which the terminal device 200 is classified is recorded for each type. In addition, in the asset type DB, an asset type and information of accessories attached to the asset classified into each asset type are associated with each asset type. Details of the information recorded in the asset information DB and the information recorded in the asset type DB will be described later.

  Among the information acquired by the asset information input unit 112, the accessory information recording unit 114 records information of an accessory attached to the terminal device 200 in an accessory information database (hereinafter referred to as an accessory information DB). . In the accessory information DB, information on accessories is recorded for each accessory. Details of the information recorded in the accessory information DB will be described later.

  The feature information extraction unit 115 extracts information indicating a feature (hereinafter, referred to as feature information) from the information of the accessory of the terminal device 200 among the information acquired by the asset information input unit 112. For example, in the case of a manual related to the terminal device 200, the feature information extraction unit 115 extracts information such as the name of the manual, the version (version) of the manual, the table of contents of the manual as feature information based on the electronic data of the manual. . Also, for example, in the case of the driver of the terminal device 200, the feature information extraction unit 115 extracts, for example, the directory configuration of the driver, the contents of the Readme file, and the like as the feature information.

  Here, the item extracted as feature information may not be determined in advance. When the item to be extracted is not determined in advance, for example, the feature information extraction unit 115 extracts all the words used in the text of the manual, and arranges the extracted words in the order of appearance frequency The thing is the feature information.

  The type determination unit 116 classifies the terminal device 200 into a specific asset type. Here, the type determination unit 116 determines the asset type of the terminal device 200 using the accessory information of the terminal device 200 manually input by the user instead of using only the device information of the terminal device 200. . Specifically, based on the feature information extracted by the feature information extraction unit 115, the type determination unit 116 agrees among the accessories registered in the accessory information DB regarding the accessory of the terminal device 200. Or determine whether there is something similar. The type determination unit 116 performs such similarity determination on all accessories of the terminal device 200. Then, when an accessory that matches or is similar to the accessory of the terminal device 200 (hereinafter collectively referred to as a similar product) is found by the similarity determination, the type determination unit 116 determines the type of the asset to which the similar product is attached; It is determined that the type of the terminal device 200 is the same.

  The error detection unit 117 executes a process of detecting an error of the determination result by the type determination unit 116 (hereinafter referred to as an error detection process).

  When the error detection unit 117 detects an error in the determination result, the asset type correction unit 118 presents the user with a candidate for an asset type into which the terminal device 200 is classified and causes the user to select one.

  The database storage unit 119 stores an asset information DB, an asset type DB, and an accessory information DB. In the present embodiment, an asset type DB is used as an example of the correspondence relationship.

  Note that these processing units are realized by cooperation of software and hardware resources. Specifically, the CPU 101 includes a device detection unit 111, an asset information input unit 112, an asset information recording unit 113, an accessory information recording unit 114, a feature information extraction unit 115, a type determination unit 116, an error detection unit 117, and an asset type. These processing units are realized by reading and executing a program for realizing the correction unit 118 and the like from the magnetic disk drive 103 to the main memory 102, for example. Also, the database storage unit 119 is realized by, for example, the magnetic disk drive 103.

  Here, in the present embodiment, the asset information input unit 112 has a function as an example of an acquisition unit. Also, the type determination unit 116 has a function as an example of the determination unit. Furthermore, the accessory information recording unit 114 has a function as an example of the registration unit. The asset type correction unit 118 has a function as an example of a presentation unit. Furthermore, the database storage unit 119 has a function as an example of a storage unit.

<Description of each database>
Next, each database (the asset information DB, the asset type DB, and the accessory information DB) of the asset management server 100 will be described by taking a specific example.

  FIG. 4 is a diagram showing an example of the asset information DB. "Asset ID" indicates an ID assigned to each terminal device 200 (that is, each asset), and in the asset information DB, "asset name", "category", "asset unique attribute" for each asset ID , “Asset type ID” and “accessory ID” are registered.

“Asset name” indicates the name of the terminal device 200. “Classification” indicates classification of the terminal device 200 as an asset. The “asset unique attribute” indicates a unique attribute that the terminal device 200 has, for example, the owner of the terminal device 200 and an organization to which the owner belongs. “Asset type ID” indicates an ID assigned to the asset type of the terminal device 200. “Accessory ID” indicates an ID given to each accessory attached to the terminal device 200.
Among these pieces of information, “asset name”, “division”, and “asset unique attribute” are information automatically acquired from the terminal device 200 or input by the user. The “asset ID”, “asset type ID”, and “accessory ID” are assigned by the asset management server 100.

For example, the terminal device 200 of the asset ID “0001” is a PC, and the asset name is registered as “PC1” and the category is “PC”. Also, the owner of the terminal device 200 is registered as "Mr. A", and the organization belonging to Mr. A is registered as a "Development Department". Further, the asset type ID of the terminal device 200 is "0001", and three accessory IDs "0001", "0002", and "0003" are registered.
Similarly, the terminal device 200 of the asset ID “0002” and the terminal device 200 of the asset ID “0003” are also registered as the asset type ID “0001”. That is, the three terminal devices 200 having asset IDs “0001” to “0003” have the same asset type ID, and it is determined that they are assets of the same type.

  Next, FIG. 5 is a diagram showing an example of the asset type DB. “Asset type ID” is the same item as the asset type ID of the asset information DB, and in the asset type DB, “division”, “type common attribute”, and “accessories ID” are registered for each asset type ID. Ru.

“Division” indicates the asset classification of the terminal device 200 classified into the corresponding asset type. The “type common attribute” indicates an attribute common to the terminal devices 200 classified into the corresponding asset type. “Accessory ID” indicates an accessory ID of an accessory that may be attached to the terminal device 200 classified into the corresponding asset type.
Among these pieces of information, the “division” is information that is automatically acquired from the terminal device 200 or input by the user. The “asset type ID” and the “accessory ID” are assigned by the asset management server 100. Furthermore, “type common attribute” is information extracted from an accessory registered in the asset type.

  For example, the terminal device 200 classified into the asset type ID “0001” is a PC, the classification is “PC”, the OS is “version 7”, and the manufacturer is registered as “company A”. There is. Moreover, five "0001"-"0005" are registered as accessory ID. Then, information of the OS “version 7” and the manufacturer “company A” of the type common attribute is extracted from these accessories.

  Further, for example, in the asset information DB of FIG. 4, the terminal devices 200 of asset IDs “0001” to “0003” are classified into the asset type ID “0001”, and the accessory IDs of the three terminal devices 200 are respectively , "0001, 0002, 0003", "0001, 0003, 0004", "0001, 0004, 0005". On the other hand, in the asset type DB of FIG. 5, five accessory IDs “0001” to “0005” are registered as an accessory that may be attached to the terminal device 200 classified as the asset type ID “0001”. It is done. In addition, it can be said that the five accessories of "0001" to "0005" include the accessories of three terminal devices 200 of asset IDs "0001" to "0003".

  Next, FIG. 6 is a diagram showing an example of the accessory information DB. "Accessory ID" is the same item as the accessory ID of the asset information DB, and in the accessory information DB, for each accessory ID (ie, for each accessory), "name", "by accessory type" , "Content" is registered.

"Name" indicates the name of the accessory. "By attachment type" indicates the type of accessories. "Content" is the content of the accessory. For example, when the accessory is a manual, the sentences and the like described in the manual are registered. Also, for example, when the accessory is a driver, a file of a driver such as Zip format is registered.
Among these pieces of information, “name”, “by accessory type”, and “content” are information input by the user. The “accessory ID” is assigned by the asset management server 100.

  For example, the accessory of the accessory ID “0001” is registered with the name “Operation Manual 1.0 for PC model A”, and the classification by accessory as “Manual”. In addition, according to the asset information DB of FIG. 4 and the asset type DB of FIG. 5, this accessory is a manual of the terminal device 200 classified to the asset type ID “0001”, and the asset IDs “0001” to “0003” It can be said that it is an accessory attached to each of the three terminal devices 200.

  In such three databases, information of the terminal device 200 newly detected is registered as needed in the asset information DB. The asset type DB and the accessory information DB are used when determining the asset type of the terminal device 200 detected anew. In the determination of the asset type, when the terminal device 200 to be determined is not classified into any of the asset types registered in the asset type DB, a new asset type (asset type ID) is added to the asset type DB. Moreover, if the same thing as the accessory of the terminal device 200 is already registered in the accessory information DB, it is not newly added to the accessory information DB, but if it has not been registered yet, the accessory information DB A new accessory (accessory ID) is added.

<Procedure of processing by asset management server>
Next, the procedure of processing executed by the asset management server 100 will be described. FIG. 7 is a flowchart showing an example of the procedure of processing executed by the asset management server 100. Here, it is assumed that the terminal device 200a is newly connected to the network 300.

  First, when the terminal device 200a is connected to the network 300, the device detection unit 111 detects the connected terminal device 200a, and acquires device information of the terminal device 200a that can be acquired by automatic acquisition (step 101). Next, the asset information input unit 112 acquires device information on the terminal device 200a manually input by the user and information on accessories attached to the terminal device 200a (step 102). Here, for example, the asset information input unit 112 displays on the display that the terminal device 200 a has been detected, and prompts the user to input information on the terminal device 200 a and the accessory, thereby causing the user to use the terminal device 200 a or Enter the accessory information.

  Next, the feature information extraction unit 115 extracts feature information from the information on the accessory of the terminal device 200a acquired by the asset information input unit 112 (step 103). Next, the type determination unit 116 compares the feature information extracted by the feature information extraction unit 115 with the feature information of each accessory registered in the accessory information DB to search for a similar item (step 104). ). Here, the type determination unit 116 calculates the degree of similarity between the accessory of the terminal device 200a and the accessory registered in the accessory information DB by comparing the feature information (hereinafter referred to as the similarity). . Then, if the calculated degree of similarity exceeds the predetermined threshold value, the type determination unit 116 determines that the accessory registered in the accessory information DB matches or resembles the accessory of the terminal device 200a. It is determined that

  For example, when the feature information extraction unit 115 extracts the name of the manual and the table of contents of the manual, the type determination unit 116 compares the extracted name and table of contents with the name and table of contents of the manual registered in the accessory information DB. Do. Then, for example, if the names are the same but the table of contents is different, the type determination unit 116 calculates the similarity as 10%, or if the names are the same and only a few items in the table of contents differ, the similarity is calculated as 90% To The type determination unit 116 calculates, for one accessory attached to the terminal device 200a, the degree of similarity with all the accessories registered in the accessory information DB. In addition, when there are a plurality of accessories attached to the terminal device 200a, the type determination unit 116 calculates, for each of the accessories, the similarity with the accessory of the accessory information DB.

  Thus, the type determination unit 116 determines whether a similar item is found for the accessory of the terminal device 200a (step 105). When it is determined that the similar product is not found (No in Step 105), the type determination unit 116 determines that the terminal device 200a is classified into a new asset type. Then, the asset information recording unit 113 adds the terminal device 200a to the asset information DB and the asset type DB as an asset classified as a new asset type (Step 106). Specifically, the asset information recording unit 113 assigns a new asset ID and a new asset type ID to the terminal device 200a, assigns the new asset type ID, and links the new asset type ID to the device information of the terminal device 200a. Add to information DB and asset type DB. Further, the accessory information recording unit 114 performs registration processing in the accessory information DB for each accessory of the terminal device 200a (step 107), and the processing flow ends. In addition, the detail of the registration process to accessory information DB is mentioned later.

  On the other hand, when it is determined in step 105 that a similar product is found (Yes in step 105), next, the error detection unit 117 executes an error detection process (step 108). In this error detection process, when the asset type of the terminal device 200a is specified as one, it is determined that no error is detected, and when a plurality of asset types are calculated, it is determined that an error is detected. The detailed procedure of the error detection process will also be described later.

  Next, the type determination unit 116 determines whether an error has been detected by the error detection process (step 109). If it is determined that no error is detected (No in Step 109), it means that the asset type of the terminal device 200a is specified as one in the error detection processing. In this case, the type determination unit 116 determines whether or not the ratio of similar items among the accessories of the specified asset type exceeds a predetermined threshold (step 110). For example, in the case where the asset type ID is specified as "0001" shown in FIG. 5, if there are three similar items similar to the accessory of the terminal device 200a among the five accessories, the ratio of 3/5 Is determined to be similar. Here, if the predetermined threshold value is, for example, 50%, it is determined that the predetermined threshold value is exceeded.

  When it is determined in step 110 that the predetermined threshold value is exceeded (Yes in step 110), the type determination unit 116 determines that the terminal device 200a is classified into one specified asset type. Then, the asset information recording unit 113 adds the device information of the terminal device 200a to the asset information DB (step 111). Specifically, the asset information recording unit 113 adds a new asset ID to the terminal device 200a, and adds information of the terminal device 200a to the asset information DB. The asset information recording unit 113 also acquires an asset type ID of the identified asset type from the asset type DB, and registers the acquired asset type ID in the asset information DB as information of the terminal device 200a. Then, the process proceeds to step 107.

  On the other hand, when it is determined in step 110 that the predetermined threshold is not exceeded (No in step 110), the type determination unit 116 determines that the terminal device 200a is classified into a new asset type. Then, the process proceeds to step 106.

  When it is determined in step 109 that an error has been detected (Yes in step 109), the asset type correction unit 118 presents the user with a candidate for the asset type of the terminal device 200 and causes the user to select (step 112). Here, since a plurality of asset type IDs are calculated in the error detection process, the asset type correction unit 118 sets the calculated plurality of asset type IDs as candidates, and uses the information of accessories of each asset type as a user. To present. When one of the asset types is selected by the user, the process proceeds to step 111. Further, in step 112, a plurality of asset types may be presented, and it may be possible to select to treat as a new asset type. Here, when the user selects to treat as a new asset type, the process proceeds to step 106.

  Further, in step 110 described above, the type determination unit 116 determines whether the ratio of similar items among the accessories of the specified asset type exceeds a predetermined threshold value, but The configuration is not limited to the above. For example, the type determination unit 116 may determine whether the ratio of the similar item among the accessories of the terminal device 200a exceeds a predetermined threshold. For example, if there are three accessories of the terminal device 200 a and two of them are similar to the accessories of the asset type ID “0001”, it is determined that the two are similar at a ratio of 2/3.

<Procedure of error detection process>
Next, the procedure of the error detection process by the error detection unit 117 will be described. FIG. 8 is a flowchart showing an example of the procedure of the error detection process by the error detection unit 117. Here, as in FIG. 7, description will be made on the assumption that error detection on the terminal device 200 a is performed.

  First, the error detection unit 117 selects one accessory not selected yet from the accessories of the terminal device 200a (step 201). Next, the error detection unit 117 determines, among the accessories registered in the accessory information DB, whether there is a similar product whose similarity to the selected accessory exceeds a predetermined threshold value (see FIG. Step 202). For the determination here, the processing result of step 104 in FIG. 7 may be used. If it is determined that a similar product exists (Yes in step 202), the error detection unit 117 acquires an asset type (asset type ID) associated with the similar product from the asset type DB (step 203). On the other hand, when it is determined that the similar product does not exist (No in Step 202), or after Step 203, the error detection unit 117 determines whether all the accessories of the terminal device 200a have been selected (Step 204). ).

  If it is determined that there is an accessory that has not been selected yet (No in step 204), the process proceeds to step 201. On the other hand, when it is determined that all the accessories have been selected (Yes in step 204), the error detection unit 117 determines whether there are multiple asset types acquired in step 203 (step 205). If it is determined that the asset type is not plural but only one (No at step 205), the error detection unit 117 determines that no error is detected (step 206). On the other hand, if it is determined that there are a plurality of asset types (Yes in step 205), there is a possibility that, for example, accessory information is erroneously input to the user, and the error detection unit 117 determines that there is an error detection (step 207). Then, the process flow ends.

Further, in step 205 described above, when it is determined that there is only one asset type (No in step 205), the error detection unit 117 determines that no error is detected. Similar to 110, it may be determined whether the proportion of similar products exceeds a predetermined threshold. In this case, if it is determined that the ratio of similar products exceeds a predetermined threshold, it is determined that no error is detected, and if it is determined that the ratio of similar products does not exceed a predetermined threshold, an error is made. It is determined that there is a detection.
Here, if it is determined that there is an error detection, it is confirmed in step 112 of FIG. 7 by the user whether, for example, one specified asset type ID is acceptable. Also, a new asset type may be selected.

<Procedure of registration process to accessory information DB>
Next, the registration process to the accessory information DB by the accessory information recording unit 114 will be described. FIG. 9 is a flowchart showing an example of the procedure of registration processing to the accessory information DB by the accessory information recording unit 114. Here, as in FIG. 7, description will be made assuming that registration processing for the terminal device 200 a is performed.

  First, the accessory information recording unit 114 selects one accessory of the terminal device 200a not selected yet among the accessories of the terminal device 200a (step 301). Next, the accessory information recording unit 114 determines whether or not there is an accessory registered in the accessory information DB that completely matches the selected accessory (step 302). The perfect match means that the degree of similarity is 100%, and for the determination here, the processing result of step 104 in FIG. 7 may be used. If there is a completely matched accessory (similar product) (Yes in step 302), the selected accessory is already registered in the accessory information DB. That is, there is no need to add information to the accessory information DB, and the process proceeds to step 306 described later.

  On the other hand, if there is no accessory that completely matches (No in step 302), the accessory information recording unit 114 determines whether there is a similar item similar to the selected accessory (step 303). For the determination here, the processing result of step 104 in FIG. 7 may be used. If there is a similar item (Yes in step 303), the accessory information recording unit 114 adds the information of the selected accessory to the accessory information DB as another version of the found similar item (step 304). Specifically, the accessory information recording unit 114 assigns a new accessory ID to the selected accessory, and registers the accessory information in the accessory information DB.

  On the other hand, when there is no similar item (No in step 303), the accessory information recording unit 114 adds information of the selected accessory as a new accessory to the accessory information DB (step 305). Specifically, as in step 304, the accessory information recording unit 114 assigns a new accessory ID to the selected accessory, and registers the accessory information in the accessory information DB. After step 304 and step 305, the accessory information recording unit 114 determines whether all the accessories of the terminal device 200a have been selected (step 306). If it is determined that there is an accessory that has not been selected yet (No in step 306), the process proceeds to step 301. On the other hand, when it is determined that all the accessories have been selected (Yes in step 306), this processing flow ends.

  Here, by appending the accessory ID to the accessory of the terminal device 200a, the asset information recording unit 113 registers the information of the accessory ID in the asset information DB and the asset type DB. In addition, the asset information recording unit 113 registers, in the asset information DB, the accessory ID given to the accessory in the “Accessory ID” field of the terminal device 200a. In addition, the asset information recording unit 113 registers the accessory ID given to the accessory in the column of “Accessory ID” of the asset type ID in which the terminal device 200a is classified in the asset type DB.

<Specific example of processing by asset management server>
Next, processing by the asset management server 100 will be described by taking a specific example. In the processing of this specific example, the asset information DB shown in FIG. 4, the asset type DB shown in FIG. 5, and the accessory information DB shown in FIG. 6 will be described. The following steps correspond to the respective steps in FIG.

  First, in the first specific example, it is assumed that the terminal device 200a is newly connected to the network 300. Then, the user inputs the information of the accessory of the terminal device 200a. Here, accessories of the terminal device 200a are a manual A, a manual B and a driver C. Also, as a result of the search for similar products in step 104, the manual A completely matches the manual of the accessory ID "0001" in FIG. 6, and the manual B is 95% similar to the manual of the accessory ID "0004". It is assumed that the driver C completely matches the driver of the accessory ID "0005".

  In this case, if the degree of similarity 95% exceeds the predetermined threshold value in step 104, the type determination unit 116 determines that the manual B is similar to the manual of the accessory ID "0004". Further, in the error detection process of step 108, from the asset type DB of FIG. 5, the asset type associated with the accessory IDs “0001”, “0004”, and “0005” is only one of the asset type ID “0001”. Specific to Therefore, it is determined that no error has been detected (No in step 109).

  Here, the ratio of similar items among the five accessories of the asset type ID "0001" is 3/5, and if this value exceeds a predetermined threshold (Yes in step 110), the terminal device The asset type ID of 200a is determined to be "0001". Then, the asset information recording unit 113 links the asset type ID “0001”, and adds the device information of the terminal device 200a to the asset information DB (step 111). In addition, the manual A and the driver C are not added to the accessory information DB because they completely correspond to those already registered in the accessory information DB. On the other hand, since the manual B is 95% similar, the manual B is newly registered in the accessory information DB as a version different from the manual of the accessory ID "0004" (step 107).

  When, for example, “1000” is given as the accessory ID of the manual B, “0001” of the manual A and “1000” of the manual B are displayed in the “accessory ID” column of the terminal device 200 a in the asset information DB. And “0005” of the driver C are registered. In the asset type DB, “0001” of manual A and “0005” of driver C have already been registered in the “Accessory ID” column of asset type ID “0001”, but “1000” of manual B Is not registered yet, "1000" is newly registered.

  Next, in the second specific example, it is assumed that the terminal device 200b is newly connected to the network 300. Then, the user inputs the information of the accessory of the terminal device 200b. Here, accessories of the terminal device 200b are a manual D, a manual E, and a driver F. Also, as a result of the search for similar items in step 104, the manual D completely matches the manual of the accessory ID "0001" in FIG. 4, and the manual E is 95% similar to the manual of the accessory ID "0006". It is assumed that the driver F completely matches the driver of the accessory ID "0005".

  In this case, if the degree of similarity 95% exceeds a predetermined threshold value in step 104, the type determination unit 116 determines that the manual D is similar to the manual of the accessory ID "0004". Also, in the error detection process of step 108, the asset type associated with the accessory IDs "0001" and "0005" is the asset type ID "0001" and the accessory ID "0006" from the asset type DB of FIG. The linked asset type is calculated as an asset type ID "0002". Here, since there are a plurality of asset types, it is determined that an error has been detected (Yes in Step 109).

  Therefore, asset type IDs “0001” and “0002” are presented to the user as asset type candidates (step 112). Here, when the user selects, for example, the asset type ID "0002", the asset type ID of the terminal device 200a is determined to be "0002", and the asset information recording unit 113 links it with the asset type ID "0002". The device information of the terminal device 200a is added to the asset information DB (step 111). In addition, the manual D and the driver F are not added to the accessory information DB because they completely correspond to those already registered in the accessory information DB. On the other hand, since the manual E is 95% similar, it is newly registered in the accessory information DB as a version different from the manual of the accessory ID "0006" (step 107).

  When, for example, “1001” is given as the accessory ID of the manual E, “0001” of the manual D and “1001 of the manual E” in the “accessory ID” column of the terminal device 200b in the asset information DB. And “0005” of the driver F are registered. In the asset type DB, only “0006” is registered in the “Accessory ID” column of the asset type ID “0002”. Therefore, “0001” of the manual D, “1001” of the manual E, and “0005” of the driver F are newly registered.

  Next, in the third specific example, it is assumed that the terminal device 200c is newly connected to the network 300. Then, the user inputs the information of the accessory of the terminal device 200c. Here, accessories of the terminal device 200c are a manual G and a driver H. Also, as a result of searching for similar products in step 104, the manual G is 20% similar to the manual of the accessory ID "0001" in FIG. 4, and the driver H is 40% similar to the driver of the accessory ID "0005". It shall be done.

  In this case, if the predetermined threshold value is 50% in step 104, no accessories similar to the manual G and the driver H are found (No in step 105), and the terminal device 200c is a new asset type Treated as That is, the asset information recording unit 113 adds a new asset type ID, links it with the new asset type ID, and adds the device information of the terminal device 200c to the asset information DB and the asset type DB (step 106). The manual G and the driver H are newly registered in the accessory information DB as new accessories (step 107).

  In addition, when “1002” and “1003” are given as the accessory IDs of the manual G and the driver H, for example, the manual G is displayed in the “accessory ID” column of the terminal device 200c in the asset information DB. And “1003” of the driver H are registered. In addition, if, for example, “1000” is assigned as a new asset type ID to the terminal device 200c, “1002” of the manual G in the “appendix ID” column of the asset type ID “1000” in the asset type DB. “1003” of the driver H is newly registered.

  As described above, the asset management server 100 according to the present embodiment uses the information on the accessories attached to the terminal device 200 to manage the information on the terminal device 200 that is an asset. Determine the type. In addition, the asset management server 100 performs similarity determination on the accessory, associates it with the asset type, and stores the information on the accessory.

<Example where a cloud server is arranged>
Next, an embodiment will be described in which the asset management server 100 is provided for each company, for example, and the cloud server 400 that transmits and receives data to and from each asset management server 100 is arranged. FIG. 10 is a diagram showing a configuration example in which the cloud server 400 is arranged. In the example shown in FIG. 10, the asset management server 100 is provided for each of the ranges for managing assets of company A, company B and company C, and the asset management server 100 and the cloud server 400 are connected via the network 500. There is.

  The cloud server 400 collects asset information from each asset management server 100 via the network 500, and integrates the collected information. Then, the cloud server 400 provides the integrated asset information to each asset management server 100. In the present embodiment, a cloud server 400 is used as an example of the server device.

  The network 500 is a communication means used for information communication between the asset management server 100 of each company and the cloud server 400, and is, for example, the Internet or a public line.

Although only the asset management servers 100 of companies A to C are shown in FIG. 10, the number of asset management servers 100 connected to the cloud server 400 is not limited to three as illustrated.
Further, the hardware configuration of the cloud server 400 shown in FIG. 10 may be the same as the hardware configuration of the asset management server 100 shown in FIG.

<Functional Configuration of Cloud Server>
Next, the functional configuration of the cloud server 400 will be described. FIG. 11 is a block diagram showing an example of the functional configuration of the cloud server 400. As shown in FIG. The cloud server 400 includes an asset type information collection unit 401, an asset type information learning unit 402, an asset type information provision unit 403, and an asset type information storage unit 404.

  The asset type information collection unit 401 collects information on assets from each asset management server 100. Here, the asset type information collection unit 401 collects, from each asset management server 100, information of an asset type DB, that is, information of accessories attached to assets classified for each asset type. The asset type information collection unit 401 also collects feature information of each accessory from each asset management server 100.

  The asset type information learning unit 402 integrates the information collected by the asset type information collecting unit 401. Here, the asset type information learning unit 402 generates a database (hereinafter, referred to as an asset type integrated DB) in which the information of the asset type DB held by each asset type information collecting unit 401 and the feature information of each accessory are integrated. .

  The asset type information provision unit 403 provides each asset management server 100 with the information of the asset type integration DB generated by the asset type information learning unit 402.

  The asset type information storage unit 404 stores the asset type integrated DB generated by the asset type information learning unit 402.

As described above, the cloud server 400 according to the present embodiment collects the information and the characteristic information of the asset type DB held in each of the asset management servers 100, integrates the collected information, and then integrates the information. The information is provided to each asset management server 100. That is, the asset management server 100 can collect, from the cloud server 400, information and feature information of asset type DBs held by other asset management servers 100.
Therefore, for example, even if the information is not recorded in the asset type DB of company A, if it is recorded in the asset type DB of company B, the information is added to the asset type DB of company A and complemented . In addition, in the determination of the asset type, the determination is performed not only from the information held by one asset management server 100, but also using the information held by the other asset management server 100.

  Next, processing by the cloud server 400 will be described by taking a specific example. FIGS. 12A and 12B are diagrams for explaining a specific example of processing by the cloud server 400. FIG. FIG. 12A is a diagram illustrating information of the asset type DB of the asset management server 100 of each of the company A to the company C. As illustrated, the asset type DB of company A has information of asset type IDs “0001” and “0002”, and the asset type DB of company B has information of asset type IDs “1001” and “1002”. In the asset type DB of company C, there is information of asset type IDs “2001” and “2002”. The cloud server 400 collects information of each of these asset type DBs.

Here, the accessory ID of the asset type ID "0001" is "0001" to "0005", and the accessory ID of the asset type ID "1001" is "0001" to "0004". That is, when the accessory ID of the asset type ID "0001" and the accessory ID of the asset type ID "1001" are compared, "0001" to "0004" overlap, and the asset type ID "1001" is ""0005" is not recorded. Therefore, the asset type information learning unit 402 determines, for example, the ratio of overlapping accessories, and the asset type ID “0001” and the asset type ID “1001” are the same type, and the asset type ID “ At 1001 ", it is determined that the accessory ID" 0005 "is unregistered.
Similarly, when the accessory ID of the asset type ID “0001” and the accessory ID of the asset type ID “2001” are compared, “0002” to “0005” overlap. Therefore, for example, in the asset type information learning unit 402, the asset type ID "0001" and the asset type ID "2001" are the same type, and in the asset type ID "0001", the accessory ID "0006" is not registered. In the asset type ID "2001", it is determined that the accessory ID "0001" is unregistered.
Then, the asset type information learning unit 402 integrates asset type IDs “0001”, “1001”, and “2001” determined to be the same type.

  FIG.12 (b) is a figure which shows the information of asset type integrated DB which integrated the information of asset type DB shown to Fig.12 (a). The “asset type integration ID” is an ID assigned to integrated information. In the example shown in FIG. 12B, only “asset type integration ID” and “appendage ID” are shown as the information of the asset type integration DB, but “classification” is the same as the property type DB in FIG. And “type common attribute” may be further registered.

Here, the asset type integrated ID “1” is obtained by integrating the asset type IDs “0001”, “1001”, and “2001” in FIG. Then, in the accessory ID, “0001” to “0006” including all of the accessory IDs of asset type IDs “0001”, “1001”, and “2001” are registered.
Similarly, the asset type integration ID "2" is obtained by integrating the asset type IDs "0002" and "1002" in FIG. 12A. Then, in the accessory ID, “0007” and “0008”, which include all of the accessory IDs of the asset type IDs “0002” and “1002”, are registered.
Further, the asset type integration ID "3" is the same as the asset type ID "2002" of FIG. 12 (a). The asset type ID “2002” is independently registered as the asset type integrated ID “3” because the same type does not exist in another asset type DB.

Then, the information of the generated asset type integrated DB is stored in the asset type information storage unit 404 and provided by the asset type information providing unit 403 to each asset management server 100.
For example, in the asset type DB of company B, although the accessory IDs “0001” to “0004” are registered with the asset type ID “1001”, two information are provided according to the information provided from the asset type information provision unit 403. The accessory ID is added, and the accessory IDs “0001” to “0006” are registered.
Therefore, for example, when there is a terminal device 200 having accessories with accessory IDs “0004” to “0006”, asset type information is provided even if it should originally be classified as asset type ID “1001”. Before the provision of information from the unit 403, there is a possibility that the asset type ID "1001" is not classified. On the other hand, since provision of information from the asset type information provision unit 403 increases the information on accessories, it is conceivable that the information is classified into the asset type ID “1001”.

  Also, the asset type information learning unit 402 collects information of each asset type DB, but since the asset type ID and the accessory ID are individually assigned in each asset type DB, these information are integrated. In order to do so, it is determined whether the accessories of each asset type DB are identical. Here, for example, the asset type information learning unit 402 may compare the feature information of the respective accessories to determine whether they are the same.

  In this way, the cloud server 400 collects the information of the asset type DB and the feature information of each accessory held in each asset management server 100, integrates the collected information, and then integrates the information. Are provided to each asset management server 100. Then, each asset management server 100 acquires, from the cloud server 400, information of an asset that the asset management server 100 did not hold by itself, and determines the asset type of the terminal device 200 using the acquired information.

  Further, in the present embodiment, although the terminal device 200 is connected to the network 300, the present invention is not limited to such a configuration. The asset management server 100 may also determine the asset type and the like of the terminal device 200 not connected to the network 300 based on the information input by the user.

  Further, the program for realizing the embodiment of the present invention can be provided by communication means as well as provided by being stored in a recording medium such as a CD-ROM.

  Although the present invention has been described using the embodiment, the technical scope of the present invention is not limited to the above embodiment. It will be apparent to those skilled in the art that various modifications and alternative embodiments can be made without departing from the spirit and scope of the present invention.

1 ... asset management system, 100 ... asset management server, 111 ... device detection unit, 112 ... asset information input unit, 113 ... asset information recording unit, 114 ... accessory information recording unit, 115 ... feature information extraction unit, 116 ... type Judgment unit 117 Error detection unit 118 Asset type correction unit 119 Database storage unit 200, 200a, 200b, 200c Terminal device 400 Cloud server 401 Asset type information collection unit 402 Asset type information Information learning unit, 403 ... asset type information providing unit, 404 ... asset type information storage unit

Claims (10)

Acquisition means for acquiring computerized information of accessories attached to assets to be managed,
A determination unit that determines an asset type of the asset to be managed using accessory information of an accessory attached to an asset classified into a predetermined asset type and the computerized information acquired by the acquisition unit; Asset management apparatus comprising: The determination means is attached to the asset to be managed among the accessories attached to the asset classified into the predetermined asset type by comparison between the accessory information and the information specified from the computerized information The asset management device according to claim 1, characterized in that an accessory identical or similar to the accessory is identified. The determination means is configured to manage, according to a ratio of accessories that are the same as or similar to the accessories attached to the asset to be managed among the accessories attached to the asset classified into the predetermined asset type The asset management apparatus according to claim 1 or 2, wherein it is determined whether or not the asset type of the target asset is determined to be the predetermined asset type. The storage device is further provided with storage means for storing a correspondence relationship in which the predetermined asset type and an accessory attached to the asset classified into the predetermined asset type are associated for each asset type. The asset management device according to any one of Items 1 to 3. When the accessory indicated in the correspondence relationship includes an accessory that matches or is similar to an accessory attached to the asset to be managed, the determination means determines whether or not the asset to be managed is matched or similar If there are no accessories that are classified or classified into the asset type of the item and among the accessories indicated in the corresponding relationship are the same as or similar to the accessories attached to the asset to be managed, the asset to be managed is a new asset type The asset management apparatus according to claim 4, wherein the asset management apparatus is classified into If none of the accessories indicated in the correspondence relationship corresponds to the accessory attached to the asset to be managed, the electronic information of the accessory attached to the asset to be managed is newly registered. If there is an accessory that matches the accessory attached to the asset to be managed among the accessories indicated in the correspondence relationship, newly register electronic information of the accessory attached to the asset to be managed The asset management apparatus according to claim 4 or 5, further comprising: registration means not provided. 7. The apparatus according to any one of claims 1 to 6, further comprising presentation means for presenting the asset type of the asset to be managed determined by the determination means as a selectable asset type candidate to the user. Asset management device described in. Acquisition means for acquiring computerized information of accessories attached to assets to be managed, accessory information of accessories attached to assets classified into predetermined asset types, and computerization acquired by the acquisition means An asset management apparatus having decision means for deciding an asset type of the asset to be managed using information and
It is connected with a plurality of the asset management devices via a network, and accessory information of accessories attached to each of the assets classified for each asset type is collected from the plurality of asset management devices, and the corresponding accessory information collected An asset management system comprising: a server device that provides each asset management device. The said determination means of the said asset management apparatus acquires the said accessory information of the accessory attached to each asset classified into each asset type by the other asset management apparatus from the said server apparatus, The said accessory acquired The asset management system according to claim 8, wherein information is further used to determine an asset type of the asset to be managed. On the computer
With the ability to obtain electronic information of accessories attached to the asset to be managed,
To realize the function of determining the asset type of the asset to be managed using the accessory information of the accessory attached to the asset classified into the predetermined asset type and the acquired electronic information acquired Programs.

Images