JP2006221284A - Asset management method, asset management system, and asset management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage asset in higher accuracy by collecting logon information of a terminal. <P>SOLUTION: The terminal 1 performs a logon request transmitting step of transmitting a logon request including a user ID to a server 2, a receiving step of receiving an information collecting program for collecting the logon information from the server 2, a determining step of determining whether or not the user ID of previous logon information stored in a memory unit and a user ID transmitted in the logon request transmitting step are the same, a changing step of changing the user ID of the memory unit to the user ID of the logon request transmitting step when the user ID of the memory unit is different from the user ID of the logon request transmitting step, and a logon information transmitting step of transmitting the changed logon information of the memory unit to the server 2. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technique for managing assets such as computers.

Companies manage assets by registering asset names, product names, etc. in a database for various assets they own. For example, Patent Document 1 describes an asset management system that collects asset management information using information distributed over a network and updates asset management information registered in a database.
JP 2001-290937 A

  By the way, assets such as personal computers owned by companies tend to increase with the systemization of business. In addition, when asset information changes, such as when a new asset is purchased or an asset is relocated or discarded, maintenance of the asset information management database is required. However, if the assets to be managed are enormous, it is difficult to quickly acquire changes in asset information and reflect them in the management database.

  Also, if the asset is a mobile computer such as a laptop computer, it is difficult to specify the installation location. For example, even if a notebook computer or the like is actually used in a location or user that is different from the installation location or user registered in the management database, it does not accept change applications (reports) from the user. As long as it is difficult to obtain the change information. Therefore, the asset information registered in the management database may not match the actual situation.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to manage assets with higher accuracy.

  In order to solve the above-described problem, the present invention provides an asset management method in an asset management system including, for example, at least one terminal and a server that manages the terminal. The terminal includes a terminal storage unit that stores logon information to the server, and a terminal processing unit, and the terminal processing unit transmits a logon request including a user ID to the server, and a logon request transmission step. It is determined whether the reception step of receiving the information collection program for collection from the server, the user ID of the previous logon information stored in the terminal storage unit, and the user ID transmitted in the logon request transmission step are the same. A determination step, a change step of changing the user ID of the terminal storage unit to a user ID of the logon request transmission step when the user ID of the terminal storage unit and the user ID of the logon request transmission step are different, and the changed terminal storage unit And a logon information transmission step of transmitting the logon information to the server. The server has a server storage unit that stores an information collection program and an asset management table that manages each terminal, and a server processing unit. The server processing unit accepts a logon request transmitted from each terminal, and stores the server A program transmission step of transmitting a part of the information collection program to the requesting terminal, and an updating step of accepting logon information from each terminal and updating the asset management table.

  In the present invention, logon information of terminals can be collected and assets can be managed with higher accuracy.

  Hereinafter, embodiments of the present invention will be described.

  FIG. 1 is an overall configuration diagram of an asset management system to which an embodiment of the present invention is applied.

  As shown in the figure, the asset management system of this embodiment includes at least one terminal 1 and an asset management server 2. Each terminal 1 is connected to the asset management server 2 via a network 3 such as the Internet.

  The terminal 1 is a device to be managed by the asset management server 2 and is a device used by a user such as a PC (Personal Computer). Each terminal 1 includes a processing unit 11 that performs various processes and a storage unit 12. The storage unit 12 includes a registry 13, a management file 14, an uninspected file 15, and an inventory file 16.

  The registry 13 is a file that stores setting data of an OS (Operating System) and application programs. It is assumed that a management ID unique to each terminal is set in the registry 13 of the present embodiment. The management file 14 is a file in which logon information for the asset management server 2 is set. The unchecked file 15 is a file created when the terminal 1 is not managed by the asset management server 2. The inventory file 16 is a file in which specifications of the terminal 1, such as the CPU, memory, and HDD (Hard Disk Drive) of the terminal 1, are set. The management file 14, the uninspected file 15, and the inventory file 16 will be described later.

  The asset management server 2 is a device that manages each terminal 1 (assets) connected to the network 3. The asset management server 2 includes a logon processing unit 21, a logon information management unit 22, an inventory information management unit 23, and a storage unit 24. The logon processing unit 21 receives a logon request from the terminal 1 and transmits the information collection program 29 in the storage unit 24 to the requesting terminal 1. The logon information management unit 22 updates the asset information management table 25, the logon history table 26, and the uninspected management table 27 in the storage unit 24 based on the management file 14 and the uninspected file 15 transmitted from the terminal 1. The inventory information management unit 23 updates the inventory management table 28 based on the inventory file 16 transmitted from the terminal 1.

  The storage unit 24 includes an asset information management table 25, a logon history table 26, an uninspected management table 27, an inventory management table 28, and an information collection program 29. The asset information management table 25 is a table in which information on each terminal 1 managed by the asset management server 2 is registered. The asset information management table 25 will be described later. The logon history table 26 is a table that holds (stores) the management file received from each terminal 1 as a history for each terminal 1 a predetermined number of times.

  The unexamined management table 27 is a table in which information of terminals 1 that are not managed is stored. The inventory management table 28 is a table that holds (stores) the inventory file 16 received from each terminal 1 as a history for each terminal 1 a predetermined number of times. The information collection program 29 is a program for collecting logon information and inventory information of the terminal 1 and is a program (for example, logon script) that is executed when the terminal 1 is logged on.

  Each of the terminal 1 and the asset management server 2 described above includes, for example, a CPU 901, a memory 902, an external storage device 903 such as an HDD, an input device 904 such as a keyboard and a mouse, and a display as shown in FIG. A general-purpose computer system including an output device 905 such as a printer and a communication control device 906 for connecting to a network can be used. In this computer system, the CPU 901 executes a predetermined program loaded on the memory 902, thereby realizing each function of each device.

  For example, the functions of the terminal 1 and the asset management server 2 are the CPU 1 of the terminal 1 in the case of the program for the terminal 1 (including the information collection program 29), and the asset management in the case of the program for the asset management server 2. This is realized by the CPU 901 of the server 2 executing each. Note that the memory 902 or the external storage device 903 of the terminal 1 is used for the storage unit 12 of the terminal 1, and the memory 902 or the external storage device 903 of the asset management server 2 is used for the storage unit 24 of the asset management server 2. Further, regarding the external storage device 903, the input device 904, and the output device 905, each device is provided as necessary.

  Next, the asset information management table 25 stored in the storage unit 24 of the asset management server 2 will be described.

  FIG. 3 is a diagram showing an example of the asset information management table 25. The asset information management table 25 shown in the figure has a management ID 251, a computer name 252, a model number 253, a shared terminal flag 254, and a user ID 255 for each terminal 1. The management ID 251 is identification information for identifying each terminal 1, and is information set for performing asset management. The computer name 252 is identification information unique to each terminal, and is information used in system operation. The serial number (product number) of the terminal 1 may be used as the computer name 252.

  The model number 253 is a number indicating the product type set by the manufacturer of the terminal 1. The shared terminal flag 254 is a flag for identifying whether it is a shared terminal shared by a plurality of users or a dedicated terminal used by only one user. In the present embodiment, “ON” is set for a shared terminal, and “OFF” is set for a dedicated terminal (non-shared terminal). In the user ID 255, the user ID of the user who uses the terminal 1 is set.

  Next, the management file 14, the uninspected file 15, and the inventory file 16 stored in the storage unit 12 of the terminal 1 will be described.

  FIG. 4 is a diagram showing an example of the management file 14. The management file 14 includes a management ID 141, a user ID 142, a logon date / time 143, a computer name 144, a shared terminal flag 145, a logon count 146, a shared terminal update date / time 147, and a logon ID 148. As described above, the shared terminal flag 145 is a flag indicating whether the terminal is a shared terminal or a dedicated terminal. The shared terminal update date and time 147 is set to the date and time when the user selects the “use shared terminal” radio button in the user change dialog described later. The logon ID 148 is set with the user ID actually input at the time of logon request. The logon history table 26 of the asset management server 2 is a table that is created for each management ID and stores a predetermined number of pieces of data in the management file 14 shown in the figure.

  FIG. 5 is a diagram showing an example of the uninspected file 15. The unchecked file 15 is a file created when the terminal 1 is not managed by the asset management server 2, that is, when a management ID is not given. An unchecked file 154, a user ID 151, an IP address 152, a computer name 153, and a logon date and time 154 are illustrated. The unchecked management table 27 of the asset management server 2 is a table that stores data of the unchecked file 15 shown in the figure.

  FIG. 6 is a diagram showing an example of the inventory file 16. The inventory file 16 includes a management ID 161, a computer name 162, an IP address 163, a CPU model name 164, a CPU clock number 165, a physical memory capacity 166, an HDD total capacity 167, an HDD free capacity 168, an OS A version 169 and an OS patch (difference information for correcting the OS) level 170. The inventory management table 28 of the asset management server 2 is a table that is created for each management ID and stores a predetermined number of pieces of data of the inventory file 16 illustrated.

  Next, processing at the time of logon of this system will be described. In the present embodiment, it is assumed that a management ID seal on which the management ID of each terminal 1 is printed is attached in advance to each terminal 1 to be managed by the asset management server 2. It is assumed that information of the management target terminal 1 is set in the asset information management table 25 of the asset management server 2.

  FIG. 7 is an overall process flow diagram when logging on to the system.

  First, the terminal 1 logs on to the asset management server 2 (S11). That is, the processing unit 11 of the terminal 1 transmits a logon request including a user ID (logon ID) and a password input from the input device to the asset management server 2 (S11).

  The logon processing unit 21 of the asset management server 2 receives the logon request and authenticates the user ID and password. When the user ID and password are successfully authenticated, the logon processing unit 21 transmits the information collection program 29 stored in the storage unit 24 to the logon request transmission source terminal 1 (S12).

  Then, the processing unit 11 of the terminal 1 executes the information collection program 29 to create the management file 14, the inventory file 16, or the uninspected file 15. Then, the processing unit 11 transmits the created file to the asset management server 2 (S13). Then, the asset management server 2 updates the tables 25 to 28 in the storage unit 24 based on the files 14 to 16 transmitted from the terminal 1. (S14). The processes of S13 and S14 will be described later.

  Next, the process of the information collection program 29 executed by the terminal 1 (FIG. 7: S13) will be described in more detail.

  FIG. 8 is a process flow diagram when the information collection program is executed. First, the processing unit 11 of the terminal 1 determines whether or not the management ID of the terminal 1 is stored in the registry 13 of the storage unit 12 (S21). If the terminal 1 is a management target of the asset management server 2 and has been logged on before, the management ID of the terminal 1 is stored in the registry 13. Further, if the terminal 1 is not managed by the asset management server 2 or is a management target, the management ID of the terminal 1 is not stored in the registry 13 when the first logon request is made. .

  When the management ID is stored in the registry 13 (S21: YES), the processing unit 11 sets the user ID (FIG. 7: S11) input at the time of the logon request to the management file 14 (see FIG. 4). It is determined whether or not it is the same as the user ID 142 (S22). When the user IDs are the same (S22: YES), the processing unit 11 updates the logon date and time 143 and the number of logons 146 in the management file 14 (S23). That is, the processing unit 11 acquires the current date and time (time) using a function such as an OS (Operating System), and sets the acquired date and time as the logon date and time 143. Further, the processing unit 11 adds “1” to the value of the number of logons 146.

  On the other hand, when the user IDs are different (S22: NO), the processing unit 11 refers to the shared terminal flag 145 of the management file 14 and determines whether or not it is a shared terminal (S24). In the case of a shared terminal, that is, when the shared terminal flag is “ON” (S24: YES), the processing unit 11 determines that the current date and time is within a predetermined period from the shared terminal update date and time 147 of the management file 14 (for example, within one month). ) Or not (S25). By this determination processing, the processing unit 11 displays a user change dialog, which will be described later, only when a predetermined period has elapsed, and causes the user to re-input the usage status of the terminal 1. Thereby, the user can reconfirm the current usage status of the terminal 1 at the timing when the user change dialog is displayed, and can change the usage status if it is different from the previous status.

  If it is within the predetermined period (S25: YES), the processing unit 11 changes the user ID 142 and the logon ID 148 of the management file 14 to the user ID input at the time of the logon request. Further, similarly to S23, the processing unit 11 updates the logon date / time 143 and the logon count 146 of the management file (S26).

  In the case of a non-shared terminal, that is, when the shared terminal flag is “OFF” (S24: NO), or when a predetermined period has elapsed (S25: NO), the processing unit 11 displays a user change dialog as an output device. It is displayed (S27). The user change dialog is a window (dialog box) displayed on the output device, and is an input screen for accepting a user operation / instruction. It is assumed that the user change dialog is included in the information collection program 29.

  FIG. 9 shows an example of the user change dialog. The user change dialog shown in the figure includes a radio button 61 for “use shared terminal”, a radio button 62 for “temporarily borrow another user's terminal”, and a radio button 63 for “change user”. The user change dialog includes a user ID display field 64 in which a user ID input at the time of logon request is displayed and an OK button 65 only when the “change user” radio button 63 is selected. Have.

  The user refers to the user change dialog displayed on the output device, and selects one of the radio buttons 61 to 63 according to the status of the terminal currently used. When the “user change” radio button 63 is selected, the processing unit 11 displays the user ID in the user ID display field 64. Thereby, the user can confirm whether there is no mistake in the user ID which he input. Then, after selecting any of the radio buttons 61 to 63, the user clicks the OK button 65.

  The processing unit 11 updates the management file 14 according to the type of the selected radio button (S28). That is, when the radio button 61 of “use shared terminal” is selected, the processing unit 11 changes the shared terminal flag 145 of the management file 14 to “ON (shared)”, and logs on the user ID 142 and the logon ID 148. Change to the user ID entered at times. Thereby, even in the case of a shared terminal, it is possible to manage (acquire) the currently used user ID that made the logon request. Further, the processing unit 11 changes the shared terminal update date / time 147 to the current date / time. Thus, for the shared terminal, the user change dialog is not displayed until a predetermined period has elapsed from the current date and time. Further, the processing unit 11 updates the logon date and time 143 and the number of logons 146 of the management file 14 as in S23.

  In addition, when the radio button 62 of “temporarily borrowing another user's terminal” is selected, the processing unit 11 does not change the user ID 142 of the management file 14, and only the logon ID 148 is set as the user ID input at the time of the logon request. change. In addition, the processing unit 11 updates the logon date and time 143 and the number of logons 146 in the management file 14 as in S23.

  When the “change user” radio button 63 is selected, the processing unit 11 changes the user ID 142 and the logon ID 148 of the management file 14 to the user ID input when the logon request is made. Then, the processing unit updates the logon date and time 143 and the number of logons 146 of the management file 14 as in S23.

  Then, after updating the management file (S23, S26, S28), the processing unit 11 collects inventory information and creates the inventory file 16 (see FIG. 6) (S29). Note that the processing unit 11 may create the inventory file 16 only when the number of logons 146 of the management file 14 is “1” instead of creating inventory information each time a logon request is made. Then, the processing unit 11 transmits the updated management file 14 and the created inventory file 16 to the asset management server 2 (S30).

  When the management ID is not stored in the registry 13 (S21: NO), the processing unit 11 outputs a management ID input dialog to the output device (S31). That is, the processing unit 11 displays a management ID input dialog when the terminal 1 is not managed by the asset management server 2 or at the first logon request. The management ID input dialog is a small window (dialog box) displayed on the output device, and is an input screen for allowing the user to input the management ID of the management ID sticker attached to the terminal 1. It is assumed that the management ID input dialog is included in the information collection program 29.

  FIG. 10 shows an example of the management ID input dialog. The management ID input dialog shown in the figure has a management ID input field 71, a check box 72 that is clicked (checked) when there is no management ID, and an OK button 73. When the management ID sticker is affixed to the terminal 1, the user inputs the management ID described in the management ID sticker in the management ID input field 71 using the input device. If the management ID seal is not affixed to the terminal 1, the user clicks the check box 72. Then, the user presses an OK button 73 after entering the management ID input field 71 or the check box 72.

  And the process part 11 discriminate | determines whether the input of management ID was received by the management ID input dialog (S32). When the input of the management ID is received (S32: YES), the processing unit 11 writes the received management ID in the registry 13 and creates the management file 14 (S33). That is, the processing unit 11 stores the management ID entered in the management ID 141 of the management file 14, the user ID entered in the logon request in the user ID 142 and logon ID 148, the current date in the logon date 143, and the computer name. The computer name stored in the storage unit 12 is set in 144, “OFF (non-shared)” is set in the shared terminal flag 145, and “1” is set in the number of logons. The processing unit 11 sets a space for the shared terminal update date and time 147.

  Then, as described above, the processing unit 11 collects inventory information and creates the inventory file 16 (S29). Then, the processing unit transmits the management file 14 and the event file 16 to the asset management server 2 (S30). On the other hand, when the check box 72 is clicked (S32: NO), the processing unit 11 creates the unchecked file 15 (see FIG. 5) and transmits it to the asset management server 2 (S34). That is, the unchecked file 15 in which the user ID input in the logon request, the IP address and computer name stored in advance in the storage unit 12, and the current date and time are set is created and transmitted.

  Next, the update process (FIG. 7: S14) of various tables of the asset management server 2 will be described in more detail.

  FIG. 11 is a process flow diagram of the update process of the asset management server 2. First, the logon processing unit 21 receives the management file 14, the uninspected file 15 or the inventory file 16 transmitted from each terminal 1, and temporarily stores the received files 14 to 16 in the storage unit 24 (S41). .

  Then, the logon information management unit 22 reads each management file stored in the storage unit 24 at a predetermined timing (for example, a night batch after online termination), and updates the asset information management table 25 and the logon history table 26. (S42). That is, the logon information management unit 22 performs the following processing for each management file. First, the logon information management unit 22 determines whether or not the management ID set in the management file exists in the asset information management table 25. When the management ID exists in the asset information management table 25, the logon information management unit 22 uses the shared terminal flag 145 and user ID 142 in the management file 14 and the shared terminal flag 254 and user of the corresponding management ID in the asset information management table 25. Compare with ID 255. If they are different, the logon information management unit 22 updates the shared terminal flag 254 and the user ID 255 of the asset information management table 25 with the values set in the management file 14.

  Then, the logon information management unit 22 adds the management file data to be processed to the logon history table 26 of the management ID. Note that the logon history table 26 holds a predetermined number (for example, eight) of management file 14 data as a history for one management ID. Therefore, the logon information management unit 22 deletes the data of the management file 14 having the oldest logon date and time 143 for the management files 14 exceeding the predetermined number (for example, the management files 14 for the ninth and subsequent cases), and performs new management. It is assumed that data of the file 14 is added. When the management ID does not exist in the asset information management table 25, the logon information management unit 22 outputs the data of the management file 14 to be processed to an error file (not shown).

  After finishing the processing of all the management files 14, the logon information management unit 22 reads each uninspected file 15 temporarily stored in the storage unit 24 and adds it to the uninspected management table 27 (S43). The terminal set in the uninspected management table 27 (the terminal that has transmitted the uninspected file) is a terminal that is not managed by the asset management server 2. Therefore, the administrator specifies the contact information of the user from the user ID and the IP address for each data of the uninspected file set in the uninspected management table. Then, the administrator interviews the user who has specified the contact information, assigns a management ID (issues a management ID seal) as necessary, and registers the terminal in the asset information management table 25.

  Then, the inventory information management unit 23 performs the following process for each inventory file temporarily stored in the storage unit 24. First, the inventory information management unit 23 determines whether or not the management ID set in the inventory file exists in the asset information management table 25. When the management ID exists in the asset information management table 25, the data of the inventory file to be processed is added to the inventory management table 28 of the management ID. Note that the inventory management table 28 holds a predetermined number (for example, two) of inventory file 16 data as a history for one management ID. Therefore, the inventory information management unit 23 deletes the data of the inventory file 16 with the oldest update time for the inventory file 16 exceeding the predetermined number (for example, the third and subsequent inventory files 16), and creates a new inventory file. It is assumed that 16 data are added. If the management ID does not exist in the asset information management table 25, the inventory information management unit 23 outputs the inventory file 16 to be processed to an error file (not shown).

  The embodiment of the present invention has been described above.

  In the present embodiment, the terminal 1 executes the information collection program received from the asset management server 2 at the time of logon, and transmits the management file and the inventory file that collect the logon information to the asset management server 2. Thereby, the asset management server 2 can manage terminals (assets) with higher accuracy. That is, it is possible to prevent asset management failure.

  Further, in the present embodiment, a management ID input dialog (see FIG. 10) is output, and the user is made to input whether or not the terminal is given a management ID (management ID seal). As a result, an uninspected file can be output for a logon request from a non-managed terminal, and an unknown terminal can be captured (detected).

  In this embodiment, the user ID at the previous logon and the user ID at the current logon are compared, and if they are different, a user change dialog (see FIG. 9) is output to allow the user to select the usage status. . In this way, by checking the user ID at the time of logon, it is possible to manage users that match the actual situation.

  In addition, the management file and asset information management table of the present embodiment has a shared terminal flag and can flexibly manage shared terminals shared by a plurality of users. For example, even in the case of a shared terminal, a user change dialog is displayed at a predetermined timing, and the user is allowed to re-input the terminal usage status (FIG. 8: S25). Thereby, the user can reconfirm the current usage status of the terminal at the timing when the user change dialog is displayed, and can change the usage status if it is different from the previous status.

  Further, the management file and the asset information management table of this embodiment have a user ID. That is, in this embodiment, the terminal is managed by specifying the user of the terminal, not the installation location of the terminal. Thereby, even a mobile computer such as a notebook computer or a portable information terminal that is difficult to specify the installation location can manage the terminal with higher accuracy.

  In addition, by managing the terminal using the user ID, it is possible to charge the terminal more accurately in units of departments. Moreover, the terminal owner (user) can be easily grasped at the time of simultaneous replacement of the terminals. Moreover, when a terminal breaks down, a quick response can be taken.

  In addition, the management file and the logon history table of this embodiment have a logon date and time. As a result, a terminal that has not been logged on for a certain period (for example, three months or more) can be determined as a dormant asset (unused asset), and the dormant asset can be recovered (or appropriately rearranged).

  Further, the event file and the inventory management table of the present embodiment have a memory capacity, an HDD free capacity, and the like. Thus, when distributing software all at once, it is possible to take measures such as adding HDDs in advance if necessary.

  In addition, this invention is not limited to said embodiment, Many deformation | transformation are possible within the range of the summary. For example, in the above embodiment, the asset management server 2 updates various tables at a predetermined timing (for example, a night batch) (see FIG. 11). However, the present invention is not limited to this. For example, various tables may be updated at the timing when various files are received from the terminal 1 (that is, in real time).

  In the above embodiment, the terminal 1 sets the management ID input from the management ID input dialog in the registry 13 at the first logon (FIG. 8: S33). However, the terminal 1 may set the management ID transmitted from the asset management server 2 in the registry 13. For example, the terminal 1 transmits the computer name together with the user ID / password to the asset management server 2 when logging on (FIG. 7: S11). Then, the asset management server 2 identifies the management ID corresponding to the received computer name from the asset information management table 25 and transmits it to the terminal 1 together with the information collection program 29 (S12). Then, the terminal 1 sets the management ID received from the asset management server 2 in the registry 13 and then executes the information collection program 29. This eliminates the need for the user to enter a management ID even when the user logs on for the first time.

