simatic pcs 7 – simatic it – integration · pcs 7 / simatic it integration pack 2007 quality...

Configuration Instruction

SIMATIC PCS 7 – SIMATIC IT – Integration PCS 7 / SIMATIC IT Integration Pack 2007

Quality Management

Warranty, liability and support

Quality Management 26639558

V 2.0 04.06.08 2/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

NOTE The application examples are not binding and do not claim to be com-plete 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 in ensuring that the described products are correctly used. These application examples do not relieve you of the responsibility in safely and professionally using, installing, operating and servicing equip-ment. When using these application examples, you recognize that Sie-mens cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these applica-tion 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 - then the contents of the other documents have priority.

Warranty, liability and support We do not accept any liability for the information contained in this docu-ment.

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 condi-tion which goes to the root of the contract (“wesentliche Vertragspflichten”). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health The above provisions does not imply a change in the burden of proof to your detriment.

Copyright© 2008 Siemens A&D. It is not permissible to transfer or copy these application examples or excerpts of them without first having prior authorization from Siemens A&D in writing. For questions about this document please use the following e-mail address:

mailto:[email protected]

mailto:[email protected]�

Table of Contents


V 2.0 04.06.08 3/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Table of Contents

Table of Contents ......................................................................................................... 3

1 Introduction..................................................................................................... 5 1.1 Main content ..................................................................................................... 5 1.2 Test environment .............................................................................................. 5 1.2.1 Equipment for the used system ........................................................................ 6 1.2.2 Installed software.............................................................................................. 7

Operating systems ....................................................................................... 7 SIMATIC software ........................................................................................ 7

2 Quality code management ............................................................................. 8 2.1 In General ......................................................................................................... 8 2.2 Inside SIMATIC PCS 7 ..................................................................................... 9 2.2.1 SIMATIC PCS 7 OS/ OS Multiclient ................................................................. 9 2.2.2 SIMATIC PCS 7 Engineering Station ............................................................. 17 2.2.3 SIMATIC BATCH ............................................................................................ 23 2.3 Inside SIMATIC IT .......................................................................................... 24 2.3.1 SIMATIC IT Real Time Data Server (RTDS) .................................................. 24 2.3.2 SIMATIC IT Plant Performance Analyzer (PPA)............................................. 26

PPA and Quality Code ............................................................................... 29 2.3.3 SIMATIC IT Historian Data Display (HDD) ..................................................... 36

Historian Trends......................................................................................... 36 BgViewer ActiveX control........................................................................... 37 Example of BgViewer and Quality Code .................................................... 37 X-Y Trend Viewer ActiveX control .............................................................. 43 Example of X-Y Trend Viewer and Quality Code ....................................... 43

2.3.4 SIMATIC IT Operation Debugging Support (ODS) ......................................... 44 2.3.5 SIMATIC IT Production Modeler (PM) ............................................................ 47 2.3.6 SIMATIC IT Plant Data Archive (PDA) ........................................................... 56

3 Possible failures with Quality management............................................... 67 3.1 Power failure AS ............................................................................................. 67 3.2 Network cable from the AS CP broken ........................................................... 70 3.3 Network cable from the OSM is broken or OSM is down................................ 72 3.4 CP1613 cable of the SIMATIC ES is disconnected or broken........................ 73 3.5 CP1613 on the SIMATIC ES is broken or stopped......................................... 74 3.6 CP1613 cable on SIMATIC PCS 7 OS Server is unplugged or broken.......... 76 3.7 HDD and AS stop ........................................................................................... 77 3.8 HDD and AS cable unplugged........................................................................ 78 3.9 HDD and RTDS stopped or started again ...................................................... 79

4 Example of usage of a KPI value with the help of the quality code......... 80 4.1 KPIs in general ............................................................................................... 80

Table of Contents


V 2.0 04.06.08 4/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

4.2 Example of using the quality code with PDA .................................................. 82 4.3 Example of using the quality code with PPA and KPI..................................... 89

5 Summary and example of usage................................................................. 93 5.1 Summary Quality management ...................................................................... 93 5.2 Example for the usage.................................................................................... 93 5.2.1 Status change 80 – 0 – 80.............................................................................. 96 5.2.2 Status change (80 – 0 – ) 80 – 40 – 80 .......................................................... 97 5.2.3 Status change (80 –) 40 – 0 – 40 ................................................................... 98 5.2.4 Status change with quality code 60 (SIMULATED) in the PLC

40 – 80 – 60 - 80 ........................................................................................ 99 5.2.5 Shutdown of PPA Server while running........................................................ 100 5.2.6 Usage of Aggregate functions in HDD.......................................................... 101 5.2.7 Aggregation functions supported by the PPACOM interface........................ 102 5.2.8 Modifying a sample in HDD .......................................................................... 104

6 References .................................................................................................. 110

7 Abbreviations.............................................................................................. 111

Introduction


V 2.0 04.06.08 5/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

1 Introduction

1.1 Main content

The information how to set up a running domain with SIMATIC software can be found in the document “SIMATIC software in a domain”.

Here just an overview of the environment which is used to give the informa-tion to the topic “Quality code management in SIMATIC PCS 7 and SIMATIC IT”.

1.2 Test environment

The following scheme shows the Windows active directory domain com-puters:

Figure 1-1 Schema of the Windows active directory domain computers

A private IP address band is used with fixed IP addresses.

http://support.automation.siemens.com/WW/view/en/26639558�

Introduction


V 2.0 04.06.08 6/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

1.2.1 Equipment for the used system

• 2 Windows active directory domain controllers (DNS, WINS)

• 2 SIMATIC PCS 7 OS Servers (redundant)

• 2 SIMATIC BATCH Servers (redundant)

• 1 SIMATIC PCS 7 Engineering System (ES)

• 2 SIMATIC PCS 7 OS Multiclient + SIMATIC BATCH Client

• 1 SIMATIC IT Production Modeler

• 1 SIMATIC IT Historian + PPA DB

• 1 SIMATIC IT Report Manager/ CAB engineering

• 1 SIMATIC IT components software + SITMesDB

• 1 SIMATIC AS CPU 417 with a CP 443-1

Introduction


V 2.0 04.06.08 7/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

1.2.2 Installed software

Operating systems The used operating systems for the domain computers can be found in ta-ble 1-1 Table 1-1

Station Installation

Windows 2003 MUI (Multilanguage User Interface) with SP2 Internet Explorer V6.0 SP2 (6.0.3790.3959)

Server

Image software Windows XP SP2 Client Image software Windows 2003 MUI (Multilanguage User Interface) with SP2 Domain Controller Internet Explorer V6.0 SP2 (6.0.3790.3959)

SIMATIC software SIMATIC software and its required software packages (e.g. message queu-ing, SQL Server 2005 with SPx, ..) are installed as needed. The installed software for SIMATIC PCS 7 and SIMATIC IT is the released “Integration Pack 2007” on top of the released SIMATIC Versions.

Table 1-2

Product Version

V7.0 SP1

Microsoft SQL 2005 SP1 HF

SIMATIC PCS 7

PCS 7 / SIMATIC IT Integration Pack 2007 Part1 Updates SIMATIC PCS 7 V6.3 SP1 Microsoft SQL 2005 SP2

SIMATIC IT

PCS 7 / SIMATIC IT Integration Pack 2007 Part2 Updates SIMATIC IT

