Skip to content
English
More support
Contact us
  • There are no suggestions because the search field is empty.

portier® vision – System Requirements & Performance Guidelines

In order for portier® vision to be operated reliably and with optimal performance for locking system and key management, the following system requirements must be observed. Actual performance largely depends on server capacity, database configuration, and network latency.

1. Typical Deployment Scenarios

1.1 Small Local Installation (Single Site)

  • Single office environment

  • Up to approximately 3–5 concurrent users

  • Database and clients within the same LAN

  • No WAN access required

Recommended database:

  • Firebird 4.0 or Microsoft SQL Server

This scenario is suitable for smaller installations with limited concurrency.

1.2 Shared VM / Terminal Server Deployment

  • Multiple users access portier® vision via Remote Desktop (RDS)

  • Application runs centrally on a Windows Server

  • Database hosted on a separate dedicated server (recommended)

This setup reduces WAN latency impact and centralizes system management.

1.3 Multi-Site / WAN Deployment

  • Clients connect directly to Microsoft SQL Server over LAN or WAN

  • Dedicated SQL Server required

  • Network latency significantly influences performance

Recommended database:

  • Microsoft SQL Server 2019 / 2022 Standard or Enterprise

For WAN environments, proper SQL Server sizing and low latency are essential for optimal responsiveness.

2. Client System Requirements

portier® vision can be operated on physical workstations or virtual machines.
Performance depends not only on the client hardware but also on database server performance and network latency.

2.1 Dedicated Client (Physical PC or Single-User VM)

Recommended configuration:

 
 
 

Component

 

Requirement

 

Operating System

Windows 11 (Windows 10 supported)

CPU

4 virtual cores (or equivalent physical cores)

RAM

8 GB minimum, 16 GB recommended

Storage

SSD with at least 10 GB free space
 
 
 

Notes

  • 8 GB RAM is technically sufficient for running portier® vision.

  • 16 GB RAM is recommended for typical office environments where additional applications (e.g., Outlook, Teams, web browser, Excel) are running simultaneously.

  • For very large locking plans, extensive data views, or heavy multitasking, 32 GB RAM may improve responsiveness.

2.2 Shared VM / Terminal Server (RDS)

When multiple users access portier® vision via Remote Desktop on a shared Windows Server, system resources must be sized according to the number of concurrent users.

Base configuration:

  • 4 vCPU

  • 16 GB RAM

  • SSD storage

Scaling guidance:

  • Add approximately 2 GB RAM per concurrent user

  • Increase CPU resources depending on simultaneous active usage

Resource requirements depend on workload intensity and parallel user activity.

2.3 Virtualization Considerations

When operating in virtualized environments (Azure, VMware, Hyper-V, etc.):

  • Ensure sufficient dedicated CPU and RAM resources.

  • Avoid heavy CPU or memory overcommitment.

  • Use SSD-backed storage for optimal responsiveness.

Insufficient host resources or high contention on the virtualization layer may negatively affect application performance, even if the VM meets the listed specifications.

3. Database Requirements

3.1 Firebird 4.0 (Small Installations Only)

Intended for:

  • Single-site environments

  • Up to approximately 3–5 concurrent users

  • LAN access only

Recommended configuration:

 
 
 

Component

 

Recommendation

 

CPU

2–4 cores

RAM

4–8 GB

Storage

SSD
 
 
 

Firebird is not recommended for WAN or multi-site deployments.

3.2 Microsoft SQL Server (Recommended)

Supported versions:

  • SQL Server 2019 Standard

  • SQL Server 2022 Standard

  • SQL Server 2022 Enterprise

Up to 15 Concurrent Users

  • 4–6 CPU cores

  • 16 GB RAM

  • SSD storage

15+ Concurrent Users

  • 8+ CPU cores

  • 32+ GB RAM

  • NVMe recommended

Mandatory SQL Server Configuration

  • SQL Server must run on a dedicated server or VM and must not share resources with terminal services.

  • Maximum server memory must be explicitly configured to prevent operating system memory starvation.

  • TempDB must be placed on SSD or NVMe storage to support sorting and temporary operations efficiently.

  • Regular maintenance must be implemented, including index maintenance, statistics updates, and scheduled backups.

4. Network Performance & Latency

portier® Vision 5 performs frequent database interactions, especially during application startup and large data operations.
Network latency directly affects perceived responsiveness.

 
 
 

Latency

 

Expected Behavior

 

< 5 ms

Excellent performance

5–20 ms

Very good

20–40 ms

Noticeable delay during large operations

> 40 ms

Performance degradation likely
 
 
 

Even when bandwidth is sufficient, higher round-trip latency increases the total response time of database-intensive operations.

WAN Deployment Guidance

In WAN environments:

  • Place the application and SQL Server as close as possible within the network topology.

  • Minimize round-trip latency between client and database server.

  • Ensure the SQL Server is properly sized and hosted on low-latency storage.

Higher latency combined with insufficient SQL Server resources may significantly impact overall responsiveness.

5. Dependency, Internet Connectivity & Firewall

5.1 Network Ports

The following outbound connections must be allowed:

Database Communication

  • TCP port 1433 – Microsoft SQL Server

Secure Communication

  • TCP port 443 – HTTPS

5.2 Domains to Whitelist

The following domains must be accessible from client machines and/or server environments:

Blocking these domains may affect licensing, subscription validation, or email-related functionality.

5.3 Database Setup and ODBC Driver Requirement (SQL Server)

portier® Vision requires the latest supported Microsoft ODBC Driver for SQL Server.

Requirement:

  • Install the current Microsoft ODBC Driver for SQL Server on all client machines and/or terminal servers.

  • Ensure the driver version is compatible with the installed SQL Server version.

  • Verify that TCP/IP protocol is enabled in SQL Server Configuration Manager.

  • Confirm that the SQL Server instance is configured to accept remote connections (if applicable).

Outdated ODBC drivers may cause:

  • Connection instability

  • Authentication issues

  • Reduced performance

The Microsoft ODBC Driver can be downloaded from the official Microsoft website.

5.4 WebView2 Dependency

portier® Vision uses Microsoft Edge WebView2 for embedded web-based components.

WebView2 is typically included in:

  • Windows 11

  • Windows Server (standard installations)

However, in some restricted or minimal VM configurations, WebView2 may not be installed or may be disabled by policy.

If WebView2 is not available, it must be installed manually:

Microsoft Edge WebView2 | Microsoft Edge Developer

Ensure that WebView2 runtime installation is permitted by group policy and endpoint security settings.

Performance Note

Systems that meet only the minimum hardware specifications may operate correctly but may show reduced responsiveness under higher concurrency, intensive data operations, or WAN conditions.

For multi-user or multi-site deployments, a properly sized and dedicated SQL Server environment is recommended to ensure stable and predictable performance. Storage performance, particularly for the SQL Server transaction log and TempDB, can have a significant impact on overall responsiveness.

Application performance depends on several factors, including:

  • Database server resources

  • Storage latency

  • Network round-trip time

  • Concurrent user activity

  • Database configuration and maintenance