Purpose
Start with the owner and operator decisions the information must support.
BIM · Information management · FM
Information requirements, connected to delivery.
IPM links use cases, processes, information requirements, roles, tools and FM outputs in one navigable model.
Interactive workspace
Explore the information model.
Select a scenario, inspect relationships and open a node to review its structured source information.
Information model
Use cases, delivery processes, information and operational outputs
How to read the model
Use caseInputProcessActorToolOutputEvidenceAsset type
Each node represents one class rather than a project instance. The arrows show the minimum information chain: an input supports a use case, the use case activates a process and tool, the process has a responsible actor and evidence, and the output applies to an asset type. Select a node for its definition.
Loading information model
Reading the structured data source.
Source: data/ipm.json
Verified structure
Method
From purpose to operational use.
IPM structures BIM requirements as a traceable information flow rather than a collection of disconnected documents.
Information order
Derive processes, responsibilities, data needs and delivery packages.
Validation
Translate requirements into structured checks, IDS rules and evidence.
Operational use
Connect verified information to asset management, CAFM and lifecycle decisions.
About
Jindrich Hozak
Architect and BIM / information-management specialist working across digital building, lifecycle data, BIM2FM, model quality and process transformation.
Focus: BIM2FM · IFC / IDS · Digital Twin · Solibri · dRofus · Data Strategy
A connected information-management prototype.
The model demonstrates how operational purpose, processes, responsibilities, requirements and validation can be connected in a form that decision-makers can inspect.
The next steps include explicit KBOB and FM process mappings, role and skill-gap analysis, and scenario-based generation of information requirements.