s

DesigoTM
Automation level migration
Engineering manual

CM110776en_05
14.09.2011 For internal use only Building Technologies
Siemens Switzerland Ltd
Infrastructure & Cities Sector
Building Technologies Division
Gubelstrasse 22
6301 Zug
Schweiz
Tel. +41 41-724 24 24 © 2009-2011 Siemens Switzerland Ltd
www.siemens.com/sbt Subject to change

2 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 14.09.2011
 Contents
1 About this document ..............................................................................6
1.1 Revision history.........................................................................................6
1.2 Reference documents ...............................................................................6
1.3 Before you start.........................................................................................7
1.3.1 Trademarks ...............................................................................................7
1.3.2 Copyright...................................................................................................7
1.3.3 Quality assurance .....................................................................................7
1.3.4 Document use/ request to the reader .......................................................7
2 Introduction to migration .......................................................................9
2.1 Recommendations and prerequisites .......................................................9
2.2 Workflow description ...............................................................................10
2.2.1 Workflow overview ..................................................................................10
2.2.2 Step 1: Driver – Migration ....................................................................... 11
2.2.3 Step 2: Information on installed base (IB)............................................... 11
2.2.4 Step 3: Project record .............................................................................12
2.2.5 Step 4: Establish strategy .......................................................................12
2.2.6 Step 5: Project alignment ........................................................................13
2.2.7 Step 6: Project implementation ...............................................................13
2.3 Further information and checklists ..........................................................14
2.4 Attachments / References.......................................................................15
3 Workflow overview and engineering tools.......................................................16
4 321-Workbench, Visonik workflow......................................................18
4.1 Prerequisites for Visonik migration .........................................................18
4.2 Preparations on the project.....................................................................18
4.3 Create a migration project.......................................................................19
4.3.1 Set upload options ..................................................................................19
4.3.2 Create a new migration project in 321-Workbench.................................20
4.4 Acquire Visonik data ...............................................................................21
4.5 Migration settings ....................................................................................23
4.5.1 Map alarm ...............................................................................................23
4.5.2 Map DEL01&10.......................................................................................23
4.5.3 Export/import transformation rules..........................................................24
4.6 Migrate EKL-X process units ..................................................................25
4.6.1 Set Generator options.............................................................................25
4.6.2 Add missing settings for PTM modules ..................................................26
4.7 Merge process units................................................................................34
4.8 Module migration mode ..........................................................................34
4.8.1 Change P-bus connections.....................................................................36
4.9 Interface modules ...................................................................................36
4.10 Visonik PTM migration to TX-I/O modules..............................................37
4.10.1 Migration to Visonik BPS + BIM + TX-I/O modules ................................37
4.10.2 Migration to Desigo PX-50/100/200 + TX-I/O modules ..........................38
4.11 Visonik migration to PX-50/100/200 with PTM ...............................................40
4.11.1 Migration to PX-50/100/200 + PTM ........................................................40
4.12 PXC-50/100/200 mixed PTM and TX-I/O operation ...............................41
4.13 Generate .................................................................................................42

For internal use only 3 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Contents 14.09.2011
 4.13.1 Log window .............................................................................................42
4.13.2 Generate report.......................................................................................43
4.13.3 Generate CDF file ...................................................................................43
4.13.4 Generate IOMD file .................................................................................43
4.14 Evaluate report........................................................................................44
4.14.1 Special cases ..........................................................................................44
5 321-Workbench, Unigyr workflow .......................................................45
5.1 Prerequisites for Unigyr migration...........................................................45
5.2 Update Unigyr project data .....................................................................46
5.3 Access Unigyr data .................................................................................47
5.4 Migration-critical hardware (Unigyr) ........................................................47
5.5 Merge controllers (Unigyr).......................................................................47
5.6 Migrate QD modules (Unigyr) .................................................................48
5.7 Recommended plant Unigyr Desigo....................................................48
5.8 Unigyr migration options .........................................................................49
5.8.1 Migrate to Desigo PXC-64/128-U ...........................................................49
5.8.2 Migration to Desigo PX-50/100/200 with TX-I/O .....................................50
5.8.3 Migration to Desigo PX-50/100/200 with TX-I/O .....................................51
5.9 Generate CDF file and report..................................................................52
5.9.1 Log window .............................................................................................52
5.9.2 Generate report.......................................................................................52
5.9.3 Generate CDF file ...................................................................................53
5.10 Evaluate report........................................................................................53
6 321-Workbench, Integral workflow......................................................54
6.1 Prerequisites for Integral migration.............................................................54
6.1.1 Integral system information .....................................................................54
6.2 Provide access to Integral data...............................................................55
6.2.1 Add automation station to be migrated ...................................................55
6.2.2 Document current RS module time schedules........................................56
6.2.3 Document scheduler in NCRS ................................................................57
6.3 Create a migration project.......................................................................57
6.3.1 Integral project settings ...........................................................................57
6.3.2 Create a new migration project in 321-Workbench.................................58
6.4 Integral migration options........................................................................60
6.4.1 Migrate to PXC NRUD ............................................................................60
6.4.2 Migrate to PXC NRUF.............................................................................63
6.4.3 Migrate to PX RS-bus .............................................................................64
6.5 Generate CDF file and report..................................................................66
6.5.1 Log window .............................................................................................66
6.5.2 Generate report.......................................................................................66
6.5.3 Generate CDF file ...................................................................................67
6.6 Evaluate report........................................................................................67
7 Accessibility of plant ............................................................................68
7.1 Visonik.....................................................................................................68
7.2 Unigyr ......................................................................................................68
7.3 Integral ....................................................................................................68

4 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Contents 14.09.2011
 8 XWORKS plus: Select solution............................................................69
8.1 Create PX application .............................................................................69
8.1.1 Select a solution in XWORKS plus .........................................................69
9 XWORKS plus: Point Configurator mapping .....................................71
9.1 Mapping options......................................................................................72
9.2 Map data points.......................................................................................73
9.2.1 Map data points.......................................................................................73
9.2.2 Feedback mapping .................................................................................74
9.2.3 Multistate mapping ..................................................................................75
9.3 Map trend objects....................................................................................76
9.4 Create data points in Point Configurator.................................................77
9.5 Generate in the CFC...............................................................................78
9.6 Take over parameters .............................................................................79
9.6.1 Data import limitation (Unigyr) ................................................................80
9.6.2 Take over engineering units ....................................................................80
10 XWORKS plus: Revise in the CFC .................................................................81
10.1 Clean up I/O address conflicts in CFC....................................................81
10.1.1 Special note for Integral ..........................................................................81
10.2 Save project data on the BOS ................................................................82
11 Migrate PDM/ADP/CC data ...................................................................83
12 Adapt Desigo Insight ............................................................................84
13 Appendix A ............................................................................................85
13.1 CFC import error messages....................................................................85

For internal use only 5 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Contents 14.09.2011
 1 About this document
1.1 Revision history

Version Date Changes Section Pages

V5.0 06.09.2011 CM110776de_05 Various
Update for Desigo V5. Introduction to
PXX-PBUS extension module.

V4.1 24.02.2010 CM110776en_04 —

Extensions for PTM to TX-I/O module 3, 4,
migration for Unigyr and Visonik, 5, 6,
Integral migration to PXC-NRUD 6,
XWORKS plus Point Configurator 7, 8.
V2.37 15.03.2008 CM110776en_03 —
SP1 Extensions for Integral 5, 6.3
8.9.1, 9.1.1
V2.37 30.03.2007 CM110776en_02 —
Import Visonik data from ETS output 2
Register TX-I/O bus 3.6.2
Generate IOMD file 3.11.3, 5.4.4
V2.36 06.07.2006 CM110776en_01 —
Original V2.36 —

1.2 Reference documents

Ref. Document title Document type Document

number
[1] Automation level migration PDF help CM110774
321-Workbench manual

6 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies About this document 14.09.2011
 1.3 Before you start
1.3.1 Trademarks

The table below lists the third-party trademarks used in this document and their
legal owners. The use of trademarks is subject to international and domestic
provisions of the law.

Trademarks Legal owner

BACnet American National Standard (ANSI/ASHRAE 135-1995)
Microsoft … Microsoft Corporation; see
http://www.microsoft.com/TRADEMARKS/t-mark/nopermit.htm
Windows Microsoft Corporation

All product names listed in the table are registered (®) or not registered (™)
trademarks of the owner listed in the table. We forgo the labeling (e.g. using the
symbols ® and ™) of trademarks for the purposes of legibility based on the
reference in this section.

1.3.2 Copyright

This document may be duplicated and distributed only with the express permission
of Siemens, and may be passed on only to authorized persons or companies with
the required technical knowledge.

1.3.3 Quality assurance

These documents were prepared with great care.

 The contents of all documents are checked at regular intervals.
 All necessary corrections are included in subsequent versions.
 Documents are automatically amended as a consequence of modifications and
corrections to the products described.
Please make sure that you are aware of the latest document revision date.
If you find any lack of clarity while using this document, or if you have any criticisms
or suggestions, please contact your local POC at the nearest branch office.
Addresses for Siemens RCs are available at www.siemens.com/sbt.

1.3.4 Document use/ request to the reader

Before using our products, it is important that you read the documents supplied
with or ordered at the same time as the products (equipment, applications, tools
etc.) carefully and in full.
We assume that persons using our products and documents are authorized and
properly trained and have the requisite technical knowledge to use our products as
intended.

For internal use only 7 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies About this document 14.09.2011
 Additional information on products and applications is available:
 On the intranet (for Siemens employees only) at
https://workspace.sbt.siemens.com/content/00001123/default.aspx
 At your next Siemens branch office www.siemens.com/sbt or at your system
suppliers.
 From the support team in the headquarters fieldsupport-
[email protected] if no local POC is available.

Siemens assumes no liability to the extent allowed under the law for any losses
resulting from a failure to comply with the aforementioned points or for the improper
compliance of the same.

8 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies About this document 14.09.2011
 2 Introduction to migration
This section introduces the methodology associated with handling migration
projects.
The methods described cover:
 Evaluation of possible projects.
 Preparation of migration strategies.
 Plant analysis.
 Workflow optimization.
 Implementation of projects.
 Use of the Desigo Automation Level Migration tools (321-Workbench and DME).

The document is aimed at Service personnel in sales and engineering who

understand the migration business and have already acquired some experience in
this business segment. Ideally, they also have experience with modernization
projects. This allows them to make direct use of the Best Practice described here.
The profit situation in migration projects is increasingly under pressure, and it is
easy to understand why everything possible is done to counteract the erosion of
profits.
The Desigo Automation Level Migration tool is intended to help reduce engineering
time and to import as much know-how as possible from the old system into the new
one. In addition to the tool-based engineering, the available expertise should help
to ensure that the migration process from sales to final handover is organized as
efficiently as possible. Best Practice is the means by which this expertise is to be
transferred.
This document does not deal with the following:
 Strategic selling.
 Acquisition of maintenance contracts.
 Marketing aspects.

These subjects are described in the separate migration manuals. There is also no
detailed discussion of special solutions such as room automation or third-party
integration.
The workflow presented here is based on over 10 years' experience of the
migration business.

2.1 Recommendations and prerequisites

Certain recommendations apply to the implementation and introduction of Best

Practice and of the Desigo Automation Level Migration Tool. Successful
implementation requires an awareness that the migration business is highly
complex and time-consuming. This applies especially to the process of winning a
migration order, and in particular to implementation which is right for the customer.
In order to make a success of this business, migration training is absolutely
essential for both sales and engineering personnel. The training can be devised
independently in the Regional Companies and supplemented by specialists. In the
RCs, the tool specialists must familiarize themselves with the scope of the
migration tool.

For internal use only 9 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Introduction to migration 14.09.2011
 2.2 Workflow description

The workflow for the migration business is highly complex and its effects are not
always immediately identifiable. For this reason, each step must be prepared and
checked with extreme care. The workflow always applies to an entire project. It
often requires extensive resources to correct migration errors. The next sections
describe the procedure step by step, with references to sources of additional
information.
The workflow is divided into 6 steps. Each one should be regarded as an
independent step and should be processed as such. Tasks are defined within each
step, which must be carried out by suitable staff in order to achieve the optimum
results. The more closely Sales, Engineering and the customer work together, the
more successful this will be.
This collaborative approach extends throughout the project processing period. In
the ideal situation, all parties bring their own knowledge and experience to the
support and development of the project.

2.2.1 Workflow overview

The diagram shows the idea handling of a migration project using the ALN
migration tool.

10 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Introduction to migration 14.09.2011
 2.2.2 Step 1: Driver – Migration

The first step is labeled Driver migration, because this is often the initial impetus
for a migration project. Opportunities of this kind must be picked up by the regional
sales organizations and handled accordingly.
The impulse may come from the customer, the engineer or the sales force.
Features:
– Customer enquiries with technical specifications.
– Extensions or building conversion plans.
– Support enquiries.
– Information from technical staff.
– Orders for repairs or spare parts.
– Sales activities, special promotions, customer visits etc.
– Contracting.
– Expositions.

