In my previous article I discussed how to create a custom widget with the Esri JS 4.3 API. As of the timing around this post, we now currently have version 4.4 of the API to work with. This article will show off SSP’s newest custom widget that is built with the 4.4 API. The widget integrates with SSP Lifecycle Work (formerly WFM) data for work order visualization in the field. Since Lifecycle Work job orders are not stored in a geodatabase, we need a custom widget to interact with the data in a manner that makes sense for field use. The widget simply reads from the location of the work order, which is a series of geographic points that make up the work area polygon.
Our custom widget will dynamically read data from Lifecyle Work related work orders (also called services request or work requests) based on the extent of the map. This would potentially be used by a field worker on a tablet, and they’ll easily be able to view the related work order based on their geographic location. Once they have the work order selected, the field worker can then view the details of the construction related materials used with the work order and record as-built information.
The following screenshot displays two active work orders within the area of the field crew that is assigned to the jobs. The data is coming directly from the Lifecycle Work API, highlighting the polygons that are within the bounds of the map. The work orders and polygons displayed update as the user pans and zooms around the map.
When the user zooms into a particular area it filters the list of Lifecyele Work work orders that are relevant for that location. Alternatively, when zoomed out at a larger scale, the user can tap the work order they would like to zoom to. The Lifecycle Field custom widget displays in the top right corner of the screen. The widget has the ability to automatically draw polygons on the Esri web map view based on the extent of the map.
Work Order Visualization: As-Builting Phase
When logged into the SSP Lifecycle Work application within the company’s secure web portal, the user can view the details of the work order along with the associated work area polygon where the work will be taking place. The following screenshot is the “Enter As-Built” view in Lifecyle Work. The as-built quantity information is not yet populated, only the estimated quantity.
When using mobile field view of the Lifecycle Work job, the user has the ability to view material resources that are to be installed and or removed for the job. The user can filter what materials they are viewing and also have the ability to update as-built quantities and sync those updates to the back office. Those quantities will then be displayed within the Lifecycle Work web portal. In the following view the field worker can search for the material used on the job site and enter the as-built quantity.
Ultimately an owner of the work request will be able to sign off on all as-built information. Once this action is performed Lifecycle has the ability to do any number of custom integration actions to sync important data to various systems throughout the organization. The as-built quantity information is updated to the back office and viewable in the same as-built window we reviewed earlier. You can see now the as-built quantity is verified. The owner of the work order can then complete the final signoff on the as-built information and move the work order to the next status defined in its workflow.
As we continue to evolve the capabilities of Lifecycle, this will hopefully give you a glimpse into the possibilities of increasing productivity and communication between the back office and field crews. All of this being made possible from the flexibility Lifecycle Work give to your organization.
To learn more about the Lifecycle product, you can read about its core capabilities here.