Follow

ALERT 5: Calendar-based Compliance

ALERT 5 & TRIO 5 better prepares field collectors with an expectation of collection due to meet compliance. A new calendar-based periodicity setting gives field visibility to when assets are due with options to report exceptions in lieu of data for the compliance reports in PredictivePortal.

To set Calendar-based Periodicity perform the following:

1.  Open StandardALERT

2.  Select the machine to set compliance, right-click the machine, select Open Machine

3.  Select the Machine Info tab

4.  Select the applicable Collection Periodicity (aka Minimum Compliance Periodicity)

mceclip0.png

If you have an existing machine with the Routine Collection Period (in days) set to track data collection requirements, StandardALERT will automatically set the most logical Calendar-based Collection Periodicity setting based on the number of days entered.

Note:  The Routine Collection Period field will be eventually phased out of the application, but some reports still reference this value.

Collection Periodicity vs Minimum Compliance Periodicity

Data collection periodicity is tied to collection compliance.  On the TRIO, the periodicity field is used to present the days remaining in the period to best provide the person in the field an understanding of the number of days remaining to be complaint.  A compliance metric is available on PredictivePortal to track.

See this article on understanding Collection Periodicity as presented on the TRIO.

Compliance and Wireless Vibration

Given wireless sensors capture data automatically and frequently, the calendar-based periodicity setting can be used to ensure compliance is met based on the expectation of results on a machine. The value set for periodicity indicates the minimum requirement for data capture.  Thus, if the periodicity is set for daily, there is an expectation that data must be captured every day to meet compliance as reported on the PredictivePortal.  This field should be set to the minimum expectation for compliance.

Example:

I have wireless sensors on a machine and they attempt to capture data once per day.  Sometimes the machine isn't running and thus no data will be captured.  However, I want to make sure that at least once a week I have an updated diagnostic result for my machine and therefore would set the Minimum Compliance Periodicity setting to weekly.  Though I may get more data than once a week, if no data is captured for the machine in one calendar-week, the machine will be marked as non-compliant.

 

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

Comments

Powered by Zendesk