Maintain location selection

Also, if the Functional Location that was selected in SAP does not accurately reflect the real location of the work in the 3D model.  Allow the user to edit the 3D location in a similar way as above.

Hi ​@Wrzyszczynski and thank you for taking the time to submit this product idea.

I’ve notified the Product Manager responsible for the Maintain app in CDF, and expect them to either reach out directly, or connect with you through this thread should they have any questions or any further follow-up

Hi Mark,

I think this approach makes a lot of sense. We often encounter cases where work doesn’t necessarily fit neatly under a single FLOC.

What we’ve implemented so far focuses on grid/area zones in 2D. We support annotating and digitizing areas on PDF documents, such as GA plans for platforms. Once digitized, work orders can be associated with these areas through both automated contextualization and manual mapping via a “map to area” feature in Maintain. This functionality can also be extended to static grids in 3D, allowing users to filter work orders for specific grid/area zones and visualize them on the platform in 3D (requires 3D grids from your end).

Additionally, we’re receiving requests to pinpoint work locations efficiently and more accurately on area plans to support tasks like SIMOPS assessments, also with the help of offshore workers. For instance, while you may know the work is happening within a defined area, having the ability to precisely locate the activity would allow for more granular and informed assessments.

I understand Oxy has been exploring this feature. At the moment, implementing digitized grids remains cumbersome (as it needs to be done programmatically). But could it be worth assessing if the above would start solving your needs?

Our decision to start with 2D and not 3D, for creating manual mappings of work orders, was based on its more common use as a location data type across customers.

Please share your thoughts, and feel free to elaborate on the flow or functionality you’re looking to enable.

Marius

Marius,

  Enabling the user to identify the work location in 2D before doing so in 3D seems to be perfectly in line with Agile methodology.  Ultimately, both will be needed in order to have a consistent work method for the end user.  There are two scenarios that drive these requirements: 1) The Work Order is on a piece of equipment that is not an asset within Cognite (Manual valve, minor piece of equipment or pipe such as a drip pan or drain pipe or gate).  These items may be added in the future as an asset.  2) The Work order is on an item that will never be an asset (Replacing grating, handrails, pipe supports, painting an area)  We cannot depend on upgrading the underlying data by adding assets to enable the planner to visualize the location of the work.  Both are important.  In the first case, picking a point achieves the desired outcome.  In the second, the ability to draw a polygon (in both 2D and 3D) will be useful.   

​@Wrzyszczynski, thanks for elaborating! Noted on the 3D & 2D perspective, make sense.

cc ​@Ragnhild Byrkjeland