Insights · Evergreen thinking
Understanding first. Technology second.
How modern digitalisation and automation create real business value in industry and real estate — written from the boundary between IT and OT, where strategic governance meets technical depth.
The articles span technology, information management, structure, working methods and governance — and how these interact in complex technical environments.
They address both overarching reasoning and specific questions, grounded in real challenges rather than individual products or solutions.
The aim is understanding, context and long-term thinking about how technology is used, developed and managed — reflecting our work as technical owner’s representative in industrial and facility projects.
We base our methods on established international standards such as IEC 81346 to ensure the information management requirements of the future.
Our method foundation
The lexicon
Every vendor speaks their own language. We wrote the dictionary — vendor-neutral definitions of the concepts that decide procurements, integrations and technical strategy.
Want to understand how we think before choosing a topic? Start with the Map, the Engine and the Road, or explore our five-layer model.
Editorial selection
Featured articles
-
Why Standardisation Is Critical for Digitalisation, Integration and Automation
TL;DRProblemWithout shared standards, every project creates its own structures, leading to fragmented data and fragile integrations.SolutionBy using established frameworks such as IEC 81346 and IEC 81355, a shared information foundation is created that holds over time.ImpactA “Digital Thread” – an unbroken chain of information that makes your facilities easy to understand, manage and develop further.5–8 minutes -
Digitalisation, Integration and Automation in Practice
TL;DRDigitalisationis about information – making data comprehensible, traceable and useful across the entire lifecycle.Integrationis about context – connecting systems and flows with clear interfaces and responsibilities.Automationis about governance – letting systems act independently based on logic and reliable data.3–5 minutes
Latest from HubMind
Latest articles
-
The Complete Object: Who Owns Which Truth?
TL;DRA practical owner-side guide to technical information authority: who contributes, governs and assures each part of a complete technical object.30–44 minutes -
Brick: The Semantic Interface
TL;DRTurn a Brick graph into a governed semantic interface using SPARQL discovery, external data references, SHACL validation, versioning, provenance and acceptance tests.12–17 minutes -
Brick: One Object, a Graph of Context
TL;DRBuild a useful Brick subgraph around AHU-3 using classes, instances, composition, topology, location, points, controls and governed graph boundaries.11–17 minutes -
Brick: From Tags to Meaning
TL;DRLearn how Brick turns building-system tags into machine-readable entities, classes and relationships, and why it complements IEC 81346.12–18 minutes -
IEC 81346, ISA-95 and Brick: Give Every Model the Right Job
TL;DRLearn how IEC 81346, ISA-95, Brick and CMMS/EAM answer different questions about the same technical object, and how canonical identity connects them.13–19 minutes -
IEC 81346 Explained: Structure Before Naming
TL;DRIEC 81346 is more than a naming standard. Learn how shared structure gives technical objects stable identity across disciplines and the facility lifecycle.6–9 minutes -
IEC 81346 Aspects: One Object, Several Views
TL;DRSee how one technical object can have function, product, installation and type designations under IEC 81346 without becoming several unrelated objects.6–9 minutes -
Implementing IEC 81346: From Notation to Infrastructure
TL;DRHow asset owners can implement IEC 81346 as governed information infrastructure across procurement, BIM, automation, EAM and operations.7–10 minutes -
Seven Machines, Seven OPC UA Dialects: Why Complex Operations Need a Two-Tier UNS
Automation & Control Systems Industry & Facilities Innovation & Future Technology System Integration & ArchitectureTL;DRProblemOrder seven machines and you get seven OPC UA dialects. Protocol compliance guarantees nothing about semantics – and the classic answer, connect everything and clean up in the middleware, only relocates the cost.SolutionThree concepts. The machine interface data contract (level 1.5) that turns normalisation into a delivery requirement. UNS-O – the operational namespace, assembled from contracted sources. UNS-E – a governed 1:1 projection for multidisciplinary sharing.ImpactIntegration cost per new machine approaches zero, OT is never exposed unnecessarily, and production, facility and energy data share one identity backbone.4–6 minutes -
Why Technical Information Architecture Matters in Complex Technical Environments
TL;DRProblemComplex facilities are not only built from systems and equipment. They are built from information. When objects, signals, requirements, documents and responsibilities drift apart, technical debt is created before the facility is even in operation.SolutionA coherent technical information architecture, where data mapping, information modelling, master data ownership and data governance define how information is created, owned and moved between systems.ImpactTraceability across systems, clear ownership, and a facility that can be integrated, maintained and developed throughout its lifecycle.3–5 minutes