1

MissionLab Pre-mission Planner Component (MPPC): Overview

Purpose: Use operator input of mission parameters and preferences and a case library to generate executable mission objectives

Design constraints: Broad range of mission types Broad range of asset types Generated rapidly Little human intervention Correct Robust to uncertainty Scalable

2

MissionLab Pre-mission Planning Component: Interface

Georgia Tech Pre-mission

Planning ComponentXML Pre-

mission Plan Objectives

CIM Component

GT to CIM Interface User Input:

parameters, preferences,

etc.

We are currently completing the MissionLab to CIM interface

This interface represents the only point of communication between MissionLab and ICARUS

3

MissionLab Pre-mission Planning Component: Interface

We are now capable of sending messages to LM’s CIM component, including subscribing, unsubscribing and sending mission objectives.

We are currently testing this functionality and preparing to send LM the first installment of software.

Thus far the integration effort has been exceptionally smooth.

4

MissionLab Pre-mission Planning Component: Design

MissiobLab Pre-mission Planning

ComponentXML Pre-mission Plan Objectives

GT to CIM Interface

User Input: parameters,

preferences, etc.

User Interface

CNP Task Allocation

CBR Adaptation

CBR Memory

MissionRequirements Preferences

Task-based Constraints

Sub-Missions

1

2 3

3 4

The internal design of the component will offer the user several pathways for creating mission plans including visual programming, scripts, and a case-based reasoning wizard