General SOP --- Complete!

[TullyBBurnalot]

 

General SOP: Complete!

 

Greetings, aspiring SOP writers. If you've clicked this thread, then you're either interested in contributing to Standard Operating Procedure, or are merely interested in seeing how it's going. Therefore, I shall begin by explaining what this (soon-to-be) megathread is all about:

 

Part 1: What is this?

 

Approximately 4 months ago, Necaladun approached me with a personal project of his: a complete overhaul of Standard Operating Procedure, meant to centralize SOP in such a way that allowed for more interaction with the Legal sub-Department, more actual guidelines on how to conduct one's performance, and generally formalize what was once only nebulous guidelines in an effort to get everyone on the same page.

 

This was the project that led to the current version of Security SOP. However, it was left half done, as Necaladun took his leave shortly after Sec SOP was added, and the project crumbled from lack of interest/time. However, I continued the project, but only recently picked it back up in full. The point of this megathread will be to, at the end of the line, have a single, well-defined, centralized Standard Operating Procedure that everyone can look at and fully comprehend, without any self-contradictory information. This, of course, will be changed in the Wiki, which is still the main source of information for the playerbase.

 

 

Part 2: How does it work?

 

Seeing as I actually have most of this stuff already written down, the process will be quite simple, and I'll break it down in stages:

 

Stage 1: Selection of which part of SOP to look at, out of provided options (because we have to start somewhere). This will be done via poll;

 

Stage 2: Proposal of new SOP. This will come from myself, again, because I have pretty much most of it already written down, so we have a solid base to go from;

 

Stage 3: General feedback from the community. This is the main part of the process, as it will be the one where everyone can pitch in, say which parts are right, which parts are wrong, what should be changed, etc;

 

Stage 4: Amendments made to SOP based on this feedback, and continued discussion, until a finalized version is produced;

 

Stage 5: SOP is posted on the Wiki;

 

Stage 6: Refer to Stage 1

 

Do keep in mind the following: everyone is permitted to pitch in. If you believe you have anything to add to the discussion, please do, but do try to keep this on track and problem-oriented, otherwise we'll never get off the drawing board.

 

 

Part 3: What does it entail?

 

The following are the proposed additions to this new, centralized SOP:

 

 

1. Security Job SOP; (added by Necaladun before he took his leave)

2. Engineering Job SOP; (finalized!)

Medical Job SOP; (finalized!)

Service Job SOP; (finalized!)

Supply Job SOP; (finalized!)

Science Job SOP (finalized!)

 

 

In addition to the basic SOP for each Department, I also propose:

 

 

1. Departmental SOP (as in, general guidelines for each Department that everyone should follow); (stricken to avoid bloat)

2. Command SOP; (finalized!)

Legal SOP (standardization of Legal procedures and the action of the Legal sub-Department);

A revised General SOP, for each Color Code. This will include Safety Regulations

 

 

As you can see, this is a rather big project and, as such, will be tackled in small stages. At each point, the completed section of SOP will be crossed out, and a notification written. At the end of the journey, a single, massive Standard Operating Procedure page will be added to the wiki, with all the above SOPs for everyone to look at. In addition, of course, to their own specific pages.

 

And now, you've reached the end of the page. It's time to start, ladies and gentlemen.

 

Edited June 24, 2016 by Guest

[TullyBBurnalot]

 

General SOP will encompass not only the Alert Level system, but also safety regulations and firing/hiring procedures. Enjoy.

 

Foreword: Generally, the Captain or Acting Captain should be in charge of calling/setting Alert Levels. An exception is made for Code Red, where any two members of Command should call it regardless of what the Captain commands, if there is an active emergency.

 

Code Green

 

Status: All Clear

 

Called by: Anyone with Captain-Level Access at a working Communications Console.

 

Conditions:

 

 

1. Default Alert Code at the start of the shift. Do not change unless a threat is suspected/confirmed

 

OR

 

1. All confirmed/suspected threats to the station and/or crew have been handled, or simply vanished on their own. It is recommended that, after 15+ minutes on Code Blue without any hostile activity, Code Green be called

 

 

Security:

 

 

1. All weapons must be holstered or kept in pockets/suit storage slots unless absolutely required;

2. Random searches are not permitted without express permission by either the Head of Security, Captain or Magistrate. However, searches are still permitted if there is reasonable suspicion of a crime

 

 

Secure Areas:

 

EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used

 

 

1. While it is not recommended that Secure Areas be bolted down if unused, it is not prohibited. EVA, in particular, should be left unbolted due to its use by Engineers and Atmospheric Technicians. Exceptions are below;

2. The Gateway is not to be opened without permission from the Captain or Acting Captain;

The Vault is not to be opened unless repairs are required, gold is required for Research and Development (in case Mining fails to deliver) or a critical item needs to be hidden in the safe

 

 

General Crew:

 

 

1. While not required, it is recommended that the crew activate and maximize their Suit Sensors, due to the potential for workplace accidents;

2. Free transit through the station is permitted for the crew, outside of Secure Areas

 

 

Code Blue

 

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

 

Called by: Anyone with Captain-Level Access at a working Communications Console.

 

Conditions:

 

 

1. There is a suspected threat on-board the station, or at a nearby location in space. This includes any signs of hostile activity that have not caused any damage to station or crew, but nonetheless seem present

 

OR

 

1. Confirmed Code Red threats have been properly handled or subsided on their own. It is recommended that, after 15+ minutes on Code Red without any hostile activity, Code Blue be called

 

 

Security:

 

 

1. Weapons do not need to be holstered. However, it is recommended that Security personnel follow Security SOP in order to prevent accidents and to be fully aware of armament procedure;

2. Random searches are fully permitted. Security personnel may detain any personnel refusing a random search in order to conduct said search;

 

 

Secure Areas:

 

EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used

 

 

1. It is recommended that all Secure Areas be bolted down unless their use is necessary;

2. Excursions into the Gateway are not recommended, unless they are rescue parties

 

 

General Crew:

 

 

1. All personnel are highly recommended to maximize their Suit Sensors;

2. Personnel are to report any suspicious activity to the nearest member of Security, or use their PDA or Headsets if required;

Personnel are highly encouraged to exercise caution, even if the threat is only suspected. Following simple safety procedures (such as not going through Maintenance alone) can prevent needless accidents;

Visitors to the station (anyone with Civilian-level access) are recommended to stay in public areas, for their safety

 

 

Code Red

 

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

 

Called by: Any two personnel with Command-Level Access, at a Card Swiper. Requires close timing.

 

Condition:

 

 

1. There is a confirmed, hostile threat on-board the station or nearby in space. This threat should pose recognizable danger to the station and/or crew at large

 

 

Security:

 

 

1. Security personnel should read Security SOP for armament, armory and safety procedures;

2. Random searches are fully permitted and recommended. Security personnel may detain any personnel refusing a random search in order to conduct said search;

Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station

 

 

Secure Areas:

 

EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used

 

 

1. All Secure Areas are to be bolted down. Secure Areas may be left unbolted at the discretion of Command personnel;

2. Excursions into the Gateway are prohibited, unless they are rescue parties

 

 

General Crew:

 

 

1. All personnel are required to maximize their Suit Sensors;

2. All personnel are to remain inside their Departments for the duration of Code Red, unless specifically requested by Security and/or Command;

Visitors to the station (anyone with Civilian-level access) are to remain inside the Bar, Library or Dormitories for the duration of Code Red;

Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. Failure to do so may lead to their arrest for Creating a Workplace Hazard

 

 

Code Gamma

 

Status: There is a massive threat to the safety of the station and crew

 

Called by: Central Command. Use a Communications Console or Fax Machine in order to explain the situation. Remember, Gamma is rarely called, for good reason. Having a well-written, concise fax that explains the situation to the best of your ability, as well as why it deserves Code Gamma being called, signed and stamped by the Captain or Acting Captain, goes a long way towards ensuring Gamma is provided. Remember, this is for extreme emergencies only.

 

Conditions:

 

 

1. There is a massive threat to the continued safety of the station and crew, threatening the very existence of the Cyberiad;

2. However, this threat is not yet big enough to warrant the destruction of the Cyberiad, and Central Command may still want to protect their assets

 

 

Security:

 

 

1. Martial Law is enacted. Security personnel have full permission to do whatever it takes to ensure that the safety of the station and crew is maintained, up to and including detaining any personnel interfering with emergency procedures;

2. Random searches are fully permitted, allowed and encouraged. Security personnel may detain any personnel refusing a random search in order to conduct said search;

Security is to secure the contents of the Gamma Armory and distribute it to Security personnel in order to handle the threat. Non-Security personnel (including members of the Legal Sub-Department) are not to receive these weapons unless necessary;

Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station

 

 

Secure Areas:

 

EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used

 

 

1. All Secure Areas are to be bolted down. Secure Areas may be left unbolted at the discretion of Command personnel;

2. Excursions into the Gateway are fully prohibited

 

 

General Crew:

 

 

1. All personnel are required to maximize their Suit Sensors;

2. All personnel are to remain inside their Departments until such a point as Code Gamma has passed, unless specifically requested by Security and/or Command, or their particular skills can help resolve the situation (such as Field Medics or Engineers);

Visitors to the station (anyone with Civilian-level access) are to remain inside the Bar, Library or Dormitories until such a point as Code Gamma has passed;

Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. Failure to do so may lead to their arrest for Creating a Workplace Hazard

 

 

Code Delta

 

Status: The station is about to be consumed by nuclear fire

 

Called by: Malfunctioning AI Units, Nuclear Operatives, or the on-board Nuclear Fission Device being activated

 

Conditions:

 

 

1. A Malfunctioning AI Unit has dropped all semblance of stealth and activated their Override Mechanism

 

OR

 

1. The on-board Nuclear Fission Device has been activated by Command or Central Command personnel

 

 

Security:

 

 

1. In the case of a Malfunctioning AI Unit, all Security personnel are required to drop whatever it is they are doing, and proceed to neutralize the AI Unit. Any relevant help from station personnel (such as Engineers or Scientists) is not to be turned down;

2. In the case of Nuclear Operatives, defusing the bomb is not recommended. Security personnel are to escort all other personnel off-station;

In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all Security personnel are to stand down

 

 

Secure Areas:

 

EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used

 

 

1. Procedures are irrelevant

 

 

General Crew:

 

 

1. In the case of a Malfunctioning AI Unit or Nuclear Operatives, all non-vital personnel are to evacuate off-station immediately;

2. In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all personnel are to stand down

 

 

Code Epsilon

 

Status: "The hypothetical "Code Epsilon" has somehow persisted in rumors for the past several several years among NanoTrasen crews. For the last time, no, we do not operate "Death Squads", no, we do not suddenly terminate your contracts and send heavily trained mercenaries after you, and no, I do not care what your "buddy in the ERT camp" said.

 

There is no such thing as a Code Epsilon. Now get back to work."

 

- Commodore Martin Treyan, NAS Odin

 

"The NAS Odin has since been stricken from company records. Please do not refer to the NAS Odin"

 

- CEO [REDACTED]

 

Emergency Response Teams

 

Crew Procedures:

 

 

1. Emergency Response Teams are only to be called when there is a Code Red-level threat or above;

2. Emergency Response Teams are not to be called concurrently with the NTV Charon (Escape Shuttle). Pick one or the other;

Emergency Response Teams are to be called when there is a major emergency aboard the station that the crew does not have the resources to fight properly. This includes, but is not limited to, any hostile threat present without an active Security force, or massive station damage without an active Engineering force;

Emergency Response Teams are not to be called without majority approval from Command;

Emergency Response Teams officially outrank anyone short of a Central Command Officer. Unless their actions are blatantly illegal and against the best interest of NanoTrasen, the station and its crew, their orders are to be followed above anyone else's

 

 

