===== JAS 3.10 =====

==== JAS R2.0SR3.10 VDD Extract ====

This document outlines the changes contained in JAS R2.0 SR3.10. The significant changes are summarized below:

=== System Architecture Enhancements. ===
 R2.0 SR3.10 now supports use of FIPS 140-2 validated version of OpenSSL (secure socket layer) in the application layer of the system for encrypted communications over TCP/IP.  This feature is transparent to the user.  In addition, it includes several enhancements to the JAS Administrative Control System (JACS) to support remote processing:
  * Simulation process termination from JACS

  * Support Multiple Simulation Versions within a network.

  * Support use of overlays for JACS itself

  * Deployment of administrative files via JACS

  * Load balancing function for multiple Environmental Servers

  * Support use of overlays for Environmental Server


=== Enhanced Functionality & User Interface ===

  * Air and Space – Addition of multi-resolution Close Air Support (CAS) planning and supporting changes to the Airspace Control Order. Enhanced user control of Preassigned Missions for Joint Targeting.  Support of explicitly flown cruise missiles for missions (e.g. OnCallStrike, LSEADStandoff, SWSurv & CDCMs, and CAS) other than Joint Targeting (previously the only supporting mission area).

  * Maritime – Enhancements to standardize the methodologies used in surface and undersea warfare attack execution and adjudication.
  
  * Weapons of Mass Destruction (WMD) – Initial representation of Electromagnetic Pulse (EMP) events and a low resolution of their effects on assets within range of the event.

  * BSEs, BSE Types, and Assets may now have Alias names assigned to them to aid in the integration of externally sourced data for scenario construction.


=== Error Corrections and Enhancements ===
R2.0 SR3.10 provides integration of the remaining error corrections and minor enhancements identified by user change requests and overlays. Appendix B lists those JAS Change Requests (JCRs) addressed in R2.0 SR3.10 that were reviewed and deemed appropriate for integration at this time.

=== Instruments and Output ===
R2.0 SR3.10 provides some new instruments and minor modifications to a few other instruments.  Appendix C lists those instrument changes in R2.0 SR3.10.

=== Human Control Interfaces (HCIs) ===
R2.0 SR3.10 has several new or modified HCI screens that either accommodate new functionality or provide enhanced usability. Most new functionality focus around JAS System Administration, Run Definitions, CAS Planning, Preassigned Mission Planning, Air Defense System, SCL Editor, JAOP Target Area Graphics, and the Video Playback tool. 

=== JAS Database and Data Model ===
R2.0 SR3.10 introduces changes to the data model necessary to support the new functionality. Scenario transformation and scenario import/export features provide support for transitioning existing scenarios to the new data model. New in this Service Release is the movement of the data dictionary from a separate table and imbedding the information into the data objects.  This means that users no longer need to manually update their input data tables in their JAR. The table structure is automatically updated upon selection of the export function.  See Section 9 for additional details.  Appendix C contains a list of database and data model changes implemented in R2.0 SR3.10.

=== Scenario Transformation ===
Every database change introduced in R2.0 SR3.10 has a corresponding software change in the Import/Export functions and scenario transform function designed to assist the user in upgrading prior scenario data to meet R2.0 SR3.10 requirements.  Of particular interest is the method for determining which sensors are “on” has changed and is handled by the transform function.  (See Section 3.3 for additional information.)  
  
=== Run Output Import/Export ===
Also new with this release is the ability to “Archive” run output data (collected Instruments) for a given run.  Run output stored in Oracle in BLOB format can be exported to a set of files stored in a user specified folder, and imported back into Oracle.  User may then export the output to a JAR for post-analysis.  Users may also use a compression application, like WinZip, to compress the exported files.  These exported files are in specific Oracle file types and should not be altered in any manner (e.g. no file name changes) or the re-import will not function properly.
