You are on page 1of 40

Adaption of existing PCS 7 Projects for the Use of Advanced ES

SIMATIC PCS 7 Application Description  November 2013

Applications & Tools
Answers for industry.

Warranty and Liability

Warranty and Liability
Note The Application Examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These Application Examples do not relieve you of the responsibility to use sound practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these Application Examples and other Siemens publications – e.g. Catalogs – the contents 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 shall be excluded. Such an exclusion shall not apply 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, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (“wesentliche Vertragspflichten”). The damages for a breach of a substantial contractual 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 to life, 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 excerpts hereof is prohibited without the expressed consent of Siemens Industry Sector.

Copyright  Siemens AG 2013 All rights reserved

Caution The functions and solutions described in this entry predominantly confine themselves to the realization of the automation task. Please also take into account that corresponding protective measures have to be taken in the context of Industrial Security when connecting your equipment to other parts of the plant, the enterprise network or the Internet. For more information, please refer to Entry ID 50203404. http://support.automation.siemens.com/WW/view/en/50203404

Siemens Industry Online Support This entry is taken from the Siemens Industry Online Support. The following link takes you directly to the download page of this document: http://support.automation.siemens.com/WW/view/en/82949027

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

2

Table of Contents

Table of Contents
Warranty and Liability ................................................................................................. 2 1 2 3 Preface ................................................................................................................ 4 Task ..................................................................................................................... 5 Solution and Implementation ........................................................................... 6 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.3 3.4 3.4.1 3.4.2 4
Copyright  Siemens AG 2013 All rights reserved

Saving PCS 7 project data ................................................................... 7 Updating/preparing PCS 7 project data ............................................. 13 Procedure: CFCs created directly in the project without using a master data library.............................................................................. 13 Procedure: CFCs created directly in the project but no master data library available in the project..................................................... 17 Procedure: PTs created out of conventional PTTs, master data library used ......................................................................................... 24 Procedure: CMs created out of CMTs, master data library used ....... 26 Processing in AdvES .......................................................................... 27 Project postprocessing in PCS 7 ........................................................ 34 New project in the multiproject ........................................................... 34 Old project in the multiproject ............................................................. 36

Conclusion ....................................................................................................... 38 Further Links .................................................................................................... 38 History............................................................................................................... 40

5 6

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

3

1 Preface

1

Preface
This document describes how to adapt an already existing SIMATIC PCS 7 project in order to apply the new PCS 7 type concept (with control module types and control modules) and PCS 7 Advanced ES (AdvES). Note From version V8.0 on, SIMATIC PCS 7 provides a new type concept which - in combination with AdvES - enables improved mass engineering on the one hand and allows changes to already instantiated control module types on the other hand. For details on the new type concept, please refer to the "SIMATIC Process Control System PCS 7 CFC for SIMATIC S7 (V8.0)" function manual, chapter "Handling of control module types". Please find the link to the manual in chapter 5. "Further Links".

Objective of the application

Copyright  Siemens AG 2013 All rights reserved

Validity Valid for SIMATIC PCS 7 V8.0 or higher (incl. option package PCS 7 Advanced Engineering System V8.0 or higher)

Abbreviations
Table 1-1: Abbreviations Abbreviation CMT CM PTT PT CFC Description Control module type (new type model) Control module (instance of a CMT) Process tag type (old type model) Process tag (instance of a PTT) Continuous function chart

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

4

2 Task

2

Task
You want to adapt your SIMATIC PCS 7 project in such a way that you can apply the new type concept in combination with AdvES. The reasons for that could be the following: • • • You want to apply the new type concept to your SIMATIC PCS 7 project and use the AdvES functionalities. You want to use an existing SIMATIC PCS 7 project either completely or at least in parts in a new PCS 7 project. You want to make changes (for example, adapt parameter values) and possibly expansions in a new SIMATIC PCS 7 project in an efficient manner. (For example, if the changes or expansions are already available in Excel files, these data can be transferred using AdvES.) In the application "Performance Mass Data Engineering with PCS 7 Advanced ES on a Practical Example", section 2.2 specifies further advantages of the new type concept in combination with AdvES. http://support.automation.siemens.com/WW/view/en/61627479

