Who We Are

1
(No Transcript)
2
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

3
Who We Are
4
Purpose of Briefing

• To familiarize you with the most up-to-date
  capabilities development guidance
• To understand the basic components of the JCIDS
  process and how it will impact your programs
• To understand the underlying analytical
  approaches for producing these products (and
  stabilizing our efforts)
• To understand the CJCSI 6212 and the impact to
  programs
• Insight into Joint initiatives and trends which
  effect solution development

5
Course Emphasis

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

6
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

7
Acronym Survival Guide

• DOTMLPF doctrine, organization, training,
  materiel, leadership, personnel, facilities
• JCIDS Joint Capabilities Initiative Development
  System
• FCB Functional Capabilities Board
• JROC Joint Requirements Oversight Council
• FAA Functional Area Analysis
• FNA Functional Needs Analysis
• FSA Functional Solution Analysis
• ISP Information Support Plan
• GIG Global Information Grid
• NR KPP Net Ready Key Performance Parameter
• AMA Analysis of Materiel Alternatives

8
Acronym Survival Guide

• AOA Analysis of Alternatives
• DAB Defense Acquisition Board
• IER Information Exchange Requirements
• ICD Initial Capabilities Document
• CDD Capabilities Development Document
• CPD Capabilities Production Document
• SOS System of Systems
• FOS Family of Systems
• JOpsC Joint Operations Concept
• JOC Joint Operating Concept
• JFC Joint Functional Concept
• JIC Joint Integrating Concept

9
(No Transcript)
10
Material vs. Non-material
Multiple DOTMLPF Strategies
11
Interoperability

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

12
Why JCIDS?

• A person may have the ability to paint
• She may have a set of brushes, oils, and a canvas
  on which to paint
• But she still may not have the capability to
  produce a finished painting.
• She still needs
• A room with proper lighting
• Training and experience as a painter
• A vision or set of guidelines for what the
  finished product is supposed to look like
• Time

13
Why JCIDS?

• If you want a new portrait of your spouse to hang
  in the ballroom of your recently built castledo
  you simply order a set of paints?
• The old Requirements Generation System
  concentrated on the systems and system
  infrastructure piece of the solutions.
• Training was identified and often used as trade
  space.
• JCIDS focuses on delivering and refining
  full-spectrum solutions across DOTMLPF which
  result in new or improved capabilities.
• Program offices are no longer simply tasking a
  manufacturer with specifications to build a
  widget. You are also tasking military
  organizations across the services to develop and
  deliver
• training
• organizational changes
• implementation actions
• facility upgrades
• new or revised occupational specialties
• which result in capabilities solution whether
  or not materiel is involved.
• The old RGS was about writing a document.
• JCIDS is about delivering and managing a fielded
  solution.

14
What Does this Mean?

• More responsibility
• Responsible not only for the materiel portion of
  the solution, but also for all the other things
  needed to make your system work
• Increased scope
• Across the DOTMLPF spectrum
• Not just systems
• More control
• Have more input into how a capability will be
  executed
• More input into how a capability will spiral
  toward future goals and objectives
• More involvement over a longer period of time
• Long-term relationship with
• Functional Capabilities Board(s)
• Other programs in your Family of Systems
• JFCOM
• If C4I is involvedall the organizations and
  approval bodies responsible for ensuring you are
  net ready, net centric, interoperable, and
  working properly within the Global Information
  Grid (GIG)

15
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 sights.
2020
2005
2015
2010
16
What Changed?

• May the best man win.
• You compete.
• You must 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.

17
Additional Considerations

• 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 underlying analytical
  method to produce these documents hasnt changed
• JCS wants us to focus on ALL the products and
  services delivered in increments over a period of
  time that result in effective warfighting
  capabilities
• Thinkchange implementation and management
• 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.

18
The Old Way
CRD
Instructions - Manuals
Arch
Direction
Direction
C4ISP
TEMP
Acq Strat
ORD
MNS
Program Guidance
APB
LCCE
AoA
Drivers
Cumulative Rqmts
Service Rqmts
Spec
19
The New Way
JCD
IA
Instructions - Manuals
Global
Direction
Direction
TEMP
Acq Strat
CDD
FAA FNA FSA
ICD
Specific 1 for 1
Prgm Guidance
APB
LCCE
AoA
CPD
Drivers
Joint Rqmts
Service Rqmts
Spec
ISP
Cumulative Rqmts
20
ICD

• Makes the case for a materiel approach to resolve
  a specific capability gap
• Defines the capability gap in terms of
• Functional area(s)
• Relevant range of military operations
• Time
• Obstacles to overcome,
• Key attributes with appropriate measures of
  effectiveness, e.g., distance, effect (including
  scale), etc.
• Captures the evaluation of different materiel
  approaches that were proposed to provide the
  required capability