Emergency Response Team Procedures:

 

 

1. The Emergency Response Team Leader is to ensure that all members of the Team are present before boarding the Cyberiad;

2. The Emergency Response Team Leader is to be considered the top authority inside the Emergency Response Team. Unless their orders are blatantly illegal and against the best interest of NanoTrasen, the station and its crew, they are to be followed above anyone else's;

All members of the Emergency Response Team are to activate their helmet cameras (by clicking the button next to their helmet) and maintain open lines of communication between them;

The Emergency Response Team is to prioritize whatever it was they were called over. Digressions are not permitted;

The Emergency Response Team is to ensure that none of its equipment falls in the hands of either the crew or hostile forcesl

 

 

NTV Charon --- The Escape Shuttle

 

 

1. The NTV Charon is not to be called concurrently with an Emergency Response Team. Pick one or the other;

2. In the event of hostile biohazard lifeforms appearing on the station (such as Xenomorphs or Class 7-10 Blob Organisms), Central Command is to be notified before the NTV Charon is called. Failure to do so may lead to the Charon being recalled in order to enforce quarantine. Similarly, Central Command may prohibit calling the Charon in order to handle the biohazard;

In the event that the NTV Charon is called, all personnel are to wrap up their current task and head to the Escape Lobby within, at most, five minutes before departure;

Forcing an early departure of the NTV Charon is not permitted unless the structural integrity of the Charon is endangered (such as a nearby Gravitational Singularity, or a Meteor Storm), or the safety of the crew aboard the Charon is threatened (such as nearby hostile Ascendants or Nar-Sie Constructs);

All currently brigged personnel are to be kept in the Shuttle Brig;

All personnel in critical medical condition are to be kept inside Stasis Bags, or given emergency medical aid

 

 

Hiring/Transfer Procedures:

 

 

1. No new hires or transfers are permitted without contacting the relevant Head of Staff. If one is not available, promoting an Acting Head of Staff is recommended. If none is available, the Head of Personnel/Captain are to utilize their best judgement (see Command SOP for any exceptions);

2. Promotion to Acting Head of Staff requires authorization by the Captain or Acting Captain;

The following jobs require permission from Central Command before hiring/transfer is done: Blueshield, NanoTrasen Representative, Magistrate, Security Pod Pilot, Brig Physician, Mechanic and Barber. The same applies to any functionally identical job with another title;

All new hires to the Security Department, and Legal Sub-Department, are to be loyalty implanted and fully checked for unauthorized materials or suspicious communications

 

 

Firing/Demotion Procedures:

 

 

1. In the case of a full dismissal, the relevant ID is to be terminated;

2. In the case of a demotion, Civilian-level access is recommended. Alternatively, jobs such as Janitor or Clown may also be used;

No dismissals or demotions are to be performed without authorization from the relevant Head of Staff or Captain. See Chain of Command for how to handle dismissing a member of Command;

Personnel are to report to the Head of Personnel for dismissal/demotion. Failure to do so will lead to Security detaining them forcefully;

After a legal dismissal/demotion order is given to the person dismissed/demoted (e.g: by radio), any activity inside the previously assigned Department is to be considered Trespassing/Major Trespassing, and any item kept from said Department is to be considered Petty Theft/Theft. It is, as such, highly recommended that dismissed/demoted personnel willingly turn in all restricted items and cooperate with the process if they wish to avoid being brigged

 

 

Causes for Dismissal:

 

Refer to the above for dismissal authority. Ultimately, the decision to fire/demote any personnel falls to the relevant Head of Staff or Captain. This is merely a list of reasons to fire someone over.

 

 

1. Any medium-severe breach of Standard Operating Procedure without proper cause;

2. Any medium crime or higher;

Critical incompetence at a given job;

Refusal to follow legal and relevant orders by the respective Head of Staff. Legality and relevance of said orders are to be judged by the Captain or Head of Personnel;

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

 

 

Situational SOP

 

Defined as any situation that falls so far out of conventional operation, that special procedures must be drawn up for it.

 

Fires/Gas Spills

 

 

1. All personnel are to vacate the affected area;

2. 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

 

 

Meteor Storm

 

 

1. Personnel are to head to the Central Primary Hallway for the duration of the storm;

2. 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

 

 

1. 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;

 

 

1. In the case of massive station damage, the NTV Charon is to be called;

2. 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

 

 

1. The Tesla Matrix is to be tracked at all costs, and its current location announced to the crew;

2. If the Tesla Matrix remains inside the Cyberiad rather than arcing into space, the Charon is to be called

 

 

Supermatter Delamination Event

 

 

1. The Supermatter Crystal is to be vented to space;

2. 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

 

 

1. All weapons restrictions are lifted. Beepsky, and any other Security Bots, should have their protocols updated to reflect this;

2. 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

 

 

1. 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 Loyalty Implantation, at the discretion of the Head of Security, or Acting Head of Security;

2. All personnel that are brigged for Medium Crimes or higher are to receive Loyalty 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

 

 

Edited June 20, 2016 by Guest

[Kyet]

 

Warning, bluespace artillery fire detected!

 

Called by: Anyone with Captain-Level Access at a working Communications Console.

 

Might be useful to say it is the Captain's job to call/change alert levels in general, with the caveat that other heads should call red regardless of the Captain if the situation obviously warrants it and the Captain is failing to act.

 

Random searches are not permitted without a warrant signed by either the Head of Security, Captain or Magistrate. However, searches are still permitted if there is reasonable suspicion of a crime;

 

Usually, if sec wants to search, its easier to get code blue declared than it is to get a warrant. It is certainly faster!

That is arguably bad. Since it leads to code blue being the norm if there is even the slightest reason for it.

Perhaps warrants should be made easier to get, ie: the word of the HoS / Captain should be enough to authorize them.

That might enable green to see more use.

 

Security may not forcefully relocate personnel to any location on the station

 

Translation: Security can't arrest people and haul them to the brig, unless...?

 

EVA Storage, Tech Storage, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used

 

