SARTrack Operator info

People who have SARTrack capability on their computers and are reasonably confident in its use may log in to the Auckland AREC SARTrack group 6400 to take part in the exercise. We will use the SARTrack stations to represent the Incident Management Team functions of an operation

Depending on numbers we will use SARTrack terminals for some or all of the following functions:

· OPERATIONS – Creating taskings for the field stations

· RADIO OP – Transmitting the Taskings (Questions) to the field stations and updating the Ops Log.

· RADIO OP – Receiving messages (answers) from field stations, entering them into SARTrack and maintaining the Ops Log

· LOGISTICS – Assigning callsigns, loading data, managing the SARTrack mapping function etc.

The functions can be rotated around the available SARTrack operators during the exercise so everyone gets a turn at each function.

Guest logins will be available to allow SARTrack operators from outside the Auckland District to monitor and participate in non-transmitting functions if they wish. Contact Andy ZL1COP for guest logins for the 6400 Group.

SARTrack Procedure for the exercise

Most of the people participating in the exercise will not have GPS capable radios, and their stations will generally by at fixed locations. For this reason we will not be using the radio tracking functions of SARTrack.

We can however use the Map objects functions to plot locations and create and mark clues, objects etc. Those people with SARTrack Android apps will be able to update their location, create objects and message other SARTrack terminals if they wish.

For the purpose of the exercise the following procedures are suggested. (As this is an exercise we can try different options if there any issues with the suggested procedures).

Creating Tasks.

The Operation will be set up and a set of initial taskings created before the exercise starts. The tasks will be initially in OPEN status, and will take the form of Questions which the field stations must answer.

During the operation the OPERATIONS terminal may create additional task for any participant. Additional Tasks will be created using the NEW button on the Tasks Form. When creating a new task use the Task Type OTHER.

Task Names

The Question Tasks will be given Question number starting at 1. The Task Name will be in the form "Q1", "Q2" etc. (upper case no spaces). The task names will also form the message numbers when assigning the tasks to stations.

Other Tasks created during the exercise will be in the form T1, T2 etc. (Make sure to refer to the Task Form to avoid duplicate numbers when creating new tasks)

Re-Cycling Questions.

If we use up all the questions during the exercise we can re-cycle them by selecting completed tasks in the Team Setup Tasking Tab and marking them as OPEN. They can then be reassigned to different stations.

Assigning Tasks to Stations

The Comms operator handling outgoing tasks will have the Team Status and Team Setup Forms on their screen.

Team Status will show the status of all stations in the right-hand pane. This will indicate which stations are available for a new Tasking (Question) and which are still working on their Question.

In the example below ZK1EBA and ZK1EBC are busy with their tasks, and ZK1EBB is available for a new task.

By selecting the callsign tabs above the left pane, the operator can view the entire histroy for that callsign since the start of th exercise.

Assigning Tasks - Procedure

To assign a new task to a callsign the opertaor uses the Team Setup form. Select the TASKS Tab on the right-hand pane.

The right-hand pane shows all active tasks and their current status. The tasks are colour coded to indicate status. Pale blue indicates unassigned new tasks, Orange indicates assigned tasks (and the callsign is displayed). Green indicates completed (closed) tasks with the Callsign which actioned the task (in brackets).

To assign a task to a callsign, select the Tab of the callsign, click on the task in the right pane and drag and drop it into the Current Tasking box on the left.

The task will be assigned to the callsign and will change colour from blue to orange.

If you try to drop a task onto a callsign that is already assigned to a task, you will be asked to confirm you wish to remove the current task from that callsign and replace it with a new one. If you answer yes, the current task will be marked as completed ,will turn green, and will be removed from the callsign. The new task will be assigned in its place and turn orange.

Whenever you make a change to a team status you must Click the Save Team button to confirm the action

In the example below, Task Q101 has just been assigned to ZK1EBC. The Save Team button is red, awaiting confirmation.

Logging messages to / from Field Stations

The operator receiving inbound messages will use the New Log Entry Function of the Operation Log From.

Message logging can be done in either Standard View or Radio Ops View.

• Click the New Log Entry Button and complete the Log Entry Form as follows:

• Date/Time are automatically populated with the current time. You only need to fill these in if you are logging a message after the event.

• For log type we will use the default setting of Standard for this exercise

• Select From or To depending on in the message is going in or out.

• Select the callsign that the message is from/to from the drop down list in the centre box

• Enter the message text in the Message/Log Entry box. Put the message number at the begining of the text. The first line of text is transferred into the message summary field and is included in the ops log list. Putting the message number at the beginning ensures it is visible within the summary.

• Click OK to save the message to the log.

Log entry form for logging inbound and outbound messages. Note central drop down list for selection of callsigns.

The only fields that need to filled in for this exercise are From/to, Callsign, and Message.