Glossary — explained in one place.
Every term that recurs throughout this website — from Gate to Handover Readiness — collected in full and in alphabetical order. See the control center itself, interactive: control center on the Solution page.
A
Formal confirmation that an asset or service has been delivered as contracted. In the control center the last gate (G6) — it requires every record demanded for it to be in place.
The sequence of approval stages a section passes through. The control center shows what is blocking, what comes next and who decides.
The documents handed over to operations once an asset is completed — such as as-built drawings, inspection reports and manufacturer documentation. In the control center part of the handover (G5).
C
Central project data environment for construction documents and models during the build phase. Manages projects — not the record-keeping logic behind them.
The continuous, evidenced path from a statement or status light in the control center back to the source document. Makes every statement verifiable.
The header of every LAD template with document ID, template version, confidentiality, document class and area — plus the QR link back to the QR·DMS resolver.
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.
The recommended LAD offer: the ongoing control center for your network, as an annual license tiered by number of disciplines — recurring rather than one-off. Details on the Packages page.
D
The view in the control center with four perspectives on the same status: Documents, Assets, Deadlines & Gates, Source Systems — each showing the same truth, just sliced differently. Demo example in Solution, Document Room section.
Manages and archives files, usually company-wide. Knows where a document is stored — not whether it is still missing for an acceptance.
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.
F
A roughly 30-minute initial conversation without system access: sector, network section, the operator's problem, source systems and the success criterion are defined — Phase 0 of the Pilot Blueprint, before anything is connected.
G
A checkpoint in a project or in operations at which every required record must be complete before an asset or construction section may be approved or handed over.
The four gates in the control center, always in this order: G3 · Construction, G4 · Approval, G5 · Handover, G6 · Acceptance.
H
The state in which every record required for a handover or acceptance is complete and verified — measurable, not estimated.
The risk that an asset or construction section will not be ready for acceptance or handover by the planned date because records are missing or a deadline is approaching — visible per asset in the control center before it turns into a delay.
I
The twelve-point checklist for the initial architecture check by IT and information security. Full version on the Security & Compliance page.
K
The regulatory framework for operators of critical infrastructure: KRITIS (critical infrastructure), the EU NIS2 directive, the German Energy Industry Act (EnWG), and the German Federal Office for Information Security (BSI). LAD supports structured record-keeping in this environment — the legal assessment remains with the operator.
M
The index LAD places over your source systems: asset, record type, version, deadline, status. Document content is only indexed where this has been contractually agreed in advance. More on the Security page.
N
A company that operates a utility or transport network and is responsible for its technical condition, maintenance and record-keeping — for example for electricity, gas, water, wastewater, district heating or rail networks.
O
The third LAD offer for multiple networks with custom integrations, SLA and security — individual rather than standard, for early operator partners. Details on the Packages page.
P
The LAD entry-level offer: one network section, ready in 8–12 weeks — the proof of value, at a fixed price from €29,500 (net). Details on the Packages page.
The five-phase process for a pilot: Fit Check, Scope & Data Intake, Mapping, Validation, Proof of Value & Decision. Full version on the Packages page.
Q
A QR code on a template or asset nameplate that jumps from the printed paper back to the stored record in the DMS — regardless of who scans the code, including external inspectors or expert assessors.
R
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.
A document that proves a requirement has actually been met — for example an inspection report, a declaration of conformity or an acceptance record.
An inspection that falls due again at fixed intervals — for example the periodic inspection of electrical equipment or a protection test. In the control center it appears as a deadline with lead time, not only at the next audit.
S
A fictitious network operator with synthetic sample data. The control center demo, the app and the sample PDFs on this website use it — no real operator, no real asset data.
One of the twelve infrastructure sectors for which LAD provides a dedicated domain pack: electricity, rail, water and wastewater, gas, district heating — in development: airports, roads and tunnels, hydrogen, data centers, food production, telecommunications, nuclear decommissioning.
A contractually agreed service framework, e.g. response and recovery times. Part of the individual contract under the Operator Program, not promised as a blanket guarantee.
T
Status indicator in the control center per asset, area or gate. Green means the required records are in place — and every green light is traceable to its record via the chain of evidence.
These terms recur throughout the control center, the document room demo, the FAQ and the use cases — always with this exact meaning. Missing a term you expected, or found something unclear? We're happy to clarify in a discovery call.
Still have a question about a term?
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.