Armory?

Gravity Generator?

 

Also, this SOP permits, for example, the AI to mass-bolt every secure area on code green at round start.

 

The Vault is not to be opened without direct permission from Central Command, or to place high-risk items inside the safe (not applicable to the Nuclear Authentication Disk)

 

 

The vault is not to be opened unless it is to:

1) Secure the nuclear disk or other critical items

2) Check it for damage/breakin

3) Acquire gold for R&D in the absence of miners bringing it in

 

Security may relocate personnel to their respective Departments if it is required to ensure their safety. Visitors to the station (anyone with Civilian-level access) should be relocated to the Bar, Library or Dormitories if this happens

 

Not sure the point of this. Security never forcibly relocates people for their safety. Ever.

 

New:

- I see no guideline along the lines of "crew are requested to be alert for, and report, suspicious activity to their nearest security officer"

- I also see no guideline along the lines of "crew are expected to maintain a healthy sense of caution, e.g: not to deliberately expose themselves to as-yet-unidentified dangers for no good reason.

 

 

[*]Random searches are fully permitted and recommended for suspicious personnel;

 

Perhaps add: "Security has the right to detain someone for a search should they not comply."

 

Security is to relocate all personnel to their Departments, unless they are running vital errands. Visitors to the station (anyone with Civilian-level access) are to be relocated to the Bar, Library or Dormitories;

Perhaps: "Security is advised to consider searching non-head personnel wandering outside of their departments without good reason."

Relocating them is time-consuming and achieves nothing. Security never does it.

 

All Secure Areas are to be bolted down;

 

Perhaps add "Preferably by the AI, who is best suited for this task".

 

Called by: Central Command. Use a Communications Console or Fax Machine in order to explain the situation

 

Perhaps add: "Gamma is called rarely, by CC at their sole discretion. A well-written Fax, signed and stamped by at least one competent head, providing details of a clear and overwhelming threat, is required for CC to consider calling it."

 

Martial Law is enacted. Security personnel have full permission to do whatever it takes to ensure that the safety of the station and crew is maintained, up to and including detaining any personnel interfering with emergency procedures;

 

I would also add: "At this level, Security should be equipped with lethal weapons". Perhaps even add this to code red.

 

Random searches are fully permitted and allowed;

 

"And encouraged"

 

Security is to secure the contents of the Gamma Armory and distribute it to Security personnel in order to handle the threat. Non-Security personnel (including members of the Legal Sub-Department) are not to receive these weapons unless absolutely necessary;

Realistically, if GAMMA is called, arming more crew is probably going to be necessary.

 

Security is to ensure that all non-vital personnel remain inside their Departments. Any personnel attempting to interfere with emergency procedures are to be detained and brigged until such a time as the threat has passed;

 

Again, trying to keep crew in their departments is pointless.

 

Status: The station is about to be consumed by nuclear fire

 

"The station is about to get very, very warm and toasty."

(kidding, not a serious change suggestion)

 

Called by: Malfunctioning AI Units, Nuclear Operatives, or the on-board Nuclear Fission Device being activated

 

Since when do nuclear ops ever trigger delta?

I would list the "called by" as: "Malfunctioning (ie: hostile to all non-synthetic life) AI units, and unsalvagable disasters such as uncontained xenomorph outbreak"

 

Nuclear Operatives have activated their Nuclear Fission Device (does not trigger actual Code Delta. Result is the same)

 

If it doesn't trigger actual code delta, either it should... or this should not be covered here.

 

The on-board Nuclear Fission Device has been activated by Command or Central Command personnel

That's a better condition.

 

In the case of a Malfunctioning AI Unit, all Security personnel are required to drop whatever it is they are doing, and proceed to neutralize the AI Unit;

Perhaps add: "help from crew should not be turned down, as it could potentially save the station".

 

In the case of Nuclear Operatives, defusing the bomb is not recommended. Security personnel are to escort all other personnel off-station;

 

"In the case of nuclear operatives, ..." actually, what could they possibly do other than defuse the bomb once armed? Prior to that, secure the disk?

 

In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all Security personnel are to stand down

 

"In the case of a CC-authorized nuclear self-destruct, all personnel are instructed to pray to their deity of choice"

 

Procedures are irrelevant

Why have an entire section labeled irrelevant?

 

In the case of a Malfunctioning AI Unit or Nuclear Operatives, all non-vital personnel are to evacuate off-station immediately;

Good idea.

In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all personnel are to stand down

... yeah, sure. We'll get right on that. Just... standing here. *runs for his life!*

 

The station is in such a state as to be irrecoverable. Central Command is cutting their losses and terminating anything on-board the station that can move

ICly, I don't think the official CC-issued SOP doc would admit this.

OOCly, its good for people to realize what it means.

I still can't help feeling that this could be better worded, though. Perhaps formatted differently, tacked on, like a scrawled note, to the bottom of the SoP guide, like a rumor or unofficial post-it would be.

 

 

Security:

 

Procedures are irrelevant

These sections are irrelevant. Yet they are still here. Why?

 

Procedures are irrelevant

Again...

 

Procedures are irrelevant

Tully, stop the madness!

 

Emergency Response Teams are to be called when there is a major emergency aboard the station that the crew does not have the resources to fight properly. This includes any hostile threat present without an active Security force, or massive station damage without an active Engineering force;

"Or major outbreak of a dangerous virus with no/inadequate medical staff?"

 

Emergency Response Teams are not to be called without majority approval from Command

... this happens?

 

All members of the Emergency Response Team are to activate their helmet cameras and maintain open lines of communication between them;

 

Maybe tell them HOW they're supposed to turn on their helmet cams...

 

The NTV Charon is not to be called if there are hostile biohazard lifeforms aboard the station. This includes Xenomorphs and Class 7-10 Blob Organisms. Calling an Emergency Response Team is more appropriate in these conditions;

Most people won't know what a 7-10 is.

 

In the event that the NTV Charon is called, all personnel are to wrap up their current task and head to the Escape Lobby within, at most, five minutes of departure;

 

