Joint SIAP System Engineering Organization Precision Strike Technology Symposium October 2004

1. Joint SIAP System Engineering Organization Precision Strike Technology Symposium October 2004 Brig Gen (S) Rick Dinkins, USAF Director, JSSEO Col Harry Dutchyshyn, USAF Deputy Director, JSSEO CAPT Jeffery W. Wilson, USN Technical Director LTC (P) David Cook, USA Director, Staff, Plans, Resources

2. Today’s Purpose Describe the problem—the “Deadly Sins” Understand what “good” looks like— requirements & attributes Introduce Behavior Model approach— digitized spec & programming tool • Its about making architecture real • Its about sensor to shooter • Its about fielding Joint & coalition warfighting capability at a pace and level we can afford

3. Air Ground Maritime What problem must we solve? • Operational Problem: • Engagements constrained by • Procedural controls • Target ID • Sensor limitations • Lack of interoperability among • Weapon Systems • Sensors • C4I • Operational Elements: • Single Integrated Air Picture • Combat Identification • Integrated Fire Control • Automated Battle Management Aids • Attack Operations • Passive Defense / Early Warning Joint Engagement Zone

4. The Objective… Joint Combat Capability • Exploit our weapons to their full kinematic range • Reduce the risk of fratricide • Counter emerging threats Single Integrated Air Picture…Getting everyone on the same sheet of music

5. 3055N 3045N 8025W 8010W 7955W 7940W 3055N 3045N 8025W 8010W 7955W 7940W SIAP system engineering . . . Getting everyone on the same sheet of music System A’s View Of The World 303 Data Not Correct 306 01227 02547 2 observed; Only 1 real aircraft Data Not Available Not observed System B’s View Of The World 306 1227 Data Not Processed Consistently Across Network 2547 Looks like a friendly, but it’s not 303

6. Today’s air picture problem A B C D 14 minutes of Link 16 track history taken in May 2000 Ave. track lifetime is 2 minutes. A B C D Constant turnover of target designation limits warfighter ability to make decisions. 30 Track Changes on Target B Occurred on Link-16.

7. What are the “Deadly Sins”? • What time is it? Lack of a common time standard across the force • Where am I? INS/GPS integration factors impact Position Quality & navigation functions with the TADIL J network • How well…? Poor tracking performance & inaccurate Track Quality (TQ) calculations, resulting in improper assumption/retention of Reporting Responsibility (R2) • Can you hear me? BLOS relay requirements & throughput limits can create connectivity shortfalls • Where are WE? Failure to achieve common geodetic coordinate frame translation issues

8. What are the “Deadly Sins”? • Can we agree? Correlation/de-correlation algorithm differences • Who is it? Automated identification processing differences • IFF/SIF association • Multi-Source Integration • Can I understand you? Message standard implementation differences • “Minimum Implementation” • Taxonomy support for identification • Options & interpretation differences • CM & compliance Issues • Service & Joint certification issues • Multi-TADIL translation issues DIFFERENCES in Host implementation and operational procedures reduced overall network performance

9. SIAP Attributes • Completeness: The air picture is complete when all objects are detected, tracked and reported • Clarity: The air picture is clear when it does not include ambiguous or spurious tracks • Continuity: The air picture is continuous when the tracks are long lived and stable • Kinematic Accuracy: The air picture is kinematically accurate when the position and velocity of a track agrees with the positionand velocityof the associated object • ID Completeness: The ID is complete when all tracked objects are labeled in a state other than unknown • ID Accuracy: The ID is accurate when all traced objects are labeled correctly • ID Clarity: The ID is ambiguous when a tracked object has two or more conflicting ID states • Commonality: The air picture is common when the tracks held by each participant have the same track number, position and ID JROC Approved Requirements

10. How Do We Express Our Needs? Static Specifications • English on paper… • Complete? • Correct? • Clear? • Different interpretations by each prime contractor in each product line

11. Legacy approach results in known deficiencies Same functionality developed differently

