Differences

This shows you the differences between two versions of the page.

--- ddsf:public:guidebook:03_user:07_gva [2021/03/29 12:25]
murphy
+++ ddsf:public:guidebook:03_user:07_gva [2021/10/29 02:03] (current)
char
@@ Line 1: / Line 1: @@
-====== Use Case 5: DDS in General Vehicle Architecture (GVA) ======
+====== Use Case 5: General Vehicle Architecture (GVA) ======
-[[ddsf:private:guidebook:03_user| Return to User Experiences]]
+[[ddsf:public:guidebook:03_user:start| Return to User Experiences]]
-<color #FF0000><todo @nick>Please Review</todo></color>
 ===== Details =====
@@ Line 15: / Line 13: @@
 ===== Abstract =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
-[[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] as an enabler for armoured fighting vehicle equipment and systems integration.
+[[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] as an enabler for armoured fighting vehicle equipment and systems integration.
 In service and future defense vehicle systems comprise an increasing range of attached equipment and systems. These require frequent refresh and addition to mitigate emerging threats and maintain operational edge.
@@ Line 24: / Line 22: @@
 The seminar will explain the use of DDS using production examples as a key part of the GVA to provide platform management systems, and further up the value chain to platform mission systems and extensions to secondary platforms such as unmanned ground vehicles.
-====== Presentation =====
+===== Presentation =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 ===== Seminar Content =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /* 3:31*/
@@ Line 35: / Line 33: @@
 In the next 20 minutes, this is going to be a challenge to get through all of this. I am going to explain some of the challenges around integration within modern defense vehicles. Why software is important in that role and I think you can all recognize that.
-A bit about the General Vehicle Architecture standard, where did it come from? how does it use [[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]]? and Why does it use DDS?
+A bit about the General Vehicle Architecture standard, where did it come from? how does it use [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]]? and Why does it use DDS?
 Something that is important to me, in all of this is what does the user get out of the implementation with DDS and some ideas of what we can use within the DDS world next in this problem space and a bit of context.
@@ Line 41: / Line 39: @@
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-10_at_9.41.34_am.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-10_at_9.41.34_am.png?700  |}}
 <caption>Seminar Content</caption>
 </figure>
@@ Line 47: / Line 45: @@
 ===== Defence vehicle integration challenges =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /* 4:16 */
@@ Line 78: / Line 76: @@
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-10_at_9.44.36_am.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-10_at_9.44.36_am.png?700  |}}
 <caption>Picture of a UK Panther; Defense vehicle integration challenges</caption>
 </figure>
@@ Line 84: / Line 82: @@
 ===== Software is essential =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*6:21*/
 ^Hardware|<WRAP>
@@ Line 106: / Line 104: @@
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-10_at_9.51.43_am.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-10_at_9.51.43_am.png?700  |}}
 <caption>Pitcure of a UK 'Warrior' vehicle; Software is essential to exploit open standards based vehicle architectures</caption>
 </figure>
 ===== (NATO) Generic Vehicle Architecture Components =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 GVA is the UK/Australian mandated standard for OPEN vehicle
@@ Line 118: / Line 116: @@
 It covers:
 ^How to connect equipment|<WRAP>Power/ Ethernet</WRAP>|<WRAP>Mandates how to connect, using ethernet or power method.</WRAP>|
-^How to communicate|<WRAP>[[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] messaging</WRAP>|<WRAP>Mandates how to communicate DDS Messages, also DDS is mandated in the GVA</WRAP>|
+^How to communicate|<WRAP>[[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] messaging</WRAP>|<WRAP>Mandates how to communicate DDS Messages, also DDS is mandated in the GVA</WRAP>|
 ^How to describe items|<WRAP>Land Data Model (LDM)</WRAP>|<WRAP>Very strict rules on how to describe data moving around DDS(The Land Data Mdoel)</WRAP>|
-^System look and feel|<WRAP>[[ddsf:private:guidebook:06_append:glossary:h:hmi|HMI]] – Not in NGVA</WRAP>|<WRAP>Guidelines for the look and feel for the users, not mandated because you don't know what's coming in the future</WRAP>|
+^System look and feel|<WRAP>[[ddsf:public:guidebook:06_append:glossary:h:hmi|HMI]] – Not in NGVA</WRAP>|<WRAP>Guidelines for the look and feel for the users, not mandated because you don't know what's coming in the future</WRAP>|
 ^Storage of diagnostic data & Alarms|<WRAP>HUMS</WRAP>|<WRAP>Storage of diagnostic data and alarms to help the user.</WRAP>|
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_11.40.23_am.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_11.40.23_am.png?700  |}}
 <caption>(NATO) Generic Vehicle Architecture Components</caption>
 </figure>
 ===== Why (N)GVA uses DDS =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*9:55*/
-Both the UK [[ddsf:private:guidebook:06_append:glossary:m:mod|Ministry of Defense (MOD)]] and the [[ddsf:private:guidebook:06_append:glossary:n:north_atlantic_treaty_organization|North American Treaty Organization (NATO)]] require the use of [[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]].
+Both the UK [[ddsf:public:guidebook:06_append:glossary:m:mod|Ministry of Defense (MOD)]] and the [[ddsf:public:guidebook:06_append:glossary:n:north_atlantic_treaty_organization|North American Treaty Organization (NATO)]] require the use of [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]].
   * Enables system of systems approach (modularity and connectivity)
   * Platform agnostic
   * Mature, multi-vendor standard
-  * Minimises data on the wire via [[ddsf:private:guidebook:06_append:glossary:q:quality_of_service_qos_policies|Quality of Service (QoS)]]
+  * Minimises data on the wire via [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|Quality of Service (QoS)]]
   * Robust – no single point of failure
   * Efficient
@@ Line 145: / Line 143: @@
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_11.43.59_am.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_11.43.59_am.png?700  |}}
 <caption>Why (N)GVA uses DDS</caption>
 </figure>
 ===== GVA high level architecture and benefits =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*11:42*/
 Benefits:
-  * GVA [[ddsf:private:guidebook:06_append:glossary:h:hmi|HMI]]: human factors, shared SA, reduction in training need / skills fade (other platforms)
+  * GVA [[ddsf:public:guidebook:06_append:glossary:h:hmi|HMI]]: human factors, shared SA, reduction in training need / skills fade (other platforms)
   * Application: roles, security, alarms, HUMS etc. Systems Integration, (FC Comms), offboarding
-  * GVA messaging ([[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]]): through life & capability insertion, data interchange
+  * GVA messaging ([[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]]): through life & capability insertion, data interchange
   * Network – ease of access (SWAP)
@@ Line 162: / Line 160: @@
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_11.47.52_am.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_11.47.52_am.png?700  |}}
 <caption>GVA high level architecture and benefits</caption>
 </figure>
@@ Line 168: / Line 166: @@
 ===== GVA based vehicle data architecture =====
 /*13:45*/
-All vehicle systems connected to the data bus using GVA [[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] are resources. They can represent something as simple as a cabin light to as complex as another subsystem with multiple components and processors
+All vehicle systems connected to the data bus using GVA [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] are resources. They can represent something as simple as a cabin light to as complex as another subsystem with multiple components and processors
 ==== Resource ====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 A service resource is a specific type of resource, rather than a piece of hardware it is a service defined by GVA such as GVA Registry Service, Usage and Condition Monitoring Service.
 ==== GVA Service Resource ====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 A service resource is a specific type of resource, rather than a piece of hardware it is a service defined by GVA such as GVA Registry Service, Usage and Condition Monitoring Service.
 ==== Crew Intelligent Display (CID) ====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 A Crew Intelligent Display (CID) resource is a specific type of resource that includes the interface for a single screen or crew member.
 ==== Gateway Resource (J1939) ====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 A gateway resource is a specific type of resource that translates between another data bus (often legacy) and the GVA DDS data bus. The J1939 CanBUS gateway is of particular interest because while other legacy data buses may be replaced over time with GVA DDS compliant resources the underlying vehicle platform is like to continue to use j1939 as it is a well established protocol.
 ==== GVA DDS Data Bus ====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
-The GVA DDS data bus uses standard [[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] and GVA defined data types. Vehicle integrators are at liberty to add nonGVA DDS topics for any data required that is not defined by GVA
+The GVA DDS data bus uses standard [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] and GVA defined data types. Vehicle integrators are at liberty to add nonGVA DDS topics for any data required that is not defined by GVA
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_11.51.08_am.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_11.51.08_am.png?700  |}}
 <caption>GVA based vehicle data architecture</caption>
 </figure>
 ===== How GVA Makes Use of DDS (Highlights) =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*15:31*/
   * GVA Defines Data Types
   * GVA Defines a Type Naming Convention
   * GVA Defines a Topic Naming Convention
-  * GVA Defines [[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] Domain ID Allocation Rules
+  * GVA Defines [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] Domain ID Allocation Rules
-  * GVA Defines [[ddsf:private:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] Policies
+  * GVA Defines [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] Policies
-  * GVA Uses [[ddsf:private:guidebook:06_append:glossary:i:idl|IDL]] Inheritance to reduce the number of topics on the wire
+  * GVA Uses [[ddsf:public:guidebook:06_append:glossary:i:idl|IDL]] Inheritance to reduce the number of topics on the wire
-  * GVA Uses [[ddsf:private:guidebook:06_append:01_family_of_standards:01_core:dds_extensible_types_dds-xtypes|X-Types]] to aid backwards compatibility between versions
+  * GVA Uses [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:dds_extensible_types_dds-xtypes|X-Types]] to aid backwards compatibility between versions
   * GVA tools create IDL from the model for DDS implementation
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_12.03.53_pm.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_12.03.53_pm.png?700  |}}
 <caption>How GVA Makes Use of DDS (Highlights)</caption>
 </figure>
 ===== GVA data standards developed collaboratively with industry  =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*17:09*/
 As of all standards, How is it developed? When talking about the Land Data model, its been collaboratively brought together in industry. This is a picture of the Land Data Model group in progress. Man pointing at the screen is an CGI employee, but around the room we got UK and European manufactures there talking about how it all works.
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_12.06.29_pm.png?700 |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_12.06.29_pm.png?700 |}}
 <caption>GVA data standards developed collaboratively with industry</caption>
 </figure>
 ===== Example Platform Independent Model (PIM) Module: Sensors =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*17:56*/
-The sensors module provides data for use by an environmental sensor of some sort. It provides a few specific known sensor types and a method of defining a generic sensor of a type not specifically represented in the [[ddsf:private:guidebook:06_append:glossary:p:pim|PIM]].
+The sensors module provides data for use by an environmental sensor of some sort. It provides a few specific known sensor types and a method of defining a generic sensor of a type not specifically represented in the [[ddsf:public:guidebook:06_append:glossary:p:pim|PIM]].
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_12.09.31_pm.png?800|}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_12.09.31_pm.png?800|}}
 <caption>Example Platform Independent Model (PIM) Module: Sensors</caption>
 </figure>
 ===== GVA Human Machine Interface (HMI) =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*18:15*/
-I said I was going to talk about the Machine Interface, and I've got passion about how the users get benefit from it. So this is a typical UK GVA [[ddsf:private:guidebook:06_append:glossary:h:hmi]]. Looks a bit boring, got a status bar at the top and some bessel's around the edge. My explanation for this system is that its designed for the 0.01% use edge case. You are working in a vehicle moving at speed, on rough ground, you're under a nuclear biological chemical threat, you have the thickest gloves on you have ever seen, you can hardly see through your goggles, its night, you haven't slept in two days and someone is trying to kill you. You're under extreme stress and the fear of dying. This interface is designed to be so intuitive. People use it without thinking, very easy to use.
+I said I was going to talk about the Machine Interface, and I've got passion about how the users get benefit from it. So this is a typical UK GVA [[ddsf:public:guidebook:06_append:glossary:h:hmi]]. Looks a bit boring, got a status bar at the top and some bessel's around the edge. My explanation for this system is that its designed for the 0.01% use edge case. You are working in a vehicle moving at speed, on rough ground, you're under a nuclear biological chemical threat, you have the thickest gloves on you have ever seen, you can hardly see through your goggles, its night, you haven't slept in two days and someone is trying to kill you. You're under extreme stress and the fear of dying. This interface is designed to be so intuitive. People use it without thinking, very easy to use.
   * ALL systems and platform accessed through one screen