Of->Before.

 

All currently brigged personnel are to be kept in the Charon Brig;

 

Shuttle Brig. Yes, I know, same thing. But why call it the Charon throughout when "Shuttle" is clearer?

 

No new hires or transfers are permitted without contacting the relevant Head of Staff. If one is not available, promoting an Acting Head of Staff is recommended. If none is available, the Head of Personnel/Captain are to utilize their best judgement (see Command SOP for any exceptions);

So, technically, if I'm HoP, I can give people extra access, even to a department that isn't theirs, so long as it isn't officially a "transfer"

 

The following jobs require permission from Central Command before hiring/transfer is done: Blueshield, NanoTrasen Representative, Magistrate, Brig Physician, Mechanic and Barber;

 

"The same applies to any functionally identical job with another title".

 

All new hires to the Security Department, and Legal Sub-Department, are to be loyalty implanted and fully checked for unauthorized materials or suspicious communications

Searching everyone hired into these roles is not going to accomplish anything. People will learn it and just stash their items first. It just slows down hiring and makes it harder to get sec officers during rounds where they are understaffed.

 

Personnel are to report to the Head of Personnel for dismissal/demotion. Failure to do so will lead to Security detaining them forcefully;

 

"As will them failing to surrender ANY of the items from their previous job, as this is considered theft".

Or maybe not, with the next point.

 

After a legal dismissal/demotion order is given, any activity inside the previously assigned Department is to be considered Trespassing/Major Trespassing, and any item kept from said Department is to be considered Petty Theft/Theft. It is, as such, highly recommended that dismissed/demoted personnel willingly turn in all restricted items and cooperate with the process if they wish to avoid being brigged

"given to the person dismissed/demoted, e.g: by radio"

 

Hazard Lock systems are to be left untouched. Opening Hazard Locks during a Fire/Gas Spill is to be considered Sabotage/Grand Sabotage;

 

Uh... really?

Perhaps "deliberately helping the fire/gas to spread". People open them by accident regularly.

 

No repair activities are to be performed for the duration of the storm;

 

"until after the storm has safely passed, due to safety risk"

 

Tesla Containment Failure

 

 

1. The Tesla Matrix is to be tracked at all costs, and its current location announced to the crew;

2. All personnel are to hide in the nearest locker;

The NTV Charon is to be called

 

 

"If it is safe to do so, whoever released it, or is thought to have released it, should be detained"

 

Supermatter Delamination Event

 

 

1. The Supermatter Crystal is to be vented to space;

2. 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

 

 

When was the last time the supermatter was used?

 

Syndicate Declaration of War

 

 

1. All weapons restrictions are lifted. Beepsky, and any other Security Bots, should have their protocols updated to reflect this;

2. 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

 

 

This is remarkably sensible.

 

Nar-Sie Summoning

 

 

1. All personnel are to evacuate off-station;

2. Central Command is to be alerted;

An Emergency Response Team will be sent to recover all evacuees

 

 

"evacuate off-station via pods, and the eng/science/etc shuttles. Nar-sie is easily able to overpower a large gathering, such as at Escape, so dispersal and fleeing maximizes your chances of survival"

 

[pinatacolada]

 

[*]The following jobs require permission from Central Command before hiring/transfer is done: Blueshield, NanoTrasen Representative, Magistrate, Brig Physician, Mechanic and Barber;

 

sec pod pilotttttttttttttttttttt

 

[liran424]

 

Code Epsilon? we really shouldn't be talking about this. Death Squad is here! run away!

 

And you missed in situational SOP what to do when there's a wizard or a blob on board.

 

[Coldflame]

 

My suggestions to improve it:

 

-Get rid of mentioning warrants for searches on green. Random searches shouldn't be happening either way, and you don't need a warrant to search people who are suspect of a crime.

-The crew don't have the vault's safe combo, so you can't store items inside. The Vault also has things inside the crew might need to use, so banning opening it might be a little questionable.

-'All secure areas are to be bolted down' as a blanket rule will probably cause more trouble than it's worth for the crew during red alert. Leaving things like that to command's discretion might be wiser than specifying it in SoP.

-Code Epsilon having a section in (IC) SoP seems a little odd- After all, it doesn't exist...

 

I'd also suggest an addition of situation SoP for rev, given how security and command have to act differently in order to combat them:

1. All crew are to comply with security and command requests without question as to not be confused with revolutionaries.

2. Security may implant any crew members who lack an implant, and may exercise force to do so if the crew resists.

3. If revolutionaries have gained control of the station, security may utilize lethal force as needed to regain control of the station.

 

[SkyPing]

 

I don't want to go FULL nitpick node since TZO already did his blurb, but I'll add a few of my thoughts when I was just skimming the SoP

 

[*]Random searches are not permitted without a warrant signed by either the Head of Security, Captain or Magistrate. However, searches are still permitted if there is reasonable suspicion of a crime;

 

If the person is suspicious enough for the HoS, Captain, or Magistrate to actually go out of their way to sign a search warrant, is it still considered a "Random" search?

 

[*]Security may relocate personnel to their respective Departments if it is required to ensure their safety. Visitors to the station (anyone with Civilian-level access) should be relocated to the Bar, Library or Dormitories if this happens

 

I feel like the chapel should be added to that list; just because it feels REALLY fitting.

 

I'll do a full fledged nitpicking after the first few rounds of comments and changes are made.

 

[Ansari]

 

The Paramedic must carry, at all times, enough materials to provide for adequate first aid of all Major Injury Types (Brute, Burn, Toxic, Respiratory and Brain)

 

I think brain damage part should be removed. I have never seen any case where immediate first aid for brain damage is required on the spot and the patient cannot be taken back to medbay for treatment.

 

[TullyBBurnalot]

 

THE TIME FOR QUOTE WALLS IS NOW.

 

LINE BEGINS HERE.

 

---

 

