1

Don Brutzman

Naval Postgraduate School (NPS)Modeling, Virtual Environments & Simulation (MOVES) Institute

Naval Postgraduate School

8 June 2006

NPS AUV Workbench for CARUSO

Human Systems Interoperability (HSI) Considerations

2

AUV Workbench Project Description

• Rehearsal, reality, replay for diverse robots

• Open source, Java, XML, X3D graphics

• Mission planning, environmental web services

• Robot mission execution, telemetry playback

• Hydrodynamics response, sonar modeling

• Synchronized OpenMap GIS display

• Visualization using X3D Graphics standard

• Demonstrating HSI techniques throughout

AUV Workbench poster

4

5

6

HSI Stack Summary

• Coalition

• Joint

• Battlegroup

• Ship, aircraft, submarine

• Watch team

• Operator

• Offboard unmanned systems

Usual focus of effort

• Need to go further, up + down the HSI stack

7

Lots of AUVW HSI work underway

• Team effort with larger CARUSO group Dr. Don Brutzman NPS, strong 2D/3D team Dr. Lynee Murray NUWC

• Potentially new HSI concepts HSI in large: collaborative situational awareness HSI in small: show best practices in AUVW app HSI in robots: coherent tasking despite diversity

• Consider potential new role for NAVSEA 03: HSI interoperability across multiple systems Recent initial work, plan elaboration next year

Inputs/Outputs Interoperability Layers How to Accomplish

Effective, Efficient, Gridded Coalition Systems

Common Operational Picture,

Situational Awareness (SA)

Consistent Semantic Understanding

------------------------------------------------------------------------------------------

Tactical

Messaging C2IEDM/JC3IEDM providing

common shared context, tactical data interoperability

Shared coherent XML among participating platforms

------------------------------------------------------------------------------------------

HSI Level

VIII

VII

VI

------------------------------------------------------------------------------------------

Navy Battle GroupCommon CIC/CDC tactical picture for coordinated operations/shared data communications: NTDS, Link 11, Link 16, etc.

No XML interoperability,legacy stovepipe protocols

Groups of systems,HSI “in the large”

External connectionsNetworks

[Macro HSI]Complex Constructs for both humans and systems

_________________________________________________________________

Internationalization (I18N)

and Localization (L10N)

for sensible coalition usage

Inputs/Outputs How to Accomplish HSI Level

Consistent XML targets, swappable terms, labels, annotations

I

Individual Systems,HSI “in the small”

_________________________________________________________________

Internal connectionsGUI designs

[Micro HSI]Discrete Human Factors/Ergonomics

---------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------

IV

III

V

II

Multimodal consistency in menus,human re-orientation capability[keyboard/pointer/tactile/voice]

Java Look & FeelCoherent usability

Some help annotationsdesirable for functionality

Application help pages & tool tips,both context-sensitive & embedded

Java Help, HTML pages,XML content & catalog

---------------------------------------------------------------------------------------------

XML datasets & GIG enterprise services,data updates via XSLT

Within-platform softwareSoftware updates

Synchronized corresponding viewsfor text / 2D / 3D displays

Based on GIG XMLdata-driven model

Java, open source andpublic software libraries

Interoperability Layers

Autonomous Vehicle Control Language (AVCL)

Inputs/Outputs How to Accomplish HSI Level

Consistent messaging for tasking & reporting by diverse robots

Unmanned Systems,HSI “when adding robots”

---------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------

-1

0

Distinct, different, incompatible robot systems being directed by shipboard operators

JAUS architecture only permits internal re-use of software components

XSLT stylesheets,custom converters

Interoperability Layers

XSLT stylesheets,common converters

_________________________________________________________________

Comments welcome.

12

Don Brutzman

brutzman@nps.navy.mil http://web.nps.navy.mil/~brutzman

Code USW/Br, Naval Postgraduate SchoolMonterey California 93943-5000 USA

1.831.656.2149 voice1.831.656.7599 fax

Contact