Colour Database

Hi, My name is Nichole Clarke and I work as a Laboratory Manger for a large winery in New South Wales. We are looking to move from a manual data recording system for field and laboratory testing to an automated platform which would be able to link with several other systems currently used to manage workflow. An overview of what is currently being used to what would be expected is provided below and in the attachments Vintage Sampling Officer (VSO) Program + Maturity Data Management System VSO program: * a database system designed to accept import from EZY Wine that provides base data on blocks * limited to use of updated data from EZY - i.e. program has no memory, so cannot exclude blocks sampled on that day or blocks for which data is not in or updated in EZY. This is currently overcome by manually checking and excluding * Manipulate data through a series of queries and filters to determine blocks to be sampled * Create run sheets of blocks to be sampled & number samples per block per subregion * Create associated sticker labels with ID barcode to go on bags of sampled grapes * VSO take printed run sheets and barcode labels into field * VSO record location of samples, who, date, time and comments on run sheets &/or stickers * Use iPad for navigation and block identification using GPS overlay on Google maps * Use iPad to take georeferenced photos where need to report anomaly (e.g. disease) to Grower Liaison Officer (GLO) * VSO deliver samples to lab that require colour and / or laccase testing * Colours lab process samples and record data on the go on the colour worksheets - refer to Lab flowchart * VSO process Baume only samples and record results on run sheets * Grower Services Admin receive run sheets from VSO + worksheets from Lab and enters the results into the colour spreadsheet for calculation, then final numbers into Ezy. * Number of hours spent on data input for maturity results requires addition of 1 casual vintage employee and regular weekend work to have data updated in Ezy for use in creating sampling and intake plans Upgrade of VSO program + addition of maturity data management into a live system means: * VSO run sheets move from paper to iPad for direct input of field data * Continuous update of blocks sampled and bags collected so lab can see incoming work load and VSO GLO can monitor what blocks have been sampled / not sampled * Relevant block data from VSO program flows into maturity data management system awaiting analysis results * For VSO processed samples, Baume’s to be entered into iPads - block averages calculated within system and results exported for uptake by Ezy. This removes one set of data input and one source of human error. * For lab processed samples, data is entered into system, predominantly direct ex equipment. System runs an update at a set interval (e.g. every 30 minutes), calculates average for blocks with all samples complete and results exported for uptake by Ezy. This removes a major set of data input and source of human error * Increased speed of data throughput means more up-to-date information available, and able to remove the need to highlight "final samples" for processing first - a time consuming step removed from the lab. * Maturity data - the results or just having confirmation they have been collected and are in process, feed into both the VSO program for sampling planning and the Intake Schedule for winery intake planning. * Use of info from Intake Schedule to identify blocks for sampling due to harvest (this is currently done manually and is very time consuming)