The document discusses how FIWARE components can be used to implement the concepts and architecture of the Industrial Data Space (IDS). Specifically: - FIWARE Context Brokers can be used as the core component to implement IDS Connectors for both external and internal data connections. - FIWARE Generic Enablers like IoT Agents, processing engines, and the Context Broker can integrate data from various industrial systems and applications via IDS Connectors. - FIWARE and IDS will collaborate on domain data models and specifications to ensure their architectures remain compatible and that FIWARE can provide a valid open source implementation of the IDS architecture.

1. FIWARE implementation of IDS concepts
Juanjo Hierro
FIWARE Foundation CTO
juanjose.hierro@fiware.org, @JuanjoHierro, @FIWARE
www.slideshare.net/JuanjoHierro

2. Materializing the IDS Architecture using FIWARE
1

3. Materializing the IDS Architecture using FIWARE
2
FIWARE Context
Broker components
can be used as core
component of IDS
Connectors
Extended CKAN
Data Publication
Platform
Both External and
Internal IDS Connectors
are implemented using
FIWARE Context Broker
components
Docker-based tools relying on
Docker Hub Services enabling
automated deployment and
configuration of Data Apps
standard vocabularies
are being proposed at
https://www.fiware.org
/data-models
Data Apps map to
NGSI adapters or
Apps processing
context information
Interface between IDS
connectors based on
FIWARE NGSI

4. IDS and FIWARE: collaboration to accelerate delivery of a
common vision
§ It is a common goal that a valid open source implementation of
the IDS Architecture can be based on FIWARE, compatible with
FIWARE Architecture principles:
• IDS does not intend to incorporate elements within the
specification of the IDS Architecture that prevent
development of a valid implementation of such
architecture using core FIWARE Generic Enablers
• the FIWARE Foundation will work towards making sure
that core FIWARE Generic Enablers can be integrated
together to build a valid open source implementation of the
IDS Architecture
§ Both organizations will:
• collaborate on the development of domain data models
• collaborate on and communicate about the development of
their respective specifications and architectures to keep
them compatible
3

5. End to end communication through IDS Connectors
4
FIWARE NGSI

6. FIWARE
Context Broker
(Orion)
PDP / PAP
(AuthZForce)
PEP
CDR gen
Biz Framework
IdM
(Keyrock)
Proxy
(Wilma)
Federation
router
IoT Agent 1
IoT Agent m
System Adapter 1
System Adapter n IDS Connector
token OK + user info
XACML
request
(req +
user info)
OK
CDR
IDS Connector implementation: Data Provider side
FIWARE NGSI
FIWARE NGSI

7. PDP / PAP
(AuthZForce)
PEP
CDR gen
Biz Framework
IdM
(Keyrock)
token OK + user info
XACML
request
(req + user
info)
OK
CDR
FIWARE
Context Broker
(Orion)
Proxy
(Wilma)
Federation
router
processing engine 1
processing engine m
Data sink 1
Data sink nIDS Connector
Cygnus
IDS Connector implementation: Data Consumer side
FIWARE NGSI
FIWARE NGSI

8. IoT
Agent
(MQTT)
Complex Event
Processing
Big Data
Algorithms
Smart Industry Management Services
IDAS Systems Adapters
cameras
and IoT sensors
deployed in shop floor
IdM&AccessControl
APIManagementand
BizFramework
Cyber-Physical Systems (CPS) in shop floor
Demand
Mngt
Supply
Mngt
Information systems
IDAS IoT Agents
KPIs
monitoring
Operation
Dashboards
Shopfloor
map
BI
plafform
(Knowage)
Mashup
platform
(Wirecloud)
FIWARE Context Broker
(Orion)
Processing Engines
(Flink, Hadoop, Spark, Storm, …)
AI
Algorithms
History
Data
Stream
IDS
Connector
3rd organizations
robotic systems
…
3D Printer
Machine
Welding
robots
IoT
Agent
(OPC-UA)
IoT
Agent
ROS-2
interf.
ROS-2
interf.
System
adapter
System
adapter
System
adapter
System
adapter
Fast RTPS
CMM
system
Transport
robots
Assembly
robots
Milling
Machine
… … … …
… … ……… …
…
Extended
3rd-party enabler
FIWARE GE
FIWARE GE module
FIWARE
Context Broker
IDS
Connector
Real-time
media
processing
(Kurento)

9. Thank you!
http://fiware.org
Follow @FIWARE on Twitter
Juanjo Hierro
FIWARE Foundation CTO
juanjose.hierro@fiware.org
www.slideshare.net/JuanjoHierro

10. FIWARE NGSI: Basic interaction
§ Context Producers publish context information by invoking the
updateContext operation on a Context Broker.
§ Context Consumers can retrieve context information by invoking the
queryContext operation on a Context Broker
9
Bus = “X”, location = (x, y)
updateContext
Context Producer
Context Consumer
queryContext
FIWARE Context Broker

11. FIWARE NGSI: Context Providers
§ Context Providers can be registered to the Context Broker as “holders” of
certain context information.
§ A Context Broker will invoke the queryContext or updateContext operations
exported by Context Providers whenever they are queried for, or asked to
update, context information they hold
10
Bus = “X”, location = (x, y)
queryContext / updateContext
Context Provider
(provider-x)
Context Consumer
queryContext / updateContext
registerContext (provider-x,
registration_data, duration, id)
)
FIWARE Context Broker

12. FIWARE NGSI: Subscription to notifications
§ Context Consumers can be subscribed to reception of context information
complying with certain conditions, using the subscribeContext operation a
ContextBroker exports. Such subscriptions may have a duration.
§ The Context Broker notifies updates on context information to subscribed
Context Consumers by invoking the notifyContext operation they export
11
Bus = “X”, next_stop = “A”, arrived = “Yes”
updateContext (context_info)
Context Producer
Context Consumer
(consumer1)
notifyContext (id, context_info)
Id = subscribeContext (consumer1,
condition, duration
)
FIWARE Context Broker