• Proposes the recommended materiel approach(s)
  based on
• Analysis of the relative cost
• Efficacy (the power to produce an effect)
• Sustainability
• Environmental quality impacts,
• Risk posed by the materiel approach(s) under
  consideration

21
ICD

• How the recommended approach best satisfies the
  desired joint capability
• Operational context for assessing the performance
  characteristics of alternatives
• Once approved, not normally updated
• Baseline document for
• FoS and SoS approaches
• Linkages between associated CDDs and CPDs
• Overarching DOTMLPF aspects necessary to meld the
  FoS or SoS into an effective capability

The CDD then serves as the living document to
carry contributing systems and subsequent
increments through the SDD phase.
22
ICD

• A tool that provides guidelines and performance
  standards to help services design, plan for, and
  budget for systems that function effectively in a
  Joint environment
• The building code, not the building
• What, not how
• Operational features and benefits to the
  warfighter
• Solid Operational Concept to assist the services
• A specific, time-phased illustration of your FoS
  concept and operational concept in action (use
  cases)
• How a capabilities benefits the performance of
  Joint Operations and Functional Areas
• Universal requirements
• Full spectrum DOTMLPF solutions

23
CDD

• The CDD provides the operational performance
  attributes necessary for the acquisition
  community to design a proposed system(s) and
  establish a program baseline.
• It states the performance attributes, including
  KPP that will guide the development and
  demonstration of the proposed increment.
• The performance attributes and KPPs will apply
  only to the proposed increment.
• If the plan requires a single step to deliver the
  full capability, the KPPs will apply to the
  entire system(s).
• Each increment must provide an operationally
  effective and suitable capability in the intended
  mission environment that is commensurate with the
  investment, and independent of any subsequent
  increment.

24
CPD

• Captures the information necessary to support
  production, testing, and deployment of an
  affordable and supportable increment within an
  acquisition strategy
• Provides operational performance attributes
  necessary for acquisition community to produce a
  single increment of a specific system
• Presents performance attributes, including KPP,
  to guide the production deployment of the
  current increment
• If plan requires a single step to deliver the
  full capability, KPPs will apply to the entire
  system(s)
• There may be cases where Validation Authority
  decides to use a combined CPD to describe closely
  interdependent systems that provide the desired
  capability
• Each increment must provide an operationally
  effective, suitable useful capability in the
  intended environment, commensurate with the
  investment.
• Refines threshold objective values for
  performance attributes KPPs that were validated
  in the CDD for the production increment
• Each production threshold listed in the CPD
  depicts the minimum performance that the program
  manager is expected to deliver for the increment
  based on the system design subsequent to the
  design readiness review.
• The refinement of performance attributes and KPPs
  is the most significant difference between the
  CDD and the CPD

25
ISP

• Intended to explore information-related needs
  required to support operational functional
  capabilities
• Provides a mechanism to identify and resolve
  implementation issues related to IT, including
