THE MANY ASPECTS OF C4I INTEROPERABILITY

1. THE MANY ASPECTS OF C4I INTEROPERABILITY PROCEDURAL, DOCTRINAL (Process) AND TRAINING INTEROPERABILITY • AIR CONTROL PROCEDURES (NAVY VS AIRFORCE) • JTIDS CONOPS, ETC. • JOINT TACTICS AND TRAINING • JOINT C2W (MOP 6, 30) • JOINT SURVEILLANCE • ETC. COMMUNICATION INTEROPERABILITY • DATA • BOM Links (11,4A,16 ,etc) • Character Links (TADIX A, OTCIXS) • VOICE • RF Waveform/Compression • IMAGERY • RF Waveform/Compression • APPLICATION FILE TRANSFERS • ATO • User Pull (MIDS IDB, etc) • SECURITY • Crypto (Procedural) • Over the Air Rekeying • Sanitizers • MLS C2 SYSTEM INTEROPERABILITY (Software, Hardware and Data base Compatibility) • LANGUAGES • TERMINOLOGY • DISPLAY SYMBOLOGY • DATA DICTIONARY • DATA BASES • NWTDB • MIDS/IDBH • MAPS • CHARTS • DECISION AIDS • CORRELATION AND FUSION • OTH-T BGDBM • CS TRACK MANAGEMENT • ETC.

2. Interoperability-Communications Data Standards- Deficiency: Conflicting Message Standards / Data Elements/Relationships contributes to Combat ID Problems (e.g. Conflicts) SOLUTION CAN REDUCE FRATRICIDE Reconcile Differences with Intel Data Bases Recommendation: • Identify differences between OTH-GOLD, TADIL A,J and TADIL K (VMF) Data Elements • Investigate differences with Intel. Data Bases • Provide a Normalized Core Data Model • Provide XML/XMI standard and Standard translators for both bit oriented and character oriented standards. Step 2 Step 3 Step 1 Existing Standards Bit Oriented Message Formats: M - Series (LK-11) V/R Series (LK-4A) IJMS (LK-16 INTERIM JTIDS MESSAGE STD.) J Series (LK-16)* K Series (VMF) F Series (LK-22)* TIBS (J Variant Special Message)* TADIX B Character Oriented Format: OTH-GOLD (OTCIXS) Sensor Reps (USMTF) Establish Common Data Elements, Meanings and Ontological Relationships (Data Model) Establish Common Data Elements and Standard Translations Step 4 Establish Common Data, ontology bases, Translations To Legacy Systems

3. COHERENT TACTICAL PICTURE SYNCHRONOUS EXECUTION COLABORATIVE PLANNING C2W HIGH CAPACITY COMMUNICATIONS ESSENTIAL TO ALL AREAS MANY KIND OF ARCHITECTURES(Do Not Proceed to develop without Specific definition and scope) C2 ARCHITECTURES • CORRELATION/FUSION ARCHITECTURE • BATTLE FORCE ORGANIC SENSORS • DIRECTLY COOPERATING OTHER SERVICE SENSORS • CJTF/CINC SENSOR ASSETS • NATIONAL ASSETS • CONTROL ARCHITECTURE (FORCE(S), WEAPONS, COOPERATIVE ENGAGEMENT, SENSORS, COMMS, LOGISTICS, ETC.) • PLANNING ARCHITECTURE • MISSION • STRIKE • FORCE DEFENSE • C2W • COMMUNICATIONS • SURVEILLANCE • LOGISTICS • SYSTEM FUNCTIONAL INTERACTION ARCHITECTURE • COMPUTER ARCHITECTURE • LAN ARCHITECTURE • LAN/POINT-TO-POINT HYBRID ARCHITECTURE • SOFTWARE CORE SERVICES ARCHITECTURE (E.G. TAFM) • SOFTWARE (APPLICATION) INTER-SYSTEM INTERACTION ARCHITECTURE C2 REQUIREMENTS DRIVE COMM REQUIREMENTS WAR FIGHTING CAPABILITES DRIVE C2 REQUIREMENTS SPACE SURVEILLANCE ARCHITECTURE COMMUNICATIONS ARCHITECTURES • CONNECTIVITY ARCHITECTURE • INFORMATION FLOW ARCHITECTURE • CONTROL ARCHITECTURE • DYNAMIC ROUTING • DYNAMIC LOAD LEVELING • BEARER SERVICES ARCHITECTURE • NETWORK/CIRCUIT ARCHITECTURE • HARDWARE/SOFTWARE BUILDING BLOCK ARCHITECTURE SPACE BASED COMM ARCHITECTURE OCEAN SURVEILLANCE ARCHITECTURE ETC., ETC., ETC., ETC.

4. CHANGING WARFARE REQUIREMENTS YESTERDAY WEAPONS ON TARGET TODAY THE RIGHT WEAPON ON THE RIGHT TARGET AT THE RIGHT TIME -PRECISION MUNITIONS -PRECISION TARGETING -PRECISION PLANNING -SYNCHRONOUS EXECUTION

5. THE NEVER ENDING GOAL “COOPERATIVE WARFARE” THE NEVER ENDING QUESTION “HOW DO WE DO IT BETTER?” THE NEVER ENDING INHIBITOR “COOPERATIVE MANAGEMENT” MAJOR CONCLUSION AT TIG 92-C4I IS MORE OF A MANAGEMENT PROBLEM THAN A TECHNOLOGY PROBLEM

6. IDEAL COMMUNICATION SYSTEMSUPPORTING TACTICAL C2 Provide Transparent Worldwide Information Transfer