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

Usage Triggers

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

NOTE:  For Time Interval and Usage triggers (which use Valid Start and Valid End settings), if the interval falls beyond the Valid End, the trigger does not fire.

The trigger fires if the readings for the specified measurement have a delta greater than the specified interval. The delta is determined by the difference between the most recent reading and the reading at the time of the last PM action. To be considered, the readings must be marked as Done. For more information, see Warranty View. 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 delta is calculated as follows:

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

Usage triggers may also specify a valid start and end, defining the values of the reading for which the trigger is valid.

A measurement is specified only by its type. For more information, see Measurements View. If an asset is given more than one measurement of the type specified by a Usage trigger, then if any of the measurements exceed the usage specified by its type, the trigger fires. To avoid this, you should define specific types, as applicable, in the measurement type LOV (ASSET_MEAS_TYPE).

Siebel Field Service Guide Copyright © 2007, Oracle. All rights reserved.