Improved column organization in datatables (multiple level grouping, importing asset tree...)

[FN]

In manufacturing is very common to handle datasets with more than a hundred columns, each corresponding to a sensor.

Manufacturing systems have a tree hierarchy that is defined in PI AF (also used in JMP 17 and PI to find the sensor names).

This information is lost when moved to a JMP table.  We open-sourced an add-in to reorganize columns (see image and code here)

However, JMP only allows two levels (parent group and child), which is very limiting in terms of organization and analysis.
For manufacturing data, multiple grouping levels are a must-have or users won't be able to use JMP for their daily tasks in manufacturing (too much information to handle).

Please have a look at PI AF to understand how engineers are used to finding data.

This information can be coded into a column property. This metadata can eventually allow users to swap analysis between assets.

[SamGardner]

Thanks for the suggestion @FN .  We will look into this further.  

[SamGardner]

We feel this is a good idea but it will require some significant development work to make it happen.  When we get closer to this becoming a new feature in JMP we update you.  

[Sarah-Sylvestre]

Hello! This will be available in JMP 19, where you can have column groups of any level of nesting.