Managing a laboratory instrument

Abstract

The disclosure pertains to a computer-implemented method of managing a software update of at least one laboratory instrument by a computing device communicatively couplable to the laboratory instrument, the method comprising: providing, by a computing device, a pause command receivable the at least one laboratory instrument, wherein the pause command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to at least temporarily prevent installation of the software update on the laboratory instrument; providing, by the computing device, a resolution command to the at least one laboratory instrument, wherein the resolution command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to allow installation of the software update, to replace the software update by an updated version, or to permanently prevent installation of the software update on the laboratory instrument.

Description

[0001] MANAGING A LABORATORY INSTRUMENT

[0002] CROSS REFERENCE TO RELATED APPLICATION

[0003] This is a PCT International application of, and claims the benefit of priority to, Indian provisional patent application IN202441005280 for “ Managing a Laboratory Instrument” filed on January 25, 2024 in the Indian Patent Office, the disclosure of which is hereby incorporation by reference in its entirety.

[0004] TECHNICAL FIELD

[0005] The present invention relates to the field of managing laboratory instruments and / or devices, such as for example sample rack manipulation devices and / or sample testing systems, such as semi- or full-automatic sample analysis and testing apparatuses for testing sample material. The present invention may particularly relate to managing a software update of a laboratory instrument, in particular for remotely managing a software update of a laboratory instrument.

[0006] BACKGROUND

[0007] The contents of this section only provide background information related to the present disclosure, which may not necessarily be the prior art.

[0008] Various analytical testing instruments for testing samples or sample material, e.g., sample tubes, sample containers or cups, are indispensable in the medical field, especially in clinical medicine and laboratory medicine. In particular for processing a large number of samples per unit time, fully- or semi-automated laboratory instruments, are widely used in clinical laboratories and have become an important part in modem laboratory testing.

[0009] Fully- or semi-automated laboratory instruments are usually employed in laboratories with high throughput. These systems can be run around the clock at minimum operational pauses, as operational pauses may be detrimental to the workflow and / or speed of providing the analysis or testing results of a plurality of samples. It is therefore desirable to minimise pause times in these laboratory instruments.

[0010] The laboratory instruments in question typically comprise a controller or a control unit, which typically runs a software or software application in order to control the laboratory instruments and / or their workflow. There may be provided a software update for the software or software application used on the laboratory instruments, for example by the manufacturer of the laboratory instruments. These updates may be received by the laboratory instruments either through an online service, for example as a download from a server, or through an offline medium, for example a computer-readable medium storing the software update. However, as installation of the software update may cause the laboratory instrument to pause work during installation, the installation of the software update may be postponed or scheduled to a specific time when a planned downtime of the laboratory instrument is available.

[0011] Even with thorough testing of the software, a software update may lead to unwanted effects on the laboratory instrument. Such scenarios may pertain to special circumstances which may not even be predictable before releasing a software update for laboratory instruments. On the other hand, improvements of a software may be released before a previous software update has been installed on a laboratory instrument.

[0012] SUMMARY

[0013] Therefore, it may be desirable to provide control of a software update procedure for laboratory instruments and / or to provide an improvement in managing at least one laboratory instrument, particularly minimizing unnecessary downtime of the laboratory instrument. Accordingly, aspects of the present disclosure can allow for an improvement in managing at least one laboratory instrument, particularly the prevention of unnecessary downtime. Also, aspects of the present disclosure can allow for an improvement in managing a software update of at least one laboratory instrument, particularly preventing negative or unwanted effects of the software update and / or allowing for an early installation of software improvements.

[0014] This is achieved by the subject matter of the independent claims, wherein further examples are contained in the dependent claims and the following description.

[0015] Aspects of the present disclosure relate to a computer-implemented method. The method may be a computer-implemented method of managing a software update of at least one laboratory instrument by a computing device communicatively couplable to the laboratory instrument, or may be a computer-implemented method of managing a software update by at least one laboratory instrument. Further aspects of the present disclosure relate to corresponding one or more computer programs, and to corresponding one or more computer- readable mediums, for example non- transitory computer-readable mediums, storing such one or more computer programs. Further aspects of the present disclosure relate to a computing device, a laboratory instrument and a laboratory instrument servicing system. Any disclosure presented herein with reference to one aspect of the present disclosure equally applies to any other aspect of the present disclosure.

[0016] According to a first aspect of the present disclosure a computer-implemented method, e.g., a computer implemented method for of managing at least one laboratory instrument and / or managing a software update of at least one laboratory instrument is provided. The method may be a method of remotely managing at least one laboratory instrument and / or a software update of at least one laboratory instrument by a computing device communicatively couplable and / or coupled to the laboratory instrament. The method according to the first aspect of the present disclosure comprises:

[0017] - providing, by a computing device, a pause command to at least one laboratory instrument, the laboratory instrument being communicatively coupled with the computing device, wherein the pause command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to at least temporarily prevent installation of the software update on the laboratory instrument; and

[0018] - providing, by the computing device, a resolution command to the at least one laboratory instrument, wherein the resolution command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out a resolution action, the resolution action being one of: action of allowing installation of the software update, action of replacing the software update by an updated version, and the action of permanently preventing installation of the software update on the laboratory instrument.

[0019] The laboratory instrument may be a laboratory analyzer. In particular, the laboratory instrument is used in a clinical laboratory to perform laboratory tests on biological samples. The laboratory instrument may be designed to measure clinical parameters, e.g., chemical substances, cellular components, or biomarkers. The laboratory instrument may be designed to assist in one or more of the diagnosis, monitoring and treatment of medical conditions. The laboratory instrument may be a pre-analysis laboratory instrument and / or a post-analysis laboratory instrument.

[0020] The laboratory instrument may be or be comprised in an automated laboratory system (ALS). The laboratory instrument may be capable of communicating with other laboratory instruments and / or communicating with other devices (e.g., computers). The laboratory instrument may be referred to as a laboratory device or laboratory equipment and may include laboratory automation. The laboratory instrument may be a medical or clinical analyzer. The laboratory instrument may include one or more pre-analysis, analysis and post analysis components.

[0021] A laboratory analyzer is, in particular, a laboratory instrument configured to carry out one or more analytic steps, such as measuring one or more characteristics of a biological sample, e.g., the concentration of an analyte. The laboratory analyzer may include an immunoassay analyzer, a chemistry analyzer, and identification and antibiotic susceptibility analyzer, a bacteriology analyzer, a molecular analyzer, a hematology analyzer or a urinalysis instrument.

[0022] An automation component may be for moving containers from one laboratory instrument to another laboratory instrument or for moving containers from one component of a laboratory instrument to another component of the same laboratory instrument or to another component of another laboratory instrument. The automation component may include a track, a belt and / or a container carrier configured to move biological samples.

[0023] Generally, an ALS is an assembly comprising a plurality of components and a computing device, wherein the computing device is operatively connected to the plurality of components and is configured to control each component. A component may be a laboratory analyzer, a pre-analysis laboratory instrument, a post analysis laboratory instrument, and input / output module, an automation component (e.g., track, belt, container carrier) configured to move a biological sample within the laboratory. In particular, the ALS may comprise one or more subsystems, wherein a subsystem comprises one or more components of the ALS.

[0024] A pre-analysis laboratory instrument is configured to carry out one or more analytic steps on a biological sample to prepare the biological sample for the analytic instrument(s). A preanalysis laboratory instrument may include a centrifuge, a decapper, recapper (e.g., for putting caps back on containers) and / or aliquoter.

[0025] A post-analysis laboratory instrument is configured to carry out one or more post-analytic steps on the biological sample after the biological sample has been processed by one or more laboratory analyzers. A post-analysis laboratory instrument may include one or more of a recapper, a storage device, a refrigerator, and an input / output device. Both pre-analysis and post-analysis laboratory instruments may be referred to as peri-analytical laboratory instruments.

[0026] In particular, the laboratory instrument may generally be a laboratory device for laboratory or clinical testing of a sample, for example a sample containing sample material obtained from one or more patients or individuals. The term laboratory instrument may include, for example, devices for collecting, manipulating, preparing, transporting, sorting, storing and / or actually analysing one or more samples, for example to obtain and / or measure one or more parameters based on the analysis. The biological sample (or simply “sample”) may be a sample of a bodily fluid of a human or animal subject. For example, the bodily fluid may be a physiological fluid, such as blood, saliva, urine, sweat, amniotic fluid, cerebrospinal fluid, ascites fluid, or the like. The biological sample may be put into a sample container after collection and it may be held in the container while being processed. The sample container may be a sample tube. Typically, sample tubes comprise a closed tube end and an end opposite thereto. The latter end defines an opening for inserting the sample in the sample tube. The opening may be closed, e.g., sealed, by a cap.

[0027] The laboratory instrument may run a software application, for example a firmware, used to control the laboratory instrument. In the context of the present disclosure, the “software update” may be or may comprise an alteration, modification and / or an addition to this software application, for example a feature update pertaining to work functions of the laboratory instrument and / or a security update pertaining to data and / or process security. In particular the laboratory instrument may comprise a computing device.

[0028] According to the present disclosure, the computing device may comprise or be a cloud computing system or platform. It may comprise or be a distributed computer system. A computing device may comprise or be a network of connected desktop PCs and / or workstations and / or laptops and / or tablet PCs or the like. The network may be a LAN and / or a wireless LAN. In particular, according to the present invention, a computing device may be a desktop PC, a workstation, a laptop or a tablet PC or the like. As described herein, a computing device, e.g., the first computing device, may comprise one or more processors, e.g., a CPU, a GPU, a Tensor Processing Unit (TPU), or the like and a memory.