12. IABM- A stepping stone to Service implementation Displays Joint Tactical BMC2 Weapons Sensors System – specific Tactical BMC2 Displays Joint Tactical BMC2 Weapons Sensors System – specific Tactical BMC2 Displays Joint Tactical BMC2 Weapons Sensors System – specific Tactical BMC2 TDL Requirements Requirements . . . . . . 101010101010101010101010 101010101010101010101010 System A 010101010101010101010101 010101010101010101010101 + + 101010101010101010101010 101010101010101010101010 010101010101010101010101 010101010101010101010101 for (i=0;9; i++) for (i=0;9; i++) 101010101010101010101010 101010101010101010101010 * * * * {a {a =sin(i =sin(i PI);} PI);} 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 Standards Standards 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 . . . . . . Requirements Requirements . . . . . . 101010101010101010101010 101010101010101010101010 010101010101010101010101 010101010101010101010101 + + 101010101010101010101010 101010101010101010101010 System B 010101010101010101010101 010101010101010101010101 for (i=0;9; i++) for (i=0;9; i++) 101010101010101010101010 101010101010101010101010 * * * * {a {a =sin(i =sin(i PI);} PI);} 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 Standards Standards 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 . . . . TDL . . Requirements Requirements . . . . . . 101010101010101010101010 101010101010101010101010 010101010101010101010101 010101010101010101010101 + + 101010101010101010101010 101010101010101010101010 010101010101010101010101 010101010101010101010101 for (i=0;9; i++) for (i=0;9; i++) System C 101010101010101010101010 101010101010101010101010 * * * * {a {a =sin(i =sin(i PI);} PI);} 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 Standards Standards 010101010101010101010101 010101010101010101010101 101010101010101010101010 101010101010101010101010 . . . . . . Function Requirements Requirements Track Mgmt Distributed Resource Mgmt IABM JSSEO + + Data Dissemination Mgmt Joint C2 Standards Standards Service Common Services System Interfaces

13. JSSEO & Services making architectures real It’s about the data • Making it correct • Making it available • Processing it consistently “Net-Ready” Requirement Behavior Model is the strategy • Interoperability • Life-cycle cost avoidance • Reduced time to field new and modified capability Requires the right talent & skills sets and leadership commitment to realize goals

14. Summary What the warfighter gets: • Confidence in tracking targets & friends • Flexibility to engage on our terms • Robustness for reacting to change To achieve what effects: • Exploit our weapons at their full kinematic range • Reduce the risk of fratricide • Counter emerging threats Joint & Coalition Warfighting…the product of partnerships between governments & industry

15. Back-up

16. Warfighting benefit Object Appears Establish Track ID Track Assess Threat Assign Weapon Engage Track Assess Detect Current Timeline SIAP Timeline Counter Emerging Threat Extend Battlespace Reduce Fratricide Shared measurements yield improved and early engagement, quicker assessment, earlier follow-on action Shared “picture” & automated battle mgt aids allow distributed and earlier decision Shared measurements improve weapon performance Collective & shared surveillance yields earlier detection Shared “picture” allows earlier allocation of ID resources & earlier ID resolution Shared measurements improve decision-making Shared measurements establish track earlier

17. Reduced Overall Cost • Original Service estimates accounted for redundant development • A change in business model should reduce total cost and help synchronize development Pgm Mgt Design Int Code Test System A a b c d e f a b c d e f System B Common Total $ = System A + System B Block 0 & Block 1 Total $ = a + b + c + Ad + Bd + Ae + Be + Af + Bf New Method Int Test System A Pgm Mgt Design Code d e f a b c System B d e f Demands change in business model

18. Correlation assessment example Warfighter Picture Today New Link 16 Algorithm Ideal Tracks/obj = 2.6ID Accuracy = 62%TN Commonality=41% Tracks/obj = 1.0ID Accuracy = 100%TN Commonality =100% Tracks/obj = 1.2ID Accuracy = 100%TN Commonality=91% - - We are making progress - - Developing tools to support decision making

19. B0: Reduce Dual Tracks / Operator Confusion • Link 16 Fixes • Common ID Taxonomy • Joint ID Conflict Resolution • Common Correlation • Formation tracking (pending) ICPs Block 0 Systems Patriot AMDPCS FAAD C2 AEGIS E-2C F/A-18 ACDS (CV/LHA…) TAOC AWACS Rivet Joint MCE F-15 Service Execution SIAP System Engineering Road Map 00 01 02 03 04 05 06 Overarching Mission (Capstone) Requirements • Engage at full kinematic range of our weapons • Reduce fratricide • Counter emerging asymmetric threats B1: Improve Accuracy and Commonality Improve Combat ID Capability B2: Improve efficiency / throughput Improve gateways and beyond LOS { • Host implementation consistency • Dist. database consistency imp. • Network latency reduction • Interface w/ ground systems • Imp. missile defense performance • Further Reduce Dual Tracks • Improve Combat ID Capabilities • Improve TBMD performance • Improve data sharing • US Funding Copntraints • Reduce to 10 C2 systems • Reduce common non- recurring engr • Integrate 270K SLOC IABM Block 1 Candidates PatriotA2C2SMIDS TAISATCCSJTIDS SICP ApacheSentinelCDLMS HIMARSFBCB2TAOC JLENSAvengerCAC2S SLAMRAAMTacticalUAVCLAWS AFATDSLinebackerMSCS MEADSACSAWACS ComancheATACMSF-15 AMDPCSAEGISF-16 MLRSSSDS MK2Rivet Joint EAADE-2CAOC JTAGSF/A-18MCE FAADC2 CEC ABL THAADSBIRS SMDS Systems for Block 1 • Patriot • AMDPCS • FAAD C2 • CG/DDG • CV • E-2C • CAC2S • AWACS • Rivet Joint • BCS(F) Acquisition Strategy

20. Model Driven Architecture • Industry standard approach (Object Management Group) • Separates functionality and implementation; focuses attention on functionality • Provides design stability as implementation technologies evolve and improve (platform* independent) *Note: Platform refers to specific equipment, operating systems, and programming languages, not combat systems as used in the traditional sense Design for change

21. Requirements + Standards For (i=0;9; i++) {a=sin(i  PI);} . . . 101010101010101010101010 010101010101010101010101 101010101010101010101010 010101010101010101010101 101010101010101010101010 010101010101010101010101 101010101010101010101010 010101010101010101010101 101010101010101010101010 010101010101010101010101 101010101010101010101010 . . . The Integrated Arch Behavior Model • Unambiguously describes dynamic system behavior • Supports selection among alternative material and non-material solutions • Delivered with reference implementation and verification / validation data Gives industry & JITC a model of the distributed system to show what “good” looks like--automate the standards

22. Construct the system from large, reusable components Build precise, predictive models Establish a well-defined and automated construction process SPECIFY SYSTEM CONSTRUCTION PROCESS Define/Buy PIM To PSM Mapping Rules Build/Buy PIM compiler Partition Software Beta Test Sites Develop Model Compiler BUILD PLATFORM INDEPENDENT MODELS (PIMS) Model domain use cases Build Static Model - Class Diagram Build Behavioural Model - State Charts & Interactions Build Action Model - Operations & State Actions Compile and debug PIMS Integrated Architecture Behaviour Model (IABM) Subject the models to rigorous testing before implementation GENERATE SYSTEM Apply PIM to PSI Mapping Rules (Execute PIM Compiler) Perform target testing Host System Integration VALIDATE PIMS Execute domain use cases Execute system use cases JITC is independent V&V Agent To build this Overview of the Model Driven Architecture Process SPECIFY DOMAINS Identify new/reused domains Model system use cases Track Mgt, TDL Processing, Sensor I/F, Host Data Exchange, Peer to Peer Comm The MDA process can be summarized as:

23. TRUTH Completeness • The air picture is complete when all objects are detected, tracked and reported. Complete Incomplete

24. TRUTH Clarity • The measure of the portion of the SIAP that contains ambiguous tracks and/or spurious tracks. The air picture is clear when it does not include ambiguous or spurious tracks. Unclear Clarity

25. Continuity • The air picture is continuous when the track number assigned to an object does not change. 4567 4567 4567 4567 1234 7654 4321 1234 1234 1234 TRUTH Continuous Not Continuous

26. TRUTH Kinematic Accuracy • The air picture is kinematically accurate when the position and velocity of each assigned track agree with the position and velocity of the associated object. Kinematic Accuracy Inaccurate

27. TRUTH ID Completeness • The measure of the portion of tracked objects that are in an identified state. The ID is complete when all tracked objects are in an identified state. Incomplete ID Completeness

28. TRUTH ID Correctness • The measure of the portion of tracked objects that are in the correct ID state. The ID is correct when all tracked objects are in the correct ID state. Incorrect ID Correctness

29. TRUTH ID Clarity • The measure of the portion of tracked objects that are unambiguously identified. The ID is clear if no tracked object is in the ambiguous ID state. Unclear ID Clarity

30. 4567 4567 4567 1234 1234 1234 System Y System X System Z Commonality • The air picture is common when the assigned tracks held by each participant have the same track number, position, and ID. 4567 3456 5656 System A 4545 2345 3434 1234 System B 1212 TRUTH System C Commonality Lack of Commonality

31. 4567 4567 4567 4567 4567 1234 1234 1234 1234 System W System X System Y System Z 1234 TRUTH IABM integrated and fielded Completeness Clarity Continuity Accuracy Timeliness Correctness ID Probability Prob of Correct ID Everyone has a “picture” … and they’re all the same