Sandbox:Command and Communications: Difference between revisions
mNo edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{WIP|assign=William Murdoch}} | {{WIP|assign=William Murdoch}} | ||
During missions and expeditions, group cohesion and management is an essential part of ensuring mission success. Organizational structures and tools used to keep cohesion and accomplish mission goals are called Command and Communications, Command and Control, or simply C2 systems. One such system exists for use by ship command to organize, direct, and track crew members on away missions to avoid chaos. | During missions and expeditions, group cohesion and management is an essential part of ensuring mission success. Organizational structures and tools used to keep cohesion and accomplish mission goals are called Command and Communications, Command and Control, or simply C2 systems. One such system exists for use by ship command to organize, direct, and track crew members on away missions to avoid chaos. | ||
| Line 6: | Line 5: | ||
==Group Position== | ==Group Position== | ||
One of the most important aspects of the C2 system is the relative position of each team member. This is typically tied to | One of the most important aspects of the C2 system is the relative position of each team member. This is typically tied to team cohesion, which itself is vital for proper operations. Periodically, every 2 second, the C2 system will check each member's location within a team. It compares this location to that of the other members, and determines clusters of members and isolated members. Take the following example, where letters A through G represent members of a team. | ||
<pre> | <pre> | ||
| Line 14: | Line 13: | ||
</pre> | </pre> | ||
Members that are close together will form groups. As seen, A, B, C, and D are close enough together to form GROUP1. E and F are close enough to each other to form GROUP2, but far enough from GROUP1 to be considered a separate cluster. Finally, member G is far enough from both GROUP1 and GROUP2, but is alone and therefore an isolate. If, during the next C2 update, GROUP2 had traveled close enough to GROUP1, the groups would merge into a single group. | |||
The primary group is always wherever the Team Leader is located, in this example that is member A. Every other group are called 'detached subgroups'. Members that are alone are called 'isolates'. | |||
Distance is shown in the above examples as the dash marks (-). Those close together show compact dash marks, while those starting to lag behind are seen with spaced out dash marks. This represents relative distance to the group, which is displayed on the program as "Close" or "Extended". Should, in this example, member D continue to the right, they will go from "Extended" to detached from GROUP1 and become an isolate. This allows for oversight of team cohesion. | |||
{{Command}} | |||
Latest revision as of 18:47, 19 July 2026
This section or article is a Work in Progress.
Assigned to: William Murdoch
Please discuss changes with assigned users. If no one is assigned, or if the user is inactive, feel free to complain on the forums or try summoning another staff member.
During missions and expeditions, group cohesion and management is an essential part of ensuring mission success. Organizational structures and tools used to keep cohesion and accomplish mission goals are called Command and Communications, Command and Control, or simply C2 systems. One such system exists for use by ship command to organize, direct, and track crew members on away missions to avoid chaos.
INSERT MECHANICS HERE
Group Position
One of the most important aspects of the C2 system is the relative position of each team member. This is typically tied to team cohesion, which itself is vital for proper operations. Periodically, every 2 second, the C2 system will check each member's location within a team. It compares this location to that of the other members, and determines clusters of members and isolated members. Take the following example, where letters A through G represent members of a team.
[A]---[B]---[C]- - - - [D] [E]--[F] [G]
^----------GROUP1----------^ ^-GROUP2-^ ^-GROUP3-^
(Primary Group) (Detached Subgroup) (Isolate)
Members that are close together will form groups. As seen, A, B, C, and D are close enough together to form GROUP1. E and F are close enough to each other to form GROUP2, but far enough from GROUP1 to be considered a separate cluster. Finally, member G is far enough from both GROUP1 and GROUP2, but is alone and therefore an isolate. If, during the next C2 update, GROUP2 had traveled close enough to GROUP1, the groups would merge into a single group.
The primary group is always wherever the Team Leader is located, in this example that is member A. Every other group are called 'detached subgroups'. Members that are alone are called 'isolates'.
Distance is shown in the above examples as the dash marks (-). Those close together show compact dash marks, while those starting to lag behind are seen with spaced out dash marks. This represents relative distance to the group, which is displayed on the program as "Close" or "Extended". Should, in this example, member D continue to the right, they will go from "Extended" to detached from GROUP1 and become an isolate. This allows for oversight of team cohesion.
Command
| |
| Heads of staff | Captain - Executive Officer - Head of Security - Chief Engineer - Research Director - Chief Medical Officer - Operations Manager |
| Administrative/Other | Corporate Liaison - Consular Officer - Bridge Crewman |
| Useful guides | Guide to Command - Guide to Alert Levels - Corporate Regulations - Guide to Paperwork - Guide to Faxes - Guide to Standard Procedure - Job Accessibility Requirements |