Test schedule management method and management device, and test schedule management program

Abstract

Provided is a management method for a test schedule that includes a first step and a second step. The time slots for the first step include time slots for which work on the part of a worker is not required, and the time slots for the second step include time slots for which work on the part of a worker is required. When the second step is arranged in a portion of the first step in a test schedule, the second step is arranged in the test schedule such that time slots in the second step for which work on the part of a worker is required overlap only time slots in the first step for which work on the part of a worker is not required.

Description

Experiment schedule management method and management device, and experiment schedule management program

[0001] The present invention relates to the management of an experiment schedule.

[0002] Various techniques have been proposed for managing schedules using computers. For example, Japanese Patent Laid-Open Publication No. 06-282446 (Patent Document 1) and Japanese Patent Laid-Open Publication No. 08-055036 (Patent Document 2) disclose techniques for efficiently utilizing resources for computational processing in a computer. Japanese Patent Laid-Open Publication No. 2005-190318 (Patent Document 3) discloses a method for creating an experiment schedule in a computer system.

[0003] JP 06-282446 JP 08-055036 JP 2005-190318

[0004] In Patent Document 3, even when the number of operating devices is small compared to the number of specimens in a chemical experiment, a schedule is created to appropriately control the operating devices. However, factors to be considered in managing the experiment schedule are not limited to experimental equipment such as operating devices.

[0005] The present invention has been devised in view of the above circumstances, and its purpose is to provide a technique that enables more efficient management of experiments.

[0006] A method for managing an experimental schedule according to one aspect of the present disclosure is a computer-implemented method for managing an experimental schedule that includes a first step and a second step, wherein a time period for the first step includes a time period when no worker work is required, and a time period for the second step includes a time period when worker work is required, and the method includes a step of arranging the second step in a portion of the first step in the experimental schedule, wherein the arranging step arranges the second step in the experimental schedule such that the time period when worker work is required in the second step overlaps only with the time period when worker work is not required in the first step.

[0007] An experimental schedule management device according to one aspect of the present disclosure includes one or more processors and a storage device storing a program that, when executed by the one or more processors, causes the one or more processors to implement the above-mentioned experimental schedule management method.

[0008] A program for managing an experiment schedule according to an aspect of the present disclosure is executed by one or more processors, causing the one or more processors to perform the above-described experiment schedule management method.

[0009] According to one aspect of the present disclosure, the time periods when workers are required to work are taken into consideration in managing an experiment schedule, thereby enabling more efficient management of experiments.

[0010] 1. A block diagram showing the configuration of an automated experiment system 50 including an experiment schedule management device according to the present disclosure. 2. A block diagram showing the hardware configuration of the terminal device 400 of FIG. 1. 3. A diagram showing an example of an experiment schedule display screen. 4. A diagram showing another example of an experiment schedule display screen. 5. A diagram showing an example of a screen (schedule editing screen) displayed when editing of an experiment schedule begins. 6. A diagram showing an example of a screen (button creation screen) displayed in a process for creating an item button 9D corresponding to an experiment process. 7. A diagram for explaining the relationship between an experiment item 7 displayed in detailed display and information entered in the button creation screen. 8. A diagram for explaining a process for manually arranging processes in a schedule table 1. 9. A diagram showing an example of a screen (automatic setting screen) displayed on a display 431 by a terminal device 400 in response to an operation of the automatic setting button 16. 10. A diagram showing a modified example of the simplified display screen shown in FIG. 3. 11. A diagram showing a modified example of the detailed display screen shown in FIG. 4. 12. A diagram showing an example of a simplified display screen including an experiment schedule corrected from FIG. 10. 13. A diagram showing an example of a detailed display screen including an experiment schedule corrected from FIG. 11. 14. A diagram showing another example of a simplified display screen including an experiment schedule corrected from FIG. 10. 17 is a diagram showing another example of a detailed display screen including an experiment schedule modified from that of FIG. 11. FIG. 18 is a flowchart of a main routine. FIG. 19 is a flowchart of a subroutine of step S100 of FIG. 16. FIG. 20 is a flowchart of a subroutine of step S160 of FIG. 17. FIG. 21 is a flowchart of a subroutine of step S170 of FIG. 17. FIG. 22 is a flowchart of a subroutine of step S200 of FIG. 16.

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.

[0012] 1. Configuration of the Automated Experiment System Fig. 1 is a block diagram showing the configuration of an automated experiment system 50 including an experiment schedule management device according to the present disclosure. As shown in Fig. 1, the automated experiment system 50 includes an experiment facility 100 and a terminal device 400. The terminal device 400 is an example of an experiment schedule management device. In one implementation example, the terminal device 400 manages the schedule of experiments using the experiment facility 100.

[0013] The terminal device 400 includes an input / output unit 430. The input / output unit 430 includes a display 431, a keyboard 432, and a touchpad 433. The terminal device 400 is, for example, a laptop computer, a personal computer, a smartphone, or a tablet. The experimental equipment 100 and the terminal device 400 are connected to each other via a network NW. The network NW includes, for example, the Internet, a WAN (Wan Area Network), or a LAN (Local Area Network). Note that the terminal device 400 connected to the network NW may be realized by two or more information processing devices that work together. The terminal device 400 may manage the schedules of experiments using each of multiple experimental equipments.

[0014] A program for managing experimental protocols (hereinafter referred to as the "management program") is pre-installed in the terminal device 400. The keyboard 432 and touchpad 433 accept GUI (Graphical User Interface) operations for the management program by the user. By operating the GUI via the keyboard 432 and touchpad 433, the user of the terminal device 400 can design the sequence of multiple processes to be performed by one or more experimental devices included in the experimental equipment 100. The terminal device 400 can manage the experiment schedule and control the experimental equipment 100 according to the experimental protocol designed by the user.

