Transcription

1 Acknowledgement of WinCC Messages with forced comments WinCC V7 Siemens Industry Online Support

2 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 safe 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 the Siemens AG. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens products and solutions only form one element of such a concept. Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks. Systems, machines and components should only be connected to the enterprise network or the internet if and to the extent necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place. Additionally, Siemens guidance on appropriate security measures should be taken into account. For more information about industrial security, please visit Siemens products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer s exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under Entry-ID: , V1.1, 08/2017 2

3 Table of contents Table of contents Warranty and liability Task definition Solution Overview of the general solution Description of the core functionality Hardware and software components used Functional Mechanisms of this Application Message system Changing the predefined reason of the forced comment Functions and picture scripts C functions C actions Picture scripts ForcedComment.h header file Installation Startup of the Application Startup of the application example Integration of the functionality in a customer project User and authorization Creating tags Configuring Alarm Logging Creating messages Copying of pictures and renaming graphics and pictures Copying of header files, functions and actions Editing header file Adjusting Alarm Controls Operating the Application Description of the operator screens Description of important buttons Operating scenarios Operating the messages that are acknowledged with forced comment Operating the default messages Further Notes, Tips & Tricks, etc Literature History Entry-ID: , V1.1, 08/2017 3

4 1 Task definition 1 Task definition Introduction In the pharmaceutical branch and the food and beverage sector the documentation of operator actions is becoming increasingly important. The documentation of production processes is to ensure that all operator actions are comprehensible. For these operator actions an acknowledgement (electronic signature and/or comment) by the operator may be required. Overview of the automation task The figure below provides an overview of the automation task. Figure 1-1 Automation process SCADA system Warning or error Message generation Message acknowledgement + Documentation Achiving Description of the automation task The aim is that the operator is consciously aware of the message and acknowledges it through the mandatory acknowledgement and does not just click it away. The operator actions are furthermore traceable through the archiving. Entry-ID: , V1.1, 08/2017 4

5 2 Solution 2 Solution 2.1 Overview of the general solution Schematic layout The following figure gives a schematic overview of the most important components of the solution: For this application example you need a PC with the installation of the following software: SIMATIC WinCC and SIMATIC Logon. Figure 2-1 SIMATIC Logon WinCC WinCC Script (application example) Topics not covered by this application This application does not include a description of the installation of SIMATIC WinCC of the installation of SIMATIC Logon Basic knowledge of these topics is assumed. Required knowledge Basic knowledge of SIMATIC WinCC and of the Microsoft Windows operating system is assumed. Entry-ID: , V1.1, 08/2017 5

6 2 Solution 2.2 Description of the core functionality What does the application example perform? The application example expands the message function of WinCC by an additional acknowledgement function with comment. These additional comments are mandatory, they have to be used. It is not possible to acknowledge the messages with out a comment. Not all messages have to be acknowledged with comment. They are defined through a certain message class. If a message is acknowledged with mandatory comment, an additional dialog (WinCC picture window) appears first. In this dialog box, the comment is assigned. Through an additionally generated operator message, the comment is stored in the message archive. The correlation between message and operator message can be made through date, time and message text. User and comment are also stored in the operator message. Through this operator message the following is comprehensible: What user, acknowledged this message with forced comments at what time. Overview and description of the user interface The application example contains two screens, the messages overview and the operating messages. In the message overview screen all messages are displayed in two different Alarm Control screens. It is distinguished between mandatory comments and default messages. In the Operating messages screen, mandatory messages can be created (with a simulation) and they can be acknowledged in Alarm Control. Entry-ID: , V1.1, 08/2017 6

7 2 Solution Principle of the core functionality Figure 2-2 Message pending Message acknowledged with comment Operating message is archived Table 2-1 Advantages of this solution Action Note 1. Message is pending A message that has to be acknowledged with a comment is pending. 2. Acknowledging message with a comment Acknowledging the message creates an operator message with the acknowledged comment. 3. Archiving operator message Operator message with user name and comment is archived. The solution presented in this document offers the following advantages: Increased security through comprehensibility of the acknowledgements with operator messages. Better documentation through the automatic comment process in WinCC. 2.3 Hardware and software components used The application document was generated using the following components: Entry-ID: , V1.1, 08/2017 7

