What we do — and how we do it.

Most manufacturers don't have a data problem. They have a connection problem. The data exists — in CAD systems, PLM platforms, ERP, MES, CPQ tools — but it doesn't flow. Every system boundary is a handoff point where information gets recreated, simplified or lost entirely.

We start by mapping the current system landscape: what exists, what it contains, how it connects today, and where the breaks are. Then we design the target integration architecture — the right tool for each integration type, the right data objects, the right transformation rules — before any implementation begins.

Henry was among the first to implement eMatrix PDM (now Dassault ENOVIA) in Finland and built the Finnish integration practice around Boomi. That foundation — knowing both the PLM domain and the integration tooling at depth — is what allows us to design architectures that actually hold up in production rather than becoming maintenance burdens.

We cover the full stack: PLM to ERP (SAP, IFS Cloud), PLM to CPQ, MES integration, CRM connectivity, and the installed base layer that ties operations to the service organisation. Where needed, we work alongside implementation partners — but the architecture and the critical design decisions stay with us.

This is often the unglamorous core of a digital transformation. The PLM platform gets selected, the ERP gets upgraded, the integration gets built — and then the project stalls because nobody agreed what a material master actually is, or who owns the EBOM, or how as-installed data differs from as-designed.

We define what lives where, who owns it, how it flows, and how changes are managed. That means data ownership matrices, RACI frameworks, BOM strategies (EBOM, MBOM, SBOM, As-Built, As-Maintained), classification structures, lifecycle state definitions, and the governance processes that keep everything consistent over time.

Markus built the data management systems at a global telecommunications equipment manufacturer covering mechanical design, electrical design and simulation — three separate domains, each with its own data model, connected into one coherent backbone. That experience of designing data governance at scale, under real engineering pressure, is what we bring to every engagement.

We have done this work across SAP (including clean-core Z-table retirement), Dassault 3DEXPERIENCE, Siemens Teamcenter, ARAS, COMOS and IFS Cloud. We understand the constraints of each platform and how to design a data model that works within them — not just on a whiteboard.

The data is there. After years of running PLM, ERP and CRM systems, most manufacturers are sitting on a substantial body of product, customer and operational information. The problem is that it is spread across systems, inconsistently structured, and never assembled into a form that a business leader can actually use to make a decision.

We design the analytics layer that sits on top of your existing data sources — pulling from PLM, ERP, field service, installed base — and presents the information in a way that reflects how your business actually works. That means understanding the meaning of the data, not just its format. What does a service interval mean for this product family? Which assets are approaching end of warranty? Where is aftermarket capture rate lowest, and why?

This work led directly to Clientry — our Salesforce-native product that turns installed base data into proactive service sales opportunities. The same thinking applies to bespoke analytics work: we start from the business question, not the data schema.

Shipbuilding is one of the most demanding PLM environments in manufacturing. The product is unique per project. The engineering data spans hull, outfitting, piping and electrical across multiple CAD systems. The manufacturing execution layer — cutting, nesting, production sequencing — runs on specialist tools that most PLM consultancies have never worked with.

Teemu has worked at the intersection of all of these. Cadmatic — including their next-generation Wave platform — for 3D design and information management. Aveva Nestix for production planning, nesting and cutting in the shipyard. PLM as the backbone connecting design, production and the project lifecycle. And ERP as the financial and procurement layer underneath.

For clients outside the marine sector, we bring the same delivery capability to PLM implementation programmes — requirements definition, process design, configuration, data migration, training and go-live support — working across Dassault 3DEXPERIENCE, Siemens Teamcenter, ARAS and other platforms.