JP2005301543A - Method and system for managing da tool, terminal for using da tool, its program, management server, and its program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method for counting the operation time of a DA tool without depending on the DA tool and a simulation method and system for predicting the appropriate number of DA tools. <P>SOLUTION: A terminal for using the DA tool detects the start and end of the operation of the DA tool on the basis of the generation and extinction of an operation window in the DA tool, and sends the DA tool's identification information available at that time, the time that the operation started or ended, and the terminal's identification information to a DA tool management server. The DA tool management server stores the information, counts the time, and, on the basis of this counting data, runs a simulation to predict the appropriate number of DA tools to be installed. In this way, the system for counting the operation time of the DA tool can be provided at reduced development and maintenance costs, while also reducing the costs of purchasing and maintaining the DA tools. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention includes a DA tool management method, a management system, a utilization terminal, and a program for performing a simulation for totalizing the operating time of a DA tool and predicting the necessary number of DA tools based on the total data, and The present invention relates to a management server and its program.

  Currently, CAD (Computer Aided Design) and DA (Design Automation) technologies have been introduced in various design sites as well as machine design and circuit design, and designs utilizing computers are performed. The entity that implements the CAD or DA technology is a computer program, which is called a CAD tool or DA tool. In this specification, CAD or DA is generically referred to as DA, and CAD tool or DA tool is generically referred to as DA tool.

  Conventionally, management for monitoring and counting the usage time of a DA tool is mainly performed for the purpose of managing the number of licenses for DA tool users. That is, the DA tool vendor that provides the DA tool provides the DA tool after contracting the number of licenses to the user. In order to prevent the use exceeding the number of contract licenses, a license management program is often incorporated in the DA tool itself. The outline of the management method will be described as follows.

  The user prepares a license management server for performing license management and a computer (use terminal) for installing the DA tool, and connects them through a network. The CAD vendor provides the user with a DA tool to be licensed, its license management program, and a license key generated by a code such as a host ID for identifying the user's license management server. The user can use the DA tool in the user terminal by installing the CAD tool in the user terminal and installing the license management program and the license key in the license management server.

  When the DA tool is activated in the DA tool using terminal, the DA tool inquires of the license management server about the availability of the license. The license management server manages the number of DA tools used at that time, and checks whether the number of simultaneous use exceeds the number of licenses. If the number of concurrent uses does not exceed the number of licenses as a result of the check, a use permission is returned to the DA tool of the use terminal. When the DA tool usage terminal receives the usage permission, the DA tool usage is permitted. On the other hand, when the number of simultaneous uses exceeds the number of licenses, the use permission is not issued and the DA tool cannot be used in the DA tool using terminal.

