Latest / MBA Training Data / MES and ERP integration: the real Siemens Amberg win
Transcript
- 0:00Host: Welcome to the Leaders Insights Podcast.
- 0:07Host: Today's episode, how Siemens built a unified manufacturing data backbone by integrating
- 0:12Host: MES and ERP.
- 0:15Host: Everyone loves the Siemens-Amberg plant story, 99.99885% quality, robots everywhere, the poster
- 0:22Host: child for the smart factory.
- 0:24Host: So tell me the part the case studies leave out.
- 0:27Expert: The part they leave out is that the robots were never the hard bit.
- 0:31Expert: Amberg has been highly automated for over a decade.
- 0:34Expert: What actually moved the needle recently was boring plumbing, getting the MS and the ERP
- 0:39Expert: to stop lying to each other.
- 0:42Expert: MES is the Manufacturing Execution System, the software that runs the factory floor minute
- 0:48Expert: to minute, which machine makes what, when.
- 0:51Expert: ERP is enterprise resource planning, the business brain that handles orders, inventory,
- 0:57Expert: finance, classic setup, the floor knows one thing, the finance system believes another,
- 1:03Expert: and nobody reconciles until month end.
- 1:05Host: And month end reconciliation is where careers go to die.
- 1:08Expert: Right.
- 1:09Host: So the consensus lesson people draw from Amberg is invest in more automation, more sensors.
- 1:15Expert: Wrong lesson.
- 1:16Expert: Their real win was collapsing the gap between those two systems, so a production decision
- 1:21Expert: and a financial fact came from the same source.
- 1:24Host: That's unglamorous.
- 1:26Host: Nobody puts a data pipeline on the factory tour.
- 1:28Host: But isn't Integrate Your Systems the advice every consultant has given since 2005?
- 1:34Host: What's new?
- 1:35Expert: What's new is they stopped trying to build one giant monolithic system, the fantasy
- 1:39Expert: where a single platform does everything.
- 1:42Expert: That project always dies.
- 1:44Expert: Instead they treated manufacturing data as a product, with owners, contracts, and quality
- 1:49Expert: checks feeding both systems.
- 1:51Expert: DBT Labs and Alflagit, they sell the data transformation tooling, so crosscheck against
- 1:58Expert: independent work, reports customers cutting data pipeline failures sharply after adopting
- 2:03Expert: that model.
- 2:05Expert: Take the vendor number with salt, but the direction matches what O'Reilly's engineering
- 2:09Expert: surveys show independently.
- 2:11Expert: Modular beats monolithic.
- 2:13Host: You're dodging.
- 2:14Host: Give me a number that isn't from someone selling software.
- 2:17Expert: Fair.
- 2:18Expert: MIT Sloan Management Review has tracked this, wad.
- 2:22Expert: Firms that tie shop floor data directly to decision making, not just reporting, make
- 2:27Expert: production changes in hours instead of the weeks their peers take.
- 2:31Expert: That's the actual Amberg effect.
- 2:34Expert: Not fewer defects, faster reactions.
- 2:37Expert: When a supplier part shifts tolerance, the line adjusts before the bad units pile up,
- 2:42Expert: because the MES and ERP agree on reality in near real time.
- 2:47Host: So what does everyone get wrong when they copy this?
- 2:50Expert: They buy the dashboard and skip the discipline.
- 2:52Expert: A CDO, Chief Data Officer, the person accountable for data as an asset, walks in, commissions
- 2:58Expert: a gorgeous real time factory dashboard, and declares victory.
- 3:03Expert: Six months later, nobody trusts the numbers, because there's no data contract.
- 3:08Expert: No agreement on what a completed unit even means across systems.
- 3:12Host: Define that failure precisely.
- 3:14Host: Where does it actually break?
- 3:16Expert: The MES counts a unit complete when it leaves the line.
- 3:20Expert: The ERP counts it complete when it's booked to inventory.
- 3:23Expert: 10 minute gap, harmless, until someone builds a supply forecast on it and orders parts for
- 3:29Expert: phantom output.
- 3:31Expert: Multiply across a plant, and you're managing fiction with beautiful graphics.
- 3:35Host: That's the funny because it's true category.
- 3:38Host: So the fix is definitions, not technology?
- 3:41Expert: The fix is agreeing what a word means before you spend eight figures visualizing it.
- 3:46Expert: Students did the semantic work first.
- 3:48Expert: One definition of a unit, a batch, a defect, shared across both systems.
- 3:54Expert: Deeply boring.
- 3:55Expert: It's also why it worked when the flashier projects at other plants stalled.
- 3:59Host: Push back on yourself.
- 4:00Host: Isn't Amberg a special case?
- 4:02Host: Massive budget, one product family, German engineering culture?
- 4:06Host: Why should a mid-sized, discreet manufacturer believe any of this transfers?
- 4:11Expert: It transfers precisely because the expensive part isn't the part you need.
- 4:15Expert: You don't need their robot fleet.
- 4:17Expert: You need their reconciliation logic, and that's cheap.
- 4:21Expert: A mid-sized plant with 200 people can define shared metrics and wire mess to ERP integration
- 4:27Expert: for a fraction of the automation spend.
- 4:30Expert: The insight is portable, even when the hardware isn't.
- 4:33Host: Give me the one thing a CDO does Monday morning.
- 4:36Expert: Pull your MEES and ERP side by side and count how many units each says you made yesterday.
- 4:43Expert: If the numbers differ, and they will, you've just found your first project, and it costs
- 4:48Expert: nothing but a meeting to start fixing it.
- 4:50Host: Definitions before dashboards.
- 4:52Host: That'll do it.
- 4:53Host: Sources for today's episode.
- 4:55Host: Towards Data Science, KD Nuggets, The New Stack, DBT Labs, Vendor, Data Tooling, O'Reilly
- 5:02Host: Radar, MIT Sloan Management Review.
- 5:04Host: Done.
- 5:05Host: Want to know where you actually stand?
- 5:08Host: Take the CDO self-assessment at MBA-training.com.