Notes
Slide Show
Outline
1
Joint Interoperability Challenges of Today…
The Operational Imperatives of Tomorrow…
A Capabilities Based Solution Approach
  • Mark N. Klett
  • Senior System Integrator
  • President & CEO
  • Klett Consulting Group, Inc
  • www.kcg-inc.net
  • 757.721.5040


2
Director DOT&E Tom Christie
  • If OT&E, as a total process, is to be effective, it must extend over the entire life cycle of a system, from initial requirements to extending its life by adaptation to new uses. It must use analytical studies, operations research, systems analysis, component testing, testing of other systems, and eventually testing of the system itself.
  • We need to do much more in cultivating and serving the users, the operational forces and even the CINCs themselves as prime customers for our products. They need to know the capabilities and limitations of the new systems they are deploying, based on our best estimates of what the testing to-date has demonstrated. Where else, may I ask, will they get that information in a timely and straightforward fashion?
3
JOINTNESS
  • To improve our effectiveness with less redundancy and more synchronization requires each capability to be optimized and integrated for the benefit of a Joint Force Mission.
  • True Joint military operations will only be realized when seamless integration of each service is accomplished: Institutionally, Organizationally, Intellectually, and Technically.
4
Joint Interoperability
  • Everyone agrees it is needed - everybody wants it – some ‘think’ they have it – few don’t want it… They all just want it yesterday, and wonder why it already hasn’t been fixed… or is it just another unfunded requirement?  This is not a new issue – so what is going on?
5
 
6
SITUATION
  • OUT OF ‘SYNC’ CYCLES
    • Requirements, POM, Technology, Acquisition
  • Acquisition Reform
    • Concept/Capabilities Based
    • Spiral Development
    • ACTDs
  • Revolution in Business and Military Affairs
  • Transformation Imperative
7
How Did We Get Here
  • Through the valiant efforts of great Americans:
    •  Developing combat systems and associated support capabilities,
    •  Designed, built, and rigorously tested to MILSTD  specifications and requirements,
    •  By a lot of smart people from corporations and organizations determined to be the best value bidder.
  • Systems were built and procured mostly by individual Military services to meet their specific military missions in a non-synchronized manner even within  own service.
8
SECDEF Directive on Interoperability & Connectivity
  • JFCOM and Joint Staff co-lead


  • Options that must be explored:
    • Creation of an agency which would address, fund and implement aspects of BMC2 interoperability and connectivity
    • Allocation of monies directly to all Combatant Commanders to buy “joint” BMC2 systems


    • Authority and allocation of money directly to JFCOM to buy “joint” BMC2 systems to support combatant commanders


  • Directive tasking, 25 Day which equals 16 Nov 2002



9
PROCESS FINDINGS SUMMARY
(1999)
  • Joint interoperability requirements lack definition
  • Joint Mission Areas (JMA) not defined, no JMA Operational Architectures
  • No periodic Joint Mission Area Assessments Conducted
  • Joint Interoperability issues not prioritized
  • No dedicated funding for joint requirements development and assessment
  • Program reviews lack clearly defined interoperability exit criteria
  • Interoperability tests lack outcome-based standards
  • Current certification policy lacks enforcement
  • Ineffective Joint coordination of technical and system migrations
  • Unclear what office(s) is/are in charge of interoperability


10
 
11
 
12
 
13
CORE RECOMMENDATION
14
Explore Ideas – Invest in What can be  Executed
  • Develop an Executable Process
    • DOT + T = I  (Co-evolution of Doctrine, Organization, Technology + Training = Interoperability)
    • DOTTI Process
      • Meaningful & Relevant MOEs, MOPs, Metrics
        • 3 Network Centric Domains – Information, Physical, Cognitive
      • Training
      • Iterative Process - Constant Improvement
  • Value of JDEP Process to provide T&E Capability for Developers, Testers & Warfighters
    • Root Cause discriminator with CBA for Synchronized Development and Implementation of ‘Fixes’
  • ACTDs can be Valuable – when ‘Certified’
    • Optical Correlator
15
SUMMARY
  •  Interoperability is an Operational Imperative. Network Centric Operations is How we will fight and win in this Century.
  •  Transformation is about Change. Put An Organization in Charge
    of Interoperability - 
    Resource them… and It
    will get Fixed.
  •          JUST Do IT !!