Maintain Layers

The feature layers to be maintained in this setting are those coming from an ESRI ARC GIS Server. 


Important: ESRI ArcGIS is a world leading comprehensive solution for managing spatial data and it includes many optional features. In the same way that BlueWorx does not support all SAP Plant Maintenance options, neither does it support all ESRI ArcGIS options. Rather its focus is on supporting common-use features.


Configuration Fields

An explanation of the fields used in this list and maintenance of its values are detailed in the Layer Definition Tab section below.

Functions

FunctionDescription/ Usage
Add a new (ESRI ARC GIS) Layer

Layer Definition Tab

This is accessible on navigation from the Layers list and on Add Layer. It is where the layer and its fields are defined.

Configuration Fields

The following is a definition of the configuration fields:

FieldDescription/ Usage
Layer IDExternally assigned Unique ID for the Feature Layer
DescriptionDescription for the Feature Layer
Endpoint URLThe URL for the map tile source. At this stage, this is limited to ESRI ARC GIS services
Min ZoomThe minimal zoom level at which this layer will be visible where selected. Note that the map service itself can control this setting and the maximum returned number of features
Max ZoomThe maximum zoom level at which this layer will be visible where selected. Note that the map service itself can control this setting and the maximum returned number of features
Tile LevelWhen using maps offline, the Work Order objects with lat/ long coordinates, are used as the basis to download tiles. The Map Defaults > Max Download Zoom and > Work Download Radius controls this. The tiles are downloaded  for each level (i.e. 19, 18, 17, 16, etc) in a 'cone'. Each four tiles at a level are represented by 1 tile at the level above. So 4 tiles at 19 = 1 tile at 18 and 4 tiles at 18 mean 1 tile at 17 - with some optimization in how we process the 'cone'. That ratio is common for map tile images.

Having downloaded the map tiles, the Layers, where set as Downloadable, are downloaded at the Tile Level set by this config setting. It does this by querying the map server using the coordinates (x and y) and this map tile level (z). If this level is set very low, like 19 then a call to the map server will be 4 times more than level 18, and 16 time more than 17 and so on. Calls to the server take time to process (at the map server end) because of the query requirements. So the fewer calls the better. However, this must be tempered by two things:

a. If you have a very intensive asset class, like power line connections, and set this level very high in a built-up area, then the return data would be large, and likely larger than needed to do the job; and

b. It's common practice to restrict the number of features returned per request to 1000.

So, the right setting for this depends on the assets and your user's data needs. Set too low and you may slow down the sync time, set too high and you may take too much data for your needs/ or miss some of the applicable data with the 1000 layer item limit. Set right and you will dramatically improve your sync times.

This is a new setting added with SP6.
OpacityControl the opacity of geometric polygons for feature areas so that they don't obliterate the underlying map of other feature layers. Examples: 1 = solid, .5 = 50% opacity    
DownloadableControl whether this feature layer will be downloaded for offline reference. Only set on where absolutely necessary
Hide Label    Set on to hide the Feature Layers defined label. This can be used where labels overwhelm the display and offer no value to their interpretation
Download Concurrent RequestsWhen the layer can be downloaded, you may control how many concurrent queries will be active at any one time. Defaults to 5
Download TimeoutWhen the layer can be downloaded, you may control how long in seconds to let a query run for before canceling it. This prevents the sync from getting stuck waiting for a slow feature service to respond. Defaults to 4 seconds


Note: If you're consistently getting an error response in your User Syncs for a given map layer then it could be that the server/ service you're calling does not have the capacity to respond in within the Download Concurrency/ Download Timeout settings. You can tune this by making the setting for layer ti perform less concurrent requests and providing a greater timeout. For example 3 and 10.

Conversely if you have a high performance ESRI ARC GIS server/ service you may be able to up the concurrent requests.

Functions

FunctionDescription/ Usage
Once you have maintained a Feature Layer URL, using this function will call the ESRI ARC GIS service definition and allow you to select which fields from that service you want to copy back into the Layer Fields List.
Copy this Layer definition.
Delete this Layer definition.
Save this Layer definition.

Definition Tab - Layer Fields

This configuration is where you specify the pop-up information displayed when you select a feature layer item from a map in BlueWorx. 

Configuration Fields

These fields are defined in the ESRI settings and may contain a large number of fields that are not relevant to display to a user:

FieldDescription/ Usage
OrderThe field display order in the pop-up (Must be unique)
Source Field NameThe service description for the field
Display Field LabelThe label to be displayed in the pop-up
Display FieldDisplay this field in the pop-up
HTTP LinkSwitch on to display the value of this field as a URL
CallbackCreate a button to call back BlueWorx and open this object's record. See related settings below
HTTP Link PrefixOptional maintained with HTTP fields to provide the domain prefix address were not fully provided by the field source.

For example, you might have a Share Point site in which you store photos for Equipment by its SAP Equipment ID. The HTTP prefix might then be something like this:
https://sharepoint.yourcompany.com/photos?equipment=
You would use this on a field with the equipment value and its value would be appended to the URL.
Callback DataUsed in conjunction with the activation of the Call Back Link above. Used where the map service has an Equipment or Functional Location reference. Single results will open a dialog with the SAP object reference, multiple results will return a list to select from.

The reference SAP Technical objects are limited to:
OBJECT: "EQUI" - for Equipment
OBJECT: "FLOC" - for Functional Locations
The reference fields are limited to:
Equipment: EQUIPMENT, TECHID, SORTFIELD, READ_OBJNR, TPLNR, INVENTORY, MANSERNO

Functional Location: READ_OBJNR, STRNO, TPLNR, SORTFIELD, MANSERNO
Examples

1. You have a your legacy asset id stored in your GIS system in the field 'ASSETID'. You have loaded this into SAP in the Technical ID field of the Equipment. The callback parameters you would maintain are:
OBJECT: "EQUI", TECHID: "{ASSETID}"
2. You have maintained your SAP Equipment ID your GIS system in the field 'EQUIPMENT'. The callback parameters you would maintain are:
OBJECT: "EQUI", EQUIPMENT: "{EQUIPMENT}"
3. Tour have maintained your SAP FL Label Field in your GIS System in the Field 'SAPFL'. The callback parameters you would maintain are:
OBJECT: "FLOC", STRNO: "{SAPFL}"
Callback Remove ZerosUsed in conjunction with the above callback settings, when set to true, the comparison between fields to find local objects will ignore leading zeros, this switch would be used when the feature layer field has no leading zeros for a field, but the field in SAP (E.g. Equipment Number) has leading zeros.

Functions

FunctionDescription/ Usage
Add new field

Layer Field Wizard Dialog

In addition to maintaining layer fields manually, the Layer Field Wizard can be used to quickly generate the required fields. Once a layer's URL has been defined, click the Layer Field Wizard button in the bottom left of the screen. This will open a dialog enabling you to search for and select the fields you want to display: