Please note that usage-based maintenance plans are based on asset metrics. Please follow this guide before attempting to add metrics to maintenance plans:
Read Full Guide: Asset Metrics
While asset metrics track equipment usage, the true effectiveness of our system lies in its ability to initiate service events through various triggers. These triggers can be added to maintenance plans in addition to or instead of traditional time/calendar-based events:
Interval (Every): This trigger operates on a cyclical basis. For example, setting an interval of every ten units (hours, cycles, etc.) means the system will trigger a service event at each multiple of 10 at 10, 20, 30, and so forth.
Milestone (At): Milestones are pre-set markers. A service event is triggered when the value reaches these set milestones. While the intervals between milestones can vary, it's important to note that new ones must be established once the final milestone is reached to continue effective monitoring.
Threshold (Above): This trigger activates when a value ascends past a specified threshold. It's particularly useful for monitoring metrics that should remain within a certain range, triggering a service event if the value rises above the set point.
Threshold (Below): This trigger is engaged when a value descends below a defined threshold. It's essential for metrics where a minimum value is critical, ensuring that a decrease beyond this point prompts immediate action.
Capture Only (No Trigger): Sometimes, collecting data without triggering a service event is necessary. This option allows for the continuous monitoring and recording of data, providing insights without initiating maintenance actions.
Note: Please be aware that integrating a metric with a maintenance task necessitates an initial saving of the task. This requires specifying the Task Name. Once the task is saved, the “Add Metric” button will appear, and you can add various metric-based options.