Security Officer Simming Guide: Difference between revisions

From 118Wiki
Jump to navigation Jump to search
Line 6: Line 6:
Pre-Mission duties of the Starfleet Security Officer begins with the mission briefing. This briefing, usually administered by the section chief or the mission commander, is a compilation of the information obtained to date about the mission at hand.  The briefing underlines the parameters of the mission, including key players, expected outcomes, potential complications, venue, and other components of the mission.
Pre-Mission duties of the Starfleet Security Officer begins with the mission briefing. This briefing, usually administered by the section chief or the mission commander, is a compilation of the information obtained to date about the mission at hand.  The briefing underlines the parameters of the mission, including key players, expected outcomes, potential complications, venue, and other components of the mission.
After the briefing, the mission commander or security department head can assign components of the pre-mission planning to members of the security department.  The planning for the mission from the security aspect can be delegated into two components; Risk Assessment and Risk Management.
After the briefing, the mission commander or security department head can assign components of the pre-mission planning to members of the security department.  The planning for the mission from the security aspect can be delegated into two components; Risk Assessment and Risk Management.
'''RISK ASSESSMENT:'''Through the compilation of information about the various aspects of the mission, the security department can determine the associated risks to the away team and the mission. Using the acronym P.E.A.C.E., the assessment can be managed and delegated to reduce the individual workload.
'''Planning:'''  Logistics planning, such as numbers of crew, mission goals, potential outcomes, and other factors.
'''Event:''' Specifics about the mission event(s) complexity and dynamics
'''Asset:''' Selection of appropriate resources. Factors that effect risk including time at unit, familiarity with the operational area, time on scene causing fatigue, crew selection, and management resources.
'''Communications''': Ability to maintain communications throughout the entirety of the mission.
'''Environment''': External conditions surrounding the mission, such as weather conditions, terrain structure and composition, visibility.
'''RISK MANAGEMENT:'''Risk Management is the decision to control or reduce hazards.
One method of Control Options to assist in risk control or reduction uses the acronym S.T.A.A.R. During the mission, security staff must review the options and reassess the risks as appropriate.
'''Spread-out''' – Disperse the risk by increasing the time between events or using additional assets.
'''Transfer''' – If practical, locate a better-suited asset to conduct the mission (i.e. different type of asset or crew).
'''Avoid''' – Circumvent hazard: Wait for risk to subside (i.e. wait until daylight or weather passes).
'''Accept''' – In some cases the benefit might justify the assumption of risk. In these cases, a decision to accept risk may be made with the stipulation that risk is reevaluated as the mission progress.
'''Reduce''' – Reduce or limit risk exposure through the use of personal protective gear (Environmental Suits, Forcefields, Constructing Barriers, etc.), additional training or rest or rest periods for stress reduction, and timed interactions with potentially hostile negotiations.


The completion of the risk assessment and risk management component of the pre-mission planning helps to identify the mission specific and general equipment that will be needed by the security team. The selection of equipment is to be approved by the Chief of Security and the mission commander.   
The completion of the risk assessment and risk management component of the pre-mission planning helps to identify the mission specific and general equipment that will be needed by the security team. The selection of equipment is to be approved by the Chief of Security and the mission commander.   


Each member of the security department who has a role in the mission should familiarize themselves individually with the mission requirements, possible threats, and possible mission outcomes. Any questions or comments regarding the mission should be directed to the Chief of Security, who should discuss the issues with the mission commander.
Each member of the security department who has a role in the mission should familiarize themselves individually with the mission requirements, possible threats, and desired mission outcomes. Any questions or comments regarding the mission should be directed to the Chief of Security, who should discuss the issues with the mission commander.


===In-Mission Duties===
===In-Mission Duties===

Revision as of 22:12, 30 January 2011

This article needs to be discussed.
Please enter your input on the discussion page.


Note: This article is currently under construction.
 This notice was placed here by Whale, so go bug him to finish the page if nothing's happening.
Header security-wiki.jpg
Edit this nav

Pre-Mission Duties

Pre-Mission duties of the Starfleet Security Officer begins with the mission briefing. This briefing, usually administered by the section chief or the mission commander, is a compilation of the information obtained to date about the mission at hand. The briefing underlines the parameters of the mission, including key players, expected outcomes, potential complications, venue, and other components of the mission. After the briefing, the mission commander or security department head can assign components of the pre-mission planning to members of the security department. The planning for the mission from the security aspect can be delegated into two components; Risk Assessment and Risk Management.

The completion of the risk assessment and risk management component of the pre-mission planning helps to identify the mission specific and general equipment that will be needed by the security team. The selection of equipment is to be approved by the Chief of Security and the mission commander.

Each member of the security department who has a role in the mission should familiarize themselves individually with the mission requirements, possible threats, and desired mission outcomes. Any questions or comments regarding the mission should be directed to the Chief of Security, who should discuss the issues with the mission commander.

In-Mission Duties

Outside-Mission Duties

For the Head of the Department


Mission Specialist Helm/Com/Ops Engineer Science Officer Medical Officer Nurse
Intelligence Officer Security Officer Tactical Officer Marine Counselor Civilian
Duty Posts
Retrieved from "https://wiki.starbase118.net/wiki/index.php?title=Security_Officer_Simming_Guide&oldid=88923"