1. UK Architecture Methodology
Information Systems of Systems Analysis Team
Lieutenant Nick Trosh Royal Navy
SOSA Task 78 Project Lead and
UK Lead Architect for AMN

2. Contents Mission Thread Approach
AMN Service and Process Architecture Links
Deriving Benefits Through Architecture
Mission Thread Analysis

3. The Mission Thread Approach
MISSION THREADS
ENABLING
SERVICES
Mission Threads provide a framework to:
Focus discussion
Identify “Th Hot Spots”
Identify solution options
Modular “Operational Activity” enables a service-based approach to achieving Military Effect
Modular
“OPERATIONAL
ACTIVITY”
Building Blocks
for Planning,
Analysis &
Reuse
The Mission Threads Approach uses the 8 IJC endorsed Coalition Mission Threads
This allows:
Focussed discussion
Identification of “Hot Spots”
Identification of solution options
It is all based on operational activities (what the soldier does) which enables a service-based approach to achieving Military Effect
Definition of Mission Thread from the NATO C3 Classification Taxonomy:
Mission Threads are an operational description of end-to-end activities that accomplish the execution of a mission.  Mission Types and Tasks provide the Operational Mission Area context for the development of complete end-to-end Mission Thread architectures that will also describe the Information Products, User Applications and Technical Services required to successfully execute a Mission Thread from end-to-end.
MILITARY EFFECT
Return to Contents

4. AMN Process Architecture
Battlespace Management
MEDEVAC
Reactive Activity
Reports + Return
Estimate
Orders
Focussed Activity
C-IED
Proactive Activity
Military Effect
Jt Fires
FofM
Force P
Store
Manage
Configure
Display
Exploit BA
Disseminate
Process
Collect
Direct
Jt ISR
ITIL Service Management Processes
Service Management

5. AMN Process Architecture
Battlespace Management
MEDEVAC
Force P
C-IED
FofM
Jt Fires BA
Jt ISR
Proactive Activity
Reactive Activity
Reports + Return
Estimate
Orders
Focussed Activity
Store
Manage
Configure
Display
Exploit
Disseminate
Process
Collect
Direct
Military Effect
ITIL Service Management Processes
Service Management

6. AMN Service/Process Architecture
Technical Services
Enabling Services
Military/Business Services
Battlespace Management
MEDEVAC
Reactive Activity
Reports + Return
Estimate
Orders
Focussed Activity
C-IED
Proactive Activity
Military Effect
Jt Fires
FofM
Force P
Store
Manage
Configure
Display
Exploit BA
Disseminate
Process
Collect
Direct
Jt ISR
ITIL Service Management Processes
Service Management
Return to Contents

7. Deriving Benefits Through Architecture
Military Effect
CMT Reviews
Doctrine
Training Docs
Military Process Analysis
Theatre Agnostic
Architecture
Training Info
User Requirements
IER
Interoperability
SERVICE SELECTION
Integration Spec
Test & Trial Schedules
IES
Infrastructure Requirements
System Specific
Architecture
This high-level diagram shows the benefits derived from a properly structured architecture. [CLICK]
By taking inputs from
CMT Reviews
Doctrine
Training Docs
and undertaking Military Process Analysis [CLICK]
We can model the process architecture [CLICK] which is Theatre Agnostic and reuseable [CLICK]
This gives us the following benefits
Training Info
User Requirements
IER – the What
Interoperability [CLICK]
These benefits enable decision makers to select the right applications to achieve the desired military effect [CLICK]
Applying the systems to the process architecture [CLICK] gives us the system specific architecture, [CLICK] which has the following benefits [CLICK]
Integration Spec
Test & Trial Schedules
Information Specification Requirement – the How
Infrastructure Requirements
[CLICK]

8. Training Documentation APPLICATION SELECTION
Theatre Agnostic
Architecture
Properly Structured Architecture leads you through the complexity
This is what the ISSA Team can do for you.
Solutions Identified Here
SOP Change &
Training Documentation
APPLICATION SELECTION
Information Estimate Process – Military Judgement Leading to Capability, System and Application Selection
This is the same diagram as the previous slide, but taken directly from the model
We have found that stakeholder problems are often reported in the interaction between 2 systems.
Using the model to analyse the problem will often lead to the solution being identified [CLICK]
in an SOP change, or change to training documentation – not buying more equipment.
Return to Contents
System Specific
Architecture
Problems Reported
Here

9. Analysing a Mission Thread using Properly Structured Architecture
CMT Analysis
Analysing a Mission Thread using Properly Structured Architecture

10. UK Architecture Methodology (Adopted by AWG)8.
Map Services to Capabilities 7.
Map Service Functions to Services 6.
Map Systems to Service Functions
1a.
Select the Mission Thread
2. Understand the Operational Activities
6a.
Map System Functions to Operational Activities
2a. Understand Node Interaction (IER) 1.
Identify the Operational Activities
1. The Military Process Analyst begins with OV5a – Identify the Operational Activities. [CLICK]
2. Then, by mapping the end-to-end military process, produces an OV-6c – Understand the Operational Activities
Identify People, Organizations and Information Requirements (IER)
Leads to Identifying Military and Enabling Services
Identify What capability is being used at every step of the End to End task [CLICK]
1a. Or, the Operational Activities can be decomposed to understand the relationships between activities (OV-5b) – Understand the Mission Thread
3. Then, by adding the systems to the OV-6c to create an SV-10c, you can – Understand the Systems
Identify Interfaces, Interactions and Integration Requirements
Identify the Information Exchange Specification (IES)
Leads to Identifying Testing & Trialing Requirements
Identifies Individual and Collective Training Needs.
At this point, enough analysis has been performed to understand the Mission Thread, but to map Services and Capabilities, further analysis is required [CLICK]
2a. Or, using the model, an OV-2 can be generated to describe the node interactions
4. This can be simplified to an SV-1 – Understand the System Interactions [CLICK]
5. The SV-1 can then be decomposed to understand the system function (SV-4) – this is very difficult to do given the lack of system function information available. We currently do not know what our Apps do, what they are capable of doing, which ones do something best and what an app should be able to do to support the troops. [CLICK]
6. System Functions can then be mapped to Service Functions (SV-5) [CLICK]
6a. Or – System Functions can be mapped to Operational Activities (SV-5)
7. Service Functions can then be mapped to Services (SOV-5) [CLICK]
8. Which in turn, can be mapped to Capabilities (SOV-3) [CLICK] 3.
Understand the Systems (IES) 4.
Simplify to Understand System
Interaction 5.
Decompose to Understand the System Function
HERRICK Decision Support Team
Return to Contents

11. Any Questions?
MHLS 11