Might be useful to say it is the Captain's job to call/change alert levels in general, with the caveat that other heads should call red regardless of the Captain if the situation obviously warrants it and the Captain is failing to act.

 

Added:

 

Foreword: Generally, the Captain or Acting Captain should be in charge of calling/setting Alert Levels. An exception is made for Code Red, where any two members of Command should call it regardless of what the Captain commands, if there is an active emergency.

 

To before Code Green.

 

NEXT!

 

Usually, if sec wants to search, its easier to get code blue declared than it is to get a warrant. It is certainly faster!

That is arguably bad. Since it leads to code blue being the norm if there is even the slightest reason for it.

Perhaps warrants should be made easier to get, ie: the word of the HoS / Captain should be enough to authorize them.

That might enable green to see more use.

 

 

I agree. Changed to:

 

[*]Random searches are not permitted without express permission by either the Head of Security, Captain or Magistrate. However, searches are still permitted if there is reasonable suspicion of a crime;

 

Changes in bold.

 

NEXT!

 

Translation: Security can't arrest people and haul them to the brig, unless...?

 

The original intent was to follow suit in the whole "relocation" thing. That said, logistics make this pointless, so stricken.

 

Armory?

Gravity Generator?

 

Woops, forgot the Grav Gen.

 

Armory is irrelevant, as it is already locked to hell behind several access-levels and can only normally be accessed via space, unless Security is utterly incompetent.

 

NEXT!

 

Also, this SOP permits, for example, the AI to mass-bolt every secure area on code green at round start.

 

As is currently permitted. Basic Decency stops that, however. People can, people still do not. No real need for change there (huzzah!)

 

NEXT!

 

The vault is not to be opened unless it is to:

1) Secure the nuclear disk or other critical items

2) Check it for damage/breakin

3) Acquire gold for R&D in the absence of miners bringing it in

 

 

Added.

 

NEXT!

 

Not sure the point of this. Security never forcibly relocates people for their safety. Ever.

 

Stricken. See above.

 

NEXT!

 

New:

- I see no guideline along the lines of "crew are requested to be alert for, and report, suspicious activity to their nearest security officer"

- I also see no guideline along the lines of "crew are expected to maintain a healthy sense of caution, e.g: not to deliberately expose themselves to as-yet-unidentified dangers for no good reason.

 

 

Interesting. Added:

 

Personnel are to report any suspicious activity to the nearest member of Security, or use their PDA or Headsets if required;

 

And:

 

Personnel are highly encouraged to exercise caution, even if the threat is only suspected. Following simple safety procedures (such as not going through Maintenance alone) can prevent needless accidents

 

To Code Blue General Crew.

 

And that rhymes.

 

NEXT!

 

Perhaps add: "Security has the right to detain someone for a search should they not comply."

 

Already covered in Sec SOP. That said, cannot hurt to remind non-Sec of that. Added:

 

Security personnel may detain any personnel refusing a random search in order to conduct said search

 

To Code Blue, Red and Gamma.

 

NEXT!

 

Perhaps: "Security is advised to consider searching non-head personnel wandering outside of their departments without good reason."

Relocating them is time-consuming and achieves nothing. Security never does it.

 

 

Stricken. See above.

 

NEXT!

 

Perhaps add "Preferably by the AI, who is best suited for this task".

 

This, I maintain is not necessary, as it is already done mainly by the AI on a roundly basis.

 

NEXT!

 

Perhaps add: "Gamma is called rarely, by CC at their sole discretion. A well-written Fax, signed and stamped by at least one competent head, providing details of a clear and overwhelming threat, is required for CC to consider calling it."

 

Excellent point. Added:

 

Remember, Gamma is rarely called, for good reason. Having a well-written, concise fax that explains the situation to the best of your ability, as well as why it deserves Code Gamma being called, signed and stamped by the Captain or Acting Captain, goes a long way towards ensuring Gamma is provided. Remember, this is for extreme emergencies only.

 

To Code Gamma.

 

NEXT!

 

"And encouraged"

 

Love it. Added.

 

NEXT!

 

Realistically, if GAMMA is called, arming more crew is probably going to be necessary.

 

Removed the "absolutely" from "absolutely necessary".

 

NEXT!

 

Again, trying to keep crew in their departments is pointless.

 

Stricken. See above.

 

NEXT!

 

Since when do nuclear ops ever trigger delta?

I would list the "called by" as: "Malfunctioning (ie: hostile to all non-synthetic life) AI units, and unsalvagable disasters such as uncontained xenomorph outbreak"

 

If it doesn't trigger actual code delta, either it should... or this should not be covered here.

 

In practice, it is the same thing. I will strike it from the Conditions, however.

 

NEXT!

 

Perhaps add: "help from crew should not be turned down, as it could potentially save the station".

 

*nod

 

Added:

 

Any relevant help from station personnel (such as Engineers or Scientists) is not to be turned down

 

To Code Delta Security.

 

NEXT!

 

"In the case of nuclear operatives, ..." actually, what could they possibly do other than defuse the bomb once armed? Prior to that, secure the disk?

 

If the nuke is armed, odds are you do not have the time to do anything about that, and securing the disk is pointless. Better to cut losses and get everyone out.

 

"In the case of a CC-authorized nuclear self-destruct, all personnel are instructed to pray to their deity of choice"

 

Praying is a waste of company time and, therefore, company money. You are therefore stealing money from NanoTrasen A Deathsquad (there is no Deathsquad) police team has been dispatched to your location.

 

NEXT!

 

Why have an entire section labeled irrelevant?

 

It gets the point across.

 

NEXT!

 

... yeah, sure. We'll get right on that. Just... standing here. *runs for his life!*

 

*BANG BANG BANG*

 

NEXT!

 

ICly, I don't think the official CC-issued SOP doc would admit this.

OOCly, its good for people to realize what it means.

I still can't help feeling that this could be better worded, though. Perhaps formatted differently, tacked on, like a scrawled note, to the bottom of the SoP guide, like a rumor or unofficial post-it would be.

 