A detailed list of the installed SIMATIC software can be found in the at-tachment A of the document “SIMATIC software in a domain”.


Quality code management


V 2.0 04.06.08 8/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2 Quality code management

2.1 In General

On the Wikipedia webpage (http://en.wikipedia.org/wiki/Quality) you can find currently several interpretations how the word “quality” is defined.

However, the “American Society for Quality” defines "quality" as "a subjec-tive term for which each person has his or her own definition” (http://www.asq.org/glossary/q.html).

In this document where we have a look at the quality code management of SIMATIC software we cannot let each person make a subjective decision weather a tag has a GOOD or a BAD value – the possible quality code of a tag within the SIMATIC software must be very clear defined, so that in the databases the status of a tag is clear and not discussable. Referring to the usage of the SIMATIC software, where e.g. reports for the production are created (e.g. for the FDA) it seems logical that the quality code must be de-fined very clear.

In the beginning is a tag inside the AS which is changed by the process (e.g. temperature, pressure,.. like the later seen “TEMPERATURE” of the reactor RC02). This value has a specific quality code which indicates whether the value is:

• a valid value,

• a simulated value or a

• non valid value.

It clearly makes no sense to use a not valid value of the “TEMPERATURE” to calculate an average over time using this value.

In the following chapters we will have a look at the possible quality codes of a tag, of the usage overall of the SIMATIC systems and possible failures which can impact the system.

The quality code informs of the quality of a tag independent where this code was formed.

http://en.wikipedia.org/wiki/Quality�

http://www.asq.org/glossary/q.html�



V 2.0 04.06.08 9/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.2 Inside SIMATIC PCS 7

2.2.1 SIMATIC PCS 7 OS/ OS Multiclient

SIMATIC PCS 7 OS is a powerful HMI system for use with Microsoft opera-tion systems. HMI stands for "Human Machine Interface", i.e. the interface between the person (the operator) and the machine (the process). The automation process retains actual control over the process. Communication between the SIMATIC PCS 7 OS and the operator on the one hand and SIMATIC PCS 7 OS and the automation systems on the other is affected.

• SIMATIC PCS 7 OS is used to visualize the process and develop the graphic user interface for the operator.

• SIMATIC PCS 7 OS allows the operator to observe the process. The process is displayed graphically on the screen. The display is updated each time a status in the process changes.

• SIMATIC PCS 7 OS allows the operator to control the process. He can, for example, predefine a set point or open a valve from the graphic user interface.

• An alarm will automatically signal in the event of a critical process status. If, for example, a predefined limit value is exceeded, a message will appear on the screen.

When working with SIMATIC PCS 7 OS, process values can either be printed or electronically archived. This facilitates the documentation of the process and allows subsequent access to past production data.

In SIMATIC PCS 7 OS, there are two quality indicators which allow you to evaluate the quality of tags. These two indicators are “tag status” and “qual-ity code”.

Tag status The “tag status” is formed in SIMATIC PCS 7 OS and informs of the quality of configuration settings within the OS. The tag status informs additionally of the connection status to the SIMATIC PCS 7 OS communication partner. This may be an automated system or the server computer.

Quality code The quality code contains the same information as the tag status. In addi-tion to this information, the quality status contains quality statements on partners which assess or process tags. Possible partners are:

• Automation systems

• Automation systems with field equipment

• OPC Server



V 2.0 04.06.08 10/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

• OPC Server with subordinate automation systems

Therein the quality code is forwarded within the processing chain. If at one point in the processing chain several quality codes are pending for a tag, the worst code is forwarded.

NOTE The quality code informs of the quality of a tag independent where this code was formed.

Cascading Quality Code By using the example of an automation system with field equipment con-nected, the cascading of quality codes shall be outlined.

The automation system reads the quality codes generated by the field de-vice. Using analysis logic, quality codes pending for the same tag concur-rently are evaluated by priority. The quality code with the worst status is as-signed to the tag. This quality code must be saved in a data block directly behind the associated tag value.



V 2.0 04.06.08 11/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-1 Quality of tags in the SIMATIC OS help

Using the analysis logic in the data manager, the quality code is generated from the tag status of the data manager and the quality code of the automa-tion device. Here too, the code with the worst status is passed on and saved as quality code by SIMATIC PCS 7 OS. For tags that do not have a quality code in the automation system, the quality code is always identical with the tag status.

The quality code has the following binary structure: QQSSSSLL

• Q: Quality

• S: Sub-status of the quality

• L: Limits. This value is optional.

NOTE The quality codes shown in the "Quality" table are basic values of the quality stages. Making use of the Sub-status and Limit elements gives rise to intermediate values over and above the quality stage concerned.



V 2.0 04.06.08 12/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Quality The first two places specify the quality of the tag.

Table 2-1

Q Q S S S S L L

Bad - The value is not useful. 0 0 Uncertain - The quality of the value is less than normal, but the value may still be useful.

0 1

Good (Non-Cascade) - The quality of the value is good. Possible alarm conditions may be indicated by the sub-status.

1 0

Good (Cascade) - The value may be used in control. 1 1

Substatus The quality alone is not enough. Individual qualities are divided into sub-states. The quality code is binary coded. In order to analyze quality codes their values must be converted into their hexadecimal representation.

Possible quality codes are listed in a table which can be found in the online help of the SIMATIC PCS 7 OS system.

Limits Quality codes can be further subdivided by limits. Limits are optional but in some cases these limits help to decode the quality. Also for this topic the online help provides a table with detailed information.

Quality Codes in Communication with OPC In the communication via the "OPC" channel, the quality codes that the OPC does not support will be converted.

Table 2-2

Quality Code in WinCC Quality Code in OPC Explanation (Detail see above)

0x48 0x40 Uncertain 0x4C 0x40 Uncertain 0x5C 0x40 Uncertain 0x60 0x40 Uncertain 0x80...0xD4 0xC0 Good

0xD8 0xC0 Good



V 2.0 04.06.08 13/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

If a tag does not have the expected value in Runtime, you can use the fol-lowing procedure to check the tag.

• In SIMATIC WinCC explorer in tag management, select the entry "Inter-nal tags" or “Named Connection” (Depending where your tag is to be found).

• In the data window, select the tag that you wish to check. To accom-plish this, open the directory structure until the tag is displayed in the data window.

• Move the mouse pointer over the tag to be checked. A tool tip window will open showing the current tag value, the quality code and the last time that the value changed.

• Check the quality code. If the value "80" is displayed, the tag value is OK. A description from the online help of the other values can be found in the online help.

• If the quality code is not equal to "80", select the tag in tag management and click on "Properties" in the pop-up menu to open the "Tag Prop-erties" dialog.

• Check whether values have been configured for the upper or lower lim-its or start value on the "Limits/Reporting" tab control. These values can affect the display.

• If the tag value is affected by one of the configured values, deactivate the project and change the limit or substitute value.

NOTE Tag values, quality codes etc. are only displayed in runtime.

Figure 2-2 Quality code “80” (GOOD) of a SIMATIC OS tag

The same applies not only to internal tags but to all tags in the project.



V 2.0 04.06.08 14/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

NOTE Tags which have a quality code in the AS are recognizable in the SIMATIC PCS 7 OS WinCC explorer as DBxxx, Dxx, QC (in the “Pa-rameters” column of the WinCCExplorer view).

Figure 2-3 Example of tags from the PLC in the form DBxxx, Dxx, QC

General approaches of the status of tags are the included status of the driver connections…

Figure 2-4 Status of driver connections inside SIMATIC OS



V 2.0 04.06.08 15/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

…and the channel diagnosis as first trouble shooting tool if the value of a tag is not displayed correctly.

Figure 2-5 SIMATIC WinCC channel diagnosis



V 2.0 04.06.08 16/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

In case a SIMATIC PCS 7 OS Client is not in runtime the logical connec-tions show a “Disconnected”.

Figure 2-6 SIMATIC PCS 7 OS logical connections



V 2.0 04.06.08 17/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.2.2 SIMATIC PCS 7 Engineering Station

In this chapter we show with an example of the test project “COLOR” how the quality code is managed in the SIMATIC PCS 7 Engineering Station. The “TEMPERATURE” of the Reactor RC02 from the Chart RC02_FC02 will serve as example.

Figure 2-7 SIMATIC Manager view

From the SIMATIC Manager we are able to open the CFC. CFC (Continu-ous Function Chart) is an editor with a graphical user interface, an exten-sion based on the SIMATIC STEP 7 software package. It is used to create the software structure of the CPU and is using preconfigured blocks. The editor lets you insert blocks into function charts, assign block parameters and interconnect blocks.



V 2.0 04.06.08 18/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Interconnecting in this context refers to connections created between blocks that allow data to be transferred from an output to one or more in-puts.

We open the chart “RC02_FC02” with a double click and see several blocks inside the CFC chart. As input we have a CH_AI block which is con-nected to the block and this one is connected to the CH_AO. You can see this in the following picture.

Figure 2-8 The chart RC02_FC02 from the COLOR project

In the following picture you have a detailed view on the CH_AI block.

In our test environment we do not have a real plant and therefore we simu-late the external hardware on the CH_AI block with the SIM_ON value set to 1.



V 2.0 04.06.08 19/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-9 Detailed view on the chart with blocks CH_AI and CTRL_PID

This setting enables the code 16#60 as output for the quality code which indicates that the simulation is turned on.

Figure 2-10 Quality Code 16#60 = Simulated



V 2.0 04.06.08 20/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Other possible values of the quality code for the CH_AI block can be found in the next table.

Table 2-3

Status Quality Code Possible Statuses for CH_AI

Valid value 16#80

Simulation 16#60 Last valid value 16#44 Substitute value 16#48 Invalid value 16#00

The possible values of the quality code for the CH_AO block can be found in the next table.

Table 2-4

Status Quality Code Possible statuses of CH_AO

Valid value 16#80 High range limited 16#56 Low range limited 16#55 Simulation 16#60 Invalid value 16#00

For more detailed information for the CH_AI, CH_AO and CTRL_PID block we refer to the online help.

The CTRL_PID block is also connected to our SFC-Instance “EM_TEMPERATURE” of our SFC-Type “TEMPERATURE” which handles the different states of the temperature (in general: Starting > Running > Completing > Completed > Holding > Held > Stopping > Stopped > Resum-ing > Aborting > Aborted > Idle) and in our case (Idle > Starting > Temp Control > HOLD_HELD_RESUME > ABORT_STOP_COMPL).



V 2.0 04.06.08 21/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-11 The SFC-Type “TEMPERATURE”

Figure 2-12 The SFC view of the SFC-Type “TEMPERATURE



V 2.0 04.06.08 22/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-13 CFC view of the EM_temperature

The quality codes can be monitored via the online connection of the CPU direct on the needed blocks.

Mostly a monitoring of these values inside the SIMATIC PCS 7 Engineering Station is only used during start-up of a plant or in case of a failure needed and most probably done on the SIMATIC PCS 7 OS side and not on SIMATIC PCS 7 ES side.



V 2.0 04.06.08 23/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.2.3 SIMATIC BATCH

SIMATIC BATCH is a SIMATIC PCS 7 program package with which dis-continuous processes, known as batch processes, can be configured, planned, controlled and logged.

Simple batch processes with configurable sequential control systems are automated with the CFC and SFC tools included in the SIMATIC PCS 7 Engineering System. SIMATIC BATCH is used for high requirements with recipe control strategy. With SIMATIC BATCH, recipe structures are de-signed, modified, and started graphically on an operator station or on a separate computer.

SIMATIC BATCH is suitable for batch processes of any complexity. It pro-vides simple support for batch applications from small to extremely large.

NOTE Inside SIMATIC BATCH the values of the quality codes are not displayed directly as this is the case in SIMATIC PCS 7 OS or SIMATIC PCS 7 Engineering Station.



V 2.0 04.06.08 24/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.3 Inside SIMATIC IT

2.3.1 SIMATIC IT Real Time Data Server (RTDS)

SIMATIC IT is in general an engineering platform for manufacturing based on the ISA S95 standard. According to this standard, explicit business and production rules coordinate functionality to achieve optimal workflow.

NOTE In SIMATIC IT it is possible to work with a general key named “Enable quality flag management” to work with the quality codes provided by the DCS/ OPC system or not. The setting is located under:

“Unit > Real Time Data Engine > RTDE Offline Configu-ration”

in the tab “Advanced” choose the tab “General”.

Figure 2-14 The key “Enable quality flags management”

We have enabled the quality flag management in our project.

NOTE In this example we are using the “Enable quality flags management” to describe the usage of the quality management inside SIMATIC IT in the general settings of RTDS.



V 2.0 04.06.08 25/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

SIMATIC IT Real Time Data Server (RTDS) is a software layer building up a bridge between SIMATIC IT components and field devices. It manages a common data memory for all data coming from the field, making it available to all upper-level components.

Figure 2-15 System architecture of RTDS

RTDS is communicating in two possible ways with the data coming from external:

• SIMATIC Data Access Channel driver (DRIVAR2) (Recommended)

• OPC Client driver (OPCLIENT)



V 2.0 04.06.08 26/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-16 The recommended data access channel to SIMATIC PCS 7

2.3.2 SIMATIC IT Plant Performance Analyzer (PPA)

SIMATIC® IT Plant Performance Analyzer (PPA) is a long-term archiving package, suitable for storing, validating and aggregating process data into a standard RDBMS (SQL Server). It is part of the SIMATIC IT Historian so-lution.

In conjunction with SIMATIC IT RTDS and SIMATIC IT Plant Data Archive (PDA), PPA allows the user to:

• retrieve real-time process data from very different field devices (via the Real Time Data Server drivers and the OPC Data Access interfaces).

• compress and store such data in a proprietary file archive (the SIMATIC IT PDA archive).

• sample, validate and aggregate such data for storage in the Plant Per-formance Analyzer relational database.

In addition to data from RTDS and the PDA Server, PPA can also collect data from any external relational database, provided a suitable ODBC driver is available for such a RDBMS.

In the beginning you start with creating a database inside PPA. For a de-tailed description of how to create a PPA database see the knowledge management document “Data exchange between SIMATIC PCS 7 / BATCH and SIMATIC IT Historian”.





V 2.0 04.06.08 27/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Here in short the basic settings of the new created database for the quality management.

Figure 2-17 Basic settings of the PPA DB – register “General”

Figure 2-18 Basic settings of the PPA DB – register “Project Type”



V 2.0 04.06.08 28/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-19 Basic settings of the PPA DB – register “Database online”

The registers “Lock” and “E.S. Settings” are in our project empty and not used. The shown settings are just an example. They can defer from your settings in your project.



V 2.0 04.06.08 29/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

PPA and Quality Code PPA can also influence the quality code of a tag. If you are archiving a tag from an historical data source or after an aggregation, PPA can validate the samples. If the values don’t fit into the validation criteria, PPA will change the quality stamp. As an example we show here the usage of an aggrega-tion function of PPA. As starting point create a tag inside the PPA in a Class which is using WinCCTaglogging as data source.

Figure 2-20 Creation of a new tag



V 2.0 04.06.08 30/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Apply a name, choose the tag, configure the display options and finally choose in the Sample validation an available function. Note that the de-scription states that these functions apply to the raw samples a quality code. Choose e.g. “WithinRange” as function.

Figure 2-21 Sample validation - WithinRange



V 2.0 04.06.08 31/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Use the button "Configure" for the Configuration.


Configure the Constant with a Low and High Threshold. As we are using as source point the level of a Silo, which can range from 0 – 1000 kg we use as “Low Threshold” 25.

Figure 2-23 Configure Threshold



V 2.0 04.06.08 32/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

After the configuration the "Sample Validation" window looks like that.


Complete the Tag configuration wizard, approve the configuration. Create a new Trend and run the Chart configuration wizard. Choose PPA as source.

Figure 2-25 Standard trend Configuration with PPA



V 2.0 04.06.08 33/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

In the Item selection choose the tag which was created before.




V 2.0 04.06.08 34/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Apply if wanted an aggregate function and finish the wizard.




V 2.0 04.06.08 35/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The values of the tag are displayed in a trend. The silo gets emptied and once the value of the tag gets lower then our configured threshold of 25, the values will be displayed in the table on the right side in red.


The quality details show that the values for the threshold limits failed.

Figure 2-29 Quality Details – Threshold Limits



V 2.0 04.06.08 36/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.3.3 SIMATIC IT Historian Data Display (HDD)

SIMATIC® IT Historian Data Display (HDD) is the presentation client of SIMATIC IT Plant Data Archive (PDA) and SIMATIC IT Plant Performance Analyzer (PPA).

Several graph types can be configured and saved as files:

• Historian Trends (i.e. Standard Trend and Time Overlay Trend)

• BgViewer

• Production Viewer

• Message Viewer

• Message Analyzer

• X-Y Trend Viewer

An HDD can contain up to 64 charts of those types listed above. Fre-quently-used Historian Data Display configurations can be saved as user workspaces for reuse.

Historian Trends The HDDX control is one of the ActiveX controls available in the SIMATIC IT Historian Data Display module. Like all ActiveX controls, it can be in-serted in any container application that you are working with and it can also be programmed, customized, and managed using script codes.

The HDDX control is used to display historical data stored in SIMATIC IT PPA or SIMATIC IT PDA in time-based trends, by means of two different chart types:

• Standard Trend: …charts that display several items within the same time interval.

• Time Overlay Trend: ...charts that display a single item over different time intervals.

Features:

• Both Standard Trend and Time Overlay Trend charts may contain up to 64 trends.

• Standard Trend charts support automatic updates with a configurable refresh rate.

• Table view to show stored or interpolated samples.

• Quality information for stored samples.



V 2.0 04.06.08 37/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

BgViewer ActiveX control The BgViewer ActiveX control is displayed in the HDD container. Like all ActiveX controls, it can be inserted in any container application, and it can be programmed, customized, and managed by using script codes.

The BgViewer ActiveX control is used to display historical data stored in SIMATIC IT PPA or SIMATIC IT PDA in the form of a bargraph. For more information on the corresponding properties/methods, see SIMATIC IT His-torian Data Display COM Interface online help.

The bargraph is built with data aggregated over various time intervals:

• Each time interval is called a cluster.

• Each bar is called a data series and represents the value of an item over a certain period of time (a certain cluster).

Features:

• Aggregating data series using predefined functions.

• Configuring table view to display samples.

• Quality information for stored samples.

Example of BgViewer and Quality Code Run in the HDD viewer a new bargraph (BgViewer). Start the Chart Con-figuration Wizard and choose PPA as Source.

Figure 2-30 Example for BgViewer and Quality Code



V 2.0 04.06.08 38/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Choose the PPA project and archive and select the items to display.


Choose in the Cluster Management the "Add" button to define a new Clus-ter.




V 2.0 04.06.08 39/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Configure the Time for the display cluster.


Add a second Cluster with another time frame if you like. The result can be seen in the next picture.




V 2.0 04.06.08 40/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

With the aggregate function you can choose to apply a function to the tags now or later.


Finish the Wizard. Apply in the window chart configuration an aggregate function.




V 2.0 04.06.08 41/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

From here you can also with a double click assign an Aggregate Function.




V 2.0 04.06.08 42/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Choose e.g. the “PERCENTGOOD” or “PERCENTBAD” Aggregate Func-tion and after applying these settings the Bargraph viewer might look like this.


NOTE With this function you have the possibility to have a look at the quality codes of your tags over a specified time range. You can also compare the same tags qualities over two or more time frames (hours, days, months).



V 2.0 04.06.08 43/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

X-Y Trend Viewer ActiveX control The X-Y Trend Viewer ActiveX control is displayed in the HDD container. Like all ActiveX controls, it can be inserted in any container application, and programmed, customized, and managed through script codes.

The X-Y Trend Viewer ActiveX control manages the X-Y chart display whe-re each data point is the result of the intersection of X values and Y values; the values of both tags are interpolated onto the same time base.

The X-Y Trend Viewer ActiveX control is used to display historical data sto-red in SIMATIC IT PPA or WinCC in the form of a temporal trend.

For more information on the corresponding properties/methods/events, see SIMATIC IT Historian Data Display COM Interface online help.

Example of X-Y Trend Viewer and Quality Code In the X-Y Trend Viewer you can see the Quality Code of the values X and Y. With this view you can in an overview compare two values X and Y – e.g. the temperature of two reactors.

Figure 2-39 X-Y Trend Viewer and Quality Code



V 2.0 04.06.08 44/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.3.4 SIMATIC IT Operation Debugging Support (ODS)

The SIMATIC® IT Operation Debugging Support (ODS) module allows the programmer to test and view an application program. Thanks to ODS you can display the variables used by the program, and detailed information about each of them, in different representation formats. You can also mod-ify their value in runtime, in order to check the behaviour of the application program.

Each time you run or stop a RTDS Unit, or suspend or resume a sequence, or set a variable from a monitor window, ODS automatically notifies the SIMATIC IT Event Manager Server, so that it keeps track of these events.

Figure 2-40 Starting Operation Debugging Support

NOTE Quality information is displayed only if quality flag management is en-abled.



V 2.0 04.06.08 45/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

1. Insert the variable, whose quality value you want to read, in a Monitor window.

2. Select the variable in the Monitor window and choose command: "Debug > Quality Information…", or: right-click the variable and choose command “Quality Information…” from the shortcut menu.

3. The following information is displayed: Table 2-5

Attribute Description

Status value Integer value, not masked Quality Quality value. Value describing the quality status. Substatus Detailed description of the quality status. Depends on the quality

value, which can be GOOD, BAD, UNCERTAIN. Limit Value providing useful diagnostic information.

Figure 2-41 Quality information inside SIMATIC ODS

The status value 192 is coming from RTDS. The following Quality status flags are available:

Table 2-6

Quality (bits 6 and 7)

BAD_QUALITY 0: Bad (see substatus below for more details) UNCERTAIN_QUALITY 1: Uncertain (see substatus below for more details) N_A_QUALITY 2: Not used by OPC GOOD_QUALITY 3: Good



V 2.0 04.06.08 46/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

NOTE The value 192 decimal is binary 11xxxxxx. This means that the bits 6 and 7 are 1 which means decimal 3 if you look only at these two bits. A bad quality would be binary 00xxxxxx.

In case the quality code inside the ODS is bad, you see a red circle with an white x as symbols in front of the value.


In case the quality code inside the ODS is uncertain, you see a green circle with a white "?" as symbol in front of the value.




V 2.0 04.06.08 47/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.3.5 SIMATIC IT Production Modeler (PM)

Inside the Production Modeler (PM) it is possible to have a look at the qual-ity codes via a script caller and a function called: “SCRIPT.read-scattered-values”.

For the usage of this function create a new “REPAC-LEAF” and insert a “Script caller”.

Figure 2-44 Adding a script caller to a rule inside PM



V 2.0 04.06.08 48/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-45 Configuration of a script caller to a rule inside PM

Figure 2-46 The configured Rule with the script caller

The script caller “SCRIPT.READ-SCATTERED-VALUES” must be config-ured.

Figure 2-47 Configuration of a script caller to a rule inside PM



V 2.0 04.06.08 49/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

You have to configure the input arguments “Input-Data” and “Input-Option”. The detailed configuration for these two input arguments can be seen in the following pictures. The return argument remains in our case empty as this rule only shows how to get values out of RTDS into the PM.

Figure 2-48 Configuration of a script caller to a rule inside PM >Input-Data



V 2.0 04.06.08 50/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-49 Configuration of a script caller to a rule inside PM >Input-Option



V 2.0 04.06.08 51/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The description of what to fill in into the expression can be found in the online help of the Production Modeler.

Figure 2-50 Online help of the SCRIPT.read-scattered-values



V 2.0 04.06.08 52/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

After you activated the rule you can have a look at the execution copy.

Figure 2-51 Activating the rule and showing the execution copy

Figure 2-52 The activated rule with the return-data

In the execution copy you can see in the return arguments, the quality code (RTDS-QUALITY). In this example the well known code 192 (GOOD - ex-plained in the ODS chapter). You can have a look at the return values ei-ther on clicking the Button … in the properties window in the line Return-Data which opens a Textual Editor box,

or



V 2.0 04.06.08 53/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

clicking on the script caller with a right mouse click "Properties" in the tab "Return Arguments" with a tool tip text which shows up when going with the mouse over the Value.

Figure 2-53 The activated rule with the return-data



V 2.0 04.06.08 54/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Make sure that the external connections (RTDS Units and SIMATIC IT In-terface) are configured and started otherwise you cannot have the values from the RTDS inside the PM.

Figure 2-54 External Connections

NOTE In the online help you can find a good description for the Sample Librar-ies. On of these libraries called RT-Basic-Library.Lib.kb provides exam-ples of using the quality code change as source of an event.



V 2.0 04.06.08 55/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-55

Have also a look at the following chapter:

• Triggering Actions when the values of RTDS tags change.

Where an event is triggered each time the value of the RTDS tag changes, and its quality is "Good".



V 2.0 04.06.08 56/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2.3.6 SIMATIC IT Plant Data Archive (PDA)

PDA is a storage tool which can store thousands of variables at a minimum of a one second sampling rate while saving mass memory. These perform-ance levels are possible due to data compression techniques that prevent PDA from writing each individually sample to disk. In every case, quality flag from RTDS is propagated by PDA.

You can start PDA either over

”Server > Plant Data Archive (PDA)”

Figure 2-56 Starting plant data archive server

or: with an double click on “Server” in: Tab Historian > Historical > Server

Figure 2-57 Starting plant data archive server



V 2.0 04.06.08 57/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The configuration can also be opened in two ways: "Configuration > Plant Data Archive > Configuration" Figure 2-58 Starting plant data configuration

or: in the Historian Register of the management console with a double click on "Historical > Configurator".

Both actions open the following editor.

Figure 2-59 Server configuration of PDA



V 2.0 04.06.08 58/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Over the “Config” Button you can check if the quality management is en-abled.

Figure 2-60 Server configuration of PDA

With the “Back” button it is possible to change the setting for the quality management.

Figure 2-61 Configuration of the quality management in PDA



V 2.0 04.06.08 59/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The path where the archives are being stored is the path of the Plant – in this case D:\COLORV7.PLT\DATA.log\ARCH

Figure 2-62 Storing path of the archives

For configuring a tag (point) for PDA - open the Database Editor from the management console: "Unit > Database Editor".

Figure 2-63 Configuring tags (points) for PDA



V 2.0 04.06.08 60/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Then mark the tag (point) you want to archive with PDA in the database editor and with “View > Point Viewer…”

Figure 2-64 Point Viewer

…open the dialog window Point Viewer.

Change the register from Main to PDA.


Mark the check box “Present” if you want to have this tag (point) in the ar-chive of the PDA.



V 2.0 04.06.08 61/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Do not forget to update these new points in the PDA Server. You can do it directly in the Database Editor.


If you select “NO” you have to do it manually in PDA server Configuration. To update the points, use the button “Points”.


The button “Arch” starts the archiving with PDA. It also allows stopping the archiving.



V 2.0 04.06.08 62/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed


With the button “Show” you can select the tags (points) with the help of a fil-ter.

Figure 2-69 Filter

After the filtering you can select which tag (point) must be archived and which not.



V 2.0 04.06.08 63/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed


After configuring the PDA archive you can start the HDD and run the con-figuration wizard. Choose the Plant Data Archive (PDA) as the source for the HDD screens.

Figure 2-71 HDD view of PDA archives



V 2.0 04.06.08 64/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Then choose the previous marked tags for PDA in the COLOR project.




V 2.0 04.06.08 65/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Here, as an example, the remaining capacity of a Silo. You can see the Quality Code of the Tag in the column “Quality”.


NOTE PDA does not have an interface but you can check if it is running in the task list of the management console.



V 2.0 04.06.08 66/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 2-74 Task list of the management console

NOTE If you modify the PDA configuration – for instance number of archives, flush time – all archives will be lost!

Possible failures with Quality management


V 2.0 04.06.08 67/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3 Possible failures with Quality management

3.1 Power failure AS

In the case that the AS has a power failure you have for sure no valid val-ues anymore from the AS. In that case you will have the following message in case your SIMATIC ES is online connected to the AS.

Figure 3-1 Message in CFC when the AS has a power failure

Figure 3-2 Message and view to CFC in case of a power failure

In addition the online monitored values are shown in red stars.



V 2.0 04.06.08 68/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

On the SIMATIC PCS 7 OS Servers you might observe the power loss in two ways. One way is the monitoring of the “Channel diagnosis”, a build in tool to monitor the online connection to the AS. The dialog “Channel diag-nosis” is only available on the SIMATIC PCS 7 OS Servers.

Figure 3-3 SIMATIC OS channel diagnosis window in case of AS power loss



V 2.0 04.06.08 69/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Another possibility is to see in the SIMATIC PCS 7 OS runtime pictures all values greyed out. This view is also visible on the SIMATIC PCS 7 OS Mul-ticlients.

Figure 3-4 SIMATIC OS greyed out values due to a AS power loss



V 2.0 04.06.08 70/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3.2 Network cable from the AS CP broken

In case that the cable from the AS CP is broken or unplugged you receive the same messages on the SIMATIC ES and OS side as in the previous chapter.

Figure 3-5 Network cable from AS CP

Figure 3-6 Message in CFC when the AS network cable is broken



V 2.0 04.06.08 71/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 3-7 SIMATIC OS channel diagnosis window in case of AS network cable is broken

NOTE The online connection on the Engineering System (test mode) to the AS is not restored automatically. Turn off the test mode and start it again in order to have a connection back.

The SIMATIC PCS 7 OS connection is restored automatically while plug-ging in the cable again.



V 2.0 04.06.08 72/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 3-8 Notes on the online connection of the CFC

3.3 Network cable from the OSM is broken or OSM is down

Also in the case a cable of the OSM is unplugged (or broken) or the power of the OSM is down the same messages as in the previous two chapters can be seen.



V 2.0 04.06.08 73/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3.4 CP1613 cable of the SIMATIC ES is disconnected or broken

In case the cable of the CP1613 on the ES is broken or unplugged the fail-ure message can only be seen on the SIMATIC ES side. The SIMATIC OS does not recognize an error in that case.

Figure 3-9 Cable of ES disconnected or broken

Figure 3-10 Message in CFC when the CP1613 network cable on the ES is broken



V 2.0 04.06.08 74/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3.5 CP1613 on the SIMATIC ES is broken or stopped

In case the CP1613 on the SIMATIC ES side is broken or stopped also, here a loss of the online connection can be seen.

Figure 3-11 CP1613 on ES broken/stopped

Figure 3-12 CP1613 on ES broken/stopped



V 2.0 04.06.08 75/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 3-13 Message in CFC when the CP1613 on the ES is broken or stopped



V 2.0 04.06.08 76/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3.6 CP1613 cable on SIMATIC PCS 7 OS Server is unplugged or broken

In case the cable of the CP1613 on the SIMATIC PCS 7 OS Server is bro-ken or unplugged the “Channel diagnosis” shows a disconnected failure.

Figure 3-14 Network cable OS broken or unplugged

Figure 3-15 Message in SIMATIC OS when the CP1613 cable on the SIMATIC OS Server is broken



V 2.0 04.06.08 77/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3.7 HDD and AS stop

In case the AS is going to stop the monitored quality values will be dis-played with a value of BAD. Once the AS is powered on the value will be displayed with a GOOD value.

Figure 3-16 HDD and its behavior when the AS goes to stop



V 2.0 04.06.08 78/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3.8 HDD and AS cable unplugged

In case the network cable is unplugged the monitored values will have the quality code BAD. Once the cable is reconnected the value shows the qual-ity value GOOD again.

Figure 3-17 HDD and its behavior when the AS cable is unplugged



V 2.0 04.06.08 79/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

3.9 HDD and RTDS stopped or started again

In case you stop the RTDS the values cannot be provided anymore to the PPA databases. In this case the monitored quality values in the HDD will show a BAD quality.

Figure 3-18 Details of the stop of the RTDS

Figure 3-19 Details of the stop of the RTDS

Once the RTDS is restarted again the monitored quality values will have a GOOD quality value again.

Example of usage of a KPI value with the help of the

quality code


V 2.0 04.06.08 80/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

4 Example of usage of a KPI value with the help of the quality code

4.1 KPIs in general

Key Performance Indicators (KPIs) are values, which can be aggregated in various ways depending on the level of the person by whom they are de-fined and calculated. KPIs can be applied to various plant areas, contextu-alized and added to the production process by integrating PPA with SIMATIC IT Production Modeler.

Examples:

• Measures stored cyclically to be displayed as trends in a business con-text (e.g. a Production Operation), such as weights, motor amperages, steam demands, tank levels, etc.

• Aggregations (averages, max, min, etc.) calculated cyclically over the historical data logged by SIMATIC IT Process Data Archive, WinCC Tag Logging System, or any OPC-HDA Server.

• Any data relevant to a particular production phase (calculations, energy consumption, yield, and efficiency calculations, quality data, etc.): this data is typically represented by a single value for each production phase and is processed on event.

• Statistics calculated over binary signals and status information (total du-ration, number of events per period, etc.).

Prerequisites for using KPIs Before creating a KPI, it is necessary to define its type, using one of the fol-lowing:

• Cyclic

• On Event

• On Event Over Time

• Dummy

Engineering - To create a KPI, do as follows: • Within SIMATIC IT Production Modeler, create the equipment hierarchy

model.

• Within SIMATIC IT Production Modeler, create and configure KPIs.

• Import the KPI into SIMATIC IT Business Process Modeler by downloading the Plant Model.


quality code


V 2.0 04.06.08 81/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

• Within SIMATIC IT PPA, import KPIs from SIMATIC IT Business Proc-ess Modeler.

• If necessary, define tags (this can also be done after step 3).

• Associate KPIs with tags.

Runtime - To display a KPI, do as follows: • Within SIMATIC IT Plant Performance Analyzer, start Configuration Edi-

tor.

• Within SIMATIC IT PM, start POs or activate Rules.

Important To schedule properties and set production keys correctly, the SIMATIC IT PPA Server must be in RUN status and its property and key configuration perfectly aligned with the Production Modeler configuration.

Note It is also possible to declare a Tag in the PPA configuration with an attribute “Is KPI”.


quality code


V 2.0 04.06.08 82/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

4.2 Example of using the quality code with PDA

In the AS system you have e.g. the CTRL_PID with the value PV_IN and the corresponding quality code QC_PV_IN. In the following picture the quality code is 16#80 which indicates a GOOD quality.

Figure 4-1 GOOD quality in the AS

This value is transferred to the SIMATIC PCS 7 OS system and can be monitored in the WinCC explorer of the system. The value is the same as in the AS system.

Figure 4-2 Good quality in the OS system


quality code


V 2.0 04.06.08 83/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

When you change e.g. the value manually in the CFC chart to a bad quality 16#0, …

Figure 4-3 BAD quality code of the value PV_IN

…the value is immediately transferred to the SIMATIC PCS 7 OS system.

Figure 4-4 BAD quality in the OS system

NOTE For usage with PDA you have to enable the tag of the PV_IN for the PDA in the database editor.

This can be done over the Point viewer in the register PDA.


quality code


V 2.0 04.06.08 84/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Figure 4-5 Settings in the database editor

In a detail view the PDA register looks like that:

Figure 4-6 Register PDA


quality code


V 2.0 04.06.08 85/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The corresponding RTDS setting looks like this:

Figure 4-7 Register RTDS

Then you have to update the configuration via the “Points” button.

Figure 4-8 Update the point configuration


quality code


V 2.0 04.06.08 86/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Now we can begin with the HDD settings and run the wizard and choose the PDA as source.

Figure 4-9 Running the wizard for the PDA

After choosing the desired variables – in this case only the value PV_IN from the Reactor 2 …

Figure 4-10 Choosing the variables


quality code


V 2.0 04.06.08 87/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

…you can choose the aggregate function.

With no function you choose all data which comes from the field.

Figure 4-11 Aggregate function


quality code


V 2.0 04.06.08 88/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

If you run now a SIMATIC BATCH batch which uses the temperature of the Reactor 2…

Figure 4-12 Running a batch

…you can see the value and in the right side in the table the corresponding quality code of the tag.

Figure 4-13 Quality code inside HDD

With a double click on the quality you open a window with the “Quality de-tails” of the specific entry (see picture above).


quality code


V 2.0 04.06.08 89/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

4.3 Example of using the quality code with PPA and KPI

In the beginning you have to define the specified Tag inside the PPA con-figuration editor.

Figure 4-14 Configuring PPA tag


quality code


V 2.0 04.06.08 90/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

In this example we configure the temperature of the Reactor 2 which is ex-plained in the previous chapters. We will not use the Audit Trail support as this is part of another knowledge management document.

Figure 4-15 Configuring PPA tag

In this example we will use the KPI as a possible choice for this tag.

Figure 4-16 Configuring the PPA tag


quality code


V 2.0 04.06.08 91/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Then you have to select where to store the tag. As this is an example for PPA we choose the settings visible in the screenshot.

Figure 4-17 Configuring the PPA tag


quality code


V 2.0 04.06.08 92/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

After configuring the tag and approving the configuration it is possible to start the HDD and configure with the help of the configuration wizard the HDD screen with the desired tag. With the table on the right side visible you can have an immediately view of the quality code.

Figure 4-18 Using the configured PPA tag inside HDD

Summary and example of usage


V 2.0 04.06.08 93/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5 Summary and example of usage

5.1 Summary Quality management

The quality management is a chain which is coming from values of the AS. These values will be either used inside the Engineering System (CFC) and/or displayed in the SIMATIC PCS 7 OS. There every value is displayed with a quality code. You can not choose not to display the quality code.

In SIMATIC IT you can choose while starting your project if you want to use the quality codes provided or not. If you choose to use them you can see the quality code of tags inside HDD (with tags from the PPA database and the other described SIMATIC IT software packages). If you choose not to use the Quality Codes, SIMATIC IT creates its own quality codes.

5.2 Example for the usage

Here an example for the usage of the quality code. We take the process value for the PID_CTRL of the temperature from the RC02_FC02 chart. Here you can change manually the quality code inside the PLC of the value PV_IN.

Figure 5-1 The CFC chart RC02_FC02



V 2.0 04.06.08 94/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Possible status changes in the PLC are the following: Table 5-1

Possible Status Description Info

16#00 BAD Used in HDD 16#40 UNCERTAIN Used in HDD 16#60 SIMULATED NOT supported in HDD 16#80 GOOD Used in HDD

A matrix shows the possible jumps from one quality code to another quality code in the AS. The value 16#60 (SIMULATED) which is not directly sup-ported in the HDD (supports BAD, GOOD and UNCERTAIN) is shown also as UNCERTAIN value in the HDD.

Table 5-2

Possible jumps from

to Status in HDD before

Status in HDD after

Result

16#00 16#40 16#00 UNCERTAIN OK 16#00 16#60 16#00 UNCERTAIN OK 16#00 16#80 16#00 GOOD OK 16#40 16#60 16#40 UNCERTAIN OK 16#40 16#80 16#40 GOOD OK 16#40 16#00 16#40 BAD OK 16#60 16#00 16#60 BAD OK 16#60 16#40 16#60 UNCERTAIN OK 16#60 16#80 16#60 GOOD OK 16#80 16#00 16#80 BAD OK 16#80 16#40 16#80 UNCERTAIN OK 16#80 16#60 16#80 UNCERTAIN OK



V 2.0 04.06.08 95/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The value PV_IN from the PID_CTRL can be added with the help of the SIMATIC tag browser to the RTDS dictionary.

Figure 5-2 Adding the value PV_IN with the PCS 7 tag browser to the RTDS data dictionary

The value PV_IN has then to be configured in the PPA configuration to col-lect the value in a specific time frame.

NOTE Please remember that in SIMATIC IT you can decide to enable the qual-ity information or not (see chapter 2.3.1 “SIMATIC IT Real Time Data Server (RTDS)”). Depending what you have chosen there you will see the quality code information or not.



V 2.0 04.06.08 96/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.1 Status change 80 – 0 – 80

The status change from a quality code 80 (GOOD) to 0 (BAD) and back in the AS and the affects on the projected PV_IN value in HDD can be seen in the next picture.

Figure 5-3 Status change 80-0-80

The value of the PV_IN is “GOOD” as long as the value QC_PV_IN is “GOOD” (for test reasons here manually changed directly in the AS). Once changed to “BAD” the quality code in the HDD is displayed also as “BAD”.

NOTE As you can see the value of the PV_IN is NOT displayed in the HDD as long as the quality code is „BAD“. The value is collected but in the curve drawing these values are not used.



V 2.0 04.06.08 97/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.2 Status change (80 – 0 – ) 80 – 40 – 80

The status change from a quality code 80 (GOOD) to 40 (UNCERTAIN) and back in the AS and the affects on the projected PV_IN value in HDD can be seen in the next picture.


The value of the PV_IN is “GOOD” as long as the value QC_PV_IN is “GOOD” (for test reasons here manually changed directly in the AS). Once changed to “UNCERTAIN” the quality code in the HDD is displayed also as “UNCERTAIN”.

NOTE As you can see the value of the PV_IN is also displayed in the HDD as long as the quality code is „UNCERTAIN“. The value is collected and in the curve drawing the values are displayed.



V 2.0 04.06.08 98/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.3 Status change (80 –) 40 – 0 – 40

The status change from a quality code 40 (UNCERTAIN) to 0 (BAD) and back in the AS and the affects on the projected PV_IN value in HDD can be seen in the next picture.


The value of the PV_IN is “UNCERTAIN” as long as the value QC_PV_IN is “UNCERTAIN” (for test reasons here manually changed directly in the AS). Once changed to “BAD” the quality code in the HDD is displayed also as “BAD”.

NOTE As you can see the value of the PV_IN is displayed in the HDD as long as the quality code is „UNCERTAIN“. The value is collected and in the curve drawing the values are displayed. As soon as the quality code is “BAD” the value is not written.



V 2.0 04.06.08 99/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.4 Status change with quality code 60 (SIMULATED) in the PLC 40 – 80 – 60 - 80

The value of the PV_IN “SIMULATED” will be displayed in the HDD as “UNCERTAIN”. The value “SIMULATED” is not directly supported and is changed to “UNCERTAIN” in the display.

Nevertheless to find out if the value in the AS was really “UNCERTAIN” (16#40) or “SIMULATED” (16#60) you have the possibility to check this in the HDD display. Simply make a double click on the table in the HDD and the quality details will be displayed. There you can read the quality code and judge if it is 16#60 or 16#40 “UNCERTAIN” value.

Figure 5-6 Open the quality details window with a double click on the Quality field



V 2.0 04.06.08 100/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.5 Shutdown of PPA Server while running

In case the PPA Server is going down (e.g. due to the start of a new con-figuration - and you have no redundancy covered through a proper PDA configuration) naturally no values are displayed in HDD. The Start and Stop of the PPA Server is marked in the HDD view.

NOTE As you can see the value of the PV_IN is not written in the HDD as long as the PPA Server is down.

Figure 5-7 No values are written when the PPA Server is down



V 2.0 04.06.08 101/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.6 Usage of Aggregate functions in HDD

One of the key features of SIMATIC IT Plant Performance Analyzer is its capability of applying calculation functions to the samples.

• During the collection of the data (PPA configuration necessary) in order to aggregate them and store a smaller amount of data.

• During the data display on the HDD on collected data.

NOTE Quality information is used to validate the samples before performing a calculation: raw samples marked with a “BAD” or “UNCERTAIN” quality are not used for the calculation.

If the aggregation function needs at least a certain number of samples to be applied, it is possible to configure a minimum percentage of valid samples as a pre-requirement for applying the aggregation function. A suitable func-tion, Min. percentage of valid samples, with a configurable parameter (the percentage itself), is provided to this purpose. If, in a certain buffer, the valid samples (according to their quality and to the validation functions, if any) are fewer than this percentage, no calculation is applied and an invalid sample (with an OPCHDA_NODATA quality) is stored.

The time stamp associated to the aggregated value can be chosen to be one of the following three:

• the time stamp of the most recent sample used for the aggregation

• the time stamp of the oldest sample

• the mean of the oldest and the newest

Aggregation functions can be applied not only to the whole set of samples, but also to subsets of samples. This is achieved by defining an application frequency for the function: for example, when SIMATIC IT Plant Perform-ance Analyzer retrieves 24 hours samples (with a 1-minute resolution), it is possible to apply the average to every hour’s samples (i.e. SIMATIC IT Plant Performance Analyzer will calculate and store 24 averages, each one over 60 samples).

This choice is available as a configuration option, named “Apply function every”, and is disabled when the data are obtained from the data source not at a fixed time resolution, i.e. when they are not interpolated samples. In such a case, the aggregation functions are applied only once to the whole set of samples (provided they have been suitably validated).



V 2.0 04.06.08 102/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.7 Aggregation functions supported by the PPACOM interface

Figure 5-8 Possible aggregate functions

Table 5-3

Aggregate Name Description

No Function PPA_PERCENTBAD Returns the ratio between samples with quality flag = BAD

and the total number of samples in the specified time interval (i.e. a value between 0 and 1).

PPA_TOTAL Retrieve the totalized value (time integral) of the data over the resample interval.

PPA_AVERAGE Retrieve the average data over the resample interval. PPA_TIMEAVERAGE Retrieve the time weighted average data over the resample

interval. PPA_STDEV (unbiased) Retrieve the standard deviation over the resample interval. PPA_STDEV (biased) Retrieve the standard deviation over the resample interval

(BIASED). PPA_MINIMUM Retrieve the minimum value in the resample interval.



V 2.0 04.06.08 103/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Aggregate Name Description

PPA_MINIMUMACTUALTIME Retrieve the minimum value with the corresponding time stamp.

PPA_MAXIMUM Retrieve the maximum value in the resample interval. PPA_MAXIMUMACTUALTIME Retrieve the maximum value with the corresponding time

stamp. PPA_VARIANCE (unbiased) Retrieve the variance over the sample interval. PPA_VARIANCE (biased) Retrieve the variance over the sample interval (BIASED). PPA_RANGE Retrieve the difference between the minimum and maximum

value over the sample interval. PPA_SUM Returns the sum of all samples in the specified time interval. PPA_COUNT Returns the number of samples in the specified time interval. PPA_PERCENTGOOD Returns the ratio between samples with quality flag = GOOD

and the total number of samples in the specified time interval (i.e. a value between 0 and 1).



V 2.0 04.06.08 104/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

5.2.8 Modifying a sample in HDD

NOTE This function requires the installation of the Compliance Service (CS) database and the installation of the needed licenses for the CS.

Here are the steps described in case you want to change a sample in the HDD. For a basic setting in the PPA configuration you have to allow the change of a sample (Audit trail). In the register Audit trail support you can choose one of the following AT support:

• None

• Audit Trail

• AT with Electronic Signature (used in example)

Figure 5-9 Register “Audit Trail support”



V 2.0 04.06.08 105/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

After approving the configuration and starting the PPA Server with this new configuration you can change collected values inside the HDD.

• Right-click the sample of interest, either in the chart or in the table.

• Select the Modify Sample command from the shortcut menu: the Modify Sample dialog box is displayed.

Figure 5-10 Function modify sample



V 2.0 04.06.08 106/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

• Choose current logged user or enter your user name and the password respectively in the User box and in the Password box.

• In the Current Sample area, the current sample value and quality (GOOD, BAD, or UNCERTAIN) are displayed respectively in the Value box and in the Quality box.


In the New Sample area:

• Enter the new sample value in the Value box.

• Select a quality status from the Quality list box (GOOD, BAD, UNCERTAIN).

• Click "OK": a dialog box is displayed, which summarizes the previously entered information and notifies you that the operation has been com-pleted (successfully or not).



V 2.0 04.06.08 107/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

• Fill in the ES Request box with a user who can sign for the change.


Figure 5-13 Result of function modify sample

• Click "Close".



V 2.0 04.06.08 108/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The change and an eventually inserted comment will be stored in the com-pliance service database. The entries there can be looked up with the com-pliance service viewer. This application can be started from the manage-ment console.

Figure 5-14 The change is tracked in the compliance service

The compliance service viewer shows the changed value and the com-ment.

Figure 5-15 The compliance service viewer



V 2.0 04.06.08 109/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

The function “modify chart item” and the register settings allows setting AT markers for the actions Inserted, Modified and Deleted inside the HDD.

Figure 5-16 AT markers in the HDD

References


V 2.0 04.06.08 110/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

6 References

From the web:

http://en.wikipedia.org/wiki/Quality

From SIEMENS sources:

SIMATIC OS online help

SIMATIC ES online help

SIMATIC IT online help

Security Handbook

http://support.automation.siemens.com/WW/view/en/26462131 (English)

Service and Support Automation and Drives

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

http://en.wikipedia.org/wiki/Quality�



Abbreviations


V 2.0 04.06.08 111/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

7 Abbreviations

Abbreviations used in this manual: Table 7-1

Abbreviation Complete name

AD Active Directory AT Audit Trail BgViewer Bargraph Viewer BoM Bill of Material BPM Business Process Modeler CAB Client Application Builder CF Custom Field CFC Continuous Function Chart CIB Com Interface for BATCH CIB COM Interface for SIMATIC BATCH CP Communication Processor CS Compliance Service DB Data Base DHCP Dynamic Host Configuration Protocol DNS Domain Name Service ERP Enterprise Resource Planning ES Engineering System FAQ Frequent Asked Question FDA Food and Drug Administration HDD Historian Data Display HF Hot Fix HMI Human Machine Interface IP Internet Protocol KPI Key Performance Indicator LBM Lifebeat Monitoring MES Management Execution System MM Material Manager MUI Multilanguage User Interface ODS Operation Debugging Support OPC OLE for Process Control OS Operator Station OSM Optical Switch Module OU Organizational Unit PDefM Production Definition Manager

Abbreviations


V 2.0 04.06.08 112/112

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

Abbreviation Complete name

PLC Programmable Logical Unit PM Production Modeler PO Production Operation POM Production Order Manager PPR Product Production Rule PS Product Segment RTDE Real Time Data Engine RTDS Real Time Data Server SIT SIMATIC IT SP Service Pack SQL Structured Query Language UoM Unit of Measure UTC Coordinated Universal Time WINS Windows Internet Naming Service

simatic pcs 7 – simatic it – integration · pcs 7 / simatic it integration pack 2007 quality...

Documents