> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/design/environment/electricity.md). # Electricity The power system is the system that connects and grants functionality through electricity to all aspect of the station. It’s primary purpose is to be a link between objects which produce power and objects which consume power. It is additionally be responsible for the events related to power, such as when a component's power is lost or when it is reconnected. At any time a power consuming or producing object will be able to easily access the electrical information such as available watt’s (or joules per second).

Power system overview

## Terminology & Physics The physics implementation has been partially inspired by a popular simulation game, Oxygen Not Included (ONI). You can find a brief description of the power system in ONI [here](https://oxygennotincluded.fandom.com/wiki/Guide/Power_Circuits).

Power in ONI

The power system will be described electrically with two components, Watts and Joules. The relationship between them is: $$ Watts = Joules/Time $$ In other words, 60W = 60J/s. Watts and joules are different physically speaking, a joule is a measure of energy (or work) used when doing something, and a watt is a measure of how many joules you are using over time (Joules / s). If your microwave says it uses 900 watts then it is consuming 900 joules per second to heat up your microwave dinner. Therefore we can describe electrical relationships really simply and effectively, for example a 60 watt light bulb operated for an hour will use 60J \* 3600s = 360kJof energy. ## Power System The power system will consist of any amount of circuits which allow the connection of producers and consumers, the circuit will be made up of continuous wires and likely Area Power Controllers (APC’s), an APC is a special object which connects to a wire on one side and allows for the wireless connection of energy consuming components to the electrical circuit. The electrical wires will be able to be damaged, repaired, cut, and reconnected. If a wire is damaged too much it will become cut, a player or script can also cut wires. When a wire is cut or reconnected the circuit/s will be updated and refreshed. All objects on a circuit are instantaneously and logically connected to one another, the entire circuit is one logical object and has some given wattage based on its producers and consumers. The station will be made of several circuits which logically separate objects based on geography and power consumption, circuits can be subdivided through objects such as transformers or other objects. A transformer will allow for a high wattage circuit to be subdivided to a low wattage circuit (i.e. a 2000W circuit connected to several 500W circuits) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ss3d.gitbook.io/design/environment/electricity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.