I have a great idea for this. See the initial post for how it was changed.

 

NEXT!

 

These sections are irrelevant. Yet they are still here. Why?

 

 

Again...

 

Tully, stop the madness!

 

Your pain. It feeds me.

 

Seriously though, stricken, see above.

 

NEXT!

 

"Or major outbreak of a dangerous virus with no/inadequate medical staff?"

 

Added:

 

but is not limited to

 

Because I am lazy.

 

NEXT!

 

... this happens?

 

Yes.

 

NEXT!

 

Maybe tell them HOW they're supposed to turn on their helmet cams...

 

I fear the day we get an ERT that does not know how to click their buttons.

 

Added:

 

(by clicking the button next to their helmet)

 

*shiver

 

NEXT!

 

Most people won't know what a 7-10 is.

 

 

Hence me calling it a 7-10 Blob Organism.

 

NEXT!

 

Of->Before.

 

I find your pedantry to be incredibly sexy.

 

Fixed.

 

NEXT!

 

Shuttle Brig. Yes, I know, same thing. But why call it the Charon throughout when "Shuttle" is clearer?

 

Because I am a nerd and my apostrophe key was broken. Changed.

 

NEXT!

 

So, technically, if I'm HoP, I can give people extra access, even to a department that isn't theirs, so long as it isn't officially a "transfer"

 

Command SOP says otherwise

 

NEXT!

 

"The same applies to any functionally identical job with another title".

 

Bloody rules lawyers...

 

*grumble

 

Added. Also added the Security Pod Pilot (thanks Pinata).

 

NEXT!

 

Searching everyone hired into these roles is not going to accomplish anything. People will learn it and just stash their items first. It just slows down hiring and makes it harder to get sec officers during rounds where they are understaffed.

 

I still maintain this is relevant enough to be kept here. I am certain Sec regulars will agree.

 

NEXT!

 

"given to the person dismissed/demoted, e.g: by radio"

 

 

Good point. Added.

 

NEXT!

 

Uh... really?

Perhaps "deliberately helping the fire/gas to spread". People open them by accident regularly.

 

That was the intention.

 

Changed to:

 

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;

 

Changes in bold.

 

NEXT!

 

"until after the storm has safely passed, due to safety risk"

 

...

 

Meh, sure, why not.

 

Changed to:

 

No repair activities are to be performed until the end of the storm, for safety reasons;

 

Changes in bold.

 

NEXT!

 

"If it is safe to do so, whoever released it, or is thought to have released it, should be detained"

 

This should be a given with Space Law, not SOP.

 

NEXT!

 

When was the last time the supermatter was used?

 

It happens.

 

NEXT!

 

"evacuate off-station via pods, and the eng/science/etc shuttles. Nar-sie is easily able to overpower a large gathering, such as at Escape, so dispersal and fleeing maximizes your chances of survival"

 

 

Added:

 

Using the Supply, Engineering and Science Shuttle Pods is highly recommended. Nar-Sie Constructs, and Nar-Sie Itself, are capable of overpowering large concentrations of people (like the ones normally focused on the Escape Lobby). Dispersing and fleeing increases your chances of survival

 

NEXT!

 

sec pod pilotttttttttttttttttttt

 

See above, Ruskie.

 

NEXT!

 

Code Epsilon? we really shouldn't be talking about this. Death Squad is here! run away!

 

And you missed in situational SOP what to do when there's a wizard or a blob on board.

 

Ammended Code Epsilon.

 

Also, Wizards and Blobs are not that exceptional. OSHA inspectors would cry.

 

NEXT!

 

-Get rid of mentioning warrants for searches on green. Random searches shouldn't be happening either way, and you don't need a warrant to search people who are suspect of a crime.

-The crew don't have the vault's safe combo, so you can't store items inside. The Vault also has things inside the crew might need to use, so banning opening it might be a little questionable.

 

-Code Epsilon having a section in (IC) SoP seems a little odd- After all, it doesn't exist...

 

See above.

 

NEXT!

 

-'All secure areas are to be bolted down' as a blanket rule will probably cause more trouble than it's worth for the crew during red alert. Leaving things like that to command's discretion might be wiser than specifying it in SoP.

 

Good point. Added:

 

Secure Areas may be left unbolted at the discretion of Command personnel

 

To Code Red and Gamma Secure Areas.

 

COFFEE BREAK!

 

.

 

..

 

...

 

....

 

.....

 

......

 

NEXT!

 

I'd also suggest an addition of situation SoP for rev, given how security and command have to act differently in order to combat them:

1. All crew are to comply with security and command requests without question as to not be confused with revolutionaries.

2. Security may implant any crew members who lack an implant, and may exercise force to do so if the crew resists.

3. If revolutionaries have gained control of the station, security may utilize lethal force as needed to regain control of the station.

 

I would rather not add actual round types to "Situational" SOP. That said, considering it is no longer in rotation, how about:

 

1. 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, inspection and subsequent loyalty implantation;

2. All personnel that pass through the Brig must submit to loyalty implantation. Security may also force implantation of random personnel if the number of revolutionaries begins to exceed the number of loyalists;

Lethal force is fully authorized to handle large numbers of revolutionaries

 

 

NEXT!

 

If the person is suspicious enough for the HoS, Captain, or Magistrate to actually go out of their way to sign a search warrant, is it still considered a "Random" search?

 

See above.

 

NEXT!

 

I feel like the chapel should be added to that list; just because it feels REALLY fitting.

 

Stricken. See above.

 

NEXT!

 

...

 

Oh, nothing more. AWESOME.

 

[Garoon]

Situational SOP for Shadowling Ascendants? Just in case you need a guide to tell you how not to get turned into a pile of gore on the floor, or enslaved. Or is it the same as Nar'Sie summoning SOP?

[necaladun]

 

ERT:

 

Some clarification into their ranking.

 

Escape Shuttle:

 

I think instead of not calling for blobs, xenomorphs, etc, it should simply be that CC are to be made aware and may recall it for quarantine. Mostly for OOC reasons - a single xenomorph appearing at 13:50 shouldn't stop a crew transfer.

 

