Professional Documents
Culture Documents
Edge Data Gathering, Analytics For Automation Average or Excellent Hardware and Software
Edge Data Gathering, Analytics For Automation Average or Excellent Hardware and Software
Edge Data Gathering, Analytics For Automation Average or Excellent Hardware and Software
automation
About the viewer panel
Technical problems?
Click on the “Question Mark Symbol” on the upper right hand corner of your screen, where you will be directed to a list
of system checks
Send a question from the “Ask a Question” window. Individual technical questions will be answered in the “Answered
Questions” on the left hand side of your screen
Slides:
Click the four pronged arrow button at the top right corner of the slides to view an expanded window
Slides should change automatically
Click on “Download Webcast Slides” under “Event Resources” for a PDF of all slides
Warning: The PDF will be a large file
Archive:
Take the Learning Unit Exam use the “Learning Unit Exam Tab” at the top of the screen; the exam will open in a new
browser window and the Iink will break when the Webcast signs off. The on-demand version of the webcast includes
the exam, which is for one (1) RCEP / ACEC Certified Professional Development Hour (PDH).
Within 7 days, an archive with Q&A will be posted
We will send an email to registered attendees with hyperlink
Can also access from home pages for www.controleng.com under online training.
RCEP Quality Assurance Statement
®
Course description:
Hardware and software used to gather and analyze collected data may require more
capabilities than traditional controllers used in automation applications. What hardware and
software characteristics are particularly useful for industrial edge data gathering and
analytics? When should cloud-based connections be considered for analytics, how can
cloud data analytics help and what needs to happen to data before going to the cloud?
®
Learning Objectives:
• See how data should be treated during collection and before
analysis, either on premise or in the cloud
®
Today’s Presenters
PRESENTER MODERATOR
®
Learning Objective 1
See how data should be treated during collection and before analysis, either
on premise or in the cloud.
Focus on the Analysis
Not the infrastructure
®
Artificial Intelligence (AI) changes everything
Big Data is at the heart of success
Less is no longer more
®
MQTT, REST and more new acronyms
Different technologies for different applications
®
Edge as the data broker
Applications that store, pre-process and forward
• Enables IT/OT convergence IT
• Local buffering of high-frequency in-plant data
gathering
• Off-loaded device functionality
• Optimized transactional cloud communication Edge
• Hysteresis and change-of-state
OT
®
Learning Objective 2
Understand how hardware and software for industrial edge applications are
helping with data gathering and data preparation before analytics.
Defining the Edge
Application workloads running on a compute surface
®
You are the key to sensor data
Democratization of artificial intelligence
and machine learning (AI & ML)
Was data scientists -> is IT/OT Convergence
Contextualization is critical
®
Security
Provide isolation between Plant, Enterprise and Cloud
• Authenticity
• Confidentiality
• Trust
• Data diodes
Patch management
®
Learning Objective 3
Explore how hardware and software needs for industrial edge applications
differ from more traditional hardware and software for automation
applications.
Not simply an IT problem
Adapting software and hardware delivery for industrial environments
These workloads and devices live at the edge of the plant, interacting
directly with the enterprise and cloud
• Do no harm. Must not introduce disruption to 24/7 operations
• For mission critical applications, must maintain continuous
availability even through updates
Compliance
• Industries often require strict standards adherence as a license to
operate (e.g. security, safety, audit logs)
Be careful what you wish for…
The advancement of edge solutions raises a new problem for automation end users
Patches need to be deployed These workloads may be less This results in problems with
once by the vendor and semi- mission critical than deployment at scale that we
automatically distributed traditional process control, so have not typically seen in
everywhere the workload or vendors move to much industrial automation
device is deployed shorter release cycles to software and devices before
quickly deliver value to the where stability was and is
market valued more than new
features once a system is
deployed
Learning Objective 4
Not “one size fits all” for the industrial edge. This creates interoperability challenges.
®
Industrial edge personas
Hardware/software needs are ultimately driven by business value
Main persona
System Machine
Integrator Builder
Application interoperability
Deploying edge applications at scale
User Story - A plant operator wants to Proof of Concept Deployment & management at scale
deploy applications from different vendors
at scale. Manual Automated
process process
• The plant operator has a preferred Plant A Plant B
hardware vendor 1 2 2 2
1 1
• Hardware must support the required Equipment 01
applications 1 2
• Must monitor and manage all required
applications using the same
orchestration solution Plant C
1 1 2 2
Difficult to achieve due to many
applications having strict dependencies on 1 App from supplier X 1 2
hardware or orchestration solutions.
2 App from supplier Y
Device interoperability
Managing edge devices at scale
User Story - A plant operator wants to Proof of Concept Deployment & management at scale
manage devices from different vendors at
scale. Manual Automated
process process
• Multiple devices are required to fulfill Plant A Plant B
different application requirements (e.g. DEV DEV DEV DEV
GPU processing, small form factor) 1 2 1 DEV DEV
1
DEV 2 2
• Must monitor and manage all edge DEV
1
devices using the same orchestration 2
solution Plant C
• Must minimize the effort to patch and DEV DEV
DEV DEV
1 1
supervise these devices DEV1 Device from supplier X
2
DEV 2
DEV
1
DEV2 Device from supplier Y 2
Difficult to achieve due to lack of
standardization for managing devices.
Complexity is a barrier to innovation
An argument for interoperability
• Archive:
Within 7 days, an archive with Q&A will be posted