Automated laboratory equipment

Abstract

This invention provides automated laboratory equipment for analyzing biological samples, a computer implementation method, and a computer-readable storage medium. [Solution] The automated laboratory equipment 1 includes a controller 10 for adjusting the automated laboratory equipment, which causes the automated laboratory equipment to perform one or more processing runs. Each processing run includes one or more protocols to be performed for each biological sample. The automated laboratory equipment also triggers maintenance routines to be performed on the automated laboratory equipment and monitors the number of processing runs completed by the laboratory equipment, triggering maintenance when the number of processing runs exceeds a predetermined run threshold.

Description

Technical Field

[0001] The present disclosure relates to automated laboratory equipment, computer-implemented methods, and computer-readable storage media.

Background Art

[0002] In analytical laboratories, particularly in vitro diagnostic laboratories, one or more automated laboratory instruments may perform pre-analysis protocols, analysis protocols, and post-analysis protocols on biological samples.

[0003] To ensure that the automated analytical instrument is operating correctly and to extend the life of the instrument, it is important to perform preventive maintenance on the automated analytical instrument. Maintenance routines typically include multiple activities, such as checking, cleaning, and replacing various components (e.g., fan filters and filter fluids) or resources within the instrument.

[0004] These activities are typically performed manually, but automated maintenance activities may also be performed after some setup has been performed by the user or after a confirmation signal has been provided by the user. Each activity may have a different time deadline and may be very time-consuming for the user to perform, leading to delays or neglect of maintenance.

[0005] Traditionally, maintenance routines have been scheduled using time-based offline methods, where users track and perform maintenance activities after a predetermined time period of scheduled appointments. However, such methods can lead to excessive downtime of equipment by scheduling maintenance too frequently, or to excessive wear and tear and failure of equipment if maintenance is not performed frequently enough due to excessive use. In addition, conventional methods for scheduling maintenance require users to manually log which activities have been performed. Therefore, an improved method for scheduling preventive maintenance of laboratory equipment is desired.

[0006] This invention was made in view of the above considerations. [Overview of the project]

[0007] In general, this disclosure provides automated laboratory equipment configured to schedule preventive maintenance activities according to the usage of the automated laboratory equipment. Furthermore, in some examples, preventive maintenance activities may be scheduled according to the usage of each asset of the automated laboratory equipment so that the maintenance activities of each asset are coordinated with one another.

[0008] Accordingly, in the first embodiment, an automated laboratory instrument for analyzing biological samples is provided. The automated laboratory instrument comprises a controller for regulating the automated laboratory instrument, which is configured to cause the automated laboratory instrument to perform one or more processing runs, each processing run comprising one or more protocols to be performed for each biological sample, and to trigger a maintenance routine to be performed on the automated laboratory instrument. Furthermore, the controller is configured to monitor the number of processing runs completed by the laboratory instrument and to trigger maintenance when the number of processing runs exceeds a predetermined run threshold.

[0009] Advantageously, preventative maintenance of automated laboratory equipment can be timed to be neither too frequent nor too insufficient, but when needed, thereby reducing downtime of the automated laboratory equipment while decreasing the likelihood of equipment failure or disruption.

[0010] Automated laboratory equipment (e.g., analytical systems) can be automated molecular workspaces for performing in vitro diagnostic (IVD) tests on biological samples, such as polymerase chain reaction (PCR)-based nucleic acid (NAT) tests. Automated laboratory equipment can provide easy access to a stock of consumables and reagents for performing tests and may be equipped with onboard storage and cooling systems to maintain stock.

[0011] The controller may be a processor or system manager configured to receive test orders, determine a workflow to fulfill each test order, and configure automated laboratory equipment to execute the workflow. For example, the controller may receive status information about the test hardware, consumables, and reagents of automated laboratory equipment to determine an efficient workflow from sample preparation to result interpretation.

[0012] Each processing run may include one or more, preferably more, test orders, which are completed by automated laboratory equipment or by modules of laboratory equipment.

[0013] The execution of processing runs may be postponed to allow for periodic preventative maintenance to be performed on automated laboratory equipment. Maintenance routines scheduled and triggered by the controller may include multiple maintenance activities performed on the automated laboratory equipment. Each maintenance routine may be referred to as a maintenance package that includes multiple maintenance activities. By triggering multiple maintenance activities at once in this manner, the overall downtime of the equipment may be reduced, and therefore the overall throughput of the equipment may be improved.

[0014] Maintenance activities may include one or more of the following: checking, cleaning, replacing, processing, or lubricating one or more assets of the laboratory equipment. Assets may include the test hardware of the automated laboratory equipment and / or consumables such as reagents, filtrates, or needles. Maintenance routines may be accepted and / or performed by the user of the automated laboratory equipment.

[0015] Triggering a maintenance routine may include generating a notification that the maintenance deadline has arrived. For example, the notification may be a user notification displayed on a user interface or automated laboratory equipment, or the notification may be sent to a remote computer system for processing. Thus, a given run threshold may be called a deadline threshold that indicates that the deadline for performing maintenance has arrived.

[0016] The number of processing runs may be the total number of processing runs completed by the automated laboratory equipment (all modules). Therefore, the triggered maintenance routine may be, for example, an equipment maintenance routine that includes the maintenance activity of the automated laboratory equipment as a whole. In this example, a given run threshold may be referred to as the equipment run threshold.

[0017] Alternatively, the number of processing runs may be the number of processing runs completed by the module of the automated laboratory equipment, and the triggered maintenance routine may be a module maintenance routine performed on the module. In this example, a given run threshold may be called the module run threshold.

[0018] The controller may include an instrument run counter for monitoring the total number of processing runs completed by the laboratory equipment. Therefore, a predetermined threshold number of processing runs may be called a counter threshold or instrument counter threshold.

[0019] As described later, the controller may have one or more counters, each configured to monitor the number of runs completed by each asset of the laboratory equipment. Assets may include modules or units of automated laboratory equipment, or entire pieces of laboratory equipment. Each counter may be associated with a common or individual predetermined run threshold, which, when exceeded by one of the counters, triggers a maintenance routine to be performed on the asset associated with that counter.

[0020] A predetermined number of processing runs may be a first threshold (e.g., an expiration threshold) indicating when the deadline for each maintenance routine arrives. Additionally, the controller may be configured to determine when the number of processing runs exceeds a second predetermined number of processing runs (e.g., an overdue threshold) that is higher than the first threshold. The second threshold may indicate when each maintenance threshold has been exceeded. Thus, the automated laboratory equipment may operate in a default state, an expiration state, or an overdue state, depending on whether a threshold has been exceeded.

[0021] An automated laboratory instrument may comprise multiple modules (or submodules or units) for performing one or more processing runs. For example, each module may include one or more pipette heads of the laboratory instrument.

[0022] As described above, the controller may be further configured to monitor the number of processing runs completed by one or more (or each module) of the automated laboratory equipment. When the number of processing runs for each module exceeds a predetermined module run threshold, the controller may be configured to trigger a module maintenance routine to be executed for that module. For example, the controller may be configured to send a notification to the user interface or a remote system indicating that the maintenance deadline for that module has arrived.

[0023] Triggering equipment maintenance routines and / or optionally each module maintenance routine may include generating a signal indicating that maintenance is due. For example, triggering a maintenance routine may include one or more of the following: generating a user notification indicating that maintenance is due, starting an automated maintenance routine, and / or sending a notification to a remote service.

[0024] The controller can be configured to reset the monitored processing run count when it detects that an equipment maintenance protocol (or the respective module maintenance routine) has been performed. For example, the controller may be configured to reset one or more run counters (e.g., an equipment run counter and / or the respective module run counters).

[0025] As described above, the predetermined run threshold or each predetermined run threshold may be a first predetermined run threshold. The controller may then be further configured to determine when the total number of processing runs or the number of each run exceeds a second predetermined run threshold (e.g., an overdue threshold) that is higher than the first predetermined run threshold. If the monitored number of runs is determined to have exceeded the second predetermined threshold, the controller may be configured to prevent or reduce the operation of the automated laboratory equipment until the triggered maintenance routine is performed. For example, if the total number of runs exceeds the equipment run overdue threshold, the controller may be configured to lock the automated laboratory equipment to prevent further use until the equipment maintenance routine is performed. In contrast, if the number of each run completed by a module exceeds the respective overdue threshold run count, the controller may be configured to reduce and allow the use of the automated laboratory equipment.

[0026] After determining that the first predetermined run threshold has been exceeded, the controller may be configured to receive a user request for an extension and obtain an extension key from a remote service. Thereafter, the controller may use the extension key to extend (e.g., increase) the second predetermined run threshold. Thus, the user may be permitted to have more time and / or more runs performed before it is determined that the maintenance routine has expired and optionally before the automated laboratory equipment is locked.

[0027] The above-mentioned predetermined run threshold or each predetermined run threshold may be a fixed value obtainable from a configuration file of the automated laboratory equipment. The configuration file may be editable offline. That is, the configuration file may be downloaded to another location, edited, and then re-uploaded to be read by the controller. In this way, the change of the threshold may be implemented using a convenient and efficient software update with little impact. The configuration file may include fixed values of expiration thresholds and / or expiration exceeded thresholds of equipment maintenance routines and / or module maintenance routines.

