Factory Field Notes cover art

Factory Field Notes

Factory Field Notes

Written by: Vladimir Romanov
Listen for free

Factory Field Notes is a practical podcast for manufacturing leaders, engineers, and technical managers who want real lessons from the plant floor. Hosted by Vladimir Romanov, the show breaks down automation, controls, SCADA, MES, OT networks, industrial data, downtime, reliability, project execution, and the messy work of modernizing factories without vendor fluff or empty transformation talk.© 2026 Vladimir Romanov
Episodes
  • Ep. 5 | Allen-Bradley vs Siemens: Why Plants Pick One PLC Platform and Live With It [Field Q&A]

    Ep. 5 | Allen-Bradley vs Siemens: Why Plants Pick One PLC Platform and Live With It [Field Q&A]
    Jun 2 2026
    Allen-Bradley vs Siemens is rarely a pure technology decision, and this field Q&A breaks down why region, hiring, support networks, and vendor lock-in usually decide your PLC standard long before specs do. If you own a platform decision, this gives you the real reasoning to defend it upward.Most managers inherit a control system standard rather than choose one from a clean sheet. A plant accumulates machines from different builders, each arriving with its own controller, and over time the cost and difficulty of supporting many vendors pushes the organization toward harmonizing on one platform. The honest answer to "why Allen-Bradley and not Siemens" starts there. Allen-Bradley and Rockwell Automation dominate North American plants because the surrounding ecosystem dominates: the integrators, the distributors, the training centers, and the engineers who can be on site during a midnight shift all cluster around the regionally entrenched brand. Siemens carries that same weight across most of Europe, while Omron and Mitsubishi hold strong positions across much of Asia. Standardizing on a platform your region cannot easily staff or source is a real operational risk, not a spec sheet footnote.There is a genuine technical contrast worth understanding too. In this episode the comparison is framed as Rockwell being easier to use but more prescriptive, similar to a closed and guided ecosystem, while Siemens offers more flexibility and customization at the cost of engineering complexity. North American teams tend to lean heavily on ladder logic and external integration resources, whereas European teams more often carry deeper in-house engineering capability and reach for structured text. Once a platform is embedded, the surrounding products follow it: the HMIs, the VFDs, the servo drives, the managed switches, and the energy monitors all integrate more cleanly inside Studio 5000 or TIA Portal, which is exactly how vendor lock-in compounds and why switching platforms after you scale almost never pencils out.This Q&A also tackles the questions that fill a maintenance manager's week. We cover whether to suspect PLC logic or field hardware first when a conveyor stops intermittently, using a real example of a Siemens S7 line where an intermittent proximity sensor tripped the stop logic without ever holding an alarm long enough to be obvious. We get into building latches and trending the exact stop bits so an intermittent fault can be captured instead of chased for hours. We look at a vandalized PanelView Plus terminal, what a screen replacement actually involves, and why a full terminal can run $2,000 to $5,000 depending on features and source. And we close on whether every control system inevitably becomes harder to modify over time, why software segmentation per line keeps that complexity contained, and where SCADA and MES layers genuinely do raise the risk.If you are serious about manufacturing, automation, and making technical decisions you can defend to leadership, subscribe and join the community.Learn more at Joltek:- Control System Modernization Strategy: https://www.joltek.com/blog/control-system-modernization-strategy- Rockwell PLC Lifecycle Migration Guide: https://www.joltek.com/blog/rockwell-plc-lifecycle-migration-guide- Root Causes of Downtime in Industrial Automation: https://www.joltek.com/blog/root-causes-downtime-industrial-automation- System Integrators in Manufacturing: https://www.joltek.com/blog/system-integratorsTimestamps0:00 Intro to Factory Field Notes0:38 On the road at a client site1:08 New apprentice: how long until you feel competent5:05 Why Allen-Bradley and not Siemens6:00 Standardizing a plant on one PLC platform9:00 How region decides Rockwell, Siemens, Omron, Mitsubishi9:55 Rockwell vs Siemens: ease of use vs flexibility11:20 How vendor lock-in compounds across the ecosystem13:28 Troubleshooting: do you check logic or hardware first15:50 Reading the HMI fault and working backwards17:00 Latches and trending to catch intermittent faults18:45 A vandalized PanelView Plus and what repair costs20:55 Do PLC systems get harder to modify over time24:30 Where SCADA and MES layers add real complexityFind more from Joltek and Vladimir Romanov:Website: https://www.joltek.comBook a modernization consultation: https://www.joltek.com/book-a-modernization-consultationNew episodes of Factory Field Notes drop regularly. Subscribe so you do not miss the next one.
    Show More Show Less
    26 mins
  • Ep. 4 | PLC and Automation Q&A: Engineer Burnout, IT/OT Skill Gaps, and the 2026 Hiring Reality

    Ep. 4 | PLC and Automation Q&A: Engineer Burnout, IT/OT Skill Gaps, and the 2026 Hiring Reality
    May 22 2026
    This PLC and Automation Q&A answers six field questions on engineer burnout, IT/OT skill pressure, Studio 5000 bitwise AND, and the 2026 entry level job market.Every question maps to a decision an engineering manager is already navigating: retention, training, IT and OT scope, and how to hire and evaluate junior talent.Subscribe for analysis of engineering team dynamics, capital planning, and the operational realities of running an industrial automation function.Learn more at Joltek:- IT and OT Architecture Integration: https://www.joltek.com/services/service-details-it-ot-architecture-integration- Workforce Development and Education: https://www.joltek.com/services/service-details-workforce-development-education- Automation Leadership: https://www.joltek.com/blog/automation-leadership- Recruiting Robotics and Automation in Small Manufacturers: https://www.joltek.com/blog/recruiting-robotics-automation-small-manufacturersThe first question is a familiar one. Controls engineers used to spend most of their time inside PLC logic, and now the harder problem is everything around the PLC: HMI servers, edge devices, OPC UA, MQTT, historians, and the IT side consuming plant floor data. At larger sites this still gets handled by dedicated controls teams who never touch a switch or a domain controller. At smaller sites the same engineer is expected to do both, and the gap between job description and actual workload is widening fast.The second question is the one engineering managers should pay closest attention to. A practitioner asked whether people are generally miserable in this field after two and a half years across two jobs. The pattern in the post is structural, not personal: zero training, no mentorship, hostile reception to mistakes, operators escalating against engineers, and a previous occupant of the seat who left in under a year. Schneider Electric's 2024 workforce survey reports 59 percent of frontline skilled workers over 55 plan to retire within five years, and only 9 percent of workers ages 19 to 24 are entering skilled trades. The retention play is unglamorous: structured onboarding, named mentors, and shielding junior engineers from blame culture during the first 12 to 18 months on the floor.The third question was technical. A practitioner asked why Studio 5000 logic was applying a bitwise AND with 65,535 to a Local:2:I.Data array. That mask preserves the lower 16 bits of the 32 bit input register and discards the upper 16, a common pattern when an analog card packs two values into a double integer or when the upper bits hold status flags the application should not act on. For managers approving training spend, this is the type of question every junior engineer carries into their first commissioning, and a short internal documentation library of these patterns saves hours per project.The fourth and fifth questions both connect to skill development. One practitioner posted a wall of secondhand PLCs including SLC 500, ControlLogix L71, CompactLogix, Micro800, MicroLogix 1000 through 1400, Point I/O, GE Fanuc, ABB, and Mitsubishi units, most sourced for a fraction of new pricing. Another engineer with 15 years in the field admitted feeling behind on virtualization, domain controllers, and firewall rules. The structured path is Cisco CCNA fundamentals, then VLAN configuration on Rockwell Stratix or equivalent managed switches, then IP planning, OT segmentation, and the IT and OT DMZ patterns common to modern plant networks. Sponsoring a shared lab and protecting dedicated learning time are the two interventions engineering managers control most directly, and both compound.The sixth question was the entry level PLC market in Germany. The honest read is that Germany has a real shortage of automation engineers and a soft labor market for new graduates at the same time. Plant closures driven by pressure from Chinese electric vehicle manufacturers, rising energy costs, and broader economic conditions are pushing experienced engineers into open roles before junior candidates compete. The platform expectation in most German plants is Siemens TIA Portal and WinCC, with Beckhoff and Phoenix Contact present in specific verticals. The consistent hiring filter regardless of region is the same: can the candidate operate safely on a live plant floor, and will they put in legwork before escalating.Timestamps0:00 Intro and How to Submit Questions0:30 Q1: Is Automation Now Software Infrastructure4:00 Q2: Why Controls Engineers Burn Out10:30 About Vladimir and Joltek11:00 Q3: Bitwise AND in Studio 5000 Explained14:50 Q4: Building a Personal PLC Training Bench18:20 Q5: The IT and OT Skills Gap23:00 Q6: PLC and Automation Job Market in Germany28:30 What Senior Engineers Look For in Junior Hires31:30 Closing ThoughtsConnect with Vladimir and Joltek:Website: https://www.joltek.comBook a modernization consultation: https://www.joltek.com/book-a-modernization-consultationAbout Joltek: https://www.joltek.com/about
    Show More Show Less
    33 mins
  • Ep. 3 | Rockwell State of Smart Manufacturing Report 2026: What Executives Should Actually Believe [Review]

    Ep. 3 | Rockwell State of Smart Manufacturing Report 2026: What Executives Should Actually Believe [Review]
    May 21 2026
    The Rockwell State of Smart Manufacturing Report 2026 is the most cited smart manufacturing study of the year. This executive review pulls apart which findings hold up on the plant floor.Rockwell Automation surveyed 1,560 decision makers across 17 countries for the eleventh annual edition, with 62 percent holding spend authority.Subscribe for executive analysis of industry research, capital allocation, and the operational reality behind digital transformation.Learn more at Joltek:- Digital Transformation in Manufacturing: https://www.joltek.com/blog/digital-transformation-in-manufacturing- Industry 4.0 and Smart Manufacturing: https://www.joltek.com/blog/industry-4-0-smart-manufacturing- Industrial Cybersecurity (ICS): https://www.joltek.com/blog/industrial-cybersecurity-ics- Unlocking Industrial Data in Manufacturing: https://www.joltek.com/blog/unlocking-industrial-data-in-manufacturingThe report frames 2026 as the start of an execution era, with smart manufacturing moving from pilot to production. The directional read is right. The specific numbers behind it deserve closer scrutiny from anyone carrying P&L responsibility for a plant or a portfolio of plants.The most generous figure in the report is the claim that 43 percent of collected manufacturing data is now used effectively. In dozens of plant walks across food and beverage, CPG, life sciences, and pharmaceuticals, the realistic number looks closer to 5 to 7 percent once "effectively" is defined as data that is captured, contextualized, and actively moving OEE, quality, yield, or cost. Most production data still dies at the PLC and DCS layer, never reaching a historian, never landing in a database, and never informing a decision. The companion claim that 34 percent of operations are AI augmented today is similarly soft. Microsoft Copilot helping a quality engineer write a better email is not the same as a machine learning model closing a vision loop on a packaging line, and the survey does not separate the two.The cybersecurity finding is more credible and more strategically important. 46 percent of respondents reported a cyber incident in the past year, and the report correctly identifies the IT and OT integration layer as the most vulnerable surface. The angle that the prose underweights is insurance. Cyber regulations already in force in the European Union under NIS2 are penalizing critical infrastructure manufacturers for extended downtime, and equivalent frameworks are expected to reach North America by 2027. Premiums for industrial cyber coverage are rising in advance of those frameworks, and underwriters increasingly demand evidence that legacy Windows XP machines, SLC 500 controllers, and PLC 5s are either retired, patched, or placed behind defensible firewall architecture. That is the dynamic shaping CapEx priorities right now, more so than the headline AI numbers.The eight step path forward published in the report is recognizable to any operations leader who has run a transformation program. Two of the items deserve more weight than they typically receive. The first is communicating progress to build organizational momentum. A measurable share of transformation programs lose their best engineers to roadblocks, IT pushback, and approval friction long before the technical work is the bottleneck. The second is governance, because the data and decision rights questions only get harder as more systems become connected.A useful framing for the data side of this work is connect, collect, store, visualize. Connect is mostly a protocol decision across OPC UA, MQTT, and EtherNet/IP in a mixed Rockwell, Siemens, Beckhoff, and Opto 22 estate. Collect introduces software on top of the control layer and pulls in OT to IT cybersecurity considerations directly. Store is a question of historian, time series database, and cloud strategy. Visualize is where the human in the loop decision discipline lives, and where most organizations still underinvest. PwC's 2024 Digital Trends in Operations finding that only 32 percent of industrial products companies say their operations technology investments delivered expected results sits honestly alongside the more optimistic figures Rockwell publishes. Deloitte and the Manufacturing Institute project 2 million unfilled manufacturing jobs in the United States by 2030, which reframes automation investment as a labor strategy as much as a productivity one.The full report is free to download from Rockwell Automation and the link is provided in the description below.Timestamps0:00 Why Industry Reports Matter1:30 Note From the Chairman and CEO5:20 Demographics and Who Actually Responded8:50 Executive Insights and Headline Stats11:30 Energy, Workforce, and Cyber Pressures13:40 Is 34 Percent of Operations Really AI Augmented16:00 The 43 Percent Data Utilization Claim22:00 Workforce Reskilling Reality Check24:30 IT and OT Cybersecurity Incidents30:20 Five Capabilities of the Execution Era36:20 Connect, Collect, Store, ...
    Show More Show Less
    59 mins
adbl_web_anon_alc_button_suppression_t1
No reviews yet