On The Road To Jointness

1
(No Transcript)
2
On The Road To Jointness?

• Have the COURAGE to transition to or be born
  joint?
• Have the HEART to integrate capabilities?
• Have the BRAIN to use JCIDS and get everyones
  input?
• Have a transformation strategy and PLAN?

3
Who We Are

• JII (Joint Interoperability Integration)
• J85
• Reviewers of your documents
• Jointness
• Interoperability
• We see about 300 program documents per year
• Joint Requirements Trainers
• TRADOC
• MCCDC
• AFXOR
• N81
• Over 60 programs
• J84
• C2 Functional Capabilities Board

4
Who We Are
5
Course Emphasis

• Mission-centric approach to Capabilities-Based
  Requirements
• Problem Solving and Investigation
• Data Mining
• Processes
• Development of DOTMLPF requirements
• Big DOTMLPF - little dotmlpf
• Testability and measurability
• Requirements and function to anchor integrated
  architecture
• Interoperability the NR-KPP

6
What We Cover in Follow On Training

• CDDs
• CPDs
• Mission Assessment Process
• Spiral Acquisition/Development
• Net Ready KPPs
• Implementation Requirements
• Transformation Change Packages
• C2 Functional Concept

7
Points of Order

• Were not here to debate
• The purpose of this visit
• Jointness
• DOTMLPF Requirements
• 3170 and 3180
• NR-KPP
• Road to Approval
• Recommendations
• Comment
• Joint perspective
• DOTMLPF Perspective
• Speed up the process
• Ensure youve made your case

8
Joint Capabilities Integration and Development
System
The CJCSI 3170
9
Future Requirements Future Threat Future
Capabilities
Future military goals are a moving target. You
have to know which point in the future you are
aiming for, you must be looking in the direction
of your target, and you must continually adjust
your sites.
2020
2001
2010
2005
10
Introduction
The New 3170 Environment

• May the best man win. You compete.
• You have to make your case to the Functional
  Capabilities Board.
• How well you address spiral development could
  mean the difference between getting the nod to go
  into full production and getting your program
  canceled.
• No way of getting around the type of analysis
  that was in the old MNS.
• The answer must address DOTLMPF. Even if you are
  on the material only path, you will still be
  required to address all DOTMLPF factors.

11
Introduction
For better or worse

• A capabilities-based requirement is still a
  requirement
• Capabilities-based requirements are the kind of
  mission centric requirements the DOD has been
  talking about since Cohen kicked off the Y2K
  operational evaluations
• It doesnt matter how many time JCS changes the
  requirements systems or OSD overhauls the
  acquisition system, the analytical method to
  produce these documents hasnt changed
• They dont expect you to define requirements with
  100 percent accuracy anymore.. Perfection is no
  longer the goal. What they want is the best we
  can do for now.

12
Introduction
Foundational Principles
13
Master Process

• Visualize the operating environment
• Apply common scenarios
• Provide context to the mission need

• Issues
• Capabilities
• Requirements

• Obsolescence
• Observations
• Lessons Learned/After Action
• Experimentation
• Technical/RD
• Management Directive

Trigger Event
ClearStep Process
Benchmark Process
Put effort in context
Scope Effort
Impact Interoperability

• Task Decomposition
• Operational Thin Lines

ID GIG producers consumers for specific events
Ensure youve captured ALL the major, relevant
issues
Family of Systems Matrix
IER Matrix
COI or pt to pt
Full Spectrum Analysis Process
JMT Process

• Ties Ops Arch to Sys Arch
• Begins to ID focus COIs

Pick list of templates to view effort from
different perspectives to capture implications
across DOTMLPF

• Relevance
• Decomposition

• Data Correlation
• Threads capability needs to architecture products

Operational Concept Matrix

• Ties it all together
• Facilitates OPS Concept narrative

14
System of Systems

• System of System A set or arrangement of
  systems that are related or connected to provide
  a given capability. The loss or any part of the
  system will degrade the performance or
  capabilities of the whole.

15
Family of Systems

• A set or arrangement of independent systems that
  can be arranged or interconnected in various ways
  to provide different capabilities. The mix of
  systems can be tailored to provide desired
  capabilities dependent on the situation.

• Public rail-based system
• Virginia Rail Express (VRE) Fredericksburg to
  Crystal City
• Metro Rail (Yellow, Orange, Blue, Red, Green)
• Public road-based system
• DC buses
• Fairfax Connector
• Commuter buses
• Commuter vans
• School buses
• Private road-based system
• Privately owned vehicles
• Taxis
• Limousines

16
Symbiosis
Foundational Principles
Operational analysts
System analysts

• System functionality
• SOS functionality
• FOS functionality interoperability
• System design

Mission Functions

• Operational functions
• Operations
• Activities
• Events

System Functionality
Operational Requirement
System Requirement

• Attributes which directly effect
  mission performance
• Distance
• Timeliness
• Security
• Survivability

• System attributes and specifications which define
  HOW the system must perform to support the
  mission
• Range
• Speed
• Data Integrity
• Hardness

Material Qualities
Drivers and Barriers
Operational Performance Requirements
System Performance Requirements
ST
Intelligence Considerations
JMETLs, SMETLs, other theater considerations
Network Considerations
Human Interface
EnvironmentalConsiderations
Battlespace AOR
Operational IERs
System IERs
FOS Considerations
Interoperability Considerations
17
Mission Assessment Process
Dendritic Model
18
Interoperability

• C4I
• Connectivity
• Processing
• Protocols and standards
• Display
• DOTMLPF
• Theater FoS Considerations

19
Why Function?
20
Why Function?

• The key to understanding where a problem is
  occurring and initiation of the formulation of
  architecture views which demonstrate which
  mission threads or business processes are/will be
  effected is understanding the organization and
  its component functions.
• Even though the mission of a hospital is provide
  quality and affordable patient care, support
  (sometimes referred as Administrative) is always
  broken out as a separate set of functions.
• While critical to the accomplishment of the
  overall mission, support functions and
  operational functions performance goals are
  slightly different. Support functions are judged
  solely on how well they support the front line.
  Operational functions are judged on the extent
  they meet command operational objectives.

21
What is Function?
Merriam-Websters says

• professional or official position OCCUPATION
• the action for which a person or thing is
  specially fitted or used or for which a thing
  exists PURPOSE
• any of a group of related actions contributing to
  a larger action especially the normal and
  specific contribution of a bodily part to the
  economy of a living organism

22
Functions Health Care Example
Support and Operations Are Different
Director
Support
Clinical
Personnel
Finance
Medical
Diagnostic Imaging
Quality Control
Surgery
Mental Health
Supply
MAS
Public Affairs
Lab
Pathology
Chaplain
Voluntary
Risk Assessment
Dental
Rehab
Engineering
Building Management
Pharmacy
Geriatric
IRM
Dietary
23
Support Operational

• The key to understanding where a problem is
  occurring and initiation of the formulation of
  architecture views which demonstrate which
  mission threads or business processes are/will be
  effected is understanding the organization and
  its component functions.
• Even though the mission of the hospital is
  provide quality and affordable patient care,
  Support (sometimes referred as Administrative) is
  always broken out as a separate set of functions.
• While critical to the accomplishment of the
  overall mission, support functions and clinical
  functions performance goals are slightly
  different. Support functions are judged solely
  on how well they support the front line staff
  (clinicians, pharmacists, medical technologists,
  etc.). Clinical functions are judged on the
  quality of patient care provided to customers.

24
Common Military Functions

• Personnel - J1
• Intelligence - J2
• Operations - J3
• Logistics - J4
• Planning - J5
• Communication - J6
• Training - J7
• Requirements - J8
• Concept Development - J9
• Finance
• Engineering
• Medicine
• Command and Control

25
Common Military Functions
Operations
26
Functional Decomposition
any of a group of related actions contributing to
a larger action
Function
Sub-functions
Operations
Functions
Operations
Plans Products
Functions
Operations
Plans Products
Activities Service Joint components
Activities Service Joint components
Planning Activities
Coordination Activities
Execution Activities
Planning Activities
Coordination Activities
Execution Activities
27
Functional Decomposition
any of a group of related actions contributing to
a larger action
28
Functional Decomposition
any of a group of related actions contributing to
a larger action
Deployment
Pre- Deployment
JRSOI
Movement to Activity at POE
Movement to POD
Reception
Staging
Onward Movement
Integration
Assemble forces
Prepare the force
Complete force integration
Prepare to receive the force
Conduct tactical assembly area ops
Marshal the forces
Onward Movement
Conduct POD operations
29
Define the Family of Systems
Understanding the Need
Family of Systems Matrix - Operational View
IER Sender/Receiver/Node Candidates

• Interoperability issues
• Connectivity
• Processing (network design)
• Protocols and standards
• Display
• DOTMLPF (for each command)
• Other in-theater drivers and barriers to
  interoperability

30
Staging
31
Why Function?