Note

Copyright  Siemens AG 2013 All rights reserved

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

5

3 Solution and Implementation 3.1 Saving PCS 7 project data

3

Solution and Implementation
This chapter demonstrates the steps that have to be taken in principle to prepare your PCS 7 project for the use of AdvES and to convert to the new type concept. The procedure for that can be divided into four process steps.
Figure 3-1: Workflow

Copyright  Siemens AG 2013 All rights reserved

This process provides the following advantages: • • The hardware configuration and interconnection of the driver blocks with the I/O modules do not get lost during the conversion. Cross-process tag interconnections of the existing project are copied and do not need to be reconfigured.

To which extent the individual steps have to be processed depends on whether you want to continue to use the existing project and how the existing process tags were created in the project (see section 3.2.)

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

6

3 Solution and Implementation 3.1 Saving PCS 7 project data

3.1

Saving PCS 7 project data
This section describes how to save your PCS 7 project data before converting your PCS 7 project into the new type concept.

Procedure Regardless of how you created your PCS 7 project (for example, with CFCs and thus without a master data library, with process tag types or control module types in a master data library), you have to save your project data first. 1. For this purpose, open your PCS 7 project in SIMATIC Manager. 2. Open the Process Object View. 3. Select your subproject and right-click to open the context menu. Click on: "Process Objects > Select I/Os...".
Figure 3-2: SIMATIC PCS 7 Process Object View

Copyright  Siemens AG 2013 All rights reserved

The "Filter: Select I/Os" dialog opens. Confirm the dialog by clicking on the "OK" button.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

7

3 Solution and Implementation 3.1 Saving PCS 7 project data
Figure 3-3: "Filter: Select I/Os" dialog

Copyright  Siemens AG 2013 All rights reserved

4. If not yet done in the source project: Check all check boxes in the "Parameters" column for the parameters with cross-process tag interconnections.
Figure 3-4: Selecting parameter flags

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

8

3 Solution and Implementation 3.1 Saving PCS 7 project data Note In larger projects, this may affect a great deal of parameters. To save time and filter by the interconnected parameters only and save these, proceed as follows: 1. Select the subproject in the Process Object View, right-click to open the context menu and click on the command: "Process Objects > Export All I/Os...". 2. Save the CSV file. The Excel file created out of that contains all interconnections, even the interconnections between inputs/outputs without a parameter flag. 3. Filter the interconnections in column H (without blanks), for example:

Copyright  Siemens AG 2013 All rights reserved

4.

Compare the entries in column B (Chart) with those in column H (Interconnection): The interconnection starts with the name of the target/source chart. If the name differs from that in column B (same row), it is a cross-process tag interconnection. Via columns B and D you can determine the I/O in the chart.

You can use the following formula to evaluate larger amounts of data: Excel command: German: =ISTFEHL(WENN(H2<>"";FINDEN(B2;LINKS(H2;FINDEN("\";H2;1)1);1);"no_conn")) Excel command: English: =ISERR(IF(H4<>"";FIND(B4;LEFT(H4;FIND("\";H4;1)-1);1);"no_conn")) This formula gives the result "TRUE" if it is a cross-process tag interconnection. Enter this formula in each cell of a blank column and then filter by "TRUE". This provides an overview of all cross-process tag interconnections and you can save these.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

9

3 Solution and Implementation 3.1 Saving PCS 7 project data 5. Select the subproject in the Process Object View, right-click to open the context menu and click on the command: "Process Objects > Export I/Os...".
Figure 3-5: SIMATIC PCS 7 Process Object View

Copyright  Siemens AG 2013 All rights reserved

6. Save the parameters and assign a unique name to the CSV file. You will need this file later to reimport the information (see section 3.4).
Figure 3-6: Saving the export file

Note

Since you set all parameter flags, all the information about interconnections and parameter values is saved.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

10

3 Solution and Implementation 3.1 Saving PCS 7 project data 7. Open the "General" tab in the Process Object View. In this view, all CFCs contained in the project are displayed. 8. Select the subproject in the Process Object View and right-click to open the context menu. Click on the command: "Process Objects > Export Current View...".
Figure 3-7: SIMATIC PCS 7 Process Object View

Copyright  Siemens AG 2013 All rights reserved

9. Save the general project data (CSV file).
Figure 3-8: Saving the export file

10. Open this CSV file with Microsoft Office Excel and save the file under a unique name in Excel format. You will need this Excel list later to reimport the data in AdvES (see section 3.3).

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

11

3 Solution and Implementation 3.1 Saving PCS 7 project data 11. Open the "Signals" tab in the Process Object View. In this view, all signals and their associated HW information are displayed. 12. Select the subproject in the Process Object View and right-click to open the context menu. Click on the command: "Export Current View...". 13. Save the signal data (CSV file). 14. Open this CSV file with Excel and save the file under a unique name in Excel format. You will need this Excel list later to reimport the data in AdvES (see section 3.3). 15. Open the "Blocks" tab in the Process Object View. In this view, all blocks and their associated information (for example, block icon) are displayed. 16. Select the subproject and right-click to open the context menu. Click on the command: "Export Current View...". 17. Save the block data (CSV file). 18. Open this CSV file with Excel and save the file under a unique name in Excel format. You will need this Excel list later to reimport the data in AdvES (see section 3.3).
Copyright  Siemens AG 2013 All rights reserved

Note

This procedure serves for saving the project data of the "old" project in order to transfer them to AdvES later using the Excel list import.

Example: Creating Excel lists
Figure 3-9: Creating Excel lists

csv file Excel file created out of the csv file

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

12

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data

3.2

Updating/preparing PCS 7 project data
This section describes how to adapt/prepare your SIMATIC PCS 7 project in order to optimally use AdvES in combination with the new type concept. The procedure for that depends on whether in the project: • • • • you created the CFCs directly without using a master data library (see section 3.2.1). you created the CFCs directly and no master data library is available (see section 3.2.2). you created the process tags (PT) out of conventional process tag types (PTT) in the master data library (see section 3.2.3). you created the control modules (CM) out of control module types (CMT) in the master data library (see section 3.2.4).

3.2.1
Copyright  Siemens AG 2013 All rights reserved

Procedure: CFCs created directly in the project without using a master data library
Your project includes a master data library. However, you did not use it and created the CFCs directly (without a process tag type). Proceed as follows: 1. If you have several CFCs with exactly the same structure in your project (for example, for a valve or motor), copy the relevant CFC that is to serve as a template (CMT) to the master data library. If your project includes CFCs that occur only once and are additionally interconnected with various I/Os or other CFCs, these must also be converted into CMTs. If this is not done, this interconnection information will get lost.
Figure 3-10: Converting CFCs into CMTs

NOTICE

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

13

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data 2. Convert the CFCs in the master data library into CMTs. For this purpose, open a CFC and create a new object for a control module in the plant I/Os. For this, you have to open the context menu by right-clicking in the white field of the plant I/Os and then click on the command: "Insert new object > Control module".
Figure 3-11: Converting CFC into CMT

Copyright  Siemens AG 2013 All rights reserved

The CFC has now automatically been converted into a CMT. 3. Now click on the "F5" button to refresh the chart. The blocks in the chart are colored in green. Note This procedure is only possible for converting CFCs into CMTs. If your project includes process tag types, you have to proceed as described in section 3.2.3. 4. Make an assignment for the name of the control module type. For this purpose, right-click in the field of the "Assignment" column and the "Name" row. The "Add chart ..." button is displayed. Click on the "Add chart ..." button to assign a chart to the name.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

14

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data
Figure 3-12: Assigning the name of the control module

NOTICE

If this assignment is not made, as a consequence the instances will not be created correctly when the chart names are generated. 5. Now define the plant I/Os of the CMT.

Copyright  Siemens AG 2013 All rights reserved

Note

The basic functional principles of that are not described explicitly in this section. The functional principles and configuration of CMTs are described in great detail and well-illustrated in the following document. Application Example: "Performance Mass Data Engineering with PCS 7 Advanced ES on a Practical Example" http://support.automation.siemens.com/WW/view/en/61627479 6. Check in the plant I/Os whether the sampling time of the CMT is correct.
Figure 3-13: Plant I/Os

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

15

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data
Figure 3-14: Created CMT

Copyright  Siemens AG 2013 All rights reserved

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

16

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data

3.2.2

Procedure: CFCs created directly in the project but no master data library available in the project
If there is no master data library available yet in the project, proceed as follows: 1. Create a master data library if there is none available yet. For this purpose, select your PCS 7 multiproject and right-click to open the context menu. Click on the command: "Multiproject > Create in Multiproject...".
Figure 3-15: Creating a library in the project

Copyright  Siemens AG 2013 All rights reserved

The "New Project" dialog opens. 2. In this "New Project" dialog, open the "Libraries" tab. Assign an appropriate name. 3. Then click on the "OK" button.
Figure 3-16: "New Project" dialog

1.

2.

3.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

17

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data 4. Select the created library and right-click to open the context menu. Click on the command: "Multiproject > Define as Master Data Library".
Figure 3-17: Defining a library as master data library

Copyright  Siemens AG 2013 All rights reserved

5. Open the Component View of your project. 6. Select the master data library and right-click to open the context menu. Click on the command: "Insert New Object > S7 Program".
Figure 3-18: Inserting an S7 program

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

18

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data 7. Select the created "S7 Program" folder and right-click to open the context menu. Click on the command "Insert New Object > Chart folder" to create the "Charts" folder.
Figure 3-19: Creating a chart folder

Copyright  Siemens AG 2013 All rights reserved

8. Open the Plant View of your project and create the shared declarations in the master data library. For this purpose, select the master data library and right-click to open the context menu. Click on the command: "Insert New Object > Shared Declarations". 9. Open the Plant View of your project and create a folder in the master data library. For this purpose, select the master data library and right-click to open the context menu. Click on the command: "Insert New Object > Hierarchy Folder".

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

19

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data
Figure 3-20: Creating a hierarchy folder in the master data library

Copyright  Siemens AG 2013 All rights reserved

10. Assign an appropriate name to the folder. 11. If you have several CFCs with exactly the same structure in your project (for example, for a valve or motor), copy the relevant CFC that is later to serve as a template (CMT) to the folder you created in the master data library.
Figure 3-21: Copying CFCs to the master data library

NOTICE

If your project includes CFCs that occur only once and are interconnected with various I/Os or other CFCs, these must also be converted into CMTs. If this is not done, this interconnection information will get lost.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

20

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data 12. Convert the CFCs in the master data library into CMTs. For this purpose, open the CFCs and create a new object for a control module in the plant I/Os. For this, open the context menu by right-clicking in the white field of the plant I/Os and then click on the command: "Insert new object > Control module".
Figure 3-22: Converting CFC into CMT

Copyright  Siemens AG 2013 All rights reserved

The CFC has now automatically been converted into a CMT. 13. Now click on the "F5" button to refresh the chart. The blocks in the chart are colored in green. Note This procedure is only possible for converting CFCs into CMTs. If your project includes process tag types, you have to proceed as described in section 3.2.3. 14. Make an assignment for the name of the control module type. For this purpose, right-click in the field of the "Assignment" column and the "Name" row. The "Add chart ..." button is displayed. Click on the "Add chart ..." button to assign a chart to the name.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

21

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data
Figure 3-23: Assigning the name of the control module

NOTICE

If this assignment is not made, as a consequence the instances will not be created correctly when the chart names are generated.

Copyright  Siemens AG 2013 All rights reserved

15. Now define the plant I/Os of the CMT. Note The basic functional principles of that are not described explicitly in this section. The functional principles and configuration of CMTs are described in great detail and well illustrated in the following document. Application Example: "Performance Mass Data Engineering with PCS 7 Advanced ES on a Practical Example" http://support.automation.siemens.com/WW/view/en/61627479 16. Check in the plant I/Os whether the sampling time of the CMT is correct.
Figure 3-24: Plant I/Os

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

22

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data 17. Close the CFC editor. In the Plant View of your project, the "Process tag types" folder has been created in the master data library.
Figure 3-25: Created "Process tag types" folder

The standard functions are created automatically when the CMTs are created. These are only relevant to COMOS and immaterial for AdvES. The standard functions cannot be deleted.

Copyright  Siemens AG 2013 All rights reserved

18. Copy the CMT and the remaining CFCs to the "Process tag types" folder and delete the folder you created before in the master data library.
Figure 3-26: Created CMT

19. Convert all other CFCs into CMTs in the same way.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

23

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data

3.2.3

Procedure: PTs created out of conventional PTTs, master data library used
1. Convert the process tag types in the master data library in the "Process tag types" folder into control module types. Select the "Process tag types" folder in the master data library of your multiproject and open the context menu. In the context menu, select "Control modules > Create control module type from process tag type ...".

NOTICE

In automatic conversion, structured control tags might be created that cannot be controlled by AdvES. These must be corrected manually.
Figure 3-27: Converting process tag types into CMTs

Copyright  Siemens AG 2013 All rights reserved

A selection dialog opens. Select all process tag types and click on the "Create..." button.
Figure 3-28: Selection dialog for the conversion of process tag types into CMTs

The CMT is now created in the master data library.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

24

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data 2. After conversion, the process tag types are kept and the control module type is automatically assigned a name extension. Example: Example_Motor (PTT) and Example_Motor(1) (CMT)
Figure 3-29: Created CMTs

3. Delete the process tag types from the master data library and rename the control module types.
Copyright  Siemens AG 2013 All rights reserved

Example: CMT > "Example_Motor(1)" to "Example_Motor"
Figure 3-30: Deleting process tag types and renaming CMTs

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

25

3 Solution and Implementation 3.2 Updating/preparing PCS 7 project data 4. Open the created control module types and make an assignment for the name of the control module type in the plant I/Os of the respective control module type. For this purpose, right-click in the field of the "Assignment" column and the "Name" row. The "Add chart ..." button is displayed. Click on the "Add chart ..." button to assign a chart to the name.
Figure 3-31: Assigning the name of the control module

Copyright  Siemens AG 2013 All rights reserved

NOTICE

If this assignment is not made, as a consequence the instances will not be created correctly when the chart names are generated.

Note

The basic functional principles of that are not described explicitly in this section. The functional principles and configuration of CMTs are described in great detail and well-illustrated in the following document. Application Example: "Performance Mass Data Engineering with PCS 7 Advanced ES on a Practical Example" http://support.automation.siemens.com/WW/view/en/61627479

3.2.4

Procedure: CMs created out of CMTs, master data library used
In this case you do not have to make any changes as you already use the new type concept.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

26

3 Solution and Implementation 3.3 Processing in AdvES

3.3

Processing in AdvES
This section describes how to import your updated PCS 7 project data in AdvES, transfer the previously saved project data from Excel lists to AdvES, and then export the data to PCS 7.

Note

The basic functional principles of AdvES are not described explicitly in this section but are a prerequisite for further processing. Basic information on AdvES and its functional principles are described in great detail and well-illustrated in the following document. Application Example: "Performance Mass Data Engineering with PCS 7 Advanced ES on a Practical Example" http://support.automation.siemens.com/WW/view/en/61627479

Procedure
Copyright  Siemens AG 2013 All rights reserved

1. Open AdvES. 2. Only import the Control module types (CMT) and Hardware in AdvES.
Figure 3-32: AdvES user interface

1.

2.

3.

3. Assign the signals and parameters to the mapping labels and generate the copy templates.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

27

3 Solution and Implementation 3.3 Processing in AdvES 4. Create a configuration file for the import of the project data from the previously saved Excel file that contains the information from the "General" tab in the Process Object View (see section 3.1, steps 7.-10.). Create the configurator with the respective assignments as shown in the following table: Table 3-1: Configurator structure
Excel column A Hierarchy Example: Plant(1)\ Plant section(1)\ Function(1)\ Name Mapping class Technological hierarchy Mapping target 02 (hierarchy folder level 1) Use splitting to filter out the information: Plant(1) Plant(1)\Plant section(1)\ Function(1)\ Use splitting to filter out the information: Plant section(1) Plant(1)\Plant section(1)\ Function(1)\
Copyright  Siemens AG 2013 All rights reserved

02 (hierarchy folder level ...) Use splitting: ... B L Name (of the chart) AS Example: SIMATIC 400(1)\CPU 416-3 DP\S7 Program(1) Measuring point Process tag attribute 02 (control module AdvES) Station name Use splitting to filter out the information: SIMATIC 400 (1) SIMATIC 400(1)\CPU 416-3 DP\S7 Program(1)

Figure 3-33: AdvES configurator for the Excel list with the "general" project information

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

28

3 Solution and Implementation 3.3 Processing in AdvES 5. Create a configuration file for the import of the project data from the previously saved Excel file that contains the information from the "Signals" tab in the Process Object View (see section 3.1, steps 11.-14.). Create the configurator with the respective assignments as shown in the following table: Table 3-2: Configurator structure
Excel column A Hierarchy Example: Plant(1)\ Plant section(1)\ Function(1)\ Name Mapping class Technological hierarchy Mapping target 02 (hierarchy folder level 1) Use splitting to filter out the information: Plant(1) Plant(1)\Plant section(1)\ Function(1)\ 02 (hierarchy folder level 2) Use splitting to filter out the information: Plant section(1)
Copyright  Siemens AG 2013 All rights reserved

Plant(1)\Plant section(1)\ Function(1)\ 02 (hierarchy folder level ...) Use splitting: ... B T Chart AS Example: SIMATIC 400(1)\CPU 416-3 DP\S7 Program(1) Measuring point Process tag attribute 02 (control module AdvES) Station name Use splitting to filter out the information: SIMATIC 400 (1) SIMATIC 400(1)\CPU 416-3 DP\S7 Program(1) Signal Use splitting: Use splitting to filter out the information: M100_FBR M100_FBR K Signal Example: M100_FBR Signal attribute PCS 7 signal name

K

Signal Example: M100_FBR

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

29

3 Solution and Implementation 3.3 Processing in AdvES
Q HW address Example: SIMATIC 400(1)/CPU 4163 DP/1/3/4/0 Signal attribute Signal attribute Station name Use splitting to filter out the information: SIMATIC 400 (1) SIMATIC 400(1)/CPU 416-3 DP/1/3/4/0 Subnet Use splitting to filter out the information: 1 SIMATIC 400(1)/CPU 416-3 DP/1/3/4/0 Signal attribute Address Use splitting to filter out the information: 3 SIMATIC 400(1)/CPU 416-3 DP/1/3/4/0 Signal attribute
Copyright  Siemens AG 2013 All rights reserved

Slot Use splitting to filter out the information: 4 SIMATIC 400(1)/CPU 416-3 DP/1/3/4/0

Signal attribute

Channel Use splitting to filter out the information: 0 SIMATIC 400(1)/CPU 416-3 DP/1/3/4/0

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

30

3 Solution and Implementation 3.3 Processing in AdvES
Figure 3-34: AdvES configurator for the Excel list with the "signal" information

Figure 3-35: AdvES configurator for the Excel list with the "signal" information

Copyright  Siemens AG 2013 All rights reserved

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

31

3 Solution and Implementation 3.3 Processing in AdvES 6. Create a configuration file for the import of the project data from the previously saved Excel file that contains the information from the "Signals" tab in the Process Object View (see section 3.1, steps 15.-18.). Create the configurator with the respective assignments as shown in the following table: Table 3-3: Configurator structure
Excel column A Hierarchy Example: Plant(1)\ Plant section(1)\ Function(1)\ Name Mapping class Technological hierarchy Mapping target 02 (hierarchy folder level 1) Use splitting to filter out the information: Plant(1) Plant(1)\Plant section(1)\ Function(1)\ Use splitting to filter out the information: Plant section(1)
Copyright  Siemens AG 2013 All rights reserved

Plant(1)\Plant section(1)\ Function(1)\ 02 (hierarchy folder level ...) Use splitting: ... B G Chart Block icon Measuring point Process tag attribute 02 (control module AdvES) Control icon

Figure 3-36: AdvES configurator for the Excel list with the "block" information

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

32

3 Solution and Implementation 3.3 Processing in AdvES 7. Import the data from the Excel files. 8. Type the control modules. 9. Adapt the name of the Profibus master system (in AdvES) to the name of the PCS 7 project, for example, from "1" (AdvES) to "PROFIBUS(1) (PCS 7)". 10. Export the data to your STEP 7 project. You can now continue to work either in a new project or in the existing project. The following options are provided for that: – If you want to export the data to a new PCS 7 project, you can check the check boxes for Plant hierarchy, Control modules, and Hardware in the filter settings for the export (that is the default setting).
Figure 3-37: AdvES export to a new PCS 7 project

Copyright  Siemens AG 2013 All rights reserved

If you want to export the data to the existing PCS 7 project, check the check boxes for Plant hierarchy and Control modules in the filter settings for the export. You do not have to export the hardware as it has already been created.
Figure 3-38: AdvES export to an existing PCS 7 project

Note

1. If you use a new project, mind that the OS project has to be adapted. 2. If you continue to use the old project, you should delete the hierarchy and the CFCs contained therein.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

33

3 Solution and Implementation 3.4 Project postprocessing in PCS 7

3.4

Project postprocessing in PCS 7
This section describes the tasks to be accomplished subsequently. These depend on where you exported your data to using AdvES: – – You exported the AdvES data to a new project in the multiproject (see section 3.4.1). You exported the AdvES data to your "old" project in the multiproject (see section 3.4.2).

3.4.1
Procedure

New project in the multiproject
In the project, the control modules are now created on the basis of the CMTs and the I/Os are interconnected with the module channels. As the next step you now have to transfer the remaining project data from the "old" PCS 7 project that you have saved before (see section 3.1, steps 1.-6.). 1. Open the Process Object View in PCS 7 for that. 2. Select the subproject and right-click to open the context menu. Click on the command: "Process Objects > Import I/Os...".

Copyright  Siemens AG 2013 All rights reserved

Figure 3-39: SIMATIC PCS 7 Process Object View

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

34

3 Solution and Implementation 3.4 Project postprocessing in PCS 7 3. The "Import I/Os" dialog opens. To transfer the data, select the backup file in the dialog (see section 3.1, step 6.) and click on the "OK" button.
Figure 3-40: "Import I/Os" dialog

Copyright  Siemens AG 2013 All rights reserved

Note

Warnings may occur during the transfer of the project data because already existing data are overwritten. You have now adapted the project in such a way that you can use AdvES and the new type concept.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

35

3 Solution and Implementation 3.4 Project postprocessing in PCS 7

3.4.2
Procedure

Old project in the multiproject
In the project, the control modules are now created on the basis of the CMTs and the I/Os are interconnected with the module channels. If you had not deleted the plant hierarchy and the CFCs contained therein before you exported the AdvES project data to the PCS 7 project, the PCS 7 project now contains not only the existing CFCs but also the control modules.
Figure 3-41: Example of double instances after the AdvES export

Delete the "old" CFCs and rename the CMTs to the original names of the equivalent CFCs. Example: Delete the CFC "Example_Motor" and rename the CMT "Example_Motor(1)" to "Example_Motor". As the next step you now have to transfer the remaining project data from the "old" PCS 7 project that you have saved before (see chapter 3.1, steps 1.-6.). 1. Open the Process Object View in PCS 7 for that. 2. Select the subproject and right-click to open the context menu. Click on the command: "Process Objects > Import I/Os...".
Figure 3-42: SIMATIC PCS 7 Process Object View

Copyright  Siemens AG 2013 All rights reserved

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

36

3 Solution and Implementation 3.4 Project postprocessing in PCS 7 3. The "Import I/Os" dialog opens. To transfer the data, select the backup file in the dialog (see section 3.1, step 6.) and click on the "OK" button.
Figure 3-43: "Import I/Os" dialog

Copyright  Siemens AG 2013 All rights reserved

Note

Warnings may occur during the transfer of the project data because already existing data are overwritten.

You have now adapted the project in such a way that you can use AdvES and the new type concept.

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

37

4 Conclusion

4

Conclusion
With the help of this procedure you have prepared a PCS 7 project for AdvES, taken over the interconnections of the old project, and transferred the hardware inclusive of the icon table and interconnection with the channel driver blocks. Moreover, you have updated your "old" PCS 7 project to the new SIMATIC PCS 7 type concept and can thus use all new functionalities for mass data engineering (for example, CMT/CM comparison or variants formation). Furthermore, you now have the option to exchange parameter value changes bidirectionally between PCS 7 and AdvES.

Copyright  Siemens AG 2013 All rights reserved

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

38

5 Further Links

5

Further Links
Table 5-1: Internet links Subject 1 Application: Performance Mass Data Engineering with PCS 7 Advanced ES on a Practical Example "SIMATIC Process Control System PCS 7; Advanced Engineering System" "SIMATIC Process Control System PCS 7 CFC for SIMATIC S7 (V8.0)" FAQ: How can you export and then re-import PCS 7 Advanced ES project data? Application: Integrated Engineering with COMOS and SIMATIC PCS 7 using a practical example Online article: Service Pack 1 for SIMATIC PCS 7 V8.0 (EU) Released for Delivery Online article: SIMATIC PCS 7 Advanced Engineering System V8.0 Service Pack 1 Siemens Whitepaper "Fast Track Engineering" Entry ID: 61.627.479
http://support.automation.siemens.com/WW/view/en/61627479

Title

2

Entry ID: 57.414.032
http://support.automation.siemens.com/WW/view/en/57414032

3

Entry ID: 60.283.984
http://support.automation.siemens.com/WW/view/en/60283984

4
Copyright  Siemens AG 2013 All rights reserved

Entry ID: 62.884.021
http://support.automation.siemens.com/WW/view/en/62884021

5

Entry ID: 70.922.226
http://support.automation.siemens.com/WW/view/en/70922226

6

Entry ID: 67.798.122 http://support.automation.siemens.com/WW/view/en/67798122

7

Entry ID: 68.402.701
http://support.automation.siemens.com/WW/view/en/68402701

8

German:

http://www.automation.siemens.com/mcms/process-controlsystems/SiteCollectionDocuments/efiles/pcs7/support/marktstudi en/WP_Fast-Track-Engineering_DE.pdf

English:
http://www.automation.siemens.com/mcms/process-controlsystems/SiteCollectionDocuments/efiles/pcs7/support/marktstudi en/WP_Fast-Track-Engineering_EN.pdf

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

39

6 History

6

History
Table 6-1 V1.0 Version Date 11/2013 First version Modifications

Copyright  Siemens AG 2013 All rights reserved

Adaption of existing PCS 7 Projects for the Use of Advanced ES V1.0, Entry ID: 82949027

40