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
Access and security
16
214 | 351 CM110664en_07
30 days is exceeded, then the server shuts down. Unless new licenses are made available, after a manual
restart the system again goes into courtesy-mode exceeding and shut down.
Any unauthorized attempt to modify system license data directly in the database (e.g., changing the
remaining time of a specific license mode) shuts down the system.
16.3 Access and security
User management
User privileges can be assigned to users and to workstations, allowing users to be granted the same access
from everywhere or different access depending where they're logged on. The user interface displays only
elements, such as menus, buttons, list items, tree nodes, where the user has at least read access.
Access privileges can be assigned to resources/groups, such as workstations, features, applications,
system objects, system object properties and logical groups of these resources.
User authorization
User access rights in Desigo CC are determined by four main factors:
● The system must know the user (authentication).
● The user must be assigned to a user group.
● The user must have the appropriate application rights.
● The user must have the appropriate scope rights.
If all of these conditions are met, the user can log on to Desigo CC, and read/write objects and execute
tasks, depending on the assigned rights.
See
Desigo CC Engineering Manual
(A6V10415473).
Scopes
Scope is the general term for specific object access in Desigo CC. A scope segments and implements
certain rules for the user role in the project. A user only sees the area of the building assigned to him, e.g.,
pumps, receives only alarms from this area in the event of an emergency and can only acknowledge those
alarms. If an emergency occurs in an area that is not in the scope of this user, e.g., ventilators, the user
does not receive an alarm about this event.
Communication security
In general, communication channels are non-encrypted due to performance reasons. Exceptions are
communication channels for file transfer using web and video transfer. Sensitive data (passwords during
authentication or user management configuration) is transferred as encrypted message content.
Wireless input devices (especially keyboards) use radio transmission that is often not or inadequately
cryptographically protected. Even from greater distances, it is possible to listen in or even plant external
data in the system.
We recommend that you do not use wireless input devices. If you must use wireless input devices, use only
devices with proven encryption.
Communication ports and protocols
Which ports are used depends on the actual deployment and subsystem integration of the whole system.
See
Desigo CC System Description
(A6V10415500).
16.4 Event management
Desigo CC lets you quickly, easily, and accurately respond to any event.
Summary Bar
The Summary Bar contains a summary of the events occurring in the system and lets you quickly access
functions, such as the Event List. It also displays information, such as the system status, the logged in
user, etc. Depending on the client profile in use, the Summary Bar can be docked on the desktop or freely
opened and closed as needed.
Event List
The Event List provides a complete and easily filtered list of events under control of Desigo CC. When the
Event List is expanded, it clearly shows each event source, severity, current status, custom messages and
suggested action steps through the use of text, color, and icon representations. You can acknowledge,
silence, and reset alarms from the Event List.