[0015] The experimental equipment 100 includes a control device 110 and a plurality of experimental devices 120. The experimental equipment 100 may further include at least one image capture device that captures images for recognizing the status of the experimental equipment 100. The control device 110 controls the plurality of experimental devices 120 to automatically execute an experimental protocol from a terminal device 400. The plurality of experimental devices 120 include a robot 121, an incubator 122, a pre-treatment device 123, a microplate reader 124, a centrifuge 125, a liquid chromatograph mass spectrometer (LCMS) 126, a microscope 127, and a sterilization device 128.

[0016] The robot 121 moves a culture vessel Cn1 (e.g., a petri dish, flask, or well plate) containing a sample to the experimental equipment corresponding to each of the multiple processes according to the order of the processes defined in the experimental protocol. The culture vessel Cn1 contains, for example, agar containing cultured cells (analyte). The incubator 122 cultures the cells seeded in the culture vessel Cn1 while controlling the temperature. The pretreatment device 123 automatically distributes (dispenses) a fixed amount of sample to each of multiple microplates (wells). The microplate reader 124 measures the optical properties of the sample in the microplate (e.g., absorbance measurement and fluorescence intensity measurement). The centrifuge 125 separates the components of the analyte contained in the container Cn2 by centrifugal force. The LCMS 126 separates the analyte contained in the analytical container Cn3 (e.g., a vial or well plate) using liquid chromatography and performs mass spectrometry to separate the separated components of the analyte by mass-to-charge ratio (m / z). The microscope 127 magnifies minute analytes (e.g., cells) and allows the analytes to be observed with the naked eye. The sterilization device 128 includes a sterilization chamber that provides a dry, high-temperature environment and sterilizes instruments (e.g., culture vessels) contained in the sterilization chamber.

[0017] When the culture medium of the culture vessel Cn1 is replaced, a stock vessel or a pipette tip containing new culture medium is placed in a predetermined location in the pretreatment device 123. The robot 121 takes out the culture vessel Cn1 stored in the incubator 122. The robot 121 transports the culture vessel Cn1 to the pretreatment device 123 and places it in the specified location.

[0018] The pretreatment device 123 aspirates and removes the culture medium from the culture vessel Cn1, and then washes the culture vessel Cn1. The pretreatment device 123 dispenses new culture medium from a stock container into the culture vessel Cn1. After the pretreatment device 123 has completed dispensing, the robot 121 holds the culture vessel Cn1 and transports it to the incubator 122.

[0019] When the growth condition or state of the cells in the culture vessel Cn1 is to be observed, the culture vessel Cn1 stored in the incubator 122 is taken out by the robot 121. The robot 121 transports the culture vessel Cn1 to the microscope 127 and places the culture vessel Cn1 on the observation stage of the microscope 127. The microscope 127 adjusts the focal length so that the cells to be observed are in focus, and then photographs the cells. After photographing by the microscope 127 is complete, the robot 121 holds the culture vessel Cn1 and transports it to the incubator 122.

[0020] When performing a culture medium analysis of cells in culture vessel Cn1, an analysis vessel Cn3, a centrifugation vessel Cn2, a standard sample, an organic solvent for protein removal, and the like are placed in a predetermined location in the pretreatment device 123. The robot 121 retrieves the culture vessel Cn1 stored in the incubator 122, transports it to the pretreatment device 123, and places it in the designated location. After the organic solvent is dispensed into the vessel Cn2, the culture medium is dispensed from the culture vessel Cn1 into the vessel Cn2. After the culture medium and the organic solvent are sufficiently stirred, the robot 121 holds the vessel Cn2 and transports it to the centrifuge 125. The centrifuge 125 rotates at a designated speed for a designated time. As a result, the liquid contained in the vessel Cn2 is separated into an organic solvent layer and a culture medium layer. The robot 121 then holds the vessel Cn2 and places it in the designated location in the pretreatment device 123. The pretreatment device 123 dispenses the culture medium supernatant separated in the container Cn2 into an analytical container Cn3, and then dispenses the standard sample into the same location in the container Cn3 as the culture medium supernatant. The robot 121 transports the container Cn3 from the pretreatment device 123 to the LCMS 126 and stores it in the LCMS 126. The LCMS 126 begins automatic analysis of the substance contained in the container Cn3 according to pre-specified analytical conditions.

[0021] When a series of culture experiments is completed, the user cleans the instruments used in the experiment and sets them in the robot 121. The robot 121 transports the instruments to the sterilization device 128. The sterilization device 128 sterilizes the instruments in a manner in accordance with the experiment protocol. The robot 121 removes the sterilized instruments from the sterilization device 128 and returns them to a given position.

[0022] [2. Hardware Configuration of Terminal Device 400] Fig. 2 is a block diagram showing the hardware configuration of the terminal device 400 in Fig. 1. As shown in Fig. 2, the terminal device 400 includes a processor 421, a memory 422 and a hard disk 423 as storage units, a communication interface 424, and an input / output unit 430. These are connected to each other via a bus 440 so as to be able to communicate with each other.

[0023] The hard disk 423 is a non-volatile storage device. For example, an operating system (OS) program 40, a management program 41, and schedule data 42 are stored on the hard disk 423. The schedule data 42 is data used by the management program 41 and represents the experiment schedules of one or more users. In addition to the data shown in FIG. 2, the hard disk 423 also stores, for example, settings and outputs of various applications. The memory 422 is a volatile storage device and includes, for example, a dynamic random access memory (DRAM).

