Introduction

The 'Operator Runs' page allows you to view and manage the machine runs completed by your company operators. The Operator Runs page will not be visible in the MachineMetrics Settings menu unless the Operator Insight feature is enabled. See the Operators article for more information on the implementation of the Operator Insight feature.

Topics covered in this article

This article includes the following topics:

• Accessing the Operator Runs Page
• Operator Runs Page Layout and Functions
  • Operator Runs Page Layout
  • Operator Runs Page Functions
    • Date/Time Range
    • Manage View
    • Machines
    •  Operator Runs
    • Current Timeline
    • Create New Run
• Managing Operator Runs
  • Example: Operator Run Errors
    • Example: Executive/Manager Intervention Reasons
• Creating a New Operator Run
• Editing an Operator Run

Accessing the Operator Runs Page Back to Top

To access the Operator Runs report, do the following:

1. Login to MachineMetrics. Once logged in, the Dashboards module will open to the default view of the Current Shift Dashboard.
   
   
   
   
2. Hover over Reports in the main navigation and select Operator Runs as highlighted below.
   
   
   
   
3. The Operator Runs report will open as shown in the following section.

Operator Runs Page Layout and Functions Back to Top

The Operator Runs page displays the operators by name on a timeline for each machine indicating the runs they have completed or started on that machine. Operator runs cannot be scheduled into the future.

Operator Runs Page Layout

The following figure presents the layout of the Operator Runs page, with the available functions highlighted.

Operator Runs Page Functions

The following sections describe the functionality provided in the Operator Runs page.

Date/Time Range

The date/time fields above the Operator Runs timeline allows you to set the date and time range that you want to be the outer limits of the operator run data displayed. 

Manage View

The Day/Week/Month buttons above the Operator Runs timeline allow you to set the scope of the timeline view presented. The left and right "arrow" buttons allow you to scroll horizontally through the selected date/time range, and the Today button brings you back to the view that includes the current timeline.

Machines

This column lists name of the machine(s) in MachineMetrics associated with the operator runs.

Operator Runs

Displays the name of the operator associated with the run and allows you to edit the operator run information. See Managing Operator Runs.

Current Timeline

 Indicator of the current day/time. The indicator is progressive and moves with time.

Create New Run

 Button that allows you to create a new operator run. Most operator runs will be created by operators when they log in to a machine (see Operators article). Executive and Manager users at times may need to create a new operator run to address an operator run data mismatch. See Managing Operator Runs.

Managing Operator Runs Back to Top

Operators can make errors in designating their operator runs, such as forgetting to log in or selecting the incorrect operator (see the Operators article for a description of the operator login/logout process). Some of these errors will require the intervention of a MachineMetrics Executive or Manager user. The following section presents an example of how this intervention may be required.

Example: Operator Run Errors

Consider the company in the example shown earlier in this article, with two machines named CNC 115 and CNC 116. There are four operators to cover two daily shifts, which run from 6:00 AM-2:00 PM and 2:00 PM-12:00 AM on each machine:

• CNC 115: Jack Wilson works the 6:00 AM-2:00 PM shift and Jenny Smith works the 2:00 PM-12:00 AM shift.
• CNC 116: John Doe works the 6:00 AM-2:00 PM shift and John Jones works the 2:00 PM-12:00 AM shift.

Review the following Operator Runs example:

In the above Operator Runs example, there are the following errors:

• No Operator: The operator Jack Wilson forgot to log in for the 6:00 AM-2:00 PM shift on Wednesday April 17 for CNC 115.
• Incorrect Operator: The operator John Jones incorrectly selected John Doe instead of himself for the 2:00 PM-12:00 AM shift on Wednesday April 17 for CNC 116.

Example: Executive/Manager Intervention Reasons

Both of the above error examples will require the intervention of a MachineMetrics Executive or Manager user for the following reasons:

• No Operator: Since the shift for which Jack forgot to login is already completely past, Jack cannot address the issue. If the shift was still ongoing, Jack could login and select the "Start of Shift" login option (see Operators article). Since the shift is completely past (as indicated by the current timeline), an Executive or Manager user must create a new operator run to correct the issue.
• Incorrect Operator: Once he is already logged in, John Jones cannot change and correct the name of the logged in operator. In this case, an Executive or Manager user must edit the operator run to correct the issue.

Creating a New Operator Run Back to Top

To create a new Operator Run, do the following:

1. Navigate to the MachineMetrics Operator Runs page.
2. Click the Create Operator Run button at the bottom right of the Operator Runs table.
3. In the Operator Run dialog, select the Machine, Operator, and the Start/End date and time of the shift.
   
   
   
   
4. Click the Save Changes button to create the new operator run for that shift.

Editing an Operator Run Back to Top

 To edit an existing Operator Run, do the following:

1. Navigate to the MachineMetrics Operator Runs page.
2. Click the name of the operator in the Operator Runs table for the shift you want to change.
3. In the Operator Run dialog, make the required changes to the Machine, Operator, and the Start/End date and time of the shift.
   
   
   • Note: You can also click the Delete button to remove the operator run. If you do, you will be prompted with a You Sure? button to confirm that you want the run removed.
     
     
     
     
4. Click the Save Changes button to apply the changes to the operator run.