User Manual
Table Of Contents
- 1 Cyber security disclaimer
- 2 Preconditions of this document
- 3 System overview
- 4 Desigo workflow, tools and programming
- 4.1 Coverage of the technical process
- 4.2 Coverage of the system
- 4.3 Main tasks
- 4.4 Tools for different roles
- 4.5 Working with libraries
- 4.6 Working in parallel and subcontracting
- 4.7 Workflow for primary systems
- 4.8 Workflow for room automation classic
- 4.9 Workflow for Desigo room automation
- 4.10 Desigo Configuration Module (DCM)
- 4.11 Desigo Xworks Plus (XWP)
- 4.12 Desigo Automation Building Tool (ABT)
- 4.13 Programming in D-MAP
- 5 Control concept
- 6 Technical view
- 7 Global objects and functions
- 8 Events and COV reporting
- 9 Alarm management
- 9.1 Alarm sources
- 9.2 Alarm example
- 9.3 Effects of BACnet properties on alarm response
- 9.4 Alarm response of the function blocks
- 9.5 Alarm functions
- 9.6 Alarm management by notification class
- 9.7 Alarm routing over the network
- 9.8 Alarm queuing
- 9.9 Common alarms
- 9.10 Alarm suppression
- 9.11 Alarm message texts
- 10 Calendars and schedulers
- 11 Trending
- 12 Reports
- 13 Data storage
- 14 Network architecture
- 15 Remote access
- 16 Management platform
- 17 Desigo Control Point
- 18 Automation stations
- 19 Logical I/O blocks
- 20 Room automation
- 21 Desigo Open
- 22 System configuration
- 22.1 Technical limits and limit values
- 22.2 Maximum number of elements in a network area
- 22.3 Desigo room automation system function group limits
- 22.4 Devices
- 22.4.1 PXC..D automation stations / system controllers
- 22.4.2 LonWorks system controllers
- 22.4.3 Automation stations with LonWorks integration
- 22.4.4 PX Open integration (PXC001.D/-E.D)
- 22.4.5 PX Open integration (PXC001.D/-E.D + PXA40-RS1)
- 22.4.6 PX Open integration (PXC001.D/-E.D + PXA40-RS2)
- 22.4.7 PX KNX integration (PXC001.D/-E.D)
- 22.4.8 TX Open integration (TXI1/2/2-S.OPEN)
- 22.4.9 Number of data points on Desigo room automation stations
- 22.4.10 Number of data points for PXC3
- 22.4.11 Number of data points for DXR1
- 22.4.12 Number of data points for DXR2
- 22.4.13 PXM20 operator unit
- 22.4.14 PXM10 operator unit
- 22.4.15 Desigo Control Point
- 22.4.16 PXG3.L and PXG3.M BACnet routers
- 22.4.17 SX OPC
- 22.4.18 Desigo CC
- 22.4.19 Desigo Insight
- 22.4.20 Desigo Xworks Plus (XWP)
- 22.4.21 Desigo Automation Building Tool (ABT)
- 22.5 Applications
- 23 Compatibility
- 23.1 Desigo version compatibility definition
- 23.2 Desigo system compatibility basics
- 23.2.1 Compatibility with BACnet standard
- 23.2.2 Compatibility with operating systems
- 23.2.3 Compatibility with SQL servers
- 23.2.4 Compatibility with Microsoft Office
- 23.2.5 Compatibility with web browsers
- 23.2.6 Compatibility with ABT Go
- 23.2.7 Compatibility with VMware (virtual infrastructure)
- 23.2.8 Compatibility of software/libraries on the same PC
- 23.2.9 Hardware and firmware compatibility
- 23.2.10 Backward compatibility
- 23.2.11 Engineering compatibility
- 23.2.12 Compatibility with Desigo Configuration Module (DCM)
- 23.2.13 Compatibility with Desigo PX / Desigo room automation
- 23.2.14 Compatibility with Desigo RX tool
- 23.2.15 Compatibility with TX-I/O
- 23.2.16 Compatibility with TX Open
- 23.3 Desigo Control Point
- 23.4 Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3
- 23.5 Siemens WEoF clients
- 23.6 Migration compatibility
- 23.7 Hardware requirements of Desigo software products
- 24 Desigo PXC4 and PXC5
- 25 Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5
Management platform
Technical details
16
CM110664en_07 209 | 351
Desigo CC is a flexible, full client-server architecture allowing scalability from small and medium to large
and complex systems. The platform provides customizable and market-specific distributions.
Desigo CC can be installed on one single computer, with full server and client functionality. Furthermore,
Installed, Web, and Windows App Clients can also be added on separate hardware. Additional system
connections can be made through systems installed with Desigo CC Front End Processors (FEP)
configurations. Web interfaces provide the customer an increased flexibility for operation and future
extensions, e.g. mobile applications for tablets and smart phones.
Main server
The main server contains the project database and the software that monitors and commands the system
network. Clients connect to this server to monitor and control the facility. If the same computer runs
Microsoft IIS, the installation provides web clients with access to the facility. The Desigo CC server
installation always includes an installed client with a user interface for monitoring and controlling the
facility. The main server has interface connections to the field (either directly or using FEP) and provides a
centralized database and other services to the connected clients. The main server can support a number of
clients that are connected using a network (LAN) or Intranet (WAN).
Installed client
The Installed Client is typically used for operators who are focused entirely on monitoring and managing
building systems. In this configuration, software components used for event management are locked in
place and cannot be moved or covered by other applications. This ensures that critical events are never
missed or hidden. Installed Clients can optionally be configured to run in a closed mode where only Desigo
CC and other specifically identified applications are allowed to run. In closed mode, the workstation is
dedicated to running Desigo CC, with access to the Start menu or other operating system and customer
applications available only to administrative users.
Web client (browser client)
The web client is deployed on the intranet with full trust and allows access to local resources. The system
runs in the Internet Explorer browser (using HTTP or HTTPS as communication protocol) and is
downloaded on demand each time the user launches the system as web application. When working in a
browser, you can have the same capabilities as those working on an Installed Client, or can be restricted to
have different access when connected remotely.
As web clients require low latency and high network bandwidth, they are appropriate for intranet use. We
do not recommend it for internet use.
See
Desigo CC Installing the Web Client Application Certificate
(A6V10415479).
Windows app client (ClickOnce)
The Desigo CC Windows App Client looks like the standard system software, but is a light application that
can be downloaded from the Desigo CC server when connecting through a browser. When the Windows
App Client is downloaded, it runs like any other Windows application on the desktop. It can be launched
from the Start menu, desktop icon, quick-launch toolbar, and so on. This deployment does not require
administrative privileges. The Windows App Client runs in its own pane, without the overhead of the
internet browser application and menus.
Web server
To use the Desigo CC Web and Windows App Clients, you must install the web server. To install the web
server, you must first install Microsoft IIS on the web server computer. Usually the web server is on the
Desigo CC server. It might be located on a separate computer, if the customer's IT department requires the
web server to be installed in a separate controlled environment, or if it is preferred not to use the resources
of the system server for the Microsoft IIS tasks.
The web server lets you to access the system using the intranet and a web browser. You can add only one
web server. It lets you download all files required for the Web Client and Windows App Client environments.
It provides a system web page to access the Web Client, the Windows App Client, and the system