[ Communiqués de Presse ]

SWORD 6.1.1 Preview

Major New Features

Scheduled for release towards the end of April, here we take you into our development center in Paris and provide a sneak preview of some powerful new features you’ll find in SWORD 6.1.1.

Total Control over the Messages you Receive from the Field

Communication is crucial

Receiving radio messages from units in the field is crucial to your ability to react decisively during a fast-moving exercise. For this reason in this release we have paid particular attention to this area, with a view to producing a system that optimizes the way you view electronic messages emitted by units in the field.

Redesigned from scratch

Reception of live messages you receive from units has been re-thought and is now centralized in a brand newReports window. The selection of messages displayed is now completely configurable, allowing you to use multiple filters in multiple views on the entire live input of messages from the field. Design principles closely follow those of the Timeline, a universally-acclaimed recent addition to the SWORD feature set.

All field reports in a unique knowledge center

A unique knowledge center is now available to view reports from every unit on the field, if you wish, as they are sent in to headquarters during action. A first view of this universal field report view is shown below.


Filter the view for more precision

As well as providing a unique global view of reports sent by units in the field, you can choose to filter the view to suit your needs.


Multiple views for multiple filters

Assign your filters to views, so you can flick between them to have an instant look at which sector of the battle is reporting what. In the example below you have created multiple filters, and assigned them to custom tabs. Any number can be created.


Customize the view for instant recognition of message types

Customize colors for each category of message for instant recognition of a preponderance of messages types and hence trends in the balance of power during exchanges


Further filter any view by selecting message categories

Messages are divided into any number of categories, depending on how your physical database is set up. In any view you can also choose the categories of messages you wish to display, as shown below.

Managing Medical Logistics Requests Manually

 Context: logistics process, previously handled automatically

To summarize, the logistics treatment cycle for the wounded depends on the:

–  availability of evacuation and collection ambulances with the required capacity and capability
–   availability of specialized doctors
–  severity of each injury
–  duration of diagnosis and triage
–  duration of treatment and convalescence
–  estimated lifespan following injury, and the expected ability to return to action, depending on the severity and type of injury
In version 6.1.1, every step in this complex process can be handled manually by the user.

Note: In SWORD, all of the above are configurable to suit any doctrine.

Concrete example in the field

Shown below is a standard logistics chain that supports a main battle tank squadron, where one tank platoon has been selected. It comprises a backup logistics base, shown furthest to the south, a primary supporting base in the center, and a logistics combat train that supports the squadron, positioned furthest to the north.


A request for medical assistance

A main battle tank platoon is carrying a trooper who has sustained an injury during battle, in this case in the highlighted unit on the map. When this occurs, the Blue side commander receives a request for medical assistance. This is shown here in the (also new) Reports window.


Prior to the request, the decision was made to switch to manual mode

Prior to the reception of the request the user decided that all medical requests would be handled manually, by simply choosing an option in a dropdown menu, as shown below.


What the user first sees

Now that the user is in manual mode, in the dedicated Health system window, which was opened following reception of the request, the user is now expected to start the manual process by clicking on the waiting for evacuation ambulance system prompt.


On clicking the first prompt, the first choice has to be made

When the user clicks on the waiting for evacuation ambulance selection prompt, the user is confronted by the first choice, as shown below.


If the user selects an ambulance, next comes triage doctor selection

If the user selects an ambulance for evacuation, then the process remains totally in his/her hands. Each stage continues in this fashion, with choices for equipment and doctors for triage and treatment. In the example below the user chooses a doctor for the triage of the wounded.


Skipping a manual option

At any stage in the manual process, if the user is unsure of the unit or doctor to select, he/she can always temporarily switch back to automatic mode, by choosing the Resolve automatically option, as can be seen above.

Requesting assistance from logistics superiors

In the logistics chain the combat train, also termed TC2, situated in the vicinity of the tank squadron, would normally deal with this medical request. However, the user can now intervene manually to instruct the stricken unit to switch its attention to the logistics superior of the combat train. The result of this is shown below, where the user has chosen the Request evacuation by logistics superior option, and as a result a pink dashed line now makes its way to the primary supporting logistics base, rather than the combat train.


Tags: , ,