wonderware finland solutions for alarm management in power...
TRANSCRIPT
Solutions for Power Industry
Summary
Business Value
Wonderware Finland solutions for alarm management in power industry extend the Wonderware Alarm System with new functions, features and capabilities. Improved handling of alarms and events greatly increases the performance, capabilities and reliability of data processing in power and energy applications.
The ready set of products enables faster, more reliable and better performance alarm/event processing for power industry applications running in Wonderware System Platform environment. There are software tools offered for:
• Alarm/event configuration,filteringand archiving
• Avoiding alarm loss in time critical applications
• Secure remote transfer of alarm/event data
• Integration with external alarm systems
Wonderware Finland solutions for alarm management in power industryNeW SoluTIoNS exTeNd WoNderWAre AlArm SySTem WITh more FuNcTIoNAlITy Wonderware Finland solutions for alarm management in power industry are built to extend the today existing Wonderware standard alarm functionality with new features, still using thestandardWonderwareAlarmSystem.Newfeaturesincludeadvancedalarmfiltering,accuratealarmtimestampsfromfielddevices(PLCs),nolossofshorttimeandfluctuatingalarms,supportformimicalarms,possibilitiestouseandmodifytheuserdefinedfieldsandeventpriorityfields,loggingandarchivingalarms/eventstodifferentdatabases,reductionofalarms,integrationwithotheralarmenginesoftware(UReason),andmanyother.
The Wonderware modules for Power Industry supplied by Wonderware Finland, are developed together with the leading global power/energy companies to meet the functional requirements in power industry. The Wonderware modules for Power Industry complete Wonderware standard software to make it more optimal for power/energy applications.
AlArm GATeWAyTarget of the product: extend the Wonderware standard alarm functionality with new features, still using the standardWonderwareAlarmSystem,byprovidingthehighlyflexibleconfigurablealarm/eventgatewaysolutionforWonderware System Plaform environment.
Main benefits reached with the product: Avoids alarm loss and duplicated alarms in high loaded systems, enablesthefilteringofalarms/events,suportsthealarm/eventcustomattributesandcustomizedeventpriorities,supports mimic alarm windows and connection to ureason Alarm management system.
Typical applications: Largepowergenerationandothersystemswherecustomizedprocessingofalarms/eventsisrequired.
The Alarm Gateway Object(AlarmGateway)isabasiccomponentofWonderwareFinlandAlarm Extension Pack Standard EditionandprovidesfunctionalitytocreateseparateconfigurableAlarmProviderforalarmscomingfromWonderware Application Server and/or other Alarm Providers compatible with Wonderware Alarm System. In case included in Wonderware Finland Alarm Extension Pack UReason Edition, the Alarm Gateway object provides also the functionality to send/receive alarms to/from Wonderware alarming system from/to UReason Alarm Management system. The Alarm Gateway object is developed by using Wonderware distributed Alarm Toolkit.
The general schema of Alarm Gateway is following:
Alarm Gateway
Alarm Providers:•Application
Server•InTouch•other
AlarmConsumers(AlarmClient
control, InTouchAlarmViewerctrl,
other)
Alarmconsumer
AlarmProvider
Alarm Gateway application examplesUsing Alarm Gateway to avoid alarm loss in high loaded systems Wonderware Application Server historical alarms and events are stored in a circular buffer, where the oldest entries are discarded to make the space for new ones, so in case there are generated a lot of events then important alarms can be lost. By using the Alarm Gateway, it is possible to store all important alarms in separate. Alarm Gateway buffer - that can be done by querying alarms/events only with priorities e.g. from 1 to 998. Alarm Gateway avoids alarm lossinhighloadedsystems,byusingownalarmbufferandfilteringEventPriorities:AlarmGatewayalarmbuffercancontainabout6000-7000alarms.Thetotalnumberofstoredalarmsdependsonsizeofalarms:
Functions for filtering, custom properties,mimic alarms, etc.
AlarmGateway
StandardAlarmClient
Engine
Area
Object
Platform 1AlmBuf
AlmBuf
AlarmBuffer
AlarmBuffer
Using Alarm Gateway to change the event priorityWonderwareApplicationServeralarmingsystemdoesnotprovidethepossibilitytoconfigureeventpriority-allevents have built-in priority 999. By using the Alarm Gateway, it is possible to change the event priority by using the setPriority custom attribute.
AlArm dB loGGerTarget of the product:Enablethestoringofalarms/eventscomingfromWonderwareAlarmProviders(ApplicationServer,InTouch)toseparateSQLdatabase.
Main benefits reached with the product: Several Alarm dB logger objects can run on same computer, so needed functionality is provided for applications where it is necessary to distribute alarms/events to several databases on same computer - as standard Wonderware AlarmdBlogger does not support such possibility.
Typical applications:Largepowergenerationandothersystemswherecustomizedprocessingofalarms/eventsisrequired.
The Alarm DB Logger Object(AlarmDBLogger)isacomponentofWonderwareFinlandAlarm Extension Pack andprovidesfunctionalitytostorealarms/eventsintoSQLdatabaseforalarms/eventscomingfromWonderwareApplication Server and/or other Alarm Providers compatible with Wonderware Alarm System. The Alarm dB logger object is developed by using Wonderware distributed Alarm Toolkit.
The general schema of Alarm dB logger is following:
Alarm DB Logger
Alarm Providers:•Application
Server•InTouch•other
SQL Server•Wonderware
alarm/event database
•custom database
Alarmconsumer
SQLclient
AlArm dB coNVerTerTarget of the product: ProvidethefunctionalityofcustomizableconvertingofWonderwareorcustomalarm/eventdatabasestounlimitedsizeexternallifetimestoragedatabases.Main benefits reached with the product: The limited storage alarm/event data can be archived to external archivingstations,bybypassingfirewallsandsatisfyingexternallifetimedatastoragerequirements.Typical applications: Largepowergenerationandothersystemswherecustomizedprocessingofalarms/eventsisrequired.The Alarm DB Converter Object(AlarmDBConverter)isacomponentofWonderwareFinlandAlarm Extension Pack and can be used for archiving alarms and events to external archiving stations. The source and destination databases canbeWonderwarestandardalarm/eventdatabasesorcustomSQLdatabasesusedforalarm/eventstorage.The general schema of Alarm dB converter is following:
Example of using Alarm DB Converter in large power generation application Thetargetistoenablelong-termlifetimestorage(forseveralyears)ofalarms/eventsgeneratedbypowergeneration equipment.The power generation equipment is divided in several groups and all generated alarms/events are received in Wonderware InTouch applications, acting as Alarm Providers of initial alarm/event data for the rest of system. Alarms/eventsatfirstarefilteredandthentemporarilystoredincustomalarmdatabasebyAlarm DB Converter before being pushed by specially developed Alarm ArchiverObjectthroughafirewalltothefinaldestinationinthearchivingstation,wherealarm/eventdataarestoredforlifetime.Thedatainthefinalstoragearesplitintoseveraldatabasestoincreasetheperformanceandkeeptheoptimalsizeofdatabases.AswellspecialAlarm Client .NeT application is developed for accessing the external archiving station databases.Such approach allows to solve possible Wonderware Alarm System capacity problems and store very hugevolumes of alarm/event information:
Alarm dBconverter 1
Alarm Achiver 1
Alarm dBconverter 2
Alarm Achiver 2
Alarm client
Alarm dBconverter 3
Alarm Achiver 3
dB12013
dB22013
dB32013
dB12014
dB22014
dB32014
dB1 dB2 dB3
Firewall
Power generation equipment
Wonderware InTouch(AlarmProvider)1
Wonderware InTouch(AlarmProvider)2
Wonderware InTouch(AlarmProvider)3
PRO
CESS
ING
ARCH
IVIN
G
FIN
Al l
ON
GTER
M
STO
RAG
EIN
TER
MEd
IATE
STO
RAG
E,E.
G. O
NE
MO
NTH
Alarm DB Converter
SQL Server•Wonderware
alarm/event database
•custom database
SQL Server•Wonderware
alarm/event database
•custom database
SQLclient
SQLclient
PC
SuiteLink/DDE Client (InTouch)
“CL Server/Client“ application
Wonderware’s own made DAServer(s) or Klinkmann’s Omron Ethernet Direct DAServer
Suitelink/dde interface
Suitelink/dde Server & oPc client
oPc interface
Ethernet
omron cS1
rockwell logix
Siemens Simatic
cl SerVerTarget of the product: Getting the alarm/event time stamping data from Plcs, to avoid possible loss of short time andfluctuatingalarms.
Main benefits reached with the product: exact till milliseconds Plc alarm time stamps are delivered to WonderwareSuiteLink/DDEClients(e.g.InTouch),nolossofshorttimealarms.
Typical applications: Time critical systems where very large amount of alarms are generated in short time intervals.
TheCLServer/Clientapplication(CLServer,CompositeLayerServer/Client)isusedforgettingalarm/eventtimestampingdatafromPLCs,disablingpossiblelossofshorttimeandfluctuatingalarmsandbufferingthealarm/eventdata.ThefollowingPlcsaresupported:SiemensS7,Allen-BradleyControlLogix,ModiconQuantumandOmronCS1.TheCLServercorrespondinglyusesWonderwareSIDirectDAServer(DASSIDIRECT),WonderwareABCIPDAServer(DASABCIP),WonderwareMBTCPDAServer(DASMBTCP)orKlinkmannAutomationOmronEthernetDirectDAServer(DASOmronEth)forcommunicationwiththesePLCs:
TousetheCLServer/Client,theappropriateadditions/modificationsmustbedoneincontrollerprogramfromwhere the alarm/event time stamping data is coming. The cl Server/client delivery package includes the program examples for Siemens S7-300, Allen-Bradley logix5555 and omron cS1 Plcs.
The cl Server/client application consists of two main parts:
oPc client part, for connection to appropriate dAServer via oPc interface; Suitelink/dde Server part, providing data for Suitelink/dde clients, e.g. Wonderware InTouch.
FromSuiteLink/DDEClient(e.g.InTouch)pointofview,theaccessingtoCLServer/Clientiscompletelysameas accessing to corresponding dAServer, i.e. same topic names and I/o point naming syntax is used, the only difference is the Server application name is “clServer”.
For cl Server/client Suitelink/dde Server part, the alarm bit I/o item names have the exactly same syntax as corresponding dAServer bit item names. For example, when accessing the S7-300 Plc via clServer and DASSIDIRECT,thealarmbititemDB123X4.5specifiesthebit5inbytewithaddress4inDB123.
Yekaterinburgtel. +7 343 287 [email protected]
St. Petersburgtel. +7 812 327 [email protected]
Moscowtel. +7 495 641 [email protected]
Кievtel. +38 044 495 33 [email protected]
Helsinkitel. +358 9 540 [email protected]
Vilniustel. +370 5 215 [email protected]
Rīgatel. +371 6738 [email protected]
Мinsktel. +375 17 200 [email protected]
Tallinntel. +372 668 [email protected]
Samaratel. +7 846 273 95 [email protected]
Wonderware_Finland_solutions_for_alarm_management_in_power_industry_en_0413
Ordering information
description order NumberAlarm Gateway PR 185 10Alarm DB Logger PR 186 10Alarm DB Converter PR 187 10CL Server/Client application DR 520 10SDTCP Server and SDOPC Server DR 530 10
InTouchtagname database
Configurationfiles
3rd Party oPcclient1
3rd Party oPcclientN
3rd Party oPcclient2
Firewall
PtAcc accessmodule
TcPServer
oPcServerfor 3rd Party oPc clients
TcP clientSdTcP Server
SdoPc Server
SdoPc Server 2SdoPc Server N
SdTcP SerVer ANd SdoPc SerVerTarget of the product:Providethemanageable,configurableandsecurealarm/eventdatatransferbetweenWonderware InTouch and 3rd party remote oPc clients.
Main benefits reached with the product: SecureandconfigurableremotedatatransferbetweenWonderwareInTouch and oPc clients.
Typical applications:PowergenerationandothersystemswheresecureandcustomizedcommunicationbetweenWonderware InTouch and oPc clients is required.
TheSDTCPServer(SecureDataTCPServer)andSDOPCServer(SecureDataOPCServer)aresoftwareproductsforprovidingmanageable,configurableandsecurealarm/eventdatatransferbetweenWonderwareInTouchand3rd party remote oPc clients over the internet or intranet via TcP/IP connection. Any single TcP port can be used forcommunication,soallowingfreelyconfigurableaccessthroughfirewalls.The3rdpartyOPCClientcanaccessonly to limited part of InTouch tagname database, these accessible InTouch tags and their access rights are configuredforeachremoteclientatInTouchside: