Auto-Location Attention: SAP Field Service Management documentation is now available at the SAP Help Portal. On 31 December 2020, docs.coresystems will no longer be available. Until that time, documentation will NOT be updated in docs.coresystems. In a Nutshell The Auto-Location feature sends continous location data from the technician’s device to Field Service Management in order to improve planning accuracy and transparency. Using this feature mainly makes sense if you rely on automated planning. However, before using this feature there are some factors to be aware of. The use of this feature without proper consideration of impact is discouraged. Sending too many location updates will drain the techicians’ devices batteries and produce a lot of noise for the planning algorithms. This feature is only available for Android and iOS. The Google Maps services embedded in our products are not allowed to be used in the following countries and regions: China, Crimea, Cuba, Iran, Myanmar, North Korea, Sudan, Syria, Vietnam. Due to the restriction of background tracking for iOS, Auto-Location will only work on the iOS application when the app is maintained in the foreground. The feature uses various sources for positioning, thus it is not accurate to the meter. The name Auto-Location has been chosen because it can be configured to use live location as well as event-triggered location updates. A Closer Look In order to utilize the Auto-Location feature, the following steps must be taken: Clarify with an expert which values shall be used for your planning. For example, if your technicians work in an urban area a displacement of 100m is too shallow, it will trigger without actually moving the device due to ray deflection. Also, if your service area has heavy traffic at times an update is not needed every 5 minutes. Choose these values carefully, we recommend using FSM Expert Services for it. Enable the feature by setting CoreSystems.Location.Tracking.Enabled to true. You find more details below as well as in the Admin Portal on how each setting works. According to point (1) set the values of CoreSystems.Location.Tracking.TimeThresholdInMinutes and CoreSystems.Location.Tracking.MinDisplacementInMeters respectively. 🧨 Carefully read their documentation to understand how they work, start with bigger values and narrow it down later. Sync your mobile device to test (of course all technicians also later need to sync to pull the changed Company Setting). Grant access to the location on the mobile device. Enabling on Mobile Device After the relevant company settings have been enabled and configured as well as synced to the devices, you will be able to provide tracking information by giving consent when prompted by the application. The location information can only be sent if the user grants the application access to the location. Company Settings The following settings are managed at Admin > Your company > CompanySettings. Detailed descriptions of the settings (below) are also available there in-place! CoreSystems.Location.Tracking.Enabled Option to enable the feature to request the user’s current location after a certain threshold is reached. This helps to enable tracking of a technician’s location and to be able to see the current location of a technician in a report or on a map. Valid Values Value Effect 0 All Tracking disabled. 1 Continuous tracking enabled. 2 Event-based tracking (workflow steps, check-in). No continuous tracking. CoreSystems.Location.Tracking.TimeThresholdInMinutes This feature works due to privacy restrictions on Android only. Option to define a duration in minutes that represent the time threshold, which, once exceeded, will trigger a request for the user’s current location. This helps to define the frequency for tracking the technician’s location depending on time change. Valid Values Numeric integer value between 5 and 240 (minutes). If the boundaries are neglected the default threshold of 60 min is applied. Example If the value is set to 10, then a new location is requested at least every 10 minutes. It may happen more frequently, if another metric, such as the displacement in meters kicks in first. This can be the case if the user takes 1 minute to travel 200 meters - which would result in a location request every minute. CoreSystems.Location.Tracking.MinDisplacementInMeters Option to define a distance in meters that represent the distance threshold, which, once exceeded, will trigger an update of the user’s current location. This helps to define the frequency for tracking the technician’s location depending on the location change. Valid Values Numeric integer value between 200 and 100000 (meters). If the boundaries are neglected the default distance of 1000 m is applied. Example If the value is set to 1000, then a new location is requested at least every 1 km. It may happen more frequently, if another metric, such as the time threshold defined kicks in first.