Skip to content

Configuring Lines

User interface

In “Machines and Lines”, you can perform the following actions:

Config-lines-intro

① Navigates to the “Configuration” tab
② Adds a new “Line”
③ Edits the existing “Line”
④ Deletes the existing “Line”
⑤ Displays the current step
⑥ Navigates to the previous step

Procedure

To add a new line and the corresponding machines, proceed as follows:

  1. From the navigation tab, click “Configuration” and select “Machines & Lines”.
  2. In “Manage Lines”, click “Add Line”.
    The following window appears: Config-lines-step1
  3. Click “Select Asset”.
    The following window appears: Config-lines-step2
  4. Select the desired “Asset” from the list and click “Select” to auto-fill the asset parameters.
    The following window appears: Config-lines-step3
  5. Using the “Calendar” dropdown option, select the calendar that you have instantiated earlier. Every created calendar will appear here. If the dropdown list is empty, create a calendar before it can be assigned to the line.
  6. Click the “OEE Setup” tab to configure and enable the OEE calculation for the line.
    The following window appears: Config-lines-step4
  7. In the “KPI Targets” area, you can modify the bandwidth for Error, Warning and Success displayed through the colors Red, Yellow, and Green in the gauges. It helps you to identify if you are currently reaching your targets or not. For this, fill in the table in the following way: Config-lines-KPIs
    In the example above, two limits for Warning and Error are defined. The bandwidth for Success follows accordingly. In this example it works following in the following way:
    • OEE Warning: 70%
    • OEE Error: 60%
      The two values given in the configuration always describe the upper levels. Therefore, in the OEE gauge it will display the following colors for the following bandwidths:
    • Red: 0 - 60
    • Yellow: 61 - 70
    • Green: 71-100
      The gauges for Availability, Performance, and Quality follow the same approach.
  8. Perform variable mapping. It has two steps, Operand Mapping and Source Mapping. Each step is described in detail later in this chapter.

If OEE needs to be calculated on a line level, five out of the following six variables must be specified for the line:

Variable Mandatory
Status Mandatory
Order Mandatory
Product Mandatory
Good Parts Mandatory or auxiliary expression
Rejected Parts Mandatory or auxiliary expression
Total Parts Mandatory or auxiliary expression

The following logic applies to the three Quality KPI relevant variables - good parts, rejected parts, and total parts. You need to map two out of three variables, two data points from the asset model and the third one can be calculated through the auxiliary expression which you need to select in that step.

Refer to Section Configuring KPIs to learn about the auxiliary expressions for the Good Parts, Rejected Parts, and Total Parts.

Operand Mapping

In the Operand Mapping, you map the counter variables for the quality KPI calculation - Good Parts, Rejected Parts, and Total Parts.

Config-lines-operandmapping-empty

For each of them, a type needs to be selected. Following are the three different types available:

  • Difference Counter - Only the difference to previous time interval is counted
  • Progressive Counter - The counter increases over time
  • Calculated - This variable will be calculated through the defined auxiliary expression

In the following scenario, good parts and rejected parts are measured through variables as difference counters, while the total parts are calculated through the auxiliary expression. To map these variables, proceed as follows:

  1. Select the Type “Difference counter” using the radio button for the Good Parts.
  2. Click the Pen icon icon on the right side to open the Asset / Aspect selector.
    The following window appears: Config-lines-operandmpapping-aspect
    As shown in the image, the asset “Filling Line” is selected by default. The selection is highlighted in light Blue color. The selection has an influence on the aspects displayed under “Available aspects and variables”.
  3. Click the Plus icon add on the relevant variable. This selection will also be reflected in the area below, where the asset, aspect, and variable can be selected. In this example, the selected asset is “Filling Line”, the aspect is “Machine Values” and the selected variable is “GoodProducts”.
  4. Once the selection is done, click “Select” and the window will get closed.
  5. For Rejected Parts, follow steps 1 to 4 again.
  6. For measuring the Total Parts, proceed as follows:

    a. Select the Type “Calculated” using the radio button.
    This action populates a dropdown field “Select Auxiliary Expression”:
    Config-lines-operandmapping-totalparts
    b. Select “Total Parts” from the dropdown.

The following screen shows the completed Operand Mapping:

Config-lines-operandmapping-done

Note

Two other scenarios are also possible here:
Scenario 1: Rejected Parts and Total Parts measured through variables, therefore the type for Good Parts has to be “Calculated” and the dropdown selection has to be “Good Parts”.
Scenario 2: Good Parts and Total Parts are measured through variables, therefore the type for Rejected Parts has to be “Calculated” and the dropdown selection has to be “Rejected Parts”.

Next step in the configuration is Source Mapping.

Source Mapping

The Source Mapping follows a similar approach compared to Operand Mapping.

Config-lines-sourcemapping-empty

In this step, you define under which variables the order, product, and status information can be found. To achieve this, proceed as follows:

  1. Click the Pen icon icon on the right side to map the Order information.
    The following Asset / Aspect selector window appears: Config-lines-sourcempapping-aspect As shown in the image, the asset “Filling Line” is selected by default. The selection is highlighted in light Blue color. The selection has an influence on the aspects displayed under “Available aspects and variables”.
  2. Click the Plus icon add on the relevant variable. This selection will also be reflected in the area below, where the asset, aspect, and variable can be selected. In this example, the selected asset is “Filling Line”, the aspect is “Machine Values” and the selected variable is “OrderID”.
  3. Once the selection is done, click “Select” and the window will get closed.
  4. For Products, follow steps 1 to 4 again and select the proper variable for the product information.
  5. For Status Mapping, select the applicable Status Mapping from the dropdown “Select Status Mapping”. Config-lines-sourcempapping-statusmapping
    It is recommended to create a Status Mapping in advance. For more information on this topic, refer to Section Configuring Status Mapping.
  6. Once the applicable status mapping selection for the line asset is done, select the variable where to find the status information. This follows the same process as the order and product information.

The following screen shows the completed Source Mapping:

Config-lines-sourcemapping-done

Info

When both Operand and Source mappings are finished, the line asset configuration can be deemed complete.

Any questions left?

Ask the community


Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.


Last update: July 24, 2022