JTLS Global Operations JTLSGO Continuing Forward Ellen Roland

JTLS – Global Operations JTLS-GO Continuing Forward Ellen Roland JTLS Development Team Leader

Current Status • Promising It For Two Years – First Release Is Now Available • Major Rewrite – Remove Hexagon Terrain Representation • Variable Size Gridded Terrain – Add Execution Plans For All Objects – Expand Service Oriented Architecture November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 2

JTLS 5. 0 Basics • Major Improvement To JTLS – Terrain • Old: – Game Board Maximum 2000 NM by 2000 NM – Hexagons Over Lambert Conformal Projection – Rivers, Shorelines, National Boundaries Hex Edges • New – World Wide Terrain, Thus The New JTLS-GO – River, Road, Rail, Air Corridors, and Sealane Networks – Shoreline, Barriers, and National Boundary Polylines November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 3

JTLS 4. 1 Terrain November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 4

JTLS 4. 1 Terrain November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 5

JTLS 5. 0 Terrain November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 6

JTLS 5. 0 Terrain November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 7

JTLS 5. 0 Terrain November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 8

JTLS 5. 0 Terrain November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 9

JTLS 5. 0 Terrain November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 10

JTLS 5. 0 Networks • Air Corridors – Worldwide – Mission Type Defines Default Usage • Example – Use Network: Mobility Missions, Transfer Missions – Direct Path: Attack Missions – Concept Fly Real-World Air Routes • If Air Mission Deviates – Important Exercise Event – User Can Override Default Choice November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 11

JTLS 5. 0 Air Corridors November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 12

JTLS 5. 0 Networks • Sea Corridors – Worldwide – Sealanes Default For All Movement – User Can Override And Select Direct Path – Desire Different That Air Corridors • Would Look Unrealistic If Ships Lines Up On • Lanes Have Widths – Ship Selects Random Offset and Stays Close To Lane November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 13

JTLS 5. 0 Sea Lanes November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 14

JTLS 5. 0 Sea Lanes November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 15

JTLS 5. 0 Networks • Other Movement Networks – Road – Shortest Time Algorithm • Segments Have Speed Limit • Objects Have Maximum Speed – Rail – Shortest Distance Algorithm • All Rail Has Constant Speed – Rivers – Shortest Distance Algorithm • Each Type Of Small Boat Has Its Own Speed • River Current Not Considered. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 16

JTLS 5. 0 Networks November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 17

JTLS 5. 0 Terrain • Every Aspect Of The Model Changed – Method To Move Objects • No Longer Hex-by-Hex • One Grid May Be – 600 NM Across – 250 Meters Across – Area Effects Data • Cannot Be Considered To Cover Entire Grid (Hex) November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 18

JTLS 5. 0 Terrain Contaminate Example With Hexes November 2016 Copyright 2016, ROLANDS &

JTLS 5. 0 Terrain Contaminate Example With Grids November 2016 Copyright 2016, ROLANDS &

JTLS 5. 0 Terrain Constant Sunrise / Sunset Time Determination - Location - Date/Time

JTLS 5. 0 Execution Plans • In JTLS 4. 1 – There Were Some Execution Plans • High Resolution Units • Naval Ships • Naval Formations • In JTLS 5. 0 – All Objects Now Have Execution Plans • Air Missions, Supply Convoys, and Ground Units November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 23

JTLS 5. 0 Execution Plans • Helps In Innumerable Ways – Object Plans Viewable On IMT – Easier To Edit The Future For The Object – Ability To Submit Plans In Advance • No Need To Monitor Closely. – For Example: Tanker Mission Orbit At: » Exxon High From 0930 to 1015 » Shell Low From 1050 to 1130 – Once Plan Is In – No Monitoring Needed • Reduces Number Of Interface Controllers November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 24

JTLS 5. 0 Execution Plans November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 25

U. S. JS/J 7 Services • U. S. Joint Staff / J 7 Project – Service Oriented Architecture (SOA) – Names • JLVC 2020 • Joint Training Environment (JTE) – JTLS Already Uses SOA • Investigated Functional Services For This Project November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 26

JTLS 5. 0 Services • Air Tasking Order (ATO) – Translator – Translate Exercise ATO • Air Tasking Order – Generator – Take High Level Commander Guidance – Suggest and Create Orders For • Missions That Should Be Flown • Targets That Should Be Hit November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 27

JTLS 5. 0 Services • Satellite Service – Computes Orbital Mechanics For Satellites – Uses Two-Line Entry (TLE) Data – Needed Because Global Representation • C 4 I Interface Service – Always A JTLS Capability Executing On Server – Takes Perception • Feed Link-16 and OTH-Gold – Web-Enabled Filtering November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 28

