Thank you. Excellent responses as always from the foxboro@xxxxxxxxxxxxx<mailto:foxboro@xxxxxxxxxxxxx>! +----------------------------------------+ | Todd J. Pioch, V&V Engineer | | NextEra Energy - NPE/PSL, UMF-3038 | | 6501 S. Ocean Drive | | Jensen Beach, FL 34957 | | W: 772-467-4900 | | C: 561-797-3646 | | E-mail: Todd.Pioch@xxxxxxx<mailto:Todd.Pioch@xxxxxxx> | +----------------------------------------+ -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, Alex P (IOM) Sent: Tuesday, December 06, 2011 1:36 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Historize I/A Workstation Status? Re: It is possible to write the values using omset to a Compound:Block.parameter. That is possible and I recommend the following variation: 1) Use omsetimp to eliminate multicasts. 2) Store the data in Shared Variables in the AW/WP Shared variables are OM data stores with a flat names space. Names can be up to 14 characters long, e.g., <wpLbug>HD The use of SVs means that the data does not have to travel across the control network for storage and it is MUCH faster to store locally than in a CP. The Historian, FoxView, and other OM applications can read these values and manipulate them. The are created by using /opt/fox/bin/omcrt. Type it without arguments to get a syntax summary. You want to create a "go_" script in /usr/fox/apps to create them and run that script from /usr/fox/apps/foxapps.dat. (I think I got the directory names wrong. I can't get to a system at the moment, but it's the directory with all the "go_" scripts.) 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 1700 (Central Fax) alex.johnson@xxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of andreas.weiss@xxxxxxxxx Sent: Tuesday, December 06, 2011 8:59 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Historize I/A Workstation Status? Hi Todd, you may decide if you want to use scripts or to buy a management solution e.g. from MS. An installation with more than 5 machines cries at a out of the box solution. Scripting guys prefer the shell or powershell. It is possible to write the values using omset to a Compound:Block.parameter. 1. % hard drive space remaining -> http://powershell.com/cs/media/p/1617.aspx 2. % CPU load -> http://powershell.com/cs/media/p/12254.aspx 3. Networking load -> Buy the NetSight offer from Invensys. Regards, Andreas _______________________________________________________________________ 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 _______________________________________________________________________ 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