40 likes | 51 Vues
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
E N D
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
MissionLab Pre-mission Planning Component: Interface • We are currently completing the MissionLab to CIM interface • This interface represents the only point of communication between MissionLab and ICARUS CIM Component GT to CIM Interface Georgia Tech Pre-mission Planning Component User Input: parameters, preferences, etc. XML Pre-mission Plan Objectives
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.
MissionLab Pre-mission Planning Component: Design GT to CIM Interface • 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 MissiobLab Pre-mission Planning Component User Input: parameters, preferences, etc. XML Pre-mission Plan Objectives