{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Manufacturing Hub","title":"Ep. 246 - Building a Life Sciences Virtual Factory Enterprise C, MQTT, and UNS w/ Amy Williams","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/85e45f05\"></iframe>","width":"100%","height":180,"duration":3888,"description":"In this special ProveIt edition of Manufacturing Hub, Vlad Romanoff and Dave Griffith sit down with Amy Williams from Skellig Automation to unpack Enterprise C, a life sciences virtual factory built to look and feel like the reality inside many regulated facilities today. If you work around batch processes, compliance, historian projects, electronic batch records, or industrial data architecture, this conversation is a practical walkthrough of what it actually takes to turn raw signals into a story you can defend, improve, and scale.Amy has spent years working exclusively in life sciences manufacturing, starting deep in DeltaV automation for batch pharma and moving into digital transformation projects that focus on open architectures, modern data pipelines, and real operational outcomes. In this episode, she explains what Enterprise C is simulating, why it was designed as an Industry 3.0 style biotech startup, and what kind of data and documentation a vendor would have to wrestle with in the real world. The factory is producing a fictional enzyme using a fed batch fermentation process, and the UNS publishes realistic one second resolution batch data across four pieces of single use equipment including a mixer, a bioreactor, a chromatography skid, and a TFF skid.One of the most valuable parts of this episode is the reminder that data sitting in an MQTT broker is not inherently valuable. The value comes when the data is contextualized enough that different teams can use it without tribal knowledge, and when the resulting traceability helps you answer the questions that matter in life sciences. What happened during the batch, what changed compared to previous runs, what went out of spec, what documentation proves compliance, and what you should do next time to avoid losing a batch that can cost millions. Amy also explains why Enterprise C intentionally includes uncontextualized tags and paper files, because that is exactly where many facilities still are. The hard...","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}