MOD Architectural Framework MODAF

1
MOD Architectural Framework(MODAF)
Concepts Doctrine Processes 20 June 2005
2
Agenda

• Engagement Objectives
• MODAF Overview
• MODAF Concepts Doctrine Deskbook
• Developing common understanding of Concepts
  Doctrine process
• Related Views and Potential View Uses
• Next Steps

3
Objectives

• To Validate MODAF Team Interpretation Of Concepts
  Doctrine Processes Based Upon
• COI Concepts Doctrine Workshops 7 December 2004
• JDCC Seven Step Process
• NEC 2020 Pilot
• Joint Fires Pilot
• To Begin MODAF View Mapping
• Key MODAF Views or equivalent already in use
• Identification of additional MODAF Views that
  would be useful to the Concepts Doctrine
  Community

To Complete A Draft Version Of Concepts
Doctrine Deskbook End July
4
Introductions

• Lets get to know who we are going to be spending
  the day with
• Your name
• Organisation
• Post
• Brief background
• What you enjoy doing when not at work

5
Workshop Style Rules
6
Agenda

• Engagement Objectives
• MODAF Overview
• MODAF Concepts Doctrine Deskbook
• Developing common understanding of Concepts
  Doctrine process
• Related Views and Potential View Uses
• Next Steps

7
Increasing Complexity

• Life has become too complicated for ad-hoc
  acquisition
• Projects and programmes now link and overlap
  pan-defence
• Multiple operational, technical and service
  boundaries emerging, which must be managed
  coherently
• Overlapping functionality in subsystems, eg
  BISAs
• Network Enabled Capability is a key element to
  meet this changing need
• NEC is the linking of sensors, decision makers
  and weapon systems so that information can be
  translated into synchronised and overwhelming
  military effect at optimum tempoCM(IS), July
  2002
• Enables us to federate systems, sensors,
  effectors and hence improve military
  effectiveness
• We need a more structured approach to manage the
  complexity whilst balancing all appropriate user
  perspectives

8
MODAF Authority

• This project originated from CM(IS) NEC Next
  Steps Paper to the JCB, issued in April 03
• Working with major stakeholders (DG(Info),
  DCSA, IA and others) DEC CCII has identified the
  US Department of Defense Architecture Framework
  (DoDAF) as the most appropriate framework to
  underpin the development of NEC.
• VCDS Network Enabled Capability workshop action
  DMB NEC workshop, February 2005, agreed that
  MODAF should be mandated via IAB by April 2006

9
DoDAF DoD Architectural Framework

• Proven way of delivering high complexity
  capability
• 8 years proven structured approach
• Numerous other nations adopting similar approaches

Applied to the Enterprise across
10
MOD Architectural Framework

• MOD Architectural Framework modelling using six
  Viewpoint sets
• MODAF is largely based on best practice DoDAF
• It is being tailored to MOD processes and
  lifecycles
• It will take a pragmatic approach
• Model all appropriate views
• Only model what is needed (based upon a core
  mandated set)
• Enhancements include Views that support
  capability management and acquisition programmes
• Other nations watching with interest

11
Abstracting Real World Problems
Abstracting real world problems
enables structured analysis
12
User Focused Viewpoints

• Structured Viewpoints provide user focus
• Viewpoints encompass different user perspectives
• Strategic Viewpoint (StV)
• Operational Viewpoint (OV)
• Systems Viewpoint (SV)
• Technical Viewpoint (TV)
• Acquisition Viewpoint (AcV)
• All Viewpoints (AV)

13
Common Language
Enterprise Arch.
MODAF Meta Model (M3)
Architectural Repository
14
Common Language

• Bringing together systems, organisations and
  processes
• Re-using architectural components

Falcon
Bowman
Warrior
FRES
Skynet
Challenger
15
Robust Analysis

• MODAF supports robust analysis at a progressively
  more detailed level
• Capability issues and gaps are understood
• View points are joined up

CRD/Capability Taxonomy
Capability Management
URD
Scenarios
Acquisition Cycle
User Requirements
OV
OV-1 OV-2 OV-3
SRD
Procurement
Standards
CIP
SV-1 SV-2 SV-3 SV-8 SV-9
SV
Fielding
AcV
AcV-2
16
Pan Defence Stakeholder Involvement

• Operational plans made with greater effect
  through wider stakeholder involvement

17
Benefits Realisation

• Reducing the amount of rework and cost overrun
  through application of MODAF in conjunction with
  supporting initiatives

Before
After
18
MODAF Project Governance

• Project owned by ECC - DEC CCII
• Full consultation through user group
• Technical group supporting dependencies eg
  Taxonomy, meta model
• MODAF Partners PA Consulting Group Cornwell
  Management Consultants

CM(IS)
Tech
Group
Suppliers, (eg IA, DG(Info),DCBM(A))
CCII / DD
DEC CCII
Interop
19
MODAF Project Schedule

• Initial documentation April 2005
• MODAF Handbook ECC Deskbook
• First version of MODAF released August 2005

Development Stage
Bridging Phase
Roll-out Stage
Produce Products
Start-up
Mandate
Maintain
Interim Guidance
MODAF User Help Facility
Development
COI Deskbooks
Initial Development
Tiger Team Support
Pre-Pilot work
Pilot work
Training
20
Implementation Timeline
2005 2006

• Mar 05 Handbook and 1st COI Deskbook in
  draft
• Apr - Jul 05 MODAF pilots and development of
  documentation and remaining Deskbooks
• Aug 05 MODAF V1 issued
• Apr 06 MODAF expected to be mandated for all IAB
  business cases

21
Agenda

• Engagement Objectives
• MODAF Overview
• MODAF Concepts Doctrine Deskbook
• Developing common understanding of Concepts
  Doctrine process
• Related Views and Potential View Uses
• Next Steps

22
MODAF Supporting Materials
Concepts Doctrine
MODAF Volume 1 Executive Summary
MODAF COI Deskbook (x 5)
MODAF Volume 2 Handbook

• MODAF Overview
• MODAF Composition
• Concept Of Use
• Benefits
• Tool Support

• Technical Spec
• Detailed Descriptions Of MODAF Views

• COI Practical Guidance
• MODAF Views Informing Business Processes and
  Activities
• Worked Examples Of MODAF View Development In
  Support Of Processes

23
MODAF COIs
Doctrine
Concepts Doctrine
Operations
Capability Gaps
Future Op Needs
Capability Management
C
A
D
M
D
I
Funded Options
C
A
D
M
I
D
24
COI Deskbooks

• Foreword
• Introduction
• MODAF relationship to COI business process and
  activities
• Worked example(s)
• Reference guide to COI process usage of MODAF
  views
• Pocket guide format

N x Reference Guides
25
Agenda

• Engagement Objectives
• MODAF Overview
• MODAF Concepts Doctrine Deskbook
• Developing common understanding of Concepts
  Doctrine process
• Related Views and Potential View Uses
• Next Steps

26
Process from COI Workshop Dec 04
27
7-Step JDCC Process
28
Combined Concepts Doctrine Process
C. Applied Concepts
B. Analytical Concepts
A. Pre-Analytical Concepts
Existing Capability
Futures Work
ConEmp
ConUse
Future Capability Development Paper
Draft ConOps
Concepts
Endorsed ConOps
HLOC
Joint Vision
Concept To Capability
Doctrine
Capability Management
C
A
D
M
I
D
Funded Options
C
A
D
M
I
D
New Capability
SOPs TTPS
Modified Doctrine
D. Concepts Doctrine In Delivery
29
Break-out Session 1 Concepts Doctrine Process
i.e. Applied Concept

• Objective To define the Concepts Doctrinal
  linkages between each community
• Inputs from other areas
• Activities
• Outputs to other areas
• Epoch/Time Frame
• Individually, write post-it notes detailing
  inputs, activities, outputs and epochs for each
  of the four areas (Pre-Analytical, Analytical,
  Applied, Delivery)
• As a group, stick the post-its to the
  flip-charts, and agree a set of inputs,
  activities, outputs and epochs for each area
• We will then return for a plenary between the two
  groups

Inputs (From)
Activities
Outputs (To)
Epoch
30
Plenary

• Agree flip-charts between the two groups
• Identify the various strands to the Concepts and
  Doctrine Process.
• What are the inputs/outputs that feed these
  processes from the perspective of the Joint and
  Single Service Concepts and Doctrine communities
  and Customer 2?
• Are any of these processes specific to particular
  epochs?

31
Agenda

• Engagement Objectives
• MODAF Overview
• MODAF Concepts Doctrine Deskbook
• Developing common understanding of Concepts
  Doctrine process
• Related Views and Potential View Uses
• Next Steps

32
Strategic Viewpoint

• What are these views?
• Formal articulation of the High Level Concepts
• Primarily support capability management processes
• Support interfaces with other key MOD processes
  such as operational concepts and Capability
  Planning.
• How would they benefit the Concepts Doctrine
  Community?
• Articulate concepts leading to identification of
  required defence capabilities (Step 1)
• Identify and enable the management of
  cross-capability dependencies support the
  development of the FCD paper (Step 2)
• Support concept generation and capability
  development and assessment (CONOPs) Steps 3 4
• Ensure capability selection, endorsement and
  integration across all LoDs

33
Strategic Views
StV-5 Cap / System Deployment
StV-1 Op Concept
StV-3 Cap Phasing
OVs
StV-6 Cap to Use Case Mapping
StV-2 Cap Taxonomy
34
Operational Viewpoint

• What are these views?
• Formal descriptions of military operational
  requirements, missions, scenarios and
  relationships
• Primarily support requirements development
• Support interfaces with other key MOD processes
  such as operational concepts and contracting with
  industry.
• How would they benefit the Concepts Doctrine
  Community?
• Clear articulation of requirements to industry
  partners
• Support evaluation of solution options through
  scenario analysis

35
Operational Views
OV-2 Op Node Interactions
OV-1 Concept of Operations
OV-3 Information Flows
OV-6c Sequence Diagram
OV-7 Information Model
OV-5 Activity Model
36
System Viewpoint

• What are these views?
• Descriptions of system functions, interfaces and
  performance
• Primarily support solution development and
  maintenance
• Developed during solution design.
• How would they benefit the Concepts Doctrine
  Community?
• Provide a common language for system
  specification and design between MOD and Industry
• Ensure system requirements articulated through
  System Views are traceable back to user
  requirements shown in Operational Views

37
System Views (1)
OVs
SV-1 System Interconnections
SV-5 Op Activity to System Mapping
SV-11 Data Model
SV-6 Data Flows
SV-3 System Interfaces
38
System Views (2)
SV-4 System Functions
SV-1 System Interconnections
SV-7 System Performance
TVs
SV-9 Technology Forecast
SV-8 System Evolution
SV-2 System Interoperability
39
Technical Viewpoint

• What are these views?
• Formal descriptions of technical and defence
  industry standards
• Primarily support requirements development.
• Could be used to specify the use of concepts and
  applied in Operational Analysis
• How would they benefit the Concepts Doctrine
  Community?
• Clear baseline of constraints applied to the
  solution design
• Facilitate up-front communication of any
  additional cost to comply with these standards
• Articulate underpinning doctrine and identify
  doctrinal gaps in the employment of systems,
  formations and task forces

40
Technical Views
TV-1 Technical Standards Profile
TV-2 Standards Forecast
?
41
Acquisition Viewpoint ?

• What are these Views?
• Programmatic Views of the overall Acquisition
  programme within the MOD
• Support Acquisition planning, LOD maturity
  evaluation and managing dependencies between
  projects
• Support interfaces with other key MOD processes
  such as operational concepts and Capability
  Planning.
• How would they benefit the Concepts Doctrine
  Community?
• Potentially identify dependencies impacting
  Concept development
• Highlight gaps or overlaps that will result from
  any re-scheduling of capability delivery dates

42
Acquisition Views
Generic AcV-2 System of Systems Acquisition
Programmes
JCB NEC Roadmap AcV-2 Format
43
Break-out Session 2 View Mapping

• Objective Identify Views which may be useful for
  the agreed inputs, activities and outputs for
  each Concept Doctrine area
• As one group suggest relevant Views for the
  inputs, activities and outputs for each area,
  using post-its to agree a set of relevant Views
• Agree the links/dependencies between areas
• NOTE There may be inputs, activities or outputs
  with no relevant Views, and there will certainly
  be some with multiple relevant Views

Input Views
Output Views
Concept Doctrine Area
Activities
OV1
AcV2
44
Agenda

• Engagement Objectives
• MODAF Overview
• MODAF Concepts Doctrine Deskbook
• Developing common understanding of Concepts
  Doctrine process
• Related Views and Potential View Uses
• Next Steps

45
Concepts Doctrine Next Steps
8 July
Internal Release
15 July
Release Review Deadline
Engagement
29 July
Formal Draft Release
12 August
Development
Formal Review Deadline
Release Review
16 August
Update
Review Board
26 August
Detailed Review
Full Release
Initial Sift
Finalise Baseline
46

• Points of Contact
• Project Manager
• kathy.lamb134_at_mod.uk
• 0207 807 8884
• Concepts Doctrine COI lead
• john.taylor_at_paconsulting.com
• 07841 947175
• MODAF development POC
• david.mawby_at_paconsulting.com
• 07887 540406

47
Articulating Concepts Doctrine

• From the abstract to the tangible

48
Supporting Concept Development

• Operational analysis informing the development of
  applied concepts

49
Specifying Concepts Doctrine

• Specifying the use of concepts, doctrine, SOPs/
  TTPs across military organisations and levels