Or, actively driven by sales:

– Analysis of the installed base.
– Follow-up visits to customer sites.
– In-house exhibitions, customer meetings.
Impetus from Product Marketing:
– Product withdrawals / life cycle.
– New developments.
– Special promotions, Migration Plus.
– Maintenance contracts etc.
– New business ideas.

In particular, the information from Product Marketing should be processed with an

appropriate evaluation for the customer and put into practice in suitable ways.
It is incomprehensible for customers when they only discover shortly before the
event, that a product range is to be discontinued. Customers always want the
whole picture in relation to the plans associated with their installed products.
Note
A lack of information makes the migration business extremely difficult, because
customers cannot make plans from one day to the next, and cannot alter their
budgets at short notice.

2.2.3 Step 2: Information on installed base (IB)

The second step is the maintenance of information about the installed base (IB) of
the systems at regional level. The checklist to acquire project data can be used as
a sample IB structure. IB is the heart of the migration business. It is impossible to
actively drive a business without access to all the relevant data.
This information also helps with the evaluation of market opportunities, the
implementation of special promotions, estimates of potential and the control of
sales.
In conjunction with step 1, the control of sales activities clearly involves potential
for the optimization of processes, as well as migration potential. In the IB, all
information from the sales and technical staff can be maintained and used as
required.

For internal use only 11 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Introduction to migration 14.09.2011
 2.2.4 Step 3: Project record

Step 3 is the most important step, because it is here that the foundation stone is
laid for the success or failure of the project.
The main purpose of the project record is:
1. Acquisition of all information, both technical and commercial.
2. Record of the requirements.
3. Record of the ACTUAL status.
4. Procurement of data backups.
The project record phase is an advance investment in the business of the future. At
the same time, it is extremely useful to have more than one iron in the fire,
because customers also take a relatively long time to make up their minds.
This project record applies to the complete project. The work involved only needs
to be done once, and it can be referred to later for further planning if necessary. For
maintenance customers, this record should be mandatory, and be written up during
the first maintenance session. The data recorded for this purpose is saved with the
IB.
The project record must cover the acquisition of all information and the clarification
of any questions. The effect of obtaining information retrospectively is always
negative. Checklists should always be used for analysis, firstly to avoid errors, and
secondly because they refer to important points which are otherwise very easy to
overlook. The lists ask about all points which might be important for migration. The
list can also be used for meeting minutes. The time spent on recording the data
always pays off. Ideally, this data can be recorded when visiting a customer, or
during a maintenance or service call. A digital camera is useful when recording the
plant. In this way, it is not usually necessary, for example, for the control panel
manufacturer to come to site again to prepare an offer.

Note This information is absolutely essential for use of the AL Migration tool.
The AL Migration tool (321-Workbench) also defines the bill of quantities for the
required hardware, thereby providing a fundamental basis for calculation.

2.2.5 Step 4: Establish strategy

The strategy should always be based on a "top down" approach. This assumes
that first the management level followed by the automation level are to be
modernized. This approach is essential to avoid impairing compatibility. It is equally
important always to evaluate and assess the system as a whole. The information
from the first four steps and the AL Migration tool can now be used to create the
migration strategy in collaboration with sales and engineering. In normal
circumstances, an increasing number of options will be available. These must be
matched with the customer's requirements and the technical options.
The standard solutions are described in the migration manuals. For the finer
details, refer to the relevant system documentation and data sheets.
In conjunction with the information from the site record, it is now possible to suggest
very detailed solutions without the risk of neglecting important aspects. In more
complex projects, the engineering and sales personnel should work in close
cooperation.

12 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Introduction to migration 14.09.2011
 The knowledge of system specialists is especially important for questions of
compatibility. This step should always result in a proposed solution for the customer,
which should be agreed with the customer and costed.
5. Clarification of financial aspects.
6. Definition of a time schedule.
Note As a self-check, make sure that all the "w/h" questions (who, where, what, when,
how and how much) have been answered. Staff should have attended the AL
Migration Tool seminars, to enable them to ask the right questions.

2.2.6 Step 5: Project alignment

Step 5 consists of the alignment of the migration strategy with the customer. It is
absolutely essential to explain the effects and the extent of migration. For large and
very large projects, and for sensitive customers, it may be advisable to visit a
reference site. A visit of this kind should be accompanied by a system specialist
who can answer outstanding questions or clarify open points. Another option is to
provide a demo plant for the operator of a site so that the customer can get to
know the new technologies. In order to benefit from the new IT solutions, it is
especially important to include those responsible for customer's IT infrastructure if
solutions are to be used which affect the customer network or which could affect
data security regulations. This is always the case if wireless networks (WLAN) or
external access to the network (Web or remote access) are required.
When the detailed questions have been clarified the definitive solutions and options
can be defined. These should be checked again in technical and commercial terms
by specialists in these areas before the tender is submitted.
Further optimization can also be achieved by analyzing the workflow, reviewing the
chronological sequence and manufacturing components in advance. It has been
found that enabling the customers to use their own staff in the migration progress
can provide additional motivation for the award of a migration contract.
Another important point for coordination of the project is the chronological process.
Time scales should be agreed for all the relevant steps. In particular periods when
plant is switched off, or the time frame for building conversions are defined in this
way, and delays can thus be avoided. This can be supplemented by an agreement
on setting-up times, and a clarification of access rights and the handling of
materials on the company's premises.

2.2.7 Step 6: Project implementation

In the last of the six steps the project is implemented. Here, it is especially
important to keep rechecking the agreements and requirements. The
implementation of the project also requires very thorough planning, as deadlines
must be adhered to, or specific jobs can only be carried out with the cooperation of
other companies. The building conversion work should always be prepared for as
well as possible, to avoid difficulties resulting from unexpected events.
Preassembly of components, provisioning all building materials on site, loading
programs into the controller, checking documentation, and performance of all work
that can be carried out in advance, all contribute to additional reliability and
reduced costs. This also applies, of course, to the implementation of plants by use
of the AL Migration Tool.

For internal use only 13 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Introduction to migration 14.09.2011
 One aspect that always leads to discussion after commissioning is that the
behavior of the plant seems to have changed. Customers are often highly sensitive
to the smallest changes. This effect can be countered by involving the customer in
the commissioning process and explaining the changes. This step protects
technical staff from re-engineering and generates a high level of customer
satisfaction. This positive experience for the customer can very rapidly generate
follow-up work.
As a follow-up to migration, a feedback discussion should always be conducted at
short notice with the customer. It is very important that customers do not get to
know their new technology without guidance, and equally important that the
Regional Companies take the opportunity to optimize the workflow.
Further information on implementation is available on the Global Service pages in
the intranet.

2.3 Further information and checklists

Checklists in Excel format are available for all systems, for recording the plants.
There is thus a project list, a control panel list and a system list for Visonik, Unigyr,
Integral and Desigo respectively.

How are the checklists The lists are divided into different sections and can be partially completed before
used? the visit to the customer. This is also a way of checking the validity of the master
data.
Staff can ask about individual points and record the answers in the form of an
interview. To save time, there are numerous questions which can be answered with
a "Yes" or "No". However, all questions must be answered, even if it appears that
everything is clear.
The member of staff handling the next stage who was not present at the meeting
will otherwise be unable to work on the project without further questions. Follow-up
questions are often time-consuming and can produce errors.
For work on the project, it is very important that all documents, such as wiring
diagrams, control diagrams, photos, data backups etc. are enclosed with the
checklists.
A complete list of the companies involved in the building works must also be
available. It must also be clarified whether the contractor is in a position to
undertake the qualification process and able to provide the necessary resources.
More information on migration to Desigo is available on the intranet at:
https://intra.industry.siemens.com/bt/global/en/business/building_comfort/systems/
migration/mig_des/Pages/mig_des_intro.aspx

BAU Lifecycle Management - Migration Group:

https://workspace.sbt.siemens.com/content/00001002/lcm/Pages/Migration.aspx

Link to Desigo AL Migration Intranet Site:

https://intra.industry.siemens.com/bt/global/en/business/building_comfort/systems/
desigo/tools/Pages/des_tool_dalm.aspx

If additional requirements are necessary, or if you notice an error in the checklists,

please forward the relevant information by e-mail to: [email protected]

14 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Introduction to migration 14.09.2011
 2.4 Attachments / References

The migration manuals contain a list of documents about migration.

Compatibility lists for the various systems are provided in the respective migration
manuals.
Information available on the intranet:
– Compatibility lists for the systems (Migration manuals).
– Checklists for:
– Project data
– Panels
– Systems
Visonik system
Unigyr system
Integral system
Desigo system

– Life cycle information.

– Migration manuals: Desigo, Visonik, Unigyr, Integral.
– System descriptions for each of the systems.

Link to Siemens BT Building Automation / Life Cycle Management / (Migration

Group)

https://workspace.sbt.siemens.com/content/00001002/lcm/Pages/Migration_Comm
unity.aspx

For internal use only 15 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Introduction to migration 14.09.2011
 3 Workflow overview and engineering tools
The diagram below shows the activities to be carried out in the UVI system and in
321-Workbench.
To a large extent, the data flow associated with taking over engineering data also
determines the workflow. The data is exported from the UVI system individually
according to the system. The exported engineering data is converted into a data
format with similar syntax.

1 Export engineering data from the existing UVI systems (server or controller).
The data export largely depends on the existing UVI tool mechanisms.
Data that cannot be reused directly in Desigo is needed to create reports, and
is used for information when documenting the existing plant.
The ETS output (HVAC and VIS files) can also be imported as of Desigo
V2.37 for Visonik.
7. Conversion and transformation into a common data format (Controller Data
Format (CDF)).
8. Manual selection and configuration of a Proven Solution in XWORKS plus, or
program structure created directly in CFC. Selection is based on knowledge of the
plant, supported by legacy controller code (e.g. Visonik COLBAS), project
documentation, and the generated re-engineering reports.
9. Manual mapping of UVI data points to PX data points. This process, where PX
objects are linked to UVI data, is the main and most important workflow. Hardware-
related parameters and I/O addresses are transferred in the mapping process.
10. Generation of engineering data in the CFC. The engineering data contains the
structure of the PX program, enhanced with transformed data from the UVI system.
11. Post-engineering & integration of imported data takes place directly in CFC using
associated editors (Parameter Editor and I/O Address Editor). This stage also
includes not only integration of controllers into the existing system and
management level, e.g. for communication, global system functions, alarm
management, trend objects, time scheduling, but also integration into ADP/CC.

16 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Workflow overview and engineering tools 14.09.2011
 The tool strategy involves three different tools to migrate the engineering data:
1. 321-Workbench to export and convert UVI data.
2. XWORKS plus Point Configurator to map UVI data to Desigo PX data
points.
3. CFC Editor for PX programming (I/O Address Editor, Parameter Editor)

For internal use only 17 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Workflow overview and engineering tools 14.09.2011
 4 321-Workbench, Visonik workflow
321-Workbench ("three-to-one" workbench) is used to prepare the project data
from the UVI systems for migration to Desigo PX.
When migrating a Visonik system, additional project-specific settings are required
for data point migration (e.g. without these, the new PTM modules are not correctly
addressed).
In 321-Workbench, migration of a Visonik system takes place at two levels:
DCS level
The following elements are defined at DCS level:
– Migration of process units and possible merging of several process units.
– Mapping Visonik alarm groups to PX alarm classes.
– Mapping ERSTA delay times.

Process unit level

The following elements are defined at the process unit level:
– Module migration mode (per process unit).
– PTM module adjustments.
– Process unit selection (PXC-64/128 or PXC-50/200).
– Migration of PTM to TX-I/O modules for PXC-50/100/200.

4.1 Prerequisites for Visonik migration

 Supported Visonik process units

– EKL-X
– PRV1
– BPS

 Supported Visonik DCS versions

Version Revision and patch

V 26 16.317 and higher Direct migration possible
V 24 14.154 and higher Direct migration possible
V 22 14.154 and higher Direct migration possible
V 20 14.154 and higher Direct migration possible
V 18 06 Takeover required

 VisoExe: Minimum V 24.16.000

 Communication access to Visonik Container (DCS or VisoExe) with DCT.exe.

4.2 Preparations on the project

 All data points generated on the process units must also be generated on
Visonik DCS. This is true in particular for fictitious data points such as CVP,
RGB, VIP etc.. Use PRO, GPR to check this for the process unit. If data points
are missing from the Visonik system, they can be generated automatically with
$xx’PS.OP=SAPA.

 The data must be complete. As the upload comes directly from the DCS, it is
strongly recommended that you check for data consistency between the DCS

