Data Science Talent Logo
Call Now

Bringing Intelligence to Steel: How SHS is Reshaping a Traditional Industry with AI by SHS Group

Dr Michael Schäfer is a technology expert with a PhD in Artificial Intelligence for Materials Science. He’s Head of AI & Digitalisation at SHS, founding and building the department and driving the enterprise-wide adoption of AI across the entire group.

Dr Anna Vocke studied physics in Mainz and Stony Brook. She joined SHS in late 2022 and now leads the company’s Specialised AI department, which develops and deploys tailored AI solutions in close collaboration with domain experts across the group.

Dr Ulrike Faltings studied mathematics in Bonn and Kaiserslautern. She leads the R&D group within SHS’s AI department, which focuses on more experimental AI approaches and solutions for internal projects. R&D also handles funded research projects.

Dr Tobias Bettinger has been working with AI in mechanical engineering since his research at Kaiserslautern University and RWTH Aachen University. He leads the Generative AI department, driving the group-wide adoption of generative AI and the implementation of scalable, production-ready use cases.

In our latest post, data experts from Stahl Holding Saar, the German holding company behind Saarstahl and Dillinger Steel, explain how AI is transforming one of the world’s oldest industries. Data and AI is now deployed across the entire production process at SHS, optimising performance, quality and yield. With such advancements being made, what does the future hold for AI in the heavy industry?

THE EVOLUTION OF AI AT SHS GROUP

By Michael Schäfer

For those unfamiliar with the steel industry, what does a modern steel plant look like today?

A modern steel plant is no longer simply a mechanical facility; it’s a digital ecosystem. Sensors, simulation, and automation work in combination to drive quality and efficiency. At SHS, significant investment in digitalisation, computer science, and AI runs throughout our steel and rolling mills. Equally important, though, is the human dimension: this transformation requires people with the mindset and willingness to embrace change.

Can you describe the mission of your AI team within SHS?

Our team’s focus is AI. Specifically, industrial AI for production environments. Importantly, we started long before the recent surge of public interest in AI.

We started in 2017 with just three full-time employees and one working student, with an exclusive focus on applying AI directly to our manufacturing processes. That focused foundation has been central to everything we’ve built since.

How has the AI team grown, and what does it look like today?

Since those early days, we’ve grown significantly and now operate across three distinct sub-departments, totalling 20 people. Today, we serve both Saarstahl and Dillinger Steel, as well as all subsidiary companies across the group.

The team is deliberately interdisciplinary, bringing together computer scientists, mathematicians, physicists, mechanical engineers, and computational linguists. That breadth of expertise is essential and it means AI now touches almost every part of our business.

How did the AI function evolve from those early days to where it is now?

When we started, AI was far from accepted even within the Industry. The turning point came from involving business units and domain experts early on, making AI a collaborative endeavour rather than something imposed from outside. Over time, we delivered projects with tangible production impact, and that track record built credibility.

If I were to distil our approach, it would be this: start early, prioritise collaboration, and stay open to new ideas. But fundamentally, it comes down to people. That has always been the most important factor.

Can you describe what each of the three sub-departments focuses on?

Each team has a distinct focus. Anna Vocke’s Specialised AI team concentrates on AI applications within steel production itself. Tobias Bettinger’s GenAI team is currently more active in administrative and business functions. Ulrike Faltings’s R&D team works across all areas of the business and leads our national and international research projects.

How would you describe the operational complexity of your data environment?

It’s significant. As a company with a long industrial history, we work across a broad and heterogeneous technology landscape, multiple databases, ERP and MES systems, and a large number of in-house applications.

On the sensor side alone, the range is striking: older facilities operate with around 500 sensors, while our newest continuous casting plant at Saarstahl has over 10,000. Managing that complexity is a core part of what we do.

Why does SHS operate its own data centres rather than relying on the cloud?

Speed and data security are the primary reasons. Steel production is a real-time environment and there is no tolerance for latency or downtime. Depending entirely on cloud infrastructure makes it extremely difficult to guarantee continuous availability.

Running our own data centres gives us the control and reliability that production demands. Temperature control in a steel mill is a good example of this. When you need to adjust conditions on the production line, waiting even ten seconds for a result is not an option. The decision has to happen immediately.

