Danaos

Why Shipyard Automation Needs More Than IIoT Connectivity

A shipyard supervisor discusses changing work with a ship owner representative beside a vessel under refit

The cover is an AI-generated editorial illustration; it does not depict a real shipyard, customer or employee.

A shipyard is full of automation opportunities. Programmable logic controllers (PLCs), supervisory control and data acquisition (SCADA), manufacturing execution systems (MES), sensors and industrial internet of things (IIoT) platforms can monitor equipment, capture machine data and help teams control repeatable processes. Platforms such as AVEVA’s industrial software, Ignition by Inductive Automation, and Siemens’ digital manufacturing portfolio are examples of technologies used across industrial environments.

The challenge is not that these tools cannot be useful in a shipyard. It is that connectivity and machine control do not, by themselves, coordinate the changing work of a shipyard project. Treating an automation layer as the complete operating model can leave a dangerous gap between what the equipment reports and what the project team, workshop and ship owner need to decide next.

Shipbuilding & repair

Why is a shipyard different from a repetitive production line?

A shipyard may build a vessel, repair it, convert it, or carry out a time-critical dry-docking campaign. Each job has its own scope, vessel condition, contract, sequence, constraints and acceptance requirements. Even sister vessels can diverge once inspection exposes hidden damage or the owner requests a modification.

Work moves across docks, berths, workshops, stores and specialist subcontractors. Structural work, piping, electrical systems, machinery, coatings, inspection and commissioning compete for people, space, lifting equipment and access. A change to one task can affect several trades and the next handover. The production environment is therefore project-based and interdependent, even where some individual processes are highly automated.

Shipbuilding & repair

Where does connectivity stop being enough?

Industrial automation is often strongest at connecting assets and observing or controlling defined processes: a machine state, alarm, production count, temperature, equipment cycle or work-centre status. Those signals matter. But a signal does not automatically answer the project questions around it:

  • Which vessel, contract, work package and approved scope does this activity belong to?
  • Has the owner approved the work, and which revision is now valid?
  • What trades, materials, permits, inspections and access windows depend on it?
  • Who needs to be told, and what should happen to cost, schedule and forecast?
  • Is the crew working to the latest drawing and method statement?

These questions need shared operational context and controlled decisions. A SCADA screen may show that a pump is running; it does not necessarily show whether that pump test is a contractual hold point, whether the owner’s representative has witnessed it, or whether a late change has made the test sequence obsolete. An IIoT platform can carry data between systems without establishing one reliable, approved version of the job.

Shipbuilding & repair

How does operational chaos build on the shop floor?

The gap becomes visible when daily plans meet reality. An inspection discovers corrosion behind a plate. The ship owner asks for a modification. A drawing revision arrives after fabrication has started. A specialist team is delayed, a crane slot moves, or a repair uncovers another dependency.

If the change is handled through scattered messages, calls, spreadsheets and paper mark-ups, the workshop may keep working from old priorities. Materials can be issued against superseded scope; supervisors may resequence work without a shared view of knock-on effects; and planners, commercial teams and the owner may each hold a different status. People on site then spend time reconciling instructions instead of executing the approved work. The result is operational disorder: avoidable waiting, rework, congestion and disputes over what was agreed.

More sensors will not resolve this by themselves. Better visibility helps only when the information is tied to the project, translated into an actionable work status and delivered to the people who must coordinate the response.

Shipbuilding & repair

Why must the shipyard and owner communicate frequently?

Frequent, structured communication with the ship owner or the owner’s agent is a control mechanism. It helps both sides surface condition findings, clarify intent, assess impact and decide whether a proposed change is approved before the yard commits more labour or material.

A practical change path records the request, the affected vessel and work package, supporting evidence, cost and schedule implications, technical review, approval authority, decision and revised instructions. The yard can then update the work plan, documents, procurement needs and forecast from the same decision. Urgent safety or operational issues still follow the shipyard’s established escalation process; a digital workflow should support that process, not delay it.

The goal is not to ask the owner to approve every routine task. It is to make material changes visible, traceable and timely, with clear responsibilities on both sides.

Shipbuilding & repair

What should a shipyard operations model connect?

