Switching from Viewpoint Enterprise Cloud (VEC) RDP or Vista SaaS or Delaware to Trimble Construction One (TC1) / Viewpoint One (VP1) with VRL

Author: Eric Vasbinder

IMPORTANT - This Cloud FAQ is for VEC RDP or Vista SaaS (a.k.a. Delaware) to TC1 Moves ONLY.  

VFC to TC1 moves are significantly more complex and are detailed here:  Moving to Viewpoint One / VRL for VFC Customers 

IMPORTANT:  The ONLY item that MUST be performed right away is upgrading your commercial contract to a Trimble Construction One (TC1) contract.

Once completed, you will be able slowly consume the new elements of TC1 as your time allots, beginning with a move to Trimble ID SSO for authentication (if not already in use). 

Starting to use VRL will be the most impactful portion of this effort, can be done slowly per user, and is NOT required for using Analytics or Automatic Invoicing.

Overview

Viewpoint Enterprise Cloud (VEC) is a robust cloud solution for Viewpoint's customers.  Launched in 2017, VEC was designed to be the premiere way for our customers to experience the power of our Office, Team, and Field solutions.  Specifically, VEC was designed to bridge the gap between more legacy cloud solutions, such as Viewpoint for Cloud (VFC), and our modern clouds that use Vista Remote Link (VRL).  To that end, VEC uses a published applications approach for client-side application interaction that allows the Vista client and associated third-party apps to seem as if they are running natively on an end user's workstation, when in fact, they are running on our RDP terminal servers in our cloud.  This is why VEC is often called by its more full name, VEC RDP.

However, we always knew that VEC RDP, and its immediate contractual successor "Vista SaaS" (also known as Delaware), was to be a stepping stone to a much more "cloud and user-friendly" solution that would make use of Vista Remote Link (VRL).  VRL in our modern clouds is used to ensure that the Vista rich client can run over the Internet on an end user's local workstation over HTTPS, similar to how Microsoft Outlook with hosted Exchange functions.  This in turns completely avoids the need for Trimble Viewpoint to host any client-side applications in our cloud, such as Microsoft Office, Vista's client itself, Spreadsheet Server, and more.  Thus, in our modern clouds, whilst the Vista server and associated back end components are still hosted in our cloud, the client side applications reside on an end user's local workstations, or possibly in a customer-hosted and managed virtual desktop solution, such as Azure Virtual Desktop (AVD).  As such, there are a number of capabilities that are not available for VEC customers that are available for TC1 customers.  

Based on the desire of many VEC customers to experience the "latest and greatest" Trimble Viewpoint cloud capabilities, they have been approaching our teams to inquire about how they might "convert" to TC1 from VEC.  To that end, this Cloud FAQ article will provide descriptive steps on how to upgrade from VEC RDP to TC1 with VRL and a link to a detailed architectural and end user differences article between VEC RDP and TC1.

Please read on for directions to the new, shiny awesomeness!

IMPORTANT

Note that the processes described below are the same for Vista SaaS contract customers, also known as Delaware, as they are for VEC RDP.   If your contract is on the Vista SaaS generation of contracts, please follow this process to start using the powerful, new TC1 capabilities.

Differences Between VEC RDP (or Vista SaaS / Delaware) and TC1 with VRL

When it comes to VEC RDP and TC1 with VRL, we need first understand the differences in capabilities that are available and then mentally segment the client-side applications from the server-side infrastructure.  At the highest level, while the server-side architecture is nearly the same between the two cloud types, client-side applications are handled differently. 

 Please note however, that end user process and client-side application hosting details do NOT need to change right away after moving to TC1 from VEC RDP.  Continue reading the following FAQ article for more details on additional capabilities, architectural differences, and end user changes.

Differences Between VEC RDP and TC1 / VP1 with VRL 

Detailed Steps to Move to TC1 from VEC RDP

There are a number of steps that are performed to move from VEC RDP to TC1.  Please note that, as mentioned above, the architecture on the back end of TC1 is the SAME as VEC RDP, but with the simple addition of the VRL reverse proxy server and a greater emphasis on using Trimble ID SSO for logins.  As such, the contract signing to TC1 will be a non-event for your end users; they will only notice a change when you and your team are ready to move your end users toward making use of VRL.  Your steps to move to VRL can be performed slowly over a period of months or sometimes years, there is currently no deadline to fully move TC1 customers who were formerly on a VEC RDP contract over to VRL.

Please see below for the steps involved from both a commercial standpoint and for technology to move to TC1.

REMINDER:  The COMMERCIAL Steps in Part A MUST be performed FIRST as being on a TC1 (VP1) contract is a REQUIREMENT for using VRL.

Part A - Commercial Steps

As mentioned above, VEC/RDP customers need to be first fully converted to a Viewpoint One (VP1) / Trimble Construction One (TC1) contract if not already.  Please note:  many VEC/RDP customers were brought into our cloud as VP1.  If you are unsure, please reach out to your Viewpoint account manager to help you find out if you are on a VP1 / TC1 contract.

• If you are not, please work to switch your contract over to TC1 / Viewpoint One.

  • NOTE:  There will be a charge for professional services to implement the Viewpoint One components (e.g. Team, HFF, Search, Analytics) in addition to possible increased monthly charges for the move itself.  Please contact your rep for details specific to your situation.

  • NOTE:  We recommend that, as part of this process, that you convert your contract from Concurrent User Licensing (CUL) to named users.  A named user licensing (NUL) model will allow you to much more easily take advantage of powerful new capabilities in TC1 especially Vista Web Office Tools.

Part B - Baseline Technology Steps

Getting Ready

If you are a VEC/RDP customer, once you have converted to a Viewpoint One contract, here are the technology steps to move forward with VRL:

• 1. Ensure that your network latency to one of our supported datacenters is no more than 60ms.  Please follow the instructions on this page to properly test your latency:

     1. How do I know if my network can handle hosting Vista in your cloud?  What are your network standards?

        1. NOTE:  30ms or below is HIGHLY PREFERRED.

IMPORTANT:  If your network latency is significantly higher than 30 ms to where your Vista database is currently hosted, you may see suboptimal Vista VRL performance.  To that end, please review the datacenter speed results for the datacenters that Viewpoint currently supports for VRL (see here for instructions:  Network Standards for VRL Cloud Connections and Testing Them).  If you find a supported datacenter with much faster (smaller) latency values, please make a note of those and reach out to cloud support to see if you are a candidate for relocating your Vista instance to a datacenter that is closer to where your data entry experts are located.  

• 2. REMINDER:  Ensure that you are on a Trimble Construction One contract as PER SECTION A, ABOVE.  Trimble Construction One (TC1), formerly known as Viewpoint One (VP1), is our powerful bundle of cloud-hosted technologies, including web extensions for Vista (HFF, formerly known as Keystyle), Viewpoint Analytics, Viewpoint Search, Team Project Management, Vista or Spectrum ERP, as well as forthcoming technologies.  Please reach out to your account rep to ensure you are on a TC1 contract.

VIEWPOINT ACTION:  Back-end Infrastructure - TC1 Added Components

NOTE:  The following steps should be performed with no involvement from the customer once the contract is signed.

1. If they are not already installed, the Trimble Viewpoint Team will install the components on the back end for the other TC1 solutions, including HFF, connector to Team Project Management, and Trimble ID SSO.

2. If you do have Viewpoint Analytics turned on, we will activate it behind the scenes during this step.

3. The Trimble Viewpoint team will also activate any additional Vista modules that you did not already have licenses for on your VEC contract.

VIEWPOINT ACTION:  Back-end Infrastructure - VPN and/or TLS Database Endpoint (TLS VPN)

NOTE:  Setting up a VPN is likely to have already been done by your organization when it first moved into our VEC solution.  However, if you do not have either an IPSEC VPN or a TLS Database Endpoint (TLS VPN) already set up, you'll need to have that turned on.