1 is a diagram illustrating an overall configuration of an asset management system to which an embodiment of the present invention is applied. It is a figure which shows the hardware structural example of each apparatus. It is a figure which shows an example of an asset information management table. It is a figure which shows an example of a management file. It is a figure which shows an example of an unchecked file. It is a figure which shows an example of an inventory file. It is a whole processing flow figure of logon processing. It is a processing flow figure of logon information collection processing. It is a figure which shows an example of a user change dialog. It is a figure which shows an example of a management ID input dialog. It is a processing flowchart of a table update process.

Explanation of symbols

1: terminal, 11: processing unit, 12: storage unit, 13: registry, 14: management file, 15: unchecked file, 16: inventory file, 2: asset management server, 21: logon processing unit, 22: logon information Management unit, 23: Inventory information management unit, 24: Storage unit, 25: Asset information management table, 26: Logon history table, 27: Unchecked management table, 28: Inventory management table, 29: Information collection program, 3: Network

Claims (5)

An asset management method in an asset management system having at least one terminal and a server that manages the terminal,
The terminal includes a terminal storage unit that stores logon information to the server, and a terminal processing unit,
The terminal processing unit
A logon request transmission step of transmitting a logon request including a user ID to the server;
A receiving step of receiving from the server an information collection program for collecting the logon information;
A determination step of determining whether or not the user ID of the previous logon information stored in the terminal storage unit is the same as the user ID transmitted in the logon request transmission step;
When the user ID of the terminal storage unit is different from the user ID of the logon request transmission step, the changing step of changing the user ID of the terminal storage unit to the user ID of the logon request transmission step;
The logon information transmission step of transmitting the changed logon information of the terminal storage unit to the server, and
The server includes a server storage unit that stores an asset management table that manages the information collection program and each of the terminals, and a server processing unit,
The server processing unit
A program transmission step of accepting a logon request transmitted from each of the terminals, and transmitting the information collection program of the server storage unit to the requesting terminal;
An asset management method comprising: an update step of receiving the logon information from each of the terminals and updating the asset management table. The asset management method according to claim 1,
The terminal processing unit, when the user ID of the terminal storage unit and the user ID of the logon request transmission step are different, an output step of outputting an input screen for accepting an input of the usage status of the terminal;
An asset management method, further comprising: a usage status change step of changing logon information of the terminal storage unit based on the usage status input from the input screen. The asset management method according to claim 1,
The terminal processing unit outputs an input screen for receiving input of identification information of the terminal;
An asset management method, further comprising: a setting step of setting the identification information input from the input screen in the terminal storage unit. An asset management system having at least one terminal and a server that manages the terminal,
The terminal
Terminal storage means for storing logon information to the server;
Logon request transmission means for transmitting a logon request including a user ID to the server;
Receiving means for receiving from the server an information collection program for collecting the logon information;
Execution means for executing the information collection program,
The execution means includes
A determination step of determining whether or not the user ID of the previous logon information stored in the terminal storage unit and the user ID transmitted by the logon request transmission unit are the same;
When the user ID of the terminal storage means is different from the user ID transmitted by the logon request transmission means, the changing step of changing the user ID of the terminal storage means to the user ID transmitted by the logon request transmission means;
A logon information transmission step of transmitting the changed logon information of the terminal storage means to the server,
The server
Server storage means for storing the information collection program and an asset management table for managing each of the terminals;
A program transmission unit that accepts a logon request transmitted from each of the terminals, and transmits the information collection program of the server storage unit to the requesting terminal;
An asset management system comprising: update means for receiving the logon information from each of the terminals and updating the asset management table. In an asset management system having at least one terminal and a server that manages the terminal, an asset management program executed by the terminal,
The terminal includes a storage unit that stores logon information to the server, and a processing unit.
In the processing unit,
A logon request transmission step of transmitting a logon request including a user ID to the server;
A receiving step of receiving from the server an information collection program for collecting the logon information;
A determination step of determining whether or not the user ID of the previous logon information stored in the storage unit is the same as the user ID transmitted in the logon request transmission step;
When the user ID of the storage unit is different from the user ID of the logon request transmission step, the changing step of changing the user ID of the storage unit to the user ID of the logon request transmission step;
An asset management program, comprising: executing a logon information transmission step of transmitting the changed logon information of the storage unit to the server.

Images