March 26, 2025

Our latest release introduces new features that advance the capabilities and expand the way the ThinkIQ platform is used. 

Process Layout

• Configurable colors on Diagram nodes: You can now select or multi-select (using shift+click) a node and set its color in the Process Layout diagram. The changes are saved and are the same for all users.
  The default color selection of the process layout is based on the hierarchy under the root node of a process layout. Custom color selection allows users to group Nodes that otherwise might have different colors, and differentiate nodes that would share a color. For example, an area named "Forming Line 1" may have many equipment items directly under it. All of the equipment will have the same color, because they share the same parent. Let's say you wanted equipment that help with the "Stacking" process (collects and stacks the finished parts) to be a slightly different color without giving them their own parent, now you can.
• You can now re-arrange the layout structure using the following algorithms:
  • Longest Path
  • Tight Tree
  • Network Simplex
    What are the layout algorithms?

The default layout is determined in the Admin Console where the Process Layout diagram is created and edited. Users who are in the Engineer or Configuration access group can change the layout from the Process Layout diagram itself (in the Platform), and the setting will be retained.

Platform Applications

The Platform applications - Trend, Correlation Analyzer, Process Stability Analyzer, Material Process Analyzer, Timeseries Dashboard and Raw Data Report now use the same building blocks and have a more consistent look and feel and operation:

• The Duration Picker at the top of the application is the same Duration Picker for all apps.
• Information graphic next to the Title that describes the purpose of the application.
• Help graphic at top right for quick help 
• Consistent way to add attributes
• Consistent way to publish to the menu system
• Consistent way to copy and paste information into URLs

Model Explorer

It is now possible to create type without a measurement unit - which implies a specific Quantity Kind - and then assign a measurement unit to an instance of the type independently from the type definition.
In the past, the system was quite restrictive in two ways:

• Types were required to have a default measurement unit and
• Measurement units of instances only allowed selecting engineering units that match the Quantity Kind of the measurement unit on the type.

For example, a measurement unit of inch, or foot, are of the Quantity Kind 'Length quantity'. Any instance of this type would require an attribute to have a measurement unit that is of Quantity Kind 'Length quantity': inch, foot, centimeter, meter, et.al.

These rules have now been relaxed. You can now define types without default measurement units, and when a type doesn't have a measurement unit you can add one a measurement unit at an instance level.

Why?
There are occasions when measurements for a specific instance can differ from another instance of the same type. For example, two silos at a facility can be configured to calculate Content in two different ways: one by feet of air space left in the tank and another by percent full. Both can be used to calculate the total content weight in the silos in a comparable manner.

GraphQL

The Request Header Token menu item has been removed: it is now integrated into the GraphiQL application itself: when you open GraphiQL, you will automatically be prompted to copy and paste an Authorization Token.