[0024] The processor 421 includes a CPU (Central Processing Unit). The processor 421 loads a program stored on a hard disk 423 into a memory 422 and executes the program. The processor 421 is connected to a network NW via a communication interface 424.

[0025] 3. Display of Experiment Schedule (Simplified Display) Fig. 3 is a diagram showing an example of a display screen for the experiment schedule. The terminal device 400 displays the experiment schedule on the display 431 in two modes: simplified display and detailed display. Screen 800 shown in Fig. 3 is an example of a simplified display screen. The detailed display screen will be described with reference to Fig. 4.

[0026] The screen 800 includes a schedule table 1 , a calendar 2 , a person list 3 , a display switching button 4 , and an edit button 5 .

[0027] Schedule 1 shows the experimental schedule for each day. Schedule 1 includes one or more experimental items 6. One experimental item 6 corresponds to one process.

[0028] In the example of Figure 3, Schedule 1 includes two experimental items ("Turbidity Measurement - Culture Medium Analysis" and "Culture Medium Preparation") for Friday, April 5. Schedule 1 also includes two experimental items ("Culture Medium Preparation" and "Reagent Preparation") for Monday, April 1, two experimental items ("Protein Quantification" and "Inoculation") for Tuesday, April 2, three experimental items ("Turbidity Measurement," "Cultivation," and "Plasmid Purification") for Wednesday, April 3, and three experimental items ("Genetic Recombination," "Inoculation," and "Sterilization") for Thursday, April 4.

[0029] By operating the calendar 2, the terminal device 400 identifies the period to be displayed in the schedule table 1. The person list 3 displays a list of one or more users whose schedules are managed by the management program. By selecting a user in the person list 3, the terminal device 400 identifies the user to be displayed in the schedule table 1. By operating the display switch button 4, the terminal device 400 switches the screen that is actively displayed on the display 431 between a simple display screen and a detailed display screen. By operating the edit button 5, the terminal device 400 starts processing for editing the experiment schedule. In this specification, "editing an experiment schedule" includes both creating a new experiment schedule and modifying an experiment schedule that has already been created.

[0030] (Detailed Display) Fig. 4 is a diagram showing another example of the display screen for the experiment schedule. A screen 810 shown in Fig. 4 is an example of a detailed display screen.

[0031] Screen 810 shown in Fig. 4 differs from screen 800 shown in Fig. 3 in the content displayed in schedule 1. More specifically, schedule 1 on screen 810 includes one or more experiment items 7. Each of the one or more experiment items 7 corresponds to one process. Each of the one or more experiment items 7 on screen 810 corresponds to one or more experiment items 6 on screen 800. Screen 810 differs from screen 800 in that the content displayed by each experiment item 7 differs from the content displayed by each experiment item 6.

[0032] More specifically, each experiment item 6 displays only the name of each process, whereas each experiment item 7 displays, in addition to the name of each process, the time periods during which work by workers is required for each process and the time periods during which such work is not required.

[0033] For example, schedule table 1 on screen 810 includes two experiment items 7 ("protein quantification" and "inoculation") for Tuesday, April 2nd. Of these, experiment item 7 for "protein quantification" includes one block representing the name of the process "protein quantification," as well as two blocks representing "work" and one block representing "standby." The block representing "work" represents a time period when work is required from a worker (e.g., a user of terminal device 400). The block representing "standby" represents a time period when work is not required from a worker. The block representing "standby" may represent a time period when experimental equipment is operating.

[0034] 4. Editing the Experiment Schedule Editing of the experiment schedule will be described with reference to Figures 5 to 9. Figure 5 shows an example of a screen (schedule editing screen) that is displayed when editing of the experiment schedule begins. For example, in response to operation of edit button 5, the terminal device 400 displays screen 820 of Figure 5 on the display 431.

[0035] The screen 820 includes a schedule table 1 and a calendar 2, similar to the screens 800 and 810. The screen 820 also includes an item list 9.

[0036] The item list 9 includes four types of buttons (an add button 9A, a delete button 9B, an edit button 9C, and seven item buttons 9D). Each of the seven item buttons 9D represents one experimental process. As will be described with reference to FIGS. 6 and 7 , the terminal device 400 receives input of information about the experimental process from the user and creates the item button 9D corresponding to that experimental process.

[0037] In response to an operation on the Add button 9A, the terminal device 400 starts creating an item button 9D corresponding to the experimental process. In response to an operation on the Delete button 9B while the item button 9D is designated, the terminal device 400 deletes the designated item button 9D from the item list 9. In response to an operation on the Edit button 9C while the item button 9D is designated, the terminal device 400 starts editing the information associated with the designated item button 9D by performing a process similar to the process described with reference to Figures 6 and 7.

[0038] 6 is a diagram showing an example of a screen (button creation screen) displayed in the process of creating an item button 9D corresponding to an experimental process. In response to, for example, operation of the Add button 9A on the screen 820 of FIG. 5, the terminal device 400 displays the screen 830 shown in FIG. 6 on the display 431.

[0039] The screen 830 includes a field 12 for receiving input of the name of the process, a table 13 for receiving input of the schedule of the process, a save button 14, and a cancel button 15.

[0040] The user inputs the name of the process in column 12 and the schedule for that process in table 13. Table 13 includes "time" and "content." "Time" indicates the time elapsed since the start of the process. "Content" indicates whether or not worker action is required in the process by using the value "work" or the value "standby." The value "work" indicates that worker action is required. The value "standby" indicates that no worker action is required.

[0041] In the example of Figure 6, Table 13 has the value "Work" for the time period from 0:00 to 1:00, which means that worker work is required for one hour from the start of the process.

[0042] Table 13 also has a value of "Waiting" for the time slot from time 1:00 to time 2:00, which means that no operator action is required between one hour and two hours after the start of the process.

