What is the LOIN?
The LOIN (Level of Information Need) describes, under EN 17412 and within ISO 19650, which information is needed per element, phase and use case. It is not a standalone wish list — it concretises the requirements from the EIR.
LOG & LOI — the two dimensions
- LOG (Level of Geometry) — geometric detail: granularity, dimensional accuracy, representation of an element.
- LOI (Level of Information) — alphanumerical properties: attributes, classification, materials, FM data.
Together LOG and LOI form the LOIN. Crucially, both are determined per use case — an element can be geometrically coarse but data-rich, or vice versa.
LOIN instead of LOD: the older LOD (Level of Development) model is often too rigid. ISO 19650 / EN 17412 replace it with the need-based LOIN — you deliver only what the use case actually requires. That saves modelling effort and fees.
Requirement vs. delivery LOIN
The cascade has two views: the requirement LOIN is part of the EIR — what the client requires. The delivery LOIN is the response in the BEP — how the delivery team meets it operationally.
Common mistakes
- Blanket LOD levels with no link to the use case → too much or too little detail.
- High LOG, forgotten LOI — pretty models without usable data.
- LOIN not linked to the EIR → the delivery team guesses the detail.
Generate it
In the generator you set LOG and LOI per element class and use case. The LOIN stays linked to the EIR and is ready for the BEP — as a consistent, ISO-compliant document (DOCX/PDF).