--- title: Order Cockpit slug: order-cockpit createdAt: 2026-05-04T09:01:26.866Z --- :::hint{type="info"} **In short:** The Order Cockpit is the single screen where operators run production orders in Mantsu: start and stop orders, book consumption and production, register scrap and downtime, and execute quality checks and checklists. ::: The Order Cockpit is **built around the operator**. Rather than forcing operators to navigate between tools, it brings every action in the MES domain they need into a single, focused view: confirmations, consumption, scrap, quality inspections, downtime registration, and checklist execution are all operated from one place. Because every production environment is different, the cockpit adapts to the use case: operators only see what is relevant for their equipment and the orders planned for it. Where the standard cockpit does not fully match a plant's specific needs, Mantsu's template foundation allows it to be tailored to fit the exact workflow required, keeping the interface clean and the work focused. You can see the cockpit in action at [mantsu.io/product](https://mantsu.io/product). # Who uses the Order Cockpit? The Order Cockpit is aimed squarely at **shop-floor operators**. Supervisors and team leads use it to monitor order progress, and technical personnel use the integrated downtime window to declare stops. Configuration is done by functional administrators in the [Core Manager](docId\:jn2nMWPv2pxEuqLHmop0a). # How do you use the Order Cockpit? The cockpit provides **real-time status updates** that help operators make informed decisions and respond faster. It has a user-centric and data focused view for shopfloor operators. ::::WorkflowBlock :::WorkflowBlockItem See order schedule The Order Cockpit gives an overview of all the scheduled orders. This gives an overview of the upcoming orders & their status. ::: :::WorkflowBlockItem Start the order & ready the equipment An order can be selected in the order list of the cockpit. This opens the dashboard for that order. Orders are filtered depending on the assigned workcenter. The operator can use the order cockpit to send the correct parameters to the machine. This will enable the operator to make less mistakes, and to lose time with manual actions. After all correct settings are sent to the machine, you can start the order in Mantsu and on the HMI; this will set the order to active. If allowed via workcenter configuration, it is possible to run multiple orders in parallel. The operator can switch between the orders via the order list or via a button on the cockpit dashboard. ::: :::WorkflowBlockItem Book material consumption & confirm production The workcenter can be configured in such a way that: - Consumption is booked manually only - Consumption is booked automatically with option to add manually - Consumption is booked automatically only - Production is booked manually only - Production is booked automatically with option to add manually - Production is booked automatically only When booking a production or consumption manually, the operator will need to select a Unit of Measurement (UoM) from the approved list (set in master data). The confirmations will be added to the progression graph where a line for the planned production is viewable; it is immediately visible if the production speed is on track, too slow, or ahead of schedule. Registrations are also added to the log of the order. It allows for a more human readable history of the progression (operator-centric interface). ::: :::WorkflowBlockItem Report scrap & loss reasons You can log scrap manually. You must add a loss reason when registering the scrap. It is also possible to add an automatic counter to add scrap with a loss reason. The scrap (manual & automatic) will be added to the progression graph, so that the accumulation of loss due to scrap can be viewed throughout the operation run. ::: :::WorkflowBlockItem Report downtimes & downtime reasons When production is stopped and the production progress is halted, an automatic or manual downtime can be added. Downtimes are initially created as 'undeclared' downtimes. The operator, or technical personnel, need to assign a downtime reason to each downtime. This allows correct tracking & analysis of lost time during production (unplanned downtimes). Downtimes are managed in the [Downtimes Manager](docId\:edCrFJUVFr92L7hVssPYE) module. However, the operator can declare the downtime via a fully integrated window in the Order Cockpit. They do not need to switch applications. ::: :::WorkflowBlockItem Perform product quality inspections The [Quality Management](docId\:eTP5ljIolAdnIiFBdUkSk) module is integrated into the Order Cockpit. The operator will receive a warning if a test is required. They can open the test via the button in the order cockpit. After completion, the operator will be guided back to the order cockpit view for the order. ::: :::WorkflowBlockItem Perform checklists on the equipment and for SOPs The [Checklists](docId\:mICHuEokSqbDfDfSlMcNN) module is integrated into the Order Cockpit. The operator will receive a warning if a test is required. They can open the test via the button in the order cockpit. After completion, the operator will be guided back to the order cockpit view for the order. ::: :::WorkflowBlockItem Consult BOM You can consult the BOM at all times. The BOM will be shown as it is provided in product master data, or via the production order (e.g.; an exception is loaded as BOM). ::: :::WorkflowBlockItem Stop & complete the order It is possible to stop the order without closing it. E.g.; if an urgent order needs to be started or packaging material is insufficient but the order is not yet completed. The order can be re-started. The order can be completed. This prevents the order from being restarted. The confirmation will be sent to ERP (if applicable). The time that the order ran, is automatically tracked. This includes the start time & the stop time. But also all downtimes. Extra safety measures: the operator would not be able to stop an order in Mantsu if the physical machine is still running. Mantsu integrates with the machine, and gets the live status of the machine. This enables us to live track the status, and use the status to enable certain actions in the order cockpit. ::: :::: *** ## Sections ::::LinkArray{contentSource="CUSTOM"} :::LinkArrayItem [Confirmations](docId\:SNpfHWdAHjRXkCrJsTHaB) Log finished product output ::: :::LinkArrayItem [Scrap](docId\:D9d7B9jFTPcwf68RUb8JT) Register & categorize scrap quantities ::: :::LinkArrayItem [Consumptions](docId\:R3S51JuyAF_R-2yTUwzEP) Log material consumptions ::: :::LinkArrayItem [Quality Management](docId\:eTP5ljIolAdnIiFBdUkSk) Execute product quality inspections ::: :::LinkArrayItem [Checklists](docId\:mICHuEokSqbDfDfSlMcNN) Perform checklists and SOPs ::: :::LinkArrayItem [Downtimes](docId:4LVLGo0KRULr-OTWQ0Ocx) Register machines stops ::: ::::