ISO 19650 Certification: What It Means for BIM Delivery at TEBIN

TEBIN has achieved ISO 19650 certification for Building Information Modeling and information management. The certification confirms that the company has established and independently assessed processes for organizing project information within a BIM-based delivery environment.

ISO 19650 is concerned with information management across the lifecycle of buildings and infrastructure. It provides a structured approach to defining what information is needed, assigning responsibility, producing and reviewing information, controlling its status, and exchanging it at agreed points. The standard is not a software specification and certification does not mean that every project follows an identical template. It establishes a management framework that must be applied to the requirements and delivery structure of each project.

BIM is a process, not only a model

Building Information Modeling, or BIM, is often understood primarily as three-dimensional geometry. Geometry is important, but complex projects also depend on naming, classification, parameters, responsibility, approval status, revision history, exchange timing, and the relationship between models and documents.

A coordinated model can still create uncertainty if teams do not know which file is current, who approved it, what information it is expected to contain, or whether it is suitable for coordination, construction, or handover. ISO 19650 addresses this wider information-management problem. It helps project teams establish how information moves from work in progress through review, authorization, sharing, publication, and archive.

For a multidisciplinary design and engineering company, that process connects directly with delivery. Architecture, structural, civil, mechanical, electrical, plumbing, fire protection, information and communications technology, and specialist systems all produce information that must be coordinated without losing ownership or status.

Information requirements come before deliverables

Effective BIM delivery begins by understanding the information the appointing party requires and when it is needed. Project requirements influence model content, classifications, parameters, document formats, review stages, exchange dates, and the information expected at handover.

The delivery team translates those requirements into a practical plan. A BIM Execution Plan describes how the team will meet the project information requirements, including roles, software environments, model structure, naming rules, coordination routines, quality checks, and exchange procedures. Responsibility matrices and delivery plans clarify who produces each information container and at which milestone.

This preparation matters because “deliver a BIM model” is not a complete requirement. A model intended for early coordination differs from one intended for tender quantities, construction documentation, asset information, or operational use. The purpose of the information must be clear before its required detail and attributes can be defined.

What is a common data environment in ISO 19650?

A common data environment, commonly shortened to CDE, is the agreed source through which project information is managed and exchanged. It may be implemented using different platforms, but the platform itself does not create an ISO 19650 workflow. The workflow depends on permissions, naming, status codes, revision control, review steps, authorization, and consistent use by the project team.

Information should move through controlled states. Work-in-progress information remains within the responsible task team while it is being developed. Information is shared when it is suitable for coordination or a defined review. Published information is authorized for its stated contractual purpose. Superseded information is retained in an archive so the project record remains traceable.

This structure helps a distributed team understand not only where a file is located, but also how it may be used. It reduces reliance on email attachments, local copies, and undocumented decisions that can separate models from drawings or leave different teams working from different revisions.

Model federation, coordination, and quality control

Each discipline remains responsible for its own model and technical decisions. Federation brings those models together for multidisciplinary review without removing that ownership. The combined environment supports interface coordination, clash detection, design review, issue assignment, and verification that agreed changes have been incorporated.

Clash detection is only one quality check. Model reviews can also examine naming, coordinates, classification, parameter completeness, element status, agreed levels of information, and consistency with drawings and schedules. Automated checks are useful for repeatable rules, while engineering judgement is still required to assess constructability, access, maintainability, safety, and technical intent.

Issues should be recorded with clear responsibility, context, status, and resolution evidence. This creates a review trail that is more useful than comments scattered across meetings, screenshots, and email threads. At an exchange milestone, the team can verify both the technical content and the information-management requirements before issuing the package.

Structured exchanges and digital handover

Information exchanges are planned milestones, not simply file uploads. Before an exchange, models and documents are checked against the agreed requirements, naming conventions, revision rules, and intended purpose. The issued package should be internally consistent: models, drawings, calculations, schedules, and registers need to describe the same coordinated design.

Handover requirements should be considered early rather than added at the end. If the client needs structured asset information, equipment identifiers, classifications, maintenance data, or links to documents, the model and data workflow must support those fields during delivery. Otherwise, the project team faces a late exercise in reconstructing information that was never managed consistently.

ISO 19650 does not prescribe every handover field. It provides the framework for agreeing, producing, reviewing, and delivering the information the project actually requires.

What does ISO 19650 certification mean for TEBIN clients?

Certification is evidence that TEBIN's information-management processes have been assessed against the standard. It does not replace a project-specific BIM strategy, technical reviews, or collaboration with the wider delivery team. Each appointment still requires clear requirements, responsibilities, platforms, exchange dates, and acceptance criteria.

For clients and project partners, the practical value is a defined basis for setting up and controlling digital delivery. TEBIN can connect multidisciplinary design and engineering with BIM Execution Plans, model federation, common data environment workflows, issue tracking, model quality control, coordinated exchanges, and structured handover.

The certification assessment was conducted by Murillo Piazzi and Ella Walker of Simply Certification, with advisory support from Evgeniy Bachinskiy and Sigma Software Group. The work involved a wider TEBIN team that developed, documented, and validated the processes behind the certification.

The important outcome is not the certificate as a graphic on a website. It is the repeatable information discipline behind it: requirements understood before production begins, responsibilities made visible, information reviewed before exchange, and project records kept traceable from design through handover.