Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
At Celanese we have got to a limit where our 3D Models are not getting uploaded into CDF because of the limitation for node size data. We would like to preserve the meta data as much as possible.
Need to have an ‘Upsert API’ for Rest interfaces in Cognite, in similar lines as Cognite Java SDK ‘Upsert’. This is to minimize the load and code complexity, particularly in (SAP PO/PI scheduled/real-time) On a high level there are two types of Rest interfaces which are coming from SAP to CDF Assets Functional Location, Equipment Events Notifications, Work order In case of Events, there are two major concerns As Cognite doesn’t have an Upsert API – we need to check every time whether the record exists from PI/PO, and then call create/ update API based on the response. This is doubling the calls from PI PO side. In the event API, as per the documentation available (https://docs.cognite.com/api/v1/#tag/Events/operation/createEvents) the request body schema for assetIds, originating from PI/PO expects internal ID of Cognite. SAP won’t have the Cognite internal id of the equipment (to create/update work order details) The event API doesn’t even have event id to link
We need the ability to create status of assets e.g. out of service, idle in place, on, off, in service and then have the ability to have a different checklists for each status. We also need to have a default status for each round, for example, if a pump is “in service” then it remains in service until the default status is changed to off or out of service.
It would be great if Cognite Reveal can have blue sky and landscape options os the 3D model does not look hanging in a black background.
I am following up on the ability to view native files such as DWG and DGN in Cognite? We were promised that this will be enabled at some point.
Does Cognite CDF have a standard PowerApp connector read/write? if not can we build one.
I would like the ability to search a Time Series Tag and find documents that are contextualized to the time series in Infield. This is not possible today. I can only do this Asset Centric way.
We have an aggregation resolver, but we are unable with this resolver to group the data using the "Foreign key" for another object type as the group key. I think it would be a cool resource to suggest improvements to the tool in the future @Lucas Leocardo Araujo please elaborate more
Current Observations:When joining multiple Tables (in Cognite Raw) the Transformation (query) is taking a very long time Cognite is advising that Cognite Raw is a “Key-Value” store that is not optimized for running queries with multiple joins And that, currently, it is not possible to index or partition data in Cognite Raw to support efficient querying of data Given these limitations: Cognite Raw is not an ideal solution to store unfiltered data from source systems, in its original state Cognite Raw therefore should not be considered as equivalent to a Data or Delta Lake “Raw Zone” or “Bronze Layer” Other issues:It is not easy to debug or identify error conditions for long running transformation queries e.g., a long running query (with multiple joins, with say million records in few tables) can fail after ~10 hours if there are invalid node references all this after reading millions of records – only to fail with an error message that a node reference is invalid or that there is a du
Imagine the Reporting Site and the Reporting Unit entities, 1 reporting site has N reporting units.Currently, If I am in the Reporting Site entity, there is no way to filter reporting sites based on a reporting unit condition using graphql. Like: Give me reporting sites that have reporting units with the name "CLKVAM" to solve that , we need to go to the reporting unit level and query using a reverse edgewhich makes data modeling and querying more complex ... sometimes we even need to do some transformations to remove duplicated data
Missing features for granting or excluding access to certain spaces based on a regex pattern. Permissions for data model and data model instances should be divided into read, write, create, edit delete, and update actions by scope.
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
We really need to get SAP Extractor going: Product Open item Category Ticket # Status Link SAP extractor Support for OData v4 Product idea 3288 Gathering interest cognite-sap-extractor-support-for-odata-v4-0-endpoints-3288 SAP extractor Performance concerns with larger SAP tables SAP extractor Attachments support Product idea 2528 Planned For Development cognite-sap-extractor-attachment-2528 SAP extractor SAP extractor with "nested/dependent" entity queries Product idea 2753 Planned For Development sap-extractor-with-nested-dependent-entity-queries-2753 SAP extractor Cognite SAP extractor: Intgerate with T-codes Product idea 2532 Closed cognite-sap-extractor-intgerate-with-t-codes-2532 SAP extractor Cognite SAP extractor: Splitting large data ranges inputs Product idea 2529 Planned For Development cognite-sap-extractor-splitting-large-data-ranges-inputs-2529 SAP extractor Cognite SAP extractor doesn
Problem Description: Cognite File Extractor for Sharepoint is not able to recursively retrieve documents from a Sharepoint site where site and sub-sites, e.g. Document Control System Alternatives explored: Provide Sharepoint URL as mentioned in documentation for site (Sharepoint Online | Cognite Documentation) Results: no errors, however, no documents are loaded Evaluation: recursion does not occur from site-level down to the document or folder level where Sharepoint stores documents Provide document library and folder / sub-folder Results: working, however, sustainability not ideal Evaluation: will require potentially >100 URLs to be configured and kept up-to-date in case of new document libraries or folders created or deleted Recommended enhancement Recursion from root node (Sharepoint site). E.g. if site URL is provided recursion should go through each sub-site (if present) to document libraries and sub-folders to retrieve documents This should be treated as high-prio
We need the ability to write back Basic Finish dates to SAP from Maintain
We need Semantic Search to do searches at least 500 documents in one shot. We also need simalility index on the results as well as handle pdf and microsoft office files….
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.