Maintenance Forecasting Engine for Recurring PM Plans
The Maintenance Forecasting Engine in PTC Orbit calculates forecasted maintenance visits for PM Plans that use recurring PM Schedule Definitions, enabling planners to see projected workload for assets with no upfront PM Schedules.
PM Plans in ServiceMax Core follow two scheduling approaches. Some plans generate upfront PM Schedule records; individual, forward-dated visits created when the plan runs. Others use recurring PM Schedule Definitions that specify a frequency and interval but produce no upfront schedule records. For assets on recurring-definition plans, the Demand Forecasting feature had no confirmed visit dates to include in a forecast.
The Maintenance Forecasting Engine resolves this gap. It runs calculations inside PTC Orbit to project maintenance visits across the lifespan of each PM Plan that uses recurring definitions, then makes those projected visits available to the Demand Forecasting feature. Planners can now build forecasts that include both confirmed upfront schedules and dynamically calculated recurring visits for a complete picture of expected maintenance demand.
This engine is a backend capability. It has no standalone UI. Its output is visible through the Demand Forecasting page in PTC Orbit, where forecasted work orders and work hours reflect the projected visits calculated by the engine alongside historical AI forecast data.
This is Phase 2 of preventive maintenance demand forecasting. Phase 1 integrated confirmed upfront PM Schedule data from ServiceMax Core. Phase 2 extends coverage to plans that operate on recurring definitions, closing the forecasting gap for organizations that use that scheduling strategy.
How It Works
The engine reads PM Plan and PM Schedule Definition data from the PTC Orbit Canonical Data Model, which is populated by the maintenance data pipeline. For each qualifying PM Plan, the engine computes projected visit dates using the following inputs.
• PM Plan start date: The date from which the calculation begins projecting visits.
• PM Plan end date: The boundary beyond which no visits are projected.
• PM Schedule Definition frequency and interval: Determines the cadence of projected visits; for example, quarterly or every 6 months.
• Last scheduled-on date: Derived from the PM Schedule Definition's history, this anchors the calculation to the most recent known visit and prevents duplicate projections.
Projected visits are stored in the Canonical Data Model as forecast outputs. They are not written back to ServiceMax Core and are not persistent outside PTC Orbit.
Key Capabilities
• Calculates forecasted maintenance visits for PM Plans that use recurring PM Schedule Definitions, where no upfront schedule records exist.
• Feeds projected visit data into the Demand Forecasting feature so planners see a complete view of expected maintenance workload.
• Runs as a background calculation; no manual trigger or configuration step is required after the maintenance data pipeline is in place.
Considerations
Review the following constraints before relying on forecasting engine output in your demand forecast results.
• Only time-based recurring PM Schedule Definitions are supported. Condition-based PM Plans are not processed by this engine.
• Projected visits exist only in PTC Orbit. They are not written back to ServiceMax Core and do not create work order records in the source system.
• The maintenance data pipeline must be deployed and actively syncing data from ServiceMax Core before the engine can calculate visits.
Related Topics