> 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/production-the-shop-floor.md). # Production: the shop floor The operators and shift supervisors who run the machines and use the apps every shift. **Many of the apps built on UMH are for the people on the shop floor.** Operators and shift supervisors run the machines. They work under [production management](/product/who-we-build-for/production-production-management.md) and rarely build anything on UMH. * An OEE dashboard is for the shift supervisor. They act on it every shift. Operators enter the stop reasons. * A tank alarm is for whoever refills the tank. * A maintenance app for unplanned downtime is for the maintenance technician. Some apps are for knowledge workers instead. They belong to production but do not work at the machines. At one customer, data scientists in production use a tool to track quality defects. Operators can slow an app's adoption by claiming it does not work. An app often means extra work for them at the machine. It can also mean they have to improve how they produce. An app has to work for them at the machine. --- # 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/production-the-shop-floor.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.