Trimble Quadri System Overview On Premise Environments March 2019

civil.trimble.com/quadri

2

Table of Contents

Document History 3 1 Trimble Quadri Design Goals 4 2 Trimble Quadri Information Model 4 3 Trimble Quadri Systems Overview 6 4 Trimble Quadri Main Access Points / Access Types 7

4.1 Trimble Quadri Technical Management 7 4.2 Trimble Quadri Model Manager (QMM) 7 4.3 Quadri Clients 8

5 Trimble Quadri System Components 8 5.1 Trimble Quadri Database structure 8 5.2 File directory structure 9

6 System Security 10 6.1 Communication security 10 6.2 User Accounts Authorization and Authentication 11 6.3 Data Back-up and Restoration 13 6.4 Restoration 14

Trimble Quadri System Overview On Premise Environments 3 March 2019

Document History

Date Document Version Description of change 17/04/2013 1.00 Trimble Quadri release 1.0 06/06/2013 1.01 Updated info about default file location for the installation 13/11/2013 1.02 Extended chapter 6 - Data Back-up and Restoration 27/01/2015 1.03 Updated to reflect that only IIS is used.

Active Directory as possible source for user accounts. 12/10/16 1.04 Updated to reflect that this is now a Trimble product 13/03/19 1.05 Updated document name, style and figures, path. Minor textual updates.

Trimble Quadri System Overview On Premise Environments 4

4

1 Trimble Quadri Design Goals The paradigm behind Trimble Quadri is built around the concept of a server which provides access to models through objects, tasks and networks. The server also retains a hierarchical overview of objects with parent-child relationships. The main design goals for the system can be summarized thus:

• Allow users to collaborate over distance and across disciplines • Provide access to project data at object granularity • Provide security with regard to user authentication and model access • Provide a flexible framework for representing business processes • Allow business rules to be automatically embedded within the project

The combination of these features allows for complete control of the model with respect to individual users, objects and projects and provide the foundation for true collaboration. Another important foundation of Trimble Quadri is the ability to use the model throughout the infrastructure lifecycle, i.e. from Design, through Construction to Maintenance & Operations.

2 Trimble Quadri Information Model

Figure 1 Trimble Quadri Information Model

Trimble Quadri System Overview On Premise Environments 5

5

A Trimble Quadri Model may contain:

• Network model • Feature model (aka Objects) • Task model

All manipulating of the feature and the network model is done through tasks. The list of allowed users on one task gives end users access to the part of the model specified by the query associated to the task. One type of task is DesignProject, another is ViewFeatures, which due to the value of the use case parameter (set to VIEW) can only be used to view the content of the information model.

Figure 2 Trimble Quadri Information Model

A ProjectMember of a DesignProject performs model-based design through the use of a Workset. The Workset belongs to the ProjectMember identified by OwnedByUser. The Designtasks are performed on a FeatureWorkset, which is a subset of the complete Trimble Quadri FeatureModel. The performed DesignTask becomes a sub task of the DesignProjects Designtasks.

Trimble Quadri System Overview On Premise Environments 6

6

3 Trimble Quadri Systems Overview Trimble Quadri is based on Web architecture and all clients connect to the system through a Web server. Trimble Quadri consists of multiple software servers, but all the servers are installed on the same computer running Microsoft Windows Server. Currently supported versions of Microsoft Windows Server are 2008 R2 and 2012 R2. The computer used to host Trimble Quadri may be a physical or virtual machine. However, only one Trimble Quadri can be installed on one computer. In addition to the commercial webserver needed to connect to the system, a Trimble Quadri implementation consists of a Trimble Quadri Application Server and a Trimble Quadri Database Server.

Figure 3 Trimble Quadri Implementation

Trimble Quadri System Overview On Premise Environments 7

7

4 Trimble Quadri Main Access Points / Access Types There are three main types of access to a Trimble Quadri site:

1. Perform technical tasks (start/stop servers, configuring properties, viewing logs etc.) related to the server component

2. Manage the models provided (ex.: user management)

3. Perform design tasks that create, delete and modify the objects and tasks (ex.: Authoring applications)

Figure 4 Trimble Quadri main access points / access types

4.1 Trimble Quadri Technical Management To perform technical tasks related to the server components (start/stop servers, configuring server properties, update with new software versions etc.) you need access to the server’s desktop, either directly physical access or trough remote desktop.

4.2 Trimble Quadri Model Manager (QMM) Trimble Quadri Model Manager is a web browser-based application that enables you to administer the models provided by a Trimble Quadri site. QMM is built using ASP.NET technology, which requires a commercial application server with .NET support to run. Trimble Quadri uses the Microsoft Application server included in Microsoft Windows Server 2008 / 2012 R2.

Trimble Quadri System Overview On Premise Environments 8

8

This server runs QMM specific business components that access the models trough a web service. The implementation of this web service manipulates the Trimble Quadri Database partly by direct SQL access, and partly by using services implemented in the Trimble Quadri API. For more details about QMM see Trimble Quadri Model Manager User guide.

4.3 Quadri Clients Quadri Clients use Trimble Quadri to achieve full collaboration support for a group of users performing model based Design, Construction and / or Maintenance. It is implemented as Windows applications that uses Microsoft IIS as webserver and manipulate the provided model trough the Trimble Quadri API on the Trimble Quadri Application server. Trimble Novapoint is an example of a Quadri Client for designing and documenting infrastructure projects, including delivering drawings and stakeout data for machine control.

5 Trimble Quadri System Components

5.1 Trimble Quadri Database structure One Trimble Quadri contains two Trimble Quadri Database instances. There is one normal production instance where all models provided by a Trimble Quadri are stored. There is also an auxiliary instance that is used during recovery of models from backup files. The auxiliary instance is normally not running and only started when needed.

Figure 5 Trimble Quadri Database System

The storage of each model is implemented as one database schema for each model. In addition to these schemas there is a system schema that contains metadata (model type, available TRUE/FALSE etc.) for all the model schemas. In the Trimble Quadri Database instance, also a schema stores the end user accounts if a configuration with embedded user accounts is selected.

Trimble Quadri System Overview On Premise Environments 9

9

Figure 6 Trimble Quadri Database Structure

5.2 File directory structure This section provides a guide and description of the Trimble Quadri directory structure and the related files that are necessary when the server is running. Normally, the root directory of Trimble Quadri is located at ‘C:\Program Files\Trimble\QMS’.

Figure 7 Trimble Quadri Files

5.2.1 Server files Server files are binaries and libraries essential for running Trimble Quadri. Server files are located in three subfolders who are named as following:

• C:\ProgramData\Trimble\Quadri Model Server\Bin • C:\ProgramData\Trimble\Quadri Model Server\Client

The Bin folder contains the binaries essential for running the Trimble Quadri Application Server.

Trimble Quadri System Overview On Premise Environments 10

10

The Client folder stores a collection of configuration and executable files that are used by QMM Web services in order to use services delivered by the Trimble Quadri Application Server (for example to activate the feature catalogue).

5.2.2 Configuration files Configuration files are located in two subfolders named

• C:\ProgramFiles\Trimble\QMS\Conf • C:\ProgramFiles\Trimble\QMS\SQL

The Conf folder consists of a series of feature-catalogues and web service-packages. The FeatureCatalogues subfolder stores the different versions of DAT-files of feature catalogues. The WebPackages subfolder contains the files and patches for installing QMM web services. The SQL folder stores files needed by maintenance and administration of the server. It contains the SQL-scripts used by QMM in order to administrate the models, and restore scripts in the case of backup and restore of the model.

5.2.3 Log files All log files are stored at ‘C:\ProgramData\Trimble\Quadri Model Server\Logs’ by default.

5.2.4 Database files This is the files that actually stores the content of the Trimble Quadri Database Default location is C:\App\QMS\Oradata

5.2.5 Data backup files This is the folder where the backup of the Trimble Quadri Database is stored. Default location is C:\App\QMS\Backup

5.2.6 Temporary files Several temporary files are created and later deleted when Quadri DCM is running. They are all stored in %TEMP%

6 System Security

6.1 Communication security As default the communication to and from a Trimble Quadri site, use HTTP - Hypertext Transfer Protocol. There is possible to enable SSL - Secure Sockets Layer, on top of HTTP, to establish an encrypted link to and from a Trimble Quadri site.

Trimble Quadri System Overview On Premise Environments 11

11

6.2 User Accounts Authorization and Authentication Trimble Quadri may use a system of embedded user accounts or it may integrate with a user accounts in Microsoft Active Directory trough a LDAP connection.

Figure 8 Trimble Quadri with embedded user accounts

Figure 9 Trimble Quadri integrated with Active Directory

Trimble Quadri System Overview On Premise Environments 12

12

6.2.1 User Accounts

6.2.1.1 Embedded User Accounts The intention behind the embedded user account strategy is to allow customers to establish a Trimble Quadri without bindings to existing user account systems. This facilitates the use of Trimble Quadri across organization boundaries without the need of adopting user account information from one organization into the user account system for another organization. In this configuration user account are stored in one dedicated schema in the database server used by Trimble Quadri.

6.2.1.2 Integrated with Active Directory User Accounts The intention behind the strategy to use Active Directory as source for user accounts is to allow customers to establish a Trimble Quadri that utilize the most of user account information already managed by their organization. In this configuration, a LDAP connection from the database server to Active Directory is established. A configurable filter makes only applicable users available for Trimble Quadri.

