Transport Interface: (DRAFT) This document specifies the Transport Layer format and associated protocols required to implement the proposed JAUS-over-IP transport standard. This is not the proposed SAE-AS4B document, but rather an immediate stand-in until that document can be ratified. (Transport Interface.pdf)

Dynamic Configuration Control Document: (DRAFT) JAUS defines a system in terms of subsystems, nodes, and components. The component provides a specific capability and is the main building block of the system. A node is defined to be a set of related components, and a subsystem is defined to be a set of related nodes. During system operation, components work together for the purpose of achieving a common goal. Before a component can make use of any other components’ capabilities, it must be able to uniquely identify each component along with its specific capabilities. This information can be set up statically before the system is started, or it can be set up dynamically after the system is started. Dynamic Configuration is a process defined in this document that provides a mechanism for setting up a JAUS system, or part of a JAUS system, when needed rather than in advance. (Dynamic Configuration Control.pdf)

Events and Service Connections: (DRAFT) This document defines the need for and use of period (Service Connections) and non-period (Events) messages and the protocols and messages needed to instantiate, modify, and terminate them. (Events and Service Connections.pdf)

Payload Interface: (DRAFT) This document defines the messages and protocols required to create JAUS-compliant payloads that JAUS-compliant Operator Control Units can control and interact with. (Payload Interface.pdf)

World Model Knowledge Store Components: (DRAFT) This document defines the database of knowledge about the world, plus a database management system that stores and retrieves information. (World Model Knowledge Store.pdf)

Mission Spooler Interface: (DRAFT) This document defines the method that a sequence of JAUS messages are stored and transmitted to other JAUS components in a predetermined fashion. This capability is a building block to enable the execution of complex plans within the JAUS framework. (Mission Spooler Interface.pdf)

OPC 3.0 Experiment Overview: This document provides information about how the above documents are used within the context of real interoperability requirements to accomplish a specific mission. It should be thought of as the “domain knowledge” required to actually implement, test, and demonstrate JAUS fully. It is an example of a “best practices guide” for JAUS implementations. (OPC 3.0 Overview.pdf)