Every pole number is in the file

Everyone who checks as-builts knows it. Two files, two crews, every pole number present, and it looks complete. It isn't until every row sits against the schedule, the week the as-builts are due. One slipped number makes every shot after it look wrong.

One case on our Try page: two as-built files for OCS foundations against the pole schedule. Yesper found the second crew had slipped a number: 12 rows belonged to the next pole. Renumbered, one row was a duplicate and the grade crossing foundation had no shot. Three are out of tolerance.

You order the re-shot before accepting the file. The missing shot and the foundation off its mark surface now instead of at the final inspection. Same for any survey file, and the rest of the Try page: cable tags against the cable list, QC records against the archive, an IFC model of existing catenary masts.

Try it yourself →

Benjamin Glaser Co-founder at Yesper. Writes about AI and the industry that builds the world. benjamin@yesper.ai

Yesper is the AI civil engineer for construction and infrastructure. AFRY, COWI, NRC Group and other Nordic firms use it to halve the time on a study, rerun calculations in minutes, and catch errors that would otherwise slip through. Get in touch if you'd like to see what it can do for you.

Book demo