JP5031662B2 - Information processing apparatus, setup support method, and setup support method - Google Patents

Description

  The present invention relates to a technique for setting up software in common for a plurality of apparatuses via a storage medium.

  Information processing devices used for water quality analysis and the like are often used in a form that is not connected to a network in consideration of security problems. In that case, when setting up the latest software, the software is installed on the Internet or the like. Can't download from a server on my network. Therefore, it is required to install the latest software with a simple operation and perform a trial run (hereinafter referred to as “setup”) for the information processing apparatus.

As a method of introducing software to a terminal that is not connected to a network, there is a method of interposing a storage medium. For example, in Patent Document 1, an agent and software are stored in a storage medium, the agent installs the software in the terminal at the timing when the storage medium is inserted into the terminal, and the introduction result is stored in the storage medium as inventory information. A method of transferring the inventory information to the asset management server at the timing of insertion into a terminal connected to the network is disclosed. This document describes that inventory information of terminals that are not connected to the network can be managed in the same manner as terminals that are always connected to the network.
JP 2004-178121 A

  Multiple information processing devices used for water quality analysis are often installed in laboratories, etc., and software that is common to these devices is set up when analysis software is upgraded. There can be a situation. As described above, when software is set up in an information processing apparatus used for water quality analysis or the like, an error may occur during the setup process.

  However, since information regarding errors during setup is not shared among multiple devices, and the user individually determines whether to set up software for each device. In many cases, the error that occurred in the above process occurred again during software setup for another device. The presence of such errors has been a major factor that reduces the efficiency of the setup work and requires time before the apparatus can be used. This problem cannot be solved even by using the technique disclosed in Patent Document 1.

  An object of the present invention is to provide an information processing apparatus, a setup support system, and a setup support method that can prevent the occurrence of errors during software setup in advance.

  The information processing apparatus according to the present invention includes a self-device information table that holds self-device information related to the configuration of the self-device, software that is set up in common with a plurality of devices (hereinafter referred to as “common software”), and common software setup work Holds information about the configuration of devices that have already been set up (this information is included in, for example, the registered device information 107 of the embodiment) and setup result information on common software for the devices that have been set up. An interface for reading the data of the storage medium, means for determining common software to be set up in its own device among the common software, and performing setup work corresponding to the determined common software from the storage medium via the interface Used equipment Information is compared, and the read setup operation completed device information is compared with the own device information stored in the own device information table. Having the same configuration device or a similar configuration device having a configuration similar to that of the own device according to a predetermined standard, and the same configuration device or similar configuration determined from the storage medium via the interface And a success / failure information output means for reading setup result information relating to the apparatus and outputting it as setup success / failure information of the determined common software.

  In an embodiment of the present invention, it is provided with the same reference table that designates hardware or software as a reference for determining the identity between the own device and another device, and the same / similarity determination means Among them, a device that has undergone a setup operation that matches the configuration of the own device with respect to the hardware or software specified in the same reference table is determined as the same component device.

  In another embodiment of the present invention, the storage medium operates for each of the plurality of devices for each operation test performed when common software is installed on the device. A test operation management table in which a combination of hardware and software is described, wherein the same / similarity determination means corresponds to the combination described in the test operation management table corresponding to the own device and the device on which the setup work has been performed; Compared with the combination described in the trial operation management table, among the devices that have been subjected to the setup work, a device that has been subjected to the setup work in which the number of operation tests that match the combination of the hardware and software is equal to or greater than a specified value. The similar configuration device is determined.

  In still another embodiment of the present invention, after the success / failure information output means outputs the setup success / failure information, the determined common software is installed in the own device, and the installation result information is shared with the own device. As software setup result information, there is provided an installation means for writing to the storage medium in association with the determined common software.

  In still another embodiment of the present invention, an operation test is performed when the determined common software is installed in the own device, and the result of the operation test is set as the common software setup result information for the own device. And test means for writing to the storage medium in association with the common software.

  In any one of the above embodiments, the storage medium holds a setup management table representing a correspondence relationship between common software and each of the plurality of devices, and the means for determining the software is configured to store the storage via the interface. The setup management table is read from the medium, and among the common software, the common software corresponding to the own device in the read setup management table can be determined as the common software to be set up in the own device.

  A setup support system of the present invention is a system for setting up software provided from a management system in common to a first device and a second device using a storage medium, and the management system includes the first Means for storing software set up in common with one apparatus and the second apparatus (hereinafter referred to as “common software”), registration apparatus information regarding the configuration of the first apparatus, common software, and the registration apparatus Means for associating information with the storage medium, and the first device comprises means for storing the common software setup result information for the device in the storage medium in association with the common software; The second apparatus includes an own apparatus information table for holding own apparatus information relating to the configuration of the own apparatus, and the management system. Of the common software stored in the storage system, the registered device information stored in the management system, the interface for reading the storage medium data holding the setup result information stored in the first device, and the common software. Means for determining common software to be set up in a device, and reads out registered device information corresponding to the determined common software from the storage medium via the interface, and is stored in the read registered device information and the own device information table. Of the first device, the same configuration device having the same configuration as the configuration of the own device or a similar configuration device having a configuration similar to the configuration of the own device according to a predetermined standard Same / similarity determining means to be determined and the storage medium via the interface Reads the setup result information about the same configuration device or similar configuration apparatus al the determined, characterized in that it comprises a means for outputting a setup success information of the common software that the determined.

  The setup support method of the present invention includes software that is set up in common for a plurality of devices (hereinafter referred to as “common software”), device information that has been set up for a configuration of devices that have been set up for common software, The step of determining the common software to be set up in its own device among the common software from the storage medium holding the common software setup result information for the device for which the setup work has been performed, and the setup corresponding to the determined common software from the storage medium Read the completed device information, compare the read setup operation completed device information with the own device information held in the own device information table holding the own device information related to the configuration of the own device, and perform the setup. Determining the same configuration device having the same configuration as the configuration of the own device or a similar configuration device having a configuration similar to the configuration of the own device, among the already-executed devices, and determining from the storage medium Reading out the setup result information relating to the same configuration device or similar configuration device, and outputting the setup result information as the determined common software setup success / failure information.

  According to the present invention, when software is set up in the own device, the other device (same component device) having the same configuration as that of the own device or the other device (similar component device) having a configuration similar to that of the own device. ) Is output as setup success / failure information, so that the user knows in advance the possibility that an error similar to the error at the time of setup of the software that has occurred in other devices will occur in advance. Thus, the occurrence of the error can be prevented.

  Embodiments of the present invention will be described below with reference to the drawings.

  In the present embodiment, an apparatus configuration and a system configuration that can prevent an error that has occurred during software setup for the first device from occurring again during setup for the second device, and a configuration based on these configurations. How to prevent errors during software setup in advance. Note that the first device is an information processing device for which software setup work has already been performed, and the second device is an information processing device for which software setup work has not been performed or is being performed. In this embodiment, software setup refers to installing software in an information processing apparatus and performing a test run.

  FIG. 1 shows a configuration of a setup support system 1 including analysis apparatuses 118 to 122 of the present invention and a data flow in the system.

  The setup support system 1 includes a management system 2 and a plurality of analyzers 118 to 122 for water quality analysis. In the present embodiment, software (hereinafter referred to as “common software”) that is provided for setting up in common from the management system 2 to the analysis apparatuses 118 to 122 includes, for example, GUI software, data analysis software, and sequence control. Software, driver software, and the like are included.

  The management system 2 stores in the storage medium 114 one or more common software 156 and a setup management table (hereinafter referred to as “scenario”) 108 representing the correspondence between each common software 156 and each of the analysis apparatuses 118 to 122. Is configured to do. As the storage medium 114, any storage medium capable of reading and writing data, such as a storage medium (such as a memory stick) incorporating a flash memory or a CD-RW (Compact Disk ReWritable), can be used. In this embodiment, a storage medium that incorporates a flash memory and can read and write data by connecting to a USB terminal is adopted. The contents of the scenario 108 will be described later.

  In addition, the management system 2 includes a relay client 109 provided in an analysis room including the analysis devices 118 to 122, and a service server 101 that is communicably connected to the relay client 109 via a network (for example, the Internet). Consists of.

  For example, when the storage medium 114 is connected, the relay client 109 transmits an identifier (analysis room identifier) 104 that identifies a group of analysis apparatuses 118 to 122 managed by the service server 101 to the service server 101. At the same time, it requests transmission of registered device information 107, scenario 108, software related information 124, and setup target device number 128 for storage in the storage medium 114, and stores the received data in the storage medium 114. Further, the analysis room identifier 104, the scenario execution information 105 indicating the execution status of the scenario 108 stored in the storage medium 114, and the latest configuration information (latest configuration information) of the analysis devices 118 to 122 stored in the storage medium 114. ) 106 is transmitted to the service server 101.

  The analysis room identifier 104 may be stored in the storage medium 114 by the apparatus manufacturer that provides the analysis apparatuses 118 to 122, or may be written in the storage medium 114 by the user. In the service server 101, the configuration information of each analysis device 118 to 122 is managed as the registered device information 107 in association with the analysis room identifier 104.

  The registered device information 107 is information related to the configuration of each analysis device 118 to 122 managed by the service server 101. The software-related information 124 includes common software 156 corresponding to each analysis device 118 to 122 managed by the service server 101, and a test run program (trial operation performed when the common software is installed in the analysis device 118 to 122). Script) 157 and information including a test operation management table 158 in which a combination of hardware and software in the analysis devices 118 to 122 operating during the test operation is described. The number 128 of setup target devices is the number of analysis devices corresponding to the common software 156 provided from the service server 101, and specifically has the same value as the number of records for each device stored in the scenario 108. . Details of the registration device information 107 and the trial operation management table 158 will be described later.

  In response to a request from the relay client 109, the service server 101 registers the common software setup progress information and the latest device information 106, or receives the analysis room received from the relay client 109 in response to a request from the relay client 109. The scenario 108 corresponding to the analysis device specified by the identifier 104 is created, and the registration device information 107 related to the analysis device 107, the software related information 124 corresponding to the scenario 108, and the number 128 of setup target devices are stored in the relay client 109. Send to.

  When the relay client 109 receives the registered device information 107, the scenario 108, the software related information 124, and the setup target device number 128 from the service server 101, the relay client 109 stores these data in the storage medium 114. The storage medium 114 storing these data is connected to each analyzer 118-122 by a researcher in the laboratory.

  For example, when the storage medium 114 is connected to the analysis device 122, in the process of setting up the common software 156, the analysis device 122 executes execution information (self-scenario) 127 corresponding to the own device among the scenarios 108. (Scenario execution information) 111, the number of setup not executed devices 129, and in some cases, the latest configuration information of the own device (latest own device information) 117 are written in the storage medium 114. The self-scenario execution information 111 includes information on the result of setting up the common software 156 for the self-device. The number of unexecuted setup devices 129 is the number of analyzers that have not been set up for the common software 156. Specifically, each time the setup work for the common software 156 for each analyzer is started, The number of devices 128 to 1 is a decremented value.

  On the other hand, from the storage medium 114, information on the result of setup of the common software 156 for other devices (other device setup result information) 115, information on the configuration of other devices (other device information) 125, and registered device information 107 related to the own device. Of the information (registered own device information) 116, the own scenario 127, and the software related information 124, information (self software related information) 126 corresponding to the own device and the number 128 of setup target devices are read into the analysis device 122.

  Thereafter, when the storage medium 114 is connected to the relay client 109, the scenario execution information 105 regarding the analysis devices 118 to 122 for which the setup operation of the common software 156 has been performed, and the latest configuration information regarding any of the analysis devices 118 to 122 are stored. When stored in the storage medium 114, the latest device information 106, the number of setup target devices 128, and the number of setup not executed devices 129 are read from the storage medium 114 to the relay client 109.

  Hereinafter, the analysis apparatus 122 is the second apparatus, and one or more other apparatuses 118 to 121 are the first apparatuses. The configuration of the analysis apparatus 122 and the storage medium 114 are executed when the analysis apparatus 122 is connected. The processing procedure and the processing procedure executed when the storage medium 114 is connected to the relay client 109 will be described. The configuration of the other devices 118 to 121 and the processing executed when the storage medium 114 is connected The contents of are the same.

  FIG. 2 shows an example of the table configuration of the registration device information 107 related to the analysis device 122.

  The registered device information 107 is information representing hardware and software provided in the analysis device 122. Specifically, the registered device information 107 includes an identifier 200 that identifies a device, a series identifier 201 that identifies a device type, a controller identifier 202 that is provided in the device, and a unit that is provided in the device. The number 203, the unit identifier 204, the number 205 of accessories provided for each unit, the accessory identifier 206, the number 208 of common software installed in the apparatus, and the number 209 of installed GUI software An identifier 210 of each GUI software, a number 212 of installed data analysis software, an identifier 213 of each data analysis software, a number 215 of installed sequence control software, an identifier 216 of each sequence control software, Installed driver software The number 218 of A, composed of the identifier 219 Metropolitan of each driver software. It is assumed that the service server 101 holds registered device information 107 for each device to be managed. It should be noted that the configuration of the registered device information 108 relating to the other analysis devices 118 to 121 and the configuration information of each device that is held in each analysis device 118 to 122 and stored in the storage medium 114 at a predetermined timing (see FIG. 1). The configuration of the latest device information 117) is the same as the table configuration in FIG.

  FIG. 3 shows (A) the table configuration of the scenario 108 and (B) the table configuration of the scenario execution information 105.

  The scenario 108 includes information specifying the common software 156 corresponding to each analysis device 118 to 122 managed by the service server 101, and a test run related to a test run executed when the common software 156 is installed. It is a table which manages the information which specifies the management table 158, and the information which specifies the trial run script 157 for performing a trial run in association with each other. Specifically, this table includes an identifier 1703 for each device for which the common software 156 is set up, a number 1713 of the common software 156 set up for each device, an identifier 1704 for each common software 156, and the common software 156. It consists of an identifier 1705 of a test run management table 158 corresponding to a test run performed when installed, and an identifier 1706 of a test run script 157.

  The scenario execution information 105 includes information indicating whether the setup work of the common software 156 specified by the scenario 108 has been performed for each of the devices 118 to 122, and the setup result information when the setup work has been performed. Is a table that holds

  Specifically, this table includes a device identifier 1709, a setup execution flag 1710 indicating whether or not the setup operation of the common software 156 has been performed on the analysis device corresponding to the device identifier 1709, and the installation result of the common software 156. 1711, the total result 1712 of the test run, a test item identifier 1714 for identifying one or a plurality of operation tests included in the test run, and an individual result 1716 representing the result of each operation test.

  FIG. 4 shows the configuration of the trial operation management table 158 included in the software related information 124. The trial operation management table 158 describes, for each operation test included in each trial operation, a combination of hardware and software in the analyzers 118 to 122 that operate at the time of the operation test. The trial operation management table 158 is created for each trial operation composed of one or a plurality of operation tests, and is stored in the storage medium 114 from the service server 101 as necessary.

  Specifically, this table includes a test item identifier 602 that identifies each operation test that constitutes a test run, a number 603 of units (related units) that operate in the operation test corresponding to the test item identifier 602, and each Related unit identifier 604, number 605 of accessories (related accessories) that operate during an operation test corresponding to test item identifier 602, identifiers 606 of each related accessory, and operations corresponding to test item identifier 602 It consists of the number 608 of software (related software) that operates during the test, and an identifier 609 of each related software.

  FIG. 5 shows the structure of the storage medium 114. The storage medium 114 includes an area 501 for storing the analysis room identifier 104, an area 502 for storing the latest apparatus information 106, an area 503 for storing the registered apparatus information 107, an area 504 for storing the scenario 108, and scenario execution information. 105, an area 506 for storing common software 156, an area 507 for storing a test run management table 158, an area 508 for storing a test run script 157, an area 509 for storing the number of setup target devices, And an area 510 for storing the number of setup unexecuted devices.

  FIG. 6 shows the configuration of the relay client 109.

  For example, when the storage medium 114 is connected, the relay client 109 transmits an identifier (analysis room identifier) 104 that identifies a group of analysis apparatuses 118 to 122 managed by the service server 101 to the service server 101. In addition, transmission request means 151 that requests transmission of registered device information 107, scenario 108, software related information 124, and number of setup target devices 128 to be stored in the storage medium 114, and stores the received data in the storage medium 114. Have Further, the analysis server identifier 104, the scenario execution information 105 indicating the execution status of the scenario 108 stored in the storage medium 114, and the latest apparatus information 106 of the analysis apparatuses 118 to 122 stored in the storage medium 114 are stored in the service server. 101, registration request means 152 that transmits to the server 101 and requests registration of the progress information of the setup of the common software 156 and the latest configuration information 106. The transmission request unit 151 and the registration request unit 152 are functional units that are realized by the central processing unit (CPU) of the relay client 109 executing a predetermined program. Specific procedures of processing by these units are as follows. Will be described later with reference to FIG.

  The relay client 109 employed in this embodiment includes a central processing unit (CPU), a storage device (such as RAM and HDD), an input device (such as a mouse and keyboard), an output device (such as a display and speaker), and communication. This is realized by an information processing apparatus having a general configuration including apparatuses (such as an Ethernet adapter and a USB terminal). The same applies to the service server 101 and the analysis apparatuses 118 to 122.

  FIG. 7 shows the configuration of the service server 101.

  The service server 101 creates data such as the scenario 108 in response to a request from the storage client 102 and the relay client 109 for storing the registered device information 107, the software related information 124, and the scenario management table 159, and sends the data to the relay client 109. A scenario creating unit 153 for transmission and a data storage unit 154 for storing setup progress information and latest device information 106 in the storage unit 102 in response to a request from the relay client 109 are provided. The scenario management table 159 is a table (not shown) representing the corresponding relationship among the combination of hardware and software that the apparatus managed by the service server 101 can have, the common software 156, the test run management table 158, and the test run script 157. ). The storage means 102 is realized by a storage device such as a memory (RAM or the like) or an HDD. The scenario creation means 153 and the data storage means 154 are functional means realized by the central processing unit (CPU) of the service server 101 executing a predetermined program. Specific procedures of processing by these means are as follows. Will be described later with reference to FIG.

  FIG. 8 shows the configuration of the analyzer 122 of the embodiment. The analysis device 122 includes a host computer 303 having a storage medium IF (USB terminal in this embodiment) 302 for reading data of the storage medium 114 and a plurality (for example, three) each having accessories 325, 326, and 327. ) Units 322 to 324 and a controller 320 for controlling the operation of each unit 322 to 324. The host computer 303 and the controller 320 are connected by a communication cable 319 such as an RS-232C cable, a USB cable, or a LAN cable. The controller 320 and the units 322 to 324 are also connected by the communication cable 321 in the same manner as described above.

  In this embodiment, the analysis device 122 is a device for sampling water quality data and analyzing the water quality. For example, the unit 322 is a pump for pumping water (sample), and the unit 323 is a specific component in the sample. The unit 324 is an injection that injects a sample into the column. The accessories 325 to 327 are components having a function of improving the functions of the units 322 to 324, and are provided according to the units 322 to 324. The controller 320 has a function of controlling each of the units 322 to 324 in accordance with an instruction from the host computer 303 and passing the water quality data acquired by the unit 323 to the host computer 303, for example.

  In addition to the storage medium IF 302, the host computer 303 includes storage means 123, software determination means 351, identity / similarity determination means 352, success / failure information output means 353, installation means 354, test means 355, and auxiliary calculation means 356.

  The storage unit 123 includes the own device information table 305, the same configuration device determination policy 408, the similar configuration device determination policy 409, the setup related device management table 330, the number of related devices 361, the own device variation information 362, the pre-verification software 328, and the installer software. 307, commissioning software 308, general-purpose GUI software 309, routine GUI software 310, a plurality (eg, three) of data analysis software 311a to 311c, a plurality (eg, two) of sequence control software 314a, 14b, and a plurality (eg, three) ) Driver software 316a to 316c. The storage unit 123 is realized by a storage device such as a memory (RAM or the like) or an HDD.

  The own apparatus information table 305 is a table that holds information (own apparatus information) related to the latest configuration of the analysis apparatus 122 (own apparatus), and the configuration is the same as the table configuration shown in FIG.

  The identical component device determination policy 408 is a table (identical reference table) that specifies hardware or software as a reference for determining the identity of the own device 122 and the other devices 118 to 121. FIG. 9 (A). The user determines the component that is the reference for determining the identity, and stores “1” in the flag column corresponding to the component in the table of the identical component device determination policy 408 so that the component is the same. It becomes the standard for judging sex. In the present embodiment, the unit and the sequence control software are defined as components that serve as a reference for identity. The specific contents of the identity determination will be described later.

  The similar configuration device determination policy 409 is a table that defines a criterion for determining a similar configuration device having a configuration similar to that of the own device 122 among the other devices 118 to 121. The table configuration is shown in FIG. . In the present embodiment, the similar configuration device determination policy 409 corresponds to a test operation management table 158 (FIG. 4) corresponding to the own device 122 and a device for which the common software 156 has been set up among the other devices 118 to 121. Compared with the test operation management table 158 (FIG. 4), among the devices that have undergone the setup work, the devices that have undergone the setup work in which the number of operation tests that match the combination of hardware and software are equal to or greater than a prescribed value (for example, three). Is a similar component device. The similar configuration device determination policy 409 may be determined by either the administrator or the common software manufacturer. Specific contents of the similarity determination will be described later.

  The setup related device management table 330 stores information on other devices (setup related devices) for which the setup work of the common software 156 has been performed among other devices associated with the common software 156 set up in the own device 122. This table is created when the common software 156 is set up for the device 122 and stored in the storage unit 123. Details of the setup-related device management table 330 will be described later. The number of related devices 361 is the number of the setup related devices.

  The own device fluctuation information 362 includes the registered own device information 116 included in the registered device information 107 managed by the storage unit 102 of the service server 101 and the latest own device information 117 held in the storage unit 123 of the own device 122. It is the information showing the structure which is different between.

  The pre-verification software 328 determines the common software 156 set up in the own device, determines whether the own device and the other device have the same or similar configuration, and sets up the common software 156 in the same configuration device and the similar configuration device. It is software that defines processing procedures such as output of result information.

  The installer software 307 is software that defines a procedure for installing the common software 156 stored in the storage medium 114 on the own device 122.

  When the common software 156 is installed in the own device 122, the test run software 308 reads the test run script 157 stored in the storage medium 114 and performs a test run in conjunction with the read test run script 157. Software that defines the procedure.

  The software determination unit 351 reads the self-scenario 127 from the storage medium 114 via the storage medium IF 302, identifies the common software 156 corresponding to the self-device 122 in the read self-scenario 127, and identifies the common software 156. The common software 156 is determined as the common software 156 set up in the own apparatus 122. If the scenario 108 stored in the storage medium 114 is information related to the setup of the common software 156 for the analyzers 118 to 122 in the same analysis chamber, one or a plurality of common software stored in the storage medium 114 is stored. All of 156 are determined as common software 156 to be set up in its own apparatus. On the other hand, if the scenario 108 stored in the storage medium 114 is information related to the setup of the common software 156 for an apparatus in another analyzer, only a part of the common software 156 stored in the storage medium 114 is It may be determined as the common software 156 set up in its own device.

  The identical / similarity determining unit 352 reads the configuration information (device information on which setup work has been performed) of the device on which the setup work has been performed corresponding to the common software 156 determined by the software determination unit 351 from the storage medium 114 via the storage medium IF302. The read-out setup work completed device information is compared with the own device information held in the own device information table 305, and the same configuration device having the same configuration as that of the own device 122 among the setup work completed devices Alternatively, a similar configuration device having a configuration similar to the configuration of its own device 122 is determined according to a predetermined criterion. The setup work completed device information is information related to the configuration of another device for which the setup work of the same common software 156 as the common software 156 set up in the own device 122 has been performed. In the present embodiment, the same component device is determined according to the same component device determination policy 408, and the similar component device is determined according to the similar component device determination policy 409. Details of the method of determining the same configuration device and the similar configuration device will be described later.

  The success / failure information output unit 353 reads the other device setup result information 115 related to the same component device or similar component device determined by the same / similarity determination unit 352 from the storage medium 114 via the storage medium IF 302 and reads the other device setup result read out. The information 115 is output as setup success / failure information of the common software 156 determined by the software determination unit 351. The output setup success / failure information is displayed on a display provided in the analyzer 122, for example.

  After the success / failure information output unit 353 outputs the setup success / failure information, the installation unit 354 installs the common software 156 for the own device 122, and sets the installation result information as the setup result information of the common software 156 for the own device 122. Are written in the storage medium 114 in association with the common software 156. Specifically, the setup result information in the own device 122 is stored in the scenario execution information 105 (FIG. 3B) held in the scenario execution information storage area 505 (FIG. 5) of the storage medium 114. When installation result information is stored in the scenario execution information 105, it is held in the scenario 108 (FIG. 3A) based on the value of the device identifier 1709 in the record in which the installation result is stored. Since the common software identifier 1704 is specified, the setup result information corresponds to the common software 156.

  The test unit 355 performs a test run when the common software 156 is installed in the own device 122, and stores the result of the test run in association with the common software 156 as setup result information of the common software 156 for the own device 122. Write to 114. Specifically, the result of the trial run is stored in the scenario execution information 105 held in the scenario execution information storage area 505 of the storage medium 114. The reason why the result of the trial operation corresponds to the common software 156 is the same as described above.

  The auxiliary calculation means 356 is executed by the software determination means 351, the same / similarity determination means 352, the success / failure information output means 353, the installation means 354, and the test means 355 among the above-described various processes executed in the analyzer 122. Execute processing other than processing.

  The software determination unit 351, the identity / similarity determination unit 352, and the success / failure information output unit 353 are functional by executing the pre-verification software 328 read from the storage unit 123 by the central processing unit (CPU) of the analysis device 122. To be realized. The installation unit 354 is functionally realized by the installer software 307 read from the storage unit 123 by the CPU of the analysis device 122. The test unit 355 is functionally realized by the test run software 308 read from the storage unit 123 and the test run script read from the storage medium 114 by the CPU of the analyzer 122. The auxiliary calculation unit 356 is functionally realized by the CPU of the analyzer 122 executing the pre-verification software 328, the installer software 307, the test operation software 308, or the test operation script as necessary.

  FIG. 10 shows a table configuration of the setup related device management table 330 held in the storage unit 123 of the analyzer 122. This table is created by the same / similarity determination means 352 in the process of setting up the common software 156 in the own apparatus 122 and stored in the storage means 123.

  The setup related device management table 330 includes a setup related device identifier 1602, the same device device flag 1603, an installation result 1609, a test run total result 1610, a similar configuration device flag 1604, a related test item number 1611, a related test item identifier 1606, and a result 1612.

  The identical component device flag 1603 is information indicating whether the setup related device is the same component device, and the similar component device flag 1604 is information indicating whether the setup related device is the similar component device.

  The installation result 1609 and the total test operation result 1610 are information stored only when the setup-related devices are the same component devices. The installation result 1609 is the same as the content of the installation result 1711 of the scenario execution information 105 (FIG. 3B) held in the scenario execution information storage area 505 of the storage medium 114. The test run total result 1610 is the same as the content of the test run total result 1712 of the scenario execution information 105 (FIG. 3B) held in the scenario execution information storage area 505 of the storage medium 114.

  The related test item number 1611, the related test item identifier 1606, and the result 1612 are information stored only when the setup related device is a similar configuration device. The related test item identifier 1606 is the same as the content of the test item identifier 602 stored in the test operation management table 158 (FIG. 4) corresponding to the similar configuration device among the setup related devices, and the related test item number 1611 is , The number of related test item identifiers 1606. The result 1612 is a result for each operation test corresponding to each related test item identifier 1606 among one or a plurality of operation tests constituting the test run. Specifically, the similar configuration device among the respective setup related devices. This is the same as the content of the individual result 1716 stored in the scenario execution information corresponding to (FIG. 3).

  FIG. 11 shows a procedure of processing executed when the storage medium 114 is connected to the analyzer 122.

  First, when the storage medium 114 is connected to the storage medium IF 302, the auxiliary calculation means 356 of the analysis apparatus 122 determines whether or not the execution of the scenario 108 has been completed, that is, all corresponding to the device identifier 1703 described in the scenario 108. It is determined whether or not the setup operation of the common software 156 for the analyzers is completed (step 801).

  Specifically, referring to the value stored in the number of setup unexecuted device storage areas 510 of the storage medium 114, if the value is 0, it is determined that the execution of the scenario 108 has been completed, and is greater than 0. If it is a value, it is determined that the execution of the scenario 108 is not completed.

  If it is determined in step 801 that the execution of the scenario 108 has been completed, the auxiliary computing means 356 sends a message indicating that the scenario 108 has been completed (for example, “Common software setup is complete. Relay client. Display a message such as “Please connect the storage medium to” on the display screen (step 802), and the process is terminated.

  On the other hand, if it is determined in step 801 that the execution of the scenario 108 has not been completed, the auxiliary calculation means 356 determines whether the self-scenario 127 has been completed, that is, whether the common software 156 has been set up for the self-device 122. It is determined whether or not it is completed (step 803).

  Specifically, from the scenario execution information 105 (FIG. 3B) stored in the scenario execution information storage area 505 of the storage medium 114 using the device identifier 200 of the own device information table 305 (FIG. 2) as a search key. The device identifier 1709 having the same value is searched. If the setup execution flag 1710 of the record corresponding to the device identifier 1709 found by the search is 0, it is determined that the execution of the self scenario 127 is not completed. It is determined that the scenario has been executed.

  If it is determined in step 803 that the execution of the self-scenario 127 has been completed, a message indicating that fact (for example, a message such as “Common software setup for this analyzer has been completed”). Is displayed on the display screen (step 804), and the process is terminated. Alternatively, based on the device identifier 1709 of the scenario execution information 105 (FIG. 3B) stored in the storage medium 114, a record relating to the other devices 118 to 122 is specified, and the value of the introduction execution flag 1710 is 0. A message prompting you to select another device and set up the common software 156 for the other device (for example, a message such as “Please insert storage media into analyzer A and analyzer C.”) is displayed on the display. The next operation to be performed may be presented by displaying on the screen.

  On the other hand, if it is determined in step 803 that the execution of the self-scenario 127 has not been completed, the identity / similarity determining unit 353 executes pre-verification (step 805).

  When the pre-verification is executed, the setup result information of the common software for the setup related device is stored in the setup related device management table 330 (FIG. 10) held in the storage unit 123 of the analysis device 122. The procedure of the pre-verification process (step 805) will be described later with reference to FIGS.

  After completing Step 805, the success / failure information output means 353 presents a pre-verification result (Step 806).

  Specifically, the setup related device management table 330 is referred to, and the setup result information regarding the setup related device is output as the setup success / failure information of the common software 156. Examples of the setup success / failure information that is output include a message such as “An error has occurred during installation on another device with the same configuration of the common software α and the common software β to be set up” or “Setup The common software α and common software β you are trying to set up are normally set up for other devices with the same configuration, or the message “The common software β you are trying to set up is similar in configuration. An error has occurred during the trial run when the setup work was performed on the device of "." If no information is stored in the setup-related device management table 330, a message indicating that the common software 156 to be set up is software set up for the first time in the device in the analysis room (for example, “Setup is about to be performed”). There is no setup result information for other devices related to the common software α. If an error occurs during the setup process, please contact the administrator. ”

  Before the user sets up the common software 156 with respect to the analysis device 122, the pre-verification result as described above is presented, so that an error that may occur at the time of setting up the common software 156 in the analysis device 122 is preliminarily determined. And can determine whether to continue the setup work. For example, when setup success / failure information with a negative content is presented as a pre-verification result, the user can take measures such as making an inquiry to the administrator or the manufacturer of the common software 156 without performing the setup. Thus, it is possible to prevent the same error as that generated in the above step from occurring again in the analyzer 122.

  Next, the success / failure information output means 353 displays a message such as “Do you want to continue the setup of the common software?” On the display screen, accepts input of information regarding whether or not the user intends to continue the setup work, and sets up the setup. It is determined whether or not to continue the work (step 807). The user can determine whether or not to continue the setup operation after understanding the pre-verification result, and can input information regarding the intention of continuing through the input device.

  In step 807, when the success / failure information output means 353 determines that the setup work is not continued, that is, when an input of information to stop the setup work is received from the user, the success / failure information output means 353 ends the process. .

  On the other hand, when the success / failure information output unit 353 determines in step 807 that the setup operation is to be continued, that is, when the input of information indicating that the setup operation is continued is received from the user, the auxiliary calculation unit 356 stores the storage medium 114. The record corresponding to the identifier of the own device 122 in the scenario execution information 105 stored in the record is specified, and 1 is written in the setup execution flag 1710 in the record (step 808).

  Next, the auxiliary calculation means 356 decrements 1 from the value of the number of setup unexecuted devices storage area 510 of the storage medium 114 (step 809). Specifically, the data in the area 510 is once read, and 1 is decremented from the read value, and then the data is written back to the number of setup unexecuted apparatus storage area 510 on the storage medium 114.

  Then, the software determining unit 351 determines one or a plurality of common software 156 to be installed in the own apparatus 122 (Step 810).

  Specifically, among the records of the scenario 108, a record corresponding to the identifier 1703 of the own device 122 (self scenario 127) is specified, and the common installation is performed on the own device 122 based on the software identifier 1704 in the specified record. Software 156 is determined.

  Next, the installation unit 355 installs the common software 156 determined by the software determination unit 351 in the own apparatus 122 (step 811).

  Specifically, using the software identifier 1704 of the determined common software, the common software 156 to be installed is read from the software storage area 506 of the storage medium 114, and installation is performed on the own device 122.

  The installation unit 355 stores the installation result information in the storage medium 114 (step 812).

  Specifically, when the common software 156 is successfully installed, a record corresponding to the own device 122 in the scenario execution information 105 (FIG. 3B) held in the scenario execution information storage area 505 of the storage medium 114 is displayed. Specify 1 and store 1 in the installation result 1711 in the record. On the other hand, when installation fails, −1 is stored in the installation result 1711.

  Next, the installation unit 354 determines whether or not the installation is successful (step 813). If the installation is unsuccessful, the process ends. On the other hand, if the installation is successful, the process proceeds to the next process.

  When the installation unit 354 determines that the installation is successful, the test unit 355 performs a test run (step 814).

  Specifically, the test run script 157 to be executed is read from the test run script storage area 508 in the storage medium 114 using the test run script identifier 1706 of the self scenario 127 in the scenario 108. The read test run script 157 is executed by the CPU of the own device 122.

  Next, the test means 355 stores the test run result information in the storage medium 114 (step 815).

  Specifically, a record corresponding to the own device 122 is specified in the scenario execution information 105 (FIG. 3B) held in the scenario execution information storage area 505 of the storage medium 114, and the test run comprehensive result in the record 1711, the test item identifier 1714, and the individual result 1716 store the test run result information. In the present embodiment, the result information (1 for success and 0 for failure) for each operation test constituting the test run is stored in the individual result 1716, and the overall result (one or one if all test item results are successful). However, if there is a failure, -1) is stored in the test run total result 1712.

  Then, the front auxiliary calculation means 356 executes Step 801 again.

  FIG. 12 shows the procedure of the pre-verification process (step 805 in FIG. 11) by the identity / similarity determination means 353.

  First, the identity / similarity determination unit 353 verifies the fluctuation state of the self-device information table 305 of the analysis device 122 (step 1801). The procedure of the change state verification process (step 1801) will be described later with reference to FIG.

  Next, the identity / similarity determination unit 353 determines whether or not the self-device information table 305 has changed (step 1802).

  If it is determined in step 1802 that there is no change in the own apparatus information table 305, the identity / similarity determining means 353 determines the contents of the own apparatus fluctuation information 362 stored in the storage means 123 (regardless of the presence or absence of the contents). ) Is cleared to 0 (step 1803).

  Next, the identity / similarity determining means 353 identifies a setup-related device (step 1804). The procedure of the setup related device specifying process (step 1804) will be described later with reference to FIG.

  After identifying the setup-related device, the identical / similarity determination unit 353 acquires setup result information of the setup-related device of the same configuration device among the setup-related devices (step 1805). The processing procedure of step 1805 will be described later with reference to FIG.

  Then, the identical / similarity determination unit 353 acquires setup result information of similar configuration devices among the setup related devices (step 1806). The processing procedure of step 1806 will be described later with reference to FIG.

  On the other hand, if it is determined in step 1802 that there is a change in the self apparatus information table 305, the identity / similarity determination means 353 stores the self apparatus fluctuation information 362 in the storage means 123 of the analyzer 122 (step 1807). .

  Specifically, information indicating the difference between the registered device information 116 stored in the storage medium 114 and the content of the device information table 305 stored in the storage unit 123 of the device 122 is used as the device fluctuation information 362. To store. For example, it is conceivable to store configuration information included only in one of the registered device information 116 and the host device information table 305, or configuration information included only in the host device information table 305. It should be noted that information indicating whether or not the contents of the own device information table 305 have changed (for example, 1 if there is a change, 0 if there is no change) is stored in a predetermined area (for example, the storage unit 123 of the analyzer 122). The information may be stored in the own device information table 305 or the like.

  Next, the identity / similarity determination means 353 stores the information of the own apparatus information table 305 stored in the storage means 123 of the analysis apparatus 122 in the latest apparatus information storage area 502 of the storage medium 114 (step 1808).

  Then, the identity / similarity determination means 353 prompts the user to obtain the latest common software corresponding to the device 122 (for example, “The device configuration has been updated. In order to obtain the common software corresponding to the current device configuration. And the like "on the display screen (step 1809), and the process is terminated. This is because when the content of the own device information table 305 is updated from the registered own device information 116, it is preferable to set up the common software 156 according to the current own device information.

  FIG. 13 shows the procedure of the fluctuation status verification process (step 1801 in FIG. 12).

  First, the identity / similarity determination unit 353 uses the device identifier 200 of the own device 122 held in the own device information table 305 as a search key, and the registered own device stored in the registered device information storage area 503 of the storage medium 114. Information 116 is searched, and registered device information 116 found by the search is read (step 901).

  Next, the identity / similarity determination unit 353 reads the latest own device information from the storage unit 123 of the own device 122 (step 902). Specifically, the contents of the own device information table 305 held in the storage unit 123 are read.

  Then, the identity / similarity determination unit 353 compares the registered own device information 116 read from the storage medium with the latest own device information read from the storage unit 123, and extracts information representing the difference (step 903). The process proceeds to step 1802 in FIG.

  FIG. 14 shows the procedure of the setup related device identification process (step 1804 in FIG. 12).

  First, the identity / similarity determining unit 353 acquires the identifier of the common software 156 corresponding to the own device (step 1501).

  Specifically, the self scenario 127 is stored in the scenario storage area 504 of the storage medium 114 using the device identifier 221 of the self device 122 held in the self device information table 305 in the storage unit 123 of the self device 122 as a search key. A search is performed, and the value of the software identifier 1704 described in the self-scenario 127 found by the search is acquired.

  Next, the identity / similarity determination means 353 identifies another device associated with the same common software 156 as the own device 122 (step 1502).

  Specifically, using the value of the software identifier 1704 acquired in step 1501, one or a plurality of records including the software identifier 1704 having the same value is detected from the scenario storage area 504 of the storage medium 114. The value of the described device identifier 1703 is acquired. In this embodiment, when a plurality of software identifiers 1704 are described in the self-scenario 127, a record in which the combination of identifiers completely matches is detected. However, a threshold value for the number of combinations is defined in advance. In addition, a record in which the number of matching combinations is equal to or greater than a threshold may be detected.

  Then, the identical / similarity determination unit 353 detects other devices for which the setup work of the common software 156 has been performed among the other devices identified in Step 1502 and determines them as setup related devices (Step 1503).

  Specifically, the scenario execution information 105 stored in the storage medium 114 is read, and the corresponding record is searched using the value of the device identifier 1703 of the other device acquired in step 1502 as a search key. The records relating to the devices are sequentially referred to, the value of the device identifier 1709 described in the record in which 1 is stored in the setup execution flag 1710 is obtained, and another device corresponding to the value of the device identifier 1709 is set as the setup related device. decide.

  After step 1503, the identity / similarity determination unit 353 determines whether there is a setup-related device (step 1504).

  In step 1503, the identity / similarity determination unit 353 determines that there is no setup-related device if the identifier value of the setup-related device is not acquired, and proceeds to the processing of step 806 in FIG.

  On the other hand, if the identifier value of the setup related device is acquired, the identity / similarity determination unit 353 determines that there is a setup related device, and stores the number of setup related devices and the identifier in the storage unit 123 (step 1505). ).

  Specifically, the number of identifiers of the setup related device acquired in step 1503 is stored in the storage unit 123 of the own device 122 as the number of related devices 361, and the setup related device identifier is stored in the storage unit 123. Stored in the column of the setup-related device identifier 1602 of the management table 330 (FIG. 10).

  After step 1505, the identity / similarity determination means 353 proceeds to step 1805 in FIG.

  FIG. 15 shows the processing procedure of step 1805 in FIG.

  In this processing, the same / similarity determination means 353 is the hardware or software specified in the same configuration device determination policy 408 (FIG. 9A) among the setup related devices (in the embodiment, unit and sequence control software). A setup-related device that matches the configuration of the own device (the contents of the own device information table 330) is determined as the same component device. Details will be described below.

  First, the identical / similarity determination unit 353 reads the identical configuration device determination policy 408 from the storage unit 123 of the own device 122 (step 1001).

  Next, the identity / similarity determination unit 353 reads the contents of the own device information table 305 from the storage unit 123 of the own device 122 (step 1002).

  Then, the identity / similarity determination unit 353 reads configuration information from the storage medium 114 for each setup-related device (step 1003).

  Specifically, one value of the setup related device identifier 1602 is read from the setup related device management table 330 held in the storage unit 123 of the own device 122, and the read value of the setup related device identifier 1602 is used as a search key. The configuration information of the corresponding setup related device is retrieved from the registered device configuration storage area 503 stored in the storage medium 114 and read.

  Next, the identity / similarity determination unit 353 determines whether the own apparatus information read in step 1002 is the same as the configuration information of the setup related apparatus read in step 1003 (step 1004).

  Specifically, in the configuration information of the setup-related device, if the hardware or software specified in the same configuration device determination policy 408 read in step 1001 matches the configuration of the own device 122, it is the same. Judge that there is. In this embodiment, the value of the unit identifier 204 stored in the configuration information (FIG. 2) of the setup-related device matches the value of the identifier 204 of the units 322 to 324 of the own device 122, and If the value of the sequence control software identifier 216 stored in the configuration information matches the value of the identifier 216 of the sequence control software 314a, 314b of the own device 122, it is determined that they are the same. Note that the configuration information of the setup-related device and the configuration information of the own device 122 have the same table configuration, and both have been described with reference to FIG. In addition, the setup related apparatus determined to be the same as the configuration of the own apparatus 122 is treated as the same configuration apparatus in the following processing.

  When it is determined in step 1004 that the own device information and the configuration information of the setup related device are the same, the identical / similarity determination unit 353 sets the setup related device management table held in the storage unit 123 of the own device 122. 330 (FIG. 10) is turned ON (step 1005). Specifically, 1 is stored in the identical component device flag 1603.

Next, the identical / similarity determining unit 353 reads the setup result information of the same component device from the storage medium 114 (step 1007).
Specifically, using the value of the setup related device identifier 1602 of the setup related device management table 330 as a search key, the corresponding record is searched in the scenario execution information storage area 505 of the storage medium 114 and stored in the record found by the search. The value of the installed installation result 1711 and the value of the trial operation result 1712 are read.

  The identity / similarity determination unit 353 registers the setup result information read from the storage medium 114 in step 1007 in the setup-related apparatus management table 330 in the storage unit 123 (step 1008).

  Specifically, among the read setup result information, the value of the installation result 1711 is written in the column of the installation result 1609 of the setup related device management table 330, and the value of the test run result 1712 is written to the test run of the setup related device management table 330. Write in the column of result 1610.

  On the other hand, if it is determined in step 1004 that the own device information and the configuration information of the setup related device are not the same, the identity / similarity determination unit 353 manages the setup related device management held in the storage unit 123 of the own device 122. The identical component device flag 1603 of the table 330 is turned OFF (step 1006). Specifically, −1 is stored in the same component device flag 1603.

  Next, the same / similarity determination means 353 determines whether or not the processing of steps 1003 to 1008 has been completed for all the setup related devices (step 1009).

  Specifically, it is determined whether or not the processing in steps 1003 to 1008 has been completed for other devices corresponding to all the setup related device identifiers 1602 stored in the setup related device management table 330.

  If it is determined in step 1009 that the processing has not been completed, the identity / similarity determination unit 353 proceeds to step 1003 and executes the above-described processing (steps 1003 to 1008) for the next setup-related device. To do.

  On the other hand, if it is determined in step 1009 that the processing has been completed, the identity / similarity determination unit 353 proceeds to step 1806.

  FIG. 16 shows the processing procedure of step 1806 in FIG.

  In this process, the identical / similarity determining unit 353 determines the combination of hardware and software described in the test run management table 158 (FIG. 4) corresponding to the own device 122 and the setup related device (in this case, other than the same component device). The combination of hardware and software described in the trial operation management table 158 corresponding to the setup related device) is compared, and the number of operation tests that match the combination of hardware and software among the setup related devices exceeds the specified value. A setup-related device corresponding to the trial operation management table 158 is determined as a similar component device. Details will be described below.

  First, the identical / similarity determination unit 353 reads the similar configuration device determination policy 409 stored in the storage unit 123 of the own device 122 (step 1101).

  Next, the identity / similarity determination means 353 reads the test run management table corresponding to the own device 122 from the storage medium 114 (step 1102).

  Specifically, using the device identifier 200 of the own device 122 stored in the own device information table 305 as a search key, a record corresponding to the own device 122 from the scenario storage area 504 of the storage medium 114 (self scenario 127. FIG. (See (A).) And the value of the test run management table identifier 1705 described in the self-scenario 127 found by the search is acquired. Then, using the acquired value of the test operation management table identifier 1705 as a search key, the test operation management table 158 corresponding to the own device 122 is searched from the test operation management table storage area 507 of the storage medium 114, and the test operation management table 158 found by the search is searched. Read data.

  Then, the identity / similarity determination unit 353 reads one value of the setup-related device identifier 1602 from the setup-related device management table 330 (FIG. 10) held in the storage unit 123 of the own device 122 (step 1103).

  The identical / similarity determining unit 353 determines whether or not the identical component device flag 1603 in the record corresponding to the read value of the identifier 1602 is OFF (−1) in the setup related device management table 330 (step 1104). That is, it is determined whether the setup related devices to be processed are not the same device.

  If it is determined in step 1104 that the same component device flag 1603 is ON, that is, if the setup-related device to be processed is the same component device, the identity / similarity determination unit 353 proceeds to step 1103 and proceeds to the next step. Step 1103 and subsequent steps are executed for the setup-related apparatus that is the processing target.

  On the other hand, if it is determined in step 1104 that the identical component device flag 1603 is OFF, that is, if the setup-related device to be processed is not the same component device, the identity / similarity determination unit 353 A test run management table 158 (FIG. 4) corresponding to the apparatus is read from the storage medium 114 (step 1105).

  Specifically, using the setup related apparatus identifier 1602 read in step 1103 as a search key, the corresponding record is searched in the scenario 108 stored in the scenario storage area 504 of the storage medium 114, and the record found by the search is searched. The value of the described test operation management table identifier 1705 is acquired. Then, using the acquired value of the test operation management table identifier 1705 as a search key, the test operation management table 158 corresponding to the setup related device to be processed is searched from the test operation management table storage area 507 of the storage medium 114, and the test operation management found by the search is searched. The data of the table 158 is read.

  Next, the identity / similarity determination unit 353 performs the test operation corresponding to the setup-related device read in step 1105 and the combination of hardware and software described in the test operation management table corresponding to the own device 122 read in step 1102. The combination of hardware and software described in the management table is compared, and it is determined whether or not the number of operation tests that match the combination of hardware and software is equal to or greater than a specified value (step 1106).

  In the present embodiment, in the similar component device determination policy 409 read in step 1101, it is specified that the number of operation tests that match the combination of hardware and software is three or more as the determination criterion of the similar component device. Therefore, the determination is made according to this. In addition, a setup-related device corresponding to the trial operation management table 158 in which the number of operation tests with matching combinations is equal to or greater than the specified value is treated as a similar component device in the following processing.

  Specifically, the same / similarity determination unit 353 compares the test run management table corresponding to the own device 122 read in step 1102 with the test run management table corresponding to the setup related device read in step 1105, and determines the test item. When the number of operation tests that match the combination of hardware (unit, accessory, controller) and software is three or more, the determination result is Yes, and the setup-related device to be processed is a similar component device decide.

  If it is determined in step 1106 that the number of operation tests that match the combination of hardware and software is less than the specified value, that is, if it is determined that the setup-related device to be processed is not a similar component device, the same The similarity determination unit 353 proceeds to step 1103, and executes the processing after step 1103 for the setup-related apparatus to be the next processing target.

  On the other hand, if it is determined in step 1106 that the number of operation tests for which the combination of hardware and software matches is greater than or equal to the specified value, that is, if it is determined that the setup-related device to be processed is a similar component device, The identical / similarity determination means 353 turns on the similar component device flag of the setup related device management table 330 (step 1107).

  Specifically, in the record corresponding to the setup related device to be processed (the value of the setup related device identifier 1602 read in step 1103) in the setup related device management table 330 held in the storage unit 123 of the own device 122. Then, 1 is stored in the similar component device flag 1604.

  Next, the identity / similarity determination unit 353 reads setup result information and the like related to the processing target similar configuration device from the storage medium 114 (step 1108), and stores it in the setup related device management table 330 (step 1109).

  Specifically, in the test operation management table 158 stored in the test operation management table storage area 507 of the storage medium 114, the record data corresponding to the similar configuration device (the value of the identifier 1602 of the setup-related device to be processed). In step 1106, the value of the test item identifier 602 stored in the record relating to the operation test in which the combination of hardware and software matches is read and stored in the related test item identifier 1606 of the setup related device management table 330.

  Further, by using the value of the setup related device identifier 1602 regarding the similar configuration target device to be processed as a search key, the corresponding record is searched from the scenario execution information 105 stored in the scenario execution information storage area 505 of the storage medium 114, and the search is performed. The field of the test item identifier 1714 is searched from the found record using the value of the read test item identifier 602 as a search key, and the data of the individual result 1716 of the operation test corresponding to the test item identifier 1714 found by the search is read. And stored in the test result 1612 of the setup related device management table 330.

  Next, the same / similarity determination unit 353 determines whether or not the processing from step 1103 onward is completed for the devices corresponding to all the setup related device identifiers 1602 stored in the setup related device management table 330. (Step 1110).

  If it is determined in step 1109 that the processing has not been completed, the identity / similarity determination unit 353 proceeds to step 1103 and executes the processing in and after step 1103 for the setup related apparatus to be processed next. To do.

  On the other hand, if it is determined in step 1109 that the processing has been completed, the identity / similarity determination unit 353 proceeds to step 806 in FIG.

  FIG. 17 shows a procedure of processing executed by the relay client 109 when the storage medium 114 is connected to the relay client 109.

  First, the relay client 109 determines whether the scenario 108 related to the setup of the common software 156 exists in the storage medium 114 by referring to the value stored in the setup target device number storage area 509 of the storage medium 114. (Step 1201).

  In this embodiment, if the value stored in the setup target device number storage area 509 is 1 or more, it is determined that the scenario 108 exists, and the value stored in the setup target device number storage area 509 is 0. For example, it is determined that the scenario 108 does not exist.

  If it is determined in step 1201 that the scenario 108 exists, the relay client 109 refers to the value of the setup unexecuted device number storage area 510 of the storage medium 114 and is stored in the scenario storage area 504 of the storage medium 114. It is determined whether or not the execution of the scenario 108 has been completed (step 1202).

  In this embodiment, if the value of the storage area 114 setup unexecuted device number storage area 510 is 0, it is determined that the scenario 108 has been executed, and the setup unexecuted apparatus number storage area 510 is 1 or more. If there is, it is determined that the execution of the scenario 108 is not completed.

  If it is determined in step 1202 that the execution of the scenario 108 has not been completed, the relay client 109 determines whether to interrupt the scenario 108 (step 1203). In this embodiment, the determination is made by receiving an input from the user.

  If it is determined in step 1203 that the scenario 108 is to be interrupted, or if it is determined in step 1202 that the scenario has been completed, the registration request unit 152 of the relay client 109 stores the analysis room identifier storage area 501 in the storage medium 114. The analysis room identifier stored, the latest apparatus information 106 stored in the latest apparatus information storage area 502, and the scenario execution information 105 stored in the scenario execution information storage area 505 are transmitted to the service server 101, and the setup Registration of progress information and registration of the latest device information 106 are requested (step 1204).

  Next, the registration request unit 152 receives a response (message indicating that the progress information has been registered) from the service server 101 to confirm that the setup progress information has been registered (1205).

  Then, the registration request unit 152 initializes information in the storage medium 114 (step 1206).

  Specifically, the latest device information storage area 502, scenario storage area 504, scenario execution information storage area 505, software storage area 506, test run related table storage area 507, test run script storage area 508, setup target device in the storage medium 114 The values in the number storage area 509 and the setup unexecuted device number storage area 510 are cleared to zero.

  Next, the relay client 109 executes Step 1201 again.

  If it is determined in step 1201 that the scenario 108 does not exist in the storage medium 114, the transmission request unit 154 of the relay client 109 uses the analysis room identifier stored in the analysis room identifier storage area 501 of the storage medium 114. The service server 101 is requested to transmit the scenario 108 by attaching the read laboratory identifier to the service server 101 (step 1207).

  Next, the transmission request unit 154 receives data such as the scenario 108 from the service server 101 (step 1208).

  Specifically, the registered device information 107, scenario 108, software related information 124, and setup target device number 128 are received.

  Then, the transmission request unit 154 stores the data received from the service server 101 in the storage medium 114 (step 1209).

  Specifically, the registered device information 107 is stored in the registered device information storage area 503 of the storage medium 114, the scenario 108 is stored in the scenario storage area 504 of the storage field 114, and the common software in the software related information 124 is stored. Store in the software storage area 506, store the test run management table in the software related information 124 in the test run management table storage area 507, store the test run script in the software related information 124 in the test run script storage area 508, and set up The value of the number of devices 128 is stored in the setup target device number storage area 509 of the storage medium 114.

  The relay client 109 stores the data received from the service server 101 in the storage medium 114, and then ends the process.

  On the other hand, if it is determined in step 1203 that the scenario is to be interrupted, the relay client 109 prompts the continuation of the setup operation (for example, “Connect storage media to the analysis devices A and C”). Is displayed on the display screen (step 1210).

  This eliminates the need for the user to determine to which analyzer the common software 156 should be set up, and the setup work can be reliably performed for the analyzer that requires the common software 156 to be set up. .

  FIG. 18 shows a procedure of processing executed by the service server 101 in response to a request from the relay client 109.

  First, the service server 101 receives a request from the relay client 109, and switches processing according to the content of the request (step 1301).

  In step 1301, when the scenario 108 transmission request is received, the scenario creation means 153 of the service server 101 refers to the analysis room identifier attached to the scenario 108 transmission request (step 1302).

  Next, the scenario creating unit 153 selects the registered device information 107 related to a plurality of devices corresponding to the referenced laboratory identifier from the storage unit 102 (step 1303).

  Next, the scenario creating unit 153 selects common software corresponding to the selected registered device information 107 from the storage unit 102 (step 1304).

  Specifically, the scenario creation unit 153 includes a combination of hardware and software that can be included in the management target device, the common software 156, the test run management table 158, and the test run script 157, which are stored in the storage unit 102. Is selected from the scenario management table 159 associated with the common software corresponding to the combination of hardware and software included in the selected registered device information 107.

  Next, the scenario creation means 153 selects a trial run script corresponding to the common software selected in step 1304 from the storage means 102 (step 1305), and a trial run management table corresponding to the common software selected in step 1304 from the storage means 102. Is selected (1306).

  Specifically, the scenario creation unit 153 selects the test run script 157 and the test run management table 158 corresponding to the common software 156 selected in step 1304 from the scenario management table 159.

  Then, the scenario creating means 153 includes an apparatus identifier relating to a plurality of apparatuses corresponding to the laboratory identifier referenced in step 1302, an identifier of the common software 156 selected in step 1304, an identifier of the test run script 157 selected in step 1305, The scenario 108 (FIG. 3A)) is created using the identifier of the trial operation management table 158 selected in Step 1306 (Step 1307).

  When creating the scenario 108, the scenario creating means 153 creates the registration device information 107 selected in step 1303, the scenario 108 created in step 1307, the common software 156 selected in step 1304, the test run script selected in step 1305, 157 The software-related information 124 configured from the trial operation management table 158 selected in step 1306 and the number of setup target devices (for example, the number of registered device information selected in step 1303) are transmitted to the relay client 109 (step 1308). ), The process is terminated.

  On the other hand, when the progress information registration request is received in step 1301, the data storage unit 154 stores the setup progress information in the storage unit 102 (step 1309) and the latest device information received from the relay client 109. 106 is stored in the registration device information 107 of the storage means 102, a message indicating that the progress information has been registered is transmitted to the relay client 109 (step 1310), and the process is terminated. The latest device information 106 is stored in the storage unit 102 by being overwritten on the record corresponding to the corresponding device in the registered device information 107. Also, by managing the setup progress information with the service server 101, the administrator can grasp the progress of the setup work of the common software 156 for each analysis room.

  As described above, as shown in the above-described embodiment, the recording apparatus 114 is interposed between the management system 2 and the analysis apparatuses 118 to 122, so that the analysis apparatuses 118 to 122 are presented while receiving the operation plan and the setup success / failure information. The setup work of the latest common software 156 according to the configuration can be advanced.

  In addition, this invention is not limited to the structure demonstrated in the said Example, The following modifications can be employ | adopted.

  For example, in the embodiment, the management system 2 is configured by the relay client 109 installed in the analysis room and the service server 101 installed on the network. However, the management system 2 is configured as one apparatus having both configurations. Also good. In this case, a mode in which the management system 2 is installed in the analysis room, a mode in which the management system 2 is installed in a system management room in the operating company of the analysis room, or the like can be considered.

  Moreover, although the analyzer 122 of an Example is provided with several functional means 351-356 for convenience of explanation, the aspect comprised combining these means arbitrarily, and these means are comprised collectively. Embodiments are possible. Alternatively, the functions of the units 351 to 356 may be subdivided so that more functional units are provided.

  In the embodiment, a storage medium 114 that incorporates a flash memory and can read and write data by connecting to a USB terminal is employed, and a corresponding USB terminal is employed as the storage medium IF 302. However, when a readable / writable optical disk such as CD-RW or DVD-RW, a readable / writable magnetic disk such as a floppy disk, or a readable / writable magneto-optical disk such as MO is used as the storage medium 114, A device capable of reading and writing data from and to the storage medium 114 may be employed as the storage medium IF302.

  Furthermore, in the embodiment, in step 806 of FIG. 11, the setup result information regarding the same configuration device and the similar configuration device among the setup related devices is output as the setup success / failure information of the common software 156. From the registered device information 107 stored in the medium 114, another device for which the common software 156 is not set up is specified, and information indicating the same component device and a similar component device among the specified other devices is also combined. May be output. In this case, for example, “The software you are trying to set up is set up correctly on another device that is the same or similar. Therefore, it is likely that setup will be successful for device B that has the same configuration as this device A. It is preferable to present a message such as “.

The figure which shows the structure of the setup assistance system containing the analyzer of an Example, and the data flow in the system. The figure which shows an example of the table structure of the registration apparatus information regarding an analyzer. The figure which shows the table structure of (A) scenario 108, and the table structure of (B) scenario execution information 105. FIG. The figure which shows the structure of a trial run management table. The figure which shows the structure of a storage medium. The block diagram which shows the structure of a relay client. The block diagram which shows the structure of a service server. The figure which shows the structure of the analyzer of an Example. The figure which shows the table structure of (A) same structure apparatus determination policy, and the table structure of (B) similar structure apparatus determination policy. The figure which shows the structure of the setup related apparatus management table hold | maintained at the memory | storage means of an analyzer. The flowchart which shows the procedure of the process performed when a storage medium is connected to the analyzer. The flowchart which shows the procedure of the prior verification process by the same / similarity determination means. The flowchart which shows the procedure of a fluctuation condition verification process. The flowchart which shows the procedure of the specific process of a setup related apparatus. The flowchart which shows the process sequence of step 1805 of FIG. 12 is a flowchart showing the processing procedure of step 1806 in FIG. 6 is a flowchart illustrating a procedure of processing executed by a relay client when a storage medium is connected to the relay client. The flowchart which shows the procedure of the process which a service server performs according to the request | requirement from a relay client.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 ... Service server, 102, 123 ... Storage means, 104 ... Analysis room identifier, 105 ... Scenario execution information, 108 ... Scenario, 109 ... Relay client, 114 ... Storage medium, 118, 119, 120, 121, 122 ... Analysis device 156 ... Common software, 157 ... Test run script, 158 ... Test run management table, 302 ... Storage medium IF, 305 ... Self-device information table, 307 ... Installer software, 308 ... Test run software, 328 ... Pre-verification software, 330 ... Setup Related device management table, 408... Same component device determination policy, 409... Similar component device determination policy

Claims (8)

An own device information table for holding own device information related to the configuration of the own device;
Software that is set up in common for a plurality of devices (hereinafter referred to as “common software”), device information that has been set up for the configuration of devices that have been set up for common software, and common software for devices that have been set up An interface for reading storage medium data holding setup result information of
Among the common software, means for determining the common software to be set up in the own device,
Read the setup work completed device information corresponding to the determined common software from the storage medium via the interface, and read the setup work completed device information and the own device information held in the own device information table The same / similarity is determined according to a predetermined standard among the devices that have been set up, and the same configuration device having the same configuration as the configuration of the own device or a similar configuration device having a configuration similar to the configuration of the own device is determined. A determination means;
Success / failure information output means for reading setup result information regarding the determined identical configuration device or similar configuration device from the storage medium via the interface and outputting the determined common software setup success / failure information;
An information processing apparatus comprising: Equipped with the same reference table for designating hardware or software as a reference for determining the identity between the own device and another device,
The same / similarity determination means determines, as the same configuration device, a device that has already been set up with respect to the hardware or software specified in the same reference table among the devices that have been set up. The information processing apparatus according to claim 1, wherein: In the storage medium, for each of the plurality of devices, a combination of hardware and software that operates during the operation test is described for each operation test performed when common software is installed in the device. A test operation management table is provided.
The same / similarity judging means compares the combination described in the test operation management table corresponding to the own device with the combination described in the test operation management table corresponding to the setup operation completed device, and sets up the setup. 3. The apparatus which has been subjected to setup work in which the number of operation tests in which the combination of the hardware and software is equal to or greater than a predetermined value is determined as the similar component apparatus among the apparatuses which have already performed the work. The information processing apparatus described.   After the success / failure information output means outputs the setup success / failure information, the determined common software is installed in the own device, and the installation result information is set as the common software setup result information for the own device. The information processing apparatus according to any one of claims 1 to 3, further comprising an installation unit that writes to the storage medium in association with common software.   When the determined common software is installed in the own device, an operation test is performed, and the result of the operation test is stored in the storage medium in association with the determined common software as the common software setup result information for the own device. The information processing apparatus according to claim 4, further comprising a writing test unit. The storage medium holds a setup management table representing a correspondence relationship between common software and each of the plurality of devices,
The means for determining the software reads the setup management table from the storage medium via the interface, and among the common software, the common software corresponding to the own device in the read setup management table is stored in the own device. The information processing apparatus according to claim 1, wherein the information processing apparatus is determined as common software to be set up. A setup support system for setting up software provided from a management system in common to a first device and a second device using a storage medium,
The management system includes:
Means for storing software that is set up in common with the first device and the second device (hereinafter referred to as “common software”), and registered device information regarding the configuration of the first device;
Means for associating common software and the registered device information with each other and storing them in the storage medium;
The first device comprises means for storing common software setup result information for the device in the storage medium in association with the common software,
The second device includes:
An own device information table for holding own device information related to the configuration of the own device;
An interface for reading data of the storage medium holding the common software stored by the management system, the registered device information stored by the management system, and the setup result information stored by the first device;
Among the common software, means for determining the common software to be set up in the own device,
The registered device information corresponding to the determined common software is read from the storage medium via the interface, the read registered device information is compared with the own device information held in the own device information table, The same / similarity determining means for determining, in accordance with a predetermined standard, the same configuration device having the same configuration as the configuration of the own device or a similar configuration device having a configuration similar to the configuration of the own device,
Means for reading setup result information relating to the determined identical configuration device or similar configuration device from the storage medium via the interface, and outputting the determined common software setup success / failure information;
A setup support system comprising: Software that is set up in common for a plurality of devices (hereinafter referred to as “common software”), device information that has been set up for the configuration of devices that have been set up for common software, and common software for devices that have been set up Determining the common software to be set up in its own device from the storage medium holding the setup result information of
Reads out the setup work completed device information corresponding to the determined common software from the storage medium, and holds the read setup work completed device information and the own device information related to the configuration of the own device. The same configuration apparatus having the same configuration as the configuration of the own apparatus or a similar configuration apparatus having a configuration similar to the configuration of the own apparatus according to a predetermined standard. A step to determine;
Reading setup result information regarding the determined identical configuration device or similar configuration device from the storage medium, and outputting the determined common software setup success / failure information;
A setup support method comprising:

Images