Blog: OT Democratization Journey #2455
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Yndira-E Do you know if it okay if I used this image or will we need to recreate it? https://www.ciscopress.com/articles/article.asp?p=3004581&seqNum=2 |
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 15.3%, saving 24.23 KB.
1314 images did not require optimisation. |
ZJvandeWeg
reviewed
Aug 14, 2024
ZJvandeWeg
requested changes
Aug 14, 2024
Comment on lines
+21
to
+23
| ## Industry 3.0: The Rise of PLCs | ||
|
|
||
| Industry 3.0 saw significant acceleration with the advent of Programmable Logic Controllers (PLCs). These devices transitioned the use of physical relays into their electronic counterparts. Initially, PLCs were programmed using five languages outlined by IEC 61134-3. This standard laid the groundwork for modern PLC programming, with Ladder Logic emerging as a popular method due to its visual similarity to traditional relay logic. This eased the transition for many engineers from physical to digital logic design, arguably creating one of the first widely adopted low-code solutions. |
There was a problem hiding this comment.
Maybe spend a sentence to explain where Industry 2.0 left the world? What state were manufacturing companies in? And use that hook to show why PLCs were required with democratization?
|
|
||
| ## The Evolution of Data Handling Models | ||
|
|
||
| This period also witnessed the rise of ISA-95 and the Purdue Model, which were instrumental in structuring data transport between layers. Each layer chose protocols best suited to its needs, creating a point-to-point model that, while effective, was cumbersome to establish. Although some organizations emerged as industry leaders by successfully implementing this architecture, they often struggled with the last 5%+ of integration and incorporate of modern technologies. Seemingly simple tasks were complex due to data not being in the right place or in the right format, stripping away vital meta-information not considered during the initial data point definition. |
There was a problem hiding this comment.
Suggested change
| This period also witnessed the rise of ISA-95 and the Purdue Model, which were instrumental in structuring data transport between layers. Each layer chose protocols best suited to its needs, creating a point-to-point model that, while effective, was cumbersome to establish. Although some organizations emerged as industry leaders by successfully implementing this architecture, they often struggled with the last 5%+ of integration and incorporate of modern technologies. Seemingly simple tasks were complex due to data not being in the right place or in the right format, stripping away vital meta-information not considered during the initial data point definition. | |
| This period also witnessed the rise of ISA-95 model, which were instrumental in structuring data transport between layers. Each layer chose protocols best suited to its needs, creating a point-to-point model that, while effective, was cumbersome to establish. Although some organizations emerged as industry leaders by successfully implementing this architecture, they often struggled with the last 5%+ of integration and incorporate of modern technologies. Seemingly simple tasks were complex due to data not being in the right place or in the right format, stripping away vital meta-information not considered during the initial data point definition. |
Don't think a customer themselves brought up Purdue, let's stick with ISA-95 and link to a post explaining it on our blog?
Comment on lines
+38
to
+49
| ## Redefining Industry 4.0: The Birth of Industry 4.5 | ||
|
|
||
| This leads us to revisit our strategies, refining solutions like the Digital Thread and the UNS to continue advancing Industry 4.0's connectivity initiatives. The upcoming iteration, which could be termed Industry 4.5, aims to enhance this connectivity by integrating applications that add a new layer of complexity and capability to connectivity issues. | ||
|
|
||
|
|
||
| ## The Role of FlowFuse in Industry 4.5 | ||
|
|
||
| An example of this integration is how companies might choose FlowFuse, a platform that not only provides application-building capabilities but also solves connectivity challenges. Organizations might use FlowFuse as a complete solution or augment it with bespoke applications, similar to how vanilla Node-RED is currently being adopted in the industry. | ||
|
|
||
| ## The Future | ||
|
|
||
| In conclusion, the democratization of technology in industrial contexts not only makes powerful tools widely accessible but also continuously evolves to meet the changing needs of the industry. As we look towards Industry 4.5 and beyond, the focus will increasingly be on how applications can enhance connectivity to drive further innovation and efficiency. |
There was a problem hiding this comment.
This part needs expansion, it's very short but the main point of the post?
Co-authored-by: Zeger-Jan van de Weg <[email protected]>
Co-authored-by: Zeger-Jan van de Weg <[email protected]>
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 20.6%, saving 20.56 KB.
1318 images did not require optimisation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist