The challenge

All requirements — including standards for asset data and systems engineering — were managed in Excel in a non-standardised way. This made it extremely difficult to track which requirements were applicable to a given project, monitor progress, and maintain consistency across engagements. Every new project involved significant manual setup, duplication of effort, and the risk of diverging structures between teams.

The goal was to design a scalable setup that reduced duplication, improved consistency, and made it significantly easier to start and manage new projects in a controlled, repeatable way.

What I built

I designed and implemented a Relatics setup consisting of a central library workspace and separate project workspaces. The library workspace acts as the authoritative source for reusable templates, reference data, and standard structures. Project workspaces can be created in a consistent and repeatable way by applying the right project parameters — no reinventing the wheel for each new engagement.

This required clear data model decisions about what should be standardised centrally and what should remain project-specific. I worked on the information model structure, the setup of reusable objects and relations, and the processes for transferring and reusing data between workspaces.

Outcome

The new setup gave Qirion a more repeatable and controlled way of starting and managing projects. It reduced manual setup work, improved consistency between projects, and created a stronger basis for scaling Relatics use across the organisation. Standards for TenneT and Liander — covering asset data and technical requirements for systems engineering — are now managed centrally within this environment.

The programme

TenneT is the Dutch and German transmission system operator responsible for delivering offshore grid connections at a scale and speed the sector has never attempted before. Rather than treating each connection as a bespoke project, the 2GW programme introduces an industrialised approach: repeatable 525 kV HVDC platform designs, framework contracts with major delivery partners, and a programme structure that spans all 14 connections simultaneously.

Key delivery partners include Hitachi Energy, Petrofac, Siemens Energy, and Dragados Offshore. The programme underpins national offshore wind targets in both the Netherlands and Germany, supporting TenneT's broader 40 GW offshore ambition by 2030.

The challenge

Managing changes to configuration items across a programme of this scale was largely uncontrolled. A version control system existed, but there was no structured way to manage changes in a controlled, traceable manner — meaning requirement updates could be applied inconsistently across partnerships and contracts, with no clear audit trail.

Beyond change management, the team needed a systematic way to manage contract control (SCC — systematic contract control) and to shift their thinking from managing individual projects to managing the programme as a whole.

What I built

Together with the team, I designed and implemented a three-tier Relatics workspace architecture — library, partnership, and contract — each connected to the others, reflecting how the programme is actually structured.

The library acts as the starting point for each new partnership. When standards evolve, changes can be communicated to contractors and — once accepted — pushed through to relevant partnerships and contracts in a controlled way.

Outcome

The programme now has a live, structured overview of which requirements are applicable in which contract and where deviations exist. Change management on configuration items is controlled and traceable, and the library-to-contract chain ensures consistency across a programme of unprecedented scale.

The product

Gappless connects office teams and field workers in one unified workflow. The web platform is used by project managers and administrators to prepare projects, define templates, manage findings and measures, set up inspection plans, and review incoming field data.

The mobile app serves on-site users — allowing them to capture registrations, photos, findings, and follow-up information directly in the field, often in offline-first or low-connectivity situations. Together, they guide teams through structured inspections using TouchForms, bridging the gap between office preparation and field execution.

My role as Product Owner

I was responsible for shaping the product direction and translating user needs into a clear, prioritised backlog for the development team — making day-to-day decisions on scope, sequencing, and trade-offs between usability, technical feasibility, and business value.

A strong part of my role combined product ownership with UX thinking. I helped steer user flows, interaction design, and functional details — validating user problems, refining concepts into workable solutions, and ensuring the product stayed intuitive for the different user groups it served.

Key product decisions

I shaped decisions across project setup, field registrations, reporting, workflows, and integrations — deciding which problems to solve first, how to keep the product manageable, and where to simplify or standardise functionality across customers.

My contribution was strongest in translating real user pain points into concrete improvements — redesigning workflows, introducing new features, simplifying complex screens, and improving reporting and export. In each case, I balanced short-term delivery needs with the longer-term product vision.

Outcome

The product evolved in a more focused and user-centred direction, with clearer priorities for the team and features that better matched day-to-day usage in the field. Key deliverables during this period included findings, measures, and inspection plans.

The challenge

DPI needed two things solved at once. On the project side, they lacked a standardised way to manage their client projects with systems engineering — each engagement started from scratch with no shared structure for requirements, objects, work packages, or activities.

On the internal side, tracking new and potential hires was ad hoc — conversations, backgrounds, and follow-up tasks were scattered with no central overview, no task ownership, and no way to keep the right people informed automatically.

What I built

I delivered two separate Relatics workspaces, each designed for a very different purpose — demonstrating how far Relatics can stretch beyond its traditional engineering use cases.

Outcome

DPI now has a repeatable, structured starting point for new client projects — a clean data model they can confidently extend without starting from scratch. The hiring workspace replaced scattered tracking with a single, actionable overview: candidate status, conversation history, open tasks, and automated notifications all in one place.