The plan to use Groov is to have a guy in a truck with a smartphone in hand. He drives to a site, does a visual of the site, checks the data on his smartphone and moves forward from that. The system will be a network of compact logix controllers connected via a wifi system like Ruckus. In the “office”, there is a pc with kepserver ex and groov on it, a wifi network manager component, and a connection to corporate IT. At each PLC site there will be a NAT device between the WiFi connection and the equipment, (PLC,HMI etc). In kepserver there will probably be one channel for each node with one plc per channel.
Now, the implementation of kepserver and groov will be sophisticated enough that troubleshooting it from halfway around the world could be challenging at best. So, I am thinking why not virtualize it? If the install gets “damaged”, it could be easier to delete it and copy a backup back onto the pc than trying to fix whatever is wrong.
I realize that a backup image could be made of the installed system too, and am working on that idea.
So, if we did a VM, we would put kepserver, its app, and Groov, and it’s app on a windows 7 pro vm, on a windows 7 64 pro host. Would your people be willing to support us in that kind of environment? How would the licensing issues work with Groov? Are there other concerns/issues that would make this a bad idea?