Automation for a production and technical department
As-built documentation for overhead contact line poles
The task
After overhead contact line poles are installed, a surveyor measures their position in plan and elevation. Each pole needs its own A3 as-built sheet: the deviation calculation, a small diagram and a comparison with the tolerance under GOST R 51872-2024. A section can have 200–300 poles. It used to take an engineer two weeks.
The data comes from different sources: the project PDF from CAD, the DXF plan, TXT and XML from the field total station. Every contractor's formats are slightly different. A mistake on one pole means redoing the sheet and delaying the as-built documentation for the client.
The production and technical department is a bottleneck at engineering companies: few people, many sites, strict deadlines under GOST standards. Automation here is about taking routine off the engineer, not about a nice dashboard.
The solution
A Streamlit app: upload the project PDF, the DXF plan (if there is one) and the field instrument's measurement files. The output is a ZIP with a PDF sheet for every pole, a summary Excel table and, optionally, a DXF to insert into the project.
Deviation calculations and GOST tolerance checks are built into the pipeline. The engineer doesn't recalculate each pole by hand. The summary table shows right away which items are out of tolerance.
The hardest part turned out to be parsing pole tables from PDF. They are exported from CAD, and plain pdfplumber trips over them. We connected OpenRouter Gemini 2.5 Pro Vision: we render the page to an image and give it to the model with the prompt "extract the list of poles as a JSON array". It works where classic parsers give up.
How it works
A four-stage pipeline: extracting the list of poles from the PDF, matching coordinates from the field files, geometric calculation of deviations, generating PDF sheets from the A3 template.
The vision model is called only for "broken" tables. If pdfplumber copes, the LLM isn't used. This keeps the cost of a run down on typical projects.
On Windows we had to write a PowerShell script for some of the conversions: Cursor and CI run in an isolated environment, while field engineers work on locked-down corporate laptops.
Industry context
Needs like "automating as-built documentation" and "automation for a production and technical department" come up at contractors for overhead contact lines, power lines and bridge construction. What they share: many identical sheets, strict regulations, mixed input formats.
General-purpose CAD systems don't cover post-installation as-built documentation specifically. You need a narrow tool built for one client's regulations.
The result
Two weeks of an engineer's manual work shrank to one working day for a section of 200+ poles. Recalculation errors were replaced by automatic tolerance checks. The department handles more sites with the same people.
How the work went
We started with one real section: 47 poles and a full set of source files. We checked the first five sheets against the engineer's calculations by hand until the automation matched to the millimetre.
We separately debugged PDF parsing from two different CAD systems. This is where vision was needed: tables with merged cells broke pdfplumber.
The department's engineers got a Streamlit interface with nothing to install: open it in the browser, upload the files, download the ZIP. In field conditions this is critical.
Documentation for the department: what to do if a pole is missing from the measurements, how to mark a manual correction in the summary Excel.
Similar tasks come up at grid companies and general contractors with as-built documentation under GOST: a narrow tool beats general-purpose CAD on time.
FAQ
Which file formats are supported? The project PDF, the DXF plan, TXT/DXF/XML from the total station. If your instrument exports something else, we'll work it out from samples.
Why use a vision model on PDF? Pole tables from CAD often have merged cells. A classic parser breaks, while the model reads the page the way a person does.
Does it need installing on every PC? No. Streamlit runs in the browser; access to the internal network or a VPN is enough.
Does it work for other GOST standards? The tolerance logic is configurable. The current case is set up for GOST R 51872-2024 for overhead contact line poles.
Who it's for
Engineering companies and subcontractors that hand over as-built documentation for poles, masts and structures under survey control. A narrow task with a large volume of identical sheets.
If a two-person department is running five sites in parallel, compressing two weeks into a day changes the schedule of the whole unit. The tool requires no CAD training.
General contractors can give subcontractors access: the same pipeline and one sheet format at acceptance.
Compared with the alternatives
General-purpose CAD calculates geometry but doesn't assemble an A3 as-built sheet with text blocks in the client's template. Excel tricks don't hold up at 300 poles.
Outsourcing the technical department's work for every section costs more than a year's licence for a narrow tool. An in-house engineer with the app handles the volume alone.
Vision on PDF costs more than a classic parser, but less than two weeks of manual work on every site.
Summary
The department's engineers no longer spend two weeks on a single section. The summary Excel shows problem poles right away, and the client accepts the PDF sheets without format changes.
Do you have a similar volume of as-built documentation under GOST? Send an anonymised set of files, we'll run it on a test bench and show the processing time on your example.
Working with the studio
Legenda Studio runs projects like this from auditing the client's files to production release. For a technical department it's important to start with one real section rather than an abstract spec. We ask for sample PDFs, measurements and a reference sheet, and check the automation against the engineer's manual calculation.
Then we extend it to other types of structures and GOST standards. Support includes updating the parsers when the CAD system changes its export format.
Have a similar task? We'll go through it on a half-hour call. For new clients we build a working prototype in 5–9 days, with no prepayment.