Simulated Hostile Encounter (Atlantis): Difference between revisions

Jump to navigation Jump to search
Added Operations Report
(Added overview & objectives)
(Added Operations Report)
Line 27: Line 27:
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActOne">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActOne">


<!-- Provide Command related content beneath this line. Analysis of outcomes/Analysis of the performance shown on critical tasks/Recommendations.-->
<!-- Provide Command related content beneath this line. Crew Performance Review/Departmental Analysis/Analysis of the performance shown on critical tasks/Recommendations.-->


</div>
</div>


<div class="mw-customtoggle-ActTwo" style="cursor:pointer" >{{SubHeading|Security Report|#29235C}}</div>
<div class="mw-customtoggle-ActFour" style="cursor:pointer" >{{SubHeading|Tactical Report|#29235C}}</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActTwo">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActFour">


<!-- Provide Security related content beneath this line. Analysis of outcomes/Analysis of the performance shown on critical tasks/Recommendations.-->
<!-- Provide Tactical related content beneath this line. Departmental Analysis/Analysis of the performance shown on critical tasks/Recommendations.-->


</div>
</div>
Line 41: Line 41:
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActThree">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActThree">


<!-- Provide Operations related content beneath this line. Analysis of outcomes/Analysis of the performance shown on critical tasks/Recommendations.-->
<!-- Provide Operations related content beneath this line. Departmental Analysis/Analysis of the performance shown on critical tasks/Recommendations.-->
===Analysis===
In the event of Hostile Spacecraft encounters, the defined role of Operations staff is not always immediately obvious. While many of our personnel are cross trained between security or engineering disciplines, perhaps the suddenness of combat situations evolving and changing caused them to become flustered and lose focus, especially amongst the lower ranks. Several new members of the department lacked direction for much of the simulation, which didn’t contribute to overall departmental efficiency. Cross trained personnel help to bolster departments are essential, where and when necessary, so it is important to ensure appropriate training is administered when possible.
 
That said, during situations where the ship has sustained significant damage, the need for dedicated operations staff who are able to take on the role of Damage Control - that is, controlling the effects of damage already sustained throughout the ship, as opposed to repairing it - is of paramount importance. It is through the action of said Damage Control experts that any impairment of the ship, or it’s systems, does not get worse until an engineering team can move in and replace or repair the component/area in question.
 
As a department, Operations did exceptionally well to maintain a high level of efficiency for tasks they were assigned, from ensuring areas of the ship were adequately maintained to shuttlecraft preparation, though their relative successes were not without certain difficulties. For example, there were a number of instances where crew members on the Damage Control teams were forced to a halt when barred by forcefields, or could not erect necessary forcefields. This was, in part, due to power constraints on the ship, but also due to existing security fields that were in place, that many of the lower ranked members of the department lacked the clearance to deactivate. While it is recognised that the security protocols that erect the forcefields are a necessity during a hostile boarding action, in a time critical nature such as this, they not only slowed down the response time, they actually caused a number of additional problems, with crew members actively looking for higher ranked personnel, or security officers in order to deactivate the forcefields in their path, which put a number of them in direct lines of fire between ship personnel and hostile intruders.
 
From a holistic point of view, the tasks afforded to the Operations department were met with vigour and readiness, with only a few small areas needing significant improvement. This is not to say that everything that happened was perfect. Critical Systems were not always fully staffed, the aforementioned directive issues caused serious problems and a chance death reduced the effectiveness of damage control teams in the latter part of the simulation.
 
In summary, while the department operated within reasonable margins of error and to an acceptable degree of success, improvements can and will be made in light of this.
 
===Recommendations===
In response to the points presented above, several recommendations are being put forward in an attempt to maximise operational efficiency while maintaining departmental autonomy and flexibility.
 
The first of which is an immediate mandate for heightened cross training, especially those in Security related disciplines. When a hostile force boards the ship, it is imperative that security responds quickly and efficiently, and as a result, having personnel from other departments come in as additional bodies can sometimes be detrimental. An increase in security drills specifically for these members of the crew would be of great assistance, but also the opportunity to run training sessions with other members of the security department to increase unit cohesion and effectiveness would make a great deal of difference.
 
Secondly, regarding Security’s excessive use of forcefields. It is the opinion of this report that, while effective at slowing the rate of intrusion, there were simply too many forcefields in place, many of which were situated on decks that saw no hostile incursion. A solution to this would present itself in the form of using the internal sensor grid to apply the forcefields to sections, instead of decks, and only on the decks where a hostile presence has been detected. That way, the majority of the crew without higher levels of security clearance can still move around the ship, performing critical tasks without hindrance.
 
Thirdly, a clearly defined manual for the role of operations staff during combat scenarios must be outlined. Having too many bodies in one place makes working extremely difficult, especially in high-pressure environments like Engineering. Only a limited number of Operations personnel should move to Engineering to assist with staffing; likewise with Security. Typically these would be persons that have the highest amount of skill or level of training in those particular areas. The rest should either: Proceed to Lower Decks and man critical system control rooms, alongside any other personnel assigned there, or work on Damage Control teams, co-ordinated by the Bridge, in conjunction with Damage Control on Deck 14.
 
Finally, on the subject of Damage Control, only assigning a single member of staff to the control room was a grave error, and will subsequently be remedied in any successive combat instance. In addition to this, placing a security cross trained member of the department inside, or close to the centre will go a long way to helping keep the area secure, given it’s critical nature to the well being of the ship.
 
With these recommendation, departmental readiness and performance will no doubt see an improvement, hopefully benefiting the continued success of the Atlantis in the Par'tha Expanse.


</div>
</div>


<div class="mw-customtoggle-ActFour" style="cursor:pointer" >{{SubHeading|Tactical Report|#29235C}}</div>
<div class="mw-customtoggle-ActSeven" style="cursor:pointer" >{{SubHeading|Engineering Report|#29235C}}</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActFour">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActSeven">
 
<!-- Provide Security related content beneath this line. Departmental Analysis/Analysis of the performance shown on critical tasks/Recommendations.-->
 
</div>
 
<div class="mw-customtoggle-ActTwo" style="cursor:pointer" >{{SubHeading|Security Report|#29235C}}</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActTwo">


<!-- Provide Tactical related content beneath this line. Analysis of outcomes/Analysis of the performance shown on critical tasks/Recommendations.-->
<!-- Provide Security related content beneath this line. Departmental Analysis/Analysis of the performance shown on critical tasks/Recommendations.-->


</div>
</div>
Line 55: Line 85:
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActFive">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActFive">


<!-- Provide Medical related content beneath this line. Analysis of outcomes/Analysis of the performance shown on critical tasks/Recommendations.-->
<!-- Provide Medical related content beneath this line. Departmental Analysis/Analysis of the performance shown on critical tasks/Recommendations.-->


</div>
</div>
Line 62: Line 92:
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActSix">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-ActSix">


<!-- Provide Marine related content beneath this line. Analysis of outcomes/Analysis of the performance shown on critical tasks/Recommendations.-->
<!-- Provide Marine related content beneath this line. Departmental Analysis/Analysis of the performance shown on critical tasks/Recommendations.-->


</div>
</div>
894

edits

Navigation menu