ERP for seaports is often built disconnected from the equipment-maintenance system, under the implicit assumption that vessel-arrival scheduling and crane-maintenance scheduling are independent matters, only needing manual cross-checking when a conflict arises. In reality, both schedules compete for the same scarce resource — the Ship-to-Shore crane — and a single unplanned crane failure can halt more than 2,000 container moves, triggering berth-delay penalties. When the vessel/berth scheduling system doesn't know which crane is inside a preventive-maintenance window, or is showing an early-warning signal from vibration monitoring, the decision to assign a crane to an incoming vessel gets made without full information.
This is the core break point: the ERP/port operating system needs a single source of truth for real-time equipment status — not the administrative "maintenance ticket closed" status, but the equipment's actual operating state at the exact moment a scheduling decision is made.
Why "Temporal Asymmetry" between SCADA and CMMS directly affects scheduling decisions
There's a meaningful time gap between the moment SCADA registers a crane as "back to normal running" and the moment a technician administratively closes the work order in the CMMS. If the vessel/berth scheduling system reads equipment status from the CMMS (administrative status) rather than SCADA (real operating status), it may still treat a crane as "under maintenance" while it's actually ready to run — wasting crane capacity unnecessarily. Conversely, if the scheduling system trusts the SCADA "running normally" signal while ignoring that the post-maintenance safety sign-off hasn't been closed yet, a crane could be assigned to a vessel schedule before it's genuinely cleared to operate safely.
ERP for seaports: 2 common scheduling break points
Break point 1 — Preventive-maintenance schedule (MMBF/MTTR) never reaches the vessel scheduling system
The Hutchison Korea Terminal metric framework builds Mean Movements Between Failure (MMBF) and Mean Time to Repair (MTTR) as real reliability measures grounded in actual operating data — enabling a reasonably accurate forecast of when a specific crane is likely to need preventive maintenance based on moves already performed. But if this metric only lives inside the maintenance system and never reaches the vessel/berth scheduling system, the scheduling team has no basis to avoid assigning a crane nearing its preventive-maintenance threshold to a large vessel call, extending handling time.
Break point 2 — Early-warning signals from vibration/oil monitoring can't block a crane assignment
Vibration sensors and oil analysis can detect early degradation signs — bearing wear, gear wear — before an actual failure occurs. But if that early-warning signal only appears on an equipment-monitoring dashboard with no automatic block or flag inside the scheduling system, a crane with a clear warning sign can still get assigned to a peak-demand shift — exactly when the risk of an unexpected failure is highest.
The scheduler's lens: what conditions need to be met before assigning a crane to a vessel call
Before assigning a specific crane to handle a vessel call, an ideal scheduling team needs to know: whether the crane is currently inside a preventive-maintenance window per the MMBF schedule, whether there's an unresolved early-warning signal from vibration/oil monitoring, and whether the real operating status per SCADA matches the "ready" status in the maintenance system. When these three data sources sit scattered across separate systems, the scheduling team has to cross-check manually under vessel-handling time pressure — exactly the kind of decision most likely to get missed when the vessel schedule is packed.
Illustrative scenario: closing the gap between maintenance schedule and vessel scheduling
This is an illustrative scenario for a common type of problem in the industry, not a specific case from any named port: a container terminal assigns cranes to vessel calls based purely on crane availability in the scheduling system, without cross-checking against the preventive-maintenance schedule maintained separately in the CMMS. A crane nearing its MMBF threshold (expected moves before needing maintenance) still gets assigned to a large vessel call, and mid-shift the crane has to stop unexpectedly for emergency maintenance — delaying the entire vessel's handling schedule. After the scheduling system is connected to read real-time MMBF data from the CMMS, cranes nearing their maintenance threshold are prioritized for smaller vessel calls or scheduled for preventive maintenance before the next large vessel arrives.
Reference table: data source — signal — scheduling impact — system link
| Data source | Signal to read | Scheduling decision impact | System link |
|---|---|---|---|
| CMMS — MMBF/MTTR metrics | Crane approaching preventive-maintenance threshold | Avoid assigning a near-due crane to a large vessel call | Push MMBF metric in real time to the scheduling system |
| Vibration/oil monitoring | Early degradation warning signal | Flag at-risk cranes before peak-shift assignment | Automatic alert surfaced inside the scheduling system |
| SCADA — real-time PLC status | Whether the crane has actually resumed running | Avoid wasting capacity from misread administrative status | Direct sync, bypassing CMMS ticket-closed status |
| Post-maintenance safety sign-off | Whether fully signed off or not | Blocks vessel assignment until sign-off is complete | Scheduling system checks sign-off status before confirming |
Conclusion
"A good seaport ERP/scheduling system isn't the one that assigns a crane to the next vessel fastest — it's the one that knows which crane shouldn't be assigned, based on real-time maintenance signals."
Three things worth doing this week if you are evaluating or running a scheduling/ERP system for a seaport:
- Check whether the scheduling system reads real-time MMBF/MTTR metrics from the CMMS, or maintenance and vessel schedules still run as two disconnected systems.
- Confirm whether early-warning signals from vibration/oil monitoring get pushed into the scheduling system as an alert flag, or only display separately on an equipment dashboard.
- Review a few recent crane assignments: has a crane nearing its MMBF threshold ever been assigned to a large vessel call? If so, that's the break point to close first.