FIWARE: Cross-domain concepts and technologies in domain Reference Architectures
1. FIWARE: CROSS-DOMAIN CONCEPTS AND
TECHNOLOGIES IN DOMAIN REFERENCE
ARCHITECTURES
Juanjo Hierro
FIWARE
0
OPENDEI Webinar sessions – The role of the Reference Architectures in data-
oriented Digital Platforms
The role of the Reference Architectures in data-
oriented Digital Platforms
2. The essential architecture pattern behind Smart Solutions
1
The essential architectural pattern of Smart Solutions:
gather data from many different sources (including but not limited to IoT)
to build a digital twin representation of the real world
(also referred as “context representation”)
which is constantly analyzed and processed in order to
simulate /automate certain process or bring support to smart decisions
Data =
Context / Digital Twin
Information
Process
Capture Actuate
3. What is a Digital Twin?
§ Digital Twin = Digital representation of an asset
• Characterized by attributes
□ Properties
□ Relationships ßà Linked Data
• Values of attributes may change over time (or not)
• Typically have a location (but it is not a must requirement)
§ (digital representation of) Context = Digital Twins Collection
§ A standard API for getting access to info about Digital Twins
would be essential and should support:
• Simple and complex queries
• Geo-queries
• Temporal operations (Digital Twins have history!)
• Subscription/Notification support
• Multiple “renderings” of the data in responses/notifications
§ Digital Twin = Asset Administrative Shell in RAMI 4.0
2
4. Modeling Context using Digital Twins
3
… in Cities Entities
(Digital Twins)
Bus
• Location
• No. passengers
• Driver
• License plate
Citizen
• Birthday
• Preferences
• Location
• ToDo list
Incident / claim
• Date
• Location
• Type
• Issuer
• Description
Shop
• Location
• Business name
• Franchise
• offerings
Attribute
5. Modeling Context using Digital Twins
4
Tractor
• Location
• Speed
• Planed route
Crop
• Humidity
• Leaf area
• Age
Drone
• Location
• Battery level
• Speed
• Planed route
… in Agrifood
Attribute
Entities
(Digital Twins)
6. Modeling Context using Digital Twins
5
Pallet
• id
• product
• Items quantity
• Layers
• Size
• Weight
Transport robot
• Id
• location
• speed
• transported items
• destination
Operator
• Id
• location
• assigned task
• profile
… in Manufacturing
Shopfloor Door
• Id
• location
• status (open/close)
Entities
(Digital Twins)
7. Modeling Context using Digital Twins
6
… in Energy
Wind Turbine
• location
• power
• wind speed
• pitch angle
Energy Storage
• active power
• reactive power
• SoC
• SoH
Substation
• Hi voltage
• Lo voltage
• nominal power
• power flow
Attribute
Entities
(Digital Twins)
8. Modeling Context using Digital Twins
7
… in Energy
Attribute
Tanker
• Driver
• Location
• Max Volume
• Current Level
• Speed
• Direction
Gas Tank
• Station
• Max Volume
• Current Level
• Min Threshold
• Temperature
Station
• Location
• Owner
• SLA
Entities
(Digital Twins)
9. NGSI-LD: Standard API for Context / Digital Twins info management
§ The NGSI-LD API is a simple yet powerful public, royalty-free standard API for Context
Information Management
• Simple: A RESTful API which any web programmer learns how to use in one day
• Yet powerful: supports to geo-queries, notification/subscription, federation, Linked Data …
§ Standardized by ETSI, Multiple Open Source implementations available in FIWARE
8
Application/Service
FIWARE NGSI API
Context Broker
Bus
• Location
• No. passengers
• Driver
• Licence plate
Citizen
• Name-Surname
• Birthday
• Preferences
• Location
• ToDo list
Shop
• Location
• Business name
• Franchise
• offerings
10. NGSI-LD: Standard API for Context / Digital Twins info management
§ The NGSI-LD API is a simple yet powerful public, royalty-free standard API for Context
Information Management
• Simple: A RESTful API which any web programmer learns how to use in one day
• Yet powerful: supports to geo-queries, notification/subscription, federation, Linked Data …
§ Standardized by ETSI, Multiple Open Source implementations available in FIWARE
99
Application/Service
NGSI-LD API
Context Broker
Smart Home
• location
• address
• installed PV
• energy consumption
Wind Plant
• Location
• Active Power
• Reactive Power
• Frequency
Wind Turbine
• location
• power
• wind speed
• pitch angle
11. What is a Context Broker?
§ NGSI-LD API servers are usually referred as Context Brokers
§ A Context Broker is associated to a transport end point
§ A Context Broker does not necessarily hold the data you are looking for but “knows” how that
data can be obtained. Strictly speaking, they provide access to data (using the NGSI-LD API)
10
Application/Service
Pallet
• Id
• product
• Items quantity
• layers
• Size
• weight
Operator
• Id
• Location
• Assigned task
• Profile
Transport robot
• Id
• location
• speed
• transported items
• destination
FIWARE NGSI API
Context Broker
12. What categories of Reference Architectures we may consider?
11
Vertical Smart Solutions Smart Organizations
• Cities (e.g., Smart Traffic)
• Farms (e.g., Smart Watering)
• Factories (e.g., Smart Welding)
• Smart Cities
• Smart Farms
• Smart Factories
13. What categories of Reference Architectures we may consider?
12
Vertical Smart Solutions Smart Organizations
• Cities (e.g., Smart Traffic)
• Farms (e.g., Smart Watering)
• Factories (e.g., Smart Welding)
• Smart Cities
• Smart Farms
• Smart Factories
14. Vertical Smart Solution for Cities: Reference Architecture
§ Four major layers:
• Data acquisition
• Data management
• Data processing, analysis
and visualization
• Application layer
§ Ability to integrate FIWARE IoT
Agents or 3rd party IoT platforms
§ Integration with most popular
Apache processing engines
(Spark, Flink, Hadoop)
§ Advanced web mashup and
Business Intelligent components
13
15. Vertical Smart Solution for Farms: Reference Architecture
§ Four major layers:
• Data acquisition
• Data management
• Data processing, analysis
and visualization
• Application layer
§ Ability to integrate FIWARE IoT
Agents or 3rd party IoT platforms
§ Integration with most popular
Apache processing engines
(Spark, Flink, Hadoop)
§ Advanced web mashup and
Business Intelligent components
14
16. Vertical Smart Solution for Factories: Reference Architecture
§ Four major layers:
• Data acquisition
• Data management
• Data processing, analysis
and visualization
• Application layer
§ Ability to integrate FIWARE IoT
Agents or 3rd party IoT platforms
§ Integration with most popular
Apache processing engines
(Spark, Flink, Hadoop)
§ Advanced web mashup and
Business Intelligent components
15
17. Vertical Smart Solution for Energy: Reference Architecture
§ Four major layers:
• Data acquisition
• Data management
• Data processing, analysis
and visualization
• Application layer
§ Ability to integrate FIWARE IoT
Agents or 3rd party IoT platforms
§ Integration with most popular
Apache processing engines
(Spark, Flink, Hadoop)
§ Advanced web mashup and
Business Intelligent components
16
24. Conclusions (1 of 2)
▪ How to materialize the concept of Digital Twin?
• Digital Twins match entities representing real and digital world
objects characterized by properties, describing the context
• We can leverage on a standard API to get access to info of a
Digital Twin (ETSI NGSI-LD) supported by multiple open
source implementations (FIWARE)
§ A Digital Twin representation of Context brings the
basis for architectures integrating multiple technologies:
• Integration of data from IoT devices / Robotic systems as well
as information systems
• Distributed Ledger / Blockchain bringing a mechanism to
register transactions on Digital Twins – trustworthy accounting,
transparency, forensics
• Digital Twin info as “raw material” over which processing (e.g.,
AI), analysis (BigData) visualization and simulation applies but
also as “material” where results are shared
• Digital Twin info as “coin of exchange” for Data Sharing,
Brokering and Trading (Data Marketplace)
• Digital Twin Data Access and Usage Control required
23
25. Conclusions (2 of 2)
▪ Architectures gravitating around Digital Twin / Context
Information Management are applicable to:
▪ Vertical Smart Solutions solving specific challenges
▪ Whole Organizations, turning them into smart organizattons
following a “System of Systems” approach
▪ Properties in a System of Systems architecture:
• Extensibility (new systems can be added easily)
• Replaceability (systems can be replaced)
• Loose coupling (systems can evolve independently)
• Low intrusiveness (systems do not need to change)
• Recursiveness (systems of systems at different levels)
▪ Ingredients for trusted exchange of data among
organizations:
▪ IDS Connectors providing a Security Framework
▪ NGSI-LD and standard-based data models as “coin of exchange”
24