Jump to content

Anderson Robotics GOI - Denied


GLaDOS

Recommended Posts

As per the request of Igneous, I am posting a detailed document of how Anderson Robotics would work as a GOI based Branch.

What do you want to see? - Anderson Robotics implemented as a branch.

Why should we add it? - Because it would add more experiences to be had and more roleplay, lore, etc. to be made and played. In the interest of the server, I think of the current time being, the best branch addition would be one of a GOI similar to how the Chaos Insurgency works, for the purpose that there are already too many Foundation branches to consider adding another because the numbers from all the other branches would deplete/thin out to compensate for the new branch. So I am here to display the best possible candidate I see fit to fill the role of a New GOI Branch in the server.

Anderson Robotics

Quick Summary: It is believed that Anderson Robotics has been founded since somewhere within the 1990s, it only first came to the attention of the Foundation upon the initial capture of SCP- 1360 in 2007, during a raid on para tech warehouse in Seattle and first and foremost became the leader of robotic para-technology. The company has since grown to an estimated net worth of over $20 billion+ and receives over $750 million annually, along with its anomalous capabilities this threat is resourceful and dangerous. 
General Branch Overview: There will be two branches to Anderson Robotics, similar to CI, there will be Engineering (basically R&D) and Robotic Operations (Military). 

-The Engineering Department: The Engineering Department will work to create more combat and utility robots to help around the branch, they will be the ones "creating" robots with the technology the raids recover (see General Expectations below), and writing logs based on their findings creating robotic anomalies. The Engineering Department will also be "repairing" the robots after raids.

-The Robotic Operations Department: The Robotic Operations Department will consist of mainly robots, however, commanding positions will be human because robots are incapable of decision-making like humans are. The robots are expendable, which is why command members will not be in the raids they will be "piloting" the robots remotely, the rest of the robots are "programmed" to follow orders of command.

General Expectations: Anderson Robotics, similar to CI, will raid the foundation every so often with their armed robots. On these raids, they will try to collect intel on Redacted documents pertinent to their goals, such as information on MTF Gamma-13 patrols and confiscated AR technology they mean to recover. They could also kidnap and take hostage Researchers and Technicians (primarily technicians but researchers work too), whereas to gain information, clearance, other means of ransoming. additional Note: CI and AR Cannot Raid at the Same Time and/or Together!

Raids: Per the request of Rangitea, when raiding the cooldown timer would be different and coordinated between GOIs, if CI just finished raiding, there should be a 10-20 minute cooldown timer in between raids. The simple fix to this is having a shorter "in-between" timer, like 15 minutes. If the timer was 15 minutes Anderson Robotics could raid and CIs cooldown timer wouldn't even be up yet, leaving each GOI breathing room to conduct coordinated raids.

Recruitment: The recruitment will be mainly D-Class, by means of escape or raids, they can choose to be trained for either Engineering or Robotic Operations. Should they choose Engineering, they will be trained on their duties and expectations, creating robots, logging robotic anomalies, etc. Should they choose Robotic Operations, this will result in an OOC Player Kill because there is no realistic way to make a human into a robot, they will simply be PK'd as a D-Class and begin a new Life in ARs Robotic Operations, simply because they escaped and got whitelisted. I see an alternate form of recruitment as well, should Technicians be captured and brought to the ARs base they can choose an option, have their IDs stripped and used and killed normally or, be PK'd in Technical to get into Engineering DPT. 

Chain of Command: The chain of command would go like this:

-=GOI Administration=-
The Overseer Council - Councilman ##
The rank that oversees Anderson Robotics and GOIs, sort of like the O5 Council but friendly to GOIs and The Foundation to serve as middle-ground for the two.
(Per the request of Rangitea)

-=High Command=-
Chief Executive Officer - CEO (Head of Entire Branch)

Head of Robotic Operations - HoRO - (Head of Branch)
Head of Engineering - HoE (Head of Breach )

-=Engineering Command=-
Chief of Processing - CoP
Maintainance Manager - MM
Production Supervisor - PS

-=Robotic Ops. Low Command=-
Chief Operator Supervisor - COS
Operations Coordinator - OC
Remote Piloting Overseer - RPO
Piloting Conductor In Charge - PCIC
 

-=Robotic Ops. Enlisted=-
Strategic Assault Operative
Advanced Assualt Operative
Nominal Assault Operative
Conditioned Assault Operative
Default Procedural Operative

-Name Changes: The name changing for this branch will be a little different, for the human aspect of the branch, I.E Engineering, and Robotic Ops. Command, will be the standard format (AR (Rank) Name). Then we have the Robotic Ops. Enlisted, remember they are just AI in the lore, so their name will follow this format: AR (rank) Unit (4 digit callsign), for example: "AR SAO Unit A674" just to make it feel more like roleplay and fun!

Head Quarters/Base Location: I understand that this location I have chosen for this is filled up already, but perhaps that could be reinstituted in a different location, for the location I have chosen is the only unoccupied location in town that worked as far as space goes. So I have chosen and decorated this building to how I envisioned it, just to give an example of how the locations would work. 

Building: Northern Petrol/Yellow Factory
The following are some photos I've taken around the building, to help you envision how it would look and function.

https://imgur.com/a/jLr0aqG - Pictures
Video Tour

Relations With Other Branches: Obviously Anderson Robotics is hostile towards the foundation, this section is specific to Anderson Robotics and Chaos Insurgency. During a raid: Chaos and AR do not have to be hostile towards each other, however, if the other party preventing the other from their goal in any way they can engage the other. When there is no active raid and/or they're on the surface they should not be engaging each other unless there is a valid reason.

Playermodels: Most of the player models used are already in the server and we have plenty of suit and robot models, however, should demand arise for new models I am fully prepared to make a separate suggestion/branch update to get them implemented.

Punishments & Promotions: As every branch has, the lowest rank will be on a One-Strike Policy. Below this, you will see a Chain of Command chart explaining what can and cannot promote/punish and the ranks they can promote/punish up to.

-=High Command=-

Chief Executive Officer
can promote/demote/strike up to any rank.
Chief Operating Officer can promote/demote/strike up to any rank below their own.

Head of Robotic Operations can promote/demote/strike up to any rank below their own, within their branch.
Deputy Head of Robotic Operations can promote/demote/strike up to any rank below their own, within their branch.

Head of Engineering can promote/demote/strike up to any rank below their own, within their branch.
Deputy Head of Engineering can promote/demote/strike up to any rank below their own, within their branch.

-=Engineering Low Command=-
 

Chief of Processing can promote/demote/strike up to Maintainance Manager
Asst. Cheif of Processing can promote/demote/strike up to Production Supervisor
Maintainance Manager can promote/demote/strike up to Engineering Specialist
Production Supervisor can promote/demote/strike up to Trusted Engineer
Coordinating Engineer can promote/demote/strike up to Engineer Intern

-=Robotic Ops. Low Command=-

Chief Operator Supervisor can promote/demote/strike up to Operations Coordinator
Operations Coordinator can promote/demote/strike up to Piloting Conductor
Remote Piloting Overseer can promote/demote/strike up to Advanced Assualt Operative
Piloting Conductor In Charge can promote/demote/strike up to Nominal Assault Operative

Note: Should this be accepted, I will make a separate forum post about the jobs and player models used and anything else required by separate post.

In Conclusion: Thank you for reading to the end of this, I understand this is a lot of information to process. If you have any questions, concerns or editing suggestions or additions feel free to leave a reply explaining this and I'll try my best answer/accommodate them. Thanks again please rate fairly!

What are the advantages of having this? - More roleplay and fun to be experienced as well as more ranks to climb up and enjoy.

Who is it mainly for? - Everyone.

Links to any content - N/A

Edited by GLaDOS
Added Raids Section + New Job (Request of Rang)
  • Gaminglight Love 1

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

+support - i actually like this idea, i'm not sure there are specific Anderson Robotics player models but it should be easy to tell the difference between staff and one of those skinny robots. even though this could be very heavy for the server, i'd like to see it tested out.

(edit) sorry i was just also thinking it'd be cool to hear robot voices in like in VC though that probably isn't possible some people might go that length for the experience

Edited by HammerJack1 24/7
  • Gaminglight Love 1
Link to comment
Share on other sites

Just now, Propane said:

That yellow building is the CI killhouse btw

 

I'll talk to Skela about that if it gets far enough, the bottom line is one of us would have to relocate and I'm fine to work around that, need it come down to it.

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

Just now, [GL] M-2033 said:

+ Support this is an excellent idea that would be very fun to play against as MTF during raids. However would CI and Anderson be able to raid at the same time?

No they cannot raid at the same time, I will specify that now.

 

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

5 minutes ago, Bread said:

Although this is a good suggestion, the server has enough branches as is.

True, but something new is definitely refreshing, as it keeps the attention of players.

Former Security Captain | Former RCF Commander | Former Admin of SCP:RP | King Penguin 
200.gif

Link to comment
Share on other sites

There are a few things I would change (Promo limits and maybe add a rank) but other than that this is a very good suggestion

A few concerns I have if this does get implemented

1. How will raids work? if one branch raids will they both be on cooldown

2. I dont like the idea of the research branch too much as you can see even on the CI side the research branch is very small 

If this branch does get added I might try to get a sorta "site adminy" position that is above both CI and AR like the DOC is with MTF and then above the "GOI admin" is just O5 (as far as COC goes) 

(in case people dont like O5 being in charge keep in mind we already are in charge of CI we just don't interfere unless something bad happens or a new HCMD is needed)

EDIT: Also if this branch does get added this could turn into the problem where both branches have activity problems

"A good soldier obeys without question. A good officer commands without doubt."

 

Link to comment
Share on other sites

Alright, after reading this clearly, I think this is an unnecessary idea, personally. 
CI is already a main group of interest for people to be trained for when they escape.
If you introduce another branch, (or three, as that is what I'm getting from this) either: It will kill CI's influx of new recruits, or will be dead on arrival with most people still joining CI.

We already have 9 branches (or 10 if you include CI RND), and you are proposing adding even more, to split players up further.
As far as I can tell, this is mostly a carbon copy of CI that can raid, capture, and enlist Class-D.
If this branch cannot raid with CI, it would be a cluster of raid after raid, with each one waiting for the other to finish.
If they can raid with CI, it would end up having the same numbers as CI does currently, as I see numbers being split or one-sided to a branch.
This branch is mostly CI, but you steal things that arent there and technicians and Class-D. CI has RND, Military, and the foundation has Technical and their own research team.
All in all, there really is no point to this, because you'd basically be joining CI/Research/Technical but have a robot playermodel.
-Support

Edited by Bread

lol, lmao even

Link to comment
Share on other sites

10 minutes ago, Rangiatea said:

There are a few things I would change (Promo limits and maybe add a rank) but other than that this is a very good suggestion

A few concerns I have if this does get implemented

1. How will raids work? if one branch raids will they both be on cooldown

2. I dont like the idea of the research branch too much as you can see even on the CI side the research branch is very small 

If this branch does get added I might try to get a sorta "site adminy" position that is above both CI and AR like the DOC is with MTF and then above the "GOI admin" is just O5 (as far as COC goes) 

(in case people dont like O5 being in charge keep in mind we already are in charge of CI we just don't interfere unless something bad happens or a new HCMD is needed)

EDIT: Also if this branch does get added this could turn into the problem where both branches have activity problems

Added Specifications + That "Site Adminy" thing you were talking about.

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

 
 
0
 Advanced issue found
 
 
5 minutes ago, Bread said:

This branch is mostly CI, but you steal things that arent there and technicians and Class-D. CI has RND, Military, and the foundation has Technical and their own research team.

Main concern right there ^^

"A good soldier obeys without question. A good officer commands without doubt."

 

Link to comment
Share on other sites

10 minutes ago, Rangiatea said:

1. How will raids work? if one branch raids will they both be on cooldown

2. I dont like the idea of the research branch too much as you can see even on the CI side the research branch is very small 

If this branch does get added I might try to get a sorta "site adminy" position that is above both CI and AR like the DOC is with MTF and then above the "GOI admin" is just O5 (as far as COC goes) 

The head of the branch would most likely have to cooperate with Gamma to get some ideas and middle grounds in, and to the research thing I think would be more shortened down to a sort of "side job" since this branch right now is huge @GLaDOS if you could evaluate on that. Lastly I actually quite like the idea of more SA in general. 

 
 
 
 
3 minutes ago, Bread said:

CI is already a main group of interest for people to be trained for when they escape.
If you introduce another branch, (or three, as that is what I'm getting from this) either: It will kill CI's influx of new recruits, or will be dead on arrival with most people still joining CI.

First, to what was stated above, however, with this in mind, there might be an Application system that would fill up most slots from the start, it's the same as any introduction to any new branch (or dying one)

insert cliched signature 

Link to comment
Share on other sites

Yeah I think it's better to make a side job be the research division, or vice versa with military

@GLaDOS I personally don't mind the ranks but you would have to make the engineering (or military) part of the branch smaller for the other one.

insert cliched signature 

Link to comment
Share on other sites

Update!

-Removed Engineering Enlisted and Low Command Positions
-Reduced the Amount of High Command Positions to the 3 Essentials 

Notes: I'm getting the impression that people think the Engineering branch is R&D. This isn't the case, I compared it to R&D because I had no other reference. Engineering is the people, in the lore, who are creating the robots because they needed a place to come from.

 

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

23 minutes ago, Bread said:

Also, 6 high command slots are way too much. It would be 2-3 High Command and then Heads of side branches that do not count as High Command.

Aren't there also 6 high command slots in Utility?  8 actually just counted

Edited by The Light

Former  

70672632_Untitled(15).png.7d232f74c3ac9624b835990cffc361e8.png

"Foundation Doctor and a Medical Doctor are 2 god damn different things." -Light   "Can you heal me."-Entire Foundation   "Ok Sophia"-Arium

Link to comment
Share on other sites

Update!

-Removed Engineering Enlisted Ranks (To Shorten In For Now)
-Added System Where Engineering Is Left to Command Only
You now have to work up through the Military to eventually get to apply for Engineering.
Changes will be made in future Events!

Edited by GLaDOS

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...