[0043] Table 13 also has a value of "Work" for the time period from 2:00 to 2:30, which means that worker work is required between 2 hours and 2 hours and 30 minutes after the start of the process.

[0044] Table 13 has the value "Finish" for time 2:30, which means the process will finish in 2 hours and 30 minutes.

[0045] In one implementation example, terminal device 400 stores the contents entered in column 12 and table 13 in memory 422. When cancel button 15 is operated, terminal device 400 discards the contents stored in memory 422 and returns the screen displayed on display 431 to the schedule editing screen. On the other hand, when save button 14 is operated, terminal device 400 returns the screen displayed on display 431 to the schedule editing screen and displays item button 9D representing the name entered in column 12 in the item list 9 of the schedule editing screen. Furthermore, when save button 14 is operated, terminal device 400 adds information to schedule data 42 that associates item button 9D with column 12 and table 13.

[0046] 7 is a diagram for explaining the relationship between the experiment item 7 displayed in the detailed display and the information entered on the button creation screen. Fig. 7 shows the experiment item 7 displayed by entering the information shown in Fig. 6 on the button creation screen.

[0047] 7, the experiment item 7 includes a block 7A that displays the name of the process, as well as three blocks 7B, 7C, and 7D that display whether or not worker work is required in each of the three time periods that make up the process. Blocks 7B, 7C, and 7D each display the value ("Work" or "Wait") entered for each of the time periods 0:00 to 1:00, 1:00 to 2:00, and 2:00 to 2:30 in Table 13 of FIG.

[0048] FIG. 8 is a diagram illustrating a process for manually arranging a process in schedule 1. As indicated by arrow 7X in FIG. 8 , the user drags and drops an item button 9D toward a position on schedule 1 that corresponds to the intended time. In response, terminal device 400 displays an experiment item 7 corresponding to item button 9D at the dropped position. Terminal device 400 further stores in memory 422 information indicating that the process corresponding to the dragged-and-dropped item button 9D will be placed at the time corresponding to the dropped position on the experimental schedule (information representing the created experimental schedule). After displaying the experiment item 7 on schedule 1, terminal device 400 may erase the item button 9D corresponding to the experiment item 7 from the item list 9.

[0049] When an operation is performed to extend or shorten the area corresponding to the value "work" or the value "standby" for an experiment item 7 displayed on schedule 1, terminal device 400 may edit the information about the experiment item 7 and the process corresponding to experiment item 7 according to the content of the operation. That is, terminal device 400 may change the shape of experiment item 7 according to the content of the operation, and may also change the length of the period corresponding to the time zone corresponding to the value "work" or the value "standby" for the process.

[0050] In response to a drag-and-drop operation on one or more item buttons 9D in the item list 9, the terminal device 400 displays the corresponding experiment item 7 on the schedule table 1 for each item button 9D, and arranges the corresponding process in the experiment schedule, as described above.

[0051] 5 , the screen 820 further includes an automatic setting button 16. When the automatic setting button 16 is operated, the terminal device 400 automatically places, in the experiment schedule, the processes corresponding to one or more item buttons 9D on the item list 9 (without requiring the user to perform operations such as drag-and-drop).

[0052] FIG. 9 is a diagram showing an example of a screen (automatic setting screen) that the terminal device 400 displays on the display 431 in response to the automatic setting button 16 being operated.

[0053] 9 includes an item list 17, an area 18, and an execute button 24. Like the item list 9, the item list 17 includes four types of buttons including an item button.

[0054] Area 18 includes table 19, delete button 20, field 21, save button 22, and delete button 23. Table 19 displays the processes that are to be automatically arranged in the experimental schedule. More specifically, table 19 includes "item" and "number of times." More specifically, table 19 includes the name of the process that is to be automatically arranged as the value of "item." "Number of times" indicates the set value of the number of times each process is performed in the experimental schedule created by the automatic arrangement of processes.

[0055] In response to dropping an item button into area 18 by drag-and-drop, terminal device 400 adds the name of the process corresponding to the item button to table 19. Table 19 displays the names of items to be automatically arranged in the experiment schedule. In other words, accepting the operation of dropping an item button in item list 17 into area 18 constitutes an example of accepting the designation of a process to be automatically arranged.

[0056] Table 19 further includes a check box corresponding to each item. The check box is used to delete an item from Table 19. More specifically, when the user operates the delete button 20 with a check mark placed in the check box for an item (process) in Table 19, the terminal device 400 deletes the item from Table 19.

[0057] The terminal device 400 accepts input of conditions for arranging each item (step) in the table 19 in the experiment schedule in column 21. The input conditions specify, for example, the period (date) during which the step is to be arranged, the time period within a day, and the relationship with other steps (before step A, immediately before step A, after step A, immediately after step A, within 30 minutes after step A is performed, etc.). In one implementation example, the user specifies one item in table 19 and inputs the conditions for the specified step in column 21. When the save button 22 is input, the conditions input in column 21 are confirmed. When the delete button 23 is operated, the conditions input in column 21 are deleted.

[0058] When the execute button 24 is operated, the terminal device 400 creates an experiment schedule in which one or more items (steps) in the table 19 are arranged so that the conditions established for all items are satisfied. This determines the arrangement of each of the one or more items (steps) in the experiment schedule in the table 19. Information representing the created experiment schedule is stored in the memory 422.

[0059] Returning to FIG. 5 , the screen 820 further includes a save button 25 and a cancel button 26. When the save button 25 is operated, information representing the created experiment schedule stored in the memory 422 is stored as schedule data 42 on the hard disk 423. This confirms the information representing the manually or automatically created experiment schedule. The terminal device 400 can also edit the confirmed experiment schedule. More specifically, the terminal device 400 can manually or automatically correct a manually created experiment schedule in the manner described with reference to FIGS. 5 to 9 . The terminal device 400 can also manually or automatically correct an automatically created experiment schedule in the manner described with reference to FIGS. 5 to 9 .

