Specifications

Today I embark on getting, saving, updating and deleting specifications for components within an analysis. I hope to say its done by the end of the day. This is kinda a week late. I mean, I was really hoping to have more done sooner, but support calls are coming in. You see we are in the middle of grape harvest. So the core product is being used extensively by tired and confused winemakers, enologist and cellar workers. It could be made a lot easier. In the future I hope I can do that.

Back to the LIMS project. The specifications are key to how an Analysis will be able to define the limits, ranges and hold times for each particular component. The crux of this design is that all labs within the enterprise have a stack of available components. These components make up the basis for all labs being able to exchange data. Then each lab combines those components into their specific methodology. For example, Lab X creates Metal analysis, specific to their lab, means they test for Calcium, Potassium and Sodium. Second Lab Y creates a Metal analysis, but they test for Potassium, Lithium and Beryllium. Within each analysis there are specifications for each component. Dated with a start date and end date - so at any point in time, you can see what the limits were for that component. A tree forms, Analysis has Component branches. A Component has Specification branches.

Let's see how well this works in action...