Laboratory execution and workflow applications
Paper worksheets and free-form spreadsheets leave the hard parts to people: following the current version of a method, doing the calculations correctly, checking that instruments are in calibration, noticing that a value is out of limits. A laboratory execution application guides analysts through each step and records what happened as it happens.
Situations we often hear about
- Analysts work from printed methods and paper or Excel worksheets that reviewers check line by line.
- Calculation and transcription errors turn up during review, or later.
- It is hard to show which method version was used and whether the instrument was in calibration.
- Training a new analyst on a method takes a long time.
What we deliver
- Method design
- Methods defined as versioned, step-by-step procedures with instructions, inputs, units and acceptance criteria.
- Guided execution
- Analysts follow the published version step by step, with calculations performed by the system.
- Checks at the bench
- Limits evaluated as values are entered, and instruments out of calibration blocked from use.
- Exceptions in context
- Deviations captured, with an explanation, at the step where they occurred.
- Review by exception
- Reviewers see the complete record and can focus on what was flagged.
- Workflow tracking
- Work queues, assignments, progress and turnaround visible to the whole lab.
How we approach it
Digitizing a method is a design exercise, not a transcription. We work with the people who run the method to decide where the system should guide, where it should check and where it should stay out of the way.
We usually start with one high-volume method, prove it in routine use and expand from there. Execution applications can run on their own or receive work from, and return results to, your LIMS.
See it in a working application
The Laboratory Execution System (LES) demonstration shows this kind of software end to end. Methods defined as versioned, step-by-step procedures; analysts guided through each execution with calculations, limits and instrument checks; exceptions, review and a complete audit trail.
A demonstration and starting point, not a finished or validated product.
Chapters and screenshotsQuestions we often hear
What is the difference between a LES and a LIMS?
A LIMS manages samples, tests, results and reporting across the lab. A LES focuses on how each test is performed, guiding the analyst through the method step by step. Many labs use both, with the LES receiving work from the LIMS and sending results back.
Does a LES replace an electronic lab notebook?
Usually not. An ELN is built for flexible, exploratory work; a LES is built for routine, standardized methods. They serve different purposes and can coexist.
Can you digitize our existing methods?
Yes. We work through each method with your analysts and QA to turn it into a structured procedure. It is also a good opportunity to clarify steps that are ambiguous on paper.
Related
Tell us what your lab needs
Describe the process, the systems involved and what is getting in the way. We will reply personally and suggest a sensible next step, even if that step is not a project with us.