[0028] The predetermined run threshold may be determined based on historical performance information. The historical performance information may be recorded when the automated laboratory equipment is subject to low throughput and / or average throughput and / or high throughput. The above-mentioned predetermined run threshold or each (first) predetermined run threshold may be selected from a range defined by the number of historical runs completed between maintenance routines when the automated laboratory equipment is subject to low throughput, and the number of historical runs completed between maintenance routines when the automated laboratory equipment is subject to average throughput. The number of historical runs completed between maintenance routines may refer to the number of runs that can be completed before the state of the automated laboratory equipment indicates that a maintenance routine should be performed.

[0029] Each predetermined module threshold value may be configured to be exceeded when a predetermined device threshold value is exceeded. Accordingly, the trigger for each module maintenance routine may be configured to match the trigger for the device maintenance routine or a certain trigger. In this way, the downtime of the automated laboratory equipment can be reduced by ensuring that module maintenance can be performed simultaneously with equipment-level maintenance. The controller may be configured to balance the workload of each module when assigning runs to each module. Accordingly, the controller may be configured to trigger the device run routine each time x runs are completed by the device at this time, and to trigger the module maintenance routine each time x / n runs are completed by the module, where n is the number of modules into which the workload is divided.

[0030] The triggered device maintenance routine may be one of a plurality of device maintenance routines or maintenance packages selectable by the controller. Each of the plurality of device maintenance routines may correspond to a respective level of maintenance to be performed. For example, a higher-level maintenance routine may include a greater number of maintenance activities and / or may require more time and / or resources for implementation than a lower-level maintenance routine. For example, the plurality of maintenance routines may be referred to as a selection of menus or packages and may optionally include small, medium, and large packages of maintenance activities.

[0031] For example, the plurality of maintenance routines may include at least a lower-level maintenance routine including checking the device assets and a higher-level maintenance routine including replacing the device assets.

[0032] The controller may be configured to select equipment maintenance routines to trigger based on a schedule (e.g., a sequence) of equipment maintenance routines.

[0033] The equipment maintenance routine schedule may be configured to ensure that a higher-level maintenance routine is performed only after one or more lower-level maintenance routines have been performed. For example, the equipment maintenance routine schedule may alternate between different levels of maintenance routines, or schedule lower-level maintenance routines more frequently than higher-level maintenance routines.

[0034] In a further aspect, the Disclosure provides a computer implementation method for triggering maintenance of an automated laboratory instrument, the automated laboratory instrument being configured to perform one or more processing runs, each processing run comprising one or more protocols to be performed for each of a biological sample, the method comprising monitoring the total number of processing runs completed by the laboratory instrument and triggering the automated laboratory instrument to perform an instrument maintenance routine when the total number of processing runs exceeds a predetermined run threshold.

[0035] The computer implementation method may be carried out by a controller of automated laboratory equipment. Accordingly, the computer implementation method may include any of the optional features described herein with respect to the first embodiment.

[0036] Further aspects of this disclosure provide a computer-readable medium that, when executed by a computer, causes the computer to perform one of the computer implementation methods described herein.

[0037] Additional aspects of this disclosure may relate to a system configured to perform any of the computer implementations discussed herein. Specifically, the system may include a processor configured to perform any of the computer implementations of this disclosure.

[0038] Additional aspects of the present disclosure may provide a computer program that, when executed by a computer, includes instructions causing the computer to perform steps of any computer implementation method disclosed herein. Further aspects of the present invention may provide a computer-readable storage medium storing a computer program of the aforementioned aspects of the present disclosure.

[0039] This disclosure includes combinations of the described embodiments and preferred features, unless such combinations are clearly unacceptable or expressly avoided. [Brief explanation of the drawing]

[0040] Next, embodiments and experiments illustrating the principle of the present invention will be described with reference to the attached figures.

[0041] [Figure 1] Diagram of automated laboratory equipment. [Figure 2] A diagram of a controller for automated laboratory equipment. [Figure 3] A flowchart illustrating the process implemented by the controller to schedule preventative maintenance. [Figure 4] A more detailed flowchart of the process implemented by the controller. [Figure 5] A diagram illustrating an example schedule of a planned maintenance activity package. [Figure 6] A diagram showing an example of maintenance intervals. [Figure 7] A diagram illustrating an example of maintenance activities. [Figure 8] A diagram illustrating an example of the execution sequence for a preventative maintenance package. [Figure 9]A diagram illustrating exemplary maintenance intervals for performing equipment and module maintenance routines. [Figure 10] A diagram showing a comparison between the equipment maintenance schedule and the module maintenance schedule. [Figure 11] A diagram illustrating an example maintenance schedule. [Figure 12] A diagram showing the extended deadline threshold. [Modes for carrying out the invention]