A shipyard needs layers that work together:

  1. Automation and control: PLCs, SCADA, sensors, equipment systems and specialist applications perform or monitor defined technical processes.
  2. Project and production coordination: work packages, priorities, labour, materials, access, inspections, progress and dependencies are managed against the vessel and contract.
  3. Commercial and owner change control: requests, evidence, decisions, approved scope, cost and schedule impacts remain linked to the work they affect.
  4. Enterprise control: procurement, inventory, cost control, finance, document control and reporting use consistent project information and permissions.

This is where a project-centred enterprise resource planning (ERP) system can complement automation. ProjectVIEW ERP is designed to support project operations and business processes such as cost control, procurement, materials, machinery, finance and document management. It is not a replacement for safety-rated control systems or a claim that every machine should be operated from an ERP. The integration design should define which system owns each record and which events or approved statuses need to cross the boundary.

ProjectVIEW AI can be considered as an assistance layer where verified project data is available. For example, an AI workflow could compare a proposed change with the affected work packages, material requirements and schedule records, then prepare an impact summary and draft questions for review. The project and commercial leads would validate the evidence and approve consequential changes; the AI should not silently revise an approved scope or issue work instructions on its own.

Shipbuilding & repair

Where does this lesson apply beyond shipyards?

The same distinction matters in construction, where site conditions and design changes affect trades; marine and offshore projects, where weather windows and vessel access constrain work; mining and quarrying, where maintenance and production plans compete for equipment; and project-based manufacturing or fabrication, where engineered orders vary and revisions can reach the shop after work begins. In each case, connectivity is valuable, but operations also need project context, change governance and clear ownership of decisions.

Shipbuilding & repair

What should shipyard leaders ask before buying automation?

Ask vendors and integrators to demonstrate a real change scenario, not just a dashboard. Follow a defect or owner request from initial evidence through technical review, approval, work-package revision, material impact, schedule update, site communication and commercial forecast. Test what happens when the work is already in progress, when approval is delayed, and when teams lose connectivity.

Also ask which platform owns each data item, how revisions are controlled, how site users receive current instructions, what is synchronized with the owner or agent, and what remains a human decision. Define the operational process first; then connect the right automation, project and enterprise systems to it.

FAQ

Frequently asked questions

Are AVEVA, Ignition or Siemens systems unsuitable for shipyards?

No blanket conclusion follows from the product names. These vendors offer industrial technologies that may serve useful roles, and their portfolios differ. The concern is relying on connectivity, control or production data alone to coordinate project scope, owner approvals, changing priorities and commercial impacts. Assess each product, configuration and integration against the shipyard’s actual workflow.

Does a shipyard need IIoT?

IIoT can help collect and share equipment and process data. Its value increases when that data is connected to the correct vessel, work package, responsible team and decision process. IIoT is one part of the operating model, not the whole model.

How should a shipyard handle an owner change request?

Record the request and evidence, identify affected work, assess technical, cost and schedule impacts, obtain approval from the authorized parties, and issue the revised instructions to the teams doing the work. Keep the decision linked to the relevant project records.

What role should ERP play beside shipyard automation?

ERP can coordinate project, procurement, inventory, cost, finance and document processes around the vessel and contract. It should complement dedicated machine-control and safety systems through explicit integrations and clear data ownership.

Shipbuilding & repair

Build the operating model around the work

Shipyards need industrial automation, but they also need a reliable way to organize project work as conditions and approved scope change. IIoT can connect the yard. A project-centred operating model helps people understand what the data means, what work is authorized, who needs to act and how a change affects the wider job. That connection between technology, project control and frequent owner communication is what keeps a dynamic shipyard from becoming a collection of disconnected signals and competing instructions.

Discuss shipyard project operations

About the author

Eng. Vassilis Sakorafas

Chief Technology & Innovation Officer, DANAOS Projects

Eng. Vassilis (Bill) Sakorafas is Chief Technology & Innovation Officer at DANAOS Projects and a subject-matter expert in enterprise software architecture, cloud-native platforms, systems integration and data security. With more than 15 years of experience designing and developing enterprise business applications, he directs the continuous development of ProjectVIEW ERP and all DANAOS Projects software, sets the company's technology vision and…

Search or Ask AI