18 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 and the plant beforehand. To do this, we recommend that the following actions
be carried out individually for each process unit:
$xx’PS.OP = Gacq
$xx’PS.OPLS = SaFi
Subsequently, monitor the $xx’PS.OP parameter until the actions are complete.
 There are two options:
 Either 321-Workbench is used for direct access to the running Visonik
Container, or
 a shadow container (VisoDat1.vis) is generated on the running project. The
shadow container is taken to the office and started with DCS-Light on an
office PC. This is possible because all necessary data is present in the
Visonik Container.

Hint In rare cases, data points have IDC=0. The tool, however, requires a correct IDC.
1. Search for data points with IDC=0. Create a project report, e.g. with
Pro,CSS,$*,IDC=0,, .
2. Assign the correct IDCs manually to the data points found.

4.3 Create a migration project

Begin by setting the project settings and creating a new project. Access to the
Visonik Container is also defined in this process.

4.3.1 Set upload options

Set the options in 321-Workbench (Tools > Options).

Tab: Visonik Upload

Select this option if you want to use the Visonik project name (SYS;PROJ)
automatically for the migration project.

For internal use only 19 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.3.2 Create a new migration project in 321-Workbench

Important When defining a new migration project, set up valid communications with the
Visonik Container, otherwise no new migration project is created.

Prerequisites  Visonik container on the DCS (on the project)

or
 Visonik container on the PC with VisoExe (in the office). There is no need to
connect process units for 321-Workbench to function. All necessary data is
already in the process image of the Visonik Container.

1 Select File > New Project.

2 Select the UVI system Visonik and enter the project root path.
Note: Neither the UVI system nor the project root path can be changed
retroactively.
3 Enter the project name.
A new project folder is created with the project name entered. Where
applicable, indicates that there is already a folder.
Note: If Automatically rename project is selected, the project folder is
assigned the name of the Visonik project (Tools > Options, Visonik-Upload
tab).
4 Enter the texts for the report.
5 Click Next >.
---> The Define sources for DCS data dialog box opens.
6 321-Workbench uses the program DCT.exe for access to the Visonik
Container. The required communication settings are saved in file DCT.ini
When setting up a new migration project, you can create a new DCT file
(Start DCT now….) or you can copy an existing DCT.ini file to the migration
project (Copy existing DCT.INI…).

Configure DCT.ini 1 Click Start DCT now…

2 Select Tools > Configuration Wizard....
---> DCT is started directly in a separate window.
3 Now define the required connection to the Visonik Container.
4 Close the Configuration Wizard.
5 Close the DCT window.
---> The settings are imported into 321-Workbench.

Hints – For Connection to the Visonik Container, prefer socket communication in

DCT.
– If 321-Workbench and the Visonik Container are on the same PC, enter the local
host (127.0.0.1) as the Host name.
– Select the correct Language (XX=) to migrate project-specific text.

Copy DCT.ini 1 Click Copy an existing DCT.INI....

2 Locate the required DCT.ini
---> (e.g. in folder …/ProjectName/_AlMig_Dct/...).
3 Click Open.
---> The selected file is copied to the current folder.
4 Click Next >.
---> This opens the dialog box Upload from a running DCD container.
5 Select the required DCT connection.

20 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 6 Select the language required for the DCS.
Note: Selecting the correct DCS language makes the project-specific data
available (e.g. point description, enumeration, unit).
7 Click OK.
A new project is created with the appropriate folder structure.

4.4 Acquire Visonik data

Note TRDLG data is uploaded via the Visonik-DAP,DIR dialog box. This dialog box
supplies data only if the DCS system time is valid. It is therefore vital to define the
system time via the DA dialog box.
Note: If the Visonik Container was "rescued" from the site and the migration upload
is carried out in the office, the system time, by default, is NOT defined.

Hints – ALconf: Visonik projects on which Desigo Insight is not yet in use do not
necessarily operate with alarms. Remember to set parameter ALconf before an
upload via PKX, otherwise this has to be done manually in the CFC.
– Check Data points defined as fictive and, if possible, switch to "real",
especially in the case of points from EKL-X stations. Otherwise the scope for
configuration is severely limited in the tool.

Procedure in Visonik data is acquired in two stages via 321-Workbench task DCS Upload:
321-Workbench
1. Step Global Visonik data (i.e. Visonik data valid for all process units) is uploaded from
the Visonik Container (TextDcs.txt). This data consists mainly of text catalogs with
"I" and "U" text. 321-Workbench also interrogates each process unit for its type
(IDC) and version.
1. Select the "not yet uploaded" check box.
2. Click the green arrow.

---> Global data is uploaded (via DCT).

After uploading, a list is displayed of all process units containing project data.

For internal use only 21 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
2. Step The process data is uploaded from the process units to be migrated.
1. Select the process units to be migrated.
2. Click the green arrow.
The process-station-specific data is uploaded (via DCT). Process units
uploaded in this way are marked in light green.

This completes the upload procedure.

22 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.5 Migration settings

Visonik data is prepared so that it can be mapped as required to the PX project in

the Generator task of 321-Workbench.
The Generator generates the CDF files that can be further processed by XWORKS
plus Point Configurator. The following settings are required for this purpose:

4.5.1 Map alarm

Use the Map Alarming tab to define the mapping of the Visonik MSGP and AlConf
to the PX alarm classes. You can also specify whether or not data points set to
OSV must be capable of generating alarms.

The following mapping rules apply:

 If MSGP > 0 and OSV = 0  EnAlm = TRUE else FALSE
 If AlConf > 0 and OSV = 0  AlmFnct is set accordingly:
Alconf AlmFnct
No alarm. ---
Alarm Basic
Simple alarm Simple
Extended alarm Extended

 Alarms from Visonik overwrite the corresponding alarm settings (from PX

solution). Thus, the Visonik value is taken over.

Note The DCS tabs are only displayed if the DCS is selected in the tree structure.

4.5.2 Map DEL01&10

For almost all data point types, Visonik has two separate delay times for incoming
and cleared faults (alarms). With most function blocks in PX, there is only one
delay time:TiMonDvn. However, data points BI and BO have the following three
delay times: TiMonDvn, TiMonOn und TiMonOff. This tab allows you to define how
these delays are handled system-wide.

For internal use only 23 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 Note
The DCS tabs are only displayed if the
DCS is selected in the tree.

4.5.3 Export/import transformation rules

The settings for Map Alarming and Map DEL01/10 can be saved in a file for use
with other migration projects.

Export (Tools > Export; Generator task only).

In the second stage of the wizard, you can specify a file to save the rules.

Import (Tools > Import; Generator task only).

24 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.6 Migrate EKL-X process units

Migrating EKL-X process units requires using new PTM modules. The following
migration steps are required:
 Set for automatic conversion of the EKX-IDC to a (temporary) 321 IDC.
 Verify or modify the PTM modules proposed by 321-Workbench.
 Add any missing PTM module settings (e.g. for INV, switching, sensor types
etc.)
 To migrate to TX-I/O modules, you can specify which TX-I/O module
corresponds to what PTM module and what addresses are to be assigned to the
various relays.
See also: Process map, BPS V12/14, Engineering documentation, CM2Z8303E
 Specify TX-I/O module migration rules.
Note: Migrating EKL-X to TX-I/O modules is indirect by migrating to PTM
modules.

4.6.1 Set Generator options

Set the options in 321-Workbench (Tools > Options).

Tab: Visonik EKX Migration of EKL-X controllers. Use this tab to define special cases for the
migration of EKX to P-bus modules throughout the project.
Note IDCs migrated in this way can still be modified later.

EKL-X module types SB1_D, SBR1-D and SBR1_DE have bistable outputs. The
corresponding P-bus modules are available in monostable or bistable versions.
Normally, old modules of this kind are replaced with type 2Q250 modules. As an
option, the bistable version can be pre-set here.

For internal use only 25 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 The mapping of module types SBR3_D, SBR3_DE and ST_U is for information
purposes only.
When replacing module type SBR1_P, either 4Q250P or 4Q250_AP can be
selected. When replacing one module type with another, changes in the wiring are
always necessary, due to differences in the electrical circuits. The version selected
should be the one which requires the least effort. As a rule of thumb, 4Q250_AP is
better for lighting control, otherwise use 4Q250_P.
In the case of the SBR2_D module, you can choose whether to map it to a two-
stage (4QD-M2) or 3-stage (3Q-M3) P-bus module.
The special case, ST_P, appears at the bottom of the tab. This module, type
LVF#.4601, has a 3-position output and an internal feedback signal via a resistor in
the actuator, and is thus self-balancing. This module does not exist in the P-bus
range. You must decide whether to replace it by ST3_P without feedback or ST_U.
In the first case, there will be problems with accuracy. In the second case,
electronics must be upgraded for 3-point conversion and feedback, or the actuator
must be exchanged.

4.6.2 Add missing settings for PTM modules

Since the DCS does not have all the required information in the process image,
any missing settings have to be added manually.
– In the case of signaling modules with indicators, the DIP switches on the back
cannot be read, and as a result, there is no information on the inversion status.
Similarly, it is not known whether a module does or does not have a memory
function (both IDC=16).

– With pulse switching modules and 3-point control outputs the RAN cannot be
read.

– In the case of measured values, the switch position cannot be read. The signal
transmitter is also unidentifiable.

– With switching outputs, it is not possible to determine whether or not there is a

manual operating level.

Tab: P-bus or TX-I/O The P-bus tab or TX-I/O-bus shows appropriate replacements for the EKX
bus hardware.
The P-bus tab allows for defining if the old ML modules should be replaced by
8D20E, 4D20 or 4D20/4D20R.
The TX-I/O bus tab allows for defining how PTM modules are to be migrated to TX-
I/O modules.
Hint Use the wiring diagram for additional help.

26 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 opens a dialog box for each PTM module to check and, if necessary, change
the settings.
The next subsections deal with the special features of the individual EKX modules.

4.6.2.1 ML modules

With ML modules the inversion can be selected separately for every data point.
Depending on whether you select 8D20E, 4D20 or 4D20/4D20R, either INV is set,
or a 4D20R module is inserted.
Select 4D20/4D20R if the LED on the signaling module is to indicate the actual
status.
Any other combination is allowed, provided it complies with the Visonik
requirements. However, it is not permissible to mix IDC16 (volt-free) and
IDC17(non-floating).
In the example below, the first three inputs are inverted. As a result, a 4D20R is
added. The last data point, which now no longer fits this combination, is linked to a
new 4D20 module. Ultimately of course, the arrangement is optimized to avoid the
unnecessary use of hardware.

For internal use only 27 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
Note MX data point restriction: If ML data points on a EKL module are summarized to
form one or several MX data points, they can be migrated automatically to PTM
modules provided they are located on the same module, in direct sequence, and
match 2D20 or 4D20 completely.

4.6.2.2 MW modules

With MW modules, the switch setting of the old module must be given for each
data point. The next stage is to select the connected sensor in each case. 321-
Workbench selects the relevant module.

28 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
Note Desigo PX does not support 2N100K modules. A replacement solution must be
considered, e.g. sensor replacement or use of corresponding TX-I/O modules.

4.6.2.3 ZW modules

No settings are necessary with the ZW modules.

For internal use only 29 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.6.2.4 STU modules

With STU modules, you are required to define which module type is to be used.
This mainly depends on whether or not the customer wants a manual operating
level. The required combination is selected via the PTM combination.

30 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.6.2.5 STP modules

With STP modules, the actuator runtimes must be entered.

The EKL-X three-point modules have 6 outputs per module. The BPS supports a
maximum of 4 outputs per module. In such cases the software generates a new
module at the end for the remaining 2 data points.

For internal use only 31 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.6.2.6 SB modules

In the case of the SB modules, a distinction is made between SBs with and without
feedback. In the case of switch commands without feedback, you can select
whether to use modules with or without manual operation.

4.6.2.7 Switching command with feedback

There are more options for commands with feedback: Firstly, types 2QD and 4QD
are available as additional options, and secondly you can determine whether an
external local/remote contact is required. The following rules apply:
– 2QD/4QD: The feedback mechanism is an integral part of the module. If an
additional signaling module is specified, the signaling inputs are used for
external local/remote contacts.

32 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 – 2Q250: Feedback is via a 2D20.
If a 4D20 module is selected, the additional signaling inputs are used for
external local/remote contacts. Effectively – after generation – 4D20 modules
are always used, irrespective of whether a 2D20 or 4D20 was selected in the
input form. The only reason for distinguishing between the two is to allow you to
define whether or not a local/remote contact is required.
The following pictures illustrate this: For EKL-X modules $61’02 and $61’04, the
selected combination is 2Q250-M /2D20, i.e. without an external local/remote
contact.

The report view shows the result after generation: The feedback from four
switching commands is switched to a 4D20 module.

4.6.2.8 Pulse switching module

Pulse switching modules are another special feature of the SB modules.

