Routing

The Routing task can create routes for a specified employee, for a supervisor and subordinates, for a specified department, or for all employees. Each route lists an employee's work assignments for today, such as inspections, service requests, and work orders, and shows their locations.

Employees can view their routes in the Map Browser or in the Infor Field Inspector mobile app. If an employee's starting and ending locations are specified in the Employee InfoViewer, then the route starts and ends at those locations. Otherwise, the default locations specified in the MapApplications configuration are used.

The work assignments that can be routed are asset inspections, CDR inspections, service requests, and work orders. The order of assignments depends on whether the route is optimized. If the route is not optimized, then the order is based on the type of work assignment, with assignments listed in this order:

  • Asset inspections
  • Building application inspections
  • Business license inspections
  • Case inspections
  • Planning inspections
  • Project application inspections
  • Use application inspections
  • Service requests
  • Work orders

For example, if you create an unoptimized route that includes service requests and work orders, it will first show all assigned service requests and then all assigned work orders.

If the route is optimized, the task uses the ESRI optimizer to organize the assignments so they can be completed in the most efficient manner.

Note: An authentication ID and secret are required to use the optimizer. Specify these values in the MapApplications configuration. The optimizer can process a maximum of 100 locations per route at a time. Most routes will include fewer than 100 locations, but if a route does include more than 100 locations, then only the first 100 will be optimized.

A route can also include assignments with no location data. Assignments with location data are represented by circles, and assignments without location data are represented by squares. If the route is optimized, assignments without location data are shown at the end of the list. In the map, the markers for assignments without location data are shown at the ending location of the route.

Setup

This table describes the Configuration Editor settings that affect this task:

Configuration Comments
MapApplications configuration Contains basic routing settings. The ROUTING node specifies information such as the URL and authentication ID for the ESRI route optimizer, and the starting and ending locations for routes. The default starting and ending location are used if an employee's starting and ending coordinates are not specified in the Employee InfoViewer.

This table describes the Infor Public Sector setup forms that are used to configure this task:

Setup form Comments
Employee InfoViewer Use the Routing tab to specify an employee's starting and ending coordinates.

This table lists the database tables that store setup information for this task:

Table Comments
RESOURCES.EMPLOYEE Stores employees' starting and ending coordinates.

Invocation

The Routing task can be scheduled and invoked manually through the Infor Public Sector Batch Manager form, and it can also be invoked through the console.

This table describes each parameter for this task:

Form Console Description
Create Routes For RouteMode (string) Specifies the employee or employees for whom routes will be created. You can select one of these options:
  • All: Routes will be created for all employees.
  • Employee: A route will be created for a specified employee.
  • Supervisor: Routes will be created for the specified supervisor and all employees who report that supervisor.
  • Department: Routes will be created for all employees in a specified department.
ID RouteFor (string) ID of the employee, supervisor, or department for which routes will be created.
Optimize Routes Optimize (bool) Indicates whether you want to optimize the routes. Optimizing routes organizes the assignments so they can be completed in the most efficient manner.
Asset Inspections Activitytypes (ulong) (Asset Inspections = 64) Select this check box to include asset inspections in the routes that you are creating.
CDR Building Application Inspection Activitytypes (ulong) (Building Inspections = 1) Select this check box to include building inspections in the routes that you are creating.
CDR Business License Inspection Activitytypes (ulong) (License Inspections = 32) Select this check box to include license inspections in the routes that you are creating.
CDR Case Inspection Activitytypes (ulong) (Case Inspections = 16) Select this check box to include case inspections in the routes that you are creating.
CDR Planning Inspection Activitytypes (ulong) (Planning Inspections = 4) Select this check box to include planning inspections in the routes that you are creating.
CDR Project Inspection Activitytypes (ulong) (Project Inspections = 2) Select this check box to include use inspections in the routes that you are creating.
CDR Use Inspection Activitytypes (ulong) (Use Inspections = 8) Select this check box to include in the routes that you are creating.
Service Request Activitytypes (ulong) (Service Requests = 256) Select this check box to include service requests in the routes that you are creating.
Work Order Activitytypes (ulong) (Work Orders = 128) Select this check box to include work orders in the routes that you are creating.

When you invoke this task from the console, use the Activitytypes parameter to specify the types of assignments that you want to include. Each type of assignment is identified by a number, as indicated in the table. Because these numbers are powers of two, they will always produce a unique result when added, which can be parsed to identify the types of records that you want to route. For example, to include building inspections, planning inspections, and project inspections you would enter 7 (1 + 4 + 2).

Data output

This table lists the database tables in which this task adds or updates records:

Table Comments
GIS.ROUTE Stores the routes that are created by the task. Each record in the ROUTE table specifies the route date, the employee for whom the route was created, and the starting and ending locations.
GIS.ROUTEACTIVITY Stores the work activities, such as inspections and work orders, that make up a route.

This table lists the Infor Public Sector forms that you can use to review the results of this task:

Form Comments
Map Browser Shows your routed assignments on the map.
Infor Field Inspector mobile app Shows routed assignments if you select a routed query.