Standard Operating Procedure overhaul

[Streaky Haddock]

 

THIS THREAD IS ABOUT STANDARD OPERATING PROCEDURE, FOR ALTERATIONS TO SPACE LAW CHECK HERE

 

I was going to do SOP after Space Law, but the two are so intertwined that it's hard to make changes to one without having an impact on the other.

 

http://nanotrasen.se/wiki/index.php/Standard_Operating_Procedure

 

http://nanotrasen.se/wiki/index.php/Legal_Standard_Operating_Procedure

 

These aren't Space Law, but you can still get demoted/fired for not following these. Some of these have been ported, unedited from Bay and are rules which the unimplanted can get brigged for, and the implanted can get jobbanned for. They are rules for how you should do your job, and how you should do them properly. SOP should be broad enough to allow antags to operate but still prevent blatant shittery.

 

This is also the place to discuss the role of paperwork in certain jobs.

 

[Citinited]

 

 

• CE shouldn't be demoted if the singulo is sabotaged, and indeed if the singularity is eating the station then the last thing sec want to bother with is the CE's demotion.

• The code blue / red suit sensors stuff is very hard to enforce and even check, wastes sec's time, and hardly anyone bothers with them anyway. Change to optional.

AIs don't bother with bolting down secure areas, this could probably be removed.

Change the requirement for crew to be in their departments to allow them out of it if needed (e.g. paramedic responding to a medical emergency). Allow crew to be in dorms or the bar.

Allow AIs to be brought back to Centcomm for whatever reason.

Disallow an early shuttle launch if no threat to the shuttle is evident.

 

 

[Hairy Ban Jhankri]

 

• CE shouldn't be demoted if the singulo is sabotaged, and indeed if the singularity is eating the station then the last thing sec want to bother with is the CE's demotion.

• The code blue / red suit sensors stuff is very hard to enforce and even check, wastes sec's time, and hardly anyone bothers with them anyway. Change to optional.

AIs don't bother with bolting down secure areas, this could probably be removed.

Change the requirement for crew to be in their departments to allow them out of it if needed (e.g. paramedic responding to a medical emergency). Allow crew to be in dorms or the bar.

Allow AIs to be brought back to Centcomm for whatever reason.

Disallow an early shuttle launch if no threat to the shuttle is evident.

 

 

Devil's Advocate: How about, no?

 

*Why would the CE not be demoted, if the situation is handled safely? The CE is the head of that department, and that is like the main duty they have, which is to make sure it is not tampered with. They have underlings to boss around, but they need to be on top of their department.

 

*Hard to enforce, rarely is, but why get rid of it? It is more for heads to enforce in their own departments, and the captain to enforce on heads. It is meant to prevent harm, and to enforce them staying where they belong.

 

*They don't bother because they either don't know they are supposed to, or are ordered otherwise. IE, new to the job.

 

*Why would crew be allowed out of the department freely enjoying a drink when there is a station wide threat? Some staff should be ignored, like you said, paramedic, but only at the discretion of the CMO/captain/hos.

 

*Lore wise, AIs are not meant to leave the station unless the integrity of the station is compromised.

 

