Figure 2.

AWL. Depictions of operation, operation type, plan, and job models that comprise an AWL. (a) An example of a ‘Bacterial Transformation’ operation type is displayed. Operation types define specific ways in which input samples and items can be processed to produce outputs. Each operation type contains specifications for its input and output types. For example, the ‘DNA’ input of a hypothetical bacterial transformation operation type may be satisfied by a ‘maxiprep of plasmid library’ or a ‘miniprep of plasmid’. Input and output types are entirely customizable and may include any number of sample type and object type specifications. Sample routing, if provided, ensures the input and output samples are mapped correctly upon operation execution; here the input ‘DNA’ sample will be mapped to the ‘Transformed Cells’ output sample. Non-inventory inputs (i.e. parameters) can also be defined as inputs to operation types. (b) An example of a bacterial transformation connected to a colony PCR operation. Operations types are instantiated to operations when their input and output types are satisfied by items. Here, a bacterial transformation uses specific items in the LIMS and a parameter (37°C) to produce a bacterial plate. After executing the transformation, the output plate is wired to the colony PCR operation. The colony PCR outputs the amplicon to an empty well in a stripwell. Notice that the operation type sample routing ensures sample information (here pUC19-GFP, sample 442) is maintained throughout the series of tasks. (c) Operations from several different researchers and different plans can be batched together into jobs if they have the same operation types. For instance, all ‘Colony PCR’ operations from all users can be run as a single job. (d) Once operations have been batched into jobs, jobs can be run divorced from Aquarium plans because all necessary information for execution is included in the job. These jobs can then be performed concurrently by separate technicians.