Yes, but the level depends on the target system.
API/SSO: deeper integration depends on your stack. If you share the names of your PMS, SMS/HSEQ, ERP, and reporting tools, we’ll confirm what is available now and what would need a small integration sprint.
Simple link/workflow: we embed links from the twin to PMS tasks, HSEQ records, or documents and back. This works immediately.
File exchange: we attach PDFs, procedures, photos, and model snippets to locations in the twin.

Currently, Mari-Twin operates as a hosted platform, which means access to the interactive twin is tied to an active licence — this covers server costs, storage, updates, and viewer access across departments.
However, we understand that long-term data ownership and continuity are critical, especially in maritime. So here’s how we handle it clearly:

• You always retain ownership of the source scan data (E57/point cloud files)
• If you need a fully offline export for regulatory, legal, or long-term asset retention reasons, we can provide a structured export package, and will work with your digital team to ensure long-term compatibility.
• If a licence ends, will maintain the Twin on our servers for a further 6 months to prevent unnecessary data loss.

Yes—as a spatial context layer.
The twin provides location truth, access paths, and equipment context. That makes future AI or sensor outputs easier to interpret and act on. Live telemetry is not required for value today, but if you later add sensors or analytics, the twin can serve as the spatial UI to surface it. If you have a roadmap for CBM or analytics, share it and we will map how the twin fits.

Yes—by improving scope certainty before commitment.
Teams use the twin to verify access, envelopes, routes, lifting paths, and tie-ins before dock. This cuts late discoveries that trigger variation orders. We can review one planned retrofit with your team and mark the exact checks we would run inside the twin. That gives you a clear “with vs without” view.

Today we support per-vessel twins with enterprise viewing.

• One twin per vessel.
• Organisation-wide viewer access so departments are not gated.
• Options for editor seats are limited to the teams who need to curate tags, POIs, or notes.
• Storage/hosting scales with data size.

If you prefer a fleet licence with predictable cost across many vessels, we can price that. Tell us vessel count today, expected adds in the next 12–24 months. We will propose both per-vessel and fleet rates so you can choose.

• For most vessels, a full capture typically takes 4–6 days onboard, even when scanning at sea. In many cases, sailing conditions are actually more efficient to work in as there is less congestion and fewer competing work parties than during a shipyard period.

• Once scanning is complete, we begin processing immediately. Depending on the vessel’s scale and deliverables, the digital twin is usually accessible within 3-4 weeks. If you need rapid turnaround for engineering or yard planning, we can fast-track priority areas while the rest of the twin is being finalised.

• Fewer site visits and travel: engineers resolve more questions from shore.
• Faster planning: less time spent chasing drawings and photos.
• Reduced rework: clashes and access issues are spotted earlier.
• Crew readiness: fewer onboarding delays and fewer basic “where is it?” calls.
• Audit prep: HSEQ teams review spaces remotely and arrive prepared.