What are Equipment Schedules?
Equipment schedules are recurring maintenance, inspection, or service tasks assigned to wells, plants, PSVs, or individual pieces of equipment. Each schedule tracks what work needs to happen, how often it must occur, when it is next due, and how urgently it needs attention.
Naming: The schedule module in Admin is still labeled Equipment Schedules. The form type operators fill when a schedule requires a form is Machine Schedule in Form Config (older screens and reports may still say "Equipment Schedule"). Use Machine Schedule when talking about the form type.
Key point: Schedules do not exist in isolation — they belong to a schedule type (the category of work), and every completion automatically creates the next occurrence, keeping the chain of records continuous.
Why Equipment Schedules Matter- Accountability - Creates a permanent record of every completion, deferral, and edit
- Automated sequencing - Next due date or service hour is calculated automatically on completion
- Urgency tracking - Warning levels flag upcoming and overdue work for field teams and dashboards
- Flexibility - Supports date-based, hour-based, or hybrid scheduling across any asset type
- Integration - Schedules can require forms to be completed as part of finishing the work
Setting up equipment schedules involves two administrative steps that must be done in order:
- Create schedule types — Define the categories of work available to your organization
- Create schedules on assets — Assign a schedule type and parameters to specific wells, plants, PSVs, or equipment
Schedule types are the named categories of work (for example, "Annual Service", "Emissions Check", "Oil Change"). They must exist before a schedule can be created.
You can manage schedule types in the Admin section under Equipment Schedules → Schedule Types:
- Classification - Internal code used by EZ Ops to group types (for example, MSAPR types handle emission and performance test workflows automatically)
- Readable type - The name shown to users on schedules and reports
- Entity - Optionally scopes the type to a specific asset category
Some schedule types are system-level (global) and cannot be deleted. Organization-specific types can be created, edited, and soft-deleted. Soft-deleting a schedule type does not affect schedules already created with that type — they remain active.
Step 2: Creating a Schedule on an AssetSchedules are created from the asset's detail view (well, plant, PSV, or equipment page) in the admin or management interface. The fields required depend on the schedule type selected.
Core Fields (all schedules)
- Schedule type - Select from the available types for your organization
- Work type - The category of work (for example, Maintenance, Safety, MSAPR)
- Description - A short label describing this specific schedule instance
- Repetition type - How the next due date is calculated after each completion (see below)
- Sub-unit / child - Optional: attach the schedule to a specific sub-component (engine, compressor, etc.) rather than the whole asset
Schedule Trigger Type
The Schedule By dropdown sets how the schedule is measured:
- Date - Scheduled by calendar date. Requires a next due date, date frequency, and frequency unit (day / week / month / year)
- Hours - Scheduled by equipment runtime hours. Requires a total hours key (the equipment log field tracking runtime), a frequency in hours, and a next service hour value
- Hybrid (Hours/Date) - Triggered by whichever comes first: a calendar date or a runtime hour threshold. Requires all fields from both date and hours
- Usage - Scheduled by any counter on a reading sheet other than runtime hours, such as cycles, volume pumped, or kilometres. Requires a log key to count against, a frequency, and a next service value. Works the same way as Hours, but the counter is whatever field you point it at
Repetition Types
| Type | How next due date is set | Use when |
|---|---|---|
| Dynamic | Calculated forward from the actual completion date | Work should always have the full interval between completions |
| Static | Resets to a fixed calendar anchor point (specific day of month) | Work must always fall on the same calendar date |
| Window | Tied to a fixed period (month, quarter, year); never flagged overdue while open | Work can be done any time within the period; missed periods are recorded as Delinquent |
For a detailed explanation of each type, see the "Schedule Repetition Types" article.
Frequency Settings (Date Schedules)
- Date frequency - The number of units between occurrences (for example,
3for every 3 months) - Frequency type - The unit:
day,week,month, oryear - Repeat on - Optional anchor for Static schedules; sets the specific day of the month (or
lastfor last day of month) that the due date always falls on
Frequency Settings (Hour Schedules)
- Total hours key - The equipment log answer field that holds the current runtime reading
- Frequency (hours) - How many hours between each service (for example,
250for every 250 hours) - Next service (hours) - The runtime hour value at which this schedule next becomes due
- Last completed hours - Set automatically on completion; used as the baseline for next service calculation
Warning Settings
Warning settings control when the schedule is flagged as upcoming on dashboards and triggers email notifications. There are two ways warnings are configured:
Automatic (default) — EZ Ops calculates warning level automatically based on the schedule's frequency and how close it is to the due date. No setup required.
Custom — Override the default thresholds with a specific trigger. Choose Custom, then set an amount and a unit:
- days — Flag the schedule when it is within N days of the due date
- percentage — Flag the schedule when the percentage of the interval remaining drops below N%
- unit — Flag the schedule when the counter on the reading sheet comes within N of the next service value. This option only appears on Usage schedules, where counting down in raw units is more meaningful than counting days
If no custom warning is set, the automatic thresholds apply (see the Warning Level Calculation section below).
Usage schedules now warn and appear in Upcoming. Previously a Usage schedule never entered a warning state and never surfaced in the Upcoming view, so the only way to notice one coming due was to look at it directly. Usage schedules now behave like Hours and Date schedules: they enter their warning period, appear in Upcoming, and trigger the same notifications. If your organization has Usage schedules that have been quiet, expect them to start appearing.
Optional Fields
- Planned date - A target date for when the work is intended to be done (does not affect the due date)
- Sub-group - Groups sub-unit schedules together under a parent asset for reporting
- Reset key - For hour-based schedules on equipment with an odometer-style reset: identifies the log field that tracks hours-since-last-service
[Image placeholder: Screenshot of the schedule creation form showing schedule type, type (date/hours/hybrid), repetition type, frequency fields, and custom warning fields]
Warning Level CalculationThe warning_level field is stored on each schedule record and updated automatically by a background job. It is also saved as email_notification when a level change triggers an alert.
Warning level values:
0ornull— No warning, schedule is not yet approaching3— Upcoming (first warning, yellow) — work is approaching but not urgent2— Soon (second warning, orange) — work is coming up soon1— Urgent or overdue (final warning, red) — work is imminent or past due
Default Thresholds by Frequency
Long-frequency schedules (date frequency greater than 60 days):
| Warning Level | Condition |
|---|---|
| 3 (yellow) | Within 60 days of due date |
| 2 (orange) | Within 10 days OR less than 5% of interval remaining |
| 1 (red) | Within 5 days, less than 1% remaining, or past due |
Short-frequency schedules (date frequency 60 days or less) and all hour schedules:
| Warning Level | Condition |
|---|---|
| 3 (yellow) | Within 7 days of due date |
| 2 (orange) | Within 4 days OR less than 5% of interval remaining |
| 1 (red) | Within 2 days, less than 1% remaining, or past due |
Window schedules do not have a warning_level computed — the background job explicitly excludes them. Equipment schedule windows also do not have a warning_period field — that concept exists only on inspection schedules (where it controls how early the planner flags the schedule as urgent). For equipment schedule windows, there is no built-in mechanism to turn the flag red earlier within the window period.
Instead, window status is tracked through the operational_actions table, which stores two dates for every window schedule:
active_date— the start of the current window period (calculated asnext_date - frequency + 1 day)due_date— the end of the current window period (next_dateon the schedule)
When a window closes without completion, the machine_schedules record is marked status = 'Delinquent' and a new window opens automatically.
For reporting on equipment schedule windows, derive status from these fields — there is no system-defined urgency threshold within an open window, so any "closing soon" threshold is calculated in your view:
| Desired status | Query logic |
|---|---|
| Window open (in progress) | active_date <= today AND due_date >= today (on operational_actions) |
| Window closing soon | DATEDIFF(due_date, today) <= N days (your chosen threshold — no built-in default) |
| Window missed (delinquent) | status = 'Delinquent' on machine_schedules |
Custom Warning Override
When a schedule has custom_warning_amount and custom_warning_unit set, the custom threshold replaces the default calculation, but warning_level is still written to the record exactly the same way — the background job runs the custom path instead of the default path and saves the result. You can still query warning_level on custom-warning schedules in your reporting views.
How the custom path calculates the level:
- If past due → always level 1
- If the unit is days → level 1 when within N days of the due date; otherwise level 3
- If the unit is percentage → level 1 when the percentage of the interval remaining is ≤ N%; otherwise level 3
- If the unit is unit (Usage schedules only) → level 1 when the logged counter value is within N of the next service value; otherwise level 3
Custom warnings produce only two states (1 or 3) — there is no level 2 intermediate with a custom warning.
How Hour-Based Due Dates Are Estimated
For hour-based schedules, the system estimates the due date by:
- Finding the most recent equipment log entry with a reading for the
total_hours_key_idfield - Calculating the hours remaining:
next_service - last_log_answer - Converting to approximate days:
hours_remaining / 24
This estimated day count is then used in the same warning threshold logic as date schedules.
Using warning_level in Reporting Views
The stored warning_level value is safe to use for display purposes (dashboards, lists). Keep the following in mind:
- It is a cached value — updated by the background scheduler job, not in real-time
- Works for both default and custom warning schedules — the same
warning_levelfield is written regardless of whether a schedule uses the default thresholds or a custom override; the only difference is that custom schedules only produce levels 1 or 3, never 2 - Hour schedules drift — because equipment hours change continuously, the stored warning level for hour-type schedules may lag behind the actual urgency. For precise reporting, recalculate using current runtime hours
- Window schedules are excluded —
warning_levelis never set for Window schedules; useoperational_actions.active_dateandoperational_actions.due_dateto determine window open/close status, andstatus = 'Delinquent'on the schedule record for missed periods - Past-due detection — for date schedules, you can also derive urgency directly:
next_date < today AND completed = 0 AND active = 1
"Schedule type not appearing in dropdown"
- Check that the schedule type has not been soft-deleted
- Confirm the type's entity setting is compatible with the asset you are scheduling on
- MSAPR classifications are system-reserved — use standard types for general work
"Next due date does not look right after completion"
- Verify the repetition type is correct for the intent of the schedule
- For Static schedules, confirm
repeat_onis set to the anchor day - For Dynamic schedules, the next date calculates from the actual completion date, not the planned date
"Warning level is not updating"
- The warning level is refreshed by a scheduled background job — it will not change instantly
- If a schedule was just completed and a new one created, allow the job to run before the new record shows a warning level
"Hours schedule shows no warning level"
- The schedule requires at least one equipment log entry with a reading for the linked
total_hours_key_idfield - If no log exists, the system cannot calculate hours remaining and will skip the warning level calculation
- Set schedule types before bulk importing - Schedule types must exist before import files are processed
- Use Custom Warnings for critical regulatory schedules - Override defaults on schedules with hard regulatory deadlines to ensure they are flagged at the right threshold
- Use Window type for period-based compliance - Quarterly or annual certifications belong on Window schedules so missed periods are permanently recorded as Delinquent
- Link a reset key when tracking hours-since-service - For equipment where you track run hours since last service separately from total hours, setting the reset key enables accurate log recalculation if a completion is backdated
- Keep descriptions consistent - Descriptions appear in reports and notifications; use a standard naming convention across similar assets
- Window schedules are never flagged overdue — they go directly to Delinquent when missed
- The
warning_levelfield is 1 (red), 2 (orange), or 3 (yellow); null or 0 means no warning active - For reporting, supplement
warning_levelwith a directnext_date < todaycheck for date schedules - Hybrid schedules track both date and hours — either threshold being reached will make the schedule appear due
- Planned dates are informational only and do not change when the schedule becomes due
Remember: Equipment schedules drive field work completion tracking and compliance reporting — correctly configuring schedule type, repetition type, and warning thresholds at setup time avoids data quality issues downstream.