JTLS 5.0 JTLS – Global Operations March 2008 JTLS 5.0 JTLS – Global Operations Scenario Data Repository John Ruck ROLANDS & ASSOCIATES Corporation

Copyright 2016, ROLANDS & ASSOCIATES Corporation Agenda Background and Motivation. End Goal. Phased Approach. Phase One Details. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Background and Motivation The Standard Database delivered with JTLS has become a defacto data repository. Leads to scenario databases with significant amounts of unneeded data. Limited set of systems represented. Hard to combine the order of battle of multiple scenarios. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Copyright 2016, ROLANDS & ASSOCIATES Corporation End Goal Provide a tool that allows copying order of battle and engineering data from one scenario to another. Compress a database by removing unneeded data. Ability to synchronize a database with an updated repository. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Copyright 2016, ROLANDS & ASSOCIATES Corporation Phased Approach Phase 1 (by end of 2016) Ability to copy order of battle with limitations. Some tables will be required to hold the same data in both scenarios. (More details later.) Phase 2 (JTLS 5.1) Remove the restriction above. Depends on removal of CS_CSP and SLP_SC. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Phased Approach (cont.) Copy engineering data Phase 4 Add the ability to compress the database. For example, delete all unused TUP, SUP, HUPs (with user confirmation.) November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Phase 1 Limitations (cont.) Add the ability to synchronize a database to an updated repository. For example, move over updated prototype data. Note, partial implementation of phases 3, 4, & 5 may be able to be accomplished prior to 5.1. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Copyright 2016, ROLANDS & ASSOCIATES Corporation Phase 1 Details Design is in progress. Details may change. Add the capability to the Database Development System (DDS) to copy order of battle from one database to the other. User will open 2 databases in the DDS. Each will have a command hierarchy window. Desired units dragged and dropped between. Multiple units can be copied at a time. Required related table data copied automatically. This includes prototype data. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Copyright 2016, ROLANDS & ASSOCIATES Corporation Phase 1 Limitations The following data must be identical between the 2 databases. Combat Systems, Supply Categories, Altitude Zones, Depth Zones, Targetable Weapons, Aircraft Classes, Lethality Data. Force Sides and Factions must be defined. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Phase 1 Limitations (cont.) Missing supply support units will be blanked out. That is, if a unit’s initial or regular support unit is not being copied and doesn’t exist in the new scenario, then it will be set to none. Missing higher head quarters will be blanked out. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Phase 1 Limitations (cont.) Still deciding whether to automatically copy Airbases when a Squadron is copied. (leaning to no.) When copying, if an object of the same name exists in the target database, it is assumed to be the same object and will not be copied. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Copyright 2016, ROLANDS & ASSOCIATES Corporation Conclusions First phase is to get an initial capability by the end of the year. Remaining phases will add capability and reduce restrictions as scheduling permits. November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation

Copyright 2016, ROLANDS & ASSOCIATES Corporation Questions November 2016 Copyright 2016, ROLANDS & ASSOCIATES Corporation