[0042] Hereinafter, aspects and embodiments of the present invention will be described with reference to the attached figures. Further aspects and embodiments will be apparent to those skilled in the art. All documents referenced in this text are incorporated herein by reference.

[0043] Figure 1 shows an automated laboratory apparatus 1 for performing pre-analysis, analysis, and post-analysis procedures on biological samples.

[0044] The automated laboratory instrument 1 includes a controller 10 for coordinating the automated laboratory instrument 1 to perform one or more processing runs. Each processing run includes one or more protocols to be performed on multiple biological samples. The controller 10 is configured to receive a series of test orders specifying the tests to be performed on each biological sample, and then to determine a workflow for processing those test orders.

[0045] Additionally, the automated laboratory equipment 1 comprises several modules 14a to n for performing processing runs. For example, each module may include one or more p-head units (also known as processing heads or pipettes) for processing biological samples. As part of the workflow, the controller 10 is configured to assign processing runs to one or more of the p-head units. Preferably, the controller 10 is configured to balance the workload of each module 14n by distributing the processing runs evenly among the modules 14n. In this way, the preventative maintenance required for each module 14n is required at the same frequency as they are subjected to similar usage.

[0046] Finally, the automated laboratory interface includes a user interface (UI) 12 for communicating with the user and receiving commands from the user. For example, the UI may be configured to display a notification indicating when the maintenance deadline for one of the automated laboratory equipment 1 and / or module 14n is approaching.

[0047] In addition to adjusting laboratory equipment 1 to perform processing runs, controller 10 is configured to monitor the total number of processing runs completed by laboratory equipment 1 using a run counter and to trigger an equipment maintenance routine to be performed on automated laboratory equipment 1 when the total number of processing runs exceeds a predetermined run threshold. For example, controller 1 may trigger the maintenance routine to be performed by sending a notification to UI 12 to inform the user that it is time for preventative maintenance to be performed on equipment 1.

[0048] Additionally, the controller may be configured to monitor the number of processing runs completed by each module 14n and trigger a module maintenance routine to be performed on that module 14n when the number of processing runs exceeds a predetermined module run threshold. As described in detail below, the controller 10 is preferably configured to set each of the thresholds so that an equipment maintenance routine and one or more module maintenance routines are performed simultaneously.

[0049] Figure 2 shows a diagram of the controller 10 of the automated laboratory equipment 1. The controller 10 includes various functional modules for adjusting and controlling the automated laboratory equipment 1.

[0050] In this context, the term “module” is used to refer to a functional module configured or adapted to perform a particular function. A module (e.g., a counter) may be implemented in hardware (i.e., they may be separate physical components within a computer), software (i.e., they may represent separate sections of code that, when executed by a processor, cause a processor to perform a particular function), or a combination of both.

[0051] The controller 10 includes a workflow manager 20 for determining the processing runs of each module 14n of the automated laboratory equipment 1 according to the test orders received in the equipment 10, and a maintenance coordinator module 22 for scheduling preventive maintenance to be performed on the equipment 1.

[0052] The maintenance coordinator 22 includes multiple run counters 220 for monitoring the number of processing runs completed by each asset of the automated laboratory equipment 1 since the last maintenance routine was performed for that asset. In particular, the run counters 220 include an equipment run counter 2200 for monitoring the total number of processing runs completed by the equipment 1, and multiple module run counters 2202n, each module run counter 2202n monitoring the number of processing runs completed by each module 14n of the automated laboratory equipment 1.

[0053] The controller 10 has read access to a configuration file 24, which is stored, for example, in the non-volatile memory of the automated laboratory equipment or stored remotely. The configuration file 24 includes an equipment maintenance threshold 242 for scheduling maintenance of the automated laboratory equipment 1 and a module maintenance threshold 244 for scheduling maintenance of module 14a of the automated laboratory equipment 1.

[0054] The maintenance thresholds for device 242 and module 244 each include a first due date threshold 2420 and 2440, which are the number of processing runs indicating when the maintenance deadline will arrive. Additionally, the maintenance thresholds for device 242 and module 244 each include a second overdue threshold 2422 and 2442, which are higher than the first due date thresholds 2420 and 2440, respectively. The overdue threshold indicates the number of processing runs when the maintenance deadline is exceeded.

