<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vladimir Romanov on Medium]]></title>
        <description><![CDATA[Stories by Vladimir Romanov on Medium]]></description>
        <link>https://medium.com/@vrom?source=rss-2c74f814558a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QunY_exyS4bEB9D5Uplfyg.jpeg</url>
            <title>Stories by Vladimir Romanov on Medium</title>
            <link>https://medium.com/@vrom?source=rss-2c74f814558a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:40:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vrom/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Understanding Networks 101: Building the Foundation for OT Systems]]></title>
            <link>https://vrom.medium.com/understanding-networks-101-building-the-foundation-for-ot-systems-2195b045d50a?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2195b045d50a</guid>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Mon, 17 Nov 2025 01:26:40 GMT</pubDate>
            <atom:updated>2025-11-17T01:26:40.910Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJUpVYNO1bdY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJUpVYNO1bdY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJUpVYNO1bdY%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/adaad83a3e17527d250d85b7af9c61a5/href">https://medium.com/media/adaad83a3e17527d250d85b7af9c61a5/href</a></iframe><h3>Introduction</h3><p>Understanding how networks function is the foundation for anyone working in operations, engineering, or systems integration. Before we can design, secure, or optimize industrial systems, we need to step back and understand how devices talk to one another. The same way signals travel across your home network from your laptop to your router to the cloud, data flows across the factory floor. The difference lies in how we manage, protect, and scale that communication inside an operational environment.</p><p>In this article, we will expand beyond the video lesson to connect the dots between <strong>consumer networking and industrial networking</strong>. We will explore what makes a simple home network both powerful and limiting, and how those same principles evolve inside a manufacturing plant. This foundational knowledge helps build toward more advanced concepts such as VLANs, subnets, managed switches, and industrial firewalls.</p><p>A strong understanding of networking fundamentals is the single most important step toward mastering <strong>OT and industrial systems integration</strong>. It allows engineers and technicians to visualize how information moves between sensors, controllers, and higher level systems such as SCADA or MES. Once you see the structure, you begin to see where performance bottlenecks, communication gaps, and cybersecurity vulnerabilities emerge.</p><p>This is not a theoretical overview. It is a <strong>practical guide</strong> meant to help you recognize familiar concepts from everyday technology and apply them to industrial networks that demand higher reliability, tighter control, and stronger security. If you are new to these topics, start here, build confidence in the basics, and then continue exploring how these same principles scale within real production environments.</p><p>For a deeper look at how networking and data connectivity form the backbone of modern plants, read<a href="https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing"> <strong>Unlocking Industrial Data in Manufacturing</strong></a>.</p><h3>What a Basic Network Actually Is</h3><p>Every network, whether in your home or inside a production facility, follows the same essential principle. Information must move from one place to another in a structured and reliable way. Understanding how this flow happens on a small scale helps engineers appreciate the complexity of large industrial networks. <strong>A basic network is simply a pathway that allows devices to exchange information through clearly defined layers and components.</strong></p><p>In homes, that pathway begins with your internet provider. On the plant floor, it begins with a carefully designed network boundary that separates operational systems from the outside world. The foundation is the same, but the implementation could not be more different.</p><figure><img alt="Lecture 2.3.1 — Home Networks to Plant Networks" src="https://cdn-images-1.medium.com/max/1024/0*DUiC0R8ETaWnZlt6" /><figcaption>Lecture 2.3.1 — Home Networks to Plant Networks</figcaption></figure><h3>The Role of the Internet Service Provider (ISP)</h3><p>An Internet Service Provider, or ISP, is the company that delivers your connection to the internet. It is the invisible bridge between your local devices and the wider web. In your home, this might be a regional telecom provider. In a factory, the equivalent is the organization or infrastructure that connects the plant network to the corporate network or external systems such as cloud services.</p><p>In industrial environments, this external link might take several forms:</p><ul><li><strong>Remote support connections</strong> that allow engineers or vendors to troubleshoot equipment from outside the facility.</li><li><strong>Corporate VPNs</strong> that securely connect plants to enterprise data centers or cloud applications.</li><li><strong>Cloud platforms</strong> that collect production data, run analytics, or host dashboards accessible to decision makers.</li></ul><p>In both homes and industrial settings, the ISP or external gateway is the single entry and exit point for all data traffic. It defines how securely, quickly, and reliably information moves beyond local boundaries. Poorly configured connections can lead to downtime, security incidents, or unauthorized access. The same fundamental rules that govern your home internet apply to industrial networks, but the stakes are far higher.</p><p>For a detailed look at how industrial connectivity is expanding through modern platforms, explore<a href="https://www.joltek.com/blog/edge-solutions-industrial-automation"> <strong>Edge Solutions in Industrial Automation</strong></a>.</p><h3>Modem and Router: Translating and Routing the Signal</h3><p>To understand how data travels between networks, we need to look at two core devices that every network relies on: the modem and the router.</p><p>A <strong>modem</strong> converts one type of signal into another. It receives data from the ISP as analog or optical signals and converts them into digital packets that can move across your internal network. The term modem comes from the words modulation and demodulation, which describe this process of encoding and decoding data for transmission.</p><p>A <strong>router</strong> takes the data received by the modem and decides where that information should go. It assigns IP addresses to connected devices and ensures that each message reaches the correct destination. In a home, the router typically handles both wired and wireless connections. It decides how your laptop, phone, and smart TV each access the internet through a single shared connection.</p><p>Modern consumer devices often combine both functions into a single box. However, in industrial settings, these components are more specialized and separated for better control and reliability. A plant network may use industrial routers, firewalls, and managed switches to create multiple layers of security and segmentation. This separation allows engineers to protect critical control systems from unnecessary exposure while still enabling controlled data exchange.</p><p><strong>In manufacturing environments, physical and logical separation is not a luxury but a requirement for safety, uptime, and security.</strong></p><p>When you understand how a simple home modem and router pair functions, you can better grasp the structure of industrial communication systems. The difference is that plant networks must ensure deterministic communication, redundancy, and resilience under demanding conditions.</p><p>To see how these foundational concepts scale into complete industrial architectures, read<a href="https://www.joltek.com/blog/manufacturing-concepts-edge-devices-plcs-ipcs-industrial-automation-software-hardware-architectures"> <strong>Manufacturing Concepts: Edge Devices, PLCs, IPCs, and Industrial Automation Architectures</strong></a>.</p><h3>Local vs Wide Area Networks</h3><p>Every modern network can be divided into two broad categories: what happens locally and what happens across long distances. Understanding the difference between these two layers is essential before moving into industrial architectures. <strong>The relationship between the Local Area Network and the Wide Area Network determines how data travels from the factory floor to the enterprise level.</strong></p><p>In consumer terms, this is the difference between devices communicating inside your home and data being sent to the internet. In industrial systems, it is the difference between machines talking to each other in a production cell and data being exchanged with business applications or cloud platforms.</p><h3>Defining the Wide Area Network (WAN)</h3><p>A Wide Area Network, or WAN, connects local systems to external destinations. It is the bridge between your private network and everything outside of it. In a home, this means connecting your router to the internet. In a plant, this means connecting the factory network to corporate infrastructure, remote data centers, or cloud services.</p><p>The WAN is what allows organizations to centralize their data and access production information from multiple facilities. It is what makes global manufacturing visibility possible. However, the design of a WAN connection in an operational setting must account for very different priorities compared to traditional IT environments.</p><p>Industrial use cases of WAN connectivity include:</p><ul><li>Sending production data from plant historians to enterprise databases.</li><li>Connecting multiple facilities to a centralized ERP or MES platform.</li><li>Enabling remote diagnostics or updates through secure VPN connections.</li><li>Integrating with cloud-based analytics or digital twins for performance monitoring.</li></ul><p>Each of these use cases introduces unique challenges in <strong>latency, reliability, and security</strong>. Unlike an office network, a delay of even a few milliseconds in an industrial setting can disrupt production processes or impact quality. Networks designed for operations must be deterministic, meaning that communication happens predictably and within strict timing requirements.</p><p>Security is also a critical consideration. Every connection to the outside world becomes a potential entry point for cyber threats. This is why OT networks often use industrial firewalls and segmented gateways to tightly control WAN access. The goal is to balance connectivity with protection, ensuring that critical systems remain isolated from external risk.</p><p>For a deeper look at how secure connectivity and data flow can be implemented across plants and enterprises, read<a href="https://www.joltek.com/blog/industrial-cybersecurity-ics"> <strong>Industrial Cybersecurity in Manufacturing</strong></a>.</p><figure><img alt="Lecture 2.3.2 — IP Addressing That Engineers Can Trust" src="https://cdn-images-1.medium.com/max/1024/0*uZG5UA6a9A_oABjz" /><figcaption>Lecture 2.3.2 — IP Addressing That Engineers Can Trust</figcaption></figure><h3>Defining the Local Area Network (LAN)</h3><p>A Local Area Network, or LAN, represents the group of devices that communicate within a specific location or environment. In a home, this might include your laptop, television, and smart speaker. In a plant, it includes PLCs, HMIs, SCADA servers, robots, and sensors working together to execute a production process.</p><p>Within a LAN, devices communicate at high speed through Ethernet connections or industrial switches. This environment is typically private and isolated from external networks, allowing for faster communication and greater control.</p><p>In manufacturing, LANs often mirror the physical structure of the facility:</p><ul><li>Each production line might have its own dedicated LAN to manage communication between controllers, drives, and operator interfaces.</li><li>Work cells may have smaller LANs with their own subnet, focused on local automation tasks.</li><li>Supervisory systems may connect to multiple LANs for centralized monitoring and data collection.</li></ul><p>To optimize performance and reliability, engineers often design LANs using <strong>segmentation and broadcast domains</strong>. A broadcast domain defines the group of devices that can communicate directly without routing. Limiting the size of this domain prevents network congestion and ensures that only relevant traffic flows where it is needed.</p><p>Understanding these local boundaries is essential before designing VLANs and subnets. Without this foundation, network segmentation can become inconsistent, leading to overlapping traffic or unintended communication paths. A well-structured LAN ensures that every device communicates efficiently, securely, and predictably within its intended environment.</p><p>To see how these principles evolve into advanced industrial architectures that balance performance and scalability, explore<a href="https://www.joltek.com/services/service-details-it-ot-architecture-integration"> <strong>IT and OT Architecture Integration</strong></a>.</p><h3>IP Addressing Fundamentals</h3><p>Every device on a network needs a clear identity in order to communicate. Think of it as a precise mailing address for data packets that must arrive at the correct destination without confusion. <strong>If you understand how addressing works, you can design plant networks that are predictable, secure, and easy to troubleshoot.</strong> For a deeper dive into how control systems move data once devices can see each other, read<a href="https://www.joltek.com/blog/plc-scan-cycles-polling-scada-systems-data"> PLC Scan Cycles and SCADA Data Flow</a>.</p><h3>What an IP Address Is</h3><p>An Internet Protocol address is a numerical label that uniquely identifies a device on a network. Laptops, PLCs, HMIs, vision systems, and servers all use IP addresses to send and receive packets.</p><h4>IPv4 vs IPv6</h4><p>IPv4 uses four numbers separated by dots and is still the most common in OT environments. IPv6 uses a longer hexadecimal format that greatly expands the available address space. Many plants remain on IPv4 due to legacy systems and tooling, while gateways and firewalls can bridge to IPv6 where needed.</p><h4>Public vs Private Ranges</h4><p>Private ranges are reserved for internal use and are not routable on the public internet. Typical choices in plants include:</p><ul><li>10.0.0.0 to 10.255.255.255</li><li>172.16.0.0 to 172.31.255.255</li><li>192.168.0.0 to 192.168.255.255</li></ul><p>Public addresses are assigned by providers and appear on the internet facing side of your network boundary.</p><h4>Static vs Dynamic Assignments</h4><p>Static addresses are manually set and remain fixed. They are preferred for PLCs, HMIs, historians, and servers that other systems must always find at the same location. Dynamic addresses are handed out automatically by a DHCP server and are common for laptops, tablets, and maintenance devices that come and go.</p><h3>How Routers Assign IP Addresses</h3><p>Routers often run a DHCP service that automatically gives an available address, a subnet mask, a default gateway, and DNS information to each client that requests it. This reduces manual work for noncritical endpoints.</p><p>Network Address Translation allows multiple private devices to share a single public facing address. When a device inside the plant initiates outbound communication, the router rewrites the source address to the public address and keeps a short state table so that replies return to the correct internal device.</p><p>NAT is widely used in manufacturing to isolate control networks while still allowing controlled outbound traffic for updates, telemetry, or secure remote access. It limits unsolicited inbound sessions and reduces the exposed surface of the plant.</p><h3>Why IP Management Matters</h3><p>Poor address management causes downtime and confusing failures. Duplicate addresses lead to intermittent communication. Incorrect gateways break access across subnets. Wrong masks create silent islands where devices cannot reach each other.</p><p>Adopt a simple and disciplined approach:</p><ul><li>Use static addresses for critical devices such as PLCs, HMIs, SCADA servers, historians, time servers, and gateways.</li><li>Maintain a living IP register with device names, locations, owners, and change history.</li><li>Segment by function and criticality so that motion control, safety, vision, and enterprise traffic do not compete.</li></ul><p>With these practices in place, you will prevent most network issues before they appear and create a foundation that scales cleanly as your plant grows.</p><h3>Routing and Packet Transmission</h3><p>Every useful network takes raw data from a source and moves it to a destination through a series of precise decisions made at different layers. <strong>Packets carry the payload while addresses and tables make sure each packet reaches the correct device with minimal delay.</strong> For broader architectural context around devices and data paths, explore<a href="https://www.joltek.com/blog/manufacturing-concepts-edge-devices-plcs-ipcs-industrial-automation-software-hardware-architectures"> Manufacturing Concepts: Edge Devices, PLCs, IPCs, and Industrial Automation Architectures</a>.</p><h3>How Data Actually Travels</h3><p>When an application needs to send information, the system breaks the data into packets. Each packet gets headers that describe where it came from and where it is going. At Layer 2, the frame includes a source MAC address and a destination MAC address. At Layer 3, the packet includes a source IP address and a destination IP address. Switches make forwarding decisions based on MAC addresses. Routers make forwarding decisions based on IP networks and routing tables. <strong>Switches think locally in terms of MAC addresses while routers think globally in terms of IP networks.</strong></p><h4>ARP in simple terms</h4><p>Address Resolution Protocol answers a very basic question. I know the IP of the device I want to reach, what is its MAC address on this segment. A host broadcasts an ARP request asking who has a given IP. The owner replies with its MAC address. The sender stores the result in an ARP cache for a short time to avoid asking again immediately.</p><h4>Example from PLC to HMI</h4><ul><li>The HMI client needs a tag value from a PLC.</li><li>The HMI checks its ARP cache. If the PLC MAC is unknown, the HMI broadcasts an ARP request and learns the PLC MAC from the reply.</li><li>The HMI builds a frame with destination MAC set to the PLC, wraps the IP packet that targets the PLC address, and sends it to the switch.</li><li>The switch forwards the frame out the correct port based on its MAC table.</li><li>If the PLC is in another subnet, the HMI targets the default gateway MAC. The router then forwards the packet toward the PLC network based on its routing table.</li><li>The PLC responds, and the return path follows the same logic in reverse.</li></ul><h3>Packet Collisions and Network Performance</h3><p>Older shared media networks could suffer collisions when two devices transmitted at the same time. Modern switched Ethernet isolates traffic into separate switch ports which prevents collisions and allows full duplex communication. Consumer gear still relies on basic switching and CSMA or CD rules where appropriate, while plant networks lean on quality of service, traffic engineering, and strict segmentation. <strong>Industrial systems depend on predictable timing which means the network must be engineered for consistent latency and bounded jitter.</strong></p><p>Deterministic communication matters because controllers, drives, and safety systems expect updates within tight time windows. Common strategies include isolated VLANs for control traffic, priority queuing for critical frames, and selection of protocols designed for time awareness. Time sensitive networking features, scheduled traffic, and protocol level design choices help ensure that motion, safety, and synchronization do not contend with general traffic such as file transfers or maintenance laptops.</p><figure><img alt="Lecture 2.3.3 — How a Packet Finds Its Way" src="https://cdn-images-1.medium.com/max/1024/0*W3MSMRJDldACOJVB" /><figcaption>Lecture 2.3.3 — How a Packet Finds Its Way</figcaption></figure><h3>Consumer Networks vs Industrial Networks</h3><p>Home networks and plant networks share familiar building blocks, yet they serve very different goals. Convenience rules at home. Predictability rules in production. <strong>The way we design and govern the network must match the level of risk and the cost of downtime.</strong> For a deeper discussion of securing connected operations, read<a href="https://www.joltek.com/blog/industrial-cybersecurity-ics"> Industrial Cybersecurity in Manufacturing</a>.</p><h3>The Simplified Consumer Model</h3><p>Consumer environments are designed for ease of use. A single device often combines modem, router, switch, and wireless access point. Devices appear and disappear without ceremony. DHCP quietly assigns addresses. Automatic updates run in the background. The experience feels invisible, which is exactly the point for a household. <strong>The essential idea is convenience first, where automation hides complexity so that devices just work.</strong></p><h3>The Controlled Industrial Model</h3><p>Production environments demand reliability, uptime, and predictable timing. Engineers select hardware deliberately. Configurations are explicit. Redundancy is planned. Diagnostics are routine. The goal is to keep control traffic stable while the process runs without interruption.</p><p>In practice this means thoughtful choices and simple rules that everyone follows.</p><ul><li>Fixed addressing for controllers, HMIs, historians, and servers</li><li>Managed switches that support segmentation and quality of service</li><li>Routine backups of switch and router configurations</li><li>Clear failover paths for critical services</li></ul><p><strong>The defining principle is intentional control of every variable that can affect safety, quality, or throughput.</strong></p><h3>Security and Access</h3><p>A home network trusts a simple secret. A plant network cannot. Access is granted based on role, location, and need. Wireless may be allowed for maintenance tools within a defined zone. Vendor access is time bound and audited. Firewalls enforce boundaries. Managed switches enforce who can talk to whom. Logs and alerts provide visibility that a household would never need.</p><p>Engineers use zoning to separate business services from operations, and operations from safety. They use segmentation so that only necessary paths exist. The result is a system that contains failure and resists intrusion while still delivering data to stakeholders who need it.</p><p><strong>Security through segmentation is the core practice that keeps critical operations safe while allowing necessary connectivity.</strong></p><h3>Common Components in Any Network</h3><p>Every healthy network relies on a small set of building blocks that move, isolate, and protect traffic. <strong>The right component choice and simple structure create predictable communication and easy troubleshooting.</strong></p><h3>Switches</h3><p>A switch connects devices within the same local network and forwards frames based on MAC addresses. It learns which device is on which port and sends traffic only where it needs to go. A router makes decisions between networks based on IP subnets, while a switch focuses on local forwarding within one network. <strong>Think of the switch as the local traffic director and the router as the city planner that connects neighborhoods.</strong></p><h4>Unmanaged and managed</h4><p>Unmanaged switches are plug and play with no configuration. They are suited for simple, low risk segments. Managed switches give you control over features such as port speed, spanning tree, mirroring, quality of service, and security settings. They also expose diagnostics that help you find errors before they become downtime. <strong>Managed switches let you shape traffic, enforce policy, and see problems early.</strong></p><h4>Preview of VLANs</h4><p>Virtual LANs create logical separation inside the same physical switch. They keep different kinds of traffic apart, reduce broadcast noise, and improve security. VLANs are the first step toward purposeful segmentation in plants and set the stage for clean routing between well defined zones. <strong>VLANs carve a single switch into tidy neighborhoods that only talk when you allow it.</strong></p><h3>Wireless Access Points</h3><p>At home, a wireless access point delivers convenience for phones, tablets, and laptops. It trades wire speed for mobility, which is perfect for casual use. In plants, wireless is best used where mobility is essential, such as maintenance tablets, warehouse scanners, or autonomous vehicles. For control loops and motion, wired links remain the default. <strong>Use wireless for mobility and noncritical workflows while keeping time sensitive control on copper or fiber.</strong></p><h4>Where wireless fits in OT</h4><ul><li>Walk and troubleshoot with a tablet in defined maintenance zones</li><li>Move material with automated guided vehicles inside a well planned coverage map</li><li>Provide temporary connectivity for commissioning teams without touching core control links</li></ul><figure><img alt="Lecture 2.3.4 — Segmentation, Security, and Documentation" src="https://cdn-images-1.medium.com/max/1024/0*RdAR1yei16YhEzj8" /><figcaption>Lecture 2.3.4 — Segmentation, Security, and Documentation</figcaption></figure><h3>‍Firewalls</h3><p>A firewall enforces which traffic can pass between networks. At home, it blocks unsolicited inbound traffic and keeps devices safer by default. In industry, firewalls sit between business and operations, between operations and remote access, and at the plant edge. They filter by IP, port, service, and even by protocol content using deep packet inspection. Vendors offer industrial models that tolerate temperature, vibration, and electrical noise, such as platforms from Moxa, Hirschmann, and Stratix. <strong>Firewalls create the control points that turn a flat network into a governed system.</strong></p><h4>Deep packet inspection</h4><p>Inspection engines can recognize industrial protocols and apply precise rules. You can allow reads to a PLC while blocking writes, or permit historian collection while denying configuration changes. This turns connectivity into a safe utility rather than an open door. <strong>Protocol aware filtering lets you enable data sharing without exposing control.</strong></p><h3>Practical Takeaways Before Moving to OT Networking</h3><p>Strong fundamentals make advanced design simpler and safer. When you understand the role of each component, configuration becomes a matter of applying clear rules.</p><ul><li>Subnets organize address space so that routing is explicit and predictable</li><li>VLANs keep unrelated traffic separated and quieter</li><li>Firewalls define which paths exist and who can use them</li><li>Managed switches provide visibility, priority, and health checks</li></ul><p><strong>Most troubleshooting reduces to checking the simple things first such as addressing, VLAN membership, and allowed paths.</strong> For an applied view of how these pieces fit together in real architectures, read<a href="https://www.joltek.com/blog/manufacturing-concepts-edge-devices-plcs-ipcs-industrial-automation-software-hardware-architectures"> Manufacturing Concepts: Edge Devices, PLCs, IPCs, and Industrial Automation Architectures</a>.</p><h3>Conclusion</h3><p>A clear picture of how data moves gives you the confidence to build networks that are fast, resilient, and secure. <strong>The fundamentals you master at home translate directly to the plant floor.</strong> You now have the language to describe how devices identify themselves, how traffic stays local, and how it safely reaches external destinations.</p><h3>Practice on your own network</h3><p>Use a short exercise to turn concepts into muscle memory.</p><ul><li>Identify your router and confirm the connection to your provider or modem combo</li><li>List a few devices and note their IP addresses along with whether they connect by wire or by wireless</li><li>Sketch a quick map that shows which traffic stays local and which traffic leaves your home</li></ul><h3>Why this matters in manufacturing</h3><p>The same structure applies to PLCs, HMIs, SCADA, and MES. Fixed identities prevent confusion. Segmentation reduces noise. Firewalls and routing policies protect what matters while still enabling the right data to reach the right people. For an applied perspective on how these choices come together in real environments, read<a href="https://www.joltek.com/services/service-details-it-ot-architecture-integration"> IT and OT Architecture Integration</a>.</p><p>“In the next section, we will look at how industrial networks evolve from these fundamentals through segmentation, VLANs, and managed switch design.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2195b045d50a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Local Data, Global Impact: Why Manufacturing Transformation Starts at the Machine]]></title>
            <link>https://vrom.medium.com/local-data-global-impact-why-manufacturing-transformation-starts-at-the-machine-55e72dcf1359?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/55e72dcf1359</guid>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Mon, 17 Nov 2025 00:05:54 GMT</pubDate>
            <atom:updated>2025-11-17T00:05:54.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*59nX8a9wi3DMxrbPRtfL-g.gif" /></figure><h3>Introduction to Local Data</h3><p>In the world of industrial automation and manufacturing, we often get caught up with conversations around an entire enterprise when it comes to data. With the popularization of topics such as UNS, Industry 4.0, IIoT, it’s not surprising that all many care about is scale and projects that span across multiple facilities.</p><p>What I’ve personally noticed is that if you neglect local, or machine data, none of the above becomes possible. Operators aren’t going to be sold on the idea of funneling data into dashboards and being presented with insights if they can’t understand why the machine they’re standing in front of is at a standstill. They simply don’t care about the previous quarter as much as they do about getting the machine back up and running with what they have in front of them.</p><p>For that reason, I’d like to focus the conversation for this post around machine / local data. To set this stage, local data can be defined as mostly “raw” data coming from field devices with minor changes made at the PLC / IPC layer. Although it’s possible to send data back from the upstream layers (Ex: SCADA, MES, ERP), for the purposes of this post, we’re going to talk about the data needed at the PLC / HMI layer without the use of any other layers whatsoever.</p><figure><img alt="Local Data: The Foundation of Reliable Manufacturing" src="https://cdn-images-1.medium.com/max/1024/0*xJpoPadXBUmMKrvi" /><figcaption>Local Data: The Foundation of Reliable Manufacturing</figcaption></figure><h3>The Origin of Local Data</h3><p>Every machine, process, packaging, or otherwise is made from various inputs and outputs. All the field devices will send or receive digital / analog signals directly via PLC modules, or indirectly through hubs, drives, etc. This is somewhat of an oversimplification as you’ve got multiple protocols, different hardware, and some other means of getting this done. However, to keep things simple let’s assume that there are inputs that generate data and outputs that consume data.</p><p>The most basic example of data would be a push button which when energized sends a HIGH signal to the PLC which can then start a motor. A second pushbutton is used to send a signal and stop the same motor. In this instance, we have two push buttons and an output to a contactor which is tied to a three phase motor. We also have a PLC which stores the registers associated with the inputs and outputs.</p><p>The real world is rarely as simple, so let’s paint a broader picture. In general, the pushbuttons aren’t going to be physical, but presented to the user via a local HMI. Now, we’ve got signals between the PLC and HMI. Similarly, it’s much more frequent to see a VFD being used for a motor over a contactor (They’re not exactly the same cost, but negligible enough for most applications), which means that we’ve now got 3 devices on the network. Let’s not forget that at this point we need a switch to facilitate communication between the devices, and we probably need some sort of safety mechanism (Ex: E-Stops).</p><p>As you can see, it’s not difficult to picture a rather simple application to dictate less than simplistic solutions on the automation side.</p><p>So where does data come into the picture?</p><p>Well, now that we’ve got all these devices, we can start adding various layers of information that may or may not be relevant for this specific application. First of all, we have the general states of the hardware: ON / OFF, LOW / HIGH, Running / Stopped, etc. These components are critical to “run” the system as it is intended. Additional data can be “created” and “accessed” for configuration purposes. For example, I may want to change the parameters of the VFD — all of that data is usually stored in the registers and allows the end-user to set specific motor information, but also process variables (Ex: speed, acceleration, limits, etc.). Next, we have system configurable data which is process specific. For example, the user may want to start the motor for 5 minutes after the press of the button, or they might want to start it until it is stopped. Lastly, we have data associated with the state of the system. For example, the user may want to confirm that the motor is actually running by using a high speed counter, or by reading the registers of the VFD. The user may want to collect information about the time the system has had the motor on to perform maintenance. Similarly, the team probably wants to display a tangible alarm based on the state of the VFD. For example, Error 73 for a PowerFlex525 system may mean “overtorque” which is going to give the operations team a starting point as opposed to scrambling to find the manual.</p><p>The relatively simple application can very quickly spiral out of control.</p><h3>What Data is Actually Relevant?</h3><p>With all of the above in mind, it’s easy to go overboard. The biggest question in our industry — which data is relevant for my facility? is probably never getting a tangible answer… It depends.</p><p>Let’s start by classifying different types of data and prioritizing based on the type.</p><figure><img alt="Enterprise Goals Begin with Local Clarity" src="https://cdn-images-1.medium.com/max/1024/0*NXbqAQ6FHHqkXrs_" /><figcaption><strong>Enterprise Goals Begin with Local Clarity</strong></figcaption></figure><h3>Type 1 Data — Control System</h3><p>When it comes to control system design principles, the answer is clear — if we have field devices tied to our system, we must ensure that the data coming in or out is of highest priority. In other words, the raw data coming from sensors, or the raw data going out to output devices needs to be collected, processed, and sent out first. Without this data, the system simply can’t operate.</p><p>Type 1 data needs to be protected at all cost which generally means that the “mission critical” routines within a PLC will almost always take precedence over any other “activities.”</p><p>Type 1 data is generally used in “high-speed” logic and leads to the execution of the core process.</p><h3>Type 2 Data — Control System State</h3><p>Once the control logic performs its basic purpose of turning inputs into outputs, the next layer of information concerns <em>how the system behaves</em>. This is what we call state data. It does not drive the process directly but tells us whether the process is healthy, safe, or even functioning as intended. State data is what allows engineers and operators to move beyond “Is it running?” to “Why did it stop?” and “What exactly is happening right now?” It is a layer of awareness that transforms a purely reactive control system into a diagnosable and optimizable environment.</p><h4>The Nature of State Data</h4><p>At this level, the control system starts to describe itself. It reports on modes of operation, system availability, and alarms. For example:</p><ul><li>Is the machine in automatic, manual, or maintenance mode</li><li>Has a safety circuit been broken</li><li>Has the drive tripped due to overcurrent</li><li>Is the process waiting for upstream or downstream equipment</li></ul><p>Each of these states is captured as discrete signals within the PLC and may be displayed on the HMI. In modern systems, this information can also be stored for historical analysis. The moment this data becomes available, operators gain visibility into the true condition of the process rather than only its result.</p><h4>Why This Matters</h4><p>Industry research continues to show that the average cost of unplanned downtime exceeds <strong>two hundred sixty thousand dollars per hour</strong>. While that number is dramatic, it illustrates a truth that every plant manager knows: it is not the major project delays that hurt most, but the accumulation of small, unexplained stoppages.</p><p>When a motor fails to start and the operator cannot tell whether the fault is mechanical, electrical, or network related, valuable minutes are lost. A clear state structure in the PLC and HMI eliminates this guesswork.</p><p>This is why during Joltek’s Plant Systems Health Assessments we focus heavily on how fault and state information is represented at the control layer. Poorly designed state logic is one of the most common root causes of recurring downtime, yet it rarely appears in executive dashboards because it is a local problem.</p><h4>Common Issues in Capturing State Data</h4><p>Many systems in operation today were designed without a consistent method for communicating state. Each OEM or integrator implemented its own naming, structure, and logic conventions. As a result:</p><ul><li>Fault codes differ from one machine to another</li><li>Alarm messages are unclear or nonexistent</li><li>State transitions are not logged or timestamped</li><li>Operators rely on intuition instead of system feedback</li></ul><p>The result is tribal knowledge instead of structured intelligence. This situation makes scalability nearly impossible. You cannot standardize analytics when even the definition of “Running” differs across assets.</p><h4>How to Approach State Data Structuring</h4><p>Establishing a consistent way of representing system states does not require a new technology stack. It requires discipline in design. A few key principles help:</p><ol><li><strong>Define clear operating modes.</strong> Each asset should have distinct states such as “Stopped,” “Starting,” “Running,” “Stopping,” and “Faulted.”</li><li><strong>Standardize alarms and fault codes.</strong> Messages should be understandable by maintenance and operations without needing a manual.</li><li><strong>Use timestamping wherever possible.</strong> Even a basic local buffer or SD card can store valuable event history.</li><li><strong>Ensure one source of truth per state.</strong> Avoid duplicate or conflicting logic that leads to false indications.</li></ol><p>Once these basics are in place, the plant begins to generate consistent, actionable information from the ground up.</p><figure><img alt="From Inputs to Insights: The Origin of Local Data" src="https://cdn-images-1.medium.com/max/1024/0*nC570os9kZNf7A_L" /><figcaption><strong>From Inputs to Insights: The Origin of Local Data</strong></figcaption></figure><h3>Type 3 Data — Process and System Configuration</h3><p>As discussed in the previous sections, once the control system is capable of receiving and sending reliable signals, the next layer concerns <em>how the process behaves within its designed limits.</em> Configuration data defines how a machine or system should perform under specific conditions. It represents the rules and settings that shape the process but do not necessarily change from cycle to cycle.</p><p>Almost every industrial process relies on some level of configuration. These are the parameters that make a machine flexible enough to handle variation while still preserving control and repeatability. For example, a packaging line may need to adjust the speed of a conveyor, the acceleration and deceleration of a motor, or the fill level of a product tank. These parameters do not change on every start, but they are crucial when shifting between products, formats, or recipes.</p><h4>The Nature of Configuration Data</h4><p>Configuration data sits between static design and dynamic operation. It defines limits, targets, and recipes. Unlike real-time inputs and outputs, this data often lives in memory locations within the PLC or on the HMI that are accessed only when necessary.</p><p>In its simplest form, configuration may include motor acceleration rates, PID loop gains, or sensor thresholds. In more advanced processes, such as batching, mixing, or thermal control, the configuration layer becomes a full-fledged logic engine that determines setpoints based on recipes, SKUs, or production modes. This is where local data begins to blur the line between automation and information technology. The control system must not only execute instructions but also interpret data structures that define the “what” and “how” of production.</p><h4>The Role of Configuration in Modern Manufacturing</h4><p>Configuration data represents the heart of flexibility. Manufacturers increasingly face smaller batch sizes, faster changeovers, and product customization. The ability to load a set of parameters that instantly adapts the machine to a new SKU or process condition is what enables modern operations to stay competitive.</p><p>This is why so many manufacturers are investing in recipe management at the control layer. When configuration data is structured well, it can be synchronized with higher systems such as MES, ERP, or quality management software. The plant floor becomes capable of receiving validated recipes electronically, rather than relying on manual adjustments by operators or technicians.</p><p>Unfortunately, many facilities remain far from this level of maturity. Configuration data is often scattered across operator screens, local CSV files, or hard-coded constants buried in ladder logic. Without standardization, every change becomes a risk. Each adjustment requires deep technical knowledge, increasing reliance on a few key individuals rather than empowering the operations team as a whole.</p><h4>Security and Access Control</h4><p>Because configuration data defines how the system runs, it must be treated with caution. It is not uncommon to find an HMI page labeled “Advanced Settings” behind a password gate. In better implementations, access is restricted by user role so that only maintenance or engineering can modify parameters. In weaker designs, access may be uncontrolled, leading to inadvertent changes that destabilize the process.</p><p>In highly regulated industries such as pharmaceuticals or medical devices, configuration management is subject to strict validation and audit requirements. Changes must be logged, versioned, and approved. Even in less regulated environments, establishing a clear change control policy for configuration data is a hallmark of operational discipline.</p><p>A well-structured configuration layer supports both flexibility and governance. It allows necessary changes while maintaining traceability and protecting the system from human error.</p><figure><img alt="The Four Layers / Types of Local Data" src="https://cdn-images-1.medium.com/max/1024/0*GqwBn3_v5ai5l4AP" /><figcaption><strong>The Four Layers / Types of Local Data</strong></figcaption></figure><h4>The Risks of Poor Configuration Practices</h4><p>Over the years, I have seen many systems where operators were not given any permission to make adjustments. In some cases, this was due to poor design. In others, it was the result of management’s fear that someone might “break” the process. The unintended consequence is that people develop workarounds. They bypass safety interlocks, modify PLC code directly, or use unapproved files to tweak parameters.</p><p>This environment creates risk at multiple levels. It undermines safety, introduces inconsistency, and makes troubleshooting far more complex. When configuration data is not well defined or controlled, every shift becomes a new experiment. The system drifts away from its validated state, and performance metrics such as yield or quality begin to fluctuate without clear explanation.</p><p>In contrast, strong configuration practices build confidence. Engineers can implement changes safely, operators understand what is adjustable and what is not, and leadership can trace every modification back to its source.</p><h4>Moving Toward Standardized Configuration Models</h4><p>The goal is not to eliminate flexibility but to structure it. A robust configuration strategy should include:</p><ol><li><strong>Parameter definition.</strong> Identify which settings truly affect performance and which should remain fixed.</li><li><strong>Role-based control.</strong> Define who can change what and under which circumstances.</li><li><strong>Change management.</strong> Ensure that every adjustment is logged and approved before implementation.</li><li><strong>Central storage.</strong> Where possible, store configuration data in structured registers, databases, or recipe files that can be easily backed up and restored.</li><li><strong>Synchronization.</strong> Integrate configuration with higher systems so that recipes and parameters remain aligned with business objectives.</li></ol><p>When configuration data is standardized, plants achieve the best of both worlds: consistent operation with the ability to adapt quickly to new requirements. It also lays the groundwork for digital transformation initiatives by ensuring that the foundational data used for analysis and optimization is both accurate and contextual.</p><h3>Type 4 Data — Diagnostic and Predictive</h3><p>When most people talk about predictive maintenance, their minds immediately jump to machine learning models, cloud analytics, and sophisticated dashboards. But before any of that is possible, reliability begins with something much simpler: <strong>local diagnostic data.</strong></p><p>This is the layer that tells you not what the machine is doing, but <em>how healthy</em> it is while doing it.</p><p>Early in my career, I remember standing next to a packaging line that would trip almost daily. Every time it stopped, production called maintenance, and we would spend hours going through the same routine. We would check sensors, replace contactors, reset drives, and eventually get it running again. What we never did was look at the diagnostic information that the system was already generating. The PowerFlex drives had torque, current, and bus voltage data available in the registers, but none of it was being read, displayed, or logged.</p><p>Once we pulled those values into the HMI and plotted them locally, the issue became obvious. The motor was drawing progressively higher current during startup, which told us that the mechanical load was binding. What used to take hours to identify suddenly took minutes.</p><p>That moment completely changed how I think about diagnostics.</p><figure><img alt="Visibility That Eliminates Guesswork" src="https://cdn-images-1.medium.com/max/1024/0*RkkB4FI-GzXUdYDt" /><figcaption><strong>Visibility That Eliminates Guesswork</strong></figcaption></figure><h4>What Local Diagnostic Data Really Means</h4><p>Local diagnostics are not complex algorithms. They are the direct feedback signals that a machine provides about its own condition. Torque, temperature, vibration, current, pressure, and even network quality can all serve as early indicators of trouble. Every drive, motor, and controller today has the ability to expose this information, but in most plants, it goes completely unused.</p><p>A drive might be capable of reporting motor overload, phase imbalance, or line voltage deviation, yet none of that reaches the operator’s screen. A PLC might detect increasing scan time or packet loss on a network, but no one ever sees it. The result is that teams continue to operate in a reactive mode, even though the equipment has been warning them for days or weeks.</p><p>The most powerful form of predictive maintenance is often the simplest. It begins by making local diagnostics visible.</p><h4>The Role of Drives and Smart Devices</h4><p>Modern variable frequency drives are among the best examples of built-in diagnostics. Beyond basic control, they continuously measure electrical and mechanical parameters that describe the system’s behavior in real time. Torque trends reveal when a conveyor belt is starting to drag. Motor current spikes show when a gearbox is seizing. DC bus fluctuations indicate line instability or grounding issues.</p><p>In one project, I worked with a plant that experienced random motor faults on a filler. Operators blamed software. Maintenance blamed the drive. It turned out that the supply voltage from a nearby transformer was dropping under load, causing undervoltage trips. The information was already available in the drive’s voltage register, but it had never been mapped. Once we brought that data into the local HMI, the team could see it immediately and call the utility before it caused another shutdown.</p><p>This is the value of diagnostic visibility. It turns guesswork into observation.</p><p>Smart sensors have brought the same philosophy to smaller devices. Many of them now embed temperature, vibration, or position feedback directly into the communication protocol. When used properly, this transforms the control system from a set of binary signals into a living, breathing representation of machine health.</p><h4>How Diagnostic Data Shapes Maintenance</h4><p>Once local diagnostic data becomes visible, maintenance planning changes entirely. Instead of waiting for something to fail, technicians can intervene at the right time. Torque trending on a drive can be used to schedule lubrication. Temperature data from a bearing sensor can trigger inspection before a catastrophic failure. Even simple data, such as the number of motor starts or runtime hours, can be used to drive preventive maintenance cycles with precision.</p><p>In a food manufacturing plant I supported, we configured drives to report runtime hours directly to the PLC. The local system generated a small reminder on the HMI when a motor exceeded its service interval. It was not complicated, but it eliminated hundreds of hours of unplanned work annually because the maintenance team could plan downtime around real usage rather than fixed calendars.</p><p>Local diagnostic data also improves collaboration between engineering and maintenance. When everyone can see the same data in real time, the conversation shifts from speculation to evidence. The maintenance team stops chasing ghosts, and engineering gains the confidence that the system is behaving as designed.</p><figure><img alt="The Illusion of Scale" src="https://cdn-images-1.medium.com/max/1024/0*uhgDv5M44p8y8peu" /><figcaption><strong>The Illusion of Scale</strong></figcaption></figure><h3>The Importance of Local Context</h3><p>Once you start to see how much information exists at the local level, you realize that the quality of that data determines the quality of every other decision. The conversations in our industry often begin with big ideas like enterprise visibility or cloud analytics. But the truth is that none of those systems can make sense of data that lacks context. Local data gives that context. It defines what each value actually means and how it relates to the physical process.</p><p>In every manufacturing environment, the most valuable data is usually the simplest. It is not a complex model or algorithm, but a clear signal tied to something real. A properly named tag in a PLC, an alarm that describes the actual root cause, or a drive parameter that reflects true load conditions can create more impact on daily operations than any abstract KPI. These are the pieces of information that make the system understandable to the people running it.</p><p>When local data is inconsistent, the entire organization suffers. Operations struggles to see why a process is not performing. Maintenance reacts to symptoms instead of causes. Engineering cannot prove whether a change improved anything. Leadership ends up questioning the data itself. By contrast, when the local layer is structured and consistent, everyone across the plant speaks the same language. A stop reason in one area means the same thing in another. A temperature value, a torque reading, or a fault code all carry clear meaning.</p><h3>Why Decision-Makers Should Care</h3><p>For leaders, local data might seem like a technical concern, but it is the foundation of reliability and visibility. The cost of poor local data is rarely captured on a balance sheet, yet it appears every time a line goes down without a clear cause or when a report takes days to reconcile because no one trusts the inputs. The fastest way to improve uptime, reduce waste, and enable real analytics is to make sure the machines themselves communicate accurately.</p><p>When I walk through plants, I often see large digital programs underway. New dashboards are being designed, and data pipelines are being built. But on the floor, operators are still reading “Fault 9” on their HMIs with no explanation of what it means. Maintenance teams are resetting drives without knowing why they tripped. These are not small oversights. They are the reason large transformation efforts lose momentum. If people on the floor cannot act on the data in front of them, the initiative stalls before it reaches scale.</p><p>The real opportunity for decision-makers is not in adding more systems but in strengthening the foundation. A plant that invests in clean, reliable local data can scale confidently. A plant that ignores it will spend years chasing inconsistencies across every new platform it introduces.</p><p>Trust in data does not begin with the dashboard; it begins with the equipment. The moment an operator sees a screen that accurately reflects what they observe on the line, trust is created. When maintenance can confirm a fault reason without opening a panel, confidence grows. When engineers can tune a process and see immediate, traceable impact, data becomes an asset instead of a burden.</p><p>This local trust becomes the backbone of digital maturity. It creates a natural flow of accurate, contextual information upward to SCADA, MES, and analytics systems. Each layer above can now focus on insight rather than correction. The organization moves from reaction to understanding, from understanding to improvement, and from improvement to scale.</p><p>Modernization always starts at the source. Before a plant can optimize or automate, it must first understand itself. That understanding comes from local data. It is what reveals how the process behaves, how healthy the equipment is, and what actions need to be taken in real time. Digital transformation is not a leap into complexity. It is a disciplined focus on fundamentals. A well-structured control system, clear state logic, reliable configuration management, and meaningful diagnostics form the base of every successful initiative. Once those elements are in place, connecting to higher systems is simply a matter of choice.</p><figure><img alt="The Real Cost of Poor Local Data" src="https://cdn-images-1.medium.com/max/1024/0*qLi1IWXvghjdPIBh" /><figcaption><strong>The Real Cost of Poor Local Data</strong></figcaption></figure><h3>Closing Thoughts</h3><p>Every manufacturer wants visibility, agility, and resilience. The path to those outcomes does not begin in the cloud. It begins on the floor. When the machines can explain what they are doing and why, the entire organization operates with confidence.</p><p>Local data is not a technical detail. It is the foundation of operational truth. It connects people to process, aligns teams around facts, and gives leaders a reliable view of performance. Before any system can be connected, before any data can be analyzed, it must first be understood. And that understanding always starts locally.</p><p>At Joltek, this is where every conversation begins. Before we talk about enterprise systems, we focus on the plant floor. We help manufacturers bring clarity to their local data so that operators, engineers, and executives all see the same picture. When that happens, the results follow naturally. Modernization becomes simpler, decisions become faster, and the organization finally moves with confidence in the information that drives it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55e72dcf1359" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Root Causes of Downtime in Industrial Automation and How to Eliminate Them]]></title>
            <link>https://vrom.medium.com/the-root-causes-of-downtime-in-industrial-automation-and-how-to-eliminate-them-ab795ae2a27a?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab795ae2a27a</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[industrial-automation]]></category>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Sun, 16 Nov 2025 23:58:18 GMT</pubDate>
            <atom:updated>2025-11-16T23:58:59.709Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vrwQuhAtNRAz-XcsVSyRA.gif" /></figure><h3>Introduction to the Paradox of Investment Without Reliability</h3><h3>The reality that investment is not translating into stability</h3><p>Manufacturers continue to invest significant capital into automation, modernization, and digital tools, yet many plants still face recurring unplanned downtime. <strong>The core challenge is that investment in technology alone does not guarantee reliability.</strong> In practice, major capital projects often coexist with the same failures that existed before, creating a frustrating paradox for engineering leaders and executives. Despite new systems, new equipment, and new software, production lines continue to stop without warning. These events disrupt supply chains, create losses that compound throughout the organization, and can quickly erode confidence in both teams and tools.</p><h3>The financial weight of downtime</h3><p>Unplanned downtime remains one of the most expensive and disruptive events in manufacturing. Industry research places the average cost at approximately two hundred and sixty thousand dollars per hour, a figure reported by Aberdeen Research. This benchmark represents an average across multiple verticals and is often higher in sectors with continuous or high speed operations. The financial impact includes lost production, labor inefficiencies, material waste, delayed shipments, and cascading operational problems that ripple far beyond the immediate event. Many organizations are surprised that despite investing heavily in modernization, these events persist with little reduction in frequency or severity.</p><figure><img alt="The Paradox of Modern Manufacturing Investment" src="https://cdn-images-1.medium.com/max/1024/0*M_vjQJkvsg9xtPi8" /><figcaption><strong>The Paradox of Modern Manufacturing Investment</strong></figcaption></figure><h3>Why the root causes are rarely what leaders expect</h3><p>It is common for leadership teams to assume that downtime is primarily driven by equipment age or isolated component failure. However, field assessments and plant systems reviews show a much more complex picture. <strong>Downtime is often the outcome of systemic weaknesses, not isolated hardware issues.</strong> During comprehensive reviews such as a Plant Systems Health Assessment, recurring patterns emerge across facilities. These patterns include undocumented control architectures, unsupported firmware, legacy networks, inconsistent programming standards, and gaps in visibility that prevent teams from understanding the real state of their systems. These factors create hidden fragility, which new technology alone cannot resolve.</p><h3>The hidden misalignment between people, process, and technology</h3><p>Even with new investments, many plants struggle because the underlying operating environment has not changed. Engineering teams may not have access to updated documentation or may lack visibility into the true system dependencies. IT and OT teams may each assume responsibility lies with the other, creating ambiguity in ownership. Operators may continue to rely on manual workarounds or tribal knowledge that masks deeper issues. Leaders often lack reliable data on what is actually happening on the plant floor, making it difficult to distinguish symptoms from root causes. These human and process gaps are equally responsible for unplanned downtime.</p><h3>The central thesis of this article</h3><p>The persistent nature of unplanned downtime is not due to a lack of investment. It is the result of investments made without full visibility, cross functional alignment, or a systems level understanding of how people, process, and technology operate together. By exploring these underlying dynamics, this article aims to provide a clearer view of why downtime continues even in highly capital intensive environments. It will also outline the structural issues that prevent plants from realizing the full value of their modernization efforts and point to complementary topics such as data visibility and manufacturing execution strategies, which you can explore further through resources like<a href="https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing"> https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing</a>.</p><h3>Why Modern Investments Fail to Reduce Downtime</h3><h3>Upgrading the hardware without upgrading the system</h3><p>Many manufacturers continue to replace aging PLCs, drives, or HMIs in an effort to reduce unplanned downtime. These investments are well intentioned and often address immediate reliability concerns, but they rarely solve the deeper structural issues that cause production instability. <strong>The core insight is that individual hardware upgrades cannot overcome weaknesses in the surrounding control, network, and software environment.</strong> In many facilities, new components are installed on top of legacy architectures that have not been re evaluated in years. This creates a scenario where a modern device is connected to an outdated network, running alongside unsupported firmware, and operating within an undocumented control strategy that few people fully understand.</p><p>Field assessments frequently uncover situations where obsolete PLCs have been replaced while the network infrastructure remains unchanged. Teams may modernize a motor control center yet leave the original drive communication configuration untouched. A plant may deploy a new SCADA server while still operating on an unsupported Windows environment. These conditions introduce technical debt and create a fragile system where the upgraded component cannot perform reliably because the foundation beneath it has not been strengthened. The Plant Systems Health Assessment consistently shows that a significant portion of manufacturers continue to operate with obsolete hardware and undocumented architectures, which means that most teams lack a clear view of what high quality system design should look like.</p><figure><img alt="Why Equipment Upgrades Do Not Fix System Instability" src="https://cdn-images-1.medium.com/max/1024/0*mfbQV_75sUULP7pb" /><figcaption><strong>Why Equipment Upgrades Do Not Fix System Instability</strong></figcaption></figure><h3>Flat, overloaded, and undocumented OT networks</h3><p>Modern equipment depends on consistent, predictable communication. When that communication layer is weak, even the most advanced machine cannot stabilize production. <strong>The key insight is that network failures often manifest as equipment failures, even though the equipment is not at fault.</strong> Many plants continue to run flat networks without segmentation, which allows broadcast traffic to saturate the system. In such an environment, safety messages, HMI updates, historian logging, and inter device control signals all compete for the same bandwidth. As network load increases, devices begin to drop packets or lose communication intermittently, causing production stops that appear random and are extremely difficult to troubleshoot.</p><p>The absence of proper VLAN segmentation is only one part of the problem. Many facilities continue to rely on unmanaged switches used in ways that exceed their intended purpose. Firmware patching routines are often inconsistent, leaving devices vulnerable to communication instability. OT cyber incidents have increased significantly in recent years, and recovery from a serious attack can take anywhere from one to three weeks. The underlying contributors to these risks are regularly found during technical reviews. Teams often operate without accurate network topology documentation, and outdated hardware increases insurance premiums while limiting the ability to improve segmentation or security.</p><h3>Investments made without understanding the current state</h3><p>Capital planning is often driven by perceived needs rather than a complete understanding of the existing system. Plants invest in a new MES or a new SCADA platform or a newly automated piece of equipment, only to discover that the surrounding infrastructure cannot support it. <strong>The central insight is that modernization efforts fail when the true condition of the plant’s systems is unknown.</strong> When leadership approves upgrades without a complete assessment, the result is predictable. Commissioning delays occur because networking issues are uncovered late. Critical items such as unsupported firmware or configuration gaps surface only during testing. Equipment functions correctly in isolation but not when integrated with the rest of the plant.</p><p>These issues represent hidden risks that remain invisible until they interrupt production. Single points of failure, outdated servers, missing backups, and inappropriate device configurations frequently surface during integration projects. As a result, engineering change orders escalate and project costs expand rapidly. The Plant Systems Health Assessment highlights this challenge clearly. A recurring observation is that leadership teams often lack accurate documentation of their systems, which leads to decisions made without the necessary visibility to ensure success.</p><h3>Tribal knowledge and workforce capability gaps</h3><p>New technology cannot overcome organizational or process limitations. Many plants continue to rely heavily on tribal knowledge, where only a few individuals understand critical parts of the system. <strong>The essential insight is that modern tools cannot deliver value when they are layered on top of manual workarounds and inconsistent operating practices.</strong> Operators may continue to run equipment based on habit, bypassing designed workflows. Maintenance teams may focus on firefighting instead of structured root cause analysis because that is what daily pressures require. When a key technician retires or moves to another role, the plant discovers that system understanding was concentrated in one person rather than embedded in the team.</p><p>The people dimension of operations plays a significant role in downtime. Skills gaps, insufficient training, and the absence of standardized RCA frameworks all contribute to recurring failures. Even when new hardware, software, or analytics tools are deployed, these investments do not change the fundamental behaviors that keep a plant running. A strong capability foundation is required before technology can truly improve reliability.</p><h3>Broken data flows that lead to late or incorrect decisions</h3><p>Many manufacturers choose to invest in MES, SCADA, historians, or analytics platforms believing that better data will solve operational issues. The reality is that these systems depend entirely on the quality of the information flowing from the plant floor. <strong>The critical insight is that modern tools fail when the underlying data foundation is weak or inconsistent.</strong> Local machine data may be incomplete, outdated, or incorrectly mapped to higher level systems. In some plants, critical tags are not exposed at all, making it impossible to calculate KPIs like OEE, MTTR, or MTTF with accuracy.</p><p>A common pattern is the absence of a single source of truth. SCADA, MES, and ERP systems often hold conflicting values for the same process metric because data pipelines are not aligned. The Industrial Data overview describes this as running the plant blind, and that description is accurate. Without reliable visibility into machine performance, downtime patterns, quality response, or root cause drivers, even sophisticated software cannot support timely or correct decisions. For readers interested in related topics, the article on unlocking industrial data provides additional context and can be accessed at<a href="https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing"> https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing</a>.</p><figure><img alt="The Hidden Drivers of Recurring Downtime" src="https://cdn-images-1.medium.com/max/1024/0*5s1edB8JGYo0ui4g" /><figcaption><strong>The Hidden Drivers of Recurring Downtime</strong></figcaption></figure><h3>The Real Root Causes of Persistent Downtime</h3><h3>Obsolete and unsupported infrastructure</h3><p>Many plants continue to experience recurring downtime because segments of their control and automation infrastructure have quietly aged into a state where reliability can no longer be guaranteed. <strong>The central insight is that outdated infrastructure creates failure modes that no amount of new software or equipment can compensate for.</strong> When a facility depends on end of life PLCs, unsupported operating systems, or aging drives, the risk of intermittent or catastrophic failure becomes embedded in daily operations. These components may appear to function normally during steady state production, but they lack vendor support, firmware updates, and spare parts availability, which significantly increases the likelihood of extended outages when problems arise.</p><p>The Plant Systems Health Assessment consistently reveals that a large portion of facilities still operate with obsolete control hardware across critical processes. Unsupported Windows servers may continue to host SCADA applications long after security patches have ended. Legacy HMIs and drives may generate intermittent faults that operators attribute to normal variation, even though the true cause is the slow degradation of older hardware. When these issues accumulate across an entire plant, they form a foundation that cannot support modern reliability expectations. The challenge is not always visible to leaders because the equipment appears to run adequately until it fails under stress.</p><h3>Poor network design and cybersecurity exposure</h3><p>Beyond individual devices, the network itself plays a decisive role in uptime. Many of the most challenging and unpredictable downtime events stem from communication instability rather than equipment malfunction. <strong>The key insight is that unreliable network architecture introduces systemic fragility throughout the plant.</strong> Flat networks allow broadcast traffic to spread unchecked, unmanaged switches limit control over data flow, and unpatched firmware creates both reliability and security vulnerabilities. When network load increases, devices may lose communication, triggering faults that appear unrelated to the network but originate from overloaded or poorly segmented traffic paths.</p><p>Cybersecurity exposure adds another layer of risk. Plants that rely on outdated network equipment or unsupported firmware face higher insurance premiums and longer recovery times after security incidents. Incidents involving OT environments have increased in frequency, and recovery from such events often takes multiple days or even weeks. In facilities without accurate network documentation, identifying the source of an issue becomes a lengthy process that prolongs downtime. The combination of design flaws, security vulnerabilities, and undocumented connections makes the network one of the most common yet least visible contributors to persistent production interruptions. Readers who wish to build a deeper foundation in this area can explore the SCADA fundamentals article at <a href="https://www.joltek.com/blog/scada.">https://www.joltek.com/blog/scada.</a></p><h3>Unclear ownership between IT and OT</h3><p>A significant contributor to ongoing downtime is the lack of clarity regarding who is responsible for system reliability. IT and OT teams often operate with different priorities, incentives, and perspectives, which can create operational blind spots. <strong>The core insight is that downtime thrives in environments where ownership is fragmented across teams.</strong> IT groups may prioritize cybersecurity patches or network policies, while OT teams focus on equipment uptime and production continuity. Without a shared operating model, decisions about when to patch systems, how to manage backups, and how to maintain servers can become inconsistent or delayed.</p><p>This lack of alignment leads to gaps in accountability. If it is unclear who maintains firmware levels, restores backups, or monitors network health, critical tasks may be assumed to be someone else’s responsibility. When an incident occurs, diagnosing the cause becomes slow and inefficient because teams lack a shared understanding of the architecture, the documentation, or the intended operating procedures. Over time, this misalignment increases the frequency and duration of downtime events, even in plants that have invested heavily in modernization.</p><h3>Lack of standardized processes and RCA discipline</h3><p>Technical issues often receive significant attention, but process discipline is an equally powerful predictor of downtime. Many plants operate without consistent failure analysis routines or standardized documentation practices. <strong>The critical insight is that operational inconsistency allows small failures to escalate into recurring downtime.</strong> When an issue is resolved quickly without a structured root cause investigation, the plant loses the opportunity to address the underlying drivers. Without standardized shift passdowns, important context is lost between teams, making repeat failures more likely.</p><p>In environments where documentation practices are inconsistent, troubleshooting becomes time consuming and dependent on tribal knowledge. Maintenance technicians often rely on personal experience rather than a standardized set of procedures or historical failure records. Over time, this creates an environment where recurring issues persist because teams are equipped to fix symptoms but not equipped to resolve deeper causes. Plants that embed RCA frameworks into their daily operations tend to see measurable improvements in equipment reliability and overall operational stability.</p><h3>Investments made without a strategic foundation</h3><p>Modernization efforts often focus on the introduction of advanced technologies such as MES, SCADA platforms, robotics, or industrial analytics. These tools can deliver significant value when implemented on a stable foundation, but they do not resolve foundational issues on their own. <strong>The essential insight is that technology investments fail when they are not aligned with plant reality or business needs.</strong> For example, plants may invest in a new MES while local machine data remains inaccurate or incomplete. Robotics may be deployed on a production line without addressing upstream variability that causes inconsistent feeds. A new SCADA system may be installed without mapping the required data flows or ensuring the supporting network can handle the load.</p><p>These misalignments occur because technology is sometimes selected before the underlying problem is fully understood. Investments become reactive rather than strategic, which leads to expensive deployments that do not address the root cause of downtime. A more effective approach begins with a clear understanding of process constraints, data readiness, and system health. From there, technology becomes an enabler rather than a substitute for foundational improvements. For readers interested in the role of manufacturing execution and data flow within this context, the MES overview at<a href="https://www.joltek.com/blog/manufacturing-execution-systems-mes"> https://www.joltek.com/blog/manufacturing-execution-systems-mes</a> provides helpful background.</p><figure><img alt="What Leading Plants Do Differently" src="https://cdn-images-1.medium.com/max/1024/0*Q5gTNG-pYc-z98Kr" /><figcaption><strong>What Leading Plants Do Differently</strong></figcaption></figure><h3>What Leading Plants Do Differently</h3><h3>Starting with a Plant Systems Health Assessment</h3><p>The most reliable and forward thinking plants approach modernization by first developing a complete understanding of their current environment. <strong>The key insight is that meaningful reliability improvements begin only when leaders have full visibility into the systems that support production.</strong> A structured assessment gives teams an accurate inventory of all PLCs, HMIs, drives, servers, panels, and network devices, which is essential for identifying the underlying causes of downtime. These assessments often reveal unsupported firmware, obsolete components, aging infrastructure, and undocumented modifications that have accumulated over many years. Without this foundation, investments tend to treat symptoms rather than root causes.</p><p>A comprehensive assessment also highlights single points of failure across control systems, networks, and data paths. These vulnerabilities frequently explain why plants experience unpredictable downtime even after significant capital projects. By mapping the architecture and clarifying how OT and IT systems interact, leadership gains a clear view of data movement, dependency chains, and operational risk exposure. Deliverables such as current state documentation, critical risk summaries, and prioritized modernization roadmaps help teams focus investments where they will have the highest impact. Readers who want a deeper overview of how these assessments support modernization can explore related context in the article on manufacturing plant audits at<a href="https://www.joltek.com/blog/manufacturing-plant-audit-digital-transformation"> https://www.joltek.com/blog/manufacturing-plant-audit-digital-transformation</a>.</p><h3>Aligning people, process, and technology before spending</h3><p>Leading facilities do not treat modernization as a purely technical effort. They recognize that people and processes often create the conditions under which downtime occurs. <strong>The central insight is that alignment among engineering, operations, maintenance, IT, and leadership dramatically reduces the likelihood of recurring failures.</strong> Before committing to major investments, high performing plants bring these groups together to agree on objectives, responsibilities, and decision making frameworks. Leadership alignment sessions clarify what the organization is trying to achieve, while also surfacing conflicting expectations that might otherwise hinder implementation.</p><p>Process discipline is equally important. Plants that adopt structured RCA frameworks increase their ability to resolve failures permanently rather than temporarily. These frameworks create consistent routines for investigating issues, documenting findings, and implementing corrective actions. Project governance also plays a vital role by ensuring that new initiatives follow a clear scope, risk management structure, and execution plan. When these elements come together, modernization becomes a coordinated and supported effort rather than a series of disjointed technical projects.</p><h3>Fixing local machine data before scaling enterprise data</h3><p>Organizations often prioritize enterprise level tools, yet the quality of those systems depends entirely on the accuracy and completeness of data generated on the plant floor. <strong>The essential insight is that reliable plant intelligence starts at the machine level, not at the enterprise layer.</strong> Local visibility is the foundation for everything that follows. When machine level data is inconsistent, incomplete, or not exposed properly, higher level systems cannot produce dependable KPIs, historical trends, or performance analytics. As a result, plants invest in advanced tools that ultimately depend on unreliable inputs.</p><p>Best in class facilities adopt a staged approach. They begin with local machine data, then extend that visibility to the line, the plant, and finally the enterprise. Practical steps include defining key performance indicators, implementing historians, configuring secure and efficient data collection, and deploying edge devices that simplify data movement. These actions create a solid data foundation that can be reliably scaled upward. The importance of correct data modeling and visibility is explored in the industrial data article at<a href="https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing"> https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing</a>, which provides additional context on how data quality affects operational decisions.</p><h3>Modernizing network architecture and patching firmware</h3><p>A stable network is one of the most influential factors in achieving high reliability. Many downtime events occur not because equipment fails, but because communication between devices becomes unstable. <strong>The key insight is that network modernization delivers more uptime than many equipment upgrades.</strong> Plants that invest in secure and well segmented architectures significantly reduce the frequency of intermittent faults, dropped packets, or communication losses that disrupt production.</p><p>Leading facilities move away from flat networks and adopt segmentation, VLANs, and NAT where appropriate. Managed switches replace unmanaged ones so that traffic can be controlled, monitored, and optimized. Firmware patching routines are implemented consistently to reduce both reliability risks and cybersecurity exposure. These network improvements support not only stability but also the data movement needed for SCADA, MES, and enterprise level systems. For readers who want a clearer understanding of how SCADA depends on reliable communication, the SCADA fundamentals article at <a href="https://www.joltek.com/blog/scada">https://www.joltek.com/blog/scada</a> provides valuable perspective.</p><h3>Maintaining documentation and building workforce capability</h3><p>Even the most advanced systems cannot deliver sustained reliability without the people who maintain and operate them. High performing plants recognize that the workforce is a critical component of system stability. <strong>The core insight is that strong documentation and a capable, well trained team are essential for maintaining long term reliability.</strong> Documentation ensures that knowledge is retained even when personnel changes occur. It also provides a consistent reference point for troubleshooting, project planning, and process improvement.</p><p>Workforce capability programs reinforce the skills needed to manage modernized equipment and digital systems. Training on controls, networking, SCADA, data tools, and RCA increases confidence and reduces dependency on a small group of experts. When documentation and skills development are integrated into continuous improvement routines, plants are better equipped to prevent recurrence of failures, accelerate troubleshooting, and sustain the value generated by modernization investments.</p><h3>How Joltek Helps Plants Eliminate Downtime at the Source</h3><h3>Providing vendor agnostic visibility into system health</h3><p>Modern manufacturing environments rely on a diverse mix of control platforms, network equipment, and software systems. Plants often work with a combination of legacy and modern technologies that have accumulated over many years, which makes it difficult to understand how the entire environment functions as a whole. <strong>The essential insight is that reducing downtime requires an objective view of the system, independent of any specific vendor or technology preference.</strong> A vendor agnostic approach allows assessments to focus exclusively on the real conditions inside the plant rather than on promoting a particular hardware or software solution. This perspective is especially important in facilities where different generations of equipment coexist or where multiple vendors have been involved in past expansions.</p><p>During assessments, attention is placed on evaluating PLC platforms, HMI deployments, network devices, SCADA servers, MES interfaces, and the configuration of data paths that connect them. The goal is to surface the underlying risks that contribute to recurring production issues. By approaching the system holistically, teams gain clarity on the root causes of instability and can prioritize improvements that deliver meaningful operational outcomes. This method supports plants in developing modernization efforts that align with their actual needs rather than following predefined vendor roadmaps.</p><h3>Combining OT, IT, and operational strategy in a unified approach</h3><p>Downtime is rarely caused by a single failure point. It emerges from the interaction of control systems, networks, data pipelines, and organizational practices. <strong>The key insight is that addressing downtime effectively requires expertise that spans OT systems, IT infrastructure, and operational strategy.</strong> Plants that rely on only one of these perspectives often miss critical dependencies that exist across the broader environment. For example, a networking issue may not be identified if the review focuses on control logic alone. Similarly, a SCADA misconfiguration may go unnoticed if the assessment centers exclusively on network stability.</p><p>By integrating these domains, teams are able to understand how decisions in one area influence reliability in another. This unified perspective improves alignment between engineering, maintenance, IT, and leadership. It also strengthens project planning by ensuring that modernization initiatives incorporate cybersecurity, data architecture, and operational workflows from the start. Readers interested in the role of data architecture within this integrated view can explore plant level visibility concepts in the following resource:<a href="https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing"> https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturing</a>.</p><h3>Leveraging field experience from diverse manufacturing environments</h3><p>A significant advantage in addressing downtime is practical familiarity with real world manufacturing conditions. Plants operate under unique constraints related to product type, production speed, regulatory requirements, and organizational culture. <strong>The important insight is that meaningful improvement comes from applying lessons learned across many different environments.</strong> Experience from high speed consumer goods, food and beverage, regulated environments, and large scale discrete manufacturing provides perspective on patterns that repeat across industries.</p><p>Field exposure to projects at organizations such as P and G, Kraft Heinz, and Post Holdings demonstrates how control systems, workforce capability, equipment design, and cross functional alignment influence operational outcomes. These experiences also reveal how plants adapt to the tension between production pressures and the need for long term reliability. Exposure to a wide range of PLCs, HMIs, SCADA systems, networks, and data platforms strengthens the ability to diagnose issues quickly and anticipate challenges that often arise during modernization. This practical understanding is essential for helping teams navigate the complexities of system upgrades and integration.</p><figure><img alt="A Practical Framework for Eliminating Downtime at the Source" src="https://cdn-images-1.medium.com/max/1024/0*sdn7yim76oUb2Z8J" /><figcaption><strong>A Practical Framework for Eliminating Downtime at the Source</strong></figcaption></figure><h4>Supporting improvement through a structured engagement flow</h4><p>Modern manufacturing requires more than technical fixes. Sustainable reliability comes from a structured approach that guides teams from initial understanding to long term execution. <strong>The central insight is that a disciplined methodology increases the likelihood of eliminating downtime at its source.</strong> A structured engagement begins by discovering the operational context, the pain points experienced by plant teams, and the goals of leadership. This discovery step ensures that the broader business impact is understood before any technical evaluation begins.</p><p>The next stage involves assessing the systems in detail. This includes walking the plant floor, reviewing documentation, capturing system inventories, evaluating network architectures, and analyzing control logic. The assessment identifies where risks, inefficiencies, or undocumented changes exist. Following assessment, the design phase converts findings into a prioritized roadmap. This roadmap outlines short term actions that reduce immediate risk as well as long term improvements that support growth, modernization, and data enablement.</p><p>The final stage focuses on delivering improvements. This may include supporting integration projects, guiding migrations, enhancing documentation, aligning teams, or improving RCA processes. The emphasis is always on ensuring that plants achieve reliable, stable operations while building the capability to maintain those outcomes over time.</p><h3>The Path to a Reliable, Modern Plant</h3><h3>Understanding that downtime is a systems problem</h3><p>Many organizations begin their modernization journey by replacing equipment, adding new software, or introducing more automation. These efforts often deliver localized improvements, yet unplanned downtime continues to appear across lines, shifts, and assets. <strong>The central insight is that downtime rarely originates from a single piece of hardware and almost always reflects weaknesses across the broader system.</strong> Control components, networks, data flows, workforce capability, and process discipline work together to determine reliability. When any of these elements operate below the required standard, the entire system becomes vulnerable. Plants that recognize this interconnectedness gain a significant advantage because they can target the true origin of instability rather than repeatedly treating symptoms.</p><h3>Recognizing why investments fail without visibility, alignment, and architecture</h3><p>Modernization often accelerates once teams identify that their earlier efforts were limited by blind spots in their understanding of the plant. Without clear documentation, a shared architectural view, or aligned priorities across IT, OT, engineering, and operations, investments tend to drift toward isolated improvements. <strong>The essential insight is that reliability improves only when leaders have a complete picture of how their systems function and how decisions in one area affect another.</strong> Plants that skip this visibility phase often discover late stage integration issues, data inconsistencies, unsupported equipment, or unmanaged risks that undermine the value of their projects. Alignment ensures that the organization is moving in one direction, and architectural clarity ensures that new investments strengthen the system instead of adding complexity.</p><h3>Applying a structured approach to reduce risk and improve reliability</h3><p>A consistent pattern across high performing plants is their commitment to structured evaluation, planning, and execution. These plants avoid reactive modernization and instead follow a clear methodology that begins with understanding the current state, identifying risks, and shaping a roadmap grounded in operational priorities. <strong>The important insight is that discipline in how improvements are planned greatly reduces the likelihood of unexpected failures or costly rework.</strong> A structured approach also protects capital by ensuring that each investment has a defined purpose within the larger system, whether the goal is improved data visibility, safer operations, higher throughput, or better asset reliability. This type of planning creates clearer governance and more predictable outcomes.</p><figure><img alt="The Path to a Reliable, Modern Plant" src="https://cdn-images-1.medium.com/max/1024/0*GwHt2yA9XKMgtLNz" /><figcaption><strong>The Path to a Reliable, Modern Plant</strong></figcaption></figure><h3>Unlocking higher performance and sustainable modernization</h3><p>Plants that follow the principles described in this article tend to experience more stable equipment performance, increased uptime, and stronger confidence in their operational systems. They also create an environment where improvements build upon each other rather than conflict. <strong>The key insight is that sustainable modernization comes from strengthening the foundations that support technology, not from the technology itself.</strong> By focusing on visible data flows, strong network design, consistent RCA discipline, and clear ownership between teams, organizations position themselves to benefit from advanced tools such as SCADA, MES, and analytics platforms. For readers who want additional perspective on how modern data systems support reliability, the article on manufacturing execution systems at<a href="https://www.joltek.com/blog/manufacturing-execution-systems-mes"> https://www.joltek.com/blog/manufacturing-execution-systems-mes</a> provides a useful resource.</p><h3>Final reflections on the modernization journey</h3><p>Reliable operations and modern manufacturing capabilities do not emerge from isolated initiatives. They develop through a deliberate process of understanding, alignment, and continuous improvement. The plants that succeed are those that recognize that their systems must operate as a cohesive whole rather than as a collection of individual technologies. Modernization does not start with what equipment is purchased or which software is selected. It begins with a clear understanding of what truly needs to change, why it matters, and how the organization will support that change over time.</p><p>‍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab795ae2a27a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Top Manufacturing Teams Cut Through Noise, Trust Operators, and Focus on What Matters]]></title>
            <link>https://vrom.medium.com/how-top-manufacturing-teams-cut-through-noise-trust-operators-and-focus-on-what-matters-daa90124947e?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/daa90124947e</guid>
            <category><![CDATA[lean-six-sigma]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[manufacturing]]></category>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 16:19:53 GMT</pubDate>
            <atom:updated>2025-07-31T16:19:53.859Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Looks Good Is Not Always What Works</h3><p>There is a strange pattern in manufacturing today. Many plants have the tools. The systems are connected. The dashboards are green. But the problems are still there. Output misses the target. Teams chase anomalies that do not exist. And smart people spend their time fixing things no one asked them to solve.</p><p>This issue of FRAME is about the difference between what looks good and what actually works. You will read how a line operator caught what automation missed. You will see how your most trusted metric might be hiding the truth. And if you are an engineer looking to grow, you will learn how to shift from solving tasks to driving outcomes. These are not tactics. They are patterns of thinking that change how performance is built.</p><h3>Clarity Outsmarts Complexity</h3><p>In modern manufacturing, complexity is often mistaken for progress. When teams launch five digital pilots, roll out multiple platforms, and add layers of visualization, it can feel like things are moving forward. The problem is that complexity alone rarely leads to results. The real power lies in clarity &amp; knowing what matters, why it matters, and how to act on it. Without clarity, all the dashboards in the world will only give you prettier confusion.</p><h3>The Trap of Doing More</h3><p>Many manufacturing leaders fall into the same well-intentioned trap. They keep adding tools, teams, and tactics because they believe more activity means more improvement. I’ve seen plants layer MES on top of SCADA, add AI-powered maintenance alerts, and then struggle to understand why nothing actually improves.</p><p>This happens because <strong>complexity creates the illusion of action</strong>, while often obscuring the root problem. Uncoordinated projects lead to duplicated efforts. Digital initiatives run in silos. Data becomes harder to trust. Everyone is busy, but few are aligned. The result is an operation that feels modern but functions reactively.</p><p>Before starting anything new, ask three questions:</p><ul><li>What specific outcome are we solving for?</li><li>Who owns the result across functions?</li><li>What will we stop doing to make space for this?</li></ul><p>If those answers are not crystal clear, you are not solving a problem. You are adding to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jY25UhYevu-HWcQ2" /><figcaption>Figure 1 — How Top Manufacturing Teams Cut Through Noise, Trust Operators, and Focus on What Matters | Clarity Outsmarts Complexity</figcaption></figure><h3>One Clear Outcome Beats Ten Half Baked Efforts</h3><p>In a recent engagement, a manufacturer had spent close to a million dollars on analytics tools over the past three years. They had predictive maintenance software, real-time performance dashboards, and an enterprise historian. When I visited their facility, I asked one simple question: which of these tools helped you improve your worst-performing line?</p><p>The answer was silence.</p><p>They had not identified a weakest link. They had not defined what success looked like for the system as a whole. They had not used any of their tools to solve one core issue from start to finish. It was a perfect case of motion without progress.</p><p>To break this cycle:</p><ul><li>Identify a specific operational bottleneck that is costing time or quality</li><li>Align stakeholders from maintenance, operations, and engineering around it</li><li>Use your digital stack only to support that mission, not to prove it exists</li></ul><p>Improvement happens when a team builds muscle around solving problems completely. Not when they decorate the process with more tech.</p><h3>Reflection as a Strategy</h3><p>The factories that improve year over year are not necessarily the ones with the best automation or newest tools. They are the ones that carve out time to ask what is working, what is not, and why.</p><p>One of the most successful leadership teams I’ve worked with has a thirty-minute weekly reflection meeting. No slides. No excuses. Just one question: what did we learn this week that changes how we work next week?</p><p>Reflection is not a soft skill. It is a strategic process for sense-making. It enables faster correction, better alignment, and sharper insight. When reflection is built into the culture, people feel less pressure to chase trends and more freedom to stay focused.</p><p>If your plant is struggling to make progress despite being “busy,” you do not need more complexity. You need clarity. And that clarity begins when you stop to think.</p><h3>When an Operator Becomes the Best Sensor</h3><p>The most expensive software in the world cannot hear a strange vibration or sense hesitation in a machine’s rhythm the way a seasoned operator can. While many plants invest heavily in sensors, PLCs, and machine learning tools to diagnose equipment health and optimize performance, there are still critical insights that come from the people closest to the equipment. Not everything worth knowing is visible on a screen.</p><p>This section explores a real-world example from a factory floor where it was not a dashboard or alert that solved the issue, but the human ear. More importantly, it shows how good leadership can make these moments more common and more intentional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w3Kv-O1U6yjWU5vQ" /><figcaption>Figure 2 — How Top Manufacturing Teams Cut Through Noise, Trust Operators, and Focus on What Matters | Sensors Don’t Hear Everything</figcaption></figure><h3>The Case of the Phantom Valve</h3><p>A mid-sized facility was struggling with inconsistent batch cycle times on one of its core production lines. Some batches would finish on schedule, while others ran five to eight minutes longer, with no clear pattern. The team had deployed every available tool to get to the bottom of it. They combed through the historian, pulled SCADA logs, reviewed alarms, and even introduced a temporary thermal camera to monitor equipment temperature.</p><p>Nothing stood out.</p><p>It was during a floor walk that one of the line operators, who had worked the same machine for nearly a decade, mentioned that the startup “sounded off” on slower batches. He could not explain exactly what he meant at first, but he insisted something felt different. That comment triggered a closer manual inspection of the system. Eventually, they discovered that a diaphragm valve upstream had started to drift slightly from its set position due to a worn actuator spring. It was opening slower than usual, causing a delayed pressure equalization which affected mixing time.</p><p>None of the sensors were sensitive enough to detect the slow change. The actuator’s feedback still reported that the valve was in position. But the process was being impacted. The fix cost under a thousand dollars. The downtime it had been causing was estimated at over seventy thousand dollars per month.</p><p>This was not a failure of technology. It was a failure of reliance on technology alone. <strong>The lesson is simple: the most powerful diagnostic tool is often a human who knows the process deeply.</strong></p><h3>People and Data Are Partners</h3><p>Too often, there is an implicit assumption that data is clean, complete, and sufficient. But all data has gaps. Sensors have blind spots. Systems drift slowly over time. A flow meter can be calibrated. A PLC can be reprogrammed. But an operator who notices subtle changes in how a machine sounds, shakes, or smells is an irreplaceable asset.</p><p>That is why advanced systems should not aim to replace operators but to partner with them. Human sensing is not a fallback. It is a parallel system that fills in the blanks where digital tools fall short.</p><p>To make this partnership work:</p><ul><li>Capture observations during operator rounds, especially when performance varies</li><li>Add structured “gut check” notes to digital logs where appropriate</li><li>Cross-reference production anomalies with shift logs or verbal reports</li></ul><p>Human input is data. It just needs a place to live.</p><h3>Coaching for Embedded Insights</h3><p>One of the best things you can do as a technical leader is help your team learn how to listen. Not just to alarms or metrics, but to what the floor is telling you in real time. When I work with site managers or operations leaders, I always include coaching on floor walk strategy.</p><p>Here are a few simple but effective practices I have taught:</p><ul><li>Start with open-ended questions like “What feels different today?”</li><li>Walk the floor during changeovers or startups when problems are most likely to emerge</li><li>Use silence. Let people fill it. That is when the real information comes out</li><li>Pair engineers with veteran operators and rotate them across shifts for pattern recognition</li></ul><p>The result is not just early detection. It is cultural. Operators start to feel their input matters. Engineers build deeper process understanding. And problems start to get solved before they ever become metrics.</p><p>If your factory feels like it is getting smarter but your problems are not going away, it may be time to stop asking for more data and start listening to the people already living inside the process.</p><h3>Availability Doesn’t Mean Attainment</h3><p>Availability is one of the most widely reported metrics on the plant floor. It is also one of the most misunderstood. Teams often celebrate high uptime numbers, assuming they are a sign of strong performance. But if the actual output does not match the plan, something is off. The truth is that availability, when used without context, can be deeply misleading. Just because the line is technically running does not mean it is delivering what the business needs.</p><p>This section explores the hidden flaws inside availability metrics and offers practical advice on what to track instead. It is a reminder that real performance comes from flow, not from checkmarks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4cSKRiCyApOp8BM-" /><figcaption>Figure 3 — How Top Manufacturing Teams Cut Through Noise, Trust Operators, and Focus on What Matters | When Uptime Lies</figcaption></figure><h3>Why Uptime Numbers Can Lie</h3><p>I was once working with a food manufacturing plant that reported an availability of over 93 percent on their packaging lines. That would suggest world class performance. But when we looked deeper, they were missing their weekly production targets by 8 to 12 percent consistently. The operators were frustrated. The planners were behind. The managers were confused. On paper, everything looked fine. In practice, it was not.</p><p>The problem was how downtime was defined and measured. Micro stops under ten seconds were not recorded. Manual resets were logged as part of run time. Changeovers were treated as planned time regardless of duration. As a result, the availability number looked healthy but it was disconnected from the real experience of operating the line.</p><p>This is a common pattern. In many plants, <strong>the availability metric gives a false sense of control because it filters out the friction that operators live with every day</strong>. If you want the number to mean something, you have to clean up the definition and track what actually interrupts flow.</p><h3>Measure Human Interruptions</h3><p>The most valuable signal you can track might not be a classic KPI. It might be something like how often a line requires human input to keep running. In stable operations, human involvement should be intentional and focused. When operators are constantly hitting reset buttons, adjusting speeds, or using joysticks to correct product positions, it tells you that your system is not truly autonomous.</p><p>Here are some indicators that often get ignored but reveal more than a percentage ever could:</p><ul><li>Number of operator-initiated resets per shift</li><li>Frequency of stop and start cycles outside scheduled breaks</li><li>Incidents of unattended stops requiring investigation</li><li>Manual overrides of machine logic</li></ul><p>This kind of data is hard to get from traditional systems because it lives in gray areas. That is why we recommend working closely with operators and line leads to build logging tools that capture their reality. Even simple paper forms or mobile checklists can surface valuable patterns over time.</p><p>If you are interested in exploring better methods for <strong>system troubleshooting and root cause visibility</strong>, check out Joltek’s post on <a href="https://www.joltek.com/posts/plc-data-structures-polling-troubleshooting?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=how-top-manufacturing-teams-cut-through-noise-trust-operators-and-focus-on-what-matters"><em>troubleshooting PLC data structures</em></a>. It includes practical examples from the field where traditional KPIs failed to expose the real issue.</p><h3>Go Beyond Rate to Rhythm</h3><p>A number that looks good over a full shift can still hide volatility. That is why some of the most advanced manufacturers focus on flow-based metrics like average uninterrupted run time or time between interventions. These metrics give you insight into rhythm — the consistency and predictability of the process.</p><p>When a line can run cleanly for two or three hours without any touch, you know it is healthy. When it needs to be nudged every few minutes, it is just surviving. In one case, we helped a plant move from a pattern of fifty small stops per shift to just five, by focusing not on increasing rate but on smoothing rhythm. Their availability number barely changed. But their throughput increased by twelve percent.</p><p>Think of it this way:</p><ul><li>Rate is how fast you can go</li><li>Rhythm is how long you can stay there without interruption</li></ul><p>You need both, but it is rhythm that unlocks performance you can rely on.</p><h3>Stop Solving Problems That Only You Care About</h3><p>Many highly capable engineers plateau in their careers not because they lack skill, but because they focus on the wrong problems. They chase technical wins that are invisible to the broader organization. They optimize small systems no one is watching. They spend hours troubleshooting issues that are technically interesting but have little impact on cost, safety, or customer satisfaction. The result is quiet frustration. They feel overlooked. But from the outside, no one sees the value they bring.</p><p>This section explores how to shift from being a strong individual contributor to being seen as a strategic player. It is not about working harder. It is about aligning your work with what the business actually cares about.</p><h3>Do Your Wins Matter to Others?</h3><p>I once coached a young engineer who had just completed a major optimization of a tank cleaning sequence. He shaved off four minutes from each CIP cycle and was excited to show the logic improvements. When he told leadership, they nodded politely and moved on. He was confused. The work had been smart. But he had missed one thing. The tank was not a bottleneck. The line was waiting on packaging. His work was good, but it did not move the needle.</p><p>That is a common pattern.</p><p><strong>You cannot earn influence by solving problems that only you understand or care about.</strong> If you want to grow in your career, you have to connect your work to something larger. That means:</p><ul><li>Asking how your project impacts other teams</li><li>Aligning with the biggest constraints in the operation</li><li>Tying improvements to financial, safety, or throughput outcomes</li></ul><p>When you start selecting your priorities through a business lens, your wins will get noticed. And your name will come up in the right conversations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0nc99XGMmprmlLk0" /><figcaption>Figure 4 — How Top Manufacturing Teams Cut Through Noise, Trust Operators, and Focus on What Matters | From Technical Hero to Strategic Leader</figcaption></figure><h3>Master the Abstract Summary</h3><p>As you move up, your audience changes. You are no longer explaining your work to other engineers. You are explaining it to plant managers, directors, and VPs who manage dozens of priorities. They do not need to understand the code or the electrical drawings. They need to understand the business case, the risk profile, and the result.</p><p>One of the most valuable skills you can build is writing clear, concise, abstract summaries of your work. Think of them as internal memos. Instead of a technical walkthrough, you write a short narrative:</p><ul><li>What problem did we observe?</li><li>What was the risk if left unaddressed?</li><li>What was the chosen solution?</li><li>What did it achieve?</li></ul><p>No jargon. No screenshots. No ladder logic. Just impact. If you need help structuring these, you might find value in how we approach project documentation and analysis over at Joltek. It is about clarity that travels.</p><p>Once you master this form of communication, you will find that people in the organization start bringing you into broader conversations. They see you as someone who understands not just systems, but strategy.</p><h3>Grow by Teaching, Not Just Doing</h3><p>One of the fastest ways to level up your leadership is to teach. When you explain something well to others, you deepen your own understanding. When you help others improve, you multiply your value. And when people around you grow, your influence grows with them.</p><p>A few years ago, I started organizing weekly peer sessions for a client’s engineering team. Each week, one person would share a project, a failure, or a technique. These were not formal. No PowerPoint. Just a whiteboard or a live walkthrough of something useful. Within three months, the team’s technical competency improved. But more importantly, their confidence improved. People started reaching across departments. Knowledge became culture. And the engineers who ran those sessions? They got promoted.</p><p>Teaching does not require perfection. It requires generosity. It signals maturity. It creates space for others to rise.</p><h3>Clear Thinking Is a Competitive Advantage</h3><p>In a world where complexity is easy to buy, clarity is hard to earn. But it is the teams who think clearly, act early, and stay grounded in what matters that actually move the needle. Whether it is catching drift before downtime, choosing better metrics, or communicating work that aligns with the business, progress starts with awareness.</p><p>Use this issue as a prompt to reflect. Where are you doing too much? Where are you not listening enough? What are you solving that no one needs? And what could change if you took thirty minutes a week to ask better questions?</p><p>That is where performance begins.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daa90124947e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Stalled Transformations to Stable Operations: How Floor Presence, Standards, and Teaching…]]></title>
            <link>https://vrom.medium.com/from-stalled-transformations-to-stable-operations-how-floor-presence-standards-and-teaching-7612174e38eb?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7612174e38eb</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 02:10:07 GMT</pubDate>
            <atom:updated>2025-07-31T02:10:07.329Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Stalled Transformations to Stable Operations: How Floor Presence, Standards, and Teaching Create Real Change</h3><p>In this issue of FRAME, we explore what actually drives sustainable improvement. Not slogans. Not dashboards. But presence, clarity, and the often overlooked skill of teaching.</p><p>You’ll find lessons drawn from factory floors in Japan, breakdowns of response time versus repair time, examples of how standards like centerlines create operational consistency, and why your ability to teach might be the most underrated skill in your career.</p><p>If you care about building stronger systems, developing leadership that matters, and executing change that lasts beyond the kickoff meeting, this issue is for you.</p><p><strong>Subscribe at </strong><a href="https://framexl.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-stalled-transformations-to-stable-operations-how-floor-presence-standards-and-teaching-create-real-change"><strong><em>framexl.com</em></strong></a><strong> to get future editions delivered directly to your inbox.</strong><br><strong>To learn more about consulting, audits, and technical training, visit </strong><a href="https://joltek.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-stalled-transformations-to-stable-operations-how-floor-presence-standards-and-teaching-create-real-change"><strong><em>joltek.com</em></strong></a><strong>.</strong></p><h3>Core Insight: You Can’t Solve Plant Problems from the Boardroom</h3><h3>𝗪𝗵𝗮𝘁 𝗝𝗮𝗽𝗮𝗻 𝗧𝗮𝘂𝗴𝗵𝘁 𝗠𝗲 𝗔𝗯𝗼𝘂𝘁 𝗩𝗶𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆</h3><p>Years ago, I spent several weeks in Japan during a series of Factory and Vendor Acceptance Tests for Procter &amp; Gamble. I had just passed my first year with the company and, surprisingly, I was the most senior person from our team on site. On the Japanese side, the youngest engineer had already been with the machine builder for five years. When I asked about his experience, he smiled and said he was still learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oK-TOMEFvk_52uxx" /><figcaption>Figure 1 — From Stalled Transformations to Stable Operations | Strategy vs. Presence</figcaption></figure><p>That humility was real, but what impressed me more was the depth of training. These were not engineers pushed into roles early. They were deeply immersed in the process. They understood the machinery, the people, the expectations, and the purpose of every detail on the floor. Every engineer I met had spent years walking the line before ever being asked to lead it.</p><p>𝗧𝗵𝗲𝗿𝗲 𝘄𝗮𝘀 𝗮 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗶𝗻 𝗽𝗮𝗰𝗲, 𝗯𝘂𝘁 𝗮𝗹𝘀𝗼 𝗶𝗻 𝗽𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲. Instead of rushing projects to meet a date, they tightened their tolerances. Instead of assuming the customer would find defects during factory acceptance, they checked and double-checked every specification. And most importantly, they brought senior leadership to the floor for every validation. Department heads, plant leaders, and technical specialists stood together as the equipment was tested. They watched. They asked questions. And when problems were found, both sides worked together to solve them immediately. No blame. No delay. Just focused, structured resolution in full view of the people responsible for using the equipment every day.</p><h3>𝗬𝗼𝘂 𝗛𝗮𝘃𝗲 𝗧𝗼 𝗚𝗼 𝗧𝗼 𝗪𝗵𝗲𝗿𝗲 𝗧𝗵𝗲 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 𝗟𝗶𝘃𝗲𝘀</h3><p>That moment has stayed with me. Not because it was organized. Because it was honest. I realized something that day that I carry with me still. <strong>𝗬𝗼𝘂 𝗰𝗮𝗻𝗻𝗼𝘁 𝘀𝗼𝗹𝘃𝗲 𝗮 𝗽𝗹𝗮𝗻𝘁 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗯𝘆 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 𝗮 𝗿𝗲𝗽𝗼𝗿𝘁.</strong> You have to walk the floor. You have to hear the machine. You have to see how operators interact with it, how workarounds form, and how real issues surface in motion.</p><p>In North America, we often try to fix operations through strategy meetings and PowerPoint decks. But the reality is that many decisions are made far from the line. And when they are, they miss the nuance. They miss the friction. They miss the impact of a ten-second delay or a misaligned changeover or a half-trained operator trying to keep production going with outdated instructions. 𝗧𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗱𝗼𝗲𝘀 𝗻𝗼𝘁 𝗳𝗮𝗶𝗹 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗼𝗳 𝗯𝗮𝗱 𝗶𝗱𝗲𝗮𝘀. 𝗜𝘁 𝗳𝗮𝗶𝗹𝘀 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗻𝗼 𝗼𝗻𝗲 𝗴𝗼𝗲𝘀 𝘁𝗼 𝗰𝗵𝗲𝗰𝗸 𝗵𝗼𝘄 𝘁𝗵𝗲 𝗶𝗱𝗲𝗮 𝗳𝗶𝘁𝘀 𝗶𝗻𝘁𝗼 𝗿𝗲𝗮𝗹 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲.</p><h3>𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝗟𝗶𝘃𝗲𝘀 𝗢𝗻 𝗧𝗵𝗲 𝗙𝗹𝗼𝗼𝗿</h3><p>Most manufacturing teams are not struggling for vision. They are struggling for visibility. A great strategy that ignores operational context will always create more confusion than progress. I have seen beautifully designed rollouts collapse because no one checked whether the people running the machines could actually use the new system. I have seen KPI dashboards that looked great to leadership but meant nothing to the supervisors below them. And I have seen initiatives that completely missed their target simply because no one asked the operator what the real issue was.</p><p>𝗧𝗵𝗲 𝗺𝗼𝘀𝘁 𝘀𝘂𝗰𝗰𝗲𝘀𝘀𝗳𝘂𝗹 𝗶𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁𝘀 𝗮𝗿𝗲 𝗮𝗹𝘄𝗮𝘆𝘀 𝗯𝘂𝗶𝗹𝘁 𝗼𝗻 𝗽𝗿𝗲𝘀𝗲𝗻𝗰𝗲. Not presence for a tour or a check-in, but presence as a habit. Walking the line. Asking questions. Watching the work as it actually happens. It is not glamorous, but it is where the truth lives.</p><h3>𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆𝘀</h3><p><strong>𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗲𝘀 𝗱𝗼 𝗻𝗼𝘁 𝘄𝗼𝗿𝗸 𝘂𝗻𝘁𝗶𝗹 𝘁𝗵𝗲𝘆 𝗮𝗿𝗲 𝘁𝗲𝘀𝘁𝗲𝗱 𝗮𝗴𝗮𝗶𝗻𝘀𝘁 𝗳𝗿𝗶𝗰𝘁𝗶𝗼𝗻.</strong> If you want a new process to work, you need to take it to the floor and test it with the people doing the job.</p><p><strong>𝗣𝗲𝗼𝗽𝗹𝗲 𝗳𝗶𝘅 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝘁𝗵𝗲𝘆 𝗰𝗮𝗻 𝘀𝗲𝗲.</strong> The earlier you get leadership involved on the floor, the more context they build. The better they understand how to support real change.</p><p><strong>𝗧𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗮 𝗰𝗼𝗻𝘁𝗮𝗰𝘁 𝘀𝗽𝗼𝗿𝘁.</strong> You cannot coach it from a distance. You have to be in it. Watching. Learning. Adjusting.</p><p>If you want to modernize your operation, begin with the simplest habit you can build. Walk the floor. Do it often. Do it with curiosity. Talk less and observe more. Then ask yourself one question. Is the strategy I am building something that this team can actually use tomorrow? If the answer is no, you have more walking to do.</p><h3>On the Floor: The Overlooked Discipline Behind High-Performing Lines</h3><h3>Why Centerlines Are Not Just a TPM Tool</h3><p>Walk into any world-class facility and you will notice something subtle but powerful. Near every major piece of equipment, there is a clear visual or digital reference that tells the operator where the system should be. These are <strong>centerlines</strong>, and they are not just marks on a machine. They are the foundation of control, consistency, and continuous improvement.</p><p><strong>Centerlines capture the ideal operating conditions</strong> for key parameters. That could mean roller positions, clamp torque, feed speeds, valve settings, or sensor distances. In essence, they are a contract between engineering, maintenance, and operations. When things go wrong, centerlines provide a known baseline. When things go right, they are the reason performance can be repeated.</p><p>The issue is that in many North American plants, <strong>centerlines are treated as optional.</strong> They are either not documented, not enforced, or quietly bypassed as teams chase daily output. That kind of informal culture is what erodes quality over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ldiezibtivPuTIWL" /><figcaption>Figure 2 — From Stalled Transformations to Stable Operations | The Centerline Maturity Curve</figcaption></figure><h3>Small Deviations Become Big Costs</h3><p>The most dangerous problems in a plant are not always dramatic. Often, they are slow drifts. A belt tension that is off by just a few newtons. A heat sealer that runs a few degrees too cold. A sensor that creeps a centimeter out of position. Without a centerline, those changes go unnoticed until performance degrades beyond the control of frontline teams.</p><p>A study by the Japan Institute of Plant Maintenance found that <strong>lack of centerline adherence is one of the top three contributors to chronic minor stoppages</strong>. Another benchmarking report from the TPM Awards Council showed that <strong>plants with mature centerline systems see an average of 15 to 25 percent improvement in changeover time</strong> within the first six months of implementation. That is not a software upgrade. That is not an expensive consultant. That is the result of clarity, visibility, and process ownership.</p><h3>Lessons from the Floor</h3><p>In one facility I audited, three identical machines were producing three very different results. When we reviewed the documentation, two of the machines had handwritten settings posted from five years ago. The third had nothing. Operators adjusted settings based on feel. One crew swore the optimal feeder speed was 75 percent. Another insisted it was 68. There was no common truth. Just tribal knowledge and habit.</p><p>We brought together line leads, maintenance, and engineering. Over the next week, we ran short controlled batches, captured performance, and documented the best known conditions. Then we locked in the settings and trained every shift. Within three weeks, the scrap rate dropped by nine percent and changeovers stabilized across all crews. No new equipment. No major investment. Just <strong>a structured way to hold the process accountable to its potential.</strong></p><h3>Centerlines Are a Leadership Tool</h3><p>Here is the real insight. <strong>Centerlines are not a technical solution. They are a leadership choice.</strong> When they are absent, it tells the team that inconsistency is acceptable. When they are enforced, it signals that standards matter and performance is expected.</p><p>The absence of centerlines is not a sign of complexity. It is a sign of neglect. In facilities that invest millions into automation, it is surprising how often no one can answer a basic question: how should this machine be running?</p><p>Until that is clear, no digital transformation will fix the chaos. If you want to talk about machine learning, predictive maintenance, or AI on the floor, but you cannot confirm the mechanical position of a forming plate, <strong>you are skipping steps</strong>.</p><h3>The Right Time to Start Is Now</h3><p>You do not need to overhaul the plant. Start with one piece of equipment. Define the settings. Mark them visually. Document them digitally. Train the team. Then measure how performance changes. You might be surprised by how much waste was hiding in those tiny misalignments.</p><p>If your operators cannot show you the ideal setup for their station in under sixty seconds, the opportunity is right in front of you. Start with what you can see. Build trust with what you can prove. Lead with what you can repeat. That is the work.</p><h3>The Metrics That Matter: Why Time to First Action Is the Hidden Cost Driver in Downtime</h3><h3>From the Board to the Wrench</h3><p>For a period of time, I was the maintenance manager at a Kraft Heinz facility in Fullerton, California. We shut it down in 2018, but the lessons I took from that plant still inform how I look at manufacturing operations today. I led a team of 26 mechanics, technicians, and electricians. Each day, our job was to keep the lines running and keep the team improving. The work was reactive, relentless, and often thankless. But it also provided one of the clearest insights into what truly separates stable operations from constant firefighting.</p><p>One metric I tracked obsessively was what I called <strong>Time to First Action</strong>. It measured how long it took between the moment operations called for support and the moment someone from the maintenance team actually began working on the issue. Not when the line was fixed. Not when the downtime event was logged. But when someone showed up, tools in hand, and started addressing the problem.</p><p>What I saw was striking. Sometimes, the team jumped into action in under three minutes. Other times, it took fifteen, twenty, even thirty minutes before anyone moved. And that was not due to laziness or incompetence. It was due to everything else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xDRsStI_LmkmYFCX" /><figcaption>Figure 3 — From Stalled Transformations to Stable Operations | Response Time Breakdown</figcaption></figure><h3>Understanding the Delay Before the Fix</h3><p>In many plants, metrics like <strong>Mean Time to Repair (MTTR)</strong> are tracked religiously. But they miss the prelude. The handoffs. The wait time. The confusion. The missing context. The technician searching for the right drawing. The call to a supervisor. The walk across the floor because radios were not working. The operator unsure how to describe what went wrong.</p><p>That gap between detection and first response is pure loss. And in reactive plants, it is where the majority of unmeasured waste lives.</p><p>A McKinsey report on downtime response patterns found that <strong>as much as 30 percent of total downtime is consumed before any repair begins</strong>. That is not failure time. That is response time. And it is invisible in most reporting systems.</p><h3>People, Process, and Clarity</h3><p>Improving Time to First Action is not just a matter of staffing. It is a function of system clarity. In Fullerton, we began documenting the delay reasons. Sometimes we found process gaps: the notification went to the wrong screen. Sometimes it was resource availability: two techs were already mid-repair. But often, it was a lack of clarity. What was the issue? Who owned it? Did the operator try a reset first?</p><p>So we started with what we could control. We trained operators on a basic triage process. We posted visual standards for escalation. We put radio protocols in place to eliminate confusion. We made sure work orders included the right context. Over time, response times improved, not because we hired more people, but because we reduced friction.</p><h3>Technology Without Clarity is Just Noise</h3><p>Later in my career, I saw facilities try to automate this response layer with software. They wired up alerts to tablets, screens, and smart watches. But the same delays crept in. Why? Because <strong>pushing a notification is not the same as mobilizing action</strong>. A sensor alarm that no one understands is just noise. A work order without context is just another task in the queue.</p><p>If you want to drive down unplanned losses, you cannot just invest in detection. You need to invest in reaction. That means <strong>well-defined escalation protocols</strong>, <strong>clear task ownership</strong>, <strong>shared language between ops and maintenance</strong>, and most importantly <strong>a culture that respects the time between failure and first movement</strong>.</p><h3>Final Thought</h3><p>You do not need to wait for an expensive integration to start tracking this. Pick a line. Note when an issue is reported. Note when someone begins working on it. Do it for a week. You will quickly see patterns, and you will see where improvement lives.</p><p>Because the truth is simple. <strong>Until someone starts turning a wrench, no progress is being made.</strong> And in the world of manufacturing, minutes are not just numbers. They are margin.</p><h3>Career Shift: 𝗧𝗵𝗲 𝗠𝗼𝘀𝘁 𝗨𝗻𝗱𝗲𝗿𝗿𝗮𝘁𝗲𝗱 𝗖𝗮𝗿𝗲𝗲𝗿 𝗦𝗸𝗶𝗹𝗹 𝗶𝗻 𝗠𝗮𝗻𝘂𝗳𝗮𝗰𝘁𝘂𝗿𝗶𝗻𝗴 is 𝗞𝗻𝗼𝘄𝗶𝗻𝗴 𝗛𝗼𝘄 𝘁𝗼 𝗧𝗲𝗮𝗰𝗵</h3><p>As many of you know, I consider myself an educator. That may have come from my father who spent most of his life in academia. He had a PhD in nuclear physics, a master’s in computer science, and served as the dean of a university. His career was built on helping others grow. That mindset stayed with me. Even in fast-paced and high-pressure technical environments, I have always found value in being able to explain something clearly, walk someone through a process, or help others succeed by transferring what I know. And over time, I have come to believe something very simple. If you want to grow your career in manufacturing, engineering, or operations, you need to get good at teaching.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ksduDg9ku9icqO7g" /></figure><p>Figure 4 — From Stalled Transformations to Stable Operations | The Engineer’s Ladder of Influence</p><p>This shows up earlier than most people realize. The first time a junior engineer joins your team, your ability to teach defines whether they contribute quickly or struggle for months. When you roll out a new system, your ability to train others defines whether it sticks. When you troubleshoot downtime on the floor, your ability to walk someone through the logic determines whether they become independent or call you every time it happens again. Teaching is not something extra. It is how knowledge scales. It is how teams stop relying on one person to solve everything. It is how leaders emerge without needing a title.</p><p>Most engineers were never taught how to teach. The education system rewards you for solving problems alone. It rarely teaches you to explain your thinking in a way others can use. So when engineers enter the workforce, they often default to the same frustrating cycle. They say things like just watch me or you’ll figure it out or I had to learn the hard way and so should you. That attitude does not build strong teams. It builds dependence. And it erodes performance every time someone leaves, rotates, or burns out.</p><p>The best engineers I have worked with shared one thing in common. They did not just understand the system. They could explain it to others in a way that made sense. They slowed down enough to show the why behind their decisions. They adapted how they taught based on the audience. They used visuals, questions, and examples. And they cared whether the person in front of them actually understood. That kind of communication is what builds resilience. It is what keeps a team aligned during high stress. It is what separates a technical expert from a trusted leader.</p><p>Teaching also improves your own mastery. If you want to know whether you really understand something, try explaining it to a new operator or junior engineer. You will quickly discover where your assumptions are. You will catch the shortcuts in your logic. You will be forced to clarify what you usually gloss over. That loop of feedback strengthens your own thinking while helping others build theirs. That is a powerful career advantage.</p><p>When you are known as someone who can explain the complex in a simple way, your influence grows. You get pulled into earlier conversations. You get trusted with more responsibility. People seek out your opinion. And leadership sees you not just as a technician but as a communicator and decision-maker. The people who can teach well are often the ones who drive change, build trust, and scale progress.</p><p>So if you are thinking about your next step, your next role, or your next impact, do not just focus on what you can do. Focus on what you can teach. Invest in the clarity of your explanations. Take time to walk others through your process. Make documentation part of your workflow. And most importantly, pay attention to whether the people around you are getting better because of how you show up. That is what will carry your career farther than any title or tool ever could.</p><h3>Conclusion</h3><p>Too many transformation efforts stall not because people don’t care, but because the connection between strategy and execution is broken. You cannot bridge that gap from a meeting room. You have to walk the floor. You have to see what your teams see, understand how they work, and be willing to fix what doesn’t align with reality.</p><p>The best manufacturers don’t just rely on tools or titles. They build cultures where presence is normal, standards are visible, and teaching is expected. That is what makes improvement stick. Not just for one project or one person, but across teams, shifts, and years.</p><p>If you want to lead meaningful change in your facility, start with what you can control. Show up. Document what works. Teach what you know. And ask better questions every time you walk the line.</p><p><strong>Thanks for reading. If this resonated with you, share it with someone who might need to hear it. And if you haven’t already, subscribe at </strong><a href="https://framexl.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-stalled-transformations-to-stable-operations-how-floor-presence-standards-and-teaching-create-real-change"><strong><em>framexl.com</em></strong></a><strong> and visit </strong><a href="https://joltek.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-stalled-transformations-to-stable-operations-how-floor-presence-standards-and-teaching-create-real-change"><strong><em>joltek.com</em></strong></a><strong> to see how we help teams take these principles and put them into action.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7612174e38eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up]]></title>
            <link>https://vrom.medium.com/numbers-narratives-and-the-plant-floor-building-trust-in-data-from-the-ground-up-2a14a054600c?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a14a054600c</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[industrial-automation]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Fri, 30 May 2025 13:06:36 GMT</pubDate>
            <atom:updated>2025-05-30T13:06:36.851Z</atom:updated>
            <content:encoded><![CDATA[<h3>𝐌𝐚𝐤𝐞 𝐬𝐮𝐫𝐞 𝐭𝐨 𝐬𝐢𝐠𝐧 𝐮𝐩 𝐭𝐨 𝐫𝐞𝐜𝐞𝐢𝐯𝐞 𝐭𝐡𝐞 𝐰𝐞𝐞𝐤𝐥𝐲 𝐢𝐬𝐬𝐮𝐞 𝐢𝐧 𝐲𝐨𝐮𝐫 𝐦𝐚𝐢𝐥𝐛𝐨𝐱! — <a href="https://www.framexl.com/">https://www.framexl.com/</a></h3><p>Many manufacturers say they want to be data-driven. But few understand what it really takes to make data usable and trustworthy.</p><p>This issue looks at why so many data projects fall short. We start by exploring the hidden challenges behind collecting and using plant floor data. From legacy equipment to unclear ownership, the obstacles are often more practical than technical.</p><p>We then shift to the floor itself. You will learn how to spot bottlenecks, where bad metrics take root, and how label games with planned and unplanned downtime can distort entire improvement efforts.</p><p>To close, we share a career guide for those entering the world of controls. With the right focus and tools, you can make meaningful progress and build a foundation that lasts.</p><h3>The Hidden Cost of Getting Usable Data</h3><p>Collecting data in a manufacturing setting is far more complex than most people admit.</p><p>In a recent set of conversations with potential customers, a clear pattern emerged. They understood the value of data. They were excited about what it could unlock in terms of operational improvements. But they had little awareness of how much effort it takes to get that data to a state where it is actually usable. Not just collected or visualized, but structured and reliable enough to support decisions, power analytics, or drive automation.</p><p>That is the focus of this insight. I want to walk through why turning raw machine data into something that generates real return on investment remains so difficult for many manufacturers. I also want to connect this to technologies I keep discussing with clients and partners, including control systems, edge infrastructure, industrial protocols, and cloud platforms.</p><p>Most facilities are not starting from a blank slate. Instead, they have machines from multiple vendors, built during different eras, each controlled by different systems. These were often tied together by integrators with limited documentation and later maintained by in-house teams with varying skill sets. In most cases, data is already being generated and visualized through local SCADA systems. But getting beyond the SCADA screen into usable data flows is where the friction begins.</p><figure><img alt="Figure 1 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | The Real Bottlenecks in Your Data Strategy" src="https://cdn-images-1.medium.com/max/1024/0*_psHjkXEU4Wpax_-" /><figcaption>Figure 1 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | The Real Bottlenecks in Your Data Strategy</figcaption></figure><h3>Challenge 1: Obsolete Equipment</h3><p>This continues to be the most common and frustrating roadblock. Many teams will say, “We have been collecting data from these machines for years. Why is it a problem now?” The problem is not whether the data exists. The problem is in how difficult it is to access it in a meaningful and scalable way.</p><p>First, older equipment often requires costly and time-consuming workarounds. Specialized hardware and rare expertise are needed to extract signals cleanly and safely. Second, many original equipment manufacturers no longer support key components. This leaves internal teams without guidance when issues arise. Third, connecting legacy systems to modern networks creates serious cybersecurity concerns. These risks need to be addressed before any meaningful data movement can occur.</p><h3>Challenge 2: Reverse Engineering Machines</h3><p>It is rare to find two identical control systems in the field. Despite all the talk about standardization, most machines are configured differently. Different versions, different applications, and different integrators or end-users lead to dramatically different programming.</p><p>For example, one filler may be installed at a small facility in Italy packaging olive oil. Another may be deployed in Florida producing orange juice at scale. Even if both machines were built by the same manufacturer, their setup and integration will differ significantly.</p><p>Before any data can be used, each machine and line needs to be reverse engineered. This process takes time and resources. It also often lacks reusability. Incoming teams do not trust prior work and typically start from scratch. As a result, even well-documented systems are re-analyzed, line by line, adding cost and delay to every project.</p><h3>Challenge 3: Plant Architecture Gaps</h3><p>Many facilities simply lack the digital foundation needed to support robust data strategies. I regularly meet manufacturers who still operate on unmanaged switches, inconsistent naming conventions, fragmented networks, and outdated server hardware.</p><p>Even when edge devices or data loggers are installed, the overall architecture is often an afterthought. There is no clear source of truth, no namespace strategy, and no visibility into the full picture of what is connected where. These gaps make any scalable data project much more difficult and expensive to maintain.</p><h3>Challenge 4: Protocol Fragmentation</h3><p>Industrial protocols are not plug-and-play. Many facilities have a mix of Ethernet/IP, Modbus, OPC DA, Profinet, and proprietary OEM variants. These protocols do not communicate natively with each other, and the effort to translate or normalize data streams is rarely accounted for early in a project. Without protocol awareness at the planning stage, teams often discover late that data loss, mismatched timestamps, or unreliable polling are holding back their entire analytics stack. Bridging these systems requires thoughtful design, not just more hardware.</p><h3>Challenge 5: Organizational Disconnects</h3><p>The biggest barrier is often not technical. It is organizational.</p><p>Data initiatives are launched by leadership teams who expect insight. But the effort to collect, contextualize, and maintain data accuracy falls on engineering teams who are already stretched thin. These teams are often not consulted in the early stages, leading to gaps in expectations, budgeting, and implementation timelines.</p><p>I have seen projects stall for months simply because no one defined ownership for system integration or data modeling. Even worse, data is collected and stored but never used because it was not aligned with the original operational goals.</p><h3>Conclusion: Usable Data Requires More Than Infrastructure</h3><p>When people say “just get the data,” they overlook the full cost of getting it right.</p><p>Data is not useful just because it is available. It is useful when it is accurate, contextual, trustworthy, and delivered in the right format to the right people at the right time. That takes more than a few sensors or dashboards. It takes architecture. It takes standardization. And it takes collaboration across roles that rarely sit at the same table.</p><p>For manufacturers looking to modernize, this is where the real work begins. Not at the cloud. Not on the screen. But on the floor, in the systems, and in the conversations that shape how your data actually flows.</p><h3>How to Identify and Validate Bottlenecks</h3><p>One of the most important concepts on the plant floor is the bottleneck.</p><p>Bottlenecks are the machines, work cells, or processes that restrict the output of an entire production line. They are the limiting factor, the constraint that defines how fast or how effectively a process can run. If you remove or improve a bottleneck, you unlock immediate throughput gains. If you ignore it, no amount of improvement elsewhere will make a difference.</p><p>The good news is that most plant managers and engineers already know the theory. The challenge is putting it into practice.</p><p>So how do you identify and validate where the bottleneck actually is?</p><figure><img alt="Figure 2 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | The Three-Lens Bottleneck Diagnostic" src="https://cdn-images-1.medium.com/max/1024/0*gEMTymehdoejo82h" /><figcaption>Figure 2 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | The Three-Lens Bottleneck Diagnostic</figcaption></figure><h3>Step 1: Observe the Process in Motion</h3><p>There is no substitute for time spent on the floor. Stand and watch the process from raw materials to finished goods. In some environments, it is obvious. One piece of equipment causes all the backups. You see queues building up in front of it. Operators are waiting. Downstream assets are starved.</p><p>But in many facilities, the signal is buried in the noise. The constraint may move over time. It may vary between shifts or change based on product type. That is why direct observation needs to be paired with process understanding, conversations with operators, and basic data review.</p><h3>Step 2: Understand the Full Process</h3><p>You do not need to be a chemical engineer to understand a chemical process. But you do need to know how materials flow, what the control points are, and where rework, waste, or waiting tends to happen.</p><p>This takes time. Not documentation. Not just SCADA tags. Time.</p><p>Ask questions. Whiteboard it. Learn how raw materials are staged, how changeovers affect timing, and where inventory typically builds up. These conversations will give you a map of where to focus. And that map is often different from the official process flow diagram.</p><p>For a deeper breakdown of how to walk through processes and align them with system data, see:<br>🔗 <a href="https://www.joltek.com/blog/guide-tools-systems-engineering-project-management?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=numbers-narratives-and-the-plant-floor-building-trust-in-data-from-the-ground-up"><em>Guide to Manufacturing Line Assessments</em></a><br>🔗 <a href="https://www.solisplc.com/learn/introduction-to-sequential-function-chart-sfc?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=numbers-narratives-and-the-plant-floor-building-trust-in-data-from-the-ground-up"><em>Foundations of Process Control and Sequencing</em></a></p><h3>Step 3: Talk to the Operators</h3><p>If you are serious about finding bottlenecks, talk to the people who run the equipment every day.</p><p>Engineers will often focus on faults, logic, or alarms. Operators notice different things. They know when something “feels off.” They know which machine they always have to babysit. They know which tasks break rhythm and which ones flow smoothly. Their observations are grounded in repetition, not theory.</p><p>A useful analogy is driving a car. You may not know what is wrong with your vehicle, but you know when it is running poorly. It pulls to one side. It is making a weird noise. It just does not feel right. That is the same kind of insight operators bring. They cannot always explain the root cause, but they can point you to the right part of the process.</p><p>If you are building a list of process issues or root cause targets, operator feedback should always be your starting point.</p><h3>Step 4: Validate with Data</h3><p>You do not need a full-blown digital twin to analyze bottlenecks. But you do need some basic data to support or challenge your observations.</p><p>Look at runtime data, downtime logs, counts, rejects, or manual cycle entries. Even basic metrics like idle time, starved time, or fault frequency can point you to where the constraint is most likely sitting.</p><p>A well-placed sensor or counter can clarify what an hour on the floor may not. And if you have a historian or SCADA system in place, look at event sequences or tag trends over time. One of the easiest ways to confirm a bottleneck is to track how long material waits at a specific station versus others.</p><p>For examples of how to structure plant data for these kinds of insights, check out:<br>🔗 <a href="https://www.solisplc.com/learn/designing-smarter-plc-data-models-from-arrays-to-udts?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=numbers-narratives-and-the-plant-floor-building-trust-in-data-from-the-ground-up"><em>Designing Smarter PLC Data Models</em></a><br>🔗 <a href="https://www.joltek.com/blog/plc-data-structures-scada-mes-integration?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=numbers-narratives-and-the-plant-floor-building-trust-in-data-from-the-ground-up"><em>SCADA and MES Integration Fundamentals</em></a></p><h3>Planned Downtime vs Unplanned Downtime</h3><p>I remember this story as if it happened yesterday.</p><p>At one of the plants I worked with, I noticed a senior manager editing downtime events in the MES system. Curious, I asked him what he was doing. Without hesitation, he told me he was relabeling events. Specifically, he was changing unplanned downtime into planned downtime.</p><p>This immediately raised a red flag.</p><p>In most manufacturing environments, performance metrics drive everything. They influence bonuses, reviews, and investment decisions. Plant-level KPIs are not just numbers. They are loaded with consequences. So I was surprised to see a senior leader manually adjusting production data that had been automatically collected by the system.</p><p>His reasoning? Downtime labeled as “planned” does not impact OEE, while “unplanned” does. That was enough to justify the change.</p><figure><img alt="Figure 3 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | Planned vs Unplanned Downtime: The KPI That Breaks Itself" src="https://cdn-images-1.medium.com/max/1024/0*YkLI6DB5DpYuDO99" /><figcaption>Figure 3 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | Planned vs Unplanned Downtime: The KPI That Breaks Itself</figcaption></figure><h3>Why This Matters</h3><p>This kind of behavior is not rare. In fact, according to a report by LNS Research, fewer than half of manufacturers consistently define and categorize downtime events across teams and systems. This lack of structure causes confusion, manipulation, and missed opportunities for real improvement.</p><p>Unplanned downtime reflects failures and surprises. These are the moments where something went wrong and operations stopped. Planned downtime, on the other hand, includes maintenance, cleanups, or changeovers that were known and scheduled. The two categories should be fundamentally different.</p><p>When those definitions are unclear or left to individual judgment, the integrity of the data collapses. More importantly, the improvement process stalls. Instead of using the data to drive action, teams spend time trying to control the narrative.</p><h3>What Actually Happens on the Floor</h3><p>In many facilities, what counts as planned or unplanned shifts from team to team. One shift might log a water leak as unplanned. The next shift, under pressure to hit targets, might recategorize it as a “planned inspection.” A scheduled lunch break might be extended but not tracked. A machine jam might be blamed on a supplier issue, even though it should have triggered a maintenance response.</p><p>This inconsistency builds over time. Eventually, no one really knows what the numbers mean. As a result, leadership may launch the wrong improvement projects, overlook real reliability issues, or mistakenly believe performance is improving.</p><p>In some plants, I have seen entire lines get praised for hitting OEE targets, while everyone on the floor knows that dozens of unplanned stops were relabeled to protect the dashboard.</p><h3>What Good Looks Like</h3><p>Strong operations teams take this seriously. They define their categories clearly and enforce them consistently. A few guiding principles help:</p><ul><li><strong>Create Standard Definitions</strong><br>Everyone in the plant should know what qualifies as planned downtime and what does not. These definitions should be visible, documented, and part of onboarding and daily routines.</li><li><strong>Build the Definitions into the System</strong><br>Use MES or historian platforms to automate tagging based on work orders, scheduled events, or shift change times. Eliminate ambiguity where possible.</li><li><strong>Lock Categories Where It Makes Sense</strong><br>Limit who can override downtime categories. If adjustments are needed, route them through a review process, not manual edits.</li><li><strong>Audit and Review Monthly</strong><br>Compare logs across shifts. Look for patterns. If downtime definitions are drifting, correct them quickly and use the opportunity to train or clarify.</li></ul><h3>A Final Thought</h3><p>Metrics are powerful only when they are trusted. Once teams start managing the numbers instead of managing the problems, the entire improvement culture erodes.</p><p>If your facility reports high OEE but no one believes the data, you have a deeper issue than equipment performance. Start by aligning on what your numbers actually mean. The difference between planned and unplanned downtime is not just about categories. It is about culture, accountability, and whether your data tells the truth.</p><h3>How to Break Into Controls Engineering</h3><p>I keep seeing the same question pop up on Reddit and other forums.</p><p><strong>How do I get into controls? How do I learn PLCs, HMIs, SCADA, or even get a job in automation at all?</strong></p><p>Let me start with a brief story.</p><p>When I graduated with a degree in electrical engineering, I had never even heard of manufacturing control systems. My coursework focused on power systems, renewable energy, and basic control theory using MATLAB. I had taken classes in drives and power electronics, but I had never touched a PLC or seen an HMI screen. The term SCADA might as well have been a typo.</p><p>Still, I applied everywhere I could. I managed to get through the interview process at Procter and Gamble and landed my first job in controls. No prior automation experience. No specific training in manufacturing. Just enough foundational understanding to show I could learn quickly and add value.</p><p>That story is not typical. Most companies are not Procter and Gamble. They do not run structured programs for new grads. They do not have months to get someone up to speed. They want candidates who already know the basics of control systems and can contribute early.</p><p>So how do you set yourself apart? Here’s what I would do today if I were trying to break into this field. You can tackle these in parallel, depending on your availability and learning style.</p><figure><img alt="Figure 4 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | Break Into Controls Engineering in 4 Steps" src="https://cdn-images-1.medium.com/max/1024/0*AziwdVgl3tbtHfoU" /><figcaption>Figure 4 — Numbers, Narratives, and the Plant Floor: Building Trust in Data from the Ground Up | Break Into Controls Engineering in 4 Steps</figcaption></figure><h3>Learn Control System Fundamentals</h3><p>Control systems are not complicated. Most applications on the plant floor involve simple digital logic. Inputs turn on outputs. Sensors trigger actuators. That is the majority of what happens behind the scenes.</p><p>But that does not mean you can ignore the rest. You should understand how a PLC works, what scan time is, how logic is structured, and how safety circuits tie into the overall design. You should be able to sketch out how a basic machine runs, from pushbutton to motor starter.</p><h3>Pick a Platform and Go Deep</h3><p>This is the advice I wish someone had given me earlier. Choose a platform you see often in job postings and learn it thoroughly. Whether it is Allen-Bradley, Siemens, or something else, your goal is to get comfortable with that ecosystem. Understand the hardware lineup. Learn the software interface. Know the basics of troubleshooting, wiring, and communication.</p><p>It is tempting to play with open-source PLC simulators or Arduino projects. Those can be fun and helpful for concept development. But hiring managers and integrators are looking for experience on the tools they actually use in production. Learn what makes those platforms different and how they are typically applied.</p><p>If the cost of hardware or software is an issue, do not give up. Reach out to local distributors. Explain your situation. Many are willing to loan out equipment or give you trial access to software. That one conversation may also open the door to your first internship or freelance project.</p><h3>Learn the Industry Context</h3><p>Controls engineering does not exist in a vacuum. It always supports a process. That process can be automotive assembly, food packaging, chemical blending, or something entirely different.</p><p>You do not need to become an expert in every industry. But you should become curious.</p><p>If you want to work in automotive, learn about takt time, just-in-time production, and the role of robotics. If you want to work in food and beverage, learn about washdown requirements, packaging lines, and batch processing. If you are applying to a specific company, understand their core products, production volume, and common bottlenecks.</p><p>This kind of contextual knowledge helps you speak their language. It shows that you are not just a tech enthusiast, but someone who wants to solve real manufacturing problems.</p><h3>Final Thought</h3><p>Breaking into controls engineering is not easy. But it is absolutely doable if you take a structured approach. Learn the fundamentals. Choose one platform and master it. Ask questions. Get your hands on real tools. Show genuine interest in the industries you want to support. No one expects you to know everything. But they do expect that you have put in the effort to understand the basics and build a foundation.</p><p>And when you do land that first role, remember that your career is not built on one ladder. It is built on momentum. Take the next step, then the next. With time, your questions will change. Your confidence will grow. And the door you opened with one project will turn into a long, rewarding career.</p><h3>Conclusion</h3><p>This issue was about more than data. It was about truth. We looked at why so many digital initiatives fail to deliver value. It is not because teams lack tools. It is because the reality of plant operations is often hidden behind inconsistent labels, outdated systems, and well-intentioned edits that shift the story without solving the problem.</p><p>Here are the takeaways to keep in mind:</p><ul><li><strong>Data is not useful unless it is trustworthy.</strong> That means clean inputs, consistent definitions, and aligned teams.</li><li><strong>You cannot fix what you do not understand.</strong> Spend time on the floor. Watch the flow. Talk to operators. Then check the numbers.</li><li><strong>Metrics are only as strong as the culture behind them.</strong> When teams adjust data to protect KPIs, improvement stalls.</li><li><strong>Career growth in controls starts with focused learning.</strong> Pick one platform, build something real, and connect it to the process.</li></ul><p>Whether you are building a system, running a line, or just getting started, progress begins with clear signals and honest feedback.</p><p>See you in the next issue.</p><h4>Get in Touch</h4><ul><li><a href="https://www.joltek.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=numbers-narratives-and-the-plant-floor-building-trust-in-data-from-the-ground-up"><em>Joltek</em></a></li><li><a href="https://www.linkedin.com/in/vladromanov/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=numbers-narratives-and-the-plant-floor-building-trust-in-data-from-the-ground-up"><em>Vladimir Romanov</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a14a054600c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Disciplined Factory: Tools, Thinking, and Habits That Scale]]></title>
            <link>https://vrom.medium.com/the-disciplined-factory-tools-thinking-and-habits-that-scale-8129537993eb?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8129537993eb</guid>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Wed, 21 May 2025 01:35:17 GMT</pubDate>
            <atom:updated>2025-05-21T01:35:17.624Z</atom:updated>
            <content:encoded><![CDATA[<p>Read &amp; Subscribe to the full publication — <a href="https://www.framexl.com/">FRAME | Foundation for Reliability, Automation, Manufacturing &amp; Excellence</a></p><p>What separates a stable manufacturing operation from one that constantly reacts to problems? It is not just the technology. It is the discipline behind how that technology is understood, maintained, and improved. The best teams I have worked with do more than respond quickly. They prepare deeply. They document clearly. They build systems that prevent problems from returning.</p><p>In this issue of FRAME, we examine what that discipline looks like in real-world manufacturing.</p><p>We begin with a realistic look at artificial intelligence and where it is already delivering value on the plant floor. From vision systems to robotic cell design and data analytics, AI is moving from concept to tool, and the shift is worth understanding. We then shift to the fundamentals of troubleshooting. Not the heroic kind that happens after a breakdown, but the kind that starts before anything fails. Preparedness, access to tools and documentation, and building the right relationships all play a part in recovery speed. We continue with a clear and practical explanation of Six Sigma. Too often misunderstood, Six Sigma remains one of the most powerful frameworks for reducing variation and improving quality when applied with intent and clarity.</p><p>Finally, we explore a mental model that separates good engineers from great ones: the ability to see the system. The professionals who consistently solve the right problems are not just those with deep technical knowledge. They are the ones who step back, ask better questions, and connect local symptoms to systemic causes.</p><h3>A Realistic Take on AI in Manufacturing</h3><p>Artificial Intelligence is no longer theoretical in manufacturing. It has quietly moved from abstract promise to practical deployment. While the early hype cycles produced more noise than results, we are now seeing credible tools emerge that solve real problems.</p><p>I have been skeptical of AI in the past. Early models struggled to generate coherent images or text, and many of the so-called solutions lacked any grounding in operational reality. But over time, the progress has become difficult to ignore. Last week at Automate, one of the largest industrial automation trade shows, it became clear that AI is beginning to play a legitimate role in our ecosystem. Nearly every major OEM, vendor, and integrator had something to show involving machine learning, computer vision, or generative tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wZ8Qtl9k5N5pcfMf" /><figcaption>Figure 1 — The Disciplined Factory: Tools, Thinking, and Habits That Scale | AI in Manufacturing: Where It’s Actually Working</figcaption></figure><p>Here is where the progress is most evident:</p><h3>Machine Vision is More Capable and Easier to Deploy</h3><p>Vision systems used to require hours of fine-tuning. I remember working through Cognex spreadsheets and struggling with EasyBuilder to get a reliable result. Today, AI-enhanced vision systems are far more adaptive. The underlying models can learn and generalize across a wider set of use cases, significantly reducing configuration time. This unlocks broader adoption in quality control, defect detection, and sorting.</p><h3>AI is Accelerating Robotic Workcell Design</h3><p>Vendors are releasing design tools that use AI to suggest robot cell layouts, select grippers, and optimize motion paths. These capabilities reduce engineering time and improve first-pass success rates. For high-mix or short-run production environments, this can provide a meaningful edge in deployment speed and flexibility.</p><h3>Copilots are Emerging for Industrial Use Cases</h3><p>While AI copilots are widely used by software developers, we are starting to see early-stage tools designed for manufacturing workflows. I spoke with several companies that are testing copilots for troubleshooting, documentation access, and technician guidance. These are not mature systems yet, but the intent and investment are clearly there.</p><h3>Plant Data is Finally Being Interpreted, Not Just Collected</h3><p>Many manufacturers have invested in collecting and contextualizing data. The next challenge is drawing conclusions from that data. A new wave of tools applies machine learning to structured plant information, identifying trends, detecting anomalies, and producing actionable insights. Several platforms I reviewed at Automate are doing this with surprising precision.</p><p>Like many of you, I am now taking a deeper look at how AI can be applied responsibly and effectively in industrial environments. I am not interested in vague promises or abstract visions. I want to understand the foundations so I can separate signal from noise.</p><p>If you are in manufacturing and still treating AI as a distant trend, I would encourage you to reconsider. The technology is not going to replace your operations, but it will reshape how certain decisions are made, how systems are built, and how work gets done.</p><p>Here are a few resources I am currently studying to deepen my understanding:</p><ul><li><a href="https://amzn.to/43Az9Bv?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=the-disciplined-factory-tools-thinking-and-habits-that-scale"><em>AI Engineering: Building Applications with Foundation Models</em></a> by Chip Huyen</li><li><a href="https://amzn.to/4k7d9nO?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=the-disciplined-factory-tools-thinking-and-habits-that-scale"><em>Build a Large Language Model (From Scratch)</em></a> by Sebastian Raschka</li><li><a href="https://www.udemy.com/course/aws-ai-practitioner-certified?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=the-disciplined-factory-tools-thinking-and-habits-that-scale"><em>Ultimate AWS Certified AI Practitioner AIF-C01</em></a> by Stephane Maarek</li></ul><p>As always, I am open to conversations with others who are exploring this space. We need more grounded voices in manufacturing to guide these tools toward real outcomes.</p><h3>How to Actually Get Better at Troubleshooting</h3><p>Troubleshooting is one of the most talked-about yet least taught skills on the plant floor. Everyone agrees it is important, but very few know how to develop it consistently across a team. You can only learn so much from theory. At some point, real learning requires standing in front of equipment, under pressure, and working through a problem. That said, there are steps that can significantly improve your ability to troubleshoot. These steps lead to faster response times, lower mean time to repair (MTTR), and better overall performance.</p><h3>What Troubleshooting Really Depends On</h3><p>Troubleshooting is not just a reaction to failure. It is the process of identifying the root cause, but what often goes unnoticed is how much of that process happens before anything breaks. Most teams lose time not because the failure is complex, but because they are unprepared when it happens.</p><p>Consider these questions:</p><ul><li>Do you have complete and current documentation for the systems you support?</li><li>Do you know where the latest versions of the software and backups are stored?</li><li>Do you have access to the right hardware tools and software licenses?</li><li>Do you understand how the equipment is laid out and how the system is designed?</li><li>Do you have a clear idea of who to contact when things go wrong?</li></ul><p>Each of these questions directly affects how quickly and effectively you can respond to a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6lrcnJv2U2Vf3xoX" /><figcaption>Figure 2 — The Disciplined Factory: Tools, Thinking, and Habits That Scale | The Troubleshooting Readiness Checklist</figcaption></figure><p>Case Example: A New Case Packer on the Floor</p><p>Imagine your facility just installed a new case packing machine. The commissioning is done, and the asset is now in the hands of operations. What should you do now to prepare for the first time it fails?</p><h3>Documentation is Non-Negotiable</h3><p>The first thing I ask for during any troubleshooting engagement is documentation. This includes electrical drawings, panel layouts, mechanical schematics, and network diagrams. Without this information, even basic diagnostics take longer than they should. If documentation is not available, someone needs to take responsibility for building it. No one should be supporting equipment blind.</p><h3>Hardware, Software, and License Planning</h3><p>Downtime is often extended because someone is missing a cable, the right software version, or a working license. Each critical system in your facility should have a clearly documented list of what is needed to go online, including the type of controller, the software package, the version, and who owns the license.</p><p>I have seen factories lose multiple shifts of production because they discovered mid-failure that the only licensed software was installed on a laptop that was no longer in the building. This kind of delay is avoidable.</p><p>Create a shared resource that lists the software and tools needed for each asset in the facility. Make it easy to update and easy to access.</p><h3>Building Relationships That Matter</h3><p>As a young engineer, I believed I needed to know everything myself. Over time, I learned that being resourceful is more important than being all-knowing.</p><p>When equipment fails, the people who built it usually know more than those operating it. They have seen rare faults, edge cases, and integration issues that never made it into the manuals. In many cases, solving the issue means picking up the phone and calling someone who has seen it before.</p><p>Building these relationships before you need them makes all the difference. That might include staying in contact with the OEM, attending trade shows to meet product experts, or having a trusted systems integrator on call. In every facility I have worked with, the fastest troubleshooters are the ones who know who to call.</p><h3>Pre-Troubleshooting is Real Work</h3><p>Troubleshooting begins long before the problem. The most effective teams prepare in advance. They know their systems, keep documentation organized, and have a support network they can rely on.</p><p>If you want to improve the way your team handles downtime, start with the basics:</p><ul><li>Audit your documentation</li><li>Review your software and licensing situation</li><li>Identify the key people who can help you when a failure occurs</li><li>Practice walking through systems before they go down</li></ul><p>The real work happens before the failure. If you ignore these steps, troubleshooting becomes guesswork. If you take them seriously, your facility becomes faster, more capable, and less vulnerable.</p><h3>What Six Sigma Really Means in Manufacturing</h3><p>Six Sigma is a disciplined, data-driven methodology for reducing variation, eliminating defects, and improving the repeatability of complex processes. It was originally developed at Motorola in the 1980s and later adopted at scale by companies like General Electric and Honeywell. Today, its tools and philosophy are embedded in thousands of manufacturing organizations around the world.</p><p>Yet despite its widespread adoption, Six Sigma is often misunderstood. In my experience, professionals who have not studied statistics rarely grasp what Six Sigma actually means or how to apply it in the context of production lines, quality checks, or troubleshooting efforts.</p><p>This section is not a certification course. It is a practical explanation designed to help you speak confidently about Six Sigma with your colleagues, collaborate more effectively with engineering teams, and think more critically when making data-driven decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*58Lc-sbkHel2c8p-" /><figcaption>Figure 3 — The Disciplined Factory: Tools, Thinking, and Habits That Scale | What Six Sigma Really Means</figcaption></figure><p>Foundations of Six Sigma</p><p>Imagine standing on a production floor where your team is producing 1,000 popsicles every minute. Your job is to make sure that every one of those popsicles meets a strict quality standard based on sugar content. But there is a challenge: the test for sugar content is destructive. Once you sample a popsicle for testing, you cannot put it back into inventory.</p><p>This leaves you with two competing constraints. First, you want to minimize the number of units you discard as a result of testing. Second, you want to minimize the number of defective products that reach your customers. Your job is to balance these risks intelligently using a structured approach to sampling and decision-making.</p><p>At this point, the most important question to ask your leadership is: <strong>how many defects are we willing to accept?</strong> If the answer is “as few as possible,” then the standard you are aligning with is likely Six Sigma.</p><h3>What Six Sigma Means Statistically</h3><p>The term Six Sigma comes from statistics and is based on the behavior of <strong>normal distributions</strong>, also known as bell curves. In any stable process, the majority of output will cluster around a central average, or mean. Sigma refers to the standard deviation, which is a measure of how much variation exists in that process.</p><p>Here is how coverage works in a typical normal distribution:</p><ul><li>One Sigma from the mean captures approximately 68.2 percent of all output</li><li>Two Sigma captures about 95.4 percent</li><li>Three Sigma includes roughly 99.73 percent</li><li>Six Sigma captures 99.99966 percent</li></ul><p>A Six Sigma process is so stable and consistent that the probability of a defect occurring is only <strong>3.4 per one million opportunities</strong>. This assumes a small, long-term drift in the process mean, which is built into the Six Sigma model.</p><p>In practical terms, Six Sigma is not a guarantee of perfection. Instead, it is a quality benchmark that says: we have reduced process variability to the point where defects are extremely rare and statistically predictable.</p><h3>Why This Matters on the Plant Floor</h3><p>Six Sigma thinking is especially useful in high-volume production environments where:</p><ul><li>Defects are expensive or dangerous</li><li>Testing is destructive, slow, or difficult</li><li>Minor deviations can cascade into large quality issues</li><li>Continuous improvement requires real structure, not just experience or guesswork</li></ul><p>Using Six Sigma tools and principles allows your team to make smarter decisions about inspection frequencies, control limits, sampling strategies, and corrective actions. It supports better conversations between operators, quality teams, engineers, and managers.</p><p>It also encourages a shift away from reactive thinking toward preventive control. Instead of asking “what broke,” Six Sigma pushes you to ask “why did the variation occur, and how do we prevent it in the future?”</p><h3>Good Engineers Fix Problems. Great Engineers See the System.</h3><p>One of the most powerful shifts I have observed in manufacturing professionals as they grow is this:</p><ul><li>They stop focusing only on isolated tasks, machines, or issues.</li><li>They start seeing how the entire system operates.</li></ul><p>This shift is not about experience alone. It is about learning to think <strong>across time, across departments, and across causes</strong>. It is the difference between someone who reacts well and someone who builds processes that eliminate the need for reaction in the first place. This is what separates good from great. And in many organizations, it is what separates those who remain stuck in daily firefighting from those who get trusted with transformation initiatives.</p><h3>The Limits of Local Thinking</h3><p>In most manufacturing environments, the pressure to solve problems quickly is high. When a machine goes down or a KPI slips, teams are expected to respond fast. That usually means solving the most visible issue.</p><ul><li>A sensor is not reading correctly, so we replace it.</li><li>A label is misaligned, so we adjust the printer.</li><li>A pallet is jammed, so we re-teach the robot position.</li></ul><p>None of these are wrong. But all of them may be incomplete. Local thinking optimizes the symptom. Systems thinking identifies and redesigns the pattern. Let me give you a few real examples from the field.</p><h3>Example 1: The Filler That Was Not the Problem</h3><p>At a beverage facility, the team kept missing their production targets. The assumption was that the filler was the bottleneck. Technicians requested better nozzles, faster controls, and changes to the cleaning cycle.</p><p>But when the process was mapped, it turned out the problem was upstream. Ingredient availability was inconsistent. The batching system was releasing the wrong flavors out of sequence, which delayed changeovers and starved the filler for extended periods.</p><p>No amount of local optimization at the filler could overcome the variability in the supply schedule. The root of the problem was in planning and materials coordination.</p><p>The team that saw this not only fixed the issue, but also redesigned how batch instructions were released from ERP to the floor.</p><h3>Example 2: The Alarm Everyone Ignored</h3><p>At another plant, operators regularly ignored an HMI alarm that warned of high temperature in a hydraulic system. When asked why, the response was simple: “It always goes off, and nothing happens.”</p><p>The alarm had been hardcoded years ago, and no one had revisited the logic. Over time, the system drifted. A sensor degraded, the control loop lagged, and the temperature occasionally did creep too high, leading to a major pump failure.</p><p>But because the alarm became noise, no one connected the dots.</p><p>A true systems thinker would have asked:<br>Why does this alarm keep triggering?<br>What was the original design intent?<br>Has the process or control system changed?</p><p>They would not just fix the hardware. They would revalidate the purpose of the system, check the alarm thresholds, and update the logic to reflect the actual risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fAsQ3Wq9l26ez2SC" /><figcaption>Figure 4 — The Disciplined Factory: Tools, Thinking, and Habits That Scale | From Reaction to Redesign: What Systems Thinkers See</figcaption></figure><p>What Systems Thinkers Do Differently</p><p>Systems thinking is not just about being clever. It is about developing structured awareness. It is a deliberate effort to step back and ask bigger questions:</p><ul><li>Where is the true constraint in this process?</li><li>How do inputs, workflows, and decisions interact over time?</li><li>Which performance metrics are competing with each other?</li><li>What incentives or assumptions are embedded in this setup?</li></ul><p>Great engineers, operators, and managers train themselves to notice misalignments between departments. They see how quality metrics might compete with throughput. They understand how procurement choices affect downtime. They recognize that a new automation project might fail not because of the code, but because no one aligned on changeover protocols.</p><p>This way of thinking is not abstract. It is tactical.</p><h3>How to Build This Skill</h3><p>You do not need a systems engineering degree to think this way. Here are a few habits that develop systems awareness:</p><ol><li><strong>Start asking “Why is this happening here and now?”</strong><br>Not just “what failed,” but “why now, why this asset, why this pattern?”</li><li><strong>Use process mapping regularly</strong><br>Even simple diagrams of material flow, information handoffs, or decision points can reveal inefficiencies no one is talking about.</li><li><strong>Involve people across silos</strong><br>A maintenance issue might be rooted in procurement delays. A production miss might be due to a change in forecast logic. Invite other functions to the discussion.</li><li><strong>Treat KPIs as interconnected, not isolated</strong><br>If OEE goes up but quality complaints spike, something else is broken. Good metrics balance trade-offs.</li><li><strong>Look for recurring failure themes</strong><br>Not just repeated downtime on one machine, but patterns that show up in different forms across the operation.</li></ol><h3>Why This Matters for Your Career</h3><p>The professionals who rise in manufacturing are not just technical experts. They are the ones who can think across departments, across time horizons, and across goals.</p><ul><li>They connect frontline issues to executive strategy.</li><li>They see how capital investments ripple into training, maintenance, and change management.</li><li>They can translate from machine behavior to system behavior.</li><li>And most importantly, they are trusted to solve problems that matter.</li></ul><p>If you want to accelerate your growth in manufacturing, start by asking better questions. Step back. Zoom out. And train yourself to see the system, not just the symptom.</p><p>This is not just how you solve problems. This is how you become someone others trust to solve the right ones.</p><h3>Conclusion</h3><p>Excellence in manufacturing does not come from a single innovation. It is built through consistent habits, clear thinking, and disciplined execution. Whether you are adopting AI, improving troubleshooting processes, applying Six Sigma, or learning to see the full system, the most impactful changes are often the result of small, intentional steps taken over time.</p><p>This issue is a reminder that modern tools are only as effective as the structure behind them. Documentation, preparation, collaboration, and the ability to ask better questions are what drive meaningful and lasting improvements.</p><p>As always, I encourage you to reflect on how these ideas apply to your work. Share them with your team. Start a conversation. The real value of this newsletter comes from how these insights are used, challenged, and turned into action on the floor.</p><p>If you have thoughts, questions, or examples of your own, I would love to hear them. Let’s keep learning and building together.</p><h3>Get in Touch with Us</h3><ul><li><a href="https://www.linkedin.com/in/vladromanov/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=the-disciplined-factory-tools-thinking-and-habits-that-scale"><em>Vladimir Romanov</em></a></li><li><a href="https://www.joltek.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=the-disciplined-factory-tools-thinking-and-habits-that-scale"><em>Joltek</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8129537993eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Quality Metrics to Electrical Panels: How to Read the Hidden Signals in Your Plant]]></title>
            <link>https://vrom.medium.com/from-quality-metrics-to-electrical-panels-how-to-read-the-hidden-signals-in-your-plant-8c5d3eba5fc9?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c5d3eba5fc9</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Wed, 21 May 2025 01:31:40 GMT</pubDate>
            <atom:updated>2025-05-21T01:31:40.805Z</atom:updated>
            <content:encoded><![CDATA[<p>Read &amp; Subscribe to the full publication — <a href="https://www.framexl.com/">FRAME | Foundation for Reliability, Automation, Manufacturing &amp; Excellence</a></p><p>Welcome to Issue #3 of <em>FRAME</em>. This week, we focus on a simple but powerful idea: the way people show up determines what improves.</p><p>In manufacturing, performance is not just about systems or strategy. It is about how leaders act, how teams work, and how clearly the operation reflects its priorities. Whether it is a plant manager showing up on the weekend, the condition of your electrical panels, or your ability to understand quality metrics, each example reveals the same truth.</p><p>Improvement starts with presence, awareness, and a willingness to act.</p><h3>Modern Manufacturing Demands Engaged Technical Leadership</h3><p>Last week, I had a series of conversations with manufacturing executives. In one of them, we veered into a discussion about leadership in today’s factories. Not systems. Not tools. But the people actually driving the work forward.</p><figure><img alt="Figure 1 — From Quality Metrics to Electrical Panels | 5 Behaviors of Engaged Technical Leaders" src="https://cdn-images-1.medium.com/max/1024/0*KtL10DQx9jQARaos" /><figcaption>Figure 1 — From Quality Metrics to Electrical Panels | 5 Behaviors of Engaged Technical Leaders</figcaption></figure><p>One story always comes to mind.</p><p>In 2015, while I was working at Procter &amp; Gamble, I was responsible for engineering projects that involved bringing production lines from Italy and Japan to a site in the United States. As is often the case, the startup phase was rough. Sensors weren’t configured, equipment wasn’t aligned, product kept spilling onto the floor.</p><p>It was intense.</p><p>Several weekends in a row, we were onsite for long hours, trying to get machines running. I still remember the plant manager showing up. He wasn’t there to criticize or micromanage. He came to understand what we were dealing with. And more than that, he picked up a broom and helped clean up product waste.</p><p>This was someone four levels above me in the hierarchy: Plant Manager, Engineering Manager, Team Lead, then me.</p><p>He didn’t send a message through management. He showed up himself.</p><p>That stuck with me. In high-pressure environments, people don’t need more noise from the top. They need presence. They need engagement.</p><p>Now, contrast that with some of the conversations I’ve had more recently. I was told directly after one meeting that key directors and VPs on a digital initiative were already job hunting. They were not focused on their site’s future. No curiosity. No commitment. No real chance of success.</p><p>You can hire external consultants. You can invest in data infrastructure. But if your leadership is disengaged, none of it will matter.</p><p>Digital transformation does not begin with technology. It begins with leadership that is involved, committed, and willing to get close to the work.</p><p>Here’s the question:<br><strong>Is your leadership fully engaged in building a better operation? Or are they already planning their next move?</strong></p><h3>Your Electrical Panels Reflect the Culture of Your Plant</h3><p>One of the most reliable ways I’ve found to understand the state of a manufacturing operation is to open an electrical panel.</p><p>This is a habit I developed early in my career. Whenever I was brought on-site to help with a controls retrofit, automation upgrade, or facility assessment, I would take a moment during the tour to stop by a panel and see what was inside. Not because I was curious about that specific system, but because of what it signaled about the organization.</p><p>Over time, I began to notice a consistent pattern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uBx3j7CMn1V0Ar0C" /><figcaption>Figure 2 — From Quality Metrics to Electrical Panels | Your Electrical Panels Reflect Your Culture</figcaption></figure><p>In some plants, the inside of a panel looks cleaner than the break room. Wiring is labeled and routed with care. There is no dust, no loose components, no debris. Spare relays and parts are properly stored. There is a clear sense that someone owns this piece of equipment and takes pride in how it’s maintained.</p><p>In other plants, the picture is different. I have opened panels filled with loose wires, pulled cable trays, missing covers, or an inch of dust thick enough to leave a fingerprint. In one extreme case, I found 480V lines partially submerged in standing water that had accumulated in the base of the enclosure.</p><p>What matters is not just the visual condition. What matters is what it reveals about how the site operates.</p><p>A clean panel often reflects a proactive, disciplined, and structured team. A messy panel tends to reflect firefighting, understaffing, and an absence of preventive systems. Over hundreds of site visits, this correlation has held true. What’s hidden behind a closed door often reveals more than what’s displayed on a KPI dashboard.</p><p>This is not about judgment. I have walked into many facilities where the team knows things are not where they should be. The real question is whether they are working to change that. Are they trying to build systems that support reliability? Are they planning upgrades? Are they investing in skills?</p><p>In many cases, the answer is no. And it is not for lack of desire. It is because the team is underwater.</p><p>According to the 2024 Deloitte and Manufacturing Institute report, over 75 percent of manufacturers report having difficulty filling critical roles in maintenance and engineering. Many plants are running legacy systems from five or more vendors, patched together over decades. Their best technicians are nearing retirement. Their new hires are hard to retain. And they simply do not have the bandwidth to plan and execute system-wide improvements.</p><p>What results is a vicious cycle. Panels stay in poor condition. Platform complexity increases. More time is spent reacting, and less time is available for redesign or prevention.</p><p>This is why the panel matters. Not as an isolated issue, but as a visible proxy for the hidden strain your operations may be under.</p><p>If your team is constantly in crisis mode, something is going to give. It may not be today, but it will happen. The smarter approach is to surface these signals early, build a roadmap, and start small but steady improvements.</p><p>Take a walk this week. Open one panel. Ask yourself what it says about your current culture. Then ask what it could look like six months from now, if you made it a priority.</p><p>Improvement starts behind the door.</p><h3>Metrics that Matter , Understanding Quality on the Floor</h3><p>I have to admit something. Early in my career, I didn’t enjoy working with quality departments.</p><p>They always felt like the ones slowing things down. Shutting off production. Flagging issues right as things were starting to run smoothly. In theory, they were supposed to be partners to operations and engineering. In practice, it often felt like we were working against each other.</p><p>That changed.</p><p>Once I started to actually understand the metrics coming from quality inspections, I realized we were chasing the same goals. The problem wasn’t the data. The problem was the disconnect in how we used it.</p><p>In most manufacturing environments today, a lot of quality inspections are still done manually. You will often see dedicated labs in food and beverage facilities, where technicians run pH checks, moisture tests, or other product validations. These tests are essential. They help ensure that what gets shipped is safe for consumption.</p><p>In other verticals like automotive or electronics, the purpose of quality inspections can vary. Sometimes the goal is to confirm that a part meets a customer specification. Other times, it is to make sure a downstream process won’t be disrupted by a small variation upstream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jx4d2ZKVzCD8XBa7" /><figcaption>Figure 3 — From Quality Metrics to Electrical Panels | Understanding Quality: From Tolerance to Action</figcaption></figure><p>Regardless of the industry, every quality inspection produces a data point. And every data point tells a story. The question is whether your team knows how to read it.</p><p>Let’s take a simple example. Say you are drilling five holes in an aluminum part. A vision system counts the holes. If it detects fewer or more than five, it rejects the part. This is a basic pass-fail check based on an integer count.</p><p>But most real-world inspections involve continuous measurements. Nothing produced is ever perfect. There will always be some level of variation. The key is understanding how much variation is acceptable.</p><p>For example, if the spec calls for a part that is 10.00 centimeters long, does a part measuring 10.01 centimeters still pass? That depends entirely on your tolerance range. If the acceptable window is plus or minus 1 millimeter, then yes, it passes. If the limit is plus or minus 0.1 millimeter, then it fails.</p><p>This is what quality metrics actually tell you. Not just whether a product passed or failed, but how close your process is running to its limits. Is it centered? Is it drifting? Are the failures random, or is there a trend forming?</p><p>In my experience, many engineers and managers struggle to answer these questions. They see rising reject rates but can’t explain why. They don’t know if a recent spike is just noise or a real sign of process instability. They miss opportunities to make improvements because they don’t fully understand what the data is telling them.</p><p>This is where the real value lies.</p><p>By learning what each metric means, you can begin to spot patterns. You can trace defects back to specific machines, materials, or shift teams. You can run simple experiments and track whether a change actually improves the outcome. And most importantly, you can reduce the amount of waste that piles up before anyone notices something is wrong.</p><p>Here is my advice to every manufacturing leader:</p><ul><li>Take time to understand your critical quality metrics.</li><li>Know what the tolerances are, and what happens when they are exceeded.</li><li>Learn how your process variables influence those outcomes.</li><li>Review the trends, not just yesterday’s results.</li><li>Build a response plan that kicks in before things reach the red zone.</li></ul><p>Quality data is not a burden. It is a signal. Learn to listen, and it becomes one of your most valuable tools.</p><h3>Career Shift , Document What You Know to Unlock Opportunities</h3><p>I have worked in some of the most rigorously documented environments, like medical device manufacturing at Procter &amp; Gamble, and in some of the least documented ones, such as a fast-moving software startup.</p><p>What I have learned is this: no one enjoys writing documentation. It rarely feels urgent. It often gets dismissed as low-value. People would much rather build, fix, or implement than write about it.</p><p>But the ability to document your work is one of the most powerful habits you can build in your career.</p><p>In fact, the people who consistently get promoted are often the ones who find a way to make themselves replaceable. That does not mean they are no longer needed. It means they create systems, train others, and build repeatable processes that allow the organization to grow. When they are promoted, they leave behind something that others can follow.</p><p>Think about it from a leadership perspective. Would you rather keep someone in a role indefinitely because no one else knows how to do the job, or would you promote the person who built a process and trained a replacement while continuing to solve more complex problems?</p><p>This sounds simple. But in practice, asking your manager for more time to “write documentation” will rarely go well.</p><p>A better approach is to start with your own time. Where are you spending the most energy each week? Which tasks keep showing up on your calendar? Where are you answering the same questions again and again?</p><p>That is where documentation should begin.</p><p>Let me share a real example.</p><p>An engineer I worked with spent about 30 percent of his time doing CAD work. It was not his core skill, and it pulled him away from other high-value responsibilities. His hourly cost to the business was high, and he was not the most efficient at drafting because of how many other tasks he had to manage.</p><p>He had a few options. He could keep doing the work himself. He could hire an external contractor. Or he could make the case to bring someone in-house to take over the work completely.</p><p>He chose the third option. But to make it successful, he had to spend time documenting the CAD standards, file storage rules, revision process, and how projects were scoped. That took time and effort, and it required him to slow down in the short term.</p><p>The projected return on investment was around three months. In reality, it took five. But once the process was in place, the company had a dedicated designer who was faster, more cost-effective, and fully ramped. The engineer moved on to lead larger automation initiatives. Everyone won.</p><p>The lesson is simple. Documentation is not just about writing things down. It is about scaling yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*79PGvxu5NXHfEtSc" /><figcaption>Figure 4 — From Quality Metrics to Electrical Panels | THE DOCUMENTATION LADDER, How Teams Scale and Leaders Emerge</figcaption></figure><p>In manufacturing, every role has some repetitive component that can be standardized, structured, or offloaded with the right documentation. Creating that clarity is not busywork. It is leadership.</p><p>If you want to grow your career, start by making what you know usable by others. That is how you free yourself to do more meaningful work. That is how you become someone your organization cannot afford to keep in the same role for long.</p><h3>Conclusion</h3><p>Operational performance is not about heroic effort. It is about creating clarity, building routines, and making better decisions over time.</p><p>If leadership is present, if systems reflect reality, and if data is understood, improvement becomes consistent and sustainable. That is true on the plant floor, in quality labs, and in personal careers.</p><p>I hope something in this issue helps you take a step forward. As always, thank you for reading. And if you found value here, consider sharing it with someone who wants to do better work</p><h3>📚 Further Reading &amp; Resources</h3><p>If this issue sparked something for you, here are some of the best resources to go deeper into the ideas discussed:</p><p><strong>1. </strong><a href="https://www.themanufacturinginstitute.org/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-quality-metrics-to-electrical-panels-how-to-read-the-hidden-signals-in-your-plant"><strong><em>The Manufacturing Institute — Workforce &amp; Leadership Reports</em></strong></a><br>Key insights into the manufacturing labor shortage, leadership trends, and what’s holding back operational improvement.</p><p><strong>2. </strong><a href="https://www.lean.org/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-quality-metrics-to-electrical-panels-how-to-read-the-hidden-signals-in-your-plant"><strong><em>The Lean Enterprise Institute (LEI)</em></strong></a><br>A practical library of case studies, tools, and thinking around Lean, continuous improvement, and factory culture.</p><p><strong>3. </strong><a href="https://www.isa.org/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-quality-metrics-to-electrical-panels-how-to-read-the-hidden-signals-in-your-plant"><strong><em>ISA — International Society of Automation</em></strong></a><br>Technical standards and thought leadership on controls, instrumentation, and system reliability — ideal for those working behind the panel.</p><p><strong>4. </strong><a href="https://sloanreview.mit.edu/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-quality-metrics-to-electrical-panels-how-to-read-the-hidden-signals-in-your-plant"><strong><em>MIT Sloan Management Review — Leadership &amp; Culture</em></strong></a><br>High-quality writing on how leadership behavior influences performance, especially under pressure.</p><p><strong>5. </strong><a href="https://www.controleng.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=from-quality-metrics-to-electrical-panels-how-to-read-the-hidden-signals-in-your-plant"><strong><em>Control Engineering Magazine</em></strong></a><br>Industry news and application insights for engineers and managers dealing with plant systems, automation, and infrastructure challenges.</p><p><strong>6. </strong><a href="https://www.framexl.com/"><strong><em>FRAMEXL Archives</em></strong></a><br>Explore past FRAME issues for more insights on digital transformation, technical leadership, and building better manufacturing teams..</p><h3>Get in Touch with Us</h3><ul><li><a href="https://www.linkedin.com/in/vladromanov/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=the-disciplined-factory-tools-thinking-and-habits-that-scale"><em>Vladimir Romanov</em></a></li><li><a href="https://www.joltek.com/?utm_source=www.framexl.com&amp;utm_medium=referral&amp;utm_campaign=the-disciplined-factory-tools-thinking-and-habits-that-scale"><em>Joltek</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c5d3eba5fc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Operational Resilience: Skills, Systems, and Strategies for Modern Manufacturing]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vrom.medium.com/building-operational-resilience-skills-systems-and-strategies-for-modern-manufacturing-0f5e7e80662b?source=rss-2c74f814558a------2"><img src="https://cdn-images-1.medium.com/max/1292/0*8MJVdaZSGB_aUxQR" width="1292"></a></p><p class="medium-feed-snippet">Read &amp; Subscribe to the full publication&#x200A;&#x2014;&#x200A;FRAME | Foundation for Reliability, Automation, Manufacturing &amp; Excellence</p><p class="medium-feed-link"><a href="https://vrom.medium.com/building-operational-resilience-skills-systems-and-strategies-for-modern-manufacturing-0f5e7e80662b?source=rss-2c74f814558a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vrom.medium.com/building-operational-resilience-skills-systems-and-strategies-for-modern-manufacturing-0f5e7e80662b?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f5e7e80662b</guid>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Sat, 26 Apr 2025 18:09:40 GMT</pubDate>
            <atom:updated>2025-04-26T18:09:40.065Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Hidden Costs of Obsolescence, Misused Metrics, and Misaligned ERP]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vrom.medium.com/the-hidden-costs-of-obsolescence-misused-metrics-and-misaligned-erp-7d84b1eb5c3d?source=rss-2c74f814558a------2"><img src="https://cdn-images-1.medium.com/max/1292/0*_go3bJZErDwdO6-J" width="1292"></a></p><p class="medium-feed-snippet">Read &amp; Subscribe to the full publication&#x200A;&#x2014;&#x200A;FRAME | Foundation for Reliability, Automation, Manufacturing &amp; Excellence</p><p class="medium-feed-link"><a href="https://vrom.medium.com/the-hidden-costs-of-obsolescence-misused-metrics-and-misaligned-erp-7d84b1eb5c3d?source=rss-2c74f814558a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vrom.medium.com/the-hidden-costs-of-obsolescence-misused-metrics-and-misaligned-erp-7d84b1eb5c3d?source=rss-2c74f814558a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d84b1eb5c3d</guid>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Vladimir Romanov]]></dc:creator>
            <pubDate>Sat, 26 Apr 2025 17:58:41 GMT</pubDate>
            <atom:updated>2025-04-26T17:58:41.443Z</atom:updated>
        </item>
    </channel>
</rss>