8 2 Solution Hardware components Table 2-2 Component Qty. MLFB / order number Note Industrial PC for WinCC 1 For example, Siemens IPC Standard software components The application example was tested with the Windows 10 operating system. Table 2-3 Component Qty. MLFB / order number Note SIMATIC WinCC V7.4 SP1 Update 1 1 6AV6381-2BM07-4AX0 SIMATIC Logon Version Sample files and projects The following list includes all files and projects used in this example. Table 2-4 Component ForcedComment_Demo_WinCC.zip ForcedComment_doku_en.pdf Note This zip file contains the sample project and the user-specific buttons. This document describes the sample project. Entry-ID: , V1.1, 08/2017 8

9 3 Functional Mechanisms of this Application 3 Functional Mechanisms of this Application Figure 3-1 Message pending Message is to be acknowledged. yes no no User has authorization for acknowledgement yes of forced comment in message class? no Message acknowledged without comment yes Comment dialog for acknowledgement is opened Comment is assigned no yes Message acknowledged w/ith comment Operator message for acknowledgement is created Acknowledged message and operator message are located in archive 3.1 Message system Messages classes and messages types The message classes and message types determine numerous basic settings for the messages. There are two additional message classes and message types in the message system of the application example. Entry-ID: , V1.1, 08/2017 9

10 3 Functional Mechanisms of this Application Table 3-1 Assignment of the new message classes Messages Message classes Message type Forced comment message Forced comment ForcedCommentType Operator message ForcedCommentAck ForcedCommentTypeAck Forced comment message The messages that are acknowledged with a forced comment are assigned to the ForcedComment class and the ForcedCommentType type. The number of this message class and this message type is also used in the ForcedComment.h for ForcedCommentClass and ForcedCommentType. Operator message The operator message that is generated after an acknowledgement with a forced comment, is assigned in the ForcedCommentAck class and the ForcedCommentTypeAck type. To ensure that the comment transmitted during the acknowledgement can not be changed afterwards, the Comment assigned to unique user property has to be set in the ForcedCommentAck message type. Among other things, the operator message contains the following information: computer name operator time (date and time) message number of the just acknowledged message message text of the just acknowledged message Figure 3-2 Operator message Message blocks The information of the messages is specified in the message blocks. System blocks These blocks enable the display of predefined information. System blocks used: date time message duration status acknowledgement number class type Entry-ID: , V1.1, 08/

11 3 Functional Mechanisms of this Application comment info text User text blocks These blocks enable the display of freely defined information. User text blocks used: Table 3-2 User text blocks User text blocks Name Character length Text block 1 Source 32 Text block 2 Area 32 Text block 3 Event 255 Text block 4 Batch name 32 Text block 5 Operation 255 Text block 6 Message text 255 Text block 7 Forced comment 255 This is what the content of the operator message looks like: Table 3-3 Content of the operator message User text blocks Name Text block 1 Text block 2 Content Text block Text block 4 Batch Text block Text block 6 Message Text block 7 Process value blocks These blocks enable the display of values from tags. Process value blocks used Entry-ID: , V1.1, 08/

12 3 Functional Mechanisms of this Application Table 3-3 Process value blocks Process value block Name Content Process value block 1 Process value block 1 Batch name / batch ID Process value block 4 Process value block 4 Old value Process value block 5 Process value block 5 New value Process value block 6 Process value block 6 Action Process value block 7 Process value block 7 Operator Process value block 8 Process value block 8 Unit Process value block 9 Process value block 9 Area Process value block 10 Process value block 10 Source In the Working with WinCC manual you will find more information on the message system issue. WinCC ->Setting up a message system 3.2 Changing the predefined reason of the forced comment The forced comment consists of a freely worded comment and/or a predefined reason from a list. This list of predefined reasons can be found in the ForcedCommentAlarmPicture picture window. Figure 6-4 Screen window Table 3-4 No. Action Screen 1. Open the ForcedCommentAlarmPicture picture in WinCC > Graphics Designer. 2. Double click the Reasons list box. 3. Select Properties > Miscellaneous. Under Miscellaneous there are the attributes Selected box and Selected text. Enter the field number in the list box in the Selected box attribute and assign the text to this field number under the Selected text attribute. Entry-ID: , V1.1, 08/

