COLLECTUS → OWNER’S DATA STANDARD VIA LODi - LEVEL OF DATA INFORMATION

The Collectus Data Standard is structured to become the Owner’s Data Standard. It is formally documented in the BIM Execution Plan (BEP) through the Level of Data Information (LODi) framework and embedded directly within the Collectus Revit content.

It unifies the Collectus Data framework with the owner’s existing operational data requirements—from facility management and space planning to asset management, maintenance, GIS, safety, finance, and beyond—into a single, coordinated, and enforceable data structure.

Through the Collectus DDMV workflow (Define → Distribute → Manage → Validate), this unified LODi structure is Defined by the owner and formally documented in the BEP. It is then Distributed to AEC BIM consultants at project kickoff through Collectus, where LODi 300, 400, and 500 requirements are embedded in the Revit schedules. This ensures AEC teams populate BIMs with the exact design, manufacturer, and operations data required—structured to match the owner’s operational systems.

These same embedded LODi Revit schedules provide the Validate step of the DDMV process. Throughout design, documentation, construction, and closeout, the owner can simply review the model schedules to confirm that required data has been properly populated and complies with the Owner’s BEP and LODi requirements.

With requirements defined, distributed, managed, and validated from day one, the result is Data-Rich BIMs aligned with the owner’s workflows, reducing rework at handover and enabling seamless BIM data harvesting into operations within hours of occupancy. This ensures a smooth transition from construction to operations and delivers immediate value for asset management, maintenance, and long-term facility performance.

LOD VS.LODI

The key difference between LOD (Level of Development) and LODi (Level of Data Information) lies in their focus. LOD defines the level of physical model detail at various stages of design and construction, from conceptual through as-built. LODi focuses on the specific data associated with the model at each stage, ensuring that required design, manufacturer, and operations data are captured in Revit schedules for facility management use. While LOD represents the model’s geometric and visual development, LODi ensures the completeness and accuracy of the data that supports operations. Collectus recommends that Revit models generally not exceed LOD 350, ensuring the owner receives usable, manageable models focused on structured data rather than excessive geometry.