Transcript MOD Architectural Framework (MODAF)

ECC – Information
Superiority
MOD Architectural
Framework
(MODAF)
Concepts & Doctrine Processes
20 June 2005
Developing the MOD Architectural Framework
IA
Agenda
• Engagement Objectives
• MODAF Overview
• MODAF Concepts & Doctrine Deskbook
• Developing common understanding of Concepts
& Doctrine process
• Related Views and Potential View Uses
• Next Steps
Developing the MOD Architectural Framework
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
Developing the MOD Architectural Framework
Introductions
• Let’s 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
Developing the MOD Architectural Framework
Workshop Style & Rules
•Issu
es
Developing the MOD Architectural Framework
Agenda
• Engagement Objectives
• MODAF Overview
• MODAF Concepts & Doctrine Deskbook
• Developing common understanding of Concepts
& Doctrine process
• Related Views and Potential View Uses
• Next Steps
Developing the MOD Architectural Framework
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 BISA’s
• 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 tempo”CM(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
Developing the MOD Architectural Framework
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
Developing the MOD Architectural Framework
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:
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
Developing the MOD Architectural Framework
Abstracting Real World Problems
Abstracting real world problems…
…enables
structured
analysis
Command Battlespace Management
Decision Support
1. Operational Planning:
1.
 Initiation
 Mission Analysis
 CCIR & planning
guidance
 Estimate
2.
- COA
- W argaming

 Decision
 CONOPS
 SoM
 Assemble/review Plan
 Orders
2. Operational Analysis
3. Mission Rehearsal
4. Situational Awareness:

 Physical Env
 Mission Env
 Blue Env
 Red Env
 W hite Env
 APNLRS
 CID
5. Intelligence:
 CCIRM
 Int Direction
 Collection mgt
 Collation mgt
 All-source fusion
 Dissemination
6. Functional Planning
Support:
 Arty Fire planning
 Engr Obs planning
 Engr Sp planning
 EOD planning
 AD planning
 EW planning
 Air planning
 Avn planning
 CIS planning
 Info ops planning
 Log planning
 Sup
 ES
 Tpt
 Med
 Personnel planning
Information
Information Management &
Acquisition
Information Management
 Information Analysis
 Information Fusion
 Information Quality
Assurance
 Information Dissemination
STAR
STAR Asset
Management/Tasking:
 STAR asset status
monitoring
 Mission planning
 Mission control
 Sensor cueing
STAR Product Management:
 Product analysis
 Collation and fusion
 Product Dissemination
Effects
1. Targeting:
CAPABILITY FUNCTION
Target selection
Target List management
Decision Support
Attack Guidance Matrix
Targeting Situational
Cycle:
Awareness
 Detect
 Recognise
CCIRM
 Identify
Op Planning
 Track
Intelligence
 Decide
Interoperability
 Engage
 Assess
Joint Strategic Intelligence
Operational Intelligence
Joint Logisitcs
NATO C2 & Int
NATO Comms
Allied Interoperability
Maritime
Air C2/Coord
Functional Planning Support
CSS
Medical
NBC
GBAD
Fire Support
Aviation C2
Aviation Logistics Support
Engineer/EOD
2. Plan Engagement:
Commsselection
Management
 Effects
 Resource
allocation
IS Management
 Synchronisation Interoperability
NATO AD
3. Conduct Engagement:
Allied
Fire
Support
 Decision
 Fires/Mission
Control
JTF/ARRC IS
 BDA
Fmn IS
 Reporting
BG & below IS
In barracks IS
Unit IS
Individual IS
Epoch 1 (Now - 2008)
Epoch 2 (2004-2007)
Epoch 3 (2006-2011)
Epoch 4 ( NEC enablers 2008-2012)
COMMAND BATTLESPACE MANAGEMENT
RESTRICTED
BMETS/JOCS/GP3(HQ ARRC
only)/RNCSS
BMETS/JOCS/BSAM/GP3(HQ
ARRC only)/RNCSS/HVM SIFF
JOCS (IPM only)/GP3(HQ ARRC only)
JOCS (IPM only)/GP3(HQ ARRC only)
JOCS (IPM only)/GP3(HQ ARRC only)
LOCE
INT-C
DRAFT
ComBAT/GP3 (HQ ARRC
ComBAT/CID?/JOCS/HVMSIFF/ARRC C2IS/GBAD RAP IOC-FOC
only)/JOCS/RNCSS/HVM SIFF/GBAD
EPOCH 2 - CBM & CBM(Land) Increments 1 through 4 (2004 - 2007) Epoch 1
RAP IOC
JOCS/ComBAT/GP3
(HQ ARRC only) JOCS/ComBAT/ARRC C2IS
JOCS/ComBAT/GP3 (HQ ARRC only) JOCS/ComBAT/ARRC C2IS
Interop
Effector
s
Decision
Suppor
t,
Functional
Support & Effects
STAR
JOCS/G2 BISA/GP3 (HQ ARRC only) Full Intelligence BISA
BRACIS/BATESBRACIS NT
ADCIS
BATES
WAH-64 GSS
ACCESS
ASH
ATacCS
FOCSLE
MIP Database/US-GCCS
PJHQ
NIDTSNSWAN
DII(F)
SGIS/Medical BISA?
NBC BISA
IGBAD IOC
DII(F)
FCBISA/IFPA
JTFHQ
GCCS,
AM BISA?
GRIFFIN
ACCESS
Air Support BISA?
MAKEFAST/EOD BISA Intelweb
FALCON CMS/BCMS/CORMORANT CMS
DBL II FOC
Intelweb
ACCS LOC1Comp
Cmds
AFATDS II
JOCS/E-IARRCIS MLI/RNCSS
BOWMAN IOC/ATacCS/II EOC
DII
DII
BOWMAN PUDT, BRAD
N
I
M
R
O
D
JOCS, JC2SS(C),
JTOC IOC, JCS
Log, RN CSS
O
JOCS/E-IARRCIS MLI/RNCSS
JOCS/ARRC C2IS/RNCSS
MIDB
DBL II IOC/DBL II FOC/BOWMAN
FOCDBL II FOC/BOWMAN FOC
Platform BISA IOC/FOC/BGTI
Pltm BISA FOC/BGTI
?
TACISYS 2
C
O
R
M
O
R
A
N
T
E
3
D
L/Log/SF CC
JOCS, JC2SS(C),
JTOC IOC, JCS Log
MCC
RN CSS,
JC2SS( C),
JTOC IOC,
ACC
NICC, NIRS, JPC,
RAF CCIS,
JC2SS(C), JTOC
IOC, NBC BISA
NIDTSNSWAN
E-IARRCIS,
GP3, GP3 G2, AP3
ARRC
FIST/BOWMAN PUDT, BRAD
DII(F)
O
MIP Msg
and Communications Infrastructure
A
S
T
O
R
TACISYS 2
O
DII(F)
ATacCS, AP3
TACISYS 2
ASCA
O
Div
GRIFFIN
P
1
RN CSS,
JC2SS( C),
JTOC IOC,
AD BRIC, NBC,
E Plt, EOD BISAs,
E ComBAT, BSAM, FCA
O
O
D
E
T
T
E
BMETS
MIP
Developing the MOD Architectural Framework
ASCA
Bde
DII(F)
ATacCS, AP3
TACISYS 2
AD BRIC, NBC,
E Plt, EOD, BAMPS
BISAs, E ComBAT,
BSAM, FCA
D
B
S
AH MPS
P
E
I
A
R
R
C
I
S
F
A
L
C
O
N
P
t
a
r
m
i
g
a
P n
i
l
o
t
I
A
&
B
S
k
y
n
e
t
4
A
L
E
S
B
O
W
M
A
N
BMETS
O
I
n
f
r
a
s
t
r
u
c
t
u
r
e
R
A
P
T
O
R
M
R
A
4
TACISYS 2
DII(F)
GCCS
J
O
C
S
DACCS/JFACC
SGIS
NBC BISA/BATES
AD BriC
FCA
IS INFRASTRUCTURE
JOCS/E-IARRCIS/RNCSS
ATacCS
ATacCS
CASH (SLI/RLI)/EMS
UNICOM/EMS
JOCS, JC2SS(C),
JTOC IOC, JCS Log,
RN CSS, RAFCCIS
CWAN
GCCS,
GRIFFIN
Log C4I?/G1 BISA?
AFATDS
Infrastructure
Lychgate
AP3
BCMS/CORMORANT CMS
II IOC/II FOC
Comms
Intelweb
CRONOS (IPM only)
Bi-SCAIS
CWAN (IPM only?)
US-GCCS (IPM only)
MIP Messaging/US-GCCS
RNCSS/LPD(R)/T22/T23/T42/CVS RNCSS/LPD(R)/T22/T23/T42/CVS/T45
JFAC (IPM only)
RAFCCIS/JFAC
AP3/QP24
Epoch 2
MIDB, LOCE
MIDB/LOCE
INTELWEB?
JCS Log JCS Log
NIUTS/NSWAN
B
I
E
I
I
I
n
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)
OV-1
Overview
OV-2
Organisations
OV-5
Processes
Developing the MOD Architectural Framework
Common Language
MODAF
Enterpris
e Arch.
Taxonomy
MODAF
Meta
Model (M3)
Object
Taxonomy
Architectural
Repository
system
weapon system
business system
A system
which has the
capability to…
A system which
manages the…
HR system
accounts system
A system which
manages the…
A system which
manages the…
etc …
Developing the MOD Architectural Framework
Common Language
• Bringing together systems, organisations and processes
• Re-using architectural components
Bowman
Falcon
FRES
Skynet
Warrior
Challenger
AWACS
Watchkeeper
Phoenix
Developing the MOD Architectural Framework
Robust Analysis
CRD/Capability
Taxonomy
StV-2
StV-3
StV-4
…
StV
Capability
Management
Gap
• MODAF supports robust analysis at
a progressively more detailed level
• Capability issues and gaps are
understood
• View points are joined up
URD
Scenarios
OV-1
OV-2
OV-3
…
TV-1
TV-2
User
Requirements
OV
Acquisition
Cycle
SRD
TV
Procurement
Standards
CIP
SV-1
SV-2
SV-3
…
SV-8
SV-9
SV
Fielding
AcV
AcV-2
Developing the MOD Architectural Framework
Pan Defence Stakeholder Involvement
• Operational plans made with greater effect through wider
stakeholder involvement
Developing the MOD Architectural Framework
Benefits Realisation
• Reducing the amount of rework and cost overrun
through application of MODAF in conjunction with
supporting initiatives
Before:
After:
Developing the MOD Architectural Framework
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)
User
group
Tech
Group
User (eg ECC, FLC,
DPA, DCSA, IA)
Suppliers, (eg IA,
DG(Info),DCBM(A))
CCII / DD
Interop
DEC CCII
MODAF Partners
Developing the MOD Architectural Framework
MODAF Project Schedule
• Initial documentation – April 2005
– MODAF Handbook & ECC Deskbook
• First version of MODAF released – August 2005
Development Stage
Bridging Phase
Mandate
Start-up
Produce Products
Interim Guidance
Development
Initial Development
Pre-Pilot work
Roll-out Stage
MODAF User Help Facility
COI Deskbooks
Tiger Team Support
Pilot work
Training
Developing the MOD Architectural Framework
Maintain
Implementation Timeline
2005
•
•
Mar 05
Apr - Jul 05
•
Aug 05
•
Apr 06
Handbook and 1st COI Deskbook in draft
MODAF pilots and development of documentation
and remaining Deskbooks
MODAF V1 issued
2006
MODAF expected to be mandated for all IAB
business cases
Developing the MOD Architectural Framework
Agenda
• Engagement Objectives
• MODAF Overview
• MODAF Concepts & Doctrine Deskbook
• Developing common understanding of Concepts
& Doctrine process
• Related Views and Potential View Uses
• Next Steps
Developing the MOD Architectural Framework
MODAF Supporting Materials
Concepts
& Doctrine
MODAF
MODAF
Volume 1
Volume 2
Executive
Handbook
Summary
COI
MODAFDeskbo
COI ok
COI
Deskbo
Deskbook
ok
(x 5)
• MODAF Overview • Technical Spec
• COI Practical Guidance
•
•
•
•
• MODAF Views Informing
Business Processes and
Activities
• Worked Examples Of
MODAF View Development
In Support Of Processes
MODAF Composition
Concept Of Use
Benefits
Tool Support
• Detailed
Descriptions Of
MODAF Views
Developing the MOD Architectural Framework
MODAF COIs
Concepts & Doctrine
Doctrine
Concepts &
Doctrine
Operations
Capability Gaps
Future Op
Needs
Customer 2
Acquisition
Capability Mgmt
Capability
Management
C
Funded
Options
A
C
D
A
M
D
I
M
D
I
Sustain
Developing the MOD Architectural Framework
D
COI Deskbooks
1. Foreword
2. Introduction
3. MODAF relationship to COI
business process and
activities
4. Worked example(s)
+ N x Reference Guides
•
•
Reference guide to COI
process usage of MODAF
views
Pocket guide format
Developing the MOD Architectural Framework
Agenda
• Engagement Objectives
• MODAF Overview
• MODAF Concepts & Doctrine Deskbook
• Developing common understanding of Concepts
& Doctrine process
• Related Views and Potential View Uses
• Next Steps
Developing the MOD Architectural Framework
Process from COI Workshop – Dec 04
Developing the MOD Architectural Framework
7-Step JDCC Process
The Seven Step Process
Step 1: Capability Identification
Step 2: Future Capability Reconciliation
Step 3: Concept Generation
Step 4: Capability Development and Assessment
Step 5: Capability Selection and
Endorsement
= Steps in the process
Step 6: CADMID/T Validation
Step 7: LoD Oversight
SRO / SPA
Transition
Point
Initial Gate
Main Gate
Capability in Use
Lessons Identified / Feedback / Op Experience Gp
Gap Analysis:
-Across the epochs
-Against existing and future
capabilities
Direction and Prioritisation
JDCB (+) Part 1
1
Concept Generation
3
DSG a DMB Endorsed process
Futures Work
- DCF Structure
- Initial Implications for DLoDs
DSG
Future Capability
Development
HLOA
JHLOC
6
DOCTRINE
5
DPA
DPA
DIST
Strategic
Trends
Continued validation and
refinement of
concepts and capability
Joint Concepts
Environmental
Concepts
FMOC/FLOC/FAOC
Environmental
Sub-concepts
Draft
CONOPS
PPSG
Selection and
Endorsement
CONOPS
(A Range of
Capabilities)
CONEMP
(A Capability)
CONUSE
(An Eqpt)
2
EP/STP
CAPABILITY
4
Validation/Refinement Cycle
JDCB(+) Part 2
(JOCC Management)
JCB Capability Pull & Concepts + Doctrine push to achieve
transparency
Issues: (Across all DLODS)
7
1. Coherence to Conceptual Provenance.
2. Reduction of Technical Risk
3. Risk analysis and risk register
DLOD / SRO Involvement: Information, Doctrine and Concepts, Equipment,
Personnel, Training, Organisation, Interoperability and Logistics
4. Affordability
5. Implications of Real World Change
Developing the MOD Architectural Framework
Combined Concepts & Doctrine Process
Step 1
Step 2
A. Pre-Analytical Concepts
Step 7
Step 5
Step 6
C. Applied Concepts
Step 3
Step 4
B. Analytical Concepts
Existing Capability
Futures Work
HLOC
Joint Vision
Doctrine
Future Capability
Development Paper
Draft
ConOps
Concepts
Endorsed
ConOps
ConEmp
ConUse
Concept To Capability
Capability
Management
C
Funded
Options
A
C
D
A
M
D
I
M
New
Capability
I
SOPs &
TTPS
Modified
Doctrine
D. Concepts & Doctrine In Delivery
Developing the MOD Architectural Framework
D
D
Break-out Session 1 – Concepts &
Doctrine Process
i.e. Applied Concept
Inputs (From)
•
Activities
•
Outputs (To)
Epoch
•
•
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
Developing the MOD Architectural Framework
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?
Developing the MOD Architectural Framework
Agenda
• Engagement Objectives
• MODAF Overview
• MODAF Concepts & Doctrine Deskbook
• Developing common understanding of Concepts
& Doctrine process
• Related Views and Potential View Uses
• Next Steps
Developing the MOD Architectural Framework
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
Developing the MOD Architectural Framework
Strategic Views
StV-1
Op Concept
StV-5 Cap / System
Deployment
StV-3 Cap Phasing
Capability
Functions
Epoch 1
Epoch 2
Epoch 3
Information Acquisition
Strategic
Operational
Tactical
NEMESIS
NEMESIS
SPECS
LOOKER
Information Management
Analysis
NEMESIS
NEMESIS
Fusion
NEMESIS
NEMESIS
Quality
Assurance
NEMESIS
NEMESIS
Dissemination
BOWMAN, SAT
BOWMAN, SAT
Effects
Information
Acquisition
1. Strategic
Information
Management
1. Analysis
Range: 120km 1000km
Duration: 24hrs
2. Operational
Effects
Targeting
Plan
Engagement
1. Targeting
Conduct
Accuracy: 10m
Engagement
BDA
2. Fusion
3. Quality Assurance
Information
Acquisition
BISA
CR2, MILAN,
FGA
CR2, FGA
FGA, SAT
FGA, SAT
3. Conduct
Engagement
Information
Management
Effects
CR2, FGA
Recce
FGA, SAT
X
Collate Intelligence
X
Conduct Estimate
X
2. Plan Engagement
Range: 20km - 120km
Duration: 20hrs
3. Tactical
LOOKER,
SPECS
BISA
Coordinate Plan
X
X
X
Attack
X
X
X
Range: 0km - 20km
Duration: 16hrs
4. Dissemination
4. Battle Damage
Assessment
StV-2 Cap Taxonomy
Recuperate
OVs
X
StV-6 Cap to Use Case Mapping
Developing the MOD Architectural Framework
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
Developing the MOD Architectural Framework
Operational Views
OV-2 Op Node Interactions
OV-1
Concept of
Operations
OV-3 Information Flows
Needline
ID
OV-6c Sequence
Diagram
OV-5 Activity Model
From
To
Content
Medium
1
PJHQ
BDE HQ
BDE TASKING ORDER
SAT COMM
2
BDE HQ
MAIN OPERATING BASE
BG TASKING ORDER
BOWMAN
3
MAIN OPERATING BASE
FIGHTING PATROL
PATROL TASKING ORDER
BOWMAN
4
FIGHTING PATROL
KESTREL
KESTREL TASK ORDER
UHF RX/TX
5
KESTREL
FIGHTING PATROL
TACTICAL ISTAR INFO
UHF RX/TX
6
BDE HQ
GROUND STATION
OPERATIONAL ISTAR TASK ORDER
BOWMAN
7
GROUND STATION
SPECS 2
SPECS 2 TASK ORDER
LINK 16
8
PJHQ
AIRCRAFT CARRIER
STRATEGIC ISTAR TASK ORDER
SAT COMM
9
AIRCRAFT CARRIER
NEMESIS
NEMESIS TASK ORDER
LINK 16
10
NEMESIS
AIRCRAFT CARRIER
STRATEGIC ISTAR INFO
LINK 16
11
NEMESIS
GROUND STATION
STRATEGIC ISTAR INFO
12
SPECS 2
GROUND STATION
OPERATIONAL ISTAR INFO
13
BDE HQ
14
MAIN OPERATING BASE
15
FIGHTING PATROL
16
GROUND STATION
BDE HQ
17
AIRCRAFT CARRIER
PJHQ
<< entity >>
<< entity >>
relationship_1
Entity 1
-attribute_1:string
-attribute_2:int
PJHQ
BDE HQ
MAIN OPERATING BASE
0..1
Entity 2
*
-attribute_3:int
BDE AFTER ACTION REPORT
BG AFTER ACTION REPORT
PATROL AFTER ACTION REPORT
relationship_4
OPERATIONAL ISTAR INFO
STRATEGIC ISTAR INFO
1..*
relationship_3
relationship_2
<< entity >>
Entity 3
-attribute_4:date
<< entity >>
Entity 4
-attribute_5:boolean
Developing the MOD Architectural Framework
LINK 16
LINK 16
SAT COMM
BOWMAN
OV-7
Information
Model
BOWMAN
BOWMAN
SAT COMM
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
Developing the MOD Architectural Framework
OVs
System Views (1)
SV-1 System Interconnections
SV-5 Op Activity to
System Mapping
<< entity >>
<< entity >>
relationship_1
Entity 1
-attribute_1:string
-attribute_2:int
Entity 2
*
-attribute_3:int
0..1
relationship_4
1..*
relationship_3
Needline
ID
SV-3 System Interfaces
From
To
Content
relationship_2
Medium
Entity 3
-attribute_4:date
1
PJHQ
BDE HQ
BDE TASKING ORDER
SAT COMM
2
BDE HQ
MAIN OPERATING BASE
BG TASKING ORDER
BOWMAN
3
MAIN OPERATING BASE
FIGHTING PATROL
PATROL TASKING ORDER
BOWMAN
4
FIGHTING PATROL
KESTREL
KESTREL TASK ORDER
UHF RX/TX
Entity 4
5
KESTREL
FIGHTING PATROL
TACTICAL ISTAR INFO
UHF RX/TX
-attribute_5:boolean
6
BDE HQ
GROUND STATION
OPERATIONAL ISTAR TASK ORDER
BOWMAN
7
GROUND STATION
SPECS 2
SPECS 2 TASK ORDER
LINK 16
8
PJHQ
AIRCRAFT CARRIER
STRATEGIC ISTAR TASK ORDER
SAT COMM
9
AIRCRAFT CARRIER
NEMESIS
NEMESIS TASK ORDER
LINK 16
10
NEMESIS
AIRCRAFT CARRIER
STRATEGIC ISTAR INFO
LINK 16
11
NEMESIS
GROUND STATION
STRATEGIC ISTAR INFO
LINK 16
12
SPECS 2
GROUND STATION
OPERATIONAL ISTAR INFO
LINK 16
13
BDE HQ
PJHQ
BDE AFTER ACTION REPORT
SAT COMM
14
MAIN OPERATING BASE
BDE HQ
BG AFTER ACTION REPORT
BOWMAN
15
FIGHTING PATROL
MAIN OPERATING BASE
PATROL AFTER ACTION REPORT
BOWMAN
16
GROUND STATION
BDE HQ
OPERATIONAL ISTAR INFO
BOWMAN
17
AIRCRAFT CARRIER
PJHQ
STRATEGIC ISTAR INFO
SAT COMM
SV-6 Data Flows
Developing the MOD Architectural Framework
<< entity >>
<< entity >>
SV-11 Data Model
System Views (2)
SV-4 System Functions
SV-1 System Interconnections
SV-7 System
Performance
TVs
SV-9 Technology Forecast
SMTP
TCP/IP
Ethernet
CAT 5 Cable
System 3
Port: 3c
3-5 e-mail
System 5
Port: 1a
1-3 Operational Feedback
SHORT TERM
MEDIUM TERM
SV-8 System Evolution
LONG TERM
APPLICATION SOFTWARE
PLCS DEX 7
HTTP
TCP/IP
Bowman
System 1
TECHNOLOGY FORECASTS
TECHNOLOGY AREA
Port: 5f
OFFICE APPLICATIONS
MICROSOFT OFFICE 2000
MICROSOFT OFFICE 2005
(DISTRIBUTED)
MICROSOFT DISTRIBUTED
OFFICE APPS
BUSINESS
APPLICATIONS
INDIVIDUAL APPS - BATES,
QP24
BISA'S
INTEGRATED BISA SUITE
APPLICATION PLATFORM
System 3
DATA MANAGEMENT
ORACLE 9
ORACLE 10
OPERATING SYSTEM
WINDOWS 2000
Port: 3b
SV-2 System Interoperability
NEXT WINDOWS OS
OPEN SOURCE OS
EXTERNAL ENVIRONMENT
USER INTERFACE
THIN TOUCH SCREEN
BIOMETRIC INTERFACE
STORAGE
HDD
SOLID STATE MEMORY
CHIPS
ORGANIC STORAGE
COMMS
BOWMAN
BOWMAN+VOIP
ALL IP COMMS
Developing the MOD Architectural Framework
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
Developing the MOD Architectural Framework
Technical Views
TV-1 Technical Standards Profile
TV-2 Standards Forecast
T RM
CATEGORY
ST ANDARDS FORECASTS
SHORT TERM
M ID T ERM
LONG TERM
(1 year)
(3 years)
(5 years)
Application Platform
Data Interchange
Document Interchange
Mapping
Security Marking DTD – in
CAPCO coordination (proposed
IC standard)
Geography DTD 2.0 – accepted
by GIS Consortium
?
Commercial products that
use the standard become
available
Geospatial XSD – in
coordination Open GIS
Communications
Electronic Mail
W orld W ide W eb
Services
Communications
Transport Ser vices
Geospatial XSD – accepted by
Open GIS
IETF RFC2060 Internet
Mail Access Protocol
(IMAP) – accepted,
replaces de facto standard
IETF - Common Gateway
Interface (CGI) 1.2 – becomes
proposed standard
IETF –Common Gateway Interface
(CGI) 1.2 – accepted, replaces CGI
1.1, the de facto standard
IETF – RFC 2818 HTTP Over TLS –
accepted, replaces RFC 2616
IETF –W ireless Extensions
to TLS – becomes
proposed standard
IETF – RFC 2002 IP
Mobility Suppor t - accepted
Security
Developing the MOD Architectural Framework
IETF –IPv4 Mobile IP Protocol –
becomes propose standard
IETF - RFC 2246 The Transport
Layer Security (TLS) Protocol
Version1.0 – accepted; replaces
SSL
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
Developing the MOD Architectural Framework
Acquisition Views
Generic AcV-2 System of Systems Acquisition Programmes
JCB NEC Roadmap – AcV-2 Format
Developing the MOD Architectural Framework
Break-out Session 2 – View Mapping
Input
Views
StV1
AcV2
Output
Views
Concept &
Doctrine Area
Activities
•
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
StV1
OV1
•
•
NOTE: There may be inputs,
activities or outputs with no
relevant Views, and there will
certainly be some with multiple
relevant Views
Developing the MOD Architectural Framework
Agenda
• Engagement Objectives
• MODAF Overview
• MODAF Concepts & Doctrine Deskbook
• Developing common understanding of Concepts
& Doctrine process
• Related Views and Potential View Uses
• Next Steps
Developing the MOD Architectural Framework
Concepts & Doctrine – Next Steps
8 July
Internal
Release
15 July
Release
Review
Deadline
Engagement
Development
Release
Review
29 July
Formal
Draft
Release
Update
12 August
Formal
Review
Deadline
16 August
Review
Board 26 August
Detailed
Full
Review
Release
Initial
Sift
Finalise
Baseline
Developing the MOD Architectural Framework
ECC – Information
Superiority
Points of Contact:
• Project Manager
[email protected]
0207 807 8884
• Concepts & Doctrine COI lead
[email protected]
07841 947175
• MODAF development POC
[email protected]
07887 540406
Developing the MOD Architectural Framework
IA
Articulating Concepts & Doctrine
• From the abstract to the tangible…
StV-1
Articulate Analytical
Concepts/ Doctrine
Operational Viewpoint Suite
StV-1
OV-1
OV-2
OV-4
Articulate ConOps/
ConEmp/ ConUse
Operational Viewpoint Suite
StV-6
OV-1
OV-2
OV-3
OV-4
OV-5
Articulate SOPs/ TTPs
Developing the MOD Architectural Framework
OV-6
Supporting Concept Development
• Operational analysis informing the
development of applied concepts…
Strategic
Viewpoint Suite
Operational
Viewpoint Suite
System
Viewpoint Suite
Technical
Viewpoint Suite
Operational Analysis
Analyse Operational
Capability
Articulate Operational
Capability &
Characteristics
Developing the MOD Architectural Framework
Specifying Concepts & Doctrine
• Specifying the use of concepts, doctrine,
SOPs/ TTPs across military organisations
and levels…
Specify Use Of
Concept & Doctrine
Publications
(Levels 2-5)
TV-1
Developing the MOD Architectural Framework