Product data architecture
Product Information
I structure product information so that it can be understood, governed and reused across departments, systems and publishing channels.
Skills
My profile sits at the intersection of product, data, documentation, systems, processes, and automation.
The value does not come from knowing each area independently, but from understanding how they influence one another.
Areas of expertise
In complex industrial organisations, product information rarely belongs to one department. It moves across systems and people before becoming a catalogue, a manual, a website, a spare-parts list, a commercial document or the trusted context for an AI agent.
Product data architecture
I structure product information so that it can be understood, governed and reused across departments, systems and publishing channels.
Structured technical content
I design documentation as an information system rather than a collection of independent files, with particular attention to modularity and multilingual reuse.
Systems and information flows
I connect the places where product information is created, maintained and published, reducing duplication and unclear ownership.
Enterprise AI orchestration
I design governable automation and AI agents where language models orchestrate and deterministic code validates critical operations.
Cross-functional work
One of the most important parts of my work is acting between R&D, IT and Product Management to turn slow, fragmented documentation processes into automated, secure and governable pipelines. The goal is not to make everyone work in the same way, but to give everyone a reliable shared information foundation.
technical specifications, product evolution and engineering requirements
portfolio, product families, positioning and market variants
catalogues, product communication and localisation
systems, integrations, data flows and governance
repair information, spare parts and field documentation
price lists, commercial configurations and product information
System view
variants, configurations and technical meaning
attributes, content and relationships
ERP, PIM, CMS and integrations
manuals, catalogues, web, service and AI agents
The strongest solutions appear when these layers are designed as parts of the same information architecture rather than as separate projects: data, systems, outputs and automation must stay coherent.
The objective
The tools change from project to project. The objective remains coherent, reusable and governable product information that can feed both people and AI-enabled workflows.