61627479 Application AdvES En

7/28/2019 61627479 Application AdvES En

1/113

Applications & Tools Answers for industry.

Cover

Performance Mass Data Engineering with PCS 7 Advanced ESon a Practical Example

SIMATIC PCS 7

Application Description July 2013


2/113

2SIMATIC PCS 7 Advanced ES

V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Industry Automation and Drive Technologies Service & Support Portal

This article is taken from the Service Portal of Siemens AG, Industry Automationand Drive Technologies. The following link takes you directly to the download pageof this document:

http://support.automation.siemens.com/WW/view/en/61627479
http://support.automation.siemens.com/WW/view/en/61627479http://support.automation.siemens.com/WW/view/en/61627479


3/113

SIMATIC PCS 7 Advanced ESV2.0, Entry ID: 61627479 3

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

s

SIMATIC PCS 7

Performance Mass DataEngineering with PCS 7 AdvESon a Practical Example

Application Description

Task 1

Solution 2

Creating and Adaptingthe PCS 7 Project 3

Configuring with AdvES 4

Conclusion 5

Further Links 6

History 7


4/113

Warranty and Liability


V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Warranty and Liability

Note The Application Examples are not binding and do not claim to be completeregarding the circuits shown, equipping and any eventuality. The applicationexamples do not represent customer-specific solutions. You are responsible for ensuring that the described products are used correctly. These applicationexamples do not relieve you of your responsibility to use safe practices inapplication, installation, operation and maintenance. When using theseapplication examples, you recognize that we cannot be made liable for anydamage/claims beyond the liability clause described. We reserve the right tomake changes to these application examples at any time without prior notice. If there are any deviations between the recommendations provided in thisapplication example and other Siemens publications e.g. catalogs thecontents of the other documents have priority.

We do not accept any liability for the information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc.,described in this application example will be excluded. Such an exclusion will notapply in the case of mandatory liability, e.g. under the German Product Liability Act(Produkthaftungsgesetz), in case of intent, gross negligence, or injury of life, bodyor health, guarantee for the quality of a product, fraudulent concealment of adeficiency or breach of a condition which goes to the root of the contract(wesentliche Vertragspflichten). The damages for a breach of a substantialcontractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury tolife, body or health. The above provisions do not imply a change of the burden of proof to your detriment.

Any form of duplication or distribution of these application examples or excerptshereof is prohibited without the expressed consent of Siemens Industry Sector.


5/113

Preface


C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

PrefaceObjective of this application

This application describes the functionality of a PCS 7 Advanced Engineering

System V8.0 (AdvES) based on a practical example.Furthermore, the advantages of AdvES in comparison to the import/export wizardare explained.

Main topics of this application

The following core points are discussed in this application:

Describing AdvES and its advantages

Configuring an example project using AdvES

Validity

Valid from SIMATIC PCS 7 V8.0 SP1(incl. option package PCS 7 Advanced Engineering System V8.0 SP1)


6/113

Table of Contents


V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Table of Contents

Warranty and Liability .............................................................................................. 4

Preface ...................................................................................................................... 5 Table of Contents ..................................................................................................... 6

1 Task................................................................................................................. 7

2 Solution........................................................................................................... 8

2.1 PCS 7 Advanced Engineering System ....... ....... ....... ........ ....... ....... .... 8 2.2 AdvES advantages ........ ....... ....... ........ ....... ....... ........ ....... ....... ....... . 10 2.3 AdvES Principle of Operation ........................................................... 12 2.4 Required engineering components................................................... 15

3 Creating and Adapting the PCS 7 Project ................................................... 17

3.1 Required prerequisites of the PCS 7 project ..................................... 17

3.2 Creating a project ............................................................................ 18 3.3 Deriving a CMT from Advanced Process Library (APL) ............ ........ 23 3.4 Changes in the CMT and the technological connections............ ....... 26 3.5 Configuring optional blocks of the "ValveAnalog" CMT ....... ........ ...... 30 3.6 Configuring messages ..................................................................... 31

4 Configuring with AdvES ............................................................................... 33

4.1 Data import from PCS 7 to AdvES ................................................... 33 4.2 Assigning mapping labels for the technological I/Os of a CMT ........ .. 39 4.2.1 Assigning the mapping labels ......... ........ ....... ....... ....... ........ ....... ..... 42 4.2.2 Creating variants and copy templates in AdvES ........ ....... ....... ........ . 46 4.2.3 Creating individual mapping labels ....... ....... ....... ........ ....... ....... ........ 49 4.2.4 Transferring mapping labels ............................................................. 53 4.3 Data import of external data ....... ........ ....... ....... ....... ........ ....... ....... ... 55 4.3.1 Creating the configurator for importing ............................................. 58 4.3.2 Importing Data ................................................................................. 71 4.4 Specifying control modules .............................................................. 75 4.5 Configuring connections .................................................................. 80 4.5.1 Determine connections at the CMTs ................................................ 80 4.5.2 Execute interconnections for the CM instances ........ ....... ....... ........ .. 82 4.6 Assigning hardware ....... ....... ....... ........ ....... ....... ........ ....... ....... ........ 84 4.7 Consistency check ........................................................................... 91 4.8 Exporting data to PCS 7 .................................................................. 94 4.9 Other useful functions in AdvES ..................................................... 103 4.9.1 Report folder.................................................................................. 103 4.9.2 Control module (CM) test sheets ........ ....... ....... ........ ....... ....... ....... . 105

Procedure ...................................................................................... 105 4.9.3 Table views ................................................................................... 107 4.9.4 Project properties .......................................................................... 110

5 Conclusion.................................................................................................. 111

6 Further Links .............................................................................................. 112

7 History ........................................................................................................ 113


7/113


8/113

2 Solution


V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

2 Solution

2.1 PCS 7 Advanced Engineering System

SIMATIC PCS 7 Advanced Engineering System (AdvES) expands the functionalityof the system configuration. It serves as a link between standard engineering toolsfrom the SIMATIC PCS 7 Engineering Toolset (CFC, HW config, technologicalhierarchy (Plant Hierarchy)) and basic and detail planning tools, e.g. EPlan,ELCAD, or SmartPlant.

Properties

AdvES is a SIMATIC PCS 7 optional package.

AdvES prepares data for use in the PCS 7 ES.

