If you’ve ever been part of a major digital transformation in manufacturing, you know the feeling: the thrill of building something big, and the stress when the wheels start to come off. This is the story of the SAP MII “Video Wall Operations Center” project at a large Brazilian steel plant — a project that picked up two major industry awards, delivered real business value, and nearly burned out the team that made it happen.
The Setup: Why This Project Mattered
Back in 2008–2009, this steel producer was the biggest in Latin America, with a plant that could crank out 5 million tons of liquid steel a year. Their operations were sprawling: blast furnaces, steelmaking, continuous casting, rolling mills, and a supply chain that stretched from iron ore to finished coils. But information was scattered. Each department had its own dashboards, data lived in silos, and the supply chain team was always chasing its own tail. Everyone wanted real-time visibility, but nobody had it.
The goal was ambitious: centralize all production and supply chain data, and make it visible — live — to everyone who needed it, from shop-floor operators to senior management. The centerpiece would be a massive video wall in a new Operations Center, pulling live data from SAP, historians, PLCs, and even GPS trackers on material movements. It was one of the first attempts in the region to give manufacturing that kind of real-time, end-to-end visibility.
The Technical Challenge: Building the “Nerve Center”
On paper, the solution was elegant. We used SAP MII as the integration backbone, pulling data from dozens of systems — production tracking, quality management, asset monitoring, OEE, and more — and marrying it with SAP ERP. The video wall would display everything: live process KPIs, alerts, logistics flows, even camera feeds from the production floor. Operators could track steel from the blast furnace to the shipping dock, spot bottlenecks, and coordinate responses in real time.
But the reality was messy. The plant’s systems had grown up in silos over decades. Some lines ran on modern PLCs, others on ancient DCS systems. Data formats were all over the place. Some teams guarded their databases like family secrets. We had to write custom connectors for legacy systems, reverse-engineer undocumented interfaces, and sometimes convince skeptical engineers just to let us plug in a cable.
The video wall itself was a beast: dozens of screens, each showing synchronized dashboards, alerts, and live video. The amount of data moving across the network was massive. We spent weeks tuning performance, chasing down bottlenecks, and fighting with network latency. At one point, a single misconfigured switch brought down half the displays for a day. Not my favorite memory.
The Human Side: Pressure, Burnout, and Close Calls
Here’s the part most people don’t see: what it took from the team. We were a small, tight-knit group — maybe a dozen core people, but it felt like less when the crunch hit. The timeline was brutal. The client wanted the Operations Center live before the next fiscal year, and every department had their own “must-haves.” We worked weekends, pulled late nights, and lived on too much coffee and too little sleep.
Integration was a marathon of firefighting. Every time we fixed one data flow, another broke. There were days when we’d finish a 12-hour shift, only to get called back because a dashboard froze or an alert didn’t trigger. Our QA lead once slept under his desk. More than once, I had to pull people aside and tell them to go home before they crashed.
The pressure wasn’t just technical. The Operations Center was a flagship project for the plant’s leadership. Every delay, every bug, every missing KPI was visible — literally — on a screen the size of a bus. We felt watched, and we were. There were moments when the stress nearly broke us. I remember one week when three people threatened to quit. We lost two, and the rest of us had to pick up the slack.
The Turning Point: Why It Worked (and Almost Didn’t)
What saved us? A few things. First, we learned to say “no.” At the start, we tried to deliver every feature for every stakeholder. Halfway through, we realized that was impossible. We prioritized hard, cut scope, and focused on what really moved the needle: live production tracking, critical alerts, and the core supply chain flows. Some people were unhappy, but it meant we shipped something that worked.
Second, we leaned on each other. When someone hit a wall, someone else stepped in. We got better at sharing knowledge, documenting fixes, and dividing up the “hero” work. I stopped pretending I could do it all myself and started trusting the team more. That was a big lesson for me as a leader.
Third, we kept the end users involved — not just in requirements, but in testing and daily feedback. Operators gave us real-world scenarios we never would have thought of in the office. Sometimes their requests were painful to implement, but they made the system better (and more likely to be adopted).
The Aftermath: Recognition and Real Impact
When we finally went live, the change was obvious. For the first time, everyone had the same view of what was happening — production, logistics, quality, all in sync. Operators could answer questions about orders, equipment, and shipments in seconds, not hours. Supply chain risks were visible early. Decisions got made faster, and firefighting went down. The president of the plant called it “materializing the aspiration” of true integration. I’ll admit, that felt good.
The project picked up the 2010 SAP Strategic Reference Award and the 2010 ASUG Impact Award for technical excellence and business value. Those plaques looked great on the wall. But honestly, the best reward was seeing the system in use — and knowing we’d survived the journey.
Lessons Learned (and One Honest Opinion)
Looking back, here’s what I’d do differently — and what I’d keep the same.
- Don’t try to deliver everything. Ruthless prioritization is your friend.
- Protect your team from burnout. No project is worth losing good people.
- Get end users involved early and often. They’ll save you from yourself.
- Document everything. When you’re exhausted, your memory is useless.
- Celebrate the wins, even the small ones. It keeps people going.
And my honest opinion? Awards are nice, but they don’t heal burnout. If you’re leading a project like this, make sure you’re looking after your people — and yourself. The work matters, but so does the team that gets it done.
Leave a Comment