What's covered by the Desigo tools?

The Desigo tools let you design, document and maintain Desigo systems, that is, you design and document technical configurations and programs for the Desigo system.

What's not covered by the Desigo tools?

The following processes and products are covered locally by SSP or VAPs and not by the Desigo tools:

  • Sales: Offer preparation and tracking
  • Planning/Engineering: Network planning and design, floor plan, cabling, designing control cabinets, designing electrical wiring diagrams, creating rating plates, validating pharma systems
  • Project management: Ordering devices, project planning, claim management, project task planning
  • Service management: Service database for devices, network planning, remote service platform

Sales support

Desigo Configuration Module (DCM) is in phase-out from 2023-10-31 until the end of 2026.

Desigo Configuration Module (DCM) supports the calculation of the Desigo configuration for the sales process.

You can verify if:

  • The Desigo configuration is technically correct, that is, the solution that was sold can be implemented with Desigo
  • The system limits have been taken into account, that is, the number of possible devices and functions in the network is verified
  • The quantity is correct, that is, correct device types for the automation and room functions, field devices, accessories and licenses
  • Services are correctly calculated
  • The design for the review with the customer is well documented
  • Prices are correct (regional companies can add their prices to the DCM database)

Configuration and programming

The configuration and programming flexibility of system devices depends on the product or product family. Some devices contain preloaded applications and connections only to specific periphery device types.

You can configure and parameterize the devices offline or partly online with a configuration tool. You can replace the preloaded applications on some devices in the project.

You can freely program some devices. To create loadable applications, you can use libraries to create project-specific solutions.

Degree of standardization and flexibility

The table below shows engineering methods by degree of standardization and flexibility:

  • Level A: High degree of standardization with predetermined flexibility
  • ...
  • Level E: Low degree of standardization with very high flexibility

Solutions with a high degree of standardization

Solutions with a high degree of standardization are:

  • More efficient to configure and commission than freely programmed solutions
  • Easier to maintain, because the functions are verified and well documented

Solutions with a low degree of standardization

Solutions with a low degree of standardization, that is, freely programmed solutions, are:

  • More laborious to create and document
  • More error-prone than verified solutions
  • Harder to maintain in the service phase, because they do not adhere to the standard and are often not as well documented as verified solutions

The intermediate levels B, C and D allow you to choose a solution with the right balance of flexibility and standardization.

Desigo PX:






Engineering effort



Solution Browser in XWP

Locked CAS solutions





Solution Configurator in CFC, CAS library

CAS solutions, aggregates, components

AHU10, fan, valve




CFC programming, CFC library

Charts, blocks

CAS library with charts


High flexibility


CFC programming, solution creation

Charts, blocks, LMU (Library Maintenance Utility), simulation

RC library




CFC programming, SCL block creation

CFC, SCL, simulation, LMU, development tools

HQ library


Desigo room automation:






Engineering effort



Application selection

Application type

Standard, VAV




Application assembling

Application modules

Blinds, radiator, lighting




Application creation




High flexibility


Application engineering


Regional specialties





All levels



Level A

You can create solutions with the available options and variants with little prior training and detailed knowledge.

The device is preconfigured and can be configured for the specific project. The functions are predefined. You can configure the application using options and variants. You can set the function of the application and the field devices with a configuration tool. The solutions are delivered by HQ as verified and documented solutions.

Level B

The device can be configured for the specific project. You can create the application using library elements. This is a major advantage of the Desigo application libraries. Even though assembling a solution is relatively easy, the functions of the solutions are powerful. Using many options and variants, you can customize the standard solutions to your project requirements.

Level C

The device is preconfigured and can be configured for the specific project. You can create the application using library elements. You can program the application with default function modules with predefined interfaces. You can program using simple programming functions.

Level D

This level offers full flexibility, but requires detailed knowledge of the application's structure, the programming tools, BACnet and the Desigo system functions. You can program in CFC (Continuous Function Chart) with basic function modules. You can use all available programming functions. You must ensure that the programs you develop fit together regarding how they are run, priorities, auto-connecting in the tool, interface usage, etc.

Level E

This level offers full flexibility, but requires detailed knowledge of the application's structure and the programming tools. You must ensure that the functions of the program work. You must ensure that the 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 the web interface, 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
    • Control of project data access, through login data
    • Checking in and out project parts for working on engineering data in parallel