AdvES is an application for importing data.Data can be imported into AdvES from process tag and signal lists and can betransferred to PCS 7 ES.

After a first assignment, AdvES will detect the control module types (CMTs)and automatically generate the control modules (CMs).

In this context, technological hierarchy, signal, and parameter settings canautomatically be taken over from the process tag and signal lists.

Hardware (decentralized periphery including channel assignment) can begenerated from the signal lists.

Object-dependent mass data processing and queries are possible.

Figure 2-1: Engineering with AdvES

Note Automatic generation of SFCs is not yet possible in this version of AdvES.


9/113


10/113

2 Solution


V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

2.2 AdvES advantages

General information

Reduction of configuration and start-up times Easier qualification through standardized interfaces Less coordination efforts with the systems planner Technological engineering in Advanced ES without PCS 7 system

knowledge Changes to process tags can be exchanged bidirectionally

Increase in quality Fault prevention through standardized interfaces Verifiability of plausibility and data consistency

Secured return of automation changes to systems planning Change management for supplied planning data

Saving the expenditures for creating and maintaining separate tools andsolutions

Advantages of AdvES over the import/export wizard

The following table shows the advantages of AdvES over the import/export wizard:

Table 2-1: Comparison of AdvES and import/export wizard

Import/export wizard PCS 7 Advanced Engineering System

- Import of arbitrary Excel structures isnot possible. An IEA file must becreated for each process tag typeprior to every import of process tag or signal lists.

+ Any Excel structures can be imported.Process tag or signal lists can beimported directly without intermediatesteps.

- No change identification duringimport

+ Change identification during Excelimport


11/113

2 Solution


C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Import/export wizard PCS 7 Advanced Engineering System

- No support of the new type concept(CMT and CM)

+ Support of the new type concept(CMT and CM)

- Not extendable for functional planning and E&ICplanning with COMOS

+ Extendable for functional planningand E&IC planning with COMOS

- No check for data plausibility andcompleteness

+ Check for data plausibility andcompleteness.

- No generation of the PCS 7 hardwareconfiguration

+ Generation of the PCS 7 hardwareconfiguration

+ Change management for dataexchange with PCS 7

+ Table editors with conveniencefunctions for searching/filtering/fillingout

+ Well-structured user interface

+ Rule-based interconnecting of process tags


12/113

2 Solution


V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

2.3 AdvES Principle of Operation

General overview

With AdvES you can import engineering data such as hardware, control moduletypes (CMs) and the technological hierarchy from the SIMATIC PCS 7 processcontrol system in AdvES and merge it with data from process tag and signal lists(in Microsoft Excel format).The data from process tag and signal lists can be automatically imported in AdvES.When exporting data from AdvES to PCS 7, the technological hierarchy, the controlmodules (CMs), symbolic names and the appropriate I/O modules are generated inPCS 7.

Note AdvES provides the user with an integrated change management for importingchanged data from Microsoft Excel.

Note Within AdvES, you can also manually create the CMs, signals, parameters, etc.on the basis of the imported CMTs.

AdvES is based on an object model which is different from that of the PCS 7 world.

The AdvES database model is based on a relational SQL database. In thisdatabase, data records are stored as objects.

The properties of an object depend on the type that the object is based on.

There are 5 object types in AdvES:

Technological Hierarchy (TH)Control module (CM)

CM parameter

CM signal

Signal parameter

Note The AdvES database is not identical with the PCS 7 database. It will not bearchived together with the PCS 7 multi-project.

The AdvES database must be secured separately.This procedure is described in detail in chapter 2.5 of the Process ControlSystem PCS 7 Advanced Engineering System manual.


13/113

2 Solution


C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Every AdvES project includes many objects of these types; each of these mustadhere to a certain structure:

TH folders can be found underneath the object node or underneath other THfolders.

CMs are inside TH folders.

CM parameters are placed underneath CMs.

Signal parameters are placed underneath signals.

Signals are placed underneath CMs.

Figure 2-3: Objects in AdvES


14/113

2 Solution


V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Overview of the AdvES workflow

The figure below shows the AdvES principle of operation:

Figure 2-4: AdvES Principle of Operation


15/113

2 Solution


C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

2.4 Required engineering components

Advanced Engineering is an independent application for additional installation on

the PCS 7 engineering system already installed. AdvES is subject to license and free storage capacity of about 2 GB will berequired. A setup is available for installation.

The application was set up with the following components:

Standard software components

Table 2-2: Required software

Component No. Order number Note

SIMATIC PCS 7 V8.0SP1

1 6ES7658-5AX08-0YA5 Updating the SIMATICPCS 7 V8.0 software or V8.0 update 1 to V8.0

SP1:

http://support.automation.siemens.com/WW/view/en/6779812 2

SIMATIC PCS 7 Advanced EngineeringSystem V8.0

1 6ES7658-1GX08-2YA5 Updating the SIMATICPCS 7 V8.0 AdvancedEngineering Systemsoftware or V8.0 update 1to V8.0 SP1:

http://support.automation.siemens.com/WW/v

iew/en/6840270 1 MS Excel 2003 All Excel versions that are

approved for therespective SIMATIC PCS7 version.

Sample files and projects

The following list contains all files that are used in this example.

Table 2-3: Supplied project files

Component Note

DEMO_AdvES.zip This zipped file includes a PCS 7library with 4 CMTs and oneExcel signal list

61627479_Application_AdvES_en.pdf This document.

Note The types used in the examples must be checked for use outside of thisapplication.
http://support.automation.siemens.com/WW/view/en/67798122http://support.automation.siemens.com/WW/view/en/67798122http://support.automation.siemens.com/WW/view/en/67798122http://support.automation.siemens.com/WW/view/en/68402701http://support.automation.siemens.com/WW/view/en/68402701http://support.automation.siemens.com/WW/view/en/68402701http://support.automation.siemens.com/WW/view/en/68402701http://support.automation.siemens.com/WW/view/en/68402701http://support.automation.siemens.com/WW/view/en/68402701http://support.automation.siemens.com/WW/view/en/67798122http://support.automation.siemens.com/WW/view/en/67798122http://support.automation.siemens.com/WW/view/en/67798122


16/113

2 Solution


V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Example project

The ZIP file includes a library with 4 CMTs from the basic control module libraryand a signal list for the example project.The signal list includes information for 170 CMs, TH, hardware, signals andparameters.

The following steps must be taken to import, generate, and export this data toPCS 7 through AdvES:

Table 2-4: Configuration steps in AdvES

Chapter Action

3 Creating and Adapting the PCS 7 Project

4.1 Data import from PCS 7 to AdvES

4.2 Assigning mapping labels for the technological I/Os of a CMT

4.3 Data import of external data

4.4 Specifying control modules

4.5 Configuring connections

4.6 Assigning hardware

4.7 Consistency check

4.8 Exporting data to PCS 7

4.9 Other useful functions in AdvES


17/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d


3.1 Required prerequisites of the PCS 7 project

Prerequisites for working with AdvES are the following components in the PCS 7multiproject:

A master data library with the required control module types.

At least one sub-project with an AS.

At least one PROFIBUS master system in the hardware configuration of the AS.

Figure 3-1: Project step in the overall workflow


18/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

3.2 Creating a project

Procedure

1. Open the SIMATIC Manager.

2. Create a new multi-project with a sub-project using the 'New project'Wizard.File > New Project Wizard...

Figure 3-2: Creating a multi-project

The PCS 7 Wizard: New Project opens.

3. Click on the Next button.

Figure 3-3: PCS 7 Wizard: New Project dialog


19/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4. Select a "AS 417-4" CPU with a matching bundle.

5. Select "0" for the "number of communication modules" of the CP-443-5 in thedrop-down menu.



7. Select 1 for the number of levels for the technological hierarchy. OS objectsfor PCS 7 OS, SIMATIC BATCH, route control and open PCS 7 are notrequired.


8. Click on the Next button. Assign a suitable name for the project, e.g. AdvES_example.

9. Then click on the Finish button. A new PCS 7 multi-project is generated.


20/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d


10. When you have created the project, change the name of the AS to AS1 andthe Process cell(1) technical hierarchy folder to Process cell.

11. Delete the plans SFC(1) and CFC(1) in the Process cell technologicalhierarchy folder.

Figure 3-7: Deleting the plans

12. Open NetPro in the toolbar of the SIMATIC Manager

and delete the MPI bus there.

Figure 3-8: "NetPro


21/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

13. Retrieve the included library with the CMTs.

Figure 3-9: Retrieving library

14. Drag the included CMTs ("AMON_Std", "CTRL_Std", "MOT_1sp_2fb_1cm"and "MOT_2sp") into the master data library of your project.

Figure 3-10: Accepting the control module types

Note As of V8.0, PCS7 provides you with a new type concept which, together with

PCS 7 Advanced Engineering (AdvES), allows for improved mass dataengineering as well as for changes to control module types already instantiated.

For details on the new type concept, please refer to chapter Handling of controlmodule types in the SIMATIC Process Control System PCS 7 CFC for SIMATIC S7 (V8.0) function manual.


22/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 3-11: PCS 7 configuration

The default functions areautomatically created when youare dragging the CMTs into theproject.


23/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

3.3 Deriving a CMT from Advanced Process Library (APL)

Procedure

1. Open the "PCS 7 AP Library V80" library and drag the process tag type"ValveAnalog" into the "Process Tag Type" folder of the master data library.

Figure 3-12: Integrating the ValveAnalog process tag type

2. Select the ValveAnalog process tag type, open the context menu and clickProcess Tag > Create/Change Process Tag Type...:The Create/Change Process Tag Type... dialog box opens.


Figure 3-13: Adapting the "ValveAnalog" type


24/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4. Delete all connecting points for parameters and signals.

Figure 3-14: Deleting the connecting points of the "ValveAnalog" process tag type

5. Click on the Finish button.

6. Delete any external interconnections in the chart of the type.

7. Select the Process tag types folder in the master data library of your multi-project and open the context menu.

8. In the context menu, select Control Modules > Create control module typefrom process tag type....

A selection dialog box opens.

Figure 3-15: Converting process tag types into CMTs


25/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 3-16: Selection dialog for converting process tag types into CMTs.

The CMT will now be created in the master data library.

9. Delete the "ValveAnalog" process tag type and assign the name "ValveAnalog"to the "ValveAnalog(1)" CMT.

Figure 3-17: "ValveAnalog CMT


26/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

3.4 Changes in the CMT and the technologicalconnections

Procedure

1. Open the "ValveAnalog" control module.

2. Open the Technological connections view in the CFC Editor.

3. Check the assignment of the control module type. A ValveAnalog chart must be assigned to the name of the ValveAnalogcontrol module in the field of the Assignment column and the Name row(see Figure 3-18 ).

Figure 3-18: Assigning the control module name

4. If this is not the case, right-click into the field of the Assignment column andthe Name row. The "Plan ValveAnalog" button will open. Click on the buttonand you will have assigned a plan to the name.

Figure 3-19: Assigning the control module name

NOTICE If this assignment does not exist, the chart names of the instances will notbe created correctly in the process of creation.


27/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

5. Select the "ValveAnalog" object and open the object by right clicking thecontext menu of the object.

6. Click on the Insert new object > Control module entry. A new object named Control unit is created.In the next step, instantiate the object with the FbkOpen input driver block.

Figure 3-20: Technological connections

7. Select the Control module object.The attributes of the object are opened.

8. Drag the "FbkOpen" block into the field of the "assignment" column and the"assigned block" row via drag & drop.

9. Assign the name FbkOpen for this object.

Figure 3-21: Instantiating the "FbkOpen" object


28/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

10. Select the PV_In input of the FbkOpen block and drag it onto the FbkOpenobject.

A Signal type control tag is automatically created.

11. Adjust the name of the control tag.

Figure 3-22: Defining CMT connecting points

Note You can also create objects via drag & drop. For this purpose you have to selectthe respective block and drag it via drag & drop to the respective object.

The object is created automatically.


29/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

12. Please perform these steps also for the following blocks.

Table 3-1: Blocks that must be instantiated

Block Input/Output

FbkClose PV_In (Signal)

Output PV_Out (Signal)

ValveAnalog MV_Ext (Parameter)

Note If the Select Structure Element dialog opens up during the assignment of aparameter, you have the following options:

1. Select a complete structure2. Select an individual structure member if you do not use the complete structure

