Rivet Work - Resource Scheduling and Management

NOTE:  This product is NOT the same product as Viewpoint's newly purchased API solution, called RYVIT.

Author:  Eric Vasbinder

Support Status:  APPROVED

Integration Method:  ODBC Direct Database

Connection Methods:

• PREFERRED:  TLS Database Endpoint (TLS VPN)

• IPSEC VPN

Hosted:  NO

Hosting Location:  EXTERNALLY in vendor’s cloud, connected over TLS Database Endpoint (TLS VPN) or IPSEC VPN.

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

Vendor URL:   https://www.rivet.work

Product Use Case:

Rivet is a workforce + equipment operations, management, and scheduling platform for commercial and industrial construction subcontractors + self-perform groups.  Joint customer operations teams, safety teams, project management teams, and HR teams use Rivet to plan, allocate, and measure labor and equipment utilization.

Similar Products:

This product is similar to and competes with other resource planning and scheduling solutions.

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.  To ensure that the two systems can communicate, we set up either a TLS Database Endpoint (TLS VPN) or a server-to-server IPSEC VPN between our cloud and the vendor's multi-tenant cloud.

Deployment Methodology:

We do not support hosting of this product in our cloud.  As such, the customer must continue to host the actual program (i.e. "bits") in either their on-premise environment or in another cloud.  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. (PREFERRED) TLS Database Endpoint (TLS VPN) with the remote, public, static IP of the vendor's cloud added to the pre-approved list for the customer's environment:  TLS Database Endpoint 

        1.  OR

     2. 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. Configure the third-party solution to talk to the IP address of the new Vista server in our cloud.