*SOP states if there are at least two heads dead, then a shuttle call is warranted. This should also be done with a body census, which should be discussed amongst the CMO, who would tally up the bodies, and determine the cause of death, the HOS, which would assess the situation in terms of if security can handle it all, and the captain, who should keep the wellbeing of his crew and the company in mind. So, threat passed? Good! "CMO, give me a body census, ASAP!" "We have 8 recovered bodies, captain! 3 burned in the freak fire accident, 2 died of carp bites, one because of the depressurization due to the carp, and two with blunt trauma to the heads. Scanners show at least two other bodies we could not recover due to suit sensors being offline! One died of toxins overdose, the other died of a combination of burns, blunt trauma, and oxygen loss!" "Good, HOS, give me your assessment, how is security handling things?" "Captain, we brigged 10 people. 3 were simple petty criminals, one case of minor theft of medical supplies, one case of minor assault, and one vandal. We captured and dealt with 4 rogue elements that seem to have infiltrated the corporation. We ascertained what they were here to do, and punished them accordingly. The remaining 3 we have dealt with thus far were employees needing to be demoted, one of which included an officer of mine. Starting with a force of myself, a warden, a detective, and two officers, I hired 3 more officers, one was killed in action and was never recovered, two went to cryo, and one was poor at following instruction . With all of this in mind, it is in my professional opinion that security will not be able to handle much of anything more than escorting the crew to a shuttle, should you ascertain a shuttle is needed." "Good, thank you, HOS, keep up the good work. All other heads, give me a sitrep on your department, ASAP." The captain needs to be on top of the heads, and make sure everything is run smoothly. If people are dead, then things are not okay. Clone or borg them. Still that means something has happened, and the captain needs to make the call for saving lives. Crew should be thought of as people, and not just statistics for the company. Maybe MAYBE the rep would think that way, but they shouldn't, otherwise lawsuits. So, example? Here: Syndis invade station, blow holes in places, a whole department dies within minutes due to depressurization. Those who attempt to save the wounded, dying, and dead, also perish to the lack of air, and the syndis. Let us agree on at least 10 dead WITH station integrity compromised. HOWEVER, most of the boarding team has been killed. As a competent captain or head in general, the shuttle call should be heavily weighed and considered. Bear in mind, you are not just weighing in on IC factors, OOC factors should perhaps be considered too. 10 crew dead, let us agree on 3 antags down, and nobody wants to deal with station damage, even though it COULD be dealt with.

 

[Citinited]

 

*Why would the CE not be demoted, if the situation is handled safely? The CE is the head of that department, and that is like the main duty they have, which is to make sure it is not tampered with. They have underlings to boss around, but they need to be on top of their department.

 

Oh actually I reread SOP and it says demotion if no threat manifests so that's fine. Still, often as CE I find I'm doing other things than sitting in engineering babysittng the engine.

 

*Hard to enforce, rarely is, but why get rid of it? It is more for heads to enforce in their own departments, and the captain to enforce on heads. It is meant to prevent harm, and to enforce them staying where they belong.

 

I get the intent but it's a line that rarely if ever comes up. Either it's enforced and you have most of sec's job on code red being to catch and brig people without suit sensors, or you don't have it enforced in which case why have it in the first place? I feel it's just too stringent to have on a 70+ player round.

 

*They don't bother because they either don't know they are supposed to, or are ordered otherwise. IE, new to the job.

 

True.

 

*Why would crew be allowed out of the department freely enjoying a drink when there is a station wide threat? Some staff should be ignored, like you said, paramedic, but only at the discretion of the CMO/captain/hos.

 

Good point, I guess allowing crew out for a drink is a little nonsensical for a code red. Dorms is fairly central though so I don't think it'dt be that big of a deal, it just feels a little strict for a large server such as ours.

 

*Lore wise, AIs are not meant to leave the station unless the integrity of the station is compromised.

 

Lore-wise, tajarans are loyal and cooperative but I don't really see that in our server population.

 

