Further improvements to the Jidoka user experience r8676

A word that we return to constantly when asked about our organisation is ‘agile’. Our ability to respond is prized by our customers. This week sees yet another iteration of Jidoka, this time focused on various customer and tester user experience requests.

  • Refresh frequencies have been set on alarm and pareto chart components so that users are kept appraised of the latest data automatically.

  • Attentive users will note that a total improvement opportunity cost has been added to the main process variable table header so its easy to get an overall view of what the total is for the entire system.
  • The main process variable table filters have been moved to allow for more space in the header bar for the upcoming inclusion of advanced table filters and other functionality we will announce soon.
  • A new reporting widget has been added to the Jidoka widget store, this widget allows you to create, view and export to Excel some common types of reports: excursions between certain dates, process variables currently outside limits and process variables currently switched off manually. These reports respect the currently selected location.
  • Added the ability to turn a node in the process view off and on. You need Edit access for this feature.

  • We’ve updated the drag mode in Jidoka to include the option to copy the variable you’re dragging to the same node or a different node. Everything on the variable being dragged is copied apart from the name. If you copy the variable into a node with the same prefix then the parameter number will be incremented. If the parameter is dragged into a node with a different prefix than the new prefix and a new number is used for the parameter name.

  • We’ve added the ability to set the parameters page to auto-refresh on a frequency (currently every 1 minute 30 seconds). All users will find this useful but those who display Jidoka on a large TV screen for general consumption will see particular benefit.

  • The process variable editor has been modified to be more intuitive. If you open a variable which is already open, it’ll now switch to that tab instead of adding it again. Also the user interface deals better with opening multiple new process variable tabs at the same time.

  • Updated the events widget to show events which are context sensitive to the selected node. This link means it’s now obvious which areas are raising the events.

  • The PINP and NC columns have been removed, freeing up real estate to provide a larger default width to the description column. This cleans up the interface. An externally controlled variable is now indicated through the ‘SYS’ badge on the Name column.

  • We’ve updated our audit logging feature in Jidoka to log the Sabisu user name instead of the automatically assumed Windows AD account name.

  • We’ve fixed a problem with the calculate on demand feature of the process variable editor. Under certain circumstances the editor would report that it couldn’t find what you were looking for, particularly when using multiple properties of a variable within the same variable’s calculations. This now responds correctly for existing variables but for new variables you are asked to save your changes first.

  • Another one for the more attentive users; you may have spotted that when you sorted the parameters table using the PONC column it sorted alpha, rather than numerically. Most of the time this had the same result but we’ve updated this so that it always sorts properly. We’ve also updated all of the other numerical columns to sort descending first by default; a logical choice designed to show you your biggest improvement opportunities first.

  • Comments for process variables are now only promoted when the variable is deployed to the live environment.
  • We’ve fixed a problem with moving a process variable where it would be removed from the variable list if moved to the same tree node.


In addition to Jidoka, we’ve also made a couple of important changes to the platform itself:

  • All web service calls now allow impersonation where specified – this is important further support for developers using web services to integrate with different back-end systems.

  • All IP21 data types now map fully to .NET data types. This means that all graph types are supported in all situations and makes life easier for developers exploiting the platform.

 

Start typing and press Enter to search