[0029] The computing device may, for example, be a server device or server network. For example, the computing device may be a web server and / or a cloud server. The computing device may provide a web service and / or a cloud service, wherein the service may be used for communication with the laboratory instrument, for instance via the Internet. The computing device may be configured to be connectable and / or communicatively couplable to the laboratory instrument for instance through loT connectivity, cellular connectivity, Wi-Fi connectivity, WLAN connectivity, LPWAN connectivity or Bluetooth connectivity. This is especially suitable if the method is directed to remote management. In an alternative embodiment, the computing device may also be a portable device, for example a portable computer, laptop, handheld, or smartphone, which may, for example, be used by a service technician servicing the laboratory instrument. Communication with the laboratory instrument may then be established through local wired or wireless communications, like LAN, WLAN, LPWAN, Wi-Fi, Bluetooth, or any other suitable communications technique.

[0030] The present disclosure is described as a method which may be performed by the computing device and / or a method which may be performed by the laboratory instrument and / or a method which may be performed by a laboratory instrument servicing system, the last of which may be a combination of the first two. However, regardless of the point of view, the methods disclosed herein are highly interrelated and correspond to each other. Therefore, the features of one of the methods disclosed herein are equally and analogously applicable to the other methods and vice versa.

[0031] According to the present disclosure, a command may comprise, e.g., consists of, one or more data items. In particular, a command may be or be comprised in a computer file, which e.g., is provided by the computing device to the laboratory instrument. The computer file may be a json file, a text file and / or an executable file. For example, a command comprises information that specifies to the laboratory instrument a respective action to be carried out by said instrument. For instance, in case of the pause command, the respective action is the pause action, i.e., the action of at least temporarily prevent installation of the software update on the laboratory instrument. Exemplarily, in case of the resolution command, the respective action is the resolution action. In particular, when processed by the laboratory instrument, the information comprised in the command instructs and / or causes the laboratory instrument to carry out the respective action. In particular, the information comprised in a command may be comprised in the value of one or more variables. Exemplarily, the laboratory instrument may comprise computer executable instructions which, when executed by the laboratory instrument, cause the laboratory instrument to access the information comprised in the command and, based on said information, carry out the respective action. For instance, said information is comprised in a set of computer executable instructions e.g., which when executed by the laboratory instrument, cause the laboratory instrument to carry out the respective action. For example, the pause command may comprise information that specifies that the laboratory instrument shall prevent, at least temporarily, the installation of the software update. Alternatively or in addition, the resolution command may comprise information that specifies that the laboratory instrument shall carry out the resolution action.

[0032] According to the present disclosure, providing a data item (e.g., a command, an identifier, software, a software update, a piece of information) to a device (e.g., a computing device or a laboratory instrument, in particular the computing device comprised therein) may be carried out by making said item available to said device, e.g. by storing said information in a memory comprised in or accessible by said device and / or by granting said device access to said item, so that said device can retrieve, copy and / or access said data. For example, providing a data item to a device may comprise sending and / or transmitting, e.g., over a network, said data to said computing device. For instance, providing a data item to a laboratory instrument comprises providing said data item to a computing device comprised in the laboratory instrument.

[0033] To prevent an abrupt interruption of the workflow of the laboratory instrument whenever a software update is provided by the computing device or obtained by the laboratory instrument, the laboratory instrument may be configured to store the software update without immediately installing it. The actual installation may therefore be scheduled or initiated by a user or operator of the laboratory instrument when convenient. An installation due date may be assigned to the software update, wherein the installation due date defines a date on or after which an installation of the software update on the laboratory instrument is forced. Until the installation due date arrives, an operator of the laboratory instrument is free to schedule the installation of the software update whenever convenient for the workflow of the laboratory instrument. It may be provided that the installation due date is at least one month or at least two months or at least three months or at least five months or at least seven months, for example nine months, after the provision of the software update on the cloud server and / or after the obtaining of the software update on the laboratory instrument.

[0034] This may provide the operator of the laboratory instrument with a high degree of flexibility regarding when to install the software update. Typically, software updates may be provided for a plurality of laboratory instruments. Therefore, at any point of time between the provision of the software update and the installation due date, there may be a plurality of laboratory instruments that have already installed the software update and there may be a plurality of laboratory instruments that have not yet installed the software update. The publisher of the software update, for example the manufacturer of the laboratory instrument, may therefore become aware of and / or find out one or more undesired effects that the software update may have on the laboratory instruments, if the software update is installed on those laboratory instruments. For example, this information may be provided by operators of laboratory instruments which have already installed the software update and / or automatically by the laboratory instruments which have already installed the software update themselves.

[0035] In this constellation, the present disclosure provides a way of preventing the undesired effects on the laboratory instruments which have not yet installed the software update. By providing the pause command, the computing device may prevent the software update from being installed on any further laboratory instruments which have not yet been completely updated. The installation of the software update may, through the present disclosure, even be prevented on laboratory instruments which have already obtained the software update and stored it locally, for example in a local data storage of the laboratory instrument itself, for example before the installation due date arrives. By only altering or stopping the provision of the software update to the laboratory instruments that have not downloaded the software update yet, the laboratory instruments which have downloaded but not yet installed said software update would normally not be reached and would therefore possibly experience the undesired effect of the software update. Through providing a pause command that also reaches these laboratory instruments, installation of the software update and therefore the respective undesired effects may be prevented.

[0036] The provider of the software update may therefore gain a time window to rectify any faults and to solve any problems pertaining to the software update. In this time window, at least no additional installations occur. After a resolution of the underlying problem may have been found, the resolution command may be provided to resolve the suspended software update in one of different ways. If it has been found that there actually were no undesired effects or that the undesired effects are negligible or that the one or more undesired effects of the software update are outweighed by the positive effects, the resolution command, when processed by the laboratory instrument, may cause and / or instruct the laboratory instrument to allow the installation of the software update, i.e., cause and / or instruct the laboratory instrument to carry out the action of allowing the installation of the software update. If an updated version of the software update is provided, the resolution command, when processed by the laboratory instrument, may cause and / or instruct the laboratory instrument to obtain the updated version of the software update and install the updated version, for example at the installation due date, which may be the installation due date of the original software update or a new one applicable to the updated version of the software update. Hence, in this case, the resolution command, when processed by the laboratory instrument, may cause and / or instruct the laboratory instrument to carry out the action of obtaining the updated version of the software update. If the best course of action is determined to be to cancel the software update entirely, the resolution command may, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out the action of permanently preventing installation of the software update on the laboratory instrument, for example by deleting the software update.

[0037] Exemplarily, the method according to the first aspect of the present disclosure may further comprise receiving, by the computing device, pause information specifying that the pause command shall be issued. In particular, receiving the pause information is carried out after the manufacturer of the laboratory instrument has become aware of and / or found out one or more undesired effects that the software update may have on laboratory instruments, if that update is installed on those laboratory instruments. The method according to the first aspect of the present disclosure may further comprise receiving, by the computing device, resolution information specifying that the resume command shall be issued. In particular, the resolution information may further specify the resolution action that the laboratory instrument shall carry out. In particular, receiving the resolution information is carried out after a resolution of the underlying problem has been found, e.g., by the manufacturer of the laboratory instrument. For instance, the pause information and / or the resolution information may be provided to the computing device by the manufacturer of the laboratory device, e.g., by an employee of the manufacturer of the laboratory instrument and / or of the software, e.g., by using a dedicated software and / or via a network.

[0038] The method may comprise obtaining, by the computing device, the software update for download by the laboratory instrument. In particular, obtaining the software update is carried out before providing the pause command. Moreover, the method may further comprise providing, by the computing device, the software update to the laboratory instrument. It may be sufficient for the computing device to simply provide the software update in a way to make the software update accessible for the laboratory instrument, for example through the online service or cloud service. The computing device may also provide the software update as push data, for example actively sending the software update to the laboratory instrument. Any way of transmitting the software update from the computing device to the laboratory instrument may be employed.

[0039] According to the present disclosure, obtaining a data item (e.g., a command, an identifier, software, a software update, an indication, a log message, a schedule, a piece of information) from a device (e.g., a computing device or a laboratory instrument, in particular the computing device comprised therein) may comprise receiving the data item from a device, which e.g., sends and / or transmits said data item. Obtaining a data item from a device may comprise retrieving the data item from the device, which, e.g., makes said data item available. In this case, obtaining the data item from the device may comprise accessing said data item e.g., by accessing the memory of the device that stores the data item. For instance, obtaining a data item from a device may comprise receiving a link to that data item and accessing and / or downloading the data item by using that link.

[0040] The same may apply to the steps of providing the pause command and / or the resolution command. For instance, providing the pause command may comprise transmitting and / or sending the pause command from the computing device to the laboratory instrument. Additionally or alternatively, providing the resolution command may comprise transmitting and / or sending the resolution command from the computing device to the laboratory instrument. Alternatively, it may be sufficient for the computing device to provide the pause command and / or resolution command in a way to make the pause command and / or resolution command accessible for the laboratory instrument, for example through the online service or cloud service. In this case, it is advantageous if the laboratory instrument is configured to regularly check whether or not a pause command and / or resolution command is available / provided on the computing device.