13 3 Functional Mechanisms of this Application 3.3 Functions and picture scripts In the scripts, functions from the WinCC option "WinCC Open Development Kit" (ODK) are used C functions StartGlobalScriptMsgService.fct The StartGlobalScriptMsgService.fct function is used for the declaration of global tags. In addition it starts a message service (MsgService) with the respective filter settings in order to only process messages that can be acknowledged with a comment. The ID of this MsgService is saved in a global tag so that it can be used by other functions. GlobalScriptMsgServiceCallback.fct C actions This function is at least called once when MSRTEnumMsgRTData is called in the global CountForcedCommentAlarms action. The number of messages that have to be acknowledged with a comment are calculated and written in a tag. The determined number of messages is displayed in the toolbar of the pictures. CountForcedCommentAlarms.pas This global action cyclically calls (default cycle: 2 seconds) the MSRTEnumMsgRTData ODK function in order to count the messages that are acknowledged with a comment. If no MsgService is started the StartGlobalScriptMsgService function is called. ForcedCommentShowStartPicture.pas If there is no operation for 5 minutes, the user is automatically logged off. Through this global action, subsequently, a change of picture to the start screen is executed. This prevents non-authorized persons from making changes Picture scripts WinCC Alarm Control.OnToolbarButtonClicked This script is configured on the OnToolbarButtonClicked event of the WinCC Alarm Control. When clicking the user-defined button, the ID of the button is transferred to the script in the IId parameter. At the beginning of the script it is checked whether this ID corresponds with the ForcedCommentButtonID parameter in the ForcedComment.h file. If the ID matches, the data of the selected message is read. The picture window with the forced comment dialog and the message data is displayed. Entry-ID: , V1.1, 08/

14 3 Functional Mechanisms of this Application UserComment.OnPropertyChanged This script is configured on the Output/input-> Input value -> Changes event of the user comment field in the forced comment dialog. If you have entered a user comment or a predefined reason, then the OK button is released for operation. Reasons.OnPropertyChanged ButtonQuit.OnClick This script is configured on the Other -> Selected field -> Changes event of the field for selecting a predefined reason in the forced comment dialog. If you have entered a user comment or a predefined reason, then the OK button is released for operation. This script is configured on the Mouse click event of the OK button. When the OK button is clicked, it is checked whether the user comment and/or a predefined reason was selected. If this is the case, the message is acknowledged and the user comment and/or selected reason is written in the comment of the message. After successful acknowledgement an operator message is created that contains the user and the message number and the message text of the just acknowledged message, among other things ForcedComment.h header file To be able to adjust the functionality to the other projects in the simplest possible way, certain parameters such as: message classes, message type, ID of the button in Alarm Control message text name of picture window message number of the operator message date and time format for the comment the name of the WinCC Alarm Control that is used for the forced comments position of the message block a character to determine whether a predefined comment was selected have to be defined in the header file. If you integrate the forced comments function into your project, it is necessary to adjust the parameters. Entry-ID: , V1.1, 08/

15 4 Installation 4 Installation For this application example you need a PC with the installation of the following software: SIMATIC WinCC and SIMATIC Logon. Software installation Table 4-1 No. Action Comment 1 Install the SIMATIC WinCC V7.4 SP1 and the option SIMATIC Logon 2 Install the Update 1 for SIMATIC WinCC V7.4 SP1 Installing the application software Table 4-2 No. Action Screen 1 Unzip the ForcedComment_Demo_WinCC.zip file 2 The file contains 2 folders: ForcedComment_Demo_WinCC and Alarm Control. The ForcedComment_Demo_WinCC file contains the demo project. The Alarm Control folder contains the files for the user-defined buttons. The files: IconsDisabledEx.png and IconsNormalEx.png. 3 Copy the files for the user-specific buttons of the toolbar of Alarm Control into the Common Files\Siemens\bin\CCAxControlSkins \AlarmControl\ToolBar folder. If the path does not exist, it is mandatory to create it. Entry-ID: , V1.1, 08/

