Bookshelf Home | Contents | Index | Search | PDF

Siebel Field Service Guide > Preventive Maintenance > The Preventive Maintenance Engine >

Running the Preventive Maintenance Engine

---

There are two methods of invoking the Preventive Maintenance Engine: through server requests and through the Field Service client.

Using Server Requests

Administrators can set up requests (one-time or repeating) for tasks that are serviced by the Preventive Maintenance Engine. The component-specific parameters specified by the request determine what the engine does for that request. For a detailed explanation, see Parameters for the Preventive Maintenance Engine.

In general, tasks must define these variables:

A set of objects for the engine to operate on.
A date that is the latest date to schedule preventive maintenance during the run.
The mode in which the task is to be run. When invoking the PM Engine through server requests, you can specify either ID or SQL mode for this variable. (The Field Service client uses another mode, TempTbl, when invoking the PM engine.)
The sub-mode, which determines the entities that are specified for the selected mode.

The set of objects must include either assets and plans or agreements, as defined by the sub-mode parameter in the request. In the case of assets and plans, if only assets or only plans are specified, then all of the other object types are assumed. For example, if only assets are specified (SubMode=Assets), then the Preventive Maintenance Engine checks the specified assets against all plans. When agreements are specified, each agreement implicitly defines a set of assets and plans (entitlements have both associated assets/products and PM plans) that the engine is to process for that agreement.

Bookshelf Home | Contents | Index | Search | PDF