1. The TLS Database Endpoint (TLS VPN) is recommended where possible and instructions on how to get that working are listed here:  TLS Database Endpoint 

2. The IPSEC VPN is also available, but is only needed for automated, server to server file imports OR for outbound ODBC traffic FROM Vista to another solution (extremely rare).  Here is a Vista Cloud FAQ article that will provide more details on this topic:  How do I set up an IPSEC VPN to access my Vista database directly? 

VIEWPOINT ACTION:  TRIMBLE ID SSO

1. Our team will coordinate with the customer to identify if external authentication tools should be tied or linked to Trimble ID SSO.  This can include tools such as Microsoft Azure AD (Entra ID) and Okta.  

2. There is a defined process by which we add in Trimble ID components into a customer environment, set up Trimble ID, and link or federate third-party authentication providers to Trimble ID SSO.  Here is a Vista Cloud FAQ article that will provide more details on this topic:  The Three Steps to SSO Joy - Setting up Trimble ID SSO 

   1. NOTE:   For customers in Australia or New Zealand, the following cloud FAQ article is more appropriate:  The Three Steps to ANZ SSO Joy - Setting up Viewpoint ID SSO 

VIEWPOINT ACTION:  Back-end Infrastructure - VRL

• 1. Please submit a Cloud Support case and request the installation of the VRL reverse proxy server.

     1. CUSTOMER WILL NEED TO APPROVE THE CASE

  2. Our team will install the VRL Reverse Proxy server into your environment.

ONCE YOU HAVE VRL INSTALLED, PLEASE FOLLOW THE INSTRUCTIONS ON THIS PAGE FOR TRAINING ON VRL

Setting VRL Performance Expectations

In the past, if you were using VEC RDP, you had the fastest possible means of experiencing Vista; your rich clients were installed right on top of the Vista database server, directly in the same cloud environment.  By moving the client to be on your local workstations, connecting over the Internet, certain operations in Vista will slow down.  As long as your latency to your datacenter is 30ms or less, this speed decrease should not be too impactful; performance should be "good enough" vs. screaming fast.  Please remember, your end users will also see improved usability with VRL as opposed to RDP for things such as local file access, printing, scanning, and more. 

As such, we find that even with a speed decrease for things like data entry by moving to VRL, the dramatically improved usability of VRL vs RDP more than compensates for the increased lag with 10 key data entry.

Part C - A Methodical Adoption

Moving to the use of TC1 from VEC RDP does NOT require extensive changes for your end user community.  Trimble ID SSO may be a change for your team, but the overall experience, especially when federated to your existing authentication provider, such as OKTA or Microsoft Azure AD, will likely be even smoother than your current authentication processes for your end-users.  

The convenient truth is that because VEC RDP and TC1 with VRL share so much back end architecture, you can purchase a TC1 contract and NOTHING will change for your end users, at least not until you and your team are ready for things to change.  Moving to the use of SSO should be first, followed by VRL.

To that end, once Parts A and B above are completed, you may choose 1-2 users to pilot the use of VRL in testing, starting even months after you move to a TC1 contract.  

IT IS NOT NECESSARY TO MOVE ALL END USERS TO VRL OR TO INSTANTLY CHANGE HOW THEY WORK AFTER SWITCHING TO A TC1 CONTRACT.

Please keep in mind that we have designed this process considering your needs foremost.  As such, for most customers, moving to TC1 will be a non-event, at least initially.

IMPORTANT:  Certain capabilities in TC1 are more easily experienced with the use of VRL; they work more seamlessly.

Some examples of this include Team Deep Linking, dragging and dropping files into Vista, and printing and scanning to local scanners and printers from the Vista client itself.  Keep this in mind when deciding how long to take before moving toward the use of VRL as your primary way to experience Vista and your client-side applications.

Please see below for a high-level sample, relaxing timeline for a move to a full TC1 experience for your end users.

Sample Timeline for Local VRL Rollout

