Thanks for logging this @shubha k v we’re looking into this feature and will followup as we consider it further.Apologies for the slow response. Unfortunately, we had a bug which meant we did not get this feature idea reflected in our internal system for review until 2 days ago.
Thanks for the feedback @Lok Mun Soh! We’ve captured this feedback and made sure it’s directed to our Extractor team. Will followup here as we further consider the request.
@rsiddha thanks for submitting this idea! By “search and pull SAP work orders”, do you mean searching in the top-bar on infield, instead of going to the asset, then reviewing the work orders there? cc @Kristoffer Knudsen
Hi @Harsha apologies for the slow response. I believe @Diego Antonino was following up with some procedures for how this can be implemented based on the API today.As mentioned, it’s not something we are considering as an update at this time in the Assets API, as our primary focus is on getting Assets fully into Data Modeling, but we will keep this idea open as we can consider it at a later time as a feature on the Data Modeling version of Assets.
Hi @Harsha, thanks for the feedback!Is this something that you’re encountering with the Cognite SAP Extractor or a custom extraction method? If it’s the latter, it should be possible with a few extra lines of code to recreate an asset under a new root node based on the condition that the root is changing. I’m sure @Christian Flasshoff @Diego Antonino and team can advise further if you decide to go that route. However, in general we are not prioritizing features on the “classic” asset resource type at this time as the strategy is to move this to Data Modeling (DM). I will raise this with the team working on bringing Assets into DM to see if this same behavior is expected there.
@rsiddha @Joanna Wiedmann @Marcela Young @crgomez13
Thanks for checking in on this one @Marcela Young. This is certainly still a goal, and high on our priority list to improve the InField login flow. The team is currently dependent on some updates we’re making to our Authorization scheme which are planned to be ready in Q2. Happy to provide more updates here once we have more clarity on the concrete timeline on the InField side.
Hi all! Just some brief updates on this based on a few conversations: General best-practice for web applications based on our engineering team is leveraging browser-based proxy settings as @Eira Monstad mentioned above. As of today, this is the only planned mechanism for supporting proxies for InField, Maintain, and Fusion. However, as mentioned, we do have one web application that uses UDP - InRobot. However, I’ve been informed by the team that there is a fallback to TCP, so that should circumvent the issue. You should be able to test out connection by visiting: https://networktest.twilio.com/ And here are our firewall configs can be found here: https://docs.cognite.com/cdf/admin/allowlist/. For the Remote desktop application does not have a mechanism for configuring a proxy. However, this application is scheduled to be sunset on June 30, 2024 (per this notice and as discussed in a few different release forums). We have brought most of the major features and workflows already into th
@Harsha could you explain what you mean by “we are seeing a high volume of data interfaces and they can be reduced by half”?As @Thomas Sjølshagen mentioned above in the thread, this capability is already present in our new Data Modeling service. Ultimately, this will be the primary place for data like assets and events. I know Celanese still has a blend of classic and new data models, but you have much of your data in FDM or are moving that direction to my understanding. Therefore, I would expect this to not be a significant problem no (even though it may have been 6 - 12 months ago). As you know @rsiddha, we have many additional features we should add to FDM which I believe you would agree should take priority to what will become a legacy data model soon.
Hi Marcela, great feedback! For feature requests like this, it’s best if their posted in the Hub “Product Ideas” section. Those are automatically populated into a Jira backlog for review by the product teams for future development. Feel free to post on Celanese behalf and just either Tag it with “Celanese” or write in the text somewhere. It should automatically be labeled as Celanese and included in reports that we share with Ibrahim, Ram and team.
Thanks for raising this!Seems like a very sensible request. We’re following up with the teams to see if we can include this in the upcoming GA releases of Maintain and InField. Will update here when we know more. FYI @Abram Ziegelaar
Thanks for tagging me on this @rsiddha! We’ve certainly modeled these sort of alarms as events in the past, though that has limitations on filtering/querying that FDM will dramatically improve.Definitely see the benefit in reference guides, and after the release of FDM to General Availability, we’re planning to work on lots of reference guides for common data models. No need to reinvent the wheel if industry standards or common patterns already exist. Out of curiosity @rsiddha and @KC Goh, what sort of volumes of these alarms would you anticipate from a typical process unit? And what sort of information would you typically report on: criticality, frequency, location, type, etc? FYI @Arun Arunachalam @Anders Hafreager
Thanks for reaching out Ram! Solutions Portal, as Philippe pointed out, is still in beta. We are actively exploring the future of the functionality and how we can bring the core features even closer to Cognite Data Fusion. As such, a strict timeline is not yet set for development. Would love to hear more about how you’re thinking to use Solutions Portal, and what’s most critical to your use!
Hi @pratish dewangan! Thanks for your interest, would love to hear more about your use case. We have many ways to support accessing contextual data from Software Development Kits (SDKs), 3rd party tools (e.g., Grafana), Cognite Industry Tools (e.g., Cognite Charts), and more.
Hi Ibrahim! Great to hear from you, and would love to explore this more. It’s a wide ranging topic, and it’s something we’ve tackled with various other clients and believe CDF can and should play a central role in. I would love to hear the thoughts from you and the rest of the community on this in more detail!
Btw, @Stig Grafsrønningen and @Angeliqa Axelsson the geospatial services / API may have some applicability to the fishing vessels and data. Have dug into detail myself, but worth checking out.
The common term these days is “Smart Factory,” but we like to think of what we’re doing as turning our “Smart Factory” into a “Learning Factory.” There is so much more value to realize from an asset that can learn too. Fantastic quote from the podcast! So much opportunity if you can elevate every worker and machine to the same level as the best version of itself on the shopfloor.
Already have an account? Login
Enter your username or 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.