Author: Eric Vasbinder
The Trimble Viewpoint Vista solution is a powerful, construction-focused ERP system that provides customers with some of the most flexible and robust financial, project, services, and materials tracking, amongst many other capabilities. As such, the Vista solution is utilized by customers both large and small, covering the gamut from small customers with only a few million dollars in revenue each year, to large, publicly traded construction behemoths with annual revenues in the billions of dollars.
To that end, the architecture to deploy Vista is not a once size fits all solution: as customers increase in size, sophistication, and transaction volume, the demands on our cloud infrastructure also increases.
As such, we have developed three main deployment architectures for Vista in our cloud:
Standard Architecture
Enterprise Architecture (EA)
Enterprise Architecture (EA) with Vista Enterprise Database (VED)
The following is a high-level comparison of these three architectural deployment models, followed by links to more details about each deployment architecture.
Designed for customers with average volume and scale needs, including daily active data entry, handling real-time project management, job costing, accounts payable, and payroll processing.
This is the default architecture into which almost all new (non-EA) customers in our cloud are placed.
NOTE: ESB customers obtain EA by default.
Uses additional resource splitting and activity isolation designed to provide scaling for larger enterprises with large transaction volumes or substantial concurrent user activity.
Includes all the scaling horsepower of EA, but provides additional horizontal scaling by splitting read only reporting, queries, BI, analytics, etc. into a near real time replicated SQL server, thus isolating this activity from data entry and batch processing.
The resources for the Application Server, Database Server, and Crystal Report generation are all combined into the D1 box.
The resources for the Vista Web Server and the VRL server are all combined into the D2 box.
The combined nature of the Vista "D1" server and the "D2" server increases risk of resource contention when faced with high transaction volumes and/or heavy concurrent usage.
Overall, this architecture horizontally scales much of the load in the Vista environment to accommodate larger user counts and higher volumes of batch processing activity.
The resources for the database, application server, and crystal reporting server are split into separate VMs, allowing for easier scaling, monitoring, and targeted resource optimization
-DB1, -APP, and -CN1
The resources for the Vista Web server and the VRL server are split into separate VMs, allowing for easier scaling, monitoring, and targeted resource optimization
D2 and -VRL
This architecture is designed for the most extreme Vista implementations, taking the horizontal scaling of EA one step further by splitting out the read only query activity from the main transactional DB into a separate, near real time replica, fronted by an Azure listener (for reliability and efficiency).
The resources for the database, application server, and crystal reporting server are split into separate VMs, allowing for easier scaling, monitoring, and targeted resource optimization
-AG, -SQL1, -SQL2, -APP, and -CN1
The resources for the Vista Web server and the VRL server are split into separate VMs, allowing for easier scaling, monitoring, and targeted resource optimization
D2 and -VRL
Included by default with any basic Vista installation.
Included with the Enterprise Solutions Bundle (ESB) for Vista at the Bronze tier or higher
This requires a separate purchase of the ESB program as well as the purchase of an implementation project to enable the complex move from standard to EA.
Please reach out to your account executive for more details about the ESB program.
Available as a specialized add-on for ESB customers at the Silver tier or higher of the ESB program; cloud-hosted customers only.
It requires an explicit purchase of an additional implementation project, in addition to regular costs of the ESB program to establish the secondary reporting replica.
Please reach out to your account executive for more details about the ESB program.
The following pages provide details for each deployment architecture, as well as a timeline for the move to EA or EA with VED:
Standard Architecture: Standard Architecture for Vista
Enterprise Architecture (EA): Enterprise Architecture - Vista
Enterprise Architecture (EA) with Vista Enterprise Database (VED): Vista Enterprise Database (VED)
changelog
Tuesday, 16 June 2026 at 05:02PM:
Initial posting