Bookshelf Home | Contents | Index | PDF |
Siebel Field Service Guide > Preventive Maintenance > Preventive Maintenance Engine > Running the Preventive Maintenance EngineThere are two methods of invoking the Preventive Maintenance Engine: Related TopicFS Preventive Maintenance Business Service Using Component JobsAdministrators can set up jobs (one-time or repeating) for tasks that are serviced by the Preventive Maintenance Engine. The component-specific parameters specified by the job determine what the engine does for that job. For a detailed explanation, see Parameters for the Preventive Maintenance Engine. In general, tasks must define these variables:
The set of objects must include either assets and plans or agreements, as defined by the sub-mode parameter in the job. 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 (Sub-mode=Assets), then the Preventive Maintenance Engine checks the specified assets with 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. Usually these jobs use a SQL parameter that completes a SQL statement. The SQL statement locates the objects that the Preventive Maintenance Engine will process for that run. Component jobs can also use ID parameters instead of the SQL parameters. CAUTION: Do not run component jobs in Temp-Table Mode to invoke the Preventive Maintenance Engine. This mode is reserved for interactive engine jobs sent directly from a client application. Using the Field Service ClientEnd users can pass client requests directly from the client application. They can do this by performing one of the following: |
Siebel Field Service Guide |