E N D
1. 1
2. 2 On The Road To Jointness? Partnership - We believe that providing capabilities is best done by partnering with services, agencies, program offices, and the people at the grass roots level. While it may just be a game of semanticsPartnership - We believe that providing capabilities is best done by partnering with services, agencies, program offices, and the people at the grass roots level. While it may just be a game of semantics
3. 3 Who We Are JI&I (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. 4 Who We Are Partnership - We believe that providing capabilities is best done by partnering with services, agencies, program offices, and the people at the grass roots level. While it may just be a game of semanticsPartnership - We believe that providing capabilities is best done by partnering with services, agencies, program offices, and the people at the grass roots level. While it may just be a game of semantics
5. 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. 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. 7 Points of Order We’re 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 you’ve “made your case”
9. 9 Future Requirements =Future Threat + Future Capabilities
10. 10 Introduction 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. 11 Introduction 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 doesn’t matter how many time JCS changes the requirements systems or OSD overhauls the acquisition system, the analytical method to produce these documents hasn’t changed
They don’t 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.”
13. 13 Master Process
14. 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. 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.
16. 16 Symbiosis
17. 17 Mission Assessment Process
18. 18 Interoperability
19. 19 Why Function?
20. 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. 21 What is Function? 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. 22 Functions: Health Care Example
23. 23 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. Support & Operational
24. 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. 25 Common Military Functions
26. 26 Functional Decomposition
27. 27 Functional Decomposition
28. 28 Functional Decomposition
29. 29
30. 30 Staging
31. 31