Skip to main content

Product Ideas Pipeline

1170 Ideas

Cognite Data Fusion: Use Case for a Reliability Engineer in ChartsGathering Interest

Cognite Charts Team, I would like Cognite Charts and CDF help User From Celanese:Here’s my scenario – I’m going to be as vague as an actual problem statement that we would get – At the base of T109 are a set of pumps.  I believe they basically pump on-spec AA to the tankfarm.  They have been debottlenecked so much over the years that they have essentially run out of NPSH.  The scenario is to find the NPSHa of these pumps and figure out how often they cavitate and cause upsets (I’m honestly not sure if they do or not).  To do a full analysis on that we’re going to need: The NPSHr of the pumps (pump datasheets aren’t in Bentley, so that’s a problem but I can get it) The historical level in T109 and the ability to translate that level in actual ft of elevation The elevation of T109 relative to the pumps (ie, the isometric on the pumps’ suction or 3D) The temp in T109 The flow from the pumps to the tank farm The ability to correlate drops in flow to the T109 level and temperature Any other time series around this system that may be helpful in the analysis We can then build a calculation showing the NPSHa of those pumps and track it in real time – ideally we would also set an alert when it started to get marginalHow would i get to the last point without speniding hours searching in CDF and then flipping to Charts? Any ideas how i can have all that to build the caclulation in Charts. Access to ISOMETRICS, 3D, Time series and P&ID 

HarshaCommitted

Sequencing Extractors , Transformations , downstream objects for Enhanced data WorkflowsPlanned for development

 Add support for sequencing-specific extractors and transformations and downstream objects. This would enable users to easily use tools for common sequencing data processing tasks.Key features:support to trigger data workflows post competition of extraction process.currently it is happening in silos and the transformation assumes that the extraction process is complete and runs on a predefined frequency. we would like to have the transformation triggered post completion of the extraction process  Automated Workflows in relativity enables users to streamline and automate data processing tasks, particularly for sequencing-specific operations. Key features include:Sequencing-Specific Extractors and TransformationsThe system should support specialized extractors and transformations tailored for sequencing data. This allows users to easily process common sequencing data types without manual intervention.Downstream Object SupportAutomated Workflows can now handle downstream objects, enabling more complex data processing pipelines that depend on earlier extraction and transformation steps.Triggered TransformationsA crucial improvement is the ability to trigger transformations immediately upon completion of the extraction process. This replaces the previous model where transformations ran on predefined schedules, regardless of extraction status.Workflow ChainingUsers should be able to  chain multiple workflows together, with each step triggering the next upon completion. This creates a seamless, end-to-end automated process for data handling.Customizable TriggersThe system offers flexible trigger options, allowing workflows to start based on various conditions such as  completion of other workflows. 

Trond SActive

Establishing relations in instantiated data model through visual toolGathering Interest

The tags for Yggdrasil (and other assets) are represented in CDF. There is a need for making relations between tags to build more knowledge into the model.I am working within the maintenance domain, and the simplest use case where such a capability would be needed, is when the CBM engineer want to express that two (or three) sensors are comparable in terms of measurement value. The concept is called transmitter comparison, and it ties into the fact that if two or more transmitters are to output the same value (pressure, temperature, level etc.), you can monitor the outputted values, and perform maintenance if one of the transmitters starts drifting/freezes etc.Currently these kind of relationships are kept in the condition monitoring system, it is difficult to integrate changes to the plant (modifications) that might affect such models. Keeping these relation close to the LCI-data in CDF, would enable governance on this kind of data. CBM engineers currently reads P&IDs to identify relevant transmitter pairs (or trios). When such a relationship is identified, this needs to be expressed in a model (13PT1012 isComparable to 13PST1202). One possible solution would be to add this capability to the Graph with available in DM. There you can filter out relevant tags, and one could imagine being able to “draw lines between tags” to represent the relationship. In the background a transformation could be run on demand, establishing the relationship. As mentioned, this is the simplest use case. If you want to monitor a centrifugal pump, you would like to use approx 20 timeseries from different sensors/electrical equipment, like temperature, power, current, pressure, flow etc. Here you can imagine being able to represent stuff like that the temperature transmitter 13PT1012 can be used to represent the inletPressure of the pump.  Such a generic mechanism would be very helpful in order to represent the connectiveness of things in the process plant, both for maintenance, production optimization and barrier management.