Figure 3-23: Result: Objects of the "ValveAnalog" type

1.

2.


30/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

3.5 Configuring optional blocks of the "ValveAnalog" CMT

In AdvES you have the option to create different variants from one control module

type (CMT).One or several function blocks have to be marked as optional.This makes it possible to create different variants of the type in AdvES.

Procedure

1. Enable the Optional attribute in the attributes of the FbkOpen andFbkClose blocks.Chapter 4.2.1 of the application example shows you how you can form differentvariants of the ValveLean type in this way.

Figure 3-24: "Optional" block attribute

Note The optional blocks, for example, can be disabled in an instance of the typeand can be enabled in another instance.

The huge advantage is that you no longer require many different process tagtypes, for a valve for example.

A universal control module type which contains and can reproduce all variants of a valve is sufficient.


31/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

3.6 Configuring messages

Requirements

The block at which you wish to configure the messages must support themessaging function.

Procedure

1. Open the Technological connections of the ValveAnalog control moduletype.

2. Right click on the ValveAnalog object. A context menu opens.

3. Click on Insert new object > Message.

Figure 3-25: Creating the message object

4. Select the ValveAnalog block and using drag & drop, move it into the field for assigning the message (Column: Assignment row: Assigned message) andselect the SIG1 message identifier (possible message identifiers: SIG1 ...SIG8).

Figure 3-26: Configuring messages


32/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Note "MsgEvID2" messages cannot be configured in this way.For blocks containing more than one Alarm_8P, hence also an MsgEvID2,

you need to proceed as follows:1. Switch the connections "MsgEvID1" and "MsgEvID2" visible.2. Select the MsgEvID2 connection and use drag & drop to move it onto the object of

the appropriate block. A message with the assignment to the message-capable block is automaticallygenerated.

3. Select the desired message identifier.


33/113

4 Configuring with AdvES


C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4 Configuring with AdvESBased on an example project, this chapter describes how to perform mass dataengineering with AdvES V8.0.

4.1 Data import from PCS 7 to AdvES

This chapter describes how PCS 7 data is imported to AdvES.The procedure will be described in the following.

The technological hierarchy, control modules and hardware already available in theproject as well as the control module types available in the master data library canbe transferred to AdvES through importing the PCS 7 data.


Procedure

1. Select your sub-project and right click to open the context menu.

2. Click on "Open project in AdvancedES" to open AdvES.

Figure 4-2: Opening AdvES


34/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Note The "Open project in AdvancedES" item will only be shown with correctinstallation and can only be selected with a valid license.

Standard templates will be transferred when an AdvES project is opened for thefirst time, the opening process will therefore take a little longer. The progress of copying will be displayed.

AdvES will open with an empty project, i.e. no data will be available in the threetabs of the navigation area, only the name of the project.

Figure 4-3: AdvES dialog

3. Click on "PCS 7 Import" in the workflow bar.

Figure 4-4: "PCS 7 Import" menu


35/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4. Select the "Import from PCS 7" tab.

5. Enable all selectable filter options.

Note For the first import of PCS 7 data or after hardware changes (or changes to thecontrol module types) it is mandatory to enable the filters for control moduletypes and the hardware.

6. Click on the "Import" button to start importing.

Figure 4-5: Filter selection dialog for data import

After that, AdvES will automatically check for differences between the PCS 7project and the AdvES project. The result of the comparison will be displayedin the "Data transfer - Generate/import" window.

7. Click on the button to start the import to AdvES.

Figure 4-6: Comparison of AdvES and PCS 7 project


36/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Note The button will only be enabled if differences between the two projects arefound.

Note Enable the "delete at target" function if you wish to delete obsolete data in the AdvES project.

Note Only the changes will be imported.

Example

You have already imported control module types and a hardware configurationinto the AdvES project. Then you delete a control module type in the master datalibrary and change the name of the PROFIBUS master system in the hardwareconfig.

With the Delete at target function, the new name of the PROFIBUS master system will be adopted when importing, and the old control module type willbe removed from the AdvES project.Without the delete at target function, an additional PROFIBUS master system is created and the data of the already existing PROFIBUS master system remains in COMOS.

8. After the import, you will be shown a log for the import process, acknowledgethe dialog with OK.

Figure 4-7: Dialog box for the import process

9. The Data transfer dialog box opens. Here you have the option of comparing the AdvES project with the PCS 7 project.

10. Click on the "Yes" button to start the data synchronization. After synchronization, check whether all data were correctly transferred to AdvES.


37/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-8: Dialog box for starting data synchronization

Figure 4-9: Synchronized data (data identical in both projects)

11. Click on the Close button to close the import dialog box. Subsequently, thedata is adopted in AdvES and displayed in the automation view.

You will see a generation log with errors, warnings and messages.

Figure 4-10: Generation log after data import


38/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

12. Click on the button to confirm the "PCS 7 Import" menu item. Thisenables the next menu item "Assign signals/parameters".

Figure 4-11: Confirming the "PCS 7 Import" step


39/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.2 Assigning mapping labels for the technological I/Os of a CMT

Mapping labels are required because the names for signals and parameters inPCS 7 projects or the master data library may differ in the process tag or signallists.In order for Advanced ES to be able to merge such different data, it is necessary tostandardize this data.

The terms from Namur 1.10 are used for standardization.

Note You will find the list with the Namur labels available in AdvES V8.0 in chapter 7.5of the "Process Control System PCS 7 Advanced Engineering System"configuration manual.

You can also create individual mapping labels (see chapter 4.2.3 ).

The mapping labels for 2 areas are assigned on a separate basis in AdvES. Onone hand for the data from PCS 7 and on the other hand for the external data fromthe Excel lists.The identifiers are a link between PCS 7 and AdvES as well as between AdvESand Excel tables.They enable the file import and fulfill the function of maintaining the structure duringimport, i.e. the assignment of signals and parameters to the CMTs.



40/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Example

Looking for example at the ValveAnalog CMT from the example project.The CMT has an input signal for the feedback open and closed and an analog

output signal for the current position of the valve (see Figure 4-13 ).The signal name is made up of the block name and the input name in the controlmodule type.

Figure 4-13: Technological connections of the "ValveAnalog" CMT

The same information for the signals of a valve is also included in the signal list of the example project (see Figure 4-14 ).

Figure 4-14: Excerpt of a signal list

In AdvES, the labels "FBO", "FBC", and "OUTOC" are assigned as mapping labelsfor the signals from the control module type and from the Excel list. This way

AdvES can link the information from the "ValveAnalog" CMT with the informationfrom the Excel list (see Figure 4-15 ).


41/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-15: Linking information from PCS 7 and AdvES

You will find a detailed description of how to assign the mapping labels in chapters4.2.1 , 4.2.3 and 4.3.1 .

Note The mapping labels only have to be assigned once.If the same master data library is used in a different AdvES project, which meansthe mapping labels have already been assigned, the mapping labels can beimported from that project (see chapter 4.2.3 ).


42/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.2.1 Assigning the mapping labels

Introduction

In this section you will learn how to assign mapping labels to the technologicalconnections (signals and parameters) of the CMTs imported into AdvES (seeFigure 4-16 ).

Figure 4-16: Assigning signals and parameters

Procedure

1. Click on the "Assign signals/parameters" button in the workflow bar.

Figure 4-17: "Assign signals and parameters" menu

In the AdvES work area all CMTs in the project are displayed with thecorresponding status for assignment. In this example the "AMON_Std",

"CTRL_Std", "MOT_1sp_2fb_1cm", "MOT_2sp", and "ValveAnalog" CMTs aredisplayed.

Note Possible statuses:

Redno mapping label assigned yet

Yellow mapping labels incomplete

Green mapping labels complete


43/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-18: Dialog box for assigning mapping labels

2. Click a CMT, e.g. AMON_Std.You will receive a list of all technological connections (signals and parameters)of the type. Here you can assign the mapping labels.

3. Click the icon in the Mapping label" column. A dropdown selection menu is opened with a list of the mapping labels for parameters or signals stored in AdvES.

4. As shown in the following diagram, assign the mapping labels to the signals of the "AMON_Std" type.

Figure 4-19: Mapping labels of the "AMON_Std" CMT

Note After you assigned a label, the status of the type will change to "yellow". After you assigned the mapping labels for all signals, the status will change to "green".


44/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

5. Now assign the mapping labels for the remaining CMTs.

Figure 4-20: Mapping labels of the "CTRL_Std" CMT

Figure 4-21: Mapping labels of the "MOT_1sp_2fb_1cm" CMT

Note If you assign a mapping label to a connection for the first time, it will be appliedto all equal connections in the CMTs. These connections will then be markedblue, as shown in Figure 4-22 .

If you change existing mapping labels you can choose whether the mappinglabel will also be changed for the connections with the same name of all CMTS.

Alternatively, you can define exceptions via the "Only for this connector" button.These will then be marked red.


45/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-22: Mapping labels of the "MOT_2sp" CMT

6. In the next step, as shown in the following diagram, assign the mapping labelsto the signals of the "ValveAnalog" type.

Figure 4-23: Mapping labels for the "ValveAnalog" CMT


46/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.2.2 Creating variants and copy templates in AdvES

Procedure

1. Open the Variants tab.

Note If the status of all CMTs is green than the Variants tab is enabled.

2. Click the "ValveAnalog" entry.

3. Click on "Click here to add a new variant".

Figure 4-24: Creating variants of the "ValveAnalog" type

4. Enter the name "Valve_FBC".

5. Disable the option for the "FbkOpen" block.

6. Create another variant for the "ValveAnalog" CMT:

Table 4-1: Variants of the type "ValveAnalog"

Variant Name FbkOpen FbkClose

2 Valve_no_FB disable disable

Figure 4-25: Variants of the type "ValveAnalog"


47/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Note The blocks "FbkOpen" and "FbkClose" are included in the "ValveAnalog" basictype.

Variants of the basic type

Valve_FBC Valve_no_FB

This way you created, as described in chapter 3.5 , two variants from one"ValveAnalog" CMT.

7. After you assigned all signals and parameters of the types, click the "Generate"button in order to create the copy templates of the CMTs.

NOTICE Loss of the assignments

When generating the copy templates, the selection of the mapping labels is notsaved in this dialog.To save, click the OK button or Apply.

Figure 4-26: Generating copy templates


48/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-27: Copy templates of the example project

You need the copy templates in order to specify the process tags later on (seechapter 4.4 ).

Result

Figure 4-28: Assignments for data from PCS 7


49/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.2.3 Creating individual mapping labels

With AdvES V8.0 SP1 it is possible to create individual mapping labels.

Note This section is for information purposes and is not relevant for the exampleproject.

Procedure

1. Click the button in the header bar next to the Menu. A drop-down menu will open.

2. Click the Manage mapping labels menu entry.

Figure 4-29: Creating mapping labels

The Manage mapping labels dialog box opens.

The editing mask is divided into three areas: parameter, signal and signalparameters. If you would like to, for example, create a new mapping label for aparameter, you have to proceed as follows:

Figure 4-30: Manage mapping labels dialog


50/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

3. Click the Parameter tab.

4. Click the Add new element button . A new empty row is recreated. It is stored under the User defined status.

Figure 4-31: Creating mapping labels for parameters

5. Here, you assign the new name and the description of the new mapping labels.

6. The mapping labels have to be switched visible, so that they can be used asmapping labels.

7. Subsequently, click the "Apply" button.

8. Click the Manage mapping labels dialog box.

Note Only once the Manage mapping labels dialog has been closed, are newlycreated mapping labels read out and can be used for assignments.

Figure 4-32: Creating mapping labels for parameters


51/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

9. If you have created a mapping label, assigned it and created the copytemplate, the mapping label status inUser-defined mapping label will change. You can therefore no longer delete

the mapping labels via the button.

Figure 4-33: Assigning mapping labels

Figure 4-34: Created mapping label for a parameter

10. If you are replacing the mapping label you have created by another one andyou are creating the copy template again, your mapping label created by you isno longer used and this is displayed under the user defined status. You cantherefore delete the mapping label again.


52/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-35: Assigned mapping label is not assigned to a parameter

Note When you enable the Show predefined labels option box, all default mappinglabels are displayed.

You cannot edit or delete them. They can only be switched visible or invisible.This has the advantage that only all relevant default mapping labels are visibleand that they are displayed in the dropdown selection menu.


