JAUS Compliance Situation

1
JAUS Compliance Situation

• Engineer view vs. market view of
  Compliance/Interoperability Call Compliance
• JAUS Standard vs JAUS Message Standard
• Belonging to OPC or ETG is required for current
  compliance
• Official documents do not enable Compliance
• Unofficial / Incomplete documents currently
  describe compliance
• Continuing engineering vs. design engineering
• Compliance is 1 issue facing JAUS Community

2
JAUS Compliance Goals

• Engage JAUS Community in Compliance Discussion
• Assure JAUS Documents are capable of a Compliance
  process
• Enable a JAUS Compliance community through
  definition

3
JAUS Compliance Plan

• Stand-up a JAUS committee that is focused on
  compliance issues
• Generate a document that describes compliance
  requirements for future released documents
• Generate a document that describes a general
  compliance process
• 1st minute of life? Come si dice JAUS

4
Quick Compliance Approach

• Creation of a living JAUS Acceptance Test
  Procedure (ATP)
• Formal Usage of ATP at beginning of each ETG
  function
• Self-Usage of ATP at beginning of VPN experiments
• Start with initial ETG 1 process as defined by
  Ruel/Parag/Clark
• Review other standard compliance process

5
JAUS Interoperability
1st Minute
Power-On
Application Interoperability
JAUS Interoperability Level 1
Level 2
Level 3

• Transport Specific
• JAUS Message Compliance
• Sub-System Identification
• Communication Verification
• Certification per Transport

• Asset Alignment

• Specification Alignment

Time
6
Key Concepts

• Definition and education issues, not technical
  issue
• Once communications is established
  Interoperability level can be determined by
  applications and is a vendor distinction issue
• Decision not to interoperate is part of
  interoperability