User Manual

Management platform
Installation, setup and engineering
16
216 | 351 CM110664en_07
for Desigo CC. The operating state of Desigo CC, the number of seats, the point count, and all functions are
controlled through the LMU. Each Desigo CC management platform must be licensed locally. Licenses can
be activated, repaired, returned and renewed through the LMU.
After you install the LMU, you must activate the Desigo CC licenses using the following licensing methods:
● Online: Licensing carried out via the internet or intranet on the back office license server.
● Certificate/Dongle (including remote dongle engineering): Licensing carried out via certificate files
representing the license.
– For Dongle-bound licenses, dongles and licenses can be obtained individually and subsequently tied
to each other and loaded onto the PC.
– Engineering licenses are always dongle-bound. Where a physical connection of the dongle to the PC
is not possible, e.g., during a remote support session, the engineering license can still be used for a
limited time.
● Manual: Manually returning a license based on XML request/response files.
See
Desigo CC Installation Manual (A6V10376166).
System Management Console (SMC)
The Desigo CC server hosts the System Management Console (SMC), a stand-alone tool which is installed
on the main server only, and can only be launched locally. Once Desigo CC is installed successfully, the
field engineers must first perform the typical system administration operations, such as configuring system
users, projects, and history database in the SMC, before being able to launch a Desigo CC client.
Profiles, schemas and templates
Client profiles define the appearance and behavior of the system functions involved in event management,
such as Summary Bar, Event List, Event Detail Bar, event filters, and event treatment. Every project
template has a matching client profile, and every client profile has a matching event schema. To a ensure a
consistent configuration, the project template, the client profile and the event schema must match.
Subsystem integration
Representative data points in Desigo CC can be created manually, imported through data exchange files, or
uploaded through a selective auto-discovery mechanism depending on the type of system being connected.
A unique, extensible object modeling approach allows Desigo CC to normalize information brought in
through any interface, and to provide the same look, feel, and operation through a common set of
applications, without concern for the source of the data.
Desigo CC lets you configure connected subsystems directly and perform typical automation station
functions, such as scheduling and event generation, at the management platform for connected systems
that do not support those functions directly.
Desigo CC supports the following subsystems:
● Desigo building automation system
● Desigo room automation system
● Siclimat-X
● Sinteso Fire Safety System
● Sinteso Fire Safety System
● Intrunet Intrusion System
● Video through Milestone Video Management System
● Mass Notification System (see MNS documentation)
● Third-party Building Automation and Fire Safety systems based on BACnet/IP
● Third-party subsystems through OPC
● Third-party subsystems through Modbus/IP
● Integration through SNMP
● APOGEE Building Automation system
● XNET FireFinder XLS and MXL fire safety systems
● Desigo Fire Safety FS20 UL systems
Auto discovery
Auto discovery lets you discover and import devices, which are already on the network, into Desigo CC. You
can set filters and detect your devices on the network, which then display in the System Browser. You
would typically use this method for existing jobs, where field panels are already installed and online.
OPC server