53/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.2.4 Transferring mapping labels

In a multi-project there is only one master data library which is used in all sub-

projects and therefore also in all AdvES projects.If the mapping labels have already been assigned in an AdvES project, theassignment will not have to be repeated. In this case the mapping labels can betransferred from the existing AdvES project to the new AdvES project.

Note This section is for information purposes and is not relevant for the exampleproject.

Procedure

1. Click the button in the header bar next to the Menu. A drop-down menu will open.

2. Click the Transfer mapping labels menu entry.In the working area, an overview of all AdvES projects is opened.

Figure 4-36: Transferring mapping labels

3. Select the project from which you wish to transfer the mapping labels.

4. Subsequently, click the transfer "Apply mapping labels" button.The mapping labels are applied in your current project.


54/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-37: Project selection for importing mapping labels

Note Subsequently check the mapping labels and, if required, correct them.

NOTICE Variants will not be transferred here. New variants must be generated for the project.

5. After assigning all mappings, generate the CMTS copy templates, as describedin chapter 4.2.2 .


55/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.3 Data import of external data

In order to import data from an Excel signal list into AdvEs, you need to define a

configurator. There you determine which data from the Excel list shall be importedto AdvES and what kind of information it is.

This way, using AdvES, you can read in technological hierarchy levels, controlmodules, signals, parameters, and hardware information from an external system.

The required data from external systems must be supplied in Excel-readableformat, since AdvES uses the data in the form of Excel lists.


Requirements for importing

Excel lists must meet the following requirement to ensure the correct transfer of information from Excel and generation of data in AdvES:

Each column must be clearly defined (identical information in one column).

The sequence of entry of the columns with the respective information into theExcel list is not specified. A configurator selects the columns and assigns themcorrectly (see chapter 4.3.1 "Creating the configurator for importing ").


56/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Types of Excel lists

AdvES can process two types of Excel lists:

Process tag list The process tag list includes all process tags with name and associateddetailed information.

Signal list (used in this application example) The signal list includes all signals with name and associated detailedinformation.

In the table below the list types are clearly illustrated.In this table it is shown what information has to be included in the lists in order togenerate the respective data.

Note The following table shows which information must or can be available in aprocess tag or signal list (Excel list).

1. The column "mapping target" and "mapping class" indicates the assignment you haveto select in the configurator for the respective information.

2. The "must/can" column shows which information is optional or mandatory for therespective list type.

3. The column "when" shows the list types. It specifies which information must beavailable to achieve the corresponding target, e.g. importing data for generatingsignals and hardware.

4. The following applies to the technological hierarchy levels:Whether and how the technological hierarchy is used here depends on the level onwhich the signal data or process tag data is imported to AdvEs. The TH must begapless from the used import level on.


57/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-39: Required/possible external data from the Excel list


58/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.3.1 Creating the configurator for importing

In this chapter you will learn how to create a configurator in AdvES in order to be

able to import data from Excel lists.

Procedure

1. Click on the "Import signal/process tag list" button in the workflow bar.

Figure 4-40: "Import signal/process tag list" menu

The "PCS 7 Import/Export" dialog box will open, with the "Import" tab open.

2. Click on the "Configuration" tab to create a new configurator.

3. Click on the "New..." button to create a new configuration object.

4. Assign a suitable name.

Figure 4-41: Creating a new Excel configurator


59/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

5. Then select the Excel list for the example project and click on the Loadbutton.

Figure 4-42: Loading the Excel list

Note The selected Excel file will be opened. It is a signal list with hardwareinformation.

Figure 4-43: Configuration dialog box


60/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

6. Check the Excel list for relevant information

Note Take the list from Figure 4-39 and compare which information is available in thesignal list.Please note the following:

Which data is relevant and to be imported?Which import type can be used and is the required information available?

In this example, we are looking at a signal list with hardware information, i.e. youcan generate the control modules (CMs) with the TH, the corresponding signalinterconnections, and the corresponding hardware (DP slaves) from this list.

7. Select the Excel worksheet ("signal_list_example") and the Excel start row

from which the configurator will read out the data later on.8. Select line "2" as the Excel start row.

9. Using drag & drop, move the hierarchy folder of level 1 to the "Import target"field.

Figure 4-44: Setting the configurator

10. Define the significance of the columns in the signal list in AdvES.There are two variants according to which you can approach:

1st variantYou can transfer all Excel columns to the configurator, via the "transfer allExcel columns" function. Since the list includes a lot of information which isnot required, the second variant is recommended.

2nd variantYou can add the Excel columns individually to the configurator viaAdd column definition and via drag & drop from the Excel list tothe configurator.

This step is required for AdvES to be able to read in the data and to correctlyassign it.


61/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Example:

Table 4-2: Assigning columns

Column Name Significance in AdvESproject

AJ Unit TH1

M CMT Function Process tag function

B Controller Name of station (AS)

11. Select a cell in the "AJ" column and place the cursor on the frame of the celluntil the cursor changes its icon.

Note This will work on one of the side edges of the cell, but not on the corners.

12. With the mouse button pressed down drag the cell to AdvES. A column object is generated.

13. Enter line 1 as header row.For all other column objects, the name entered in row one is used.

Figure 4-45: Generating a column object


62/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Table 4-3: Establishing a column object

Row Content

Column Includes the letter of the Excel column

Caption Includes the cell value of the "Excel start row" that youdefined in the configuration

Mapping class Defining a category of mapping labels. Mapping labelscan be:

Technological hierarchy

Process tag

Control module attribute

Control module parameter

Signal

Signal attribute

Signal parameter

Data Includes the first three values of the Excel column fromthe defined "Excel start row"

After you inserted the column into the configuration and thus communicated itto AdvES, you now have to map it, so that AdvES can detect which informationis read and can process it correctly.

14. Assign the mapping class for TH, use Figure 4-39 for this purpose.

15. Click the arrow field of the mapping class in the column definition.

16. A menu with the selectable definitions will open.

17. Select the entry "Technological hierarchy".

Figure 4-46: Assigning the mapping class


63/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

18. After assigning the mapping class you now need to assign the associatedmapping target (see Figure 4-39 ). Depending on the selection of theassignment class, other assignments are offered in the dropdown menu.Select TH level 2.

Figure 4-47: Assigning the mapping target


64/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

