Introduction
A contractor can have a skilled modelling team, expensive software and a portfolio of award-winning buildings, and still lose a public tender at the pre-qualification stage.
The question on the form is rarely "do you use BIM?" It is "how do you manage information, who controls it, and can you prove it?" ISO 19650 is the international answer to that question, and clients increasingly want evidence rather than assurances.
Tip: Review your last project to verify information management ownership, approved model location and release authorization are clearly documented and consistent.
Mandatory BIM Adoption for Infrastructure Tenders
Governments and public clients in many countries now state BIM or information management requirements in tender documents for buildings and infrastructure, and the UK was an early example with its Level 2 BIM requirement for centrally procured projects from 2016.
Requirements are increasingly framed around ISO 19650 rather than national specifications, since the standard is international and replaced the older UK BS 1192 and PAS 1192 family.
Infrastructure owners such as rail, highways, water and airport authorities often set their own information requirements on top of the standard.
Pre-qualification questionnaires typically ask for evidence of information management capability, named roles, tools and previous project experience.
Some tenders ask for certification or independent verification, while others accept a documented self-assessment, so the exact ask must be read for each procurement.
Rules change, so teams should confirm the current requirement for the jurisdiction and client rather than relying on last year's tender.
Managing Information Across Asset Lifecycles
ISO 19650-1 sets out concepts and principles for information management using building information modelling.
ISO 19650-2 covers the delivery phase of assets, from appointment through design and construction to handover.
ISO 19650-3 covers the operational phase, so information produced during delivery remains useful for those who run the asset.
Other parts address security-minded approaches and health and safety information.
An Asset Information Model supports operation and maintenance, while a Project Information Model is developed during delivery.
Information requirements should be defined by purpose: why the client needs each piece of data, and when.
Handover is where many projects lose value, when models are delivered in formats the operator cannot use.
Clients increasingly judge suppliers on what happens after practical completion, not only before it.
Scrutinizing Common Data Environments (CDE)
Information should move through defined states, commonly work in progress, shared, published and archive, with approval gates between them.
Naming, classification and metadata conventions should be set in advance and applied consistently.
Roles and permissions need to match the appointment structure, so people see what they should and nothing more.
Version control must show who changed what and when, with the ability to find the approved version on any date.
Suitability codes or status markers should tell users what a file may be used for.
Audit trails and access logs should be available and not routinely deleted.
Exchange with partners using different platforms needs a clear rule on which environment is authoritative.
Backup, retention and archive arrangements should survive the end of the project.
Takeaway: A CDE is judged on its governance, not its brand. A modest system with enforced rules beats a premium platform where anyone can upload anything.
Delivery Plans vs Employer Requirements
Assessors read these documents together, looking for traceability from requirement to plan to delivered information.
Uncontrolled Documents on Shared Cloud Drives
Teams share drawings through personal cloud drives or messaging apps because the official system is slow.
Local copies of models and PDFs circulate with no way to confirm they are current.
Email attachments carry design changes that never reach the CDE.
Subcontractors use their own folders and send periodic exports.
Staff leaving the project take access, and sometimes copies, with them.
Document status is unclear, so superseded information is used on site.
Auditors test this by asking staff where they would find the latest version, and then checking it.
Controls such as blocking unmanaged storage, training and enforcing a single route reduce the problem more than policy alone.
Scope Does Not Match Joint-Venture Realities
A certification or assessment scope may cover one company while the project is delivered through a joint venture with several partners.
Roles, such as lead appointed party and information manager, should be assigned clearly in the venture agreement.
Each partner's tools, standards and security levels may differ, so a common set of rules needs to be agreed.
Responsibility for model federation, clash coordination and quality checks should not be left to assumption.
Evidence from one partner's projects does not automatically show capability of the venture.
Tender answers should describe how the consortium works, not only how each member works alone.
Changes in the supply chain during the project need updated plans and records.
Information Security Measures for Sensitive Projects
A security-minded approach, covered by ISO 19650-5, asks for proportionate controls based on the sensitivity of the asset and its information.
A security assessment should identify which information is sensitive and who needs access.
Access should be role-based, with stronger authentication for sensitive areas.
Sharing models outside the environment, for example with an overseas design office, needs explicit approval.
Subcontractors and software providers should be bound by security requirements in their appointments.
Disposal and archive rules should cover personal devices and removable media.
Incident reporting routes should exist for lost devices and suspected breaches.
Organizations often pair this work with an ISO/IEC 27001 information security management system for enterprise-wide controls.
Portfolio Scale and Model Layers Driving Mandays
Number of projects and the stage each has reached.
Number of sites and delivery teams using the organization's system.
Size and complexity of the models, and the number of discipline models federated together.
Number of lead appointed parties, task teams and key suppliers involved.
Variety of platforms and software tools used.
Level of automation in information checking and exchange.
Security requirements that add review steps.
Maturity of the system and the history of previous findings.
Enterprise System Audit vs Single Project Reviews
An enterprise review looks at the organization's standard processes, roles, tools and competence.
A project review looks at one appointment, including its plans, CDE and records.
Enterprise evidence supports many bids, which can save repeated explanation in questionnaires.
Project evidence is still needed where the client sets its own information requirements.
A strong enterprise system can be undermined when individual projects ignore it.
Conversely, one well-run project does not prove that the organization manages information consistently.
Many organizations use both: an enterprise assessment for tender readiness and project reviews for delivery assurance.
Attaining Accredited BIM Verification for Tenders
Read the tender documents and identify exactly what evidence is requested and whether certification is mandatory.
Define the scope of the organization, services and sites to be assessed.
Perform a gap analysis against ISO 19650, mainly Part 2 for delivery, and Part 3 where operations are involved.
Establish roles, competence records, CDE rules, naming conventions and information delivery plans.
Apply the system on live projects and gather records of how it works.
Run internal reviews and correct issues before the external assessment.
Choose a certification body whose accreditation covers the BIM scheme you need, and confirm its scope in writing.
Maintain the evidence through the scheme's follow-up arrangements and keep the certificate valid for upcoming tenders.
In the UK, UKAS has accredited BIM information management certification as process certification against ISO 19650-2 under ISO/IEC 17065, with the certification body defining its own scheme. This differs from ISO 9001-style management system certification, so check which route your client accepts.
How Pacific Certifications can help?
BIM information management certification under ISO 19650 is delivered through process certification schemes with their own accreditation requirements, so organizations should confirm a provider's accreditation scope and whether a client will accept it before engaging them. For the management system foundations that support tender pre-qualification, Pacific Certifications can provide:
Independent ISO 9001 and ISO/IEC 27001 certification audits
Stage 1 documentation and certification-readiness audits
Stage 2 implementation and effectiveness audits
Annual surveillance audits and triennial recertification audits
Pacific Certifications conducts impartial audits and does not design, implement or manage BIM, information or quality systems for its clients.
Contact Us
To schedule your ISO 19650 certification, contact us at support@pacificcert.com or +91-8595603096.
For training programs on ISO 19650 certification requirements and preparation, contact us at trainings@pacificcert.com.
Read More at: ISO certifications for construction industry
