Order Cockpit

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 low code foundation allows it to be tailored to fit the exact workflow required, keeping the interface clean and the work focused how does the operator use 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 see order schedule the order cockpit gives an overview of all the scheduled orders this gives an overview of the upcoming orders & their status start the order & 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 start the equipment this will send the parameter list via the tags provided in master data the operator can start the order; 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 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) report scrap & loss reasons the operator is able to log manually scrap they must add a loss reason to add 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 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 docid 4lvlgo0krulr otwq0ocx module however, the operator can declare the downtime via a fully integrated window in the order cockpit they do not need to switch applications 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 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 consult bom the operator 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) 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 will prevent the operator of re starting the order 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 sections confirmations docid\ snpfhwdahjrxkcrjsthab log finished product output scrap docid\ d9d7b9jftpcwf68rub8jt register & categorize scrap quantities consumptions docid\ r3s51juyaf r 2ytuwzep log material consumptions quality management docid\ etp5ljioladniifbduksk execute product quality inspections checklists docid\ michueoksqbdfdfslmcnn perform checklists and sops downtimes docid 4lvlgo0krulr otwq0ocx register machines stops