Forecast cost impacts in Jidoka r8574

This week we’re excited to announce some great new improvements to Jidoka including forecasted cost impact, live calculation testing and the ability to edit multiple process variables.

Live calculations

You can now calculate a live value for your process variables in the Editor. This makes it really quick to test your variable calculations and ensure they are working before deploying them live to Jidoka. You’ll get detailed information to help you quickly identify any problems and suggestions on how to fix them.


Forecasted total cost impact

Jidoka makes it really easy to calculate the profit/cost impact of any business KPI. This week we’ve added the ability to calculate the total forecasted profit/cost impact for a day, week, month and year. This will make it really easy to evaluate the increasing impact of a non-conformance over time.


Editing multiple process variables

We understand that process variables are often dependent on other process variables, leading to hierarchies of calculations. The Editor now lets you work on multiple process variables at the same time, so you can quickly switch between related or dependent calculations. The new tabs allow you to open up as many process variables as you need making it much easier to work on complex dependencies.


To historise or not to historise

We’ve added a new option in the editor which allows you to turn off the historisation of a process variable’s calculation. This can be useful if you have a lot of static or intermediate calculations that you may never want to trend but you need a value calculating for them.


Improved user experience

We’ve made a number of improvements to the user interface that make Jidoka even easier to use. We’ve improved the feedback mechanism which is used to inform you what is happening on screen.

If a process variable is controlled by an external APC system, for example by a DMC, then an Operator would not usually affect it. However it may be required in Jidoka for information purposes, or so a cost can be calculated. These variables will show as follows:


Note that this is to be changed to ‘SYS’ in the latest version so as to be more intuitive.

If an Operator has manually turned a process variable off then this variable will no longer calculate and costs will not be attributed to the variable. In this case you will see the ‘M-Off’ status.


We’ve also added the location of a process variable to the Editor and the hierarchical view making it easier to see where the parameter resides.


Improvements to the Builder

Finally in Sabisu, we’ve improved the way developers add a series of fields to represent a single property for a component in the Builder. These properties no longer display blank rows by default on the component; they now display an “Add New…” feature until a new one is added.


  • We’ve updated the historisation routines in Jidoka to only store calculated values that can be trended by default. For example it is unlikely that you would ever need/want to trend calculations that return status values, so these will no longer be historised by default.
  • We’ve fixed a problem which prevented you using the tab key in the decimal places textbox in the Editor.
  • We’ve updated how numbers are displayed in the parameter list to make them easier to read. This includes comma separators and currency units being displayed in the column title.
  • We’ve fixed an issue in the Builder where formatting HTML syntax such as <tab/> would display in your SQL queries making them difficult to read.
  • We’ve fixed an issue in the Builder that prevented you from using the arrow keys to navigate text fields where an autocomplete is utilised.
  • Combo charts can now properly display more than one series type.
  • Web service calls now utilise a proxy where required for the On-Premise.





Start typing and press Enter to search