16 5 Startup of the Application 5 Startup of the Application 5.1 Startup of the application example Table 5-1 No. Action Screen 1 Unzip the zip file and start the application example by double clicking the ForcedComment_Demo_WinCC.mcp file. The file is located in the ForcedComment_Demo_WinCC folder. 2 WinCC is opening and the Server not available request appears, click Start server locally. 3 Click the right mouse button in WinCC on Computer and select the Properties from the displayed dialog. With pushing the button Use Local Computer Name the local computer name is overtaken in the WinCC project. Entry-ID: , V1.1, 08/

17 5 Startup of the Application No. Action Screen 4 Close the WinCC Explorer via the "Exit" button. 5 Open the Computer Management via Start > Run > compmgmt.msc. Create the Operator-Group group. 7 Create the Operator user. Assign the user to the Operator-Group group. Entry-ID: , V1.1, 08/

18 5 Startup of the Application No. Action Screen 8 Restart the application example via double click and click the Activate button. Runtime is started. Note: In the application example, the Operator-Group group is created in WinCC. SIMATIC Logon is enabled. Additional settings for SIMATIC Logon have to be made in the operating system. Make the settings, as described in the manual. SIMATIC Logon > Installation > How to make the required settings in the operating system It is also possible to use the application example without SIMATIC Logon. To do this, remove the activation in the WinCC Explorer/UserAdministrator. The password of the Operator user is operator. 5.2 Integration of the functionality in a customer project User and authorization Table 5-2 No. Action 1. Copy the graphics for the user-defined buttons. See Table 4.2 No 3_Installation_der_Applikationssoftwa 2. Create the Operator group and the Operator user in the computer management. This user is necessary for the SIMATIC Logon. See Table 5.1 No 6 and Create the Operator group in the User Administrator editor in WinCC. 4. Create the Quit forced Comment authorization and allow the release for the Operator group Creating tags Table 5-3 No. Action 1. In the tag management create the ForcedComment group in the internal tag folder. Proceed as follows: Right click on Internal tags and select New group from the menu. Assign the ForcedComment group name in the dialog that follows and confirm it with OK. 2. Create the following tags in this group: Proceed as follows: Right click on ForcedComment group. Enter in the rows of the accompanying table the following tags with its corresponding data type. Entry-ID: , V1.1, 08/

19 5 Startup of the Application Table 5-4 Tags No. Tag names Data type Note 3. Alarm Count Unsigned 32-bit value 4. ForcedCommentTrigger01 Binary tag Only for test purposes, can later be deleted 5. ForcedCommentTrigger02 Binary tag Only for test purposes, can later be deleted 6. ForcedCommentTrigger03 Binary tag Only for test purposes, can later be deleted 7. ForcedCommentTrigger04 Binary tag Only for test purposes, can later be deleted 8. ForcedCommentTrigger05 Binary tag Only for test purposes, can later be deleted 9. OtherAlarmTrigger01 Binary tag Only for test purposes, can later be deleted 10. OtherAlarmTrigger02 Binary tag Only for test purposes, can later be deleted 11. OtherAlarmTrigger03 Binary tag Only for test purposes, can later be deleted Configuring Alarm Logging Messages classes and messages types Table 5-5 No. Action 1. Open the Alarm Logging in the WinCC Configuration Studio. Select the Messages node in the tree structure on the top and open the context menu with right mouse click. 2. Select the entry New message class and enter the name ForcedComment 3. Create another new message class with the name ForcedCommentQuit in the same way. 4. Configure a new message type for the ForcedComment message class. Open the context menu via right mouse click. 5. Select the entry New message type and enter the name ForcedCommentType. 6. Select the new message type ForcedCommentType. 7. Activate the properties Acknowledement came in and Unique user in the properties on the right hand side under Acknowledgement Theory. 8. Create a new message type named ForcedCommentTypeQuit for the ForcedCommentQuit message class in the same way. 9. Select the ForcedCommentTypeQuit message type. 10. Activate the properties Without status went out and Unique user under Acknowledgement Theory. 11. Write down the number of the forced comment message class and the ForcedCommentType message type. You will need it later in the header file. User text blocks and system blocks Entry-ID: , V1.1, 08/

20 5 Startup of the Application Table 5-6 No. Action 1. Select User text blocks below Message blocks in the tree structure and change the names and the character lengths in accordance with Table 3.2 User text blocks. If you do not want to create the message text under number 6, write down the message texts. You will need it later in the header file. 2. Add the user name system block under Message blocks > System blocks Creating messages Creating forced comment messages Table 5-7 No. Action 1. Select the ForcedCommentType message type in the ForcedComment message class in the tree structure. 2. Insert a new message number at the end of the table. 3. Select the message number and activate the properties Single acknowledgement and Archived in the properties on the right hand side under Parameter. 4. Select the ForcedCommentTrigger01 tag for the Message tag. 5. Enter the texts from Table 3.3 "Content of the operator message"_alarmmeldungen in the user text blocks on the right hand side. Enter 1. Message with forced comment for the message text. 6. Create four more messages according to this procedure. (Only for test purposes, the messages can later be deleted.) Alarm messages Table 5-8 No. Action 1. Select the Alarm message type in the Error message class in the tree structure. 2. Insert a new message in the accompanying table and add the OtherAlarmTrigger01 tag for the Message tag. 3. Select the new message and activate the properties Single acknowledgement and Archived in the properties on the right hand side. 4. Enter the texts from Table 3.3 "Content of the operator message" in the user text blocks on the right hand side. Assign 1. Message without forced comment for the message text. 5. Create two more messages according to this procedure. For the two messages, assign the Warning type once and once the Failure type. (Only for test purposes, the messages can later be deleted.) Entry-ID: , V1.1, 08/

21 5 Startup of the Application Creating operator message Table 5-9 No. Action 1. Select the ForcedCommentTypeQuit message type below the ForcedCommentQuit message class in the tree structure. 2. Insert the message number 1000 in the accompanying table. If you do not want to create this message under number 1000, write down the number. You will need it later in the header file. 3. Select the message and activate the property Archived in the properties on the right hand side. 4. Enter the texts from Table 3.3 "Content of the operator message" in the user text blocks on the right hand side. 5. The configuration is saved automatically in the WinCC Configuration Studio Copying of pictures and renaming graphics and pictures Table 5-10 No. Action 1. Copy the pictures Start.pdl ForcedCommentControl_integrated.pdl, ForcedCommentAlarmPicture.pdl AlarmPicture_integrated.pdl from the GraCS directory of the demo project into the GraCS directory of your project. 2. Rename the ForcedCommentControl_integrated.pdl pictures to ForcedCommentControl.pdl and AlarmPicture_integrated.pdl to AlarmPicture.pdl. 3. Copy the *.bmp files from the GraCS directory of the demo project into the GraCS directory of your project. Entry-ID: , V1.1, 08/

22 5 Startup of the Application Copying of header files, functions and actions Table 5-11 No. Action 1. Copy the files ForcedComment.h, GlobalScriptMsgServiceCallback.fct and StartGlobalScriptMsgServiceCallback.fct from the Library directory of the demo project into the Library directory of your project. 2. Copy the files CountForcedCommentAlarms.pas ForcedCommentShowStartPicture.pas from the PAS directory of the demo project into the PAS directory of your project Editing header file AP_PBIB.H Table 5-12 No. Action 1. Open the Global Script C Editor in your WinCC project. 2. Open the Apdefap.h header file via File > Open. The header file is located in the Library directory of your project and has the file ending.h. 3. Add the #include ForcedComment.h line in front of the #include AP_PBIB.H line. 4. Save the changes, close the file and execute the Generate Header function via the toolbar. ForcedComment.h Table 5-13 No. Action 1. Adjust the parameters to your project in the ForcedComment.h file. Only change the values at the end of each line, not the names in front of it. Otherwise the functionality cannot be guaranteed. 2. Adjust the parameters ForcedCommentClass, ForcedCommentType and ForcedCommentMessageNumber to your project. Open the ForcedComment header file via File > Open and carry out the changes. The header file is located in the Library directory of your project and has the file ending.h. 3. Save the changes, close the file and execute the Generate Header function via the toolbar. 4. Close the Global Script C Editor Entry-ID: , V1.1, 08/