[0055] The controller 10 is configured to obtain thresholds from the configuration file 24 and compare each run counter 2200 with its respective expiration threshold and expiration threshold. When the instrument run counter 220 exceeds the instrument expiration threshold 2420, the controller 10 is configured to trigger a maintenance routine. If the instrument expiration threshold 2422 is exceeded, the controller 10 is configured to lock the automated laboratory instrument 1 to prevent its use until the necessary maintenance routine is performed.

[0056] If the module run counter 2202n exceeds the module expiration threshold 2440, the controller 10 is configured to trigger a maintenance routine. If the module expiration threshold 2442 is exceeded, the controller 10 is configured to reduce the available operation of the automated laboratory equipment 1 and restrict its use until the necessary maintenance routine is performed.

[0057] Figure 3 shows a flowchart illustrating the method implemented by the controller 10 to schedule preventive maintenance for automated laboratory equipment 1.

[0058] First, in step S100, the controller 1 starts a run counter to monitor the number of processing runs completed by the device 1.

[0059] In step S102, the controller 1 determines whether the number of completed runs exceeds a predetermined deadline threshold (for example, obtained from the configuration file 24 as described above).

[0060] If the number of runs exceeds a predetermined time threshold, the controller proceeds to step S104 to trigger a maintenance routine, for example, by generating a notification or by sending a signal to a remote service. Once the maintenance routine is performed, the controller 10 is configured to reset the run counter and return to step S100.

[0061] Figure 4 shows a more detailed flowchart of the method implemented by controller 10.

[0062] In step S200, the controller 10 starts the instrument run counter 2200, which monitors the total number of processing runs completed by the automated laboratory instrument 1.

[0063] In step S202, the controller determines whether the run counter 2200 has exceeded a first predetermined (deadline) threshold. If it has exceeded the first predetermined threshold, the controller 10 proceeds to step S204, where the equipment maintenance routine is triggered by generating a notification that the equipment maintenance routine has expired.

[0064] In step S206, the controller 10 determines whether the necessary maintenance routine has been performed. If so, the controller 10 proceeds to step S208, where the run counter 2200 is reset, and then returns to step S200. If the necessary maintenance routine has not been performed, the controller 10 proceeds to step S208.

[0065] In step S208, the controller 10 determines whether the run counter 2200 has exceeded a second predetermined threshold number of runs (overdue). If the second predetermined threshold has not been exceeded, the controller 10 repeats steps S206 and S208 until the second predetermined maintenance routine is executed.

[0066] If the controller 10 exceeds a second predetermined threshold, it proceeds to step S212, where the device 1 is locked for further use. Next, the controller 10 proceeds to step S214 and waits until the necessary maintenance routine is performed. Once the maintenance routine is performed, the controller unlocks the device 1, proceeds to step S208 to reset the counter 2200, and restarts the operation.

[0067] The controller 10 is configured to perform the same method using each of the module run counters 2202n and their respective first and second predetermined module thresholds.

[0068] Figure 5 shows an exemplary schedule of planned maintenance activity packages. Packages are grouped into packages of procedures according to the level of maintenance to be performed on equipment 1. In this example, the packages are referred to as small, medium, and large packages. Controller 10 is configured to schedule preventive maintenance routines to be performed on the equipment according to one of the shown schedules, for example. The schedules and frequencies are fixed on a run basis, for example, preventive maintenance is required every 100 runs, the due date of one of the maintenance packages arrives, and then it becomes overdue.

[0069] Figure 6 shows an example of predicted time intervals (i.e., time periods) compared to the number of processing runs for two types of automated laboratory equipment (equipment A and equipment B) in the upper table. The lower table of Figure 6 shows exemplary intervals in run count units for scheduling each maintenance package to be performed. The controller is configured to trigger a scheduled maintenance package if the threshold time period is exceeded before the threshold number of runs is exceeded.

[0070] Figure 7 shows examples of maintenance activities that may be included in each maintenance package. As shown in the table, maintenance activities may include inspection and / or replacement of parts (e.g., components 1-12), as well as cleaning, lubrication, and / or checking operations depending on which package's maintenance activities are scheduled.

[0071] For example, fan filters do not need to be replaced with every maintenance. In small maintenance packages, they should be checked. If they appear to be in good condition, they do not need to be replaced. However, in medium and large maintenance packages, replacement is necessary. Furthermore, this includes sweeping out the waste liquid line, cleaning the sample rack conveyor belt, and cleaning and lubricating the reagent storage area.

[0072] The following run counters are used to schedule each of these activities.

