User Manual

Part A: System Overview

System Architecture - How the System is Organized

A6V10415500_en_a_42

Restricted

27 | 53

1.2.2.1 All-In-One (One Seat) System

This is the configuration choice in all cases where only one client is required, and

system size is limited. Management System Server, database service and one

installed client are deployed on the same hardware platform, which can be physical

or virtual. The field networks are connected directly to the Management System

Server.

1.2.2.2 Client/Server inside the Customer Network

This is the configuration choice for the cases where multiple Installed Clients,

connected via a dedicated or shared local area network (LAN) are required. Web

connectivity is not required. Communication between the key components can be

secured through standard IT security mechanisms like certificates.

The Management System Server, database service and the first installed client are

deployed on the same hardware platform, which can be physical or virtual. If Web,

Windows App or Flex Clients are required, the Web Server can also be installed on

the same platform.

Field networks are connected directly to the Management System Server.

FEP can be used to better balance the communication load or to better adapt to

the distribution of the field systems. A typical case for FEP usage would be a

system with multiple remote sites and one central control location.

Installed and Windows App Clients are connected to the server via the system

LAN.

The size of the field system and the number of clients that can be supported by this

configuration depend on the server hardware configuration.

➜ See Part B: System Dimensioning [➙ 31].

1.2.2.3 Client/Server with Internet Access

This is the configuration choice for the cases in which multiple Installed Clients,

connected via a dedicated or shared LAN are required, but web connectivity is also

required to allow remote access via a Desigo CC Web or Flex Client or provide