Everything else you wanted to ask — by topic.
The ten core questions first, then 43 more, organized in depth by topic.
The ten core questionsWhat grid operators ask first
How quickly will we see impact?
A pilot on a real network section is usually ready to start within 8–12 weeks — with your real section in the control center, not a slide deck. Exactly how fast depends on scope, data availability and access.
Do our data stay secure, and where do they run?
Read-only at operational boundaries, running on-premises in your own data center or in your own cloud. The operator keeps authority; the public-facing interface and privileged cores are separated. Details on a security review before the pilot are in the full FAQ.
Which sectors does LAD support?
Twelve sectors have their own document type catalog, each as a separate domain pack on the same core. Established: electricity (including ground-mounted solar and onshore wind), rail, water and wastewater, gas and district heating — electricity, rail and district heating with template sets; for gas and for water and wastewater the templates are produced per project. In development, as draft catalogs pending expert review: airports, roads and tunnels, hydrogen, data centers, food production, telecommunications and nuclear decommissioning. More on the Domains page. Which building blocks are ready today and which are still being built is shown on the product status page.
Does LAD automatically make us legally or regulatorily compliant?
No. LAD supports structured record-keeping — for example around inspection, archiving and critical-infrastructure (KRITIS) obligations. Legal assessment and responsibility remain with you and your subject-matter owners or inspectors. We promise no certification and no legal advice.
What happens to our existing documents and folder structures?
They stay right where they are — in SAP, ELO, GIS, SharePoint, or in folder structures that have grown over time. LAD reads read-only and links metadata, deadlines and chains of evidence on top. Even incompletely maintained legacy data can be opened up step by step; how much effort that takes depends on the current state.
How much effort is required from us as an operator, and what does it cost?
For a pilot: a named contact, a clearly scoped area, one to two validation meetings. On pricing: the pilot is fixed-price from €29,500 (net), followed by the Control License as an annual license tiered by number of disciplines, and the Operator Program is individually priced. Details are in the Comparison Matrix and in your personal proposal. Our ROI Calculator gives a first, rough sense of your current effort.
Can a green light in the control center be wrong?
Every system is only as reliable as its rules, sources and approvals — LAD included. That's why every status statement stays traceable back to its record, and the technical review remains with you. This honesty matters more to us than a light you're meant to trust blindly.
What's the contract commitment? Can we cancel?
The pilot is time-limited and non-binding. The Control License runs as an annual license; specific terms and notice periods are defined in the individual proposal. What exactly happens upon cancellation is covered in the full FAQ under "Contract, Costs & Exit".
What is LAD not — and what doesn't it decide?
LAD doesn't switch anything, doesn't grant operational approval in place of the responsible person, doesn't automatically decide on legal compliance, and doesn't replace an inspector or expert at acceptance. More on this in the "Why you can trust LAD" section on the Packages page.
Systems & IntegrationHow LAD fits into your existing landscape
How does LAD concretely differ from a DMS or a CDE?
A DMS manages files, a CDE manages projects. LAD manages the records logic behind them — which document belongs to which asset, with which deadline, in which gate. Both keep working as before; LAD sits above them as an ordering layer. More terms in the glossary.
Which systems can LAD connect to?
Practically any network operator system in production use — via a standardized interface, a customer-specific connector, or a file/metadata import. A pilot typically runs at first without deep live integration, using exports or a defined subset. Architecture and seven concrete examples: System Connections.
Does our existing data need to be migrated?
No — concretely, "no migration" means your documents are not moved wholesale into a new system. That does not necessarily mean zero integration effort, though: mapping between your structures and the LAD record categories may be needed.
We don't have SAP or ELO yet — does it still work?
Yes. LAD does not require a specific source system. Depending on how much of your existing documentation is already digital, we start with what's there — even from folder structures or file storage — with transparent visibility into data quality.
What happens if we later switch source systems, e.g. from SAP to a different software?
The relevant read-only adapter is set up again for the new source system. Assets, records and deadlines already managed in the control center are unaffected, since they are maintained independently in LAD — not in the source system itself.
Data, Data Sovereignty & SecurityWhat your IT and information security teams want to know first
Bundled together with the architecture principle, data flow and IT checklist on the Security & Compliance page.
What data does LAD actually read?
Asset and object metadata, document metadata, version and status, deadlines and gates, and references to the records. The actual document content is only read if that is intended for your use case and has been clarified contractually beforehand.
Does LAD write data back into our production systems?
No. Read-only at operational boundaries is a principle, not a configuration option — LAD reads and organizes, it does not write back and does not make operational decisions.
What logs are generated during ongoing operation?
Every status change, rule change and approval is logged in a traceable way with timestamp and author — part of the same chain of evidence that also links records to assets. This concerns the business level, not just technical system access. Retention periods, SIEM integration or export formats for your log management are defined in the operator project.
Do our documents leave the network?
As long as LAD only indexes metadata, the document content stays at its place of origin. For certain integrations, content may also be included — that is then named concretely in advance, never assumed as a blanket default.
What does a security review before the pilot look like?
Architecture discussion → data classification → interfaces → permissions → operating model → approval. You'll find the compact checklist on the Security & Compliance page under "The IT Checklist."
Does LAD support SSO and encryption?
We only state details on SSO, encryption, backup figures or certifications publicly to the extent they are genuinely verifiable — matching security documentation for your specific case is available on request. More on this in the Security section and in the IT checklist on the Security & Compliance page.
Records Logic & Data QualityHow a status statement in the control center comes about
See it in the control center — the same view your team would get in the pilot.
How does handover readiness come about in the control center?
From the required record, through the "present?" and "valid?" check, to the gate and the overall view. Every single stage is traceable back to the record — no summary statement without a traceable origin.
What happens with poor or contradictory existing data?
LAD does not hide data quality problems — it makes them visible instead of glossing over them. Incomplete or contradictory data shows up as a gap, not as a false green light.
Who decides which documents must be complete?
Your own business rules and project requirements remain authoritative. LAD structures and operationalizes this logic — it does not replace it.
Who is allowed to change rules, deadlines or gates?
That is a governance question decided individually by each operator — concrete roles and approval paths are defined in the operator project.
Can you see in the control center who last changed a deadline or a gate?
Yes. Every status change, rule change and approval is logged in a traceable way with timestamp and author — part of the same chain of evidence that also links records to assets. More on this under "What logs are generated during ongoing operation?" above.
Audit, Compliance & ResponsibilityWhat LAD can deliver — and explicitly what it cannot
How does LAD support audits?
From the dashboard down to the record: every status statement can be traced back to its origin, which speeds up audit preparation. Important: supporting audit-readiness is not the same as guaranteeing an audit outcome.
Which standards and regulations are built in?
We only state publicly what has been cleared for release. The complete, proprietary records catalogs per domain pack are not publicly viewable — they are part of what we configure together in the pilot and operator project.
Can LAD map NIS2, KRITIS, EnWG or BSI requirements?
Where in scope, such requirements can be translated into records and governance logic. This is not a certification and not legal advice — the regulatory assessment remains your responsibility.
Who bears responsibility for approval and acceptance?
Always the operator, or the responsible party or inspector in charge. LAD delivers the basis for the decision — not the legally binding decision itself.
Can external inspectors or experts access LAD directly?
Within the agreed scope, yes. The QR link-back from the asset nameplate to the stored record works the same regardless of who scans the code — access rights for external inspectors or experts run through the same permission model as internal access.
Does a green light in the control center replace an official acceptance or an inspection by an expert?
No. The status light shows handover readiness according to the stored records rules — it does not replace an official acceptance or an expert's inspection. More on this under "What LAD does not decide" in the "Why LAD can be trusted" section on the Packages page.
Pilot & OnboardingHow getting started works in practice
How long does initial setup really take?
For a single network section in a pilot, typically 8–12 weeks — depending on scope, data availability, access, data quality and integration type. The exact framework is scoped during the discovery call.
Do we need to approve IT interfaces already during the pilot?
Not necessarily. A pilot can start with exports or a defined data subset — a live connection is not required in every case to demonstrate initial impact.
What happens if the pilot doesn't show sufficient benefit?
Then it ends cleanly, with no artificial lock-in. An honest "no rollout" is a legitimate pilot outcome — more on this in the Pilot Blueprint on the Packages page.
How are our staff trained to work with LAD?
The interface follows terms already familiar in network operations — asset, record, deadline, gate. A short briefing at the start of the pilot is usually enough; scope and format are defined together with the named point of contact.
What is the timeline for the individual steps of a pilot?
Five phases — from the roughly 30-minute Fit Check through scope, mapping and validation, to a joint review meeting. The full breakdown with a guideline duration per phase is in the Pilot Blueprint on the Packages page.
Operations & ScalingFrom pilot to a running control center
How does a pilot become production operation?
By expanding the scope — more assets, more domain packs, more integrations and roles — up to the agreed operating model under the Control License.
Can multiple sectors or network operators use LAD together?
Yes. The product core is the same for all operators and sectors; each operator works with its own, separate instance and its own data. There is no shared data storage between operators.
What happens when staff change?
Knowledge stays in the system instead of in people's heads: explicit rules, chains of evidence and roles make handovers between staff traceable instead of person-dependent.
Can further sectors or network sections be added later?
Yes — through the same mechanism that also moves a pilot into production operation: expanding the scope with more assets, domain packs, integrations or roles, see "How does a pilot become production operation?" above.
Contract, Cost & ExitWhat procurement and legal should know before commissioning
What does LAD cost, and what does the price depend on?
A fixed-price pilot from €29,500 (net, 8–12 weeks), followed by an annual license tiered by number of disciplines, with the Operator Program priced individually. The scope of the network and assets, the number of sectors/domain packs, integrations and your operator structure all feed into the specific quote. Concrete figures are available on request.
Are there hidden migration or project costs?
There is no blanket migration project — but integration, mapping or special effort can arise depending on your starting position. A credible quote states this effort transparently instead of hiding it.
What happens upon termination?
Which LAD components end, what remains with you, and how configurations or exports are handled is set out contractually and made concrete in the operator project — this exit framework is a fixed part of a credible quote.
Does vendor lock-in result?
Part of the usual lock-in risk is already removed by the fact that your source systems remain unchanged. Operator-specific LAD rules and configurations still need to be cleanly settled in the event of an exit — that is part of the contract terms.
Does the price change if our network or scope grows?
The annual license is tiered by number of disciplines — if your network or the agreed scope grows, that is reflected in the respective quote. Details of the exact adjustment are set out in the individual contract.
Vendor & ContinuityWhat procurement, IT and project management want to know about a young vendor
Linea Aurea is a young, small company — why should we take the risk?
A fair question, and we answer it honestly: Linea Aurea is young and owner-managed. That is why the entry point is cut to keep your risk small — a time-limited, fixed-price pilot on a defined section, read-only, with no system change and no migration, with a clear acceptance and a clean exit. You test on your own project rather than on someone else’s reference names. Behind it are four years of document management in the transmission grid and twelve years in industry before that. More about us →
What happens if Linea Aurea is no longer available?
Your documents and source systems are not affected — they stay where they are; LAD only reads. The records standard is file-based and remains in your hands. A business continuity package is included in the pilot; for ongoing operation we agree it in the offer: master data export, data model description, release manifest and continuation documentation, plus a documented handover concept. With it, your own team or a service provider of your choice can carry the work forward.
Who is our contact — and how is cover arranged?
Your contact is the founder himself, from the Fit Check into operation — no handing you on between sales, project and support. We only commit to binding response times (SLA) where cover is arranged contractually. This is set out specifically in the offer for the operator program — in writing, before you place the order, not promised across the board.
Can a small vendor meet our procurement requirements — supplier assessment, tendering, security questionnaires?
Yes, within the usual scope. The pilot is a separate, narrowly defined service; your procurement team decides which award procedure it needs. We answer supplier self-assessments and security questionnaires, and suitable security documentation is available on request. For a later license we support you with the specification of services. Request IT and security pre-review →
Why choose a specialized vendor rather than a large software house?
Short paths: you talk directly to the person who developed and maintains the standard. Expert feedback from your pilot flows into catalogs and rules without corporate loops. And LAD does not require a platform change — DMS, CDE and ERP stay where they are; LAD adds order on top.
How does Linea Aurea scale when more networks or sectors are added?
Step by step, with the orders. The standard is fully documented — catalogs, rules, templates and a defined onboarding path — so that new colleagues work by the same method. How much capacity is planned for your project is stated bindingly in the offer.
Can we get to know Linea Aurea in person first?
Yes — that is exactly what the 30-minute Fit Check is for: no system access, on your use case. Bring your IT and procurement colleagues along if you like, so the questions in this section are settled right away. Request Fit Check →
What your colleagues will ask.
Six perspectives, six typical first questions — with a direct link to the matching answer.
In detailQuestions by roleWhat management, project lead, DM, asset management, IT and procurement ask first.Expand
Before signing off, Executive Management wants to see a solid business case — not a slide graphic. The ROI Calculator gives a first figure.
- What is the economic benefit?
- Where does handover and liability risk decrease?
- How do we measure the impact?
Before the next status report, Project Management wants to know where delays actually threaten — not only once they've already happened.
- Which gates are at risk?
- What's blocking handovers?
- Which records are missing?
During internal alignment, Document Management wants to know exactly what happens to the structure that's grown over time — nothing gets lost, nothing is migrated wholesale.
- How are document type, metadata, version and status organized?
- What happens to existing DMS structures?
- What happens if we switch source systems later?
In day-to-day operations, Asset Management mainly wants to know how an asset is actually linked to its records in the system.
- How is the link to the asset created?
- Which inspection and recurring deadlines become visible?
- What example records already exist for our sector?
Before any approval, IT/Information Security checks the architecture and data flow first — not the marketing promise.
- Where does the system run, what data does it read?
- What permissions and interfaces are created?
- Does LAD support SSO and encryption?
Before signing, Procurement wants to see commitment terms, pricing logic and exit conditions in black and white — not buried in the fine print.
- Scope, contract commitment, SLA?
- Data processing, exit, liability limitation?
- Does the price change as our network grows?
Your question wasn't listed?
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.
