User Manual

Network Security Controls
3
27
Siemens Application Note
Smart Infrastructure
3.2.2 Client/Server inside the Customer Network
Intended Use Case
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 by standard IT security mechanisms like certificates.
Figure 8: Client/Server inside the Customer Network.
Customer IT – Server Backbone
Customer IT – Local Office
DCC – Control Room
Customer IT - DMZ
DCC – Server Backbone
DCC – Subsystem nDCC – FS20 DCC – System One
FS20 System One Cameras
DCC – Subsystem m
VMS
DCC – Sipass
Sipass
DCC – Desigo PX
Desigo PX
DCC – SPC
Cameras
DCC Server
WinCC OA
MS SQL
Tomcat
DCC Client
BIRT
IIS
DCC WSI
DCC Server
WinCC OA
DCC FEP
WinCC OA
DCC Client
HTML5
DCC Client
HTML5
DCC Client
HTML5
DCC Client
HTML5
MS SQL
BIRT
Tomcat
IIS
DCC WSI
Firewall Firewall Firewall Firewall FirewallFirewallFirewall
Firewall Firewall
Firewall
Firewall
Firewall
Figure 9: Local Network.
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
Windows App 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.