Process Analysis

All the relevant data concerning the processing of a procedure is saved in a separate run database. This can be archived for a process as documentation.

All analyses which can be carried out in runtime for a procedure can also be processed retrospectively using the run database.

Runtime Behavior

For each processed labware important data are recorded, e.g. when a function was started and how long did the processing take.

• This information is represented in different views using Gantt charts, other 2-D charts or 3-D charts.

Measurement Data

• If devices supply data in accordance with the SiLA Data Capture Standard, this can be visualized online.
• This enables assessment of the assay stability and the correct method of operation of specified devices.

User Interface

Workflows for any labware (microtitre plates, vials, petri dishes etc.) can be created and processed. A mixture of different labware is also possible.

Procedure Editor

In niceLAB, a workflow is depicted using a 2-dimensional arrangement of stations. In this context, a station corresponds to the use of a device at the corresponding location in the workflow. The device functions can be used in the stations. In niceLAB, a workflow is referred to as a procedure.

• Any desired procedure can be defined by dragging and dropping stations and functions.
• Parallel sequences (threads) can be defined through parallel arrangement of stations. All threads are processed independent of each other.
• Parallel sequences can be synchronized using synchronization points.
• Procedures can be conveniently parameterized through the use of variables.
• Procedures can be exported and imported.
• All procedures are saved in a database. This enables system-wide consistency of data for all procedures to be safeguarded with the pool of existing devices and their functions.
• Procedures can be well-structured saved in folders.

Runtime Interface

Processing of a procedure can be controlled from an additional user interface. This contains only the information which is necessary for processing.

• Variables which can be used during processing are set by entering values in the fields.
• The status of all devices and of the system is displayed.

SiLA Device Driver

A standard for the interface between devices and control software was developed by the Association Consortium Standardization in Lab Automation (SiLA). This standard (SiLA Device Control & Data Interface Specification, DCDIS) is freely available and can be downloaded from the SiLA website by registered users.

niceLAB Dynamic Scheduler

The niceLAB dynamic scheduler provides an optimum schedule for a procedure.

• The scheduler works event-controlled resulting in a maximum throughput.
• Alternatively, time-controlled mode may be used if well-defined timing is an issue for the processed labware.
• The niceLAB scheduler provides automatic deadlock prevention.

• Programmed events may be used for modelling of loical dependencies.
• Logical dependencies can be reproduced in the procedure using user-defined events.
• Chronological dependencies can be implemented in event-controlled operation using timestamps.
• niceLAB implements the error handling defined in the SiLA standard. This means that the procedure can be continued after the error has been eliminated.
• During runtime, it is possible to redirect the workflow to another location in the same thread or in another thread depending on
  • Variable values
  • Data supplied by devices
  • External information (e.g. results of a database query)
• Procedures may be kept simple using loops.
• Threads can be used like subroutines.
• Procedures can be simulated using the niceLAB scheduler.