The AGVRA Mission Model assists in the mission engineering activities to decompose and relate mission segments in support of system design. The mission model elements can be used effectively with the AGVRA Functional Decomposition Model and the AGVRA Interoperability Profile Model to express how system requirements relate to mission needs.
Intro to AGVRA Mission Models
Large Unit Mission Profile
The Large Unit Mission (LUM) profile provides support for modeling the top of Army doctrine to establish the context for a system being developed using AGVRA. The LUM profile is based on the Unified Architecture Framework (UAF) which is used in procurement to describe the goals and context of an organization. In combination with UAF, the LUM profile can be used at the platoon and higher echelons to model:
- The goals of the organization.
- The capabilities required by the organization.
- The operational activities of the organization.
- The services provided and consumed by the organization.
- The personnel structure and roles.
The LUM profile is intended to model down to a small team, a section of 2-3 vehicles or a platoon of 4 vehicles that perform tasks and maneuvers in a tightly synchronized manner. Below this level of detail, modeling hands off to the STM profile.
Small Team Model Profile
The Small Team Task Model (STM) profile provides support for modeling short tasks and maneuvers executed by a small team of vehicles. The STM profile is built around “Tasks”. “Movements” are also defined for conceptual convenience but are just tasks. Tasks can be defined for the entire team or defined for individual vehicles. Examples of tasks and movements include:
- Bounding overwatch.
- Formation transitions.
- Positioning the vehicle for firing angle.
- Observing the context.
The current working assumption for AGVRA is that autonomy software works within a single vehicle. The purpose of models built using the STM profile is to clarify the coordination between vehicles. STM models flush out required capabilities such as:
- Pre-trained knowledge of standard maneuvers that must be stored in the vehicle.
- Coordination communication which could be radio, but also visual or other signals.
- Sensing requirements such as visual alignment between vehicles.
The STM profile is built on plain SysML (not UAF) to allow for convenient linking of lower-level engineering models built using the other AGVRA components. STM models are intended to hand off to FDM models for functional decomposition inside a single vehicle down to sensing, mobility, and other packages such as RTK.
Doctrine Reference Profile
The Doctrine Reference (REF) profile provides support for modeling explicit and clear traceability to specific content in Army Doctrine, international standards, and other publications. The REF profile contains one stereotype for each of three types of traceability links:
- Traceability to paragraph numbers and text in formal Army Doctrine publications
- Traceability to international standards
- Traceability to other publications
The REF profile is built on plain SysML and can be used in either UAF or plain SysML models. The three stereotypes contain attributes to identify the title of the publication, source, publication date, and so on. These attributes are aligned with the Dublin Core standard for publication metadata now in use by leading libraries worldwide.
Mission Data Model
The Mission Data Model can be used in data exchanges to support the concept of operations from the LUM, STM, and REF. These data exchanges can be conceptual or logical. For conceptual models, the data exchanges are not concerned with how machines represent information – only with defining the innate information itself. In contrast, logical models convey the values of a properties.