MMV Offline has to work reliably in an environment MMV doesn't fully control — vessel hardware, vessel network, vessel bandwidth, other software the vessel runs. This article explains the challenges and the rules MMV puts in place to minimize failure.
Why offline is harder than online
Once a vessel has offline capability, they can work either online (with internet access) or offline (over the vessel's Local Area Network). Crew simply want the system to work either way. What's often not realized is that MMV can only fully control the online cloud version — that software and data live on MMV's own servers in controlled IT centers.
An offline installation sits on the vessel's server, in the vessel's network. This creates several inherent challenges for MMV and the management company:
- MMV doesn't control the hardware. The vessel or its contractors may make hardware changes without notifying MMV, which can alter the environment and cause the system to fail in various ways.
- MMV doesn't maintain the vessel's operating system. We don't know when (or whether) OS updates and patches are being applied correctly, or how much memory or disk space is available.
- MMV doesn't control the vessel's bandwidth or LAN. If the vessel's own network has issues, users onboard can't access MMV Offline.
The rules MMV enforces to reduce risk
To minimize the chance of failure or issues onboard, MMV requires the following:
- The offline version must be installed on a dedicated PC or VM with no other software running on it. See minimum system requirements.
- MMV must retain remote access via LogMeIn only. Granting an offline install grants perpetual permission for MMV to log in for support and updates.
- The dedicated machine must remain powered on and connected to the vessel's LAN and internet at all times. It cannot be shut down or disconnected.
- The vessel must have a qualified IT person onboard to install the PC on the vessel's network and maintain it. MMV will not proceed without this technician's verification.
What happens when things go wrong
If an issue is caused by something under MMV's control — the offline application code itself — MMV fixes it under the monthly support fee.
If an issue is caused by something under the vessel's control — hardware problems, internet connectivity, unauthorized changes to the MMV server — MMV can still help resolve it, but that work is billed separately. See Offline Support & Re-Installation Costs.
Common questions
What if our vessel's internet goes down for an extended period?
The offline client keeps working — that's the whole point. When connectivity returns, sync automatically catches up. But if the vessel is unsynced for six months, the system loses the ability to sync automatically and requires a re-install (see the Offline Sync Inactivity article).
Can we run other software on the dedicated MMV server?
No. The server must be dedicated to MMV Offline. Running other software increases the risk of conflicts, resource contention, and instability — and voids MMV's support terms for that install.