The conversion can be set in the IDC field. This can differ from the global setting,
i.e. the setting that defines whether the conversion should be in accordance with
4Q250P (IDC 48) or 4Q250AP (IDC 49).
The pulse duration should also be entered:

For internal use only 33 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.7 Merge process units

Process units can be merged in the migration process. Any combination of EKL-X,
PRV1 and BPS can be merged.
In the process of merging, the individual P-bus rails are connected in series and
the data points are assigned new addresses. The number of load units is checked
in this process, to ensure that it does not exceed the maximum.

Prerequisites The process units must be in the same Visonik Container.

Hints – As a general rule, the addressing is retained by the first process unit specified in
the merging process.
– The first process unit you select should be the one with the most modules.

When merging several controllers to one Desigo PXC automation station (PXC-
64/128, PXC-50/100/200), check the load units as well as the max. allowed data
points. See the related data sheets for system limits.

4.8 Module migration mode

During migration, unused connections to the PTM modules can be eliminated by P-

bus compression. Existing PTM modules can be replaced by higher-performance
TX-I/O modules.
321-Workbench has five settings for module migration. These settings limit the
number of changes necessary.

Keep PTMs, wiring, and This setting ensures that the P-bus addresses and PTM modules are not changed
addresses (green) during migration. The P-bus rail is adopted without modification.

Note When process units are merged, their P-bus rails are connected in series, i.e.
physically interconnected. This makes it necessary to modify the P-bus addresses
of the second process unit. In such cases, the program automatically switches P-
bus compression for the second process unit to the next compression mode ("Keep
modules, keep wiring").

Application PRV1 and BPS migration without changing the P-bus.

Keep PTMs and wiring, This setting avoids the need to use other PTM modules for migration, or changing
compress addresses the wiring.
(yellow)
The P-bus rail is adopted without modification. P-bus addresses do change,
however.
This setting compresses the P-bus addresses. After migration, PX also makes use
of P-bus addresses which Visonik could not use (optimize gaps).

34 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
Example Although module 8D20 requires only one P-bus address, A1, P-bus addresses
A1…A4 had to be kept free in Visonik. This limitation does not exist in PX. This
setting releases P-bus addresses A2…A4 and uses them for new P-bus modules.

Application PRV1 and BPS migration, when the P-bus address range is not large enough.

Keep PTMs, change This setting avoids the need to use other PTM modules for the migration. P-bus
wiring (orange) addresses and wiring do change, however.

This setting moves data points to so far unused I/O spaces. After migration, it may
be that some modules are no longer required.

Example Only three data points are connected to the 4D20 module. Elsewhere on the P-bus
is a 4D20 module to which only one data point is connected. This setting
configures the single data point on the 4D20 module. The wiring must be changed.
The 4D20 module is now empty and can be removed.
Use: Reduce number of empty spaces.
Important: The valid result of this P-bus compression is visible only in the report
(i.e. not under the P-bus tab).

Migrate to TX I/O, This setting replaces PTM modules or EKL-X modules with TX-I/O modules. At the
change wiring (red) same time, the P-bus addresses are converted to TX-I/O island bus addresses.
And a rewiring list is created in the engineering report for PTM  TX-I/O. (See
Section 3.10).
If you select this option, you can specify if you want to use the Visonik BPS with
BIM (and IOMD) or a Desigo PXC-50/100/200-D automation station.
Note: When an EKL-X process unit is migrated to Desigo PXC-50/100/200-D, the
rewiring list is run via PTM modules, i.e. there is no direct rewiring list from EKL-X
 TX-I/O.

Retain PTM/TX-I/O This setting retains the PTM/TX-I/O modules as is including wiring and addressing.
modules In existing TX-I/O modules (e.g. PRV with BIM), the BIM is removed and the TX-I/O
wiring and addressing module connected directly to PXC-50/100/200.
(green)
If PTM modules are retained, they can be connected directly to a PXC-50/100/200
via the PXX-PBUS extension module.
Addressing can be taken over. (Example: P=1.1).

For internal use only 35 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.8.1 Change P-bus connections

Basically migration does not impact connections to the P-bus.

However, manual adaptation of the P-bus connections required in cases where:

 Automatic migration of data points requires changes (e.g. other PTM modules or
addresses).
 Data points could not be migrated during automatic migration of data points.
These must be dealt with manually.
 New P-bus connections generated by P-bus compression need to be modified.
 Connections to the P-bus generated by migrating EKL-X process units are to be
changed.
 New P-bus connections generated by merging process units need to be
modified (other PTM modules)
 Unused connections on PTM modules are to be eliminated.
 Simple PTM modules are to be replaced with more powerful ones.
 New field devices/functions are to be implemented.

4.9 Interface modules

When migrating PRV1/BPS process units to PXC-64/128-U and PXC-50/100/200

(using the PXX-PBUS extension), PTM modules can be taken over as is.
Exception The following interface modules are not supported:
– PTE-MBUS.60
– PHM1.36TL

These modules form a predefined combination from standard ICD to P-bus. 321-
Workbench cannot identify these modules and thus displays the hardware from the
interface module. Interface modules must be acquired manually as they are not
detected automatically.

36 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.10 Visonik PTM migration to TX-I/O modules
Migrating PTM modules to TX-I/O modules is supported for the following cases.

Migration to Visonik BPS + BIM with TX-I/O modules

Visonik BPS is extended by a bus interface module
(BIM) to talk directly to TX-I/O modules (island bus).
BPS BIM TX-IO An IOMD file is required to configure the BIM. The
IOMD file contains the TX-I/O module addressing.

Migration to Desigo PX-100/200 with TX-I/O modules

Controller migration from Visonik PRV/BPS to Desigo
PXC-50/100/200. New TX-I/O module addresses are
created. (IOMD file not needed).
PXC-50/100/200 + TX-IO
In addition, a rewiring list is created (PTM  TX-I/O).

Restriction Migration to Desigo PX-64/128 + BIM with TX-I/O modules

 Migrating Desigo PXC-64/128 with BIM and TX-I/O modules is not supported, as
migration always requires the latest hardware configuration (i.e. the latest PXC-
50/100/200 automation stations).

4.10.1 Migration to Visonik BPS + BIM + TX-I/O modules

Select the following options if Visonik BPS is retained and new data points or
existing PTM modules are replaced with TX-I/O modules.

An IOMD file with the I/O configuration is created in this process. The P-bus
interface module BIM must be configured as per the IOMD file. The BIM
automatically converts the P-bus addresses to island bus addresses (for TX-I/O
modules).
See Section 3.12.4 "Generate IOMD file" for more information on IOMD files
creation.

For internal use only 37 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.10.2 Migration to Desigo PX-50/100/200 + TX-I/O modules

The P-bus addresses and the PTM modules are converted to TX-I/O modules
during migration from Visonik PRV/BPS to Desigo PXC-50/100/200 with TX-I/O
modules (direct on island bus). A CDF file with the new TX-I/O module
assignments is created in the process.
In addition, a rewiring list is created for PTM  TX-I/O modules.
Adhere to the following procedure:

1. Define rails and TX-I/O modules.

a. Define the preferred rails in the TX-I/O bus tab. You can e.g. define a
distinction between mains power and control in the panel based on the P-
bus address range as needed.
b. In addition, you can select the preferred modules for input/output signals as
well as the corresponding feedback data points. The settings are saved
accordingly.

2. Generate CDF files and rewiring list

During migration to TX-I/O, the corresponding report file must be generated, as
it contains the rewiring list.

38 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 3. Check the rewiring list.
The report contains the rewiring list. The report header contains a link to the
rewiring list.

4.10.2.1 Rewiring list (PTM  TX-IO)

4.10.2.2 Rewiring list description

What From To
Rail Rt: Selected rail (as per Step 1a).
Module Bp: Original PTM module Mt: Selected TX-I/O module (as per Step 1b).
Address Ap: P-bus address At: Island bus address
Channel Cp: Point address Ct: TX-I/O channel
Clamp CLp: PTM terminal Clt: TX-I/O terminal selected accordingly

For internal use only 39 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.11 Visonik migration to PX-50/100/200 with PTM

Use the PXX-PBUS extension module to migrate PRV/BPS process units while
retaining PTM modules to PXC-50/100/200.

Migration to Desigo PX-50/100/200 with PTM modules

Use the PXX-PBUS extension module to migrate
controllers from Visonik PRV/BPS to Desigo PXC-
50/100/200 while retaining PTM modules.
PXC-50/100/200 +
The wiring and addressing can be taken over as is.
PXX-PBUS +
PTM

4.11.1 Migration to PX-50/100/200 + PTM

If a Visonik PRV/BPS is migrated to Desigo PXC-50/100/200 while retaining PTM

modules, enter the following settings.

Addressing and wiring of PTM module remains as

is. The PXC-50/100/200 can talk directly to P-bus
addresses (P=1.1) using the PXX-PBUS
extension module.

PXX-PBUS extension module

40 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.12 PXC-50/100/200 mixed PTM and TX-I/O
operation
When using the PXX-PBUS extension module, both TX-I/O and PTM modules can
be operated using the same controller (PXC-50/100/200) from Desigo V5.
Migration of Visonik BPS with PTM modules and TX-I/O modules can be supported
using a PXC-50/100/200 with PXX-PBUS extension module. The PBUS-BIM no
longer is needed.

Migrate BPS with BIM To Desigo

If TX-I/O modules are connected to a For mixed operation of PXC-50/100/200,

BPS via PBUS-BIM, the IOMD file note that two new addresses may occur
(BIM configuration) must be used for (e.g. 1.1). On via island bus (T=..), and one
addressing. via P-bus addressing (P=…). The
uniqueness of the addresses is checked in
For migration, we recommend the CFC I/O Address Editor.
uploading the current I/O configuration
using the BIM tool directly from the
BIM and saving it to the corresponding
folder in 321-Workbench. The path is
available in 321-Workbench under
Sources.

For internal use only 41 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.13 Generate

Function (Tools > CDF/Generate report) comprises several steps:

– The uploaded data is processed in accordance with the settings. The information
from the PKX file is read and checked for plausibility.
– Migration data is then calculated.
– Finally, the selected files (CDF/report files) are created.

Details of the process, in the form of INFO, WARNING and ERROR messages, are
displayed in the log window or saved in the log file. WARNING and ERROR
messages are also written to the report file.

Notes – Generating is also carried out at other times to check feasibility of settings
(e.g. PS merge) or to check proposed migration in relation to PTM modules.
In this case, the log window or report provides important information, indicating
faulty configuration of Visonik, for example, or adjustments required on the PX
side.
– Generation is only carried out for the process units selected in the tree. If
nothing is selected, the function is inactive.

4.13.1 Log window

The log window displays the steps during generation along with information,
warnings and error messages.
Note the following information in the log window:
– CANCEL: No properly functioning CDF file.
– ERROR: Migration not completed.
– WARNING: Indicates that a migration solution was generated that still requires
certain actions (e.g. replacement of hardware, manual adjustment of data points
etc.).

Example -WARNING-> AL:$d63'140: PX supports max 4 inputs per MI.

Thus, STR is limited from 0&1&2&3&4&5&6&7 to 0&1&2&3.

An MX point with 8 signal inputs (STR*) is defined on Visonik. However, the

associated PX object (MI) can only accommodate up to 4 inputs.

The contents of the last log window are saved to file

..\Projectname\_AL_Mig_Log\DCSUpload.rtf or Generator.rtf.

42 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.13.2 Generate report

The report is based on the following settings:

– Project settings: Determines the project information, project description etc.
– Options: Determines the file name and path.
– Report tab: Determines the contents.
– The report additionally contains the rewiring list when migrating to TX-I/O
modules. Rewiring list (PTM  TX-IO)
These settings must be defined prior to generation.

If Generate Report File (above the tree view) is selected, the report is created
automatically during generation.
A separate report is created for each selected process unit (unless they are
merged).
The reports are written to the folder ..\ProjectName\_AL_Mig_Report or to the
relevant PS folder (in accordance with the option selected via Tools > Options,
Generator tab).
After a report is generated, it can be displayed directly via the preview option
(Report Preview tab – this tab is not displayed unless a report is available).

Note The report can be created in various file formats (xml, html, doc) depending on the
option selected under Tools > Options; Generator tab).

Hint Select only the required data format (one format only).

4.13.3 Generate CDF file

If Generate CDF File (above the tree view) is selected, the report is created
automatically during generation.
A separate CDF file is created for each selected process unit (unless they are
merged).
The CDF files are written to the directory ..\ProjectName\_AL_Mig_Cdf or to the
relevant PS directories (in accordance with the option selected under Tools >
Options; Generator tab).

4.13.4 Generate IOMD file

The IOMD file is created automatically upon generation, when the option Generate
IOMD File (above the tree directory) is selected.
An IOMD file is created for each selected process unit (unless they are merged).
The IOMD files are written to the folder ..\Projectname\_AL_Mig_Iomd or to the
corresponding PS folders (corresponding to the selection option Tools > Options ;
Generator tab).

