Alfred PerlingerGuestStephanieHostNow that we know where the data comes from, so from this architecture, let's connect to data-driven solutions.
And here we do have the whole Centric ecosystem in place.
We've heard a lot about it already.
So what exactly or where exactly does a solution like Centric sit within this system architecture that you just explained?

So it connects the field data coming from the sensors with centralized software that evaluates the trends, generates alerts, and supports maintenance decisions.

In that sense, it is the bridge between the physical turnout and the practical asset management.
And if we didn't have that bridge, what would happen?

Without it, operators would miss much of the condition transparency and analytics-driven support that make proactive maintenance possible.

You would have less centralized visibility, fewer trend-based insights, and weaker integration with routine workflows.

In short, the monitoring might exist, but the system intelligence would be less effective.
And how does Centrek connect to systems that are already in use then?

Well, Centric integrates with superior ERP systems, for example, or with interlockings and control systems.

So it sends secure data to a central analytics platform where trends, alerts and recommended actions are brought together.

That is important because it allows condition monitoring to support existing processes instead of creating a separate data silo.
And that's what we definitely want to avoid, to have some silos in general.
And unfortunately, digitalization initiatives often create isolated silos, like you just explained.
Silos if this interoperability is not considered from the very beginning.
And therefore, why is interoperability that critical in railway infrastructure?

Well, because railway infrastructure already depends on multiple connected systems.

If turnout intelligence cannot integrate into that wider environment, much of its operational value is lost.

Interoperability is what allows local asset data to support network-level decisions, remote diagnostics, and also broader infrastructure management.
Could we also retrofit all of this on already existing turnouts?
Now that we know where the data comes from, so from this architecture, let's connect to data-driven solutions.
And here we do have the whole Centric ecosystem in place.
We've heard a lot about it already.
So what exactly or where exactly does a solution like Centric sit within this system architecture that you just explained?

So it connects the field data coming from the sensors with centralized software that evaluates the trends, generates alerts, and supports maintenance decisions.

In that sense, it is the bridge between the physical turnout and the practical asset management.
And if we didn't have that bridge, what would happen?

Without it, operators would miss much of the condition transparency and analytics-driven support that make proactive maintenance possible.

You would have less centralized visibility, fewer trend-based insights, and weaker integration with routine workflows.

In short, the monitoring might exist, but the system intelligence would be less effective.
And how does Centrek connect to systems that are already in use then?

Well, Centric integrates with superior ERP systems, for example, or with interlockings and control systems.

So it sends secure data to a central analytics platform where trends, alerts and recommended actions are brought together.

That is important because it allows condition monitoring to support existing processes instead of creating a separate data silo.
And that's what we definitely want to avoid, to have some silos in general.
And unfortunately, digitalization initiatives often create isolated silos, like you just explained.
Silos if this interoperability is not considered from the very beginning.
And therefore, why is interoperability that critical in railway infrastructure?

Well, because railway infrastructure already depends on multiple connected systems.

If turnout intelligence cannot integrate into that wider environment, much of its operational value is lost.

Interoperability is what allows local asset data to support network-level decisions, remote diagnostics, and also broader infrastructure management.
Could we also retrofit all of this on already existing turnouts?
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.