> 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-production-management.md). # Production: production management Who leads production, what they want from an app, and why each plant needs its own applications. **Any application production management buys has to reduce costs or increase revenue.** Production management leads production. Its goal is usually to reduce costs or to increase revenue by producing more. For example, an application for maintenance can reduce unplanned downtime. Production management includes several teams. * The lean or operational excellence team measures and improves how the plant runs, for example its OEE (overall equipment effectiveness). It defines what the numbers mean, such as how OEE is calculated. * Process engineers use a historian to find out why a batch deviated. * Quality, maintenance and energy teams often get results from one system into another, for example production hours written into the maintenance system every night. * Production planning works in SAP. An app can write the produced quantities into it. The [power user](/product/who-we-build-for/the-power-user.md) builds the apps for these teams, often together with our Value Engineers. ## How a plant produces **What production management wants depends on how a company produces.** OEE matters in asset-heavy plants with expensive machines. Personnel costs matter in labour-intensive plants with cheap machines. Some customers have cheap labour and machines but expensive raw materials. They care most about quality and want to reduce scrap. A job shop makes small batches or single pieces, each one different. What matters there is getting each order through on time. So each plant needs applications built for how it produces. Most manufacturing software is tailored to each customer for this reason. With UMH, the power user builds these applications, often in a couple of hours. --- # 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-production-management.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.