23 5 Startup of the Application Adjusting Alarm Controls Alarm Controls in the AlarmPicture.pdl file Tabelle 5-14 Nr Aktion 1. Open the AlarmPicture.pdl picture in the WinCC Graphics Designer. 2. Select the top WinCC AlarmControl and open the configuration dialog by double clicking it. 3. Open the Message lists tab. 4. Open the selections under Selections > Edit. 5. New creates a new selections with the settings: Criterion = class, Operand = same and Setting = forced comment 6. Close the dialog with "OK". 7. New creates a new selections with the settings: Criterion = class, Operand = same and Setting = ForcedCommentAck. 8. Enable the two selection criteria with the tick and close the dialog with OK. 9. Select the bottom WinCC AlarmControl and open the configuration dialog by double clicking it. 10. Open the Message lists tab. 11. Open the selections under Selections > Edit. 12. New creates a new selections with the settings: Criterion = class, Operand = same and Setting = (Select all message classes without forced comment and forced comment acknowledgement) 13. Enable the two selection criteria with the tick and close the dialog with OK. Alarm Controls in the ForcedCommentControl.pdl file Table 5-15 No. Action 1. Open the ForcedCommentControl.pdl picture in the WinCC Graphics Designer. 2. Select the WinCC AlarmControl and open the configuration dialog by double clicking it. 3. Open the Message lists tab. 4. Open the selections under Selections > Edit. 5. Create a new selection with the New button, with the settings: Name = ForcedCommentControl, First line: Criterion = class, Operand = same and setting = forced comment Second line: Criterion = mode, Operand = same and setting = came in or went out or acknowledged (emergency) Entry-ID: , V1.1, 08/

24 5 Startup of the Application No. Action 6. Enable the two selection criteria with the tick and close the dialog with OK. 7. Here, select the Toolbar tab. Assign the Quit forced Comment authorization for the userdefined buttons. 8. Save the two screens and exit the WinCC Graphics Designer. Start WinCC Runtime and test your configuration. Once the test has been carried out successfully, the test tags and test messages can be deleted. Now create the desired forced comment messages. Entry-ID: , V1.1, 08/

25 6 Operating the Application 6 Operating the Application 6.1 Description of the operator screens The application example contains two screens, the most important message overview (start screen) and operating messages. The figure Figure 6-1 Start screen and message overview displays the start screen. In the toolbar of the start screen, the number of the unacknowledged messages with forced comments, the user name and the computer name is displayed. The user login is carried out with the help of the Login button. A login dialog is opened in which you enter user name and password. When clicking the Messages overview and Operating messages button, the respective screen will appear. With the help of flag icons, the selected language is changed. With the red button, Runtime is ended. For this purpose the login of the Operator user is mandatory. On the right side of the screen you trigger default messages and messages that have to be acknowledged with forced comment via the + button. With the - buttons next to the + buttons, messages are set to the went out mode. These objects described so far, are also located in the Operating messages screen. There are two WinCC Alarm Controls under the toolbar. In the top one, all messages that are to be acknowledged with forced comment are displayed. An acknowledgement of the messages is not possible via this Alarm Control. In the bottom one, all other messages are displayed that are not to be acknowledged with forced comment. These messages are acknowledged via this Alarm Control. Select the message to be acknowledged and click the Single acknowledgement button. Display the archived messages in the two Alarm Controls via the Long-term archive list button. If you push the Operator messages button or click the output field, which displays the number of unacknowledged messages with forced comments, you go to the Operating messages screen. Entry-ID: , V1.1, 08/

26 6 Operating the Application Figure 6-1 Start screen and message overview Entry-ID: , V1.1, 08/

