{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Manufacturing Hub","title":"Ep. 242 - From Controls to MES Building Manufacturing Systems That Scale Without Breaking Operations","html":"","width":"100%","height":180,"duration":3527,"description":"In this episode of Manufacturing Hub, hosts Vlad Romanov and Dave Griffith welcome back Amos Purdy for a wide ranging conversation that connects plant floor reality with SCADA, MES, and the business decisions that actually fund modernization. Amos shares his path from early software and programming work into industrial automation, including building an industrial automation class and lab, leading MES and SCADA efforts, and working across industries where the pace, constraints, and validation expectations can feel like completely different worlds. If you have ever wondered why a solution that looks obvious on a whiteboard takes months or years to land on a production line, this episode breaks down the human, technical, and financial reasons in plain terms.A big thread throughout the conversation is what it takes to build systems that last. The group digs into hiring and mentoring for Ignition based teams, what backgrounds translate well, and why “hobbyist energy” can be a real superpower in interviews and on the job. The practical takeaway is simple: credentials help you get in the door, but projects help you stand out, especially when you can explain the problem, the architecture, and the tradeoffs you made. The conversation also gets real about legacy plants, where the constraint is often not ambition but risk, ROI, and operational disruption. The group frames modernization as a sequence of targeted moves that improve data availability, reduce cybersecurity exposure, and create a foundation for future applications without betting the entire facility on a massive rip and replace.You will also hear a grounded take on AI in industrial settings. The panel separates what is useful today from what is still hype, and explains why industrial AI needs context, standards, and purpose built training data to be trusted. They connect that to the “data transparency” problem: companies want answers faster, but the hard part is making the data accessible, reliable, and safe in...","thumbnail_url":"https://img.transistorcdn.com/yoKAvzBXZ3YjQTekFk7KFGXeuwJ29WgXvop3dVEfhLs/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzE3MjEzLzE2MDk0/MzA1OTgtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}