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:
- Include This PM in the Forecast field
- Frequency information
- Seasonal Dates information
- insertion or deletion of job plan sequences
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:
- If the Use Last WO's Start Information to Calculate
Next Due Frequency check box is selected (set to Yes),
the forecast dates remain the same, and the job plan information is
automatically updated on the Forecast tab.
- If the Use Last WO's Start Information to Calculate
Next Due Frequency check box is cleared (set to No), the
forecast is deleted. You must generate a new forecast, or wait for
the PMForecast cron task to run.
Status changes
Status changes affect the
PM forecast in the following ways:
- Changing the status of a PM, or any child within a PM hierarchy,
deletes the PM forecast.
- Changing the status of an asset or location on the PM record deletes
the PM forecast.
Asset moves
Assets are often moved from
place to place within an organization. Asset moves affect the PM forecast
in the following ways:
- When an asset is moved within its current site, the forecast remains
in place, unaffected.
- When an asset is moved to a new site, the forecast is deleted
from the original PM. If a master PM exists, a new PM record is created
for the asset in its new site. The forecast must be generated for
the new PM, manually or by using a cron task.