> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/product/who-we-build-for/the-power-user.md). # The power user The primary user of the Management Console, who builds the apps a plant needs. ## Where the power user sits **The power user is the primary user of the Management Console.** They understand the machines, the software and how the business works. They can come from IT, from the [OT team](/product/who-we-build-for/production-ot-team.md), or from an IIoT (Industrial Internet of Things) or digitalization team. The power user gets [IT](/product/who-we-build-for/it-system-administration.md) to install UMH and the [OT team](/product/who-we-build-for/production-ot-team.md) to connect the machines and describe their data. Our [Value Engineers](/culture/working-with-the-rest-of-umh.md#value-engineer) build the first apps with them and train them until they build apps on their own. The power user's manager usually [pays for UMH](/product/who-we-build-for.md#our-users). Power users usually prefer to work in [code](/product/product-standards/code-and-ui.md), because they do a lot in the system and code scales better. ## Apps nobody else would build **With UMH, the power user builds many small apps that would never pay off with a system integrator.** At one customer, an empty tank stopped production. The power user knew this and built an alarm for when the tank runs empty in about 20 minutes. The alarm had a big business impact. A system integrator first needs someone to explain the problem. Project management and other overhead come on top. For a small app like the tank alarm, this costs more than the app is worth. That is why such apps usually never get built without UMH. We at UMH can guess which apps would help and can help the power user build them. Ideally, the power user trains more people in the plant until they can build such apps themselves and become power users too. --- # 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://engineering.umh.app/product/who-we-build-for/the-power-user.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.