Chapter 3 – Project information

The chapters on project information in the regulations contain the basic framework conditions of the project. In the non-project-specific templates (AIA – company template, sample BAP), the relevant information is stored as standard company content. As soon as project-specific sets of rules (AIA project-specific, preBEP and also BAP) are available, these standard contents must be formulated on a project-specific basis.

The project information can be regarded as part of the Organizational Information Requirement (OIR for short, in accordance with ISO 19650-1:2019). They are divided into:

• Project goals
  • All project goals are objectives of the client. All measures to achieve these project objectives are contained in the regulations.
• Project participants
  • Naming of all relevant project participants, with particular attention to BIM-related responsibilities and activities. It is not necessary to list all project participants, but all responsible parties and suppliers of BIM-related content should be listed as contacts.
• Project phases
  • List of all project phases for uniform understanding. The abbreviations of the project phases are relevant, as these are mentioned in the use cases (from preBEP/BAP) in order to classify use cases that are to be carried out several times.
• Collaboration platform
  • Storage of the platform with its address as a central data exchange platform.
• Model types
  • Explanation of the model types expected and required by the client in the project (e.g. specialist models, coordination model, collaboration model, federated model).
• Interface specifications
  • List of BIM-related digital interface formats. Special attention must be paid here to the versions of interfaces in order to rule out the possibility that required information cannot be provided or cannot be provided in accordance with the contract.
• Final project documentation
  • The final project documentation is the end product to be achieved. It is normally also managed as a separate use case in the set of rules. To clarify the final results to be delivered, it is also listed as a basic description in the project information. Especially if use cases are only fully formulated in the BAP, the project end documentation should be included as AIA content to ensure the contractual basis.

Publication from Krischmann, T., Malzer, W.: buildingSMART Austria Standard-AIA. Edition 2026.

Status: 17.02.2026