Workbench: The Basics

capture your progress planeus isn’t just a scheduler it’s a modular solution that brings planning, execution, and data management together on a synergetic platform unlike traditional systems that separate planning from execution you can choose to run planeus solely as a planning system and integrate it to your existing shop floor systems (for example, an mes), or; you can have an in system option to integrates planning & ex into a single workflow that’s where the workbench comes in what is workbench? workbench is a lightweight, in system execution module to capture real time operation data fed directly by your shop floor employees it makes workers to enter feedback and time data easily, helping keep your plan and reality perfectly in sync workbench makes planeus a new, different experience — by ensuring your production data is always accurate andconnected to your plan two ways to capture feedback workbench offers two types of interfaces workbench classic the standard interface for entering times and feedback manually workbench terminal the device oriented interface linked to screens or portable devices for precise tracking what’s the difference? in workbench classic , times are recorded as absolute values the workbench terminal includes a start/stop feature for automated time calculation and only work steps (not processes) can be reported both systems share the same data structure, which means you can use them side by side without conflict only resources marked as “allow feedback” are visible in the workbench resources docid\ acbxipcos3d6r5xz1fnbi completed work steps older than 3 weeks will not be shown in workbench basic workbench features here’s what you can do in the workbench to record what’s happening on the shop floor recording disruptions & causses of disruptions sometimes things don’t go as planned in the workbench, you can record disruptions (like machine issues or delays) you’ll choose a causes of disruption from a list of causes, which you’ll find under configuration → disruptions scanning in the workbench if your shop floor uses barcodes, you can integrate it into workbench using this feature once an operator scan a barcode, planeus will instantly find the work step they need to work on, and pull up the right screen for the operator to enter data quickly this saves time, reduces errors, and helps keep production moving smoothly how it works? click the scan icon at the bottom right in the workbench and a window will open for you to enter the barcode you can scan the barcode directly using a scanner enter the barcode number manually if you want to enter the barcode number manually, you can type it using your keyboard, or use the on screen number pad by clicking the keyboard icon in the bottom right corner once you enter or scan the barcode the related work step will open automatically , so you can enter your feedback or data right away generating a routing slip (job ticket) for each production order, a routing slip that includes a barcode can be generated you can find it under planning objects → production orders you can also find it by clicking on the production process in the gantt chart uploading photos & documents sometimes you need to add more than just numbers and in workbench, you can take a photo or upload a file directly when providing feedback or updating progress where to find the upload button? in workbench classic in workbench terminal you can see the uploaded photos and document in history you can also open or download these files later in reporting docid\ xkywbqn1kpuzz8zicplgx , like feedback on work steps or feedback on processes settings for workbench interfaces you can adjust how the workbench works under settings docid\ mcscw6cemmikvg wspxzv auto complete predecessors if this setting is enabled, when you complete a work step, it will automatically complete any earlier steps plausibility checks this feature helps keep your data accurate plausibility checks for work step for work steps it checks that the quantity you report in a work step is less than or equal to what was recorded in the previous step while entering data, you’ll also see the quantity recorded in the previous step plausibility checks for process plausibility checks also work for processes , even though they don’t have quantities in this case, the previous process needs to be finished before you can report the next one plausibility checks for assembly for assemblies you must finish the production order for a sub assembly before you can report feedback on work steps in the main assembly partial quantity checks only apply within the same production order missing predecessor feedback if an earlier work step has no feedback yet, you’ll see an hourglass icon this icon will only appear when plausibility check for work step is enabled under settings > workbench "show not plausible" switch you can use the “show not plausible” switch to hide or show any work steps that are not ready to start yet this switch will only appear when plausibility check for work step is enabled under settings > workbench mandatory fields in the workbench you can make certain fields mandatory for users set "yield" as mandatory field allows feedback on the quantity yield and scrap set "duration" as mandatory field allow feedback on the time consumed by yield, scrap, and disruptions anonymous feedback planeus allows anonymous feedback , where no user name is recorded anonymous entries will have a special icon in the workbench this switch will only appear when add feedback anonymously is enabled under settings > workbench customizable texts & headings you can tailor the workbench to fit your team’s language and preferences you can customize your headings and text in both list and detail views quantity check on completion this setting makes sure that every step in production follows the actual yield from the work step before the remaining quantity always matches what was finished in the last work step the first work step starts with the target quantity provided by the prodcution order yield and scrap automatically reduce the remaining quantity when would you need “quantity check on completion”? this setting is helpful when every step depends on the last one example in assembly, you can’t have more finished products in step 2 than what step 1 actually produced you need to avoid over reporting without the check, someone could accidentally enter a higher yield than what was really available you want a clear chain of quantities each step passes its actual yield to the next one, so the numbers always add up scrap must be tracked correctly if something is scrapped in one step, it won’t magically reappear in later steps example in the workbench terminal a step can only start when the previous step is completed a step can only be completed if yield + scrap = yield from the previous step the target quantity of the first step is based on the full order quantity if the previous step is not completed the “complete operation” button stays grayed out the system fills in the remaining quantity for you if you enter more than the target quantity, you’ll see an error “feedback quantity > target quantity ” the workbench helps you quickly collect real time progress from your shop floor it’s flexible, customizable, and designed to fit the way you work!