Project Snapshot
Client: municipal infrastructure department, anonymized. Scope: BIM overflow modeling, model setup, BEP support, clash workflow, standards documentation, and practical enablement for 12 internal staff. Result: six-month rollout with every production deliverable on time.
Client type
A municipal infrastructure department that had committed to moving its design production from 2D drafting to BIM. The department had live projects in delivery throughout, and an internal team that needed to learn Revit-based, ISO 19650-aligned workflows while still meeting its deadlines. The department is not named because the work was delivered under NDA.
Scope
- Overflow BIM modeling on live projects.
- Model setup: template models and naming conventions.
- Support for the department’s emerging BIM Execution Plan.
- A repeatable clash and issue-tracking workflow.
- Standards documentation and hands-on enablement for 12 internal staff.
Constraints
The department had committed to a BIM transition, but live project work did not pause while standards were written and staff trained. Its internal team needed room to learn without missing deliverables. The common failure mode in this situation is trying to turn every production deadline into a training event.
Standards
The work was aligned to ISO 19650 and to the client’s own emerging BIM Execution Plan. Rather than writing standards in the abstract, we documented practical rules for level of development (LOD), federation, file naming and handover, and tested them on the department’s real deliverables so they held up on the first live deadline.
Deliverables
- Template models and naming conventions aligned to the client’s emerging BEP.
- Overflow modeling, so internal staff could focus on adopting the standards and reviewing work.
- Clash rounds and issue tracking run as repeatable model-coordination steps.
- Written rules for LOD, federation, file naming and handover.
- Focused working sessions with staff, using live project examples.
Timeline
The engagement ran for six months. Production support and standards work ran side by side from the start: as each rule was written it was used on live projects, and staff practised the workflow on real deliverables in working sessions rather than in separate training.
Outcome
Production work stayed on schedule while the internal team built competence. By the end of the six-month engagement, the department had a usable BEP, project templates, model review routines, and staff who had practised the workflow on real deliverables.
The lesson
BIM transition succeeds faster when production support and standards work are treated as one operating system. If standards are written away from live delivery, they often fail on the first real deadline. If production runs without standards, the team simply creates another unmanaged drafting queue.
Start with a defined scope.
Agree the source information, deliverables and review requirements before the first issue.