Predictive Maintenance for Phinisi and Fast Boat Operations
Move from reactive repair to planned reliability with engine-hour based servicing, failure pattern tracking, and route-aware spare-part coverage.
Status: Production-ready for preventive workflow, reliability KPI close, and engineering review cadence.
Operational scope
Qail Maintain helps fleet teams standardize reliability work across multiple vessels, routes, and engineering shifts.
Preventive work-order cycles
Schedule tasks by engine-hour and calendar; enforce completion evidence before the next dispatch window.
Failure and incident taxonomy
Capture failure mode, subsystem, root cause, and route context so recurring issues are visible at fleet level.
Critical-parts coverage
Set min/max thresholds by vessel class and route risk, then alert before stockouts threaten departures.
Reliability governance
Run weekly engineering close with open backlog, overdue critical tasks, MTBF trend, and readiness for peak periods.
Core KPIs and formulas
| KPI | Formula | Use |
|---|---|---|
| Preventive compliance rate | Completed preventive tasks / scheduled preventive tasks | Detect backlog risk before dispatch impact |
| MTBF (hours) | Operating hours / failure events | Reliability trend by vessel and subsystem |
| MTTR (hours) | Total repair duration / repair incidents | Repair execution and part availability signal |
| Dispatch reliability | On-time departures / planned departures | Commercial service-level metric |
| Critical stockout rate | Critical part stockout events / period | Procurement and planning effectiveness |
Target profile for mature operations: preventive compliance >= 95% and critical stockout rate = 0 on active routes.
Data contract (minimum fields)
Asset and service registry
- vessel_id, subsystem, component, serial_no
- service_interval_hours, service_interval_days
- criticality_level, route_group
Work order and incident events
- wo_id, wo_type, opened_at, due_at, closed_at
- failure_mode, root_cause, downtime_minutes
- parts_used, labor_hours, verification_status
30-60-90 rollout
0-30 days
Standardize taxonomy, onboard asset registry, and close first preventive cycle for one pilot vessel group.
31-60 days
Turn on MTBF/MTTR dashboard, run weekly reliability review, and enforce critical-part threshold alerts.
61-90 days
Expand to full fleet, measure dispatch reliability uplift, and publish quarterly maintenance ROI report.
Pilot success thresholds
- Preventive work completion >= 90% in first 8 weeks
- Overdue critical work orders <= 2% of open backlog
- Root cause filled on 100% of breakdown incidents
- Critical route dispatch cancellation from technical issues trending down