An outfitting status is copied twice before anyone can act on it

Ask three people on a cruise newbuild whether cabin 8042 is ready for its first inspection and you can get three answers. Not because anyone is wrong, but because each of them is reading a different copy of the same fact, written down at a different hour.

That is the problem Sightyard was built for. Sightyard is our own product, developed at Lean Maritime for outfitting control in newbuild and in dry dock.

The status is correct and out of date

The work happens inside the hull. Someone finishes a work package in a cabin, notes it, and carries the note out. The contractor enters it into their system. The yard takes it from there into theirs. Inspection keeps a third list, because the inspection sequence does not match either of the other two.

Each of those steps is defensible on its own. Together they mean the status that reaches a decision is at least second hand. Every copy costs time, and every copy is an opportunity to lose a detail: which work package exactly, which date, whether the defect was closed or only looked at.

The yard is not short of process or discipline here, and the data exists. What is missing is a way to record the fact once, where it happens.

Why the existing tools stop at the gangway

There is no shortage of planning systems in a shipyard, and the good ones are very good. They were designed for an office, where there is a desk, a large screen and a network.

Four decks down inside a steel hull there is usually no usable network at all. The mobile views of office systems assume there is. So the field falls back on what always works offline: paper, a photo on a phone, a list to be typed up later.

The tool has to survive the conditions of the place where the work is done. For outfitting that means offline as the normal state, not as an error case, and a screen that can be operated with one hand while the other holds a torch.

One object, five steps

Sightyard puts capture, inspection, punch and dates on a single object, the space and its work packages, and runs each work package through the same five steps.

Capture is a status with one tap, offline. Check covers progress, quality and the functional test. Inspect covers functional tests, internal inspections and the Pre and First inspections. Punch records a defect with a photo, the fix, and the re-check. Accept is the final inspection and the space is signed.

Punch loops back into fix and a new check until the Final is signed. Every step has an owner and a timestamp, so the question of who said a cabin was ready, and when, has an answer rather than a recollection.

Yard, contractor and owner look at the same status. Not three reconciled versions of it.

Steering the build instead of the list

The three ideas underneath are the ones we use in every project.

Flow means each space runs through the trades in a fixed phase sequence. The cabin train shows six phases as wagons, and the gap between two wagons, in percentage points, is how far a phase has fallen behind the one in front of it. A site manager reading that train sees which phase is slipping, not which cabins are open.

Takt means daily dates, as planned. The baseline stays fixed, the forecast moves, and actuals are measured against both. A forecast that moves while the baseline stays put is the only honest way to show drift.

Pull means each trade takes its next lot from what has been released for it, with blocked spaces and open punch first.

That is the difference between steering the pace of a build and working down a list.

What is live and what is not

We would rather say this plainly than let a demo imply more than it should.

The cabin module is live. It covers cabin outfitting deck by deck and fire zone by fire zone, with three sign-off gates per cabin, in the field and in the site office.

USPH is in beta and works on its own, free for users. Public spaces, machine area, block building and the other disciplines are in beta. On the intelligence side, readiness and forecast are live; what-if and early warning are alpha.

A platform that claims everything is finished is usually describing a roadmap.

Where this comes from

We did not start with a software idea. We started on cruise newbuilds, where we kept watching the same thing: the plan was sound, the people were capable, and the status still arrived too late to act on.

Sightyard is that observation turned into a tool. It runs on the device in your hand, in the space where the work is, and it syncs when there is a connection.

If you want to see it against your own build, request a demo. If you want something you can use this week without a contract, the USPH module is free and needs no login to start.