[0073] Equipment level run counter: - A run counter for the entire device 1 to schedule and trigger recurring preventative maintenance packages. -Measurement unit: Completed run at the instrument level. Module-level run counter - Processing module A -p Head front lan counter -Measurement unit: completed run performed by the front of the head. -p Head rear lan counter -Measurement unit: completed run performed by the rear of the p-head. Module-level run counter - Processing module B -p Head front lan counter -Measurement unit: completed run performed by the front of the head. -p Head rear lan counter -Measurement unit: completed run performed by the rear of the p-head.

[0074] A key limiting factor for triggering preventive maintenance packages is the sample head (e.g., pipette head or "p-head" of instrument 1). Sample head usage defines how often instrument maintenance is performed. Therefore, run-based maintenance, which counts the number of runs since the last preventive maintenance as disclosed herein, is particularly suitable when load balancing of sample heads (e.g., module 14n) is performed, and thus it can be assumed that the usage of each individual sample head is equivalent (to the usage of other sample heads).

[0075] This specification describes the predetermined thresholds for each counter and the corresponding factors considered when determining each threshold.

[0076] As described above, two thresholds are defined for each counter to trigger the corresponding maintenance routine. For example, triggering a maintenance routine may include generating a notification configured to inform the user of the current state of the maintenance operation and the necessary subsequent steps. The threshold values ​​are fixed and specified in the configuration file as described above. Therefore, the thresholds may be changed using software updates with very little impact.

[0077] Each of the two thresholds corresponds to two corresponding maintenance states into which the equipment asset can enter: "expired" and "overdue."

[0078] Figure 8 shows examples of predetermined deadline exceeding thresholds and execution sequences for preventive maintenance packages for two different automated laboratory equipment. In this example, the deadline exceeding threshold for performing preventive maintenance is 100 runs since the last maintenance package was executed for each equipment type.

[0079] The use of load balancing between modules 14n allows the controller 10 to effectively balance the use of redundant modules 14n. For example, if equipment 1 includes redundant modules 14n that are not used at full capacity, modules 14n may be used alternately. In addition, if the planned processing run determined by the workflow manager 20 is not full, redundant units (e.g., sample heads) within the same module 14n may be used alternately.

[0080] The effect of load balancing is the balancing of the occurrence of maintenance activities performed on each of the modules 14n (and the units within those modules 14n). This facilitates the simultaneous occurrence of maintenance package needs for modules 14n (e.g., p-heads) and equipment 1. For example, in a full processing run, the maintenance activities of each module 14n (e.g., p-heads) may reach an overdue state simultaneously with the large package equipment maintenance of both pieces of equipment. As a result, equipment 1 may suffer less overall downtime.

[0081] This concept is illustrated in Figure 9, which shows exemplary maintenance intervals for performing matching equipment maintenance routines and module (e.g., p-head) maintenance routines by selecting predetermined deadline exceedance thresholds to trigger each maintenance routine.

[0082] Each defined counter among the run counters 220 requires the definition of a predetermined expiration threshold. The method for defining each threshold includes the following steps: 1. Determine the tolerance interval ranges for maintenance performed for average, low, and high throughput use of Equipment 1. 2. Determine the tolerance interval ranges for maintenance performed for average, low, and high throughput use of a module or unit of a module (e.g., p-head maintenance). 3. Preferably, assign thresholds based on interval ranges that result in the simultaneous occurrence of module maintenance and equipment maintenance packages.

[0083] The tolerance interval range may be determined based on the usage history of equipment 1. The table below shows exemplary maintenance interval values ​​for low, average, and high equipment throughput for two different pieces of equipment. [Table 1]

[0084] For example, the fixed value of the first predetermined threshold may be set to be between the number of run intervals for low throughput and average throughput (for example, 80 runs for device A).

[0085] The default value of the expiration threshold applied to the module maintenance counter may also be determined based on usage history data and hypothetical calculations. Preferably, the maintenance expiration value for module 14n is defined to facilitate the simultaneous occurrence of maintenance for module 14n and maintenance packages for equipment 14n.

[0086] Assuming that equipment maintenance packages are performed between equipment expiration thresholds (e.g., 80 runs) or near equipment overage thresholds (e.g., 100 runs), module maintenance may be scheduled (using the module expiration threshold) and therefore performed, for example, every 4 or 8 equipment maintenance packages.

[0087] Figure 10 shows a comparison between equipment maintenance and module (p-head) maintenance, illustrating situations where simultaneous occurrence may be possible. Module maintenance is configured to be performed every four equipment maintenance packages. Areas where simultaneous maintenance activities are possible are represented by gray boxes.

[0088] Figure 11 shows an example maintenance schedule for automated laboratory equipment.