For internal use only 43 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 4.14 Evaluate report

The report is an important tool for reviewing and documenting migration of data
points. The report provides information on the following points:
 Hardware/software data from the UVI system.
 Settings in 321-Workbench during the migration process.
 Migration of data points.
 Intended PTM or TX-I/O modules.
 Module migration mode.
 Manual adjustments required.

After a report is generated, it can be displayed in the Preview.

For information on specific problems, refer to the heading $...Parser Info.

4.14.1 Special cases

The report is useful when dealing with the following special cases:
Visonik EKL-X PX does not support 3-point modules with feedback. An alternative solution must
migration be considered, e.g. changing the actuator.

PTM modules, general PX does not support 2N100K modules. A replacement solution must be
considered, e.g. sensor replacement or use of corresponding TX-I/O modules.

44 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Visonik workflow 14.09.2011
 5 321-Workbench, Unigyr workflow
321-Workbench ("three-to-one" workbench) is used to prepare the project data
from the UVI systems for migration to Desigo PX.

5.1 Prerequisites for Unigyr migration

 Unigyr tool version V7R54 must be installed on the computer. However, you do
not need a Unigyr license to use the migration tool. (Unigyr data is read-only
data.)
 Supported controller versions
– Migration from V3.30 - V7.02
– Not supported < FBB V3.30
 Unigyr controllers supported
– PRU1.xx
– PRU2.xx
– PRS10.xx / PRV10.xx
– RWM.xx
– RWP.xx
 The Unigyr project data file structure must already exist.

Uni_data
Project A Unigyr project folder A
Segment 1
PRU (.PLN)
PRU (.PLN)
Segment 2
PRU (.PLN)
PRU (.PLN)
Project B Unigyr project folder B
Segment 1
...

For internal use only 45 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.2 Update Unigyr project data

Unigyr projects >= FBB V3.30 do not require updating.

A Unigyr project prior to FBB Version 3.30 must be updated to Unigyr FBB Version
7.02 by use of the Unigyr tools HLK Back Translator followed by HVAC Compiler.

1. Drag the PLN file onto the HVAC Back Translator icon.

Unigyr: HVAC back translator (1)

Drag the HVAC file (extension HLK) onto the HLK Compiler and select FBB
Version 7.02.

Unigyr: HVAC back translator (2)

46 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.3 Access Unigyr data

Unigyr data can be accessed from the local PC, from a data storage medium such
as a memory stick or CD etc., or over a network.

Prerequisites – 321-Workbench requires that the project data be set up in accordance with
Unigyr data structure rules. (See Section 4.1).
– The Unigyr project is the starting point for 321-Workbench. The controllers in the
segments below the project can be selected in the 321-Workbench dialog box,
either as a whole or individually.

Note If the data is accessed over the network, the network drive must be mapped to a
drive letter. Open a connection via the Windows Explorer menu Tools > Map
network drives. Here, observe IT guidelines for drive allocation.
In addition, the names of Unigyr projects and segments must meet Rule 8.3 and
may not contain any blanks in the path.

5.4 Migration-critical hardware (Unigyr)

Desigo PX does not support all hardware components from the Unigyr
environment. For migration purposes, the following components must be replaced
by an equivalent solution.
Unigyr hardware Possible solution in Desigo PX
PHM1.36-TL PXM 20
PXM10
Local alarm or report printer on the Printer connected to Desigo Insight
automation station
Fax transmission via automation station Fax transmission via Desigo Insight
QAA 23.71 room operator unit QAX 3x.xx
QAW50 room operator unit QAX 3x.xx

5.5 Merge controllers (Unigyr)

321-Workbench does not offer a function that supports merging of controllers.

Two or several controllers can be merged into one PX automation station using
XWORKS plus Point Configurator. However, the I/O addresses must be changed in
the CFC accordingly.
As an alternative, the I/O addresses can be modified in Unigyr Design before
loading into 321-Workbench. For example, P-bus addresses 1…80 can be
assigned to the first controller with the addresses of the second controller starting
at 100.

For internal use only 47 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.6 Migrate QD modules (Unigyr)

QD switching modules are not addressed in the same way in Unigyr as in PX.
However, the migration tools automatically take account of IO addressing.

Address type Unigyr PX

I/O address Channel 1 P=1.1(QD)

FB address Channel 2 P=1.1(QD)

5.7 Recommended plant Unigyr Desigo

The plant recommendations in the 321-Workbench report are based on the

following criteria.

Unigyr block Condition Recommended plant

BWL_E Available DhwHyd10
BWL_OPTI Available DhwHyd10
BWL_P Available DhwHyd10
FERNW Available {Dstb1}
HEIZGR_Gross Available HGrp15
HEIZGR_Klein Available HGrp10
Boiler If no. of boilers in Unigyr program = 1 HGen11
Boiler If no. of boilers in Unigyr program > 1 HGenCas10
KESSEL_Master Available HGenCas10
MOTOR Step 1 Ahu10
MOTOR Step > 1 Ahu20

Note – The plant recommendations are based only on the existence of individual blocks
which can indicate the appropriate PX application.
To migrate Unigyr, a PX programmer must know the specified functionality. The
plant recommendation is not guaranteed to be correct.
– At present, only solutions from the Desigo Libset are proposed.
– Country-specific library extensions are not taken into account.

48 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.8 Unigyr migration options

The following migration options are available for Unigyr:

Migration Unigyr PRU to Desigo PXC-64/128-U + PTM modules

When migrating a Unigyr process unit PRU to Desigo
PXC-64/128-U, the PTM modules are retained and only
the process unit is replaced with a Desigo PXC
PXC-64/128 + PTM
automation station.

Migration Unigyr PRU to Desigo PX-50/100/200 with TX-I/O modules

Controller migration from Unigyr PRU to Desigo PXC-
50/100/200-D. The PTM modules are replaced with TX-
I/O modules.
PXC-50/100/200 + TX-
In addition, a rewiring list is created for PTM  TX-I/O
IO
modules.

Migration Unigyr PRU to Desigo PX-50/100/200 with PTM modules

Controller migration from Unigyr PRU to Desigo PXC-
50/100/200-D. The PTM modules remain as is and are
connected to the PXC using a PXX-PBUS extension
PXC-50/100/200 +
module. No rewiring required, addresses can be taken
PXX-PBUS +
over.
PTM

Caution! Migration to Desigo PX-64/128 + BIM with TX-I/O modules

 Migrating Desigo PXC-64/128 with BIM and TX-I/O modules is not supported,
as migration always requires the latest configuration (i.e. the latest PXC-
50/100/200).

5.8.1 Migrate to Desigo PXC-64/128-U

Migration to PXC-64/128-U while keeping PTM modules is supported as of Desigo

V2.36 and uses the same process.

The migration option must newly be selected in Desigo V4.1. The CDF file and
reports created contain all P-bus assignment information. This information can be
transferred to Desigo as is and processed further in XWORKS plus Point
Configurator.

For internal use only 49 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.8.2 Migration to Desigo PX-50/100/200 with TX-I/O

Desigo V4.1 and higher supports migration to PXC-50/100/200 and TX-I/O

modules. TX-I/O modules replace the PTM modules, thereby requiring a module
rewiring. The rewiring list PTM  TX-I/O is part of the report generated.
Migration to TX-I/O modules occurs in three steps:
1 Select target automation station PXC-50/100/200-D (see Figure 4-4). Define
the default TX-I/O modules and rails.
2 In a second step, define the rails and the default TX-I/O modules (incl.
preferred feedback modules). The definition is described already for Visonik
(see Section 3.10.2).

3 The report generated contains the rewiring list required by the panel builder.
The rewiring list for Visonik is described in Section 3.10.2.1.

50 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.8.3 Migration to Desigo PX-50/100/200 with TX-I/O

Use the PXX-PBUS extension module to migrate Unigyr PRU process units while
retaining PTM modules to PXC-50/100/200. The following setting must be set when
generating the CDF file.

PTM module wiring and addressing remains as

is when using the PTM modules via PXX-PBUS
extension module. The PXC-50/100/200 can
talk directly to P-bus addresses (P=1.1).

PXX-PBUS extension module

For internal use only 51 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.9 Generate CDF file and report

Function (Tools > Start CDF generation) calculates the migration data and
creates the required CDF/report files (if selected).
Details of the process, in the form of INFO, WARNING and ERROR messages, are
displayed in the log window or saved in the log file. WARNING and ERROR
messages are also written to the report file.
Generation is only carried out for the segments or controllers selected in the tree
structure. If nothing is selected, the function is inactive. The same applies in
principle to the creation of CDF and report files.
Note As the CDF/Report Generator relies on the existing mechanisms of the Unigyr
Design tool, the Unigyr Design tool (or the corresponding segment) must not be
open during generation.

5.9.1 Log window

The log window displays the steps during generation along with information,
warnings and error messages.
Note the following information in the log window:
– CANCEL: No properly functioning CDF file.
– ERROR: Migration not completed.
– WARNING: Indicates that a migration solution was generated that still requires
certain actions (e.g. replacement of hardware, manual adjustment of data points
etc.).
The contents of the last log window are saved in file
..\Projectname\_AL_Mig_Log\Generator.rtf

5.9.2 Generate report

The report is based on the following settings:

– Project settings: Determines the project information, project description etc.
– Options: Determines the file name and path.
– Report tab: Determines the contents.
– The report additionally contains the rewiring list when migrating to TX-I/O
modules. Rewiring list (PTM  TX-IO)
These settings must be defined prior to generation.

If Generate Report File (above the tree view) is selected, the report is created
automatically during generation.
A separate report is created for each process unit selected.
The reports are written to the folder ..\ProjectName\_AL_Mig_Report or to the
relevant PS folder (in accordance with the option selected via Tools > Options,
Generator tab).
After a report is generated, it can be displayed directly via the preview option
(Report Preview tab – this tab is not displayed unless a report is available).
Note: The report can be created in various file formats (xml, html, Office 2003 XML)
depending on the option selected under Tools > Options; Generator tab). Hint:
Select only the required data format (one format only).

52 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 5.9.3 Generate CDF file

If Generate CDF File (above the tree view) is selected, the report is created
automatically during generation.
A separate CDF file is created for each process unit selected.
The CDF files are written to the directory ..\ProjectName\_AL_Mig_Cdf or to the
relevant PS directories (in accordance with the option selected under Tools >
Options; Generator tab).

5.10 Evaluate report

The report is an important tool for reviewing and documenting migration of data
points. The report provides information on the following points:
 Hardware/software data from the Unigyr system.
 Project setting.
 I/O overview, module types, existing PTM modules.
 Automation station information.
 Data acquisition
 Station interfaces.
 Common alarms.
 Popcard operation.
 Scheduler program/Calendar.
 Setpoints.
 Desigo plant recommendation.

After a report is generated, it can be displayed in the Preview.

The report also contains a rewiring list for PTM to TX-I/O modules in the event of
migration to a TX-I/O module.

For internal use only 53 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Unigyr workflow 14.09.2011
 6 321-Workbench, Integral workflow
321-Workbench ("three-to-one" workbench) is used to prepare the project data
from the UVI systems for migration to Desigo PX.

6.1 Prerequisites for Integral migration

Data migration from Integral to Desigo PX is based on inputs and outputs,

associated parameters, and additional setpoints.
In addition, existing text descriptions for objects can be transferred. A lot of legacy
information from the corresponding Integral controller is documented in a report.

Note Existing graphics information from Integral Plan is not evaluated (e.g. for
conversion into Desigo PX graphics).

6.1.1 Integral system information

Integral is a heterogeneous system created and extended over many years. The
RS module serves as the basis for automation level control of the system. The
automation level is integrated via interfaces (e.g. NICO-N) in the system controller
(NCRS); the RS modules can be connected directly to the management station
using NITEL.

Important!  For correct migration to Desigo PX, the data from the customer site must be
updated with the engineering data.
 The project data of an Integral project must first be updated before exporting
Integral project data using 321-Workbench.

54 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
Supported versions Type Version File Replaced by
RSC compact All versions Export.sas PXC-NRUF
RSA application All versions Export.sas PXC Modular
RSM modular All versions Export.sas PXC-NRUD
NCRS From V3.1 *.dbs PX-Open RS-Bus
NITEL From V1.43 *.abb; *.inf; *.asc PX-Open RS-Bus

Integral data sources The Export.sas file is the common interface for all "project" cases. Depending on
the engineering and type of project, additional files can be used as sources of
information.
Controller/System Controller/Structur File Description
e
AS1000 1 controller Export.sas Engineering data exported with the
(RS module) Register.SR2 SAPIM400 (RS Backup)
Sapim(n).asc engineering tool Integral Plan or
Sapim(n).asc INDAGEN.
AS1000 --- Engineering data directly read with
the RS-Reader.
TS1500 (NITEL) Maximum *.abb; *.inf; AS1000 data plus engineering data
15 RS modules *.asc for management functions
(acquired from the plant).
MS2000 (NCRS) Maximum 4 trunks *.dbs AS1000 data plus engineering data
with max. 15 for management functions
RS modules each (retrieved from the plant with
Restore).

