Follow

Download - VTAG Templates

Vibration Test and Analysis Guide

Summary

The VTAG is an essential tool to ensure the repeatability of an Azima DLI trending program.  Additionally, with proper VTAG documentation, analysts and program managers can leverage multiple assets to rapidly deploy a program across larger enterprises.

Using the VTAG

The ExpertALERT (EA) software does not store nameplate information which would allow a user to make references to different assets.  The content of the VTAG include:

  1. Nameplate information for each component of the machine
  2. Test operating conditions for data collection
  3. Sensor locations and orientation references
  4. Known machine components and forcing frequencies

Azima DLI technicians and engineers use paper or electronic forms to create VTAGs for all machines to be included in a vibration program.  This step is generally completed prior to any vibration data being collected and during the "blocking" stage, installation of the sensor attachment pads.

The VTAG is on "paper", MID is in ExpertALERT

From the VTAG a user then builds the machine structure, known as Machine Identification or "MID" in the ExpertALERT software.  All machines that are applicable to the same VTAG, meaning machines that have the same components, nameplate information, test conditions, and process would all be included in one VTAG and then created as one MID in ExpertALERT.

Consider if you have six machines in a room that all perform the same function, made by the same manufacturer, and operate at the same test conditions.  These machines would all have comparable vibration spectrum and thus could all be used to develop an average baseline.  All of these machines would be included together in one VTAG and thus there would only be one MID.  

From the MID, machines are born

Users of ExpertALERT would then create the machines from the MID.  As such, the MID should be named so as to give good indication to the EA user as to which MID is applicable.  For example, below there are three machines.  The last machine has a slightly different motor.  Thus there would be two VTAGs and two MIDs.  From the software's perspective both use the same rules for performing analysis so technically, they would appear the same.  This means that the only way to make sure a user could differentiate between the two MIDs is from the name that each is given.

It is suggested that the name is created that refers to the differences, in this case the motor manufacturer is different and thus the MIDs could be named something like:

  • Circ Water Pump Reliance 40HP Aurora Pump
  • Circ Water Pump GE 40HP Aurora Pump

If there are difference sheave diameters, for example, the name of the MID might reference the ratio.  Or maybe one unit has a different number of pump vanes, that could be referenced in the MID name.

If a repair facility replaces the last machine in that picture with a different model, it could be easy then to reference the MIDs that are already built in the system and just assign the new MID, which may already have built the average baseline.

Last point, if there are two facilities that each have a pump room like the one above, the VTAG information can be shared so as all machines are setup the same way and the rulebase and average baseline can be collectively utilized to quickly develop accurate automated diagnostics.

Bottom line

By creating the VTAG users have:

  1. a document for which the program can be built
  2. a paper file can be created in case a database has to be restored
  3. core principles from which repeatability can be ensured
  4. ability to leverage more machines to rapidly build a program

A VTAG is merely a document.  There are a couple of templates available here to download to get users started.  WATCHMAN customers should follow the advice of their lead analyst for which to use.

Additional help on completing the VTAG can be found in the User Training section of the Azima DLI Resource Center.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk