He saved the file: .
He sighed. The foundation guys. The concrete pour phases weren’t aligned with the steel embeds. If the concrete was poured a week before the embeds arrived, the steel columns would have nothing to grab onto. This was the curse of a Tekla Designer—you had to be an architect, an engineer, a logistics planner, and a fortune teller, all rolled into one. tekla designer
He clicked . A whirring sound filled his headphones as the server rendered 300 sheets of perfectly dimensioned, error-free blueprints. He saved the file:
Tonight, the monster was fighting back. A conflict log blinked red in the corner of his screen: Somewhere in the tangled heart of the model, a horizontal beam was trying to occupy the exact same space as a diagonal brace. In the real world, that meant a welder in six months would be holding two pieces of metal that couldn’t fit, cursing the name of the “office guy” who drew it. The concrete pour phases weren’t aligned with the
He wouldn’t make that mistake again.
He pulled up the Organizer . This was his favorite tool. It was a spreadsheet, but not like Excel. This spreadsheet was alive. It showed every single piece of steel in the stadium: 14,222 parts. 8,933 bolts. 2,101 assemblies. He filtered by “Phase: Foundation.” There it was. A group of anchor rods set to arrive in Week 8, but a concrete pour scheduled for Week 7.