Rev:

...forced implanting I am 100% against. I'd be ok with it being allowed on anyone who commits a crime, but not " of random personnel if the number of revolutionaries begins to exceed the number of loyalists" - as that's an impossible number to gauge.

 

What a "large number" is should be clarified. Lethal force should also only be used if they're actively dangerous.

 

[Coldflame]

Forced implanting is the only way to actually survive a rev round as sec/command after lolflashing takes place- not to mention being implanted doesn't detriment you in any way. I agree that lethal force during rev should be restricted to when loyal crew have become the minority, though.

[necaladun]

 

Forced implanting is the only way to actually survive a rev round as sec/command after lolflashing takes place- not to mention being implanted doesn't detriment you in any way. I agree that lethal force during rev should be restricted to when loyal crew have become the minority, though.

 

OOCly, it's a detriment because you can't join the revolution and get your murderbone on.

ICly, it's an invasive implant shoved into your brain that alters your brain.

 

Once a revolution is confirmed (By a deconversion or a head found) then I'm fine with anyone arrested for any medium+ crime (maybe even minor?) being implanted, but forcing implants on everyone I think is just too far - and I've seen loyalists win without doing it plenty of times.

 

[liran424]

 

Didn't we remove revolution from the rotation?

 

And how do you call NTV Charon to come?

 

[Keroman]

 

And how do you call NTV Charon to come?

 

The NTV Charon is the official corporate designation of the evac shuttle that shows up when called due to out-of-control emergency situations or at the end of a shift.

 

[TullyBBurnalot]

 

Some clarification into their ranking.

 

Added:

 

Emergency Response Teams officially outrank anyone short of a Central Command Officer. Unless their actions are blatantly illegal and against the best interest of NanoTrasen, the station and its crew, their orders are to be followed above anyone else's

 

To ERT Crew Procedures.

 

And:

 

The Emergency Response Team Leader is to be considered the top authority inside the Emergency Response Team. Unless their orders are blatantly illegal and against the best interest of NanoTrasen, the station and its crew, they are to be followed above anyone else's

 

To ERT Procedures.

 

NEXT!

 

I think instead of not calling for blobs, xenomorphs, etc, it should simply be that CC are to be made aware and may recall it for quarantine. Mostly for OOC reasons - a single xenomorph appearing at 13:50 shouldn't stop a crew transfer.

 

Very true. Changed to:

 

In the event of hostile biohazard lifeforms appearing on the station (such as Xenomorphs or Class 7-10 Blob Organisms), Central Command is to be notified before the NTV Charon is called. Failure to do so may lead to the Charon being recalled in order to enforce quarantine. Similarly, Central Command may prohibit calling the Charon in order to handle the biohazard

 

NEXT!

 

...forced implanting I am 100% against. I'd be ok with it being allowed on anyone who commits a crime, but not " of random personnel if the number of revolutionaries begins to exceed the number of loyalists" - as that's an impossible number to gauge.

 

What a "large number" is should be clarified. Lethal force should also only be used if they're actively dangerous.

 

Forced implanting is the only way to actually survive a rev round as sec/command after lolflashing takes place- not to mention being implanted doesn't detriment you in any way. I agree that lethal force during rev should be restricted to when loyal crew have become the minority, though.

 

Entire section changed to:

 

Confirmed Revolution

 

 

1. 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 Loyalty Implantation, at the discretion of the Head of Security, or Acting Head of Security;

2. All personnel that are brigged for Medium Crimes or higher are to receive Loyalty 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

 

 

Changes in bold

 

[Dumbdumn5]

This is all cool, that's all I want to say, but I've been told to be verbose, sooo... This is very,super,amazingly,sorta of, kind of, somewhat, like, ultra, omega, supreme, magic-based, fighter type, level 1 warrior, sleeping carp style, ninja, clan based, chinese bootleg, shady, very very very very very very very very very very very very very very good, I mean holy crap, this is pretty alright in my eyes, mostly because i'm not incredibly enthusiastic about it, but it's ok, because in my eyes, this is really, just super alright with me, because it's cool, I guess, I mean, why not.

[TullyBBurnalot]

 

Nar-Sie Summoning Situational SOP stricken for not being something that Situational SOP should cover.

 

Seriously, its Nar-Sie being summoned. Kiss your ass goodbye.

 

[Vivalas]

The only thing I see missing on a preliminary glance is that you omitted the whole "crew must comply with security requests" and "security can demand enterance into departments during regular patrols" thing on code red and blue. These are useful and I think they should be in.

[TullyBBurnalot]

 

Second one is covered in Sec SOP.

 

First one falls under the "you are expected to know this going in " category.

 

[TullyBBurnalot]

Considering the lack of responses, moving this as finished in... 3 days.

[Vivalas]

 

First one falls under the "you are expected to know this going in " category.

 

 

This is assuming people aren't rule-lawyering assholes, which they are. If you tell someone to do something on code red and tell em "it's because code red, you need to listen to me" they'll go "the fuck it is, show me where officer".

 

Almost all of SOP can be condensed into common sense. If you leave that bit out you can bet people won't follow it.

 

[TullyBBurnalot]

 

For the sake of testing, the following had been added to Code Red/Gamma General Crew SOP:

 

Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew

 

[necaladun]

 

For the sake of testing, the following had been added to Code Red/Gamma General Crew SOP:

 

Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew

 

I think this needs a bit more - if a crewmember doesn't, then what? Can they be detained, charged, fired, airlocked, given a harsh talking to, etc?

 

[Farya]

 

I think this needs a bit more - if a crewmember doesn't, then what? Can they be detained, charged, fired, airlocked, given a harsh talking to, etc?

I think that should depend from Code and amount of damage caused to station and its crew by malcompliance.

If you do shit during Red code - security could just execute you on sight.

During Blue code - security could detain and beat the crap out of you.

But how to describe that perfectly?