Introducing the New MagicDraw
Plug-In for RTI Connext DDS:
Industrial IoT Meets SysML
István Ráth, PhD
CEO, IncQuery Labs Ltd.
Hamburg, 2019
RTI Connext DDS
Content by Gerardo Pardo-Castellote, Ph.D.
Chief Technology Officer, RTI
©2018 Real-Time Innovations, Inc. Confidential.
DDS and the Industrial Internet of Things
• Reliability: Severe consequences if
offline for 5ms (or 5 min)
• Real-time: measure in ms or µs
• Interface scale: 10+
applications/teams
• Dataflow complexity:
data has many destinations
• Architecture: Next generation IIoT
Deployed in 1000s of Systems Industrial IoT Systems
Industries: Energy, Industrial Control, Transportation, Healthcare, Defense
3+ Yes?
Typical Deployment
Sensing
Planning
Vehicle
Control
Logging
CONNEXT DDS DATABUS
Traffic Maps
Error
Management
Situation
Awareness
Situation
Awareness
Cameras,
LIDAR, Radar…
Cameras,
LIDAR, Radar…
Cameras,
LIDAR, Radar…
Data Fusion Cameras,
LIDAR, Radar…
Localization
Vehicle
Platform
Visualization Navigation
CONNEXT DDS DATABUS
©2018 Real-Time Innovations, Inc.
Siemens Wind Power Distributed Control
• Wind turbine farms can include 500
turbines, 100m blades
• Gust control across the array
requires fast communications with
dynamic, selective filtering
• DDS enables large, distributed
intelligent machines
Audi Hardware-in-the-loop simulation
• Audi hardware-in-the-loop simulation feeds
realistic data to components for testing
• The system offers plug-n-play between
simulation vendor solutions
• RTI software enables a modular test environment
that scales to work with hundreds of devices
GE Transportation
©2017 Real-Time Innovations, Inc.
GE Transportation freight and
passenger locomotives require safe
and reliable control, signaling, and
communications
The system is being developed using
SysML, Simulink, and DDS
MagicDraw Plug-in for Connext DDS
DDS Toolchain
IDL
DDS-XML
RTI SDK
C / C++ /
Java / …
System Designer
DDS Concepts
Topic A
QoS
Topic C
QoS
Topic D
QoS
DDS DOMAIN
Persistence
Service
Recording
Service
CRUD operations
Topic B : “Turbine State”
Source (Key) Speed Power Phase
WPT1 37.4 122.0 -12.20
WPT2 10.7 74.0 -12.23
WPTN 50.2 150.07 -11.98
QoS
DDS-XML
• Complements IDL specifications
with configuration and
deployment concepts
• Defines
• Types, Topics,
• Writers, Readers,
• Applications
• QoS profiles
• Standard and vendor-specific
flavors
Extended DDS Toolchain
DDS-XML RTI SDK
C / C++ /
Java / …
Automatically
generate DDS-XML
configuration
• Integrated system communication architecture
• The power of SysML: modeling and validation
SysML Profile for Connext DDS
• Interface definitions
• Data Types
• DDS Topics
• Application Definition
• DDS Domains, Participants
• Ports àWriters, Readers
• Quality of Service Definitions
• DDS QoS Profiles
Designing Applications
Custom
types
DDS-
XTYPES
Complex
types
DDS Topics
MyDomain: Domain
DataTypes
topics
domainParticipants
DP: Block
<<domainParticipant>>
SysML model
dp1: Dp dp2: Dp
<domain_library name="MyDomainLibrary">
<domain name= " MyDomain" domain_id="1">
<register_type name= " MyType" type_ref= "M::MyType">
<topic name="MyTopic" register_type_ref="MyType"/>
</domain>
</domain_library>
<participant_library name="participants">
<domain_participant name="dp1_dp" domain_ref="MyDomain">
<subscriber name="p1_subscriber">
<data_writer name="p1" topic_ref="MyTopic"/>
</subscriber>
</domain_participant>
<domain_participant name="dp2_dp" domain_ref="MyDomain">
<subscriber name="p1_subscriber">
<data_writer name="p1" topic_ref="MyTopic"/>
</subscriber>
</domain_participant>
</participant_library>
MyTopic
type
MyDomainLibrary
<<instance>> <<instance>>
Part Property instances of the
Domain Participant result in
DDS DP instances
<<ddsDataPort>>
MyDomain: Domain
DataTypes
topics
domainParticipants
DP: Block
<<domainParticipant>>
SysML model
dp1: Dp dp2: Dp
<domain_library name="MyDomainLibrary">
<domain name= " MyDomain" domain_id="1">
<register_type name= " MyType" type_ref= "M::MyType">
<topic name="MyTopic" register_type_ref="MyType"/>
</domain>
</domain_library>
<participant_library name="participants">
<domain_participant name="dp1_dp" domain_ref="MyDomain">
<subscriber name="p1_subscriber">
<data_writer name="p1" topic_ref="MyTopic"/>
</subscriber>
</domain_participant>
<domain_participant name="dp2_dp" domain_ref="MyDomain">
<subscriber name="p1_subscriber">
<data_writer name="p1" topic_ref="MyTopic"/>
</subscriber>
</domain_participant>
</participant_library>
MyTopic
type
MyDomainLibrary
<<instance>> <<instance>>
<<ddsDataPort>>
Domain-Topic relationships
explicitly defined
DDS Data Ports will result in
Data Readers and Writers
depending on SysML direction
DP_A
~ p1
p2
~p3
p4
np1
np2
DomainParticipant_DP_A
Subscriber_DP_A
Subscriber_np1
Publisher_np1
dataReader_p1
dataReader_p3
dataWriter_p2
dataWriter_p4
SysML DDS XML
Subscribers and
Publishers derived
from nested Ports
Data Reader/Writer
nature calculated
from port direction
DataTypes
DP: Block
<<domainParticipant>>
SysML model
dp1: Dp dp2: Dp
MyTopic
type
<<instance>>
p1
QoS Profiles
QoSAssignment
p2
QoSAssignment
QoSAssignment
p2
<participant_library name="participants">
<domain_participant name="dp1_dp" domain_ref="MyDomain">
<subscriber name="p1_subscriber">
<data_writer name="p1" topic_ref="MyTopic">
<datareader_qos base_name="p1"/>
</data_writer>
</subscriber>
</domain_participant>
<domain_participant name="dp2_dp" domain_ref="MyDomain">
<subscriber name="p1_subscriber">
<data_writer name="p1" topic_ref="MyTopic"/>
</subscriber>
</domain_participant>
</participant_library>
<<instance>>
QoS Assignments
<<ddsDataPort>>
QoS profile is only
applied to dp1
QoS Assignment
using type and
instance level
Generic Tables
• Domain relationship definition
• QoS Assignment definition
Takeaways
• Use of proven, standard DDS connectivity databus enables robust and
secure deployment of distributed applications and components
• New MagicDraw Plugin for Connext DDS integrates SysML and DDS
• Plugin enables going from SysML design to implementation and
deployment on a distributed system
More information
• Further information
• Visit the IncQuery Labs booth for discussions any time
• Roadmap
• Demo available now for evaluation
• First limited release with 19.0 SP3, with support for RTI Connext DDS 5.3 & 6
• Pointers
• http://rti.com
• http://portals.omg.org/dds/

Introducing the New MagicDraw Plug-In for RTI Connext DDS: Industrial IoT Meets SysML

  • 1.
    Introducing the NewMagicDraw Plug-In for RTI Connext DDS: Industrial IoT Meets SysML István Ráth, PhD CEO, IncQuery Labs Ltd. Hamburg, 2019
  • 2.
    RTI Connext DDS Contentby Gerardo Pardo-Castellote, Ph.D. Chief Technology Officer, RTI ©2018 Real-Time Innovations, Inc. Confidential.
  • 3.
    DDS and theIndustrial Internet of Things • Reliability: Severe consequences if offline for 5ms (or 5 min) • Real-time: measure in ms or µs • Interface scale: 10+ applications/teams • Dataflow complexity: data has many destinations • Architecture: Next generation IIoT Deployed in 1000s of Systems Industrial IoT Systems Industries: Energy, Industrial Control, Transportation, Healthcare, Defense 3+ Yes?
  • 4.
    Typical Deployment Sensing Planning Vehicle Control Logging CONNEXT DDSDATABUS Traffic Maps Error Management Situation Awareness Situation Awareness Cameras, LIDAR, Radar… Cameras, LIDAR, Radar… Cameras, LIDAR, Radar… Data Fusion Cameras, LIDAR, Radar… Localization Vehicle Platform Visualization Navigation CONNEXT DDS DATABUS ©2018 Real-Time Innovations, Inc.
  • 5.
    Siemens Wind PowerDistributed Control • Wind turbine farms can include 500 turbines, 100m blades • Gust control across the array requires fast communications with dynamic, selective filtering • DDS enables large, distributed intelligent machines
  • 6.
    Audi Hardware-in-the-loop simulation •Audi hardware-in-the-loop simulation feeds realistic data to components for testing • The system offers plug-n-play between simulation vendor solutions • RTI software enables a modular test environment that scales to work with hundreds of devices
  • 7.
    GE Transportation ©2017 Real-TimeInnovations, Inc. GE Transportation freight and passenger locomotives require safe and reliable control, signaling, and communications The system is being developed using SysML, Simulink, and DDS
  • 8.
  • 9.
    DDS Toolchain IDL DDS-XML RTI SDK C/ C++ / Java / … System Designer
  • 10.
    DDS Concepts Topic A QoS TopicC QoS Topic D QoS DDS DOMAIN Persistence Service Recording Service CRUD operations Topic B : “Turbine State” Source (Key) Speed Power Phase WPT1 37.4 122.0 -12.20 WPT2 10.7 74.0 -12.23 WPTN 50.2 150.07 -11.98 QoS
  • 11.
    DDS-XML • Complements IDLspecifications with configuration and deployment concepts • Defines • Types, Topics, • Writers, Readers, • Applications • QoS profiles • Standard and vendor-specific flavors
  • 12.
    Extended DDS Toolchain DDS-XMLRTI SDK C / C++ / Java / … Automatically generate DDS-XML configuration • Integrated system communication architecture • The power of SysML: modeling and validation
  • 13.
    SysML Profile forConnext DDS • Interface definitions • Data Types • DDS Topics • Application Definition • DDS Domains, Participants • Ports àWriters, Readers • Quality of Service Definitions • DDS QoS Profiles
  • 14.
  • 15.
    MyDomain: Domain DataTypes topics domainParticipants DP: Block <<domainParticipant>> SysMLmodel dp1: Dp dp2: Dp <domain_library name="MyDomainLibrary"> <domain name= " MyDomain" domain_id="1"> <register_type name= " MyType" type_ref= "M::MyType"> <topic name="MyTopic" register_type_ref="MyType"/> </domain> </domain_library> <participant_library name="participants"> <domain_participant name="dp1_dp" domain_ref="MyDomain"> <subscriber name="p1_subscriber"> <data_writer name="p1" topic_ref="MyTopic"/> </subscriber> </domain_participant> <domain_participant name="dp2_dp" domain_ref="MyDomain"> <subscriber name="p1_subscriber"> <data_writer name="p1" topic_ref="MyTopic"/> </subscriber> </domain_participant> </participant_library> MyTopic type MyDomainLibrary <<instance>> <<instance>> Part Property instances of the Domain Participant result in DDS DP instances <<ddsDataPort>>
  • 16.
    MyDomain: Domain DataTypes topics domainParticipants DP: Block <<domainParticipant>> SysMLmodel dp1: Dp dp2: Dp <domain_library name="MyDomainLibrary"> <domain name= " MyDomain" domain_id="1"> <register_type name= " MyType" type_ref= "M::MyType"> <topic name="MyTopic" register_type_ref="MyType"/> </domain> </domain_library> <participant_library name="participants"> <domain_participant name="dp1_dp" domain_ref="MyDomain"> <subscriber name="p1_subscriber"> <data_writer name="p1" topic_ref="MyTopic"/> </subscriber> </domain_participant> <domain_participant name="dp2_dp" domain_ref="MyDomain"> <subscriber name="p1_subscriber"> <data_writer name="p1" topic_ref="MyTopic"/> </subscriber> </domain_participant> </participant_library> MyTopic type MyDomainLibrary <<instance>> <<instance>> <<ddsDataPort>> Domain-Topic relationships explicitly defined DDS Data Ports will result in Data Readers and Writers depending on SysML direction
  • 17.
    DP_A ~ p1 p2 ~p3 p4 np1 np2 DomainParticipant_DP_A Subscriber_DP_A Subscriber_np1 Publisher_np1 dataReader_p1 dataReader_p3 dataWriter_p2 dataWriter_p4 SysML DDSXML Subscribers and Publishers derived from nested Ports Data Reader/Writer nature calculated from port direction
  • 18.
    DataTypes DP: Block <<domainParticipant>> SysML model dp1:Dp dp2: Dp MyTopic type <<instance>> p1 QoS Profiles QoSAssignment p2 QoSAssignment QoSAssignment p2 <participant_library name="participants"> <domain_participant name="dp1_dp" domain_ref="MyDomain"> <subscriber name="p1_subscriber"> <data_writer name="p1" topic_ref="MyTopic"> <datareader_qos base_name="p1"/> </data_writer> </subscriber> </domain_participant> <domain_participant name="dp2_dp" domain_ref="MyDomain"> <subscriber name="p1_subscriber"> <data_writer name="p1" topic_ref="MyTopic"/> </subscriber> </domain_participant> </participant_library> <<instance>> QoS Assignments <<ddsDataPort>> QoS profile is only applied to dp1 QoS Assignment using type and instance level
  • 19.
    Generic Tables • Domainrelationship definition • QoS Assignment definition
  • 20.
    Takeaways • Use ofproven, standard DDS connectivity databus enables robust and secure deployment of distributed applications and components • New MagicDraw Plugin for Connext DDS integrates SysML and DDS • Plugin enables going from SysML design to implementation and deployment on a distributed system
  • 21.
    More information • Furtherinformation • Visit the IncQuery Labs booth for discussions any time • Roadmap • Demo available now for evaluation • First limited release with 19.0 SP3, with support for RTI Connext DDS 5.3 & 6 • Pointers • http://rti.com • http://portals.omg.org/dds/