|
|
| Line 1: |
Line 1: |
| − | {{DISPLAYTITLE: Changing teamwork tasks in international mission collaboration - Tasks and workload}}
| |
| | | | |
| − |
| |
| − | {| class="wikitable" style="width: 75%; background-color: white;"
| |
| − | | style="background-color: #eeeeee; width: 125px;" |'''Year'''
| |
| − | |2017
| |
| − | |-
| |
| − | | style="background-color: #eeeeee; " |'''Project Name'''
| |
| − | |SweCan-Teams Pilot 1
| |
| − | |-
| |
| − | | style="background-color: #eeeeee; " |'''Project'''
| |
| − | |Pilot study to test team role changes in international mission oriented tasks.
| |
| − | |-
| |
| − | | style="background-color: #eeeeee;" |'''Acronym'''
| |
| − | |SweCanTeam1
| |
| − | |-
| |
| − | | style="background-color: #eeeeee;" |'''Organisation'''
| |
| − | |RISE SICS East, Linköping University, Laval University, Saab
| |
| − | |-
| |
| − | | style="background-color: #eeeeee;" |'''Country'''
| |
| − | |Sweden, Canada
| |
| − | |-
| |
| − | | style="background-color: #eeeeee;" |'''Contact Person'''
| |
| − | |[mailto:Rego.Granlund@C3Fire.org Rego.Granlund@C3Fire.org]
| |
| − | |-
| |
| − |
| |
| − | | style="background-color: #eeeeee;" |'''Project Members'''
| |
| − | |Rego Granlund, Jens Alfresson, Sebastien Tremblay, Isabelle Turcotte, Björn Johansson, Peter Bergström, Oscar Bjurling and Jacob Weilandt <br>
| |
| − | '''Experiment Design:''' Rego Granlund, Oscar Bjurling and Jacob Weilandt. <br>
| |
| − | '''Experiment Leaders:''' Jacob Weilandt and Oscar Bjurling<br>
| |
| − | '''Thesis advisors:''' Björn Johansson and Peter Bergström
| |
| − | |-
| |
| − | | style="background-color: #eeeeee;" |'''System'''
| |
| − | |C3Fire
| |
| − | |-
| |
| − | | style="background-color: #eeeeee;" |'''Founders'''
| |
| − | |NFFP7 VINNOVA, Sweden.<br>
| |
| − | |-
| |
| − | | style="background-color: #eeeeee;" |
| |
| − | |
| |
| − | |}
| |
| − |
| |
| − |
| |
| − | = Project =
| |
| − |
| |
| − | This project is performed in collaboration between research groups in Sweden and Canada. In Swenden the works is performed by RISE, Saab and Linköping university. In Canada the work is performed by Laval university. The long time goal is to study collaboration in international teams when the team role structure changes during mission or between missions.
| |
| − |
| |
| − | In this specific experiment series we studied:<br>
| |
| − | 1) how the workload in a team was related to the team members individual workload.<br>
| |
| − | 2) the possibility to detect if any individual team role had a greater impact on team performance than the other roles.
| |
| − |
| |
| − |
| |
| − | == Experiment modules ==
| |
| − |
| |
| − |
| |
| − | {{Multicol}}
| |
| − |
| |
| − | {| class="wikitable" style="background-color: white;"
| |
| − | !colspan="2"|'''Tasks'''
| |
| − | |-
| |
| − | |style="width: 150px;"|Forest Fire
| |
| − | |Yes
| |
| − | |-
| |
| − | |Search and Rescue
| |
| − | |Yes
| |
| − | |}
| |
| − |
| |
| − | {{Multicol-break}}
| |
| − |
| |
| − | {| class="wikitable" style="background-color: white;"
| |
| − | !colspan="2"|'''Resources'''
| |
| − | |-
| |
| − | |style="width: 150px;"|Fire Fighters
| |
| − | |Yes
| |
| − | |-
| |
| − | |Fuel Logistic
| |
| − | |No
| |
| − | |-
| |
| − | |Water Logistic
| |
| − | |Yes
| |
| − | |-
| |
| − | |FireBreak
| |
| − | |No
| |
| − | |-
| |
| − | |UAV / Drone
| |
| − | |Yes
| |
| − | |-
| |
| − | |People Transportation
| |
| − | |Yes
| |
| − | |}
| |
| − |
| |
| − | {{Multicol-break}}
| |
| − |
| |
| − | {| class="wikitable" style="background-color: white;"
| |
| − | !colspan="2"|'''Communication Tools'''
| |
| − | |-
| |
| − | |style="width: 150px;"|Mail
| |
| − | |Yes
| |
| − | |-
| |
| − | |Chat
| |
| − | |No
| |
| − | |-
| |
| − | |Diary
| |
| − | |No
| |
| − | |-
| |
| − | |Chared Map
| |
| − | |No
| |
| − | |-
| |
| − | | Map Symbols
| |
| − | |No
| |
| − | |-
| |
| − | |Voice
| |
| − | |No
| |
| − | |}
| |
| − |
| |
| − | {{Multicol-break}}
| |
| − |
| |
| − | {| class="wikitable" style="background-color: white;"
| |
| − | !colspan="2"|'''Decision Suport'''
| |
| − | |-
| |
| − | |style="width: 150px;"|Prediction
| |
| − | |No
| |
| − | |}
| |
| − |
| |
| − | {{Multicol-end}}
| |
| − |
| |
| − | = Method =
| |
| − |
| |
| − | == Scenario ==
| |
| − |
| |
| − | The first two scenarios were training scenarios designed to give the participants time to
| |
| − | familiarize themselves with their respective roles. The first training scenario was a simple
| |
| − | scenario with only one active fire and a slow ignite time. Its purpose was to allow the
| |
| − | participants to get a handle on the basics of how each of their role functioned, how the map
| |
| − | functioned, how movement functioned and how to communicate. The second training
| |
| − | scenario was designed to be more hectic and utilized a slow ignite time but starts with three
| |
| − | fires simultaneously. This scenario was meant to introduce the participants to the task of
| |
| − | fighting several fires at once and further show the participants the importance of having a
| |
| − | functioning supply chain and communication as well as division of labour.
| |
| − | 17
| |
| − | The three experiment scenarios were all similar in function and game length, each scenario
| |
| − | lasting for 15 minutes. The scenarios only differed in ignite time and map rotation. Each
| |
| − | scenario was structured to have three fires ignite during the play time, with each fire starting
| |
| − | at a different time. One fire started immediately as the scenario was started, the second fire
| |
| − | started four minutes after that and the third fire starting another three minutes after that. As
| |
| − | the map was rotated in each scenario the fires spawned at different coordinates for each
| |
| − | scenario.
| |
| − |
| |
| − |
| |
| − | The independent variable used in this study was the ignite time configuration in C3Fire. The
| |
| − | ignite time setting dictates how long it takes for any cell adjacent to a fire cell to burst into
| |
| − | flame. It is one of the primary settings that define how quickly fire spreads, and thus the level
| |
| − | of difficulty. The ignite times used in this study were 60, 80, and 100 time units, where 60 is
| |
| − | the shortest ignite time which would make this the most difficult setting since the fire would
| |
| − | spread more quickly. These ignite times were configured in three separate scenarios; D3-100,
| |
| − | D1-80, and D2-60, representing the 100, 80, and 60 ignite time settings, respectively. The
| |
| − | simulated world was partially hidden from view on the interface maps. Static objects like trees,
| |
| − | houses, and pumps were always visible to participants, but certain objects—like civilians, fires,
| |
| − | or even the units of other participants—were invisible on the map until they were within the
| |
| − | line of sight of any unit. These objects would then be visible to the participant controlling the
| |
| − | unit that spotted the object.
| |
| − | Five scenarios were used in total; two for training, and three for data collection. Each training
| |
| − | scenario ran for 10 minutes and each data collection scenario ran for 15 minutes.
| |
| − | The first training scenario was intended to teach participants on the basics of maneuvering their
| |
| − | units and understanding the interface. Only one fire was present in this scenario so participants
| |
| − | could train in fighting it.
| |
| − |
| |
| − | The second training scenario was noticeably more difficult than the first. Three fires started
| |
| − | simultaneously, making this training scenario a “baptism by fire”, if you will. This challenge
| |
| − | further highlighted the concept and importance of teamwork.
| |
| − | The three data scenarios shared the same map but were rotated 90º in different directions to
| |
| − | give the illusion of a new setting. The only things that differed between them were the locations
| |
| − | of where fires would start and, more importantly, the ignite time configuration. There were
| |
| − | three fires in each scenario, one of which always began immediately at the start of each scenario.
| |
| − | Participants received an automated email message from the system telling them the location of
| |
| − | this initial fire. Fires two and three, however, were not advertised, leaving teams with the
| |
| − | responsibility of finding them. Fire number two began four minutes into each scenario, and the
| |
| − | third and final fire began after 10 minutes had passed in total and only five minutes remained.
| |
| − | This left teams with the prospect of possibly fighting one fire for four minutes, two fires for six
| |
| − | minutes, and three fires for a maximum of five minutes.
| |
| − |
| |
| − | To control for any learning effects, groups of teams encountered the three scenarios in different
| |
| − | order. This order was in a sense semi-determined – it was decided beforehand that the twelve
| |
| − | teams were to be divided into three groups of teams where each group encountered a different
| |
| − | scenario order. The idea being that no group of four teams were to play the same scenario in
| |
| − | any given order. It was decided upon the arrival of the first team in each block which order
| |
| − | should be implemented to make this work. The same scenario order was then used for the three
| |
| − | subsequent teams in that block. The first block of four teams began by playing the medium
| |
| − | scenario (D1-80), followed by the difficult scenario (D2-60), and lastly the easy scenario (D3-
| |
| − | 100). The second block of four teams played the difficult scenario first, then the easy scenario,
| |
| − | and finished by playing the medium scenario. The third and final block of teams first played
| |
| − | the easy scenario, then the medium scenario, and finally the difficult scenario.
| |
| − |
| |
| − |
| |
| − |
| |
| − | == Map ==
| |
| − |
| |
| − | [[File:2017-SweCanTeam-1-Map-1.png|none|IMap]]
| |
| − |
| |
| − | === Objects ===
| |
| − | The scenario contain the following map objects.
| |
| − | {| class="wikitable"
| |
| − | |+Objects on map
| |
| − | |-
| |
| − | |
| |
| − | |
| |
| − | |Fire<br>Spread<br>Delay
| |
| − | |
| |
| − | |-
| |
| − | |
| |
| − | |Normal
| |
| − | |1
| |
| − | |Normal
| |
| − | |-
| |
| − | |[[File:C3fire-pic-object-birch.gif|Birch]]
| |
| − | |Birch
| |
| − | |2
| |
| − | |Slow
| |
| − | |-
| |
| − | |[[File:C3fire-pic-object-pine.gif|Pine]]
| |
| − | |Pine
| |
| − | |0.5
| |
| − | |Fast
| |
| − | |-
| |
| − | |style="padding-bottom: 1px; vertical-align: text-top;" |
| |
| − | [[File:C3fire-pic-object-fuelpump.gif|Fuel]]
| |
| − | |Fuel
| |
| − | |-
| |
| − | |style="padding-bottom: 1px; vertical-align: text-top;" |
| |
| − | [[File:C3fire-pic-object-waterpump.gif|Water]]
| |
| − | |Water
| |
| − | |-
| |
| − | |[[File:C3fire-pic-object-house.gif|House]]
| |
| − | |House
| |
| − | |-
| |
| − | |[[File:C3fire-pic-object-tent.gif|Tent]]
| |
| − | |Tent
| |
| − | |-
| |
| − | |[[File:C3fire-pic-object-people.gif|People]]
| |
| − | |People
| |
| − | |-
| |
| − | |[[File:C3fire-pic-object-medicaltransitpoint.gif|Medical Transit Point]]
| |
| − | |Medical Transit Point
| |
| − | |}
| |
| − | {| class="wikitable"
| |
| − | |[[File:c3fire-pic-object-biglandingarea.gif|Big landing area]]
| |
| − | |Big landing area
| |
| − | |}
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Units ===
| |
| − |
| |
| − |
| |
| − | {| class="wikitable"
| |
| − | |[[File:c3fire-pic-number-red-1.gif|Fire Fighting]] [[File:c3fire-pic-number-red-2.gif|Fire Fighting]] [[File:c3fire-pic-number-red-3.gif|Fire Fighting]] [[File:c3fire-pic-number-red-4.gif|Fire Fighting]] [[File:c3fire-pic-number-red-5.gif|Fire Fighting]] [[File:c3fire-pic-number-red-6.gif|Fire Fighting]] [[File:c3fire-pic-number-red-7.gif|Fire Fighting]] [[File:c3fire-pic-number-red-8.gif|Fire Fighting]] [[File:c3fire-pic-number-red-9.gif|Fire Fighting]]
| |
| − | |Fire Fighting Units
| |
| − | |-
| |
| − | |[[File:c3fire-pic-number-blue-10.gif|Logistic]] [[File:c3fire-pic-number-blue-11.gif|Logistic]] [[File:c3fire-pic-number-blue-12.gif|Logistic]]
| |
| − | |Logistic Units
| |
| − | |-
| |
| − | |[[File:c3fire-pic-number-green-13.gif|Search and Rescue]] [[File:c3fire-pic-number-green-14.gif|Search and Rescue]]
| |
| − | |Search and Rescue Units
| |
| − | |-
| |
| − | |[[File:c3fire-pic-number-gray-15.gif|Drone]]
| |
| − | |Drone / UAV
| |
| − | |}
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Maps ===
| |
| − | The experiment did use four maps.
| |
| − |
| |
| − | {|
| |
| − | |[[File:2017-SweCanTeam-1-Map-1.png|200px|none|IMap 1]]
| |
| − | |
| |
| − | |[[File:2017-SweCanTeam-1-Map-2-RL.png|200px|none|Map 2]]
| |
| − | |
| |
| − | |[[File:2017-SweCanTeam-1-Map-3-FVRR.png|200px|none|Map 3]]
| |
| − | |
| |
| − | |[[File:2017-SweCanTeam-1-Map-4-RR.png|200px|none|Map 4]]
| |
| − | |-
| |
| − | |style="text-align: center;" |
| |
| − | Map 1<br>
| |
| − | Orginal<br>
| |
| − | CanSwe1-C1-F80.con
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Map 2<br>
| |
| − | Rotate Left<br>
| |
| − | CanSwe1-C2-F60.con
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Map 3<br>
| |
| − | Flip Vertical<br>
| |
| − | Rotate Right<br>
| |
| − | CanSwe1-C3-F100.con
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Map 4<br>
| |
| − | Rotate Right<br>
| |
| − | Not Used
| |
| − | |}
| |
| − |
| |
| − |
| |
| − |
| |
| − | === People ===
| |
| − | The task for the search and rescue chef is to evacuate people if needed.<br>
| |
| − | The area contain the following people that may need to evacuate. <br>
| |
| − |
| |
| − | {|
| |
| − | |[[File:2017-SweCanTeam-1-Map-1-People.png|200px|none|IMap 1]]
| |
| − | |
| |
| − | |[[File:2017-SweCanTeam-1-Map-2-RL-People.png|200px|none|Map 2]]
| |
| − | |
| |
| − | |[[File:2017-SweCanTeam-1-Map-3-FVRR-People.png|200px|none|Map 3]]
| |
| − | |
| |
| − | |[[File:2017-SweCanTeam-1-Map-4-RR-People.png|200px|none|Map 4]]
| |
| − | |-
| |
| − | |style="text-align: center;" |
| |
| − | Map 1
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Map 2
| |
| − |
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Map 3
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Map 4
| |
| − | |}
| |
| − |
| |
| − |
| |
| − |
| |
| − | = Organisation =
| |
| − |
| |
| − | [[File:2017-SweCanTeam-1-Organisation.png|Organisation]]
| |
| − |
| |
| − | == Roles ==
| |
| − |
| |
| − | === Information Chief ===
| |
| − |
| |
| − | This role’s main objective is to provide the other roles with extended information about the state of the environment.
| |
| − |
| |
| − | The Information Chief had access to a Drone / UAV (Unmanned Aerial Vehicle) unit that could scout the map to look for fires, houses, or civilians.
| |
| − | The UAV is faster compared to its ground unit counterparts and can therefore cover the area faster.
| |
| − | The UAV can also see a larger view, 5x5 squares, as opposed to the 3x3 square for all other units in the system.
| |
| − | The UAV has several options for patrolling and can engage in different patrol patterns,
| |
| − | such as circling a certain location and moving between different points.
| |
| − | In this way, the Information Chief had the option of instructing the UAV to patrol certain areas autonomously and instead focus his or her efforts on
| |
| − | instructing the other team members through the mail system.
| |
| − |
| |
| − | For the Information Chief there is a choice between providing support to current events or scouting for new events.
| |
| − | The Information Chief is not dependent on any resource and therefore isn’t as dependent on the Logistics Chief as the other roles.
| |
| − |
| |
| − | The Information Chief could also tag individual squares on the map with icons for fire, houses, civilians, etc., to alert the other
| |
| − | team members of events outside their own line of sight.
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Fire Chief ===
| |
| − |
| |
| − | The objective for the Fire Chief is to putting out the forest fire.
| |
| − |
| |
| − | The Fire Chief commands five fire fighting units and had the main responsibility of putt out fires. The Fire Chief can also command Logistics Chief and the Search and Rescue Chief to use the extra four fire fighting units.
| |
| − |
| |
| − | The fire fighting units needed to be provided with water to function efficiently but had an unlimited amount of fuel.
| |
| − | Therefore the Fire Chief needs to communicate with the Logistics Chief to ensure that there is a supply of water ready.
| |
| − | The fire fighting units are highly dependent on the efforts of the logistics chief to get water.
| |
| − | However, the Fire Chief could choose to refill the fire fighting units with water at certain water pumps scattered across the map.
| |
| − |
| |
| − | When a fire is located the Fire Chief must relocate an appropriate amount of firefighter units to the fire.
| |
| − | The Fire Chief must also keep in mind that fires can spread and start in several locations at once, so the Fire Chief
| |
| − | must be strategic with the use of the available firefighter units.
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Logistics Chief ===
| |
| − | The main objective for the Logistics Chief is to distribute water to the fire fighting units and fuel to the Search and rescue units.
| |
| − | The Logistics Chief also have two support fire fighting units that can be used under command from the Fire Chief.
| |
| − |
| |
| − | The logistics chief have three water and fuel trucks, two of which carried only water, the third one transported both water and fuel.
| |
| − | A logistics unit can only hold a limited amount of water, so as the logistic trucks support the other units the Logistics Chief must keep track of the amount of water available in each truck. Therefore, the Logistics Chief must plan and strategize the use of logistic units as to ensure no fire truck depletes its water supply. If a logistics unit completely runs out of water the unit must move to a water station to resupply.
| |
| − | The logistics unit that can supply fuel have an unlimited fuel tank that does not require refilling.
| |
| − | The Logistics Chief can see the position of the water and fuel pumps on the map.
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Search and Rescue Chief ===
| |
| − | The main objective of this role is to find and rescue civilians that are spread out around the
| |
| − | map. The Search and Rescue Chief also have two support fire fighting units that can be used under command from the Fire Chief.
| |
| − |
| |
| − | These individuals that may need to be rescued can be positioned in the woods, in houses or at camp-sites.
| |
| − | The Search and Rescue Chief have two rescue units that could carry four civilians at a time. The rescued individuals needs to be transported to a hospital before the Search and Rescue Chief can attempting to rescue more individuals.
| |
| − |
| |
| − | The rescue vehicles needed fuel to move around, and could fill up with fuel at a fuel pump or by the logistic fuel unit commanded
| |
| − | by the Logistic Chief.
| |
| − | While the rescue unit could locate stranded civilians on their own,
| |
| − | their short viewing distance meant that the Search and Rescue Chief benefited substantially from the efficient information flow provided by the Information Chief.
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Screen Pictures ===
| |
| − |
| |
| − | ==== Manager ====
| |
| − |
| |
| − | [[File:2017-SweCanTeam-1-gui-Manager.png|900px|Manager]]
| |
| − | <br>
| |
| − | <br>
| |
| − |
| |
| − | ==== Chief ====
| |
| − |
| |
| − | [[File:2017-SweCanTeam-1-gui-Chief.png|900px|Manager]]
| |
| − | <br>
| |
| − | <br>
| |
| − | [[File:v4-gui-uav-control.png|Uav]]
| |
| − | <br>
| |
| − | <br>
| |
| − |
| |
| − | ==== Fire Fighter ====
| |
| − |
| |
| − | [[File:2017-SweCanTeam-1-gui-Fire.png|900px|Manager]]
| |
| − | <br>
| |
| − | <br>
| |
| − |
| |
| − | ==== Logistics ====
| |
| − |
| |
| − | [[File:2017-SweCanTeam-1-gui-Logistics.png|900px|Manager]]
| |
| − | <br>
| |
| − | <br>
| |
| − |
| |
| − | ==== Rescue ====
| |
| − |
| |
| − | [[File:2017-SweCanTeam-1-gui-Rescue.png|900px|Manager]]
| |
| − | <br>
| |
| − | <br>
| |
| − | [[File:v4-gui-resacue-control.png|Rescue]]
| |
| − | <br>
| |
| − | <br>
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Photos ===
| |
| − |
| |
| − |
| |
| − |
| |
| − | = Files =
| |
| − | == Experiment ==
| |
| − | {| class="wikitable"
| |
| − | |Player Instructions
| |
| − | |
| |
| − |
| |
| − | |-
| |
| − | |Configurations
| |
| − | |
| |
| − |
| |
| − | |-
| |
| − | |Video Recordings
| |
| − | |
| |
| − |
| |
| − | |-
| |
| − | |Logfiles
| |
| − | |
| |
| − |
| |
| − | |}
| |
| − |
| |
| − |
| |
| − | Forest Fire
| |
| − | Water Logistic
| |
| − | Fuel Logistic
| |
| − | FireBreak
| |
| − | People
| |
| − | UAV
| |
| − | Map Symbols
| |
| − | Prediction
| |
| − |
| |
| − |
| |
| − | == End State ==
| |
| − | End state in the last session for the groups.
| |
| − |
| |
| − | {|
| |
| − | |'''Slow fire'''
| |
| − | |
| |
| − | |[[File:G01-S3-C2-Log61-End.png|none|200px|G01-S3-C2]]
| |
| − | |
| |
| − | |[[File:G02-S3-C2-Log67-End.png|none|200px|Ignit time 2]]
| |
| − | |
| |
| − | |[[File:G03-S3-C2-Log73-End.png|none|200px|Ignit time 3]]
| |
| − | |
| |
| − | |[[File:G04-S3-C2-Log78-End.png|none|200px|Ignit time 3]]
| |
| − | |-
| |
| − | |style="text-align: center;" |
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 1
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 2
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 3
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 4
| |
| − | |-
| |
| − | |'''Normal fire'''
| |
| − | |
| |
| − | |[[File:G05-S3-C1-Log83-End.png|none|200px|G01-S3-C2]]
| |
| − | |
| |
| − | |[[File:G06-S3-C1-Log89-End.png|none|200px|Ignit time 2]]
| |
| − | |
| |
| − | |[[File:G07-S3-C1-Log94-End.png|none|200px|Ignit time 3]]
| |
| − | |
| |
| − | |[[File:G08-S3-C1-Log99-End.png|none|200px|Ignit time 3]]
| |
| − | |-
| |
| − | |style="text-align: center;" |
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 5
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 6
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 7
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 8
| |
| − | |-
| |
| − | |'''Fast fire'''
| |
| − | |
| |
| − | |[[File:G09-S3-C3-Log104-End.png|none|200px|G01-S3-C2]]
| |
| − | |
| |
| − | |[[File:G10-S3-C3-Log109-End.png|none|200px|Ignit time 2]]
| |
| − | |
| |
| − | |[[File:G11-S3-C3-Log114-End.png|none|200px|Ignit time 3]]
| |
| − | |
| |
| − | |[[File:G12-S3-C3-Log119-End.png|none|200px|Ignit time 3]]
| |
| − | |-
| |
| − | |style="text-align: center;" |
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 9
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 10
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 11
| |
| − | |
| |
| − | |style="text-align: center;" |
| |
| − | Group 12
| |
| − | |}
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Art work===
| |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | |Organisation
| |
| − | |
| |
| − | |-
| |
| − | |Icones
| |
| − | |
| |
| − | |-
| |
| − | |Pictures
| |
| − | |
| |
| − | |}
| |
| − |
| |
| − |
| |
| − |
| |
| − | = Analysis =
| |
| − |
| |
| − |
| |
| − |
| |
| − | = Publications =
| |
| − |
| |
| − | (Bjurling 2017) '''Most valuable player? - Assessing the impact of individual team role activity on team performance in a microworld environment'''<br>
| |
| − | <br>
| |
| − | Artur : Oscar Bjurling <br>
| |
| − | Type : Bachelor thesis, Linköping University, Sweden. <br>
| |
| − | The full thesis can be downloaded at: http://liu.diva-portal.org/smash/get/diva2:1111835/FULLTEXT01.pdf<br>
| |
| − | <br>
| |
| − | '''Abstract''' <br>
| |
| − | Studying team performance dynamics in tasks and activities has proven difficult because of the dynamic and unpredictable nature of the real world. Microworld systems aim to address that issue by providing researchers with controllable simulated environments that captures the essence of their real-world counterpart activities. This study utilized one such microworld system, called C3Fire, to simulate a forest firefighting setting where 48 participants divided into 12 teams were tasked with cooperating in extinguishing the fires. Teams consisted of four roles – each with its different responsibilities and resources. The aim of this study was to determine whether any individual team role had a greater impact on team performance than the other roles. Each team encountered three distinct scenarios of varying difficulty. Command input action counts and self-assessed performance scores were collected for each participant. These measurements were tested for correlations with team scores. The logistics chief role, who was responsible for re-filling and re-fueling other units, stood out as being the only role whose command input count correlated with team score, and being one of only two roles for which command inputs and self-assessed performance scores were correlated, as well. Results of a multiple regression procedure also indicated that the command counts of the logistics chief was a significant predictor of team score.
| |
| − |
| |
| − |
| |
| − | (Weilandt 2017)''' Individual Workload’s Relation to Team Workload - An investigation'''<br>
| |
| − | <br>
| |
| − | Artur : Jacob Weilandt <br>
| |
| − | Type : Bachelor thesis, Linköping University, Sweden. <br>
| |
| − | The full thesis can be downloaded at: http://liu.diva-portal.org/smash/get/diva2:1111849/FULLTEXT01.pdf<br>
| |
| − | <br>
| |
| − | '''Abstract'''<br>
| |
| − | There is an ongoing debate regarding the construct of team workload and a central point in that debate is team workload’s relation to individual workload. This study set out to investigate this relationship. To assess the participants’ workload a microworld called C3Fire was used to simulate a complex control situation in which teams had to cooperate to complete the task of fighting a forest fire. Twelve teams that consisted of four members in each team were recruited. In the microworld each member of the team took on one out of four separate roles and completed three different scenarios with varying degree of difficulty in C3Fire. After each scenario, a number of questionnaires aimed at gauging different aspects of the teams’ experience in the microworld were administered. The questionnaire in focus of the current study was the DATMA questionnaire, which was used to measure individual workload and team workload. To assert the relationship between the two constructs a multiple linear regression was conducted. The results provided showed that individual workload could be used as a significant predictor for modeling team workload. The study therefore concludes that there is evidence for a relationship in which each team members individual workload could be the parts of the total sum of team workload
| |