*SOP states if there are at least two heads dead, then a shuttle call is warranted. This should also be done with a body census, which should be discussed amongst the CMO, who would tally up the bodies, and determine the cause of death, the HOS, which would assess the situation in terms of if security can handle it all, and the captain, who should keep the wellbeing of his crew and the company in mind. So, threat passed? Good! "CMO, give me a body census, ASAP!" "We have 8 recovered bodies, captain! 3 burned in the freak fire accident, 2 died of carp bites, one because of the depressurization due to the carp, and two with blunt trauma to the heads. Scanners show at least two other bodies we could not recover due to suit sensors being offline! One died of toxins overdose, the other died of a combination of burns, blunt trauma, and oxygen loss!" "Good, HOS, give me your assessment, how is security handling things?" "Captain, we brigged 10 people. 3 were simple petty criminals, one case of minor theft of medical supplies, one case of minor assault, and one vandal. We captured and dealt with 4 rogue elements that seem to have infiltrated the corporation. We ascertained what they were here to do, and punished them accordingly. The remaining 3 we have dealt with thus far were employees needing to be demoted, one of which included an officer of mine. Starting with a force of myself, a warden, a detective, and two officers, I hired 3 more officers, one was killed in action and was never recovered, two went to cryo, and one was poor at following instruction . With all of this in mind, it is in my professional opinion that security will not be able to handle much of anything more than escorting the crew to a shuttle, should you ascertain a shuttle is needed." "Good, thank you, HOS, keep up the good work. All other heads, give me a sitrep on your department, ASAP." The captain needs to be on top of the heads, and make sure everything is run smoothly. If people are dead, then things are not okay. Clone or borg them. Still that means something has happened, and the captain needs to make the call for saving lives. Crew should be thought of as people, and not just statistics for the company. Maybe MAYBE the rep would think that way, but they shouldn't, otherwise lawsuits. So, example? Here: Syndis invade station, blow holes in places, a whole department dies within minutes due to depressurization. Those who attempt to save the wounded, dying, and dead, also perish to the lack of air, and the syndis. Let us agree on at least 10 dead WITH station integrity compromised. HOWEVER, most of the boarding team has been killed. As a competent captain or head in general, the shuttle call should be heavily weighed and considered. Bear in mind, you are not just weighing in on IC factors, OOC factors should perhaps be considered too. 10 crew dead, let us agree on 3 antags down, and nobody wants to deal with station damage, even though it COULD be dealt with.

 

I meant disallow an early launch - after the shuttle docks, but before it is scheduled to leave.

 

[TullyBBurnalot]

 

Actually, I'm all for not demoting the Chief Engineer in case Almighty Singuloth gets released. Yes, he's the boss. Yes, he's supposed to be in charge. Then again, all it takes is one idiot/antag Engineer and Almighty Singu-chan is on his way to devouring the station. Technically speaking, you're there to babysit the department, but you should be able to expect a basic level of competency from your crew.

 

That said, if a culprit can't be found, the CE is free to take the blame if he so desires, but firing a Head of Staff for the actions of one of his underlings seems excessive.

 

As for proposed additions:

 

 

1. During Directive 7-10, Security should cease all activies and focus on fighting the blob (getting tired of trying to saw my way to the core while Shitcurity is off arresting the clown for slipping someone with a banana peel);

2. If the station's reason for calling Code Red is 100% confirmed to be dealt with (ie, all antags are dead/loyalty implanted), station should be called down to Code Green, not Code Blue, as all threats are dealt with (pretty minor, but still);

Trials should not be called for offenses that carry a sentence below 20 minutes, period (I've seen Magistrates pull trials for, among other things, petty theft, as a way to stave off boredom);

Any Head of Personnel that hands over all-access to anyone without consulting with Command/Captain first should be demoted and/or terminated;

During Code Red, Medbay should be guarded by at least one Security Officer;

During a viral outbreak, the AI must maintain Medbay's front doors open, and only institute a Virology lockdown. Furthermore, the AI should actively allow infected personnel in, while keeping the ones inside out (because apparently common sense isn't a thing and AIs just lock down Medbay with all the infected outside);

In the aftermath of a meteor shower, Engineering and Atmospherics should be granted emergency access to the affected areas;

I agree that bolting down areas like EVA is frankly pointless. The AI has motion alarms anyway:

Suit Sensors should always be maxed out, regardless of the current Code, because the station is dangerous enough without someone actively trying to murder us;

During Code Red, Security Officers gain emergency access to most of the station (barring Head Offices, Command locations and the AI Core);