ANNA VOCKE

SPECIALISED AI IN STEEL MANUFACTURING

What has actually changed in steel manufacturing as a result of AI?

AI has made people braver. Steel production is a deeply traditional industry and AI has given people the confidence to test new approaches and challenge established ways of working. The suggestions generated by AI models create a kind of permission to experiment, and that shift in mindset is significant.

From a technical standpoint, we can now do things that were simply not possible a decade ago: optimising complex processes, implementing hyper-automation, and replacing static physical models with dynamic, data-driven alternatives. The pace at which we can develop and deploy models has increased dramatically, and that has a real impact on how we run our operations.

AI allows us to optimise and hyper-automate processes in ways that weren’t previously feasible. More specifically, it enables us to replace slow physical models with fast, dynamic AI models. The ability to deploy models rapidly and have them operate online rather than statically is a significant competitive advantage, in steel and across industry in general.

How is the Specialised AI team structured?

Much like the wider department, the team is deliberately interdisciplinary. We have computer scientists, mathematicians and I’m a physicist by background myself. That diversity of perspective is central to how we work. Approaching problems from different angles, drawing on different training and intuitions, is what allows us to tackle the complexity of what we’re dealing with.

What does ‘specialised AI’ actually mean in your context?

It means AI that is built specifically for our company and, more precisely, for each individual process we are working on. Our production processes are complex and highly particular so there is no viable off-the-shelf solution.

Every model we build is tailored to the data we have and the process it needs to describe. That specificity is the defining characteristic of what we do.

What methods and techniques does the team draw on?

The full spectrum of modern data science. For computer vision applications, we work for instance with YOLO models; for structured tabular data, gradient-boosted decision trees are a frequent choice. The method always follows the problem – we assess what the challenge requires, evaluate the available approaches, and adapt the most appropriate one to our specific data and process context. Given the diversity of our project portfolio, the range of techniques in active use at any one time is equally broad.

What types of operational problems is the Specialised AI team solving on a daily basis?

The range is again very broad. The classic operational challenges are increasing yield and reducing downtime, which we address through predictive and optimisation models. But we also work on safety-critical applications, using computer vision, for example, to identify when individuals have entered hazardous areas and trigger immediate alerts. The variety of problems is what makes the work genuinely interesting.

What does poor data quality look like in practice within a steel plant?

It takes many forms and it’s one of our most persistent challenges. Because steel is a traditional industry, data collection was never designed around a clean, structured model. It grew incrementally, and much of it still lives in Excel spreadsheets with inconsistent formats. In databases, we encounter missing columns, data entered into the wrong fields, and unexplained legacy entries that have never been cleaned up. Missing values are pervasive. All of this creates significant friction when building AI models.

In my experience, the single hardest part of any AI project is not the modelling itself, it’s acquiring clean, reliable data to work with.

How reliable is sensor data compared to other data sources in the plant?

Sensor data written directly to a database is genuinely the best-case scenario. It’s structured, timely, and consistent. That said, it isn’t without its own challenges. Sensors can fail, and quality still needs to be validated. The more insidious issue is data drift. Sensors degrade over time, furnaces are relined, raw materials change, and signals that were normal six months ago gradually shift.

For AI models that were trained on historical sensor data, that slow drift can be a serious problem and requires constant attention.

Where does poor data quality cause the most damage in practice?

It’s most painful when you have a compelling, well-reasoned concept for an AI model, one that would clearly deliver value, but the data simply isn’t there to build it.

Either it was never collected, or the quality is too low to be useful. We have techniques to work around certain data limitations, but there is a genuine ceiling. Without data, you cannot do data science. That is a frustrating reality when you have a strong idea and no way to realise it.

Can modelling from first principles bridge these gaps?

It can help at the margins. We do use first principles to supplement missing values when a partial data foundation exists. But replacing an entire AI model with first-principles modelling is a different matter entirely. Steel processes are extraordinarily complex. No model, for example, captures the processes and interactions inside a blast furnace in its entirety from first principles nearly impossible.

Our approach is to use first principles as a complement to data, not a replacement for it.

What does a robust data pipeline look like in a steel plant environment?

