VTScada can run on NUC (Next Unit of Computing) devices that are WINTEL based.
A demo \ test was performed running the VTScada WaterDemo (about 10,000 tags) on a $99 USB-stick computer (with Windows10 OS and flash drive). Hard to get much cheaper considering your time to add a case, power supply, wi-fi, & other interfaces for cheaper devices.
http://shop.lenovo.com/us/en/desktops/ideacentre/stick-300/
Performance was adequate while VTScada was performing server functions such as providing thin client displays, historian, local keyboard & mouse display, etc.). The only problem is you tend to lose these tiny devices easily
Now, if you couple that low cost hardware with VTScada's ability to run MULTIPLE historians locally and sync each one (or only select ones) across a network some really cool stuff could happen (i.e. like syncing only the slow historian with a central site to keep cellular data costs down, but copying locally triggered high speed historian "events" into the slow historian for remote analysis. **As VTScada performs historian synchronisation automatically, and bidirectionally with automatic fault recovery, this gives high speed local event capture but at low speed data bandwidth costs**). That application was custom, so more info would be needed from Trihedrals application engineering group.
VTScada can run on NUC (Next Unit of Computing) devices that are WINTEL based.
A demo \ test was performed running the VTScada WaterDemo (about 10,000 tags) on a $99 USB-stick computer (with Windows10 OS and flash drive). Hard to get much cheaper considering your time to add a case, power supply, wi-fi, & other interfaces for cheaper devices.
http://shop.lenovo.com/us/en/desktops/ideacentre/stick-300/
Performance was adequate while VTScada was performing server functions such as providing thin client displays, historian, local keyboard & mouse display, etc.). The only problem is you tend to lose these tiny devices easily :)
Now, if you couple that low cost hardware with VTScada's ability to run MULTIPLE historians locally and sync each one (or only select ones) across a network some really cool stuff could happen (i.e. like syncing only the slow historian with a central site to keep cellular data costs down, but copying locally triggered high speed historian "events" into the slow historian for remote analysis. _**As VTScada performs historian synchronisation automatically, and bidirectionally with automatic fault recovery, this gives high speed local event capture but at low speed data bandwidth costs_******). That application was custom, so more info would be needed from Trihedrals application engineering group.
edited Mar 2 '17 at 12:20 am