Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
We have a few use cases where our team wants to set the min and max within InField based off of existing timeseries.
Scenario - we’re tracking chemical injection and want to input into InField what the injection setpoint is. We’re calculating what that setpoint should be based off of current well production, so the setpoint is more dynamic. Currently the chemical team needs to print out their estimates from that morning, run their calculations and print that out to take with them in on the platform. We’ve created calculated timeseries directly in CDF which is contextualized to the equipment that their entering the value for, but they don’t want to click on the asset to see the target and click back to the checklist - they’d like for it to be part of the template / checklist more as a “one-stop-shop”
Celanese has similar use cases and would be very interested in seeing a solution to this.
Hi@rmaidla !
Thnx for the input. We are re-design the way of exploring data in InField, and one key concept of that is the ability to always explore data in the context of what you are working with. This means that you will have the possibility to investigate a datapoint (such as the calculated one you mention above) while setting the setpoint in the Template/Checklist without being taken away from the context. So hopefully as a more “one-stop-shop”.
I’ve attached an example below of how this could look like when working with a Checklist, with a numerical reading task, on Desktop. If you are building out a Template and setting “min/max” values you will also be able to have that similar exploration context in the same views as the Template.
How does this resonate with the need you describe above?
Br,
Kristoffer
I think what we would like is the ability to have dymanic min and/or max setting on the checklists which is changing based on another set point tag or a calculation or another time series. Currently min and max are static numbers.
Yes, talked with@rmaidla and as I understand they are also after that.
I think right now, the view above should at least make it easier to keep the limits/setpoint up to date although it’s not automatically updated.
Having it automatically updated based on some calculations makes sense to do as well, but I think before we can enable something like that we have to enable a way to keep track of the historic limits, as pointed out by@Brendan Buckbee in the attached hub post. I would assume that when you are analysing the data, and the limit keeps changing, it is important to always know what the limit was in the timeframe where you are analysing the data?
Yes, talked with@rmaidla and as I understand they are also after that.
I think right now, the view above should at least make it easier to keep the limits/setpoint up to date although it’s not automatically updated.
Having it automatically updated based on some calculations makes sense to do as well, but I think before we can enable something like that we have to enable a way to keep track of the historic limits, as pointed out by@Brendan Buckbee in the attached hub post. I would assume that when you are analysing the data, and the limit keeps changing, it is important to always know what the limit was in the timeframe where you are analysing the data?
I think for dynamic infield points we would need to capture the transformation done on the data to set the range, and the point that is used for the transformation. Store that info rather than a constantly updating range. If you change a transformation from ex. System Pressure ± 5psig to System Pressure +-3psig, that calculation gets logged as changed in CDF. That way it can just be back calculated