cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X

Track Issues with Pareto Chart Part 1

No ratings

 

 

Use the Pareto Chart Widget to visualize how issues compound to cause problems.

 

GUIDE CONCEPT

 

The Pareto Chart Widget is a useful method of displaying aggregate information. 

In particular, it is often used to display multiple issues and how they combine to form an overall, larger problem. 

 

This can be helpful when trying to determine "easy wins" by pointing out where your efforts will have the greatest impact.

 

 

01-tipc-tile.png

 

YOU'LL LEARN HOW TO

 

  • Create a Data Shape
  • Create a Thing
  • Create an Info Table Property
  • Populate an Info Table with appropriate data for a Pareto Chart
  • Create a Mashup
  • Utilize a Pareto Chart to display issue-aggregation

 

NOTE: This guide's content aligns with ThingWorx 9.3. The estimated time to complete this guide is 30 minutes

 

 

 

Step 1: Scenario

 

In this guide, we'll assume a scenario where a factory is being automated using ThingWorx Foundation. In particular, this factory has some known issues with a robot arm that performs welding at a point along a conveyor belt. 

 

When this welding robot has these issues, the factory line has to come to a complete halt while maintenance is performed on it.

 

Management has decided that these slow-downs are costing enough money that the robot arm needs some extra attention, up to and including modification to help alleviate these maintenance stops. 

 

However, they're not sure what to tackle first. Every issues leads to a slow down, but some happen more frequently than others. 

 

After talking with maintenance, four primary issues are identified, i.e.

 

  1. Excess temperature on the welding end has caused some welds to fail due to simply burning through the material.
  2. Some of the joints need regular lubrication, preventing the arm from getting to the correct location in time as the part moves down the conveyor belt.
  3. The welding filler-material sometimes runs out, causing a stop while more is reloaded.
  4. The welding shielding gas sometimes runs out, causing a stop while more is reloaded.

 

Your task, then, is to start counting the number of times each of these failures occur. In addition, you need to create a small GUI which displays both how often these errors occur, and how they contribute to the overall downtime. 

 

To accomplish this, you'll use a Pareto Chart Widget.

 

 

Step 2: Create Data Shape

 

In this scenario, we'll store the Pareto Chart's data in a Property type called an Info Table.

 

An Info Table is a spreadsheet-like Property, but in order to define the columns of the table, we first have to define a Data Shape. We'll do that in this step.

 

  1. In the left-side navigation, click Browse > Modeling > Data Shapes.

    02-tipc-data-shapes.png

  2. At the top, click + New.

    03-tipc-new-data-shape.png

  3. In the Name field, type TIPC_DataShape.

  4. If Project is not already set, search for and select PTCDefaultProject.

    04-tipc-data-shape-name-02.png

  5. At the top, click Field Definitions.

    05-tipc-field-defs.png

  6. At the top-left, click + Add.

    06-tipc-add-def.png

  7. On the right-side slide-out, in the Name field, type month.
    • Note that you want to leave "Base Type" as the default of "STRING".

  8. Check Is Primary Key.

    07-tipc-issue-type-02.png

  9. Click the "check with a plus" button for Done and Add.

    08-tipc-done-add-02.png

  10. Add each of the following Field Definitions, entering the Name and selecting the Base Type from the drop-down as described in the table:
    • Note that you will NOT enable "Is Primary Key" on any other Field Definitions, as you only need one Primary Key.
    • Note that you will simply click the "check" button for Done after the last entry
      .
      NameBase Type
       excess_temperatureNUMBER
       need_lubricantNUMBER
       low_fillerNUMBER
       low_gasNUMBER

      09-tipc-done-field-defs-02.png

  11. At the top, click Save.

    10-tipc-data-shape-save-04.png

 

Step 3: Create Thing

 

Now that we have our Data Shape, we can create a Thing to hold the collected counts of various issues.

 

As already mentioned, we'll use an Info Table Property, formatted by the previously-created Data Shape, to do so.

 

  1. Click Browse > Modeling > Things.

    11-tipc-things.png

     

  2. Click + New.

    12-tipc-new-thing-02.png

  3. In the Name field, type TIPC_Thing.

  4. If Project is not already set, search for and select PTCDefaultProject.

  5. In the Base Thing Template field, search for and select GenericThing.

    13-tipc-thing-name-02.png

     

  6. At the top, click Save.

    14-tipc-thing-save-02.png
     

     

Add Info Table Property

 

Now that we have our Thing instantiated, we want to both add an Info Table Property, as well as set some Default Values.

 

  1. At the top, click Properties and Alerts.

    15-tipc-properties-02.png

     

  2. Click + Add.

    16-tipc-new-property-02.png

     

  3. On the right-side slide-out, in the Name field, type InfoTable_Property.

  4. Change Base Type to INFOTABLE.

  5. In the Data Shape field, search for and select TIPC_DataShape.
    • Note that the Data Shape field will not appear until you set Base Type to INFOTABLE.

  6. Check Persistent.

    17-tipc-property-name.png

     

  7. At the top-right, click the "check" button for Done.

  8. At the top, click Save.

    18-tipc-property-done.png
     

Set Value of Property

Now that we have a place in which to store spreadsheet-like values, we'll do so manually for testing.

 

  1. On the InfoTable_Property row, under the Value column, click the "pencil" icon for Set value of property.

    19-tipc-set-value-of-property.png

     

  2. On the pop-up, click + Add.

    20-tipc-infotable-add-02.png

     

  3. Enter the following values in each field as per the table below:

    Field NameValue
    month January
    excess_temperature5
    need_lubricant2
    low_filler1
    low_gas2

    21-tipc-first-add-values.png

     

  4. Click Add.

    22-tipc-first-values-added.png

     

  5. Click + Add again, enter the following values, and finish input by clicking Add, as per above.

    Field NameValue
    monthFebruary
    excess_temperature7
    need_lubricant1
    low_filler3
    low_gas2


6. Click + Add again, enter the following values, and finish input by clicking Add, as per above.

Field NameValue
monthMarch
excess_temperature6
need_lubricant2
low_filler1
low_gas1


23-tipc-more-values-added.png

 

7. On the pop-up, click Save.

24-tipc-values-input.png

 

8. At the top, click Save.

25-tipc-final-thing-save.png

 

Step 4: Create Mashup

 

Now that we have our data in-place for testing (and could be connected to automated systems after we finish testing), we need to visualize the data.

 

As mentioned, we'll use a Pareto Chart Widget, but first, we need to create a Mashup into which we can place the Widget.

 

  1. Click Browse > Visualization > Mashups.

    26-tipc-mashups.png

     

  2. Click + New.

    01-uiv92-new-mashup-popup.png

     

  3. Leave the defaults and click OK.

    28-tipc-mashup-geninfo.png

     

  4. In the Name field, type TIPC_Mashup.

  5. If Project is not already set, search for and select PTCDefaultProject.

  6. At the top, click Save
    .
    29-tipc-mashup-saved.png

     

  7. At the top, click Design.

    30-tipcs-design.png

     

  8. At the top-left, click the Widgets tab.

    31-tipc-widgets.png

     

  9. Drag-and-drop a Pareto Chart Widget onto the central Canvas.

    32-tipc-drag-drop-pareto.png

     

  10. At the top, click Save.
 


Click here to view Part 2 of this guide.

Version history
Last update:
‎Mar 07, 2023 02:20 PM
Updated by:
Labels (1)
Contributors