Cadmatic Podcast

In 2016, Ulstein Verft asked its own people what slowed them down. Their answers pointed to a single source of truth for drawings, parts and the knowledge that often sat with people rather than in a system.

In this episode of Cadmatic Data-Driven Shipbuilding, Gaute, head of PLM at Ulstein, and Evgeny, PLM project manager at Cadmatic, talk about Ulstein’s move to Cadmatic Wave. Connecting PLM to Ulstein’s Cadmatic design tools was key, along with a data model that treats the ship as one connected object. Changing systems in the middle of a live project is risky, so Ulstein is starting with new vessels and bringing older data in step by step. You’ll also hear how the team got through user acceptance testing while delivering a large vessel, and why staying close to the standard product makes future upgrades easier.

Gaute’s advice to other shipyards: treat it as a change in how you work, and give it time.

What does it take to make PLM work for the people who use it every day? In this episode of Data-driven Shipbuilding, Beatriz Gonzalez from Share PLM and Ankit Talati from Cadmatic discuss the human side of PLM in shipbuilding. They explore why technology alone is not enough, how change management and user involvement support adoption, and what the Cadmatic and Share PLM partnership brings to successful PLM projects.

SARC's customers have wanted to reuse their early design data in later stages since the 1980s. In this episode, Cadmatic's Evgenii Egorov talks with Herbert Koelman of SARC and NHL Stenden, and Diego De León of NHL Stenden, about the SEUS project. SEUS connects SARC’s PIAS software, Cadmatic, and a PLM platform, enabling ship data to move seamlessly between design phases - and back again. Key topics in this episode:

• One clear data flow between PIAS and Cadmatic
• Why the reason for a design change must travel with the data
• Machine learning checked by engineering calculations
• Faster layout options for alternative fuels such as methanol
• Shipyard feedback from Ulstein and Gondan
• What comes after SEUS

Large electrical projects bring a different kind of pressure. More engineers, more data, more changes, and far less room for error.

In this Product Insights episode, our specialists Antto Heino and Niko Liimatainen explore how smarter electrical design helps teams stay in control as projects scale. The discussion looks at common challenges in large projects, from managing complexity and consistency to keeping teams aligned over long timelines.

You’ll hear how structured data, shared ways of working, and scalable design practices support smoother execution and more predictable outcomes in large electrical projects.

A practical listen for electrical engineers and project teams working on complex designs in shipbuilding or construction.

How do shared engineering environments actually work in complex plant projects? 

In this episode, Nicklas Eriksson from NIER explains how engineering teams collaborate in one environment using master–replica architecture. Learn how projects are set up, how multiple companies work in parallel, and how controlled libraries and standards improve consistency and reduce errors. 

NIER is a trusted engineering consultancy focused on plant digitalization and complex project delivery. They help Swedens biggest owner-operators to set up and run shared Cadmatic environments, enabling large-scale collaboration while ensuring full control of engineering data from design through operations. 

Key topics in this episode: 

• Faster execution through efficient workflows  

• Fewer procurement and construction issues  

• Reliable, structured data for operations 

Just as a neighborhood becomes safer and more connected when people can see what’s happening around them, projects benefit when information is visible and accessible to everyone who needs it.In this episode, we explore the idea that “the streets have eyes” in the digital world: more eyes mean fewer blind spots. We discuss how human expertise, shared visibility and digital twin technology can break down information silos, create shared ownership, and help teams spot issues before they become problems.Discover how a digital twin can become a shared space where people across engineering, production and operations explore information in context, collaborate with greater confidence, and make better-informed decisions.

Keeping teams in sync isn't easy when disciplines, phases, and companies all move at different speeds. In this episode, Markus and Jim unpack where collaboration really breaks down on process plant projects – and what closes the gap.

Key topics in this episode:

• Why silos and shifting information cause misalignment
• Collision control and shared 3D data between disciplines
• Managing the engineering-procurement "delta"
• Realistic progress tracking vs. optimistic status reports
• Change management and traceable markups (eShare)
• Why data handover should start on day one, not at the end

What happens when owner-operators take control of their engineering data from day one? 

In this episode, Nicklas Eriksson from NIER shares how data ownership is changing plant projects. Learn why traditional project setups lead to fragmented data and how a shared engineering environment improves transparency, collaboration, and long-term value. 

NIER is a trusted engineering consultancy focused on plant digitalization and complex project delivery. They help Swedens biggest owner-operators to set up and run shared Cadmatic environments, enabling large-scale collaboration while ensuring full control of engineering data from design through operations. 

Key topics in this episode: 

• Better decision-making through owner-controlled data  

• Smoother handover from project to operations  

• Continuous digital twin development across the lifecycle 

What happens when you own your engineering data from day one? 

In this episode, we explore how owner-operators take control of engineering data across the full project lifecycle. 

Gian Mario Tagliaretti shares how a new approach replaces isolated workflows and milestone-based reviews with continuous access, visibility, and collaboration. 

We cover how Cadmatic enables this through a shared engineering setup that connects design, data, and teams from start to finish. 

You’ll hear how this approach helps teams: 

• stay in sync across multiple contractors and disciplines  

• reduce rework by identifying issues earlier  

• review and validate progress without waiting for 30, 60, or 90 milestones  

• build a digital twin that evolves alongside the project  

  
  

The big idea: Owning your data from day one keeps projects moving, reduces risk, and ensures your engineering data stays usable long after delivery. 

In this podcast episode, we talk with Paul Empringham from Enable ITAM and Maurits Schmidt, Strategic Transformation Director at Cadmatic, about how engineering software licensing has shifted over the past decade and where it is heading. Paul brings an independent view from his work helping engineering companies optimize and rationalize their licenses across sectors. Maurits shares the thinking behind Cadmatic's new primary subscription licensing model, Cadmatic One License, and how it was designed to match the way engineering teams actually work.

Key topics in this episode:

• The perpetual licensing era: concurrent pools, the two-thirds rule, and why niche modules were always a utilization problem.
• The subscription shift: from CapEx to OpEx, the rise of bundles and named users, and where the friction came from.
• Why consumption and credit-based token models did not fully solve the problem, and what a returnable token pool does differently.
• How the Cadmatic project lifecycle – with hull design, outfitting, and information management peaking at different phases – shaped the COL model.
• What a low-risk transition to Cadmatic One License looks like for existing customers, including hybrid options and maintenance license credits.
• Where licensing in industrial software is heading, and what customers on maintenance licenses should do first if they are curious about COL.