[0041] Prior to the providing the pause command, the method may comprise obtaining, e.g., receiving, by the computing device, an indication that the software update may have an undesired effect when installed by the laboratory instrument. This indication may comprise or may be the pause information mentioned above. It may originate, for example, from a user or provider of the computing device, which is typically the manufacturer of the laboratory instrument and therefore also the provider of the software update. Alternatively, this indication may originate from at least one laboratory instrument and / or at least one user of at least one laboratory instrument on which the software update has already been installed. For example, the cloud service of the computing device may be used to register reports of undesired effects caused by the software update on the laboratory instruments when the software update is installed on those instruments. Said indication may then be used to trigger the providing of the pause command. The indication or the pause information may or may not comprise information specifying the nature of the possible undesired effect of the software update. The indication or the pause information may therefore be a simple command or control signal to issue the pause command or may comprise further information, for example about the type and / or magnitude of the undesired effect. In case such information is included, it may also be comprised in the pause command and may be made available for the user of the laboratory instrument, for example by outputting the information on the laboratory instrument. It may also be implemented that the providing of the pause command is only triggered when a threshold number of indications of an undesired effect has been reached, for example, when a minimum number of laboratory instruments or users of laboratory instruments on which the software update has already been installed report at least one undesired effect, either to the computing device or the user or provider of the computing device.

[0042] Prior to the providing the resolution command, the method may comprise obtaining, e.g., receiving, by the computing device, an indication that the undesired effect does not exist or an indication of a resolution of the undesired effect by either one of replacing the software update by an updated version, or permanently preventing installation of the software update on the laboratory instrument. This indication may comprise or may be the resolution information mentioned above. It may originate from the user or provider of the computing device. For example, it may have been determined that the undesired effect actually does not exist or that the undesired effect may be prevented by an updated version of the software update. Alternatively, it may have been determined that the best course of action is not to install the software update at all. This indication may therefore be used as a trigger for providing the resolution command. The indication or the resolution information may or may not comprise information specifying the nature of the resolution of the possible undesired effect of the software update. The indication or the resolution information may therefore be a simple command or control signal to issue the resolution command or may comprise further information, for example about the type of the resolution of the undesired effect. In case such information is included, it may also be comprised in the resolution command and may be made available for the user of the laboratory instrument, for example by outputting the information on the laboratory instrument.

[0043] To ensure a correct sequence of steps and that the commands provided by the computing device are only implemented on eligible laboratory instruments, it may be provided that the installation of the software update is at least temporarily prevented only when each condition of a first set of conditions is fulfilled, wherein the first set of conditions comprises the condition that the software update has not yet been installed on the laboratory instrument. In particular, it may be provided that the pause command is configured to only take effect when the software update has not yet been installed on the laboratory instrument. For instance, the pause command may only be processed by the laboratory instrument, when each condition of the first set of conditions is fulfilled. In some cases, the pause command is processed by the laboratory instrument and, hence, the action specified by that command, i.e., the action of at least temporarily preventing installation of the software update on the laboratory instrument, is carried out by the laboratory instrument only when each condition of the first set of conditions is fulfilled.

[0044] Additionally or alternatively, it may be provided that the resolution action is only carried out and / or implemented when each condition of a second set of conditions is fulfilled, wherein the second set of conditions comprises one or more of: the condition that the installation of the software update is at least temporarily prevented and the condition that the software update has not yet been installed on the laboratory instrument. The second set of conditions may therefore comprise the condition that the action specified by the pause command, i.e., the action of at least temporarily preventing installation of the software update on the laboratory instrument, has been carried out and / or implemented on the laboratory instrument. In particular, it may be provided that the resolution command is configured to only take effect when the pause command has taken effect on the laboratory instrument. For instance, the resolution command may only be processed by the laboratory instrument when each condition of the second set of conditions is fulfilled. In some cases, the resolution command is processed by the laboratory instrument and, hence, the resolution action is carried out by the laboratory instrument only when each condition of the second set of conditions is fulfilled.

[0045] For example, the resolution command and / or the pause command may include instructions for the laboratory instrument to check the current status of the instrument and only take effect when the status is in agreement with the first set of conditions and the second set of conditions, respectively. For example, the pause command and / or the resolution command may be processed by eligible laboratory instruments only.

[0046] According to the present disclosure, a set may comprise one or more elements. Hence, in particular, a set of conditions may comprise one or more conditions. The method may further comprise obtaining, e.g., receiving, by the computing device, a first log message provided by the laboratory instrument, wherein the first log message is indicative of successful or unsuccessful obtaining or download of the software update at the laboratory instrument. The first log message may therefore be used to create an overview at the computing device pertaining to which laboratory instruments of a plurality of laboratory instruments managed by the computing device have successfully obtained the software update. As these laboratory instruments are the ones that may potentially realise the undesired effect of the software update, such an overview may be helpful in the resolution of the underlying problem.

[0047] The method may further comprise obtaining, e.g., receiving, by the computing device, a second log message provided by the laboratory instrument, wherein the second log message is indicative of successful or unsuccessful prevention, at least temporarily, of the installation of the software update. The second log message may therefore be used to create an overview at the computing device pertaining to which laboratory instruments have actually installed the software update and which laboratory instruments have not yet installed the software update. As it may be helpful to implement some immediate action at the laboratory instruments having already installed the software update even prior to providing the resolution command, this may be helpful in preventing downtimes. The method may further comprise obtaining, e.g., receiving, by the computing device, a third log message provided by the laboratory instrument, wherein the third log message is indicative of whether the carrying out of the resolution action has been successful or unsuccessful. In particular, the third log message may be indicative of: a) successful or unsuccessful installation of the software update, b) successful or unsuccessful replacement of the software update, or c) successful or unsuccessful permanent prevention of the installation of the software update. The third log message may therefore be used to create an overview at the computing device pertaining to at which laboratory instruments the potential threat of an undesired effect caused by the original software update has been averted. This overview may therefore be used to focus further attention on laboratory instruments at which the resolution has not yet taken effect, therefore possibly preventing downtimes.

[0048] In case any one of the first log message, the second log message and the third log message indicates an unsuccessful process, the computing device may be configured to notify a provider of the computing device and / or a user of the laboratory instrument. This may be achieved, for example, by providing and / or outputting an error message. To be able to more closely describe the problem, the notification may comprise information specifying why the respective process was unsuccessful. This notification focuses attention on laboratory instruments experiencing some kind of malfunction of the presently disclosed method, which are therefore especially prone to errors and possible downtimes. The notification therefore serves to ensure correct performance of the method and enables a user to intervene when necessary. In particular, the first log message indicates an unsuccessful process when the first log message indicates an unsuccessful receipt and / or download of the software update by the laboratory instrument. Exemplarily, the second log message indicates an unsuccessful process when the second log message indicates an unsuccessful prevention of the installation of the software update on the laboratory instrument. For instance, the third log message indicates an unsuccessful process when the third log message indicates that the carrying out of the resolution action has been unsuccessful, i.e., depending on the resolution action, an unsuccessful installation, replacement, or permanent prevention of the installation of the software update on the laboratory instrument.

[0049] Any or all of the first log message, the second log message, the third log message, and the error message may comprise or may be a cleartext message, an encoded message, or an indication of the meaning of the respective message, e.g. a respective alphanumeric code. The messages may comprise computer-readable code and / or human-readable text or numbers indicating the respective content or meaning of the message. To enable a quick and easy implementation of the method, the laboratory instruments and the software update of the laboratory instruments may be managed remotely. This may be achieved by the method further comprising one or more of causing, by the computing device, the laboratory instrument to obtain the software update and causing, by the computing device, the laboratory instrument to obtain the updated version of the software update. For example, the method may comprise remotely scheduling, by the computing device, the obtaining of the software update by the laboratory instrument, for example the download of the software update. Additionally or alternatively, the method may comprise remotely scheduling, by the computing device, the obtaining of the updated version of the software update by the laboratory instrument. This way, it is not necessary that a service technician is actually on-site with the laboratory instrument. As all of the processes that need to be carried out at the laboratory instrument may be caused, controlled, scheduled and / or initiated remotely by the computing device, a reaction speed for the prevention of undesired effects is high.

[0050] According to the present disclosure causing, by the computing device, the laboratory instrument to do something may comprise instructing, by the computing device, the laboratory instrument to do something. For instance, causing, by the computing device, the laboratory instrument to do something may comprise remotely controlling, by the computing device, one or more components of the laboratory instrument to do something.

[0051] For instance, providing the pause command comprises remotely scheduling and / or initiating the carrying out of the pause action, i.e., the action of at least temporarily preventing installation of the software update on the laboratory instrument. In particular, remotely scheduling and / or initiating the carrying out of the pause action may be performed by using the pause command. More particularly, the pause command may comprise information specifying a starting time at which the pause action shall be carried out. In this case, the pause command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out the pause action at or after the starting time. For instance, the pause command may comprise information specifying that the pause action shall be carried out directly upon processing of the pause command. In this case, the pause command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out the pause action directly upon processing of the pause command.

[0052] Exemplarily, providing the resolution command comprises remotely scheduling and / or initiating the carrying out of the resolution action, i.e., the replacement and the permanent prevention of the installation of the software update at or on the laboratory instrument. In particular, remotely scheduling and / or initiating the carrying out of the resolution action may be performed by using the resolution command. More particularly, the resolution command may comprise information specifying a starting time at which the resolution action shall be carried out. In this case, the resolution command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out the resolution action at or after the starting time. For instance, the resolution command may comprise information specifying that the resolution action shall be carried out directly upon processing of the resolution command. In this case, the resolution command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out the resolution action directly upon processing of the resolution command.

[0053] The method may comprise providing, by the computing device, an instrument identifier to the laboratory instrument, wherein the instrument identifier is indicative of which laboratory instrument or which type of laboratory instrument is addressed by the pause command, and the installation of the software update is at least temporarily prevented only when each condition of a first set of conditions is fulfilled, wherein the first set of conditions comprises the condition that the laboratory instrument is indicated or is of a type indicated by the instrument identifier. The first set of conditions may be the same first set of conditions as mentioned above. In particular, the pause command may only be run and / or implemented on laboratory devices fulfilling the first set of conditions. The pause command may comprise the instrument identifier. The instrument identifier may be indicative of which laboratory instrument or which type of laboratory instrument is addressed by the pause command. In particular, the instrument identifier is used to identify each laboratory instrument on which the pause command should be processed out of a plurality of laboratory instruments managed by the computing device. The pause command is not processed by laboratory instruments other than the ones indicated by the instrument identifier. For instance, the pause command may be configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to prevent installation of the software update on the laboratory instrument only in case the laboratory instrument is indicated or is of a type indicated by the instrument identifier of the pause command. For example, it may be that only a subgroup of laboratory instruments which received the software update actually shows the undesired effect after installation of the software update and / or that only a certain type of instruments are involved in the software update. To specifically target these laboratory instruments, the instrument identifier may be used. The instrument identifier may therefore be configured to indicate the subgroup of laboratory instruments which received the software update and which are expected to experience the undesired effect upon installation of the software update.

[0054] The instrument identifier may comprise information about at least one of software version, e.g. one or more versions of the software currently running on the laboratory instrument, instrument version, instrument build number, and geographical location of the laboratory instrument. These parameters may be used to identify the laboratory instruments which may experience an undesired effect of the software update and which are therefore targeted by the pause command. For instance, the first set of conditions may comprise the condition that the software version currently running on the laboratory instrument is one version of the one or more versions. This way, the laboratory instruments may be specifically targeted by the use of the instrument identifier.

[0055] To inform a user of the laboratory instrument, the method may comprise that the pause command is configured to cause an explanatory notice to be outputted by the laboratory instrument, the explanatory notice indicating that installation of the software update is currently prevented. In particular, the explanatory notice is outputted whenever a user tries to initiate installation of the software update on the laboratory instrument. In particular, it may be provided that, when the pause command has taken effect on the laboratory instrument, an explanatory notice is displayable on the laboratory instrument indicating that installation of the software update is currently prevented. The explanatory notice is in particular outputted whenever a user tries to initiate installation of the software update on the laboratory instrument in a time point within a time interval after the pause action has been carried out by the laboratory instrument. In particular said time interval is before the resolution action has been carried out by the laboratory instrument. Concurrently, the attempt of the user to initiate the installation of the software update may be blocked, prevented or ignored to make sure that the software update is not installed after the pause command has reached the laboratory instrument and before the resolution command has been received by the laboratory instrument. Through the explanatory notice, the user is informed that the software update is currently not installable until the resolution command has been received from the computing device. If the resolution command causes a permanent prevention of the installation of the software update on the laboratory instrument through the respective resolution action, the explanatory notice may also be used. The explanatory notice may therefore be outputted after the resolution command has been run and / or implemented on the laboratory instrument, causing the permanent prevention of the installation of the software update on the laboratory instrument. The explanatory notice may be output directly on an output device of the laboratory instrument, for example a display, or the explanatory notice may be output to a further device the user of the laboratory instrument may be using to control the laboratory instrument, for example a computer or a handheld device like a smartphone.

[0056] Outputting the explanatory notice may comprise displaying said notice, e.g., on a computer display. Outputting the explanatory notice may comprise providing said notice to a user in a human readable format e.g., by using an output device of the laboratory instrument. For instance, the explanatory notice may be a window displayed on a computer display of the laboratory instrument. In particular, the explanatory notice may be a text file printed by using a printer of the laboratory instrument. Exemplarily, the explanatory notice may be an audio file played by using one or more speakers of the laboratory instrument.

[0057] The method may further comprise providing, by the computing device, a message to the laboratory instrument and / or a user of the laboratory instrument whenever a software update is available for the laboratory instrument. The message may be displayed e.g., output to the user of the laboratory instrument similarly to the explanatory notice, i.e. on the laboratory instrument itself or on a further device. By providing the message, the computing device may assist the user in keeping the laboratory instrument up-to-date and in optimal working condition.

[0058] The method may further comprise retaining, on the computing device, a status repository of the laboratory instrument. The status repository may comprise information about the laboratory instrument. The information about the laboratory instrument may comprise at least the current software version installed on the laboratory instrument and the most recent software version available for the laboratory instrument. Further information about the laboratory instrument, for example instrument version, instrument build number, and geographical location of the laboratory instrument, or other information may also be included in the status repository. The status repository may comprise a device twin or a digital twin of the laboratory instrument. Any or all of the first, the second, or the third log message may be stored in or may be used to update the status repository. In this way, the status repository may always contain the current and up-to-date status information of the laboratory instrument. By accessing and updating the status repository by each of the computing device and the laboratory instrument, communication and / or data transmission between the computing device and the laboratory instrument may be implemented.

[0059] Another optional step of the method may be obtaining, e.g., receiving, by the computing device, an indication of a user input by a user of the laboratory instrument. The user input may be directly transmitted to the computing device or the user input may trigger the generation of a message which is then transmitted to the computing device. The user input may be indicative of whether or not the user wishes to install the software update on the laboratory instrument. The method may further comprise updating the information about the laboratory instrument in the status repository based on said indication. For example, the status repository may comprise information specifying a current software version running on the laboratory instrument, a presently available software version and a desired software version of the laboratory instrument. The desired software version is the software version which the user of the laboratory instrument wants to employ on their instrument. This may be a software version different from the presently available software version, which may require a software update that the user does not wish to receive.

[0060] A second aspect of the present disclosure pertains to a computing device configured to implement the method according to the first aspect of the present disclosure. In particular, the computing device is a server which e.g., provides a cloud a laboratory instrument. All of the features, functions and advantages of the method as described herein are also applicable to the computing device and vice versa.

[0061] A third aspect of the present disclosure pertains to a computer program, which, when executed by a computing device, instructs the computing device to perform steps of the method according to the first aspect of the present disclosure. All of the features, functions and advantages of the method or the computing device as described herein are also applicable to the computer program and vice versa.

[0062] A fourth aspect of the present disclosure pertains to a computer-implemented method. Said method may be a method of managing at least one laboratory instrument and / or managing a software update by at least one laboratory instrument. The method according to the fourth aspect of the present disclosure comprises: obtaining, e.g., receiving, by the laboratory instrument, a pause command provided by a computing device, wherein the pause command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to prevent installation of the software update on the laboratory instrument; and obtaining, e.g., receiving, by the laboratory instrument, a resolution command provided by the computing device, wherein the resolution command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out a resolution action, the resolution action being one or more of the action of allowing installation of the software update, the action of replacing the software update by an updated version, and the action of permanently preventing installation of the software update on the laboratory instrument. Obtaining the pause command may comprise receiving, by the laboratory instrument, the pause command. Obtaining the resolution command may comprise receiving, by the laboratory instrument, the resolution command. The method may comprise processing, by the laboratory instrument, the pause command and / or the resolution command provided by the computing device. In particular, the method according to the fourth aspect of the present disclosure corresponds to the method according to the first aspect of the present disclosure method but describes the process from the side of the laboratory instrument. Therefore, all of the features, functions and advantages described herein for the method performed by the computing device are also applicable to the method performed by the laboratory instrument and vice versa. To avoid repetitions, reference is therefore made to the respective other method as described herein and steps and aspects that are similar to steps and aspects already described herein are not repeated. Processing a command by the laboratory instrument may comprise accessing the information comprised in the command, interpreting said information and, based on said information, causing the respective action to be carried out. If the command comprises computer executable instructions, processing a command by the laboratory instrument may comprise executing said instructions. In particular, processing the pause command by the laboratory instrument may comprise determining, by using at least a portion of the information comprised in the command, whether each condition of the first set of conditions is met and, in the positive, causing the pause action to be carried out. Processing the resolution command by the laboratory instrument may comprise determining, by using at least a portion of the information comprised in the command, whether each condition of the second set of conditions is met and, in the positive, causing the resolution action to be carried out. Processing may comprise any combination of decoding, translating, running and implementing.

[0063] The method may comprise obtaining, by the laboratory instrument, the software update from the computing device. For example, the laboratory instrument may download the software update from the computing device, e.g., from the cloud service provided by the computing device. The method according to the fourth aspect of the present invention may comprise storing, by the laboratory instrument, the software update in a memory or a storage of the laboratory instrument. The laboratory instrument may download and store the software update locally in the memory without immediately installing the software update. For example, in the time interval between the obtaining of the software update and installing the software update, the laboratory instrument may receive and / or process the pause command from the computing device, thereby preventing possible undesired effects of the software update on the laboratory instrument. After obtaining, e.g., receiving the resolution command, the method may comprise, in reaction of the obtaining of the resolution command and / or based on the resolution command, carrying out the resolution action. In particular, the method may comprise installing the software update on the laboratory instrument or replacing the software update by an updated version or permanently preventing the installation of the software update on the laboratory instrument based on the resolution command. Which one of these resolutions is implemented may be indicated in the resolution command.

[0064] The method may comprise determining, by the laboratory instrument, whether a first set of conditions are fulfilled; and, when each condition of the first set of conditions is fulfilled, processing, by the laboratory instrument, the pause command provided by the computing device. For example, the laboratory instrument may check whether or not the first set of conditions is fulfilled. Further processing of the pause command may then depend on whether or not this check is positive or not, i.e. the first set of conditions is fulfilled or not. This way, it is guaranteed that a sequence of events is correct and that the installation of the software update is only halted on laboratory instruments which may be affected by the undesired effects.

[0065] The first set of conditions may comprise one or more conditions. For example, the first set of conditions may comprise the condition that the software update has not yet been installed on the laboratory instrument. This may prevent errors from happening when the processing of the pause command tries to prevent installation of an already installed software update. The first set of conditions may additionally or alternatively comprise the condition that the software update has been obtained, for example downloaded, by the laboratory instrument. This may prevent errors from happening when the processing of the pause command tries to prevent installation of a software update which has not yet been obtained.

[0066] The method may comprise obtaining, by the laboratory instrument, an instrument identifier from the computing device, wherein the instrument identifier is indicative of which laboratory instrument or which type of laboratory instrument is addressed by the pause command, and wherein the first set of conditions comprises the condition that the laboratory instrument is indicated or is of a type indicated by the instrument identifier. As explained above, the instrument identifier may be comprised in the pause command. Also as explained herein, the instrument identifier may comprise information specifying at least one of software version, instrument version, instrument build number, and geographical location of the laboratory instrument. The first set of conditions may also comprise at least one of software version, instrument version, instrument build number, and geographical location of the laboratory instrument as a condition, meaning that the respective aspect of the of the laboratory instrument has to be similar to the aspect indicated by the condition for the condition to be fulfilled. The method may further comprise determining, by the laboratory instrument, whether a second set of conditions are fulfilled; and, when each condition of the second set of conditions is fulfilled, processing, by the laboratory instrument, the resolution command provided by the computing device. For example, the laboratory instrument may check whether or not the second set of conditions is fulfilled. Further processing of the resolution command may then depend on whether or not this check is positive, i.e. the second set of conditions is fulfilled or not.

[0067] The second set of conditions may comprise one or more conditions. For example, the second set of conditions may comprise one or more of: the condition that the installation of the software update is at least temporarily prevented and the condition that the software update has not yet been installed on the laboratory instrument. In particular, the second set of conditions may comprise the condition that the pause command has been processed and / or taken effect on the laboratory instrument.

[0068] On the laboratory instrument side, the method may comprise generating a first log message on the laboratory instrument, wherein the first log message is indicative of successful or unsuccessful receipt and / or download of the software update by the laboratory instrument. The method may further comprise generating a second log message on the laboratory instrument, wherein the second log message is indicative of successful or unsuccessful prevention of the installation of the software update on the laboratory instrument. The method may further comprise generating a third log message on the laboratory instrument, wherein the third log message is indicative of whether the resolution action has been successful or unsuccessful. In particular, the third log message may be indicative of a) successful or unsuccessful installation of the software update, b) successful or unsuccessful replacement of the software update, or c) successful or unsuccessful permanent prevention of the installation of the software update on the laboratory instrument.

[0069] The laboratory instrument may be configured to provide, e.g., transmit and / or send, the first log message and / or the second log message and / or the third log message to the computing device. Alternatively or additionally, the method may further comprise providing, e.g., transmitting and / or sending the first log message and / or the second log message and / or the third log message to the computing device. In particular, the log messages may be actively pushed to the computing device from and by the laboratory instrument. Alternatively, the log messages may also be made available by the laboratory instrument to the computing device. In this case, it may be provided that the computing device is configured to regularly check for log messages on the laboratory instrument. In case any one of the first log message, the second log message and the third log message indicates an unsuccessful process, the laboratory device may be configured to notify a provider of the computing device and / or a user of the laboratory instrument. This may be achieved, for example, by providing and / or outputting an error message. To be able to more closely describe the problem, the notification may comprise information specifying why the respective process was unsuccessful. The notification may be transmitted or sent to the computing device. The notification focuses attention on laboratory instruments experiencing some kind of malfunction of the presently disclosed method, which are therefore especially prone to errors and possible downtimes. The notification therefore serves to ensure correct performance of the method and enables a user to intervene when necessary. In particular, the first log message indicates an unsuccessful process when the first log message indicates an unsuccessful receipt and / or download of the software update by the laboratory instrument. Exemplarily, the second log message indicates an unsuccessful process when the second log message indicates an unsuccessful prevention of the installation of the software update on the laboratory instrument. For instance, the third log message indicates an unsuccessful process when the third log message indicates that the carrying out of the resolution action has been unsuccessful, i.e., depending on the resolution action, an unsuccessful installation, replacement, or permanent prevention of the installation of the software update on the laboratory instrument.

[0070] The method according to the fourth aspect of the present disclosure may comprise obtaining, e.g., receiving, by the laboratory instrument, a schedule and / or an initiation command for the obtaining of the software update from the computing device. Said method may further comprise obtaining, e.g., receiving, by the laboratory instrument, a schedule and / or an initiation command for the resolution action. In particular, the schedule and / or the initiation command may be for any one of the obtaining, the installation, the replacement and the permanent prevention of the installation of the software update from the computing device or from a user of the laboratory instrument. Exemplarily, the method may further comprise obtaining, e.g., receiving, by the laboratory instrument, a schedule and / or an initiation command for the pause action. While these steps may therefore be controlled by the computing device, it is also possible that the user of the laboratory instrument controls, i.e. schedules and / or initiates, them.

[0071] For example, the resolution command may comprise the schedule and / or an initiation command for the resolution action. For instance, the pause command may comprise the schedule and / or an initiation command for the resolution action. The method may further comprise outputting, e.g., displaying, by the laboratory instrument and in reaction of a user-initiated attempt to install the software update, an explanatory notice indicating that installation of the software update is currently prevented. As discussed above, outputting the explanatory notice may be performed whenever a user tries to initiate installation of the software update on the laboratory instrument. In particular, outputting the explanatory notice is performed whenever a user tries to initiate installation of the software update on the laboratory instrument in a time point within a time interval after the pause action has been carried out by the laboratory instrument. In particular, said time interval is before the resolution action has been carried out by the laboratory instrument. Moreover, in this case, the method according to the fourth aspect of the present invention may comprise blocking, preventing or ignoring the attempt of the user to initiate the installation of the software update, e.g., to make sure that the software update is not installed after the pause command has reached the laboratory instrument and before the resolution command has been received by the laboratory instrument.

[0072] The method according to the fourth aspect of the present invention may comprise obtaining, e.g., receiving, by the laboratory instrument, a message from the computing device indicating that a software update is available for the laboratory instrument. The message may be output, e.g., displayed to the user of the laboratory instrument, or the message may be used to trigger the obtaining the software update by the laboratory instrument, for example downloading the software update from the computing device.

[0073] The method may further comprise obtaining, by the laboratory instrument, information from a status repository of the laboratory instrument retained on the computing device, and obtaining, by the laboratory instrument, the software update from the computing device when information from the status repository of the laboratory instrument indicates that the software update is available for the laboratory instrument. The method may comprise, in particular, downloading, by the laboratory instrument, a software update from the computing device when information about the laboratory instrument stored in the status repository indicates that an updated software version is available for the laboratory instrument. To determine whether a software update is available for the laboratory instrument, a comparison between the current software version installed on the laboratory instrument and the available software version on the computing device and / or the desired software version for the laboratory instrument may be used.

[0074] The method may also comprise updating the information about the laboratory instrument stored in the status repository with updated information, the updated information comprising the current software version installed on the laboratory instrument and / or a desired software version as indicated by a user of the laboratory instrument.

[0075] A fifth aspect of the present disclosure pertains to a laboratory instrument running a software application, the laboratory instrument being configured to implement the method according to the fourth aspect of the present disclosure. All of the features, functions and advantages of the method as described herein are also applicable to the laboratory instrument and vice versa.

[0076] A sixth aspect of the present disclosure pertains to a computer program, which, when executed by a laboratory instrument, instructs the laboratory instrument to perform steps of the method according to the fourth aspect of the present disclosure. All of the features, functions and advantages of the method or the laboratory instrument as described herein are also applicable to the computer program and vice versa.

[0077] Another aspect of the present disclosure pertains to a computer-readable medium, for instance a non-volatile computer-readable medium, having stored thereon one or more of the computer programs according to the explanations herein. All of the features, functions and advantages of the computer programs or methods as described herein are also applicable to the computer-readable medium and vice versa.

[0078] Another aspect of the present disclosure pertains to a laboratory instrument servicing system, comprising at least one computing device providing a cloud service and at least one laboratory instrument, for example a computing device and / or a laboratory instrument according to the explanations herein, wherein the servicing system is configured to implement any one of the methods according to the explanations herein. All of the features, functions and advantages of the computing device, the laboratory instrument, or the methods as described herein are also applicable to the laboratory instrument servicing system and vice versa.

[0079] BRIEF DESCRIPTION OF THE DRAWINGS

[0080] The accompanying drawings described herein are only used for illustrating the selected embodiments rather than all possible embodiments, and are not intended to limit the scope of the present disclosure.

[0081] Figure 1 shows a schematic representation of a laboratory instrument servicing system.

[0082] Figure 2 shows a flowchart of a method of the present disclosure, performable by a computing device. Figure 3 shows a flowchart of a method of the present disclosure, performable by a laboratory instrument.

[0083] DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

[0084] Exemplary embodiments according to the present disclosure will now be more fully described with reference to the accompanying drawings.

[0085] Exemplary embodiments are provided such that the present disclosure will be thorough and will fully convey the scope of the present disclosure to those skilled in the art. Examples of many specific details such as specific components, devices and methods are described to provide a thorough understanding of embodiments of the present disclosure. It is apparent to those skilled in the art that the exemplary embodiments may be implemented in many different forms without specific details and should not be construed as limitation to the scope of the present disclosure. In some exemplary embodiments, the well-known methods, well-known device structures, and well-known techniques will not be described in detail.

[0086] Figure 1 shows a schematic representation of a laboratory instrument servicing system 36. The system 36 or components of the system 36 may be used to perform one or more of the methods of the present disclosure. The laboratory instrument servicing system 36 may comprise at least one laboratory instrument 1 and at least one computing device 2. The laboratory instrument 1 may be arranged remotely from the computing device 2 and may, for example, be arranged in a laboratory and may be used for medical, chemical and / or biochemical testing, for example for semi-automatic or automatic testing of a large number of samples. The laboratory instrument 1 may comprise a controller 4, which may be or which may comprise a processing unit like a CPU, MCU etc., and a storage 5, for example a data storage or memory. In particular, the laboratory instrument 1 , e.g., its controller 4, is configured to carry out the method according to the fourth aspect of the present disclosure. The computing device 2 may provide an online service or cloud service 3 through which a data connection 6 may be established between the at least one computing device 2 and the at least one laboratory instrument 1. The data connection 6 may, for example, be an internet connection and may enable transmission of data from the computing device 2 to the laboratory instrument 1 and / or from the laboratory instrument 1 to the computing device 2. Although only one laboratory instrument 1 is shown in figure 1 , the computing device 2 may be communicatively couplable and / or in data connection with a plurality of laboratory instruments 1. In particular, the computing device is configured to carry out the method according to the first aspect of the present disclosure. Therefore, in particular, the computing device 2 may be used to manage the software updates of a plurality of laboratory instruments 1.

[0087] To perform its tasks in the laboratory, the laboratory instrument 1 may be running a software application, for example on the controller 4. The computer program or computer program code of the software application may be stored in storage 5. To keep an overview of the status of the laboratory instrument 1, and in particular of all of the laboratory instruments 1 being managed by the computing device 2, the computing device 2 may maintain a status repository 35, which may be part of the cloud service 3. The status repository 35 may comprise a device twin or a digital twin of the respective laboratory instrument 1. Therefore, for example, the status repository 35 may comprise information about the software version currently running on the laboratory instrument 1. The status repository 35 may also comprise information about whether or not an updated version of the software is available for the respective laboratory instrument 1.

[0088] From time to time, it may be desirable and / or needed to update the software running on the laboratory instrument 1. As will be outlined in more detail below, for this purpose, there may be provided a software update for the laboratory instrument 1 on the computing device 2. The software update may be provided, e.g., transmitted, to the laboratory instrument 1 through the data connection 6. It may be stored in storage 5. As the work schedule of laboratory instruments 1 is usually very tight and as the actual installation of the software update may cause a temporary downtime of the laboratory instrument 1 , the software update may be stored on the laboratory instrument 1 without being immediately installed. Typically, the actual installation of the software update may be scheduled for a moment in which a pause in the workflow of the laboratory instrument 1 best fits its operation and / or the user(s) of the laboratory instrument 1. Therefore, a software update which may be applicable to a plurality of laboratory instruments 1 may not be simultaneously installed on all of the eligible laboratory instruments 1. In fact, there may be substantial time intervals between the installation of the software update on different laboratory instruments 1, for example days, weeks or months. In case a software update results in undesired effects after the installation on the laboratory instrument 1, information about the occurrence of the undesired effects may therefore be available before the software update has been installed on all of the laboratory instruments 1 managed by the computing device 2. It may therefore be advantageous to stop the installation of the software update on the laboratory instruments 1 until a resolution of the problem has been found. However, as a plurality of laboratory instruments 1 may already have obtained and / or stored the software update, albeit without having installed it, it is insufficient to only stop providing the software update on the computing device 2.

[0089] To address this problem, method 7 according to figure 2 is provided. Method 7 may be performed by the computing device 2 and / or the laboratory instrument servicing system 36. Method 7 may start with providing a pause command 10. The pause command may be provided by the computing device 2, for example through the cloud service 3, and may be provided, e.g., distributed / transmitted to the laboratory instruments 1, for example by sending the pause command from the computing device 2 to the laboratory instrument 1 , or by downloading the pause command from the computing device 2 to the laboratory instrument 1. For example, the pause command may be sent out to all the laboratory instruments 1 whose software updates are managed by the computing device 2 in a broadcast manner. The laboratory instrument 1 may receive the pause command, and the pause command may have the effect on the laboratory instrument 1 that installation of the software update is at least temporarily prevented. For this, the laboratory instrument 1 may process the pause command, which may cause and / or instruct the laboratory instrument 1 to implement the effect of the pause command. The pause command may comprise an instrument identifier which indicates which laboratory instruments 1 are eligible for the pause command. The laboratory instruments 1 receiving the pause command may check the instrument identifier, and only eligible laboratory instruments 1 may implement the effects of the pause command. As an alternative to postponing installation of the software update indefinitely, the pause command may also comprise a time period for which installation of the software update is prevented, for example one or more days, one or more weeks, or one or more months. A resolution for the underlying problem may therefore be found in this time period. By providing this pause command, installation of the software update on the laboratory instrument 1 may be prevented, at least temporarily, so that the undesired effect may also be circumvented.

[0090] Method 7 may continue by providing a resolution command 12. The resolution command is similarly provided, e.g., distributed / transmitted, for example broadcast, to the laboratory instruments 1 as the pause command. The resolution command is configured to, when processed by the laboratory instrument 1, cause and / or instruct the laboratory instrument to carry out a resolution action. In particular, the resolution action is one of: (i) the action of allowing installation of the software update, (ii) the action of replacing the software update by an updated version, and (iii) the action of permanently preventing installation of the software update on the laboratory instrument. In particular, depending on whether or not there actually may have been a problem with the software update causing undesired effects or depending on the manner by which the problem may have been resolved, the resolution command may be configured to have different effects. In particular, the resolution command may cause and / or instruct the laboratory instrument 1 to allow the installation of the software update. This may be advantageous, for example, when it has been determined that there actually were no undesired effects, for example at least for the specific laboratory instrument 1 the resolution command may be aimed at, or when the undesired effects are determined to be negligible, or when the desired effects of the software update sufficiently outweigh the undesired effects. Alternatively, the resolution command may cause and / or instruct the laboratory instrument 1 to replace the software update by an updated version. In particular, there may be provided an updated version of the software update on the computing device 2, and the laboratory instrument 1 may be instructed to obtain the updated version and install the updated version instead of the original software update. In another alternative, the resolution command may cause and / or instruct the laboratory instrument 1 to permanently prevent the installation of the software update on the laboratory instrument 1. In this case, in particular, it may have been determined that the best course of action is to at least temporarily keep the current software version as already installed on the laboratory instrument 1. It is noted that the computing device 2, through the resolution command, enables the laboratory instrument 1 to allow installation of the software update or to replace the software update or to permanently prevent the installation of the software update. While the actual installation of the software update or the replacement of the software update or the permanent prevention of the installation of the software update are implemented on the laboratory instrument 1, the resolution command may comprise respective instructions to enable the laboratory instrument 1 to do so. By having the computation device 2 provide the resolution command (and also the pause command), the computation device 2 may therefore perform all the steps of the method 7 by itself when seen from the perspective of the computation device 2. By taking the described measures, undesired effects of a software update may be prevented on a plurality of laboratory instruments 1, thereby keeping their workflow uninterrupted and preventing unnecessary downtime.

[0091] In addition to the above-mentioned steps 10 and 12, method 7 may comprise one or more additional, optional steps, each optional step being schematically illustrated by a respective box with a dashed line in figure 2. For example, prior to step 10, method 7 may comprise providing the software update 8 on the computing device 2. For example, the software update may be transmitted to the laboratory instrument 1 through the cloud service 3, for example either by actively sending the software update to the laboratory instrument 1 or through accessing the cloud service 3 by the laboratory instrument 1 and downloading the software update. Therefore, providing the software update 8 may comprise actively sending the software update to the laboratory instrument 1 or making the software update available for download by the laboratory instrument 1. Without the optional step 8, the software update may be provided to the laboratory instrument 1 through other means, for example by providing the software update on a computer-readable medium.

[0092] As another optional step before step 10, method 7 may comprise obtaining, e.g., receiving, by the computing device 2, an indication about the software update possibly having an undesired effect 9 on the laboratory instruments 1 after installation. The software update to which the indication about an undesired effect pertains may be the software update provided by the computing device 2 in step 8. This indication received in step 9 may be used as a trigger for the computing device 2 to provide the pause command in step 10. Without the optional step 9, provision of the pause command in step 10 may be triggered through other means, for example manually.

[0093] Between steps 10 and 12, method 7 may comprise obtaining, e.g., receiving, by the computing device 2, an indication about a resolution of the problem underlying the undesired effect 11 of the software update on the laboratory instrument 1. For example, it may have been determined that the undesired effect is non-existent or negligible, or an updated version of the software update may be provided or it may have been determined that the best course of action is to permanently prevent the installation of the software update. The indication about a resolution may therefore be used as a trigger for the computing device 2 to provide the resolution command in step 12. Without the optional step 1 1, provision of the resolution command in step 12 may be triggered through other means, for example manually.

[0094] After step 8, method 7 may comprise receiving, by the computing device 2, a first log message 16. The first log message may be provided by the laboratory instrument 1 and may indicate whether or not the software update was successfully obtained by the laboratory instrument 1. The receipt of the first log message and its contents may be used by the computing device 2 to update the status repository 35.

[0095] After step 10, method 7 may comprise receiving, by the computing device 2, a second log message 17. The second log message may be provided by the laboratory instrument 1 and may indicate whether or not the installation of the software update was successfully prevented, at least temporarily, through the pause command. The receipt of the second log message and its contents may be used by the computing device 2 to update the status repository 35.

[0096] After step 12, method 7 may comprise receiving, by the computing device 2, a third log message 18. The third log message may be provided by the laboratory instrument 1 and may indicate whether or not the installation of the software update was successfully completed or whether or not the software update was successfully replaced by an updated version or whether or not the installation of the software update was successfully permanently prevented. The receipt of the third log message and its contents may be used by the computing device 2 to update the status repository 35.

[0097] An additional or alternative method 22 for addressing the above-mentioned problem is shown in figure 3. The method 22 may be performed by the laboratory instrument 1 and / or the laboratory instrament servicing system 36. In general, method 22 may complement method 7, performed by the computing device 2, from the side of the laboratory instrument 1. Both method 7 and method 22 may be performed together by the laboratory instrument servicing system 36. Many of the features of method 22 may therefore be similar or complementary to the features of method 7. The features of the steps of method 7 are therefore analogously applicable to method 22 and vice versa.

[0098] Method 22 may start with obtaining, e.g., receiving, a pause command 26. The pause command may be received by the laboratory instrument 1, for example from the computing device 2, for example through the cloud service 3. For example, the laboratory instrument 1 may receive the pause command sent by the computing device 2 to the laboratory instrument

[0099] 1 , or the laboratory instrument 1 may download the pause command from the computing device

[0100] 2, for example from the cloud service 3. The processing and the effect of the pause command on the side of the laboratory instrument 1 have already been described, so that reference is made to these previous explanations to avoid repetitions.

[0101] Method 22 may continue by obtaining, e.g., receiving, a resolution command 28. The resolution command is similarly distributed / transmitted, for example broadcast, to the laboratory instruments 1 as the pause command. The resolution command is configured to, when processed by the laboratory instrument 1, cause and / or instruct the laboratory instrument to carry out a resolution action 39. In particular, the resolution action is one of: (i) the action of allowing installation of the software update, (ii) the action of replacing the software update by an updated version, and (iii) the action of permanently preventing installation of the software update on the laboratory instrument. At step 39, the laboratory instrument 1 carries out the resolution action. Hence, the resolution command may be configured to have different effects at the laboratory instrument 1. In particular, the laboratory instrument 1 may carry out the action of allowing the installation of the software update in response to receiving the resolution command. Alternatively, the laboratory instrument 1 may carry out the action of replacing the software update by an updated version in response to receiving the resolution command. In another alternative, the laboratory instrument 1 may carry out the action of preventing the installation of the software update in response to receiving the resolution command. It is noted that the laboratory instrument 1 , through the resolution command, is instructed and / or caused to allow installation of the software update or to replace the software update or to permanently prevent the installation of the software update. While the commands, i.e., the pause command and the resolution command, originate from outside the laboratory instrument, installation of the software update or the replacement of the software update or the permanent prevention of the installation of the software update are implemented on the laboratory instrument 1 itself. When seen from the perspective of the laboratory instrument 1 , the laboratory instrument 1 may therefore perform all the steps of the method 22 by itself in response to receiving the respective commands.

[0102] In addition to the above-mentioned steps 26, 28 and 39 method 22 may comprise one or more additional, optional steps, each optional step being schematically illustrated by a respective box with a dashed line in figure 3. For example, prior to step 26, method 22 may comprise obtaining the software update 23 on the laboratory instrument 1. Details have already been outlined above for step 8 of method 7, to which reference is made.

[0103] As another optional step before step 26, method 22 may comprise storing the software update 24 on the laboratory instrument 1, for example in storage 5. The laboratory instrument 1 may store the software update, e.g., the program code necessary for updating the software running on the laboratory instrument 1, without immediately installing the software update. Instead, the software update may be scheduled to be installed later at a time conveniently fitting into the work schedule of the operator of the laboratory instrument 1. Between downloading and installing the software update, a substantial period of time may pass, for example days, weeks or months.

[0104] Optionally, method 22 may comprise obtaining, e.g., receiving, by the laboratory instrument 1, a schedule command or an initiation command 25, wherein the schedule command or the initiation command may be obtained from the computing device 2. The schedule command or the initiation command may comprise instructions on when the software update is to be installed on the laboratory instrument 1. For example, the schedule command or the initiation command may comprise a period of time after which or a point of time at which an installation of the software update on the laboratory instrument 1 is forced.

[0105] After step 26, in which the pause command is obtained by the laboratory instrument 1, method 22 may comprise generating an explanatory notice in response to a user of the laboratory instrument 1 trying to install the software update 27. Step 27 may comprise outputting, e.g., displaying an explanatory notice informing the user that a pause command pertaining to the software update has been received by the laboratory instrument 1 and that therefore the installation of the software update on the laboratory instrument 1 is currently prevented. In particular, the explanatory notice is output, e.g., displayed every time the user tries to install the software update. Exemplarily, the explanatory notice is in particular output whenever a user tries to initiate installation of the software update on the laboratory instrument in a time point within a time interval after the pause action has been carried out by the laboratory instrument. In particular said time interval is before the resolution action has been carried out by the laboratory instrument. Alternatively, the user may be given the option to override the pause command in case the user decides to accept or ignore the possibility of undesired effects caused by the software update.

[0106] After step 23, method 22 may comprise generating, by the laboratory instrument 1, a first log message 32. The first log message may be provided by the laboratory instrument 1 and may be sent to the computing device 2. It may indicate whether or not the software update was successfully obtained by the laboratory instrument 1.

[0107] After step 26, method 22 may comprise generating, by the laboratory instrument 1, a second log message 33. The second log message may be provided by the laboratory instrument 1 and may be sent to the computing device 2. It may indicate whether or not the installation of the software update was successfully prevented, at least temporarily, through the pause command.

[0108] After step 39, the method 22 may comprise generating, by the laboratory instrument 1 , a third log message 34. The third log message may be provided by the laboratory instrument 1 and may be sent to the computing device 2. It may indicate whether or not the carrying out the resolution action has been successful or not. In particular, depending on the resolution action, the third log message may indicate: (i) whether or not the installation of the software update was successfully completed, (ii) whether or not the software update was successfully replaced by an updated version, or (iii) whether or not the installation of the software update was successfully permanently prevented.

[0109] Further, the methods 7, 22 may comprise notifying a user of the information comprised by any of the first, second and third log message. In the case of method 22, this may be performed after generating one of the first, second and / or third log messages at the laboratory instrument 1. In the case of method 7, this may be performed after receiving one of these log messages at the computing device 2. The user may be a user of the computing device 2, for example an employee of the manufacturer of the laboratory instruments 1 providing the software updates, or a user or operator of the laboratory instrument 1. Thus, the user may be informed about whether or not the software update was successfully obtained by the laboratory instrument 1 , about whether or not the installation of the software update was successfully at least temporarily prevented by the pause command, and about whether or not the carrying out of the resolution action was successful or not.

[0110] The information carried in the first, the second, and / or the third log message may also be used for updating the status repository 35. In this way, the device twin or digital twin of the laboratory instrument 1 stored in the status repository 35 always contains up-to-date information about the status of the laboratory instrument 1, which allows the computing device 2 to effectively manage the laboratory instrument 1.

[0111] Prior to any of the steps explained above, the methods 7, 22 may comprise receiving an indication about a user input, for example a user input of the user of the laboratory instrument 1. The indication may be received at the very beginning of the methods 7, 22, for example. The user input may be received by the laboratory instrument 1 and / or the computing device 2. The user input may, for example, be transmitted from the laboratory instrument 1 to the computing device 2. Alternatively, the user input may trigger the generation of a message which is then sent to the computing device 2. In both cases, the computing device 2 receives an indication about the user input. The user input may comprise information about whether or not the user wishes to install or receive the software update on the laboratory instrument 1. In this way, for example, the user input may define whether are not the laboratory instrument 1 is eligible for the software update. If the user does not wish to receive the software update, this information may be stored in the status repository 35, so that the software update is not even transmitted to, e.g., downloaded by, the laboratory instrument 1.

[0112] In summary, the present disclosure provides systems and methods to advantageously prevent undesired effects of software updates on a plurality of laboratory instruments 1 managed by a computing device 2. In this way, unnecessary downtime can be prevented and the working efficiency of the laboratory instrument 1 is increased.