[0060] 5. Modified Experiment Schedule Figure 10 shows a modified example of the simplified display screen shown in Figure 3. Figure 11 shows a modified example of the detailed display screen shown in Figure 4.

[0061] In the experimental schedules shown in Schedule Table 1 in each of Figures 3 and 4, the steps on each day were independent of the steps on other days. The experimental schedules shown in Schedule Table 1 in each of Figures 10 and 11 include steps that extend to other days. For example, in the experimental schedules shown in Figures 10 and 11, the step "Cultivation," which starts at 11:00 on Wednesday, April 3, continues until 11:00 on the following day, Thursday, April 4.

[0062] 6. Adjustment of Experiment Schedule After the experiment schedule has been finalized, the terminal device 400 can modify the experiment schedule in accordance with input from the user. Modification of the experiment schedule will be described in more detail with reference to FIGS. 12 and 13.

[0063] Fig. 12 is a diagram showing an example of a simplified display screen including the experiment schedule corrected from Fig. 10. Fig. 13 is a diagram showing an example of a detailed display screen including the experiment schedule corrected from Fig. 11.

[0064] 12 and 13 are screens displayed in response to user input of information indicating that the end time of the step "inoculation" on Wednesday, April 3rd is 30 minutes later than scheduled. In Schedule 1 shown in each of FIGS. 12 and 13, the end time of the step "inoculation" on Wednesday, April 3rd has been changed from 11:00 in FIGS. 10 and 11 to 11:30. In other words, the end time of the step "inoculation" has been delayed by 30 minutes. Accordingly, in Schedule 1 shown in each of FIGS. 12 and 13, the start and end times of the four steps following the step "inoculation" on Wednesday, April 3rd ("culture" from Wednesday, April 3rd to Thursday, April 4th, and "sterilization" and "data analysis" on Thursday, April 4th) have been delayed by 30 minutes from the start and end times shown in FIGS. 10 and 11. That is, in response to information input by the user indicating that the end time of the "inoculation" step on Wednesday, April 3rd has been delayed, the terminal device 400 modifies the experiment schedule to delay the above four steps by 30 minutes.

[0065] If a certain process is completed earlier than scheduled, the terminal device 400 can also modify the experiment schedule so as to expedite the placement of processes following that process.

[0066] When the end time of a certain process in the experimental schedule is changed, the terminal device 400 does not need to change the placement in the experimental schedule of processes that follow the changed process and are not expected to be affected by the process whose end time has been changed.

[0067] For example, in the above example, the process "Data Analysis" on Thursday, April 4th does not overlap in time with the process "Sterilization Work" after the location has been corrected in terms of the value "Work." Therefore, the terminal device 400 does not change the location of the process "Data Analysis" on Thursday, April 4th when correcting the experiment schedule.

[0068] The terminal device 400 may modify the experiment schedule according to input from the experimental device 120 .

[0069] More specifically, each of one or more steps constituting the experimental schedule may be associated with information identifying the experimental apparatus 120 used in that step. In one implementation example, the terminal device 400 acquires information identifying the experimental apparatus 120 used in each step by accepting input of information identifying the experimental apparatus 120 to be used along with the value "Wait" on a button creation screen such as that shown in FIG. 6 . The terminal device 400 may then output an instruction to the experimental apparatus 120 used in each step to start the step according to the experimental schedule, and may also acquire information indicating that the step has been completed from the experimental apparatus 120. If the timing at which the terminal device 400 acquires the information indicating that the step has been completed from the experimental apparatus 120 differs from the end time of the step in the experimental schedule, the terminal device 400 may modify the experimental schedule according to the difference between the timing at which the information was acquired and the end time in the experimental schedule.

[0070] Fig. 14 is a diagram showing another example of a simplified display screen including the experiment schedule corrected from Fig. 10. Fig. 15 is a diagram showing another example of a detailed display screen including the experiment schedule corrected from Fig. 11.

[0071] The screens in Figures 14 and 15 are displayed in response to information being input from the sterilization apparatus 128 associated with the process indicating that the end time of the process "Sterilization Work" on Thursday, April 4th is 30 minutes later than scheduled. In Schedule Table 1 shown in Figures 14 and 15, the end time of the process "Sterilization Work" on Thursday, April 4th has been changed from 3:00 PM in Figures 10 and 11 to 3:30 PM. In other words, the end time of the process "Sterilization Work" has been delayed by 30 minutes. In the detailed display in Figure 15, the end time of the period corresponding to the value "Waiting" for the process "Sterilization Work" has been changed from 2:30 PM to 3:00 PM.

[0072] Due to the above delay, in Schedule 1 shown in Figures 14 and 15, the start and end times of the process "Data Analysis" which follows the process "Sterilization Work" on Thursday, April 4th are delayed by 30 minutes from the start and end times shown in Figures 10 and 11. In other words, in response to the 30-minute delay in obtaining information from sterilization apparatus 128 indicating the end of the process "Sterilization Work" on Thursday, April 4th, terminal device 400 modifies the experimental schedule to delay the process "Data Analysis" by 30 minutes as described above.

[0073] 7. Processing Flow The processing flow executed for managing the experiment schedule will be described with reference to FIGS.

[0074] (Main Routine) Fig. 16 is a flowchart of the main routine. In one implementation example, the terminal device 400 implements the processing shown in Fig. 16 by causing the processor 421 to execute the management program 41, for example.

