Excavation and roadworks coordination for utilities

A Stadtwerk digs many small and a few large trenches every year, each needing a permit from the road authority, often a traffic order, and ideally coordination with other operators. Today this is paperwork plus phone calls plus spreadsheets. The feasible AI part is narrower than the title suggests: automatic conflict detection across GIS and calendar data, scheduling suggestions, and drafting the application documents. The actual coordination between organisations and the permit decisions stay with people. Maturity is emerging: there are municipal excavation-management portals, but few tools that plan across operators.

Problem & value

• Today: the utility's planners collect work orders (house connections, cable and pipe renewals, faults), look up the road, check whether another operator or the city plans something there, prepare the site plan and the application, send it to the road authority, and track answers. Municipalities differ in forms, deadlines and portals. One reported process: the utility applies, the authority circulates the application between its departments (Umlaufverfahren), attaches conditions, and later inspects the restored surface [1].
• Why it matters: an application filed against a road that was resurfaced last year, or a trench opened two months before another operator digs the same street, causes rejections, rework, extra surface restoration and public complaints. Joint trenching (Mitverlegung) is also an explicit goal of German telecom and fibre policy [2][3].
• AI value: the case study in our gap analysis counts about 35 hours per month for excavation permits at one Stadtwerk. Conflict checks and form drafting can plausibly remove a large part of that; the 20-40 percent in the front matter is an estimate for the supported task, not a measured result.
• Not solved by AI: negotiating dates with other operators and the authority. Coordination is largely voluntary in law: even for telecom works, a road authority generally cannot force coordination through the consent procedure [4].

Variants

• Stadtwerk multi-utility: power, gas, water and heating works by one company with its own crews and contractors.
• Telecom/fibre operator: consent under section 127 TKG, joint trenching, Infrastrukturatlas as data source [2][3].
• Municipality / Tiefbauamt side: the road authority receives applications and wants the same conflict view. Public-sector variant of the same logic (see also DOC-016).
• Contractor (Tiefbaufirma): applies on behalf of several utilities in one town.

How it works

1. work orders + GIS assets + road network
2. location and date window per planned excavation (geometry, length, surface type)
3. conflict check against: permits issued, other operators' plans, road moratoria, closures, events
4. scheduling: propose dates and joint-trenching candidates (constraint solver, crew capacity)
5. draft permit application + site plan + traffic-order request (LLM fills local forms)
6. human planner reviews and submits (portal, e-mail or paper)
7. tracking: answers, conditions, start and completion notices, restoration inspection

• Conflict detection: mostly geometry and calendar rules (buffer around the planned trench, time overlap), not an LLM. This is the reliable core.
• Scheduling: a small constraint or optimisation model (OR-Tools, CP-SAT) for dates under crew, contractor and permit-lead-time limits. Lead times and permit validity differ per town and must be taken from each municipality's own rules (do not hard-code assumed values).
• LLM role: extract rules and forms from municipal guidelines and notices, draft descriptions, read answers and conditions from letters and e-mails, write reminders.
• Human-in-the-loop: planners approve every date and application. Contact with other operators and with the authority stays human.

Data preparation

Which data: planned and past works from the work-order system, asset GIS, road and parcel data, municipal permit lists and excavation calendars, local excavation guidelines and fee tariffs, permit and correspondence files.

Where it lives: GIS (often Esri, Smallworld, NIS from a Stadtwerke vendor), ERP or work-management (SAP, proALPHA, specialised Stadtwerke software), Excel lists of permits, e-mail inboxes, municipal PDFs and portals. Many other operators' plans are not available digitally at all; the federal Infrastrukturatlas is not public and is accessed on application [3].

Typical gaps: no common key between work order, GIS object and permit; permits tracked only in e-mail; municipal data in PDF; different rules in each municipality of the supply area; no machine-readable moratorium list.

Preparation steps: 1. Inventory sources and owners (PREP-001, PREP-002, PREP-004). 2. Give each planned excavation one record with geometry, period and permit status. 3. Digitise permit PDFs and guidelines (PREP-006, DDOC-014 pipeline). 4. Convert GIS/CAD to a common coordinate system and format (PREP-007). 5. Write down the rules per municipality: forms, lead times, fees, who receives what.

Tools: QGIS/PostGIS, FME, a spreadsheet to start. Rough share of effort: more than half of the project, mostly data and rules per municipality (see GUIDE-003).

Implementation paths

Which path for whom

• enterprise (B): a Stadtwerk with its own GIS and work management usually builds a thin layer on its data with cloud LLM and a small solver; no product covers multi-operator planning for its specific municipalities.
• public (C): municipalities hold the permit data themselves and prefer self-hosted or sovereign stacks (PostGIS, open-source workflow).
• developer (C): software vendors can build on PostGIS, OR-Tools and an open-weight LLM and sell to many municipalities.

Path A — Buy

• Excavation-management portals for municipalities and applicants exist (for example an online service for frequent applicants in Bochum, used to apply, track and receive permits [5]) and also GIS-based Baustellenmanagement modules from Stadtwerke GIS vendors. They cover submission and tracking, rarely cross-operator conflict planning or LLM drafting. Check EU hosting, interface to your work orders and the municipality's portal.
• Choose A when: your main municipality already runs a portal, and you mostly need digital submission.

Path B — Build on cloud APIs (recommended for utilities)

• LLM with structured output (EU region or EU provider) for drafting and reading documents; geometry in PostGIS or cloud GIS; OR-Tools or CP-SAT for dates; n8n or Power Automate for workflow and reminders.
• Choose B when: you operate in several municipalities with different rules and own the work-order data.

Path C — Self-host

• PostGIS, QGIS, OR-Tools, an open-weight LLM (small models are enough for form filling, HW1-HW2), n8n. Needs GIS and Python skills in-house or from a partner.

Path D — Custom training

Rarely sensible. Possible later: learn permit lead times and rejection reasons from your own history to improve date proposals; needs a few hundred past applications with outcomes.

State of the art (2026)

• Digital permit portals and OZG-style digital applications are spreading; the Gigabitbüro points to digital approval processes and excavation management as practice examples [6].
• Conflict detection and joint-trenching matching are standard GIS-and-calendar problems; documented AI products for exactly this are few. Treat this as emerging: pilots and bespoke builds, not a mature product category.
• LLMs fill forms and read municipal letters well when the rules are given as context; they should not decide legal questions such as whether a notification or a full application is needed.
• Limits: missing data from other operators, differing municipal rules, and the fact that coordination cannot be enforced [4]. Regulation may change (not verified here), so check current law (section 143 TKG, Infrastrukturatlas rules).

Shared resources & combinations

• Same solver and GIS stack: OPT-036 (network rollout design, whose output creates the excavations), OPT-027 (construction schedules), OPT-019 (crew dispatch after the permit), OPT-001.
• Geodata building blocks: DATA-011; document reading with DOC-014 and DOC-003; rule checking of applications with DOC-016.
• Utility context: OPT-022 and OPT-023 for grid and heating works that trigger excavations.
• Workflow engine shared with AGENT-002.
• Combined effect: conflict detection feeds the dispatch plan, and drafted applications feed permit tracking; one geodata layer serves all of them.

Effort, cost & KPIs

• Path A: weeks for portal onboarding; licence per user.
• Path B/C: 3-6 months for a first version covering one or two municipalities; data and per-municipality rules dominate cost.
• KPIs: lead time application to permit, share of applications rejected or returned, number of conflicts found before submission, joint-trenching share, planner hours per application, re-excavations within a surface moratorium.

People & change

Involve early: department head for network planning or Tiefbau as process owner, GIS data owners, IT, legal for municipal rules and liability, and the contractors. Talk to the road authorities in your area: an offered shared calendar helps both sides.

Works council: no for the core tool as long as it only handles geodata and permits. It becomes relevant if planner productivity or crew locations are logged (section 87(1) no. 6 BetrVG); inform the works council in good time anyway (section 90 BetrVG). Public bodies inform the Personalrat.

Data protection: mostly non-personal data; contact persons in letters, address data of residents and applicants' names are personal data. Sign an AVV (Art. 28 GDPR) with cloud providers and involve the DPO (GUIDE-005).

AI literacy: short training for planners (Art. 4 AI Act, GUIDE-006). Start with one municipality as pilot and compare against the manual process (GUIDE-009).

Risks, regulation & compliance

• EU AI Act: minimal for planning and drafting. If AI controlled safety-relevant operation of supply networks (Annex III point 2) the picture would change; this use case does not.
• Road and telecom law: excavations in public roads need a permit under the Land road law (for example StrWG NRW in Bochum [5]); telecom operators need consent under section 127 TKG, including deemed consent after three months and the rule that coordination cannot be enforced through it [4]. A traffic order and later completion notices are usually needed in addition [6]; RSA signage plans follow from the technical rules below.
• Technical rules: RSA (Richtlinien zur Sicherung von Arbeitsstellen an Straßen), ZTV A-StB and ZTV BEA-StB for backfill and restoration; DVGW and DWA rules for the networks.
• Liability: a wrong application or missed condition is the utility's responsibility. The AI draft never replaces the planner's signature.
• Mitigations: checks against municipal rule sets, human approval, audit log of drafts and final applications.

Getting started

1. Take one year of past applications for one municipality and measure effort, rejections and conflicts.
2. Build the single record per excavation and load permits and moratoria.
3. Run conflict detection on next quarter's planned works and compare with planners' findings.
4. Add form drafting for the municipality's template; keep submission manual.
5. Extend to the second municipality only after the rule set is documented.

Sources

1. Betriebsamt Norderstedt — Aufgrabungen (Umlaufverfahren, Auflagen, Nachkontrolle) — https://www.betriebsamt-norderstedt.de/Strassenbau/Aufgrabungen/
2. Regulation (EU) 2024/1309 (Gigabit Infrastructure Act) — https://eur-lex.europa.eu/eli/reg/2024/1309/oj
3. Gigabit-Grundbuch (Bundesnetzagentur) — Infrastrukturatlas — https://gigabitgrundbuch.bund.de/GIGA/DE/Infrastrukturatlas/start.html
4. Louven Rechtsanwälte — Kann eine Koordinierung von Bauarbeiten im Rahmen einer Zustimmung nach § 127 Abs. 1 TKG erzwungen werden? — https://louven.legal/kann-eine-koordinierung-von-bauarbeiten-im-rahmen-einer-zustimmung-nach-%C2%A7-127-abs-1-tkg-erzwungen-werden/
5. Stadt Bochum, Tiefbauamt — Aufgrabung und Aufbruchgenehmigung (VIS Online) — https://www.bochum.de/Tiefbauamt/Dienstleistungen-und-Infos/Aufgrabung-und-Aufbruchgenehmigung
6. Gigabitbüro des Bundes — Zustimmungsverfahren nach § 127 TKG zielorientiert anwenden — https://gigabitbuero.de/thema/zustimmungsverfahren-zielorientiert-anwenden/
7. Regulation (EU) 2024/1689 (AI Act) — https://eur-lex.europa.eu/eli/reg/2024/1689/oj