UAF13 — Mission and Mission Threads

Enterprise Mission in UAF is a specialization of Actual Enterprise Phase. But in what sense is a Mission some kind of Phase? Mission is defined in UAF as "captures at a high level what you will do to realize your vision". A Phase is not "what you will do" but rather organizing a collection of things to do to achieves goals assigned to that Phase. Need to put Mission into UAF the way it was done in UPDM. Mission is more like an Enduring Task. In UPDM a Mission was an extension of a Use Case. Need to also add a way to capture a Mission Thread.

See attached slides.

The UAF Modeling Language (UAFML) especially suited for modeling an enterprise and as such it is appropriate for modeling a large and complex mission architecture along with its variety of scenarios, vignettes, MTs, METs, etc. The following extensions to UAF will provide support for Mission Engineering and alignment with best practice.
The following elements need to be added to UAF to support Mission Engineering.
1 Mission The task, together with the purpose, that clearly indicates the action to be taken and the reasoning behind the mission. (JP 1-02)
2 MissionThread A sequence of end-to-end mission tasks, activities, and events presented as a series of steps to achieve a mission. (OUSD(R&E))
3 ActualMission A particular mission to accomplish assigned mission objectives
4 ActualMissionPhase A particular phase in the accomplishment of an overall actual mission
5 MissionScenario Description of the geographical location and timeframe of the overall conflict. A scenario includes information such as threat and friendly politico-military contexts and backgrounds, assumptions, constraints, limitations, strategic objectives, and other planning considerations. (OUSD(R&E))
6 MissionVignette Same contents as a MissionScenario except that it can represent small, ideally self-contained parts of a scenario. (OUSD(R&E))
7 ActualMissionScenario A particular mission scenario within which an actual mission is to be accomplished
8 ActualMissionVignette A particular mission vignette within which an actual mission is to be accomplished
9 MissionTask A clearly defined action or activity specifically assigned to a system, individual or organization that must be completed. (MEG 2.0).
10 MissionTaskAction The usage of a MissionTask within a MissionThread.
11 MissionEngineeringThread A sequence of end-to-end mission-related resources, functions, actions, states, and events presented as a series of steps that supports a mission thread
12 ConflictsWith Tuple that indicates elements acting against or in opposition to each other. This means that there are elements in the model that disagree about something important or are incompatible with each other in some way
13 Opposes Tuple that indicates an open clash between two opposing groups (or individuals). This means that elements in the model are fighting against each other or are providing strong resistance to progress towards some goals
14 OpposableElement Type of element that is categorized to allow for it to have an Opposes relationship to some other opposable element.
15 DesignationKind Defines the type of structural element with respect to purpose, intent and capabilities of that element.
16 Doctrine A formal expression of military knowledge and thought, accepted as being relevant at a given time, which covers the nature of conflict, the preparation of the military forces for conflict, and the method of engaging in conflict to achieve success... it is descriptive rather than prescriptive, requiring judgement in application.
17 Defines A tuple that links the Mission and the Activity that implements it.
18 MissionKind An enumerated list of kinds of missions. These include:
19 Battle A hostile encounter between opposing military forces
20 Campaign A series of related major operations aimed at achieving strategic and operational objectives within a given time and space. (JP 5-0)
21 Engagement A tactical conflict, usually between opposing lower echelons maneuver forces. See also battle; campaign. (JP 3-0)
22 MajorOperation A series of tactical actions (battles, engagements, strikes) conducted by combat forces, coordinated in time and place, to achieve strategic or operational objectives in an operational area. (JP 3-0)
23 NationalPolicy A broad course of action or statements of guidance adopted by the government at the national level in pursuit of national objectives. (JP 1)
24 Other A different kind of mission.
25 SmallUnitAndCrewAction Small unit and Crew Action is the combat deployment of platoons and smaller units in a particular strategic and logistic environment
26 TheaterStrategy An overarching construct outlining a combatant commander’s vision for integrating and synchronizing military activities and operations with the other instruments of national power in order to achieve national strategic objectives. See also national military strategy; national security strategy; strategy. (JP 3-0)
27 ForceDesignation Indicates whether the structural element is an enemy, ally, neutral or other force. The colors may vary according to country so can be replaced as required. These include:
28 BlueForce Structural elements corresponding to the instigating or friendly force.
29 RedForce The structural element is an enemy force.
30 GreenForce The structural element is an ally.
31 GrayForce The structural element is a third party force.
32 Unknown The structural element is unknown.
33 WhiteForce The structural element is neutral.
For support of Doctrine, a new element will need to be created called Doctrine which is a subtype of both requirement and standard. It will contain the following fields:
1 createdBy The organization or creator of the standard or doctrine.
2 publishedBy An entity responsible for making the resource available.
3 createdStandards A relationship between an actual organization and the standards created by that organization.
4 publishedStandards A relationship between an actual organization and the standards published by that organization.
For enterprise architectures and mission engineering we need to be able to define a new type of a constraint which is an assumption.
Assumption EnumerationLiteral added to RuleKind Enumeration indicating that the element is accepted as true or as certain to happen, without proof.
The following Diagrams will need to be created to support modeling of Missions:
1 Resources Processes: Mission Engineering Threads
Stakeholders: Solution Providers, Systems Engineers, IT Architects.
Concerns: captures activity based behavior and flows performed by resources and organizational assets.
Definition: describes the functions that are normally conducted in the course of implementing operational activity(ies) in support of capability(ies). It describes the functions, their Inputs/Outputs, function actions and flows between them.
Recommended Implementation: SysML Activity Diagram, SysML Block Definition Diagram."
2 Operational Processes: Mission Threads "[Need a new description according to the template below]
Stakeholders: Business Architect, Systems Engineers, Enterprise Architects
Concerns: captures activity based behavior and flows performed by mission actors and related operational and strategic assets.
Definition: describes the activities that are normally conducted in the course of achieving business goals that support a capability. It describes operational activities, their Inputs/Outputs, operational activity actions and flows between them.
Recommended Implementation: SysML Activity Diagram, SysML Block Definition Diagram, BPMN Process Diagram."
3 Strategic Processes: Mission "[Need a new description according to the template below]
Stakeholders: Program/Project Managers, Portfolio Managers, Enterprise Architects, Executives.
Concerns: capability phasing.
Definition: shows the relationship between strategic phases and the Capabilities that are intended to be developed during the strategic phases, and the actual organizations involved.
Recommended Implementation: SysML Block Definition Diagram."
4 Parameters: Mission Vignette and Scenario "[Need a new description according to the template below]
Stakeholders: Capability owners, Systems Engineers, Solution Providers.
Concerns: defines the environments and conditions for execution of mission(s)+C10
Definition: shows the elements and relationships that are involved in defining the environments and conditions applicable to capability, operational concept or set of systems.
Recommended Implementation: SysML Block Definition Diagram."