Skip to content
olyzono
OLYZONO - CASE STUDY · MARINE TECHNICAL SERVICES

Know where every ship is. Never miss a job. Spend less getting there.

A marine technical-services firm services galley and laundry equipment on cruise ships - precise, specialized work, run by three people. The operation was spreadsheets and gut feel. We built the purpose-built system that runs underneath it.

Live
RUNNING ON REAL FLEET DATA
The client

A young marine technical-services firm doing precise, specialized work: keeping the ovens, dishwashers and laundry running on cruise ships, so three thousand guests never think about them once. That invisibility is the highest form of the craft.

The whole operation runs on three people and ships that never stop moving. The technical work is excellent. The operation around it - finding where a ship will be, what's due, how to get there - was manual.

The problem

Three people. Ships that never stop moving.

To plan a single visit, someone finds where a ship will be, cross-checks it against what's due, then guesses at flights and hotels. It works - but it's slow, it lives in one person's head, and it doesn't scale. The quiet risks add up:

  • A ship slips past. It calls at a port you cover, on a day you could have serviced it - and you find out too late.

  • A deadline is missed. An inspection or service window passes. With cruise hygiene and compliance, that is not a small thing.

  • Money leaks on travel. A trip booked late or routed badly costs hundreds more than it had to - every time.

  • It's all manual. Growth means hiring office help just to keep up - not doing more technical work.

A precise technical firm deserves precise operations. That's the gap we close.

The work

A system that tells you what to do.

We built a purpose-built operational system around how the firm actually works - not a generic dispatch tool. It always knows where every ship will be, what's due and when, and the cheapest way to get a technician on board in time.

Fleet calendar

One always-current screen showing where every covered ship is, every day - replacing the manual spreadsheet, never out of date.

Equipment & due-date tracker

Each ship's equipment and service intervals recorded; the system flags what's due and how urgent - so a window never slips.

Cheapest-trip planner

Pick the ships; the system builds the lowest-cost route - which port to catch each ship, fly vs drive, hotel nights - with the full cost laid out.

Heads-up alerts & automatic reports

An alert the moment a due ship is reachable at a port you cover. Inspection reports generated from the job's data - minutes, not hours.

It already works. The foundation is built and running on live cruise data today - the fleet calendar and the trip planner that builds the cheapest route to service a set of ships. Not a blank page; a system being shaped around a real operation.

FLEET CALENDAR · WHERE EVERY SHIP WILL BE
SHIP ASHIP BSHIP CSHIP D JUN 08 JUN 09 JUN 10 JUN 11 JUN 12
CHEAPEST ROUTE · 4 SHIPS · ONE TRIP
The result

A week of planning, done in minutes.

The system is a live build running on real fleet data. The projected savings below are illustrative and conservative - to be confirmed on the client's real numbers as it goes fully live.

Live
Running on real fleet data

The fleet calendar and trip planner are built and running on live cruise schedules today

€400–600
Trimmed per technician trip

Smarter routing and combining ships - illustrative, to be confirmed on the client's real numbers

3
People, freed for the real work

A lean technical team back on equipment, not spreadsheets and flight searches

One missed inspection or lost contract costs more than a whole year of the software. The math isn't close.

What this proves

Different industry. Same belief, same method.

A fragrance brand and a marine technical-services firm share no tools, no channels, no vocabulary. What they share is the operator whose skilled hours leak into manual work - and the belief that operators should spend their hours on the work only they can do.

The system looks completely different - a unified portal there, a fleet-planning system here. The method is identical: build around how the operation actually runs, build it to be left in the operator's hands, weave the automation through where it earns its keep. That's what makes the pattern travel.

Client named privately; published anonymized pending written permission, per our case-study standard. Figures marked illustrative are conservative estimates to be confirmed on the client's real numbers.

If your operation runs on spreadsheets and gut feel - like this one did - building your operational backbone with olyzono is the right decision.