Re: [foxboro] Re[2]: Alarms to Remote Stations

Daren,

Alex's explanation is correct.  The alarm messages are targeted to
workstations, printers, and historians.  There is no way to target alarms to
individual alarm managers.

Matching and filtering allow you to restrict which alarms can be viewed on
the AMs.  One approach is to create a match/filter specification file for
each FV of DMs with a name of <dmname>.ams in the directory
/usr/fox/customer/alarms/amspec.  For FV, you can then configure your
"Process" button as follows in init.user:

        PRC_BTN=rcntalms -match $DMNAME.ams

Use ALMP for DMs (I think).

When the AM is started it will apply the appropriate match/filter
specification.  If you do not want your operator's to be able to clear the
criteria you set up, you might want to consider protecting the "Match..." on
your AM displays.

There is no way with the current system to control horns, "Process" button
(FV), "Alarm" button (DM), "New Alarms", annunciator LEDs, etc. based on the
match/filter.  All of these functions are handled at the workstation level
before the alarms ever reach the AMs.

Regards,


-----Original Message-----
From: Daren Bishop [mailto:dbisho@xxxxxxxxxxxx]
Sent: Wednesday, December 05, 2001 2:12 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Re[2]: Alarms to Remote Stations 



     Alex,
     
     I have assigned DM's to remote stations. I have cofigured DMTOAM to 
     assign alarm managers to DM's. 
     
     The remote stations can access either a WP or a AW on ths same node. I 
     want to assign alarms by compound etc. to show up on those remote 
     station's alarm managers and on a "catch-all" alarm manager on the 
     WP/AW.
     
     Your explanation of configuring the alarm button with a filter file 
     sounds like what I might have to do for each station so only relevant 
     alarms go to that alarm manager.


______________________________ Reply Separator
_________________________________
Subject: Re: [foxboro] Alarms to Remote Stations 
Author:  <foxboro@xxxxxxxxxxxxx> at INTERNET-MAIL
Date:    12/5/01 1:43 PM


     
I'm confused by what you are asking.
     
Each alarm is assigned to an alarm group.
     
The first three alarm groups are tied to the compound holding the block. The

next 5 are tied to the CP holding the compound.
     
You can specify the destination of an alarm by placing the logical name of 
the target in one of the alarm group slots. In the Compound these are: 
GRxDVy where x is 1 to 3 and y is 1 to 8. The arrangement is different for 
the groups associated with the CP, but if you look at the STATION block and 
FoxDoc you will figure it out.
     
Once an alarm goes to a WP, it is sent to all Alarm Managers on that WP. 
However, that does not mean that it will be displayed on each Alarm Manager 
running on the WP.
     
You can configure the 'Alarm' button to specify a filter file when the Alarm

Manager is started. This filter file can control what alarms are displayed.
     
     
Is any of this close to what you want to know?
     
     
     
Regards,
     
     
Alex Johnson
System Products - Invensys Systems, Inc. 
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx <mailto:ajohnson@xxxxxxxxxxx> 
     
     
     
        -----Original Message-----
        From:   Daren Bishop [SMTP:dbisho@xxxxxxxxxxxx] 
        Sent:   Wednesday, December 05, 2001 11:56 AM 
        To:     foxboro@xxxxxxxxxxxxx
        Subject:        [foxboro] Alarms to Remote Stations
     
     
             All,
             
             I have implemented remote draw stations, and looking for a way 
to send 
             only relevant alarms to the remote stations' alarm manager. Now

all 
             alarms go to all stations.
             
             Does anyone know a way to send alarms configured by compound to

alarm 
             managers or display managers?? I haven't been able to find any 
             documentation on this. Tried configuring compound to address 
Alarm 
             Mangager with no success. Any ideas?? 
             
             
             Daren Bishop
             Process Control/Systems Engineering 
             ASC Inc.
             (409) 721-1510
             dbisho@xxxxxxxxxxxx
     
         
         
        ___________________________________________________________________ 
        This list is neither sponsored nor endorsed by The Foxboro Company. 
        Use the information obtained here at your own risk. For disclaimer, 
        see http://www.thecassandraproject.org/disclaimer.html#maillist
     
        list info:   http://www.freelists.org/list/foxboro
        subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join 
        unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
     
     
___________________________________________________________________ 
This list is neither sponsored nor endorsed by The Foxboro Company. 
Use the information obtained here at your own risk. For disclaimer, 
see http://www.thecassandraproject.org/disclaimer.html#maillist
     
list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join 
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
     
     

 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: