User:Eric6426: Difference between revisions

From Paradise Station Wiki
Jump to navigation Jump to search
Eric6426 (talk | contribs)
Created page with "{{Glossarytable}} '''Foreword:''' As the name indicates, Standard Operating Procedure is a set of Guidelines to be followed when the station is functioning nominally. Breaching Standard Operating Procedure without a very good reason is grounds for demotion, at the discretion of the relevant Head of Staff. In addition, blindly following the letter of SOP while ignoring the context of the shift is a '''ridiculously bad idea'''. SOP is malleable if the situation requires i..."
 
Removes category from user page.
 
(5 intermediate revisions by one other user not shown)
Line 174: Line 174:
  | title      = Security Level Delta - Status: The station's Nuclear Fission Device has been armed
  | title      = Security Level Delta - Status: The station's Nuclear Fission Device has been armed
  | header    = ''"Attention! Delta security level reached! The station's self-destruct mechanism has been engaged. All crew are instructed to obey all instructions given by heads of staff. Any violations of these orders can be punished by death. This is not a drill."''
  | header    = ''"Attention! Delta security level reached! The station's self-destruct mechanism has been engaged. All crew are instructed to obey all instructions given by heads of staff. Any violations of these orders can be punished by death. This is not a drill."''
  | content    = ''
  | content    = '''Called by:''' Malfunctioning AI Units or the on-board Nuclear Fission Device being activated.


'''Conditions:'''
'''Conditions:'''
Line 207: Line 207:
  | title      = Standard Procedures
  | title      = Standard Procedures
  | header    = The following situations are well within the range of conventional station operations and should serve as firm guidelines for standard situations.
  | header    = The following situations are well within the range of conventional station operations and should serve as firm guidelines for standard situations.
  | content    = ''
  | content    = <br>


==[[File:Id regular.png|32px]] Hiring/Transfer Policies==
==[[File:Id regular.png|32px]] Hiring/Transfer Policies==
Line 244: Line 244:
* Creation of an abusive and/or unsafe work environment. Personnel consistently berating, insulting, belittling, or otherwise treating their coworkers like dirt, should be immediately disciplined.
* Creation of an abusive and/or unsafe work environment. Personnel consistently berating, insulting, belittling, or otherwise treating their coworkers like dirt, should be immediately disciplined.


* A Vote of No Confidence, by the crewmembers of the department against their departmental Head of Staff with a 2/3 majority in favor of the vote, or by Heads of Staff against their Captain with a simple majority in favor of the vote. It must have a justified reason, detailed below, against the Head of Staff or Captain, having to be verified by an uninvolved and unbiased 3rd party who will tally the votes if they find the reason is valid.  
===Vote of No Confidence===
{{Hatnote|A Vote of No Confidence is a method for crew to arrange for demotions of unfit command members. It must have a justified reason, detailed below, against the Head of Staff or Captain in question.}}


    · The 3rd party must be the on-station Captain (not if they are the target of the vote), NT Representative, Magistrate or Centcomm if none of the previous are capable of acting as such.  
* Votes have to be verified by a 3rd party who will tally the votes and verify the validity of the reason for it. The 3rd party must be the on-station Captain (unless they are the target of the vote), NT Representative, Magistrate or Centcomm if none of the previous are capable of acting as such.  
    · If someone is to be demoted by a vote, Centcomm is to be informed afterwards via fax the details, vote count, reasons and other relevant information of the demotion.
 
    · If the 3rd party dismisses the vote reason, the target of the vote must have their authority respected and not be further harassed about it, doing so may result in a demotion for creating an abusive work environment against them.
* If the 3rd party dismisses the vote reason, the target of the vote must have their authority respected and not be further harassed about it, doing so may result in a demotion for creating an abusive work environment against them. If the department is understaffed or a tie occurs, the 3rd party may participate the vote.
 
* Votes by departamentamental crew against their Head of Staff must pass with a 2/3 majority in favor of the vote for it to take effect.
 
* Votes by Heads of Staff against their Captain must pass a simple majority in favor of the vote for it to take effect.
 
* Justified reasons for a vote include but are not limited to; 'Causes for Demotion and Dismissal' breaches, Absenteeism, critical lack of communication, abuse of authority and incompetence, among others.
 
* Unjustified reasons for a vote include but are not limited to; Personal gripes, reasonable and legal disciplining or firing of their staff and denial of permission, among others.
 
