Put connections into context
Inputs and targets can be related through shared information logic.
Expert topic · Information logic
A central layer for data and metadata.
When individual integrations implement separate rules for each channel, the shared information logic can become harder to follow. A central integration layer consolidates information from input channels, transforms different structures into a consistent form and prepares the result for each receiving system.
Digital operation power. Bundled. Anytime!
01 · Input
Receive information
Data and metadata come together from different input channels.
02 · Central layer
Bring logic together
Structures are put into context, normalised and prepared for delivery.
03 · Target side
Deliver appropriately
Receiving systems obtain information in the context they need.
Architecture idea
Information logic sits between origin and receiving systems.
When data from different inputs and for different targets is considered, its information logic needs a traceable place. The central layer describes that functional middle.
It does not eliminate every peculiarity of the system landscape. It does make clear which structures and metadata need to be put into context between input and receiving systems.
Three separate layers
Do not merge origin, preparation and target.
Separating the layers provides a discussion model for data flows and their requirements.
-
01
Separate inputs
Data sources and their metadata are treated as the origin of information.
-
02
Bring preparation together
Normalisation and contextualisation are described in a central layer rather than being assigned to individual inputs or targets.
-
03
Assign receiving systems
Target systems are considered in terms of which prepared information they need for their task.
Operational context
A traceable middle in the data flow.
Separate responsibilities
The roles of origin, normalisation and receiving systems are not merged.
Discuss dependencies
The central layer creates a clear place to describe handovers and requirements.
In focus
Questions for the central layer.
The central layer is a functional model for information logic. It does not assert a particular product or fixed technical architecture.
- Which information is consolidated from inputs?
- Which differences need to be normalised or put into context?
- Which metadata does later processing need?
- How is preparation separated from receiving systems?
Frequently asked questions
Put the central layer into functional context.
The answers describe the role of central information logic in the established data model.
What is a central integration layer for?
It brings together data and metadata from different input channels, normalises their structure and prepares them for receiving systems.
Why is preparation described centrally?
A central view separates information logic from individual inputs and targets. This makes it clearer where differences are put into context and metadata is prepared.
Does a central layer replace target systems?
No. Target systems remain receivers of the information they need for their task. The central layer describes the preparation that happens before receiving.
How does the central layer relate to metadata?
It puts metadata into context together with input data, transforms different structures into a consistent form and prepares them for delivery.
When does a central integration layer become relevant?
It becomes relevant when channel-specific integrations maintain separate rules and the shared information logic becomes harder to follow or change. A central layer provides one place for normalisation and target-specific preparation.
Next step
Let us describe the middle of your information flow.
Together, we can put into context what a central layer does between input channels and receiving systems.