A drawing-production team on a large infrastructure project, working through a full set of construction-stage sheets under deadline pressure — the kind of MicroStation output work that sits downstream of the 3D model.
Client kept anonymous, as with all BIM Global engagements.
Display rules — the settings that control how elements render and print — weren't applying the way they should. Colors that were supposed to show up on the printed sheets simply weren't there, across a full set of ten drawings.
The team member responsible had applied the settings correctly, by the book, on every single one of the ten drawings — and it still wasn't working. That's what made it worth escalating: it wasn't a mistake anyone could point to. It was a setting most modelers are never actually trained to look at, because nothing about it looks wrong until it's time to print.
A BIM Global consultant — George White — was brought in on a single support call. Rather than treating it as a one-off glitch, he traced the issue back to its root: a display-rules misconfiguration — a setting most modelers never get properly trained on, because it doesn't cause visible problems until it does.
This is the pattern behind most of the "mystery" issues teams call about: not a software bug, but a modeling-hygiene gap that nobody flagged because nobody was trained to look for it.
The consultant diagnosed and corrected the display-rules setup live on the call — walking the team through why it broke, not just how to fix it, so the same mistake wouldn't resurface on the next project.
Client kept anonymous.
Most support calls like this aren't really about the printing error, or whatever symptom surfaced first. They're about a gap in how the team was originally trained — the kind of gap that keeps resurfacing in new forms until someone actually closes it.
That's the difference between a support call that patches a symptom and one that fixes the habit behind it.