[0089] In this example, the equipment expiration threshold occurs every 80 runs (see vertical line), and the maintenance expiration threshold occurs at 100 runs (see vertical dotted line). The grace period between each expiration and expiration threshold (represented by the gray box) represents the period during which maintenance can be initiated. Preferably, the module expiration (and expiration) thresholds are configured to fall within this grace period between the expiration and expiration thresholds, so that the necessary maintenance activities can be performed during a single downtime session.

[0090] In this example, the module (p-head) maintenance deadline is set to 360 runs (see vertical gray line). The second interval (i.e., the grace period) is located immediately after the module (i.e., p-head) deadline event.

[0091] When the deadline for preventative maintenance operations arrives, for example, when one of the run counters 220 exceeds its respective predetermined deadline threshold, the controller 10 is configured to trigger the corresponding maintenance routine, for example, by displaying a message on the UI 12.

[0092] For example, the message may notify the user that the deadline for a service visit is approaching, or request the user to arrange a service appointment within, for example, the next two weeks. The message may also indicate that, otherwise, device 1 will soon no longer be allowed to start any further runs.

[0093] Furthermore, UI12 may provide information about preventative maintenance run counters and any necessary actions related thereto, such as counter resets, threshold increases, and value edits. Messages may indicate which threshold for each counter has been exceeded, and, if the due date threshold has been exceeded, the number of runs (i.e., grace period) that can be performed before the corresponding overdue value is exceeded.

[0094] Users set up appointments to ensure that preventative maintenance actions are performed in response to notifications. For remote services, automated laboratory equipment can also pass warnings and / or alarms regarding preventative maintenance actions to the remote service.

[0095] If the device or module run counter exceeds its respective expiration threshold, the controller 10 is configured to lock device 1 to prevent further runs from running. Device 1 is configured to enter a stopped status and terminate any previously started runs. Once device 1 has finished executing the remaining runs, it is configured to enter an error status. When device 1 is in the error status, it is configured to illuminate a (red) status light and / or display a (red) hardware notification on the UI 12.

[0096] In another example, if the counters of device 1 or module 14n exceed their respective expiration thresholds and a run is scheduled to run, device 1 may enter a reduced throughput mode, and device 1 will continue to run the scheduled run (after rescheduling the run).

[0097] In some cases, if device 1 enters an expired or overdue state, the user can extend the grace period by increasing the overdue threshold. If the connected device 1 is connectable to a remote service, a dedicated extend button may be activated on UI 12 as soon as the maintenance activity (e.g., module or device level) enters an expired state. Activating the extend button allows for an extension of the grace period, thus preventing the device from being locked, for example, during an urgent need. However, if device 1 is not connected to a remote service, the grace period cannot be extended, and device 1 cannot be unlocked until the necessary maintenance is performed.

[0098] At any point between a due date event and an overdue event, the extension button can be pressed to extend the overdue threshold by a certain number of runs (e.g., 50 runs). A visualization of this concept is shown in Figure 12.

[0099] Features disclosed in the foregoing description, or in the following claims, or in the accompanying drawings, and expressed in particular forms therein, or with respect to means for performing the disclosed functions, or methods or processes for obtaining the disclosed results, may be used, individually or in any combination thereof, as needed, to realize the invention in its various forms.

[0100] While the present invention is described in conjunction with the exemplary embodiments described above, many equivalent modifications and variations will be apparent to those skilled in the art given this disclosure. Accordingly, the exemplary embodiments of the present invention described above are illustrative and not limiting. Various modifications to the embodiments described can be made without departing from the spirit and scope of the invention.

[0101] To avoid any misunderstanding, any theoretical explanations provided herein are provided solely for the purpose of improving the reader's understanding. The inventors do not wish to be bound by any of these theoretical explanations.

[0102] Any headings used herein are for organizational purposes only and should not be construed as limiting the subjects described.

[0103] Throughout this Spec., including the following claims, unless the context requires otherwise, the words “comprise” and “include,” as well as variations such as “comprises,” “is equipped,” and “include,” will be understood to mean the inclusion of the integer or step or group of integers or steps described, but not the exclusion of any other integer or step or group of integers or steps.

[0104] It should be noted that the singular forms “a,” “an,” and “the” used herein and in the appended claims include multiple referents unless the context clearly indicates otherwise. Ranges may be expressed herein as “about” one particular value and / or “about” another particular value. When such ranges are expressed, another embodiment includes one particular value and / or another particular value. Similarly, the use of the antecedent “about” will be understood to mean that a particular value forms another embodiment when the value is expressed as an approximation. The term “about” with respect to numbers is arbitrary and means, for example, + / - 10%.

