== System Operator Console - Specification (DRAFT) ==
The System Operator Console is a software interface to all the major components of the TMC Simulation.  It allows the system operator to manage the operation of a simulation session.  Key features are:

 * specify session configuration options such as selecting the list of current students
 * launch a simulation session
 * reset log files
 * perform post-session tasks such as creating the unified log output

----
== Proposed Feature List ==
Play audio test clip for volume check

Delete (or reset) any existing log files:  CADcomments, Activity Log, CADdetails, unified log, evaluation log, cms and har messages, LCS database.   Might be nice to specify log files with test data for development runs.

Create or select list of students (for CAD Clients, Activity Log, etc)

Start the webserver  (locally if Development Workstation)

Select a traffic model (traffic events file)

Start the CAD server with desired traffic model

Select a simulation Scenario (XML file)

Launch the Simulation Manager with desired Scenario (Note: operator must press the "Start" button on the GUI to begin the simulation).

Launch the Lane Control System, if necessary, or show status.

Start Unified Logger Service (maybe this should be a daemon?)[[BR]][[BR]]Launch a browser with our webapps:

 * Instructor notebook
 * CPTMS
 * unified log monitor

Launch a browser on separate monitor to show CMS/Har messages

Launch the simulation clock display

Optionally, start a CAD client (VisiCAD)

Perform post-session tasks:

 * Run the log merge procedure
 * Display the unified log output in a browser.
 * Optionally, print the unified log output.

Archive log files (at end of session)

Terminate all running applications.

----
== Optional Features ==
Be able to save the settings that have been selected for a certain run and provide a description.  Then be able to load the console from saved settings, such as "Practice scenario: hay truck incident".  I think this configuration consists of three items:

 * Scenario script and resources
 * Traffic model corresponding to the script
 * LCS data corresponding to the script

but conceivably might include other items, such as CMS messages already active.