Migrated from original mech wiki:

Emergency Component Shut Off System

Explanation

The ECSOS closes off an individual part or component as listed on the Mech Parts page. ECSOS closes important lines, disconnects circuits, and essentially isolates that part from receiving or transmitting further damage of certain types.

Benefits of having a part under the effects of ECSOS include:

Power surges can not breach an ECSOS blocked component

Coolant leaks in the compartment are stopped (restoring pressure to other sections and alleviating any joint under the effects of coolant exposure)

Radiation leaks in a component are slowed from breaching other components through the utilization of the ECSOS.

Normally coolant, power, data, etc. flow through components to other components (such as part 1 communicating with part 3 through data lines in part 2) but with the ECSOS in place in component 2, 1 and 3 can no longer use that component to transfer any material. Information as to the condition of the component shut off is limited depending on the quality of the ECSOS in use. High quality ECSOS can securely transmit damage reports and other information. Low level ECSOS can not even sense if the component is still attached.

Types of ECSOS and their effects

Class A ECSOS

Class A ECSOS can have a variety of beneficial effects to help with their function:

Damage Monitoring

Damage monitoring subsystems can provide real time external damage reports to the operator even though the component is closed off.

Class A ECSOS Internal Sensors

Class A ECSOS Internal Sensors provide real time data of the component as if there was no ECSOS in effect. Internal sensors help provide an internal damage report along with data information from systems inside the component (ie. power ource inside an ECSOSed core casing). However you still can not access or change anything inside the ECSOS area.

ECSOS limited data transmission

ECSOS that have this feature enables very limited transmission of data between components. This can be without a doubt one of the best features available of Class A ECSOS. It allows for the operator to access parts within a component via the command line.

Migrated comments:

Merge ECSOS into EMLS

I definitely think the ECSOS should be part of the EMLS, rather than an addition system. This is exactly the kind of thing the EMLS could do —Josh March 19, 2:25 am
- That’s fine. Just make it an emergency feature of the EMLS but keep in mind you will have to have varying levels of ECSOS features (Class A, Class B, etc.) —Jason March 19, 12:05 pm

ECSOS an Addon?

Is the ECSOS an addon? Or is it a program in the CPU? Where does it go? —Josh March 15, 2:19 pm
- it is an add-on and is mainly a structural type piece. Currently I’m thinking of it as something that is inside every part. I think we should make one add-on apply to all parts/components. \ It seals off the section by disconnecting lines circuits and whatever else it can. It does this with hardware not software. The ECSOS disconnected the parts physically. Like unplugging a lamp. Software in the lamp can’t make itself turn back on. Likewise the lightbulb can’t get power from the wall anymore through the lamp. \ Am I describing this accurately? —Jason March 15, 2:30pm
- Yeah, that’s great. So it’s a hardware addon. I’m going to move it to the Addons section. I think we should keep the possibility of having optional ECSOS for each component. Like you may not be able to afford it for certain parts yet, but you want to get going. You have to admit, it’s far from necessary, just very good to have in emergencies. —Josh, March 15, 3:16 pm

deontologician / spaceship-build