Embed Size (px)
Citation preview
ACCELERATING THE DIGITAL TRANSFORMATION - BUILDING A 3D IOT
REFERENCE ARCHITECTURE ACROSS INDUSTRIAL SECTORS.
Ovidiu Vermesan
SINTEF
1OPENDEI Webinar sessions – The role of the Reference Architectures in data-
oriented Digital Platforms
The role of the Reference Architectures in data-oriented Digital Platforms
SINTEF
Chief Scientist
Ovidiu Vermesan
Co-Funded by the European Commission
Why developing a reference architecture?
The basis for providing a
methodology and set of
practices and templates that
are based on the
generalization of a set of
previous solutions used in the
industrial sectors.
Allows identifying the use of
common data/knowledge
formats as an integration
method to avoid every
connector/interface having to
convert data to/from every other
components' formats and/or the
use of interfaces and APIs
between components.
Includes different views along
with functional domains,
system properties, functions,
the description of interfaces
(e.g. APIs for platforms,
software and algorithms
components) and interactions
these elements and the
functions located outside the
reference architecture.
Supports the definition in the
early design phases of common
data models, communication
standards and exchange
formats, and common SW/HW
building blocks and define
reusable assets and models.
Enables tracing the data/knowledge
flows and streams between the
different architectural layers.
Facilitates the evaluations of the
level of integration of the sub-
systems at the system level and
how to combine the existing,
systems and sub-systems.
Co-Funded by the European Commission
IoT Reference Model
Source: IERC
Co-Funded by the European Commission
Reference Architectural Model Industrie4.0 (RAMI 4.0)
RAMI is a three-dimensional model reflecting:• Life Cycle and Value Stream, from development to
decommissioning, with both the perspectives of the products and services to be offered and of the supporting processes and workflows.
• Layers, in support of business and interoperability:• Business; Functions; Information; Communication;
Integration, Asset (the "Things")• Hierarchy Levels - the (factory) : from Product, Field Device,
Control Device, to Enterprise and Connected World
Source: Plattform Industrie 4.0 and ZVEI
Co-Funded by the European Commission
Industrial Internet Reference Architecture (IIRA)
The IIRA is defining the following viewpoints:• Business: identifies stakeholders and their business vision, values and
objectives.• Usage: addressing the expected system usage, it is typically represented as
sequences of activities involving human or logical (e.g. system or system components) users.
• Functional: focuses on the functional components, their structure and interrelation, the interfaces and interactions.
• Implementation: deals with the technologies needed to implement functional components
• On top of the functional model dimension, the IIRA considers two dimensions regarding:
• System Characteristics: refers to behaviours and properties resulting from the interactions of the parts of the system. Safety and security are two examples of such characteristics.
• Crosscutting Functions: refers to the additional functions that need to be provided in order to enable the major system functions. Connectivity is an example of such cross-cutting functions. Source: Industrial Internet Consortium
Co-Funded by the European Commission
Reference Architecture Model Edge Computing (RAMEC)
Guided by international standards defined by ISO/IEC/IEEE 42010:2011, the architecture systematically addresses the industry's concerns about edge computing and presents solutions and frameworks. Edge Computing Reference Architecture is demonstrated using the following views:• Concept View: describes the domain models and key concepts of edge
computing.• Function View: Describes the functions and design concepts of the
development service framework, deployment and operation framework SF, CCF, and ECN in the horizontal direction, as well as of cross-layer open services, management services, lifecycle data services, and security services in the vertical direction.
• Deployment view: Describes the system deployment process and typical deployment scenarios.
• The architecture needs to meet typical cross-industry, non-functional requirements, including real-time performance, certainty, and reliability. Related technical solution recommendations are provided in the function view and deployment view.
Reference Architecture Model Edge Computing (RAMEC) is NOT a technical system architecture but an orientation guide.
Source: ECCE
Co-Funded by the European Commission
Smart Grid Architecture Model (SGAM)
The SGAM framework and its methodology are intended to present the design of smart grid use cases in an architectural viewpoint allowing it both-specific but also neutral regarding solution and technology. • Interoperability Dimension: consists of five layers representing business
objectives and processes, functions, information exchange and models, communication protocols and components. These five layers represent an abstract and condensed version of the interoperability categories.
• Domains: covers the complete electrical energy conversion chain. This includes the domains.
• Zones: represent the hierarchical levels of power system management [IEC62357-2011]. These zones reflect a hierarchical model which considers the concept of aggregation and functional separation in power system management.
Source: CEN-CENELEC-ETSI Smart Grid Coordination Group Smart Grid Reference Architecture
Co-Funded by the European Commission
IoT 3D Architecture Approach • 3D Reference IoT Architecture• Objectives:
• Ensure that the model deals with• All the functional aspects e.g. “cross layers”• Extend to more than the functional aspects• Include extension to AI, DLTs, Digital Twins• Intelligent connectivity• Physical/Digital/Virtual/Cyber Integration• Allow the implementation of
data/information/knowledge continuum from the physical nodes, deep-edge, edge, cloud, data centre
• Platforms implementations, marketplaces• Heterogeneity of devices ( simple to autonomous,
robotics things) - Systems of Systems.• Map on other reference architectures
• A three dimensional model• Layers• Cross-cutting functions• System properties
Co-Funded by the European Commission
AUTOPILOT
IoT to transformautomated driving
Source: AUTOPILOT
https://autopilot-project.eu/
Co-Funded by the European Commission
Architecture Approach
❖Data correlation and information retrieval❖Communication❖Integration and interoperability❖Security, privacy and trust
IoT reference architectures
❖AIOTI - Reference Architecture❖ISO/IEC 30141 IoT Reference Architecture❖ITU-T Y.2060❖IOT-A ARM
Architecture patterns
❖Four-tier architecture❖Gateway-mediated and direct cloud
connectivity❖Connectivity and management❖Device-to-Cloud❖Multi-tier data storage❖Distributed analytics
Characteristic features of IoT
Source: AUTOPILOT
Co-Funded by the European Commission
LSP Architecture Approach
Application
Layer
IoT
Layer
Network
Layer
AUTOPILOT
Things
End-to-end
Communication
Network
Communication
Hop by hop
Communication
Context
ManagementSemantics
Process and Service
Management
Analytics
AUTOPILOT Applications
Device
Management
Security
Source: AUTOPILOThttps://european-iot-pilots.eu/architecture-analysis/
Co-Funded by the European Commission
Architecture Approach
Source: AUTOPILOT
Co-Funded by the European Commission
Architecture Approach
Source: AUTOPILOT
Co-Funded by the European Commission
Architecture Approach
Source: AUTOPILOT
Co-Funded by the European Commission
Thank You!
https://european-iot-pilots.eu/ https://european-iot-pilots.eu/project/create-iot/
