Linea AureaDocumenta
System Connections

Read-only, connected to your systems — without a system change.

Everything on integration in one place: architecture, a concrete example per source system, sync status, how connection works today and the limits of a read-only adapter. For your IT security team, see Security & Compliance.

Where things stand today: in the pilot, LAD works with exports or a defined extract — without touching your systems. Read-only adapters for ongoing operation are set up in the operator project. The sync figures on this page are sample values. More

Connection & Evaluation

Sits above your systems — and keeps track of their status.

Read-only and vendor-neutral. LAD can be connected to practically any network operator system already in use — without a system change:

Your systems
read-only · reads regularly
LINEA AUREA · Control Centerorganizes records, checks deadlines, shows coverage — read-only, without a system change
sits above
shows & evaluates
By AreaBy RoleBy GateRisk StatusDeadlinesSource SystemsComparisonBy Team

The same view as in the control center — by area, role, gate, risk, deadline, source system, in the sector comparison and by team.

and much more — practically any network operator system already in use. Click a system — the example further below shows in concrete terms what LAD reads from it.
Concrete instead of abstract

This is how an object from your system reaches the control center.

Seven common source systems, one example each: what LAD reads read-only — and what becomes of it in the control center. Synthetic, to illustrate the principle.

In detailTwo objects in detailAn asset from SAP and a document from the CDE — field by field, as it arrives in the Control Center.Expand
GISQGIS / ArcGIS

Geodata layer for a cable route — accessed read-only, not changed.

From the source system
  • Layer: Cable routes
  • Object ID: KT-2291
  • Geometry type: Line · Underground cable
  • Attribute: Built 2019 · Material XLPE
In the control center
  • Asset: Cable Route A9 · Underground Cable
  • Record type: Laying & test protocol
  • Gate: G3 · Construction
  • Geometry link: jump-back to GIS retained
CDECDE / BIM Platform

An execution plan from an ongoing construction project in the CDE.

From the source system
  • Project folder: 03_Execution Planning
  • Document: Pipeline plan Rev. C
  • Status in CDE: Released for review
  • Metadata: Trade, revision, date
In the control center
  • Asset: Transfer Station North
  • Record type: Execution plan
  • Version: Rev. C · current
  • Gate: G3 · Construction
SPSharePoint

A test report from a project library.

From the source system
  • Library: Grid Expansion Project 2026
  • Folder: Approvals
  • File: ProtectionTestReport_SubstationNorth.pdf
  • Metadata: Filing date, approval note
In the control center
  • Asset: Substation North
  • Record type: Protection test report
  • Inspection deadline: next inspection 07/2027
  • Status: met
SAPSAP PM / EAM

An equipment record from the asset master — accessed read-only, not changed.

From the source system
  • Equipment: 10004521 · Switching Station South
  • Assembly: Medium voltage · Bay 2
  • Maintenance order: 45231 · open
  • Status in SAP: In operation
In the control center
  • Asset: Switching Station South
  • Record type: Declaration of Conformity
  • Gate: G4 · Approval
  • Link: maintenance order retained as reference
ELOELO DMS

An archived test protocol from the document store.

From the source system
  • Filing structure: Assets \ Substation North \ Bay 3
  • Document: InspectionRecord_2024.pdf
  • Version: 2.1 · released
  • Retention deadline: 10 years · ELO rule
In the control center
  • Asset: Substation North · Bay 3
  • Record type: Inspection record (in service)
  • Retention deadline: adopted from ELO rule
  • Gate: G5 · Handover
JRJira

An open defect issue for an asset.

From the source system
  • Issue: NETZ-4471 · Defect
  • Summary: Earthing measurement overdue
  • Status in Jira: In progress
  • Assigned: Maintenance Team East
In the control center
  • Asset: Cable Route A9
  • Record type: Earthing measurement
  • Status in control center: open · Gate G3
  • Link: issue retained as reference
CFConfluence

An operating instruction as a network-wide standard.

