ddsf:public:guidebook:03_user:04_smartman
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ddsf:public:guidebook:03_user:04_smartman [2021/07/14 15:55] murphy ↷ Links adapted because of a move operation |
ddsf:public:guidebook:03_user:04_smartman [2021/07/14 16:17] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Use Case 3: Smart Manufacturing ====== | ====== Use Case 3: Smart Manufacturing ====== | ||
| [[ddsf:public:guidebook:03_user:start| Return to User Experiences]] | [[ddsf:public:guidebook:03_user:start| Return to User Experiences]] | ||
| - | |||
| - | * **<color #FF0000><todo @char>Please Review</todo></color>** | ||
| - | * **<color #FF0000><todo @DDSFmember>Please Review</todo></color>** | ||
| - | |||
| ===== Details ===== | ===== Details ===== | ||
| Line 108: | Line 104: | ||
| [[ddsf:public:guidebook:03_user:04_smartman| Return to the top]] | [[ddsf:public:guidebook:03_user:04_smartman| Return to the top]] | ||
| - | These are the problems and [[ddsf:private:guidebook:06_append:glossary:u:use_case|use cases]] on managing the sensor nodes. | + | These are the problems and [[ddsf:public:guidebook:06_append:glossary:u:use_case|use cases]] on managing the sensor nodes. |
| The use cases can range from | The use cases can range from | ||
| Line 149: | Line 145: | ||
| * The cotrast of DDS as compared with other communication standards. | * The cotrast of DDS as compared with other communication standards. | ||
| - | * Location transparent –hides the [[ddsf:public:guidebook:06_append:glossary:n:nettopo]]. DDS supports the [[ddsf:private:guidebook:06_append:glossary:u:unicast]] and [[ddsf:public:guidebook:06_append:glossary:m:multicast]] [[ddsf:public:guidebook:06_append:glossary:d:discovery|discovery]] (see [[ddsf:public:guidebook:06_append:04_otherstds:ietf:mult]]). If the DDS nodes are connected to the same [[ddsf:public:guidebook:06_append:glossary:h:hub|hub]] or managed switch and the network topology does not cross the managed switch, and they use a default configuration, the nodes find each other using a Multicast form of discovery itself | + | * Location transparent –hides the [[ddsf:public:guidebook:06_append:glossary:n:nettopo]]. DDS supports the [[ddsf:public:guidebook:06_append:glossary:u:unicast]] and [[ddsf:public:guidebook:06_append:glossary:m:multicast]] [[ddsf:public:guidebook:06_append:glossary:d:discovery|discovery]] (see [[ddsf:public:guidebook:06_append:04_otherstds:ietf:mult]]). If the DDS nodes are connected to the same [[ddsf:public:guidebook:06_append:glossary:h:hub|hub]] or managed switch and the network topology does not cross the managed switch, and they use a default configuration, the nodes find each other using a Multicast form of discovery itself |
| * Less or no deployment configuration since the applications are familiar with the global data space, configuration is not required because if nodes need the data is required they can access directly from the global data space rather than requesting the peer nodes directly. | * Less or no deployment configuration since the applications are familiar with the global data space, configuration is not required because if nodes need the data is required they can access directly from the global data space rather than requesting the peer nodes directly. | ||
| * Scalable from sensor to cloud, from the automation pyramid, the DDS Data bus will sit at any level of the Automation Pyramid and provide the data to the requested level. And here IT systems will not provide their own data system so the real-time and IT systems do not diverge and the system can be scaled | * Scalable from sensor to cloud, from the automation pyramid, the DDS Data bus will sit at any level of the Automation Pyramid and provide the data to the requested level. And here IT systems will not provide their own data system so the real-time and IT systems do not diverge and the system can be scaled | ||
| * [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies]], DDS allows the applications define and share the user data with a controlled Quality of Service such as performance, scalability, reliability, [[ddsf:public:guidebook:06_append:glossary:d:durability|durability]], and security | * [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies]], DDS allows the applications define and share the user data with a controlled Quality of Service such as performance, scalability, reliability, [[ddsf:public:guidebook:06_append:glossary:d:durability|durability]], and security | ||
| - | * DDS + [[ddsf:private:guidebook:06_append:glossary:t:tsn]] can replace legacy field-bus over the years. TSN is a set of [[ddsf:public:guidebook:06_append:glossary:i:ieee| IEEE]] standards that aim to provide the time sensitive data transfusion over the [[ddsf:public:guidebook:06_append:glossary:e:ethernet|Ethernet]] networks which works in [[ddsf:public:guidebook:06_append:glossary:o:osi]] layers 1 and 2 (i.e., [[ddsf:private:guidebook:06_append:glossary:t:transportlayer]] and [[ddsf:public:guidebook:06_append:glossary:p:physicallayer]]) and DDS works in layers 3 to 6 (i.e., [[ddsf:public:guidebook:06_append:glossary:s:sessionlayer]], [[ddsf:public:guidebook:06_append:glossary:n:netlayer]], [[ddsf:public:guidebook:06_append:glossary:d:datalinklayer]], [[ddsf:public:guidebook:06_append:glossary:p:presentlayer]]) which means that QoS settings in the application take care of the data to use a real-time model in higher OSI layers and TSN can take care of timing at the lower OSI levels ensures that timing is guaranteed on the wire. | + | * DDS + [[ddsf:public:guidebook:06_append:glossary:t:tsn]] can replace legacy field-bus over the years. TSN is a set of [[ddsf:public:guidebook:06_append:glossary:i:ieee| IEEE]] standards that aim to provide the time sensitive data transfusion over the [[ddsf:public:guidebook:06_append:glossary:e:ethernet|Ethernet]] networks which works in [[ddsf:public:guidebook:06_append:glossary:o:osi]] layers 1 and 2 (i.e., [[ddsf:public:guidebook:06_append:glossary:t:transportlayer]] and [[ddsf:public:guidebook:06_append:glossary:p:physicallayer]]) and DDS works in layers 3 to 6 (i.e., [[ddsf:public:guidebook:06_append:glossary:s:sessionlayer]], [[ddsf:public:guidebook:06_append:glossary:n:netlayer]], [[ddsf:public:guidebook:06_append:glossary:d:datalinklayer]], [[ddsf:public:guidebook:06_append:glossary:p:presentlayer]]) which means that QoS settings in the application take care of the data to use a real-time model in higher OSI layers and TSN can take care of timing at the lower OSI levels ensures that timing is guaranteed on the wire. |
| Line 184: | Line 180: | ||
| - **Data Ingest and Storage** - Real-time data ingest, [[ddsf:public:guidebook:06_append:glossary:b:bigdata]] platform | - **Data Ingest and Storage** - Real-time data ingest, [[ddsf:public:guidebook:06_append:glossary:b:bigdata]] platform | ||
| - **Data Processing** - Real-time processing, in-memory processing | - **Data Processing** - Real-time processing, in-memory processing | ||
| - | - **Machine Learning** - [[ddsf:public:guidebook:06_append:glossary:m:machinelearn]], [[ddsf:public:guidebook:06_append:glossary:s:supervislearning| Supervised]] / [[ddsf:private:guidebook:06_append:glossary:u:unsuperlearn| Unsupervised Learning]] | + | - **Machine Learning** - [[ddsf:public:guidebook:06_append:glossary:m:machinelearn]], [[ddsf:public:guidebook:06_append:glossary:s:supervislearning| Supervised]] / [[ddsf:public:guidebook:06_append:glossary:u:unsuperlearn| Unsupervised Learning]] |
| - **Analytics** - Data visualization, SQL Analytics | - **Analytics** - Data visualization, SQL Analytics | ||
| Line 286: | Line 282: | ||
| * Integratability | * Integratability | ||
| - | * [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:ddsi_rtps| DDS Interoperability Wire Protocol (DDSI-RTPS) ]] allows for data to be transferred in efficient, binary, cross vendor standardized messages. XTypes allows for the addition, remove, or modify elements in the data model of each sensor node during the runtime. This helps balance the tradeoffs of efficiency, vulnerability and compatibility of the sensor nodes over time. It provides a fast, higher frequency exchange of data in the range of sub-millisecond allowing the nodes to publish the raw data in real-time. It can run over [[ddsf:public:guidebook:06_append:glossary:m:multicast]]. Data can be transported in frames or in streams using [[ddsf:private:guidebook:06_append:glossary:u:udp]] or [[ddsf:public:guidebook:06_append:glossary:i:ip]]. In the case of manufacturing use case, there is a need to get lower granular data and in Smart City use case, there is a need to get data in "more" real-time. | + | * [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:ddsi_rtps| DDS Interoperability Wire Protocol (DDSI-RTPS) ]] allows for data to be transferred in efficient, binary, cross vendor standardized messages. XTypes allows for the addition, remove, or modify elements in the data model of each sensor node during the runtime. This helps balance the tradeoffs of efficiency, vulnerability and compatibility of the sensor nodes over time. It provides a fast, higher frequency exchange of data in the range of sub-millisecond allowing the nodes to publish the raw data in real-time. It can run over [[ddsf:public:guidebook:06_append:glossary:m:multicast]]. Data can be transported in frames or in streams using [[ddsf:public:guidebook:06_append:glossary:u:udp]] or [[ddsf:public:guidebook:06_append:glossary:i:ip]]. In the case of manufacturing use case, there is a need to get lower granular data and in Smart City use case, there is a need to get data in "more" real-time. |
| * The users in multiple layers can access the data in the way they need allowing them to associate the data they need for background analytics and other roles such as plant managers, business users, or end customers require more customized data views. This customization of views is part of the Extensible and Dynamic Topic Types for DDS (DDS-XTypes) Specification. | * The users in multiple layers can access the data in the way they need allowing them to associate the data they need for background analytics and other roles such as plant managers, business users, or end customers require more customized data views. This customization of views is part of the Extensible and Dynamic Topic Types for DDS (DDS-XTypes) Specification. | ||
| * The standard DDS Model has extended its usage to allow Web Object Model to monitor and control the Sensor Nodes from the live dashboard using the REST API defined in the [[ddsf:public:guidebook:06_append:01_family_of_standards:04_gate:ddsweb| Web-Enabled DDS (DDS-WEB) Specification]] for the managers sitting in the cloud allowing them to access the data using the|Web Enabled DDS API to access the Global Dataspace or the databus. | * The standard DDS Model has extended its usage to allow Web Object Model to monitor and control the Sensor Nodes from the live dashboard using the REST API defined in the [[ddsf:public:guidebook:06_append:01_family_of_standards:04_gate:ddsweb| Web-Enabled DDS (DDS-WEB) Specification]] for the managers sitting in the cloud allowing them to access the data using the|Web Enabled DDS API to access the Global Dataspace or the databus. | ||
| Line 292: | Line 288: | ||
| * Security | * Security | ||
| - | * [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:dds_security| DDS Security (DDS-SECURITY) ]] allows to define and enforce configurations to handle the sensor data to be encrypted or transmitted confidentially or [[ddsf:public:guidebook:06_append:glossary:a:authenticity|authenticity]] for reading the data without any additional overhead. In both the chemical and the Smart City use cases, security is a high priority. DDS-Security allows for the import and definition the configuration to handle the sensitive data to be more inclusive or transmitted confidently with [[ddsf:public:guidebook:06_append:glossary:a:authentication|authentication]] required to read the data without any overhead, while consuming data from any layer within the automation pyramid (See Figure {{ref>pyramid}}). DDS-Security also supports multicast allowing for more efficient data transfer and without compromising performance. Using other security transport protocols like [[ddsf:private:guidebook:06_append:glossary:t:tls]] or [[ddsf:public:guidebook:06_append:glossary:d:dtls]] which do not have multicast support. | + | * [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:dds_security| DDS Security (DDS-SECURITY) ]] allows to define and enforce configurations to handle the sensor data to be encrypted or transmitted confidentially or [[ddsf:public:guidebook:06_append:glossary:a:authenticity|authenticity]] for reading the data without any additional overhead. In both the chemical and the Smart City use cases, security is a high priority. DDS-Security allows for the import and definition the configuration to handle the sensitive data to be more inclusive or transmitted confidently with [[ddsf:public:guidebook:06_append:glossary:a:authentication|authentication]] required to read the data without any overhead, while consuming data from any layer within the automation pyramid (See Figure {{ref>pyramid}}). DDS-Security also supports multicast allowing for more efficient data transfer and without compromising performance. Using other security transport protocols like [[ddsf:public:guidebook:06_append:glossary:t:tls]] or [[ddsf:public:guidebook:06_append:glossary:d:dtls]] which do not have multicast support. |
ddsf/public/guidebook/03_user/04_smartman.1626292502.txt.gz · Last modified: 2021/07/14 15:55 by murphy
