Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Points of Interest that can be created in a Scene may be used for various purposes, such as near-miss incidents, work procedures, and safety notes. However, at the moment, all Points of Interest are displayed in the same color without any distinction.
It would be very helpful if Points of Interest could be tagged and visualized differently in 3D—for example, by displaying them in different colors based on their tags, or by enabling filters to show only Points of Interest with a specific tag, such as near-miss incidents. This would greatly improve usability.
New
【3D】Categorize Points of Interest
Hi
One question I have for you is with regards to the underlying data model. Today we are storing POI data in a local application storage. We have, however, considered re-using the concept of Observations which you might know from InField. This would allow these findings to be stored and retrievable via CDM, and would provide more out of the box options like the ability to upload/attach files and images. What are your current thoughts on re-using the concept of Observations as the data-model for Points of Interest?
Hi
Thank you for the thoughtful answer regarding the data model.
First, as a bit of background, please note that our company does not integrate SAP with InField and does not use Maintain. As a result, we currently view “Observations” primarily as a convenient memo or note-taking feature. We understand that this perspective may differ from that of other customer companies, and we appreciate your understanding on this point.
Based on that assumption, the types of data we envision entering as “Observations” include trouble or anomaly information such as “liquid leakage from a valve” or “abnormal noise from a pump,” as well as near-miss (Hiyari-Hatto) information like “almost tripped over a step during work.” These are not pieces of information that are considered complete at the time they are recorded as an Observation; rather, they are items that are completed only after some form of follow-up action or countermeasure has been taken.
On the other hand, although 3D Points of Interest have a reply feature, within our organization we generally do not use POIs as a place for ongoing discussion. Instead, we consider POIs to contain confirmed or finalized information—for example, in the case of trouble information, details after countermeasures have been implemented, or in the case of near-miss information, clear guidance on how to work safely and what to pay attention to. We do assume that additional information may be appended to a POI after it has been finalized, but the intent is still to store validated information.
From that perspective, we do not think it is inherently negative for Observation data to be linked with 3D. However, at this time, it is difficult for us to clearly articulate specific use cases in which we would actively want to reuse Observations as the data model for 3D Points of Interest.
Apologies if this comes across as a somewhat negative response, and thank you again for taking our feedback into consideration.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.