|Bookshelf Home | Contents | Index | PDF|
The Preventive Maintenance Engine applies to the FS Preventive Maintenance business service. For more information, see FS Preventive Maintenance Business Service.
Administrators can set up one-time or repeating jobs for tasks that the Preventive Maintenance Engine completes. The component-specific parameters that the job specifies determine the engine actions for that job. For more information, see Parameters for the Preventive Maintenance Engine.
The set of objects must include either assets and plans or agreements. The sub-mode parameter in the job defines these objects. For assets and plans, if you specify only assets or only plans, then all of the other object types are assumed. For example, if you specify only assets (sub-mode is Assets), then the Preventive Maintenance Engine checks the specified assets for all plans. If you specify agreements, then each agreement implicitly defines a set of assets and plans (entitlements have associated assets or products and PM plans) that the engine processes for the agreement.
Usually these jobs use an SQL parameter that completes an SQL statement. The SQL statement locates the objects that the Preventive Maintenance Engine processes for the run. Component jobs can also use ID parameters instead of SQL parameters.
Users can pass requests directly from the Field Service client. For information about calling the PM Engine from the Assets screen or the Agreements screen, see Running Preventive Maintenance Plans (End User).
|Siebel Field Service Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|