From the source system
  • Space: Electricity Network Operations
  • Page: BA-014 · Medium-voltage protection test
  • Version: v6 · updated
  • Status: published
In the control center
  • Scope: Cross-Cutting Documents
  • Record type: Operating instruction / standard
  • Link: linked to affected assets
  • Version: v6 · current

The same principle applies in every case: the document stays in its source system. LAD reads metadata, links it to the asset, deadline and gate — and writes nothing back. The same principle applies to the SAP example in the data flow explanation at Security & Compliance.

Sync Status

Seven source systems, one shared status.

Seven common source systems with their sync status — exactly as they appear in the document room (the "Source Systems" tab) and in the control center. Preview with synthetic data.

SAPSAP PM / EAM

Asset master data, equipment, maintenance orders.

synced2,418 objects
ELOELO DMS

Document storage, version states, retention deadlines.

synced14,207 documents
SPSharePoint

Project & construction files, approvals, storage.

synced6 project spaces
JRJira

Tasks, defects and actions per asset.

synced312 issues
CDECDE / BIM Platform

Project folders, plans and models from the construction phase.

synced3 construction projects
GISQGIS / ArcGIS

Network topology, routes, asset geometry.

syncedNetwork map linked
CFConfluence

Operating instructions, standards, knowledge.

synced87 pages
+More systems

Practically any system a network operator runs — via connector, interface or file import.

Specialist applications · sector systems …
Status today

How LAD reaches your systems today.

To be clear: we do not assume ready-made standard connectors. In the pilot, LAD works with exports or a defined extract — without touching your systems. The read-only adapters for ongoing operation are set up in the operator project for your specific system landscape.

In detailAll connection paths at a glancePer source system: path today, pilot variant and live expansion.Expand

Table scrolls sideways

Source systemIn the pilot · no live integrationIn operation · Control License
SAP PM / EAMExport of equipment and orders (e.g. CSV/Excel)
Read-only adapterRead-only adapter via the interface the system provides — set up in the operator project
ELO / DMS / ECMMetadata export of the archive: path, version, status, deadlinesRead-only adapter via the interface the system provides — set up in the operator project
SharePointExport of libraries or lists with metadataRead-only adapter via the interface the system provides — set up in the operator project
Jira / ConfluenceExport of issues or pages related to the assetsRead-only adapter via the interface the system provides — set up in the operator project
CDE / BIM platformDocument list with status and revisionRead-only adapter via the interface the system provides — set up in the operator project
QGIS / ArcGISObject and attribute export (e.g. GeoPackage, Shape, CSV)Read-only adapter via the interface the system provides — set up in the operator project
Folders & file sharesFile list with path, date and file propertiesRegular reconciliation of the file list — set up in the operator project

Which interface your system offers and how often data is reconciled is clarified in the Fit Check. What an adapter never does is shown right below.

Read-only Adapter

What a read-only adapter explicitly does not do.

The term from the glossary: Read-only Adapter — 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.

  • No changes to production source systems at operational boundariesRead-only adapters read existing systems, they write nothing back.
  • No back-channel into the source systemsNo write access at operational boundaries — the standard case is the metadata layer, see data flow.
  • No migration, no data moveYour documents stay where they are — in SAP, ELO, GIS, SharePoint or in grown folder structures.

What your IT team can concretely review before the pilot regarding interfaces, roles and data classes stands in the IT Checklist on the Security & Compliance page.

Frequently Asked

What network operators ask first about systems & integration.

The four most common questions on systems and integration. More answers in the "Systems & Integration" section of the FAQ.

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.

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.

All 43 in-depth questions — organized by Systems & Integration, Security, Records Logic, Audit, Pilot & Onboarding, Operations & Scaling, Contract, Cost & Exit as well as Vendor & Continuity — are answered in the full FAQ.

Questions about your specific systems? Let's clarify them directly.

30 minutes, no system access: using your use case we check whether a pilot area can be clearly scoped — no slide deck.

  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.
Request 30-minute Fit Check