PM edits when a forecast exists

When you change a preventive maintenance record that has an existing forecast, the forecast can be affected.

The dates within a PM forecast are determined by the values in certain fields on the preventive maintenance record, for example, frequency and seasonal information. When you edit these fields, the forecast for the PM becomes inaccurate. After a warning message indicates the conflict, the forecast is deleted. You must generate a new forecast that includes the updated information, or wait for the PMForecast cron task to run.

PM field changes that affect the forecast include the following:

PM counter

When a forecast exists, the PM counter alters the order of the job plans in the forecast (if a job plan sequence exists). Changes to the PM counter affect the PM forecast in the following ways:

Status changes

Status changes affect the PM forecast in the following ways:

Asset moves

Assets are often moved from place to place within an organization. Asset moves affect the PM forecast in the following ways:



Feedback