VWorks Software Setup Guide : Defining labware : About defining labware with the Labware Editor
About defining labware with the Labware Editor
Labware defined
Labware is a physical object such as a microplate, lid, or tip box that will be acted upon by the tasks stored in your protocol.
The VWorks software requires all labware that will be handled by the automation system to be defined in the labware database.
Labware entry defined
A labware entry is the collection of properties or parameter values that describe a specific type of labware. This information is used by the VWorks software to command the robot and other devices to do tasks based on the information in the definition. Each labware entry is saved as an .xml file in Shared Services storage.
All labware parameters are entered and accessible through the Labware Editor.
VWorks Plus only. The labware entries are records of interest. The software automatically logs audit trails for the labware entries that are in the In Validation and Released states. Optionally, the software can log audit trails for these records while they are In Development.
Labware Editor defined
The Labware Editor is the VWorks software interface through which you can enter information about labware.
You must be logged in as an administrator or technician to use the Labware Editor.
Types of information stored
Two main types of information are stored in the labware database:
Information about the labware properties
Information about labware classes
About labware properties or parameters
Labware has physical properties such as width, length, and number of wells. Labware can also have non-physical properties, such as robot-handling speed, robot grip offsets, and microplate-handling options.
After labware is defined in the Labware Editor, all you have to do is select the type of labware to use each time you set up a protocol.
About labware classes
Labware classes are sets of labware entries, grouped so they are easier to manage than many individual labware entries. Each labware class is saved as an .xml file in Shared Services storage.
Labware classes are used in combination with the device manager to restrict which types of labware can be used on which devices during a protocol run. This prevents wasted runs and damage to the devices on the platform.
An example of how damage can be prevented by labware restriction is where a tip box that is too tall for a device crashes into the device as the robot delivers it.
VWorks Plus only. The labware classes are records of interest for which the software automatically logs audit trails. These records are exempt from transitioning through development states.
Related information
 
For information about...
See...
Workflow for adding labware to the Labware Editor
Overview of the Labware Editor
Opening the Labware Editor
Audit trails (VWorks Plus only)