One logic — many networks, many roles.
The control center is broken down by sector and shows every role the view that fits. And it sits above your existing systems.
The same Control Center logic — every type of infrastructure with its own depth.
The control center is broken down by sector — each with its own document type catalog, down to the individual areas of network operations. How far the templates are built for each sector is shown openly in the status.
Twelve sectors in the catalog
Counted document types per sector, as of Nov 14, 2026. Five sectors are established, seven in development — same structure, same core. See product status →
- Electricityincluding ground-mounted solar and onshore wind5,210 document typescatalog + templates
- Rail1,513 document typescatalog + templates
- Water and wastewater749 document typescatalog · templates per project
- Gas737 document typescatalog · templates per project
- District heating632 document typescatalog + templates
- Airports941 document typesdraft catalog · expert review pending
- Roads and tunnels820 document typesdraft catalog · expert review pending
- Hydrogen467 document typesdraft catalog · expert review pending
- Data centers401 document typesdraft catalog · expert review pending
- Food production328 document typesdraft catalog · expert review pending
- Telecommunications326 document typesdraft catalog · expert review pending
- Nuclear power595 document typesdraft catalog · expert review pending
In detailExplore the sectors in depthPer sector the technical areas down to network operation — click through.Expand
Sample records — the right documents for each sector.
48 sample records from the five established sectors (water and wastewater listed separately) — a slice of what Linea Aurea structures for each type of infrastructure. The full catalogs and rules live in the system.
In detailSample records per sectorTypical documents with deadline and gate — switchable per sector.Expand
One truth — explained correctly for every role.
The same data, the view that fits. Find your role:
In detailExplained for every roleManagement, project lead, document management, operations, IT — what each role sees in the Control Center.Expand
Monday morning, before the team meeting: a glance at the control center shows where records are missing or deadlines are approaching — not only found on the next walk through folders and emails.
- Open records at a glance, not scattered across folders
- Deadline alert before the gate, not after
- QR jump-back from paper to the digital object
- Version, inspection and retention deadline per document with a single click in the Documents tab
Before the construction acceptance, the risk indicator shows which asset is not yet ready for acceptance — enough lead time to steer instead of improvising at the handover date.
- Handover risk visible before it turns into a delay
- Gate progress per asset instead of an aggregate status
- One click from the risk to the responsible record
- Documentation coverage per asset as a bar in the Assets tab, not just an aggregate figure
Before the status meeting with the supervisory board or shareholders: a portfolio view across all networks and sectors — without having to check back with three different departments.
- Portfolio view across all sectors and networks
- Risk prioritized by impact, not by volume of alerts
- Solid figures for reporting and the board
- All twelve sectors in the Sector switcher in the control center with comparable metrics
During the on-site inspection, the QR code on the asset nameplate leads directly to the stored record — instead of having to search the archive first.
- Every status statement traceable back to its evidence
- QR jump-back from asset to document
- Chain of evidence verifiable, not just claimed
- Access within the agreed scope through the same permission model as internal users, see FAQ
In a conference talk or a tender conversation, the structural principle is enough to explain the benefit — without going into system detail.
- Principle explainable in one sentence
- Comparable to familiar systems (DMS, CDE, GIS)
- Depth available on demand, not forced on you
- Every specialist term is available in the glossary on this page
Before approving the pilot, the checklist goes through point by point: deployment model, network zones, roles, interfaces — answers, not a black box.
- Read-only at operational boundaries as a principle, not an option
- Architecture conversation before every pilot, not after
- Answers to the IT checklist available in advance
- All 12 points of the IT checklist documented with a short explanation
Before placing an order, the comparison matrix clarifies commitment periods, notice periods and what happens on exit — instead of finding it in the fine print afterward.
- Pricing logic and contract terms transparent in the comparison matrix
- Exit conditions contractually defined, not left open
- No blanket migration project hidden in the proposal
- SLAⓘ is part of the individual contract under the Operator Program, not promised as a blanket guarantee
Record-keeping doesn't end at handover: recurring inspections and deadlines keep running in the control center, with lead time instead of a surprise at the next audit.
- Recurring inspection and retention deadlines under continuous view
- One view for build and operations phases, no break at handover
- Knowledge stays in the system, not tied to one person
- The Deadlines & Gates tab calculates deadlines from inspection and retention rules per asset type — as a rule, not a reminder
Sits above your systems — and continuously evaluates them.
Read-only and vendor-neutral. LAD can be connected to practically any network operator system already in use — without a system change.
How LAD connects — with architecture diagram, seven examples from SAP, ELO, GIS & co. and the sync status: View system connections →
Briefly explained — the key terms.
So it's clear what we mean — compact, without jargon. All terms, including cross-sector and cross-product ones, in the full glossary.
In detailThe key termsShort version — the complete glossary has its own page.Expand
A document that proves a requirement has actually been met — for example an inspection report, a declaration of conformity or an acceptance record.
Defines, per asset and sector, which documents must be present, in what structure, and with what inspection and retention deadlines — the basis for every documentation coverage figure in the control center.
The share of the records required by the documentation catalog that are already complete and verified for an asset, area or sector — shown as a percentage in the control center.
A predefined set of rules and records for a specific sector — electricity, gas, water, wastewater, district heating or rail — including the document types and deadlines required there.
The four gates in the control center, always in this order: G3 · Construction, G4 · Approval, G5 · Handover, G6 · Acceptance.
The state in which every record required for a handover or acceptance is complete and verified — measurable, not estimated.
The central control unit for the documentation of your networks: shows based on the current data status which records are missing, where the handover risk sits, and how far the current acceptance and handover readiness has come. Not a new DMS — a layer above it.
A connection to existing systems such as SAP, ELO, GIS or SharePoint that only ever reads data, never changes it. No migration, no data move. Seven concrete examples: System Connections.
For your sector, for your role.
30 minutes, no system access: using your use case we check whether a pilot area can be clearly scoped — no slide deck.
- Send a requestBriefly, your topic and your sector.
- 30-minute conversationOn your use case, no system access.
- A clear answerWhether a pilot area can be clearly scoped.
