Siebel Field Service Guide > Preventive Maintenance > About Triggers for Preventive Maintenance >

Usage Triggers


Usage triggers activate a PM plan when the reading from an asset changes by a specified amount. Each trigger record has start and end values, so that the PM plan activation can change according to the usage of the asset. For example, a service request is generated every 3,000 counts for the first 15,000 counts, then every 10,000 counts after 15,000 counts.

NOTE:  For Time Interval and Usage triggers that use Valid Start and Valid End fields, the trigger does not occur if the interval falls past the Valid End field value.

The trigger occurs if the readings for the specified measurement change greater than the specified interval. The change is determined by the difference between the most recent reading and the reading at the time of the last PM action. The PM engine evaluates only the readings that are marked Done. If the most recent reading is less than the reading at the time of the last PM action, then the measurement is assumed to have wrapped around and the change is calculated as follows:

change = (max - last) + (new - min) + 1

Usage triggers can also have a Valid Start field and Valid End field. These fields define the reading values for which the trigger is valid.

You specify measurement types in Usage triggers. If an asset has more than 1 measurement of the type for the Usage trigger, and if any of the measurements exceed the usage for its type, then the trigger occurs. To avoid this occurrence, define specific types in the measurement type LOV (ASSET_MEAS_TYPE). For more information, see Associating Measurement Types with Assets (End User).

Siebel Field Service Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.