It starts with deep engagement with domain experts. You cannot build a reliable pipeline without understanding what normal process ranges look like, what variability is expected, and what constitutes an anomaly worth acting on. That knowledge gets built into guardrails and constraints that prevent your data from drifting silently into territory your model wasn’t trained to handle.

Beyond that, ongoing monitoring is non-negotiable. Models that perform well in training will degrade as conditions change. The discipline of continuously checking model performance against live production data and adapting when needed is what separates a robust pipeline from one that eventually fails quietly.

Which AI use cases have delivered the greatest value at SHS?

Two projects come to my mind here.

The first involved rethinking how we evaluate input materials. Rather than assessing them purely on purchase price, we modelled their impact across the entire production chain – from the blast furnace through the steel plant and into the final products and by-products sold to customers. A seemingly marginal difference in input material cost can translate into substantial savings when multiple across thousands of tons of daily output.

The second involved a quality issue that was putting a major customer relationship at risk. Working in close collaboration with domain experts, we traced the root cause of the defects and resolved it. The financial value of retaining that customer is difficult to quantify precisely, but the stakes were clear to everyone involved.

Those examples reflect the broader pattern well. Our AI-driven temperature models for the steel mills in Dillingen and Völklingen are another strong example as they consistently outperform the traditional physical models they replaced. Similarly, our ability to predict oxygen levels in steel has dramatically reduced the need for physical testing. Across these kinds of projects, production is where we have generated the most measurable financial impact.

Beyond model building, what are the biggest technical challenges you face?

Integration is the hardest problem. Every model we build has to operate within an existing IT and OT landscape that is highly heterogeneous: legacy systems, multiple vendors, and several generations of automation technology, all running simultaneously.

Getting a new AI model to integrate cleanly into that environment is frequently more demanding than building the model itself. Training on historical and real-time data is one thing; connecting it reliably to live production systems is another challenge entirely.

How do you validate models before they go live in production?

Our standard approach is parallel running. Before a model is given any control over the process, we deploy it alongside live operations. Its outputs are made visible to engineers and relevant stakeholders in the plant, but it isn’t acting on the process yet.

During this phase, we collect both the process data and the model’s predictions, and observe how domain experts interpret and respond to the outputs. This gives us a rigorous, real-world view of how the model would perform if fully integrated without any operational risk.

How do you detect model degradation or failure in a live environment?

Our most reliable mechanism is the domain experts themselves. Because they work with the model outputs daily, they are quick to notice when predictions become unrealistic or when something doesn’t look right. That human awareness is our most effective early warning system.

This matters enormously because model failure in practice is rarely a clean crash or an obvious error. It tends to be subtle; a slow drift in behaviour that could easily go unnoticed without someone who understands the process well enough to recognise that something is wrong. A forecast that looks statistically normal to a data scientist might be immediately implausible to someone with deep process knowledge.

Automated detection methods exist, but they are less reliable than an experienced human reviewing model outputs on a regular basis. Monitoring by a human expert is a deliberate and essential part of every project we run.

How do domain experts, who are not data specialists, develop confidence in working with AI models?

It’s one of the most rewarding aspects of the work. The journey typically starts with limited data literacy on the domain side. Through close project collaboration, where they share process knowledge and we share data knowledge, something genuinely shifts over time.

You find yourself in conversations with steelworkers who are asking sophisticated questions about model behaviour or data quality, concepts they’ve absorbed through months of working alongside us. They begin to challenge the data and the models in ways that are not only informed but genuinely useful, often pointing us in directions we wouldn’t have identified on our own.

It is a mutual education: we learn the process; they learn the data.

ULRIKE FALTINGS

AI FOR R&D

What does your R&D team actually do, and how does it differ from the other AI teams?

Despite the ‘R&D’ label, this is very much applied research as we’re still a steel plant. The distinction from the other teams is essentially one of certainty. Where the Specialised AI team typically works on projects where the approach is well understood and the outcome reasonably predictable, our work is more experimental.

We might read a research paper about a technique that looks promising for our environment and decide to test it. We participate in EU and German government-funded research programmes, and by definition, those projects come without guaranteed outcomes. That uncertainty is the point and it’s why the funding model exists.

What backgrounds does the R&D team bring together?

The profile mirrors the wider department: a blend of natural scientists and computer scientists, with a range of disciplinary backgrounds. That diversity of perspective is particularly valuable in an R&D context,

