The Operator Console is designed as a Product Order centric interface to capture and display order-level data relevant to frontline workers while simplifying entry of Dispatches and Quick Fixes (Operator Fixes). It also allows capture of Comments directly against the Product Order for reference throughout the Order life cycle.
- Users need to be assigned to the Line in order for the Operator to Check-In and see the Line on the Operator Console
- Users are assigned in the Setup > Users > User Details > User Lines OR Setup > Lines > Line Users (if adding multiple users to a line, this is faster).
- The Line must have the Setup > Line > Line Details > Order Based Line setting enabled.
- This requires the above Enable Product Orders (ekanban functionality) for this Line setting to also be enabled.
The star in the upper right can be user to set this page as the active user's home page. The Filter allows you to filter out Inactive Lines, while the Search Bar let's you find a Line quickly. You can select multiple lines and they will be retained for the next time you login.
The Check In button can be used to check users into Lines and Machines as needed to record where they are applying their effort:
Users can also use the Go To Order button to select an order to be started on a particular Line:
This will then navigate the user to the new Operator Portal for the chosen Product Order.
The top left widget shows the Line Status to indicate whether the Line is up or down, and the amount of time it has spent in that condition; the font will be red for Downtime and green for Uptime. Clicking into this widget, pulls up a Dispatch Summary for events that took place that day.
Right of this is the a widget showing the Line Name, Current Build Sequence, and Product. If you've finished an order, you can click 'View Orders' and select the next order to start. Clicking into the widget itself will bring you to the standard Operator Portal page.
The last widget on the right shows the Product Order, the Order Product Code and Description, and progress bar of Order Built vs. Build Quantity.
Note: You can click the hyperlinks within these widgets to pull up the Order, Build Sequence, or Product.
The second row of widgets includes a dropdown to modify the Build Sequence status. You can click into this widget to pull up the Dispatch Summary. Filters have been added for easy navigation.
You can now see the time the Order has been in Status, statuses include:
- Start Changeover/Finish Changeover (Will show up when the order is not WIP)
- Start Cleanup/Finish Cleanup (Will only show up if you have a default cleanup duration on the Product)
- Work In Progress
- Pause (for breaks, etc. - doesn't require a changeover to start the product back up) We'll automatically place a WIP order on Pause at the end of a Shift. This can only be used if the 'Order Based' line setting is enabled and active.
- Place on Hold (requires a changeover to begin the product again; for material shortage, etc)
- Complete Order
The Timer above the Status will change color based on your selection of TEFF or PEFF thresholds. Once the time goes past 24 hours, it switches to displaying Days.
Next to the Status, you'll see a 'Documents' button. This will have any documents that are attached to the Product or Product Orders.
Note: If there is a Notification Bell in RED above the Status Bar, a Dispatch has been created via API and requires a Reason Code. The bell will show the Machine Description along with the reported timestamp. (Open Dispatches API with require reason processing parameter set to true or 1)
The Standard Work widget shows all the checklists requiring completion throughout an operator's shift. If the Widget shows a red exclamation point (!), then there is past due Standard Work. Yellow means there is Standard Work due today.
The Quick Fix Button is where the operator enters a fix that they completed; this may historically have been referred to as an Operator Fix. To simplify entry, the duration defaults to 10 minutes, but can be changed either by selecting a different button, use of the + / - buttons, or through typing.
There is also an occurrence button that can be used to quickly create multiples of the same fix completed. As a note, the number of minutes is not being multiplied by the number of occurrences. Quick Fixes are created as already completed and closed events in the background of the system.
There are also quick selection buttons for the Machine and Reason Code; these are populated by L2L's AI Insights based on recent history of Quick Fixes entered. If the button options are not suitable, a dropdown for the remaining available options can be used. Selection of Reason Code will limit the Machines available and vice versa if those relationships have been established on the Reason Codes.
If you are using Actions/Components/Why codes these will also be populated here as well.
There is an available Comments field as well that can be filled with any other valuable information, and this detail will also be transferred to the Comments modal with an identifier linking it to the specific Quick Fix.
Note: You will need to have specific dispatch type settings enabled for the Reason/Action/Component and Why Codes to populate. See the screenshot below.
Similarly, the Quick Dispatch Button allows a user to rapidly input a Dispatch for help for the most-selected Dispatch Types. This Dispatch will not be created as already completed and closed in the background like the Quick Fix; it will appear in the Dispatch Portal or classic Dispatch List view for resources to respond to.
Comments can also be added without submitting a Quick Fix or Dispatch. All Comments will show up on the Product Order. Selecting the Comments button will open a modal showing a chronological list of Comments entered from each path, and the + button in the upper right can be used to add a general Operator Comment:
Note: If you have Dispatch Questions associated with the Op Fix or the Quick Dispatch Type you choose, a pop-up will appear allowing you to answer the questions prior to submitting the dispatch.
Key Production data of Defects and Actuals are input into the fourth row of widgets. Users can add comments when adding defects. This also includes summary data on the current cumulative Defect quantity for the Product Order as well as the calculated Order % Yield, and then on to right, the Product Order Build Quantity, Built Quantity, and Units Remaining. Hovering over the white boxes will highlight the box in blue, and clicking on the box allows entry of Defects and Actuals, respectively.
Checked In Users show at the bottom of the page. Users can check in or out by clicking on the blue button.
You'll find Current Shift Metrics to the right of Checked in Users. The Metrics will refresh every ~3 mins.
The Widget at the bottom of the page shows the Target vs. Actual Trend if you have the Target vs. Actual graph turned on in the Production Settings. You can see the Current Shift or use the arrows to navigate to the 'Last 4 hours'. Note: This chart only makes sense if you are logging actuals hour by hour, as opposed to order based at the end of the shift.
Note:
- Operators will not be able to Collect Actuals and Scraps on both concurrently using the Operator Portal and the Operator Console.
- Operators will need to be assigned to at least 1 line in order for the Operator Console to show data.
- The Metrics displayed on the Operator Console are Line based Metrics and not Order Based Metrics.
Take a guided tour of the New Operator Portal by clicking here or here for the mobile view.
Watch our Tips & Tricks Video here.