Information Management System, K-IMS

Common issues

• Data gaps from lost connectivity between sensors/PLCs and the K-IMS server
• Server storage filling up when data retention/archiving is not configured correctly
• Dashboard or tag configuration drift after equipment changes are not updated in the system
• Network latency or bandwidth limits affecting shore connectivity features
• Software update failures needing manual intervention on server or client

Inspection checklist

• Verify data logging is current with no unexplained gaps
• Check server disk space and backup job status
• Confirm alarm and dashboard configuration matches the current equipment list
• Test failover/backup connectivity to shore where fitted
• Review the user access list and account hygiene
• Verify server room cooling and UPS status if the server is onboard

Service intervals

Typical intervals for this design class, not the manufacturer’s figures for your model. The manufacturer’s manual is binding.

Critical spares

• Spare server-grade hard drive/SSD matching the installed unit's specification
• UPS battery for the server, if a dedicated UPS is fitted
• Network switch matching the installed onboard network, sourced through the ship's IT supplier rather than assumed generically

Safety

• Cyber security: K-IMS connects operational data to shore-side networks - unmanaged remote access is a safety and security risk
• Do not let onboard decision-making depend solely on a system that is not itself class-approved as a safety system unless specifically notated
• Loss of data logging during an incident can compromise investigation and compliance records

Class survey

Where K-IMS supports statutory or class recordkeeping (e.g. condition monitoring), class expects the data to be retrievable and consistent with survey requirements; the platform itself typically does not carry a machinery class notation.