19. Repeat this procedure also for the following required columns.

Table 4-4: Configuring the column objectsColumn Name Mapping class Mapping target

L Control Module Name Process tag 02 (Control module AdvES)(splitting ... see paragraph below"Splitting and assigning informationfrom Excel lists")

M CMT Function Process tag attribute Function of the control module

L Control Module Name Process tag attribute PCS 7 control module name(splitting ... see paragraph below"Splitting and assigning informationfrom Excel lists")

B Controller Process tag attribute Station name

K Signal Name Signal Variable mapping (see paragraphbelow "Assigning the mapping labelsfor signal names of the Excel list")(splitting ... see paragraph below"Splitting and assigning informationfrom Excel lists")

D Station Address Signal attribute Address

H DP-IM MLFB Signal attribute DP slave order number

I I/O Type Signal attribute HW signal type

F Channel Signal attribute Channel

K Signal Name Signal attribute PCS 7 signal name

Y I/O Module MLFB Signal attribute Signal module number B Controller Signal attribute Station name

E Slot Signal attribute Slot

C Bus Signal attribute Subnet


65/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Splitting and assigning information from Excel lists

AdvES provides the option of splitting information in Excel columns.

Using the "splitting" button you can split the content of a cell and assign differentmapping classes and mapping targets to the contents.

This example shows you how to separate and assign the information for themapping class "process tag" in column "J".

Procedure

1. Click on the column definition for mapping class "process tag".

2. In the properties view of the column click on the "Splitting" button.

Figure 4-48: Splitting a column object

3. Then click the button. The "Splitting" dialog box will open.There you can define the criteria for splitting.

4. Use the following options for splitting: Split character From the back: with a space character


66/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-49: Defining the splitting criterion

5. After splitting, a second box will open which is referenced to the same column.

Figure 4-50: Splitting the "L" column


67/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

6. Hide the left splitting of column L.Click the Hide button (see Figure 4-50 ).

7. Assign "process tag" as the mapping class and "02 (control module AdvES)" asthe mapping target.

Figure 4-51: Assigning the mapping target for column "L"

8. Also split information for further mapping classes as follows:

Table 4-5: Splitting criteria for column objects of the example project

Column Splitting options

L Split character From the back: With one (blank)(right part of the splitting is relevant)

K Split character From the front: With underscore ( _ )(right part of the splitting is relevant)

Note Splittings can also be disabled via the "Hide" button. The hidden content will notbe used and will not be imported to AdvES.


68/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Assigning the mapping labels for signal names of the Excel list(Variable mapping)

When assigning the mapping labels for signals you perform a variable assignment.For the signals found in the Excel list, the corresponding NAMUR labels will beassigned.

Procedure

1. Assign the appropriate NAMUR ID in the column definition of the Signalmapping class (column I).Click on the button in order to transfer the signal names to the assignmentfield.Execute this step for all names.

Figure 4-52: Assigning the corresponding NAMUR IDs for the signal names


69/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

2. The mappings for the "Technological connections" of the CMTs were assignedin chapter 4.2.1 . Assign the mapping labels of the associated "Technologicalconnections" to the corresponding signal names of the Excel signal list. Thiscreates a link (as described in chapter 4.2 ) between PCS 7, AdvES, and theExcel list.

Figure 4-53: Assigning the corresponding mapping labels

This ensures that the structure of the data during the import from Excel ismaintained, i.e. the assignment of signals and parameters to the CMTs.

For a later export of the data from AdvES to PCS 7, for example, the signalinput of the respective CM instance is assigned to the appropriate signal.

Figure 4-54: Mapping labels for SIMATIC PCS 7 and Excel


70/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Result

Figure 4-55: Configurator part 1

Figure 4-56: Configurator part 2

Table 4-6: Mappings

Column Name Mapping class Mapping target

AJ Unit Technologicalhierarchy

02 (hierarchy file level 2)

L Control Module Name Process tag 02 (control module AdvES)

(splitting ... see paragraph above "Splittingand assigning information from Excel lists")

M CMT Function Process tag attribute Function of the control moduleL Control Module Name Process tag attribute PCS 7 control module name

(splitting ... see paragraph above "Splittingand assigning information from Excel lists")

B Controller Process tag attribute Station name

K Signal Name Signal Variable mapping (see paragraph above"Assigning the mapping labels for signalnames of the Excel list") ( splitting ... seeparagraph above "Splitting and assigninginformation from Excel lists")

D Station Address Signal attribute Address

H DP-IM MLFB Signal attribute DP slave order number I I/O Type Signal attribute HW signal type

F Channel Signal attribute Channel

K Signal Name Signal attribute PCS 7 signal name

Y I/O Module MLFB Signal attribute Signal module number

B Controller Signal attribute Station name

E Slot Signal attribute Slot

C Bus Signal attribute Subnet


71/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.3.2 Importing Data

Prerequisite for importing data from a signal or process tag list is a corresponding

list with a matching configurator.

Procedure

1. After creating the configurator, open the import dialog box.

2. Fill in the fields according to the table below:

Note Import type: Here you select whether the list to be imported is a processtag or a signal list.

Configuration: Here you select an existing configurator.

Edit: Here you change an existing configurator (e.g. after you changed the Excel list).

Create: Here you create a new configurator.

Excel file: Here you select the Excel file from which to import the data.

Importing newworking layer

When the checkbox is disabled the data to be imported isinstantly integrated into the AdvES project.

If the checkbox is enabled, the data to be imported is notinstantly transferred to the AdvES project but is first of allsaved in a working layer. This is to prevent faulty imports from

being immediately transferred into the AdvES project anddestroying it.

Import target: Here you define the import target from the "Project" tab viadrag & drop.

3. Enable the Import new working layer checkbox with a mouse click.

4. Then click on the "Import" button to import the signal list data to AdvES.


72/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-57: Import dialog box for importing from the Excel list

During import a continuous protocol will be output. It includes information on

the progress of the import and potential errors.

Note Each empty cell in a column to be read out causes a warning message.In this example, a warning message will appear that there is no content in thecells of the columns for Subnet, DP slave order number and Signal moduleorder number.

This was done deliberately in this example, to show you how to add this data in AdvES (see chapter 4.6 ).

Figure 4-58: Import dialog box

