Wasp's AssetCloud On-Premise product can be deployed in government, military, financial, and other environments where the system must be isolated for security purposes. Wasp offers mobile devices that can be ordered without Wifi/Bluetooth chips/radios. These devices can be used with wired ethernet cradles which enable communication to the PC holding the database. (Note that Wasp also offers USB cradles for these devices, but the USB cradles will not function with AssetCloud On-Premise.)
Devices that have been tested in this configuration:
* (preferred) DR5 Android-based mobile device
* (preferred but older) DR4 & DR3 Android-based mobile device
* (deprecated) HC1 Windows Mobile-based mobile device
AssetCloud uses a cached database on the mobile device, meaning the device can be used while out of the cradle (not connected to any network), for example. carried to where the assets are located. Then when the device is returned to the cradle, the mobile app should detect the network connection, and sync any mobile changes back to the PC's database.
Android devices: The AssetCloud app can be downloaded from the Google Play Store (if allowed to connect to the internet), or the apk file can be sideloaded via MicroSD. Contact Wasp Tech Support to obtain the latest apk download link.
HC1: Follow instructions in Mobility, Mobile Setup to install the Windows Mobile app from the ACLOP PC over the network connection.
There are two methods to make the network connection from the mobile device to the AssetCloud PC:
1. Use a crossover network cable directly from the cradle to the PC. Both the PC and the mobile device must be configured with static IP addresses on the same subnet. Example IP addresses: 192.168.0.1 & 192.168.0.2, with subnet mask 255.255.255.0.
2. Use regular network cables connected from each PC and device cradle into a network switch (or hub) to make the network connection (which can be isolated from any other network). This configuration can be used when there are more than just one PC and one mobile device that will be used by the ACLOP system. For assigning IP addresses, this method can use either a DHCP server, or assign unique static IP addresses to each device/PC manually.
On the ACLOP PC, an additional binding with the PC's IP address should be added to the WaspMVC site in IIS.
Then when connecting from the mobile device, the Service Url would be specified including that IP address, for example http://192.168.0.1:8082