During Code Gamma, Security Officers gain emergency all-access (if they're even alive at this point);

Either the ERT or the Shuttle gets called, not both;

Barring active sabotage, the Evacuation Shuttle should not be recalled. Special exception can be made for when the threat is suddenly eliminated via previously unthought-of methods;

When a Code Gamma is called during Directive 7-10, the area furthest from the blob can be used to evacuate remaining crewmembers before the nuke is detonated;

During Code Red, the Captain may overrule anyone's decision regarding anything, provided said decision is within the bounds of sanity/reason. As a result, CentComm will hold the Captain personally responsible for everything that happens during Code Red

 

 

[Sparkyninja]

 

 

1. During Directive 7-10, Security should cease all activies and focus on fighting the blob (getting tired of trying to saw my way to the core while Shitcurity is off arresting the clown for slipping someone with a banana peel);

2. If the station's reason for calling Code Red is 100% confirmed to be dealt with (ie, all antags are dead/loyalty implanted), station should be called down to Code Green, not Code Blue, as all threats are dealt with (pretty minor, but still);

Any Head of Personnel that hands over all-access to anyone without consulting with Command/Captain first should be demoted and/or terminated;

I agree that bolting down areas like EVA is frankly pointless. The AI has motion alarms anyway:

During Code Red, Security Officers gain emergency access to most of the station (barring Head Offices, Command locations and the AI Core);

During Code Gamma, Security Officers gain emergency all-access (if they're even alive at this point);

Either the ERT or the Shuttle gets called, not both;

Barring active sabotage, the Evacuation Shuttle should not be recalled. Special exception can be made for when the threat is suddenly eliminated via previously unthought-of methods;

When a Code Gamma is called during Directive 7-10, the area furthest from the blob can be used to evacuate remaining crewmembers before the nuke is detonated;

During Code Red, the Captain may overrule anyone's decision regarding anything, provided said decision is within the bounds of sanity/reason. As a result, CentComm will hold the Captain personally responsible for everything that happens during Code Red

 

 

 

1. This I agree with on all counts to the point I will verbally abuse any officers not doing so (As a civvie) Or directly order them to (As any form of Command) drop their shittiness. Alas, this is quite hard at times...

2. The issue I have with this one is the fact that, as a Captain, it is perfectly reasonable IC wise to presume that while the immediate threat has passed, a threat may still remain. Just because all known threats have been dealt with doesn't mean there are no more threats. I personally lower to green alert after about 10-20 minutes at blue after a situation calls for Red alert, maybe such a system would be preferable.

Already do this with gleeful brutality towards said HoPs. Would recommend every Captain does the same.

I think the bolting of secure areas should remain, it narrows down the possibilty of those who enter them to those who have the tools, which can help Security should the likes of the AI upload board be stolen, etc etc.

I think that would promote Supersec assholes who end up doing other jobs instead of their own. I think access to other departments for other officers during red alert should remain the job of the HoP and Captain on the advice of the HoS.

Contrary to my previous point, I fully agree with this.

Pretty certain the admuns enforce this, so it would become part of the SOP anyway.

I think the current 5 minute cut off should remain, it gives Command a little lee way with regards to the handling of emergancies, gives other heads time to force the recall should the Captain/AI be Shitlers and allows a recall should the likes of a rare competent Engineer show up and tell Command they can fix the MANY breaches with ease.

7-10 doesn't allow evacuation of crew, full stop. Whenever 7-12 is activated, its intention is to prevent further contamination by destroying EVERYTHING, including all crew. It is presumed Lore wise (I THINK) that any crew that escapes during 7-10 are moped up be a Death Squad later on.

Ehhh, I like and dislike this cause it not even guarenteed now that even loyalty implanted people (Looking at you shitcurity) will follow the Captain's orders, regardless of immediate threat or not. It also promoted the tyranical Captains to supress EVERYONE with little regard to the actual situation. I'd only love it if crew members were punished for denying a reasonable order.

 

 

Any others I haven't specified input to are ones I have no opinion of.