Linea AureaDocumenta
Packages & Getting Started

How to get your control center up and running.

What you get and how a first pilot delivers reliable results within 8–12 weeks. Not a replacement for your DMS or CDE — an organizing layer on top.

Read-only at operational boundariesPilot with a real network sectionVerifiable chains of evidence instead of gut feeling
What you get

Start small. Grow with your network.

You pay for the tier you need — nothing more. No big-bang rollout, no system change.

Start here

Pilot

One network section, ready in 8–12 weeks — the proof of value.
from €29,500 netFixed-price pilot · 8–12 weeks
  • Domain pack for your sector
  • Records catalog + sample asset
  • 5D control center in your pilot instance
  • Onboarding & evaluation
  • Business continuity package included

Works with exports or a defined extract — live integration optional. Scope and data provision are set out in the offer.

Request pilot

Control License

The ongoing control center for your network — recurring.
Annual licensetiered by number of disciplines · indicative figures in the Fit Check
  • All domain packs for your networks
  • Read-only adapters to source systems
  • Ongoing updates & records logic

Roadmap: Field & Command App (in development, planned for Control License)

Request proposal

Operator Program

Multiple networks, custom integrations, SLA & security.
Customfor early operator partners
  • Dedicated live operator pilot
  • Security & Trust Center
  • Training & rollout support
  • Prioritized roadmap input
Schedule a call
In detailThe three tiers compared.Unclear points are never invented — they are openly marked as "individual" or "defined in the proposal."Expand

Table scrolls horizontally

CriterionPilotControl LicenseOperator Program
Scope
GoalProof of value on a real network sectionOngoing control center for your networkMultiple networks, custom integrations, SLAⓘ
Duration / Commitment8–12 weeks, time-limited, no follow-on commitmentAnnual licenseCustom
ScopeOne network section / one assetYour networks in the licensed sectorsMultiple networks / companies
Domain PacksⓘDomain pack for your sectorAll domain packs for your networksAll domain packs needed
Technology
Data SourcesExports or a defined section; live integration optionalRead-only adaptersⓘ to your source systemsCustom integrations, dedicated live operator pilot
Control center5D control center in your pilot instance5D control center in production + Field & Command App (in development)Same as Control License, separated across tenants
Records CatalogⓘRecords catalog + sample assetFull catalog per domain packExtensible to customer specifications
Support
OnboardingIncludedIncludedTraining & rollout support
SupportIncluded as part of the pilotDefined in the proposalSLAⓘ in the individual contract
UpdatesNo ongoing operation during the pilotOngoing updates & records logicOngoing + prioritized roadmap input
Security/Trust DocumentationOn requestOn requestDedicated Security & Trust Center
Contract & operation
Customer-Specific RulesNoBy arrangementYes
Operator InstancePilot instance (ring-fenced)Your own dedicated instanceYour own instance(s) per company
Pricing LogicFixed price from €29,500 (net) — 50% credited if a license is signed within six monthsTiered by number of disciplines — indicative figures in the Fit CheckCustom
Exit / HandoverEnds automatically, no commitmentTerms & notice periods defined in the individual proposalContractually defined, individual

Terms marked with ⓘ are explained in detail in the Glossary.

It starts this simply

Your pilot in three steps.

Not a months-long project to start — a real section, quickly put to the test.

30-minute Fit Check

30 minutes, no system access: we look at your use case together and clarify whether LAD works for you.

A section in the control center

We map one section — real structure, records, deadlines. No slide deck.

A decision backed by numbers

You see coverage, gaps and handover risk in black and white — and decide based on facts.

What the pilot measures

Four example KPIs — set in the Fit Check, measured in the pilot.

  1. Number of open handover items per gateHandovers that work the first time
  2. Share of deadlines with advance warning instead of overrunNo deadline falls through the cracks
  3. Search time to the recordAudit preparation without folder hunting
  4. Share of traceable status statementsKnowledge stays in-house
Request pilot ↓ Download info sheet (PDF)
For Project Management & ITThe pilot in detail — five phases.Expand for details, for anyone who wants to know exactly what happens during those 8–12 weeks.Expand
  1. 0Fit CheckAbout 30 minutes
  2. 1Scope & Data IntakeA few days
  3. 2MappingA few days to about a week
  4. 3ValidationA few days
  5. 4Proof of Value & DecisionOne joint review meeting
0Fit Check
  • Which sector?
  • Which network/project section?
  • Which operator problem?
  • Which source systems?
  • Which success question should the pilot answer?
EstimateAbout 30 minutes — one meeting, no system access needed.
InvolvedYou, on the business side, plus your initial contact at LAD — 30 minutes, no system access needed.
OutcomeA written, clearly scoped pilot area — before anything is connected.
1Scope & Data Intake
  • Asset/object structure
  • Selected document types
  • Metadata
  • Existing deadlines/gates
  • System access or file exports
  • Roles and contacts
EstimateA few days — depending on how quickly access or exports become available.
InvolvedYour business-side contact, plus IT for system access or exports. For your IT’s pre-review: IT checklist — in the pilot LAD works read-only, with no write access to source systems.
OutcomeA complete inventory of the pilot area — the basis for mapping in Phase 2.
2Mapping
  • Mapping of assets, document types and status
  • Records catalog for the section
  • Deadline/gate logic
  • Connection or controlled import
  • Control center configuration
EstimateA few days to about a week — the most compute-intensive step, mostly without active involvement from you.
InvolvedThe LAD team, with follow-up questions to your department if anything is unclear.
OutcomeThe pilot area is mapped in the control center — with real assets, records and deadlines from your network.
3Validation
  • Spot checks
  • Review with your department
  • Gap analysis
  • Traceability from status to record
  • Checking whether handover readiness is technically verifiable
EstimateA few days — requires active involvement from your department, so it can hardly be shortened.
InvolvedYour department actively reviews with us — spot checks, comparison, feedback.
OutcomeA substantiated statement on whether the displayed statuses are technically correct and traceable.
4Proof of Value & Decision
  • Before/after comparison based on the agreed KPIs
  • Open gaps
  • Data quality findings
  • Handover risk
  • Integration effort for the rollout
  • Recommended action
EstimateOne joint review meeting — prepared by LAD in advance.
InvolvedProject management, the department and, where relevant, IT/information security together.
OutcomeA fact-based decision — rollout, further validation, or a clean end.

The estimates describe the work steps themselves. The overall 8–12 weeks also include providing your data, coordination, approvals and validation meetings — we set the exact schedule based on the agreed scope.

Rollout makes sense

The proof of value holds up — the pilot moves into production.

Further validation needed

A few points need more clarification before a decision is made.

No rollout

The pilot ends cleanly, with no artificial commitment. That, too, is a valid outcome.

What we need from you for the pilot
  • Named business-side contact
  • A clearly scoped pilot area
  • Access to, or an export of, selected data
  • Existing document structure
  • Known target requirements, if available
  • One to two validation meetings
A benchmark, not marketingWhen is a pilot successful?There's no fixed success rate — it depends too much on the starting condition of your documentation. Instead, eight concrete criteria let you check for yourself whether the pilot h…Expand
0807060504030201k1 … k8
  1. Assets and documents are unambiguously linked within the pilot area.Concrete: Visible in the "By Area" tab — every asset shows its own documentation coverage instead of one combined figure.
  2. Critical target/actual gaps in documentation coverage have become visible.Concrete: As a percentage per area (e.g. "83% documentation coverage"), not a vague estimate.
  3. Status statements in the control center can be traced back to the underlying record.Concrete: Along the chain Principle → Gate → Record → Evidence, see above.
  4. Deadlines are displayed rule-based, no longer managed from memory.Concrete: Visible in the Deadlines tab — sorted chronologically, overdue items automatically listed first.
  5. At least one gate/handover status could be reviewed by the department.Concrete: Traceable in the "By Gate" tab — how many assets have reached a gate such as G4 · Approval.
  6. You can quantify the benefit compared to today's process using the agreed KPIs.Concrete: KPIs are defined during the Fit Check, not chosen after the fact to fit the result — see Phase 0.
  7. Integration and operating effort for a rollout are transparent — including open items.Concrete: Comparable using the Comparison Matrix — Pilot vs. Control License.
  8. IT and information security could assess the target picture using the IT Checklist.Concrete: All 12 points come with a short explanation.

If these points are not met, that is not a failure of the pilot — it is a result. See "Further validation needed" and "No rollout" above.

Continuity

Small is not a risk when the handover is arranged.

We answer the fair question “What if you are no longer available?” not with a promise but with a package you can hold in your hands.

  1. Master data exportYour complete status as a file — at any time, without us.
  2. Data modelThe description of all objects, attributes and rules.
  3. Release manifestWhich version of which catalogs and rules is running at your site.
  4. Continuation documentationWith a handover concept so your team or a service provider of your choice can carry on.

The business continuity package is included in the pilot; for the license we agree it in the offer. All questions on vendor & continuity in the FAQ →

Why you can trust LAD

Every green light is backed by evidence. The operator keeps authority.

The chainEvery statement in the control center follows this line — from principle to the individual record.

PrincipleHandover readiness
→
GateApproval
→
RecordTest report
→
EvidenceDocument · Version

Read-only at operational boundaries. LAD reads, organizes and displays — it does not switch anything and does not decide. The public interface stays open; privileged core systems remain separate. Built for critical infrastructure.

In detailWhat LAD does not decideExpand
What LAD does not decide
  • No switching actionsLAD has no write access to control systems — it reads and organizes, it does not switch anything.
  • No operational approval in place of the responsible personThe control center shows handover readiness — the approval itself remains with the designated role in operations.
  • No automatic legal compliance decisionMaking documentation coverage and deadlines continuously visible does not replace a legal assessment.
  • No acceptance in place of an inspector / expertThe chain of evidence leads back to the record — the technical review remains with your inspectors.
  • No changes to production source systems at operational boundariesRead-only adapters read existing systems, they write nothing back.
This is what the chain looks like in a concrete example
PrincipleHandover readiness for Gate G4 · Approval
→
GateG4 · Approval — blocked
→
RecordDeclaration of conformity missing
→
EvidenceSwitching Station South, Electricity Network

The same example as in the control center: the "1 record missing" status for Switching Stations traces back to exactly this one missing record — not just claimed, but verifiable.

Verify, don't just trustWhat you're welcome to verify before deciding.We don't say "trust us" — we show you exactly how to verify it yourself. Every point can be substantiated on this website or in the discovery call.Expand
For IT & Information Security

What your IT team can check before the pilot.

The full 12-point checklist for the initial architecture check is on the Security & Compliance page, alongside the architecture principle and data flow.

More questions on contract, data and operation: see the FAQ.

Now · get in early

Become one of the first network operators on LAD.

30 minutes, no system access, no slide deck. Using your use case, we'll check whether a solid pilot area can be scoped.

  1. Send a requestBriefly, your topic and your sector.
  2. 30-minute conversationOn your use case, no system access.
  3. A clear answerWhether a pilot area can be clearly scoped.
Go to the Fit Check form