6.2.2 Authorization from Quadri Clients The Authorization for requests from Quadri Clients are independently of the selected user account configuration. Authenticated users are authorized to manipulate tasks and objects trough those projects that they are member of. Users who have the system role “Project Admin” can handle the membership to a project in any Quadri Client. Business logic implemented in the Trimble Quadri Application Server handle the authorization policy for Quadri Clients.

6.2.3 Authorization Trimble Quadri Model Manager Authorization for requests from Trimble Quadri Model Manager are, in contrast to Quadri Clients, dependent of the selected user account configuration. When configured with embedded user accounts one of the tasks Performed with Trimble Quadri Model Manager is to manage the user accounts. In this configuration, only one specific user-ID is authorized to use Trimble Quadri Model Manager. This specific user-id is authorized to manipulate any user account and any model properties. When configured with Active Directory integration, management of user accounts are independently of Trimble Quadri and Trimble Quadri Model Manager. When configured with Active Directory integration, users with membership in a certain user group defined inside Active Directory, is authorized to manipulate any model properties.

Trimble Quadri System Overview On Premise Environments 13

13

6.2.4 Authentication from Quadri Clients When configured with embedded user accounts the authentication method used is HTTP Digest Authentication with validation against digests stored in a table in the Quadri Database. When configured with Active Directory integration users are authenticated with integrated windows authentication.

6.2.5 Authentication from Trimble Quadri Model Manager (QMM) When configured with embedded user accounts, authentication for QMM is handled as what is known as Forms Authentication. The credentials, username and password, are conveyed to the request as HTML-form. When QMM is used on computers located in a public network it is recommended to configure the connection link to Trimble Quadri so that it requires the use of HTTPS. When configured with Active Directory integration users are authenticated with integrated windows authentication.

6.3 Data Back-up and Restoration

6.3.1 Integrated data back-up Trimble Quadri has an integrated back-up functionality that performs scheduled back-up of the database. This back-up is mainly designed to support human error recovery of one model for a limited time period.

Figure 10 Integrated scheduled hot data backup

The integrated data back-up is scheduled by Windows Task Scheduler, and as default:

1. performed every 24 hour

2. back-up files are recycled every 7th day

Trimble Quadri System Overview On Premise Environments 14

14

This data back-up is a hot back-up, performed while the database is running. It does not block normal use of Trimble Quadri and it even captures changes that occur while the back-up is running. The database content from one back-up is delivered as a file collection stored on a specified disk. There is one file folder for each scheduled data back-up.

6.3.2 Standard data back-up In the context of Trimble Quadri there are mainly two purposes for this back-up process:

1. Support human error recovery of one model for a longer time period than the time period covered by the online data back-up files from the integrated data back-up.

2. Ensure that the whole content of the Trimble Quadri database can be reconstructed after a system failure / disaster.

Figure 11 Standard data backup system

To fulfil these two requirements it is assumed that a standard back-up process is tailored so that the files from the integrated hot data back-up process are included. To ensure that this data back-up contains the expected data, this process must be scheduled so that it runs after the integrated hot data back-up.

6.4 Restoration Restore operations in Trimble Quadri is dependent of the auxiliary database instance. This database instance runs on the same computer as the production database instance. It starts automatically at the beginning of a restore operation and run in parallel with the production database instance. At the end of the restore operation the auxiliary database instance will automatically shut down.

Trimble Quadri System Overview On Premise Environments 15

15

Restore functionality is available from QMM, and is mainly meant for human error recovery of one model. Only one restore operation can be performed at the same time.

6.4.1 Human error recovery from online data back-up files

Figure 12 Restore from online data backup

A set of data back-up files from a given time is used to create an auxiliary database instance. This auxiliary instance will contain a complete copy of the production database as it was seen by the back-up system at the selected time. The database schema that represents the selected model to restore is used to completely overwrite the current version in the production database.

Trimble Quadri System Overview On Premise Environments 16

16

6.4.2 Human error recovery from offline data back-up files

Figure 13 Restore from external backup medium

From a technically point of view the only difference here is that the back-up files must be restored from the back-up medium before the Trimble Quadri supported restore operation is started. The files restored from the back-up medium must be restored to a disk available from the computer that runs Trimble Quadri. Trimble Quadri takes those files, create an auxiliary database instance and overwrite the current model in the production database.

Trimble Quadri System Overview On Premise Environments 17

17

Trimble Solutions Sandvika AS Leif Tronstads plass 4 1337 Sandvika Norway +47 67 81 70 00 Phone www.novapoint.no

Trimble Solutions Gothenburg AB Kungsgatan 56 411 08 Göteborg Sverige +4631-700 18 30 Phone www.novapoint.se

Trimble Solutions Aarhus AS Hedeager 3, 1. sal 8200 Aarhus N Danmark +45 89 30 47 50 Phone www.novapoint.dk

© 2019, Trimble Inc. All rights reserved. Trimble, the Globe & Triangle logo are trademarks of Trimble Inc., registered in the United States and in other countries. All other trademarks are the property of their respective owners.