Configuring Maximo Anywhere
Download 1.16 Mb. View original pdf
|
| Configuring Esri maps When Maximo Anywhere is configured to use the Esri map service provider, mobile workers can get a route and directions to their work order locations. Both Esri online and offline maps are supported. Map positioning information Positioning information is the geographical coordinate data that is used to determine the location of a work order and add a position marker to the map. When a work order in the enterprise system contains positioning information, such as a service address, that information is provided to the IBM Maximo Anywhere Work Execution and IBM Maximo Anywhere Inspection apps when the work order is downloaded. If work orders in the enterprise system do not have positioning information, you need to configure the information on the enterprise system. Coordinates or work order positioning information is downloaded from the map service provider to the enterprise system environment. Directions and a route to work orders on the mobile worker's current work list are available when the mobile device is configured with a map service provider. If your enterprise system includes IBM Maximo Spatial Asset Management, positioning information is obtained from work order objects that are linked to a map feature. If Maximo Spatial Asset Management is not in your environment, positioning information is obtained by using non-linked objects. A non-linked object is a work order object that is not linked to a map feature. Non-linked objects therefore provide static geographic coordinate data that you must manually add and store in the service address object. Work order objects that can contain positioning information are work order, service address, asset, and location. When Maximo Spatial Asset Management is available, positioning information is obtained by using linked objects. A linked object is an object in a work order that is linked to a map feature in the designated GIS. A linked object can be the work order object itself, or the associated service address, asset, or location. The link between the object and the map feature enables the auto-locate function to dynamically obtain geographic coordinate data from the GIS when the cron task runs. If you do not use Maximo Spatial Asset Management, positioning information comes from static geographic coordinate data that is added and stored in the service address object. The static geographic coordinate data must be manually added into the Service Address application in Maximo Asset Management. The static geographic coordinate data can also be bulk loaded or migrated into the Integration Framework application in Maximo Asset Management. For offline Esri maps, you need to setup the TPK files for the geographic areas of your organization’s work orders. The service address coordinate system must match the coordinate system that is used to create the offline map. The auto-locate function determines the geographical location of a record by processing the available positioning information in a defined sequence. The sequence is work order linked object, work order X/Y coordinates, work order linked service address, work order service address X/Y coordinates, work order linked asset, work order asset X/Y coordinates, work order linked location, and work order location X/Y coordinates. Configuring Maximo Anywhere 25 You schedule the automatic location of work orders by using the cron task, WoAutoLocateCronTask. The following diagram shows the flow of data between the Maximo Anywhere app on the mobile device, the enterprise system, and the map service provider (Esri ArcGIS server. To provide a route and directions, Maximo Anywhere must be configured to use a map service provider. Esri ArcGIS server Enterprise system Cron task Mobile device Maximo Anywhere app Maximo Anywhere map plugin (native code) Offline map (TPK file) Map service provider API (Esri Android SDK) MobileFirst Server Adapter Directions Coordinates Data (OSLC) Data (JSON over HTTP) Data is downloaded from the enterprise system environment byway of MobileFirst Server to the mobile device. The exchange of data is represented in the diagram by OSLC, between the enterprise system environment and the MobileFirst Server, and by JSON over HTTP, between the MobileFirst Server and the mobile device. Download 1.16 Mb. Share with your friends:
|