• National Security Systems (NSS
• Infrastructure support and
• IT and NSS interface requirements
• Identifies IT needs, dependencies, and interfaces
  for programs in all acquisition categories,
  focusing attention on
• Interoperability
• Supportability
• Synchronization
• Sufficiency and
• Net-centricity
• The architecture documentation previously
  captured in the C4ISP is now required in the
  JCIDS documents.
• The ISP will use the architecture from JCIDS
  documentation and focus on analysis.

26
ISP

• A completed ISP answers the following seven
  questions for information needed to support the
  operational/ functional capability(ies).
• What information is needed?
• How good must the information be?
• How much information? (needed or provided)
• How will the information be obtained (or
  provided)?
• How quickly must it be received in order to be
  useful?
• Is the information implementation net-centric?
• Does it comply with DoD information policies?

27
FCB Structure

• Functional Capabilities Board (FCB)
• FO/GO chair with 0-6 equivalent representatives
  from Services, COCOMs, Agencies
• Sponsor Coach / Warfighter Advocate / JROC
  Advisor
• Evaluates program on ability to meet joint needs
  and fill capability gaps
• Formal FCB Working Group
• Service, COCOMs (at their option), Agency reps
• Pre-brief prior to formal review by the FCB
• Evaluates format, content and identifies ALL
  issues prior presentation to the FCB
• Proposes FCB Recommendation to JCB
• FCB Working Group (FCB WG)
• FCB Subject Matter Experts (SMEs) - small subset
  of the working group above
• Informal group responsible for shepherding
  document through the JCIDS and monitoring
  program development and contribution to the
  Integrated Architecture
• Helps sponsors understand and comply with changes
  policy, etc., during life of the program to
  ensure success.

28
FCB Help Not Hammer Approach
29
Where FCBs Fit
30
JCIDS Document Approval
Submit JCIDS Document To KMDS
Sponsor prepares JCIDS Document
JCIDS document undergoes O-6 Review (25 Days)
Go to Binning Process
Submit revised JCIDS Document To KMDS
Sponsor adjudicates O-6 comments (15 Days)
Revised JCIDS document undergoes Flag Review
(21 Days)
Sponsor adjudicates Flag comments (15 Days)
Submit revised JCIDS Document To KMDS
Sponsor presents program to FCB WG
Sponsor presents program to FCB
Sponsor presents program to JCB/JROC for
approval/validation
This process is valid for all JCIDS documents -
ICDs at Milestone A, CDDs at Milestone B and
CPDs at Milestone C.
31
(No Transcript)
32
Symbiosis
Operational (qualitative) Analysis
System (quantitative) analysis

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

Mission Functions

• Operational functions
• Operations
• Activities
• Events

System Functionality
Operational Capabilities
System Requirements
i.e.
i.e.

• 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 Measures
System Performance Characteristics
ST
Intelligence Considerations
JMETLs, SMETLs, other theater considerations
Network Considerations
Human Interface
EnvironmentalConsiderations
Battlespace AOR
Operational IERs
System IERs
FOS Considerations
Interoperability Considerations
33
Function

• The early identification of functions and
  sub-functions will help
• Find, define, and clarify issues
• Establish relationships between operational
  issues and required capabilities (Functional
  Needs Analysis)
• Establish relationships between required
  capabilities and operations (Functional Area
  Analysis)
• Establish relationships between operations and
  Joint Missions and Tasks (Functional Area
  Analysis)
• To identify and understand
• Families of Systems
• Systems of Systems
• Communities of Interest

34
Why Function?
DOMAINS!
35
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

36
Capabilities Building Blocks
37
Joint Mission Thread Process
38
Define the Family of Systems
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

39
Full Spectrum Analysis

• What are they?
• What should they be?
• Do the warfighters have them?
• Are they adequate for the task?

40
Getting at the Right Issues
41
Why Spend Time on the Issues?

• To properly identify and describe what
  constitutes improved mission performance
• Not just recognize pain, but understand the
  causes
• Multiple choice vs. essay
• Efficiently identify a set of detailed
  capabilities and capabilities-based requirements
• CBRs naturally flow from well defined issues
• Good issue sets
• Make identification of architectures easier
• Make writing an operational concept for your
  program easier, and
• Help answer questions from approval authorities
• Help justifying solutions to approval authorities

42
Operational Concept Matrix
State purpose, goals, and overarching capability
in terms of warfighter benefits. (Why?)
Major Functional Areas
Sub-functions
Operations
System Types
WHAT?
WHO?
WHEN?
WHERE?
HOW?
- Threads to Operational Architecture, of
which the operational IER is a subset - Keeps
everybody working off of the same sheet of
music - Facilitates assessment of a
pre-existing Operational Concept. - Yields Ops
Concept, Testable and Measurable Requirements,
and KPPs
43
Mission Assessment Process
Functions
44
FCB Oversight
Issues
BIG DOTMLPF AOA
Operational Requirements
Integrated DOTMLPF Strategy
(Key) Performance Parameter
Threshold
Functional Requirements
Mission Context
Condition of Success
Attribute
Objective
little dotmlpf The fielded solution
Doctrine Support Plan Products
Facilities (Engineering) Support Plan Products
DOTMLPF Change Request
Training Support Plan Products
Organizational Support Plan Products
C4I Support Plan. Specs, etc. Products
Leadership Support Plan Change Mgmt Products
Personnel Support Plan Products
45
(No Transcript)
46
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.

47
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

48
MNS versus ICD

• MNS
• Talks to mission need
• Looks at non-materiel and materiel alternatives
• Developed bottom-up
• Good forever

• ICD
• Captures the analysis
• Framed by common concepts
• Whats the desired capability?
• Insufficient analysis gets help
• Evaluates multiple materiel approaches
• Recommends a specific materiel approach
• Addresses a single capability
• Archived at MS-B

Some similarity in content . . . the difference
is in the analysis and the common joint picture
49
Different Material Approaches

• Legacy Service Life Extension Program
• Legacy New Production
• Legacy Modification/Upgrade
• Legacy new technology
• New Technology integrate with legacy FoS/SoS

50
ICD Flash Cards

• 4. Capability Gap
• Missions functions that cant be performed or
  are unacceptably limited (operational
  deficiencies)
• Linkage between the required capabilities and
  appropriate JOCs, JFCs, JICs and integrated
  architectures.
• Attributes of the desired capabilities in terms
  of desired effects. Broad descriptions of desired
  effects help ensure that the required
  capabilities are addressed without constraining
  the solution to a specific, and possibly limited,
  materiel system (Conditions of Success).
• Capability definitions
• Must contain required attributes w/ MOEs, e.g.,
  time, distance, effect (including scale) and
  obstacles to be overcome
• General enough to not prejudice decisions in
  favor of a particular means of implementation
• Specific enough to evaluate alternative
  approaches to implement the capability

1. Joint Functional Area. Cite applicable
functional area(s), JFCs, ROMOs, and timeframe
under consideration.

• 2. Required Capability
• Describe the particular aspects of the JFCs that
  the ICD addresses
• Explain why desired capabilities are essential to
  Joint force commander for achieving military
  objectives
• Reference any CRDs (integrated architectures when
  available) that may be applicable to this ICD.

• 3. Concept of Operations Summary
• Describe what mission areas this capability
  contributes to
• Operational outcomes it provides
• Effects it must produce to achieve those outcomes
• How it benefits the integrated joint warfighter
  and
• Enabling capabilities required to achieve desired
  operational outcomes.

• 5. Threat/Operational Environment
• Operational environment in which capability must
  be exercised
• Organizational resources that provided threat
  support to capability development efforts
• Current projected threat capabilities (lethal
  and nonlethal) to be countered
• Current DIA validated threat documents and
  Service intelligence production center approved
  products or data used to support initial JCIDS
  analysis

51
ICD Flash Cards

• b. Ideas for Materiel Approaches
• If a materiel solution is required, list materiel
  approaches considered during the analysis
• Leverage expertise of components, laboratories,
  agencies industry to provide a robust set of
  divergent materiel approaches that includes
  single multi-service, multi-agency, allied
  other appropriate FoS or SoS approaches.
• Indicate potential areas of study for concept
  refinement.
• May include the use of existing and future
• US military systems
• Allied military systems
• Commercial systems, including
• Modified commercial systems or
• Product improvements of existing systems.

• a. DOTMLPF Analysis.
• Summarize results of DOTMLPF analysis
• ID changes in US or allied doctrine, operational
  concepts, tactics, organization, and training
  that were considered in satisfying the deficiency
• Describe why DOTLPF changes were inadequate in
  addressing the complete capability
• Summarize DOTLPF needed to provide the complete
  capability

• c. Analysis of Materiel Approaches (AMA)
• Summarize how well the proposed materiel
  approaches address capability gaps, using
• JROC-approved key attributes
• MOE of the functional area integrated
  architecture
• Address all identified materiel approaches
  reviewed by the analysis body.
• Prioritized list of materiel approaches ranked by
  how well each provides the capabilities required
  by the user.
• AMA will consider the integrated architecture
  approved MOE, technological maturity and the
  overall impact of the solution on the functional
  and cross-functional areas.
• Materiel approaches are always a combination of
  materiel and non-materiel solutions that deliver
  the desired capability through an FoS/SoS
  approach.
• For FoS/SoS approaches, the analysis will
  identify the impact of synchronization on the
  approach.

52
ICD Flash Cards

• 7. Final Material Recommendations
• Best material approaches based on analysis of
• Relative cost
• Efficacy
• Performance
• Technology
• Maturity
• Delivery time frame
• Risk
• Recommendations for further analysis during
  Concept Refinement and Technology Development
• If evolutionary acquisition approach, minimum
  capability required to fill gap in paragraph 2 of
  ICD (near term and long term)
• If proceeding immediately to milestone B or C,
  material recommendations proposed to be further
  analyzed during SDD (System Development and
  Demonstration)
• Key boundary conditions within which AoA should
  be performed
• Constraints crafted to allow reasonable
  compromise between focusing AoA and ensuring AoA
  considers novel/imaginative alternative solutions
• Must reflect thorough understanding of
  functional/operational areas and conditions under
  which ultimate system(s) must perform
• Non-material/DOTMLPF implications/constraints of
  recommended material approach or approaches

• Mandatory Appendices
• Appendix A Integrated Architecture Products
• Operational View (OV-1)
• Others as desired (only those not otherwise
  presented in document)
• Appendix B References
• Appendix C Acronym List
• Other Appendices/Annexes As required, not
  otherwise included in body of ICD

53
ICD Format

• Joint Functional Area.
• Cite the applicable functional area(s), JFCs, the
  range of military operations, and the timeframe
  under consideration.
• Required Capability
• Describe the particular aspects of the JFCs that
  the ICD addresses
• Explain why the desired capabilities are
  essential to the joint force commander to achieve
  military objectives
• Reference any CRDs that may be applicable to this
  ICD
• Concept of Operations Summary
• Describe
• mission areas the capability contributes to
• operational outcomes it provides
• effects it must produce to achieve those outcomes
• how it compliments the integrated joint
  warfighting force
• enabling capabilities are required to achieve its
  desired operational outcomes.