Transcription
Alarm management inSIMATIC PCS 7 –Smart Alarm HidingSIMATIC PCS 7 V9.0 iew/55699984SiemensIndustryOnlineSupport
Legal informationLegal informationUse of application examplesApplication examples illustrate the solution of automation tasks through an interaction of severalcomponents in the form of text, graphics and/or software modules. The application examples area free service by Siemens AG and/or a subsidiary of Siemens AG (“Siemens”). They are nonbinding and make no claim to completeness or functionality regarding configuration andequipment. The application examples merely offer help with typical tasks; they do not constitutecustomer-specific solutions. You yourself are responsible for the proper and safe operation of theproducts in accordance with applicable regulations and must also check the function of therespective application example and customize it for your system.Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have theapplication examples used by technically trained personnel. Any change to the applicationexamples is your responsibility. Sharing the application examples with third parties or copying theapplication examples or excerpts thereof is permitted only in combination with your own products.The application examples are not required to undergo the customary tests and quality inspectionsof a chargeable product; they may have functional and performance defects as well as errors. It isyour responsibility to use them in such a manner that any malfunctions that may occur do notresult in property damage or injury to persons. Siemens AG 2018 All rights reservedDisclaimer of liabilitySiemens shall not assume any liability, for any legal reason whatsoever, including, withoutlimitation, liability for the usability, availability, completeness and freedom from defects of theapplication examples as well as for related information, configuration and performance data andany damage caused thereby. This shall not apply in cases of mandatory liability, for exampleunder the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss oflife, bodily injury or damage to health, non-compliance with a guarantee, fraudulentnon-disclosure of a defect, or culpable breach of material contractual obligations. Claims fordamages arising from a breach of material contractual obligations shall however be limited to theforeseeable damage typical of the type of agreement, unless liability arises from intent or grossnegligence or is based on loss of life, bodily injury or damage to health. The foregoing provisionsdo not imply any change in the burden of proof to your detriment. You shall indemnify Siemensagainst existing or future claims of third parties in this connection except where Siemens ismandatorily liable.By using the application examples you acknowledge that Siemens cannot be held liable for anydamage beyond the liability provisions described.Other informationSiemens reserves the right to make changes to the application examples at any time withoutnotice. In case of discrepancies between the suggestions in the application examples and otherSiemens publications such as catalogs, the content of the other documentation shall haveprecedence.The Siemens terms of use (https://support.industry.siemens.com) shall also apply.Security informationSiemens provides products and solutions with industrial security functions that support the secureoperation of plants, systems, machines and networks.In order to protect plants, systems, machines and networks against cyber threats, it is necessaryto implement – and continuously maintain – a holistic, state-of-the-art industrial security concept.Siemens’ products and solutions constitute one element of such a concept.Customers are responsible for preventing unauthorized access to their plants, systems, machinesand networks. Such systems, machines and components should only be connected to anenterprise network or the Internet if and to the extent such a connection is necessary and onlywhen appropriate security measures (e.g. firewalls and/or network segmentation) are in place.For additional information on industrial security measures that may be implemented, please emens’ products and solutions undergo continuous development to make them more secure.Siemens strongly recommends that product updates are applied as soon as they are availableand that the latest product versions are used. Use of product versions that are no longersupported, and failure to apply the latest updates may increase customer’s exposure to cyberthreats.To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feedat: https://www.siemens.com/industrialsecurity.Smart Alarm HidingEntry ID: 55699984,V4.0,11/20182
Table of contentsTable of contentsLegal information . 21Introduction . 41.11.21.32Basics . 72.12.22.32.42.53 Siemens AG 2018 All rights reservedImportant alarm indicators . 7Suppression of alarms. 9Acknowledgment-triggered reporting (QTM) . 9Filtering of alarms . 10Analyzing alarms . 11Manual alarm hiding . 123.13.23.34Overview. 4Principle of operation. 4Components used . 6Configuration . 12Configuration in OS runtime . 13Diagram of manual alarm hiding . 14Automatic Alarm Hiding . 154.14.1.14.1.24.1.34.1.44.1.54.24.3Configuration . 15Configuration of the operating states . 16Configuration des status block "STRep" . 17Configuration of the block group . 21Configuration of the hiding matrix . 23Compiling the OS . 25Behavior in OS runtime . 27Principle of automatic alarm hiding . 335Summary of the functions . 346Appendix . 356.16.26.3Smart Alarm HidingEntry ID: 55699984,V4.0,Service and support . 35Links and literature . 36Change documentation . 3611/20183
1 Introduction1Introduction1.1OverviewWith the previous alarm suppression (Lock / Suppress) in SIMATIC PCS 7, thealarms at the process tag are suppressed. This means that messages from aprocess tag do not reach the alarm system of the PCS 7 OS and are not displayedand archived on the OS.With the Smart Alarm Hiding, alarms of a process tag can be filtered or hiddendepending on the plant state. A big advantage of this method is that the filtered andhidden alarms are still processed and archived in the alarm system of the OS.This allows a reduction of the reporting volume in process operation and betterhandling for the system operator.1.2Principle of operationThis application explains how you can more effectively implement your alarmmanagement in PCS 7 V7.0 or higher using Smart Alarm Hiding. Siemens AG 2018 All rights reservedAutomatic alarm hiding is basically controlled by status blocks in the AS that hideor show status-dependent alarms based on a hiding matrix.Technological (messaging) blocks are assigned to a status block via the new"block group" block property.There are two ways of implementing smart alarm hiding: Manual hiding and displaying of alarms Automatic hiding and displaying of alarmsThis application example shows you how you can use and configure both optionsin your project.Smart Alarm HidingEntry ID: 55699984,V4.0,11/20184
1 IntroductionFigure 1-1 Overview "Operating principle of automatic alarm hiding"OperationAnd04LogicalPlantStateSTRepState ReOB352/4In1In2In3In4OutSet PlantState1OpDi03Binary IntlockOosLiSet PlantState2OpDi03Binary 12/3OB35Out1Out2Out3OosActAS ESOB352/6MPSAQSTATE„Hiding Matrix“blockgroupplantstatePIC ReactorPIDConLContinuoGainTITDSP LiOpSP ExtLiSP IntLiSP ExtPVMV TrkOnMV TrkModLiOpAutModLiManModLiOosLiMV MeanSettliTiMV HiLimMV LoLimMV SafePIntlockRbkPV OpScaMV OpScaPV UnitMV UnitMV ChnSTCSFEnAcquierOB352/4OutOosAct Siemens AG 2018 All rights nFbk3InIntlockOosLiEmergencyOpDi03Binary 30State31OSrulesASOB352/6MVFIC FeedMS ReleaPIDConLGrpErrContinuoRdyToStaGainOosActTI ManActTD AutActSP ExtAcSP LiOpSP ExtLiSPSP ExtOuSP IntLiSP IntOuSP ExtBypassAcPVPV OutMV TrkOnMV Trk osLiMV MeanSettliTiMV HiLimMV LoLimMV SafePIntlockRbkPV OpScaMV OpScaPV UnitMV UnitMV ChnSTCSFEnAcquierfilterOB352/6MVLI ReactorMS ReleaMonAnLGrpErrAnalogmRdyToStaPV OosActManActSmoothTiAutActLagTimeSP ExtAcPV OpScaPV UnitSPSP ExtOuOosLiSP IntOuCSFBypassAcPV OutQI FeedERMonAnLDynDeadBAnalogmPhaseDeaPV SettlingSmoothTiLagTimePV OpScaPV UnitOosLiCSFmessagesOB352/4MS ReleaBypassAcPV OutPV GradOosActRuntimemessagesOB352/4MS ReleaBypassAcPV OutPV GradOosActarchivetechnologicalblocksHiding alarms manuallyManually hiding the alarms is characterized by the following features: The alarms are shown again after a defined period of time. Manually hidden alarms are acknowledged automatically. Manual alarm hiding applies to all clients of the relevant OS server. An operator message is triggered if alarms are hidden and shown manually.Hiding alarms automaticallyThe goal is to hide alarms depending on specific process or system conditions todisplay the relevant alarms.Smart Alarm HidingEntry ID: 55699984,V4.0,11/20185
1 Introduction1.3Components usedComponentNoteNoteSIMATIC PCS 7 ES/OS IPC547G W7For the PCS 7 V9.0 SP1 example projectSIMATIC PCS 7 V9.0 SP1Part of SIMATIC PCS 7 ES/OS IPC547GW7APL library V9.0 SP1Part of SIMATIC PCS 7 V9.0 SP1If the hardware is different, observe the minimum requirements for installing thesoftware components. The minimum requirements can be found in the PCS 7Readme under the following /view/109750097.This application example consists of the following components:ComponentThis document Siemens AG 2018 All rights reserved55699984 Alarm Hiding DOC PCS7V90SP1 en.pdfNoteSmart Alarm HidingEntry ID: 55699984,V4.0,11/20186
2 Basics2BasicsThe followingsection gives a short summary of the Alarm Management functionsalready available in PCS 7 V6.1.2.1Important alarm indicators Alarm line in the overview area of the OS runtime(Display of the highest priority alarm)Figure 2-1 OS alarm display in the overview area Preconfigured alarm views (e.g. new list, old list), freely definable alarm views(WinCC Alarm Control) Siemens AG 2018 All rights reservedFigure 2-2 OS alarm display Group displays in the overview areas and as part of the block iconFigure 2-3 Group display in the block icon Loop-in alarm with highlighting of the disturbed process tagFigure 2-4 Highlighting in the block iconSmart Alarm HidingEntry ID: 55699984,V4.0,11/20187
2 Basics Horn Siemens AG 2018 All rights reservedFigure -2-5 Horn configuration in WinCCExplorerSmart Alarm HidingEntry ID: 55699984,V4.0,11/20188
2 Basics2.2Suppression of alarmsThere are two ways to suppress alarms: You can suppress these directly at the technological blocks via the MsgLockinputs for inhibiting alarms of a block (depending on the program logic). You can suppress alarms of an individual process tagor part of the planthierarchy directly via the OS runtime. Siemens AG 2018 All rights reservedFigure 2-6 Blocking of alarms specific to the area and process tag2.3Acknowledgment-triggered reporting (QTM)To reduce the message volume in the system, the PCS 7 alarm blocks ALARM xprovide the process of acknowledgment-triggered reporting.It is based on the fact that after generating a coming message (signal change from0 to 1) for a signal, no further messages are generated for this signal until it hasbeen acknowledged on the OS.Smart Alarm HidingEntry ID: 55699984,V4.0,11/20189
2 Basics2.4Filtering of alarmsYou can configurethe filtering of alarms within the alarm lists. The filter criteria aremessage properties (date, time, message class, message text, etc.). Siemens AG 2018 All rights reservedFigure 2-7 Filtering and sorting of alarmsThe reason for changing the filter criteria online is the temporary focussing on acertain property, e.g. time period or event, for fault analysis.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201810
2 Basics2.5Analyzing alarmsThe hit list allows you to display statistic calculations for archived messages in themessage window.The following statistic calculations are available for messages:Note Frequency of a message number. The frequency is only increased when amessage with "Incoming" status is stored in the archive. The acumulated duration of an alarm number in seconds for the"incoming/outgoing"( /-) state, the "incoming/first acknowledgment"( /*1) state,or the "incoming/second acknowledgment"( /*2) state. The average duration of a message number, in seconds, for the"incoming/outgoing"( /-) state, the "incoming/first acknowledgment"( /*1) state,or the "incoming/second acknowledgment"( /*2) state.Only the "Acknowledgment", "System Acknowledgment" and "EmergencyAcknowledgment" states are included in the statistics calculation ofacknowledgment times. Siemens AG 2018 All rights reservedFigure 2-8 Hit-ListFigure 2-9 Configuration of the hit list in the alarm controlSmart Alarm HidingEntry ID: 55699984,V4.0,11/201811
3 Manual alarm hidingManual alarm hiding3Manual alarm hiding allows you to temporarily hide pending alarms that are notrelevant to the current state of the system.NoteThe manual hiding of alarms is OS server-oriented.If an alarm is manually hidden on an OS client, this alarm is not visible on anyclient that also accesses the associated server.3.1ConfigurationProceed as follows to configure the manual alarm hiding:1. Open the WinCC Explorer.2. Open the OS Project Editor.3. Click the "Message Display" tab. The configuration dialog "Smart Alarm Hiding"opens.4. Activate the check box for the manual hiding of alarms in the PCS 7 messagelists (see Figure 3-1). Siemens AG 2018 All rights reservedFigure 3-1 Configuration of the manual alarm hiding in the OS project editorNoteOn the server, you can also set the length of time after which a manually hiddenalarm is displayed again.NoteChanging the hide times and displaying the manual hiding button are deltaloadable.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201812
3 Manual alarm hiding3.2Configuration in OS runtimeProceed as follows to configure in OS runtime:1. Activate OS runtime.2. Open the configuration dialog of the WinCC alarm controls.3. Under the "Toolbar" tab, select "Hide message" and "Unhide message". Siemens AG 2018 All rights reservedFigure 3-2 Configuration of WinCC alarm control4. In the views of the WinCC alarm control "Message list", "Short-term archivelist" and "Long-term archive list" you can hide messages manually (light bulbsymbol).Figure 3-3 Additional button for hiding alarmsNoteAlarms that can be manually hidden from the message list are automaticallyacknowledged when hiding.After the configured hide time has expired, they are displayed again.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201813
3 Manual alarm hiding5. In the "List of hidden messages" view, you can manually display hidden alarmsagain.Figure 3-4 Additional button for showing alarmsNote3.3Alarms that you acknowledge by manually hiding appear in the old list afterdisplaying again if they did not come back.Diagram of manual alarm hidingFigure 3-5 Runtime Model1234567 Siemens AG 2018 All rights reservedAlarm hiding activeManual alarm hiding timeout activeAlarm in control server (AS)Alarm in alarm server (OS)Alarm in alarm viewsActivate alarm (coming)Activate alarm hiding manuallyActivate alarm hiding automaticallyDeactivate alarm hidingDeactivate alarm (going)Deactivate alarm (going)Smart Alarm HidingEntry ID: 55699984,V4.0,11/201814
4 Automatic Alarm Hiding4Automatic Alarm Hiding4.1ConfigurationThe following Figure 4-1 shows the main steps for the configuration of theautomatic alarm hiding.Figure 4-1 The 5 configuration steps for smart alarm hidingStep 1: Configuration of operating statesStep 2: Configuration of status block Siemens AG 2018 All rights reservedStep 3: Configuration of the block groupIncl. compile CFC anddownload the ASStep 4: Configuration of the hiding matrixStep 5: Compiling the OSSmart Alarm HidingEntry ID: 55699984,V4.0,11/2018Incl. Download OS andrestart OS15
4 Automatic Alarm Hiding4.1.1Configuration of the operating statesProcedureTo configure the operating states, proceed as follows:1. Open the component view of your project.2. Under "Master Data Library Shared Declarations", right-click on"Enumerations" and select "Insert New Object Enumeration". Siemens AG 2018 All rights reservedFigure 4-2: Definition of the enumeration in the multiproject3. Assign the name "Operating State" to the enumeration.4. Right-click on the generated "Operating State" enumeration and select "Insertnew object Value".Figure 4-3: Definition of the operating states in the multiprojectNoteIn this enumeration, you can define values from 1 to 32 for plant states.The value "0" is the default for the system status "normal". In this state, thesystem is in normal operation and no alarms are hidden.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201816
4 Automatic Alarm Hiding5. Name the created value according to an operating state.6. Repeat steps 4 and 5 until you have configured all the operating states.Figure 4-4 Example of the operating states7. Right-click on "Shared declarations" and select the "Shared Declarations Synchronize in Multiproject" command in the context menu. Siemens AG 2018 All rights reservedFigure 4-5 Synchronizing the Shared Declaration in the MultiprojectNote4.1.2In multiprojects consisting of several sub-projects, the "Enumerations" in theShared Declarations are created in the master data library and thensynchronized in the multiproject.Configuration des status block "STRep"This technological module is used to convert Boolean input signals into thecorresponding system status.ProcedureTo configure the "STRep", proceed as follows:1. Open a CFC chart of a corresponding sub-systemSmart Alarm HidingEntry ID: 55699984,V4.0,11/201817
4 Automatic Alarm Hiding2. Insert the block "STRep" from the library "PCS 7 AP Library V90" and group"Maint". Siemens AG 2018 All rights reservedFigure 4-6 Insert STRep block in the CFC chartNoteThe "STRep" block has 32 Boolean inputs "StateX". These inputs correspond tothe values of the enumerations that you configured in the first configuration step.Figure 4-7 Attribute "STRep " blockS7 m c trueS7 state rep trueS7 block group block group name StateStateStateStateStateS7 m c trueS7 enum Operating StateSTRep block12345BOOLBOOLBOOLBOOLBOOLState 32BOOLINTBOOLQSTATEQERRThe output "QState" is linked to the values of the enumeration "Operating State"by the attribute "S7 enum Operating State". In this way, the assignment andprocessing of the values / states configured in "Operating State" to the inputs ofthe "STRep" block is created.If no signal is present at any input of the "STRep" block, the system is in the"Normal" state and the "QSTATE" output is 0. In this case, no messages aretriggered.If two inputs have the same status as "1" at the same time, the parameter"QERR" is set to "1" and "QSTATE" is set to "0" because a system cannot be intwo different states at the same time.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201818
4 Automatic Alarm Hiding3. Double click on the "QSTATE" output and assign the respective enumeration"Operating State" Siemens AG 2018 All rights reservedFigure 4-8 Assignment of the enumeration "Operating State" to "QSTATE"4. Interconnect the block inputs according to the plant statesNoteIf, for example, the value 3 corresponds to the system status "Startup", thiscorresponds to the input "State3" at the "STRep" block. If the value "1" is appliedto the input "State3", this status corresponds to the system status "Startup",which is output at the output "QState" of the "STRep" block.5. Right-click on the "STRep" block and select "Object Properties" in the contextmenu.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201819
4 Automatic Alarm Hiding6. Define a block group in the properties dialog of the "STRep" block. Siemens AG 2018 All rights reservedFigure 4-9 Assignment of the "STRep" block to the corresponding block groupNoteIn the next step, you will define the technological area which the "StateRep"block forwards the operating state to this group.This means that a block "STRep" is permanently assigned to a block group. Thismakes it possible to hide block group granular alarms for certain operatingstates.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201820
4 Automatic Alarm Hiding4.1.3Configuration of the block groupA technological area consists of several technological building blocks that cangenerate alarms. In order to hide alarms for sub-systems, you must group all thetechnological components of a sub-system into a block group. This allows you tohide all alarms generated by blocks of the same block group for specific plantstates.There are 2 ways to assign technological blocks to a block group:Procedure: Option 11. Open the CFC chart containing a reportable block.2. Right-click on the message-enabled block and select "Object Properties" in thecontext menu.3. In the "Properties" dialog, define the "Block group" attribute Siemens AG 2018 All rights reservedFigure 4-10 Definition of the block groupNoteThe "Block Group" attribute is an ES (CFC) attribute. When migrating your ownblock libraries to PCS 7 V7.0, they are automatically adopted for thetechnological blocks of this library.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201821
4 Automatic Alarm HidingNoteThe block group attribute is also available in the import-export wizard. Siemens AG 2018 All rights reservedFigure 4-11 Block group attribute for import / export fileFigure 4-12 Block group attribute in the IEA editor4. Compile the CFC charts and download the AS.NoteAS change compilations and change loading is possibleSmart Alarm HidingEntry ID: 55699984,V4.0,11/201822
4 Automatic Alarm HidingProcedure: Option 21. Open the process object view of your project.2. Assign the respective block group to the corresponding technological blocks. Siemens AG 2018 All rights reservedFigure 4-13 Definition of the block group in the process object view3. Compile the CFC charts and download the AS.Note4.1.4AS change compilations and change loading is possibleConfiguration of the hiding matrixIn the process object view, you can define which messages of a block group are tobe hidden in which system status.RequirementChapters 4.1.1, 4.1.2 and 4.1.3 must be successfully gone through to configure thealarm hiding matrix in the process object view.ProcedureTo configure the hiding matrix, proceed as follows:1. Open the process object view of your project.2. Open the "Messages" tab3. Activate the filter "Filter by column" and filter by "Block group"4. Enter the name of the respective block group under "Display"Smart Alarm HidingEntry ID: 55699984,V4.0,11/201823
4 Automatic Alarm HidingFigure 4-14 Filter by block group in the process object view5. Configure the hiding matrix for the selected block group Siemens AG 2018 All rights reservedFigure 4-15 Message matrix in the process object view6. After completing all configuration steps in the ES, you compile and load theAS.7. Compile and download the OS.NoteChanging the "Hidingmask" of an existing block is delta loadable. If a newmessage-capable block with a configured "Hidingmask" is added, the alarmhiding functionality is not active for this user after a change download of the OSserver. To enable this functionality, the OS server must be reactivated.If the block group assignment for activating the alarm hiding functionalitychanges, the OS server must be reactivated after the downloading the changes.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201824
4 Automatic Alarm Hiding4.1.5Compiling the OSBased on the "message matrix" from the process object view, when you compilethe OS in alarm logging, a corresponding hide screen will be automaticallygenerated as an additional attribute for the alarms to be generated. This is usedlater in OS runtime to hide the corresponding alarms in the alarm lists. Siemens AG 2018 All rights reservedFigure 4-16 Hide screen OS alarm loggingFurthermore, the corresponding block group is automatically entered as anattribute for each message and a user-specific alarm group is generated for eachblock group. This contains all the alarms of the blocks in a block group. Theproperties of the alarm group contain the status tag of the "STRep" block.Figure 4-17 Integration of block groups, user-defined message classes and message classpropertiesSmart Alarm HidingEntry ID: 55699984,V4.0,11/201825
4 Automatic Alarm HidingFor each "STRep" block, a tag "QState" is created in the WinCC tag managementduring compilation. The value corresponds to the current system status. (Fig. 317)). In addition, there are internal tags of the text reference type, which contain thecorresponding configured system status in plain text (Figure 3-18). Siemens AG 2018 All rights reservedFigure 4-18 Tag "QSTATE" in the OS tag managementFigure 4-19 Text reference tag for configured system statusSmart Alarm HidingEntry ID: 55699984,V4.0,11/201826
4 Automatic Alarm Hiding4.2Behavior in OS runtimeAlarm hiding in OS runtimeThe following figures show the behavior of alarm hiding in OS runtime. In normaloperation, the alarms can be seen in the group displays of the overview area, inthe message line of the overview area, as well as in the "incoming alarm list"(Figure 4-20).Figure 4-20 Incoming list in plant state "normal"The " hidden list" is accordingly empty, as shown in Figure 4-21. Siemens AG 2018 All rights reservedFigure 4-21 Hidden list in the plant state "normal"In the plant state "Startup", the messages of the plant area "PLANT" for too low apressure as well as the alarm and warning messages of the KPIs are hiddenaccording to the configuration. Only the non-hidden messages that the tank levelexceeds the warning and alarm limits are displayed in the new list.Figure 4-22 New list in plant state "Startup"Smart Alarm HidingEntry ID: 55699984,V4.0,11/201827
4 Automatic Alarm HidingThe messages for exceeds the low warning and alarm limits for pressure and KPIsare also not displayed in the overview screen. Only the unsuppressed messagesthat the tank is full are displayed. Siemens AG 2018 All rights reservedFigure 4-23 Overview figure in the "Startup" plant stateThe messages for exceeds the low warning and alarm limits in the tank are filteredand moved to the "List of hidden messages" as shown in Figure 4-24.Figure 4-24 List of hidden messages in the plant state "Startup"In the other plant area, no alarms are hidden by the "Startup". These will continueto be contained in the message line of the overview area and the incoming listNoteAlarms that are automatically hidden will be acknowledged and reappear in theold list after re-appearing if they did not come back.Smart Alarm HidingEntry ID: 55699984,V4.0,11/201828
4 Automatic Alarm HidingRuntime diagram for automatic alarm hidingThe runtime model represents the alarm behavior and the display of alarms inprocess mode with activated and deactivated alarm hiding.Figure 4-25 Runtime Model123456789101112Alarm hiding activeAlarm in control server (AS)Alarm in alarm server (OS)Alarm in alarm viewsActivate alarm hidingActivate alarm (coming) Siemens AG 2018 All rights reservedDeactivate alarm (going)Deactivate alarm hidingRange 1-5 shows that when alarm hiding is activated, the messages generated inthe AS a
With the previous alarm suppression (Lock / Suppress) in SIMATIC PCS 7, the alarms at the process tag are suppressed. This means that messages from a process tag do not reach the alarm system of the PCS 7 OS and are not displayed and archived on the OS. With the Smart Alarm Hiding, alarms of a process tag can be filtered or hidden