[0075] As shown in FIG. 16, in step S100, the terminal device 400 creates an experiment schedule as described with reference to FIGS. 5 to 9, and in step S200, adjusts the experiment schedule as described with reference to FIGS. 10 to 15.

[0076] (Editing Experiment Schedule) FIG. 17 is a flowchart of the subroutine of step S100 in FIG.

[0077] As shown in FIG. 17, in step S110, terminal device 400 waits until an input to input / output unit 430 is detected (NO in step S110), and when an input is detected (YES in step S110), the control proceeds to step S120.

[0078] In step S120, the terminal device 400 determines whether the input detected in step S110 is an input representing editing of the experiment schedule (an operation on the edit button 5), and if so (YES in step S120), proceeds to step S140; if not (NO in step S120), proceeds to step S130.

[0079] In step S130, the terminal device 400 executes processing according to the detected input and returns control to step S110. For example, if the detected input is an operation of the display switching button 4, the terminal device 400 switches the display on the display 431 between a simplified display and a detailed display. If the detected input is an operation of the edit button 5, the terminal device 400 switches the display on the display 431 from a display screen for the experimental schedule (e.g., FIG. 3 or FIG. 4) to a schedule editing screen (e.g., FIG. 5). If the operation is for confirming the arrangement of steps in the experimental schedule determined by manual or automatic arrangement, the terminal device 400 stores the arrangement of steps stored in the memory 422 as schedule data 42 on the hard disk 423.

[0080] In addition, if the input detected in step S110 is an input indicating the end of editing the experiment schedule (for example, an input indicating the operation of an end button not shown), the terminal device 400 may terminate the processing of Figure 17 and return control to Figure 16.

[0081] In step S140, the terminal device 400 creates the item button 9D in accordance with the input from the user.

[0082] In step S150, the terminal device 400 determines whether automatic placement has been specified. Automatic placement means creating an experiment schedule by automatically arranging items. In one implementation example, when the automatic setting button 16 is operated, the terminal device 400 determines that automatic placement has been specified. If the terminal device 400 determines that automatic placement has been specified (YES in step S150), the terminal device 400 proceeds to control step S170. On the other hand, if the terminal device 400 determines that automatic placement has not been specified (NO in step S150), the terminal device 400 proceeds to control step S160.

[0083] In step S160, the terminal device 400 performs manual arrangement, and returns control to step S110. Manual arrangement means creating an experiment schedule by arranging steps according to user operations, as described mainly with reference to FIG.

[0084] In step S170, the terminal device 400 performs automatic arrangement, and returns control to step S110. Automatic arrangement means creating an experiment schedule by automatically arranging steps, as described mainly with reference to FIG. 9.

[0085] (Manual Placement) FIG. 18 is a flowchart of the subroutine of step S160 in FIG.

[0086] 18, in step S161, the terminal device 400 receives an item arrangement request from the user. An example of the item arrangement request is the drag-and-drop of the item button 9D described with reference to FIG.

[0087] In step S162, the terminal device 400 determines whether the placement location of the item specified by the placement request is a location where the time period of the item overlaps with the time period of another item already placed on the experiment schedule. For convenience of explanation, an item already placed on the experiment schedule will be referred to as a "first item," and the item that is the subject of the placement request will be referred to as a "second item." If the terminal device 400 determines that the requested time period for the second item overlaps with the time period of the first item (YES in step S162), the control proceeds to step S163; otherwise (NO in step S162), the control proceeds to step S165.

[0088] In step S163, terminal device 400 determines whether the time period for which the second item has the value "Work" in the placement request overlaps only with the time period for which the first item has the value "Wait." If terminal device 400 determines that the time period for which the second item has the value "Work" in the placement request overlaps only with the time period for which the first item has the value "Wait" (YES in step S163), control proceeds to step S165; otherwise (NO in step S163), control proceeds to step S164.

[0089] If the second item does not include the value "work", that is, if the second item includes only the value "standby", the terminal device 400 advances the control from step S163 to step S165.

[0090] In step S164, the terminal device 400 issues an error notification. In one implementation example, the error notification is implemented by displaying an error message (e.g., "The placement is not accepted") and / or outputting an audio message. The terminal device 400 then proceeds to step S168.

[0091] In step S165, the terminal device 400 determines the placement of the item that is the target of the placement request in accordance with the placement request.

[0092] In step S166, terminal device 400 stores in memory 422 the arrangement of the items that are the subject of the arrangement request in accordance with the arrangement request.

[0093] In step S167, terminal device 400 displays the arrangement according to the arrangement request on display 431. For example, if the arrangement request is a drag-and-drop of item button 9D, in step S167, experiment item 7 corresponding to item button 9D is displayed at the position on schedule 1 where item button 9D was dropped.

[0094] In step S168, terminal device 400 determines whether an operation to end manual placement has been performed. One example of this operation is an operation on save button 25. If terminal device 400 determines that the operation has been performed (YES in step S167), it returns control to FIG. 17; otherwise (NO in step S167), it returns control to step S161.

[0095] According to the processing of FIG. 18 , when the second item includes the value "Work," if an arrangement request is made such that the value "Work" of the second item overlaps with the value "Work" of the first item, an error is reported. On the other hand, if an arrangement request is made such that the value "Work" of the second item does not overlap with the value "Work" of the first item, the second item is arranged in a position in the experiment schedule according to the arrangement request. An example of an arrangement request such that the value "Work" of the second item does not overlap with the value "Work" of the first item is a request that the time slot of the second item does not overlap with the time slot of the first item. Another example is a request such that the value "Work" of the second item only overlaps with the value "Wait" of the first item.

[0096] (Automatic Placement) FIG. 19 is a flowchart of the subroutine of step S170 in FIG.

