C3Fire Organisation Documentation

From C3LearningLabs

Organisation

The emergency organisation in C3Fire can be set up as wanted depending on the training or research goals. The user interfaces and communication tools can be individual set-up for all participants in a training session. In a typical setting the environment can be set up to have a four layer organisation which can be seen as a typical hierarchical emergency organisation. The layers are the emergency alarm center, the command and control staff, the fire-fighting unit chiefs and the ground units.

The persons who run the system are located in the staff and fire-fighting unit chiefs' levels see figure 1.


C3Fire Organisation

Figure 1. Organization example.

The example organisation viewed in figure 1 can be described as:

Emergency Alarm Centre

The top layer is a computer-controlled actor that can be viewed as an emergency alarm centre. It can send text messages to the staff. The goal of the alarm centre is to let the staff acquire information from a position higher up in the emergency hierarchy. The alarm centre can be viewed as a task assignor.

Staff

The staff works strategically on a higher-order time scale by trying to understand the current situation and predict future critical situations. Their assignment is to command and control the fire-fighting organisation. This means that they should collect information from the fire-fighting unit chiefs so that they acquire an awareness of the situation. On this basis they plan and transmit orders to the fire-fighting unit chiefs in order to direct and co-ordinate actions in the organisation. The staff functions as decision maker only and does not operate directly on the system.

Fire-fighting Unit chiefs

The fire-fighting unit chiefs control the ground units, the fire-fighting units, the reconnaissance persons etc. The main responsibility of the fire-fighting unit chiefs is to follow the commands from the staff and extinguish fire. They are also responsible for informing the staff on what they see, do and plan to do. At all times a users see different parts of the map, depending on where the ground units that they are controlling are.

Ground Units

The fire-fighting units can move around in the environment and extinguish fire. The fire-fighting unit position and the fire status around the unit are displayed on the fire-fighting unit chief's map, see figure. The fire-fighting units are controlled by mouse commands on the controllers map.

External Actors

The external actors are computer-simulated and scenario-controlled actors outside the hierarchical organisation. They represent persons such as civilians or other organisations and can send text messages to the staff or fire-fighting unit chiefs.


Organization Configuration


The organisation is mainly defined by configuration of the human players and the communication structures. The organisation can be freely configuration from one to some thing around sixteen human players depending on the speed of the used computer systems. Example on organisation can be a hierarchic or a flat (net work based) organisation, see figure 2 and 3.

Hierarchic organisation          Flat organisation

Figure 2. Hierarchic organization.

Figure 3. Flat (net work based) organization.


Player Tasks

It exist different types of tasks in the C3Fire environment. Example of main roles that a player can have are:

Person-gray-f9-30x30.png

Chief

Person-graylight-f9-30x30.png

Information manager

UAV operator / Information management

Person-red-f9-30x30.png

Solving Task Type A

Fighting Fire

Person-green-f9-30x30.png

Solving Task Type B

Rescue People

Person-brown-f9-30x30.png

Solving Task Type C

Making Fire Breaks

Person-blue-f9-30x30.png

Support Type A

Water Logistics

Person-yellow-f9-30x30.png

Support Type B

Fuel Logistics

Person-graylight-f9-30x30.png

Support Type C

Find people to rescue


A player can have more than one role, and be configured to be able to do more than one task.

Person-gray-red-f9-30x30.png

Chief + Task A

Chief / UAV + Fighting Fire

Person-red-green-30x30.png

Task A + Task B

Fighting Fire + Rescue People

Person-red-brown-30x30.png

Task A + Task C

Fighting Fire + Fire Break

Person-blue-yellow-30x30.png

Support Type A + Support Type B

Water Logistics + Fuel Logistics

Person-red-blue-f9-30x30.png

Task A + Support Type A

Fighting Fire + Water Logistics

Person-brown-blue-30x30.png

Task C + Support Type A

Fire Break + Water Logistics

Person-red-yellow-f9-30x30.png

Task A + Support Type B

Fighting Fire + Fuel Logistics

Person-red-yellow-blue-30x30.png

Solving Task Type A + Support Type A + B

Fighting Fire + Water Logistics + Fuel Logistics

Person-red-blue-green-f9-30x30.png

Solving Task Type A and B + Support Type A

Fighting Fire + Rescue People + Water Logistics

Person-gray-red-blue-green-f9-30x30.png

Chief + Solving Task Type A and B + Support Type A

Chief / UAV + Fighting Fire + Rescue People + Water Logistics

Person-red-green-brown-blue-30x30.png

Solving Task Type A, B, C + Support Type A

Fighting Fire + Rescue People + Fire Break + Water Logistics



Organisation Examples

Examples on organisations.

1-2 Players

Examples on organisations with one and two players.

1Player
1Task


Task A

1Player
Info
1Task

Info, Task A

2Players
1Task


Task A, Task A

2Players
2Task


Task A, Task B




3 Players

Examples on organisations with three players.

3Players
1Task


Task A, Task A, Task A

3Players
Chief Info
1Task

Chief / Info, Task A, Task A

3Players
Dual Role
Chief Info
1Task 2Support

Chief, Task A, Task A, Support

3Players
AllDoAll
2Task 1Support

Chief / Info, Task A, Task A

3Players
1Task
Support

Task A, Task A, Task A

3Players
Chief 1Task
Support

Chief / Info, Task A, Task A

3Players
1Task
Info UAV

Chief / Info, Task A, Task A

3Players
2Task
Info UAV

Chief / Info, Task A, Task A




4 Players

Examples on organisations with four players.

4Players
1Task


Task A, Task A, Task A

4Players
1Task
Info UAV
Support

Chief / Info, Task A, Task A

4Players
Dual Role
Info UAV
1Task 2Support

Chief, Task A, Task A, Support

4Players
AllDoAll
2Task 1Support

AllDoAll 2Task 1Support

4Players
AllDoAll
1Task 2Support

AllDoAll 1Task 2Support

4Players
Chief
1Task

Task A, Task A, Task A

4Players
Chief
1Task
Support

Chief / Info, Task A, Task A

4Players
Chief
2Task

Chief / Info, Task A, Task A

4Players
Chief
2Task
Support

Chief / Info, Task A, Task A

4Players
Dual Role
Chief Info
1Task 2Support

Task A, Task A, Task A





5 Players

Examples on organisations with five players.

5Players
Chief
1Task
1Support

Task A, Task A, Task A

5Players
Chief
2Task
1Support

Chief / Info, Task A, Task A

5Players
Dual Role
Chief
3Task 1Support

Chief, Task A, Task A, Support

5Players
Staff
Chief Info UAV
2Task 1Support

Chief / Info, Task A, Task A

5Players
Chief
Info UAV
1Task 1Support

Task A, Task A, Task A

5Players
Info UAV
1Task
1Support

Chief / Info, Task A, Task A

5Players
Info UAV
2Task
1Support

Chief / Info, Task A, Task A

5Players
Dual Task
Info UAV
3Task 1Support

Chief / Info, Task A, Task A




6+ Players

Examples on large organisations.

6Players
Staff
Chief Info
1Task

Task A, Task A, Task A

8Players
Staff AllDoAll
Chief Info UAV
3Task1Support

Chief / Info, Task A, Task A

8Players
AllDoAll
Two Teams
1Task 2Support

Chief, Task A, Task A, Support


10Players
Chief
3Task
1Support

Chief / Info, Task A, Task A



Project Examples

6Players
Staff
Chief Info
1Task

Task A, Task A, Task A

8Players
Staff AllDoAll
Chief Info UAV
3Task1Support

Chief / Info, Task A, Task A

8Players
AllDoAll
Two Teams
1Task 2Support

Chief, Task A, Task A, Support


10Players
Chief
3Task
1Support

Chief / Info, Task A, Task A

2017 Colaboration monitioring of Swedish Canadians Teams

Player Definitions

A player is mainly defined by a name, what simulated units the player controls, the mail and diary tools that the player can use, and a user interface layout.

The name is used as an identification name in the communication and information tools. The player's user interface can be configured by selecting the tools that should be visible. Read more about the user interface at Player UI Configuration.

More about the configuration of the players can be read at Roles configuration in the session configuration.

Communication

The communication possibilities between the players are defined by the configuration of the mail, chat, diary, and distributed map tools. The session manager configure the communication channels for all the players, defining who can communicate with who and what information tool they can use.

The mail tool is a small mail and chat system that is used to send mail between the players during the session. The diary is a distributed tool that makes it possible to write diary notes in a shared diary base. With the distributed map the players map tools can be configured so that the players share a map view. This means that the map tool show the same map for the connected players. Read more about the user interface at Player UI Configuration.

Mail

Chat

Diary

Map



Resources

The following Libre Office files was used when creating the organisation images.