Maintenance schedule
Preventive maintenance that is planned in the system, assigned to a person and logged when done.
The problem
Preventive maintenance usually lives in a wall calendar, a supervisor's notebook or a spreadsheet nobody opens after the first month. Tasks slip, nobody knows which machine was last serviced, and the first sign of a missed service is a breakdown in the middle of a production run.
How it runs in Sundial
1. Start from the asset register. Every machine, vehicle or tool is an asset in Assets & Maintenance, with its location, custodian and purchase details.
2. Create a maintenance plan for the asset. List the tasks (oil change, belt inspection, calibration), how often each one repeats (daily, weekly, monthly, quarterly, yearly) and the start date.
3. Assign each task to a person or a maintenance team. Sundial works out the next due date for every task and keeps it on that person's list.
4. When the work is done, the technician records a maintenance log entry against the task: date, status, notes and any findings. The next due date rolls forward on its own.
5. If the inspection finds a fault, raise an asset repair from the same asset, so the corrective work, its cost and the downtime are tracked separately from routine service.
What the team sees
Maintenance managers see every task due this week and every task overdue, by asset and by assignee. Technicians see their own list on desktop or phone. Finance sees the asset's full history next to its book value and depreciation, so a decision to repair or replace starts from facts.
Sample view for Kestrel Workspace: 42 assets under plan, 9 tasks due this week, 2 overdue, last service date shown on every asset card.
With AI (coming to Sundial)
Sundial is built for an agent to read the maintenance logs and repair history, notice that the same pump has failed twice after its quarterly service, and suggest a shorter interval for a person to approve. That capability is on the roadmap, not in the product today.