6.2 Provide access to Integral data

Data from the Integral system can be accessed locally, from a data storage
medium or via the network.
Note In AS1000, data can be exported direct via RS-Reader. This is done while creating
the migration project.

6.2.1 Add automation station to be migrated

Prerequisites  The data must be available in accordance with the data directory (or online via
RS-Reader).
 The data must be available in readable form.
 Data is updated.

This checklist helps for  Current data backup and program printouts for the RS modules (Integral Plan
data recording Project or RS Reader).
 For migration to PX RS bus: What Integral RS information points must be
provided to the BACnet environment.
 Assess communications interface at AS: Modem, local printer, network, etc.
 Assess hardware.
 Room operator units, operator unit NBRN, PXM-10/20, door integration.
 Panel, space requirements and mounting options for Desigo PX automation
stations and P-bus interface.
 Parallel operation with NCRS or Nitel.
 Wiring, supply.

For internal use only 55 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 In addition, the plant diagram and further technical documents must be
considered for migration:
 RS diagrams.
 Log TSP and calendar entries.
 Network restoration functions.
 E-max peak load program.
 tx2 Economizer
 Display of common fault messages, acknowledge and reset faults.
 Special application program functions.

Note The following data cannot be read from the RS modules and documented:
 Current setpoints from schedulers.
 Current runtime totalizers.

Existing object data Object data that already exists in the RS module and has been evaluated is not
displayed as a copy in the NCRS or NITEL project.

Restrictions RS  NMID (4-x multiplexer) and NMIDK (56-x multiplexer) not

module supported.
 Hint: Replace with TX-I/O.
NCRS  NCRS blocks
This version of the CDF Generator does not support:
 The following main groups from the DBS file:
– Smart 1 (US market)
– Smart 2 (US market)
– Pronto (room integration)
– PLC blocks (US market)
 Certain blocks, required mainly for logic operations, are also not
supported) e.g. LG2,MT2 etc.).
TS1500 Not all information can be read and documented from the *.abb file, as many bits of
information are located directly in NITEL.
Adding *.inf and *.asc files or *.AND file (in folder RC1500\RZINST) can provide more
information.

6.2.2 Document current RS module time schedules

RS Service or Online RS Access allows you to read the current time schedule
entries and print them in a text file.
1. Define a text file as Printer (in Windows)
2. Print or load the time program entries
8
Example RS Access - Rothwells [Rothwell], NCRS00, Trunk 1, RS01, Clocks
Report created Tuesday, May 31, 2006 13:08:52

Week schedulers
Weekdays, Time: State, Channels
1: Mon Tue Wed Thu Fri Sat Sun, 00:01: On, 1 - - - - - - -
2: Mon Tue Wed Thu Fri Sat Sun, 00:02: Off, 1 - - - - - - -
3: Mon Tue Wed Thu --- --- ---, 13:00: Off, - - - - - - - 8
4: Mon Tue Wed --- --- --- ---, 14:25: Off, - - - - - - - 8

56 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
Example (cont.) Date schedulers
Day/Month, Time: State, Channels
1: 00/00, 00:00: Off, - - - - - - - -
2: 23/06, 14:26: Off, - - - - - - - 8
3: 23/07, 14:26: Off, - - - - - - - 8
Exception schedulers
Start Day/Month, Start Time -> End Day/Month, End Time: State, Channels
No exception schedules available...
93 scheduler(s) available

6.2.3 Document scheduler in NCRS

Use Desigo Insight to create a printout of the current scheduler programs.

6.3 Create a migration project

Begin by setting the project settings and creating a new project.

6.3.1 Integral project settings

Set the options in 321-Workbench (Tools > Options).

321 tab 1. Select the report output format (e.g. Internet HTML format, Office).

Integral tab 2. Select the PX RS-bus export rules for output points and tabs (see also
CM2Y9762).
Generate EXPORT.sas file from SAPIM<n>.ASC file, if no Export.sas is
found:

For internal use only 57 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 Default export rules for PX-RS bus modules:

6.3.2 Create a new migration project in 321-Workbench

1. Select File > New Project.

2. Select the Integral UVI system and enter the project root.
Note: Neither the UVI system nor the project root path can be changed
retroactively.
3. Enter the project name.
A new project folder is created with the project name. Where applicable,
indicates that there is already a folder.
4. Enter the texts for the report.
5. Click Next >.
The Project settings dialog box opens.
6. Select access to the Integral data:
a) Option Go to Integral project folder:
This option reads the existing data from the Integral project folder (folder
containing the EPlan project data).
Note
 Select project name or individual trunks to NCRS.
 The original data remain unchanged.

a1) Select Go to Integral project folder.

a2) Enter the path to the engineering data.

58 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 b) Option Use RS-Reader and upload data online:
This option reads existing Integral data on the RS module.
b1) Select Use RS-Reader and upload data online.
b2) Select the COM port where the RS bus is connected (via NARC
interface converted).

b3) Click Start RS-Reader.

The RS-Reader reads all available I/O data via a NARC interface
converted from the RS modules and creates a separate *.csv file.
7. Click OK.
The data are read automatically from the Integral project folder or from the
*.csv file and stored to a new Workbench structure in the new project. The
original data remain unchanged.
The data (if available) are displayed by site, NCRS/NITEL, trunks and RS
modules in a tree view. The data sources used are displayed when clicking
the corresponding device:

8. Select the site.

9. Select the migration target (solution model) where you want to migrate to.
(PXC-NRUD, PXC-NRUF or PX RS-BUS).

For internal use only 59 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 6.3.2.1 Connect RS modules

Use an NARC interface converted to connect the RS bus to a PC COM port: The
RS232 interface (on the PC) is converted to RS485 (on the RS bus).

The PC (COM port) is connected via null modem cable to the interface (3). The flat
ribbon cable (6) is connected to the RS bus.
Use the RS-Reader to read all RS modules on a trunk.

6.4 Integral migration options

The workflows differ depending on the selected migration option (PXC-NRUD,

PXC-NRUF or PX RS-BUS).

6.4.1 Migrate to PXC NRUD

As PX generally has greater performance than an NRUA..NRUD RS module,

several NRUx modules can be mapped to a PX automation station (PXC-64/128 +
PBUS-BIM or PXC-100/200-D) via a PBUS-BIM. To do this, the NRUx modules are
grouped within the same group (e.g. group 0). The group number itself has NO
function.
PXC-NRUD actually is 6 virtual TX-I/O modules on one board. To address the 6
TX-I/O modules, only the base address (offset) of the first module must be
indicated (e.g. 1) for each PXC-NRUD. The remaining 5 modules are automatically
addressed continuously (2-6).

Per default, 321-Workbench automatically assigns the offset, i.e. at the first PXC-
NRUD, Offset =1 (addresses 1-6), at the second PXC-NRUD, Offset =7 (addresses

60 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 7-12) etc. The offsets generally must be adapted manually only if other (normal)
TX-I/O modules are connected to the same PBUS-BIM.

NRUA..NRUD migration The PXC-NRUD card has an island

to PXC-64/128-U with bus connection and can be
BIM and PXC-NRUD connected to a PXC-64/128-U
automation station via P-bus BIM.
The NK modules remain in the
PXC-64/128-U BIM PXC-NRUD NK modules
panel; PXC-NRUD replaces Integral
NRUD.

NRUA..NRUD migration As the PXC-NRUD card has an

to PXC-100/200 and island bus connection, it can be
PXC-NRUD connected to Desigo V4.1 using an
island bus supply TXS1.12F10 to a
PXC-100/200-D automation station.
PXC-100/200D PXC-NRUD NK modules
No BIM is required.

6.4.1.1 Features of the PXC-NRUD adapter for Integral NK modules

Features  The PXC-NRUD adapter can be connected to a Desigo automation

station PXC-64/128-U with P-bus interface module TXB1.P-BUS (BIM).
 As an alternative, a PXC-100/200-D (without BIM) can be used.
 The PXC-NRUD adapter serves as replacement for the modular
automation stations NRUA/A, NRUB/A, NRUC/A, and NRUD/A.
 The PXC-NRUD adapter has the same housing; the card can be
inserted in an existing NHGB housing.
 Same periphery interface (plug compatible).
 Existing periphery can be assumed without a change.

Data point mix for PXC- Device / Type Data point mix
NRUD PXC-NRUD UI DI UO/DO
Adapter for 48 physical data points. 16 8 16/8

Benefits  No panel rewiring from adapter to terminal module carrier; extension and
upgrade of panel with PXC..-U und P-bus interface module BIM or PXC-
100/200-D.
 Mapping in BIM via module type TXV1-8NK.
 TX-I/O modules are used for plant extensions.

The overview shows PXC-NRUD on a PXC-

64/128-U automation station with BIM.
Desigo V4.1 allows for connecting PXC-NRUD
direct to PXC-100/200-D.

Example 16 adapters in one 19" rack with 4 I/O islands

(groups).
 Adapters 1 ... 4 are connected via island bus
CD1, via BIM to AS01.

For internal use only 61 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 Example (cont.)  Adapters 5 ... 8 are connected via island bus CD2, via BIM to AS02.
 Adapters 9 ... 12 are connected via island bus CD3, via BIM to AS03.
 Adapters 13 ... 16 are connected via the island bus plug on the front plates.

Designed for:
 PXC64-U with 200 DP
 PXC128-U
 At 150 DP ca. 1 sec., at 250 DP ca. 2 sec., and at 350 DP ca. 3 sec. cycle
time

6.4.1.2 Configure BIM (using BIM tool)

BIM must be configured accordingly if the PXC NRUD adapter is used together
with a PXC-64/128-U (+ BIM). To do this, load an IOMD configuration file in the
BIM.
The IOMD file can be generated by opening the BIM tool if the I/O addresses are
checked in the I/O Address Editor and there are not conflicts.
1. Start the BIM tool via CFC menu Chart  BIM Tool.
2. The BIM tool starts and the generated IOMD configuration is loaded in the
tool.
3. The I/O configuration can be adapted in the BIM tool before loading it in BIM
via Tools  Write to BIM.

See the BIM tool online help file for detailed information.

62 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 6.4.2 Migrate to PXC NRUF

The Desigo PXC-NRUF automation station is a compact controller designed

specifically to migrate Integral NRUF. It is based on a 68k platform and is an
extension of PXC52.
The existing RS sheet metal housing is used. This primarily to ensure that the new
PX is fully compatible with regard to dimensions, pin placement and I/O mix to the
old Integral RS compact controller types NRUE und F with 48 I/Os.
In addition, PXC-NRUF provides a further 16 DI-I/O channels.

6.4.2.1 PXC-NRUF features

Features  Native BACnet automation stations with communication.

 BACnet/LonTalk.
 BACnet / PTP via modem.

 Stand-alone application or for use with linked system or devices.

 Supports the following operator units:

 QAX… room units.
 Local/network operator units (direct connection).
 System or web operation via system network.

 Replacement for NRUE/A, NRUF/A, and NRUT/A in Integral plants.

Benefits  Same housing, same design, same interfaces for periphery, i.e.
compatible plus; thus, the existing periphery can be assumed as
is.
 No panel rewiring for 1 to 1 exchange.
 Effort required for RS bus, possibly NRD24 data points on PXC-
NRUF.
 64 physical inputs / outputs.

Data point mix for PXC- Device / Type Data point mix
NRUF PXC-NRUF UI DI UO DO
Automation station for 64 physical 16 24 8 16
data points

For internal use only 63 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 6.4.3 Migrate to PX RS-bus

6.4.3.1 PX RS bus features

Features  Use PX RS bus to read and write data point

registers in RS modules.
 Data point register from RS modules are
mapped to BACnet objects.
 Reference mapping strings to address I/O
blocks (BACnet objects).
 Via PXC00-U and PXA30-RS
 And firmware: PX RS bus.
 And license code: ACT-OPEN. 01 RSBUS
 Via PXA30-N, NT, W1, W2 for BACnet / IP.

The following RS data point registers are

supported:
Features  All physical default data point registers: UI,
UDI, DI, UO, UDO, DO.
 All data points for setpoints, calculated points
and parameters: UZ, DZ, UP, DP, US, DS.
 InterRS data point register: UA, DA, UE, UE.
 Timer register: DU.
 Alarm register: DX, DY, DR.
 Operating mode and mode register: DW.
 Operating hours count: RTT.
 Module status: RSS.

Further functions  Time synchronization of the RS bus

supported.
 PX RS bus can be operated on the RS bus