@@ Line 250: / Line 248: @@
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_12.12.19_pm.png?700   |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_12.12.19_pm.png?700   |}}
 <caption>GVA Human Machine Interface (HMI)</caption>
 </figure>
 ===== GVA – the user perspective =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*19:38*/
-Here is a GVA system in use in the Warrior CSP, thanks to Lockheed Martin we have the ability to show the picture, that it shows how uncluttered the turret is. If you've ever been in a defense vehicle turret, they usually have so many screens and so many buttons you can hardly move in them. This one is completely uncluttered because you have the single screen in front of you. What does this give you? It gives shared situational awareness, everybody in the vehicle has a single screen in front of them and they can all see what's going on. Screen on the right is a picture of some recent work we have done controlling an unmanned ground vehicle, so the commander can see what's going on from the unmanned ground vehicle while someone else is driving, or its driving itself, so everyone can see what's going on. As you can see there is a map in the top right corner so that gives you shared cognition, the commander will have a different thing to do with the data as the guy driving the whatever. That gives an information edge, able to spot things quicker, make decisions faster, on the battlefield seconds count. Its a simple and consistent interface, you have standard systems, dashboards, and specific mission systems, like the [[ddsf:private:guidebook:06_append:glossary:u:unmanned_ground_vehicle|Unmanned Ground Vehicle (UGV)]].
+Here is a GVA system in use in the Warrior CSP, thanks to Lockheed Martin we have the ability to show the picture, that it shows how uncluttered the turret is. If you've ever been in a defense vehicle turret, they usually have so many screens and so many buttons you can hardly move in them. This one is completely uncluttered because you have the single screen in front of you. What does this give you? It gives shared situational awareness, everybody in the vehicle has a single screen in front of them and they can all see what's going on. Screen on the right is a picture of some recent work we have done controlling an unmanned ground vehicle, so the commander can see what's going on from the unmanned ground vehicle while someone else is driving, or its driving itself, so everyone can see what's going on. As you can see there is a map in the top right corner so that gives you shared cognition, the commander will have a different thing to do with the data as the guy driving the whatever. That gives an information edge, able to spot things quicker, make decisions faster, on the battlefield seconds count. Its a simple and consistent interface, you have standard systems, dashboards, and specific mission systems, like the [[ddsf:public:guidebook:06_append:glossary:u:unmanned_ground_vehicle|Unmanned Ground Vehicle (UGV)]].
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_12.15.57_pm.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_12.15.57_pm.png?700  |}}
 <caption>GVA – the user perspective</caption>
 </figure>
@@ Line 267: / Line 265: @@
 ===== What’s next? =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]
 /*21:21*/
 We always need to think in terms of the users, and they usually have shiny boots and wear shiny pajamas. So what are we going to do for them? That's quite difficult to explain when you're down in the technical details...
-  * GVA defines a method to distribute for [[ddsf:private:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] policies to the resources on the data bus: COTS [[ddsf:private:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] systems connect with no modification.
+  * GVA defines a method to distribute for [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] policies to the resources on the data bus: COTS [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds|DDS]] systems connect with no modification.
-  * Use [[ddsf:private:guidebook:06_append:01_family_of_standards:01_core:dds_security|DDS-Security]] to enable different classifications of data to exist on the same wire?
+  * Use [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:dds_security|DDS-Security]] to enable different classifications of data to exist on the same wire?
   * Time sensitive networking integration?
   * Use DDS on unmanned vehicles to manage resources, with gateways to robotic standards (ROS)?
 <figure>
-{{  ddsf:private:guidebook:03_user:screen_shot_2020-12-12_at_12.16.55_pm.png?700  |}}
+{{  ddsf:public:guidebook:03_user:screen_shot_2020-12-12_at_12.16.55_pm.png?700  |}}
 <caption>What’s next?</caption>
 </figure>
@@ Line 283: / Line 281: @@
 ===== Slide Title =====
-[[ddsf:private:guidebook:03_user:07_gva| Return to Top]]
+[[ddsf:public:guidebook:03_user:07_gva| Return to Top]]

DDS Foundation Wiki

User Tools

Site Tools

Differences

Page Tools