Scheduling Logic and Job Generation define how FieldEx turns maintenance and recurring plans into real job orders. These rules determine when jobs are due, when they are created in the system, and how schedules react to delays or missed work.
Asset Maintenance Plans, Site Maintenance Plans, and Recurring Job Plans all use the same scheduling engine. Differences exist only in what entity is tracked (asset, site, or job) and which anchor dates are available.
This article covers:
How scheduling logic works in FieldEx
Fixed vs Floating scheduling behaviour
How first maintenance dates are calculated
When job orders are generated
Overdue, rescheduled, and missed maintenance behaviour
Type-specific scheduling differences
Overview of the Scheduling Engine
FieldEx currently uses a time-based scheduling model. This means maintenance and recurring work is planned using calendar intervals such as weekly, monthly, quarterly, or yearly schedules.
Once a plan is activated, FieldEx continuously evaluates:
The next due date
When the job should be generated
Whether a job is overdue
How future dates should shift, if allowed
Scheduling is calculated independently for each tracked entity:
Per asset in Asset and Contract Maintenance
Per site in Site Maintenance
Per job chain in Recurring Job Plans
Tip: Multiple assets or sites under the same plan can be on different schedules depending on their own history. |
Fixed vs Floating Scheduling
Every maintenance or recurring plan must choose how future due dates are calculated. This decision controls how the schedule behaves when work is completed early, late, or missed.
Fixed (Calendar-Based)
Due dates are calculated strictly from the calendar
Late completion does not affect future dates
Future jobs continue on the original schedule
Fixed scheduling is ideal for compliance-driven work where inspections or servicing must occur on specific calendar dates.
Floating (Based on Completion)
Next due date is calculated only after completion
Late jobs shift the entire schedule forward
Prevents stacked or overlapping jobs
Floating scheduling is best when maintenance intervals should reflect actual execution timing rather than fixed dates.
Tip: Fixed = calendar commitment. Floating = execution-based spacing. |
How the First Due Date Is Calculated
The Start schedule from setting defines the reference date used to calculate the very first due date. All future cycles are calculated by repeating the selected interval from this point.
Common anchor options
Last maintenance / site visit – uses the most recent completed job
Created date – uses the record creation date
Acquisition date – available for asset-based plans
When Fixed scheduling is selected, additional calendar alignment options appear.
Weekly schedules can align to a specific weekday
Monthly schedules can align to a specific date or weekday pattern
If no historical data exists, FieldEx automatically falls back to the plan’s start date to ensure scheduling can proceed.
When Job Orders Are Generated
Jobs are not created on the due date itself. Instead, FieldEx generates job orders in advance based on the configured job creation lead time.
Lead-time options are automatically limited based on the selected frequency to ensure they remain practical.
Weekly schedules: 3 or 7 days before
Bi-weekly schedules: 3 days, 7 days, or 2 weeks before
Monthly or longer schedules: up to 1 month before
Once generated, the job becomes an independent record. Changes to the plan affect only future jobs.
Tip: Use longer lead times when work requires customer coordination, spare parts, or third-party resources. |
Overdue, Rescheduled, and Missed Work
A job becomes Overdue when it passes its due date without being completed.
If Auto-reschedule (self-healing) is enabled:
The job remains overdue for a buffer period
The system reschedules the job to a new date
Future dates are recalculated accordingly
If self-healing is disabled, overdue jobs remain overdue until resolved manually.
Important: If two consecutive cycles are missed, job generation pauses until maintenance is completed or the schedule is corrected. |
Type-Specific Scheduling Differences
Asset Maintenance
Calculated per asset
Supports acquisition and last maintenance anchors
Missing two cycles pauses job generation for that asset
Contract Maintenance
Calculated per contract asset, using the same scheduling engine as Asset Maintenance
Assets are inherited from the contract, so the maintenance tracking view updates when contract assets change
Execution is reviewed within the contract context, supporting compliance checks, renewals, and audit evidence
Jobs generated remain valid even if the contract plan expires or is cancelled, preserving history for reporting
Site Maintenance
Calculated per site
Uses last site visit or site created date
Supports manual Generate Job and Adjust Date actions
Recurring Job Plans
Job-centric rather than asset or site-based
Fixed schedules continue regardless of delays
Floating schedules pause until jobs are completed