Re: [foxboro] Alarm management

  • From: "Gosselin, Patrick" <patrick.gosselin@xxxxxxxxxxxx>
  • To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 14 Oct 2011 16:31:26 -0400

From my experience, the am names are defined in the dmcfg file and associated 
to a dm name. That being said, I believe you can only have as many AM's as you 
have DM's or FV's.


Regards,
Patrick Gosselin, CTech
Senior System Service Representative

Invensys Systems Canada Inc.
1349-2 Kelly Lake Road
Sudbury, ON P3E 5P5

T – (705) 523-1331
F – (705) 523-1881
C – (705) 690-1642
E – Patrick.Gosselin@xxxxxxxxxxxx

http://www.iom.invensys.com

----- Original Message -----
From: Corey R Clingo [mailto:corey.clingo@xxxxxxxx]
Sent: Friday, October 14, 2011 04:25 PM
To: foxboro@xxxxxxxxxxxxx <foxboro@xxxxxxxxxxxxx>
Subject: Re: [foxboro] Alarm management

Looking into this topic myself. How many CADs can one run from a single 
WP/AW? Can it be more than the number of DMs/FVs?

Thanks,
Corey
 



From:
"Johnson, Alex P (IOM)" <Alex.Johnson@xxxxxxxxxxxx>
To:
"foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
Date:
10/14/2011 01:21 PM
Subject:
Re: [foxboro] Alarm management
Sent by:
foxboro-bounce@xxxxxxxxxxxxx



First Problem - If the contents of the file are identical, you can use a 
Solaris link (ln -s <file> <linedFile>) or a Windows shortcut and name the 
file after the CB.AlarmType. This is a bit of a maintenance effort, but...

You could also maintain that association (CBP to file name) in a file and 
have your script search the association file (grep) for the file name to 
display. This is much better, but requires a bit more script work. I'd go 
this way.


Second Problem - The most common thing is to run two CADs on the WP and 
use a filter to segregate the displayed messages. It works well.

Regards,
 
Alex Johnson
Invensys Operations Management
10900 Equity Drive
Houston, TX 77041
+1 713 329 8472 (desk)
+1 713 329 1600 (operator)
+1 713 329 1944 (SSC Fax)
+1 713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxx







 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: