Screening
Beckman Coulter (
www.beckmancoulter.com) develops systems that improve reliability through software functionality. Their systems combine best practice runtime reliability features with method development software for discovering errors before beginning a run. Obstructions on the deck of the liquid handler are known and the software pre- vents the pod from moving into a location where a crash could occur (collision detection) and will reroute gripper movements to move around obsta- cles (obstacle avoidance). Labware definitions pre- vent tips going lower in the well than the defined safe height. One or more tip touches can occur to every side or corner of the well. Volume tracking within methods prevents aspirating more liquid from a well than exists or overfilling a well. Using an accurate timing, location and resource model, SAMI EX’s planning scheduler allows a method to be reviewed without simulating the run. SAMI EX’s runtime software displays a view of the method showing plates numbered by family mov- ing through the flow chart. Any device failure can be addressed programmatically at the device mod- ule level, automatically by the system executive using response definitions, or interactively prompt- ing the user (through email alerts, alarm, and prompts). Assisting in error responses, every plate in the system is listed with its current location, position in the method and properties. Device modules can be reloaded/restarted, the method rescheduled, or families added to the method being run. Beckman’s development processes adhere to a strict ISO 9001:2008 registered quality systems. Systems are set up, maintained and serviced by a worldwide service organisation (Figure 12).
In CyBio’s (
www.cybio-ag.com) Scheduler, inaccu- racies of measurement systems can be compensat- ed by appropriated tolerant measurement value descriptions, eg specification of lower and upper bounds. Furthermore, in case of an instrument fail- ure, alternative data results can be generated or the user can be requested to submit alternative data results. A typical example is the generation of sub- stitution barcodes during a barcode reader failure. Instrument failures should be handled automatical- ly as far as possible. However, this needs a flexible failure management which is not restricted to a local failure evaluation. Instead, the overall conse- quence on the workflow must be taken into account, including the prevention of deadlock con- ditions. The CyBio® Scheduler software has imple- mented a multi-level failure management, which ensures appropriate standard failure handling for any use case. The standard failure handling can be
Drug Discovery World Winter 2010/11
Figure 12: Beckman Coulter’s SAMI EX runtime Software
overridden or adapted. To evaluate the overall effects of a locally occurred failure, the CyBio® Scheduler software uses well-known mathematical methods (such as Petri nets). This ensures that the overall process effects can be determined (such as delays or a changed execution orders). Thus, dead- locks can be avoided by an appropriate active rescheduling. Potential sources of user mistakes can be proactively reduced by input verification
Figure 13: CyBio® Scheduler: designed to be dynamic, deadlock-free and fault-tolerant 67
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80