Walker Reynolds’ Post

Can’t wait! 🙏

We are completing some updated benchmarking for a common IIoT use case. We have functional and technical requirements Technical Infrastructure Requirements - Edge Driven - Report by Exception - Lightweight - Open Architecture Functional Requirements - Convert all data to IIoT Protocol - UNS Architecture - Coalesce data from multiple points and publish to infrastructure (Data-Ops) This test will also be completed by publishing directly from a device — likely an Opto 22 Groov Epic. Our broker is HiveMQ and our OPC Server is Kepware, a PTC Technology We will also be deploying a MING stack to consume natively from the infrastructure. I need some help. I am looking for OPC-UA products to use for this part 14 implementation. Ideally — a PLC to go under the OPC Server and another OPC-UA Server to test in parallel with Kepserver. Recommendations for OPC On Board products that I can plug into the Part 14 box? Or replace Kepserver/Part14 boxes with? #iiot #digitaltransformation #unifiednamespace

Looking forward to it! 🙏

A follow up to the OPC-UA podcast yesterday and a response for Lachlan Wright who commented on the video. I go over the origin story of MQTT -- along with the the functional requirements that drove the incentive to write a new protocol. - Edge Driven - Open Architecture - Report by Exception - Lightweight I also quickly show implementations of MQTT5, Sparkplug and OPC-UA Part 14 for the same use case. - Connect to an OPC Server - Subscribe to a variable node (a tag) - Build a namespace and payload - Update both when the variable node value changes This is an example of building a simple OPC-UA to MQTT Gateway, using three different standards. I am currently working on a much more complete example to demonstrate why some standards are adopted and others are not. You can see the examples at 12:00 of the video. Lachlan -- you said I wouldn't answer your question. I did. Thanks for asking it and thanks for watching. #unifiednamespace #iiot #digitaltransformation

This release is one of the biggest announcements of the year. The new 3.4 HighByte Release includes a 2 hour resettable license for a natural land and expand licensing model. This is a big deal. Data-Ops means a lot of things — conversions of data into information through modeling, transfer of data (and/or information) from one place to another, the conversion of protocols (opc-ua to MQTT, SQL to Snowflake via Snowpipe, etc etc etc) and on and on and on. Data-ops is, for the layperson, the conversion of data into value for your business. When we talk about the data and info in your #unifednamespace — often times we can quantify the distribution this way — 30% OT data, 10% IT data and 60% coalesced data (stuff we converted from the first two). Data-Ops is how you build the 60%… and HighByte is the gold standard for how it’s done. Let me be clear — I have no commercial relationship with HighByte — I am not paid to make these statements. This is my opinion — learn HighByte, do it for free, and these will be your opinions too. 🙏 Well done Aron and team. #iiot #digitaltransformation #dataops

🚀 Who hasn't heard about our 16-Week Digital Factory Mastermind Accelerator Program? We listened. There's so much noise and content about digital transformation it can be overwhelming. So, we crafted this Accelerator to distill it down, focusing on what truly matters for your digital transformation, thereby fast-tracking your acquisition of crucial knowledge, skills, resources, and confidence. What are the top three topics you'd like to see covered first in the accelerator program? Let us know, as there's still time to tailor the curriculum to your immediate needs.

Lol -- Andreas just found one of many limitations to Part 14. I think Matthew Parris might want to chime in on this. The simple fact is, there is no 'right' way to do this with part 14 because part 14 was written by people who have never worked on the plant floor and have no idea how to write an inclusive specification for event driven architecture that applies to all use cases. C# reference is an extension of a flawed part 14. OPC-UA is not intended for interoperability. It is intended to sell products for Microsoft and Rockwell and Beckhoff. The answer to your question, Andreas, is no -- it is not defined in the spec. Welcome to reality -- OPC-UA pub/sub is nothing short of complete garbage. There are many reasons that no one outside of the working group is using it. I would love to see OPC-UA be what it was intended to be. But I accept things for what they are. Part 14 is a very poor example of a monkey patch for OPC-UA. 🙏

Jane Arnold is an excellent speaker with a proven track record in digital transformation — if you’re in the northeast — this is worth your time to attend. 🙏

An announcement for Mastermind Students at iiot.university and YouTube Followers. On Friday, April 12, at 8am CDT, in our monthly Mastermind call, we will have a very important lesson. As most of you know, we've been beta testing Litmus UNS with Litmus Edge... I've been deep diving for weeks on all of the functionality. Most of the community struggles to understand where Litmus fits in an ecosystem. What is it? How does it work? What are its strengths and weaknesses? How do I work with it? Why should I care? How much does it cost? On April 12, the Litmus team will be presenting for 2 hours. There will be two live demos -- one will be their standard Litmus Edge demo and the second will be a full integration to our community UNS. The video below gives a sneak peak into what it looks like. The full integration will leverage Kepware, a PTC Technology HighByte Inductive Automation HiveMQ and the full suite of Litmus solutions. This is meant to be an interactive session -- so please come with your questions, ideas and critiques. In the last hour of the Mastermind (hour 3), we will have Arlen Nipper Yours Truly, Aron Semle Matthew Parris to have an open discussion about MQTT, Sparkplug spec and the future of MQTT in Industry. This conversation will be published as a podcast to our YouTube channel and podcast platforms. Mastermind students will be invited to ask questions and give feedback on MQTT, sparkplug and anything else we discuss. I'd love to see your comments and questions below on these topics! See you there!! #unifiednamespace #iiot #digitaltransformation

A couple of thoughts. 1. MQTT Brokers are tech infrastructure, not solutions. 2. If you have buyers remorse after ‘buying’ an MQTT broker, then you weren’t equipped to make that decision in the first place. If you don’t understand what you are buying, bring in SME’s who do understand. 3. End Users — you should not be spending a penny on licensing until value has been proven by your vendor and your partners. Insist on a land and expand licensing strategy. 4. Digital transformation is a strategy. Do not buy tech to solve business problems (Vatsal and I definitely disagree here). You MUST build an open infrastructure (with tech) first — UPON WHICH you iteratively solve business problems. What you want (your business problem) is a function of what you know. Digital Transformation exponentially increases the collective knowledge of your org by unlocking the potential in the raw and coalesced events all across your organization (locked up inside your ‘smart things’). You don’t know your problems — you are not equipped to select tech on a business case by business case basis. A. Where are you? B. Where do you want to go (right now)? C. Where do you start? D. How do you start? - Digital Strategy - Architecture - Minimum Technical Requirements - Infrastructure - Solve, Learn, Iterate 🙏 #unifiednamespace #iiot