Model-based delivery represents a significant shift for engineering and construction teams transitioning from drawing-centric workflows. The Eskilstuna interchange project, delivered through a model-only tender using Trimble Connect, provides several clear lessons for organisations considering a similar approach.
1. Establish the model as the primary project document
Define early that the 3D model will replace drawings as the contractual source of truth.
Ensure model content is complete, accurate, and unambiguous.
Embed all critical design information—geometry, attributes, specifications—directly within model objects.
Structure the model logically so users can navigate and locate information quickly
Why it matters: A model-first approach only works when the information normally dispersed across drawings is fully integrated into the model.
2. Invest in model quality from the start
Allocate additional time during early design stages to build a precise and detailed model.
Validate geometry, object relationships, and metadata before issuing the model for tender.
Maintain a clear naming and classification system for model elements.
Why it matters: Contractors must be able to reliably interpret information without referring to drawing sheets.
3. Use a shared digital environment for communication
Adopt a cloud-based common data environment, such as Trimble Connect, to host, view, and discuss the model.
Use shared views, screenshots, and object-linked comments to communicate queries and resolutions.
Ensure all project partners—designers, clients, contractors—operate within the same environment.
Why it matters: A shared model builds a shared understanding. It reduces misinterpretation and streamlines issue resolution.
4. Maintain consistency across organisations
Align on contractual expectations for a model-based tender.
Define responsibilities for modelling standards, updates, and information ownership.
Provide clear instructions on how the model governs over any supporting documentation.
Why it matters: When drawings are reduced or eliminated, clarity around roles becomes essential.
5. Support the workflow with clear processes
Develop workflows for model review, communication, and issue tracking directly within the digital environment.
Encourage teams to use model-based viewpoints rather than marking up separate documents.
Standardise how screenshots, links, and comments are shared to maintain traceability.
Why it matters: Effective model-based collaboration depends on consistent processes, not just technology.
6. Recognise where 2D documentation still adds value
Retain selected 2D outputs—such as profiles or linear geometry—where they genuinely improve interpretation.
Use drawings as supporting information rather than primary contractual documents.
Ensure any 2D views are derived directly from the model to maintain alignment.
Why it matters: Some engineering relationships remain clearer in 2D; hybrid support can strengthen understanding.
7. Use the model as a communication tool on-site
Encourage site teams to reference the model during coordination meetings, inspections, and issue resolution.
Share model links or viewpoints when clarifying questions remotely.
Where connectivity or hardware constraints exist, provide preloaded local versions or simplified model sections.
Why it matters: Model-based discussion improves clarity and reduces rework even when live updates are not used.
8. Foster a culture of shared learning
Acknowledge that many team members may be new to model-based delivery.
Encourage openness, experimentation, and feedback throughout the project.
Document lessons learned to support continuous improvement.
Why it matters: Cultural readiness is as important as technical capability when shifting to digital delivery.
9. Ensure compliance with standards and contractual frameworks
Validate that the model aligns with national standards, classification systems, and legal requirements.
Define how the model will be archived, referenced, and preserved as formal documentation.
Engage legal and procurement teams early to align contractual frameworks with model-based workflows.
Why it matters: A model-only tender must meet technical and legal thresholds to stand as a contract.
10. Plan for the long term
Treat each model-based project as part of a broader digital transformation journey.
Document successes, challenges, and enhancements for future projects.
Invest in training, modelling standards, and scalable workflows.
Why it matters: Model-based delivery becomes more efficient as organisations build experience and refine processes.
Continue learning about solutions for model-based infrastructure delivery