WHIP ATO-Translator Service TBMCS ICC NEC-CCIS ATO/ ACO ATO-Parser XML Mission File Spreadsheet Component WHIP November 2016 ATO-T Synapse Apache ATOT Component Parsed XML File XML Linking File Web Access Copyright 2016, ROLANDS & ASSOCIATES Corporation 29

Satellite Service November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 30

JTLS-GO Future

Do Not Plan For Ventures Before Finishing What's At Hand Euripides

Current JTLS-GO Status • JTLS 5. 0 Is Delivered – It Has Not Passed Acceptance Testing • JS/J 7 – No Specific Date • NATO – Week Of 11 December – Few Cleanup Task Remains • Representation Of Strategic Movement • Use Of Material Handling Equipment (MHE) • Off-Road Route Optimization November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 33

Find Everything That Is Wrong and Fix It Elon Musk November 2016 Copyright 2016,

Remainder 2016 • Continued Testing and User Training Support – Now To 31 December 2016 – Waiting For The First Organization To Use JTLS-GO • This Was A Huge Change – Increased Flexibility – Increased Number Of Feasible Options To Test November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 35

Seek Negative Feedback Especially From Friends Elon Musk

Training Completed • We Have Trained / Tested With Several Agencies – – – Greece, Poland, Saudi Arabia NATO Centre Of Excellence For M&S NATO Consultancy Information Agency NATO Joint Warfare Centre US Joint Staff / J 7 • We Have Received An Abundance Of Feedback – Make Sure We Did Not Lose Any Capability – Small Improvements To Make New Capabilities Better November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 37

Noted Issues • Better GIS Data Format Documentation • AAR Collected Data On Tasks – Reason Codes For Cancellation – Develop AAR Useful Reports • Get Message Traffic Under Control – Who Should Get Messages • Reporting Player For Object • Player That Submitted Task Order November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 38

Noted Issues • Patrol Area Problems – Caused By • National Boundaries, Barriers, Land Grids – When Problem Encounters • Simply Pick New Point In Polygon – ATO-Translation Change Messages • Linking Bridge Data To Road / Rail Networks November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 39

We Have a Strategic Plan. It’s Called Doing Things Herb Kelleher, Southwest Airlines

JTLS 2017 • JTLS Is Not A Legacy Or Static Model – JTLS Is In The US POM Until 2021 – Still No Replacement On The Horizon • After Such A Huge Change – Need Time To Settle Down – Users Need To Learn About Changes – Concentrating On Usability Not Functional Changes November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 41

JTLS 2017 • Current Plans – Improve / Reduce Database Development Time – Combine Access To Smaller Sides In One WHIP • Jose Torres Will Discuss This Later Today – Build MEL/MIL Tool Integrated With JTLS • Greg Sullivan Will Discuss This Later Today November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 42

Data Repository • Data Repository – Engineering Level Data – Order Of Battle Data • Copy And Paste Between Databases • Tools To – Reduce Size Of Scenario Data – Automatically Calculate Supply Requirements November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 43

Improve / Reduce Database Development Time • Remove Combat System Prototype Concept • This Old Method Resulted In – Limited Number Combat Systems / Supply Categories • Too Much Memory – “Sharing” Combat Systems • Tank Limited Fire Control / Limited Survivability • Generic Name TANK 100 -LFLS – North Korean System - T 55_TYPE 69 -2 – United States System - M 48 A 3 November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 44

Old Combat Systems Array Name Avail Manned Maint Unavail KIA WIA Current Kill Time Weighed Shelter Next Repair Aircraft 0 0 0 0 0 APC 5 5 0 0 0 0 Amphib 0 0 0 0 0 Arty-SP 0 0 0 0 0 Arty-Tow 0 0 0 0 0 Anti. Tank HAW 0 0 0 0 0 Crew 5 5 0 0 0 0 Infantry 25 25 0 0 0 0 Truck 0 0 0 0 0 Equip 3 3 0 0 0 0 IFV 0 0 0 0 0 November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 45

New Combat Systems List Name Avail Manned Maint Unavail KIA WIA Current Kill Time Weighed Shelter Next Repair APC 5 5 0 0 0 0 Crew 5 5 0 0 0 0 Infantry 25 25 0 0 0 0 November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 46

Improve / Reduce Database Development Time • Once We Remove “Sharing” Structure Concept – Easier To Define • Units And Their TOE Using Repository Data – No Longer Tied To JTLS • 99 Combat System Definition / 317 Supply Category Definition • Use What You Need And Want • Build What Is Not Available November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 47

Example Generic Names November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 48

Improve / Reduce Database Development Time • JTLS Delivered With Data Repository – Called sdbkor 50 (Standard Database) – Copy And Paste Only Engineering Data Needed • Each Organization Builds – Their Order Of Battle Repository – Can Build Their Own Engineering Data If Necessary • Tools To Automatically – Retrieve Needed Engineering Data – Remove Unused Data November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation 49