Claims

1. An automated laboratory apparatus for analyzing biological samples, comprising a controller for adjusting the automated laboratory apparatus, The aforementioned controller The automated laboratory equipment is to be made to perform one or more processing runs, each processing run comprising one or more protocols to be performed for each of the biological samples. To monitor the total number of processing runs completed by the aforementioned laboratory equipment, When the total number of processing runs exceeds a predetermined run threshold, a maintenance routine is triggered to be performed on the automated laboratory equipment. An automated laboratory device configured to perform the following tasks.

2. Each processing run is assigned to a module of the automated laboratory equipment and executed by the module of the automated laboratory equipment, and the automated laboratory equipment comprises multiple modules, The controller is configured to monitor the number of processing runs completed by each module, and to trigger a module maintenance routine to be performed on the module when the number of processing runs exceeds a predetermined module run threshold. The automated laboratory equipment according to claim 1.

3. The automated laboratory equipment according to claim 2, wherein each module includes one or more pipette heads of the laboratory equipment.

4. The automated laboratory equipment according to any one of claims 1 to 3, wherein triggering the equipment maintenance routine and / or optionally each module maintenance routine includes one or more of the following: generating a user notification indicating that maintenance is scheduled, starting an automated maintenance routine, and / or sending a notification to a remote service.

5. The automated laboratory equipment according to any one of claims 1 to 4, wherein the controller is configured to reset the monitored number of processing runs when it detects that each of the maintenance routines has been performed.

6. The predetermined run threshold or each predetermined run threshold is the first predetermined run threshold, and the controller The determination is made when the total number of processing runs or the number of individual processing runs exceeds a second predetermined run threshold that is higher than the first predetermined run threshold. Preventing or reducing the operation of the automated laboratory equipment until the triggered maintenance routine is executed, An automated laboratory apparatus according to any one of claims 1 to 5, configured to perform the following:

7. After determining that the first predetermined run threshold has been exceeded, the controller, upon detecting a user request for extension, requests an extension key from the remote service. Using the extension key to increase the second predetermined run threshold, The automated laboratory apparatus according to claim 6, further configured to perform the following:

8. The automated laboratory equipment according to any one of claims 1 to 7, wherein the predetermined run threshold or each predetermined run threshold is a fixed value obtainable from the configuration file of the automated laboratory equipment.

9. The predetermined run threshold is determined based on historical performance information recorded when the automated laboratory equipment experiences low throughput and average throughput. The predetermined run threshold or each predetermined run threshold, The number of historical runs completed between subsequent maintenance routines when the automated laboratory equipment is affected by low throughput, and The number of historical runs completed between subsequent maintenance routines when the automated laboratory equipment experiences average throughput. An automated laboratory apparatus according to any one of claims 1 to 8, selected from the range defined by [the relevant definition].

10. The automated laboratory equipment according to any one of claims 2 to 9, wherein each predetermined module threshold is configured to be exceeded when the predetermined run threshold is exceeded so that the trigger for each module maintenance routine coincides with the trigger for the equipment maintenance routine.

11. The aforementioned equipment maintenance routine is one of a plurality of equipment maintenance routines selectable by the controller, and each equipment maintenance routine corresponds to the respective level of maintenance to be performed. Higher-level maintenance routines involve more maintenance activities and / or require more time and / or resources to perform than lower-level maintenance routines. The controller is configured to select the equipment maintenance routine for triggering based on the schedule of the equipment maintenance routine. An automated laboratory apparatus according to any one of claims 1 to 10.

12. The automated laboratory equipment according to claim 11, wherein the schedule of the equipment maintenance routines is configured to ensure that a higher-level maintenance routine among the plurality of equipment maintenance routines is executed only after one or more lower-level maintenance routines have been executed.

13. The aforementioned multiple maintenance routines include at least, Lower-level maintenance routines, including checking equipment assets, A higher level of maintenance routine, which includes replacing the aforementioned equipment assets, The automated laboratory apparatus according to claim 11 or 12, including the following:

14. A computer implementation method for triggering maintenance of automated laboratory equipment, The automated laboratory equipment is configured to perform one or more processing runs, each processing run comprising one or more protocols to be performed for each of the biological samples. The method described above is To monitor the total number of processing runs completed by the aforementioned laboratory equipment, When the total number of processing runs exceeds a predetermined run threshold, a trigger is activated to execute an equipment maintenance routine on the automated laboratory equipment. Computer implementation methods, including those mentioned above.

15. A computer-readable medium that, when executed by a computer, includes instructions causing the computer to execute the computer implementation method described in claim 14.

Images