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.
Start small. Grow with your network.
You pay for the tier you need — nothing more. No big-bang rollout, no system change.
Pilot
- 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 pilotControl License
- 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 proposalOperator Program
- Dedicated live operator pilot
- Security & Trust Center
- Training & rollout support
- Prioritized roadmap input
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
| Criterion | Pilot | Control License | Operator Program |
|---|---|---|---|
| Scope | |||
| Goal | Proof of value on a real network section | Ongoing control center for your network | Multiple networks, custom integrations, SLAⓘ |
| Duration / Commitment | 8–12 weeks, time-limited, no follow-on commitment | Annual license | Custom |
| Scope | One network section / one asset | Your networks in the licensed sectors | Multiple networks / companies |
| Domain Packsⓘ | Domain pack for your sector | All domain packs for your networks | All domain packs needed |
| Technology | |||
| Data Sources | Exports or a defined section; live integration optional | Read-only adaptersⓘ to your source systems | Custom integrations, dedicated live operator pilot |
| Control center | 5D control center in your pilot instance | 5D control center in production + Field & Command App (in development) | Same as Control License, separated across tenants |
| Records Catalogⓘ | Records catalog + sample asset | Full catalog per domain pack | Extensible to customer specifications |
| Support | |||
| Onboarding | Included | Included | Training & rollout support |
| Support | Included as part of the pilot | Defined in the proposal | SLAⓘ in the individual contract |
| Updates | No ongoing operation during the pilot | Ongoing updates & records logic | Ongoing + prioritized roadmap input |
| Security/Trust Documentation | On request | On request | Dedicated Security & Trust Center |
| Contract & operation | |||
| Customer-Specific Rules | No | By arrangement | Yes |
| Operator Instance | Pilot instance (ring-fenced) | Your own dedicated instance | Your own instance(s) per company |
| Pricing Logic | Fixed price from €29,500 (net) — 50% credited if a license is signed within six months | Tiered by number of disciplines — indicative figures in the Fit Check | Custom |
| Exit / Handover | Ends automatically, no commitment | Terms & notice periods defined in the individual proposal | Contractually defined, individual |
Terms marked with ⓘ are explained in detail in the Glossary.
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.
Four example KPIs — set in the Fit Check, measured in the pilot.
- Number of open handover items per gateHandovers that work the first time
- Share of deadlines with advance warning instead of overrunNo deadline falls through the cracks
- Search time to the recordAudit preparation without folder hunting
- Share of traceable status statementsKnowledge stays in-house
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
- 0Fit CheckAbout 30 minutes
- 1Scope & Data IntakeA few days
- 2MappingA few days to about a week
- 3ValidationA few days
- 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?
1Scope & Data Intake
- Asset/object structure
- Selected document types
- Metadata
- Existing deadlines/gates
- System access or file exports
- Roles and contacts
2Mapping
- Mapping of assets, document types and status
- Records catalog for the section
- Deadline/gate logic
- Connection or controlled import
- Control center configuration
3Validation
- Spot checks
- Review with your department
- Gap analysis
- Traceability from status to record
- Checking whether handover readiness is technically verifiable
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
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.
- 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
- 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.
- 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.
- Status statements in the control center can be traced back to the underlying record.Concrete: Along the chain Principle → Gate → Record → Evidence, see above.
- Deadlines are displayed rule-based, no longer managed from memory.Concrete: Visible in the Deadlines tab — sorted chronologically, overdue items automatically listed first.
- 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.
- 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.
- Integration and operating effort for a rollout are transparent — including open items.Concrete: Comparable using the Comparison Matrix — Pilot vs. Control License.
- 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.
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.
- Master data exportYour complete status as a file — at any time, without us.
- Data modelThe description of all objects, attributes and rules.
- Release manifestWhich version of which catalogs and rules is running at your site.
- 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 →
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.
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
- 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.
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
- Architecture principle — an organizing layer above existing systems, not a replacement. See Solution.
- Read-only boundaries — what LAD reads and what it explicitly does not change. See "What LAD does not decide" above.
- Data flow — which data flows where, and what never leaves the network. See FAQ "Data, Data Sovereignty & Security".
- Roles/permissions — who decides what in the pilot and operator project. See FAQ "Records Logic & Data Quality".
- Pilot scope — exactly what is defined during the Fit Check, before anything is connected. See Pilot Blueprint, Phase 0.
- KPI definition — exactly how you measure the benefit. See “What the pilot measures” and "When is a pilot successful?".
- Example chain of evidence — Principle → Gate → Record → Evidence. See the chain above.
- Exit logic — what happens to components, data and configurations upon termination. See FAQ "Contract, Costs & Exit".
- Security documentation — available on request, for your specific case. See Comparison Matrix.
- Contract/SLA framework in the Operator Program — defined in the individual proposal, not promised across the board. See Comparison Matrix.
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.
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.
- 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.