parallel to existing NICO-N and NITEL interfaces.

64 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 6.4.3.2 Desigo addressing of RS blocks

M = RSNr (RegType.RegNr[DataFormat])

RSNr: 1..16 for RS module number

RegType: Register type number (table)
RegNr: Register type number (table)
Dataformat: BOOL for binary, FLOAT for all analog data points
Example RS module address 5, calculated analog input UZ12

Register type

Desigo data
Description

Read/Write
Register

I/O type
number

Desigo

format
Tabs
UI Universal 4 1..16 R AI FLOAT
input
M = 5 (50.12[FLOAT]) DI Digital input 5 1..8 R BI BOOL
UZ Universal, 50 1..99 R AI FLOAT
calculated

UP Universal 47 1..99 R AI or FLOAT

parameter AO feedback
101..199 W AO FLOAT
DP Digital 48 1..99 R BI BOOL
parameter 101..199 W BO BOOL

6.4.3.3 Communication block / Message block

Note PX-RS must be restarted if the communication block
settings are changed
(e.g. warm start via CFC), as the settings such as e.g.
ComInfo1, PX RS bus address, ComInfo2 can be checked
only during startup.
Communication Value range Description
Block Pin
ComInfo1 1..32 PXE-RS address on the RS
bus.
If not value is entered, 17 is
used.
ComInfo2 30..100 ms Application layer request delay.
If no value is entered, 30 ms is
used.
IOAddr M=1(1) fixed I/O address (internal only).

6.4.3.4 Licensing

PXA30-RS 2000 BACnet objects/data points.

Licensing 1000 data / information points from the RS modules in the PX RS
bus ACT-OPEN.01 application RSBUS via web CGU models (light,
regular and full) support 2000 BACnet objects.
The license helps protect the solution and is free of charge!
Firmware PX RS bus.

For internal use only 65 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 6.5 Generate CDF file and report

Function (Tools > CDF/Generate report) calculates the migration data. In

addition, the selected files are created (CDF and/or report files).
Details of the process, in the form of INFO, WARNING and ERROR messages, are
displayed in the log window or saved in the log file. WARNING and ERROR
messages are also written to the report file.
Generation is only carried out for the projects or modules selected in the tree
structure. If nothing is selected, the function is inactive. The same applies in
principle to the creation of CDF and report files.

6.5.1 Log window

The log window displays the steps during generation along with information,
warnings and error messages.
Note the following information in the log window:
– CANCEL: No properly functioning CDF file.
– ERROR: Migration not completed.
– WARNING: Indicates that a migration solution was generated that still requires
certain actions (e.g. replacement of hardware, manual adjustment of data points
etc.).

The contents of the last log window are saved in file

..\Projectname\_AL_Mig_Log\Generator.rtf

6.5.2 Generate report

The report is based on the following settings:

 Project settings: Determines the project information and description.
 Options: Determines the file name and path.
 Report tab: Determines the contents.

Note These settings must be defined prior to generation.

If Generate Report File (above the tree view) is selected, the report is created
automatically during generation.
A separate report is created for each process unit selected.
The reports are written to the folder ..\ProjectName\_AL_Mig_Report or to the
relevant PS folder (in accordance with the option selected via Tools > Options,
Generator tab).
After a report is generated, it can be displayed directly via the preview option
(Report Preview tab – this tab is not displayed unless a report is available).
Note The report can be created in various file formats (xml, html, doc) depending on the
option selected under Tools > Options; Generator tab).

66 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 6.5.3 Generate CDF file

If Generate CDF File (above the tree view) is selected, the report is created
automatically during generation. A separate CDF file is created for each process
unit selected.
The CDF files are written to the directory ..\ProjectName\_AL_Mig_Cdf or to the
relevant PS directories (in accordance with the option selected under Tools >
Options; Generator tab).

6.6 Evaluate report

Reports are important tools to check, document data point migration and select a
suitable Desigo solution.
After a report is generated, it can be displayed in the Preview.

 The report contains many important project and detailed information, but does
not replace required Integral knowledge to evaluate the program.

 The report provides information on: P-bus report and Integral tab and function
block information:

 P-Bus report  Integral F-block

 Integral tab  Memory link functions (F12.x)
 I/O  Ring counter (F13.1, F29.1)
 Setpoint/Parameter  Timer (F14.x)
 Alarm register (prio=1)  Logical functions (F16, F17.x,
 Alarm register (prio=2) F18.1, F19.1).
 Time schedule  Numeric functions (F20.x,
 Intermodule communication F21.x, F22.x).
 Intermediate values  Heating curve (F24.1)
 Integral F-block  Positioning time (F28.1)
 Pages (operating mode).  Digital output (F52.x)
 Setpoint functions (F1.3, F2.1, F3.x,  Analog output (F53.1)
F4.3, F27.1).
 Control sequence (F5.x, F6.x, F7.x,
F8.x)
 2-point control sequence (F9.x)
 Modulating additional sequence (F10.x)
 Channel switch (F11.x)

For internal use only 67 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 321-Workbench, Integral workflow 14.09.2011
 7 Accessibility of plant
 Check for space in the panel. Different front plate dimensions for PX automation
stations and UV controllers.
 Wiring test.

7.1 Visonik

The Visonik P-bus or TX-I/O report contains a rewiring list (EKL-X  PTM and
PTM  TX-I/O) for the panel builder.
The existing SDLC ring cabling can, parallel with SDLC operation, be used for
BACnet communications, provided performance requirements are not very high.
This is implemented via VDSL modems. For more information, contact Field
Support.

7.2 Unigyr

Profibus cabling on BACnet?

PTM  TX-I/O rewiring list

7.3 Integral

PXC-NRUF Note that serial interface RS232 to connect the telephone modem was moved
slightly (cable length).

PXC-NRUD Make sure that there is sufficient space in the panel for one (or several) PXC-
64/128-U and the corresponding number of TXB1.PBUS.

68 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Accessibility of plant 14.09.2011
 8 XWORKS plus: Select solution
8.1 Create PX application

Use the normal XWORKS plus workflow to create the PX application. The following
sections refer only to special aspects which should be noted when migrating UVI
controllers to a PX automation station.
The following documents contain information on selecting the right solution or
creating the application:
– 321-Workbench Report (e.g. for Unigyr: Desigo plant recommendation).
– Existing plant diagram.
– Other plant documentation.

8.1.1 Select a solution in XWORKS plus

1. Set up a new project in XWP Project Manager.

2. Create a suitable controller in the XWP Project-Manager or XWP Network-
Configurator: Example:
 PXC-64/128 for PTM modules.
 PXC-50/100/200 for TX-I/O modules or
 PXC-50/100/200 with PXX-PBUS for TX-I/O and PTM modules.
3. Select the automation station and go to
a. XWP Point-Configurator
b. CFC

8.1.1.1 Select a solution in Point Configurator

1. Select Get data points from solution in the Point Configurator.

2. Right-click the desired hierarchy and select a new solution.
3. The Solution Browser dialog box opens, allowing you to select a proven
solution.
4. Go to Automation Level Migration to load and map the legacy.

8.1.1.2 Select a solution in CFC

You can also select a solution in CFC or copy and adapt an existing plant from
another project.
1. Select the desired hierarchy in the Charts tab in the CFC.
2. Go to the Libraries tab and select the corresponding proven solution.
3. Drag and drop the solution in the CFC.

For internal use only 69 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Select solution 14.09.2011
 4. Exit CFC and go to XWP Point Configurator.
5. Go to task Automation level Migration.

See the XWP online help for detailed information.

70 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Select solution 14.09.2011
 9 XWORKS plus: Point Configurator
mapping
Start XWP Point Configurator from XWP Project Manager or XWP Network
Configurator. Use task Automation Level Migration in XWP Point Configurator to
map the UVI data points.

1. Load UVI migration data in XWP Point Configurator.

The UVI migration data (CDF file) created in 321-Workbench can now be
loaded into XWP Point Configurator.
The CDF file(s) are in the migration project directory:
..\ProjectName\_AlMig_Cdf\*.cdf*“
2. Select File > Import CDF File…
UVI migration data are loaded and displayed in the UVI table.

Caution!  Pay attention to what is generated in 321-Workbench. When, for example,

migrating to PXC-64/128 while keeping the PTM modules in 321-Workbench,
the CDF file cannot be loaded in a PXC-50/100/200 automation station.

 Vice-versa, a CDF file created for migration to PXC-50/100/200 (with TX-I/O

modules) no longer can be loaded in a PXC-64/18 automation station!

In XWP Point Configurator, a number of CDF files from different UVI controllers can
be loaded (e.g. in cases where several were merged to one PX automation
station).
Note To avoid address conflicts, you must set up 321-Workbench accordingly (e.g.: via
TX-I/O address offset)!
When several controllers were loaded in the XWP Point Configurator, they can be
removed individually by selecting the automation station and Unload CDF (right in
the legacy view).

For internal use only 71 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
 9.1 Mapping options

Set the mapping options via Tools  Options or the toolbar.

You can take over (description) texts and unit texts. The following options are
available:
Unigyr Visonik Integral
Description text Name TXI, TXI2, TXI3, Description or
Text normalization, object name
Text replacement (ä,ö,ü)
Selection: (No action, take over text, append text).
Unit text Take over selectable unit texts (default setting is off).
User designation UD Select if User Designation (UD) is
taken over (default is Off).

Important – In PX, the data point description is limited to 32 characters. If this limit is
violated, the text is limited to 32 characters and a warning is output.

– XWP Point Configurator allows you to edit the texts in the Desigo object table.

Notes – From now on, this setting applies to all future mappings.

– The text taken over is displayed in the left pane when you take over legacy texts
during mapping. The text is not reset when you resolve the mapping.

– However, you can edit the text any time in the Desigo object table.

72 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
 9.2 Map data points

The procedure to map data points differs individually and dependent on the project
(e.g. technical hierarchy structure or data point type).
We generally recommend the following two steps to map data points:
1. Map all possible legacy data points to the selected solution.
2. Check all unmapped legacy data points and newly engineer the associated
data points in either XWP Point Configurator or CFC.
3. Map all remaining data points to the newly created PX data points.
4. Address all remaining PX data points.
Hint: Previously mapped data points can be hidden.

Hide previously mapped data points in Point Configurator

Hint: Check if the text mapping rules are set correctly prior to mapping.

9.2.1 Map data points

We recommend to map data points by type. To do this, use the context-sensitive

data point filter which works on both the PX data view as well as the legacy (UVI)
data view.

1. Select the legacy (UVI) data point in the legacy data view. You can set
additional filters to further limit the selection.

For internal use only 73 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
 2. Select the data point and map to the corresponding PX data point.
Important! XWP Point Configurator only allows for technically feasible and meaningful
mappings. You can only once map a data point. Corresponding parameters are
taking over during mapping; Description texts and Unit texts are taken over as per
the Option dialog box settings. The signal type is taken over from the legacy
attributes where possible.

General explanations on "Automation Level Migration", or the above picture:

 The lower two tables show detailed information on the selected legacy object
row.
 The legacy object is selected when a mapped Desigo object is selected (or vice-
versa).
– A tooltip on the Desigo object row shows the mapped legacy objects.
– A tooltip on the Type legacy object column shows the compatible Desigo
object type.
– A tooltip on the CDF combo box shows the CDF file loaded originally.

9.2.2 Feedback mapping

XWP Point Configurator allows you to map feedback to a PX data point (AO, BO,
MO) on outputs.
If, for example, you are mapping a Visonik SBR1 DP to a PX-BO, the feedback
address is mapped automatically also. You can manually map another Visonik ML
to the corresponding PX-BO, if you want to first map a different feedback. However,
you must always first map the output.
The mapping must be technically feasible, i.e. the corresponding modules (PTM,
TX-I/O) must support it.

74 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
 9.2.3 Multistate mapping

XWP Point Configurator allows you to map several data points to a PX multistate
data point (MI, MO).
For example, two Visonik ML data points can be mapped to one PX MI data point
while at the same time allowing for defining the signal sequence via a popup dialog
box.
Selection of signal
sequence for multistate
mapping

The same is true when mapping several data points to an MO (including feedback).
With MO, the output signals must be mapped before feedback. Thus for example, a
Visonik SB1 to a PX-MO (with 2 Visonik ML to the MO as feedback).
Multistate mapping
with feedback

The above example shows multistate mapping of Visonik SBR2 and SBR to Desigo
MO. In this case, the feedback of the SBR is mapped also. In the selected data
point, two Visonik ML data points (1.1 and 1.2) were mapped individually as
feedback.

Caution!  Take note if you are mapping to PTM or TX-I/O modules during multistate
mapping.
 Restriction when mapping to TX-I/O modules: Mapping several legacy
BI/BOs to one Desigo MI or MO requires that all data points be located on the
same module, and that the channels are in sequence without gaps.
 This restriction does not apply to PTM modules where an MO can be located on