where the right approach to a problem is rarely obvious from the outset.

Can you give a concrete example of a recent R&D project?

A strong example is an EU-funded project to digitalise and partially automate the scrap handling process. We developed a new approach to building a dataset for steel scrap, then trained an AI model to classify different scrap varieties. Building on that, we trained a second model to predict the chemical composition of liquid steel based on the specific scrap inputs used.

Both models were genuinely experimental and success was not guaranteed going in. The results, however, were very promising, which made it a particularly satisfying project to work on.

How does the R&D team collaborate with the Specialised AI and GenAI teams?

The collaboration is close and deliberately flexible. There are no rigid boundaries between the teams. My team leads on research projects and carries the bulk of that work, but we work in close partnership with Anna’s team throughout.

As a model matures and moves from active development into ongoing supervision, it naturally transitions across. Equally, when our team is between funding cycles, we’ll contribute to projects in the other teams. I think that fluidity is essential. A purely research-focused team that operates in isolation risks losing touch with the realities of the plant floor. Maintaining close contact across all three departments keeps the work grounded and relevant.

What do you see as the most significant unsolved problems in industrial AI?

The hardest recurring challenge is optimising processes where the data you need simply doesn’t exist. Sometimes a subtle defect is causing problems somewhere in the process, but it’s so difficult to measure directly that you wouldn’t even know where to place sensors to capture it. It may be faintly visible beneath the noise in other sensor readings, but finding and isolating it is genuinely difficult.

The question we return to repeatedly is: how do you model a process when you lack the right data, and how do you find proxies that can take you closer to an answer? That challenge is compounded by the environment itself. A steel plant is inherently noisy and imperfect; nothing behaves the way it would in a controlled laboratory setting.

Your team works on experimental problems with uncertain outcomes. How do you persuade domain experts to invest time in projects that may never deliver a clear commercial result?

The honest answer is that if the commitment feels too open-ended to the people on the shop floor, the project simply won’t get off the ground and we respect that. What makes it work in practice is that the most experimental problems rarely need to be sold in. They tend to come to us.

An engineer has been sitting with an unsolved problem for years, sometimes decades. Typically this is something that resisted previous attempts because the techniques to tackle it didn’t yet exist. When they see an opportunity to finally address it, the motivation is already there. That intrinsic drive from the domain expert side is what makes these projects viable. Without it, the dynamic wouldn’t work.

We’ve worked hard to demonstrate that we are genuine partners and not just a technical team parachuting in with solutions.

That means sharing credit when things work, and being honest when they won’t, rather than letting people invest time in a dead end. The credibility we have today with the harder, more experimental problems is built entirely on the foundation of how we handled the easier, earlier ones. Without that track record, this kind of collaboration would be very difficult to sustain.

The future of heavy industry is often perceived to be physical. Do you see the steel industry heading in that direction?

Physical AI opens up genuinely compelling possibilities, particularly around safety. If autonomous systems can operate in environments that are hazardous for humans, the case for deploying them becomes very strong. It’s not just an efficiency argument, it’s a human one.

That said, I think widespread practical application in steel is still some years away. It’s a development we’re watching closely rather than actively building towards right now.

It’s relatively uncommon to have a dedicated research function within a team of 20 people. What motivated that decision?

Staying at the cutting edge requires active investment in research and it doesn’t happen passively. To remain competitive, you have to engage with the state of the art, not just apply what’s already well established.

Having a research capability gives us direct access to new ideas, and it enables us to connect with other steel plants, researchers, and data scientists across Europe. That exchange of methods, perspectives, and approaches to shared problems is a significant advantage. You learn things from those conversations that you simply wouldn’t encounter by staying within your own environment.

TOBIAS BETTINGER

GENAI AT SHS

Tobias, what role does generative AI play at SHS, and where is it currently being applied?

While GenAI dominates the public conversation about AI, it’s worth noting that it represents just one strand of a much broader AI programme at SHS. Currently, our GenAI work is focused on administrative functions.

One significant area is the technical feasibility analysis of customer requirements, a process that currently takes domain experts up to two weeks to complete manually. AI can accelerate that considerably. A second area is the automation of customer enquiry handling, where we receive large volumes of unstructured information per email that staff currently process by hand. Both represent strong candidates for AI-assisted workflows.

GenAI is associated with risks such as hallucinations and safety concerns. How do you manage those, and are there areas where you’ve chosen not to deploy it?

Those risks are real, and they directly shape our deployment decisions. In a steel plant environment, where safety is critical, the consequences of a hallucinated output could be serious. For that reason, we are not deploying fully agentic GenAI systems in production processes at this stage.

All current use cases retain a human in the loop as a deliberate safeguard. As the technology matures and our understanding of the risk profile deepens, production applications may become viable, but that is a decision for the future, not the present.

Are you working with multi-agent systems, or primarily single-agent approaches?

Mostly single-agent systems for now, though there are specific use cases where a multi-agent architecture is the more appropriate solution. Our current priority is to map and formalise the workflows that experienced human teams already follow and then translate that logic into agentic AI systems.

Getting that foundation right is the essential first step.

How do you capture the domain knowledge needed to build effective agentic systems?

The process mirrors what the wider AI department does across all its projects: close, structured collaboration with the people who hold the knowledge. We run workshops with domain experts to understand their daily work in detail: what decisions they make, what information they draw on, and what the logic of their workflows actually looks like.

That knowledge then forms the basis for designing the agent. Without it, you cannot build a system that genuinely replicates or supports the way people work. The workshops aren’t a preliminary step; they’re central to the whole process.

How do you establish guardrails in your GenAI systems to manage risk?

Our centralised GenAI platform is the cornerstone. It incorporates elicitation prompts at key points in workflows which are essentially human-in-the-loop checkpoints that intercept potential errors before they reach downstream processes.

Beyond that, we follow the same parallel testing approach used by the other teams: running the system alongside domain experts and process owners before any production sign-off. Governance is built in from the start, not added as an afterthought.

What are the biggest barriers to adoption?

Somewhat counterintuitively, it’s not resistance from people as our domain expert collaborators are generally engaged and motivated. The real friction is integration complexity.

Operating across a heterogeneous IT landscape with numerous proprietary systems makes accessing the right data structures and sources genuinely difficult. That is consistently where the most effort goes.

What is your GenAI model strategy: commercial foundation models or locally hosted alternatives?

Both, depending on the context. For the majority of use cases, we use OpenAI models deployed via Azure as they provide the capability and scale we need. Where sensitive data is involved, we switch to locally hosted models to ensure nothing leaves our environment.

Operating in a hybrid setup gives us the flexibility to make that distinction cleanly and consistently.

What has been your standout GenAI success so far?

Our internal GenAI platform. It gives employees across the business a single, governed interface for getting answers to everyday questions – replacing the fragmented process of searching across multiple systems. The fact that it also handles security and governance centrally makes it doubly valuable. It’s the foundation on which everything else is being built.

How does your team use GenAI in your own daily work?

Coding assistance is the most widely adopted application across our team and the broader IT function. The productivity gains are tangible. The important caveat, though, is that you need strong underlying expertise to use it well. Knowing how to frame instructions clearly and being able to evaluate the output critically requires genuine technical understanding. GenAI amplifies capability; it doesn’t replace the judgment needed to direct it effectively.

What emerging technologies or model developments are you most excited about?

The pace of development in GenAI is itself remarkable. Release cycles are extremely short, and keeping up is a genuine challenge. Rather than a specific model, what excites me most is the trajectory: each new release expands what’s possible, and that momentum shows no sign of slowing.

The shift I find most significant is the move from very large, general-purpose language models towards smaller, more specialised ones. The practical implication is striking. Within weeks rather than months, it will be possible to run powerful multimodal models on standard hardware. That dramatically lowers the barrier to deployment and opens up new possibilities for how and where we apply these models within our environment.

What is the strategic vision for AI at SHS going forward?

The goal is straightforward: to make the entire SHS group AI-powered. Not AI for its own sake, but AI applied wherever it delivers genuine, measurable value.

The pieces are coming together, and the direction is clear. Over the next few years, we expect AI to be operating across significantly more of our processes, optimising, automating, and further strengthening our competitiveness.

Back to blogs
Share this:
© Data Science Talent Ltd, 2026. All Rights Reserved.