27 6 Operating the Application The Operating messages screen (Figure 6-2 Operating messages) contains a WinCC Alarm Control that only displays unacknowledged messages that are to be acknowledged with forced comment. Acknowledge the selected message via the Single acknowledgement with comment button. This function requires a login of the Operator user. Below, the forced comment input (screen window) is displayed. In Figure 6-3 Operating messages with screen window the Operating messages screen, the screen is displayed with this screen window. Figure 6-2 Operating messages Entry-ID: , V1.1, 08/

28 6 Operating the Application Figure 6-3 Operating messages with screen window You can enter the forced comment in the screen window. The screen window contains security information (time stamp, message number, status and message text) for the selected message. There is an input field for a user comment that can be freely defined under the message text and a selection list with predefined reasons. You have the option to enter a user comment and also to select a predefined reason. The respective content becomes the forced comment. If you are using both options, the forced comment is made up of both contents. The OK is only enabled once you have entered and/or selected a comment. Via the Cancel button the whole process is stopped. If Runtime is not used within the next 5 minutes, the user is logged off. Logging off the user, also automatically displays the messages overview screen. These two measures prevent non-authorized people from executing functions in the absence of the authorized user. Entry-ID: , V1.1, 08/

29 6 Operating the Application Figure 6-4 Screen window 6.2 Description of important buttons Table 6-1 Description of important buttons Button Significance Message receives the came in status Message receives the went out status WinCC Runtime is ended, for this purpose you will have to have logged in with your user name. Go to the Messages overview screen Go to the Operating messages screen Displays the login dialog Changing the language German/English Message acknowledgement The Single acknowledgement button is in the lower Alarm Control of the Messages overview screen. Entry-ID: , V1.1, 08/

30 6 Operating the Application Button Significance Message acknowledgement The Single acknowledgement with comment button is in the Alarm Control of the Operating messages screen. Displays the archive The Long-term archive list button is in the top and bottom Alarm Control of the Messages overview screen. Confirms the acknowledgement Accepting the comment Closes the screen window, Creates the archive message The button is in the screen window in the Operating messages screen. Cancels the acknowledgement. The button is in the screen window in the Operating messages screen. 6.3 Operating scenarios Operating the messages that are acknowledged with forced comment Table 6-2 No. Action Screen 1. Click the + button behind number 4 in the Messages overview screen. Entry-ID: , V1.1, 08/

31 6 Operating the Application 2. Go to the Operating messages screen via the Operating messages button. Click the Login button and enter Operator as user name in the login screen. As password enter the password that was assigned for this user. 3. Select the message and click the Single acknowledgement with forced comment button. 4. The screen window for entering the forced comment opens up. Here it is mandatory to enter a freely formulated comment and/or a predefined reason from the list. Subsequently, click the "OK" button. Changing the predefined reasons of the forced comment Entry-ID: , V1.1, 08/

32 6 Operating the Application 5. By clicking the Messages overview button you go to the Messages overview screen. In the top Alarm Control click the Long-time archive list button. The archived messages are displayed, among them also the operating message with message number Operating the default messages Table 6-3 No. Action Screen 1 Click the + button behind number 1 in the Messages overview screen. 2 Select the message created in the bottom Alarm Control and click the Single acknowledgement button. The default message has been acknowledged. Entry-ID: , V1.1, 08/

33 7 Further Notes, Tips & Tricks, etc. 7 Further Notes, Tips & Tricks, etc. For the correct functionality it is absolutely mandatory that the time stamps of the messages contain milliseconds! 8 Literature Internet Links This list is by no means complete and only presents a selection of suitable information. Table 8-1 Topic \1\ Reference to this document \2\ Siemens I IA/DT Customer Support Title \3\ Manual SIMATIC WinCC Working with WinCC \4\ Manual SIMATIC Logon \5\ FAQ WinCC Getting Started \4\ FAQ What support does Siemens AG provide to fulfill the FDA guidelines when using WinCC? \5\ FAQ How can you trigger an additional operator message that contains the message text of the acknowledged message when acknowledging a message? \6\ FAQ How can you create user-defined operator messages in WinCC? 9 History Table 9-1 Version Date Modification V First issue V Adaption to WinCC V7.4 SP1 Upd1 Entry-ID: , V1.1, 08/