any modules/channels.

For internal use only 75 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
 9.3 Map trend objects

When they are migrated to Desigo, trend objects already contain a BACnet
reference to the data point to be logged.
1. Map first the trended UVI data points (e.g. outside temperature or counter
values) to the corresponding PX data points. (Red in the picture).
2. Trendlog objects cannot be created in Point Configurator. Create thus the
required Trendlog objects in the CFC.
3. Map the UVI trend objects (Visonik trend object, Unigyr registration object) to
the PX trend log object (TRNDLOG).
(Blue in the picture).

The data point information (e.g. technical address (TD), BACnet reference) is
adopted automatically in this process.

4. Create a mapping file (e.g. ADP trend mapping file) to check the trendlogs.

76 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
Caution!  You must always first map or import trended data points, followed by the
associated trendlog objects.

 Only the trend block's object parameters are taken over if values not from a
mapped I/O data point were recorded with the trend block.
In this case, you must manually revise the BACnet references to the objects in
the CFC.

9.4 Create data points in Point Configurator

XWP Point Configurator allows you to create PX data points from legacy (UVI) data
points.
1. In the legacy data view, select several data points (multiple selection) and
drag and drop them in the PX Tree view for mapping (in the desired
hierarchy).

2. The Define Names dialog box opens after you drag and drop the data
points in the hierarchy. You can now select a short name and the desired
start index. When mapping several data points, the index based on the start
index is incremented by 1.
Sound and meaningful naming is really important, as the data point name
should match that of a later Insight genie.

The created data points are displayed as mapped data points. The
associated, transformable parameters are taken over.

For internal use only 77 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
Hint The dialog box allows for multiple object selection. As a result, you can create
many objects in the right PX structure at the same time (e.g. electric data points or
additional message points).

9.5 Generate in the CFC

We recommend to check CFC data for completeness and make sure there are not
errors prior to generating the CFC data. You can do this in Point Configurator or the
generated Excel checklist.

Are all data points mapped?

Two variants to check:

Variant 1: 1. Visual check to see if all PX data points are mapped to a legacy data point.
2. Select "Hide mapped objects" to no longer display PX data points.

Variant 2: 1. Create a mapping table (to check) via "Generate Mapping File".

2. A CSV file is created under the corresponding AS. You can filter column
"Mapping" for all assigned data points (MAPPED), PX data points not mapped
(Desigo) as well as legacy data points (e.g. Visonik) not yet mapped.

Mapping table (CSV file)

Create CFC data The mapped data points are created in the CFC via a file followed by navigation to
the CFC Editor.
11 Select File  Generate CFC data and Exit or click the button to create the
CFC data.

12

Hint Appendix A lists possible CFC generation errors.

78 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
9.6 Take over parameters

The tables below list all the parameters of the legacy systems (UVI) transferred when mapping objects to the PX blocks.

For internal use only 79 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 04.09.2011
 9.6.1 Data import limitation (Unigyr)
9.6.1.1 Interconnected pins

A value can only be adopted from a Unigyr program if the value was entered
directly at the relevant pin of the Unigyr block. If the value is supplied to the pin via
a connection, it cannot be adopted.

9.6.1.2 Value range

If values greater than the permitted Desigo value range from a Unigyr program are
to be taken over, an error message is displayed (value greater than value range);
e.g. current counter status of counter value in Unigyr = 80000, but the counter
value is limited to 50000 (PrVal.Max) in Desigo.

Procedure Set PrVal.Max of the relevant Desigo object manually to a sufficiently high value.
Caution Parameters PrVal.Max and HiLm are interdependent. If PrVal.Max is set to infinity,
HiLm in Desigo Insight can only be set with the slider with great difficulty. For this
reason, set a realistic value for PrVal.Max.

9.6.2 Take over engineering units

When mapping objects, the units are transferred together with the PX parameters
(selected in the Options dialog box). As a rule, unit texts are not taken over, as the
units in the Desigo solutions already contain the right unit texts.
If units are still taken over from a legacy system, they can be taken over as is, or
via unit mapping file translated in a standard Desigo unit.
In this case, the mapping can be defined directly in the mapping file. Units that are
not yet supported by the Desigo system must be converted appropriately.

Add to the unit 1 Öffnen Sie die Unit Mapping-Datei mit Notepad:
mapping file C:\Program Files\Siemens\Desigo\XWP500\Bin\DMEUnitMap.xml
2 Add the missing unit to section <UserDefinedUnits>.
The relevant PXUnitId is located in
<PxDefinedUnits> further below.

Note: We recommend creating a

backup copy prior to editing the units.

80 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Point Configurator mapping 14.09.2011
 10 XWORKS plus: Revise in the CFC
After mapping UVI data in XWORKS plus Point Configurator, the solution is
generated in CFC data storage.

10.1 Clean up I/O address conflicts in CFC

The mapped data generated by XWP Point Configurator is now loaded into the
CFC. In the event of address conflicts, use the CFC I/O Address Editor to check
them.

1 Open the corresponding AS in the CFC.

2 Clean up the Desigo project by opening the I/O Address Editor.
Check for conflicting I/O addresses in the CFC I/O Address Editor.
Check the correct modules and signal types.

Note New: You can connect PTM modules directly to the PXC-50/100/200 usign the
PXX-PBUS extension module. Note that data point addressing must defer to the
subsystem (island bus, P-bus). Thus, address P=1.1 and T=1.1 is possible.

10.1.1 Special note for Integral

Check the following settings in the I/O Address Editor of the CFC.

 I/O Address Editor: Check module type, data points and units.
 I/O address conflicts.
 Further settings to check:
o Controller setting.
o Scheduler programs / calendar entries.
o Storage for trendlog objects, i.e. notification threshold and buffer size,
interval.
o Modem setting.
o Heating curves / HRA / OSSC.
o Delay times/Timer/alarm response and properties.
o Plant control and operating modes in ENSEL_MS, CMD_CTL,
PWR_CTL.

All settings are listed in the migration report.

10.1.1.1 Solution PXC-NRUD (via BIM)

Remember to check the following for PXC-NRUD via BIM (bus interface module)
and adapt as needed (via the CFC, I/O Address Editor):
– Definition of data points and module types: In PXC-NRUD, the module type must
be set for all I/Os to value TXV1.8NK.
– Multistate inputs and outputs require manual adjustment.
– Manually set feedback addresses.
– Manually revise units (unit texts) as needed.

For internal use only 81 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Revise in the CFC 14.09.2011
 – If PXC-NRUD is connected directly to the PXC-50/200/200, the module is set
direct to NRUD in the Point Configurator.

10.1.1.2 Solution PXC-NRUF

Manually revise as needed in the I/O Address Editor analogous to PXC-NRUD (see
section 10.1.1.1 )

10.1.1.3 Solution PX RS bus

The specific settings were set previously via the options in 321-Workbench.

Note We recommend to activate all options for RS bus. This at most generates more
DMAP objects than needed in XWORKS plus. They can be removed in the CFC.
Furthermore, the settings assumed automatically can be revised retroactively in the
I/O Address Editor as needed analogous to PXC-NRUD (see section 10.1.1.1)

10.2 Save project data on the BOS

XWP Point Configurator automatically saves its data in AlMig, located within the
AS project data. As a result, data generated in XWP Point Configurator, are saved
automatically to the BOS server.
1. Go to AlMig data:
2. Select the AS in XWP Project Manager.
3. Right-click and select Go to storage location“.
4. Subfolder AlMig contains the associated data.

Important! The data from the legacy system (UVI) and the migration project folder of 321-
Workbench (CDF, report) is not saved in this folder. If e.g. the 321-Workbench
project or the corresponding legacy files are (e.g. Unigyr PLN file) are to be saved
also, we recommend copying it to the Al-Mig subfolder or administer the legacy
data as Misc folder in the XWP project.

82 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies XWORKS plus: Revise in the CFC 14.09.2011
 11 Migrate PDM/ADP/CC data
The goal of migration is to keep the old data series and replace it with the
corresponding new series for data upload. This means that the old, base-data
series is replaced and deactivated for data import. The migration tool creates a
logical data series to join the old and new series together. The old series is
replaced by a new logical series in reports or calculated series.
The following model shows how the new data series is joined with the old data
series.

After migration in Toolbox.net, the ADP reports contain a link to a new created
logical data series and not to the old base or derived data series as before. The
executed report containing the link to the logical displays both data from the old
and the new data series.
In the migration tool Toolbox.net only base data series are displayed as possible
source series. No derived series is displayed for migration. But how about derived
data series? Migration automatically creates a new derived data series for an
existing one to get the same structure as before. The old and new derived data
series are joined together by a new logical data series. This logical data series is
referenced in calculated data series and reports.

Trend mapping file The information on trended UVI data points (old data) and the mapped PX data
points (new data) can be created in a trend mapping file (.CSV) in XWORKS plus
Point Configurator. This contains a summary of all the available migration data and
is suitable for setting up the ADP migration.

Mapping trendlog objects is described in Section .

For internal use only 83 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Migrate PDM/ADP/CC data 14.09.2011
 12 Adapt Desigo Insight
Existing Desigo Insight graphics cannot be adopted automatically in the course of
migration to Desigo PX. The graphics must be revised manually. Note that all the
existing genies in the UVI libraries must be replaced in this process. Genies from
the global library (G library) and static graphics such as pipes, ducts or text items
can still be used. With the aid of DIGG and the integrated report function, a list can
be created showing the genies used. This makes it easy to check for "alien"
genies on the page or in the project after editing.

Procedure 1 Start the Graphics Generator.

2 Select Report > Pages.
3 Select the checkboxes to select the relevant pages.

4 Click Start. The report is created and saved in project folder \diggdata.
5 Open the Report.txt file with a text editor.
6 Select Edit > Find.
7 For Visonik enter "DCS" as the search criterion.
For Unigyr enter "Unigyr" as the search criterion.
For Integral enter "NCRS" as the search criterion.
8 Click OK.

Sample Report.txt file: Page Grafik.AHU1 contains:

Object: Genie(PX.p2_ya000.ca000_3_tz01_sg)
Property: Field(Privilege) = "2"
Property: Field(Area) = "0"
Property: Field(TD_AI) = "Site_A_TSu"
Property: Field(Pin) = "PrVal"
Object: Genie(DCS.v2_ya000.ca000_3_tz01)
Object: Genie(Unigyr.u2_ya000.ca000_3_tz01)
Object: Genie(NCRS.u2_ya000.ca000_3_tz01)
Property: Field(Area) = "0"
Property: Field(a_feedback) = "Site_0_RSUAI_1"

84 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Adapt Desigo Insight 14.09.2011
 13 Appendix A
13.1 CFC import error messages

The data to be migrated is checked during import into CFC. The following list
provides an overview of the various error messages and their possible cause.

Error Text
number
2200 Error in [%Object%]. Description: Could not find parameter
[%Parameter%].
Cause Mapping of objects with different numbers of parameters.
e.g. BI to BVAL
Action Check that the right objects were mapped.
2225 Error in [%Object%]. Description: Pin variable of parameter
[%Object%] not found.
Cause Mapping of objects with different numbers of parameters.
e.g. BI to BVAL
Action Check that the right objects were mapped.
2235 Error in [%Object%]. Description: Invalid attribute [%Object%] in
parameter [%Object%]. %s
Cause Parameter is outside the valid range.
Action Adapt PrVal.Min or PrVal.Max.
2240 Error in [%Object%]. Description: Could not write attribute
[%Attribute%] in parameter [%Parameter%].
Cause Parameter is wired in the CFC and cannot therefore be
written e.g. calculated or pre-processed setpoint in PX.
Action Check that the parameter value is relevant for the PX
application, If necessary this parameter value must be
entered in a different place in the application.
2255 Could not write shortname for [%Object%]. Description:
Cause Invalid character in "Short name" e.g. Pu_St1. The only
valid characters are a…Z and 1…9.
Action The short name for the block is not written and must be
edited manually in the CFC.
2256 Error in [% Object%] Description: Duplicate TD name. The second
Object and its children will be ignored
Cause The same object name occurs twice at the same
hierarchical level. CFC is case-sensitive: VentZuSt,
VentZuST.
Action One of the two object names must be corrected.
2260 Could not write description for [%Object%]. Description:
Cause The text description is longer than the 32 characters
permitted in PX.
Action Check and modify text in the Mapping view of XWP
Point Configurator.

For internal use only 85 / 86

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies Appendix A 14.09.2011
Siemens Switzerland Ltd
Infrastructure & Cities Sector
Building Technologies Division
Gubelstrasse 22
6301 Zug
Schweiz
Tel. +41 41-724 24 24 © 2009-2011 Siemens Switzerland Ltd
www.siemens.com/sbt Subject to change

86 / 86 For internal use only

Siemens DESIGO Automation level migration CM110776en_05

Building Technologies 14.09.2011