ALERT 5: How to Set Minimum Compliance Periodicity

also known a Collection Periodicity

This application notes covers the change to the asset collection periodicity setting in ALERT 5.

One of the changes in ALERT 5 is management of periodicity of data collection. This improvement is part of an initiative to relay a better understanding of expectation for data collectors and the delivery of compliance metrics.  This setting also covers the expectation for compliance for assets collected with wireless or online systems in addition to the traditional portable data collector.

Fundamentally, periodicity now uses a calendar cycle to set the minimum collection and compliance period in which data is expected, as opposed to defining a fixed number of days between collection sets.  This model allows users to understand what asset are due in a calendar period and relaying the compliance of this expectation via the PredictivePortal.

  • Compliance for TRIO: The Min. Compliance Periodicity, when set for portable data collection, indicates the frequency in which data is expected to be collected and analyzed.  The selection, monthly, bi-monthly, quarterly, etc., establishes the expectation of collection due for the TRIO user and will present the time remaining to accomplish data collection in order to achieve collection compliance.  Compliance includes both collection and analysis and thus the setting indicates how often data should be captured and a diagnostic result generated.
  • Compliance for Wireless and Online: Assets with permanent acquisition hardware installed also have an expectation of data collection based on operation of the asset.  The Min. Compliance Periodicity setting for these assets indicates the minimum requirement to have analyzable data captured on a machine and is recommended to set the MCP to "Weekly".  Wireless sensors will attempt to collect data daily, if the asset is not running or operating in a state that is not indicative of analysis, the wireless system may discard this test and wait for the next opportunity a day later.  Given data capture is automated, the periodicity setting is related only to the compliance of data for analysis.  Example:  the wireless system collects data daily, but the plant manager wants to ensure a machine diagnosis is available at least weekly.  Thus, if the machine is not running on some days, and the Min. Compliance Periodicity is set to WEEKLY, the asset will meet compliance as long as one valid test is collected and analyzed during the week.  A DAILY compliance periodicity setting would require the asset has collected analyzable data every day to meet compliance. 
  • Compliance for In-frequently Run Assets: Assets that do not normally run or assets that are merely available for non-periodic collection but have been setup in ALERT could be set to "Not Applicable".  Assets set as such will not be tallied in the Compliance Report.

Factors that affect compliance:

  • Planned Exception: An asset could have an extended period of time where the asset would not be available for collection such as an extended repair or a seasonal outage.  Setting a planned exception will remove the machine for the compliance calculation.
  • Period Exception: An asset may not be available when in the field attempting to collect data. A Period Exception can be entered via the TRIO or PredictivePortal to indicate report on the machine in lieu of data.  The period exception does not remove the asset for the list of due machines but will report the exception once the period has ended.
  • Rejected Test: Collected data must be analyzable to meet compliance.  An analyst could reject the test, triggering an indication on the data collector of the reason and expectation of retesting the machine.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk