Future Plans

Future Plans

ROLANDS & ASSOCIATES Corporation 2

• Currently No Concrete Plan– Improvements To JTLS 4.0

• Several Minor ECPs – Require No New Data• Expected Around February or March

– JTLS 4.1 - ECPs - Require New Data• Plan: Before Next User Conference

– JTLS 5.0 - Major Restructuring Discuss By JCW• Work Starts Almost Immediately• Plan: Delivery In 2013

Plan Of Way Forward

October 2011


• Implications– R&A Has

• Two Separate Development Streams (JTLS 4.1, 5.0)• Two Maintenance Streams (JTLS 3.4, JTLS 4.0)

– This Will Take A Month Just To Alter Procedures– When To Integrate Changes

• Immediately – Interferes With Big Changes• Postpone – Will New Changes

– Work With New Structure– Will We Remember What Needs To Be Integrated

Plan Of Way Forward

October 2011

Post JTLS 4.0

October 2011ROLANDS & ASSOCIATES Corporation 4


• Add Random Process Visualization Tool– Existed In Old DDS

• Add GDP Capabilities To DDS– Map / Terrain Changes– Object Movement– Network Creation– Command Hierarchy– Logistics Hierarchy

DDS

October 2011


• Provide Remaining Battery Time On IMT– Currently Only Get Percentage Remaining

• Address Assumptions– Speed Greater Submerged– Battery Not Used When Surfaced or Snorkel

Diesel Electric Submarines

October 2011


• Add OPM Time Unit Of Measure• BDA Summary Data In Air Mission Reports• Improve Intelligence Reports

– JCW Provided Some New Requirements• Catapults Only Limit Takeoff

– Limit Landing – Also Represent Arresting Gear• More Than One Glassfish Per Machine

Odds and Ends

October 2011


• Air Force Agency For Modeling and Simulation–Conducting Test – Can JTLS Be Used For

• Tier 3 AOC Training – Prior To Test

• Fix Some Known Tanker Reporting Issues• Expand TBMCS Reporting Details

– Three Possible Outcomes• Yes, No• Maybe Due To Restrictions

– Probably We Would Be Tasked To Correct Restrictions

AFAMS Test

October 2011


• Start Working Toward Link– 1516 Evolved

Link To JCATS / VBS2

October 2011

JTLS 4.1



• Better Representation Of– Detection

• No Change – Assign Un-Identified Number– Classification

• Obtain Ship Basic Type (Symbol)– Recognition

• Obtain Ship Class– Identification

• Obtain Ship Name

Naval Detections

October 2011


• Existing– Sensor Detects Ship

• Initial Report Time – Get Unidentified Ship Detection• Fusion Time – Get Identification

• Basic New Concept– Not Every Sensor Can Accomplish Task

• Requires Imagery Of Some Type– Not A Matter Of Time – Matter Of Distance– Fusion Time Only Used If Previously Detected

Naval Detections

October 2011


• Purpose– Make Orders More Consistent– More Flexibility In HRU Makeup

• Entire HUP Capabilities Must Be Available• Need To Add Systems / Supplies To Meet Task

– Multi-Simultaneous Tasks• Ability To Detect And Accomplish Other Tasks

– Relook At Air Missions Rules At The Same Time

Re-Write Of HRU Code

October 2011


• Also Known As Tomahawk® Block IV• Additional Capability Required

– Reprogram the missile while in-flight • Required Two-way Satellite Communications• Can Only Strike15 Pre-Programmed Alternate Targets

– May Not Implement This Restriction• Alternate Strike Any Target Coordinates

– Using Global Positioning System (GPS)

Representation Of TLAM-E

October 2011


• Additional Capability Required (Con’t)– Can Loiter Over Target Area

• Current Capability In JTLS• What Is Not Current Capability

– Intel Collection While Doing So Using On Board Camera

Representation Of TLAM-E

October 2011


• Current Capability– If Ship Has JU Source Number

• Generates Message 2.3 – PPLI– We Do Not Support Link-16 Surface Tracks

• Working With PACOM To Design Task– Consider How This Works With PIFF Codes

• Passive Identification Friend or Foe

Self Report Link-16 Ships

October 2011


• Easy Way To Indicate When– Combat Action Starts– Combat Action Ends– What Is Happening In Combat

Combat Action Alert

October 2011


• More Explicit Representation Of– Hiding

• In Bunkers• In Tunnels

– Little Design Done So Far• Size Of Hiding Area• Where To Get In / Out• Possibility Of Being Trapped

– JCATS Uses “Portals”

Unit / Target Hiding

October 2011


• Continue Improvement To– ICC / TBMCS

• New Links– PACOM - GDSS2 (Air Mobility)– JCW

• HUMINT On-Line Tasking and Reporting– HOTR

• Advanced Field Artillery Tactical Data Systems– AFATDS

Link To Real World C4I

October 2011


• Add Higher Level Planning Capability– New WHIP Tools

• Air Tasking Order Generator• Ground Plan Development Tool

– Contingency Development– Rule Based Execution Start

• Spreadsheet Type Order Specification– Automated MSEL or MEL/MIL Order Entry

Improve User Workload

October 2011


• Service Oriented Architecture – Possible Models

• Maintenance Model• Weather Model• Contamination Model• Line of Sight Model• Emitter Model

Investigate SOA

October 2011


• Service Oriented Architecture – Investigate

• Method To Communicate (HLA / Other)– One Way Service– Request Service– Two Way Service

• Speed Implications• Time Coordination Issues

Investigate SOA

October 2011


Investigate SOA

October 2011

One Way Service - Example

JTLS EmitterTurn OnTurn Off


Investigate SOA

October 2011

Request Service - Example

JTLS Weather

What Is The Weather At

The Weather Is Cloudy


Investigate SOA

October 2011

Two Way Service - Example

JTLS Maintenance

Accept Damaged SystemAssets Such As Tow Truck

System Is Repaired

JTLS 5.0



• Obviously Large Job• Terrain Service

– How To Get The Data• No Problem For U. S. Government Users• Foreign Customers - Combatant Command Access

– Time Consuming and Not Flexible– Limited To Military Customers– Civilian Customers Have No Choice

– Allows Coordinate Terrain Data – JCATS / VBS2

Remove Hex Terrain

October 2011

Remove Hex Terrain

No Restrictions To Tiles

Remove Hex Terrain

Nested Tile Restriction


• Committed To Network Overlay– Types Of Networks

• Road• River – May Be Move To 4.1• Rail• Air Corridor• Naval Lanes

– Smooth Movement

Remove Hex Terrain

October 2011

Questions

October 2011 ROLANDS & ASSOCIATES Corporation 31

Documents

Future Plans