For some time now, vintrace and TankNET have had a working bi-directional interface allowing information to be shared between the two systems.
vintrace pushes tank change to TankNET such as batch/lot codes and descriptions, product states, brix readings, wine volume, etc.
vintrace also pulls temperature readings as well as brix readings entered into TankNET (through the TankNET software, or the physical controllers on tanks). vintrace will also check a tank’s alert status and show a warning indicator when viewing wine details.
This sounds good, but what makes it even better is that after the initial configuration (which our support staff will help you with), there isn’t really anything extra you need to do in either system to have the two systems stay synchronized.
Temperature and brix readings from TankNET appear in vintrace as Analysis entries (with indicators to show you that they originated from TankNET), and any operations that you complete in vintrace that alter a tank’s state, volume, etc will trigger an update behind the scenes that will push this information to TankNET.
There are a couple of extra options when the interface has been enabled in vintrace under the “Actions” menu in the Product Overview (when you’re viewing a wine/tank)
The “View in TankNET” option will open TankNET to the tank you’re viewing in vintrace so you can see real-time temperature / alert / etc information. Also note, that if the tank is in the alert state and vintrace is displaying the alert indicator for the tank, when you click on the icon, vintrace will take you into the same tank in TankNET so you can view the alert details.
The “Sync to TankNET” option will allow you to force an update of the current tank details from vintrace to TankNET. This can be used in the rare occasion where the two systems may not be in sync (most likely due to something like a network outage between vintrace and your TankNET server). There’s also an option under your tank interface settings to sync all tanks if this happens as well.
One of the potential problems with an interface like this is where work orders may not be entered in real-time, but the temperature readings from the tanks are in real-time. For instance, you could end up moving a wine in the Winery and recording analysis against the old batch (because the work order may not have been updated in vintrace yet). vintrace has some smarts built in to stop this from being a problem. When you create an open work order for a tank, vintrace will put any brix/temp readings for that tank on-hold. Once the jobs have been completed in vintrace, the recording of temp/brix details will resume.
The frequency of the temperature readings are configured based on the product state of the wine. For instance, you’ll typically be more interested in the wine’s temperature during fermentation compared to when it’s in tank for storage. We also have an option to allow you to only record a temperature reading when a corresponding brix reading has been entered into TankNET (via the controller or through their software). This gives you some flexibility in how often the system fetches the temperature readings while the wine is fermenting.
The vintraceto TankNET interface is an added-value module so please contact vintrace ( http://vinx2.com/ ) if you are interested in using this feature. Please note that you may also be required to have features enabled in your TankNET system (contact Acrolon Technologies at http://www.acrolon.com/ for more details)