Abaqus - allGeo Field Service Automation

Author: Eric Vasbinder

Support Status:  APPROVED AND SUPPORTED

Integration Method:  ODBC Direct Database AND Automated File Imports

Connection Method:  IPSEC VPN

• TLS Database Endpoint (TLS VPN) is not an option due to the need for automated file imports

Hosting Location:  Partner Cloud

Additional Charge from Trimble Viewpoint:  NO (VPN add-on included in every cloud contract by default - if not on your contract additional charge will be required to add VPNs)

Product Use Case:

The platform helps customers build custom workflows for time attendance, jobs cost tracking, lone worker safety, mileage tracking etc. These workflows are supported by tools such as geofence job sites, QR code & mobile forms field data collection, GPS Tracking, IFTTT rules engine.

Similar Products:

This product is similar in operation and feature set to our Trimble Viewpoint Field Service tools and tools from Field Connect, Traqspera, and MSI Data.

ERP Connection Overview: 

As per many other server-side integrations to third-party products, this product is designed to talk to Vista's database directly using ODBC.  This connection requires that the Vista server be "visible" to the third party system.  In addition, it also requires file imports be made available in an automated fashion to Vista.  As such, to ensure that the two systems can communicate, we set up a server to server IPSEC VPN between our cloud and the partner's hosting environment.

Deployment Methodology:

We do not support hosting of this product in our cloud.  As such, the customer host the actual program (i.e. "bits") in Abaqus's cloud environment.  As a result, since this product and Vista will be on separate networks, a VPN is needed to bridge the gap between the two networks.  This solution uses a data connector ("shim") between the Vista server and other third-party products.

Detailed Instructions:

• 1. Stand up remote connectivity to our cloud:

     1.  IPSEC VPN between hosting location of third party product and customer's Vista environment in our cloud: How do I set up an IPSEC VPN to access my Vista database directly?

  2. Create SQL account to allow third-party to authenticate to Vista:  I need a dedicated SQL account for my integration to Vista in your cloud. How do I set that up?

  3. Mount the Vista server's Import "Pickup" folder as a drive letter in the partner's cloud, pointing to the Vista server over SMB:  https://sites.google.com/trimble.com/vista-cloud-faq/home/using-your-cloud/setting-up-automatic-imports-into-vista

  4. Configure the third-party solution to talk to the IP address of the new Vista server in our cloud.

tl;dr:   All programmatic components of this solution must be hosted externally to Viewpoint's cloud environment. Customers who need to integrate this solution with Vista in our cloud need to use an IPSEC VPN.  Once the VPN is configured and in place, we stand up a SQL account to allow communication with Vista.  The customer and/or partner then configures this solution to point to the IP address of Vista in the cloud.