The following timeline is designed for customers who are moving from VEC RDP to full VRL on TC1 / VP1 with Vista installed on local workstations.  The timing may be different if you are utilizing an Azure Virtual Desktop / thin client deployment model for Vista and associated apps.

 NOTE:  The process for VFC customers to move to TC1 is significantly more complex and is linked at the top of this article.

All timelines are examples only and may vary depending upon integrations needed, your ability to test, etc.  

NOTE:  Many customers can move through this process in 4-6 weeks depending on their ability to plan out the process, train end users, and their end users' willingness to accept the new paradigms of using Vista with VRL and having auxiliary applications outside of our AVD/RDP servers.

Steps and Sample Timing

1. Week 0:  Customer - Reach out to Trimble account manager to request move to TC1 contract

2. Weeks 1-2:  Customer and Trimble (Sales) - Finalize TC1 contract and sign

3. Week 3:  Customer - begin walk through Trimble ID SSO Federation and domain validation steps (if needed)

   1. See this FAQ for more details on SSO setup:  The Three Steps to SSO Joy - Setting up Trimble ID SSO 

4. Week 3:  Trimble (Customer Success Manager (CSM)) - Opens case on customer's behalf to have VRL proxy server installed in current VEC RDP environment.,

5. Week 3:  Customer - Responds to case from CSM with approval to have proxy server installed.

6. Week 4:   Trimble (Cloud Engineering) - spins up VRL server

7. Week 4:  Trimble (Trimble ID Team) (optional) - Federation set up for Trimble ID SSO to auth provider

8. Week 4:  Trimble (CSM)  (Optional if SSO not already in place) - Walk customer through setting up initial federation and migrating users into SSO

9. Week 5-8:  Customer - Begin migrating users to Trimble ID SSO, ideally prior to moving to VRL.

10. Weeks 5-30:  Customer's great majority of end users continue on as if nothing has happened, aside from moving to SSO (if not already on SSO).

11. Weeks 7-8:  Customer IT - sets up VRL rich client on a few workstations for IT users for review and testing.

12. Weeks 7-8:  Trimble (CSM) and Customer - Coordinate times to walk customer through differences in VRL experience vs. RDP

13. Weeks 9-11:  Customer IT - installs Vista's client on workstations for a few power users who are interested in using Vista VRL.

14. Weeks 11-15:  Customer - Power users continue to review and test the Vista client, while customer IT evaluates parallel increased use of HR Portal, Field Management, and Financial Controls.

15. Weeks 16-20:  Customer IT - works with end users to determine if client-side document files (e.g. XLSX, Estimates, PPTX, DOCX, PDF, etc.) are being hosted in the Viewpoint cloud or on their local workstations.

16. Weeks 21-30:  Customer IT and Business leaders - partner with end users to schedule a slow roll out of VRL usage and local client installs for apps to local workstations.

17. Weeks 30-35:  Customer IT and End Users - starting with ~5-10 users customers will migrate those users away from hosted client-side applications to applications on local workstations, including Vista using VRL.

18. Weeks 36-40:  Customer IT and End Users - continue slow rollout of VRL to an additional tranche of end users.

19. Weeks 41-52+:  Customer IT and End Users - continue with final rollout of VRL to all end users where it makes sense

NOTE:  You may encounter certain end users whose network speed is so slow that it does NOT make sense for them to use VRL and client apps on their local workstations.  In this situation, we recommend keeping those users hosted in Viewpoint's Terminal Services RDP until such time as your company has put into place an Azure Virtual Desktop or Terminal Services installation of your own in the same datacenter within which Vista is hosted.

Part D - Additional TC1 Components

After your VRL server is set up, and you have Trimble ID SSO configured for authentication into your environment, you will need to coordinate with your Professional Services (PS) contact and/or Project Manager to set up some of the additional, powerful tools that may be part of your TC1 contract.  These may include, but are not limited to:

• Vista Web / HFF / Keystyle (if not already set up)

• Viewpoint Analytics

  • VA Paginated Reports

  • VA Crystal Reports

• Automated Invoicing

• TC1 Workcenters

• ProjectSight

• Team Project Management