{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Manufacturing Hub","title":"Ep. 274 - David Schultz on ISA 95, Knowledge Graphs, and Building a Data Model for AI","html":"","width":"100%","height":180,"duration":4016,"description":"There is no pyramid anywhere in the ISA 95 standard. David Schultz explains what is actually inside it and how to turn it into a working data model.\nMost engineers meet ISA 95 as a layered triangle on LinkedIn and never get past it. David Schultz of Amárach StackWorks takes that image apart. The pyramid appears nowhere in the standard, which exists to define how business systems such as ERP exchange information with manufacturing and control systems. Eight parts are published today, Part 1 refreshed in 2025, with Part 9 still in committee. Start with Parts 1 and 2. Part 1 sets the scope, Part 2 delivers the resource, information and process models. Parts 3 and 4 add the activity models and the work master. Parts 5 and 6 supply the verbs and exchange patterns.\nFrom there it collapses into a frame you can hold in your head: four resources of equipment, physical asset, personnel and material, four domains of production, maintenance, quality and inventory, and four exchanges covering definition, capability, schedule and performance. Use what works and leave the rest. On adoption David is candid. The full set runs roughly $1,400, and the paywall keeps it out of most LLM workflows because ISA would forfeit copyright by opening it up.\nWhere it breaks is data governance. When every site builds bespoke models, stitching them together means inventing a fourth abstraction. Vlad offers a first hand version from Procter and Gamble, where nobody at plant level owned the data structure moving from Rockwell controls into Proficy. For brownfield sites the advice is the Strangler fig pattern: leave what runs and replace functionality over time.\nThe second half demystifies knowledge graphs using a family tree. A graph stores a subject, a predicate and an object, and the relationship is a first class citizen, not a foreign key. RDF defines the things, RDFS adds schema, OWL adds inference so a system can derive siblings from a shared parent, and SHACL constrains the shapes. Applied...","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}