A shared technical language
Make information survive projects and suppliers.
Structure objects, identifiers, documents, data ownership and semantics so technical information remains connected, reliable and usable throughout the lifecycle.
Technical Information Architecture and Data Governance
Decisions that make information ownable
Information architecture establishes what things are, how they are identified and where authoritative information belongs before integrations multiply ambiguity.
What is the same thing across systems?
Define stable identities and relationships independent of supplier labels.
Which source owns each fact?
Allocate master data responsibility and quality rules.
How should information be structured?
Use common classifications, semantics and document structures.
What must survive handover?
Specify lifecycle information that operations can trust and maintain.
How the work moves
- InventoryObjects, sources, documents and information flows
- ModelIdentity, relationships and semantics
- GovernOwnership, quality and change rules
- EmbedRequirements, mappings and handover structures
Typical outputs
Information model
Objects, relationships, attributes and shared meaning.
Identification structure
IEC 81346-aligned naming and reference designation where relevant.
Master data ownership
Authoritative sources, responsibilities and quality rules.
Exchange and handover requirements
Structured supplier and lifecycle information obligations.
Not a cleanup exercise after delivery
The information structure belongs in requirements and design early enough to shape supplier data, BIM and integration.
Semantics and data quality
Shared meaning. Verifiable quality.
We help you describe the same technical reality across engineering, automation, business systems and maintenance. An ontology can make meaning machine-readable, but it does not replace checking that information is correct or assigning responsibility for change.
One object, many systems
A pump appears in the engineering model, the control system and the maintenance system. We separate the enduring function from the replaceable product, connect the relevant measurement points and establish the authoritative source for each fact.
Quality you can test
Checks can reveal missing mappings, wrong units or outdated information. Where data checks cannot establish whether information matches the installation, technical review or physical verification takes over.
Proportionate structure
Sometimes clear definitions and mappings are enough; sometimes an explicit semantic model is needed. Choosing the right ambition level is part of the work.
Competence aligned with the standards
We participate in standardisation work for industrial data and interoperability, keeping our methods aligned with the international development around Industry 4.0.
DECISION EVIDENCE
Evidence for the next decision
Inspect the kind of artefact, experience and reasoning that can support this work before starting a conversation.
EXAMPLE ARTEFACT
One-object authority mapOne critical object traced across requirements, BIM, automation, documents and maintenance with an explicit source for each fact.
RELEVANT SPECIALIST
David NordinIndustrial Technology Strategist working across owner-side requirements, architecture, information, semantics, IT/OT and delivery assurance.
View executive profilePROJECT EVIDENCE
Selected delivery contextsTraceable roles and contributions across industry, infrastructure, healthcare, energy, water and asset-intensive environments.
Inspect selected projectsRELATED INSIGHT
Why technical information architecture mattersRead the articleContinue from here