There are four views:
- Technical view
- User view
- System view
- Program view
The technical view illustrates the technical building services equipment, such as HVAC systems and associated elements, in the building automation and control system. The technical view is always present and can be used as a substitute for the user view if the user does not have his own user designation.
Freely defined and structural user view
The user view is optional in a project. The user view is based on user designations, e.g.: PL7’FL3’ELE”HEAT.STPT
The structure and syntax of the user designations can be defined for each specific project and customer. Example of a structure: Installation/building/room/plant element/signal
User view via the User Designation (UD)
Desigo supports different user views, depending on the application:
In Xworks Plus (XWP) a User Designation (UD) can be entered for function blocks or compounds in addition to the Technical Designation (TD) and description. This entry is carried through in the system and can be evaluated by clients. The UD allows customers to use their own preferred designations for the plant without changing the technical structure. The UD can be used in the management platform in addition to the TD. The detailed view in the PXM20 operator units shows the UD as information.
User Designation for Desigo room automation
You can define the user view for Desigo room automation as follows:
- Define a structure for the user view
- Copy Desigo room automation objects into the user view
- Define UDs that can be used as object names
The system view shows the standard system hierarchy (BACnet view):
- Network, topology
- Device and third-party device view
- Flat representation (no hierarchy) of all BACnet objects in one device
The system view provides access to all BACnet devices (including third-party BACnet devices) and all BACnet objects. A third-party client displays this view of a PX device.
The system view is used in the PXM20 only for third-party devices.
The engineering and program view corresponds to the XWP/ABT view. The structure is matched to the automation station. Within an automation station, the view is program oriented: nested CFC charts (compounds) and function block instances.
Views and users
The views reflect the differing needs of their users.
Operator (without technical training)
Operator (with technical training)
Engineer (Desigo CC), User (PXM...)
Service engineer, Siemens service engineer
Flexible object name / device ID engineering
You can flexibly generate the object name during engineering in XWP. This is called the Free Designation (FD). However, the FD has no inherent hierarchical structure, which makes it tedious to engineer and lowers its helpfulness to orientate in larger buildings. It should thus be considered as a naming type for very special purposes only.
Flexible object name engineering causes a greater engineering effort and must thus be requested specifically by the customer.
Each BACnet object has an object name for identification on the BACnet network. This object name must be unique within the automation station. The Technical Designation (TD) is used as default for the object names. The TD is a technical identifier and is used to identify the plant and associated elements in the technical view.
You can select how the object name is created for each standard BACnet object. This especially applies to BACnet multivendor projects, where a special object name structure is required.
Defaults and rules
The following defaults and rules apply when you engineer the object name in the XWP Hierarchy Viewer:
- The Free Designation (FD) can be max.69 characters.
- Only ISO-Latin-1 code points from [32..127] and [160..255] may be used. This excludes all characters from [0..31] and [128..159]. These ISO-Latin-1 code points are identical to Unicode code points.
- No lead or post blanks  may exist and object names containing only blank characters are not possible.
The FD values and the object name selection are transferred automatically to the automation station or exported to the management platform during compiling or loading in the CFC.
The CFC Editor checks during compilation if the object name is unique for each automation station under the following rules:
- The same resulting object name may exist only once per automation station. This also applies to the device object that must be unique in the BACnet internetwork.
- The resulting object name may not correspond to a TD of another object in a Device. The TD is used to resolve BACnet references.
Exceptions for object name assignment
Object names cannot be engineered in CFC charts or compounds. These elements always define the TD and the object name is always the same as the TD.
Special blocks, such as Heatcurve and Discipline I/Os generate reduced value objects in the background whose object name per default is the TD during compilation.
Free definition of the Device ID
The device ID (the object ID of the device object) can be freely defined. Range: 0…4'194'303