Claims

CLAIMS1. A computer-implemented method comprising:- providing, by a computing device, a pause command to at least one laboratory instrument, the laboratory instrument being communicatively coupled with the computing device, wherein the pause command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to at least temporarily prevent installation of the software update on the laboratory instrument; and- providing, by the computing device, a resolution command to the at least one laboratory instrument, wherein the resolution command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry out a resolution action, the resolution action being one of: the action of allowing installation of the software update, the action of replacing the software update by an updated version, and the action of permanently preventing installation of the software update on the laboratory instrument.

2. The method according to claim 1, further comprising: obtaining, by the computing device, the software update for download by the laboratory instrument, in particular comprising providing, by the computing device, the software update to the laboratory instrument.

3. The method according to any one of the previous claims, wherein providing the pause command comprises transmitting and / or sending the pause command from the computing device to the laboratory instrument; and / or providing the resolution command comprises transmitting and / or sending the resolution command from the computing device to the laboratory instrument.

4. The method according to any one of the previous claims, further comprising, prior to providing the pause command: obtaining, by the computing device, an indication that the software update may have an undesired effect when installed by the laboratory instrument; and, optionally, further comprising, prior to providing the resolution command: obtaining, by the computing device, an indication that the undesired effect does not exist or an indication of a resolution of the undesired effect by either one of replacing the softwareupdate by an updated version, or permanently preventing installation of the software update on the laboratory instrument.

5. The method according to any one of the previous claims, wherein the installation of the software update is at least temporarily prevented only when each condition of a first set of conditions is fulfilled, wherein the first set of conditions comprises the condition that the software update has not yet been installed on the laboratory instrument.

6. The method according to any one of the previous claims, further comprising: providing, by the computing device, an instrument identifier to the laboratory instrument, wherein the instrument identifier is indicative of which laboratory instrument or which type of laboratory instrument is addressed by the pause command, and the installation of the software update is at least temporarily prevented only when each condition of a first set of conditions is fulfilled and wherein the first set of conditions comprises the condition that the laboratory instrument is indicated or is of a type indicated by the instrument identifier.

7. The method according to the previous claim, wherein the instrument identifier comprises information indicative of at least one of software version, instrument version, instrument build number, and geographical location of the laboratory instrument.

8. The method according to any one of the previous claims, wherein the resolution action is carry out only when each condition of a second set of conditions is fulfilled wherein the second set of conditions comprises one or more of: the condition that the installation of the software update is at least temporarily prevented and the condition that the software update has not yet been installed on the laboratory instrument.

9. The method according to any one of the previous claims, further comprising: obtaining, by the computing device, a first log message provided by the laboratory instrument, wherein the first log message is indicative of successful or unsuccessful download of the software update at the laboratory instrument.

10. The method according to any one of the previous claims, further comprising: obtaining, by the computing device, a second log message provided by the laboratory instrument, wherein the second log message is indicative of successful or unsuccessful prevention of the installation of the software update.

11. The method according to any one of the previous claims, further comprising: obtaining, by the computing device, a third log message provided by the laboratory instrument, wherein the third log message is indicative of whether the carrying out of the resolution action has been successful or unsuccessful.

12. The method according to any one of the preceding claims, further comprising one or more of: causing, by the computing device, the laboratory instrument to obtain the software update; and causing, by the computing device, the laboratory instrument to obtain the updated version.

13. The method according to any one of the preceding claims, further comprising one or more of: remotely scheduling, by the computing device, the obtaining of the software update by the laboratory instrument; and remotely scheduling, by the computing device, the obtaining of the updated version by the laboratory instrument.

14. The method according to any one of the previous claims, wherein the pause command is configured to cause an explanatory notice to be outputted the laboratory instrument, the explanatory notice indicating that installation of the software update is currently prevented, wherein the explanatory notice is optionally output whenever a user tries to initiate installation of the software update on the laboratory instrument.

15. The method according to any one of the previous claims, further comprising: providing, by the computing device, a message to the laboratory instrument and / or a user of the laboratory instrument whenever a software update is available for the laboratory instrument.

16. The method according to any one of the previous claims, further comprising: retaining, on the computing device, a status repository of the laboratory instrument, wherein the status repository comprises information about the laboratory instrument, wherein the information about the laboratory instrument comprises at least information indicative of the current software version installed on the laboratory instrument and information indicative of the most recent software version available for the laboratory instrument.

17. The method according to the previous claim, further comprising: obtaining, by the computing device, an indication of a user input by a user of the laboratory instrument, the user input being indicative of whether or not the user wishes to install the software update on the laboratory instrument; and updating the information about the laboratory instrument in the status repository based on the indication.

18. A computer-implemented method comprising:- obtaining, by a laboratory instrument, a pause command provided by a computing device, the computing device being communicatively coupled with the computing device, wherein the pause command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to prevent installation of the software update on the laboratory instrument; and- obtaining, by the laboratory instrument, a resolution command provided by the computing device, wherein the resolution command is configured to, when processed by the laboratory instrument, cause and / or instruct the laboratory instrument to carry put a resolution action, the resolution action being one of: the action of allowing installation of the software update, the action of replacing the software update by an updated version, and the action of permanently preventing installation of the software update on the laboratory instrument.

19. The method according to the previous claim, further comprising one or more of:- obtaining, by the laboratory instrument, the software update from the computing device;- storing, by the laboratory instrument, the software update in a memory of the laboratory instrument;- in reaction of the obtaining of the resolution command and based on the resolution command, carrying out the resolution action.

20. The method according to the any one of the claims 18-19, further comprising processing, by the laboratory instrument, the pause command provided by the computing device.

21. The method according to the any one of the claims 18-20, further comprising: determining, by the laboratory instrument, whether a first set of conditions are fulfilled; and, when each condition of the first set of conditions is fulfilled, processing, by the laboratory instrument, the pause command provided by the computing device.

22. The method according to the previous claim, wherein the first set of condition comprises the condition that the software update has not yet been installed on the laboratory instrument.

23. The method according to any one of claims 21-22, further comprising: obtaining, by the laboratory instrument, an instrument identifier from the computing device, wherein the instrument identifier is indicative of which laboratory instrument or which type of laboratory instrument is addressed by the pause command, and wherein the first set of conditions comprises the condition that the laboratory instrument is indicated or is of a type indicated by the instrument identifier.

24. The method according to the previous claim, wherein the instrument identifier comprises information specifying at least one of software version, instrument version, instrument build number, and geographical location of the laboratory instrument.

25. The method according to the any one of the claims 18-24, further comprising: determining, by the laboratory instrument, whether a second set of conditions are fulfilled; and, when each condition of the second set of conditions is fulfilled, processing, by the laboratory instrument, the resolution command provided by the computing device.

26. The method according to the preceding claim, wherein the second set of conditions comprises one or more of: the condition that the installation of the software update is at least temporarily prevented and the condition that the software update has not yet been installed on the laboratory instrument.

27. The method according to any one of claims 18-26, further comprising: generating a first log message on the laboratory instrument, wherein the first log message isindicative of successful or unsuccessful receipt and / or download of the software update by the laboratory instrument.

28. The method according to any one of claims 18-26, further comprising: generating a second log message on the laboratory instrument, wherein the second log message is indicative of successful or unsuccessful prevention of the installation of the software update on the laboratory instrument.

29. The method according to any one of claims 18-28, further comprising: generating a third log message on the laboratory instrument, wherein the third log message is indicative of whether the resolution action has been successful or unsuccessful.

30. The method according to any one of claims 18-29, further comprising one or more of: obtaining, by the laboratory instrument, a schedule and / or an initiation command for the obtaining of the software from the computing device; obtaining, by the laboratory instrument, a schedule and / or an initiation command for the updated version from the computing device.

31. The method according to any one of claims 18-30, further comprising: outputting, by the laboratory instrument and in reaction of a user-initiated attempt to install the software update, an explanatory notice indicating that installation of the software update is currently prevented.

32. The method according to any one of claims 18-31 , further comprising: obtaining, by the laboratory instrument, a message from the computing device indicating that the software update is available for the laboratory instrument.

33. The method according to any one of claims 18-32, further comprising: obtaining, by the laboratory instrument, information from a status repository of the laboratory instrument retained on the computing device, and obtaining, by the laboratory instrument, the software update from the computing device when information from the status repository of the laboratory instrument indicates that the software update version is available for the laboratory instrument.

34. The method according to the previous claim, further comprising:updating the information about the laboratory instrument stored in the status repository with updated information, the updated information comprising the current software version installed on the laboratory instrument.

35. A computing device, in particular a server, configured to implement the method according to any one of claims 1-17.

36. A computer program, which, when executed by a computing device, instructs the computing device to perform steps of the method according to any one of claims 1-17.

37. A laboratory instrument running a software application, the laboratory instrument being configured to implement the method according to any one of claims 18-34.

38. A computer program, which, when executed by a laboratory instrument, instructs the laboratory instrument to perform steps of the method according to any one of claims 18-34.

39. A computer-readable medium having stored thereon one or more of the computer program according to claim 36 and the computer program according to claim 38.

40. A laboratory instrument servicing system, comprising at least one computing device providing a cloud service and at least one laboratory instrument, wherein the servicing system is configured to implement the method according to any one of claims 1-17 and / or the method according to any one of claims 18-34.

Images