Skip to content

Schedules & due dates

SUPERINTENDENT Schedules drive when a job card is "due."

Frequency types

  • Running hours — interval in hours (e.g. every 500 hr); requires the parent component to have a running-hour counter
  • Calendar interval — days / weeks / months / years
  • Either-or — first to trigger fires the job

Each job card has its own frequency. The next_due column is auto-computed: last_done + interval, or, for running hours, last_done_rh + rh_interval against the latest counter reading.

Due / overdue logic

  • Due = next_due ≤ today + grace_window (typically 30 days)
  • Overdue = next_due < today

The dashboard ring "Jobs due / overdue" reflects these counts. Filter by department or by vessel.

Bulk reschedule

If a vessel goes into dry-dock and you want to defer non-critical jobs by N days:

  1. Schedules → Filter to that vessel + non-critical
  2. Tick the rows
  3. Bulk reschedule → set new next_due or shift by N days

This creates a batch of drafts; the supervisor batch-approves.

RAPAX PMS Help · v2.31.0.26 · released 2026-04-28