5. When the import in AdvES is completed, click "OK".


73/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Note By enabling the Import new working layer checkbox, AdvES will work with theworking layer when importing external data.

Imported data will not be transferred into the AdvES project immediately, but will

be stored in a working layer first. This is to prevent faulty imports from beingimmediately transferred into the project and destroying it.

6. Subsequently, a dialog will open, confirm it with Yes.Figure 4-59: Info box

The data imported to AdvES is made available in a working layer. Before youproceed you can determine whether to use or discard the imported data (incase of a faulty import).

The "project" tab in the navigation area shows the status of the objects after import as follows:

Figure 4-60: Imported data from the Excel list


74/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-61: Color coding

As soon as the import is confirmed, the control buttons in the header bar areblocked and the buttons for releasing or discarding the import are enabled.

Note The release, accepts the changes fully in the project.Discarding deletes the changes from the signal or process tag lists lastimported.

An import can only be performed after the previous import has been released or discarded.

7. Release the import if it was performed correctly.

Note Clicking on the "Release import" button will fully transfer the imported datafrom the working layer into the AdvES project and it can be further processed.

With the Discard import button, the imported data in the working layer isdeleted and is not accepted in the AdvES project.

Figure 4-62: Menu: "Release import" and "Discard import"


75/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.4 Specifying control modules

Specifying the process tags determines what CM will be connected with which

CMT (from the PCS 7 master data library) in AdvES.The process tag defined in the configurator (from the Excel list) is used for thispurpose (see chapter 4.3 ).


Procedure

1. Click on the "Specify control modules" button in the AdvES header bar.

Figure 4-64: "Specifying control modules" menu


76/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

2. Using drag & drop, move the project node into the "Start object" field. All control modules under the object node will be displayed.

Figure 4-65: Dialog box for specifying the control modules

3. Open the "Copy templates" tab in the navigation area.This is where you find the copy template of the imported CMTs from the master data library.Prerequisite is that you have correctly executed the steps described in chapter 4.2 .

4. Perform the assignment for each function type once.Drag the respective copy template via drag & drop to the respective functiontype.

Table 4-7: Specifying Control Modules

No. Function of the control module Copy template

1 M MOT_1sp_2fb_1cm

2 IC CTRL_Std

3 V Valve_no_FB

4 V_C Valve_FBC

5 V_OC ValveAnalog

6 I AMON_Std

7 MSF MOT_2sp


77/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-66: Assigning the copy templates to the corresponding CMs

Note Open the "Copy templates" tab in the navigation area.From there you can assign a copy template to each CM using drag & drop. Thisprocedure is more efficient and is used in this example.


78/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

After you performed the mapping for each function type once, you assign the

missing mappings automatically via the button on the right. This initiates the

assignment of the CMTs to the remaining CMs according to their function.

Figure 4-67: Automatic assignment of the CMs

5. Enable the mappings via the icon in the button on the right. A drop-down menu will open.

6. Click on "Execute (all)" in the drop-down menu.The assignments will be executed and their status checked.

Figure 4-68: "Execute (all)" menu


79/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

7. As soon as the status of all mappings is green you can close the dialog box.

Figure 4-69: Specifying of all CMs completed


80/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.5 Configuring connections

You can configure cross-chart interconnections in AdvES (connections between

control modules).

In this example the CMs of the CTRL_Std controller type are to be interconnectedwith the appropriate analog valves.

Two work steps are required in AdvEs to configure interconnections:

1. You determine which signals of the control module types are to be alwaysinterconnected (chapter 4.5.1 ).

2. You determine for which control module instances this option of interconnection shall be used (chapter 4.5.2 ).

4.5.1 Determine connections at the CMTs

Procedure

1. Click on the "Connect types" button in the AdvES workflow bar.

Figure 4-70: "Connect types" menu

The "Connect types" dialog box will open. Define the predecessor andsuccessor control module.

In this example, we want the "CTRL_Std" type to control the types"ValveAnalog", "ValveFBC", and "Valve_no_FB", which means the "CTRL_Std"type is the predecessor control module and the "ValveAnalog" type and itsvariants is the successor control module.

2. Drag the CTRL_Std copy template via drag & drop into the field for thepredecessor control module and the ValveAnalog copy template into the fieldfor the successor control module.

All signals of the selected control module types are displayed.

3. Using drag & drop, connect the "MV" output of the predecessor control module("CTRL_Std") with the "MV_Ext" input of the successor control module("ValveAnalog", "Valve_FBC, and "Valve_no_FB").


81/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

Figure 4-71: Defining the predecessor and successor CMT

Figure 4-72: Determining connections between the CMTs

4. Click on the "Apply" button and then "OK" to close the dialog box.

Note You can only interconnect input signals that are not connected to hardwarechannels and that are not listed in the icon table.


82/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.5.2 Execute interconnections for the CM instances

Procedure

1. Click on the "Connect instances" button in the workflow bar.

Figure 4-73: "Connect instance" menu

2. Drag the project node into the "Start object" field.3. Drag the respective IC-CM into the Interconnected predecessor cell of the

appropriate V-CM from the Acid Sel and Gas Rel hierarchy folder in thenavigations area (via drag & drop).

This is how you specify which CMs are to adopt the defined interconnections(see chapter 4.5.1 ).

Figure 4-74: Definition of connections for the individual IC CMs to the V-CMs


83/113



C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4. After you assigned the associated CTRL CMs to each of the Valve CMs, clickon the > "Execute (all)" button.

Figure 4-75: "Execute (all)" menu

5. When the status of all connected V CMs is green, click on the "close" button.

Figure 4-76: Connection definitions


84/113



V2.0, Entry ID: 61627479

C o p y r i g

h t

S i e m e n s

A G 2 0 1 3 A l l r i g

h t s r e s e r v e

d

4.6 Assigning hardware

Apart from the import of the hardware information from the external signal list, you

can also process the hardware assignment in AdvES manually.Since there is no information regarding the respective order numbers for the DPslaves and the I/O modules in the signal list of the example project, you have toassign them manually in AdvES.Furthermore, you have to change the data for the subnet.

Procedure

1. Click on the "Assign hardware" button in the AdvES workflow bar.

Figure 4-77: "Assign h

61627479 Application AdvES En

Documents

Transcript of 61627479 Application AdvES En