Sys 1 Tt Vol 2 Issue 1 Jan11
Upcoming SlideShare
Loading in...5

Sys 1 Tt Vol 2 Issue 1 Jan11






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Sys 1 Tt Vol 2 Issue 1 Jan11 Sys 1 Tt Vol 2 Issue 1 Jan11 Document Transcript

  • January 2011, Volume 2, Issue 1 SYSTEM 1 TIPS & TRICKSDear System 1 User,In the January Issue of System 1 Tips and Tricks we’ll show you how to configure severity levels for “Instrumentation Alarms” in System 1 version6.5 and later. In earlier versions the Instrument Alarm levels were fixed, giving no control over who received Instrumentation alarms..For this topic we assume that you have already configured different User Groups in System 1 and have defined the alarm severity notificationsthese groups should receive. When the Instrumentation Alarm Level is set too high for a “NOT OK”, “NO DATA” or “NO RESULT” condition, thisnotification may also go to an operator, as operators are typically configured to receive higher level alarms. The Instrument Alarms may beperceived by the operator as nuisance alarms, as they are not directly related to a machinery problem. Of course, we strongly recommend thatsomeone in your organization receives a “NOT OK”, “NO DATA” or “NO RESULT” Instrument level notification, so that this issue can be corrected.We will show you how to change these settings in the following steps. We hope you enjoy this issue.Sincerely,Your Southern Region FAE teamThis month’s tip by: Clyde Dooley, Field Application Engineer, Baton Rouge, LAVersions: User Level:6.5 and higher Power User Diagnostic UserApplies to: IT GroupSystem 1 Alarms Mid Level User Occasional User New User How to change Instrumentation Alarm Levels1 From System 1 Display, make sure the Instrument Hierarchy is visible. If not, go to step 2. If it is visible, go to step 3.
  • 2 If the Instrument Hierarchy is not visible, select “View”, “Instrument”, and check “Hierarchy”.3 To configure Instrument Alarm Severity for an existing or new Enterprise, right click at the highest level in the tree of the “Instruments Hierarchy” and select Properties. Right Click4 Specify the required severity level for “Not OK”, “No Results” and “No Data” in the Instrumentation Alarm fields, and click “OK”.
  • 5 By default, the severity level for Not OK Status is "3". That is, for any point whose status is Not OK, the severity level will be 3 by default. You can change this value within the range of 0 to 4. Changing it to “1” will prevent a nuisance hardware alarm from being sent to the Operator for a “Not OK” Status. However, the event will be recorded in the System 1 Event Manager. Similarly, the default severity level for “No Result” / “No Data” Status is "2". You can change this value within the range of 0 to 4. Again, changing this value to “1” will prevent a nuisance hardware alarm from being sent to the Operator. The Instrument Alarm severity configured is applicable to all the points both online and offline, irrespective of the number of DAQs configured for that Enterprise. Any modification in severity level will be reflected on all the points in the Enterprise. 6 After making these changes, stop and then restart the DAQ server. In some cases, you may need to reboot the DAQ server computer to reflect the changes.DID YOU KNOW?Bently Nevada now offers Motor Anomaly Detection with a unit called AnomAlert. In the next release of System 1(Version 6.8), the AnomAlert unit will be integrated into the System 1 software so that motor anomalies can bereported, trended and correlated to other measurements in System 1. For more information on AnomAlert, pleasefollow this link: Nevada Technical Support:bntechsupport@ge.com775-215-1818Bently Nevada website: 1 Blog (You’ll need to join the forum):