* If someone is to be demoted by a vote, Centcomm is to be informed afterwards via fax the details, vote count, reasons alongside other relevant information of the demotion.  


    '''Justified reasons include but are not limited to;'''
    · In breach of other 'Causes for Demotion and Dismissal' points, namely criminal offenses that relate to their department and creating an abusive and/or unsafe work environment.
    · Absenteeism: Physically disappearing at shift start and being MIA for a long time without a valid excuse.
    · Lack of communication: Not answering department radio or answering questions and requests whatsoever for a considerable period of time, to the point it's impeding the function of the department.
    · Abuse of authority: Using a telebaton or similar to physically discipline department members in an unnecessary fashion (ie: not in legal self defense), or demoting out department members for invalid reasons.
    · Total incompetence: Failure to understand the basics of their department to such a degree that they're unable to effectively lead it.
    · Endangering employees: Modifying/running the department in such a way as to risk the safety of their employees.
    '''Unjustified reasons include but are not limited to;'''
    · Management disagreement: Starting a vote against the department head simply because you disagree about how the department is being run; they're in charge, its up to them, within reason.
    · Disciplining you: In general, you shouldn't start a no-confidence vote against your department head right after they tell you off for something, or otherwise discipline you for your actions that require such treatment.
    · Request refusal: You shouldn't start a vote because they refused any request you made, unless the request is essential that to refuse the request is putting the crew at risk. (e.g: science refusing to give out welders during blob when they have the materials to print them)
    · Personal gripes: Requesting a vote due to a dislike of the person in charge is not professional whatsoever and is grounds for demotion of the one doing so.
    ''
}}
}}


Line 270: Line 268:
  | title      = Emergency Procedures
  | title      = Emergency Procedures
  | header    = The following situations are well within the range of conventional emergency station operations and should serve as firm guidelines for emergency situations.
  | header    = The following situations are well within the range of conventional emergency station operations and should serve as firm guidelines for emergency situations.
  | content    = ''
  | content    = <br>
   
   
==[[File:EmergencyResponseTeam.png|32px]] Emergency Response Teams==
==[[File:EmergencyResponseTeam.png|32px]] Emergency Response Teams==
Line 407: Line 405:
{{SOPTable}}
{{SOPTable}}
[[Category:Standard Operating Procedure]]
[[Category:Standard Operating Procedure]]
[[Category:Guides for New Players]]

Latest revision as of 03:58, 23 November 2023

Useful Resources

Foreword: As the name indicates, Standard Operating Procedure is a set of Guidelines to be followed when the station is functioning nominally. Breaching Standard Operating Procedure without a very good reason is grounds for demotion, at the discretion of the relevant Head of Staff. In addition, blindly following the letter of SOP while ignoring the context of the shift is a ridiculously bad idea. SOP is malleable if the situation requires it, and the general well-being and proper functioning of the crew and station should not be sacrificed for the sake of rigorous adherence of SOP. Remember, context is king.

Nanotrasen has a standard set of procedures for crew personnel to follow when there is (or isn't) an emergency. This is to assure that all actions are in the best interests of Nanotrasen. Failure to follow these may result in dismissal/demotion. Extreme or repeated cases may result in a jobban.

NOTE: Any mentions of "The Station" or "Station" in SOP unless otherwise specified is in reference to the reader's (employee's) assigned Nanotrasen Science Station or Area of Operations. The following (but not limited to) research stations are assigned these SOP documents: NSS Keberos, NSS Cereberon, and NSS Cyberiad.

Departmental SOP

Along with the guidelines listed below, each and every department has it's own subset of job-specific Standard Operating Procedure that is to be adhered to whenever possible.

Alert Levels

Security Level Green - Status: All clear; no threats on-board/near the station

"Attention! Security level lowered to green. All threats to the station have passed. All weapons need to be holstered and privacy laws are once again fully enforced."


Security Level Blue - Status: There is a suspected threat on-board/near the station

"Attention! Security level elevated to blue. The station has received reliable information about possible hostile activity on the station. Security staff may have weapons visible and random searches are permitted."


Security Level Red - Status: There is a confirmed, hostile threat on-board/near the station

"Attention! Code Red! There is an immediate and serious threat to the station. Security may have weapons unholstered at all times. Random searches are allowed and advised."


Security Level Gamma - Status: There is a massive threat to the safety of the station and crew

"Attention! Gamma security level activated! Central Command has ordered the Gamma security level on the station. Security is to have weapons equipped at all times, and all civilians are to immediately seek their nearest head for transportation to a secure location."


Security Level Delta - Status: The station's Nuclear Fission Device has been armed

"Attention! Delta security level reached! The station's self-destruct mechanism has been engaged. All crew are instructed to obey all instructions given by heads of staff. Any violations of these orders can be punished by death. This is not a drill."


Standard & Emergency Procedures /

Standard Procedures

The following situations are well within the range of conventional station operations and should serve as firm guidelines for standard situations.


Emergency Procedures

The following situations are well within the range of conventional emergency station operations and should serve as firm guidelines for emergency situations.


Non-Standard Emergency Procedures

Emergency Situation Procedures
The following situations are so outside the range of conventional station operation, that special procedure was drawn up for them. These are by no means rigid guidelines, but merely server as an indicator on what should be done to preserve the integrity of the station and its crew.

Fire/Gas Spills

  • All personnel are to vacate the affected area;
  • Hazard Lock systems are to be left untouched. Deliberately opening Hazard Locks during a Fire/Gas Spill in order to open way to the Hazard is to be considered Sabotage/Grand Sabotage;
  • Engineering and Atmospherics personnel are to restore the affected area to working and livable condition.

Viral Outbreak Procedures

1. All Medbay personnel are to contribute in fighting the outbreak if there are no other critical patients requiring assistance. Eliminating the Viral Threat becomes number one priority;

2. Personnel are to be informed of known symptoms, and directed to Medbay immediately if they are suffering from them;

3. All infected personnel are to be confined to either an Isolated Room, or Virology;

4. A blood sample is to be taken from an infected person, for study;

5. If any infected personnel attempt to leave containment, Medbay Quarantine is to be initiated immediately, and only lifted when more patients need to be admitted, or the Viral Outbreak is over;

6. The cure must be identified, and administered to at least one (1) infected person. A blood sample must then be taken in order to produce a Vaccine;

7. Once Vaccines are produced, they are to be handed out to all infected personnel;

8. A sample of blood with the correct Antibodies must be kept in storage, in case any stray cases remained untreated;

9. In case the Viral Pathogen leads to fluid leakage, cleaning these fluids is to be considered top priority;

10. Once the Viral Outbreak is over, all personnel are to return to regular duties.

Meteor Storms

  • Personnel are to head to the Central Primary Hallway for the duration of the storm;
  • No repair activities are to be performed until the end of the storm, for safety reasons;
  • All personnel performing EVA duty are to return to the station post haste;
  • In the case of a short storm, Engineering is to repair any damage done ASAP;
  • In the case of a prolonged storm, no repair activities on non-critical components are to be performed. Personnel are to remain in the Central Primary Hallway, and all efforts focused on maintaining the integrity of the area. The NTV Charon is to be called when possible (at the discretion of Command), and an early launch is permitted.

Singularity Containment Failure

The Gravitational Singularity is to be tracked at all costs. If the Gravitational Singularity heads towards the main station, the NTV Charon is to be called. If the Gravitational Singularity heads off-station, damage done to the station should be taken into consideration. See below:

  • In the case of massive station damage, the NTV Charon is to be called;
  • In the case of light-medium station damage, an ERT is recommended, or, in the case of a competent Engineering team, merely extensive repairs.

Tesla Containment Failure

  • The Tesla Matrix is to be tracked at all costs, and its current location announced to the crew;
  • If the Tesla Matrix remains inside the Station rather than arcing into space, the Charon is to be called.

Supermatter Delamination Event

  • The Supermatter Crystal is to be vented to space;
  • In such a case as the Supermatter Crystal containment was not equipped with a way to space the Crystal, the area around the Crystal is to be evacuated, and all personnel involved in the construction fired and brigged for Sabotage.

Syndicate Declaration of War

  • All weapons restrictions are lifted. Beepsky, and any other Security Bots, should have their protocols updated to reflect this;
  • Supply should focus on requesting as many weapons as possible. Security is to be prioritized for distribution, but regular personnel may also be armed;
  • Research and Development is to be manned. This is not negotiable. Science should work in tandem with Mining in order to fabricate weapons and equipment to fight the Syndicate Attack Team;
  • Erecting barricades in critical locations is highly recommended;
  • The NTV Charon may be called at the discretion of Command. If the station is not damaged after the fighting has subsided, it is recommended that the crew finish the shift.

Confirmed Revolution

  • All personnel are to comply with orders from Security personnel, so long as said orders are lawful. Failure to do so is grounds for detainment and inspection of possessions, as well as possible Mindshield Implantation, at the discretion of the Head of Security, or Acting Head of Security;
  • All personnel that are brigged for Medium Crimes or higher are to receive Mindshield Implantation. Similarly, if the number of active revolutionaries is more than twice the number of loyalists, the Head of Security or Acting Head of Security may order random implantation of crew members;
  • Lethal force is fully authorized if the number of active revolutionaries is more than twice the number of loyalists, and said revolutionaries are actively hostile.
Standard Operating Procedure
Departmental SOP CommandEngineeringMedicalScienceSecurityServiceSupply
Other SOP GeneralLegal