An Example Of An Effective Database Setup |
The exact nature of your database setup and the specifics must be addressed according to the vendor you purchased your software from. Most programs fail because usable, worthwhile data can not be extracted from the database. Why does this happen ? The software usually has certain useful features such as reporting capabilities that can be accessed - if the database is created in such a way as to not only take advantage but to make the best use of those features. |
By way of a single example - and their are numerous ways to set up a database - the service company Vibe-Assist looked at two ingredients that went into the collection and analysis of data - what information they wanted vs. what the reporting capability of the software was (Entek's Odyssey™) - and came up with database setup templates that are used for creating an effective database structure that uses software features of Odyssey to provide information we want. By generating a database structure that takes maximum advantage of a powerful software reporting feature, Vibe-Assist reduced their analysis time by an incredible 80% or so. This new database structure did not generate this huge improvement by reducing machinery protection or analysis accuracy. On the contrary, the new setup improved the reliability of the analysis and improved the level of protection possessed by the machines they monitor. In order to illustrate the value of an effective database setup, Vibe-Assist has agreed to share a few of their component setups along with an explanation of the logic behind the database structure. Shown below are examples of a direct drive, 4-bearing machine and a belt-drive, 4-bearing machine. The links below under the "Type" of reading will take you to explanation pages for each of the readings. |
Direct Drive | |||||
|
|||||
|
|
|
# of Lines |
|
Direction |
|
|
|
|
|
|
|
|
- or - 60kcpm* |
|
|
|
|
|
up to 60kcpm |
|
|
|
|
|
relevant period |
|
or velocity |
|
|
|
|
|
acceleration |
|
Direct Drive | |||||
|
|||||
|
|
|
# of Lines |
|
Direction |
|
|
|
|
|
|
|
|
- or - 60kcpm* |
|
|
|
|
|
up to 60kcpm |
|
|
|
|
|
relevant period |
|
or velocity |
|
|
|||||
|
|||||
|
|
|
# of Lines |
|
Direction |
|
|
|
|
|
|
|
|
- or - 60kcpm* |
|
|
|
|
|
up to 60kcpm |
|
|
|
|
|
relevant period |
|
or velocity |
|
Top
Belt Drives
Explanation
of Readings
Sample Report
|
|||||
|
|||||
|
|
|
# of Lines |
|
Direction |
|
|
|
|
|
|
|
|
- or - 60kcpm* |
|
|
|
|
|
up to 60kcpm |
|
|
|
|
|
relevant period |
|
or velocity |
|
|
|
|
|
acceleration |
|
Belt Drive | |||||
|
|||||
|
|
|
# of Lines |
|
Direction |
|
|
|
|
|
|
|
|
- or - 60kcpm* |
|
|
|
|
|
up to 60kcpm |
|
|
|
|
|
relevant period |
|
or velocity |
|
|
|||||
|
|||||
|
|
|
# of Lines |
|
Direction |
|
|
|
|
|
|
|
|
- or - 60kcpm* |
|
|
|
|
|
up to 60kcpm |
|
|
|
|
|
relevant period |
|
or velocity |
|
Top
Direct Drives
Belt Drives
Sample Report
|
There are numerous other component
setups in the templates - these are for generic, rolling element bearing
machines running at normal speed (1000 - 3600 rpm). But this seems like
an extreme amount of data - how does this help with analysis ? Well, first,
each reading has a specific job to do:
|
Top Direct Drives Belt Drives Explanation of Readings |
|
To address the high frequencies, an identical report is created to handle the acceleration spectral data. The amplitude trigger for acceleration units will typically be about 1G - a very safe, fairly low amplitude threshold. Any line on the acceleration report is investigated by first looking for any impact frequencies on the associated envelope spectrum and then by making an assessment of the vibration source. Further investigation may be necessary but the report(s) give easily accessed, easily analyzed information that prompts immediate investigation in the problem areas. Much of the data does not get looked at but that is simply because the vibration levels too low to be concerned with. |