[0097] 19, in step S171, the terminal device 400 accepts the designation of a process to be automatically placed. One example of such designation is the operation of dropping an item button in the item list 17 into the area 18, as described with reference to FIG.

[0098] In step S172, the terminal device 400 accepts input of setting conditions (for example, conditions input in the field 21 in FIG. 9) for each of the one or more processes targeted for automatic placement.

[0099] In step S173, the terminal device 400 determines the placement of each of the one or more processes that are to be automatically placed. In one implementation example, the control of step S173 is performed in response to the operation of the execute button 24. In another implementation example, the terminal device 400 sequentially determines the placement of each of the one or more processes. For example, if three processes are to be automatically placed, the terminal device 400 first places the first process in the experimental schedule, then adds the placement of the second process to the experimental schedule in which the first process has been placed, and then adds the placement of the third process to the experimental schedule in which the first and second processes have been placed.

[0100] The terminal device 400 arranges all processes in the experimental schedule so that the conditions set for all processes are satisfied. Furthermore, the terminal device 400 adds processes to the experimental schedule so that the time period of the newly added process with the value "Work" does not overlap with the time period of the process with the value "Work" already arranged in the experimental schedule. At this time, in order to satisfy the conditions set for both the process to be added and the processes already arranged in the experimental schedule, the terminal device 400 may change the arrangement of processes already arranged in the experimental schedule when adding a process.

[0101] In step S174, terminal device 400 stores in memory 422 the arrangement determined in step S173.

[0102] In step S175, the terminal device 400 displays the arrangement determined in step S173 on the display 431. In one implementation example, the terminal device 400 displays Schedule 1, which represents the experiment schedule according to the determined arrangement, on the display 431. Thereafter, the terminal device 400 returns control to FIG. 17 .

[0103] (Experiment Schedule Adjustment) FIG. 20 is a flowchart of the subroutine of step S200 in FIG.

[0104] 20, in step S210, the terminal device 400 repeats the control of step S210 until it receives input of information indicating a change in the end time of a process included in the experimental schedule (NO in step S210). When the terminal device 400 receives input of information indicating a change in the end time of a process included in the experimental schedule (YES in step S210), the control proceeds to step S220. Such input may be input by a user via the input / output unit 430, as described with reference to FIGS. 12 to 15, or may be input from the experimental device 120 via the communication interface 424.

[0105] In step S220, terminal device 400 changes the placement in the experiment schedule of the processes subsequent to the process whose end time has been changed, as described with reference to FIGS.

[0106] In step S230, the terminal device 400 displays the arrangement (experiment schedule) changed in step S220 on the display 431. Thereafter, the terminal device 400 returns control to step S210.

[0107] In the present embodiment described above, in an experimental schedule including a first step, a second step is arranged in the portion of the first step. This means that the second step may be arranged in the experimental schedule so that both the start time and the end time of the second step coincide with those of the first step, or may be arranged so that the second step overlaps with at least a portion of the first step.

[0108] Aspects It will be understood by those skilled in the art that the exemplary embodiments described above are examples of the following aspects.

[0109] (Item 1) A method for managing an experimental schedule according to one embodiment is a method for managing an experimental schedule implemented by a computer, the method including a first step and a second step, wherein a time period for the first step includes a time period when no worker work is required, and a time period for the second step includes a time period when worker work is required, and the method includes a step of arranging the second step in a portion of the experimental schedule for the first step, and in the arranging step, the second step may be arranged in the experimental schedule such that a time period when the second step requires worker work overlaps only with a time period when the first step does not require worker work.

[0110] According to the experiment schedule management method described in paragraph 1, the "time periods when workers are required to work," which was not previously taken into consideration, is taken into account in the management of the experiment schedule, thereby enabling more efficient experiment management.

[0111] (Clause 2) The method for managing an experimental schedule described in paragraph 1 may further include the steps of: accepting a request to add the second process to the experimental schedule; and, if the request indicates that at least a portion of the time period during which the second process requires an operator to work overlaps with a time period during which the first process requires an operator to work, notifying an error in the request.

[0112] According to the experimental schedule management method described in paragraph 2, when requesting the addition of a second process, the person making the request can easily recognize that at least a portion of the time period during which the second process requires workers to work overlaps with the time period during which the first process requires workers to work.

[0113] (Clause 3) The experiment schedule management method described in clause 2 may further comprise a step of displaying the time period of the first step.

[0114] According to the experimental schedule management method described in paragraph 3, the person who inputs the request to add the second process can input the request while recognizing the time period when the worker of the first process is not required to work, and thus, if an error is reported, the reason for the error can be easily understood.

[0115] (Clause 4) In the method for managing an experimental schedule described in paragraph 2 or 3, in the step of arranging the second process, the second process may be arranged in the experimental schedule in accordance with the request, provided that the time period during which the second process requires an operator to work does not overlap with the time period during which the first process requires an operator to work.

[0116] According to the experiment schedule management method described in Section 4, the second step is placed in the experiment schedule in response to a user request.

[0117] (Clause 5) The method for managing an experimental schedule described in any one of clauses 1 to 4 may further include a step of accepting input of conditions regarding the placement of at least one of the first step and the second step, and in the step of placing the second step, the second step may be placed according to the conditions.

[0118] According to the experimental schedule management method described in Section 5, the user can place the second process in the experimental schedule without making a specific placement request, as long as the user inputs placement conditions.

[0119] (Clause 6) The method for managing an experimental schedule described in any one of clauses 1 to 5 may further include a step of determining whether or not there has been a change in the time period of either the first step or the second step, and, if it is determined that there has been a change in the time period of either the first step or the second step, a step of changing the time period of the other of the first step or the second step in the experimental schedule in accordance with the change.

[0120] According to the experimental schedule management method described in Section 6, the experimental schedule prepared in advance can be adjusted according to the actual progress of each step.

[0121] (Clause 7) In the experiment schedule management method described in Clause 6, the determining step may be performed based on a signal obtained from a device that executes either the first step or the second step.

[0122] According to the experiment schedule management method described in Section 7, even if the user does not know the actual progress of each step, the experiment schedule can be adjusted according to the actual progress of each step.

[0123] (Item 8) In the experiment schedule management method described in Item 6, the determining step may be performed based on an input to an input device of the computer.

[0124] According to the experimental schedule management method described in Section 8, when a user recognizes the actual progress of each step, the user can input information according to the actual progress into the input device, and the experimental schedule can be adjusted according to the actual progress of each step.

[0125] (Clause 9) The method for managing an experiment schedule described in any one of clauses 1 to 8 may further include a step of switching the display between a simple display in which the time period of the first process is displayed only with the name of the first process, and a detailed display in which the time period of the first process is displayed so as to include the name of the first process and information indicating whether or not work by an operator is required.

[0126] According to the experiment schedule management method described in Section 9, a display of the content desired by the user can be provided.

[0127] (Clause 10) An experimental schedule management device according to one embodiment may include one or more processors and a storage device storing a program that, when executed by the one or more processors, causes the one or more processors to implement the experimental schedule management method described in any one of clauses 1 to 9.

[0128] According to the experiment schedule management device described in paragraph 10, the "time periods when workers are required to work," which was not previously taken into consideration, is taken into account in the management of the experiment schedule, thereby enabling more efficient management of experiments.

[0129] (Clause 11) The program for managing an experimental schedule according to one embodiment may be executed by one or more processors to cause the one or more processors to implement the experimental schedule management method described in any one of clauses 1 to 9.

[0130] According to the experiment schedule management program described in paragraph 11, the "time periods when workers are required to work," which was not previously taken into consideration, is taken into account in the management of the experiment schedule, thereby enabling more efficient experiment management.

[0131] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is defined by the claims, not by the description of the above-described embodiments, and is intended to include all modifications within the meaning and scope of the claims. Furthermore, it is intended that each technique in the embodiments can be implemented alone or, if necessary, in combination with other techniques in the embodiments to the extent possible.

[0132] 1 Schedule, 2 Calendar, 3 Person list, 4 Display switch button, 5, 9C Edit button, 6, 7 Experimental item, 7A, 7B, 7C, 7D Block, 7X Arrow, 9, 17 Item list, 9A Add button, 9B, 20, 23 Delete button, 9D Item button, 13, 19 Table, 18 Area, 50 Automatic experiment system, 100 Experimental equipment, 110 Control device, 120 Experimental equipment, 121 Robot, 400 Terminal device, 421 Processor, 422 Memory, 423 Hard disk, 424 Communication interface, 430 Input / output unit, 431 Display, 432 Keyboard, 433 Touchpad, 440 Bus, 800, 810, 820, 830, 850 Screen.

Claims

1. A method for managing an experiment schedule, which is implemented by a computer, comprising the steps of: A step of setting a time period for a first process, which is a time period during which no work by an operator is required, in a first experiment item; setting a time period for a second process, which is a time period during which an operator is required to perform an operation, of the first experiment item; setting a time period for a third process, which is a time period that requires an operator to work, among the second experiment items; placing the first experiment item; and in response to an operation of an automatic setting button, arranging the second experiment item so that the third step overlaps with the first step in the experiment schedule, A method for managing an experimental schedule, wherein in the step of arranging the second experimental item, the second experimental item is arranged in the experimental schedule such that a time period of the third process overlaps only with a time period of the first process in the first experimental item.

2. receiving a request to add the third process to the experimental schedule; 2. The method of claim 1, further comprising the step of notifying an error in said request when at least a part of said third step overlaps with a time period of said second step.

3. 3. The method for managing an experiment schedule according to claim 2, further comprising the step of displaying a time period for said first step.

4. 3. The method for managing an experimental schedule according to claim 2, wherein in the step of arranging the second experimental item, the second process is arranged in the experimental schedule in accordance with the request, on the condition that the time period of the third process does not overlap with the time period of the second process.

5. The method further includes a step of receiving an input of a condition regarding the arrangement of at least one of the first experiment item and the second experiment item; 2. The method of claim 1, wherein in the step of arranging the second experiment item, the second experiment item is arranged according to the condition.

6. determining whether or not a time period of either the first experiment item or the second experiment item has been changed; 2. The experiment schedule management method of claim 1, further comprising a step of: when it is determined that a change has been made to a time period of either the first experiment item or the second experiment item, changing a time period in the experiment schedule of the other of the first experiment item and the second experiment item in accordance with the change.

7. 7. The experiment schedule management method according to claim 6, wherein said determining step is performed based on a signal obtained from a device that executes either said first experiment item or said second experiment item.

8. 7. The method of claim 6, wherein said determining step is performed based on an input to an input device of said computer.

9. 2. The experiment schedule management method according to claim 1, further comprising a step of switching between a simplified display in which the time period of the first process is displayed only by the name of the first process and a detailed display in which the time period of the first process is displayed including the name of the first process and information indicating whether or not an action by an operator is required.

10. one or more processors; An experiment schedule management device comprising: a storage device storing a program which, when executed by the one or more processors, causes the one or more processors to implement the experiment schedule management method described in any one of claims 1 to 3.

11. 2. A program for managing an experiment schedule, which, when executed by one or more processors, causes the one or more processors to carry out the experiment schedule management method according to claim 1.