In the above, the DA management server monitors the usage status of the licensed DA tool in the DA tool using terminal, that is, the start and end of operation of the DA tool by the license management program. Therefore, by using this license management program, it is possible to easily construct a system for counting the operating time of the DA tool. For example, Patent Document 1 shows an example of a system that applies the license management program, totals the operating time of the DA tool used by the end user, and charges according to the operating time.
JP 2003-186562 A (paragraphs 0017 to 0053, FIGS. 1 to 3)

  By the way, the purpose of summing up the operating time of the DA tool is not only necessary for confirming the license or charging. If the user himself / herself determines whether the number of DA tool licenses he / she has contracted for is excessive or insufficient, or if the operating time or operating frequency increases or decreases, the number of licenses newly required or unnecessary It is also necessary to predict how many will be.

  However, in order to construct a system for counting the operating time of the DA tool for the user's own purpose such as predicting the required number of licenses as described above, a license management program provided by the DA tool vendor The following problems became apparent when trying to calculate the operating time of DA tools by applying the.

  In general, users of DA tools often use a plurality of DA tools at the same time. For example, in order to design a certain device, a DA tool for mechanical part design is required, and a DA tool for electronic circuit design is also required. Moreover, these DA tools are used for simulation of mechanical strength or for three-dimensional drawing. In other words, when a user uses a large number of DA tools, if the user tries to collect and manage the operation time by using a license management program that depends on the DA tools, the number of DA tools depends on the number of DA tools being used. An operating time tabulation management program is required. Developing and maintaining such a management program for each DA tool is time consuming and a significant burden in terms of man-hours and costs.

  For example, for DA tools that are not license-managed, such as in-house developed DA tools, tabulation management of DA tool operating time based on license management is not possible. In order to perform similar tabulation management, it was necessary to add a program similar to the license management program to the DA tool developed in-house.

  An object of the present invention is to solve the above problems. That is, it provides a DA tool management method and system for counting the operating time of a DA tool that does not depend on the DA tool and therefore does not incur development and maintenance costs even if the DA tool is added or changed. It is another object of the present invention to provide a DA tool management method and system provided with simulation means for optimizing the required number of DA tools.

  In order to solve the above-described problems, in the present invention, a plurality of DA tool use terminals each having one or more DA tools, which are design support software using a computer, are installed, and the plurality of DA tool use terminals and a network are provided. The DA tool management system is configured by a DA tool management server that is connected via the DA tool and manages the operating status of the DA tool in the DA tool using terminal. Then, the DA tool utilization terminal is provided with an operation status detection means for detecting the start and end of the operation of the DA tool based on the display state of a predetermined operation screen displayed by the DA tool. When the operation status detecting means detects the start or end of operation of the DA tool, the DA tool using terminal identification information, the DA tool identification information, and the date and time of the start or end of operation of the DA tool The DA tool operation status data including the above information is transmitted to the DA tool management server. When receiving the DA tool operation status data, the DA tool management server sorts and aggregates the DA tool operation status data based on the DA tool using terminal identification information and the DA tool identification information, and creates operation status aggregation data. I did it.

  That is, according to the present invention, based on the display state of a predetermined operation screen (operation window) displayed by the DA tool on the DA tool using terminal, that is, generation and disappearance of the DA tool operation window, the DA tool operation start and operation Detect end. Then, the DA tool utilization terminal identification information and the DA tool identification information are attached to the information of the operation start and operation end dates and sent to the DA tool management server. The DA management server can create operating status total data for each DA tool by receiving, storing, and tabulating the transmitted information. Since these processes are performed without depending on the DA tool program, it is not necessary to prepare a program for calculating the operating status for each DA tool.

  The DA tool management server according to the present invention further performs a simulation for predicting the appropriate number of DA tools to be installed according to the usage demand of the DA tool based on the operation status aggregation data totaled as described above. I did it.

  Therefore, based on the simulation result, the administrator of the DA tool management system can know the appropriate number of DA tools according to the usage demand of the DA tool.

  According to the present invention, the method and program of the present invention do not depend on the DA tool, and can be applied to a plurality of DA tools simultaneously. Therefore, since it is not necessary to create a program for totalizing operation status data for each DA tool, the DA tool management system, DA tool management server, etc. A DA tool using terminal can be provided. Furthermore, by providing a step and means for executing a simulation for optimizing the required number of DA tools, the number of DA tool licenses can be optimized, and the cost of purchasing and maintaining DA tools and Investment can be reduced.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram showing a configuration example of a DA tool management system according to an embodiment of the present invention. 1, the DA tool management system includes a plurality of DA tool use terminals 1 # 1, 1 # 2,..., 1 # n, a network 2, and a DA tool management server 3.

  The DA tool 101 is installed in the DA tool use terminal 1 (each of the DA tool use terminals 1 # 1, 1 # 2,..., 1 # n), and the user of the DA tool 101 uses the DA tool 101. To do. Here, a plurality of types of DA tools 101 may be installed in each DA tool using terminal 1.

  Further, the DA tool using terminal 1 includes an operation status detection unit 102 and an operation status data transmission unit 103. The operation status detection unit 102 detects the operation status of the DA tool 101, that is, the operation start and the operation end, and acquires the operation status data of the DA tool 101. The operating status data transmitting unit 103 sends the acquired operating status data to the DA tool management server 3 via the network 2.

  Further, the DA tool management server 3 includes an operating status data receiving unit 301, a DA tool operating status totaling unit 302, and a DA tool appropriate number prediction simulation unit 303. Here, the operating status data receiving unit 301 receives the operating status data of the DA tool 101 transmitted from the DA tool using terminal 1 via the network 2 and stores the operating status data in the operating status data storage file 304. . Further, the DA tool operating status totaling unit 302 totals the DA tool operating status totaling data based on the data stored in the operating status data storage file 304, and creates the operating status data totaling file 305. Further, the DA tool appropriate number prediction simulation unit 303 executes a simulation for predicting the appropriate number of installations according to the usage demand of the DA tool 101 based on the operation status data totaling file 305.

  The substance of the DA tool utilization terminal 1 in FIG. 1 is a computer, none of which is a CPU (Central Processing Unit), a storage device comprising a main memory, a hard disk device, etc., an input device comprising a keyboard, a mouse, etc. An output device including a display, a printer, and the like, and a network interface and the like are included. The DA tool 101, the operation status detection unit 102, and the operation status data transmission unit 103 are all programs, and their program codes are stored in the storage device and read out and executed by the CPU.

  Similarly, the DA tool management server 3 is a computer, all of which are not shown in the figure, a storage device such as a main memory and a hard disk device, an input device such as a keyboard and a mouse, and an output device such as a display and a printer. And a network interface or the like. The operating status data receiving unit 301, the DA tool operating status totaling unit 302, and the DA tool appropriate number prediction simulation unit 303 are all programs, and their program codes are stored in the storage device and read out by the CPU. Executed. The operating status data storage file 304 and the operating status data total file 305 are storage data areas secured on the storage device.

  FIG. 2 is a diagram showing a procedure for detecting the operating state of the DA tool in the DA tool using terminal according to the embodiment of the present invention. FIG. 2 shows a process executed by an OS (Operating System) installed in the DA tool using terminal 1 and a process executed by an operation status detection program as the operation status detection unit 102. Here, the OS refers to a basic program of a computer for operating an application program such as an operation status detection program under a simple GUI (Graphical User Interface), and includes a so-called window system.

  In FIG. 2, when the DA tool using terminal 1 is turned on, the OS is started (step S20). First, the OS executes a predetermined initialization process (not shown) and waits for an operation input by the user. When the user performs an operation to activate the DA tool 101, a predetermined DA tool activation process is executed (step S22), and a window for operating the DA tool 101 is generated (step S23). indicate. On the other hand, when the user performs an operation to terminate the DA tool 101, the OS executes a predetermined DA tool termination process (step S24), and the window display of the DA tool 101 disappears (step S25). Further, after executing the window generation / disappearance process, the OS again enters a state of waiting for an operation input by the user.

  In FIG. 2, when the OS is activated (step S20), the operating status detection program is activated accordingly (step S30). Then, the operating status detection program monitors the generation and disappearance of the DA tool window in the OS processing. When the generation or disappearance of the DA tool 101 window is detected (step S31), the operating time detection process is executed (step S32), and then the generation and disappearance of the DA tool window are repeatedly monitored. The operating status detection program ends when the OS ends (step S26) (step S33).

  As described above, the operation status detection program monitors the generation and disappearance of the DA tool window while the OS is operating. Here, in order to detect the generation or disappearance of the window, a message (for example, a global hook) sent by the window system of the OS may be monitored. Alternatively, the names of all windows opened on the window system may be listed every predetermined time, and the generation or disappearance of the window may be detected according to the relationship before and after the list.

  In any of these methods, in this embodiment, the generation or disappearance of the window can be detected independently of the program of the DA tool 101. It does not depend on the type or number of DA tools 101.

  FIG. 3 is a diagram showing in detail the flow of the operation time detection process in FIG. 3, the operation time detection process is started when the operation status detection program detects the generation and disappearance of the DA tool 101 window in FIG. 2. First, it is determined whether the window is generated or disappeared (step S40). In the case of generating a window (generated in step S40), the window title of the generated window is read (step S41). Then, it is determined whether or not the generated window is a window of the DA tool 101 to be detected (step S42).

  As a result of the determination, if the generated window is the window of the DA tool 101 to be detected (Yes in step S42), the execution image name, process ID, and window ID of the program related to the generated window are executed. Store in the middle DA tool table (step S43). Further, the DA tool name, the use start time of the DA tool 101, the process ID, the host ID, and the user ID are transmitted to the DA tool management server 3 (step S44), and the operation time detection process is terminated. Here, it is assumed that the operation start time of the DA tool 101 is the time when generation of the window is detected.

  If it is determined in step S42 that the generated window is not the window of the DA tool 101 to be detected (No in step S42), step S43 and step S44 are not executed, and the operation time detection process ends. To do.

  Furthermore, in the case of window disappearance in step S40 (disappearance in step S40), the execution image name and process ID of the window to disappear are read (step S45). Then, the executing DA table created in step S43 is referred to (step S46), and it is determined whether or not the disappearing window is the window of the DA tool 101 being executed (step S47).

  As a result of the determination, if the window of the DA tool 101 is being executed (Yes in step S47), the DA tool name associated with the disappeared window, the use end time of the DA tool 101, the process ID, the host ID, The user ID is transmitted to the DA tool management server 3 (step S48), and the operation time detection process is terminated. Here, the use end time of the DA tool 101 is assumed to be the time when the disappearance of the window is detected.

  On the other hand, if it is determined in step S47 that the disappearing window is not the window of the DA tool 101 being executed (No in step S47), step S48 is not executed, and the operation time detection process is terminated.

  In FIG. 3, the operation time detection process excluding steps S44 and S48 is a process performed by the operation status detection unit 102 (see FIG. 1), and steps S44 and S48 are performed by the operation status data transmission unit 103. It is processing. In addition, the DA tool name, the use end time of the DA tool, the process ID, the host ID, and the user ID transmitted to the DA tool management server 3 in step S44 and step S48 are the DA tool operating status data in the claims. Equivalent to.

  Here, as identification information of the DA tool using terminal 1, a host ID is used here. The identification information of the DA tool using terminal 1 may be a MAC address (Media Access Control Address) instead of the host ID.

  As the identification information of the DA tool 101, the DA tool name and process ID are used. By using the process ID as the identification information of the DA tool 101, it is possible to distinguish it even if the same DA tool 101 is used in the same DA tool using terminal 1. The DA tool name is either or both of the window title of the DA tool operation window and the execution image name of the execution program.

  As described above, in the present embodiment, the process of detecting the start and end of operation of the DA tool 101 can be performed in a form that does not depend on the program of the DA tool 101. Therefore, the DA tool operating state detection process shown in FIG. 2 and FIG. 3 is a DA tool with a license management program as long as the DA tool 101 has an operation window. It can be applied whether it is a DA tool developed in-house or not. Further, the present invention can be applied even when a plurality of DA tools 101 are installed in the DA tool using terminal 1.

  Next, processing performed by the DA tool management server 3 will be described with reference to FIGS. 1 and 4 to 6. In FIG. 1, the operating status data receiving means 301 receives DA tool operating status data transmitted from the DA tool using terminal 1, and stores the received data in the operating status data storage file 304 almost as it is. .

  FIG. 4 is a diagram showing an example of an operation status data storage file in the DA tool management server according to the embodiment of the present invention. In FIG. 4, the operation status data storage file 304 includes items of a tool name, time, start / end, host ID, process ID, and user ID. For example, in the DA tool using terminal 1 whose host ID is HOSTA, the user whose user name is AA started using the DA tool 101 whose tool name is CAD-A at 9:10:10 on February 10 I understand. Similarly, the use end time is also known. In addition, since the DA tool 101 can be distinguished by the process ID here, even when a plurality of the same DA tool 101 are used at the same time on the same DA tool utilization terminal 1, the operation start and operation end of each of them are performed. Can be correctly distinguished.

  Next, in the DA tool management server 3, the DA tool operating status totaling unit 302 performs a totaling process of data in the operating status data storage file 304. In the totaling process, first, based on the data of the operation status data storage file 304, the usage time per time when the DA tool 101 is used is obtained. The usage time is obtained as follows.

  First, in the operation status data storage file 304, the tool name, host ID, process ID, and user ID are grouped and rearranged for the same data. Then, by referring to the data of the time item for each group of data, a combination of start and end data is obtained such that the start time is earlier than the end time and the time difference from the start time to the end time is the smallest. From the start and end data thus obtained, the usage time per use when each DA tool 101 is used can be obtained.

  Furthermore, the DA tool operating status totaling unit 302 totals the usage time obtained as described above for each DA tool (tool name) and for each DA tool using terminal 1 (host ID), for example, every week. Alternatively, statistical data such as monthly averages and standard deviations are obtained. Then, the result is stored in the operation status data totaling file 305.

  FIG. 5 is a diagram showing an example of an operation status data total file in the DA tool management server according to the embodiment of the present invention. In FIG. 5, the operation status data totaling file 305 includes, for each DA tool (tool name) and DA tool using terminal 1 (host ID), an average usage time per use of the DA tool and a per day. It has items for average number of uses and average number of users. Moreover, although not shown in figure, the average value which averaged the data about DA tool utilization terminal 1 (host ID) for every DA tool (tool name) is also contained. Furthermore, not only the average value but also the standard deviation, variance, etc. are included for each item, and they are counted in the same way.

  As described above, it is possible to obtain various aggregate data regarding the operating status of the DA tool 101. As a result, the administrator who manages the DA tool can easily grasp the usage status of the DA tool 101 and the DA tool using terminal 1, and further, the number of DA tools 101 and the number of DA tool using terminals 1 It is possible to determine whether there is excess or deficiency. In addition, in the embodiment of the present invention, since various aggregated data related to the operating status can be obtained without depending on the DA tool 101, the operating status data is aggregated even if a new DA tool is added or changed. There is no need to create or change a new program.

  Next, the DA tool appropriate number prediction simulation will be described. In the present embodiment, DA tool appropriate number prediction simulation means 303 for predicting the appropriate number of DA tools 101 to be installed in the DA tool management server 3 can be applied even when the demand for using the DA tool 101 increases or decreases. Is provided. In the present embodiment, the DA tool appropriate number prediction simulation means 303 is a simulation program based on a queue model in which the number of DA tools 101 installed is the number of windows. In this case, the service time data of the counter in the queue model corresponds to the usage time of the DA tool 101, and the data on the arrival rate of the customer corresponds to the average use frequency of the DA tool 101. In this simulation, the usage demand and the number of installations of the DA tool 101 are changed as parameters, and the probability of waiting and the waiting time are obtained.

  The DA tool 101 usage request generation time interval and usage time data input to the simulation means 303 that performs the simulation as described above include the DA tool 101 usage start time stored in the operation status data storage file 304, Data corresponding to the raw data of usage time can be used. However, when increasing / decreasing the demand of the DA tool 101, the time interval of the usage request generation of the DA tool 101 is adjusted by adjusting the raw data of the time interval when the DA tool 101 starts to be used to compress / expand the time axis. There is a need to. Therefore, in this case, the raw data is appropriately thinned out or appropriate random number data is added.

  Further, the DA tool appropriate number prediction simulation means 303 can also perform Monte Carlo simulation. In this case, the data is generated based on the average usage times, average usage times, and standard deviations of the DA tool 101 collected in the operation status data totaling file 305 as the time interval and usage time data of the usage request generation of the DA tool 101. Use random numbers. As a result, the probability of waiting and the waiting time are obtained.

  In this Monte Carlo simulation, the start of operation of the DA tool 101 at a certain time follows a random number that defines the probability of occurrence determined by the average number of times of use. It may be specified that the probability of occurrence is different for each band. At this time, it is preferable to calculate the average use frequency data divided into the time zones in the operation status data totaling file 305 and use the occurrence probability based on the calculated data.

  In the queuing model of this embodiment, when it is assumed that the input data is a random number (corresponding to the above-mentioned Monte Carlo simulation), the probability of waiting and the expected value of the waiting time are obtained as mathematical solutions. (The mathematical solution is described in various textbooks explaining the queue). Therefore, the DA tool appropriate number prediction simulation means 303 can change the usage demand (average number of times of use) and the number of installations of the DA tool 101 as parameters in accordance with the mathematical solution, and can determine the probability of waiting and the waiting time. And In this case, the computer calculation time is short, but it is not possible to set the average number of times of use by dividing the time zone, for example, during working hours, outside working hours, midnight, and the like.

  FIG. 6 is a diagram showing an example of the result of the DA tool appropriate number prediction simulation in the DA tool management server according to the embodiment of the present invention. FIG. 6 shows the probability of waiting for using the DA tool 101 and the average waiting time obtained as a result of the simulation by changing the usage increase rate and the number of installations of the DA tool 101 as parameters. The simulation performed here may be any one of a simulation using raw data of the operation status data accumulation file 304, a Monte Carlo simulation based on the data of the operation status data totaling file 305, and a simulation based on a numerical solution.

  The definition of the appropriate number of DA tools differs depending on the type of DA tool and its application purpose. Therefore, if the appropriate number of DA tools is defined as “the minimum number of installations in which the average waiting time is 0”, in the example of FIG. 6, the appropriate number of installations when the DA tool usage rate increases by 10% is 15 In addition, if the appropriate number of DA tools is defined as “the minimum number of installations in which the average waiting time is within 5 minutes (300 seconds)”, in the case of the example in FIG. The proper number of installs is 16.

  As described above, the administrator of the DA management system knows the appropriate number of DA tools 101 by performing a simulation for predicting the appropriate number of DA tools 101 to be installed when the demand for the DA tools 101 increases or decreases. As a result, it is not necessary to license or purchase the DA tool 101 more than necessary, so that the cost and investment for purchasing and maintaining the DA tool 101 can be reduced.

It is a figure showing an example of composition of a DA tool management system concerning an embodiment of the present invention. It is the figure which showed the procedure which detects the operating state of DA tool in the DA tool utilization terminal which concerns on embodiment of this invention. It is the figure which showed the flow of the operation time detection process in FIG. 2 in detail. It is the figure which showed the example of the operation condition data storage file in the DA tool management server which concerns on embodiment of this invention. It is the figure which showed the example of the operation condition data total file in the DA tool management server which concerns on embodiment of this invention. It is the figure which showed the example of the result of the DA tool appropriate number prediction simulation in the DA tool management server which concerns on embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 DA tool utilization terminal 2 Network 3 DA tool management server 101 DA tool 102 Operation status detection means 103 Operation status data transmission means 301 Operation status data reception means 302 DA tool operation status totalization means 303 DA tool appropriate number prediction simulation means 304 Operation status Data accumulation file 305 Operation status data summary file

Claims (12)

A plurality of DA tool use terminals each having one or more DA tools, which are design support software using a computer, are connected to the plurality of DA tool use terminals via a network, and the DA tools in the DA tool use terminal are connected to each other. A DA tool management method in a DA tool management system comprising a DA tool management server for managing the operation status of a tool,
The DA tool using terminal is
An operation status detection step of detecting operation start and operation end of the DA tool based on a display state of a predetermined operation screen displayed by the DA tool;
When the start or end of operation of the DA tool is detected in the DA tool operation detection step, the DA tool using terminal identification information, the DA tool identification information, and the DA tool operation start or operation end And a DA tool operating status data including the date and time information of the operating status data transmitting step for transmitting the DA tool operating status data to the DA tool management server,
The DA tool management server is
An operating status data receiving step for receiving the DA tool operating status data transmitted from the DA tool using terminal;
The DA tool operation status data is classified and aggregated based on the DA tool utilization terminal identification information and the DA tool identification information, and a DA tool operation status aggregation step for creating operation status aggregation data is executed. DA tool management method. The DA tool management method according to claim 1,
The DA tool management server further includes:
DA tool management characterized by executing a DA tool appropriate number prediction simulation step for performing a simulation for predicting the appropriate installation number of the DA tool according to the usage demand of the DA tool based on the operation status summary data. Method. A plurality of DA tool use terminals each having one or more DA tools, which are design support software using a computer, are connected to the plurality of DA tool use terminals via a network, and the DA tools in the DA tool use terminal are connected to each other. A DA tool management system comprising a DA tool management server for managing the operation status of a tool,
The DA tool using terminal is
An operation status detection means for detecting the start and end of operation of the DA tool based on a display state of a predetermined operation screen displayed by the DA tool;
When the operation detecting means detects the start or end of operation of the DA tool, the DA tool using terminal identification information, the DA tool identification information, and the date and time of the DA tool operation start or operation end Operating status data transmitting means for transmitting DA tool operating status data including information to the DA tool management server,
The DA tool management server is
Operating status data receiving means for receiving the DA tool operating status data transmitted from the DA tool using terminal;
The DA tool operating status data is provided with DA tool operating status totaling means for sorting and totaling the DA tool operating status data based on the identification information of the DA tool using terminal and the identification information of the DA tool, and creating operating status totaled data. DA tool management system. In the DA tool management system according to claim 3,
The DA tool management server further includes:
A DA tool management system comprising DA tool appropriate number prediction simulation means for performing a simulation for predicting the appropriate installation number of the DA tool according to the usage demand of the DA tool based on the operation status totaling data . A plurality of DA tool use terminals each having one or more DA tools, which are design support software using a computer, are connected to the plurality of DA tool use terminals via a network, and the DA tools in the DA tool use terminal are connected to each other. A DA tool use terminal in a DA tool management system comprising a DA tool management server for managing the operating status of the tool,
An operation status detection means for detecting the operation start and operation end of the DA tool based on a display state of a predetermined operation screen displayed by the DA tool;
When the operation detecting means detects the start or end of operation of the DA tool, the DA tool using terminal identification information, the DA tool identification information, and the date and time of the DA tool operation start or operation end Operating status data transmitting means for transmitting DA tool operating status data including information to the DA tool management server,
DA tool using terminal characterized by. In the DA tool using terminal according to claim 5,
The DA tool use terminal, wherein the DA tool identification information is a window title or an execution image name of the operation screen of the DA tool and a process ID when the DA tool is executed. A plurality of DA tool use terminals each having one or more DA tools, which are design support software using a computer, are connected to the plurality of DA tool use terminals via a network, and the DA tools in the DA tool use terminal are connected to each other. A DA tool use terminal program in a DA tool management system comprising a DA tool management server for managing the operating status of a tool,
In the computer of the DA tool using terminal,
An operation status detection step of detecting operation start and operation end of the DA tool based on a display state of a predetermined operation screen displayed by the DA tool;
When the DA tool operation start or operation end is detected in the operation detection step, the DA tool using terminal identification information, the DA tool identification information, and the date and time of the DA tool operation start or operation end A DA tool utilization terminal program, comprising: performing an operation condition data transmission step of transmitting DA tool operation condition data including the information to the DA tool management server. In the program of the DA tool utilization terminal according to claim 7,
The DA tool use terminal program, wherein the DA tool identification information is a window title or an execution image name of the operation screen of the DA tool and a process ID when the DA tool is executed. A plurality of DA tool use terminals each having one or more DA tools, which are design support software using a computer, are connected to the plurality of DA tool use terminals via a network, and the DA tools in the DA tool use terminal are connected to each other. A DA tool management server in a DA tool management system comprising a DA tool management server for managing the operating status of a tool,
The DA tool utilization terminal identification information, the DA tool identification information, and the DA tool operation start or operation end transmitted when the DA tool utilization terminal detects the operation start and operation end of the DA tool. Operating status data receiving means for receiving DA tool operating status data including date and time information;
A DA tool operating status totaling unit that sorts and aggregates the DA tool operating status data based on the identification information of the DA tool using terminal and the identification information of the DA tool, and generates operating status aggregated data; DA tool management server. The DA tool management server according to claim 9, further comprising:
A DA tool management server comprising DA tool appropriate number prediction simulation means for performing a simulation for predicting the appropriate installation number of the DA tool according to the usage demand of the DA tool based on the operation status summary data . A plurality of DA tool use terminals each having one or more DA tools, which are design support software using a computer, are connected to the plurality of DA tool use terminals via a network, and the DA tools in the DA tool use terminal are connected to each other. A DA tool management server program in a DA tool management system comprising a DA tool management server for managing the operating status of a tool,
The DA tool utilization terminal identification information, the DA tool identification information, and the DA tool identification information transmitted to the computer of the DA tool management server when the DA tool utilization terminal detects the start and end of operation of the DA tool, An operating status data receiving step for receiving DA tool operating status data including information on the date of starting or stopping the DA tool;
The DA tool operating status data is sorted and aggregated based on the DA tool utilization terminal identification information and the DA tool identification information, and a DA tool operating status aggregation step for creating operating status aggregation data is executed. The DA tool management server program. A DA tool management server program according to claim 11,
In the computer of the DA tool management server,
A DA tool management characterized by executing a DA tool appropriate number prediction simulation step for performing a simulation for predicting the appropriate installation number of the DA tool in accordance with the usage demand of the DA tool based on the operation status summary data. Server program.

Images