C3LearningLabs - User contributions [en]

Doc/People

2022-03-28T23:17:30Z

Patrick Turner: /* Move people during a session */

{{DISPLAYTITLE: People}}

= Move people during a session =

People can be moved around the map by the session manager or an assigned player (People Controller).

To activate this functionality the manager or player needs to have the "PersonMoveControl" panel visible in their user interface.

This functionality is demonstrated in the demo configuration, '''\Demo\RescuePersons\P1C1-F2R1T1'''

In this demo session the manager and the player PC (People Controller) can move people.

It is located in: C:\C3LearningLabs\C3Fire\Client\SessionDef\Demo\RescuePersons\P1C1-F2R1T1

== Configuration ==
To activate the functionality the manager or player needs to have the "PersonMoveControl" panel visible in their user interface.
This is done by setting the Visible attribute to true, and setting the position of the panel in the user interface configuration.

More information at: UI Main Layout [[Config/UI/Main_Layout#PersonMoveControl|Person Move Control]]

<syntaxhighlight lang="xml">
<Object
Name = "PersonMoveControl"
BorderVisible = "True"
Enabeled = "False"
Pos = "1190,100"
Size = "140,85"
Visible = "True" />
</syntaxhighlight>

The user interface configuration must be in the xxx-UIMain-xxx.coni file.

;Player UI
The Player UI is defined in the xml element:
<syntaxhighlight lang="xml">
<UserInterfaceLayout>
...
<Layout
Name = "Ground Chief" >
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

;Manager UI
The Manager UI is defined in the xml element:
<syntaxhighlight lang="xml">
<ManagerConfig
WindowSize = "1325,945" >

<SessionControlLayout>
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

;Replay UI
The Replay UI is defined in the xml element:
<syntaxhighlight lang="xml">
<ReplayConfig
WindowSize = "1300,996" >

<SimulationMapLayout>
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

=== Color configuration ===

== People Control Panel ==

[[File:c3fire-config-ui-main-layout-person-move-control.png|border|Person Move Control]]

The "View People" button is a toggle button that is used to show the number of people at each location on the map.
The Moving number is the number of people the manager or player is currently moving.

;Map information
When the People control panel is visible all locations with people are indicated by a blue border.
When the manager or player presses the "View People" button, the map shows the number of people at each position.

{|
|[[File:c3fire-doc-people-map-normal.png|border|map normal]]
|         
|[[File:c3fire-doc-people-map-border.png|border|map border]]
|         
|[[File:c3fire-doc-people-map-number.png|border|map numberl]]
|         
|[[File:c3fire-doc-people-map-dead-2.png|border|map numberl]]
|-
|style="text-align: center;" |
Normal
|
|style="text-align: center;" |
Location visible
|
|style="text-align: center;" |
Amount visible
|
|style="text-align: center;" |
Lost people visible with red numbers
|}

== Move People ==

;Move
When the number of people at a location is visible, the manager or player can drag those people with the mouse. 
#Point the mouse pointer at a location with people.
#Press the left mouse button and keep it pressed.
#Move the mouse pointer to the desired location.
#Release the left mouse button
[[File:c3fire-doc-people-map-move-start.png||border|map border]]

;Specify the number of people to move
The manager or player can select the number of people to move. 
This is done by pressing a number key whilst dragging the mouse. 
Possible keys are <0> to <9>

#Point the mouse pointer to a location with people.
#Press the left mouse button and keep it pressed.
#Press key <0> to <9> on the keyboard.
#Move the mouse pointer to the desired location.
#Release the left mouse button.

[[File:c3fire-doc-people-map-move-end.png||border|map numberl]]

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T21:59:39Z

Patrick Turner: /* Log Events */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "A" IdName = "Ground Chief A" />
<Role IdNr = "B" IdName = "Ground Chief B" />
<Role IdNr = "C" IdName = "Ground Chief C" />
<Role IdNr = "D" IdName = "Ground Chief D" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a Unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contains all Person Move From To Unit or Pos Events is named person_move_from_to_unit_or_pos.txt. 
The database table that contains all Person Move From To Unit or Pos Events is named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of Role configuration, specifically the control of Units by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contains all Manager or player change Role Control Unit Events is named manager_or_player_change_role_control_unit.txt. 
The database table that contains all Manager or player change Role Control Unit Events is named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

=== Manager or player change Unit Send Info To Role Event ===

A Manager or player change Unit Send Info To Role Event defines the change of Unit configuration, specifically which Roles a Unit sends information (within its observation area) to.

The event type id number is 61. 
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
61 = "Manager or player change Unit Send Info To Role : Changer Unit Roles"
</source>

The event type file that contains all Manager or player change Unit Send Info To Role Events is named manager_or_player_change_unit_send_info_to_role.txt. 
The database table that contains all Manager or player change Unit Send Info To Role Events is named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID for the Unit that has been configured.
The value is an string. Example: F1 
The Unit ID numbers correspond to the Units in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles that the Unit sends information (within its observation area) to.
The value is an string. Example: A,B,C
|
|}

=== Manager or player change Role Can Send Mail To Role Event ===

A Manager or player change Role Can Send Mail To Role Event defines the change of Role configuration, specifically which Roles and Mail Groups a Role can send mail to.

The event type id number is 62. 
The information that is written to the Manager or player change Role Can Send Mail To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
62 = "Manager or player change Role Can Send Mail To Role : Changer Role Roles"
</source>

The event type file that contains all Manager or player change Role Can Send Mail To Role Events is named manager_or_player_change_role_can_send_mail_to_role.txt. 
The database table that contains all Manager or player change Role Can Send Mail To Role Events is named manager_or_player_change_role_can_send_mail_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles and Mail Groups that the Role can send mail to.
The value is an string. Example: B,C,All
|
|}

=== Manager or player change Mail Group Members Event ===

A Manager or player change Mail Group Members Event defines the change of Mail Group configuration, specifically which Roles are included in the Mail Group.

The event type id number is 63. 
The information that is written to the Manager or player change Mail Group Members Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
63 = "Manager or player change Mail Group Members : Changer MailGroup Members"
</source>

The event type file that contains all Manager or player change Mail Group Members Events is named manager_or_player_change_mail_group_members.txt. 
The database table that contains all Manager or player change Mail Group Members Events is named mmanager_or_player_change_mail_group_members. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | MailGroup
| style="vertical-align: text-top;" | The ID for the Mail Group that has been configured.
The value is an string. Example: All 
The Unit ID numbers correspond to the Mail Groups in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Members
| style="vertical-align: text-top;" | The IDs for all Roles included in the Mail Group.
The value is an string. Example: A,B,C
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T20:59:04Z

Patrick Turner: /* Log Events */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a Unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contains all Person Move From To Unit or Pos Events is named person_move_from_to_unit_or_pos.txt. 
The database table that contains all Person Move From To Unit or Pos Events is named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of Role configuration, specifically the control of Units by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contains all Manager or player change Role Control Unit Events is named manager_or_player_change_role_control_unit.txt. 
The database table that contains all Manager or player change Role Control Unit Events is named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

=== Manager or player change Unit Send Info To Role Event ===

A Manager or player change Unit Send Info To Role Event defines the change of Unit configuration, specifically which Roles a Unit sends information (within its observation area) to.

The event type id number is 61. 
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
61 = "Manager or player change Unit Send Info To Role : Changer Unit Roles"
</source>

The event type file that contains all Manager or player change Unit Send Info To Role Events is named manager_or_player_change_unit_send_info_to_role.txt. 
The database table that contains all Manager or player change Unit Send Info To Role Events is named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID for the Unit that has been configured.
The value is an string. Example: F1 
The Unit ID numbers correspond to the Units in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles that the Unit sends information (within its observation area) to.
The value is an string. Example: A,B,C
|
|}

=== Manager or player change Role Can Send Mail To Role Event ===

A Manager or player change Role Can Send Mail To Role Event defines the change of Role configuration, specifically which Roles and Mail Groups a Role can send mail to.

The event type id number is 62. 
The information that is written to the Manager or player change Role Can Send Mail To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
62 = "Manager or player change Role Can Send Mail To Role : Changer Role Roles"
</source>

The event type file that contains all Manager or player change Role Can Send Mail To Role Events is named manager_or_player_change_role_can_send_mail_to_role.txt. 
The database table that contains all Manager or player change Role Can Send Mail To Role Events is named manager_or_player_change_role_can_send_mail_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Unit ID numbers correspond to the Units in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles and Mail Groups that the Role can send mail to.
The value is an string. Example: B,C,All
|
|}

=== Manager or player change Mail Group Members Event ===

A Manager or player change Mail Group Members Event defines the change of Mail Group configuration, specifically which Roles are included in the Mail Group.

The event type id number is 63. 
The information that is written to the Manager or player change Mail Group Members Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
63 = "Manager or player change Mail Group Members : Changer MailGroup Members"
</source>

The event type file that contains all Manager or player change Mail Group Members Events is named manager_or_player_change_mail_group_members.txt. 
The database table that contains all Manager or player change Mail Group Members Events is named mmanager_or_player_change_mail_group_members. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | MailGroup
| style="vertical-align: text-top;" | The ID for the Mail Group that has been configured.
The value is an string. Example: All 
The Unit ID numbers correspond to the Mail Groups in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Members
| style="vertical-align: text-top;" | The IDs for all Roles included in the Mail Group.
The value is an string. Example: A,B,C
|
|}

Doc/People

2022-03-28T20:39:41Z

Patrick Turner: /* Move people during a session */

File:C3fire-doc-people-map-died.png

2022-03-28T20:38:59Z

Patrick Turner:

C3fire-doc-people-map-died

Doc/People

2022-03-28T20:24:08Z

Patrick Turner:

Doc/People

2022-03-28T20:18:14Z

Patrick Turner: /* Move people during a session */

{{DISPLAYTITLE: Civilian People}}

= Move people during a session =

People can be moved around the map by the session manager or an assigned player (People Controller).

To activate this functionality the manager or player needs to have the "PersonMoveControl" panel visible in their user interface.

This functionality is demonstrated in the demo configuration, '''\Demo\RescuePersons\P1C1-F2R1T1'''

In this demo session the manager and the player PC (People Controller) can move people.

It is located in: C:\C3LearningLabs\C3Fire\Client\SessionDef\Demo\RescuePersons\P1C1-F2R1T1

== Configuration ==
To activate the functionality the manager or player needs to have the "PersonMoveControl" panel visible in their user interface.
This is done by setting the Visible attribute to true, and setting the position of the panel in the user interface configuration.

More information at: UI Main Layout [[Config/UI/Main_Layout#PersonMoveControl|Person Move Control]]

<syntaxhighlight lang="xml">
<Object
Name = "PersonMoveControl"
BorderVisible = "True"
Enabeled = "False"
Pos = "1190,100"
Size = "140,85"
Visible = "True" />
</syntaxhighlight>

The user interface configuration must be in the xxx-UIMain-xxx.coni file.

;Player UI
The Player UI is defined in the xml element:
<syntaxhighlight lang="xml">
<UserInterfaceLayout>
...
<Layout
Name = "Ground Chief" >
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

;Manager UI
The Manager UI is defined in the xml element:
<syntaxhighlight lang="xml">
<ManagerConfig
WindowSize = "1325,945" >

<SessionControlLayout>
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

;Replay UI
The Replay UI is defined in the xml element:
<syntaxhighlight lang="xml">
<ReplayConfig
WindowSize = "1300,996" >

<SimulationMapLayout>
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

=== Color configuration ===

== People Control Panel ==

[[File:c3fire-config-ui-main-layout-person-move-control.png|border|Person Move Control]]

The "View People" button is a toggle button that is used to show the number of people at each location on the map.
The Moving number is the number of people the manager or player is currently moving.

;Map information
When the People control panel is visible all locations with people are indicated by a blue border.
When the manager or player presses the "View People" button, the map shows the number of people at each position.

{|
|[[File:c3fire-doc-people-map-normal.png|border|map normal]]
|         
|[[File:c3fire-doc-people-map-border.png|border|map border]]
|         
|[[File:c3fire-doc-people-map-number.png|border|map numberl]]
|         
|[[File:c3fire-doc-people-map-dead-2.png|border|map numberl]]
|-
|style="text-align: center;" |
Normal
|
|style="text-align: center;" |
Location visible
|
|style="text-align: center;" |
Amount visible
|
|style="text-align: center;" |
Lost people visible with red numbers
|}

== Move People ==

;Move
When the number of people at a location is visible, the manager or player can drag those people with the mouse. 
#Point the mouse pointer at a location with people.
#Press the left mouse button and keep it pressed.
#Move the mouse pointer to the desired location.
#Release the left mouse button
[[File:c3fire-doc-people-map-move-start.png||border|map border]]

;Specify the number of people to move
The manager or player can select the number of people to move. 
This is done by pressing a number key whilst dragging the mouse. 
Possible keys are <0> to <9>

#Point the mouse pointer to a location with people.
#Press the left mouse button and keep it pressed.
#Press key <0> to <9> on the keyboard.
#Move the mouse pointer to the desired location.
#Release the left mouse button.

[[File:c3fire-doc-people-map-move-end.png||border|map numberl]]

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T19:13:10Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a Unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of Role configuration, specifically the control of Units by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

=== Manager or player change Unit Send Info To Role Event ===

A Manager or player change Unit Send Info To Role Event defines the change of Unit configuration, specifically which Roles a Unit sends information (within its observation area) to.

The event type id number is 61. 
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
61 = "Manager or player change Unit Send Info To Role : Changer Unit Roles"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_unit_send_info_to_role.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID for the Unit that has been configured.
The value is an string. Example: F1 
The Unit ID numbers correspond to the Units in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles that the Unit sends information (within its observation area) to.
The value is an string. Example: A,B,C
|
|}

=== Manager or player change Role Can Send Mail To Role Event ===

A Manager or player change Role Can Send Mail To Role Event defines the change of Role configuration, specifically which Roles and Mail Groups a Role can send mail to.

The event type id number is 62. 
The information that is written to the Manager or player change Role Can Send Mail To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
62 = "Manager or player change Role Can Send Mail To Role : Changer Role Roles"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_can_send_mail_to_role.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_can_send_mail_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Unit ID numbers correspond to the Units in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles and Mail Groups that the Role can send mail to.
The value is an string. Example: B,C,All
|
|}

=== Manager or player change Mail Group Members Event ===

A Manager or player change Mail Group Members Event defines the change of Mail Group configuration, specifically which Roles are included in the Mail Group.

The event type id number is 63. 
The information that is written to the Manager or player change Mail Group Members Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
63 = "Manager or player change Mail Group Members : Changer MailGroup Members"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_mail_group_members.txt. 
The database table that contain all send observed unit events are named mmanager_or_player_change_mail_group_members. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | MailGroup
| style="vertical-align: text-top;" | The ID for the Mail Group that has been configured.
The value is an string. Example: All 
The Unit ID numbers correspond to the Mail Groups in the configuration files being used in the session.
|
|-
| style="vertical-align: text-top;" | Members
| style="vertical-align: text-top;" | The IDs for all Roles included in the Mail Group.
The value is an string. Example: A,B,C
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T19:06:44Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a Unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of Role configuration, specifically the control of Units by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

=== Manager or player change Unit Send Info To Role Event ===

A Manager or player change Unit Send Info To Role Event defines the change of Unit configuration, specifically which Roles a Unit sends information (within its observation area) to.

The event type id number is 61. 
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
61 = "Manager or player change Unit Send Info To Role : Changer Unit Roles"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_unit_send_info_to_role.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID for the Unit that has been configured.
The value is an string. Example: F1 
The Unit ID numbers correspond to the Units in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles that the Unit sends information (within its observation area) to.
The value is an string. Example: A,B,C
|
|}

=== Manager or player change Role Can Send Mail To Role Event ===

A Manager or player change Role Can Send Mail To Role Event defines the change of Role configuration, specifically which Roles and Mail Groups a Role can send mail to.

The event type id number is 62. 
The information that is written to the Manager or player change Role Can Send Mail To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
62 = "Manager or player change Role Can Send Mail To Role : Changer Role Roles"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_can_send_mail_to_role.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_can_send_mail_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Unit ID numbers correspond to the Units in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles and Mail Groups that the Role can send mail to.
The value is an string. Example: B,C,All
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T18:55:27Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a Unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of Role configuration, specifically the control of Units by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

=== Manager or player change Unit Send Info To Role Event ===

A Manager or player change Unit Send Info To Role Event defines the change of Unit configuration, specifically which Roles a Unit sends information (within its observation area) to.

The event type id number is 61. 
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
61 = "Manager or player change Unit Send Info To Role : Changer Unit Roles"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_unit_send_info_to_role.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID for the Unit that has been configured.
The value is an string. Example: F1 
The Unit ID numbers correspond to the Units in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles that the Unit sends information (within its observation area) to.
The value is an string. Example: A,B,C
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T18:54:26Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a Unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of Role configuration, specifically the control of Units by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

=== Manager or player change Unit Send Info To Role Event ===

A Manager or player change Unit Send Info To Role Event defines the change of Unit configuration, specifically which Roles a Unit sends information (within its observation area) to.

The event type id number is 61. 
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
61 = "Manager or player change Unit Send Info To Role : Changer Unit Roles"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_unit_send_info_to_role.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID for the Unit that has been configured.
The value is an string. Example: F1 
The Unit ID numbers correspond to the Units in the session.
|
|-
| style="vertical-align: text-top;" | Roles
| style="vertical-align: text-top;" | The IDs for all Roles that the Unit sends information (within its observation area) to.
The value is an string. Example: F1,F2,F3,F4
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T18:44:46Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of a configuration setting for the control of Units by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

=== Manager or player change Unit Send Info To Role Event ===

A Manager or player change Unit Send Info To Role Event defines the change of a configuration setting for a Unit sending information (within its observation area) to Roles.

The event type id number is 61. 
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
61 = "Manager or player change Unit Send Info To Role : Changer Unit Roles"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_unit_send_info_to_role.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T18:13:28Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 
 
The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The ID for the type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of a configuration setting for the control of a Unit by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T18:10:43Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position 

The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 

Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of a configuration setting for the control of a Unit by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T18:09:26Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* A Player loads a person from a position to a unit
* A Player unloads a person from a Unit to a position
* A Manager or Player moves a person from a position to another position

The event type id number is 51. 
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>. 
Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 6 
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. 
The value is an integer. Example: 5 
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. 
The value is an integer. Example: 10 
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1.
The value is an integer. Example: 12 
|
|}

=== Manager or player change Role Control Unit Event ===

A Manager or player change Role Control Unit Event defines the change of a configuration setting for the control of a Unit by a Role.

The event type id number is 60. 
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>. 
Example
<source>
60 = "Manager or player change Role Control Unit : Changer Role Units"
</source>

The event type file that contain all send observed unit events are named manager_or_player_change_role_control_unit.txt. 
The database table that contain all send observed unit events are named manager_or_player_change_role_control_unit. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Changer
| style="vertical-align: text-top;" | The ID for the Manager or Player that made the configuration change.
The value is an integer. Example: -1 
The ID of a Manager is -1. This is the only possible value for this property at the moment.
|
|-
| style="vertical-align: text-top;" | Role
| style="vertical-align: text-top;" | The ID for the Role that has been configured.
The value is an string. Example: A 
The Role ID numbers correspond to the Roles in the session.
|
|-
| style="vertical-align: text-top;" | Units
| style="vertical-align: text-top;" | The IDs for all Units that are under control of the Role following the configuration event.
The value is an string. Example: F1,F2,F3,F4
|
|}

C3Fire:Doc/Analysis/Log File Structure

2022-03-28T17:38:25Z

Patrick Turner: /* Event Types */

{{DISPLAYTITLE:C3Fire Log Events}}

[[File:C3ll-head-under-construction-small.png]] 
= Log Events =

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules. 
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log. 

All events belongs to a specific event type. The event types in C3Fire are described below.

 Log File Management 
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type.
In the event type description below the content of each event type log file are described in the table cells with white background.

 Database Support 
It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis.
The database will contain a table for each event type. The database tables are given a name based on the event type.
Database specific information is described in the table cells with green background.

== Log File Structure ==

== Identification numbers ==

=== Role ID Numbers ===
The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<RoleIDNrs>
<Role IdNr = "0" IdName = "Info" />
<Role IdNr = "1" IdName = "Fire" />
<Role IdNr = "2" IdName = "Logistic" />
<Role IdNr = "3" IdName = "Rescue" />
</RoleIDNrs>
</source>

=== Unit ID Numbers ===
The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<UnitIDNrs>
<Unit IdNr = "0" IdName = "F1" />
<Unit IdNr = "1" IdName = "F2" />
<Unit IdNr = "2" IdName = "F3" />
<Unit IdNr = "3" IdName = "F4" />
<Unit IdNr = "4" IdName = "L5" />
<Unit IdNr = "5" IdName = "L6" />
<Unit IdNr = "6" IdName = "R7" />
<Unit IdNr = "7" IdName = "R8" />
<Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>
</source>

=== Unit Activity ID Numbers ===

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file. 

Example
<source>
Unit Activity 0 = Not Defined
Unit Activity 1 = Inactive
Unit Activity 2 = Moving
Unit Activity 3 = Mobilizing
Unit Activity 4 = Fire Fighting
Unit Activity 5 = De Mobilizing
Unit Activity 6 = Refill Water
Unit Activity 7 = Refill Fule
Unit Activity 8 = Tap Water
Unit Activity 9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People
</source>

=== Fire State ID Numbers ===
The fire state id numbers are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<FireTypeIDNrs>
<FireType IdNr = "1" IdName = "Clear" />
<FireType IdNr = "2" IdName = "Fire" />
<FireType IdNr = "3" IdName = "ClosedOut" />
<FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>
</source>

=== Object Type ID Numbers ===
The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>. 

Example
<source>
<ObjectTypeIDNrs>
<ObjectType IdNr = "0" IdName = "Normal" />
<ObjectType IdNr = "1" IdName = "Pine" />
<ObjectType IdNr = "2" IdName = "Birch" />
<ObjectType IdNr = "3" IdName = "House" />
<ObjectType IdNr = "4" IdName = "Water" />
<ObjectType IdNr = "5" IdName = "Fuel" />
<ObjectType IdNr = "6" IdName = "People" />
<ObjectType IdNr = "7" IdName = "Tent" />
<ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
<ObjectType IdNr = "9" IdName = "UAVBaseNW" />
<ObjectType IdNr = "10" IdName = "UAVBaseN" />
<ObjectType IdNr = "11" IdName = "UAVBaseNE" />
<ObjectType IdNr = "12" IdName = "UAVBaseW" />
<ObjectType IdNr = "13" IdName = "UAVBaseC" />
<ObjectType IdNr = "14" IdName = "UAVBaseE" />
<ObjectType IdNr = "15" IdName = "UAVBaseSW" />
<ObjectType IdNr = "16" IdName = "UAVBaseS" />
<ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>
</source>

== Event Types ==

=== Scenario Event ===

A scenario event is a time stamped event that is done in the simulation, at some specified time. 

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt. 
The database table that contain all scenario events are named scenario_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | Command
| style="vertical-align: text-top;" | Events that effect the session. 
The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".
|}

=== Fire Event ===

A Fire Event defines the fire state in one specific position on the map. 

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>. 
Example
<source>
11 = "Fire Event : State PosX PosY"
</source>

The event type file that contain all fire events are named fire_event.txt. 
The database table that contain all fire events are named fire_event. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|-
| style="vertical-align: text-top;" | State
| style="vertical-align: text-top;" | The state of the fire at the specified position. 
The value is an integer. Example: 2.
 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the number represent.
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Horizontal position on the Map.
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Vertical position the Map.
|}

=== Unit State ===
When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules. 

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
12 = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"
</source>

The event type file that contain all unit state events are named unit_state.txt. 
The database table that contain all unit state events are named unit_state. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterRefillSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is refilled from a water tank unit or a water tank station. The
number of water levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterTapSpeed
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the water level is taped from the water to a unit. The number of water levels
moved every second.
The value is a decimal number. Example 5.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelRefillSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The
number of fuel levels moved every second.
The value is a decimal number. Example 3.5
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelTapSpeed
| style="background-color:#ffffff; vertical-align: text-top;" | The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second.
The value is a decimal number. Example 4.2
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportEnterTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people is enter the unit. The
number of seconds it takes for one person to enter the unit.
The value is a decimal number. Example 10.5
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportLeaveTime
| style="background-color:#f0f0f0; vertical-align: text-top;" | The current speed with which the people leave the unit. The
number of seconds it takes for one person to leave the unit.
The value is a decimal number. Example 6.0
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send Unit State to Role ===

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created. 

The event type id number are 13. 
The information that is written in the send unit state events are described in the xml element <LogEventInfo>. 
Example
<source>
13 = "Unit send Unit State to Role : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"
</source>

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt. 
The database table that contain all send unit state events are named unit_send_unit_state_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The ID number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | Activity
| style="vertical-align: text-top;" | The activity the unit currently are doing. 
The value is an integer. Example: 1 
See [[#Unit Activity ID Numbers|Unit Activity ID Numbers]] for what the activity numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | IntentionX
| style="vertical-align: text-top;" | Horizontal position on the map towards which the unit is heading.
The value is an integer. Example: 22
|
|-
| style="vertical-align: text-top;" | IntentionY
| style="vertical-align: text-top;" | Vertical position on the map towards which the unit is heading.
The value is an integer. Example: 37
|
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLevel
| style="background-color:#f0f0f0; vertical-align: text-top;" | The amount of water in the unit's water tank.
The value is an integer. Example: 34
| style="background-color:#f0f0f0; vertical-align: text-top;" | WaterLogistic
|-
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLevel
| style="background-color:#ffffff; vertical-align: text-top;" | The amount of fuel in the unit's fuel tank.
The value is a decimal number. Example 55.4
| style="background-color:#ffffff; vertical-align: text-top;" | FuelLogistic
|-
| style="background-color:#f0f0f0; vertical-align: text-top;" | PeopleTransportNrOfPeople
| style="background-color:#f0f0f0; vertical-align: text-top;" | The number of people in the unit.
The value is an integer. Example 2
| style="background-color:#f0f0f0; vertical-align: text-top;" | People
|}

=== Unit send observed Object to Role ===

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the object appears in the receiving roles map. 

The event type id number are 14. 
The information that is written in the send observed object events are described in the xml element <LogEventInfo>. 
Example
<source>
14 = "Unit send observed Object to Role : SenderUnit ReceiverRole PosX PosY Object"
</source>

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt. 
The database table that contain all send observed objects events are named unit_send_observed_object_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Object
| style="vertical-align: text-top;" | The ID number for the object this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Object Type ID Numbers|Object Type ID Numbers]] for what the object ID numbers represent.
|
|}

=== Unit send observed Fire to Role ===

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the fire appears in the receiving roles map. 

The event type id number are 15. 
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>. 
Example
<source>
15 = "Unit send observed Fire to Role : SenderUnit ReceiverRole PosX PosY Fire"
</source>

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt. 
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Unit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Fire
| style="vertical-align: text-top;" | The ID number for the fire type this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Fire State ID Numbers|Fire State ID Numbers]] for what the fire type ID numbers represent.
|
|}

=== Unit send observed Unit to Role ===

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent
to is configured in session configuration. When sent, the unit will appears in the receiving roles map. 

The event type id number are 16. 
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>. 
Example
<source>
16 = "Unit send observed Unit to Role : SenderUnit ReceiverRole PosX PosY Unit IsVisible"
</source>

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt. 
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event did occur. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | SenderUnit
| style="vertical-align: text-top;" | The id number for the unit.
The value is an integer. Example: 1 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit numbers represent.
|
|-
| style="vertical-align: text-top;" | ReceiverRole
| style="vertical-align: text-top;" | The ID number for the role that the information is send to.
The value is an integer. Example: 1 
See [[#Role ID Numbers|Role ID Numbers]] for what the role numbers represent.
|
|-
| style="vertical-align: text-top;" | PosX
| style="vertical-align: text-top;" | Current horizontal position on the Map.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | PosY
| style="vertical-align: text-top;" | Current vertical position the Map.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Unit (observed)
| style="vertical-align: text-top;" | The ID number for the unit this unit have in its range of sight. 
The value is an integer. Example: 5 
See [[#Unit ID Numbers|Unit ID Numbers]] for what the unit ID numbers represent.
|
|-
| style="vertical-align: text-top;" | IsVisible
| style="vertical-align: text-top;" | If the unit is visible or not.
The false value is used to tell the role that it no longer can see the unit.
Possible values : "false", "true" in log file and "0", "1" in the database.
|
|}

=== Person Move From To Unit or Pos Event ===

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:
* By a Player by loading the person onto a Unit

The event type id number is 51. 
The information that is written to the people movement event is described in the xml element <LogEventInfo>. 
Example
<source>
51 = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"
</source>

The event type file that contain all send observed unit events are named person_move_from_to_unit_or_pos.txt. 
The database table that contain all send observed unit events are named person_move_from_to_unit_or_pos. 

{| class="wikitable"
| style="background-color:#ddffdd;" | Database table specific properties
| style="background-color:#ddffdd;" | Description
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | GroupNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events group nr.
The value is an integer. Example: 5
|-
| style="background-color:#ddffdd; vertical-align: text-top;" | SessionNumber
| style="background-color:#ddffdd; vertical-align: text-top;" | This events session nr. 
The value is an integer. Example: 12
|-
| Event properties
| Description
| Module
|-
| style="vertical-align: text-top;" | EventNumber
| style="vertical-align: text-top;" | When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. 
The value is an integer. Example: 625
|
|-
| style="vertical-align: text-top;" | Time
| style="vertical-align: text-top;" | The session time when the event occurred. 
The value is a string "HH:MM:SS". Value example = "02:15:00"
|
|-
| style="vertical-align: text-top;" | Person
| style="vertical-align: text-top;" | The ID number for the person.
The value is an integer. Example: 1 
See [[#Person ID Numbers|Person ID Numbers]] for what the person numbers represent.
|
|-
| style="vertical-align: text-top;" | PersonType
| style="vertical-align: text-top;" | The type of person.
The value is an integer. Example: 1 
See [[#PersonType ID Numbers|Person Type ID Numbers]] for what the person ID numbers represent.
|
|-
| style="vertical-align: text-top;" | MoveType
| style="vertical-align: text-top;" | The type of person movement.
The value is an integer. Example: 6|
|
|-
| style="vertical-align: text-top;" | Unit1
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved from. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Unit2
| style="vertical-align: text-top;" | The ID number for the unit that the person was moved to. 
The value is an string. Example: R9 
|
|-
| style="vertical-align: text-top;" | Pos1X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved from.
The value is an integer. Example: 6
|
|-
| style="vertical-align: text-top;" | Pos1Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved from.
The value is an integer. Example: 5
|
|-
| style="vertical-align: text-top;" | Pos2X
| style="vertical-align: text-top;" | The horizontal position on the map that the person was moved to.
The value is an integer. Example: 10
|
|-
| style="vertical-align: text-top;" | Pos2Y
| style="vertical-align: text-top;" | The vertical position the map that the person was moved to.
The value is an integer. Example: 12
|
|}

Doc/AgileOrganization

2022-03-28T15:43:23Z

Patrick Turner: /* Organizational change during a session */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains three panels.
* Role Selector: Select which Role to edit
* Role Editor: Edit Role configuration
* Properties: View all properties for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role Editor
Edit Role configuration:
* Select and unselect which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select and unselect which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Properties

This panel is split into two sections. The left-hand side displays Role configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains three panels.
* Unit Selector: Select which Unit to edit.
* Unit Editor: Edit Unit configuration.
* Properties: View all properties for the Unit.

More information can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]
;Unit Editor
Edit Unit configuration:
* Select and unselect which Roles the Unit sends information (within its observation area) to.

[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Properties
This panel is split into two sections. The left-hand side displays Unit configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configuration. These changes take effect immediately.

Agile Configuration contains four panels.
* Unit Controlled by Role: Which Roles each Unit is controlled by.
* Unit Send Info to Role: Which Roles each Unit will send the information (within their observation areas) to.
* Mail Group includes Role: Which Roles are members of each Mail Group.
* Role can send mail to Role / Mail Group: Which Roles and Mail Groups each Role can send mail to.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Unit Controlled by Role ==
Which Roles each Unit is controlled by:
* Select and unselect Roles.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit Send Info to Role ==
Which Roles each Unit will send the information (within their observation areas) to.
* Select and unselect Roles.

[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Mail Group includes Role ==
Which Roles are members of each Mail Group.
* Select and unselect Roles.

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

== Role can send mail to Role / Mail Group ==
Which Roles and Mail Groups each Role can send mail to.
* Select and unselect Roles and Mail Groups.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

;Mail Groups
In the Agile Configuration window, it is only possible to select existing Mail Groups. It is possible to create Mail Groups but this is done in the <MailGroups> configuration element in the relevant .con or .coni file, not in the Agile Configuration window. This means that Mail Groups must be created before a session and cannot be creating during a session.

More information can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

Doc/AgileOrganization

2022-03-28T15:40:21Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains three panels.
* Role Selector: Select which Role to edit
* Role Editor: Edit Role configuration
* Properties: View all properties for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role Editor
Edit Role configuration:
* Select and unselect which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select and unselect which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Properties

This panel is split into two sections. The left-hand side displays Role configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains three panels.
* Unit Selector: Select which Unit to edit.
* Unit Editor: Edit Unit configuration.
* Properties: View all properties for the Unit.

More information can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]
;Unit Editor
Edit Unit configuration:
* Select and unselect which Roles the Unit sends information (within its observation area) to.

[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Properties
This panel is split into two sections. The left-hand side displays Unit configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configuration. These changes take effect immediately.

Agile Configuration contains four panels.
* Unit Controlled by Role: Which Roles each Unit is controlled by.
* Unit Send Info to Role: Which Roles each Unit will send the information (within their observation areas) to.
* Mail Group includes Role: Which Roles are members of each Mail Group.
* Role can send mail to Role / Mail Group: Which Roles and Mail Groups each Role can send mail to.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Unit Controlled by Role ==
Which Roles each Unit is controlled by:
* Select or unselect Roles.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit Send Info to Role ==
Which Roles each Unit will send the information (within their observation areas) to.
* Select or unselect Roles.

[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Mail Group includes Role ==
Which Roles are members of each Mail Group.
* Select or unselect Roles

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

== Role can send mail to Role / Mail Group ==
Which Roles and Mail Groups each Role can send mail to.
* Select or unselect Roles and Mail Groups.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

;Mail Groups
In the Agile Configuration window, it is only possible to select existing Mail Groups. It is possible to create Mail Groups but this is done in the <MailGroups> configuration element in the relevant .con or .coni file, not in the Agile Configuration window. This means that Mail Groups must be created before a session and cannot be creating during a session.

More information can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

Doc/AgileOrganization

2022-03-28T15:38:08Z

Patrick Turner: /* Organizational change during a session */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains three panels.
* Role Selector: Select which Role to edit
* Role Editor: Edit Role configuration
* Properties: View all properties for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role Editor
Edit Role configuration:
* Select which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Properties

This panel is split into two sections. The left-hand side displays Role configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains three panels.
* Unit Selector: Select which Unit to edit.
* Unit Editor: Edit Unit configuration.
* Properties: View all properties for the Unit.

More information can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]
;Unit Editor
Edit Unit configuration:
* Select which Roles the Unit sends information (within its observation area) to.

[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Properties
This panel is split into two sections. The left-hand side displays Unit configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configuration. These changes take effect immediately.

Agile Configuration contains four panels.
* Unit Controlled by Role: Which Roles each Unit is controlled by.
* Unit Send Info to Role: Which Roles each Unit will send the information (within their observation areas) to.
* Mail Group includes Role: Which Roles are members of each Mail Group.
* Role can send mail to Role / Mail Group: Which Roles and Mail Groups each Role can send mail to.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Unit Controlled by Role ==
Which Roles each Unit is controlled by:
* Select or unselect Roles.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit Send Info to Role ==
Which Roles each Unit will send the information (within their observation areas) to.
* Select or unselect Roles.

[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Mail Group includes Role ==
Which Roles are members of each Mail Group.
* Select or unselect Roles

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

== Role can send mail to Role / Mail Group ==
Which Roles and Mail Groups each Role can send mail to.
* Select or unselect Roles and Mail Groups.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

;Mail Groups
In the Agile Configuration window, it is only possible to select existing Mail Groups. It is possible to create Mail Groups but this is done in the <MailGroups> configuration element in the relevant .con or .coni file, not in the Agile Configuration window. This means that Mail Groups must be created before a session and cannot be creating during a session.

More information can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

Doc/AgileOrganization

2022-03-28T15:34:01Z

Patrick Turner: /* Organizational change during a session */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains three panels.
* Role Selector: Select which Role to edit
* Role Editor: Edit Role configuration
* Properties: View all properties for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role Editor
Edit Role configuration:
* Select which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Properties

This panel is split into two sections. The left-hand side displays Role configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains three panels.
* Unit Selector: Select which Unit to edit.
* Unit Editor: Edit Unit configuration.
* Properties: View all properties for the Unit.

More information can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]
;Unit Editor
Edit Unit configuration:
* Select which Roles the Unit sends information (within its observation area) to.

[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Properties
This panel is split into two sections. The left-hand side displays Unit configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configuration. These changes take effect immediately.

Agile Configuration contains four panels.
* Unit Controlled by Role: Which Roles each Unit is controlled by.
* Unit Send Info to Role: Which Roles each Unit will send the information (within their observation areas) to.
* Mail Group includes Role: Which Roles are members of each Mail Group.
* Role can send mail to Role / Mail Group: Which Roles and Mail Groups each Role can send mail to.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Unit Controlled by Role ==
Which Roles each Unit is controlled by:
* Select or unselect Roles.
[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit Send Info to Role ==
Which Roles each Unit will send the information (within their observation areas) to.
* Select or unselect Roles.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Mail Group includes Role ==
Which Roles are members of each Mail Group.
* Select or unselect Roles

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

== Role can send mail to Role / Mail Group ==
Which Roles and Mail Groups each Role can send mail to.
* Select or unselect Roles and Mail Groups.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

;Mail Groups
In the Agile Configuration window, it is only possible to select existing Mail Groups. It is possible to create Mail Groups but this is done in the <MailGroups> configuration element in the relevant .con or .coni file, not in the Agile Configuration window. This means that Mail Groups cannot be created during a session.

More information can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

Doc/AgileOrganization

2022-03-28T14:56:54Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains three panels.
* Role Selector: Select which Role to edit
* Role Editor: Edit Role configuration
* Properties: View all properties for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role Editor
Edit Role configuration:
* Select which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Properties

This panel is split into two sections. The left-hand side displays Role configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains three panels.
* Unit Selector: Select which Unit to edit.
* Unit Editor: Edit Unit configuration.
* Properties: View all properties for the Unit.

More information can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]
;Unit Editor
Edit Unit configuration:
* Select which Roles the Unit sends information (within its observation area) to.

[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Properties
This panel is split into two sections. The left-hand side displays Unit configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-28T14:54:57Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains three panels.
* Role Selector: Select which Role to edit
* Role Editor: Edit Role configuration
* Properties: View all properties for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role Editor
Edit Role configuration:
* Select which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Properties

This panel is split into two sections. The left-hand side displays Role configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains four panels.
* Unit Selector: Select which Unit to edit.
* Unit Editor: Edit Unit configuration.
* Properties: View all properties for the Unit.

More information can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]
;Unit Editor
Edit Unit configuration:
* Select which Roles the Unit sends information (within its observation area) to.

[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Properties
This panel is split into two sections. The left-hand side displays Unit configuration properties and values, in tabular format. The right-hand side displays the corresponding XML. The information in this panel updates as changes are made in the panels above.

[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

;Save Before Starting Session
If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-28T14:45:01Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Select which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property and XML viewers

These panels display Role configuration properties, which update as they are edited in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Select which Roles the Unit sends information (within its observation area) to.

[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property and XML viewers
These panels display Unit configuration properties.

[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-28T14:36:03Z

Patrick Turner: /* Pre session configuration */

Doc/AgileOrganization

2022-03-28T14:33:02Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Select which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property and XML viewers

These panels display Role configuration properties, which update as they are edited in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Role Configuration and Unit Configuration windows.

If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property and XML viewers
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder. This includes all changes made in both the Unit Configuration and Role Configuration windows.

If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Unit Configuration and Role Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-28T14:29:16Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.

[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Select which Units the Role can control.

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Select which Roles and Mail Groups the Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property and XML viewers

These panels display Role configuration properties, which update as they are edited in the panels above.

[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

;Save configuration

Clicking the Save button will generate the following dialog box:

[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

Clicking Yes will save changes to the configuration (.con and .coni) files in the relevant configuration folder.

If Save is not clicked and the user clicks Start (in the Session Control panel in the Play tab), the following dialog box appears:

[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]

;After starting a C3Fire session

The Role Configuration and Unit Configuration buttons are inactive. Only the Agile Configuration button is available in the Configuration tab.

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property and XML viewers
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration
[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]
[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-28T14:09:59Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration window contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Which Roles and Mail Groups the selected Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property XML viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property and XML viewers
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

;Save Configuration
[[File:c3fire-doc-agile-organization-save-befor-start.png|border|Person Move Control]]
[[File:c3fire-doc-agile-organization-save-warning-2.png|border|Person Move Control]]

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-agile-main-2.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:C3fire-doc-agile-organization-agile-role-can-send-mail-to-3.png|border|Send Mail To]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit-2.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:59:15Z

Patrick Turner: /* Pre session configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control

[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

* Which Roles and Mail Groups the selected Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:57:22Z

Patrick Turner: /* Organizational change during a session */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Roles are members of each Mail Group.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:57:07Z

Patrick Turner: /* Mail Groups */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Mail Groups each Role is a member of.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Roles are members of each Mail Group.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:55:50Z

Patrick Turner: /* Mail Groups */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Mail Groups each Role is a member of.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More information about Mail Group configuration can be found at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Mail Groups each Role is a member of.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:54:25Z

Patrick Turner: /* Organization change during session */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organizational change during a session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.

Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Mail Groups each Role is a member of.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create Mail Groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Mail group membership
Which Mail Groups each Role is a member of.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:51:06Z

Patrick Turner: /* Organization change during session */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the Manager is able to change the organization during a session by changing Role, Unit and Mail Group configurations.
Agile Configuration contains four panels.
* Role control unit: Which Units each Role can control.
* Unit send information to role: Which Roles each Unit will send the information (within their observation areas) to.
* Role can send mail to role: Which Roles and Mail Groups each Role can send mail to and chat with.
* Mail group membership: Which Mail Groups each Role is a member of.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
Which Units each Role can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
Which Roles each Unit will send the information (within their observation areas) to.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
Which Roles and Mail Groups each Role can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:47:26Z

Patrick Turner: /* Unit configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

Unit Configuration contains four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:44:42Z

Patrick Turner: /* Unit configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The Unit configuration tab contain four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.

[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:43:26Z

Patrick Turner: /* Role configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the Role.
* XML viewer: View the xml configuration for the Role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The Unit configuration tab contain four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:43:03Z

Patrick Turner: /* Role configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contains four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The Unit configuration tab contain four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:42:36Z

Patrick Turner: /* Role configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration tab contain four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The Unit configuration tab contain four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:42:22Z

Patrick Turner: /* Unit configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration contain four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The Unit configuration tab contain four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:41:46Z

Patrick Turner: /* Role configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration contain four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The unit configuration contain four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:41:29Z

Patrick Turner: /* Unit configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration contain four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panel display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The unit configuration contain four panels.
* Unit selector: Select which Unit to edit.
* Unit editor: Edit Unit configuration.
* Property viewer: View all properties for the Unit.
* XML viewer: View the xml configuration for the Unit.

More information about Unit configuration can be found at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
Select which Unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Edit Unit configuration:
* Which Roles the selected Unit sends information (within its observation area) to.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels display Unit configuration properties.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:37:19Z

Patrick Turner: /* Role configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration contain four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panel display Role configuration properties.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The unit configuration contain four panels.
* Unit selector: What unit to edit
* Unit editor: The editor panel
* Property viewer: View all properties for the unit.
* XML viewer: View the xml configuration for the unit.

More about the unit configuration at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
:Select what unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Whit the unit editor you can edit.
* What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels only display the properties for the unit.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:36:24Z

Patrick Turner: /* Role configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration contain four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles and Mail Groups the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels only display the properties for the role.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The unit configuration contain four panels.
* Unit selector: What unit to edit
* Unit editor: The editor panel
* Property viewer: View all properties for the unit.
* XML viewer: View the xml configuration for the unit.

More about the unit configuration at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
:Select what unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Whit the unit editor you can edit.
* What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels only display the properties for the unit.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/AgileOrganization

2022-03-27T22:34:50Z

Patrick Turner: /* Role configuration */

{{DISPLAYTITLE:Agile Organization}}

= Pre session configuration =

== Role configuration ==

The role configuration contain four panels.
* Role selector: Select which Role to edit
* Role editor: Edit Role configuration
* Property viewer: View all properties for the role.
* XML viewer: View the xml configuration for the role.

More information about Role configuration can be found at '''[[Config/Config_Role#Role|Role Configuration]]'''.

[[File:c3fire-doc-agile-organization-role-main.png|800px|border|Person Move Control]]

;Role Selector
:Select which Role to edit.
[[File:c3fire-doc-agile-organization-role-select-role.png|border|Person Move Control]]

;Role editor
Edit Role configuration:
* Which Units the selected Role can control
* Which Roles the selected Role can send mail to and chat with.
[[File:c3fire-doc-agile-organization-role-edit.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-role-edit-2.png|border|Person Move Control]]

;Property xml viewer
:These panels only display the properties for the role.
[[File:c3fire-doc-agile-organization-role-view.png|border|Person Move Control]]

== Unit configuration ==

The unit configuration contain four panels.
* Unit selector: What unit to edit
* Unit editor: The editor panel
* Property viewer: View all properties for the unit.
* XML viewer: View the xml configuration for the unit.

More about the unit configuration at '''[[Config/Config_Unit#Unit|Unit Configuration]]'''.

[[File:c3fire-do-agile-organization-unit-main.png|800px|border|Person Move Control]]

;Unit Selector
:Select what unit to edit.
[[File:c3fire-do-agile-organization-unit-select-unit.png|border|Person Move Control]]

;Unit editor
Whit the unit editor you can edit.
* What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-do-agile-organization-unit-edit.png|border|Person Move Control]]

;Property xml viewer
:These panels only display the properties for the unit.
[[File:c3fire-do-agile-organization-unit-view.png|border|Person Move Control]]

= Organization change during session =

With these panels the manager are able to change the organization when a session is running.
The organization editor contain three panels.
* Role control unit: What units the roles can control.
* Unit send information to role: What roles the units will send the information that are in it's observation area.
* Role can send mail to role: To what roles the the roles can send mail to and chat with.

[[File:c3fire-do-agile-organization-agile-main.png|800px|border|Person Move Control]]

== Role control unit ==
What units the roles can control.

[[File:c3fire-doc-agile-organization-agile-unit-controlled-by.png|border|Person Move Control]]

== Unit send information to role ==
What roles the selected unit will send the information that are in it's observation area.
[[File:c3fire-doc-agile-organization-agile-unit-send-info-to.png|border|Person Move Control]]

== Role can send mail to role ==
To what roles the the roles can send mail to and chat with.

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to.png|border|Person Move Control]]

[[File:c3fire-doc-agile-organization-agile-role-can-send-mail-to-2.png|border|Person Move Control]]

== Mail Groups ==
It is possible to create mail groups.
This is done in the <MailGroups> configuration element.

More about the mail group configuration at '''[[Config/Config_Mail#Mail_Groups|Mail Group Configuration]]'''.

;Configuration Editor
Members of the mail groups can be defined in the mail groups configuration Editor.

[[File:c3fire-doc-agile-organization-mailgroup-edit.png|border|Mail group editor]]

Doc/People

2022-03-27T22:29:49Z

Patrick Turner: /* Move people during a session */

{{DISPLAYTITLE: Civilian People}}

= Move people during a session =

People can be moved around the map by the session manager or an assigned player (People Controller).

To activate this functionality the manager or player needs to have the "PersonMoveControl" panel visible in their user interface.

This functionality is demonstrated in the demo configuration, '''\Demo\RescuePersons\P1C1-F2R1T1'''

In this demo session the manager and the player PC (People Controller) can move people.

:Located in: C:\C3LearningLabs\C3Fire\Client\SessionDef\Demo\RescuePersons\P1C1-F2R1T1

== Configuration ==
To activate the functionality the manager or player needs to have the "PersonMoveControl" panel visible in their user interface.
This is done by setting the Visible attribute to true, and setting the position of the panel in the user interface configuration.

More information at: UI Main Layout [[Config/UI/Main_Layout#PersonMoveControl|Person Move Control]]

<syntaxhighlight lang="xml">
<Object
Name = "PersonMoveControl"
BorderVisible = "True"
Enabeled = "False"
Pos = "1190,100"
Size = "140,85"
Visible = "True" />
</syntaxhighlight>

The user interface configuration must be in the xxx-UIMain-xxx.coni file.

;Player UI
The Player UI is defined in the xml element:
<syntaxhighlight lang="xml">
<UserInterfaceLayout>
...
<Layout
Name = "Ground Chief" >
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

;Manager UI
The Manager UI is defined in the xml element:
<syntaxhighlight lang="xml">
<ManagerConfig
WindowSize = "1325,945" >

<SessionControlLayout>
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

;Replay UI
The Replay UI is defined in the xml element:
<syntaxhighlight lang="xml">
<ReplayConfig
WindowSize = "1300,996" >

<SimulationMapLayout>
...
<Object
Name = "PersonMoveControl"
</syntaxhighlight>

=== Color configuration ===

== Move people Control Panel ==

[[File:c3fire-config-ui-main-layout-person-move-control.png|border|Person Move Control]]

:The "View People" button is a toggle button that is used to show the number of people at each location on the map.
:The Moving number is the number of people the controller is currently moving.

;Map information
:When the move people control panel is visible all locations with people will be indicated by a blue border.
:When the manager or player presses the "View People" button, the map shows the number of people at each position.

{|
|[[File:c3fire-doc-people-map-normal.png|border|map normal]]
|         
|[[File:c3fire-doc-people-map-border.png|border|map border]]
|         
|[[File:c3fire-doc-people-map-number.png|border|map numberl]]
|-
|style="text-align: center;" |
Normal
|
|style="text-align: center;" |
Location visible
|
|style="text-align: center;" |
Amount visible
|}

== Move People ==

;Move
When the number of people at a location is visible, the manager or player can drag those people with the mouse. 
#Point the mouse pointer at a location with people.
#Press the left mouse button and keep it pressed.
#Move the mouse pointer to the desired location.
#Release the left mouse button
[[File:c3fire-doc-people-map-move-start.png||border|map border]]

;Specify the number of people to move
The manager or player can select the number of people to move. 
This is done by pressing a number key whilst dragging the mouse. 
Possible keys are <0> to <9>

#Point the mouse pointer to a location with people.
#Press the left mouse button and keep it pressed.
#Press key <0> to <9> on the keyboard.
#Move the mouse pointer to the desired location.
#Release the left mouse button.

[[File:c3fire-doc-people-map-move-end.png||border|map numberl]]