User Manual

Desigo workflow, tools and programming
Main tasks
4
40 | 351 CM110664en_07
programs you develop fit together with all elements in the library and that they are well tested and
documented. You must take care of the compatibility, the versioning and the library packaging.
Creating a technical hierarchy
The technical hierarchy is the BACnet view on the Desigo system. It is based on the plant-related structure
in the building. This hierarchy is defined during engineering. In special cases, if the customer requires it,
the technical hierarchy can be built according to a plant-specific structure defined by the customer (user
designation).
This lets, e.g., the customer view the building in Desigo CC according to this structure:
● Building topology (area, building, floor, plant, plant section, etc.)
● Naming in the system (names according to technical hierarchy, user designation or free designation)
Creating loadable components for the automation stations
The result of the engineering are loadable configurations:
● Configuration of the automation station: Network configuration (IP, LON, MS TP addresses), BACnet
configuration (BACnet name and BACnet ID)
● Application: I/O configuration and setting parameters or program (for programmable automation
stations)
● Operating language: When you load the configuration, the operating language for the generic operation
is also loaded
● Firmware: For system upgrade or bug fixing
Creating the configuration of operation
The system devices can be operated locally, over the web, on a touch panel or in Desigo CC. Operations
can either be generic (without additional engineering) or dedicated (with additional engineering via
favorites or operating graphics).
● The generic operation is based on the technical hierarchy. It must not be engineered.
● The room operation can be configured.
● Favorites are a simple grouping of operable elements in a summarized view. This view can also be
generic, e.g., as a favorite in ABT-SSA, or it can be engineered, e.g., as a favorite for PXM20.
● The graphic operation must be engineered.
Installation, test and commissioning
An I/O configuration must be loaded for the point test. An application program is not always loaded with
the configuration.
You can carry out a point test with an application program if the application program can be turned off
during the point test. This way you can carry out a test if, e.g., a central security function would prohibit you
from operating the I/O, e.g., if a central security function does not allow lowering the blinds.
The test protocol can store which points have passed the test and which points have an error.
Creating local documentation and project documentation
The tools have two types of documentation:
● Local documents (work documents, simple templates, Excel exports) can be used to, e.g., verify results.
You can, e.g., export them to Excel and add additional data to them.
● Project documentation (template with logo, author, table of contents, etc.) can be attached to the
customer documentation either in printed form or as a PDF.
Managing project data
You can manage project data in three ways:
● Local project data management - You can save project data locally, that is, on the local computer or on
a share.
● Project data backup - You can create project data archives to, e.g., locally save the intermediate status
of engineering data.
● Project data on the Branch Office Server (BOS) - You can store project data on a BOS. This allows:
– Data storage on a server, incl. data backup