Walker can you speak to data controls when implementing a UNS I keep running into major issues with data policy just moving SCADA history to a cloud database. Additionally there are lots of legal ramifications for pipeline customer and sales reps having access to certain data
Great explanation, so for a self aware SCADA you would need to use a very precise standard on the name of your equipment, for example motor/tanks follow by the number of position, so an script look for the number of equipment with the name motor* and associate an expecific pre set image to that device on that area screen? is this how a self aware should be architecture? of one of the topics on that particular equipment will have the configuration for the standard?
Great video, thank you! Two questions: 1) Where do you standardize readings, such as different units (e.g., Tank A reports temp in celsius, Tank B in Fahrenheit)? At PLC or UNS level? 2) ISA-95 asset hierarchy works well for factories and some other value chain steps, but what about product engineering, or product telemetry (think a Tesla car sending back sensor data) - wouldn't this require another asset hierarchy?
Great video. Is it fair to say an architecture.based on Modbus would be deterministic so. As a consumer I need to know what data availible, and where it is?
Good, good, good, good Vibe rations! Excellent explanation of deterministic versus nondeterministic approaches with architecture. Definitely raises my understanding a couple of notches. The Vibe board is great!
Edge and cloud is highly decoupled when you use MQTT. If you have ever fetched data using an API, you will realize why this is the case. This means that changes in the software code is cheap on the edge. Which is why MQTT is so scalable on the edge. But what i've never heard mentioned regarding MQTT is how the dev difficulty is moved from edge to cloud.
The context of the user defines the encapsulation of the data. Since different users exist with different contexts, the idea of a single information model for an object is nuts on its face. Object models matter, because they create consistency of context for similar users across an enterprise. But the key is to enable multiple models/abstractions (through composition, or polymorphism, or whatever) for nodes so that different users can access the data in contexts that matter to them. A tank is a tank - and it has function, and sensors, and behavior. An instance of a tank should encapsulate all of that in its object model. For those that just need "tank" context, they can access the device data as a tank. For those that need process data for that tank on that line doing that thing, well, that context exists too.
Great video, Walker. Would deterministic design be considered an Industry 4.0 function? Also, it seems to me that how data is provided for consumption has evolved in this Industry 4.0 migration.
Walker can you speak to data controls when implementing a UNS I keep running into major issues with data policy just moving SCADA history to a cloud database. Additionally there are lots of legal ramifications for pipeline customer and sales reps having access to certain data
Good topic for another video!
Your content is always rich in knowledge, love the #WhiteBoardWednesday Series 👏👏
I appreciate that! Glad to bring Whiteboard Wednesday back!
Great explanation, so for a self aware SCADA you would need to use a very precise standard on the name of your equipment, for example motor/tanks follow by the number of position, so an script look for the number of equipment with the name motor* and associate an expecific pre set image to that device on that area screen? is this how a self aware should be architecture? of one of the topics on that particular equipment will have the configuration for the standard?
Great video, thank you! Two questions:
1) Where do you standardize readings, such as different units (e.g., Tank A reports temp in celsius, Tank B in Fahrenheit)? At PLC or UNS level?
2) ISA-95 asset hierarchy works well for factories and some other value chain steps, but what about product engineering, or product telemetry (think a Tesla car sending back sensor data) - wouldn't this require another asset hierarchy?
Great video. Is it fair to say an architecture.based on Modbus would be deterministic so. As a consumer I need to know what data availible, and where it is?
Exactly
Great video, Walker. Informative as always.
Thanks, Karl.
Good, good, good, good Vibe rations! Excellent explanation of deterministic versus nondeterministic approaches with architecture. Definitely raises my understanding a couple of notches. The Vibe board is great!
Glad you enjoyed it! We definitely missed using the vibe board!
Great job taking a troll and turning it into a useful teaching experience.
Way more mature (and helpful) than my response would have been! :)
Glad you enjoyed it!
Edge and cloud is highly decoupled when you use MQTT. If you have ever fetched data using an API, you will realize why this is the case. This means that changes in the software code is cheap on the edge. Which is why MQTT is so scalable on the edge. But what i've never heard mentioned regarding MQTT is how the dev difficulty is moved from edge to cloud.
The context of the user defines the encapsulation of the data. Since different users exist with different contexts, the idea of a single information model for an object is nuts on its face. Object models matter, because they create consistency of context for similar users across an enterprise. But the key is to enable multiple models/abstractions (through composition, or polymorphism, or whatever) for nodes so that different users can access the data in contexts that matter to them. A tank is a tank - and it has function, and sensors, and behavior. An instance of a tank should encapsulate all of that in its object model. For those that just need "tank" context, they can access the device data as a tank. For those that need process data for that tank on that line doing that thing, well, that context exists too.
Great video, Walker. Would deterministic design be considered an Industry 4.0 function? Also, it seems to me that how data is provided for consumption has evolved in this Industry 4.0 migration.
This is really Good and has cleared a few things for me that i was struggling with. Brilliant Thanks.
Glad it helped!
Thast why UML have the concept of Polymorphism